From 3f0ac820c949e7157a845014d3f9131b84be0fc2 Mon Sep 17 00:00:00 2001 From: str4d Date: Thu, 27 Nov 2014 12:14:02 +0000 Subject: [PATCH] Updated translation strings --- i2p2www/translations/de/LC_MESSAGES/docs.po | 567 +++++++------ .../de/LC_MESSAGES/get-involved.po | 471 +---------- i2p2www/translations/es/LC_MESSAGES/docs.po | 567 +++++++------ .../es/LC_MESSAGES/get-involved.po | 654 +-------------- i2p2www/translations/fr/LC_MESSAGES/docs.po | 567 +++++++------ .../fr/LC_MESSAGES/get-involved.po | 757 +----------------- i2p2www/translations/he/LC_MESSAGES/docs.po | 561 +++++++------ .../he/LC_MESSAGES/get-involved.po | 471 +---------- .../id/LC_MESSAGES/get-involved.po | 471 +---------- i2p2www/translations/it/LC_MESSAGES/docs.po | 562 +++++++------ .../it/LC_MESSAGES/get-involved.po | 472 +---------- .../translations/pt_BR/LC_MESSAGES/docs.po | 566 +++++++------ .../pt_BR/LC_MESSAGES/get-involved.po | 475 +---------- i2p2www/translations/ru/LC_MESSAGES/docs.po | 566 +++++++------ .../ru/LC_MESSAGES/get-involved.po | 714 +---------------- i2p2www/translations/sv/LC_MESSAGES/docs.po | 561 +++++++------ .../sv/LC_MESSAGES/get-involved.po | 471 +---------- pots/docs.pot | 561 +++++++------ pots/get-involved.pot | 459 +---------- 19 files changed, 3238 insertions(+), 7255 deletions(-) diff --git a/i2p2www/translations/de/LC_MESSAGES/docs.po b/i2p2www/translations/de/LC_MESSAGES/docs.po index 8571e8f4..140f7505 100644 --- a/i2p2www/translations/de/LC_MESSAGES/docs.po +++ b/i2p2www/translations/de/LC_MESSAGES/docs.po @@ -13,7 +13,7 @@ msgid "" msgstr "" "Project-Id-Version: I2P\n" "Report-Msgid-Bugs-To: http://trac.i2p2.de\n" -"POT-Creation-Date: 2014-11-16 02:59+0000\n" +"POT-Creation-Date: 2014-11-27 12:12+0000\n" "PO-Revision-Date: 2014-11-16 03:02+0000\n" "Last-Translator: str4d \n" "Language-Team: German " @@ -32,7 +32,9 @@ msgstr "Inhaltsverzeichnis der Technischen Dokumentation" #: i2p2www/pages/site/docs/applications/embedding.html:3 #: i2p2www/pages/site/docs/how/cryptography.html:3 #: i2p2www/pages/site/docs/protocol/i2cp.html:3 +#: i2p2www/pages/site/docs/spec/configuration.html:3 #: i2p2www/pages/site/docs/spec/updates.html:3 +#: i2p2www/pages/site/docs/transport/ntcp.html:3 msgid "November 2014" msgstr "November 2014" @@ -135,7 +137,7 @@ msgstr "" msgid "Managed Clients" msgstr "" -#: i2p2www/pages/site/docs/index.html:44 i2p2www/pages/site/docs/index.html:217 +#: i2p2www/pages/site/docs/index.html:44 i2p2www/pages/site/docs/index.html:222 msgid "Embedding the router in your application" msgstr "" @@ -152,7 +154,7 @@ msgstr "" msgid "hostsdb.blockfile Format" msgstr "hostsdb.blockfile-Format" -#: i2p2www/pages/site/docs/index.html:48 i2p2www/pages/site/docs/index.html:189 +#: i2p2www/pages/site/docs/index.html:48 i2p2www/pages/site/docs/index.html:194 msgid "Configuration File Format" msgstr "Konfigurationsdateiformat" @@ -170,371 +172,383 @@ msgstr "" msgid "Application Development Overview and Guide" msgstr "" -#: i2p2www/pages/site/docs/index.html:72 +#: i2p2www/pages/site/docs/index.html:58 +#: i2p2www/pages/site/docs/api/i2ptunnel.html:55 +#, fuzzy +msgid "I2PTunnel Configuration" +msgstr "Tunnelerzeugung" + +#: i2p2www/pages/site/docs/index.html:74 msgid "SAM Protocol" msgstr "SAM-Protokoll" -#: i2p2www/pages/site/docs/index.html:74 +#: i2p2www/pages/site/docs/index.html:76 msgid "SAMv2 Protocol" msgstr "SAMv2-Protokoll" -#: i2p2www/pages/site/docs/index.html:76 +#: i2p2www/pages/site/docs/index.html:78 msgid "SAMv3 Protocol" msgstr "SAMv3-Protokoll" -#: i2p2www/pages/site/docs/index.html:78 +#: i2p2www/pages/site/docs/index.html:80 msgid "BOB Protocol" msgstr "BOB-Protokoll" -#: i2p2www/pages/site/docs/index.html:81 +#: i2p2www/pages/site/docs/index.html:83 msgid "End-to-End Transport API and Protocols" msgstr "" -#: i2p2www/pages/site/docs/index.html:82 +#: i2p2www/pages/site/docs/index.html:84 msgid "" "The end-to-end protocols used by clients for reliable and unreliable " "communication." msgstr "" -#: i2p2www/pages/site/docs/index.html:84 +#: i2p2www/pages/site/docs/index.html:86 #: i2p2www/pages/site/docs/api/streaming.html:2 msgid "Streaming Library" msgstr "Streamingbibliothek" -#: i2p2www/pages/site/docs/index.html:86 +#: i2p2www/pages/site/docs/index.html:88 msgid "Streaming Protocol Specification" msgstr "" -#: i2p2www/pages/site/docs/index.html:88 +#: i2p2www/pages/site/docs/index.html:90 msgid "Streaming Javadoc" msgstr "" -#: i2p2www/pages/site/docs/index.html:90 +#: i2p2www/pages/site/docs/index.html:92 #: i2p2www/pages/site/docs/api/datagrams.html:2 msgid "Datagrams" msgstr "Datagramme" -#: i2p2www/pages/site/docs/index.html:92 +#: i2p2www/pages/site/docs/index.html:94 msgid "Datagram Javadoc" msgstr "" -#: i2p2www/pages/site/docs/index.html:95 +#: i2p2www/pages/site/docs/index.html:97 msgid "Client-to-Router Interface API and Protocol" msgstr "" -#: i2p2www/pages/site/docs/index.html:96 +#: 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" "Traditionally used only by Java applications and higher-level APIs." msgstr "" -#: i2p2www/pages/site/docs/index.html:101 +#: i2p2www/pages/site/docs/index.html:103 msgid "I2CP - I2P Control Protocol / API overview" msgstr "" -#: i2p2www/pages/site/docs/index.html:103 +#: i2p2www/pages/site/docs/index.html:105 msgid "I2CP Specification" msgstr "I2CP-Spezifikation" -#: i2p2www/pages/site/docs/index.html:105 +#: i2p2www/pages/site/docs/index.html:107 msgid "I2CP API Javadoc" msgstr "" -#: i2p2www/pages/site/docs/index.html:107 -#: i2p2www/pages/site/docs/index.html:136 +#: i2p2www/pages/site/docs/index.html:109 +#: i2p2www/pages/site/docs/index.html:139 msgid "Common data structures specification" msgstr "" -#: i2p2www/pages/site/docs/index.html:109 -#: i2p2www/pages/site/docs/index.html:138 +#: i2p2www/pages/site/docs/index.html:111 +#: i2p2www/pages/site/docs/index.html:141 msgid "Data Structures Javadoc" msgstr "" -#: i2p2www/pages/site/docs/index.html:112 +#: i2p2www/pages/site/docs/index.html:114 msgid "End-to-End Encryption" msgstr "Ende zu Ende Verschlüsselung" -#: i2p2www/pages/site/docs/index.html:113 +#: 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." -#: i2p2www/pages/site/docs/index.html:115 +#: i2p2www/pages/site/docs/index.html:117 msgid "ElGamal/AES+SessionTag encryption" msgstr "ElGamal/AES + SessionTag Verschlüsselung" -#: i2p2www/pages/site/docs/index.html:116 -#: i2p2www/pages/site/docs/index.html:149 +#: i2p2www/pages/site/docs/index.html:118 +#: i2p2www/pages/site/docs/index.html:152 msgid "ElGamal and AES cryptography details" msgstr "ElGamal und AES Verschlüsselungsdetails" -#: i2p2www/pages/site/docs/index.html:119 +#: i2p2www/pages/site/docs/index.html:121 #: i2p2www/pages/site/docs/how/tech-intro.html:15 #: i2p2www/pages/site/docs/how/tech-intro.html:329 msgid "Network Database" msgstr "Netzwerk Datenbank" -#: i2p2www/pages/site/docs/index.html:120 +#: i2p2www/pages/site/docs/index.html:122 msgid "" "Distributed storage and retrieval of information about routers and " "clients." msgstr "" -#: i2p2www/pages/site/docs/index.html:122 +#: i2p2www/pages/site/docs/index.html:124 msgid "Network database overview, details, and threat analysis" msgstr "" -#: i2p2www/pages/site/docs/index.html:123 +#: i2p2www/pages/site/docs/index.html:125 msgid "Cryptographic hashes" msgstr "Kryptografische Hashwerte" -#: i2p2www/pages/site/docs/index.html:124 +#: i2p2www/pages/site/docs/index.html:126 msgid "Cryptographic signatures" msgstr "Kryptografische Signaturen" #: i2p2www/pages/site/docs/index.html:127 +#: i2p2www/pages/site/docs/index.html:186 +#, fuzzy +msgid "Router reseed specification" +msgstr "Protokollspezifikation" + +#: i2p2www/pages/site/docs/index.html:130 msgid "Router Message Protocol" msgstr "Router Nachrichten Protokoll" -#: i2p2www/pages/site/docs/index.html:128 +#: i2p2www/pages/site/docs/index.html:131 msgid "" "I2P is a message-oriented router. The messages sent between routers are " "defined by the I2NP protocol." msgstr "" -#: i2p2www/pages/site/docs/index.html:130 +#: i2p2www/pages/site/docs/index.html:133 msgid "I2NP - I2P Network Protocol Overview" msgstr "" -#: i2p2www/pages/site/docs/index.html:132 +#: i2p2www/pages/site/docs/index.html:135 msgid "I2NP Specification" msgstr "I2NP-Spezifikation" -#: i2p2www/pages/site/docs/index.html:134 +#: i2p2www/pages/site/docs/index.html:137 msgid "I2NP Javadoc" msgstr "" -#: i2p2www/pages/site/docs/index.html:141 +#: i2p2www/pages/site/docs/index.html:144 #: i2p2www/pages/site/docs/how/tech-intro.html:14 #: i2p2www/pages/site/docs/how/tech-intro.html:228 msgid "Tunnels" msgstr "Tunnel" -#: i2p2www/pages/site/docs/index.html:142 +#: i2p2www/pages/site/docs/index.html:145 msgid "" "Selecting peers, requesting tunnels through those peers, and encrypting " "and routing messages through these tunnels." msgstr "" -#: i2p2www/pages/site/docs/index.html:144 +#: i2p2www/pages/site/docs/index.html:147 msgid "Peer profiling and selection" msgstr "" -#: i2p2www/pages/site/docs/index.html:145 +#: i2p2www/pages/site/docs/index.html:148 msgid "Tunnel routing overview" msgstr "" -#: i2p2www/pages/site/docs/index.html:146 +#: i2p2www/pages/site/docs/index.html:149 msgid "Garlic routing and \"garlic\" terminology" msgstr "" -#: i2p2www/pages/site/docs/index.html:147 +#: i2p2www/pages/site/docs/index.html:150 msgid "Tunnel building and encryption" msgstr "" -#: i2p2www/pages/site/docs/index.html:148 +#: i2p2www/pages/site/docs/index.html:151 msgid "ElGamal/AES" msgstr "ElGamal/AES" -#: i2p2www/pages/site/docs/index.html:148 +#: i2p2www/pages/site/docs/index.html:151 msgid "for build request encryption" msgstr "" -#: i2p2www/pages/site/docs/index.html:150 +#: i2p2www/pages/site/docs/index.html:153 msgid "Tunnel building specification" msgstr "" -#: i2p2www/pages/site/docs/index.html:151 +#: i2p2www/pages/site/docs/index.html:154 msgid "Low-level tunnel message specification" msgstr "" -#: i2p2www/pages/site/docs/index.html:152 +#: i2p2www/pages/site/docs/index.html:155 #: i2p2www/pages/site/docs/tunnels/unidirectional.html:2 msgid "Unidirectional Tunnels" msgstr "" -#: i2p2www/pages/site/docs/index.html:153 +#: i2p2www/pages/site/docs/index.html:156 #: i2p2www/pages/site/docs/how/peer-selection.html:299 msgid "Peer Profiling and Selection in the I2P Anonymous Network" msgstr "" -#: i2p2www/pages/site/docs/index.html:154 +#: i2p2www/pages/site/docs/index.html:157 msgid "2009 paper (pdf), not current but still generally accurate" msgstr "" -#: i2p2www/pages/site/docs/index.html:157 +#: i2p2www/pages/site/docs/index.html:160 msgid "Transport Layer" msgstr "Transportschicht" -#: i2p2www/pages/site/docs/index.html:158 +#: i2p2www/pages/site/docs/index.html:161 msgid "The protocols for direct (point-to-point) router to router communication." msgstr "" -#: i2p2www/pages/site/docs/index.html:160 +#: i2p2www/pages/site/docs/index.html:163 msgid "Transport layer overview" msgstr "Transportschichtübersicht" -#: i2p2www/pages/site/docs/index.html:162 +#: i2p2www/pages/site/docs/index.html:165 msgid "TCP-based transport overview and specification" msgstr "" -#: i2p2www/pages/site/docs/index.html:164 +#: i2p2www/pages/site/docs/index.html:167 msgid "UDP-based transport overview" msgstr "" -#: i2p2www/pages/site/docs/index.html:166 +#: i2p2www/pages/site/docs/index.html:169 msgid "SSU specification" msgstr "SSU-Spezifikation" -#: i2p2www/pages/site/docs/index.html:168 +#: i2p2www/pages/site/docs/index.html:171 msgid "NTCP transport encryption" msgstr "NTCP-Transportverschlüsselung" -#: i2p2www/pages/site/docs/index.html:170 +#: i2p2www/pages/site/docs/index.html:173 msgid "SSU transport encryption" msgstr "SSU-Transportverschlüsselung" -#: i2p2www/pages/site/docs/index.html:172 +#: i2p2www/pages/site/docs/index.html:175 msgid "Transport Javadoc" msgstr "" -#: i2p2www/pages/site/docs/index.html:174 +#: i2p2www/pages/site/docs/index.html:177 msgid "NTCP Javadoc" msgstr "" -#: i2p2www/pages/site/docs/index.html:176 +#: i2p2www/pages/site/docs/index.html:179 msgid "SSU Javadoc" msgstr "" -#: i2p2www/pages/site/docs/index.html:179 +#: i2p2www/pages/site/docs/index.html:182 msgid "Other Router Topics" msgstr "" -#: i2p2www/pages/site/docs/index.html:181 +#: i2p2www/pages/site/docs/index.html:184 msgid "Router software updates" msgstr "Router Software Updates" -#: i2p2www/pages/site/docs/index.html:183 +#: i2p2www/pages/site/docs/index.html:188 msgid "Native BigInteger Library" msgstr "" -#: i2p2www/pages/site/docs/index.html:185 +#: i2p2www/pages/site/docs/index.html:190 msgid "Time synchronization and NTP" msgstr "" -#: i2p2www/pages/site/docs/index.html:187 +#: i2p2www/pages/site/docs/index.html:192 msgid "Performance" msgstr "Leistung" -#: i2p2www/pages/site/docs/index.html:194 +#: i2p2www/pages/site/docs/index.html:199 msgid "Developer's Guides and Resources" msgstr "" -#: i2p2www/pages/site/docs/index.html:196 +#: i2p2www/pages/site/docs/index.html:201 msgid "New Developer's Guide" msgstr "" -#: i2p2www/pages/site/docs/index.html:198 +#: i2p2www/pages/site/docs/index.html:203 msgid "New Translator's Guide" msgstr "" -#: i2p2www/pages/site/docs/index.html:200 +#: i2p2www/pages/site/docs/index.html:205 msgid "Monotone Guide" msgstr "" -#: i2p2www/pages/site/docs/index.html:202 +#: i2p2www/pages/site/docs/index.html:207 msgid "Developer Guidelines" msgstr "" -#: i2p2www/pages/site/docs/index.html:204 +#: i2p2www/pages/site/docs/index.html:209 msgid "Javadocs on the standard internet:" msgstr "" -#: i2p2www/pages/site/docs/index.html:205 -#: i2p2www/pages/site/docs/index.html:209 #: i2p2www/pages/site/docs/index.html:210 -#: i2p2www/pages/site/docs/index.html:211 +#: i2p2www/pages/site/docs/index.html:214 +#: i2p2www/pages/site/docs/index.html:215 +#: i2p2www/pages/site/docs/index.html:216 #, python-format msgid "Server %(num)s" msgstr "Server %(num)s" -#: i2p2www/pages/site/docs/index.html:206 -#: i2p2www/pages/site/docs/index.html:215 +#: i2p2www/pages/site/docs/index.html:211 +#: i2p2www/pages/site/docs/index.html:220 msgid "" "Note: always verify that javadocs are current by checking the release " "number." msgstr "" -#: i2p2www/pages/site/docs/index.html:208 +#: i2p2www/pages/site/docs/index.html:213 msgid "Javadocs inside I2P:" msgstr "" -#: i2p2www/pages/site/docs/index.html:219 +#: i2p2www/pages/site/docs/index.html:224 msgid "Ports used by I2P" msgstr "Von I2P genutzte Ports" -#: i2p2www/pages/site/docs/index.html:221 +#: i2p2www/pages/site/docs/index.html:226 msgid "Automatic updates to development builds inside I2P" msgstr "" -#: i2p2www/pages/site/docs/index.html:223 +#: i2p2www/pages/site/docs/index.html:228 msgid "Updating the wrapper manually" msgstr "" -#: i2p2www/pages/site/docs/index.html:225 +#: i2p2www/pages/site/docs/index.html:230 msgid "User forum" msgstr "Benutzerforum" -#: i2p2www/pages/site/docs/index.html:227 +#: i2p2www/pages/site/docs/index.html:232 msgid "Developer forum inside I2P" msgstr "" -#: i2p2www/pages/site/docs/index.html:229 +#: i2p2www/pages/site/docs/index.html:234 msgid "Bug tracker" msgstr "" -#: i2p2www/pages/site/docs/index.html:231 +#: i2p2www/pages/site/docs/index.html:236 msgid "Viewmtn inside I2P" msgstr "" -#: i2p2www/pages/site/docs/index.html:233 +#: i2p2www/pages/site/docs/index.html:238 msgid "I2P Source exported to GitHub" msgstr "" -#: i2p2www/pages/site/docs/index.html:235 +#: i2p2www/pages/site/docs/index.html:240 msgid "I2P Source Git Repo inside I2P" msgstr "" -#: i2p2www/pages/site/docs/index.html:237 +#: i2p2www/pages/site/docs/index.html:242 msgid "Source translation at Transifex" msgstr "" -#: i2p2www/pages/site/docs/index.html:239 +#: i2p2www/pages/site/docs/index.html:244 msgid "Roadmap wiki" msgstr "" -#: i2p2www/pages/site/docs/index.html:241 +#: i2p2www/pages/site/docs/index.html:246 msgid "Old roadmap" msgstr "" -#: i2p2www/pages/site/docs/index.html:241 -#: i2p2www/pages/site/docs/index.html:243 +#: i2p2www/pages/site/docs/index.html:246 +#: i2p2www/pages/site/docs/index.html:248 msgid "not current" msgstr "nicht aktuell" -#: i2p2www/pages/site/docs/index.html:243 +#: i2p2www/pages/site/docs/index.html:248 msgid "To Do List" msgstr "" @@ -795,7 +809,7 @@ msgid "" msgstr "" #: i2p2www/pages/site/docs/naming.html:183 -#: i2p2www/pages/site/docs/spec/configuration.html:170 +#: i2p2www/pages/site/docs/spec/configuration.html:184 msgid "Addressbook" msgstr "Adressbuch" @@ -1165,7 +1179,7 @@ msgid "" msgstr "" #: i2p2www/pages/site/docs/plugins.html:2 -#: i2p2www/pages/site/docs/spec/configuration.html:138 +#: i2p2www/pages/site/docs/spec/configuration.html:152 msgid "Plugins" msgstr "Plugins" @@ -2541,15 +2555,20 @@ msgid "" msgstr "" #: i2p2www/pages/site/docs/api/i2ptunnel.html:54 +#, fuzzy +msgid "Configuration" +msgstr "Konfigurationsdateiformat" + +#: i2p2www/pages/site/docs/api/i2ptunnel.html:58 msgid "Client Modes" msgstr "" -#: i2p2www/pages/site/docs/api/i2ptunnel.html:55 -#: i2p2www/pages/site/docs/api/i2ptunnel.html:137 +#: i2p2www/pages/site/docs/api/i2ptunnel.html:59 +#: i2p2www/pages/site/docs/api/i2ptunnel.html:141 msgid "Standard" msgstr "Standard" -#: i2p2www/pages/site/docs/api/i2ptunnel.html:56 +#: 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" @@ -2557,7 +2576,7 @@ msgid "" " list of destinations." msgstr "" -#: i2p2www/pages/site/docs/api/i2ptunnel.html:62 +#: i2p2www/pages/site/docs/api/i2ptunnel.html:66 msgid "" "A HTTP-client tunnel. The tunnel connects to the destination specified by" " the URL\n" @@ -2565,34 +2584,34 @@ msgid "" "provided. Strips HTTP connections of the following headers:" msgstr "" -#: i2p2www/pages/site/docs/api/i2ptunnel.html:67 +#: 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 "" -#: i2p2www/pages/site/docs/api/i2ptunnel.html:75 +#: 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 "" -#: i2p2www/pages/site/docs/api/i2ptunnel.html:82 +#: 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 "" -#: i2p2www/pages/site/docs/api/i2ptunnel.html:86 +#: i2p2www/pages/site/docs/api/i2ptunnel.html:90 msgid "Outproxy:" msgstr "Outproxy:" -#: i2p2www/pages/site/docs/api/i2ptunnel.html:87 +#: i2p2www/pages/site/docs/api/i2ptunnel.html:91 msgid "Internal I2P use:" msgstr "Interne I2P-Nutzung:" -#: i2p2www/pages/site/docs/api/i2ptunnel.html:92 +#: i2p2www/pages/site/docs/api/i2ptunnel.html:96 msgid "" "Creates a connection to a random IRC server specified by the comma " "seprated (\", \") \n" @@ -2600,43 +2619,43 @@ msgid "" "allowed due to anonymity concerns." msgstr "" -#: i2p2www/pages/site/docs/api/i2ptunnel.html:96 +#: i2p2www/pages/site/docs/api/i2ptunnel.html:100 msgid "Whitelist:" msgstr "Weiße Liste:" -#: i2p2www/pages/site/docs/api/i2ptunnel.html:111 +#: i2p2www/pages/site/docs/api/i2ptunnel.html:115 msgid "Enables using the I2P router as a SOCKS proxy." msgstr "" -#: i2p2www/pages/site/docs/api/i2ptunnel.html:116 +#: 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" "IRC client mode." msgstr "" -#: i2p2www/pages/site/docs/api/i2ptunnel.html:122 +#: 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 "" -#: i2p2www/pages/site/docs/api/i2ptunnel.html:128 +#: 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" "subscribe to a streamr server tunnel." msgstr "" -#: i2p2www/pages/site/docs/api/i2ptunnel.html:136 +#: i2p2www/pages/site/docs/api/i2ptunnel.html:140 msgid "Server Modes" msgstr "" -#: i2p2www/pages/site/docs/api/i2ptunnel.html:138 +#: i2p2www/pages/site/docs/api/i2ptunnel.html:142 msgid "Creates a destination to a local ip:port with an open TCP port." msgstr "" -#: i2p2www/pages/site/docs/api/i2ptunnel.html:143 +#: 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" @@ -2644,7 +2663,7 @@ msgid "" " such a request." msgstr "" -#: i2p2www/pages/site/docs/api/i2ptunnel.html:149 +#: 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" @@ -2653,14 +2672,14 @@ msgid "" "requests, or loopback-testing an eepsite as a diagnostic tool." msgstr "" -#: i2p2www/pages/site/docs/api/i2ptunnel.html:156 +#: i2p2www/pages/site/docs/api/i2ptunnel.html:160 msgid "" "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:162 +#: 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." @@ -3453,8 +3472,8 @@ msgstr "" #: i2p2www/pages/site/docs/how/tunnel-routing.html:255 #: i2p2www/pages/site/docs/protocol/i2cp.html:687 #: i2p2www/pages/site/docs/protocol/i2np.html:226 -#: i2p2www/pages/site/docs/spec/updates.html:438 -#: i2p2www/pages/site/docs/transport/ntcp.html:535 +#: i2p2www/pages/site/docs/spec/updates.html:488 +#: i2p2www/pages/site/docs/transport/ntcp.html:544 #: i2p2www/pages/site/docs/transport/ssu.html:554 #: i2p2www/pages/site/docs/tunnels/implementation.html:506 msgid "Future Work" @@ -4005,6 +4024,14 @@ 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)." +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" "If done wrong, it could cause real harm to our network.\n" @@ -4013,11 +4040,11 @@ msgid "" "This page discusses some general guidelines." msgstr "" -#: i2p2www/pages/site/docs/applications/embedding.html:18 +#: i2p2www/pages/site/docs/applications/embedding.html:23 msgid "Talk to us" msgstr "" -#: i2p2www/pages/site/docs/applications/embedding.html:19 +#: 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" @@ -4025,11 +4052,11 @@ msgid "" "everyone." msgstr "" -#: i2p2www/pages/site/docs/applications/embedding.html:25 +#: i2p2www/pages/site/docs/applications/embedding.html:30 msgid "Choose your router wisely" msgstr "" -#: i2p2www/pages/site/docs/applications/embedding.html:26 +#: 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" @@ -4039,19 +4066,19 @@ msgid "" "Some of the following only applies to the Java router." msgstr "" -#: i2p2www/pages/site/docs/applications/embedding.html:34 +#: i2p2www/pages/site/docs/applications/embedding.html:39 msgid "Licensing" msgstr "" -#: i2p2www/pages/site/docs/applications/embedding.html:35 +#: i2p2www/pages/site/docs/applications/embedding.html:40 msgid "Ensure you meet the license requirements of the software you are bundling." msgstr "" -#: i2p2www/pages/site/docs/applications/embedding.html:40 +#: i2p2www/pages/site/docs/applications/embedding.html:45 msgid "Verify default configuration" msgstr "" -#: i2p2www/pages/site/docs/applications/embedding.html:41 +#: i2p2www/pages/site/docs/applications/embedding.html:46 msgid "" "A correct default configuration is crucial. Most users will not change " "the defaults.\n" @@ -4060,7 +4087,7 @@ msgid "" "Override the router defaults if necessary." msgstr "" -#: i2p2www/pages/site/docs/applications/embedding.html:46 +#: i2p2www/pages/site/docs/applications/embedding.html:51 msgid "" "Some important defaults to review: Max bandwidth, tunnel quantity and " "length, max participating tunnels.\n" @@ -4068,7 +4095,7 @@ msgid "" "your app." msgstr "" -#: i2p2www/pages/site/docs/applications/embedding.html:50 +#: i2p2www/pages/site/docs/applications/embedding.html:55 msgid "" "Configure enough bandwidth and tunnels to allow your users to contribute " "to the network.\n" @@ -4078,11 +4105,11 @@ msgid "" "example." msgstr "" -#: i2p2www/pages/site/docs/applications/embedding.html:57 +#: i2p2www/pages/site/docs/applications/embedding.html:62 msgid "Participating Traffic Considerations" msgstr "" -#: i2p2www/pages/site/docs/applications/embedding.html:58 +#: 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, " @@ -4094,14 +4121,14 @@ msgid "" "tunnels." msgstr "" -#: i2p2www/pages/site/docs/applications/embedding.html:65 +#: 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" "which is helped tremendously by others building tunnels through you." msgstr "" -#: i2p2www/pages/site/docs/applications/embedding.html:69 +#: i2p2www/pages/site/docs/applications/embedding.html:74 msgid "" "Secondly, over 90% of the routers in the current network allow " "participating traffic.\n" @@ -4113,13 +4140,13 @@ msgid "" " people to enable relaying." msgstr "" -#: i2p2www/pages/site/docs/applications/embedding.html:76 +#: i2p2www/pages/site/docs/applications/embedding.html:81 msgid "" "Thirdly, participating traffic is cover traffic that helps your users' " "anonymity." msgstr "" -#: i2p2www/pages/site/docs/applications/embedding.html:79 +#: i2p2www/pages/site/docs/applications/embedding.html:84 msgid "" "We strongly discourage you from disabling participating traffic by " "default.\n" @@ -4127,11 +4154,11 @@ msgid "" "the network." msgstr "" -#: i2p2www/pages/site/docs/applications/embedding.html:85 +#: i2p2www/pages/site/docs/applications/embedding.html:90 msgid "Persistence" msgstr "" -#: i2p2www/pages/site/docs/applications/embedding.html:86 +#: 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" @@ -4141,11 +4168,11 @@ msgid "" "performance." msgstr "" -#: i2p2www/pages/site/docs/applications/embedding.html:94 +#: i2p2www/pages/site/docs/applications/embedding.html:99 msgid "Configurability" msgstr "" -#: i2p2www/pages/site/docs/applications/embedding.html:95 +#: i2p2www/pages/site/docs/applications/embedding.html:100 msgid "" "Give your users a way to change the configuration of the important " "settings.\n" @@ -4155,11 +4182,11 @@ msgid "" "IP/port may be helpful." msgstr "" -#: i2p2www/pages/site/docs/applications/embedding.html:103 +#: i2p2www/pages/site/docs/applications/embedding.html:108 msgid "Floodfill Considerations" msgstr "" -#: i2p2www/pages/site/docs/applications/embedding.html:104 +#: 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" @@ -4170,11 +4197,11 @@ msgid "" "It also depends on the typical uptime for your application." msgstr "" -#: i2p2www/pages/site/docs/applications/embedding.html:114 +#: i2p2www/pages/site/docs/applications/embedding.html:119 msgid "Reseeding" msgstr "" -#: i2p2www/pages/site/docs/applications/embedding.html:115 +#: 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 " @@ -4182,11 +4209,11 @@ msgid "" "Be aware of possible blocking by hostile governments." msgstr "" -#: i2p2www/pages/site/docs/applications/embedding.html:124 +#: i2p2www/pages/site/docs/applications/embedding.html:129 msgid "Reduce Network Resource Usage" msgstr "" -#: i2p2www/pages/site/docs/applications/embedding.html:125 +#: 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" @@ -4196,11 +4223,11 @@ msgid "" "tunnel, even in the presence of some background DHT activity." msgstr "" -#: i2p2www/pages/site/docs/applications/embedding.html:133 +#: i2p2www/pages/site/docs/applications/embedding.html:138 msgid "Updatability" msgstr "" -#: i2p2www/pages/site/docs/applications/embedding.html:134 +#: 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" @@ -4215,11 +4242,11 @@ msgid "" "which you presumably are not bundling." msgstr "" -#: i2p2www/pages/site/docs/applications/embedding.html:145 +#: i2p2www/pages/site/docs/applications/embedding.html:150 msgid "Rollout" msgstr "" -#: i2p2www/pages/site/docs/applications/embedding.html:146 +#: 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 " @@ -4235,11 +4262,11 @@ msgid "" "checklist is." msgstr "" -#: i2p2www/pages/site/docs/applications/embedding.html:158 +#: i2p2www/pages/site/docs/applications/embedding.html:163 msgid "Design for and Encourage Long Uptimes" msgstr "" -#: i2p2www/pages/site/docs/applications/embedding.html:159 +#: 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 " @@ -4248,53 +4275,53 @@ msgid "" "solution." msgstr "" -#: i2p2www/pages/site/docs/applications/embedding.html:167 +#: i2p2www/pages/site/docs/applications/embedding.html:172 msgid "Show Status" msgstr "" -#: i2p2www/pages/site/docs/applications/embedding.html:168 +#: i2p2www/pages/site/docs/applications/embedding.html:173 msgid "" "Provide some indication to the user that the application tunnels are " "ready. Encourage patience." msgstr "" -#: i2p2www/pages/site/docs/applications/embedding.html:173 +#: i2p2www/pages/site/docs/applications/embedding.html:178 msgid "Graceful Shutdown" msgstr "" -#: i2p2www/pages/site/docs/applications/embedding.html:174 +#: 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 "" -#: i2p2www/pages/site/docs/applications/embedding.html:180 +#: i2p2www/pages/site/docs/applications/embedding.html:185 msgid "Education and Donation" msgstr "" -#: i2p2www/pages/site/docs/applications/embedding.html:181 +#: 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 "" -#: i2p2www/pages/site/docs/applications/embedding.html:187 +#: i2p2www/pages/site/docs/applications/embedding.html:192 msgid "External Router Option" msgstr "" -#: i2p2www/pages/site/docs/applications/embedding.html:188 +#: 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 "" -#: i2p2www/pages/site/docs/applications/embedding.html:195 +#: i2p2www/pages/site/docs/applications/embedding.html:200 msgid "Use of other Common Services" msgstr "" -#: i2p2www/pages/site/docs/applications/embedding.html:196 +#: 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" @@ -4302,11 +4329,11 @@ msgid "" "and talk to the people who are running them to make sure it's ok." msgstr "" -#: i2p2www/pages/site/docs/applications/embedding.html:204 +#: i2p2www/pages/site/docs/applications/embedding.html:209 msgid "Time / NTP Issues" msgstr "" -#: i2p2www/pages/site/docs/applications/embedding.html:205 +#: 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. " @@ -4315,11 +4342,11 @@ msgid "" "clock is correct." msgstr "" -#: i2p2www/pages/site/docs/applications/embedding.html:213 +#: i2p2www/pages/site/docs/applications/embedding.html:218 msgid "Choose What and How you Bundle" msgstr "" -#: i2p2www/pages/site/docs/applications/embedding.html:214 +#: 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" @@ -4337,11 +4364,19 @@ msgid "" "and i2psnark, for example." msgstr "" -#: i2p2www/pages/site/docs/applications/embedding.html:228 +#: i2p2www/pages/site/docs/applications/embedding.html:233 +msgid "You may also wish to bundle a hosts.txt file." +msgstr "" + +#: i2p2www/pages/site/docs/applications/embedding.html:236 +msgid "Be sure to specify a Java 6 bootclasspath if compiling with Java 8." +msgstr "" + +#: i2p2www/pages/site/docs/applications/embedding.html:244 msgid "Datagram (DHT) considerations" msgstr "" -#: i2p2www/pages/site/docs/applications/embedding.html:229 +#: 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 " @@ -4357,32 +4392,32 @@ msgid "" "have several." msgstr "" -#: i2p2www/pages/site/docs/applications/embedding.html:242 +#: i2p2www/pages/site/docs/applications/embedding.html:258 msgid "Comarketing" msgstr "" -#: i2p2www/pages/site/docs/applications/embedding.html:243 +#: 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 "" -#: i2p2www/pages/site/docs/applications/embedding.html:249 +#: i2p2www/pages/site/docs/applications/embedding.html:265 msgid "Malware" msgstr "" -#: i2p2www/pages/site/docs/applications/embedding.html:250 +#: i2p2www/pages/site/docs/applications/embedding.html:266 msgid "" "Please don't use I2P for evil.\n" "It could cause great harm both to our network and our reputation." msgstr "" -#: i2p2www/pages/site/docs/applications/embedding.html:256 +#: i2p2www/pages/site/docs/applications/embedding.html:272 msgid "Join Us" msgstr "" -#: i2p2www/pages/site/docs/applications/embedding.html:257 +#: 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" @@ -4390,11 +4425,11 @@ msgid "" "We can help get you users, testers, translators, or even coders." msgstr "" -#: i2p2www/pages/site/docs/applications/embedding.html:265 +#: i2p2www/pages/site/docs/applications/embedding.html:281 msgid "Application Examples" msgstr "" -#: i2p2www/pages/site/docs/applications/embedding.html:266 +#: 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" @@ -4404,17 +4439,17 @@ msgid "" " and Monero." msgstr "" -#: i2p2www/pages/site/docs/applications/embedding.html:274 +#: i2p2www/pages/site/docs/applications/embedding.html:290 msgid "Code Example" msgstr "" -#: i2p2www/pages/site/docs/applications/embedding.html:275 +#: i2p2www/pages/site/docs/applications/embedding.html:291 msgid "" "None of the above actually tells you how to write your code to\n" "bundle the Java router, so following is a brief example." msgstr "" -#: i2p2www/pages/site/docs/applications/embedding.html:290 +#: 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" @@ -7460,7 +7495,6 @@ msgid "The Network Database" msgstr "Die Netzwerkdatenbank" #: i2p2www/pages/site/docs/how/network-database.html:3 -#: i2p2www/pages/site/docs/transport/ntcp.html:3 msgid "October 2014" msgstr "" @@ -14714,10 +14748,6 @@ msgstr "" msgid "Configuration File Specification" msgstr "" -#: i2p2www/pages/site/docs/spec/configuration.html:3 -msgid "January 2014" -msgstr "Januar 2014" - #: i2p2www/pages/site/docs/spec/configuration.html:7 msgid "" "This page provides a general specification of I2P configuration files,\n" @@ -14826,65 +14856,66 @@ msgid "Configured via /configlogging in the router console." msgstr "" #: i2p2www/pages/site/docs/spec/configuration.html:112 -#: i2p2www/pages/site/docs/spec/configuration.html:142 -#: i2p2www/pages/site/docs/spec/configuration.html:154 +#: i2p2www/pages/site/docs/spec/configuration.html:156 +#: i2p2www/pages/site/docs/spec/configuration.html:168 +#: i2p2www/pages/site/docs/spec/configuration.html:198 msgid "Properties are as follows:" msgstr "" -#: i2p2www/pages/site/docs/spec/configuration.html:133 +#: i2p2www/pages/site/docs/spec/configuration.html:147 msgid "Individual Plugin" msgstr "" -#: i2p2www/pages/site/docs/spec/configuration.html:134 +#: i2p2www/pages/site/docs/spec/configuration.html:148 #, python-format msgid "See the plugin specification." msgstr "" -#: i2p2www/pages/site/docs/spec/configuration.html:139 +#: i2p2www/pages/site/docs/spec/configuration.html:153 msgid "Enable/disable for each installed plugin." msgstr "" -#: i2p2www/pages/site/docs/spec/configuration.html:150 +#: i2p2www/pages/site/docs/spec/configuration.html:164 msgid "Webapps" msgstr "" -#: i2p2www/pages/site/docs/spec/configuration.html:151 +#: i2p2www/pages/site/docs/spec/configuration.html:165 msgid "Enable/disable for each installed webapp." msgstr "" -#: i2p2www/pages/site/docs/spec/configuration.html:163 +#: i2p2www/pages/site/docs/spec/configuration.html:177 msgid "Router" msgstr "Router" -#: i2p2www/pages/site/docs/spec/configuration.html:164 +#: i2p2www/pages/site/docs/spec/configuration.html:178 msgid "Configured via /configadvanced in the router console." msgstr "" -#: i2p2www/pages/site/docs/spec/configuration.html:168 +#: i2p2www/pages/site/docs/spec/configuration.html:182 msgid "Applications" msgstr "Anwendungen" -#: i2p2www/pages/site/docs/spec/configuration.html:171 +#: i2p2www/pages/site/docs/spec/configuration.html:185 msgid "See documentation in SusiDNS." msgstr "" -#: i2p2www/pages/site/docs/spec/configuration.html:176 +#: i2p2www/pages/site/docs/spec/configuration.html:190 msgid "Configured via the application gui." msgstr "" -#: i2p2www/pages/site/docs/spec/configuration.html:181 +#: i2p2www/pages/site/docs/spec/configuration.html:195 msgid "Configured via the /i2ptunnel application in the router console." msgstr "" -#: i2p2www/pages/site/docs/spec/configuration.html:185 +#: i2p2www/pages/site/docs/spec/configuration.html:364 msgid "Router Console" msgstr "Routerkonsole" -#: i2p2www/pages/site/docs/spec/configuration.html:186 +#: i2p2www/pages/site/docs/spec/configuration.html:365 msgid "The router console uses the router.config file." msgstr "" -#: i2p2www/pages/site/docs/spec/configuration.html:191 +#: i2p2www/pages/site/docs/spec/configuration.html:370 msgid "See post on zzz.i2p." msgstr "" @@ -15279,6 +15310,7 @@ msgstr "" #: i2p2www/pages/site/docs/spec/updates.html:204 #: i2p2www/pages/site/docs/spec/updates.html:313 +#: i2p2www/pages/site/docs/spec/updates.html:365 msgid "Goals:" msgstr "Ziele:" @@ -15301,7 +15333,8 @@ msgid "One-pass signature verification and file extraction" msgstr "" #: i2p2www/pages/site/docs/spec/updates.html:222 -#: i2p2www/pages/site/docs/spec/updates.html:336 +#: i2p2www/pages/site/docs/spec/updates.html:328 +#: i2p2www/pages/site/docs/spec/updates.html:388 msgid "Specification:" msgstr "Spezifikation:" @@ -15310,40 +15343,80 @@ msgid "All unused fields must be set to 0 for compatibility with future versions msgstr "" #: i2p2www/pages/site/docs/spec/updates.html:308 -msgid "SU3 News File Specification" -msgstr "" +#, fuzzy +msgid "SU3 Reseed File Specification" +msgstr "SSU-Spezifikation" #: i2p2www/pages/site/docs/spec/updates.html:309 -msgid "As of 0.9.17, the news is delivered in an \"su3\" file format." +msgid "As of 0.9.14, reseed data is delivered in an \"su3\" file format." msgstr "" #: i2p2www/pages/site/docs/spec/updates.html:316 -msgid "Signed news with strong signatures and trusted certificates" +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 "" -#: i2p2www/pages/site/docs/spec/updates.html:319 +#: 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 "" -#: i2p2www/pages/site/docs/spec/updates.html:322 -msgid "Standard XML format for use with standard parsers" -msgstr "" - -#: i2p2www/pages/site/docs/spec/updates.html:325 -msgid "Standard Atom format for use with standard feed readers and generators" -msgstr "" - -#: i2p2www/pages/site/docs/spec/updates.html:328 -msgid "Sanitization and verification of HTML before displaying on console" +#: i2p2www/pages/site/docs/spec/updates.html:323 +msgid "" +"Single compressed file to speed up reseeding, which was slow to fetch 200" +" files" msgstr "" #: i2p2www/pages/site/docs/spec/updates.html:331 +msgid "The file must be named \"i2pseeds.su3\"." +msgstr "" + +#: i2p2www/pages/site/docs/spec/updates.html:334 +msgid "" +"The file must be in the same directory as the router infos on the web " +"server." +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" +"and then fetch the individual router info files found in the links." +msgstr "" + +#: i2p2www/pages/site/docs/spec/updates.html:360 +msgid "SU3 News File Specification" +msgstr "" + +#: i2p2www/pages/site/docs/spec/updates.html:361 +msgid "As of 0.9.17, the news is delivered in an \"su3\" file format." +msgstr "" + +#: i2p2www/pages/site/docs/spec/updates.html:368 +msgid "Signed news with strong signatures and trusted certificates" +msgstr "" + +#: i2p2www/pages/site/docs/spec/updates.html:374 +msgid "Standard XML format for use with standard parsers" +msgstr "" + +#: i2p2www/pages/site/docs/spec/updates.html:377 +msgid "Standard Atom format for use with standard feed readers and generators" +msgstr "" + +#: i2p2www/pages/site/docs/spec/updates.html:380 +msgid "Sanitization and verification of HTML before displaying on console" +msgstr "" + +#: i2p2www/pages/site/docs/spec/updates.html:383 msgid "" "Suitable for easy implementation on Android and other platforms without " "an HTML console" msgstr "" -#: i2p2www/pages/site/docs/spec/updates.html:440 +#: 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" @@ -15936,7 +16009,7 @@ msgstr "" #: i2p2www/pages/site/docs/transport/ntcp.html:207 #: i2p2www/pages/site/docs/transport/ntcp.html:250 #: i2p2www/pages/site/docs/transport/ntcp.html:332 -#: i2p2www/pages/site/docs/transport/ntcp.html:428 +#: i2p2www/pages/site/docs/transport/ntcp.html:437 msgid "Size:" msgstr "Größe:" @@ -15954,7 +16027,7 @@ msgstr "" #: i2p2www/pages/site/docs/transport/ntcp.html:236 #: i2p2www/pages/site/docs/transport/ntcp.html:319 -#: i2p2www/pages/site/docs/transport/ntcp.html:397 +#: i2p2www/pages/site/docs/transport/ntcp.html:398 msgid "Notes:" msgstr "Anmerkungen:" @@ -15974,7 +16047,7 @@ msgstr "" #: i2p2www/pages/site/docs/transport/ntcp.html:252 #: i2p2www/pages/site/docs/transport/ntcp.html:334 -#: i2p2www/pages/site/docs/transport/ntcp.html:430 +#: i2p2www/pages/site/docs/transport/ntcp.html:439 msgid "Unencrypted Contents:" msgstr "" @@ -15998,7 +16071,7 @@ msgstr "" #: i2p2www/pages/site/docs/transport/ntcp.html:285 #: i2p2www/pages/site/docs/transport/ntcp.html:376 -#: i2p2www/pages/site/docs/transport/ntcp.html:457 +#: i2p2www/pages/site/docs/transport/ntcp.html:466 msgid "Encrypted Contents:" msgstr "Verschlüsselte Inhalte:" @@ -16035,7 +16108,7 @@ msgid "Alice's 387+ byte `RouterIdentity`" msgstr "" #: i2p2www/pages/site/docs/transport/ntcp.html:366 -#: i2p2www/pages/site/docs/transport/ntcp.html:452 +#: i2p2www/pages/site/docs/transport/ntcp.html:461 msgid "0-15 bytes random data" msgstr "" @@ -16056,31 +16129,31 @@ msgid "" "of message #1) as the IV" msgstr "" -#: i2p2www/pages/site/docs/transport/ntcp.html:399 +#: i2p2www/pages/site/docs/transport/ntcp.html:400 msgid "Bob verifies the signature, and on failure, drops the connection." msgstr "" -#: i2p2www/pages/site/docs/transport/ntcp.html:402 +#: i2p2www/pages/site/docs/transport/ntcp.html:403 msgid "" "Bob may drop the connection if the clock skew with Alice is too high as " "calculated using tsA." msgstr "" -#: i2p2www/pages/site/docs/transport/ntcp.html:405 +#: 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 "" -#: i2p2www/pages/site/docs/transport/ntcp.html:421 +#: i2p2www/pages/site/docs/transport/ntcp.html:430 msgid "Message 4 (Session Confirm B)" msgstr "" -#: i2p2www/pages/site/docs/transport/ntcp.html:422 +#: i2p2www/pages/site/docs/transport/ntcp.html:431 msgid "This is a signature of the critical data. Bob sends Alice:" msgstr "" -#: i2p2www/pages/site/docs/transport/ntcp.html:446 +#: i2p2www/pages/site/docs/transport/ntcp.html:455 msgid "" "the `Signature` of the following concatenated data:\n" " X, Y, Alice's `RouterIdentity`, tsA, tsB.\n" @@ -16088,7 +16161,7 @@ msgid "" "the `SigningPublicKey` in his `RouterIdentity`" msgstr "" -#: i2p2www/pages/site/docs/transport/ntcp.html:470 +#: i2p2www/pages/site/docs/transport/ntcp.html:479 #, python-format msgid "" "Data AES encrypted using the DH " @@ -16099,21 +16172,21 @@ msgid "" "signature types" msgstr "" -#: i2p2www/pages/site/docs/transport/ntcp.html:479 +#: i2p2www/pages/site/docs/transport/ntcp.html:488 msgid "Alice verifies the signature, and on failure, drops the connection." msgstr "" -#: i2p2www/pages/site/docs/transport/ntcp.html:482 +#: 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 "" -#: i2p2www/pages/site/docs/transport/ntcp.html:497 +#: i2p2www/pages/site/docs/transport/ntcp.html:506 msgid "After Establishment" msgstr "" -#: i2p2www/pages/site/docs/transport/ntcp.html:498 +#: i2p2www/pages/site/docs/transport/ntcp.html:507 msgid "" "The connection is established, and standard or time sync messages may be " "exchanged.\n" @@ -16125,11 +16198,11 @@ msgid "" " the next IV." msgstr "" -#: i2p2www/pages/site/docs/transport/ntcp.html:507 +#: i2p2www/pages/site/docs/transport/ntcp.html:516 msgid "Check Connection Message" msgstr "" -#: i2p2www/pages/site/docs/transport/ntcp.html:508 +#: i2p2www/pages/site/docs/transport/ntcp.html:517 msgid "" "Alternately, when Bob receives a connection, it could be a\n" "check connection (perhaps prompted by Bob asking for someone\n" @@ -16139,58 +16212,58 @@ msgid "" "A check info connection will receive 256 bytes containing:" msgstr "" -#: i2p2www/pages/site/docs/transport/ntcp.html:517 +#: i2p2www/pages/site/docs/transport/ntcp.html:526 msgid "32 bytes of uninterpreted, ignored data" msgstr "" -#: i2p2www/pages/site/docs/transport/ntcp.html:518 +#: i2p2www/pages/site/docs/transport/ntcp.html:527 msgid "1 byte size" msgstr "" -#: i2p2www/pages/site/docs/transport/ntcp.html:519 +#: 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 "" -#: i2p2www/pages/site/docs/transport/ntcp.html:520 +#: i2p2www/pages/site/docs/transport/ntcp.html:529 msgid "2 byte port number that the local router was reached on" msgstr "" -#: i2p2www/pages/site/docs/transport/ntcp.html:521 +#: i2p2www/pages/site/docs/transport/ntcp.html:530 msgid "" "4 byte i2p network time as known by the remote side (seconds since the " "epoch)" msgstr "" -#: i2p2www/pages/site/docs/transport/ntcp.html:522 +#: i2p2www/pages/site/docs/transport/ntcp.html:531 msgid "uninterpreted padding data, up to byte 223" msgstr "" -#: i2p2www/pages/site/docs/transport/ntcp.html:523 +#: 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 "" -#: i2p2www/pages/site/docs/transport/ntcp.html:526 +#: i2p2www/pages/site/docs/transport/ntcp.html:535 msgid "Check connection is completely disabled as of release 0.9.12." msgstr "" -#: i2p2www/pages/site/docs/transport/ntcp.html:530 +#: i2p2www/pages/site/docs/transport/ntcp.html:539 msgid "Discussion" msgstr "Diskussion" -#: i2p2www/pages/site/docs/transport/ntcp.html:531 +#: i2p2www/pages/site/docs/transport/ntcp.html:540 #, python-format msgid "Now on the NTCP Discussion Page." msgstr "" -#: i2p2www/pages/site/docs/transport/ntcp.html:537 +#: i2p2www/pages/site/docs/transport/ntcp.html:546 msgid "The maximum message size should be increased to approximately 32 KB." msgstr "" -#: i2p2www/pages/site/docs/transport/ntcp.html:541 +#: 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" @@ -16201,13 +16274,13 @@ msgid "" "to create a limited number of message sizes." msgstr "" -#: i2p2www/pages/site/docs/transport/ntcp.html:549 +#: 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 "" -#: i2p2www/pages/site/docs/transport/ntcp.html:553 +#: 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?" diff --git a/i2p2www/translations/de/LC_MESSAGES/get-involved.po b/i2p2www/translations/de/LC_MESSAGES/get-involved.po index dedf5e02..25a77fc5 100644 --- a/i2p2www/translations/de/LC_MESSAGES/get-involved.po +++ b/i2p2www/translations/de/LC_MESSAGES/get-involved.po @@ -13,7 +13,7 @@ msgid "" msgstr "" "Project-Id-Version: I2P\n" "Report-Msgid-Bugs-To: http://trac.i2p2.de\n" -"POT-Creation-Date: 2014-10-22 20:13+0000\n" +"POT-Creation-Date: 2014-11-27 12:12+0000\n" "PO-Revision-Date: 2014-10-22 20:36+0000\n" "Last-Translator: Ettore Atalan \n" "Language-Team: German " @@ -438,317 +438,52 @@ msgid "" msgstr "" #: i2p2www/pages/site/get-involved/todo.html:15 -#: i2p2www/pages/site/get-involved/todo.html:53 +#: i2p2www/pages/site/get-involved/todo.html:38 msgid "Core functionality" msgstr "Kernfunktionalität" #: i2p2www/pages/site/get-involved/todo.html:15 -#: i2p2www/pages/site/get-involved/todo.html:27 -#: i2p2www/pages/site/get-involved/todo.html:51 +#: i2p2www/pages/site/get-involved/todo.html:21 +#: i2p2www/pages/site/get-involved/todo.html:36 msgid "link" msgstr "Link" #: i2p2www/pages/site/get-involved/todo.html:17 -#: i2p2www/pages/site/get-involved/todo.html:56 -msgid "NAT/Firewall bridging via 1-hop restricted routes" -msgstr "" - -#: i2p2www/pages/site/get-involved/todo.html:20 -#: i2p2www/pages/site/get-involved/todo.html:129 -msgid "High degree transport layer with UDP, NBIO, or NIO" -msgstr "" - -#: i2p2www/pages/site/get-involved/todo.html:23 -#: i2p2www/pages/site/get-involved/todo.html:217 +#: i2p2www/pages/site/get-involved/todo.html:41 msgid "NetworkDB and profile tuning and ejection policy for large nets" msgstr "" -#: i2p2www/pages/site/get-involved/todo.html:27 -#: i2p2www/pages/site/get-involved/todo.html:241 +#: i2p2www/pages/site/get-involved/todo.html:21 +#: i2p2www/pages/site/get-involved/todo.html:65 msgid "Security / anonymity" msgstr "Sicherheit / Anonymität" -#: i2p2www/pages/site/get-involved/todo.html:29 -#: i2p2www/pages/site/get-involved/todo.html:244 -msgid "" -"Per-hop tunnel id & new permuted TunnelVerificationStructure " -"encryption" -msgstr "" - -#: i2p2www/pages/site/get-involved/todo.html:32 -#: i2p2www/pages/site/get-involved/todo.html:294 -msgid "Strict ordering of participants within tunnels" -msgstr "" - -#: i2p2www/pages/site/get-involved/todo.html:35 -msgid "Randomly permuted tunnel lengths" -msgstr "Zufällig vertauschte Tunnellängen" - -#: i2p2www/pages/site/get-involved/todo.html:38 -#: i2p2www/pages/site/get-involved/todo.html:356 +#: 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 "" -#: i2p2www/pages/site/get-involved/todo.html:41 -#: i2p2www/pages/site/get-involved/todo.html:375 +#: 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 "" -#: i2p2www/pages/site/get-involved/todo.html:44 -#: i2p2www/pages/site/get-involved/todo.html:404 +#: 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 "" -#: i2p2www/pages/site/get-involved/todo.html:47 -#: i2p2www/pages/site/get-involved/todo.html:441 +#: i2p2www/pages/site/get-involved/todo.html:32 +#: i2p2www/pages/site/get-involved/todo.html:153 msgid "Stop & go mix w/ garlics & tunnels" msgstr "" -#: i2p2www/pages/site/get-involved/todo.html:51 -#: i2p2www/pages/site/get-involved/todo.html:455 +#: i2p2www/pages/site/get-involved/todo.html:36 +#: i2p2www/pages/site/get-involved/todo.html:167 msgid "Performance" msgstr "Leistung" -#: i2p2www/pages/site/get-involved/todo.html:61 -msgid "Implemented in I2P 0.6.0.6" -msgstr "Implementiert in I2P 0.6.0.6" - -#: i2p2www/pages/site/get-involved/todo.html:62 -msgid "" -"The functionality of allowing routers to fully participate within the " -"network \n" -"while behind firewalls and NATs that they do not control requires some " -"basic \n" -"restricted route operation (since those peers will not be able to receive" -" \n" -"inbound connections). To do this successfully, you consider peers one of" -" \n" -"two ways:" -msgstr "" - -#: i2p2www/pages/site/get-involved/todo.html:72 -msgid "" -"Peers who have reachable interfaces - these peers do not need to \n" -"do anything special" -msgstr "" - -#: i2p2www/pages/site/get-involved/todo.html:76 -msgid "" -"Peers who do not have reachable interfaces - these peers must " -"build \n" -"a tunnel pointing at them where the gateway is one of the peers they have" -" \n" -"established a connection with who has both a publicly reachable interface" -" \n" -"and who has agreed to serve as their 'introducer'." -msgstr "" - -#: i2p2www/pages/site/get-involved/todo.html:84 -msgid "" -"To do this, peers who have no IP address simply connect to a few peers, \n" -"build a tunnel through them, and publish a reference to those tunnels " -"within \n" -"their RouterInfo structure in the network database." -msgstr "" - -#: i2p2www/pages/site/get-involved/todo.html:89 -msgid "" -"When someone wants to contact any particular router, they first must get" -" \n" -"its RouterInfo from the network database, which will tell them whether " -"they \n" -"can connect directly (e.g. the peer has a publicly reachable interface) \n" -"or whether they need to contact them indirectly. Direct connections occur" -" \n" -"as normal, while indirect connections are done through one of the " -"published \n" -"tunnels." -msgstr "" - -#: i2p2www/pages/site/get-involved/todo.html:97 -msgid "" -"When a router just wants to get a message or two to a specific hidden " -"peer, \n" -"they can just use the indirect tunnel for sending the payload. However, \n" -"if the router wants to talk to the hidden peer often (for instance, as " -"part \n" -"of a tunnel), they will send a garlic routed message through the indirect" -" \n" -"tunnel to that hidden peer which unwraps to contain a message which " -"should \n" -"be sent to the originating router. That hidden peer then establishes an \n" -"outbound connection to the originating router and from then on, those two" -" \n" -"routers can talk to each other directly over that newly established " -"direct \n" -"connection." -msgstr "" - -#: i2p2www/pages/site/get-involved/todo.html:108 -msgid "" -"Of course, that only works if the originating peer can receive " -"connections \n" -"(they aren't also hidden). However, if the originating peer is hidden, " -"they \n" -"can simply direct the garlic routed message to come back to the " -"originating \n" -"peer's inbound tunnel." -msgstr "" - -#: i2p2www/pages/site/get-involved/todo.html:114 -msgid "" -"This is not meant to provide a way for a peer's IP address to be " -"concealed, \n" -"merely as a way to let people behind firewalls and NATs fully operate " -"within \n" -"the network. Concealing the peer's IP address adds a little more work, as" -" \n" -"described below." -msgstr "" - -#: i2p2www/pages/site/get-involved/todo.html:120 -msgid "" -"With this technique, any router can participate as any part of a tunnel." -" \n" -"For efficiency purposes, a hidden peer would be a bad choice for an " -"inbound \n" -"gateway, and within any given tunnel, two neighboring peers wouldn't want" -" \n" -"to be hidden. But that is not technically necessary." -msgstr "" - -#: i2p2www/pages/site/get-involved/todo.html:132 -msgid "Both UDP and NIO have been Implemented in I2P" -msgstr "Sowohl UDP und NIO sind in I2P implementiert" - -#: i2p2www/pages/site/get-involved/todo.html:133 -msgid "" -"Standard TCP communication in Java generally requires blocking socket \n" -"calls, and to keep a blocked socket from hanging the entire system, those" -" \n" -"blocking calls are done on their own threads. Our current TCP transport \n" -"is implemented in a naive fashion - for each peer we are talking to, we \n" -"have one thread reading and one thread writing. The reader thread simply" -" \n" -"loops a bunch of read() calls, building I2NP messages and adding them \n" -"to our internal inbound message queue, and the writer thread pulls " -"messages \n" -"off a per-connection outbound message queue and shoves the data through \n" -"write() calls." -msgstr "" - -#: i2p2www/pages/site/get-involved/todo.html:144 -msgid "" -"We do this fairly efficiently, from a CPU perspective - at any time, \n" -"almost all of these threads are sitting idle, blocked waiting for " -"something \n" -"to do. However, each thread consumes real resources (on older Linux " -"kernels, \n" -"for instance, each thread would often be implemented as a fork()'ed " -"process). \n" -"As the network grows, the number of peers each router will want to talk \n" -"with will increase (remember, I2P is fully connected, meaning that any \n" -"given peer should know how to get a message to any other peer, and " -"restricted \n" -"route support will probably not significantly reduce the number of " -"connections \n" -"necessary). This means that with a 100,000 router network, each router \n" -"will have up to 199,998 threads just to deal with the TCP connections!" -msgstr "" - -#: i2p2www/pages/site/get-involved/todo.html:156 -msgid "" -"Obviously, that just won't work. We need to use a transport layer that \n" -"can scale. In Java, we have two main camps:" -msgstr "" - -#: i2p2www/pages/site/get-involved/todo.html:161 -#, python-format -msgid "" -"Implemented in I2P 0.6 (\"SSU\") as documented elsewhere" -msgstr "" - -#: i2p2www/pages/site/get-involved/todo.html:164 -msgid "" -"Sending and receiving UDP datagrams is a connectionless operation - if \n" -"we are communicating with 100,000 peers, we simply stick the UDP packets" -" \n" -"in a queue and have a single thread pulling them off the queue and " -"shoving \n" -"them out the pipe (and to receive, have a single thread pulling in any \n" -"UDP packets received and adding them to an inbound queue)." -msgstr "" - -#: i2p2www/pages/site/get-involved/todo.html:171 -msgid "" -"However, moving to UDP means losing the benefits of TCP's ordering, " -"congestion \n" -"control, MTU discovery, etc. Implementing that code will take significant" -" \n" -"work, however I2P doesn't need it to be as strong as TCP. Specifically, \n" -"a while ago I was taking some measurements in the simulator and on the \n" -"live net, and the vast majority of messages transferred would fit easily" -" \n" -"within a single unfragmented UDP packet, and the largest of the messages" -" \n" -"would fit within 20-30 packets. As mule pointed out, TCP adds a " -"significant \n" -"overhead when dealing with so many small packets, as the ACKs are within" -" \n" -"an order of magnitude in size. With UDP, we can optimize the transport \n" -"for both efficiency and resilience by taking into account I2P's " -"particular \n" -"needs." -msgstr "" - -#: i2p2www/pages/site/get-involved/todo.html:184 -msgid "It will be a lot of work though." -msgstr "" - -#: i2p2www/pages/site/get-involved/todo.html:187 -msgid "NIO or NBIO" -msgstr "NIO oder NBIO" - -#: i2p2www/pages/site/get-involved/todo.html:188 -msgid "NIO Implemented in I2P 0.6.1.22 (\"NTCP\")" -msgstr "NIO implementiert in I2P 0.6.1.22 (\"NTCP\")" - -#: i2p2www/pages/site/get-involved/todo.html:191 -msgid "" -"In Java 1.4, a set of \"New I/O\" packages was introduced, allowing Java" -" \n" -"developers to take advantage of the operating system's nonblocking IO \n" -"capabilities - allowing you to maintain a large number of concurrent IO \n" -"operations without requiring a separate thread for each. There is much \n" -"promise with this approach, as we can scalable handle a large number of \n" -"concurrent connections and we don't have to write a mini-TCP stack with \n" -"UDP. However, the NIO packages have not proven themselves to be battle-" -"ready, \n" -"as the Freenet developer's found. In addition, requiring NIO support " -"would \n" -"mean we can't run on any of the open source JVMs like Kaffe, \n" -"as GNU/Classpath has only " -"limited \n" -"support for NIO. (note: this may not be the case anymore, as there \n" -"has been some progress on Classpath's NIO, but it is an unknown " -"quantity)" -msgstr "" - -#: i2p2www/pages/site/get-involved/todo.html:205 -#, python-format -msgid "" -"Another alternative along the same lines is the Non" -" \n" -"Blocking I/O package - essentially a cleanroom NIO implementation \n" -"(written before NIO was around). It works by using some native OS code \n" -"to do the nonblocking IO, passing off events through Java. It seems to \n" -"be working with Kaffe, though there doesn't seem to be much development \n" -"activity on it lately (likely due to 1.4's NIO deployment)." -msgstr "" - -#: i2p2www/pages/site/get-involved/todo.html:220 +#: i2p2www/pages/site/get-involved/todo.html:44 msgid "" "Within the current network database and profile management " "implementation, \n" @@ -771,152 +506,14 @@ msgid "" "code yet, since we aren't going to need it for a while." msgstr "" -#: i2p2www/pages/site/get-involved/todo.html:235 +#: 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" "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:247 -#: i2p2www/pages/site/get-involved/todo.html:331 -#, python-format -msgid "" -"Addressed in I2P 0.5 as documented elsewhere" -msgstr "" - -#: i2p2www/pages/site/get-involved/todo.html:250 -msgid "" -"Right now, if Alice builds a four hop inbound tunnel starting at Elvis, \n" -"going to Dave, then to Charlie, then Bob, and finally Alice " -"(A<--B<--C<--D<--E), \n" -"all five of them will know they are participating in tunnel \"123\", as \n" -"the messages are tagged as such. What we want to do is give each hop " -"their \n" -"own unique tunnel hop ID - Charlie will receive messages on tunnel 234 \n" -"and forward them to tunnel 876 on Bob. The intent is to prevent Bob or \n" -"Charlie from knowing that they are in Alice's tunnel, as if each hop in \n" -"the tunnel had the same tunnel ID, collusion attacks aren't much work." -msgstr "" - -#: i2p2www/pages/site/get-involved/todo.html:260 -msgid "" -"Adding a unique tunnel ID per hop isn't hard, but by itself, " -"insufficient. \n" -"If Dave and Bob are under the control of the same attacker, they wouldn't" -" \n" -"be able to tell they are in the same tunnel due to the tunnel ID, but \n" -"would be able to tell by the message bodies and verification structures \n" -"by simply comparing them. To prevent that, the tunnel must use layered \n" -"encryption along the path, both on the payload of the tunneled message \n" -"and on the verification structure (used to prevent simple tagging " -"attacks). \n" -"This requires some simple modifications to the TunnelMessage, as well \n" -"as the inclusion of per-hop secret keys delivered during tunnel creation" -" \n" -"and given to the tunnel's gateway. We must fix a maximum tunnel length \n" -"(e.g. 16 hops) and instruct the gateway to encrypt the message to each \n" -"of the 16 delivered secret keys, in reverse order, and to encrypt the \n" -"signature of the hash of the (encrypted) payload at each step. The " -"gateway \n" -"then sends that 16-step encrypted message, along with a 16-step and " -"16-wide \n" -"encrypted mapping to the first hop, which then decrypts the mapping and \n" -"the payload with their secret key, looking in the 16-wide mapping for \n" -"the entry associated with their own hop (keyed by the per-hop tunnel ID)" -" \n" -"and verifying the payload by checking it against the associated signed \n" -"hash." -msgstr "" - -#: i2p2www/pages/site/get-involved/todo.html:281 -msgid "" -"The tunnel gateway does still have more information than the other peers" -" \n" -"in the tunnel, and compromising both the gateway and a tunnel participant" -" \n" -"would allow those peers to collude, exposing the fact that they are both" -" \n" -"in the same tunnel. In addition, neighboring peers know that they are \n" -"in the same tunnel anyway, as they know who they send the message to (and" -" \n" -"with IP-based transports without restricted routes, they know who they \n" -"got it from). However, the above two techniques significantly increase \n" -"the cost of gaining meaningful samples when dealing with longer tunnels." -msgstr "" - -#: i2p2www/pages/site/get-involved/todo.html:297 -msgid "Implemented in release 0.6.2" -msgstr "Implementiert in Version 0.6.2" - -#: i2p2www/pages/site/get-involved/todo.html:300 -#, python-format -msgid "" -"As Connelly proposed to deal with the\n" -"predecessor attack (2008\n" -"update), keeping the order of peers within our tunnels consistent \n" -"(aka whenever Alice creates a tunnel with both Bob and Charlie in it, \n" -"Bob's next hop is always Charlie), we address the issue as Bob doesn't \n" -"get to substantially sample Alice's peer selection group. We may even \n" -"want to explicitly allow Bob to participate in Alice's tunnels in only \n" -"one way - receiving a message from Dave and sending it to Charlie - and \n" -"if any of those peers are not available to participate in the tunnel (due" -" \n" -"to overload, network disconnection, etc), avoid asking Bob to participate" -" \n" -"in any tunnels until they are back online." -msgstr "" - -#: i2p2www/pages/site/get-involved/todo.html:315 -msgid "" -"More analysis is necessary for revising the tunnel creation - at the \n" -"moment, we simply select and order randomly within the peer's top tier \n" -"of peers (ones with fast + high capacity)." -msgstr "" - -#: i2p2www/pages/site/get-involved/todo.html:320 -msgid "" -"Adding a strict ordering to peers in a tunnel also improves the anonymity" -" \n" -"of peers with 0-hop tunnels, as otherwise the fact that a peer's gateway" -" \n" -"is always the same would be particularly damning. However, peers with \n" -"0-hop tunnels may want to periodically use a 1-hop tunnel to simulate \n" -"the failure of a normally reliable gateway peer (so every MTBF*(tunnel \n" -"duration) minutes, use a 1-hop tunnel)." -msgstr "" - -#: i2p2www/pages/site/get-involved/todo.html:337 -msgid "" -"Without tunnel length permutation, if someone were to somehow detect that" -" \n" -"a destination had a particular number of hops, it might be able to use " -"that \n" -"information to identify the router the destination is located on, per the" -" \n" -"predecessor attack. For instance, if everyone has 2-hop tunnels, if Bob \n" -"receives a tunnel message from Charlie and forwards it to Alice, Bob " -"knows \n" -"Alice is the final router in the tunnel. If Bob were to identify what " -"destination \n" -"that tunnel served (by means of colluding with the gateway and harvesting" -" \n" -"the network database for all of the LeaseSets), he would know the router" -" \n" -"on which that destination is located (and without restricted routes, that" -" \n" -"would mean what IP address the destination is on)." -msgstr "" - -#: i2p2www/pages/site/get-involved/todo.html:349 -msgid "" -"It is to counter user behavior that tunnel lengths should be permuted, \n" -"using algorithms based on the length requested (for example, the 1/MTBF \n" -"length change for 0-hop tunnels outlined above)." -msgstr "" - -#: i2p2www/pages/site/get-involved/todo.html:359 +#: i2p2www/pages/site/get-involved/todo.html:71 msgid "" "The restricted route functionality described before was simply a " "functional \n" @@ -938,7 +535,7 @@ msgid "" "to forward it as requested." msgstr "" -#: i2p2www/pages/site/get-involved/todo.html:378 +#: i2p2www/pages/site/get-involved/todo.html:90 #, python-format msgid "" "Within the network, we will want some way to deter people from consuming" @@ -952,7 +549,7 @@ msgid "" "to make certain requests \"expensive\"." msgstr "" -#: i2p2www/pages/site/get-involved/todo.html:386 +#: 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 " @@ -970,7 +567,7 @@ msgid "" "with few resources." msgstr "" -#: i2p2www/pages/site/get-involved/todo.html:397 +#: 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" @@ -978,7 +575,7 @@ msgid "" "appropriate." msgstr "" -#: i2p2www/pages/site/get-involved/todo.html:407 +#: i2p2www/pages/site/get-involved/todo.html:119 #, python-format msgid "" "To powerful passive external observers as well as large colluding " @@ -999,7 +596,7 @@ msgid "" "tunnel mixing strategies." msgstr "" -#: i2p2www/pages/site/get-involved/todo.html:420 +#: 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" @@ -1017,7 +614,7 @@ msgid "" "available." msgstr "" -#: i2p2www/pages/site/get-involved/todo.html:433 +#: i2p2www/pages/site/get-involved/todo.html:145 msgid "" "In addition, we may want to implement code to dynamically reroute tunnels" " \n" @@ -1027,7 +624,7 @@ msgid "" "with instructions to redefine the next-hop in the tunnel." msgstr "" -#: i2p2www/pages/site/get-involved/todo.html:444 +#: 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" @@ -1042,7 +639,7 @@ msgid "" "clove exposed includes delay instructions." msgstr "" -#: i2p2www/pages/site/get-involved/todo.html:456 +#: i2p2www/pages/site/get-involved/todo.html:168 #, python-format msgid "" "Performance related improvements are listed on the\n" @@ -4175,3 +3772,15 @@ msgid "" "href=\"http://%(zzz)s/forums/14\">translation forum on %(zzz)s." msgstr "" + + + + + + + + + + + + diff --git a/i2p2www/translations/es/LC_MESSAGES/docs.po b/i2p2www/translations/es/LC_MESSAGES/docs.po index a9e40706..0dc4513d 100644 --- a/i2p2www/translations/es/LC_MESSAGES/docs.po +++ b/i2p2www/translations/es/LC_MESSAGES/docs.po @@ -15,7 +15,7 @@ msgid "" msgstr "" "Project-Id-Version: I2P\n" "Report-Msgid-Bugs-To: http://trac.i2p2.de\n" -"POT-Creation-Date: 2014-11-16 02:59+0000\n" +"POT-Creation-Date: 2014-11-27 12:12+0000\n" "PO-Revision-Date: 2014-11-27 06:37+0000\n" "Last-Translator: strel\n" "Language-Team: Spanish " @@ -34,7 +34,9 @@ msgstr "Índice de la Documentación técnica" #: i2p2www/pages/site/docs/applications/embedding.html:3 #: i2p2www/pages/site/docs/how/cryptography.html:3 #: i2p2www/pages/site/docs/protocol/i2cp.html:3 +#: i2p2www/pages/site/docs/spec/configuration.html:3 #: i2p2www/pages/site/docs/spec/updates.html:3 +#: i2p2www/pages/site/docs/transport/ntcp.html:3 msgid "November 2014" msgstr "Noviembre de 2014" @@ -147,7 +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:217 +#: i2p2www/pages/site/docs/index.html:44 i2p2www/pages/site/docs/index.html:222 msgid "Embedding the router in your application" msgstr "Encajar el router I2P en su aplicación" @@ -164,7 +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:189 +#: 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" @@ -184,27 +186,33 @@ msgstr "" msgid "Application Development Overview and Guide" msgstr "Resumen y guía del desarrollo de aplicaciones" -#: i2p2www/pages/site/docs/index.html:72 +#: i2p2www/pages/site/docs/index.html:58 +#: i2p2www/pages/site/docs/api/i2ptunnel.html:55 +#, fuzzy +msgid "I2PTunnel Configuration" +msgstr "Creación de túneles" + +#: i2p2www/pages/site/docs/index.html:74 msgid "SAM Protocol" msgstr "Protocolo SAM" -#: i2p2www/pages/site/docs/index.html:74 +#: i2p2www/pages/site/docs/index.html:76 msgid "SAMv2 Protocol" msgstr "Protocolo SAMv2" -#: i2p2www/pages/site/docs/index.html:76 +#: i2p2www/pages/site/docs/index.html:78 msgid "SAMv3 Protocol" msgstr "Protocolo SAMv3" -#: i2p2www/pages/site/docs/index.html:78 +#: i2p2www/pages/site/docs/index.html:80 msgid "BOB Protocol" msgstr "Protocolo BOB" -#: i2p2www/pages/site/docs/index.html:81 +#: i2p2www/pages/site/docs/index.html:83 msgid "End-to-End Transport API and Protocols" msgstr "Protocolos y API del transporte de fin a fin." -#: i2p2www/pages/site/docs/index.html:82 +#: i2p2www/pages/site/docs/index.html:84 msgid "" "The end-to-end protocols used by clients for reliable and unreliable " "communication." @@ -212,33 +220,33 @@ msgstr "" "Los protocolos fin a fin usados por los clientes para la comunicación " "segura y no segura." -#: i2p2www/pages/site/docs/index.html:84 +#: i2p2www/pages/site/docs/index.html:86 #: i2p2www/pages/site/docs/api/streaming.html:2 msgid "Streaming Library" msgstr "Librería de srteaming" -#: i2p2www/pages/site/docs/index.html:86 +#: i2p2www/pages/site/docs/index.html:88 msgid "Streaming Protocol Specification" msgstr "Especificación de protocolo de streaming" -#: i2p2www/pages/site/docs/index.html:88 +#: i2p2www/pages/site/docs/index.html:90 msgid "Streaming Javadoc" msgstr "Javadoc del streaming" -#: i2p2www/pages/site/docs/index.html:90 +#: i2p2www/pages/site/docs/index.html:92 #: i2p2www/pages/site/docs/api/datagrams.html:2 msgid "Datagrams" msgstr "Datagramas" -#: i2p2www/pages/site/docs/index.html:92 +#: i2p2www/pages/site/docs/index.html:94 msgid "Datagram Javadoc" msgstr "Javadoc del datagrama" -#: i2p2www/pages/site/docs/index.html:95 +#: i2p2www/pages/site/docs/index.html:97 msgid "Client-to-Router Interface API and Protocol" msgstr "Protocolo y API del interfaz cliente-a-ruter" -#: i2p2www/pages/site/docs/index.html:96 +#: 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" @@ -248,52 +256,52 @@ msgstr "" " 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:101 +#: i2p2www/pages/site/docs/index.html:103 msgid "I2CP - I2P Control Protocol / API overview" msgstr "I2CP - Protocolo de control de I2P / Resumen del API" -#: i2p2www/pages/site/docs/index.html:103 +#: i2p2www/pages/site/docs/index.html:105 msgid "I2CP Specification" msgstr "Especificación I2CP" -#: i2p2www/pages/site/docs/index.html:105 +#: i2p2www/pages/site/docs/index.html:107 msgid "I2CP API Javadoc" msgstr "Javadoc del API de I2CP" -#: i2p2www/pages/site/docs/index.html:107 -#: i2p2www/pages/site/docs/index.html:136 +#: i2p2www/pages/site/docs/index.html:109 +#: i2p2www/pages/site/docs/index.html:139 msgid "Common data structures specification" msgstr "Especificaciones de las estructuras de datos más usadas." -#: i2p2www/pages/site/docs/index.html:109 -#: i2p2www/pages/site/docs/index.html:138 +#: i2p2www/pages/site/docs/index.html:111 +#: i2p2www/pages/site/docs/index.html:141 msgid "Data Structures Javadoc" msgstr "Javadoc de las estructuras de datos" -#: i2p2www/pages/site/docs/index.html:112 +#: i2p2www/pages/site/docs/index.html:114 msgid "End-to-End Encryption" msgstr "Cifrado de fin a fin" -#: i2p2www/pages/site/docs/index.html:113 +#: i2p2www/pages/site/docs/index.html:115 msgid "How client messages are end-to-end encrypted by the router." msgstr "Cómo son cifrados por el ruter los mensajes de fin a fin." -#: i2p2www/pages/site/docs/index.html:115 +#: i2p2www/pages/site/docs/index.html:117 msgid "ElGamal/AES+SessionTag encryption" msgstr "Cifrado ElGamal/AES+SessionTag" -#: i2p2www/pages/site/docs/index.html:116 -#: i2p2www/pages/site/docs/index.html:149 +#: i2p2www/pages/site/docs/index.html:118 +#: i2p2www/pages/site/docs/index.html:152 msgid "ElGamal and AES cryptography details" msgstr "Detalles criptográficos de ElGamal y AES" -#: i2p2www/pages/site/docs/index.html:119 +#: i2p2www/pages/site/docs/index.html:121 #: i2p2www/pages/site/docs/how/tech-intro.html:15 #: i2p2www/pages/site/docs/how/tech-intro.html:329 msgid "Network Database" msgstr "Base de datos de la red" -#: i2p2www/pages/site/docs/index.html:120 +#: i2p2www/pages/site/docs/index.html:122 msgid "" "Distributed storage and retrieval of information about routers and " "clients." @@ -301,25 +309,31 @@ msgstr "" "Almacenamiento distribuido y obtención de información sobre los ruters y " "los clientes. " -#: i2p2www/pages/site/docs/index.html:122 +#: 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" -#: i2p2www/pages/site/docs/index.html:123 +#: i2p2www/pages/site/docs/index.html:125 msgid "Cryptographic hashes" msgstr "Hashes de cifrados" -#: i2p2www/pages/site/docs/index.html:124 +#: i2p2www/pages/site/docs/index.html:126 msgid "Cryptographic signatures" msgstr "Firmas de cifrados" #: i2p2www/pages/site/docs/index.html:127 +#: i2p2www/pages/site/docs/index.html:186 +#, fuzzy +msgid "Router reseed specification" +msgstr "Especificación de dirección de router" + +#: i2p2www/pages/site/docs/index.html:130 msgid "Router Message Protocol" msgstr "Protocolo de los mensajes del ruter" -#: i2p2www/pages/site/docs/index.html:128 +#: i2p2www/pages/site/docs/index.html:131 msgid "" "I2P is a message-oriented router. The messages sent between routers are " "defined by the I2NP protocol." @@ -327,25 +341,25 @@ 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:130 +#: i2p2www/pages/site/docs/index.html:133 msgid "I2NP - I2P Network Protocol Overview" msgstr "I2NP - Vista general del protocolo de red de I2P" -#: i2p2www/pages/site/docs/index.html:132 +#: i2p2www/pages/site/docs/index.html:135 msgid "I2NP Specification" msgstr "Especificación I2NP" -#: i2p2www/pages/site/docs/index.html:134 +#: i2p2www/pages/site/docs/index.html:137 msgid "I2NP Javadoc" msgstr "Javadoc de I2NP" -#: i2p2www/pages/site/docs/index.html:141 +#: i2p2www/pages/site/docs/index.html:144 #: i2p2www/pages/site/docs/how/tech-intro.html:14 #: i2p2www/pages/site/docs/how/tech-intro.html:228 msgid "Tunnels" msgstr "Túneles" -#: i2p2www/pages/site/docs/index.html:142 +#: i2p2www/pages/site/docs/index.html:145 msgid "" "Selecting peers, requesting tunnels through those peers, and encrypting " "and routing messages through these tunnels." @@ -353,152 +367,152 @@ 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:144 +#: i2p2www/pages/site/docs/index.html:147 msgid "Peer profiling and selection" msgstr "Perfiles y selección de pares" -#: i2p2www/pages/site/docs/index.html:145 +#: i2p2www/pages/site/docs/index.html:148 msgid "Tunnel routing overview" msgstr "Vista general del túnel de enrutado" -#: i2p2www/pages/site/docs/index.html:146 +#: i2p2www/pages/site/docs/index.html:149 msgid "Garlic routing and \"garlic\" terminology" msgstr "Rutado Garlic y terminología \"garlic\"" -#: i2p2www/pages/site/docs/index.html:147 +#: i2p2www/pages/site/docs/index.html:150 msgid "Tunnel building and encryption" msgstr "Cifrado y construcción de los túneles" -#: i2p2www/pages/site/docs/index.html:148 +#: i2p2www/pages/site/docs/index.html:151 msgid "ElGamal/AES" msgstr "ElGamal/AES" -#: i2p2www/pages/site/docs/index.html:148 +#: i2p2www/pages/site/docs/index.html:151 msgid "for build request encryption" msgstr "para cifrado de solicitudes de construcción (`build`, de túneles)" -#: i2p2www/pages/site/docs/index.html:150 +#: i2p2www/pages/site/docs/index.html:153 msgid "Tunnel building specification" msgstr "Especificaciones para la creación de túneles" -#: i2p2www/pages/site/docs/index.html:151 +#: i2p2www/pages/site/docs/index.html:154 msgid "Low-level tunnel message specification" msgstr "Especificaciones de los mensajes de túnel de bajo nivel" -#: i2p2www/pages/site/docs/index.html:152 +#: i2p2www/pages/site/docs/index.html:155 #: i2p2www/pages/site/docs/tunnels/unidirectional.html:2 msgid "Unidirectional Tunnels" msgstr "Túneles unidireccionales" -#: i2p2www/pages/site/docs/index.html:153 +#: i2p2www/pages/site/docs/index.html:156 #: i2p2www/pages/site/docs/how/peer-selection.html:299 msgid "Peer Profiling and Selection in the I2P Anonymous Network" msgstr "Perfiles y selección de pares en la red anónima I2P" -#: i2p2www/pages/site/docs/index.html:154 +#: i2p2www/pages/site/docs/index.html:157 msgid "2009 paper (pdf), not current but still generally accurate" msgstr "Estudio del 2009 (pdf), no es muy actual pero es bastante exacto" -#: i2p2www/pages/site/docs/index.html:157 +#: i2p2www/pages/site/docs/index.html:160 msgid "Transport Layer" msgstr "Capa de transporte" -#: i2p2www/pages/site/docs/index.html:158 +#: 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." -#: i2p2www/pages/site/docs/index.html:160 +#: i2p2www/pages/site/docs/index.html:163 msgid "Transport layer overview" msgstr "Visión general de la capa de transporte" -#: i2p2www/pages/site/docs/index.html:162 +#: i2p2www/pages/site/docs/index.html:165 msgid "TCP-based transport overview and specification" msgstr "Especificaciones y vista general de los transportes basados en TCP" -#: i2p2www/pages/site/docs/index.html:164 +#: i2p2www/pages/site/docs/index.html:167 msgid "UDP-based transport overview" msgstr "Vista general de los transportes basados en UDP" -#: i2p2www/pages/site/docs/index.html:166 +#: i2p2www/pages/site/docs/index.html:169 msgid "SSU specification" msgstr "Especificación SSU" -#: i2p2www/pages/site/docs/index.html:168 +#: i2p2www/pages/site/docs/index.html:171 msgid "NTCP transport encryption" msgstr "Cifrado del transporte de NTCP" -#: i2p2www/pages/site/docs/index.html:170 +#: i2p2www/pages/site/docs/index.html:173 msgid "SSU transport encryption" msgstr "Cifrado del transporte de SSU" -#: i2p2www/pages/site/docs/index.html:172 +#: i2p2www/pages/site/docs/index.html:175 msgid "Transport Javadoc" msgstr "Jacadoc del transporte" -#: i2p2www/pages/site/docs/index.html:174 +#: i2p2www/pages/site/docs/index.html:177 msgid "NTCP Javadoc" msgstr "Javadoc de NTCP" -#: i2p2www/pages/site/docs/index.html:176 +#: i2p2www/pages/site/docs/index.html:179 msgid "SSU Javadoc" msgstr "Jacadoc de SSU" -#: i2p2www/pages/site/docs/index.html:179 +#: i2p2www/pages/site/docs/index.html:182 msgid "Other Router Topics" msgstr "Otros temas sobre el Ruter" -#: i2p2www/pages/site/docs/index.html:181 +#: i2p2www/pages/site/docs/index.html:184 msgid "Router software updates" msgstr "Actualizaciones de software del ruter" -#: i2p2www/pages/site/docs/index.html:183 +#: i2p2www/pages/site/docs/index.html:188 msgid "Native BigInteger Library" msgstr "Librería BigInteger nativa" -#: i2p2www/pages/site/docs/index.html:185 +#: i2p2www/pages/site/docs/index.html:190 msgid "Time synchronization and NTP" msgstr "NTP y sincronización de la fecha" -#: i2p2www/pages/site/docs/index.html:187 +#: i2p2www/pages/site/docs/index.html:192 msgid "Performance" msgstr "Rendimiento" -#: i2p2www/pages/site/docs/index.html:194 +#: i2p2www/pages/site/docs/index.html:199 msgid "Developer's Guides and Resources" msgstr "Recursos y guías para desarrolladores" -#: i2p2www/pages/site/docs/index.html:196 +#: i2p2www/pages/site/docs/index.html:201 msgid "New Developer's Guide" msgstr "Guía para nuevos desarrolladores" -#: i2p2www/pages/site/docs/index.html:198 +#: i2p2www/pages/site/docs/index.html:203 msgid "New Translator's Guide" msgstr "La nueva guía de los traductores" -#: i2p2www/pages/site/docs/index.html:200 +#: i2p2www/pages/site/docs/index.html:205 msgid "Monotone Guide" msgstr "Guía de Monotone" -#: i2p2www/pages/site/docs/index.html:202 +#: i2p2www/pages/site/docs/index.html:207 msgid "Developer Guidelines" msgstr "Directrizes para los desarrolladores" -#: i2p2www/pages/site/docs/index.html:204 +#: i2p2www/pages/site/docs/index.html:209 msgid "Javadocs on the standard internet:" msgstr "Jacadocs en el Internet normal:" -#: i2p2www/pages/site/docs/index.html:205 -#: i2p2www/pages/site/docs/index.html:209 #: i2p2www/pages/site/docs/index.html:210 -#: i2p2www/pages/site/docs/index.html:211 +#: i2p2www/pages/site/docs/index.html:214 +#: i2p2www/pages/site/docs/index.html:215 +#: i2p2www/pages/site/docs/index.html:216 #, python-format msgid "Server %(num)s" msgstr "Servidor %(num)s" -#: i2p2www/pages/site/docs/index.html:206 -#: i2p2www/pages/site/docs/index.html:215 +#: i2p2www/pages/site/docs/index.html:211 +#: i2p2www/pages/site/docs/index.html:220 msgid "" "Note: always verify that javadocs are current by checking the release " "number." @@ -506,64 +520,64 @@ msgstr "" "Nota: verifique siempre que los Javadocs son actuales comprobando los " "números de versiones." -#: i2p2www/pages/site/docs/index.html:208 +#: i2p2www/pages/site/docs/index.html:213 msgid "Javadocs inside I2P:" msgstr "Javadocs en I2P:" -#: i2p2www/pages/site/docs/index.html:219 +#: i2p2www/pages/site/docs/index.html:224 msgid "Ports used by I2P" msgstr "Ports usados por I2P" -#: i2p2www/pages/site/docs/index.html:221 +#: i2p2www/pages/site/docs/index.html:226 msgid "Automatic updates to development builds inside I2P" msgstr "Actualizaciones automáticas y compilaciones de desarrollo dentro de I2P" -#: i2p2www/pages/site/docs/index.html:223 +#: i2p2www/pages/site/docs/index.html:228 msgid "Updating the wrapper manually" msgstr "Actualizando el wrapper manualmente" -#: i2p2www/pages/site/docs/index.html:225 +#: i2p2www/pages/site/docs/index.html:230 msgid "User forum" msgstr "Foro para usuarios" -#: i2p2www/pages/site/docs/index.html:227 +#: i2p2www/pages/site/docs/index.html:232 msgid "Developer forum inside I2P" msgstr "Foro para desarrolladores en I2P" -#: i2p2www/pages/site/docs/index.html:229 +#: i2p2www/pages/site/docs/index.html:234 msgid "Bug tracker" msgstr "Bug tracker" -#: i2p2www/pages/site/docs/index.html:231 +#: i2p2www/pages/site/docs/index.html:236 msgid "Viewmtn inside I2P" msgstr "Viewmtn en I2P" -#: i2p2www/pages/site/docs/index.html:233 +#: i2p2www/pages/site/docs/index.html:238 msgid "I2P Source exported to GitHub" msgstr "El código de I2P exportado a GitHub" -#: i2p2www/pages/site/docs/index.html:235 +#: i2p2www/pages/site/docs/index.html:240 msgid "I2P Source Git Repo inside I2P" msgstr "Repositorio Git del código de I2P en I2P" -#: i2p2www/pages/site/docs/index.html:237 +#: i2p2www/pages/site/docs/index.html:242 msgid "Source translation at Transifex" msgstr "Fuentes para traducir en Transifex" -#: i2p2www/pages/site/docs/index.html:239 +#: i2p2www/pages/site/docs/index.html:244 msgid "Roadmap wiki" msgstr "Wiki con el plan de trabajo" -#: i2p2www/pages/site/docs/index.html:241 +#: i2p2www/pages/site/docs/index.html:246 msgid "Old roadmap" msgstr "Plan de trabajo antiguo" -#: i2p2www/pages/site/docs/index.html:241 -#: i2p2www/pages/site/docs/index.html:243 +#: i2p2www/pages/site/docs/index.html:246 +#: i2p2www/pages/site/docs/index.html:248 msgid "not current" msgstr "no actual" -#: i2p2www/pages/site/docs/index.html:243 +#: i2p2www/pages/site/docs/index.html:248 msgid "To Do List" msgstr "Por hacer" @@ -973,7 +987,7 @@ msgstr "" "servicios distribuidos (`jump`). Mire debajo para más detalles." #: i2p2www/pages/site/docs/naming.html:183 -#: i2p2www/pages/site/docs/spec/configuration.html:170 +#: i2p2www/pages/site/docs/spec/configuration.html:184 msgid "Addressbook" msgstr "Libreta de direcciones" @@ -1492,7 +1506,7 @@ msgstr "" "una destinación." #: i2p2www/pages/site/docs/plugins.html:2 -#: i2p2www/pages/site/docs/spec/configuration.html:138 +#: i2p2www/pages/site/docs/spec/configuration.html:152 msgid "Plugins" msgstr "Complementos" @@ -3306,15 +3320,20 @@ msgstr "" "href=\"http://%(postman)s/?page_id=16\">%(postman)s" #: i2p2www/pages/site/docs/api/i2ptunnel.html:54 +#, fuzzy +msgid "Configuration" +msgstr "Configurabilidad" + +#: i2p2www/pages/site/docs/api/i2ptunnel.html:58 msgid "Client Modes" msgstr "Modos de cliente" -#: i2p2www/pages/site/docs/api/i2ptunnel.html:55 -#: i2p2www/pages/site/docs/api/i2ptunnel.html:137 +#: i2p2www/pages/site/docs/api/i2ptunnel.html:59 +#: i2p2www/pages/site/docs/api/i2ptunnel.html:141 msgid "Standard" msgstr "Estándar" -#: i2p2www/pages/site/docs/api/i2ptunnel.html:56 +#: 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" @@ -3325,7 +3344,7 @@ msgstr "" "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:62 +#: i2p2www/pages/site/docs/api/i2ptunnel.html:66 msgid "" "A HTTP-client tunnel. The tunnel connects to the destination specified by" " the URL\n" @@ -3339,7 +3358,7 @@ msgstr "" "un proxy externo (`outproxy`). Desnuda las conexiones HTTP de las \n" "siguientes cabeceras: " -#: i2p2www/pages/site/docs/api/i2ptunnel.html:67 +#: 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 " @@ -3349,7 +3368,7 @@ msgstr "" "Ranges ya que varían bastante entre navegadores y pueden usarse como " "identificador." -#: i2p2www/pages/site/docs/api/i2ptunnel.html:75 +#: i2p2www/pages/site/docs/api/i2ptunnel.html:79 msgid "" "HTTP client/server tunnels are via I2Ptunnel force-enabling compression " "via the following http headers:" @@ -3357,7 +3376,7 @@ 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:82 +#: 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:" @@ -3366,15 +3385,15 @@ msgstr "" "no, \n" "adherirá el siguiente Agente de Usuario (`User-Agent`):" -#: i2p2www/pages/site/docs/api/i2ptunnel.html:86 +#: i2p2www/pages/site/docs/api/i2ptunnel.html:90 msgid "Outproxy:" msgstr "Proxy de salida:" -#: i2p2www/pages/site/docs/api/i2ptunnel.html:87 +#: i2p2www/pages/site/docs/api/i2ptunnel.html:91 msgid "Internal I2P use:" msgstr "Uso interno de I2P:" -#: i2p2www/pages/site/docs/api/i2ptunnel.html:92 +#: i2p2www/pages/site/docs/api/i2ptunnel.html:96 msgid "" "Creates a connection to a random IRC server specified by the comma " "seprated (\", \") \n" @@ -3387,15 +3406,15 @@ msgstr "" " \n" "de la lista blanca están permitidos debido a cuestiones de anonimato." -#: i2p2www/pages/site/docs/api/i2ptunnel.html:96 +#: i2p2www/pages/site/docs/api/i2ptunnel.html:100 msgid "Whitelist:" msgstr "Lista blanca:" -#: i2p2www/pages/site/docs/api/i2ptunnel.html:111 +#: i2p2www/pages/site/docs/api/i2ptunnel.html:115 msgid "Enables using the I2P router as a SOCKS proxy." msgstr "Habilita el uso del router I2P como un proxy SOCKS." -#: i2p2www/pages/site/docs/api/i2ptunnel.html:116 +#: 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" @@ -3406,7 +3425,7 @@ msgstr "" "de comandos especificada por el modo cliente del IRC." -#: i2p2www/pages/site/docs/api/i2ptunnel.html:122 +#: 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." @@ -3414,7 +3433,7 @@ 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:128 +#: 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" @@ -3424,17 +3443,17 @@ msgstr "" "túnel \n" "del cliente streamr se suscribirá a un túnel de servidor streamr." -#: i2p2www/pages/site/docs/api/i2ptunnel.html:136 +#: i2p2www/pages/site/docs/api/i2ptunnel.html:140 msgid "Server Modes" msgstr "Modos de servidor" -#: i2p2www/pages/site/docs/api/i2ptunnel.html:138 +#: 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." -#: i2p2www/pages/site/docs/api/i2ptunnel.html:143 +#: 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" @@ -3447,7 +3466,7 @@ msgstr "" "`Accept-encoding: x-i2p-gzip`, responde con `Content-encoding: x-i2p-" "gzip` a tal petición." -#: i2p2www/pages/site/docs/api/i2ptunnel.html:149 +#: 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" @@ -3463,7 +3482,7 @@ msgstr "" "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:156 +#: i2p2www/pages/site/docs/api/i2ptunnel.html:160 msgid "" "Creates a destination that filters the reqistration sequence of a client " "and passes \n" @@ -3474,7 +3493,7 @@ msgstr "" "clave de destino de los clientes como un nombre de servidor al servidor-" "IRC." -#: i2p2www/pages/site/docs/api/i2ptunnel.html:162 +#: 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." @@ -4661,8 +4680,8 @@ msgstr "" #: i2p2www/pages/site/docs/how/tunnel-routing.html:255 #: i2p2www/pages/site/docs/protocol/i2cp.html:687 #: i2p2www/pages/site/docs/protocol/i2np.html:226 -#: i2p2www/pages/site/docs/spec/updates.html:438 -#: i2p2www/pages/site/docs/transport/ntcp.html:535 +#: i2p2www/pages/site/docs/spec/updates.html:488 +#: i2p2www/pages/site/docs/transport/ntcp.html:544 #: i2p2www/pages/site/docs/transport/ssu.html:554 #: i2p2www/pages/site/docs/tunnels/implementation.html:506 msgid "Future Work" @@ -5527,6 +5546,14 @@ msgstr "Encajar 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 "" + +#: 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" "If done wrong, it could cause real harm to our network.\n" @@ -5541,11 +5568,11 @@ msgstr "" "complejidad a sus usuarios.\n" "Esta página discute algunas directrices generales." -#: i2p2www/pages/site/docs/applications/embedding.html:18 +#: i2p2www/pages/site/docs/applications/embedding.html:23 msgid "Talk to us" msgstr "Hable con nosotros" -#: i2p2www/pages/site/docs/applications/embedding.html:19 +#: 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" @@ -5557,11 +5584,11 @@ msgstr "" "más prometedoras - y excitantes - para nosotros, para expandir la red y " "mejorar el anonimato para todos." -#: i2p2www/pages/site/docs/applications/embedding.html:25 +#: i2p2www/pages/site/docs/applications/embedding.html:30 msgid "Choose your router wisely" msgstr "Escoja su router I2P con sabiduría" -#: i2p2www/pages/site/docs/applications/embedding.html:26 +#: 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" @@ -5579,21 +5606,21 @@ msgstr "" "aplicación.\n" "Parte de lo que sigue sólo se aplica al router I2P Java." -#: i2p2www/pages/site/docs/applications/embedding.html:34 +#: i2p2www/pages/site/docs/applications/embedding.html:39 msgid "Licensing" msgstr "Licenciamiento" -#: i2p2www/pages/site/docs/applications/embedding.html:35 +#: 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." -#: i2p2www/pages/site/docs/applications/embedding.html:40 +#: i2p2www/pages/site/docs/applications/embedding.html:45 msgid "Verify default configuration" msgstr "Verificar la configuración por defecto" -#: i2p2www/pages/site/docs/applications/embedding.html:41 +#: i2p2www/pages/site/docs/applications/embedding.html:46 msgid "" "A correct default configuration is crucial. Most users will not change " "the defaults.\n" @@ -5608,7 +5635,7 @@ msgstr "" "empaquetando.\n" "Imponer la configuración por defecto del router IP2 si es necesario." -#: i2p2www/pages/site/docs/applications/embedding.html:46 +#: i2p2www/pages/site/docs/applications/embedding.html:51 msgid "" "Some important defaults to review: Max bandwidth, tunnel quantity and " "length, max participating tunnels.\n" @@ -5621,7 +5648,7 @@ msgstr "" "Muchas de estas dependen del ancho de banda esperado y del uso de " "patrones por parte de su aplicación." -#: i2p2www/pages/site/docs/applications/embedding.html:50 +#: i2p2www/pages/site/docs/applications/embedding.html:55 msgid "" "Configure enough bandwidth and tunnels to allow your users to contribute " "to the network.\n" @@ -5638,11 +5665,11 @@ msgstr "" "Revise también las configuraciones, por ejemplo, para deshabilitar el " "cierre forzado de la JVM al salir." -#: i2p2www/pages/site/docs/applications/embedding.html:57 +#: i2p2www/pages/site/docs/applications/embedding.html:62 msgid "Participating Traffic Considerations" msgstr "Consideraciones sobre el tráfico participante" -#: i2p2www/pages/site/docs/applications/embedding.html:58 +#: 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, " @@ -5664,7 +5691,7 @@ msgstr "" "Sin embargo, hay muchas razones por las que debe permitir los túneles " "participantes." -#: i2p2www/pages/site/docs/applications/embedding.html:65 +#: 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" @@ -5675,7 +5702,7 @@ msgstr "" "la cual está recibiendo una ayuda tremenda por parte de otros que " "construyen túneles a través de usted." -#: i2p2www/pages/site/docs/applications/embedding.html:69 +#: i2p2www/pages/site/docs/applications/embedding.html:74 msgid "" "Secondly, over 90% of the routers in the current network allow " "participating traffic.\n" @@ -5696,7 +5723,7 @@ msgstr "" "pasaremos nuestro tiempo suplicando a la gente que habilite la repetición" " entre nodos." -#: i2p2www/pages/site/docs/applications/embedding.html:76 +#: i2p2www/pages/site/docs/applications/embedding.html:81 msgid "" "Thirdly, participating traffic is cover traffic that helps your users' " "anonymity." @@ -5704,7 +5731,7 @@ 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:79 +#: i2p2www/pages/site/docs/applications/embedding.html:84 msgid "" "We strongly discourage you from disabling participating traffic by " "default.\n" @@ -5716,11 +5743,11 @@ msgstr "" "Si hace esto y su aplicación se vuelve enormemente popular, podría " "estropear la red." -#: i2p2www/pages/site/docs/applications/embedding.html:85 +#: i2p2www/pages/site/docs/applications/embedding.html:90 msgid "Persistence" msgstr "Persistencia" -#: i2p2www/pages/site/docs/applications/embedding.html:86 +#: 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" @@ -5737,11 +5764,11 @@ msgstr "" "Incluso si empaqueta la información (info) de los routers, I2P necesita " "datos de perfil guardados para un rendimiento óptimo." -#: i2p2www/pages/site/docs/applications/embedding.html:94 +#: i2p2www/pages/site/docs/applications/embedding.html:99 msgid "Configurability" msgstr "Configurabilidad" -#: i2p2www/pages/site/docs/applications/embedding.html:95 +#: i2p2www/pages/site/docs/applications/embedding.html:100 msgid "" "Give your users a way to change the configuration of the important " "settings.\n" @@ -5759,11 +5786,11 @@ msgstr "" "configuraciones de red tales como UPnP, IP/puerto podrían ser " "provechosas." -#: i2p2www/pages/site/docs/applications/embedding.html:103 +#: i2p2www/pages/site/docs/applications/embedding.html:108 msgid "Floodfill Considerations" msgstr "Consideraciones de inundación" -#: i2p2www/pages/site/docs/applications/embedding.html:104 +#: 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" @@ -5783,11 +5810,11 @@ msgstr "" "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:114 +#: i2p2www/pages/site/docs/applications/embedding.html:119 msgid "Reseeding" msgstr "Resembrado" -#: i2p2www/pages/site/docs/applications/embedding.html:115 +#: 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 " @@ -5801,11 +5828,11 @@ msgstr "" "también lo estará.\n" "Esté alerta ante posibles bloqueos por parte de Gobiernos hostiles." -#: i2p2www/pages/site/docs/applications/embedding.html:124 +#: i2p2www/pages/site/docs/applications/embedding.html:129 msgid "Reduce Network Resource Usage" msgstr "Reducir consumo de recursos de red" -#: i2p2www/pages/site/docs/applications/embedding.html:125 +#: 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" @@ -5822,11 +5849,11 @@ msgstr "" "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:133 +#: i2p2www/pages/site/docs/applications/embedding.html:138 msgid "Updatability" msgstr "Actualizabilidad" -#: i2p2www/pages/site/docs/applications/embedding.html:134 +#: 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" @@ -5854,11 +5881,11 @@ msgstr "" "router,\n" "que presumiblemente usted no está empaquetando." -#: i2p2www/pages/site/docs/applications/embedding.html:145 +#: i2p2www/pages/site/docs/applications/embedding.html:150 msgid "Rollout" msgstr "Presentación" -#: i2p2www/pages/site/docs/applications/embedding.html:146 +#: 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 " @@ -5887,11 +5914,11 @@ msgstr "" "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:158 +#: i2p2www/pages/site/docs/applications/embedding.html:163 msgid "Design for and Encourage Long Uptimes" msgstr "Diseño para promover ejecuciones de larga duración" -#: i2p2www/pages/site/docs/applications/embedding.html:159 +#: 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 " @@ -5906,11 +5933,11 @@ msgstr "" "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:167 +#: i2p2www/pages/site/docs/applications/embedding.html:172 msgid "Show Status" msgstr "Mostrar estado" -#: i2p2www/pages/site/docs/applications/embedding.html:168 +#: i2p2www/pages/site/docs/applications/embedding.html:173 msgid "" "Provide some indication to the user that the application tunnels are " "ready. Encourage patience." @@ -5918,11 +5945,11 @@ 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:173 +#: i2p2www/pages/site/docs/applications/embedding.html:178 msgid "Graceful Shutdown" msgstr "Cierre ordenado" -#: i2p2www/pages/site/docs/applications/embedding.html:174 +#: 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 " @@ -5933,11 +5960,11 @@ msgstr "" "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:180 +#: i2p2www/pages/site/docs/applications/embedding.html:185 msgid "Education and Donation" msgstr "Educación y donación" -#: i2p2www/pages/site/docs/applications/embedding.html:181 +#: 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." @@ -5945,11 +5972,11 @@ 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:187 +#: i2p2www/pages/site/docs/applications/embedding.html:192 msgid "External Router Option" msgstr "Opción de router I2P externo" -#: i2p2www/pages/site/docs/applications/embedding.html:188 +#: 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 " @@ -5959,11 +5986,11 @@ msgstr "" "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:195 +#: i2p2www/pages/site/docs/applications/embedding.html:200 msgid "Use of other Common Services" msgstr "" -#: i2p2www/pages/site/docs/applications/embedding.html:196 +#: 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" @@ -5971,11 +5998,11 @@ msgid "" "and talk to the people who are running them to make sure it's ok." msgstr "" -#: i2p2www/pages/site/docs/applications/embedding.html:204 +#: i2p2www/pages/site/docs/applications/embedding.html:209 msgid "Time / NTP Issues" msgstr "" -#: i2p2www/pages/site/docs/applications/embedding.html:205 +#: 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. " @@ -5984,11 +6011,11 @@ msgid "" "clock is correct." msgstr "" -#: i2p2www/pages/site/docs/applications/embedding.html:213 +#: i2p2www/pages/site/docs/applications/embedding.html:218 msgid "Choose What and How you Bundle" msgstr "" -#: i2p2www/pages/site/docs/applications/embedding.html:214 +#: 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" @@ -6006,11 +6033,19 @@ msgid "" "and i2psnark, for example." msgstr "" -#: i2p2www/pages/site/docs/applications/embedding.html:228 +#: i2p2www/pages/site/docs/applications/embedding.html:233 +msgid "You may also wish to bundle a hosts.txt file." +msgstr "" + +#: i2p2www/pages/site/docs/applications/embedding.html:236 +msgid "Be sure to specify a Java 6 bootclasspath if compiling with Java 8." +msgstr "" + +#: i2p2www/pages/site/docs/applications/embedding.html:244 msgid "Datagram (DHT) considerations" msgstr "" -#: i2p2www/pages/site/docs/applications/embedding.html:229 +#: 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 " @@ -6026,32 +6061,32 @@ msgid "" "have several." msgstr "" -#: i2p2www/pages/site/docs/applications/embedding.html:242 +#: i2p2www/pages/site/docs/applications/embedding.html:258 msgid "Comarketing" msgstr "" -#: i2p2www/pages/site/docs/applications/embedding.html:243 +#: 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 "" -#: i2p2www/pages/site/docs/applications/embedding.html:249 +#: i2p2www/pages/site/docs/applications/embedding.html:265 msgid "Malware" msgstr "" -#: i2p2www/pages/site/docs/applications/embedding.html:250 +#: i2p2www/pages/site/docs/applications/embedding.html:266 msgid "" "Please don't use I2P for evil.\n" "It could cause great harm both to our network and our reputation." msgstr "" -#: i2p2www/pages/site/docs/applications/embedding.html:256 +#: i2p2www/pages/site/docs/applications/embedding.html:272 msgid "Join Us" msgstr "" -#: i2p2www/pages/site/docs/applications/embedding.html:257 +#: 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" @@ -6059,11 +6094,11 @@ msgid "" "We can help get you users, testers, translators, or even coders." msgstr "" -#: i2p2www/pages/site/docs/applications/embedding.html:265 +#: i2p2www/pages/site/docs/applications/embedding.html:281 msgid "Application Examples" msgstr "" -#: i2p2www/pages/site/docs/applications/embedding.html:266 +#: 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" @@ -6073,17 +6108,17 @@ msgid "" " and Monero." msgstr "" -#: i2p2www/pages/site/docs/applications/embedding.html:274 +#: i2p2www/pages/site/docs/applications/embedding.html:290 msgid "Code Example" msgstr "" -#: i2p2www/pages/site/docs/applications/embedding.html:275 +#: i2p2www/pages/site/docs/applications/embedding.html:291 msgid "" "None of the above actually tells you how to write your code to\n" "bundle the Java router, so following is a brief example." msgstr "" -#: i2p2www/pages/site/docs/applications/embedding.html:290 +#: 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" @@ -10038,7 +10073,6 @@ msgid "The Network Database" msgstr "La base de datos de la red" #: i2p2www/pages/site/docs/how/network-database.html:3 -#: i2p2www/pages/site/docs/transport/ntcp.html:3 msgid "October 2014" msgstr "Octubre de 2014" @@ -20297,10 +20331,6 @@ msgstr "" msgid "Configuration File Specification" msgstr "Especificación de fichero de configuración" -#: i2p2www/pages/site/docs/spec/configuration.html:3 -msgid "January 2014" -msgstr "Enero de 2014" - #: i2p2www/pages/site/docs/spec/configuration.html:7 msgid "" "This page provides a general specification of I2P configuration files,\n" @@ -20440,69 +20470,70 @@ msgid "Configured via /configlogging in the router console." msgstr "Configurado mediante /configlogging en la consola del router." #: i2p2www/pages/site/docs/spec/configuration.html:112 -#: i2p2www/pages/site/docs/spec/configuration.html:142 -#: i2p2www/pages/site/docs/spec/configuration.html:154 +#: i2p2www/pages/site/docs/spec/configuration.html:156 +#: i2p2www/pages/site/docs/spec/configuration.html:168 +#: i2p2www/pages/site/docs/spec/configuration.html:198 msgid "Properties are as follows:" msgstr "Las propiedades son como sigue:" -#: i2p2www/pages/site/docs/spec/configuration.html:133 +#: i2p2www/pages/site/docs/spec/configuration.html:147 msgid "Individual Plugin" msgstr "Complemento (`plugin`) individual" -#: i2p2www/pages/site/docs/spec/configuration.html:134 +#: i2p2www/pages/site/docs/spec/configuration.html:148 #, python-format msgid "See the plugin specification." msgstr "" "Vea la especificación de plugins " "(complementos)." -#: i2p2www/pages/site/docs/spec/configuration.html:139 +#: i2p2www/pages/site/docs/spec/configuration.html:153 msgid "Enable/disable for each installed plugin." msgstr "Habilitar/deshabilitar para cada complemento (`plugin`) instalado" -#: i2p2www/pages/site/docs/spec/configuration.html:150 +#: i2p2www/pages/site/docs/spec/configuration.html:164 msgid "Webapps" msgstr "Aplicaciones web" -#: i2p2www/pages/site/docs/spec/configuration.html:151 +#: i2p2www/pages/site/docs/spec/configuration.html:165 msgid "Enable/disable for each installed webapp." msgstr "Habilitar/deshabilitar para cada aplicación web instalada." -#: i2p2www/pages/site/docs/spec/configuration.html:163 +#: i2p2www/pages/site/docs/spec/configuration.html:177 msgid "Router" msgstr "Router" -#: i2p2www/pages/site/docs/spec/configuration.html:164 +#: i2p2www/pages/site/docs/spec/configuration.html:178 msgid "Configured via /configadvanced in the router console." msgstr "Configurado mediante /configadvanced en la consola del router." -#: i2p2www/pages/site/docs/spec/configuration.html:168 +#: i2p2www/pages/site/docs/spec/configuration.html:182 msgid "Applications" msgstr "Aplicaciones" -#: i2p2www/pages/site/docs/spec/configuration.html:171 +#: i2p2www/pages/site/docs/spec/configuration.html:185 msgid "See documentation in SusiDNS." msgstr "Vea la documentación en SusiDNS." -#: i2p2www/pages/site/docs/spec/configuration.html:176 +#: 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." -#: i2p2www/pages/site/docs/spec/configuration.html:181 +#: i2p2www/pages/site/docs/spec/configuration.html:195 msgid "Configured via the /i2ptunnel application in the router console." msgstr "Configurado mediante la aplicación /i2ptunnel en la consola del router." -#: i2p2www/pages/site/docs/spec/configuration.html:185 +#: i2p2www/pages/site/docs/spec/configuration.html:364 msgid "Router Console" msgstr "Consola del router" -#: i2p2www/pages/site/docs/spec/configuration.html:186 +#: i2p2www/pages/site/docs/spec/configuration.html:365 msgid "The router console uses the router.config file." msgstr "La consola del router usa el fichero `router.config`." -#: i2p2www/pages/site/docs/spec/configuration.html:191 +#: i2p2www/pages/site/docs/spec/configuration.html:370 msgid "See post on zzz.i2p." msgstr "Vea el post en `zzz.i2p`. " @@ -21025,6 +21056,7 @@ msgstr "" #: i2p2www/pages/site/docs/spec/updates.html:204 #: i2p2www/pages/site/docs/spec/updates.html:313 +#: i2p2www/pages/site/docs/spec/updates.html:365 msgid "Goals:" msgstr "Objetivos:" @@ -21050,7 +21082,8 @@ msgid "One-pass signature verification and file extraction" msgstr "" #: i2p2www/pages/site/docs/spec/updates.html:222 -#: i2p2www/pages/site/docs/spec/updates.html:336 +#: i2p2www/pages/site/docs/spec/updates.html:328 +#: i2p2www/pages/site/docs/spec/updates.html:388 msgid "Specification:" msgstr "Especificación:" @@ -21061,40 +21094,80 @@ msgstr "" "futuras versiones." #: i2p2www/pages/site/docs/spec/updates.html:308 -msgid "SU3 News File Specification" -msgstr "" +#, fuzzy +msgid "SU3 Reseed File Specification" +msgstr "Especificación del archivo de noticias" #: i2p2www/pages/site/docs/spec/updates.html:309 -msgid "As of 0.9.17, the news is delivered in an \"su3\" file format." +msgid "As of 0.9.14, reseed data is delivered in an \"su3\" file format." msgstr "" #: i2p2www/pages/site/docs/spec/updates.html:316 -msgid "Signed news with strong signatures and trusted certificates" +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 "" -#: i2p2www/pages/site/docs/spec/updates.html:319 +#: 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 "" -#: i2p2www/pages/site/docs/spec/updates.html:322 -msgid "Standard XML format for use with standard parsers" -msgstr "" - -#: i2p2www/pages/site/docs/spec/updates.html:325 -msgid "Standard Atom format for use with standard feed readers and generators" -msgstr "" - -#: i2p2www/pages/site/docs/spec/updates.html:328 -msgid "Sanitization and verification of HTML before displaying on console" +#: i2p2www/pages/site/docs/spec/updates.html:323 +msgid "" +"Single compressed file to speed up reseeding, which was slow to fetch 200" +" files" msgstr "" #: i2p2www/pages/site/docs/spec/updates.html:331 +msgid "The file must be named \"i2pseeds.su3\"." +msgstr "" + +#: i2p2www/pages/site/docs/spec/updates.html:334 +msgid "" +"The file must be in the same directory as the router infos on the web " +"server." +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" +"and then fetch the individual router info files found in the links." +msgstr "" + +#: i2p2www/pages/site/docs/spec/updates.html:360 +msgid "SU3 News File Specification" +msgstr "" + +#: i2p2www/pages/site/docs/spec/updates.html:361 +msgid "As of 0.9.17, the news is delivered in an \"su3\" file format." +msgstr "" + +#: i2p2www/pages/site/docs/spec/updates.html:368 +msgid "Signed news with strong signatures and trusted certificates" +msgstr "" + +#: i2p2www/pages/site/docs/spec/updates.html:374 +msgid "Standard XML format for use with standard parsers" +msgstr "" + +#: i2p2www/pages/site/docs/spec/updates.html:377 +msgid "Standard Atom format for use with standard feed readers and generators" +msgstr "" + +#: i2p2www/pages/site/docs/spec/updates.html:380 +msgid "Sanitization and verification of HTML before displaying on console" +msgstr "" + +#: i2p2www/pages/site/docs/spec/updates.html:383 msgid "" "Suitable for easy implementation on Android and other platforms without " "an HTML console" msgstr "" -#: i2p2www/pages/site/docs/spec/updates.html:440 +#: 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" @@ -21891,7 +21964,7 @@ msgstr "" #: i2p2www/pages/site/docs/transport/ntcp.html:207 #: i2p2www/pages/site/docs/transport/ntcp.html:250 #: i2p2www/pages/site/docs/transport/ntcp.html:332 -#: i2p2www/pages/site/docs/transport/ntcp.html:428 +#: i2p2www/pages/site/docs/transport/ntcp.html:437 msgid "Size:" msgstr "Tamaño:" @@ -21909,7 +21982,7 @@ msgstr "SHA256 Hash(X) XOReado con SHA256 Hash(`RouterIdentity` de Bob) " #: i2p2www/pages/site/docs/transport/ntcp.html:236 #: i2p2www/pages/site/docs/transport/ntcp.html:319 -#: i2p2www/pages/site/docs/transport/ntcp.html:397 +#: i2p2www/pages/site/docs/transport/ntcp.html:398 msgid "Notes:" msgstr "Notas:" @@ -21931,7 +22004,7 @@ msgstr "Esta es la respuesta DH. Bob envía a Alice:" #: i2p2www/pages/site/docs/transport/ntcp.html:252 #: i2p2www/pages/site/docs/transport/ntcp.html:334 -#: i2p2www/pages/site/docs/transport/ntcp.html:430 +#: i2p2www/pages/site/docs/transport/ntcp.html:439 msgid "Unencrypted Contents:" msgstr "Contenidos no cifrados:" @@ -21957,7 +22030,7 @@ msgstr "12 bytes datos aleatorios" #: i2p2www/pages/site/docs/transport/ntcp.html:285 #: i2p2www/pages/site/docs/transport/ntcp.html:376 -#: i2p2www/pages/site/docs/transport/ntcp.html:457 +#: i2p2www/pages/site/docs/transport/ntcp.html:466 msgid "Encrypted Contents:" msgstr "Contenidos cifrados:" @@ -22003,7 +22076,7 @@ msgid "Alice's 387+ byte `RouterIdentity`" msgstr "'RouterIdentity' (identificación de router I2P) de 387+ bytes de Alice" #: i2p2www/pages/site/docs/transport/ntcp.html:366 -#: i2p2www/pages/site/docs/transport/ntcp.html:452 +#: i2p2www/pages/site/docs/transport/ntcp.html:461 msgid "0-15 bytes random data" msgstr "0-15 bytes de datos aleatorios" @@ -22033,11 +22106,11 @@ msgstr "" " 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:399 +#: i2p2www/pages/site/docs/transport/ntcp.html:400 msgid "Bob verifies the signature, and on failure, drops the connection." msgstr "Bob verifica la firma, y si falla, rechaza la conexión." -#: i2p2www/pages/site/docs/transport/ntcp.html:402 +#: i2p2www/pages/site/docs/transport/ntcp.html:403 msgid "" "Bob may drop the connection if the clock skew with Alice is too high as " "calculated using tsA." @@ -22045,7 +22118,7 @@ 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:405 +#: 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." @@ -22053,15 +22126,15 @@ 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:421 +#: i2p2www/pages/site/docs/transport/ntcp.html:430 msgid "Message 4 (Session Confirm B)" msgstr "Mensaje 4 (Confirmar Sesión B)" -#: i2p2www/pages/site/docs/transport/ntcp.html:422 +#: i2p2www/pages/site/docs/transport/ntcp.html:431 msgid "This is a signature of the critical data. Bob sends Alice:" msgstr "Esta es una firma de los datos críticos. Bob le envía a Alice:" -#: i2p2www/pages/site/docs/transport/ntcp.html:446 +#: i2p2www/pages/site/docs/transport/ntcp.html:455 msgid "" "the `Signature` of the following concatenated data:\n" " X, Y, Alice's `RouterIdentity`, tsA, tsB.\n" @@ -22075,7 +22148,7 @@ msgstr "" " con la `SigningPublicKey` (clave pública firmante) en su " "`RouterIdentity`" -#: i2p2www/pages/site/docs/transport/ntcp.html:470 +#: i2p2www/pages/site/docs/transport/ntcp.html:479 #, python-format msgid "" "Data AES encrypted using the DH " @@ -22091,11 +22164,11 @@ msgstr "" "(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:479 +#: i2p2www/pages/site/docs/transport/ntcp.html:488 msgid "Alice verifies the signature, and on failure, drops the connection." msgstr "Alice verifica la firma, y en caso de fallo, rechaza la conexión." -#: i2p2www/pages/site/docs/transport/ntcp.html:482 +#: 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." @@ -22103,11 +22176,11 @@ 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:497 +#: i2p2www/pages/site/docs/transport/ntcp.html:506 msgid "After Establishment" msgstr "Después del establecimiento" -#: i2p2www/pages/site/docs/transport/ntcp.html:498 +#: i2p2www/pages/site/docs/transport/ntcp.html:507 msgid "" "The connection is established, and standard or time sync messages may be " "exchanged.\n" @@ -22125,11 +22198,11 @@ msgstr "" "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:507 +#: i2p2www/pages/site/docs/transport/ntcp.html:516 msgid "Check Connection Message" msgstr "Mensaje de conexión del reloj" -#: i2p2www/pages/site/docs/transport/ntcp.html:508 +#: i2p2www/pages/site/docs/transport/ntcp.html:517 msgid "" "Alternately, when Bob receives a connection, it could be a\n" "check connection (perhaps prompted by Bob asking for someone\n" @@ -22145,15 +22218,15 @@ msgstr "" "formateadas como sigue. Una conexión de prueba de información recibirá " "256 bytes que contienen:" -#: i2p2www/pages/site/docs/transport/ntcp.html:517 +#: i2p2www/pages/site/docs/transport/ntcp.html:526 msgid "32 bytes of uninterpreted, ignored data" msgstr "32 bytes sin interpretar, datos ignorados" -#: i2p2www/pages/site/docs/transport/ntcp.html:518 +#: i2p2www/pages/site/docs/transport/ntcp.html:527 msgid "1 byte size" msgstr "tamaño de 1 byte" -#: i2p2www/pages/site/docs/transport/ntcp.html:519 +#: 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)" @@ -22161,11 +22234,11 @@ 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:520 +#: i2p2www/pages/site/docs/transport/ntcp.html:529 msgid "2 byte port number that the local router was reached on" msgstr "el número de puerto de 2 bytes, en donde ha sido contactado el ruter local" -#: i2p2www/pages/site/docs/transport/ntcp.html:521 +#: i2p2www/pages/site/docs/transport/ntcp.html:530 msgid "" "4 byte i2p network time as known by the remote side (seconds since the " "epoch)" @@ -22173,11 +22246,11 @@ 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:522 +#: i2p2www/pages/site/docs/transport/ntcp.html:531 msgid "uninterpreted padding data, up to byte 223" msgstr "datos de relleno sin interpretar, hasta 223 bytes" -#: i2p2www/pages/site/docs/transport/ntcp.html:523 +#: 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" @@ -22185,28 +22258,28 @@ 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:526 +#: 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." -#: i2p2www/pages/site/docs/transport/ntcp.html:530 +#: i2p2www/pages/site/docs/transport/ntcp.html:539 msgid "Discussion" msgstr "Discusión" -#: i2p2www/pages/site/docs/transport/ntcp.html:531 +#: i2p2www/pages/site/docs/transport/ntcp.html:540 #, python-format msgid "Now on the NTCP Discussion Page." msgstr "Ahora en al Página de discusión de NTCP." -#: i2p2www/pages/site/docs/transport/ntcp.html:537 +#: 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" -#: i2p2www/pages/site/docs/transport/ntcp.html:541 +#: 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" @@ -22223,7 +22296,7 @@ msgstr "" "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:549 +#: 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." @@ -22231,7 +22304,7 @@ 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:553 +#: 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?" diff --git a/i2p2www/translations/es/LC_MESSAGES/get-involved.po b/i2p2www/translations/es/LC_MESSAGES/get-involved.po index 92f7618c..0a21ba7c 100644 --- a/i2p2www/translations/es/LC_MESSAGES/get-involved.po +++ b/i2p2www/translations/es/LC_MESSAGES/get-involved.po @@ -16,7 +16,7 @@ msgid "" msgstr "" "Project-Id-Version: I2P\n" "Report-Msgid-Bugs-To: http://trac.i2p2.de\n" -"POT-Creation-Date: 2014-10-22 20:13+0000\n" +"POT-Creation-Date: 2014-11-27 12:12+0000\n" "PO-Revision-Date: 2014-10-24 14:41+0000\n" "Last-Translator: strel\n" "Language-Team: Spanish " @@ -507,433 +507,62 @@ msgstr "" "href=\"%(volunteer)s\">¡Únete!" #: i2p2www/pages/site/get-involved/todo.html:15 -#: i2p2www/pages/site/get-involved/todo.html:53 +#: i2p2www/pages/site/get-involved/todo.html:38 msgid "Core functionality" msgstr "Funcionamiento del núcleo." #: i2p2www/pages/site/get-involved/todo.html:15 -#: i2p2www/pages/site/get-involved/todo.html:27 -#: i2p2www/pages/site/get-involved/todo.html:51 +#: i2p2www/pages/site/get-involved/todo.html:21 +#: i2p2www/pages/site/get-involved/todo.html:36 msgid "link" msgstr "enlace" #: i2p2www/pages/site/get-involved/todo.html:17 -#: i2p2www/pages/site/get-involved/todo.html:56 -msgid "NAT/Firewall bridging via 1-hop restricted routes" -msgstr "Puenteando el NAT/cortafuegos a través de ruters restringidos de 1 salto" - -#: i2p2www/pages/site/get-involved/todo.html:20 -#: i2p2www/pages/site/get-involved/todo.html:129 -msgid "High degree transport layer with UDP, NBIO, or NIO" -msgstr "Capa de transporte de alto nivel con UDP, NBIO, o NIO" - -#: i2p2www/pages/site/get-involved/todo.html:23 -#: i2p2www/pages/site/get-involved/todo.html:217 +#: 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. " -#: i2p2www/pages/site/get-involved/todo.html:27 -#: i2p2www/pages/site/get-involved/todo.html:241 +#: i2p2www/pages/site/get-involved/todo.html:21 +#: i2p2www/pages/site/get-involved/todo.html:65 msgid "Security / anonymity" msgstr "Seguridad / anonimato" -#: i2p2www/pages/site/get-involved/todo.html:29 -#: i2p2www/pages/site/get-involved/todo.html:244 -msgid "" -"Per-hop tunnel id & new permuted TunnelVerificationStructure " -"encryption" -msgstr "" -"Id por salto de túnel & nuevo cifrado permutado de la estructura de " -"verificación del túnel, TunnelVerificationStructure" - -#: i2p2www/pages/site/get-involved/todo.html:32 -#: i2p2www/pages/site/get-involved/todo.html:294 -msgid "Strict ordering of participants within tunnels" -msgstr "Orden estricto de los participantes dentro de los túneles" - -#: i2p2www/pages/site/get-involved/todo.html:35 -msgid "Randomly permuted tunnel lengths" -msgstr "Tamaño de los túneles aleatorio." - -#: i2p2www/pages/site/get-involved/todo.html:38 -#: i2p2www/pages/site/get-involved/todo.html:356 +#: 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." -#: i2p2www/pages/site/get-involved/todo.html:41 -#: i2p2www/pages/site/get-involved/todo.html:375 +#: 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." -#: i2p2www/pages/site/get-involved/todo.html:44 -#: i2p2www/pages/site/get-involved/todo.html:404 +#: 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)" -#: i2p2www/pages/site/get-involved/todo.html:47 -#: i2p2www/pages/site/get-involved/todo.html:441 +#: 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." -#: i2p2www/pages/site/get-involved/todo.html:51 -#: i2p2www/pages/site/get-involved/todo.html:455 +#: i2p2www/pages/site/get-involved/todo.html:36 +#: i2p2www/pages/site/get-involved/todo.html:167 msgid "Performance" msgstr "Rendimiento" -#: i2p2www/pages/site/get-involved/todo.html:61 -msgid "Implemented in I2P 0.6.0.6" -msgstr "Implementado en I2P 0.6.0.6" - -#: i2p2www/pages/site/get-involved/todo.html:62 -msgid "" -"The functionality of allowing routers to fully participate within the " -"network \n" -"while behind firewalls and NATs that they do not control requires some " -"basic \n" -"restricted route operation (since those peers will not be able to receive" -" \n" -"inbound connections). To do this successfully, you consider peers one of" -" \n" -"two ways:" -msgstr "" -"Esta capacidad permite a los ruters participar totalmente dentro de la " -"red incluso detrás de un NAT o cortafuegos de los que no se tienen " -"control (ya que estos pares no podrán recibir conexiones entrantes). " -"Para hacer esto satisfactoriamente, consideramos a los pares de estas dos" -" formas:" - -#: i2p2www/pages/site/get-involved/todo.html:72 -msgid "" -"Peers who have reachable interfaces - these peers do not need to \n" -"do anything special" -msgstr "" -"Pares que tienen algún dispositivo accesible - estos pares no " -"necesitan hacer nada especial" - -#: i2p2www/pages/site/get-involved/todo.html:76 -msgid "" -"Peers who do not have reachable interfaces - these peers must " -"build \n" -"a tunnel pointing at them where the gateway is one of the peers they have" -" \n" -"established a connection with who has both a publicly reachable interface" -" \n" -"and who has agreed to serve as their 'introducer'." -msgstr "" -"Pares que no tienen dispositivos accesibles - estos pares tienen " -"que construir un túnel hacia ellos mismos en donde la salida es uno de " -"los pares con los que ya ha establecido una conexión y quien tiene un " -"dispositivo accesible públicamente y ha aceptado servir como su " -"'introductor'." - -#: i2p2www/pages/site/get-involved/todo.html:84 -msgid "" -"To do this, peers who have no IP address simply connect to a few peers, \n" -"build a tunnel through them, and publish a reference to those tunnels " -"within \n" -"their RouterInfo structure in the network database." -msgstr "" -"Para hacer esto, los pares que no tiene dirección IP simplemente se " -"conectan a varios pares, construye un túnel a través de ellos, y publican" -" una referencia de esos túneles dentro de la estructura RouterInfo en la " -"base de datos dela red." - -#: i2p2www/pages/site/get-involved/todo.html:89 -msgid "" -"When someone wants to contact any particular router, they first must get" -" \n" -"its RouterInfo from the network database, which will tell them whether " -"they \n" -"can connect directly (e.g. the peer has a publicly reachable interface) \n" -"or whether they need to contact them indirectly. Direct connections occur" -" \n" -"as normal, while indirect connections are done through one of the " -"published \n" -"tunnels." -msgstr "" -"Cuando alguien quiere conectar con algún ruter en particular, el primero " -"debe obtener su RouterInfo de la base de datos de la red, la que le " -"indicará que puede conectarse directamente ( por ejemplo con un par que " -"tiene un dispositivo accesible públicamente) o que necesita conectar " -"indirectamente. La conexiones directas se hacen directamente, pero las " -"indirectas se hacen a través de los túneles publicados. " - -#: i2p2www/pages/site/get-involved/todo.html:97 -msgid "" -"When a router just wants to get a message or two to a specific hidden " -"peer, \n" -"they can just use the indirect tunnel for sending the payload. However, \n" -"if the router wants to talk to the hidden peer often (for instance, as " -"part \n" -"of a tunnel), they will send a garlic routed message through the indirect" -" \n" -"tunnel to that hidden peer which unwraps to contain a message which " -"should \n" -"be sent to the originating router. That hidden peer then establishes an \n" -"outbound connection to the originating router and from then on, those two" -" \n" -"routers can talk to each other directly over that newly established " -"direct \n" -"connection." -msgstr "" -"Cuando un ruter simplemente quiere enviar un mensaje a un par oculto " -"puede usar el túnel indirecto para enviar la información. Sin embargo, si" -" el ruter quiere hablar con el par oculto a menudo (por ejemplo, como " -"parte de un túnel), enviará un mensaje enrutado a través del túnel " -"indirecto del par oculto. Entonces este par oculto establece una conexión" -" de salida hacia el ruter original y a partir de entonces estos dos " -"ruters puede hablar entre ellos directamente sobre la nueva conexión " -"directa. " - -#: i2p2www/pages/site/get-involved/todo.html:108 -msgid "" -"Of course, that only works if the originating peer can receive " -"connections \n" -"(they aren't also hidden). However, if the originating peer is hidden, " -"they \n" -"can simply direct the garlic routed message to come back to the " -"originating \n" -"peer's inbound tunnel." -msgstr "" -"Por supuesto esto solo funciona si el par original puede recibir " -"conexiones (y no están también ocultas). Sin embargo, si el par original " -"está oculto, pueden simplemente indicar la mensaje enrutado que vuelva " -"por el túnel de entrada del par original. " - -#: i2p2www/pages/site/get-involved/todo.html:114 -msgid "" -"This is not meant to provide a way for a peer's IP address to be " -"concealed, \n" -"merely as a way to let people behind firewalls and NATs fully operate " -"within \n" -"the network. Concealing the peer's IP address adds a little more work, as" -" \n" -"described below." -msgstr "" -"Esto no se ha creado para permitir que la IP de un par permanezca oculta," -" simplemente es una forma de permitir a la gente detrás de un NAT o " -"cortafuegos funcionar completamente dentro de la red. Ocultar la IP de un" -" par cuesta un poco más de trabajo, como se describe más abajo." - -#: i2p2www/pages/site/get-involved/todo.html:120 -msgid "" -"With this technique, any router can participate as any part of a tunnel." -" \n" -"For efficiency purposes, a hidden peer would be a bad choice for an " -"inbound \n" -"gateway, and within any given tunnel, two neighboring peers wouldn't want" -" \n" -"to be hidden. But that is not technically necessary." -msgstr "" -"Con esta técnica cualquier ruter puede participar como una parte de un " -"túnel. Con objeto de mejorar la eficiencia, un par oculto sería una mala " -"elección como puerta de entrada, y dentro de un túnel dado, dos pares " -"vecinos no desearían estar ocultos. Pero esto no es técnicamente " -"necesario." - -#: i2p2www/pages/site/get-involved/todo.html:132 -msgid "Both UDP and NIO have been Implemented in I2P" -msgstr "Ambos, UDP y NIO ya han sido implementados en I2P" - -#: i2p2www/pages/site/get-involved/todo.html:133 -msgid "" -"Standard TCP communication in Java generally requires blocking socket \n" -"calls, and to keep a blocked socket from hanging the entire system, those" -" \n" -"blocking calls are done on their own threads. Our current TCP transport \n" -"is implemented in a naive fashion - for each peer we are talking to, we \n" -"have one thread reading and one thread writing. The reader thread simply" -" \n" -"loops a bunch of read() calls, building I2NP messages and adding them \n" -"to our internal inbound message queue, and the writer thread pulls " -"messages \n" -"off a per-connection outbound message queue and shoves the data through \n" -"write() calls." -msgstr "" -"Las comunicaciones estándar TCP en java normalmente necesitan el bloqueo " -"de llamadas al socket, y para evitar que el socket bloqueado pare todo el" -" sistema, estos bloqueos se hacen en sus propios hilos. Nuestro sistema " -"de transporte TCP actual está implementado de una forma sencilla - por " -"cada par con el que hablamos, tenemos un hilo escribiendo y otro leyendo." -" El hilo de lectura simplemente repite un puñado de llamadas read(), " -"creando mensajes I2NP y añadiéndolos a la cola interna de mensajes de " -"entrada, y el hilo de escritura envía mensajes hacia una cola de mensajes" -" de salida y empuja los datos a través de llamadas write()." - -#: i2p2www/pages/site/get-involved/todo.html:144 -msgid "" -"We do this fairly efficiently, from a CPU perspective - at any time, \n" -"almost all of these threads are sitting idle, blocked waiting for " -"something \n" -"to do. However, each thread consumes real resources (on older Linux " -"kernels, \n" -"for instance, each thread would often be implemented as a fork()'ed " -"process). \n" -"As the network grows, the number of peers each router will want to talk \n" -"with will increase (remember, I2P is fully connected, meaning that any \n" -"given peer should know how to get a message to any other peer, and " -"restricted \n" -"route support will probably not significantly reduce the number of " -"connections \n" -"necessary). This means that with a 100,000 router network, each router \n" -"will have up to 199,998 threads just to deal with the TCP connections!" -msgstr "" -"Desde la perspectiva del uso de CPU esto se hace bastante eficientemente " -"- la mayoría del tiempo la mayoría de estos hilos están dormidos " -"esperando por algo que hacer. Sin embargo, cada uno de estos hilos " -"consume recursos (en kernels viejos de Linux, por ejemplo, cada hilo se " -"implementa como un proceso fork()'ed). Al mismo tiempo que la red crece, " -"el número de pares con el que se comunica un ruter aumentará (recuerde, " -"I2P está totalmente conectado, esto quiere decir que cualquier par debe " -"saber como enviar un mensaje a cualquier otro par). ¡Esto significa que " -"con una red de 100.000 ruters, cada ruter tendrá 199.998 hilos " -"simplemente para tratar con las conexiones TCP!" - -#: i2p2www/pages/site/get-involved/todo.html:156 -msgid "" -"Obviously, that just won't work. We need to use a transport layer that \n" -"can scale. In Java, we have two main camps:" -msgstr "" -"Obviamente esto no funcionará. Necesitamos una capa de transporte que " -"pueda escalar. En Java tenemos dos posibles soluciones:" - -#: i2p2www/pages/site/get-involved/todo.html:161 -#, python-format -msgid "" -"Implemented in I2P 0.6 (\"SSU\") as documented elsewhere" -msgstr "" -"Implementado en 2P 0.6 (\"SSU\") y documentado en en " -"otra parte" - -#: i2p2www/pages/site/get-involved/todo.html:164 -msgid "" -"Sending and receiving UDP datagrams is a connectionless operation - if \n" -"we are communicating with 100,000 peers, we simply stick the UDP packets" -" \n" -"in a queue and have a single thread pulling them off the queue and " -"shoving \n" -"them out the pipe (and to receive, have a single thread pulling in any \n" -"UDP packets received and adding them to an inbound queue)." -msgstr "" -"Enviar y recibir datagramas UDP es una operación que no necesita de " -"conexión previa - si estamos comunicándonos con 1000.000 pares, " -"simplemente ponemos los paquetes UDP en una cola y hacemos que un único " -"hilo los envíe fuera de la cola hacia una tubería ( y para recibir, " -"tenemos un único hilo tirando de cualquier paquete UDP recibido y " -"añadiéndolos a una cola de entrada)" - -#: i2p2www/pages/site/get-involved/todo.html:171 -msgid "" -"However, moving to UDP means losing the benefits of TCP's ordering, " -"congestion \n" -"control, MTU discovery, etc. Implementing that code will take significant" -" \n" -"work, however I2P doesn't need it to be as strong as TCP. Specifically, \n" -"a while ago I was taking some measurements in the simulator and on the \n" -"live net, and the vast majority of messages transferred would fit easily" -" \n" -"within a single unfragmented UDP packet, and the largest of the messages" -" \n" -"would fit within 20-30 packets. As mule pointed out, TCP adds a " -"significant \n" -"overhead when dealing with so many small packets, as the ACKs are within" -" \n" -"an order of magnitude in size. With UDP, we can optimize the transport \n" -"for both efficiency and resilience by taking into account I2P's " -"particular \n" -"needs." -msgstr "" -"Sin embargo, usar UDP significa perder los beneficios de usar el orden de" -" TCP, el control de congestión, descubrimiento de MTU, etc. Implementar " -"esto significaría mucho trabajo, sin embargo I2P no necesita ser tan " -"fuerte como TCP. Hace algún tiempo estaba tomando medida en un simulador " -"y en la red real, y la mayoría de los mensajes pueden ser transmitidas " -"dentro de un único paquete UDP no fragmentado, y el más largo de los " -"mensajes entraría dentro de 20-30 paquetes. Como mule indicó, TCP añade " -"bastante gasto cuando tiene que encargarse de muchos paquetes pequeños. " -"Con UDP, se puede optimizar el transporte para la eficiencia y la " -"flexibilidad teniendo en cuenta las necesidades particulares de I2P." - -#: i2p2www/pages/site/get-involved/todo.html:184 -msgid "It will be a lot of work though." -msgstr "Sería muchísimo trabajo por hacer." - -#: i2p2www/pages/site/get-involved/todo.html:187 -msgid "NIO or NBIO" -msgstr "NIO o NBIO" - -#: i2p2www/pages/site/get-involved/todo.html:188 -msgid "NIO Implemented in I2P 0.6.1.22 (\"NTCP\")" -msgstr "NIO fue implementada en la versión 0.6.1.22 de I2P (\"NTCP\")" - -#: i2p2www/pages/site/get-involved/todo.html:191 -msgid "" -"In Java 1.4, a set of \"New I/O\" packages was introduced, allowing Java" -" \n" -"developers to take advantage of the operating system's nonblocking IO \n" -"capabilities - allowing you to maintain a large number of concurrent IO \n" -"operations without requiring a separate thread for each. There is much \n" -"promise with this approach, as we can scalable handle a large number of \n" -"concurrent connections and we don't have to write a mini-TCP stack with \n" -"UDP. However, the NIO packages have not proven themselves to be battle-" -"ready, \n" -"as the Freenet developer's found. In addition, requiring NIO support " -"would \n" -"mean we can't run on any of the open source JVMs like Kaffe, \n" -"as GNU/Classpath has only " -"limited \n" -"support for NIO. (note: this may not be the case anymore, as there \n" -"has been some progress on Classpath's NIO, but it is an unknown " -"quantity)" -msgstr "" -"En Java 1.4 se introdujo paquetes \"I/O nuevos\", permitiendo a los " -"desarrolladores de java usar las capacidades de los sistemas operativos " -"sin bloquear las entradas y salidas - permitiendo tener un gran número de" -" operaciones I/O concurrentes si necesitar un nuevo hilo para cada una. " -"Hay muchas esperanzas puestas en este método, ya que podemos manejar un " -"gran número de conexiones y no tendríamos que que reescribir un nuevo " -"mini TCP stack con UDP. Sin embargo, los paquetes NIO no han probado aún " -"estar listos, como averiguaron los desarrolladores de Freenet. Además, " -"usar paquetes NIO significaría no poder usar ninguna JVM libre como Kaffe, ya que GNU/Classpath sólo tiene soporte " -"limitado para NIO.(nota: puede que ahora esto ya no sea verdad, ya que" -" se han hecho progreso en los NIO de Classpath, pero no sabemos su " -"calidad)" - -#: i2p2www/pages/site/get-involved/todo.html:205 -#, python-format -msgid "" -"Another alternative along the same lines is the Non" -" \n" -"Blocking I/O package - essentially a cleanroom NIO implementation \n" -"(written before NIO was around). It works by using some native OS code \n" -"to do the nonblocking IO, passing off events through Java. It seems to \n" -"be working with Kaffe, though there doesn't seem to be much development \n" -"activity on it lately (likely due to 1.4's NIO deployment)." -msgstr "" -"Otra alternativa del mismo tipo es el paquete sin " -"bloqueos I/O - básicamente es una implementación NIO tipo cleanroom " -"(escrita antes de que NIO existiese). Funciona utilizando algo de código " -"nativo del sistema operativo para hacer I/O sin bloqueos, pasando los " -"eventos a través de Java. Parece que funciona con Kaffe, aunque no parece" -" que haya mucha actividad últimamante en su desarrollo (debido " -"probablemente al desarrollo de NIO 1.4) " - -#: i2p2www/pages/site/get-involved/todo.html:220 +#: i2p2www/pages/site/get-involved/todo.html:44 msgid "" "Within the current network database and profile management " "implementation, \n" @@ -970,7 +599,7 @@ msgstr "" "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:235 +#: 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" @@ -980,221 +609,7 @@ msgstr "" "estas consideraciones. Tendremos algún trabajo por hacer, pero se puede " "dejar para mas tarde." -#: i2p2www/pages/site/get-involved/todo.html:247 -#: i2p2www/pages/site/get-involved/todo.html:331 -#, python-format -msgid "" -"Addressed in I2P 0.5 as documented elsewhere" -msgstr "" -"Conseguido en I2P 0.5 como se documenta aquí" - -#: i2p2www/pages/site/get-involved/todo.html:250 -msgid "" -"Right now, if Alice builds a four hop inbound tunnel starting at Elvis, \n" -"going to Dave, then to Charlie, then Bob, and finally Alice " -"(A<--B<--C<--D<--E), \n" -"all five of them will know they are participating in tunnel \"123\", as \n" -"the messages are tagged as such. What we want to do is give each hop " -"their \n" -"own unique tunnel hop ID - Charlie will receive messages on tunnel 234 \n" -"and forward them to tunnel 876 on Bob. The intent is to prevent Bob or \n" -"Charlie from knowing that they are in Alice's tunnel, as if each hop in \n" -"the tunnel had the same tunnel ID, collusion attacks aren't much work." -msgstr "" -"Ahora mismo si Alicia crea un túnel de entrada de cuatro saltos empezando" -" en Elvis, yendo a través de Dave, después Charlie, después Bob y " -"finalmente Alice (A<--B<--C<--D<--E), los cinco sabrán que " -"están participando en el túnel \"123\", ya que el mensaje está etiquetado" -" así. Lo que queremos hacer es dar a cada salto su propio ID de túnel - " -"Charlie recibirá el mensaje en el túnel 234 y lo enviará al túnel 876 de " -"Bob. Se intenta prevenir que Bob o Charlie sepan que están en el túnel de" -" Alice, lo que ocurriría si en cada salto tuviesen el mismo ID de túnel " -"haciendo que un ataque por colisión fuese más fácil." - -#: i2p2www/pages/site/get-involved/todo.html:260 -msgid "" -"Adding a unique tunnel ID per hop isn't hard, but by itself, " -"insufficient. \n" -"If Dave and Bob are under the control of the same attacker, they wouldn't" -" \n" -"be able to tell they are in the same tunnel due to the tunnel ID, but \n" -"would be able to tell by the message bodies and verification structures \n" -"by simply comparing them. To prevent that, the tunnel must use layered \n" -"encryption along the path, both on the payload of the tunneled message \n" -"and on the verification structure (used to prevent simple tagging " -"attacks). \n" -"This requires some simple modifications to the TunnelMessage, as well \n" -"as the inclusion of per-hop secret keys delivered during tunnel creation" -" \n" -"and given to the tunnel's gateway. We must fix a maximum tunnel length \n" -"(e.g. 16 hops) and instruct the gateway to encrypt the message to each \n" -"of the 16 delivered secret keys, in reverse order, and to encrypt the \n" -"signature of the hash of the (encrypted) payload at each step. The " -"gateway \n" -"then sends that 16-step encrypted message, along with a 16-step and " -"16-wide \n" -"encrypted mapping to the first hop, which then decrypts the mapping and \n" -"the payload with their secret key, looking in the 16-wide mapping for \n" -"the entry associated with their own hop (keyed by the per-hop tunnel ID)" -" \n" -"and verifying the payload by checking it against the associated signed \n" -"hash." -msgstr "" -"Añadir un Id único por cada salto no es difícil, pero sí insuficiente. Si" -" Dave y Bob están bajo el control del mismo atacante no sería posible " -"saber que están en el mismo túnel a causa del Id, pero podría se capaz de" -" saber sobre el cuerpo del mensaje y las estructuras de verificación con " -"solo compararlos. Para prevenir esto el túnel debe usar una capa de " -"cifrado a lo largo del camino, en el payload tunelado y en la " -"verificación de la estructura (usado para evitar ataques simples de " -"etiquetado). Esto requiere algunos cambios simples en el TunnelMessage, y" -" además, requiere del envío de claves secretas por cada salto durante la " -"creación del túnel, y además hacer llegar estas claves a la salida del " -"túnel. Tenemos que que crear un valor máximo del tamaño del túnel (por " -"ejemplo 16), e instruir a la puerta de salida para que cifre el mensaje " -"de cada una de las claves secretas enviadas, en orden inverso, y de que " -"cifre la firma del hash del payload (cifrado) en cada salto. La puerta de" -" salida envía entonces el mensaje cifrado de 16 pasos, junto con los 16 " -"pasos y el mapeado cifrado de 16 de ancho al primer salto, el cual " -"entonces descifra el mapeado y el payload con su clave secreta, buscando" -" en el mapeado de 16 de ancho por la entrada asociada con su propio salto" -" (cifrado por el Id del túnel de cada salto) y verificando el pyload " -"chequeándolo con el hash firmado asociado." - -#: i2p2www/pages/site/get-involved/todo.html:281 -msgid "" -"The tunnel gateway does still have more information than the other peers" -" \n" -"in the tunnel, and compromising both the gateway and a tunnel participant" -" \n" -"would allow those peers to collude, exposing the fact that they are both" -" \n" -"in the same tunnel. In addition, neighboring peers know that they are \n" -"in the same tunnel anyway, as they know who they send the message to (and" -" \n" -"with IP-based transports without restricted routes, they know who they \n" -"got it from). However, the above two techniques significantly increase \n" -"the cost of gaining meaningful samples when dealing with longer tunnels." -msgstr "" -"La salida del túnel todavía tiene más información que los otros pares del" -" túnel, y comprometiendo la salida y un participante en el túnel " -"permitiría a estos confabularse mostrando el hecho de que los dos " -"pertenecen al mismo túnel. Además, los pares vecinos saben que están en " -"el mismo túnel, ya que saben a quien envían el mensaje (y con transportes" -" basados en IP con rutas restrictivas saben de donde lo reciben). Sin " -"embargo, estas dos técnicas incrementan significativamente el coste de " -"conseguir ejemplos con significado cuando se trata de túneles largos." - -#: i2p2www/pages/site/get-involved/todo.html:297 -msgid "Implemented in release 0.6.2" -msgstr "Implementado en la versión 0.6.2" - -#: i2p2www/pages/site/get-involved/todo.html:300 -#, python-format -msgid "" -"As Connelly proposed to deal with the\n" -"predecessor attack (2008\n" -"update), keeping the order of peers within our tunnels consistent \n" -"(aka whenever Alice creates a tunnel with both Bob and Charlie in it, \n" -"Bob's next hop is always Charlie), we address the issue as Bob doesn't \n" -"get to substantially sample Alice's peer selection group. We may even \n" -"want to explicitly allow Bob to participate in Alice's tunnels in only \n" -"one way - receiving a message from Dave and sending it to Charlie - and \n" -"if any of those peers are not available to participate in the tunnel (due" -" \n" -"to overload, network disconnection, etc), avoid asking Bob to participate" -" \n" -"in any tunnels until they are back online." -msgstr "" -"Como propuso Connelly para tratar el ataque del predecesor(2008), manteniendo consistente el orden de los " -"pares dentro de nuestros túneles (osea cuando Alice crea un túnel con Bob" -" y Charlei en él, el siguiente salto de Bob es siempre Charlie), " -"solucionamos el problema, ya que Bob no puede obtener una muestra del " -"grupo de pares de Alice lo suficientemente grande. Incluso podríamos " -"querer permitir explícitamente a Bob participar en el túnel de Alice en " -"una dirección - recibiendo un mensaje de Dave y enviándolo a Charlie - y " -"si unos de estos pares no están disponible para participar en el túnel " -"(debido a saturación, desconexión de red, erc), evitar preguntar a Bob si" -" participa en algún túnel hasta que vuelva a estar disponible." - -#: i2p2www/pages/site/get-involved/todo.html:315 -msgid "" -"More analysis is necessary for revising the tunnel creation - at the \n" -"moment, we simply select and order randomly within the peer's top tier \n" -"of peers (ones with fast + high capacity)." -msgstr "" -"Aún hace falta un análisis más detallado de la creación del túnel - hasta" -" el momento, simplemente seleccionamos y ordenamos aleatoriamente de " -"entre uno de los mejores pares del par (uno rápido y con gran capacidad)" - -#: i2p2www/pages/site/get-involved/todo.html:320 -msgid "" -"Adding a strict ordering to peers in a tunnel also improves the anonymity" -" \n" -"of peers with 0-hop tunnels, as otherwise the fact that a peer's gateway" -" \n" -"is always the same would be particularly damning. However, peers with \n" -"0-hop tunnels may want to periodically use a 1-hop tunnel to simulate \n" -"the failure of a normally reliable gateway peer (so every MTBF*(tunnel \n" -"duration) minutes, use a 1-hop tunnel)." -msgstr "" -"Añadiendo un orden estricto a los pares de un túnel también mejoramos el " -"anonimato de los pares con túneles de 0 saltos, ya que de otra forma el " -"hecho de que la salida del par fuese siempre la misma sería bastante " -"dañino. Sin embargo, los pares con túneles de 0 saltos necesitarán usar " -"periódicamente un túnel de 1 salto para simular el fallo de un par de " -"salida normal (así cada MTBF*(duración del túnel) minutos, usaría un " -"túnel de 1 salto)" - -#: i2p2www/pages/site/get-involved/todo.html:337 -msgid "" -"Without tunnel length permutation, if someone were to somehow detect that" -" \n" -"a destination had a particular number of hops, it might be able to use " -"that \n" -"information to identify the router the destination is located on, per the" -" \n" -"predecessor attack. For instance, if everyone has 2-hop tunnels, if Bob \n" -"receives a tunnel message from Charlie and forwards it to Alice, Bob " -"knows \n" -"Alice is the final router in the tunnel. If Bob were to identify what " -"destination \n" -"that tunnel served (by means of colluding with the gateway and harvesting" -" \n" -"the network database for all of the LeaseSets), he would know the router" -" \n" -"on which that destination is located (and without restricted routes, that" -" \n" -"would mean what IP address the destination is on)." -msgstr "" -"Sin los cambios de tamaño de los túneles, si alguien de alguna forma " -"detectase que una destinación tiene un número determinado de saltos, " -"sería capaz de usar esa información para identificar la localización de " -"la destinación de ruter usando el ataque del predecesor. Por ejemplo, si" -" todo el mundo tiene túneles de 2 saltos, si Bob recibe un mensaje de " -"Charlie y lo envía a Alice, Bob sabría que que Alice es el ruter final " -"del túnel. Si Bob quisiese identificar la destinación que ese túnel " -"sirvió (confabulándose con el nodo de salida y buscando en la base de " -"datos de la red a todos los LeaseSets), conocería el ruter que está en " -"esa destinación ( y sin rutas restringidas, eso quiere decir que " -"sabríamos la IP de la destinación)" - -#: i2p2www/pages/site/get-involved/todo.html:349 -msgid "" -"It is to counter user behavior that tunnel lengths should be permuted, \n" -"using algorithms based on the length requested (for example, the 1/MTBF \n" -"length change for 0-hop tunnels outlined above)." -msgstr "" -"El tamaño de los túneles debe ser cambiante para contrarrestar el " -"comportamiento de los usuarios, usando algoritmos basados en el tamaño " -"requerido (por ejemplo, el cambio de tamaño a 1/MTBF de los túneles de 0 " -"saltos)" - -#: i2p2www/pages/site/get-involved/todo.html:359 +#: i2p2www/pages/site/get-involved/todo.html:71 msgid "" "The restricted route functionality described before was simply a " "functional \n" @@ -1226,7 +641,7 @@ msgstr "" " 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:378 +#: i2p2www/pages/site/get-involved/todo.html:90 #, python-format msgid "" "Within the network, we will want some way to deter people from consuming" @@ -1247,7 +662,7 @@ msgstr "" "anonimato del sistema. En su lugar queremos hacer que ciertas peticiones " "sean muy \"caras\"." -#: i2p2www/pages/site/get-involved/todo.html:386 +#: 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 " @@ -1275,7 +690,7 @@ msgstr "" "suficientemente caro pero no tan caro como para que agobie a la gente con" " pocos recursos." -#: i2p2www/pages/site/get-involved/todo.html:397 +#: 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" @@ -1286,7 +701,7 @@ msgstr "" " de recursos \"tengan un costo\", sería conveniente seguir investigando " "sobre este tema." -#: i2p2www/pages/site/get-involved/todo.html:407 +#: i2p2www/pages/site/get-involved/todo.html:119 #, python-format msgid "" "To powerful passive external observers as well as large colluding " @@ -1318,7 +733,7 @@ msgstr "" "href=\"%(pdf)s\">estudios sobre estos algoritmos que podríamos " "utilizar para implementar varias estrategias de mezclado de túneles." -#: i2p2www/pages/site/get-involved/todo.html:420 +#: 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" @@ -1347,7 +762,7 @@ msgstr "" "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:433 +#: i2p2www/pages/site/get-involved/todo.html:145 msgid "" "In addition, we may want to implement code to dynamically reroute tunnels" " \n" @@ -1362,7 +777,7 @@ msgstr "" "mensaje a un par en particular con las instrucciones para redefinir el " "siguiente salto del túnel." -#: i2p2www/pages/site/get-involved/todo.html:444 +#: 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" @@ -1384,7 +799,7 @@ msgstr "" "de los pares, excepto a cualquier par donde se hayan dado instrucciones " "de retardo." -#: i2p2www/pages/site/get-involved/todo.html:456 +#: i2p2www/pages/site/get-involved/todo.html:168 #, python-format msgid "" "Performance related improvements are listed on the\n" @@ -5669,3 +5084,16 @@ msgstr "" "El canal #i2p-dev del IRC, o el forum de traducción en %(zzz)s." + + + + + + + + + + + + + diff --git a/i2p2www/translations/fr/LC_MESSAGES/docs.po b/i2p2www/translations/fr/LC_MESSAGES/docs.po index 76bc6d05..0eee8a55 100644 --- a/i2p2www/translations/fr/LC_MESSAGES/docs.po +++ b/i2p2www/translations/fr/LC_MESSAGES/docs.po @@ -11,7 +11,7 @@ msgid "" msgstr "" "Project-Id-Version: I2P\n" "Report-Msgid-Bugs-To: http://trac.i2p2.de\n" -"POT-Creation-Date: 2014-11-16 02:59+0000\n" +"POT-Creation-Date: 2014-11-27 12:12+0000\n" "PO-Revision-Date: 2014-11-16 03:02+0000\n" "Last-Translator: str4d \n" "Language-Team: French " @@ -30,7 +30,9 @@ msgstr "Index de la documentation technique" #: i2p2www/pages/site/docs/applications/embedding.html:3 #: i2p2www/pages/site/docs/how/cryptography.html:3 #: i2p2www/pages/site/docs/protocol/i2cp.html:3 +#: i2p2www/pages/site/docs/spec/configuration.html:3 #: i2p2www/pages/site/docs/spec/updates.html:3 +#: i2p2www/pages/site/docs/transport/ntcp.html:3 msgid "November 2014" msgstr "" @@ -144,7 +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:217 +#: i2p2www/pages/site/docs/index.html:44 i2p2www/pages/site/docs/index.html:222 msgid "Embedding the router in your application" msgstr "" @@ -161,7 +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:189 +#: i2p2www/pages/site/docs/index.html:48 i2p2www/pages/site/docs/index.html:194 msgid "Configuration File Format" msgstr "Format de fichier de configuration" @@ -181,27 +183,33 @@ msgstr "" msgid "Application Development Overview and Guide" msgstr "Vue d'ensemble et guide de développement d'application" -#: i2p2www/pages/site/docs/index.html:72 +#: i2p2www/pages/site/docs/index.html:58 +#: i2p2www/pages/site/docs/api/i2ptunnel.html:55 +#, fuzzy +msgid "I2PTunnel Configuration" +msgstr "Création de tunnel" + +#: i2p2www/pages/site/docs/index.html:74 msgid "SAM Protocol" msgstr "Protocole SAM" -#: i2p2www/pages/site/docs/index.html:74 +#: i2p2www/pages/site/docs/index.html:76 msgid "SAMv2 Protocol" msgstr "Protocole SAMv2" -#: i2p2www/pages/site/docs/index.html:76 +#: i2p2www/pages/site/docs/index.html:78 msgid "SAMv3 Protocol" msgstr "Protocole SAMv3" -#: i2p2www/pages/site/docs/index.html:78 +#: i2p2www/pages/site/docs/index.html:80 msgid "BOB Protocol" msgstr "Protocole BOB" -#: i2p2www/pages/site/docs/index.html:81 +#: i2p2www/pages/site/docs/index.html:83 msgid "End-to-End Transport API and Protocols" msgstr "API et protocoles de transport de bout en bout " -#: i2p2www/pages/site/docs/index.html:82 +#: i2p2www/pages/site/docs/index.html:84 msgid "" "The end-to-end protocols used by clients for reliable and unreliable " "communication." @@ -209,33 +217,33 @@ 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:84 +#: i2p2www/pages/site/docs/index.html:86 #: i2p2www/pages/site/docs/api/streaming.html:2 msgid "Streaming Library" msgstr "Bibliothèque streaming" -#: i2p2www/pages/site/docs/index.html:86 +#: i2p2www/pages/site/docs/index.html:88 msgid "Streaming Protocol Specification" msgstr "Spécifications du protocole Streaming" -#: i2p2www/pages/site/docs/index.html:88 +#: i2p2www/pages/site/docs/index.html:90 msgid "Streaming Javadoc" msgstr "Javadoc streaming" -#: i2p2www/pages/site/docs/index.html:90 +#: i2p2www/pages/site/docs/index.html:92 #: i2p2www/pages/site/docs/api/datagrams.html:2 msgid "Datagrams" msgstr "Datagrammes" -#: i2p2www/pages/site/docs/index.html:92 +#: i2p2www/pages/site/docs/index.html:94 msgid "Datagram Javadoc" msgstr "Javadoc datagramme" -#: i2p2www/pages/site/docs/index.html:95 +#: i2p2www/pages/site/docs/index.html:97 msgid "Client-to-Router Interface API and Protocol" msgstr "API de l'interface client-à-routeur et protocole" -#: i2p2www/pages/site/docs/index.html:96 +#: 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" @@ -246,54 +254,54 @@ msgstr "" "Traditionnellement utilisée seulement par les applications Java et les " "API de plus haut niveau." -#: i2p2www/pages/site/docs/index.html:101 +#: i2p2www/pages/site/docs/index.html:103 msgid "I2CP - I2P Control Protocol / API overview" msgstr "I2CP - Protocole contrôle I2P / Vue d'ensemble d'API" -#: i2p2www/pages/site/docs/index.html:103 +#: i2p2www/pages/site/docs/index.html:105 msgid "I2CP Specification" msgstr "Spécification de I2CP" -#: i2p2www/pages/site/docs/index.html:105 +#: i2p2www/pages/site/docs/index.html:107 msgid "I2CP API Javadoc" msgstr "Javadoc API I2CP" -#: i2p2www/pages/site/docs/index.html:107 -#: i2p2www/pages/site/docs/index.html:136 +#: i2p2www/pages/site/docs/index.html:109 +#: i2p2www/pages/site/docs/index.html:139 msgid "Common data structures specification" msgstr "Spécification des structures de données communes" -#: i2p2www/pages/site/docs/index.html:109 -#: i2p2www/pages/site/docs/index.html:138 +#: i2p2www/pages/site/docs/index.html:111 +#: i2p2www/pages/site/docs/index.html:141 msgid "Data Structures Javadoc" msgstr "Javadoc structures données" -#: i2p2www/pages/site/docs/index.html:112 +#: i2p2www/pages/site/docs/index.html:114 msgid "End-to-End Encryption" msgstr "Chiffrage bout à bout" -#: i2p2www/pages/site/docs/index.html:113 +#: 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." -#: i2p2www/pages/site/docs/index.html:115 +#: i2p2www/pages/site/docs/index.html:117 msgid "ElGamal/AES+SessionTag encryption" msgstr "Cryptage ElGamal/AES+SessionTag" -#: i2p2www/pages/site/docs/index.html:116 -#: i2p2www/pages/site/docs/index.html:149 +#: i2p2www/pages/site/docs/index.html:118 +#: i2p2www/pages/site/docs/index.html:152 msgid "ElGamal and AES cryptography details" msgstr "Détails cryptographie ElGamal et AES " -#: i2p2www/pages/site/docs/index.html:119 +#: i2p2www/pages/site/docs/index.html:121 #: i2p2www/pages/site/docs/how/tech-intro.html:15 #: i2p2www/pages/site/docs/how/tech-intro.html:329 msgid "Network Database" msgstr "Base de données réseau" -#: i2p2www/pages/site/docs/index.html:120 +#: i2p2www/pages/site/docs/index.html:122 msgid "" "Distributed storage and retrieval of information about routers and " "clients." @@ -301,23 +309,29 @@ msgstr "" "Stockage distribué et récupération d'informations concernant les routeurs" " et clients." -#: i2p2www/pages/site/docs/index.html:122 +#: i2p2www/pages/site/docs/index.html:124 msgid "Network database overview, details, and threat analysis" msgstr "Vue d'ensemble de base de données de réseau, détails, et analyse de menace" -#: i2p2www/pages/site/docs/index.html:123 +#: i2p2www/pages/site/docs/index.html:125 msgid "Cryptographic hashes" msgstr "Hachage cryptographique" -#: i2p2www/pages/site/docs/index.html:124 +#: i2p2www/pages/site/docs/index.html:126 msgid "Cryptographic signatures" msgstr "Signatures cryptographiques" #: i2p2www/pages/site/docs/index.html:127 +#: i2p2www/pages/site/docs/index.html:186 +#, fuzzy +msgid "Router reseed specification" +msgstr "Spécification de construction de tunnel" + +#: i2p2www/pages/site/docs/index.html:130 msgid "Router Message Protocol" msgstr "Protocole message router" -#: i2p2www/pages/site/docs/index.html:128 +#: i2p2www/pages/site/docs/index.html:131 msgid "" "I2P is a message-oriented router. The messages sent between routers are " "defined by the I2NP protocol." @@ -325,25 +339,25 @@ 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:130 +#: i2p2www/pages/site/docs/index.html:133 msgid "I2NP - I2P Network Protocol Overview" msgstr "I2NP - Vue d'ensemble de protocole de réseau I2P" -#: i2p2www/pages/site/docs/index.html:132 +#: i2p2www/pages/site/docs/index.html:135 msgid "I2NP Specification" msgstr "Spécification I2NP " -#: i2p2www/pages/site/docs/index.html:134 +#: i2p2www/pages/site/docs/index.html:137 msgid "I2NP Javadoc" msgstr "Javadoc I2NP" -#: i2p2www/pages/site/docs/index.html:141 +#: i2p2www/pages/site/docs/index.html:144 #: i2p2www/pages/site/docs/how/tech-intro.html:14 #: i2p2www/pages/site/docs/how/tech-intro.html:228 msgid "Tunnels" msgstr "Tunnels" -#: i2p2www/pages/site/docs/index.html:142 +#: i2p2www/pages/site/docs/index.html:145 msgid "" "Selecting peers, requesting tunnels through those peers, and encrypting " "and routing messages through these tunnels." @@ -351,152 +365,152 @@ 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:144 +#: i2p2www/pages/site/docs/index.html:147 msgid "Peer profiling and selection" msgstr "Profilage et sélection de pair" -#: i2p2www/pages/site/docs/index.html:145 +#: i2p2www/pages/site/docs/index.html:148 msgid "Tunnel routing overview" msgstr "Vue d'ensemble de l'acheminement de tunnel" -#: i2p2www/pages/site/docs/index.html:146 +#: i2p2www/pages/site/docs/index.html:149 msgid "Garlic routing and \"garlic\" terminology" msgstr "Cheminement en ail et terminologie \"ail\"" -#: i2p2www/pages/site/docs/index.html:147 +#: i2p2www/pages/site/docs/index.html:150 msgid "Tunnel building and encryption" msgstr "Construction de tunnel et chiffrage" -#: i2p2www/pages/site/docs/index.html:148 +#: i2p2www/pages/site/docs/index.html:151 msgid "ElGamal/AES" msgstr "ElGamal/AES" -#: i2p2www/pages/site/docs/index.html:148 +#: i2p2www/pages/site/docs/index.html:151 msgid "for build request encryption" msgstr "pour construire une requête de chiffrage" -#: i2p2www/pages/site/docs/index.html:150 +#: i2p2www/pages/site/docs/index.html:153 msgid "Tunnel building specification" msgstr "Spécification de construction de tunnel" -#: i2p2www/pages/site/docs/index.html:151 +#: i2p2www/pages/site/docs/index.html:154 msgid "Low-level tunnel message specification" msgstr "Spécification de message de tunnel bas niveau" -#: i2p2www/pages/site/docs/index.html:152 +#: i2p2www/pages/site/docs/index.html:155 #: i2p2www/pages/site/docs/tunnels/unidirectional.html:2 msgid "Unidirectional Tunnels" msgstr "Tunnels unidirectionels" -#: i2p2www/pages/site/docs/index.html:153 +#: i2p2www/pages/site/docs/index.html:156 #: i2p2www/pages/site/docs/how/peer-selection.html:299 msgid "Peer Profiling and Selection in the I2P Anonymous Network" msgstr "Profilage de pair et sélection dans le réseau anonyme I2P" -#: i2p2www/pages/site/docs/index.html:154 +#: i2p2www/pages/site/docs/index.html:157 msgid "2009 paper (pdf), not current but still generally accurate" msgstr "Papier de 2009 (pdf), pas actuel mais encore assez précis" -#: i2p2www/pages/site/docs/index.html:157 +#: i2p2www/pages/site/docs/index.html:160 msgid "Transport Layer" msgstr "Couche transport" -#: i2p2www/pages/site/docs/index.html:158 +#: 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." -#: i2p2www/pages/site/docs/index.html:160 +#: i2p2www/pages/site/docs/index.html:163 msgid "Transport layer overview" msgstr "Aperçu couche transport" -#: i2p2www/pages/site/docs/index.html:162 +#: i2p2www/pages/site/docs/index.html:165 msgid "TCP-based transport overview and specification" msgstr "Vue d'ensemble et spécification du transport basé-TCP" -#: i2p2www/pages/site/docs/index.html:164 +#: i2p2www/pages/site/docs/index.html:167 msgid "UDP-based transport overview" msgstr "Vue d'ensemble du transport basé-UDP" -#: i2p2www/pages/site/docs/index.html:166 +#: i2p2www/pages/site/docs/index.html:169 msgid "SSU specification" msgstr "Spécification SSU" -#: i2p2www/pages/site/docs/index.html:168 +#: i2p2www/pages/site/docs/index.html:171 msgid "NTCP transport encryption" msgstr "Chiffrage transport NTCP" -#: i2p2www/pages/site/docs/index.html:170 +#: i2p2www/pages/site/docs/index.html:173 msgid "SSU transport encryption" msgstr "Chiffrage transport SSU" -#: i2p2www/pages/site/docs/index.html:172 +#: i2p2www/pages/site/docs/index.html:175 msgid "Transport Javadoc" msgstr "Javadoc transport" -#: i2p2www/pages/site/docs/index.html:174 +#: i2p2www/pages/site/docs/index.html:177 msgid "NTCP Javadoc" msgstr "Javadoc NTCP" -#: i2p2www/pages/site/docs/index.html:176 +#: i2p2www/pages/site/docs/index.html:179 msgid "SSU Javadoc" msgstr "Javadoc SSU" -#: i2p2www/pages/site/docs/index.html:179 +#: i2p2www/pages/site/docs/index.html:182 msgid "Other Router Topics" msgstr "Autres sujets sur routeur" -#: i2p2www/pages/site/docs/index.html:181 +#: i2p2www/pages/site/docs/index.html:184 msgid "Router software updates" msgstr "Mises à jour de logiciel routeur" -#: i2p2www/pages/site/docs/index.html:183 +#: i2p2www/pages/site/docs/index.html:188 msgid "Native BigInteger Library" msgstr "Bibliothèque native BigInteger" -#: i2p2www/pages/site/docs/index.html:185 +#: i2p2www/pages/site/docs/index.html:190 msgid "Time synchronization and NTP" msgstr "Synchronisation de temps et NTP" -#: i2p2www/pages/site/docs/index.html:187 +#: i2p2www/pages/site/docs/index.html:192 msgid "Performance" msgstr "Performance" -#: i2p2www/pages/site/docs/index.html:194 +#: i2p2www/pages/site/docs/index.html:199 msgid "Developer's Guides and Resources" msgstr "Guides et ressources de développeur" -#: i2p2www/pages/site/docs/index.html:196 +#: i2p2www/pages/site/docs/index.html:201 msgid "New Developer's Guide" msgstr "Guide du nouveau développeur" -#: i2p2www/pages/site/docs/index.html:198 +#: i2p2www/pages/site/docs/index.html:203 msgid "New Translator's Guide" msgstr "Guide du nouveau traducteur" -#: i2p2www/pages/site/docs/index.html:200 +#: i2p2www/pages/site/docs/index.html:205 msgid "Monotone Guide" msgstr "Guide Monotone" -#: i2p2www/pages/site/docs/index.html:202 +#: i2p2www/pages/site/docs/index.html:207 msgid "Developer Guidelines" msgstr "Directives développeur" -#: i2p2www/pages/site/docs/index.html:204 +#: i2p2www/pages/site/docs/index.html:209 msgid "Javadocs on the standard internet:" msgstr "Javadocs sur l'internet standard :" -#: i2p2www/pages/site/docs/index.html:205 -#: i2p2www/pages/site/docs/index.html:209 #: i2p2www/pages/site/docs/index.html:210 -#: i2p2www/pages/site/docs/index.html:211 +#: i2p2www/pages/site/docs/index.html:214 +#: i2p2www/pages/site/docs/index.html:215 +#: i2p2www/pages/site/docs/index.html:216 #, python-format msgid "Server %(num)s" msgstr "Serveur %(num)s" -#: i2p2www/pages/site/docs/index.html:206 -#: i2p2www/pages/site/docs/index.html:215 +#: i2p2www/pages/site/docs/index.html:211 +#: i2p2www/pages/site/docs/index.html:220 msgid "" "Note: always verify that javadocs are current by checking the release " "number." @@ -504,66 +518,66 @@ msgstr "" "Notez : vérifiez toujours que javadocs sont actuelles en vérifiant le " "numéro de version." -#: i2p2www/pages/site/docs/index.html:208 +#: i2p2www/pages/site/docs/index.html:213 msgid "Javadocs inside I2P:" msgstr "Javadocs à l'intérieur de I2P :" -#: i2p2www/pages/site/docs/index.html:219 +#: i2p2www/pages/site/docs/index.html:224 msgid "Ports used by I2P" msgstr "Ports utilisés par I2P" -#: i2p2www/pages/site/docs/index.html:221 +#: 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" -#: i2p2www/pages/site/docs/index.html:223 +#: i2p2www/pages/site/docs/index.html:228 msgid "Updating the wrapper manually" msgstr "Mettre à jour le wrapper manuellement" -#: i2p2www/pages/site/docs/index.html:225 +#: i2p2www/pages/site/docs/index.html:230 msgid "User forum" msgstr "Forum utilisateur" -#: i2p2www/pages/site/docs/index.html:227 +#: i2p2www/pages/site/docs/index.html:232 msgid "Developer forum inside I2P" msgstr "Forum développeur à l'intérieur de I2P" -#: i2p2www/pages/site/docs/index.html:229 +#: i2p2www/pages/site/docs/index.html:234 msgid "Bug tracker" msgstr "Traqueur de bugs" -#: i2p2www/pages/site/docs/index.html:231 +#: i2p2www/pages/site/docs/index.html:236 msgid "Viewmtn inside I2P" msgstr "Viewmtn à l'intérieur de I2P" -#: i2p2www/pages/site/docs/index.html:233 +#: i2p2www/pages/site/docs/index.html:238 msgid "I2P Source exported to GitHub" msgstr "Source de I2P exporté vers GitHub" -#: i2p2www/pages/site/docs/index.html:235 +#: i2p2www/pages/site/docs/index.html:240 msgid "I2P Source Git Repo inside I2P" msgstr "Source de I2P dans le Git Repo à l'intérieur de I2P" -#: i2p2www/pages/site/docs/index.html:237 +#: i2p2www/pages/site/docs/index.html:242 msgid "Source translation at Transifex" msgstr "Traduction source chez Transifex" -#: i2p2www/pages/site/docs/index.html:239 +#: i2p2www/pages/site/docs/index.html:244 msgid "Roadmap wiki" msgstr "Wiki de feuille de route" -#: i2p2www/pages/site/docs/index.html:241 +#: i2p2www/pages/site/docs/index.html:246 msgid "Old roadmap" msgstr "Vieille feuille de route" -#: i2p2www/pages/site/docs/index.html:241 -#: i2p2www/pages/site/docs/index.html:243 +#: i2p2www/pages/site/docs/index.html:246 +#: i2p2www/pages/site/docs/index.html:248 msgid "not current" msgstr "pas actuel" -#: i2p2www/pages/site/docs/index.html:243 +#: i2p2www/pages/site/docs/index.html:248 msgid "To Do List" msgstr "Liste de choses à faire" @@ -933,7 +947,7 @@ msgstr "" "Voir ci-dessous pour des détails." #: i2p2www/pages/site/docs/naming.html:183 -#: i2p2www/pages/site/docs/spec/configuration.html:170 +#: i2p2www/pages/site/docs/spec/configuration.html:184 msgid "Addressbook" msgstr "Carnet d'adresses" @@ -1431,7 +1445,7 @@ msgstr "" "le nom ne résout pas à une destination." #: i2p2www/pages/site/docs/plugins.html:2 -#: i2p2www/pages/site/docs/spec/configuration.html:138 +#: i2p2www/pages/site/docs/spec/configuration.html:152 msgid "Plugins" msgstr "Plugins" @@ -3193,15 +3207,20 @@ msgstr "" "href=\"http://%(postman)s/?page_id=16\">%(postman)s" #: i2p2www/pages/site/docs/api/i2ptunnel.html:54 +#, fuzzy +msgid "Configuration" +msgstr "Format de fichier de configuration" + +#: i2p2www/pages/site/docs/api/i2ptunnel.html:58 msgid "Client Modes" msgstr "Modes client" -#: i2p2www/pages/site/docs/api/i2ptunnel.html:55 -#: i2p2www/pages/site/docs/api/i2ptunnel.html:137 +#: i2p2www/pages/site/docs/api/i2ptunnel.html:59 +#: i2p2www/pages/site/docs/api/i2ptunnel.html:141 msgid "Standard" msgstr "Standard" -#: i2p2www/pages/site/docs/api/i2ptunnel.html:56 +#: 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" @@ -3213,7 +3232,7 @@ msgstr "" "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:62 +#: i2p2www/pages/site/docs/api/i2ptunnel.html:66 msgid "" "A HTTP-client tunnel. The tunnel connects to the destination specified by" " the URL\n" @@ -3225,7 +3244,7 @@ msgstr "" "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:67 +#: 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 " @@ -3235,7 +3254,7 @@ msgstr "" "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:75 +#: i2p2www/pages/site/docs/api/i2ptunnel.html:79 msgid "" "HTTP client/server tunnels are via I2Ptunnel force-enabling compression " "via the following http headers:" @@ -3243,7 +3262,7 @@ 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:82 +#: 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:" @@ -3251,15 +3270,15 @@ msgstr "" "Selon si le tunnel utilise un outproxy ou pas il ajoutera le User-Agent " "suivant :" -#: i2p2www/pages/site/docs/api/i2ptunnel.html:86 +#: i2p2www/pages/site/docs/api/i2ptunnel.html:90 msgid "Outproxy:" msgstr "" -#: i2p2www/pages/site/docs/api/i2ptunnel.html:87 +#: i2p2www/pages/site/docs/api/i2ptunnel.html:91 msgid "Internal I2P use:" msgstr "" -#: i2p2www/pages/site/docs/api/i2ptunnel.html:92 +#: i2p2www/pages/site/docs/api/i2ptunnel.html:96 msgid "" "Creates a connection to a random IRC server specified by the comma " "seprated (\", \") \n" @@ -3267,15 +3286,15 @@ msgid "" "allowed due to anonymity concerns." msgstr "" -#: i2p2www/pages/site/docs/api/i2ptunnel.html:96 +#: i2p2www/pages/site/docs/api/i2ptunnel.html:100 msgid "Whitelist:" msgstr "Liste blanche:" -#: i2p2www/pages/site/docs/api/i2ptunnel.html:111 +#: i2p2www/pages/site/docs/api/i2ptunnel.html:115 msgid "Enables using the I2P router as a SOCKS proxy." msgstr "Permet l'utilisation du routeur I2P en tant que proxy SOCKS." -#: i2p2www/pages/site/docs/api/i2ptunnel.html:116 +#: 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" @@ -3285,7 +3304,7 @@ msgstr "" "commande whitelist spécifiée par \n" "mode client IRC." -#: i2p2www/pages/site/docs/api/i2ptunnel.html:122 +#: 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." @@ -3294,7 +3313,7 @@ msgstr "" "pour construire un tunnel TCP qui d'habitude est utilisé pour SSL et " "HTTPS." -#: i2p2www/pages/site/docs/api/i2ptunnel.html:128 +#: 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" @@ -3304,15 +3323,15 @@ msgstr "" "client streamr va\n" "souscrire à un tunnel serveur streamr." -#: i2p2www/pages/site/docs/api/i2ptunnel.html:136 +#: i2p2www/pages/site/docs/api/i2ptunnel.html:140 msgid "Server Modes" msgstr "Modes serveur" -#: i2p2www/pages/site/docs/api/i2ptunnel.html:138 +#: i2p2www/pages/site/docs/api/i2ptunnel.html:142 msgid "Creates a destination to a local ip:port with an open TCP port." msgstr "" -#: i2p2www/pages/site/docs/api/i2ptunnel.html:143 +#: 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" @@ -3320,7 +3339,7 @@ msgid "" " such a request." msgstr "" -#: i2p2www/pages/site/docs/api/i2ptunnel.html:149 +#: 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" @@ -3329,14 +3348,14 @@ msgid "" "requests, or loopback-testing an eepsite as a diagnostic tool." msgstr "" -#: i2p2www/pages/site/docs/api/i2ptunnel.html:156 +#: i2p2www/pages/site/docs/api/i2ptunnel.html:160 msgid "" "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:162 +#: 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." @@ -4162,8 +4181,8 @@ msgstr "" #: i2p2www/pages/site/docs/how/tunnel-routing.html:255 #: i2p2www/pages/site/docs/protocol/i2cp.html:687 #: i2p2www/pages/site/docs/protocol/i2np.html:226 -#: i2p2www/pages/site/docs/spec/updates.html:438 -#: i2p2www/pages/site/docs/transport/ntcp.html:535 +#: i2p2www/pages/site/docs/spec/updates.html:488 +#: i2p2www/pages/site/docs/transport/ntcp.html:544 #: i2p2www/pages/site/docs/transport/ssu.html:554 #: i2p2www/pages/site/docs/tunnels/implementation.html:506 msgid "Future Work" @@ -4718,6 +4737,14 @@ 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)." +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" "If done wrong, it could cause real harm to our network.\n" @@ -4726,11 +4753,11 @@ msgid "" "This page discusses some general guidelines." msgstr "" -#: i2p2www/pages/site/docs/applications/embedding.html:18 +#: i2p2www/pages/site/docs/applications/embedding.html:23 msgid "Talk to us" msgstr "" -#: i2p2www/pages/site/docs/applications/embedding.html:19 +#: 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" @@ -4738,11 +4765,11 @@ msgid "" "everyone." msgstr "" -#: i2p2www/pages/site/docs/applications/embedding.html:25 +#: i2p2www/pages/site/docs/applications/embedding.html:30 msgid "Choose your router wisely" msgstr "" -#: i2p2www/pages/site/docs/applications/embedding.html:26 +#: 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" @@ -4752,19 +4779,19 @@ msgid "" "Some of the following only applies to the Java router." msgstr "" -#: i2p2www/pages/site/docs/applications/embedding.html:34 +#: i2p2www/pages/site/docs/applications/embedding.html:39 msgid "Licensing" msgstr "" -#: i2p2www/pages/site/docs/applications/embedding.html:35 +#: i2p2www/pages/site/docs/applications/embedding.html:40 msgid "Ensure you meet the license requirements of the software you are bundling." msgstr "" -#: i2p2www/pages/site/docs/applications/embedding.html:40 +#: i2p2www/pages/site/docs/applications/embedding.html:45 msgid "Verify default configuration" msgstr "" -#: i2p2www/pages/site/docs/applications/embedding.html:41 +#: i2p2www/pages/site/docs/applications/embedding.html:46 msgid "" "A correct default configuration is crucial. Most users will not change " "the defaults.\n" @@ -4773,7 +4800,7 @@ msgid "" "Override the router defaults if necessary." msgstr "" -#: i2p2www/pages/site/docs/applications/embedding.html:46 +#: i2p2www/pages/site/docs/applications/embedding.html:51 msgid "" "Some important defaults to review: Max bandwidth, tunnel quantity and " "length, max participating tunnels.\n" @@ -4781,7 +4808,7 @@ msgid "" "your app." msgstr "" -#: i2p2www/pages/site/docs/applications/embedding.html:50 +#: i2p2www/pages/site/docs/applications/embedding.html:55 msgid "" "Configure enough bandwidth and tunnels to allow your users to contribute " "to the network.\n" @@ -4791,11 +4818,11 @@ msgid "" "example." msgstr "" -#: i2p2www/pages/site/docs/applications/embedding.html:57 +#: i2p2www/pages/site/docs/applications/embedding.html:62 msgid "Participating Traffic Considerations" msgstr "" -#: i2p2www/pages/site/docs/applications/embedding.html:58 +#: 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, " @@ -4807,14 +4834,14 @@ msgid "" "tunnels." msgstr "" -#: i2p2www/pages/site/docs/applications/embedding.html:65 +#: 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" "which is helped tremendously by others building tunnels through you." msgstr "" -#: i2p2www/pages/site/docs/applications/embedding.html:69 +#: i2p2www/pages/site/docs/applications/embedding.html:74 msgid "" "Secondly, over 90% of the routers in the current network allow " "participating traffic.\n" @@ -4826,13 +4853,13 @@ msgid "" " people to enable relaying." msgstr "" -#: i2p2www/pages/site/docs/applications/embedding.html:76 +#: i2p2www/pages/site/docs/applications/embedding.html:81 msgid "" "Thirdly, participating traffic is cover traffic that helps your users' " "anonymity." msgstr "" -#: i2p2www/pages/site/docs/applications/embedding.html:79 +#: i2p2www/pages/site/docs/applications/embedding.html:84 msgid "" "We strongly discourage you from disabling participating traffic by " "default.\n" @@ -4840,11 +4867,11 @@ msgid "" "the network." msgstr "" -#: i2p2www/pages/site/docs/applications/embedding.html:85 +#: i2p2www/pages/site/docs/applications/embedding.html:90 msgid "Persistence" msgstr "" -#: i2p2www/pages/site/docs/applications/embedding.html:86 +#: 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" @@ -4854,11 +4881,11 @@ msgid "" "performance." msgstr "" -#: i2p2www/pages/site/docs/applications/embedding.html:94 +#: i2p2www/pages/site/docs/applications/embedding.html:99 msgid "Configurability" msgstr "" -#: i2p2www/pages/site/docs/applications/embedding.html:95 +#: i2p2www/pages/site/docs/applications/embedding.html:100 msgid "" "Give your users a way to change the configuration of the important " "settings.\n" @@ -4868,11 +4895,11 @@ msgid "" "IP/port may be helpful." msgstr "" -#: i2p2www/pages/site/docs/applications/embedding.html:103 +#: i2p2www/pages/site/docs/applications/embedding.html:108 msgid "Floodfill Considerations" msgstr "" -#: i2p2www/pages/site/docs/applications/embedding.html:104 +#: 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" @@ -4883,11 +4910,11 @@ msgid "" "It also depends on the typical uptime for your application." msgstr "" -#: i2p2www/pages/site/docs/applications/embedding.html:114 +#: i2p2www/pages/site/docs/applications/embedding.html:119 msgid "Reseeding" msgstr "" -#: i2p2www/pages/site/docs/applications/embedding.html:115 +#: 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 " @@ -4895,11 +4922,11 @@ msgid "" "Be aware of possible blocking by hostile governments." msgstr "" -#: i2p2www/pages/site/docs/applications/embedding.html:124 +#: i2p2www/pages/site/docs/applications/embedding.html:129 msgid "Reduce Network Resource Usage" msgstr "" -#: i2p2www/pages/site/docs/applications/embedding.html:125 +#: 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" @@ -4909,11 +4936,11 @@ msgid "" "tunnel, even in the presence of some background DHT activity." msgstr "" -#: i2p2www/pages/site/docs/applications/embedding.html:133 +#: i2p2www/pages/site/docs/applications/embedding.html:138 msgid "Updatability" msgstr "" -#: i2p2www/pages/site/docs/applications/embedding.html:134 +#: 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" @@ -4928,11 +4955,11 @@ msgid "" "which you presumably are not bundling." msgstr "" -#: i2p2www/pages/site/docs/applications/embedding.html:145 +#: i2p2www/pages/site/docs/applications/embedding.html:150 msgid "Rollout" msgstr "" -#: i2p2www/pages/site/docs/applications/embedding.html:146 +#: 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 " @@ -4948,11 +4975,11 @@ msgid "" "checklist is." msgstr "" -#: i2p2www/pages/site/docs/applications/embedding.html:158 +#: i2p2www/pages/site/docs/applications/embedding.html:163 msgid "Design for and Encourage Long Uptimes" msgstr "" -#: i2p2www/pages/site/docs/applications/embedding.html:159 +#: 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 " @@ -4961,53 +4988,53 @@ msgid "" "solution." msgstr "" -#: i2p2www/pages/site/docs/applications/embedding.html:167 +#: i2p2www/pages/site/docs/applications/embedding.html:172 msgid "Show Status" msgstr "" -#: i2p2www/pages/site/docs/applications/embedding.html:168 +#: i2p2www/pages/site/docs/applications/embedding.html:173 msgid "" "Provide some indication to the user that the application tunnels are " "ready. Encourage patience." msgstr "" -#: i2p2www/pages/site/docs/applications/embedding.html:173 +#: i2p2www/pages/site/docs/applications/embedding.html:178 msgid "Graceful Shutdown" msgstr "" -#: i2p2www/pages/site/docs/applications/embedding.html:174 +#: 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 "" -#: i2p2www/pages/site/docs/applications/embedding.html:180 +#: i2p2www/pages/site/docs/applications/embedding.html:185 msgid "Education and Donation" msgstr "" -#: i2p2www/pages/site/docs/applications/embedding.html:181 +#: 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 "" -#: i2p2www/pages/site/docs/applications/embedding.html:187 +#: i2p2www/pages/site/docs/applications/embedding.html:192 msgid "External Router Option" msgstr "" -#: i2p2www/pages/site/docs/applications/embedding.html:188 +#: 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 "" -#: i2p2www/pages/site/docs/applications/embedding.html:195 +#: i2p2www/pages/site/docs/applications/embedding.html:200 msgid "Use of other Common Services" msgstr "" -#: i2p2www/pages/site/docs/applications/embedding.html:196 +#: 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" @@ -5015,11 +5042,11 @@ msgid "" "and talk to the people who are running them to make sure it's ok." msgstr "" -#: i2p2www/pages/site/docs/applications/embedding.html:204 +#: i2p2www/pages/site/docs/applications/embedding.html:209 msgid "Time / NTP Issues" msgstr "" -#: i2p2www/pages/site/docs/applications/embedding.html:205 +#: 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. " @@ -5028,11 +5055,11 @@ msgid "" "clock is correct." msgstr "" -#: i2p2www/pages/site/docs/applications/embedding.html:213 +#: i2p2www/pages/site/docs/applications/embedding.html:218 msgid "Choose What and How you Bundle" msgstr "" -#: i2p2www/pages/site/docs/applications/embedding.html:214 +#: 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" @@ -5050,11 +5077,19 @@ msgid "" "and i2psnark, for example." msgstr "" -#: i2p2www/pages/site/docs/applications/embedding.html:228 +#: i2p2www/pages/site/docs/applications/embedding.html:233 +msgid "You may also wish to bundle a hosts.txt file." +msgstr "" + +#: i2p2www/pages/site/docs/applications/embedding.html:236 +msgid "Be sure to specify a Java 6 bootclasspath if compiling with Java 8." +msgstr "" + +#: i2p2www/pages/site/docs/applications/embedding.html:244 msgid "Datagram (DHT) considerations" msgstr "" -#: i2p2www/pages/site/docs/applications/embedding.html:229 +#: 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 " @@ -5070,32 +5105,32 @@ msgid "" "have several." msgstr "" -#: i2p2www/pages/site/docs/applications/embedding.html:242 +#: i2p2www/pages/site/docs/applications/embedding.html:258 msgid "Comarketing" msgstr "" -#: i2p2www/pages/site/docs/applications/embedding.html:243 +#: 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 "" -#: i2p2www/pages/site/docs/applications/embedding.html:249 +#: i2p2www/pages/site/docs/applications/embedding.html:265 msgid "Malware" msgstr "" -#: i2p2www/pages/site/docs/applications/embedding.html:250 +#: i2p2www/pages/site/docs/applications/embedding.html:266 msgid "" "Please don't use I2P for evil.\n" "It could cause great harm both to our network and our reputation." msgstr "" -#: i2p2www/pages/site/docs/applications/embedding.html:256 +#: i2p2www/pages/site/docs/applications/embedding.html:272 msgid "Join Us" msgstr "" -#: i2p2www/pages/site/docs/applications/embedding.html:257 +#: 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" @@ -5103,11 +5138,11 @@ msgid "" "We can help get you users, testers, translators, or even coders." msgstr "" -#: i2p2www/pages/site/docs/applications/embedding.html:265 +#: i2p2www/pages/site/docs/applications/embedding.html:281 msgid "Application Examples" msgstr "" -#: i2p2www/pages/site/docs/applications/embedding.html:266 +#: 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" @@ -5117,17 +5152,17 @@ msgid "" " and Monero." msgstr "" -#: i2p2www/pages/site/docs/applications/embedding.html:274 +#: i2p2www/pages/site/docs/applications/embedding.html:290 msgid "Code Example" msgstr "" -#: i2p2www/pages/site/docs/applications/embedding.html:275 +#: i2p2www/pages/site/docs/applications/embedding.html:291 msgid "" "None of the above actually tells you how to write your code to\n" "bundle the Java router, so following is a brief example." msgstr "" -#: i2p2www/pages/site/docs/applications/embedding.html:290 +#: 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" @@ -8423,7 +8458,6 @@ msgid "The Network Database" msgstr "" #: i2p2www/pages/site/docs/how/network-database.html:3 -#: i2p2www/pages/site/docs/transport/ntcp.html:3 msgid "October 2014" msgstr "" @@ -15873,10 +15907,6 @@ msgstr "" msgid "Configuration File Specification" msgstr "Specification du fichier de configuration" -#: i2p2www/pages/site/docs/spec/configuration.html:3 -msgid "January 2014" -msgstr "Janvier 2014" - #: i2p2www/pages/site/docs/spec/configuration.html:7 msgid "" "This page provides a general specification of I2P configuration files,\n" @@ -15994,65 +16024,66 @@ msgid "Configured via /configlogging in the router console." msgstr "" #: i2p2www/pages/site/docs/spec/configuration.html:112 -#: i2p2www/pages/site/docs/spec/configuration.html:142 -#: i2p2www/pages/site/docs/spec/configuration.html:154 +#: i2p2www/pages/site/docs/spec/configuration.html:156 +#: i2p2www/pages/site/docs/spec/configuration.html:168 +#: i2p2www/pages/site/docs/spec/configuration.html:198 msgid "Properties are as follows:" msgstr "Les propriétés sont comme suit :" -#: i2p2www/pages/site/docs/spec/configuration.html:133 +#: i2p2www/pages/site/docs/spec/configuration.html:147 msgid "Individual Plugin" msgstr "Plug-in individuel" -#: i2p2www/pages/site/docs/spec/configuration.html:134 +#: i2p2www/pages/site/docs/spec/configuration.html:148 #, python-format msgid "See the plugin specification." msgstr "Voir la spécification de plug-in." -#: i2p2www/pages/site/docs/spec/configuration.html:139 +#: i2p2www/pages/site/docs/spec/configuration.html:153 msgid "Enable/disable for each installed plugin." msgstr "" -#: i2p2www/pages/site/docs/spec/configuration.html:150 +#: i2p2www/pages/site/docs/spec/configuration.html:164 msgid "Webapps" msgstr "Applications web" -#: i2p2www/pages/site/docs/spec/configuration.html:151 +#: i2p2www/pages/site/docs/spec/configuration.html:165 msgid "Enable/disable for each installed webapp." msgstr "Active/désactive pour pour chaque application web installée." -#: i2p2www/pages/site/docs/spec/configuration.html:163 +#: i2p2www/pages/site/docs/spec/configuration.html:177 msgid "Router" msgstr "Routeur" -#: i2p2www/pages/site/docs/spec/configuration.html:164 +#: i2p2www/pages/site/docs/spec/configuration.html:178 msgid "Configured via /configadvanced in the router console." msgstr "" -#: i2p2www/pages/site/docs/spec/configuration.html:168 +#: i2p2www/pages/site/docs/spec/configuration.html:182 msgid "Applications" msgstr "Applications" -#: i2p2www/pages/site/docs/spec/configuration.html:171 +#: i2p2www/pages/site/docs/spec/configuration.html:185 msgid "See documentation in SusiDNS." msgstr "" -#: i2p2www/pages/site/docs/spec/configuration.html:176 +#: i2p2www/pages/site/docs/spec/configuration.html:190 msgid "Configured via the application gui." msgstr "" -#: i2p2www/pages/site/docs/spec/configuration.html:181 +#: i2p2www/pages/site/docs/spec/configuration.html:195 msgid "Configured via the /i2ptunnel application in the router console." msgstr "" -#: i2p2www/pages/site/docs/spec/configuration.html:185 +#: i2p2www/pages/site/docs/spec/configuration.html:364 msgid "Router Console" msgstr "Console du routeur" -#: i2p2www/pages/site/docs/spec/configuration.html:186 +#: i2p2www/pages/site/docs/spec/configuration.html:365 msgid "The router console uses the router.config file." msgstr "La console du router utilise le fichier router.config ." -#: i2p2www/pages/site/docs/spec/configuration.html:191 +#: i2p2www/pages/site/docs/spec/configuration.html:370 msgid "See post on zzz.i2p." msgstr "" @@ -16449,6 +16480,7 @@ msgstr "" #: i2p2www/pages/site/docs/spec/updates.html:204 #: i2p2www/pages/site/docs/spec/updates.html:313 +#: i2p2www/pages/site/docs/spec/updates.html:365 msgid "Goals:" msgstr "" @@ -16471,7 +16503,8 @@ msgid "One-pass signature verification and file extraction" msgstr "" #: i2p2www/pages/site/docs/spec/updates.html:222 -#: i2p2www/pages/site/docs/spec/updates.html:336 +#: i2p2www/pages/site/docs/spec/updates.html:328 +#: i2p2www/pages/site/docs/spec/updates.html:388 msgid "Specification:" msgstr "" @@ -16480,40 +16513,80 @@ msgid "All unused fields must be set to 0 for compatibility with future versions msgstr "" #: i2p2www/pages/site/docs/spec/updates.html:308 -msgid "SU3 News File Specification" -msgstr "" +#, fuzzy +msgid "SU3 Reseed File Specification" +msgstr "Spécification du fichier GeoIP" #: i2p2www/pages/site/docs/spec/updates.html:309 -msgid "As of 0.9.17, the news is delivered in an \"su3\" file format." +msgid "As of 0.9.14, reseed data is delivered in an \"su3\" file format." msgstr "" #: i2p2www/pages/site/docs/spec/updates.html:316 -msgid "Signed news with strong signatures and trusted certificates" +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 "" -#: i2p2www/pages/site/docs/spec/updates.html:319 +#: 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 "" -#: i2p2www/pages/site/docs/spec/updates.html:322 -msgid "Standard XML format for use with standard parsers" -msgstr "" - -#: i2p2www/pages/site/docs/spec/updates.html:325 -msgid "Standard Atom format for use with standard feed readers and generators" -msgstr "" - -#: i2p2www/pages/site/docs/spec/updates.html:328 -msgid "Sanitization and verification of HTML before displaying on console" +#: i2p2www/pages/site/docs/spec/updates.html:323 +msgid "" +"Single compressed file to speed up reseeding, which was slow to fetch 200" +" files" msgstr "" #: i2p2www/pages/site/docs/spec/updates.html:331 +msgid "The file must be named \"i2pseeds.su3\"." +msgstr "" + +#: i2p2www/pages/site/docs/spec/updates.html:334 +msgid "" +"The file must be in the same directory as the router infos on the web " +"server." +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" +"and then fetch the individual router info files found in the links." +msgstr "" + +#: i2p2www/pages/site/docs/spec/updates.html:360 +msgid "SU3 News File Specification" +msgstr "" + +#: i2p2www/pages/site/docs/spec/updates.html:361 +msgid "As of 0.9.17, the news is delivered in an \"su3\" file format." +msgstr "" + +#: i2p2www/pages/site/docs/spec/updates.html:368 +msgid "Signed news with strong signatures and trusted certificates" +msgstr "" + +#: i2p2www/pages/site/docs/spec/updates.html:374 +msgid "Standard XML format for use with standard parsers" +msgstr "" + +#: i2p2www/pages/site/docs/spec/updates.html:377 +msgid "Standard Atom format for use with standard feed readers and generators" +msgstr "" + +#: i2p2www/pages/site/docs/spec/updates.html:380 +msgid "Sanitization and verification of HTML before displaying on console" +msgstr "" + +#: i2p2www/pages/site/docs/spec/updates.html:383 msgid "" "Suitable for easy implementation on Android and other platforms without " "an HTML console" msgstr "" -#: i2p2www/pages/site/docs/spec/updates.html:440 +#: 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" @@ -17106,7 +17179,7 @@ msgstr "" #: i2p2www/pages/site/docs/transport/ntcp.html:207 #: i2p2www/pages/site/docs/transport/ntcp.html:250 #: i2p2www/pages/site/docs/transport/ntcp.html:332 -#: i2p2www/pages/site/docs/transport/ntcp.html:428 +#: i2p2www/pages/site/docs/transport/ntcp.html:437 msgid "Size:" msgstr "Taille:" @@ -17124,7 +17197,7 @@ msgstr "" #: i2p2www/pages/site/docs/transport/ntcp.html:236 #: i2p2www/pages/site/docs/transport/ntcp.html:319 -#: i2p2www/pages/site/docs/transport/ntcp.html:397 +#: i2p2www/pages/site/docs/transport/ntcp.html:398 msgid "Notes:" msgstr "Notes:" @@ -17144,7 +17217,7 @@ msgstr "" #: i2p2www/pages/site/docs/transport/ntcp.html:252 #: i2p2www/pages/site/docs/transport/ntcp.html:334 -#: i2p2www/pages/site/docs/transport/ntcp.html:430 +#: i2p2www/pages/site/docs/transport/ntcp.html:439 msgid "Unencrypted Contents:" msgstr "" @@ -17168,7 +17241,7 @@ msgstr "" #: i2p2www/pages/site/docs/transport/ntcp.html:285 #: i2p2www/pages/site/docs/transport/ntcp.html:376 -#: i2p2www/pages/site/docs/transport/ntcp.html:457 +#: i2p2www/pages/site/docs/transport/ntcp.html:466 msgid "Encrypted Contents:" msgstr "" @@ -17205,7 +17278,7 @@ msgid "Alice's 387+ byte `RouterIdentity`" msgstr "" #: i2p2www/pages/site/docs/transport/ntcp.html:366 -#: i2p2www/pages/site/docs/transport/ntcp.html:452 +#: i2p2www/pages/site/docs/transport/ntcp.html:461 msgid "0-15 bytes random data" msgstr "" @@ -17226,31 +17299,31 @@ msgid "" "of message #1) as the IV" msgstr "" -#: i2p2www/pages/site/docs/transport/ntcp.html:399 +#: i2p2www/pages/site/docs/transport/ntcp.html:400 msgid "Bob verifies the signature, and on failure, drops the connection." msgstr "" -#: i2p2www/pages/site/docs/transport/ntcp.html:402 +#: i2p2www/pages/site/docs/transport/ntcp.html:403 msgid "" "Bob may drop the connection if the clock skew with Alice is too high as " "calculated using tsA." msgstr "" -#: i2p2www/pages/site/docs/transport/ntcp.html:405 +#: 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 "" -#: i2p2www/pages/site/docs/transport/ntcp.html:421 +#: i2p2www/pages/site/docs/transport/ntcp.html:430 msgid "Message 4 (Session Confirm B)" msgstr "" -#: i2p2www/pages/site/docs/transport/ntcp.html:422 +#: i2p2www/pages/site/docs/transport/ntcp.html:431 msgid "This is a signature of the critical data. Bob sends Alice:" msgstr "" -#: i2p2www/pages/site/docs/transport/ntcp.html:446 +#: i2p2www/pages/site/docs/transport/ntcp.html:455 msgid "" "the `Signature` of the following concatenated data:\n" " X, Y, Alice's `RouterIdentity`, tsA, tsB.\n" @@ -17258,7 +17331,7 @@ msgid "" "the `SigningPublicKey` in his `RouterIdentity`" msgstr "" -#: i2p2www/pages/site/docs/transport/ntcp.html:470 +#: i2p2www/pages/site/docs/transport/ntcp.html:479 #, python-format msgid "" "Data AES encrypted using the DH " @@ -17269,21 +17342,21 @@ msgid "" "signature types" msgstr "" -#: i2p2www/pages/site/docs/transport/ntcp.html:479 +#: i2p2www/pages/site/docs/transport/ntcp.html:488 msgid "Alice verifies the signature, and on failure, drops the connection." msgstr "" -#: i2p2www/pages/site/docs/transport/ntcp.html:482 +#: 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 "" -#: i2p2www/pages/site/docs/transport/ntcp.html:497 +#: i2p2www/pages/site/docs/transport/ntcp.html:506 msgid "After Establishment" msgstr "" -#: i2p2www/pages/site/docs/transport/ntcp.html:498 +#: i2p2www/pages/site/docs/transport/ntcp.html:507 msgid "" "The connection is established, and standard or time sync messages may be " "exchanged.\n" @@ -17295,11 +17368,11 @@ msgid "" " the next IV." msgstr "" -#: i2p2www/pages/site/docs/transport/ntcp.html:507 +#: i2p2www/pages/site/docs/transport/ntcp.html:516 msgid "Check Connection Message" msgstr "" -#: i2p2www/pages/site/docs/transport/ntcp.html:508 +#: i2p2www/pages/site/docs/transport/ntcp.html:517 msgid "" "Alternately, when Bob receives a connection, it could be a\n" "check connection (perhaps prompted by Bob asking for someone\n" @@ -17309,58 +17382,58 @@ msgid "" "A check info connection will receive 256 bytes containing:" msgstr "" -#: i2p2www/pages/site/docs/transport/ntcp.html:517 +#: i2p2www/pages/site/docs/transport/ntcp.html:526 msgid "32 bytes of uninterpreted, ignored data" msgstr "" -#: i2p2www/pages/site/docs/transport/ntcp.html:518 +#: i2p2www/pages/site/docs/transport/ntcp.html:527 msgid "1 byte size" msgstr "" -#: i2p2www/pages/site/docs/transport/ntcp.html:519 +#: 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 "" -#: i2p2www/pages/site/docs/transport/ntcp.html:520 +#: i2p2www/pages/site/docs/transport/ntcp.html:529 msgid "2 byte port number that the local router was reached on" msgstr "" -#: i2p2www/pages/site/docs/transport/ntcp.html:521 +#: i2p2www/pages/site/docs/transport/ntcp.html:530 msgid "" "4 byte i2p network time as known by the remote side (seconds since the " "epoch)" msgstr "" -#: i2p2www/pages/site/docs/transport/ntcp.html:522 +#: i2p2www/pages/site/docs/transport/ntcp.html:531 msgid "uninterpreted padding data, up to byte 223" msgstr "" -#: i2p2www/pages/site/docs/transport/ntcp.html:523 +#: 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 "" -#: i2p2www/pages/site/docs/transport/ntcp.html:526 +#: i2p2www/pages/site/docs/transport/ntcp.html:535 msgid "Check connection is completely disabled as of release 0.9.12." msgstr "" -#: i2p2www/pages/site/docs/transport/ntcp.html:530 +#: i2p2www/pages/site/docs/transport/ntcp.html:539 msgid "Discussion" msgstr "" -#: i2p2www/pages/site/docs/transport/ntcp.html:531 +#: i2p2www/pages/site/docs/transport/ntcp.html:540 #, python-format msgid "Now on the NTCP Discussion Page." msgstr "" -#: i2p2www/pages/site/docs/transport/ntcp.html:537 +#: i2p2www/pages/site/docs/transport/ntcp.html:546 msgid "The maximum message size should be increased to approximately 32 KB." msgstr "" -#: i2p2www/pages/site/docs/transport/ntcp.html:541 +#: 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" @@ -17371,13 +17444,13 @@ msgid "" "to create a limited number of message sizes." msgstr "" -#: i2p2www/pages/site/docs/transport/ntcp.html:549 +#: 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 "" -#: i2p2www/pages/site/docs/transport/ntcp.html:553 +#: 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?" diff --git a/i2p2www/translations/fr/LC_MESSAGES/get-involved.po b/i2p2www/translations/fr/LC_MESSAGES/get-involved.po index f5c43d6b..469b1b43 100644 --- a/i2p2www/translations/fr/LC_MESSAGES/get-involved.po +++ b/i2p2www/translations/fr/LC_MESSAGES/get-involved.po @@ -12,7 +12,7 @@ msgid "" msgstr "" "Project-Id-Version: I2P\n" "Report-Msgid-Bugs-To: http://trac.i2p2.de\n" -"POT-Creation-Date: 2014-10-22 20:13+0000\n" +"POT-Creation-Date: 2014-11-27 12:12+0000\n" "PO-Revision-Date: 2014-10-29 13:58+0000\n" "Last-Translator: Towinet\n" "Language-Team: French " @@ -530,497 +530,56 @@ msgstr "" "Impliquez vous !" #: i2p2www/pages/site/get-involved/todo.html:15 -#: i2p2www/pages/site/get-involved/todo.html:53 +#: i2p2www/pages/site/get-involved/todo.html:38 msgid "Core functionality" msgstr "Fonctionnalité de base" #: i2p2www/pages/site/get-involved/todo.html:15 -#: i2p2www/pages/site/get-involved/todo.html:27 -#: i2p2www/pages/site/get-involved/todo.html:51 +#: i2p2www/pages/site/get-involved/todo.html:21 +#: i2p2www/pages/site/get-involved/todo.html:36 msgid "link" msgstr "lien" #: i2p2www/pages/site/get-involved/todo.html:17 -#: i2p2www/pages/site/get-involved/todo.html:56 -msgid "NAT/Firewall bridging via 1-hop restricted routes" -msgstr "Pontage NAT/Firewall via des routes restreintes à 1 étape" - -#: i2p2www/pages/site/get-involved/todo.html:20 -#: i2p2www/pages/site/get-involved/todo.html:129 -msgid "High degree transport layer with UDP, NBIO, or NIO" -msgstr "Couche transport de haute niveau avec UDP, NBIO, ou NIO" - -#: i2p2www/pages/site/get-involved/todo.html:23 -#: i2p2www/pages/site/get-involved/todo.html:217 +#: i2p2www/pages/site/get-involved/todo.html:41 msgid "NetworkDB and profile tuning and ejection policy for large nets" msgstr "NetworkDB et réglage de profil et politique d'éjection pour grands réseaux" -#: i2p2www/pages/site/get-involved/todo.html:27 -#: i2p2www/pages/site/get-involved/todo.html:241 +#: i2p2www/pages/site/get-involved/todo.html:21 +#: i2p2www/pages/site/get-involved/todo.html:65 msgid "Security / anonymity" msgstr "Sécurité / anonymat" -#: i2p2www/pages/site/get-involved/todo.html:29 -#: i2p2www/pages/site/get-involved/todo.html:244 -msgid "" -"Per-hop tunnel id & new permuted TunnelVerificationStructure " -"encryption" -msgstr "" -"Id de tunnel par-étape (per-hop) & nouveau chiffrement permuté pour " -"TunnelVerificationStructure" - -#: i2p2www/pages/site/get-involved/todo.html:32 -#: i2p2www/pages/site/get-involved/todo.html:294 -msgid "Strict ordering of participants within tunnels" -msgstr "Ordonnement strict des participants dans les tunnels" - -#: i2p2www/pages/site/get-involved/todo.html:35 -msgid "Randomly permuted tunnel lengths" -msgstr "Longueurs de tunnel permutées aléatoirement " - -#: i2p2www/pages/site/get-involved/todo.html:38 -#: i2p2www/pages/site/get-involved/todo.html:356 +#: 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" -#: i2p2www/pages/site/get-involved/todo.html:41 -#: i2p2www/pages/site/get-involved/todo.html:375 +#: 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 "Hashcash pour routerIdentity, destination, et requête de tunnel" -#: i2p2www/pages/site/get-involved/todo.html:44 -#: i2p2www/pages/site/get-involved/todo.html:404 +#: 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)" -#: i2p2www/pages/site/get-involved/todo.html:47 -#: i2p2www/pages/site/get-involved/todo.html:441 +#: i2p2www/pages/site/get-involved/todo.html:32 +#: i2p2www/pages/site/get-involved/todo.html:153 msgid "Stop & go mix w/ garlics & tunnels" msgstr "Stop & go mélangé avec tunnels oignon" -#: i2p2www/pages/site/get-involved/todo.html:51 -#: i2p2www/pages/site/get-involved/todo.html:455 +#: i2p2www/pages/site/get-involved/todo.html:36 +#: i2p2www/pages/site/get-involved/todo.html:167 msgid "Performance" msgstr "Performance" -#: i2p2www/pages/site/get-involved/todo.html:61 -msgid "Implemented in I2P 0.6.0.6" -msgstr "Implementé dans I2P 0.6.0.6" - -#: i2p2www/pages/site/get-involved/todo.html:62 -msgid "" -"The functionality of allowing routers to fully participate within the " -"network \n" -"while behind firewalls and NATs that they do not control requires some " -"basic \n" -"restricted route operation (since those peers will not be able to receive" -" \n" -"inbound connections). To do this successfully, you consider peers one of" -" \n" -"two ways:" -msgstr "" -"La fonctionnalité de permettre à des routeurs de participer entièrement " -"dans le réseau,\n" -"tandis qu'ils sont derrière des pare-feu et NATS qu'ils ne contrôlent " -"pas, exige certaines opérations\n" -"de la part de routes restreintes basiques (puisque ces pairs ne pourront " -"pas recevoir\n" -"des connexions arrivantes). Pour faire ceci avec succès, vous considérez " -"les pairs de l'une de\n" -"ces deux façons :" - -#: i2p2www/pages/site/get-involved/todo.html:72 -msgid "" -"Peers who have reachable interfaces - these peers do not need to \n" -"do anything special" -msgstr "" -"Les pairs qui ont des interfaces accessibles - ces pairs n'ont pas" -" besoin de\n" -"faire quoi que ce soit de spécial" - -#: i2p2www/pages/site/get-involved/todo.html:76 -msgid "" -"Peers who do not have reachable interfaces - these peers must " -"build \n" -"a tunnel pointing at them where the gateway is one of the peers they have" -" \n" -"established a connection with who has both a publicly reachable interface" -" \n" -"and who has agreed to serve as their 'introducer'." -msgstr "" -"Les pairs qui n'ont pas interfaces accessibles - ces pairs doivent" -" construire\n" -"un tunnel indiquant à ceux dont la passerelle est un des pairs, qu'ils " -"ont\n" -"établi une connexion dont laquelle possède une interface publiquement " -"accessible\n" -"et ayant à la fois consenti à leur servir d' 'introducteur'." - -#: i2p2www/pages/site/get-involved/todo.html:84 -msgid "" -"To do this, peers who have no IP address simply connect to a few peers, \n" -"build a tunnel through them, and publish a reference to those tunnels " -"within \n" -"their RouterInfo structure in the network database." -msgstr "" -"Pour faire ceci, les pairs qui n'ont aucune adresse IP se connectent " -"simplement à quelques pairs,\n" -"construisent un tunnel à travers eux, et publient une référence vers " -"tunnels dans\n" -"leur structure RouterInfo dans la base de données de réseau." - -#: i2p2www/pages/site/get-involved/todo.html:89 -msgid "" -"When someone wants to contact any particular router, they first must get" -" \n" -"its RouterInfo from the network database, which will tell them whether " -"they \n" -"can connect directly (e.g. the peer has a publicly reachable interface) \n" -"or whether they need to contact them indirectly. Direct connections occur" -" \n" -"as normal, while indirect connections are done through one of the " -"published \n" -"tunnels." -msgstr "" -"Quand quelqu''un veut contacter un routeur particulier, ils doivent " -"d''abord obtenir\n" -"son RouterInfo depuis la base de données de réseau, lequel leur dira " -"s''ils\n" -"peuvent s''y connecter directement (par exemple le pair a une interface " -"publiquement accessible) \n" -"ou s''ils doivent les contacter indirectement. Les connexions directes " -"arrivent\n" -"normalement, tandis que les connexions indirectes sont faites à travers " -"un des\n" -"tunnels publiés." - -#: i2p2www/pages/site/get-involved/todo.html:97 -msgid "" -"When a router just wants to get a message or two to a specific hidden " -"peer, \n" -"they can just use the indirect tunnel for sending the payload. However, \n" -"if the router wants to talk to the hidden peer often (for instance, as " -"part \n" -"of a tunnel), they will send a garlic routed message through the indirect" -" \n" -"tunnel to that hidden peer which unwraps to contain a message which " -"should \n" -"be sent to the originating router. That hidden peer then establishes an \n" -"outbound connection to the originating router and from then on, those two" -" \n" -"routers can talk to each other directly over that newly established " -"direct \n" -"connection." -msgstr "" -"Quand un routeur veut juste obtenir un message ou deux à un pair caché " -"spécifique,\n" -"ils peuvent juste utiliser le tunnel indirect pour envoyer la charge " -"utile. Cependant,\n" -"si le routeur veut parler au pair caché souvent (par exemple, lorsque " -"faisant partie\n" -"d'un tunnel), ils enverront le message en oignon acheminé à travers le " -"tunnel indirect\n" -"vers ce pair caché lequel déroule pour contenir un message qui devrait\n" -"être envoyé au routeur originaire. Ce pair caché établit alors une\n" -"connexion en partance vers le routeur étant originaire et à partir de là," -" ces deux\n" -"routeurs peuvent parler l'un à l'autre directement au moyen de cette " -"connexion directe\n" -"nouvellement établie." - -#: i2p2www/pages/site/get-involved/todo.html:108 -msgid "" -"Of course, that only works if the originating peer can receive " -"connections \n" -"(they aren't also hidden). However, if the originating peer is hidden, " -"they \n" -"can simply direct the garlic routed message to come back to the " -"originating \n" -"peer's inbound tunnel." -msgstr "" -"Bien sûr, cela ne marche seulement que si le pair peut recevoir des " -"connexions\n" -"(si elles ne sont pas cachées elles aussi). Cependant, si le pair étant " -"originaire est caché, elles\n" -"peuvent simplement diriger le message acheminé oignon de façon à revenir " -"au\n" -"tunnel arrivant du pair originaire." - -#: i2p2www/pages/site/get-involved/todo.html:114 -msgid "" -"This is not meant to provide a way for a peer's IP address to be " -"concealed, \n" -"merely as a way to let people behind firewalls and NATs fully operate " -"within \n" -"the network. Concealing the peer's IP address adds a little more work, as" -" \n" -"described below." -msgstr "" -"Ceci n'est pas pensé pour fournir un chemin pour une adresse IP d'un pair" -" à dissimuler,\n" -"mais simplement comme une façon de laisser les gens derrière des pare-feu" -" et NATs opérer\n" -"entièrement dans le réseau. Dissimuler l'adresse IP du pair ajoute un peu" -" plus de travail, comme\n" -"décrit ci-dessus." - -#: i2p2www/pages/site/get-involved/todo.html:120 -msgid "" -"With this technique, any router can participate as any part of a tunnel." -" \n" -"For efficiency purposes, a hidden peer would be a bad choice for an " -"inbound \n" -"gateway, and within any given tunnel, two neighboring peers wouldn't want" -" \n" -"to be hidden. But that is not technically necessary." -msgstr "" -"Avec cette technique, n'importe quel routeur peut participer comme " -"n'importe quelle partie d'un tunnel.\n" -"Pour des buts d'efficacité, un pair caché serait un mauvais choix pour " -"une passerelle arrivante,\n" -"et dans n'importe quel tunnel donné, deux pairs voisins ne voudraient pas" -"\n" -"être cachés. Mais ce n'est pas nécessaire techniquement." - -#: i2p2www/pages/site/get-involved/todo.html:132 -msgid "Both UDP and NIO have been Implemented in I2P" -msgstr "À la fois UDP et NIO ont étés mis en œuvre dans I2P" - -#: i2p2www/pages/site/get-involved/todo.html:133 -msgid "" -"Standard TCP communication in Java generally requires blocking socket \n" -"calls, and to keep a blocked socket from hanging the entire system, those" -" \n" -"blocking calls are done on their own threads. Our current TCP transport \n" -"is implemented in a naive fashion - for each peer we are talking to, we \n" -"have one thread reading and one thread writing. The reader thread simply" -" \n" -"loops a bunch of read() calls, building I2NP messages and adding them \n" -"to our internal inbound message queue, and the writer thread pulls " -"messages \n" -"off a per-connection outbound message queue and shoves the data through \n" -"write() calls." -msgstr "" -"La communication TCP standard dans Java exige généralement de bloquer des" -" appels\n" -"socket, et d''empêcher une socket bloquée d'accrocher le système entier, " -"ces\n" -"appels de blocages sont faits sur leurs propres threads. Notre couche " -"transport TCP actuelle\n" -"est mise en œuvre d'une façon naïve - pour chaque pair auquel nous " -"parlons, nous \n" -"avons une thread de lecture et une thread d'une écriture. La thread de " -"lecture boucle simplement\n" -"une liasse d''appels read(), ceci construisant des messages I2NP et les " -"ajoutant\n" -"à notre file d'attente interne de messages arrivants, et la thread " -"d''écriture tire des messages\n" -"d''un queue de message en partance par connexion, et pousse les données " -"via\n" -"des appels write()." - -#: i2p2www/pages/site/get-involved/todo.html:144 -msgid "" -"We do this fairly efficiently, from a CPU perspective - at any time, \n" -"almost all of these threads are sitting idle, blocked waiting for " -"something \n" -"to do. However, each thread consumes real resources (on older Linux " -"kernels, \n" -"for instance, each thread would often be implemented as a fork()'ed " -"process). \n" -"As the network grows, the number of peers each router will want to talk \n" -"with will increase (remember, I2P is fully connected, meaning that any \n" -"given peer should know how to get a message to any other peer, and " -"restricted \n" -"route support will probably not significantly reduce the number of " -"connections \n" -"necessary). This means that with a 100,000 router network, each router \n" -"will have up to 199,998 threads just to deal with the TCP connections!" -msgstr "" -"Nous faisons ceci assez efficacement, d'une perspective de CPU - à tout " -"moment,\n" -"presque tous ces fils sont assis en attente, inoccupés, bloqués attendant" -" quelque chose\n" -"à faire. Cependant, chaque fil consomme des ressources réelles (sur des " -"noyaux Linux plus vieux,\n" -"par exemple, chaque fil serait souvent mis en œuvre comme processus " -"fork() ).\n" -"Tandis que le réseau grandit, le nombre de pairs auquel chaque routeur " -"voudra parler \n" -"augmentera (souvenez-vous, I2P est entièrement connecté, cela signifiant " -"que chaque\n" -"pair devrait savoir obtenir un message de n'importe quel autre pair, et " -"les routes\n" -"restreintes ne vont probablement pas réduire significativement le nombre " -"de connexions\n" -"nécessaires). Cela signifie qu'avec un réseau de 100 000 routeurs, chaque" -" routeur\n" -"aura jusqu'à 199 998 fils juste pour traiter les connexions TCP !" - -#: i2p2www/pages/site/get-involved/todo.html:156 -msgid "" -"Obviously, that just won't work. We need to use a transport layer that \n" -"can scale. In Java, we have two main camps:" -msgstr "" -"Évidemment, cela ne marchera simplement pas. Nous devons utiliser une " -"couche de transport\n" -"qui puissent se mettre à l'échelle Dans Java, nous avons deux camps " -"principaux :" - -#: i2p2www/pages/site/get-involved/todo.html:161 -#, python-format -msgid "" -"Implemented in I2P 0.6 (\"SSU\") as documented elsewhere" -msgstr "" -"Implémenté dans I2P 0.6 (\"SSU\") comme documenté ailleurs" - -#: i2p2www/pages/site/get-involved/todo.html:164 -msgid "" -"Sending and receiving UDP datagrams is a connectionless operation - if \n" -"we are communicating with 100,000 peers, we simply stick the UDP packets" -" \n" -"in a queue and have a single thread pulling them off the queue and " -"shoving \n" -"them out the pipe (and to receive, have a single thread pulling in any \n" -"UDP packets received and adding them to an inbound queue)." -msgstr "" -"L''envoi et la réception de datagrammes UDP est une opération sans " -"connexion - si\n" -"nous communiquons avec 100000 pairs, nous collons simplement les paquets " -"UDP\n" -"dans une file d''attente et un seul fil les tirant hors de la file " -"d''attente et les poussant\n" -"vers la tuyau (et pour les recevoir, un seul fil tirant chaque\n" -"paquets UDP reçus et les ajoutant à une file d'attente arrivante)." - -#: i2p2www/pages/site/get-involved/todo.html:171 -msgid "" -"However, moving to UDP means losing the benefits of TCP's ordering, " -"congestion \n" -"control, MTU discovery, etc. Implementing that code will take significant" -" \n" -"work, however I2P doesn't need it to be as strong as TCP. Specifically, \n" -"a while ago I was taking some measurements in the simulator and on the \n" -"live net, and the vast majority of messages transferred would fit easily" -" \n" -"within a single unfragmented UDP packet, and the largest of the messages" -" \n" -"would fit within 20-30 packets. As mule pointed out, TCP adds a " -"significant \n" -"overhead when dealing with so many small packets, as the ACKs are within" -" \n" -"an order of magnitude in size. With UDP, we can optimize the transport \n" -"for both efficiency and resilience by taking into account I2P's " -"particular \n" -"needs." -msgstr "" -"Cependant, basculer vers UDP signifie perdre les avantages de l'ordre de " -"TCP, contrôle\n" -"de congestion, découverte MTU, etc. Mettre en œuvre ce code prendra du " -"travail\n" -"significatif, cependant I2P n'en a pas besoin pour être aussi fort que " -"TCP. Spécifiquement\n" -"il y a quelque temps je prenais quelques mesures dans le simulateur et " -"sur le\n" -"réseau en direct, et la grande majorité des messages transférés " -"contiendrait facilement\n" -"dans un simple paquet UDP non fragmenté, et la plus grande partie des " -"messages\n" -"contiendrait dans 20-30 paquets. Comme la mule l'a fait apparaître, TCP " -"ajoute une en-tête\n" -"significative quand il traite autant de petits paquets, car les ACKs sont" -" dans\n" -"un ordre de grandeur de taille. Tandis qu'avec UDP, nous pouvons " -"optimiser le transport\n" -"tant pour l'efficacité que la résistance en prenant en compte les besoins" -"\n" -"particuliers de I2P." - -#: i2p2www/pages/site/get-involved/todo.html:184 -msgid "It will be a lot of work though." -msgstr "Ce sera beaucoup de travail toutefois." - -#: i2p2www/pages/site/get-involved/todo.html:187 -msgid "NIO or NBIO" -msgstr "NIO ou NBIO" - -#: i2p2www/pages/site/get-involved/todo.html:188 -msgid "NIO Implemented in I2P 0.6.1.22 (\"NTCP\")" -msgstr "NIO implémenté dans I2P 0.6.1.22 (\"NTCP\")" - -#: i2p2www/pages/site/get-involved/todo.html:191 -msgid "" -"In Java 1.4, a set of \"New I/O\" packages was introduced, allowing Java" -" \n" -"developers to take advantage of the operating system's nonblocking IO \n" -"capabilities - allowing you to maintain a large number of concurrent IO \n" -"operations without requiring a separate thread for each. There is much \n" -"promise with this approach, as we can scalable handle a large number of \n" -"concurrent connections and we don't have to write a mini-TCP stack with \n" -"UDP. However, the NIO packages have not proven themselves to be battle-" -"ready, \n" -"as the Freenet developer's found. In addition, requiring NIO support " -"would \n" -"mean we can't run on any of the open source JVMs like Kaffe, \n" -"as GNU/Classpath has only " -"limited \n" -"support for NIO. (note: this may not be the case anymore, as there \n" -"has been some progress on Classpath's NIO, but it is an unknown " -"quantity)" -msgstr "" -"Dans Java 1.4, un ensemble de paquets \"Nouvelle E/S\" a été présenté, " -"permettant aux\n" -"développeurs Java de profiter du capacités de non blocage du système\n" -"d'exploitation - vous permettant d'entretenir un grand nombre " -"d'opérations ES\n" -"simultanées sans exiger un fil séparé pour chacune. Il y a beaucoup\n" -"de promesses avec cette approche, car nous pouvons maintenir de façon " -"échelonnée un\n" -"grand nombre connexions simultanées et nous ne devons pas écrire une pile" -" mini-TCP avec\n" -"UDP. Cependant, les paquets NIO ne se sont pas prouvés être prêts pour la" -" bataille,\n" -"comme le développeur de Freenet l'a découvert. De plus, exiger le support" -" de NIO voudrait\n" -"dire que nous ne pouvons pas fonctionner sur n'importe quel JVM open " -"source telles que Kaffe,\n" -"car GNU/Classpath a seulement " -"un support limité\n" -"pour NIO. (note: ceci pourrait ne plus être le cas, car il y a\n" -"eu quelques progrès sur les Classpath de NIO, mais c'est une quantité " -"inconnue)" - -#: i2p2www/pages/site/get-involved/todo.html:205 -#, python-format -msgid "" -"Another alternative along the same lines is the Non" -" \n" -"Blocking I/O package - essentially a cleanroom NIO implementation \n" -"(written before NIO was around). It works by using some native OS code \n" -"to do the nonblocking IO, passing off events through Java. It seems to \n" -"be working with Kaffe, though there doesn't seem to be much development \n" -"activity on it lately (likely due to 1.4's NIO deployment)." -msgstr "" -"Une autre alternative parmi les mêmes lignes est le paquet Non\n" -"Blocking I/O - essentiellement une mise en œuvre en salle blanche\n" -"(écrit avant que NIO soit sorti). Cela marche en utilisant du code OS " -"natif\n" -"pour faire les IO non bloquantes, faisant passer des événements via Java." -" Cela semble\n" -"fonctionner avec Kaffe, quoiqu''il ne semble pas y avoir beaucoup " -"d'activité\n" -"de développement sur cela récemment (probablement en raison du " -"déploiement de NIO 1.4)." - -#: i2p2www/pages/site/get-involved/todo.html:220 +#: i2p2www/pages/site/get-involved/todo.html:44 msgid "" "Within the current network database and profile management " "implementation, \n" @@ -1068,7 +627,7 @@ msgstr "" "ce code dès maintenant, puisque nous n'allons pas en avoir besoin pendant" " un certain temps." -#: i2p2www/pages/site/get-involved/todo.html:235 +#: 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" @@ -1079,259 +638,7 @@ msgstr "" "à l'esprit. Nous aurons du travail à faire, mais nous pouvons le remettre" " à plus tard." -#: i2p2www/pages/site/get-involved/todo.html:247 -#: i2p2www/pages/site/get-involved/todo.html:331 -#, python-format -msgid "" -"Addressed in I2P 0.5 as documented elsewhere" -msgstr "" -"Abordé dans I2P 0.5 comme documenté ailleurs" - -#: i2p2www/pages/site/get-involved/todo.html:250 -msgid "" -"Right now, if Alice builds a four hop inbound tunnel starting at Elvis, \n" -"going to Dave, then to Charlie, then Bob, and finally Alice " -"(A<--B<--C<--D<--E), \n" -"all five of them will know they are participating in tunnel \"123\", as \n" -"the messages are tagged as such. What we want to do is give each hop " -"their \n" -"own unique tunnel hop ID - Charlie will receive messages on tunnel 234 \n" -"and forward them to tunnel 876 on Bob. The intent is to prevent Bob or \n" -"Charlie from knowing that they are in Alice's tunnel, as if each hop in \n" -"the tunnel had the same tunnel ID, collusion attacks aren't much work." -msgstr "" -"Dès à présent, si Alice construit un tunnel de quatre stauts commençant " -"chez Elvis, allant chez Dave, allant chez Charlie, puis chez Bob et " -"finalement chez Alice (A<--B<--C<--D<--E), tous les cinq " -"sauront qu''ils participent au tunnel \"123\", car les messages sont " -"étiquetés comme tels. Ce que nous voulons faire est de donner à chaque " -"étape son propre ID (identifiant) d''étape unique de tunnel - Charlie " -"recevra des messages sur le tunnel 234  et les expédiera au tunnel 876 " -"chez Bob. L''intention est d'empêcher Bob ou \n" -"Charlie de savoir qu'ils sont dans le tunnel d''Alice, comme si chaque " -"étape dans le tunnel avait le même ID de tunnel, les attaques par " -"collusion ne demandent pas beaucoup de travail." - -#: i2p2www/pages/site/get-involved/todo.html:260 -msgid "" -"Adding a unique tunnel ID per hop isn't hard, but by itself, " -"insufficient. \n" -"If Dave and Bob are under the control of the same attacker, they wouldn't" -" \n" -"be able to tell they are in the same tunnel due to the tunnel ID, but \n" -"would be able to tell by the message bodies and verification structures \n" -"by simply comparing them. To prevent that, the tunnel must use layered \n" -"encryption along the path, both on the payload of the tunneled message \n" -"and on the verification structure (used to prevent simple tagging " -"attacks). \n" -"This requires some simple modifications to the TunnelMessage, as well \n" -"as the inclusion of per-hop secret keys delivered during tunnel creation" -" \n" -"and given to the tunnel's gateway. We must fix a maximum tunnel length \n" -"(e.g. 16 hops) and instruct the gateway to encrypt the message to each \n" -"of the 16 delivered secret keys, in reverse order, and to encrypt the \n" -"signature of the hash of the (encrypted) payload at each step. The " -"gateway \n" -"then sends that 16-step encrypted message, along with a 16-step and " -"16-wide \n" -"encrypted mapping to the first hop, which then decrypts the mapping and \n" -"the payload with their secret key, looking in the 16-wide mapping for \n" -"the entry associated with their own hop (keyed by the per-hop tunnel ID)" -" \n" -"and verifying the payload by checking it against the associated signed \n" -"hash." -msgstr "" -"Ajouter un ID unique de tunnel par étape n'est pas difficile, mais par " -"lui-même, insuffisant.\n" -"Si Dave et Bob sont sous le contrôle du même attaquant, ils ne seraient " -"pas capables de dire qu'ils sont dans le même tunnel en raison de l'ID de" -" tunnel, mais pourraient être capables de le dire par les corps de " -"message et les structures de vérification simplement en les comparant. " -"Pour l'empêcher, le tunnel doit utiliser du chiffrage feuilleté tout au " -"long du chemin, à la fois sur la charge utile du message transmis par " -"tunnel et sur la structure de vérification (utilisée pour empêcher les " -"attaques simples d'étiquetage). \n" -"Ceci exige quelques modifications simples du TunnelMessage, ainsi que\n" -"l'inclusion de clés secrètes par-étape livrées pendant la création de " -"tunnel\n" -"et données à la passerelle du tunnel. Nous devons fixer une longueur " -"maximale de tunnel \n" -"(par exemple 16 étapes) et charger la passerelle de chiffrer le message " -"vers chacune\n" -"des 16 clés secrètes livrées, dans l'ordre inverse, et de chiffrer la\n" -"signature du hachage de la charge utile (chiffrée) de chaque étape. La " -"passerelle\n" -"envoie alors ce message chiffré en 16 étapes, avec une cartographie " -"chiffrée à 16 étapes et 16 de largeur à la première étape, qui déchiffre " -"alors la cartographie et\n" -"la charge utile avec leur clé secrète, en regardant dans la cartographie " -"à 16 largeurs\n" -"pour l'entrée associée à leur propre étape (verrouillée par l'ID de " -"tunnel par-étape)\n" -"et en vérifiant la charge utile en la vérifiant contre le hachage signé " -"associé." - -#: i2p2www/pages/site/get-involved/todo.html:281 -msgid "" -"The tunnel gateway does still have more information than the other peers" -" \n" -"in the tunnel, and compromising both the gateway and a tunnel participant" -" \n" -"would allow those peers to collude, exposing the fact that they are both" -" \n" -"in the same tunnel. In addition, neighboring peers know that they are \n" -"in the same tunnel anyway, as they know who they send the message to (and" -" \n" -"with IP-based transports without restricted routes, they know who they \n" -"got it from). However, the above two techniques significantly increase \n" -"the cost of gaining meaningful samples when dealing with longer tunnels." -msgstr "" -"La passerelle de tunnel a vraiment toujours plus d'informations que les " -"autres pairs\n" -"dans le tunnel, et met en péril tant la passerelle qu'un participant de " -"tunnel\n" -"qui permettrait à ces pairs de s'associer, exposant le fait qu'ils sont " -"tous les deux\n" -"dans le même tunnel. De plus, des pairs voisins savent qu'ils sont\n" -"dans le même tunnel de toute façon, car ils savent à qui ils envoient le " -"message (à\n" -"avec quels transports IP sans routes restreintes, ils savent de qui ils\n" -"l'ont obtenu). Cependant, les deux susdites techniques augmentent " -"significativement \n" -"le coût pour obtenir des échantillons significatifs quand on traite avec " -"des tunnels plus longs." - -#: i2p2www/pages/site/get-involved/todo.html:297 -msgid "Implemented in release 0.6.2" -msgstr "Implémenté dans la version 0.6.2" - -#: i2p2www/pages/site/get-involved/todo.html:300 -#, python-format -msgid "" -"As Connelly proposed to deal with the\n" -"predecessor attack (2008\n" -"update), keeping the order of peers within our tunnels consistent \n" -"(aka whenever Alice creates a tunnel with both Bob and Charlie in it, \n" -"Bob's next hop is always Charlie), we address the issue as Bob doesn't \n" -"get to substantially sample Alice's peer selection group. We may even \n" -"want to explicitly allow Bob to participate in Alice's tunnels in only \n" -"one way - receiving a message from Dave and sending it to Charlie - and \n" -"if any of those peers are not available to participate in the tunnel (due" -" \n" -"to overload, network disconnection, etc), avoid asking Bob to participate" -" \n" -"in any tunnels until they are back online." -msgstr "" -"Comme Connelly l''a proposé pour traiter les\n" -"attaques précédesseur (mise" -"\n" -"à jour de 2008), garder cohérent l'ordre des pairs dans nos tunnels \n" -"(c'est-à-dire quand Alice y crée un tunnel tant avec Bob qu''avec Charlie" -" dedans,\n" -"l''étape suivante de Bob est toujours Charlie), nous abordons la question" -" comme Bob\n" -"ne parvient pas à considérablement échantillonner le groupe de sélection " -"de pairs d''Alice. Nous pouvons même vouloir explicitement permettre à " -"Bob de participer aux tunnels d''Alice de seulement\n" -"une façon - recevoir un message de Dave et l''envoyer à Charlie - et\n" -"si n'importe lequel de ces pairs n''est pas disponible pour participer au" -" tunnel (pour\n" -"cause de surcharge, déconnexion de réseau, etc), éviter de demander à Bob" -" de participer \n" -"à n''importe quel tunnel jusqu'à ce qu''ils soient de retour en ligne." - -#: i2p2www/pages/site/get-involved/todo.html:315 -msgid "" -"More analysis is necessary for revising the tunnel creation - at the \n" -"moment, we simply select and order randomly within the peer's top tier \n" -"of peers (ones with fast + high capacity)." -msgstr "" -"Davantage d''analyse est nécessaire pour réviser la création de tunnel - " -"à ce\n" -"moment, nous choisissons simplement et ordonnons aléatoirement dans le " -"niveau supérieur du pair\n" -"des pairs (ceux les plus rapides + hautes capacités)." - -#: i2p2www/pages/site/get-involved/todo.html:320 -msgid "" -"Adding a strict ordering to peers in a tunnel also improves the anonymity" -" \n" -"of peers with 0-hop tunnels, as otherwise the fact that a peer's gateway" -" \n" -"is always the same would be particularly damning. However, peers with \n" -"0-hop tunnels may want to periodically use a 1-hop tunnel to simulate \n" -"the failure of a normally reliable gateway peer (so every MTBF*(tunnel \n" -"duration) minutes, use a 1-hop tunnel)." -msgstr "" -"Ajouter un ordre strict aux pairs dans un tunnel améliore aussi " -"l'anonymat \n" -"des pairs ayant 0 étapes de tunnels, car autrement le fait que la " -"passerelle d'un pair\n" -"soit toujours la même seraient particulièrement pénalisant. Cependant, " -"les pairs avec\n" -"des tunnels à 0 étapes peuvent vouloir périodiquement utiliser un tunnel " -"à 1 étape pour simuler\n" -"l'échec d'un pair de passerelle normalement fiable (ainsi chaque " -"MTBF*(durée de\n" -"tunnel) minutes, en utilisant un tunnel à 1 étape)." - -#: i2p2www/pages/site/get-involved/todo.html:337 -msgid "" -"Without tunnel length permutation, if someone were to somehow detect that" -" \n" -"a destination had a particular number of hops, it might be able to use " -"that \n" -"information to identify the router the destination is located on, per the" -" \n" -"predecessor attack. For instance, if everyone has 2-hop tunnels, if Bob \n" -"receives a tunnel message from Charlie and forwards it to Alice, Bob " -"knows \n" -"Alice is the final router in the tunnel. If Bob were to identify what " -"destination \n" -"that tunnel served (by means of colluding with the gateway and harvesting" -" \n" -"the network database for all of the LeaseSets), he would know the router" -" \n" -"on which that destination is located (and without restricted routes, that" -" \n" -"would mean what IP address the destination is on)." -msgstr "" -"Sans permutation de longueur de tunnel, si quelqu'un devait d'une façon " -"ou d'une autre\n" -"détecter qu'une destination avait un nombre particulier d'étapes, il " -"pourrait pouvoir utiliser\n" -"cette information pour identifier le routeur sur lequel la destination " -"est localisées, par\n" -"l'attaque de prédécesseur. Par exemple, si tout le monde a des tunnels à " -"2 étapes, si Bob\n" -"reçoit un message de tunnel de Charlie et le fait suivre à Alice, Bob " -"sait que\n" -"Alice est le routeur final dans le tunnel. Si Bob devait identifier " -"quelle destination\n" -"ce tunnel dessert (par le moyen de s'associer avec la passerelle et " -"récolter\n" -"la base de données de réseau pour tous les jeux de baux), il connaîtrait " -"le routeur \n" -"sur lequel cette destination est localisée (et sans routes restreintes, " -"cela\n" -"signifierait quelle est l'adresse IP sur laquelle la destination est " -"branchée)" - -#: i2p2www/pages/site/get-involved/todo.html:349 -msgid "" -"It is to counter user behavior that tunnel lengths should be permuted, \n" -"using algorithms based on the length requested (for example, the 1/MTBF \n" -"length change for 0-hop tunnels outlined above)." -msgstr "" -"C'est pour résister au comportement d'utilisateur que les longueurs de " -"tunnel devraient être permutées,\n" -"en utilisant des algorithmes basés sur la longueur demandée (par exemple," -" le changement de longueur\n" -"1/MTBF pour les tunnels à 0 étapes décrits ci-dessus)." - -#: i2p2www/pages/site/get-involved/todo.html:359 +#: i2p2www/pages/site/get-involved/todo.html:71 msgid "" "The restricted route functionality described before was simply a " "functional \n" @@ -1375,7 +682,7 @@ msgstr "" "avec instruction\n" "de le faire suivre comme demandé." -#: i2p2www/pages/site/get-involved/todo.html:378 +#: i2p2www/pages/site/get-involved/todo.html:90 #, python-format msgid "" "Within the network, we will want some way to deter people from consuming" @@ -1400,7 +707,7 @@ msgstr "" "nous voulons \n" "rendre certaines requêtes \"chères\"." -#: i2p2www/pages/site/get-involved/todo.html:386 +#: 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 " @@ -1434,7 +741,7 @@ msgstr "" "les gens\n" "ayant peu de ressources." -#: i2p2www/pages/site/get-involved/todo.html:397 +#: 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" @@ -1447,7 +754,7 @@ msgstr "" "ce front\n" "seront appropriées." -#: i2p2www/pages/site/get-involved/todo.html:407 +#: i2p2www/pages/site/get-involved/todo.html:119 #, python-format msgid "" "To powerful passive external observers as well as large colluding " @@ -1487,7 +794,7 @@ msgstr "" "mise en œuvre des diverses\n" "stratégies de mélange de tunnels." -#: i2p2www/pages/site/get-involved/todo.html:420 +#: 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" @@ -1526,7 +833,7 @@ msgstr "" "les pairs en ont de\n" "disponible." -#: i2p2www/pages/site/get-involved/todo.html:433 +#: i2p2www/pages/site/get-involved/todo.html:145 msgid "" "In addition, we may want to implement code to dynamically reroute tunnels" " \n" @@ -1543,7 +850,7 @@ msgstr "" "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:444 +#: 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" @@ -1571,7 +878,7 @@ msgstr "" "lesquels\n" "le clou de girofle (clove) exposé inclut des instructions de retard." -#: i2p2www/pages/site/get-involved/todo.html:456 +#: i2p2www/pages/site/get-involved/todo.html:168 #, python-format msgid "" "Performance related improvements are listed on the\n" @@ -6042,3 +5349,11 @@ msgstr "" "Le canal IRC #i2p-dev, ou le forum " "translation sur %(zzz)s." + + + + + + + + diff --git a/i2p2www/translations/he/LC_MESSAGES/docs.po b/i2p2www/translations/he/LC_MESSAGES/docs.po index ad949356..85990a09 100644 --- a/i2p2www/translations/he/LC_MESSAGES/docs.po +++ b/i2p2www/translations/he/LC_MESSAGES/docs.po @@ -8,7 +8,7 @@ msgid "" msgstr "" "Project-Id-Version: I2P website\n" "Report-Msgid-Bugs-To: http://trac.i2p2.de\n" -"POT-Creation-Date: 2014-11-16 02:59+0000\n" +"POT-Creation-Date: 2014-11-27 12:12+0000\n" "PO-Revision-Date: 2014-02-09 19:53+0000\n" "Last-Translator: FULL NAME \n" "Language-Team: he \n" @@ -26,7 +26,9 @@ msgstr "" #: i2p2www/pages/site/docs/applications/embedding.html:3 #: i2p2www/pages/site/docs/how/cryptography.html:3 #: i2p2www/pages/site/docs/protocol/i2cp.html:3 +#: i2p2www/pages/site/docs/spec/configuration.html:3 #: i2p2www/pages/site/docs/spec/updates.html:3 +#: i2p2www/pages/site/docs/transport/ntcp.html:3 msgid "November 2014" msgstr "" @@ -129,7 +131,7 @@ msgstr "" msgid "Managed Clients" msgstr "" -#: i2p2www/pages/site/docs/index.html:44 i2p2www/pages/site/docs/index.html:217 +#: i2p2www/pages/site/docs/index.html:44 i2p2www/pages/site/docs/index.html:222 msgid "Embedding the router in your application" msgstr "" @@ -146,7 +148,7 @@ msgstr "" msgid "hostsdb.blockfile Format" msgstr "" -#: i2p2www/pages/site/docs/index.html:48 i2p2www/pages/site/docs/index.html:189 +#: i2p2www/pages/site/docs/index.html:48 i2p2www/pages/site/docs/index.html:194 msgid "Configuration File Format" msgstr "" @@ -164,369 +166,379 @@ msgstr "" msgid "Application Development Overview and Guide" msgstr "" -#: i2p2www/pages/site/docs/index.html:72 -msgid "SAM Protocol" +#: i2p2www/pages/site/docs/index.html:58 +#: i2p2www/pages/site/docs/api/i2ptunnel.html:55 +msgid "I2PTunnel Configuration" msgstr "" #: i2p2www/pages/site/docs/index.html:74 -msgid "SAMv2 Protocol" +msgid "SAM Protocol" msgstr "" #: i2p2www/pages/site/docs/index.html:76 -msgid "SAMv3 Protocol" +msgid "SAMv2 Protocol" msgstr "" #: i2p2www/pages/site/docs/index.html:78 +msgid "SAMv3 Protocol" +msgstr "" + +#: i2p2www/pages/site/docs/index.html:80 msgid "BOB Protocol" msgstr "" -#: i2p2www/pages/site/docs/index.html:81 +#: i2p2www/pages/site/docs/index.html:83 msgid "End-to-End Transport API and Protocols" msgstr "" -#: i2p2www/pages/site/docs/index.html:82 +#: i2p2www/pages/site/docs/index.html:84 msgid "" "The end-to-end protocols used by clients for reliable and unreliable " "communication." msgstr "" -#: i2p2www/pages/site/docs/index.html:84 +#: i2p2www/pages/site/docs/index.html:86 #: i2p2www/pages/site/docs/api/streaming.html:2 msgid "Streaming Library" msgstr "" -#: i2p2www/pages/site/docs/index.html:86 +#: i2p2www/pages/site/docs/index.html:88 msgid "Streaming Protocol Specification" msgstr "" -#: i2p2www/pages/site/docs/index.html:88 +#: i2p2www/pages/site/docs/index.html:90 msgid "Streaming Javadoc" msgstr "" -#: i2p2www/pages/site/docs/index.html:90 +#: i2p2www/pages/site/docs/index.html:92 #: i2p2www/pages/site/docs/api/datagrams.html:2 msgid "Datagrams" msgstr "" -#: i2p2www/pages/site/docs/index.html:92 +#: i2p2www/pages/site/docs/index.html:94 msgid "Datagram Javadoc" msgstr "" -#: i2p2www/pages/site/docs/index.html:95 +#: i2p2www/pages/site/docs/index.html:97 msgid "Client-to-Router Interface API and Protocol" msgstr "" -#: i2p2www/pages/site/docs/index.html:96 +#: 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" "Traditionally used only by Java applications and higher-level APIs." msgstr "" -#: i2p2www/pages/site/docs/index.html:101 +#: i2p2www/pages/site/docs/index.html:103 msgid "I2CP - I2P Control Protocol / API overview" msgstr "" -#: i2p2www/pages/site/docs/index.html:103 +#: i2p2www/pages/site/docs/index.html:105 msgid "I2CP Specification" msgstr "" -#: i2p2www/pages/site/docs/index.html:105 +#: i2p2www/pages/site/docs/index.html:107 msgid "I2CP API Javadoc" msgstr "" -#: i2p2www/pages/site/docs/index.html:107 -#: i2p2www/pages/site/docs/index.html:136 +#: i2p2www/pages/site/docs/index.html:109 +#: i2p2www/pages/site/docs/index.html:139 msgid "Common data structures specification" msgstr "" -#: i2p2www/pages/site/docs/index.html:109 -#: i2p2www/pages/site/docs/index.html:138 +#: i2p2www/pages/site/docs/index.html:111 +#: i2p2www/pages/site/docs/index.html:141 msgid "Data Structures Javadoc" msgstr "" -#: i2p2www/pages/site/docs/index.html:112 +#: i2p2www/pages/site/docs/index.html:114 msgid "End-to-End Encryption" msgstr "" -#: i2p2www/pages/site/docs/index.html:113 +#: i2p2www/pages/site/docs/index.html:115 msgid "How client messages are end-to-end encrypted by the router." msgstr "" -#: i2p2www/pages/site/docs/index.html:115 +#: i2p2www/pages/site/docs/index.html:117 msgid "ElGamal/AES+SessionTag encryption" msgstr "" -#: i2p2www/pages/site/docs/index.html:116 -#: i2p2www/pages/site/docs/index.html:149 +#: i2p2www/pages/site/docs/index.html:118 +#: i2p2www/pages/site/docs/index.html:152 msgid "ElGamal and AES cryptography details" msgstr "" -#: i2p2www/pages/site/docs/index.html:119 +#: i2p2www/pages/site/docs/index.html:121 #: i2p2www/pages/site/docs/how/tech-intro.html:15 #: i2p2www/pages/site/docs/how/tech-intro.html:329 msgid "Network Database" msgstr "" -#: i2p2www/pages/site/docs/index.html:120 +#: i2p2www/pages/site/docs/index.html:122 msgid "" "Distributed storage and retrieval of information about routers and " "clients." msgstr "" -#: i2p2www/pages/site/docs/index.html:122 +#: i2p2www/pages/site/docs/index.html:124 msgid "Network database overview, details, and threat analysis" msgstr "" -#: i2p2www/pages/site/docs/index.html:123 +#: i2p2www/pages/site/docs/index.html:125 msgid "Cryptographic hashes" msgstr "" -#: i2p2www/pages/site/docs/index.html:124 +#: i2p2www/pages/site/docs/index.html:126 msgid "Cryptographic signatures" msgstr "" #: i2p2www/pages/site/docs/index.html:127 +#: i2p2www/pages/site/docs/index.html:186 +msgid "Router reseed specification" +msgstr "" + +#: i2p2www/pages/site/docs/index.html:130 msgid "Router Message Protocol" msgstr "" -#: i2p2www/pages/site/docs/index.html:128 +#: i2p2www/pages/site/docs/index.html:131 msgid "" "I2P is a message-oriented router. The messages sent between routers are " "defined by the I2NP protocol." msgstr "" -#: i2p2www/pages/site/docs/index.html:130 +#: i2p2www/pages/site/docs/index.html:133 msgid "I2NP - I2P Network Protocol Overview" msgstr "" -#: i2p2www/pages/site/docs/index.html:132 +#: i2p2www/pages/site/docs/index.html:135 msgid "I2NP Specification" msgstr "" -#: i2p2www/pages/site/docs/index.html:134 +#: i2p2www/pages/site/docs/index.html:137 msgid "I2NP Javadoc" msgstr "" -#: i2p2www/pages/site/docs/index.html:141 +#: i2p2www/pages/site/docs/index.html:144 #: i2p2www/pages/site/docs/how/tech-intro.html:14 #: i2p2www/pages/site/docs/how/tech-intro.html:228 msgid "Tunnels" msgstr "" -#: i2p2www/pages/site/docs/index.html:142 +#: i2p2www/pages/site/docs/index.html:145 msgid "" "Selecting peers, requesting tunnels through those peers, and encrypting " "and routing messages through these tunnels." msgstr "" -#: i2p2www/pages/site/docs/index.html:144 +#: i2p2www/pages/site/docs/index.html:147 msgid "Peer profiling and selection" msgstr "" -#: i2p2www/pages/site/docs/index.html:145 +#: i2p2www/pages/site/docs/index.html:148 msgid "Tunnel routing overview" msgstr "" -#: i2p2www/pages/site/docs/index.html:146 +#: i2p2www/pages/site/docs/index.html:149 msgid "Garlic routing and \"garlic\" terminology" msgstr "" -#: i2p2www/pages/site/docs/index.html:147 +#: i2p2www/pages/site/docs/index.html:150 msgid "Tunnel building and encryption" msgstr "" -#: i2p2www/pages/site/docs/index.html:148 +#: i2p2www/pages/site/docs/index.html:151 msgid "ElGamal/AES" msgstr "" -#: i2p2www/pages/site/docs/index.html:148 +#: i2p2www/pages/site/docs/index.html:151 msgid "for build request encryption" msgstr "" -#: i2p2www/pages/site/docs/index.html:150 +#: i2p2www/pages/site/docs/index.html:153 msgid "Tunnel building specification" msgstr "" -#: i2p2www/pages/site/docs/index.html:151 +#: i2p2www/pages/site/docs/index.html:154 msgid "Low-level tunnel message specification" msgstr "" -#: i2p2www/pages/site/docs/index.html:152 +#: i2p2www/pages/site/docs/index.html:155 #: i2p2www/pages/site/docs/tunnels/unidirectional.html:2 msgid "Unidirectional Tunnels" msgstr "" -#: i2p2www/pages/site/docs/index.html:153 +#: i2p2www/pages/site/docs/index.html:156 #: i2p2www/pages/site/docs/how/peer-selection.html:299 msgid "Peer Profiling and Selection in the I2P Anonymous Network" msgstr "" -#: i2p2www/pages/site/docs/index.html:154 +#: i2p2www/pages/site/docs/index.html:157 msgid "2009 paper (pdf), not current but still generally accurate" msgstr "" -#: i2p2www/pages/site/docs/index.html:157 +#: i2p2www/pages/site/docs/index.html:160 msgid "Transport Layer" msgstr "" -#: i2p2www/pages/site/docs/index.html:158 +#: i2p2www/pages/site/docs/index.html:161 msgid "The protocols for direct (point-to-point) router to router communication." msgstr "" -#: i2p2www/pages/site/docs/index.html:160 +#: i2p2www/pages/site/docs/index.html:163 msgid "Transport layer overview" msgstr "" -#: i2p2www/pages/site/docs/index.html:162 +#: i2p2www/pages/site/docs/index.html:165 msgid "TCP-based transport overview and specification" msgstr "" -#: i2p2www/pages/site/docs/index.html:164 +#: i2p2www/pages/site/docs/index.html:167 msgid "UDP-based transport overview" msgstr "" -#: i2p2www/pages/site/docs/index.html:166 +#: i2p2www/pages/site/docs/index.html:169 msgid "SSU specification" msgstr "" -#: i2p2www/pages/site/docs/index.html:168 +#: i2p2www/pages/site/docs/index.html:171 msgid "NTCP transport encryption" msgstr "" -#: i2p2www/pages/site/docs/index.html:170 +#: i2p2www/pages/site/docs/index.html:173 msgid "SSU transport encryption" msgstr "" -#: i2p2www/pages/site/docs/index.html:172 +#: i2p2www/pages/site/docs/index.html:175 msgid "Transport Javadoc" msgstr "" -#: i2p2www/pages/site/docs/index.html:174 +#: i2p2www/pages/site/docs/index.html:177 msgid "NTCP Javadoc" msgstr "" -#: i2p2www/pages/site/docs/index.html:176 +#: i2p2www/pages/site/docs/index.html:179 msgid "SSU Javadoc" msgstr "" -#: i2p2www/pages/site/docs/index.html:179 +#: i2p2www/pages/site/docs/index.html:182 msgid "Other Router Topics" msgstr "" -#: i2p2www/pages/site/docs/index.html:181 +#: i2p2www/pages/site/docs/index.html:184 msgid "Router software updates" msgstr "" -#: i2p2www/pages/site/docs/index.html:183 +#: i2p2www/pages/site/docs/index.html:188 msgid "Native BigInteger Library" msgstr "" -#: i2p2www/pages/site/docs/index.html:185 +#: i2p2www/pages/site/docs/index.html:190 msgid "Time synchronization and NTP" msgstr "" -#: i2p2www/pages/site/docs/index.html:187 +#: i2p2www/pages/site/docs/index.html:192 msgid "Performance" msgstr "" -#: i2p2www/pages/site/docs/index.html:194 +#: i2p2www/pages/site/docs/index.html:199 msgid "Developer's Guides and Resources" msgstr "" -#: i2p2www/pages/site/docs/index.html:196 +#: i2p2www/pages/site/docs/index.html:201 msgid "New Developer's Guide" msgstr "" -#: i2p2www/pages/site/docs/index.html:198 +#: i2p2www/pages/site/docs/index.html:203 msgid "New Translator's Guide" msgstr "" -#: i2p2www/pages/site/docs/index.html:200 +#: i2p2www/pages/site/docs/index.html:205 msgid "Monotone Guide" msgstr "" -#: i2p2www/pages/site/docs/index.html:202 +#: i2p2www/pages/site/docs/index.html:207 msgid "Developer Guidelines" msgstr "" -#: i2p2www/pages/site/docs/index.html:204 +#: i2p2www/pages/site/docs/index.html:209 msgid "Javadocs on the standard internet:" msgstr "" -#: i2p2www/pages/site/docs/index.html:205 -#: i2p2www/pages/site/docs/index.html:209 #: i2p2www/pages/site/docs/index.html:210 -#: i2p2www/pages/site/docs/index.html:211 +#: i2p2www/pages/site/docs/index.html:214 +#: i2p2www/pages/site/docs/index.html:215 +#: i2p2www/pages/site/docs/index.html:216 #, python-format msgid "Server %(num)s" msgstr "" -#: i2p2www/pages/site/docs/index.html:206 -#: i2p2www/pages/site/docs/index.html:215 +#: i2p2www/pages/site/docs/index.html:211 +#: i2p2www/pages/site/docs/index.html:220 msgid "" "Note: always verify that javadocs are current by checking the release " "number." msgstr "" -#: i2p2www/pages/site/docs/index.html:208 +#: i2p2www/pages/site/docs/index.html:213 msgid "Javadocs inside I2P:" msgstr "" -#: i2p2www/pages/site/docs/index.html:219 +#: i2p2www/pages/site/docs/index.html:224 msgid "Ports used by I2P" msgstr "" -#: i2p2www/pages/site/docs/index.html:221 +#: i2p2www/pages/site/docs/index.html:226 msgid "Automatic updates to development builds inside I2P" msgstr "" -#: i2p2www/pages/site/docs/index.html:223 +#: i2p2www/pages/site/docs/index.html:228 msgid "Updating the wrapper manually" msgstr "" -#: i2p2www/pages/site/docs/index.html:225 +#: i2p2www/pages/site/docs/index.html:230 msgid "User forum" msgstr "" -#: i2p2www/pages/site/docs/index.html:227 +#: i2p2www/pages/site/docs/index.html:232 msgid "Developer forum inside I2P" msgstr "" -#: i2p2www/pages/site/docs/index.html:229 +#: i2p2www/pages/site/docs/index.html:234 msgid "Bug tracker" msgstr "" -#: i2p2www/pages/site/docs/index.html:231 +#: i2p2www/pages/site/docs/index.html:236 msgid "Viewmtn inside I2P" msgstr "" -#: i2p2www/pages/site/docs/index.html:233 +#: i2p2www/pages/site/docs/index.html:238 msgid "I2P Source exported to GitHub" msgstr "" -#: i2p2www/pages/site/docs/index.html:235 +#: i2p2www/pages/site/docs/index.html:240 msgid "I2P Source Git Repo inside I2P" msgstr "" -#: i2p2www/pages/site/docs/index.html:237 +#: i2p2www/pages/site/docs/index.html:242 msgid "Source translation at Transifex" msgstr "" -#: i2p2www/pages/site/docs/index.html:239 +#: i2p2www/pages/site/docs/index.html:244 msgid "Roadmap wiki" msgstr "" -#: i2p2www/pages/site/docs/index.html:241 +#: i2p2www/pages/site/docs/index.html:246 msgid "Old roadmap" msgstr "" -#: i2p2www/pages/site/docs/index.html:241 -#: i2p2www/pages/site/docs/index.html:243 +#: i2p2www/pages/site/docs/index.html:246 +#: i2p2www/pages/site/docs/index.html:248 msgid "not current" msgstr "" -#: i2p2www/pages/site/docs/index.html:243 +#: i2p2www/pages/site/docs/index.html:248 msgid "To Do List" msgstr "" @@ -787,7 +799,7 @@ msgid "" msgstr "" #: i2p2www/pages/site/docs/naming.html:183 -#: i2p2www/pages/site/docs/spec/configuration.html:170 +#: i2p2www/pages/site/docs/spec/configuration.html:184 msgid "Addressbook" msgstr "" @@ -1157,7 +1169,7 @@ msgid "" msgstr "" #: i2p2www/pages/site/docs/plugins.html:2 -#: i2p2www/pages/site/docs/spec/configuration.html:138 +#: i2p2www/pages/site/docs/spec/configuration.html:152 msgid "Plugins" msgstr "" @@ -2533,15 +2545,19 @@ msgid "" msgstr "" #: i2p2www/pages/site/docs/api/i2ptunnel.html:54 +msgid "Configuration" +msgstr "" + +#: i2p2www/pages/site/docs/api/i2ptunnel.html:58 msgid "Client Modes" msgstr "" -#: i2p2www/pages/site/docs/api/i2ptunnel.html:55 -#: i2p2www/pages/site/docs/api/i2ptunnel.html:137 +#: i2p2www/pages/site/docs/api/i2ptunnel.html:59 +#: i2p2www/pages/site/docs/api/i2ptunnel.html:141 msgid "Standard" msgstr "" -#: i2p2www/pages/site/docs/api/i2ptunnel.html:56 +#: 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" @@ -2549,7 +2565,7 @@ msgid "" " list of destinations." msgstr "" -#: i2p2www/pages/site/docs/api/i2ptunnel.html:62 +#: i2p2www/pages/site/docs/api/i2ptunnel.html:66 msgid "" "A HTTP-client tunnel. The tunnel connects to the destination specified by" " the URL\n" @@ -2557,34 +2573,34 @@ msgid "" "provided. Strips HTTP connections of the following headers:" msgstr "" -#: i2p2www/pages/site/docs/api/i2ptunnel.html:67 +#: 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 "" -#: i2p2www/pages/site/docs/api/i2ptunnel.html:75 +#: 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 "" -#: i2p2www/pages/site/docs/api/i2ptunnel.html:82 +#: 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 "" -#: i2p2www/pages/site/docs/api/i2ptunnel.html:86 +#: i2p2www/pages/site/docs/api/i2ptunnel.html:90 msgid "Outproxy:" msgstr "" -#: i2p2www/pages/site/docs/api/i2ptunnel.html:87 +#: i2p2www/pages/site/docs/api/i2ptunnel.html:91 msgid "Internal I2P use:" msgstr "" -#: i2p2www/pages/site/docs/api/i2ptunnel.html:92 +#: i2p2www/pages/site/docs/api/i2ptunnel.html:96 msgid "" "Creates a connection to a random IRC server specified by the comma " "seprated (\", \") \n" @@ -2592,43 +2608,43 @@ msgid "" "allowed due to anonymity concerns." msgstr "" -#: i2p2www/pages/site/docs/api/i2ptunnel.html:96 +#: i2p2www/pages/site/docs/api/i2ptunnel.html:100 msgid "Whitelist:" msgstr "" -#: i2p2www/pages/site/docs/api/i2ptunnel.html:111 +#: i2p2www/pages/site/docs/api/i2ptunnel.html:115 msgid "Enables using the I2P router as a SOCKS proxy." msgstr "" -#: i2p2www/pages/site/docs/api/i2ptunnel.html:116 +#: 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" "IRC client mode." msgstr "" -#: i2p2www/pages/site/docs/api/i2ptunnel.html:122 +#: 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 "" -#: i2p2www/pages/site/docs/api/i2ptunnel.html:128 +#: 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" "subscribe to a streamr server tunnel." msgstr "" -#: i2p2www/pages/site/docs/api/i2ptunnel.html:136 +#: i2p2www/pages/site/docs/api/i2ptunnel.html:140 msgid "Server Modes" msgstr "" -#: i2p2www/pages/site/docs/api/i2ptunnel.html:138 +#: i2p2www/pages/site/docs/api/i2ptunnel.html:142 msgid "Creates a destination to a local ip:port with an open TCP port." msgstr "" -#: i2p2www/pages/site/docs/api/i2ptunnel.html:143 +#: 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" @@ -2636,7 +2652,7 @@ msgid "" " such a request." msgstr "" -#: i2p2www/pages/site/docs/api/i2ptunnel.html:149 +#: 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" @@ -2645,14 +2661,14 @@ msgid "" "requests, or loopback-testing an eepsite as a diagnostic tool." msgstr "" -#: i2p2www/pages/site/docs/api/i2ptunnel.html:156 +#: i2p2www/pages/site/docs/api/i2ptunnel.html:160 msgid "" "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:162 +#: 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." @@ -3445,8 +3461,8 @@ msgstr "" #: i2p2www/pages/site/docs/how/tunnel-routing.html:255 #: i2p2www/pages/site/docs/protocol/i2cp.html:687 #: i2p2www/pages/site/docs/protocol/i2np.html:226 -#: i2p2www/pages/site/docs/spec/updates.html:438 -#: i2p2www/pages/site/docs/transport/ntcp.html:535 +#: i2p2www/pages/site/docs/spec/updates.html:488 +#: i2p2www/pages/site/docs/transport/ntcp.html:544 #: i2p2www/pages/site/docs/transport/ssu.html:554 #: i2p2www/pages/site/docs/tunnels/implementation.html:506 msgid "Future Work" @@ -3997,6 +4013,14 @@ 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)." +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" "If done wrong, it could cause real harm to our network.\n" @@ -4005,11 +4029,11 @@ msgid "" "This page discusses some general guidelines." msgstr "" -#: i2p2www/pages/site/docs/applications/embedding.html:18 +#: i2p2www/pages/site/docs/applications/embedding.html:23 msgid "Talk to us" msgstr "" -#: i2p2www/pages/site/docs/applications/embedding.html:19 +#: 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" @@ -4017,11 +4041,11 @@ msgid "" "everyone." msgstr "" -#: i2p2www/pages/site/docs/applications/embedding.html:25 +#: i2p2www/pages/site/docs/applications/embedding.html:30 msgid "Choose your router wisely" msgstr "" -#: i2p2www/pages/site/docs/applications/embedding.html:26 +#: 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" @@ -4031,19 +4055,19 @@ msgid "" "Some of the following only applies to the Java router." msgstr "" -#: i2p2www/pages/site/docs/applications/embedding.html:34 +#: i2p2www/pages/site/docs/applications/embedding.html:39 msgid "Licensing" msgstr "" -#: i2p2www/pages/site/docs/applications/embedding.html:35 +#: i2p2www/pages/site/docs/applications/embedding.html:40 msgid "Ensure you meet the license requirements of the software you are bundling." msgstr "" -#: i2p2www/pages/site/docs/applications/embedding.html:40 +#: i2p2www/pages/site/docs/applications/embedding.html:45 msgid "Verify default configuration" msgstr "" -#: i2p2www/pages/site/docs/applications/embedding.html:41 +#: i2p2www/pages/site/docs/applications/embedding.html:46 msgid "" "A correct default configuration is crucial. Most users will not change " "the defaults.\n" @@ -4052,7 +4076,7 @@ msgid "" "Override the router defaults if necessary." msgstr "" -#: i2p2www/pages/site/docs/applications/embedding.html:46 +#: i2p2www/pages/site/docs/applications/embedding.html:51 msgid "" "Some important defaults to review: Max bandwidth, tunnel quantity and " "length, max participating tunnels.\n" @@ -4060,7 +4084,7 @@ msgid "" "your app." msgstr "" -#: i2p2www/pages/site/docs/applications/embedding.html:50 +#: i2p2www/pages/site/docs/applications/embedding.html:55 msgid "" "Configure enough bandwidth and tunnels to allow your users to contribute " "to the network.\n" @@ -4070,11 +4094,11 @@ msgid "" "example." msgstr "" -#: i2p2www/pages/site/docs/applications/embedding.html:57 +#: i2p2www/pages/site/docs/applications/embedding.html:62 msgid "Participating Traffic Considerations" msgstr "" -#: i2p2www/pages/site/docs/applications/embedding.html:58 +#: 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, " @@ -4086,14 +4110,14 @@ msgid "" "tunnels." msgstr "" -#: i2p2www/pages/site/docs/applications/embedding.html:65 +#: 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" "which is helped tremendously by others building tunnels through you." msgstr "" -#: i2p2www/pages/site/docs/applications/embedding.html:69 +#: i2p2www/pages/site/docs/applications/embedding.html:74 msgid "" "Secondly, over 90% of the routers in the current network allow " "participating traffic.\n" @@ -4105,13 +4129,13 @@ msgid "" " people to enable relaying." msgstr "" -#: i2p2www/pages/site/docs/applications/embedding.html:76 +#: i2p2www/pages/site/docs/applications/embedding.html:81 msgid "" "Thirdly, participating traffic is cover traffic that helps your users' " "anonymity." msgstr "" -#: i2p2www/pages/site/docs/applications/embedding.html:79 +#: i2p2www/pages/site/docs/applications/embedding.html:84 msgid "" "We strongly discourage you from disabling participating traffic by " "default.\n" @@ -4119,11 +4143,11 @@ msgid "" "the network." msgstr "" -#: i2p2www/pages/site/docs/applications/embedding.html:85 +#: i2p2www/pages/site/docs/applications/embedding.html:90 msgid "Persistence" msgstr "" -#: i2p2www/pages/site/docs/applications/embedding.html:86 +#: 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" @@ -4133,11 +4157,11 @@ msgid "" "performance." msgstr "" -#: i2p2www/pages/site/docs/applications/embedding.html:94 +#: i2p2www/pages/site/docs/applications/embedding.html:99 msgid "Configurability" msgstr "" -#: i2p2www/pages/site/docs/applications/embedding.html:95 +#: i2p2www/pages/site/docs/applications/embedding.html:100 msgid "" "Give your users a way to change the configuration of the important " "settings.\n" @@ -4147,11 +4171,11 @@ msgid "" "IP/port may be helpful." msgstr "" -#: i2p2www/pages/site/docs/applications/embedding.html:103 +#: i2p2www/pages/site/docs/applications/embedding.html:108 msgid "Floodfill Considerations" msgstr "" -#: i2p2www/pages/site/docs/applications/embedding.html:104 +#: 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" @@ -4162,11 +4186,11 @@ msgid "" "It also depends on the typical uptime for your application." msgstr "" -#: i2p2www/pages/site/docs/applications/embedding.html:114 +#: i2p2www/pages/site/docs/applications/embedding.html:119 msgid "Reseeding" msgstr "" -#: i2p2www/pages/site/docs/applications/embedding.html:115 +#: 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 " @@ -4174,11 +4198,11 @@ msgid "" "Be aware of possible blocking by hostile governments." msgstr "" -#: i2p2www/pages/site/docs/applications/embedding.html:124 +#: i2p2www/pages/site/docs/applications/embedding.html:129 msgid "Reduce Network Resource Usage" msgstr "" -#: i2p2www/pages/site/docs/applications/embedding.html:125 +#: 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" @@ -4188,11 +4212,11 @@ msgid "" "tunnel, even in the presence of some background DHT activity." msgstr "" -#: i2p2www/pages/site/docs/applications/embedding.html:133 +#: i2p2www/pages/site/docs/applications/embedding.html:138 msgid "Updatability" msgstr "" -#: i2p2www/pages/site/docs/applications/embedding.html:134 +#: 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" @@ -4207,11 +4231,11 @@ msgid "" "which you presumably are not bundling." msgstr "" -#: i2p2www/pages/site/docs/applications/embedding.html:145 +#: i2p2www/pages/site/docs/applications/embedding.html:150 msgid "Rollout" msgstr "" -#: i2p2www/pages/site/docs/applications/embedding.html:146 +#: 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 " @@ -4227,11 +4251,11 @@ msgid "" "checklist is." msgstr "" -#: i2p2www/pages/site/docs/applications/embedding.html:158 +#: i2p2www/pages/site/docs/applications/embedding.html:163 msgid "Design for and Encourage Long Uptimes" msgstr "" -#: i2p2www/pages/site/docs/applications/embedding.html:159 +#: 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 " @@ -4240,53 +4264,53 @@ msgid "" "solution." msgstr "" -#: i2p2www/pages/site/docs/applications/embedding.html:167 +#: i2p2www/pages/site/docs/applications/embedding.html:172 msgid "Show Status" msgstr "" -#: i2p2www/pages/site/docs/applications/embedding.html:168 +#: i2p2www/pages/site/docs/applications/embedding.html:173 msgid "" "Provide some indication to the user that the application tunnels are " "ready. Encourage patience." msgstr "" -#: i2p2www/pages/site/docs/applications/embedding.html:173 +#: i2p2www/pages/site/docs/applications/embedding.html:178 msgid "Graceful Shutdown" msgstr "" -#: i2p2www/pages/site/docs/applications/embedding.html:174 +#: 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 "" -#: i2p2www/pages/site/docs/applications/embedding.html:180 +#: i2p2www/pages/site/docs/applications/embedding.html:185 msgid "Education and Donation" msgstr "" -#: i2p2www/pages/site/docs/applications/embedding.html:181 +#: 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 "" -#: i2p2www/pages/site/docs/applications/embedding.html:187 +#: i2p2www/pages/site/docs/applications/embedding.html:192 msgid "External Router Option" msgstr "" -#: i2p2www/pages/site/docs/applications/embedding.html:188 +#: 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 "" -#: i2p2www/pages/site/docs/applications/embedding.html:195 +#: i2p2www/pages/site/docs/applications/embedding.html:200 msgid "Use of other Common Services" msgstr "" -#: i2p2www/pages/site/docs/applications/embedding.html:196 +#: 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" @@ -4294,11 +4318,11 @@ msgid "" "and talk to the people who are running them to make sure it's ok." msgstr "" -#: i2p2www/pages/site/docs/applications/embedding.html:204 +#: i2p2www/pages/site/docs/applications/embedding.html:209 msgid "Time / NTP Issues" msgstr "" -#: i2p2www/pages/site/docs/applications/embedding.html:205 +#: 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. " @@ -4307,11 +4331,11 @@ msgid "" "clock is correct." msgstr "" -#: i2p2www/pages/site/docs/applications/embedding.html:213 +#: i2p2www/pages/site/docs/applications/embedding.html:218 msgid "Choose What and How you Bundle" msgstr "" -#: i2p2www/pages/site/docs/applications/embedding.html:214 +#: 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" @@ -4329,11 +4353,19 @@ msgid "" "and i2psnark, for example." msgstr "" -#: i2p2www/pages/site/docs/applications/embedding.html:228 +#: i2p2www/pages/site/docs/applications/embedding.html:233 +msgid "You may also wish to bundle a hosts.txt file." +msgstr "" + +#: i2p2www/pages/site/docs/applications/embedding.html:236 +msgid "Be sure to specify a Java 6 bootclasspath if compiling with Java 8." +msgstr "" + +#: i2p2www/pages/site/docs/applications/embedding.html:244 msgid "Datagram (DHT) considerations" msgstr "" -#: i2p2www/pages/site/docs/applications/embedding.html:229 +#: 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 " @@ -4349,32 +4381,32 @@ msgid "" "have several." msgstr "" -#: i2p2www/pages/site/docs/applications/embedding.html:242 +#: i2p2www/pages/site/docs/applications/embedding.html:258 msgid "Comarketing" msgstr "" -#: i2p2www/pages/site/docs/applications/embedding.html:243 +#: 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 "" -#: i2p2www/pages/site/docs/applications/embedding.html:249 +#: i2p2www/pages/site/docs/applications/embedding.html:265 msgid "Malware" msgstr "" -#: i2p2www/pages/site/docs/applications/embedding.html:250 +#: i2p2www/pages/site/docs/applications/embedding.html:266 msgid "" "Please don't use I2P for evil.\n" "It could cause great harm both to our network and our reputation." msgstr "" -#: i2p2www/pages/site/docs/applications/embedding.html:256 +#: i2p2www/pages/site/docs/applications/embedding.html:272 msgid "Join Us" msgstr "" -#: i2p2www/pages/site/docs/applications/embedding.html:257 +#: 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" @@ -4382,11 +4414,11 @@ msgid "" "We can help get you users, testers, translators, or even coders." msgstr "" -#: i2p2www/pages/site/docs/applications/embedding.html:265 +#: i2p2www/pages/site/docs/applications/embedding.html:281 msgid "Application Examples" msgstr "" -#: i2p2www/pages/site/docs/applications/embedding.html:266 +#: 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" @@ -4396,17 +4428,17 @@ msgid "" " and Monero." msgstr "" -#: i2p2www/pages/site/docs/applications/embedding.html:274 +#: i2p2www/pages/site/docs/applications/embedding.html:290 msgid "Code Example" msgstr "" -#: i2p2www/pages/site/docs/applications/embedding.html:275 +#: i2p2www/pages/site/docs/applications/embedding.html:291 msgid "" "None of the above actually tells you how to write your code to\n" "bundle the Java router, so following is a brief example." msgstr "" -#: i2p2www/pages/site/docs/applications/embedding.html:290 +#: 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" @@ -7270,7 +7302,6 @@ msgid "The Network Database" msgstr "" #: i2p2www/pages/site/docs/how/network-database.html:3 -#: i2p2www/pages/site/docs/transport/ntcp.html:3 msgid "October 2014" msgstr "" @@ -14524,10 +14555,6 @@ msgstr "" msgid "Configuration File Specification" msgstr "" -#: i2p2www/pages/site/docs/spec/configuration.html:3 -msgid "January 2014" -msgstr "" - #: i2p2www/pages/site/docs/spec/configuration.html:7 msgid "" "This page provides a general specification of I2P configuration files,\n" @@ -14636,65 +14663,66 @@ msgid "Configured via /configlogging in the router console." msgstr "" #: i2p2www/pages/site/docs/spec/configuration.html:112 -#: i2p2www/pages/site/docs/spec/configuration.html:142 -#: i2p2www/pages/site/docs/spec/configuration.html:154 +#: i2p2www/pages/site/docs/spec/configuration.html:156 +#: i2p2www/pages/site/docs/spec/configuration.html:168 +#: i2p2www/pages/site/docs/spec/configuration.html:198 msgid "Properties are as follows:" msgstr "" -#: i2p2www/pages/site/docs/spec/configuration.html:133 +#: i2p2www/pages/site/docs/spec/configuration.html:147 msgid "Individual Plugin" msgstr "" -#: i2p2www/pages/site/docs/spec/configuration.html:134 +#: i2p2www/pages/site/docs/spec/configuration.html:148 #, python-format msgid "See the plugin specification." msgstr "" -#: i2p2www/pages/site/docs/spec/configuration.html:139 +#: i2p2www/pages/site/docs/spec/configuration.html:153 msgid "Enable/disable for each installed plugin." msgstr "" -#: i2p2www/pages/site/docs/spec/configuration.html:150 +#: i2p2www/pages/site/docs/spec/configuration.html:164 msgid "Webapps" msgstr "" -#: i2p2www/pages/site/docs/spec/configuration.html:151 +#: i2p2www/pages/site/docs/spec/configuration.html:165 msgid "Enable/disable for each installed webapp." msgstr "" -#: i2p2www/pages/site/docs/spec/configuration.html:163 +#: i2p2www/pages/site/docs/spec/configuration.html:177 msgid "Router" msgstr "" -#: i2p2www/pages/site/docs/spec/configuration.html:164 +#: i2p2www/pages/site/docs/spec/configuration.html:178 msgid "Configured via /configadvanced in the router console." msgstr "" -#: i2p2www/pages/site/docs/spec/configuration.html:168 +#: i2p2www/pages/site/docs/spec/configuration.html:182 msgid "Applications" msgstr "" -#: i2p2www/pages/site/docs/spec/configuration.html:171 +#: i2p2www/pages/site/docs/spec/configuration.html:185 msgid "See documentation in SusiDNS." msgstr "" -#: i2p2www/pages/site/docs/spec/configuration.html:176 +#: i2p2www/pages/site/docs/spec/configuration.html:190 msgid "Configured via the application gui." msgstr "" -#: i2p2www/pages/site/docs/spec/configuration.html:181 +#: i2p2www/pages/site/docs/spec/configuration.html:195 msgid "Configured via the /i2ptunnel application in the router console." msgstr "" -#: i2p2www/pages/site/docs/spec/configuration.html:185 +#: i2p2www/pages/site/docs/spec/configuration.html:364 msgid "Router Console" msgstr "" -#: i2p2www/pages/site/docs/spec/configuration.html:186 +#: i2p2www/pages/site/docs/spec/configuration.html:365 msgid "The router console uses the router.config file." msgstr "" -#: i2p2www/pages/site/docs/spec/configuration.html:191 +#: i2p2www/pages/site/docs/spec/configuration.html:370 msgid "See post on zzz.i2p." msgstr "" @@ -15089,6 +15117,7 @@ msgstr "" #: i2p2www/pages/site/docs/spec/updates.html:204 #: i2p2www/pages/site/docs/spec/updates.html:313 +#: i2p2www/pages/site/docs/spec/updates.html:365 msgid "Goals:" msgstr "" @@ -15111,7 +15140,8 @@ msgid "One-pass signature verification and file extraction" msgstr "" #: i2p2www/pages/site/docs/spec/updates.html:222 -#: i2p2www/pages/site/docs/spec/updates.html:336 +#: i2p2www/pages/site/docs/spec/updates.html:328 +#: i2p2www/pages/site/docs/spec/updates.html:388 msgid "Specification:" msgstr "" @@ -15120,40 +15150,79 @@ msgid "All unused fields must be set to 0 for compatibility with future versions msgstr "" #: i2p2www/pages/site/docs/spec/updates.html:308 -msgid "SU3 News File Specification" +msgid "SU3 Reseed File Specification" msgstr "" #: i2p2www/pages/site/docs/spec/updates.html:309 -msgid "As of 0.9.17, the news is delivered in an \"su3\" file format." +msgid "As of 0.9.14, reseed data is delivered in an \"su3\" file format." msgstr "" #: i2p2www/pages/site/docs/spec/updates.html:316 -msgid "Signed news with strong signatures and trusted certificates" +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 "" -#: i2p2www/pages/site/docs/spec/updates.html:319 +#: 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 "" -#: i2p2www/pages/site/docs/spec/updates.html:322 -msgid "Standard XML format for use with standard parsers" -msgstr "" - -#: i2p2www/pages/site/docs/spec/updates.html:325 -msgid "Standard Atom format for use with standard feed readers and generators" -msgstr "" - -#: i2p2www/pages/site/docs/spec/updates.html:328 -msgid "Sanitization and verification of HTML before displaying on console" +#: i2p2www/pages/site/docs/spec/updates.html:323 +msgid "" +"Single compressed file to speed up reseeding, which was slow to fetch 200" +" files" msgstr "" #: i2p2www/pages/site/docs/spec/updates.html:331 +msgid "The file must be named \"i2pseeds.su3\"." +msgstr "" + +#: i2p2www/pages/site/docs/spec/updates.html:334 +msgid "" +"The file must be in the same directory as the router infos on the web " +"server." +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" +"and then fetch the individual router info files found in the links." +msgstr "" + +#: i2p2www/pages/site/docs/spec/updates.html:360 +msgid "SU3 News File Specification" +msgstr "" + +#: i2p2www/pages/site/docs/spec/updates.html:361 +msgid "As of 0.9.17, the news is delivered in an \"su3\" file format." +msgstr "" + +#: i2p2www/pages/site/docs/spec/updates.html:368 +msgid "Signed news with strong signatures and trusted certificates" +msgstr "" + +#: i2p2www/pages/site/docs/spec/updates.html:374 +msgid "Standard XML format for use with standard parsers" +msgstr "" + +#: i2p2www/pages/site/docs/spec/updates.html:377 +msgid "Standard Atom format for use with standard feed readers and generators" +msgstr "" + +#: i2p2www/pages/site/docs/spec/updates.html:380 +msgid "Sanitization and verification of HTML before displaying on console" +msgstr "" + +#: i2p2www/pages/site/docs/spec/updates.html:383 msgid "" "Suitable for easy implementation on Android and other platforms without " "an HTML console" msgstr "" -#: i2p2www/pages/site/docs/spec/updates.html:440 +#: 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" @@ -15746,7 +15815,7 @@ msgstr "" #: i2p2www/pages/site/docs/transport/ntcp.html:207 #: i2p2www/pages/site/docs/transport/ntcp.html:250 #: i2p2www/pages/site/docs/transport/ntcp.html:332 -#: i2p2www/pages/site/docs/transport/ntcp.html:428 +#: i2p2www/pages/site/docs/transport/ntcp.html:437 msgid "Size:" msgstr "" @@ -15764,7 +15833,7 @@ msgstr "" #: i2p2www/pages/site/docs/transport/ntcp.html:236 #: i2p2www/pages/site/docs/transport/ntcp.html:319 -#: i2p2www/pages/site/docs/transport/ntcp.html:397 +#: i2p2www/pages/site/docs/transport/ntcp.html:398 msgid "Notes:" msgstr "" @@ -15784,7 +15853,7 @@ msgstr "" #: i2p2www/pages/site/docs/transport/ntcp.html:252 #: i2p2www/pages/site/docs/transport/ntcp.html:334 -#: i2p2www/pages/site/docs/transport/ntcp.html:430 +#: i2p2www/pages/site/docs/transport/ntcp.html:439 msgid "Unencrypted Contents:" msgstr "" @@ -15808,7 +15877,7 @@ msgstr "" #: i2p2www/pages/site/docs/transport/ntcp.html:285 #: i2p2www/pages/site/docs/transport/ntcp.html:376 -#: i2p2www/pages/site/docs/transport/ntcp.html:457 +#: i2p2www/pages/site/docs/transport/ntcp.html:466 msgid "Encrypted Contents:" msgstr "" @@ -15845,7 +15914,7 @@ msgid "Alice's 387+ byte `RouterIdentity`" msgstr "" #: i2p2www/pages/site/docs/transport/ntcp.html:366 -#: i2p2www/pages/site/docs/transport/ntcp.html:452 +#: i2p2www/pages/site/docs/transport/ntcp.html:461 msgid "0-15 bytes random data" msgstr "" @@ -15866,31 +15935,31 @@ msgid "" "of message #1) as the IV" msgstr "" -#: i2p2www/pages/site/docs/transport/ntcp.html:399 +#: i2p2www/pages/site/docs/transport/ntcp.html:400 msgid "Bob verifies the signature, and on failure, drops the connection." msgstr "" -#: i2p2www/pages/site/docs/transport/ntcp.html:402 +#: i2p2www/pages/site/docs/transport/ntcp.html:403 msgid "" "Bob may drop the connection if the clock skew with Alice is too high as " "calculated using tsA." msgstr "" -#: i2p2www/pages/site/docs/transport/ntcp.html:405 +#: 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 "" -#: i2p2www/pages/site/docs/transport/ntcp.html:421 +#: i2p2www/pages/site/docs/transport/ntcp.html:430 msgid "Message 4 (Session Confirm B)" msgstr "" -#: i2p2www/pages/site/docs/transport/ntcp.html:422 +#: i2p2www/pages/site/docs/transport/ntcp.html:431 msgid "This is a signature of the critical data. Bob sends Alice:" msgstr "" -#: i2p2www/pages/site/docs/transport/ntcp.html:446 +#: i2p2www/pages/site/docs/transport/ntcp.html:455 msgid "" "the `Signature` of the following concatenated data:\n" " X, Y, Alice's `RouterIdentity`, tsA, tsB.\n" @@ -15898,7 +15967,7 @@ msgid "" "the `SigningPublicKey` in his `RouterIdentity`" msgstr "" -#: i2p2www/pages/site/docs/transport/ntcp.html:470 +#: i2p2www/pages/site/docs/transport/ntcp.html:479 #, python-format msgid "" "Data AES encrypted using the DH " @@ -15909,21 +15978,21 @@ msgid "" "signature types" msgstr "" -#: i2p2www/pages/site/docs/transport/ntcp.html:479 +#: i2p2www/pages/site/docs/transport/ntcp.html:488 msgid "Alice verifies the signature, and on failure, drops the connection." msgstr "" -#: i2p2www/pages/site/docs/transport/ntcp.html:482 +#: 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 "" -#: i2p2www/pages/site/docs/transport/ntcp.html:497 +#: i2p2www/pages/site/docs/transport/ntcp.html:506 msgid "After Establishment" msgstr "" -#: i2p2www/pages/site/docs/transport/ntcp.html:498 +#: i2p2www/pages/site/docs/transport/ntcp.html:507 msgid "" "The connection is established, and standard or time sync messages may be " "exchanged.\n" @@ -15935,11 +16004,11 @@ msgid "" " the next IV." msgstr "" -#: i2p2www/pages/site/docs/transport/ntcp.html:507 +#: i2p2www/pages/site/docs/transport/ntcp.html:516 msgid "Check Connection Message" msgstr "" -#: i2p2www/pages/site/docs/transport/ntcp.html:508 +#: i2p2www/pages/site/docs/transport/ntcp.html:517 msgid "" "Alternately, when Bob receives a connection, it could be a\n" "check connection (perhaps prompted by Bob asking for someone\n" @@ -15949,58 +16018,58 @@ msgid "" "A check info connection will receive 256 bytes containing:" msgstr "" -#: i2p2www/pages/site/docs/transport/ntcp.html:517 +#: i2p2www/pages/site/docs/transport/ntcp.html:526 msgid "32 bytes of uninterpreted, ignored data" msgstr "" -#: i2p2www/pages/site/docs/transport/ntcp.html:518 +#: i2p2www/pages/site/docs/transport/ntcp.html:527 msgid "1 byte size" msgstr "" -#: i2p2www/pages/site/docs/transport/ntcp.html:519 +#: 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 "" -#: i2p2www/pages/site/docs/transport/ntcp.html:520 +#: i2p2www/pages/site/docs/transport/ntcp.html:529 msgid "2 byte port number that the local router was reached on" msgstr "" -#: i2p2www/pages/site/docs/transport/ntcp.html:521 +#: i2p2www/pages/site/docs/transport/ntcp.html:530 msgid "" "4 byte i2p network time as known by the remote side (seconds since the " "epoch)" msgstr "" -#: i2p2www/pages/site/docs/transport/ntcp.html:522 +#: i2p2www/pages/site/docs/transport/ntcp.html:531 msgid "uninterpreted padding data, up to byte 223" msgstr "" -#: i2p2www/pages/site/docs/transport/ntcp.html:523 +#: 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 "" -#: i2p2www/pages/site/docs/transport/ntcp.html:526 +#: i2p2www/pages/site/docs/transport/ntcp.html:535 msgid "Check connection is completely disabled as of release 0.9.12." msgstr "" -#: i2p2www/pages/site/docs/transport/ntcp.html:530 +#: i2p2www/pages/site/docs/transport/ntcp.html:539 msgid "Discussion" msgstr "" -#: i2p2www/pages/site/docs/transport/ntcp.html:531 +#: i2p2www/pages/site/docs/transport/ntcp.html:540 #, python-format msgid "Now on the NTCP Discussion Page." msgstr "" -#: i2p2www/pages/site/docs/transport/ntcp.html:537 +#: i2p2www/pages/site/docs/transport/ntcp.html:546 msgid "The maximum message size should be increased to approximately 32 KB." msgstr "" -#: i2p2www/pages/site/docs/transport/ntcp.html:541 +#: 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" @@ -16011,13 +16080,13 @@ msgid "" "to create a limited number of message sizes." msgstr "" -#: i2p2www/pages/site/docs/transport/ntcp.html:549 +#: 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 "" -#: i2p2www/pages/site/docs/transport/ntcp.html:553 +#: 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?" diff --git a/i2p2www/translations/he/LC_MESSAGES/get-involved.po b/i2p2www/translations/he/LC_MESSAGES/get-involved.po index d404ef6e..ff63377d 100644 --- a/i2p2www/translations/he/LC_MESSAGES/get-involved.po +++ b/i2p2www/translations/he/LC_MESSAGES/get-involved.po @@ -8,7 +8,7 @@ msgid "" msgstr "" "Project-Id-Version: I2P website\n" "Report-Msgid-Bugs-To: http://trac.i2p2.de\n" -"POT-Creation-Date: 2014-10-22 20:13+0000\n" +"POT-Creation-Date: 2014-11-27 12:12+0000\n" "PO-Revision-Date: 2014-02-09 19:53+0000\n" "Last-Translator: FULL NAME \n" "Language-Team: he \n" @@ -397,317 +397,52 @@ msgid "" msgstr "" #: i2p2www/pages/site/get-involved/todo.html:15 -#: i2p2www/pages/site/get-involved/todo.html:53 +#: i2p2www/pages/site/get-involved/todo.html:38 msgid "Core functionality" msgstr "" #: i2p2www/pages/site/get-involved/todo.html:15 -#: i2p2www/pages/site/get-involved/todo.html:27 -#: i2p2www/pages/site/get-involved/todo.html:51 +#: i2p2www/pages/site/get-involved/todo.html:21 +#: i2p2www/pages/site/get-involved/todo.html:36 msgid "link" msgstr "" #: i2p2www/pages/site/get-involved/todo.html:17 -#: i2p2www/pages/site/get-involved/todo.html:56 -msgid "NAT/Firewall bridging via 1-hop restricted routes" -msgstr "" - -#: i2p2www/pages/site/get-involved/todo.html:20 -#: i2p2www/pages/site/get-involved/todo.html:129 -msgid "High degree transport layer with UDP, NBIO, or NIO" -msgstr "" - -#: i2p2www/pages/site/get-involved/todo.html:23 -#: i2p2www/pages/site/get-involved/todo.html:217 +#: i2p2www/pages/site/get-involved/todo.html:41 msgid "NetworkDB and profile tuning and ejection policy for large nets" msgstr "" -#: i2p2www/pages/site/get-involved/todo.html:27 -#: i2p2www/pages/site/get-involved/todo.html:241 +#: i2p2www/pages/site/get-involved/todo.html:21 +#: i2p2www/pages/site/get-involved/todo.html:65 msgid "Security / anonymity" msgstr "" -#: i2p2www/pages/site/get-involved/todo.html:29 -#: i2p2www/pages/site/get-involved/todo.html:244 -msgid "" -"Per-hop tunnel id & new permuted TunnelVerificationStructure " -"encryption" -msgstr "" - -#: i2p2www/pages/site/get-involved/todo.html:32 -#: i2p2www/pages/site/get-involved/todo.html:294 -msgid "Strict ordering of participants within tunnels" -msgstr "" - -#: i2p2www/pages/site/get-involved/todo.html:35 -msgid "Randomly permuted tunnel lengths" -msgstr "" - -#: i2p2www/pages/site/get-involved/todo.html:38 -#: i2p2www/pages/site/get-involved/todo.html:356 +#: 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 "" -#: i2p2www/pages/site/get-involved/todo.html:41 -#: i2p2www/pages/site/get-involved/todo.html:375 +#: 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 "" -#: i2p2www/pages/site/get-involved/todo.html:44 -#: i2p2www/pages/site/get-involved/todo.html:404 +#: 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 "" -#: i2p2www/pages/site/get-involved/todo.html:47 -#: i2p2www/pages/site/get-involved/todo.html:441 +#: i2p2www/pages/site/get-involved/todo.html:32 +#: i2p2www/pages/site/get-involved/todo.html:153 msgid "Stop & go mix w/ garlics & tunnels" msgstr "" -#: i2p2www/pages/site/get-involved/todo.html:51 -#: i2p2www/pages/site/get-involved/todo.html:455 +#: i2p2www/pages/site/get-involved/todo.html:36 +#: i2p2www/pages/site/get-involved/todo.html:167 msgid "Performance" msgstr "" -#: i2p2www/pages/site/get-involved/todo.html:61 -msgid "Implemented in I2P 0.6.0.6" -msgstr "" - -#: i2p2www/pages/site/get-involved/todo.html:62 -msgid "" -"The functionality of allowing routers to fully participate within the " -"network \n" -"while behind firewalls and NATs that they do not control requires some " -"basic \n" -"restricted route operation (since those peers will not be able to receive" -" \n" -"inbound connections). To do this successfully, you consider peers one of" -" \n" -"two ways:" -msgstr "" - -#: i2p2www/pages/site/get-involved/todo.html:72 -msgid "" -"Peers who have reachable interfaces - these peers do not need to \n" -"do anything special" -msgstr "" - -#: i2p2www/pages/site/get-involved/todo.html:76 -msgid "" -"Peers who do not have reachable interfaces - these peers must " -"build \n" -"a tunnel pointing at them where the gateway is one of the peers they have" -" \n" -"established a connection with who has both a publicly reachable interface" -" \n" -"and who has agreed to serve as their 'introducer'." -msgstr "" - -#: i2p2www/pages/site/get-involved/todo.html:84 -msgid "" -"To do this, peers who have no IP address simply connect to a few peers, \n" -"build a tunnel through them, and publish a reference to those tunnels " -"within \n" -"their RouterInfo structure in the network database." -msgstr "" - -#: i2p2www/pages/site/get-involved/todo.html:89 -msgid "" -"When someone wants to contact any particular router, they first must get" -" \n" -"its RouterInfo from the network database, which will tell them whether " -"they \n" -"can connect directly (e.g. the peer has a publicly reachable interface) \n" -"or whether they need to contact them indirectly. Direct connections occur" -" \n" -"as normal, while indirect connections are done through one of the " -"published \n" -"tunnels." -msgstr "" - -#: i2p2www/pages/site/get-involved/todo.html:97 -msgid "" -"When a router just wants to get a message or two to a specific hidden " -"peer, \n" -"they can just use the indirect tunnel for sending the payload. However, \n" -"if the router wants to talk to the hidden peer often (for instance, as " -"part \n" -"of a tunnel), they will send a garlic routed message through the indirect" -" \n" -"tunnel to that hidden peer which unwraps to contain a message which " -"should \n" -"be sent to the originating router. That hidden peer then establishes an \n" -"outbound connection to the originating router and from then on, those two" -" \n" -"routers can talk to each other directly over that newly established " -"direct \n" -"connection." -msgstr "" - -#: i2p2www/pages/site/get-involved/todo.html:108 -msgid "" -"Of course, that only works if the originating peer can receive " -"connections \n" -"(they aren't also hidden). However, if the originating peer is hidden, " -"they \n" -"can simply direct the garlic routed message to come back to the " -"originating \n" -"peer's inbound tunnel." -msgstr "" - -#: i2p2www/pages/site/get-involved/todo.html:114 -msgid "" -"This is not meant to provide a way for a peer's IP address to be " -"concealed, \n" -"merely as a way to let people behind firewalls and NATs fully operate " -"within \n" -"the network. Concealing the peer's IP address adds a little more work, as" -" \n" -"described below." -msgstr "" - -#: i2p2www/pages/site/get-involved/todo.html:120 -msgid "" -"With this technique, any router can participate as any part of a tunnel." -" \n" -"For efficiency purposes, a hidden peer would be a bad choice for an " -"inbound \n" -"gateway, and within any given tunnel, two neighboring peers wouldn't want" -" \n" -"to be hidden. But that is not technically necessary." -msgstr "" - -#: i2p2www/pages/site/get-involved/todo.html:132 -msgid "Both UDP and NIO have been Implemented in I2P" -msgstr "" - -#: i2p2www/pages/site/get-involved/todo.html:133 -msgid "" -"Standard TCP communication in Java generally requires blocking socket \n" -"calls, and to keep a blocked socket from hanging the entire system, those" -" \n" -"blocking calls are done on their own threads. Our current TCP transport \n" -"is implemented in a naive fashion - for each peer we are talking to, we \n" -"have one thread reading and one thread writing. The reader thread simply" -" \n" -"loops a bunch of read() calls, building I2NP messages and adding them \n" -"to our internal inbound message queue, and the writer thread pulls " -"messages \n" -"off a per-connection outbound message queue and shoves the data through \n" -"write() calls." -msgstr "" - -#: i2p2www/pages/site/get-involved/todo.html:144 -msgid "" -"We do this fairly efficiently, from a CPU perspective - at any time, \n" -"almost all of these threads are sitting idle, blocked waiting for " -"something \n" -"to do. However, each thread consumes real resources (on older Linux " -"kernels, \n" -"for instance, each thread would often be implemented as a fork()'ed " -"process). \n" -"As the network grows, the number of peers each router will want to talk \n" -"with will increase (remember, I2P is fully connected, meaning that any \n" -"given peer should know how to get a message to any other peer, and " -"restricted \n" -"route support will probably not significantly reduce the number of " -"connections \n" -"necessary). This means that with a 100,000 router network, each router \n" -"will have up to 199,998 threads just to deal with the TCP connections!" -msgstr "" - -#: i2p2www/pages/site/get-involved/todo.html:156 -msgid "" -"Obviously, that just won't work. We need to use a transport layer that \n" -"can scale. In Java, we have two main camps:" -msgstr "" - -#: i2p2www/pages/site/get-involved/todo.html:161 -#, python-format -msgid "" -"Implemented in I2P 0.6 (\"SSU\") as documented elsewhere" -msgstr "" - -#: i2p2www/pages/site/get-involved/todo.html:164 -msgid "" -"Sending and receiving UDP datagrams is a connectionless operation - if \n" -"we are communicating with 100,000 peers, we simply stick the UDP packets" -" \n" -"in a queue and have a single thread pulling them off the queue and " -"shoving \n" -"them out the pipe (and to receive, have a single thread pulling in any \n" -"UDP packets received and adding them to an inbound queue)." -msgstr "" - -#: i2p2www/pages/site/get-involved/todo.html:171 -msgid "" -"However, moving to UDP means losing the benefits of TCP's ordering, " -"congestion \n" -"control, MTU discovery, etc. Implementing that code will take significant" -" \n" -"work, however I2P doesn't need it to be as strong as TCP. Specifically, \n" -"a while ago I was taking some measurements in the simulator and on the \n" -"live net, and the vast majority of messages transferred would fit easily" -" \n" -"within a single unfragmented UDP packet, and the largest of the messages" -" \n" -"would fit within 20-30 packets. As mule pointed out, TCP adds a " -"significant \n" -"overhead when dealing with so many small packets, as the ACKs are within" -" \n" -"an order of magnitude in size. With UDP, we can optimize the transport \n" -"for both efficiency and resilience by taking into account I2P's " -"particular \n" -"needs." -msgstr "" - -#: i2p2www/pages/site/get-involved/todo.html:184 -msgid "It will be a lot of work though." -msgstr "" - -#: i2p2www/pages/site/get-involved/todo.html:187 -msgid "NIO or NBIO" -msgstr "" - -#: i2p2www/pages/site/get-involved/todo.html:188 -msgid "NIO Implemented in I2P 0.6.1.22 (\"NTCP\")" -msgstr "" - -#: i2p2www/pages/site/get-involved/todo.html:191 -msgid "" -"In Java 1.4, a set of \"New I/O\" packages was introduced, allowing Java" -" \n" -"developers to take advantage of the operating system's nonblocking IO \n" -"capabilities - allowing you to maintain a large number of concurrent IO \n" -"operations without requiring a separate thread for each. There is much \n" -"promise with this approach, as we can scalable handle a large number of \n" -"concurrent connections and we don't have to write a mini-TCP stack with \n" -"UDP. However, the NIO packages have not proven themselves to be battle-" -"ready, \n" -"as the Freenet developer's found. In addition, requiring NIO support " -"would \n" -"mean we can't run on any of the open source JVMs like Kaffe, \n" -"as GNU/Classpath has only " -"limited \n" -"support for NIO. (note: this may not be the case anymore, as there \n" -"has been some progress on Classpath's NIO, but it is an unknown " -"quantity)" -msgstr "" - -#: i2p2www/pages/site/get-involved/todo.html:205 -#, python-format -msgid "" -"Another alternative along the same lines is the Non" -" \n" -"Blocking I/O package - essentially a cleanroom NIO implementation \n" -"(written before NIO was around). It works by using some native OS code \n" -"to do the nonblocking IO, passing off events through Java. It seems to \n" -"be working with Kaffe, though there doesn't seem to be much development \n" -"activity on it lately (likely due to 1.4's NIO deployment)." -msgstr "" - -#: i2p2www/pages/site/get-involved/todo.html:220 +#: i2p2www/pages/site/get-involved/todo.html:44 msgid "" "Within the current network database and profile management " "implementation, \n" @@ -730,152 +465,14 @@ msgid "" "code yet, since we aren't going to need it for a while." msgstr "" -#: i2p2www/pages/site/get-involved/todo.html:235 +#: 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" "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:247 -#: i2p2www/pages/site/get-involved/todo.html:331 -#, python-format -msgid "" -"Addressed in I2P 0.5 as documented elsewhere" -msgstr "" - -#: i2p2www/pages/site/get-involved/todo.html:250 -msgid "" -"Right now, if Alice builds a four hop inbound tunnel starting at Elvis, \n" -"going to Dave, then to Charlie, then Bob, and finally Alice " -"(A<--B<--C<--D<--E), \n" -"all five of them will know they are participating in tunnel \"123\", as \n" -"the messages are tagged as such. What we want to do is give each hop " -"their \n" -"own unique tunnel hop ID - Charlie will receive messages on tunnel 234 \n" -"and forward them to tunnel 876 on Bob. The intent is to prevent Bob or \n" -"Charlie from knowing that they are in Alice's tunnel, as if each hop in \n" -"the tunnel had the same tunnel ID, collusion attacks aren't much work." -msgstr "" - -#: i2p2www/pages/site/get-involved/todo.html:260 -msgid "" -"Adding a unique tunnel ID per hop isn't hard, but by itself, " -"insufficient. \n" -"If Dave and Bob are under the control of the same attacker, they wouldn't" -" \n" -"be able to tell they are in the same tunnel due to the tunnel ID, but \n" -"would be able to tell by the message bodies and verification structures \n" -"by simply comparing them. To prevent that, the tunnel must use layered \n" -"encryption along the path, both on the payload of the tunneled message \n" -"and on the verification structure (used to prevent simple tagging " -"attacks). \n" -"This requires some simple modifications to the TunnelMessage, as well \n" -"as the inclusion of per-hop secret keys delivered during tunnel creation" -" \n" -"and given to the tunnel's gateway. We must fix a maximum tunnel length \n" -"(e.g. 16 hops) and instruct the gateway to encrypt the message to each \n" -"of the 16 delivered secret keys, in reverse order, and to encrypt the \n" -"signature of the hash of the (encrypted) payload at each step. The " -"gateway \n" -"then sends that 16-step encrypted message, along with a 16-step and " -"16-wide \n" -"encrypted mapping to the first hop, which then decrypts the mapping and \n" -"the payload with their secret key, looking in the 16-wide mapping for \n" -"the entry associated with their own hop (keyed by the per-hop tunnel ID)" -" \n" -"and verifying the payload by checking it against the associated signed \n" -"hash." -msgstr "" - -#: i2p2www/pages/site/get-involved/todo.html:281 -msgid "" -"The tunnel gateway does still have more information than the other peers" -" \n" -"in the tunnel, and compromising both the gateway and a tunnel participant" -" \n" -"would allow those peers to collude, exposing the fact that they are both" -" \n" -"in the same tunnel. In addition, neighboring peers know that they are \n" -"in the same tunnel anyway, as they know who they send the message to (and" -" \n" -"with IP-based transports without restricted routes, they know who they \n" -"got it from). However, the above two techniques significantly increase \n" -"the cost of gaining meaningful samples when dealing with longer tunnels." -msgstr "" - -#: i2p2www/pages/site/get-involved/todo.html:297 -msgid "Implemented in release 0.6.2" -msgstr "" - -#: i2p2www/pages/site/get-involved/todo.html:300 -#, python-format -msgid "" -"As Connelly proposed to deal with the\n" -"predecessor attack (2008\n" -"update), keeping the order of peers within our tunnels consistent \n" -"(aka whenever Alice creates a tunnel with both Bob and Charlie in it, \n" -"Bob's next hop is always Charlie), we address the issue as Bob doesn't \n" -"get to substantially sample Alice's peer selection group. We may even \n" -"want to explicitly allow Bob to participate in Alice's tunnels in only \n" -"one way - receiving a message from Dave and sending it to Charlie - and \n" -"if any of those peers are not available to participate in the tunnel (due" -" \n" -"to overload, network disconnection, etc), avoid asking Bob to participate" -" \n" -"in any tunnels until they are back online." -msgstr "" - -#: i2p2www/pages/site/get-involved/todo.html:315 -msgid "" -"More analysis is necessary for revising the tunnel creation - at the \n" -"moment, we simply select and order randomly within the peer's top tier \n" -"of peers (ones with fast + high capacity)." -msgstr "" - -#: i2p2www/pages/site/get-involved/todo.html:320 -msgid "" -"Adding a strict ordering to peers in a tunnel also improves the anonymity" -" \n" -"of peers with 0-hop tunnels, as otherwise the fact that a peer's gateway" -" \n" -"is always the same would be particularly damning. However, peers with \n" -"0-hop tunnels may want to periodically use a 1-hop tunnel to simulate \n" -"the failure of a normally reliable gateway peer (so every MTBF*(tunnel \n" -"duration) minutes, use a 1-hop tunnel)." -msgstr "" - -#: i2p2www/pages/site/get-involved/todo.html:337 -msgid "" -"Without tunnel length permutation, if someone were to somehow detect that" -" \n" -"a destination had a particular number of hops, it might be able to use " -"that \n" -"information to identify the router the destination is located on, per the" -" \n" -"predecessor attack. For instance, if everyone has 2-hop tunnels, if Bob \n" -"receives a tunnel message from Charlie and forwards it to Alice, Bob " -"knows \n" -"Alice is the final router in the tunnel. If Bob were to identify what " -"destination \n" -"that tunnel served (by means of colluding with the gateway and harvesting" -" \n" -"the network database for all of the LeaseSets), he would know the router" -" \n" -"on which that destination is located (and without restricted routes, that" -" \n" -"would mean what IP address the destination is on)." -msgstr "" - -#: i2p2www/pages/site/get-involved/todo.html:349 -msgid "" -"It is to counter user behavior that tunnel lengths should be permuted, \n" -"using algorithms based on the length requested (for example, the 1/MTBF \n" -"length change for 0-hop tunnels outlined above)." -msgstr "" - -#: i2p2www/pages/site/get-involved/todo.html:359 +#: i2p2www/pages/site/get-involved/todo.html:71 msgid "" "The restricted route functionality described before was simply a " "functional \n" @@ -897,7 +494,7 @@ msgid "" "to forward it as requested." msgstr "" -#: i2p2www/pages/site/get-involved/todo.html:378 +#: i2p2www/pages/site/get-involved/todo.html:90 #, python-format msgid "" "Within the network, we will want some way to deter people from consuming" @@ -911,7 +508,7 @@ msgid "" "to make certain requests \"expensive\"." msgstr "" -#: i2p2www/pages/site/get-involved/todo.html:386 +#: 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 " @@ -929,7 +526,7 @@ msgid "" "with few resources." msgstr "" -#: i2p2www/pages/site/get-involved/todo.html:397 +#: 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" @@ -937,7 +534,7 @@ msgid "" "appropriate." msgstr "" -#: i2p2www/pages/site/get-involved/todo.html:407 +#: i2p2www/pages/site/get-involved/todo.html:119 #, python-format msgid "" "To powerful passive external observers as well as large colluding " @@ -958,7 +555,7 @@ msgid "" "tunnel mixing strategies." msgstr "" -#: i2p2www/pages/site/get-involved/todo.html:420 +#: 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" @@ -976,7 +573,7 @@ msgid "" "available." msgstr "" -#: i2p2www/pages/site/get-involved/todo.html:433 +#: i2p2www/pages/site/get-involved/todo.html:145 msgid "" "In addition, we may want to implement code to dynamically reroute tunnels" " \n" @@ -986,7 +583,7 @@ msgid "" "with instructions to redefine the next-hop in the tunnel." msgstr "" -#: i2p2www/pages/site/get-involved/todo.html:444 +#: 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" @@ -1001,7 +598,7 @@ msgid "" "clove exposed includes delay instructions." msgstr "" -#: i2p2www/pages/site/get-involved/todo.html:456 +#: i2p2www/pages/site/get-involved/todo.html:168 #, python-format msgid "" "Performance related improvements are listed on the\n" @@ -4134,3 +3731,15 @@ 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 1685e427..11823dc5 100644 --- a/i2p2www/translations/id/LC_MESSAGES/get-involved.po +++ b/i2p2www/translations/id/LC_MESSAGES/get-involved.po @@ -8,7 +8,7 @@ msgid "" msgstr "" "Project-Id-Version: I2P\n" "Report-Msgid-Bugs-To: http://trac.i2p2.de\n" -"POT-Creation-Date: 2014-10-22 20:13+0000\n" +"POT-Creation-Date: 2014-11-27 12:12+0000\n" "PO-Revision-Date: 2014-10-22 20:24+0000\n" "Last-Translator: str4d \n" "Language-Team: Indonesian " @@ -493,317 +493,52 @@ msgid "" msgstr "" #: i2p2www/pages/site/get-involved/todo.html:15 -#: i2p2www/pages/site/get-involved/todo.html:53 +#: i2p2www/pages/site/get-involved/todo.html:38 msgid "Core functionality" msgstr "" #: i2p2www/pages/site/get-involved/todo.html:15 -#: i2p2www/pages/site/get-involved/todo.html:27 -#: i2p2www/pages/site/get-involved/todo.html:51 +#: i2p2www/pages/site/get-involved/todo.html:21 +#: i2p2www/pages/site/get-involved/todo.html:36 msgid "link" msgstr "" #: i2p2www/pages/site/get-involved/todo.html:17 -#: i2p2www/pages/site/get-involved/todo.html:56 -msgid "NAT/Firewall bridging via 1-hop restricted routes" -msgstr "" - -#: i2p2www/pages/site/get-involved/todo.html:20 -#: i2p2www/pages/site/get-involved/todo.html:129 -msgid "High degree transport layer with UDP, NBIO, or NIO" -msgstr "" - -#: i2p2www/pages/site/get-involved/todo.html:23 -#: i2p2www/pages/site/get-involved/todo.html:217 +#: i2p2www/pages/site/get-involved/todo.html:41 msgid "NetworkDB and profile tuning and ejection policy for large nets" msgstr "" -#: i2p2www/pages/site/get-involved/todo.html:27 -#: i2p2www/pages/site/get-involved/todo.html:241 +#: i2p2www/pages/site/get-involved/todo.html:21 +#: i2p2www/pages/site/get-involved/todo.html:65 msgid "Security / anonymity" msgstr "" -#: i2p2www/pages/site/get-involved/todo.html:29 -#: i2p2www/pages/site/get-involved/todo.html:244 -msgid "" -"Per-hop tunnel id & new permuted TunnelVerificationStructure " -"encryption" -msgstr "" - -#: i2p2www/pages/site/get-involved/todo.html:32 -#: i2p2www/pages/site/get-involved/todo.html:294 -msgid "Strict ordering of participants within tunnels" -msgstr "" - -#: i2p2www/pages/site/get-involved/todo.html:35 -msgid "Randomly permuted tunnel lengths" -msgstr "" - -#: i2p2www/pages/site/get-involved/todo.html:38 -#: i2p2www/pages/site/get-involved/todo.html:356 +#: 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 "" -#: i2p2www/pages/site/get-involved/todo.html:41 -#: i2p2www/pages/site/get-involved/todo.html:375 +#: 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 "" -#: i2p2www/pages/site/get-involved/todo.html:44 -#: i2p2www/pages/site/get-involved/todo.html:404 +#: 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 "" -#: i2p2www/pages/site/get-involved/todo.html:47 -#: i2p2www/pages/site/get-involved/todo.html:441 +#: i2p2www/pages/site/get-involved/todo.html:32 +#: i2p2www/pages/site/get-involved/todo.html:153 msgid "Stop & go mix w/ garlics & tunnels" msgstr "" -#: i2p2www/pages/site/get-involved/todo.html:51 -#: i2p2www/pages/site/get-involved/todo.html:455 +#: i2p2www/pages/site/get-involved/todo.html:36 +#: i2p2www/pages/site/get-involved/todo.html:167 msgid "Performance" msgstr "" -#: i2p2www/pages/site/get-involved/todo.html:61 -msgid "Implemented in I2P 0.6.0.6" -msgstr "" - -#: i2p2www/pages/site/get-involved/todo.html:62 -msgid "" -"The functionality of allowing routers to fully participate within the " -"network \n" -"while behind firewalls and NATs that they do not control requires some " -"basic \n" -"restricted route operation (since those peers will not be able to receive" -" \n" -"inbound connections). To do this successfully, you consider peers one of" -" \n" -"two ways:" -msgstr "" - -#: i2p2www/pages/site/get-involved/todo.html:72 -msgid "" -"Peers who have reachable interfaces - these peers do not need to \n" -"do anything special" -msgstr "" - -#: i2p2www/pages/site/get-involved/todo.html:76 -msgid "" -"Peers who do not have reachable interfaces - these peers must " -"build \n" -"a tunnel pointing at them where the gateway is one of the peers they have" -" \n" -"established a connection with who has both a publicly reachable interface" -" \n" -"and who has agreed to serve as their 'introducer'." -msgstr "" - -#: i2p2www/pages/site/get-involved/todo.html:84 -msgid "" -"To do this, peers who have no IP address simply connect to a few peers, \n" -"build a tunnel through them, and publish a reference to those tunnels " -"within \n" -"their RouterInfo structure in the network database." -msgstr "" - -#: i2p2www/pages/site/get-involved/todo.html:89 -msgid "" -"When someone wants to contact any particular router, they first must get" -" \n" -"its RouterInfo from the network database, which will tell them whether " -"they \n" -"can connect directly (e.g. the peer has a publicly reachable interface) \n" -"or whether they need to contact them indirectly. Direct connections occur" -" \n" -"as normal, while indirect connections are done through one of the " -"published \n" -"tunnels." -msgstr "" - -#: i2p2www/pages/site/get-involved/todo.html:97 -msgid "" -"When a router just wants to get a message or two to a specific hidden " -"peer, \n" -"they can just use the indirect tunnel for sending the payload. However, \n" -"if the router wants to talk to the hidden peer often (for instance, as " -"part \n" -"of a tunnel), they will send a garlic routed message through the indirect" -" \n" -"tunnel to that hidden peer which unwraps to contain a message which " -"should \n" -"be sent to the originating router. That hidden peer then establishes an \n" -"outbound connection to the originating router and from then on, those two" -" \n" -"routers can talk to each other directly over that newly established " -"direct \n" -"connection." -msgstr "" - -#: i2p2www/pages/site/get-involved/todo.html:108 -msgid "" -"Of course, that only works if the originating peer can receive " -"connections \n" -"(they aren't also hidden). However, if the originating peer is hidden, " -"they \n" -"can simply direct the garlic routed message to come back to the " -"originating \n" -"peer's inbound tunnel." -msgstr "" - -#: i2p2www/pages/site/get-involved/todo.html:114 -msgid "" -"This is not meant to provide a way for a peer's IP address to be " -"concealed, \n" -"merely as a way to let people behind firewalls and NATs fully operate " -"within \n" -"the network. Concealing the peer's IP address adds a little more work, as" -" \n" -"described below." -msgstr "" - -#: i2p2www/pages/site/get-involved/todo.html:120 -msgid "" -"With this technique, any router can participate as any part of a tunnel." -" \n" -"For efficiency purposes, a hidden peer would be a bad choice for an " -"inbound \n" -"gateway, and within any given tunnel, two neighboring peers wouldn't want" -" \n" -"to be hidden. But that is not technically necessary." -msgstr "" - -#: i2p2www/pages/site/get-involved/todo.html:132 -msgid "Both UDP and NIO have been Implemented in I2P" -msgstr "" - -#: i2p2www/pages/site/get-involved/todo.html:133 -msgid "" -"Standard TCP communication in Java generally requires blocking socket \n" -"calls, and to keep a blocked socket from hanging the entire system, those" -" \n" -"blocking calls are done on their own threads. Our current TCP transport \n" -"is implemented in a naive fashion - for each peer we are talking to, we \n" -"have one thread reading and one thread writing. The reader thread simply" -" \n" -"loops a bunch of read() calls, building I2NP messages and adding them \n" -"to our internal inbound message queue, and the writer thread pulls " -"messages \n" -"off a per-connection outbound message queue and shoves the data through \n" -"write() calls." -msgstr "" - -#: i2p2www/pages/site/get-involved/todo.html:144 -msgid "" -"We do this fairly efficiently, from a CPU perspective - at any time, \n" -"almost all of these threads are sitting idle, blocked waiting for " -"something \n" -"to do. However, each thread consumes real resources (on older Linux " -"kernels, \n" -"for instance, each thread would often be implemented as a fork()'ed " -"process). \n" -"As the network grows, the number of peers each router will want to talk \n" -"with will increase (remember, I2P is fully connected, meaning that any \n" -"given peer should know how to get a message to any other peer, and " -"restricted \n" -"route support will probably not significantly reduce the number of " -"connections \n" -"necessary). This means that with a 100,000 router network, each router \n" -"will have up to 199,998 threads just to deal with the TCP connections!" -msgstr "" - -#: i2p2www/pages/site/get-involved/todo.html:156 -msgid "" -"Obviously, that just won't work. We need to use a transport layer that \n" -"can scale. In Java, we have two main camps:" -msgstr "" - -#: i2p2www/pages/site/get-involved/todo.html:161 -#, python-format -msgid "" -"Implemented in I2P 0.6 (\"SSU\") as documented elsewhere" -msgstr "" - -#: i2p2www/pages/site/get-involved/todo.html:164 -msgid "" -"Sending and receiving UDP datagrams is a connectionless operation - if \n" -"we are communicating with 100,000 peers, we simply stick the UDP packets" -" \n" -"in a queue and have a single thread pulling them off the queue and " -"shoving \n" -"them out the pipe (and to receive, have a single thread pulling in any \n" -"UDP packets received and adding them to an inbound queue)." -msgstr "" - -#: i2p2www/pages/site/get-involved/todo.html:171 -msgid "" -"However, moving to UDP means losing the benefits of TCP's ordering, " -"congestion \n" -"control, MTU discovery, etc. Implementing that code will take significant" -" \n" -"work, however I2P doesn't need it to be as strong as TCP. Specifically, \n" -"a while ago I was taking some measurements in the simulator and on the \n" -"live net, and the vast majority of messages transferred would fit easily" -" \n" -"within a single unfragmented UDP packet, and the largest of the messages" -" \n" -"would fit within 20-30 packets. As mule pointed out, TCP adds a " -"significant \n" -"overhead when dealing with so many small packets, as the ACKs are within" -" \n" -"an order of magnitude in size. With UDP, we can optimize the transport \n" -"for both efficiency and resilience by taking into account I2P's " -"particular \n" -"needs." -msgstr "" - -#: i2p2www/pages/site/get-involved/todo.html:184 -msgid "It will be a lot of work though." -msgstr "" - -#: i2p2www/pages/site/get-involved/todo.html:187 -msgid "NIO or NBIO" -msgstr "" - -#: i2p2www/pages/site/get-involved/todo.html:188 -msgid "NIO Implemented in I2P 0.6.1.22 (\"NTCP\")" -msgstr "" - -#: i2p2www/pages/site/get-involved/todo.html:191 -msgid "" -"In Java 1.4, a set of \"New I/O\" packages was introduced, allowing Java" -" \n" -"developers to take advantage of the operating system's nonblocking IO \n" -"capabilities - allowing you to maintain a large number of concurrent IO \n" -"operations without requiring a separate thread for each. There is much \n" -"promise with this approach, as we can scalable handle a large number of \n" -"concurrent connections and we don't have to write a mini-TCP stack with \n" -"UDP. However, the NIO packages have not proven themselves to be battle-" -"ready, \n" -"as the Freenet developer's found. In addition, requiring NIO support " -"would \n" -"mean we can't run on any of the open source JVMs like Kaffe, \n" -"as GNU/Classpath has only " -"limited \n" -"support for NIO. (note: this may not be the case anymore, as there \n" -"has been some progress on Classpath's NIO, but it is an unknown " -"quantity)" -msgstr "" - -#: i2p2www/pages/site/get-involved/todo.html:205 -#, python-format -msgid "" -"Another alternative along the same lines is the Non" -" \n" -"Blocking I/O package - essentially a cleanroom NIO implementation \n" -"(written before NIO was around). It works by using some native OS code \n" -"to do the nonblocking IO, passing off events through Java. It seems to \n" -"be working with Kaffe, though there doesn't seem to be much development \n" -"activity on it lately (likely due to 1.4's NIO deployment)." -msgstr "" - -#: i2p2www/pages/site/get-involved/todo.html:220 +#: i2p2www/pages/site/get-involved/todo.html:44 msgid "" "Within the current network database and profile management " "implementation, \n" @@ -826,152 +561,14 @@ msgid "" "code yet, since we aren't going to need it for a while." msgstr "" -#: i2p2www/pages/site/get-involved/todo.html:235 +#: 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" "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:247 -#: i2p2www/pages/site/get-involved/todo.html:331 -#, python-format -msgid "" -"Addressed in I2P 0.5 as documented elsewhere" -msgstr "" - -#: i2p2www/pages/site/get-involved/todo.html:250 -msgid "" -"Right now, if Alice builds a four hop inbound tunnel starting at Elvis, \n" -"going to Dave, then to Charlie, then Bob, and finally Alice " -"(A<--B<--C<--D<--E), \n" -"all five of them will know they are participating in tunnel \"123\", as \n" -"the messages are tagged as such. What we want to do is give each hop " -"their \n" -"own unique tunnel hop ID - Charlie will receive messages on tunnel 234 \n" -"and forward them to tunnel 876 on Bob. The intent is to prevent Bob or \n" -"Charlie from knowing that they are in Alice's tunnel, as if each hop in \n" -"the tunnel had the same tunnel ID, collusion attacks aren't much work." -msgstr "" - -#: i2p2www/pages/site/get-involved/todo.html:260 -msgid "" -"Adding a unique tunnel ID per hop isn't hard, but by itself, " -"insufficient. \n" -"If Dave and Bob are under the control of the same attacker, they wouldn't" -" \n" -"be able to tell they are in the same tunnel due to the tunnel ID, but \n" -"would be able to tell by the message bodies and verification structures \n" -"by simply comparing them. To prevent that, the tunnel must use layered \n" -"encryption along the path, both on the payload of the tunneled message \n" -"and on the verification structure (used to prevent simple tagging " -"attacks). \n" -"This requires some simple modifications to the TunnelMessage, as well \n" -"as the inclusion of per-hop secret keys delivered during tunnel creation" -" \n" -"and given to the tunnel's gateway. We must fix a maximum tunnel length \n" -"(e.g. 16 hops) and instruct the gateway to encrypt the message to each \n" -"of the 16 delivered secret keys, in reverse order, and to encrypt the \n" -"signature of the hash of the (encrypted) payload at each step. The " -"gateway \n" -"then sends that 16-step encrypted message, along with a 16-step and " -"16-wide \n" -"encrypted mapping to the first hop, which then decrypts the mapping and \n" -"the payload with their secret key, looking in the 16-wide mapping for \n" -"the entry associated with their own hop (keyed by the per-hop tunnel ID)" -" \n" -"and verifying the payload by checking it against the associated signed \n" -"hash." -msgstr "" - -#: i2p2www/pages/site/get-involved/todo.html:281 -msgid "" -"The tunnel gateway does still have more information than the other peers" -" \n" -"in the tunnel, and compromising both the gateway and a tunnel participant" -" \n" -"would allow those peers to collude, exposing the fact that they are both" -" \n" -"in the same tunnel. In addition, neighboring peers know that they are \n" -"in the same tunnel anyway, as they know who they send the message to (and" -" \n" -"with IP-based transports without restricted routes, they know who they \n" -"got it from). However, the above two techniques significantly increase \n" -"the cost of gaining meaningful samples when dealing with longer tunnels." -msgstr "" - -#: i2p2www/pages/site/get-involved/todo.html:297 -msgid "Implemented in release 0.6.2" -msgstr "" - -#: i2p2www/pages/site/get-involved/todo.html:300 -#, python-format -msgid "" -"As Connelly proposed to deal with the\n" -"predecessor attack (2008\n" -"update), keeping the order of peers within our tunnels consistent \n" -"(aka whenever Alice creates a tunnel with both Bob and Charlie in it, \n" -"Bob's next hop is always Charlie), we address the issue as Bob doesn't \n" -"get to substantially sample Alice's peer selection group. We may even \n" -"want to explicitly allow Bob to participate in Alice's tunnels in only \n" -"one way - receiving a message from Dave and sending it to Charlie - and \n" -"if any of those peers are not available to participate in the tunnel (due" -" \n" -"to overload, network disconnection, etc), avoid asking Bob to participate" -" \n" -"in any tunnels until they are back online." -msgstr "" - -#: i2p2www/pages/site/get-involved/todo.html:315 -msgid "" -"More analysis is necessary for revising the tunnel creation - at the \n" -"moment, we simply select and order randomly within the peer's top tier \n" -"of peers (ones with fast + high capacity)." -msgstr "" - -#: i2p2www/pages/site/get-involved/todo.html:320 -msgid "" -"Adding a strict ordering to peers in a tunnel also improves the anonymity" -" \n" -"of peers with 0-hop tunnels, as otherwise the fact that a peer's gateway" -" \n" -"is always the same would be particularly damning. However, peers with \n" -"0-hop tunnels may want to periodically use a 1-hop tunnel to simulate \n" -"the failure of a normally reliable gateway peer (so every MTBF*(tunnel \n" -"duration) minutes, use a 1-hop tunnel)." -msgstr "" - -#: i2p2www/pages/site/get-involved/todo.html:337 -msgid "" -"Without tunnel length permutation, if someone were to somehow detect that" -" \n" -"a destination had a particular number of hops, it might be able to use " -"that \n" -"information to identify the router the destination is located on, per the" -" \n" -"predecessor attack. For instance, if everyone has 2-hop tunnels, if Bob \n" -"receives a tunnel message from Charlie and forwards it to Alice, Bob " -"knows \n" -"Alice is the final router in the tunnel. If Bob were to identify what " -"destination \n" -"that tunnel served (by means of colluding with the gateway and harvesting" -" \n" -"the network database for all of the LeaseSets), he would know the router" -" \n" -"on which that destination is located (and without restricted routes, that" -" \n" -"would mean what IP address the destination is on)." -msgstr "" - -#: i2p2www/pages/site/get-involved/todo.html:349 -msgid "" -"It is to counter user behavior that tunnel lengths should be permuted, \n" -"using algorithms based on the length requested (for example, the 1/MTBF \n" -"length change for 0-hop tunnels outlined above)." -msgstr "" - -#: i2p2www/pages/site/get-involved/todo.html:359 +#: i2p2www/pages/site/get-involved/todo.html:71 msgid "" "The restricted route functionality described before was simply a " "functional \n" @@ -993,7 +590,7 @@ msgid "" "to forward it as requested." msgstr "" -#: i2p2www/pages/site/get-involved/todo.html:378 +#: i2p2www/pages/site/get-involved/todo.html:90 #, python-format msgid "" "Within the network, we will want some way to deter people from consuming" @@ -1007,7 +604,7 @@ msgid "" "to make certain requests \"expensive\"." msgstr "" -#: i2p2www/pages/site/get-involved/todo.html:386 +#: 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 " @@ -1025,7 +622,7 @@ msgid "" "with few resources." msgstr "" -#: i2p2www/pages/site/get-involved/todo.html:397 +#: 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" @@ -1033,7 +630,7 @@ msgid "" "appropriate." msgstr "" -#: i2p2www/pages/site/get-involved/todo.html:407 +#: i2p2www/pages/site/get-involved/todo.html:119 #, python-format msgid "" "To powerful passive external observers as well as large colluding " @@ -1054,7 +651,7 @@ msgid "" "tunnel mixing strategies." msgstr "" -#: i2p2www/pages/site/get-involved/todo.html:420 +#: 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" @@ -1072,7 +669,7 @@ msgid "" "available." msgstr "" -#: i2p2www/pages/site/get-involved/todo.html:433 +#: i2p2www/pages/site/get-involved/todo.html:145 msgid "" "In addition, we may want to implement code to dynamically reroute tunnels" " \n" @@ -1082,7 +679,7 @@ msgid "" "with instructions to redefine the next-hop in the tunnel." msgstr "" -#: i2p2www/pages/site/get-involved/todo.html:444 +#: 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" @@ -1097,7 +694,7 @@ msgid "" "clove exposed includes delay instructions." msgstr "" -#: i2p2www/pages/site/get-involved/todo.html:456 +#: i2p2www/pages/site/get-involved/todo.html:168 #, python-format msgid "" "Performance related improvements are listed on the\n" @@ -4230,3 +3827,15 @@ msgid "" "href=\"http://%(zzz)s/forums/14\">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 ca012fa7..c7b1b6c3 100644 --- a/i2p2www/translations/it/LC_MESSAGES/docs.po +++ b/i2p2www/translations/it/LC_MESSAGES/docs.po @@ -9,7 +9,7 @@ msgid "" msgstr "" "Project-Id-Version: I2P\n" "Report-Msgid-Bugs-To: http://trac.i2p2.de\n" -"POT-Creation-Date: 2014-11-16 02:59+0000\n" +"POT-Creation-Date: 2014-11-27 12:12+0000\n" "PO-Revision-Date: 2014-11-16 03:02+0000\n" "Last-Translator: str4d \n" "Language-Team: Italian " @@ -28,7 +28,9 @@ msgstr "" #: i2p2www/pages/site/docs/applications/embedding.html:3 #: i2p2www/pages/site/docs/how/cryptography.html:3 #: i2p2www/pages/site/docs/protocol/i2cp.html:3 +#: i2p2www/pages/site/docs/spec/configuration.html:3 #: i2p2www/pages/site/docs/spec/updates.html:3 +#: i2p2www/pages/site/docs/transport/ntcp.html:3 msgid "November 2014" msgstr "" @@ -133,7 +135,7 @@ msgstr "" msgid "Managed Clients" msgstr "" -#: i2p2www/pages/site/docs/index.html:44 i2p2www/pages/site/docs/index.html:217 +#: i2p2www/pages/site/docs/index.html:44 i2p2www/pages/site/docs/index.html:222 msgid "Embedding the router in your application" msgstr "" @@ -150,7 +152,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:189 +#: i2p2www/pages/site/docs/index.html:48 i2p2www/pages/site/docs/index.html:194 msgid "Configuration File Format" msgstr "Formato del File di Configurazione" @@ -168,369 +170,379 @@ msgstr "" msgid "Application Development Overview and Guide" msgstr "Guide e panoramica delle sviluppo dell'applicazione" -#: i2p2www/pages/site/docs/index.html:72 +#: i2p2www/pages/site/docs/index.html:58 +#: i2p2www/pages/site/docs/api/i2ptunnel.html:55 +msgid "I2PTunnel Configuration" +msgstr "" + +#: i2p2www/pages/site/docs/index.html:74 msgid "SAM Protocol" msgstr "Protocollo SAM" -#: i2p2www/pages/site/docs/index.html:74 +#: i2p2www/pages/site/docs/index.html:76 msgid "SAMv2 Protocol" msgstr "Protocollo SAMv2" -#: i2p2www/pages/site/docs/index.html:76 +#: i2p2www/pages/site/docs/index.html:78 msgid "SAMv3 Protocol" msgstr "Protocollo SAMv3" -#: i2p2www/pages/site/docs/index.html:78 +#: i2p2www/pages/site/docs/index.html:80 msgid "BOB Protocol" msgstr "Protocollo BOB" -#: i2p2www/pages/site/docs/index.html:81 +#: i2p2www/pages/site/docs/index.html:83 msgid "End-to-End Transport API and Protocols" msgstr "API e protocolli di trasporto End-to-End" -#: i2p2www/pages/site/docs/index.html:82 +#: i2p2www/pages/site/docs/index.html:84 msgid "" "The end-to-end protocols used by clients for reliable and unreliable " "communication." msgstr "" -#: i2p2www/pages/site/docs/index.html:84 +#: i2p2www/pages/site/docs/index.html:86 #: i2p2www/pages/site/docs/api/streaming.html:2 msgid "Streaming Library" msgstr "" -#: i2p2www/pages/site/docs/index.html:86 +#: i2p2www/pages/site/docs/index.html:88 msgid "Streaming Protocol Specification" msgstr "" -#: i2p2www/pages/site/docs/index.html:88 +#: i2p2www/pages/site/docs/index.html:90 msgid "Streaming Javadoc" msgstr "" -#: i2p2www/pages/site/docs/index.html:90 +#: i2p2www/pages/site/docs/index.html:92 #: i2p2www/pages/site/docs/api/datagrams.html:2 msgid "Datagrams" msgstr "" -#: i2p2www/pages/site/docs/index.html:92 +#: i2p2www/pages/site/docs/index.html:94 msgid "Datagram Javadoc" msgstr "" -#: i2p2www/pages/site/docs/index.html:95 +#: i2p2www/pages/site/docs/index.html:97 msgid "Client-to-Router Interface API and Protocol" msgstr "" -#: i2p2www/pages/site/docs/index.html:96 +#: 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" "Traditionally used only by Java applications and higher-level APIs." msgstr "" -#: i2p2www/pages/site/docs/index.html:101 +#: i2p2www/pages/site/docs/index.html:103 msgid "I2CP - I2P Control Protocol / API overview" msgstr "" -#: i2p2www/pages/site/docs/index.html:103 +#: i2p2www/pages/site/docs/index.html:105 msgid "I2CP Specification" msgstr "" -#: i2p2www/pages/site/docs/index.html:105 +#: i2p2www/pages/site/docs/index.html:107 msgid "I2CP API Javadoc" msgstr "" -#: i2p2www/pages/site/docs/index.html:107 -#: i2p2www/pages/site/docs/index.html:136 +#: i2p2www/pages/site/docs/index.html:109 +#: i2p2www/pages/site/docs/index.html:139 msgid "Common data structures specification" msgstr "" -#: i2p2www/pages/site/docs/index.html:109 -#: i2p2www/pages/site/docs/index.html:138 +#: i2p2www/pages/site/docs/index.html:111 +#: i2p2www/pages/site/docs/index.html:141 msgid "Data Structures Javadoc" msgstr "" -#: i2p2www/pages/site/docs/index.html:112 +#: i2p2www/pages/site/docs/index.html:114 msgid "End-to-End Encryption" msgstr "" -#: i2p2www/pages/site/docs/index.html:113 +#: i2p2www/pages/site/docs/index.html:115 msgid "How client messages are end-to-end encrypted by the router." msgstr "" -#: i2p2www/pages/site/docs/index.html:115 +#: i2p2www/pages/site/docs/index.html:117 msgid "ElGamal/AES+SessionTag encryption" msgstr "" -#: i2p2www/pages/site/docs/index.html:116 -#: i2p2www/pages/site/docs/index.html:149 +#: i2p2www/pages/site/docs/index.html:118 +#: i2p2www/pages/site/docs/index.html:152 msgid "ElGamal and AES cryptography details" msgstr "" -#: i2p2www/pages/site/docs/index.html:119 +#: i2p2www/pages/site/docs/index.html:121 #: i2p2www/pages/site/docs/how/tech-intro.html:15 #: i2p2www/pages/site/docs/how/tech-intro.html:329 msgid "Network Database" msgstr "" -#: i2p2www/pages/site/docs/index.html:120 +#: i2p2www/pages/site/docs/index.html:122 msgid "" "Distributed storage and retrieval of information about routers and " "clients." msgstr "" -#: i2p2www/pages/site/docs/index.html:122 +#: i2p2www/pages/site/docs/index.html:124 msgid "Network database overview, details, and threat analysis" msgstr "" -#: i2p2www/pages/site/docs/index.html:123 +#: i2p2www/pages/site/docs/index.html:125 msgid "Cryptographic hashes" msgstr "" -#: i2p2www/pages/site/docs/index.html:124 +#: i2p2www/pages/site/docs/index.html:126 msgid "Cryptographic signatures" msgstr "" #: i2p2www/pages/site/docs/index.html:127 +#: i2p2www/pages/site/docs/index.html:186 +msgid "Router reseed specification" +msgstr "" + +#: i2p2www/pages/site/docs/index.html:130 msgid "Router Message Protocol" msgstr "" -#: i2p2www/pages/site/docs/index.html:128 +#: i2p2www/pages/site/docs/index.html:131 msgid "" "I2P is a message-oriented router. The messages sent between routers are " "defined by the I2NP protocol." msgstr "" -#: i2p2www/pages/site/docs/index.html:130 +#: i2p2www/pages/site/docs/index.html:133 msgid "I2NP - I2P Network Protocol Overview" msgstr "" -#: i2p2www/pages/site/docs/index.html:132 +#: i2p2www/pages/site/docs/index.html:135 msgid "I2NP Specification" msgstr "" -#: i2p2www/pages/site/docs/index.html:134 +#: i2p2www/pages/site/docs/index.html:137 msgid "I2NP Javadoc" msgstr "" -#: i2p2www/pages/site/docs/index.html:141 +#: i2p2www/pages/site/docs/index.html:144 #: i2p2www/pages/site/docs/how/tech-intro.html:14 #: i2p2www/pages/site/docs/how/tech-intro.html:228 msgid "Tunnels" msgstr "" -#: i2p2www/pages/site/docs/index.html:142 +#: i2p2www/pages/site/docs/index.html:145 msgid "" "Selecting peers, requesting tunnels through those peers, and encrypting " "and routing messages through these tunnels." msgstr "" -#: i2p2www/pages/site/docs/index.html:144 +#: i2p2www/pages/site/docs/index.html:147 msgid "Peer profiling and selection" msgstr "" -#: i2p2www/pages/site/docs/index.html:145 +#: i2p2www/pages/site/docs/index.html:148 msgid "Tunnel routing overview" msgstr "" -#: i2p2www/pages/site/docs/index.html:146 +#: i2p2www/pages/site/docs/index.html:149 msgid "Garlic routing and \"garlic\" terminology" msgstr "" -#: i2p2www/pages/site/docs/index.html:147 +#: i2p2www/pages/site/docs/index.html:150 msgid "Tunnel building and encryption" msgstr "" -#: i2p2www/pages/site/docs/index.html:148 +#: i2p2www/pages/site/docs/index.html:151 msgid "ElGamal/AES" msgstr "" -#: i2p2www/pages/site/docs/index.html:148 +#: i2p2www/pages/site/docs/index.html:151 msgid "for build request encryption" msgstr "" -#: i2p2www/pages/site/docs/index.html:150 +#: i2p2www/pages/site/docs/index.html:153 msgid "Tunnel building specification" msgstr "" -#: i2p2www/pages/site/docs/index.html:151 +#: i2p2www/pages/site/docs/index.html:154 msgid "Low-level tunnel message specification" msgstr "" -#: i2p2www/pages/site/docs/index.html:152 +#: i2p2www/pages/site/docs/index.html:155 #: i2p2www/pages/site/docs/tunnels/unidirectional.html:2 msgid "Unidirectional Tunnels" msgstr "" -#: i2p2www/pages/site/docs/index.html:153 +#: i2p2www/pages/site/docs/index.html:156 #: i2p2www/pages/site/docs/how/peer-selection.html:299 msgid "Peer Profiling and Selection in the I2P Anonymous Network" msgstr "" -#: i2p2www/pages/site/docs/index.html:154 +#: i2p2www/pages/site/docs/index.html:157 msgid "2009 paper (pdf), not current but still generally accurate" msgstr "" -#: i2p2www/pages/site/docs/index.html:157 +#: i2p2www/pages/site/docs/index.html:160 msgid "Transport Layer" msgstr "" -#: i2p2www/pages/site/docs/index.html:158 +#: i2p2www/pages/site/docs/index.html:161 msgid "The protocols for direct (point-to-point) router to router communication." msgstr "" -#: i2p2www/pages/site/docs/index.html:160 +#: i2p2www/pages/site/docs/index.html:163 msgid "Transport layer overview" msgstr "" -#: i2p2www/pages/site/docs/index.html:162 +#: i2p2www/pages/site/docs/index.html:165 msgid "TCP-based transport overview and specification" msgstr "" -#: i2p2www/pages/site/docs/index.html:164 +#: i2p2www/pages/site/docs/index.html:167 msgid "UDP-based transport overview" msgstr "" -#: i2p2www/pages/site/docs/index.html:166 +#: i2p2www/pages/site/docs/index.html:169 msgid "SSU specification" msgstr "" -#: i2p2www/pages/site/docs/index.html:168 +#: i2p2www/pages/site/docs/index.html:171 msgid "NTCP transport encryption" msgstr "" -#: i2p2www/pages/site/docs/index.html:170 +#: i2p2www/pages/site/docs/index.html:173 msgid "SSU transport encryption" msgstr "" -#: i2p2www/pages/site/docs/index.html:172 +#: i2p2www/pages/site/docs/index.html:175 msgid "Transport Javadoc" msgstr "" -#: i2p2www/pages/site/docs/index.html:174 +#: i2p2www/pages/site/docs/index.html:177 msgid "NTCP Javadoc" msgstr "" -#: i2p2www/pages/site/docs/index.html:176 +#: i2p2www/pages/site/docs/index.html:179 msgid "SSU Javadoc" msgstr "" -#: i2p2www/pages/site/docs/index.html:179 +#: i2p2www/pages/site/docs/index.html:182 msgid "Other Router Topics" msgstr "" -#: i2p2www/pages/site/docs/index.html:181 +#: i2p2www/pages/site/docs/index.html:184 msgid "Router software updates" msgstr "Aggiornamenti software del router" -#: i2p2www/pages/site/docs/index.html:183 +#: i2p2www/pages/site/docs/index.html:188 msgid "Native BigInteger Library" msgstr "" -#: i2p2www/pages/site/docs/index.html:185 +#: i2p2www/pages/site/docs/index.html:190 msgid "Time synchronization and NTP" msgstr "" -#: i2p2www/pages/site/docs/index.html:187 +#: i2p2www/pages/site/docs/index.html:192 msgid "Performance" msgstr "Prestazioni" -#: i2p2www/pages/site/docs/index.html:194 +#: i2p2www/pages/site/docs/index.html:199 msgid "Developer's Guides and Resources" msgstr "" -#: i2p2www/pages/site/docs/index.html:196 +#: i2p2www/pages/site/docs/index.html:201 msgid "New Developer's Guide" msgstr "" -#: i2p2www/pages/site/docs/index.html:198 +#: i2p2www/pages/site/docs/index.html:203 msgid "New Translator's Guide" msgstr "" -#: i2p2www/pages/site/docs/index.html:200 +#: i2p2www/pages/site/docs/index.html:205 msgid "Monotone Guide" msgstr "" -#: i2p2www/pages/site/docs/index.html:202 +#: i2p2www/pages/site/docs/index.html:207 msgid "Developer Guidelines" msgstr "" -#: i2p2www/pages/site/docs/index.html:204 +#: i2p2www/pages/site/docs/index.html:209 msgid "Javadocs on the standard internet:" msgstr "" -#: i2p2www/pages/site/docs/index.html:205 -#: i2p2www/pages/site/docs/index.html:209 #: i2p2www/pages/site/docs/index.html:210 -#: i2p2www/pages/site/docs/index.html:211 +#: i2p2www/pages/site/docs/index.html:214 +#: i2p2www/pages/site/docs/index.html:215 +#: i2p2www/pages/site/docs/index.html:216 #, python-format msgid "Server %(num)s" msgstr "Server %(num)s" -#: i2p2www/pages/site/docs/index.html:206 -#: i2p2www/pages/site/docs/index.html:215 +#: i2p2www/pages/site/docs/index.html:211 +#: i2p2www/pages/site/docs/index.html:220 msgid "" "Note: always verify that javadocs are current by checking the release " "number." msgstr "" -#: i2p2www/pages/site/docs/index.html:208 +#: i2p2www/pages/site/docs/index.html:213 msgid "Javadocs inside I2P:" msgstr "" -#: i2p2www/pages/site/docs/index.html:219 +#: i2p2www/pages/site/docs/index.html:224 msgid "Ports used by I2P" msgstr "" -#: i2p2www/pages/site/docs/index.html:221 +#: i2p2www/pages/site/docs/index.html:226 msgid "Automatic updates to development builds inside I2P" msgstr "" -#: i2p2www/pages/site/docs/index.html:223 +#: i2p2www/pages/site/docs/index.html:228 msgid "Updating the wrapper manually" msgstr "" -#: i2p2www/pages/site/docs/index.html:225 +#: i2p2www/pages/site/docs/index.html:230 msgid "User forum" msgstr "" -#: i2p2www/pages/site/docs/index.html:227 +#: i2p2www/pages/site/docs/index.html:232 msgid "Developer forum inside I2P" msgstr "" -#: i2p2www/pages/site/docs/index.html:229 +#: i2p2www/pages/site/docs/index.html:234 msgid "Bug tracker" msgstr "Bug tracker" -#: i2p2www/pages/site/docs/index.html:231 +#: i2p2www/pages/site/docs/index.html:236 msgid "Viewmtn inside I2P" msgstr "" -#: i2p2www/pages/site/docs/index.html:233 +#: i2p2www/pages/site/docs/index.html:238 msgid "I2P Source exported to GitHub" msgstr "" -#: i2p2www/pages/site/docs/index.html:235 +#: i2p2www/pages/site/docs/index.html:240 msgid "I2P Source Git Repo inside I2P" msgstr "" -#: i2p2www/pages/site/docs/index.html:237 +#: i2p2www/pages/site/docs/index.html:242 msgid "Source translation at Transifex" msgstr "" -#: i2p2www/pages/site/docs/index.html:239 +#: i2p2www/pages/site/docs/index.html:244 msgid "Roadmap wiki" msgstr "" -#: i2p2www/pages/site/docs/index.html:241 +#: i2p2www/pages/site/docs/index.html:246 msgid "Old roadmap" msgstr "" -#: i2p2www/pages/site/docs/index.html:241 -#: i2p2www/pages/site/docs/index.html:243 +#: i2p2www/pages/site/docs/index.html:246 +#: i2p2www/pages/site/docs/index.html:248 msgid "not current" msgstr "" -#: i2p2www/pages/site/docs/index.html:243 +#: i2p2www/pages/site/docs/index.html:248 msgid "To Do List" msgstr "" @@ -791,7 +803,7 @@ msgid "" msgstr "" #: i2p2www/pages/site/docs/naming.html:183 -#: i2p2www/pages/site/docs/spec/configuration.html:170 +#: i2p2www/pages/site/docs/spec/configuration.html:184 msgid "Addressbook" msgstr "" @@ -1161,7 +1173,7 @@ msgid "" msgstr "" #: i2p2www/pages/site/docs/plugins.html:2 -#: i2p2www/pages/site/docs/spec/configuration.html:138 +#: i2p2www/pages/site/docs/spec/configuration.html:152 msgid "Plugins" msgstr "Plugin" @@ -2537,15 +2549,20 @@ msgid "" msgstr "" #: i2p2www/pages/site/docs/api/i2ptunnel.html:54 +#, fuzzy +msgid "Configuration" +msgstr "Formato del File di Configurazione" + +#: i2p2www/pages/site/docs/api/i2ptunnel.html:58 msgid "Client Modes" msgstr "" -#: i2p2www/pages/site/docs/api/i2ptunnel.html:55 -#: i2p2www/pages/site/docs/api/i2ptunnel.html:137 +#: i2p2www/pages/site/docs/api/i2ptunnel.html:59 +#: i2p2www/pages/site/docs/api/i2ptunnel.html:141 msgid "Standard" msgstr "" -#: i2p2www/pages/site/docs/api/i2ptunnel.html:56 +#: 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" @@ -2553,7 +2570,7 @@ msgid "" " list of destinations." msgstr "" -#: i2p2www/pages/site/docs/api/i2ptunnel.html:62 +#: i2p2www/pages/site/docs/api/i2ptunnel.html:66 msgid "" "A HTTP-client tunnel. The tunnel connects to the destination specified by" " the URL\n" @@ -2561,34 +2578,34 @@ msgid "" "provided. Strips HTTP connections of the following headers:" msgstr "" -#: i2p2www/pages/site/docs/api/i2ptunnel.html:67 +#: 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 "" -#: i2p2www/pages/site/docs/api/i2ptunnel.html:75 +#: 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 "" -#: i2p2www/pages/site/docs/api/i2ptunnel.html:82 +#: 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 "" -#: i2p2www/pages/site/docs/api/i2ptunnel.html:86 +#: i2p2www/pages/site/docs/api/i2ptunnel.html:90 msgid "Outproxy:" msgstr "" -#: i2p2www/pages/site/docs/api/i2ptunnel.html:87 +#: i2p2www/pages/site/docs/api/i2ptunnel.html:91 msgid "Internal I2P use:" msgstr "" -#: i2p2www/pages/site/docs/api/i2ptunnel.html:92 +#: i2p2www/pages/site/docs/api/i2ptunnel.html:96 msgid "" "Creates a connection to a random IRC server specified by the comma " "seprated (\", \") \n" @@ -2596,43 +2613,43 @@ msgid "" "allowed due to anonymity concerns." msgstr "" -#: i2p2www/pages/site/docs/api/i2ptunnel.html:96 +#: i2p2www/pages/site/docs/api/i2ptunnel.html:100 msgid "Whitelist:" msgstr "" -#: i2p2www/pages/site/docs/api/i2ptunnel.html:111 +#: i2p2www/pages/site/docs/api/i2ptunnel.html:115 msgid "Enables using the I2P router as a SOCKS proxy." msgstr "" -#: i2p2www/pages/site/docs/api/i2ptunnel.html:116 +#: 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" "IRC client mode." msgstr "" -#: i2p2www/pages/site/docs/api/i2ptunnel.html:122 +#: 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 "" -#: i2p2www/pages/site/docs/api/i2ptunnel.html:128 +#: 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" "subscribe to a streamr server tunnel." msgstr "" -#: i2p2www/pages/site/docs/api/i2ptunnel.html:136 +#: i2p2www/pages/site/docs/api/i2ptunnel.html:140 msgid "Server Modes" msgstr "" -#: i2p2www/pages/site/docs/api/i2ptunnel.html:138 +#: i2p2www/pages/site/docs/api/i2ptunnel.html:142 msgid "Creates a destination to a local ip:port with an open TCP port." msgstr "" -#: i2p2www/pages/site/docs/api/i2ptunnel.html:143 +#: 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" @@ -2640,7 +2657,7 @@ msgid "" " such a request." msgstr "" -#: i2p2www/pages/site/docs/api/i2ptunnel.html:149 +#: 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" @@ -2649,14 +2666,14 @@ msgid "" "requests, or loopback-testing an eepsite as a diagnostic tool." msgstr "" -#: i2p2www/pages/site/docs/api/i2ptunnel.html:156 +#: i2p2www/pages/site/docs/api/i2ptunnel.html:160 msgid "" "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:162 +#: 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." @@ -3449,8 +3466,8 @@ msgstr "" #: i2p2www/pages/site/docs/how/tunnel-routing.html:255 #: i2p2www/pages/site/docs/protocol/i2cp.html:687 #: i2p2www/pages/site/docs/protocol/i2np.html:226 -#: i2p2www/pages/site/docs/spec/updates.html:438 -#: i2p2www/pages/site/docs/transport/ntcp.html:535 +#: i2p2www/pages/site/docs/spec/updates.html:488 +#: i2p2www/pages/site/docs/transport/ntcp.html:544 #: i2p2www/pages/site/docs/transport/ssu.html:554 #: i2p2www/pages/site/docs/tunnels/implementation.html:506 msgid "Future Work" @@ -4001,6 +4018,14 @@ 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)." +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" "If done wrong, it could cause real harm to our network.\n" @@ -4009,11 +4034,11 @@ msgid "" "This page discusses some general guidelines." msgstr "" -#: i2p2www/pages/site/docs/applications/embedding.html:18 +#: i2p2www/pages/site/docs/applications/embedding.html:23 msgid "Talk to us" msgstr "" -#: i2p2www/pages/site/docs/applications/embedding.html:19 +#: 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" @@ -4021,11 +4046,11 @@ msgid "" "everyone." msgstr "" -#: i2p2www/pages/site/docs/applications/embedding.html:25 +#: i2p2www/pages/site/docs/applications/embedding.html:30 msgid "Choose your router wisely" msgstr "" -#: i2p2www/pages/site/docs/applications/embedding.html:26 +#: 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" @@ -4035,19 +4060,19 @@ msgid "" "Some of the following only applies to the Java router." msgstr "" -#: i2p2www/pages/site/docs/applications/embedding.html:34 +#: i2p2www/pages/site/docs/applications/embedding.html:39 msgid "Licensing" msgstr "" -#: i2p2www/pages/site/docs/applications/embedding.html:35 +#: i2p2www/pages/site/docs/applications/embedding.html:40 msgid "Ensure you meet the license requirements of the software you are bundling." msgstr "" -#: i2p2www/pages/site/docs/applications/embedding.html:40 +#: i2p2www/pages/site/docs/applications/embedding.html:45 msgid "Verify default configuration" msgstr "" -#: i2p2www/pages/site/docs/applications/embedding.html:41 +#: i2p2www/pages/site/docs/applications/embedding.html:46 msgid "" "A correct default configuration is crucial. Most users will not change " "the defaults.\n" @@ -4056,7 +4081,7 @@ msgid "" "Override the router defaults if necessary." msgstr "" -#: i2p2www/pages/site/docs/applications/embedding.html:46 +#: i2p2www/pages/site/docs/applications/embedding.html:51 msgid "" "Some important defaults to review: Max bandwidth, tunnel quantity and " "length, max participating tunnels.\n" @@ -4064,7 +4089,7 @@ msgid "" "your app." msgstr "" -#: i2p2www/pages/site/docs/applications/embedding.html:50 +#: i2p2www/pages/site/docs/applications/embedding.html:55 msgid "" "Configure enough bandwidth and tunnels to allow your users to contribute " "to the network.\n" @@ -4074,11 +4099,11 @@ msgid "" "example." msgstr "" -#: i2p2www/pages/site/docs/applications/embedding.html:57 +#: i2p2www/pages/site/docs/applications/embedding.html:62 msgid "Participating Traffic Considerations" msgstr "" -#: i2p2www/pages/site/docs/applications/embedding.html:58 +#: 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, " @@ -4090,14 +4115,14 @@ msgid "" "tunnels." msgstr "" -#: i2p2www/pages/site/docs/applications/embedding.html:65 +#: 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" "which is helped tremendously by others building tunnels through you." msgstr "" -#: i2p2www/pages/site/docs/applications/embedding.html:69 +#: i2p2www/pages/site/docs/applications/embedding.html:74 msgid "" "Secondly, over 90% of the routers in the current network allow " "participating traffic.\n" @@ -4109,13 +4134,13 @@ msgid "" " people to enable relaying." msgstr "" -#: i2p2www/pages/site/docs/applications/embedding.html:76 +#: i2p2www/pages/site/docs/applications/embedding.html:81 msgid "" "Thirdly, participating traffic is cover traffic that helps your users' " "anonymity." msgstr "" -#: i2p2www/pages/site/docs/applications/embedding.html:79 +#: i2p2www/pages/site/docs/applications/embedding.html:84 msgid "" "We strongly discourage you from disabling participating traffic by " "default.\n" @@ -4123,11 +4148,11 @@ msgid "" "the network." msgstr "" -#: i2p2www/pages/site/docs/applications/embedding.html:85 +#: i2p2www/pages/site/docs/applications/embedding.html:90 msgid "Persistence" msgstr "" -#: i2p2www/pages/site/docs/applications/embedding.html:86 +#: 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" @@ -4137,11 +4162,11 @@ msgid "" "performance." msgstr "" -#: i2p2www/pages/site/docs/applications/embedding.html:94 +#: i2p2www/pages/site/docs/applications/embedding.html:99 msgid "Configurability" msgstr "" -#: i2p2www/pages/site/docs/applications/embedding.html:95 +#: i2p2www/pages/site/docs/applications/embedding.html:100 msgid "" "Give your users a way to change the configuration of the important " "settings.\n" @@ -4151,11 +4176,11 @@ msgid "" "IP/port may be helpful." msgstr "" -#: i2p2www/pages/site/docs/applications/embedding.html:103 +#: i2p2www/pages/site/docs/applications/embedding.html:108 msgid "Floodfill Considerations" msgstr "" -#: i2p2www/pages/site/docs/applications/embedding.html:104 +#: 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" @@ -4166,11 +4191,11 @@ msgid "" "It also depends on the typical uptime for your application." msgstr "" -#: i2p2www/pages/site/docs/applications/embedding.html:114 +#: i2p2www/pages/site/docs/applications/embedding.html:119 msgid "Reseeding" msgstr "" -#: i2p2www/pages/site/docs/applications/embedding.html:115 +#: 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 " @@ -4178,11 +4203,11 @@ msgid "" "Be aware of possible blocking by hostile governments." msgstr "" -#: i2p2www/pages/site/docs/applications/embedding.html:124 +#: i2p2www/pages/site/docs/applications/embedding.html:129 msgid "Reduce Network Resource Usage" msgstr "" -#: i2p2www/pages/site/docs/applications/embedding.html:125 +#: 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" @@ -4192,11 +4217,11 @@ msgid "" "tunnel, even in the presence of some background DHT activity." msgstr "" -#: i2p2www/pages/site/docs/applications/embedding.html:133 +#: i2p2www/pages/site/docs/applications/embedding.html:138 msgid "Updatability" msgstr "" -#: i2p2www/pages/site/docs/applications/embedding.html:134 +#: 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" @@ -4211,11 +4236,11 @@ msgid "" "which you presumably are not bundling." msgstr "" -#: i2p2www/pages/site/docs/applications/embedding.html:145 +#: i2p2www/pages/site/docs/applications/embedding.html:150 msgid "Rollout" msgstr "" -#: i2p2www/pages/site/docs/applications/embedding.html:146 +#: 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 " @@ -4231,11 +4256,11 @@ msgid "" "checklist is." msgstr "" -#: i2p2www/pages/site/docs/applications/embedding.html:158 +#: i2p2www/pages/site/docs/applications/embedding.html:163 msgid "Design for and Encourage Long Uptimes" msgstr "" -#: i2p2www/pages/site/docs/applications/embedding.html:159 +#: 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 " @@ -4244,53 +4269,53 @@ msgid "" "solution." msgstr "" -#: i2p2www/pages/site/docs/applications/embedding.html:167 +#: i2p2www/pages/site/docs/applications/embedding.html:172 msgid "Show Status" msgstr "" -#: i2p2www/pages/site/docs/applications/embedding.html:168 +#: i2p2www/pages/site/docs/applications/embedding.html:173 msgid "" "Provide some indication to the user that the application tunnels are " "ready. Encourage patience." msgstr "" -#: i2p2www/pages/site/docs/applications/embedding.html:173 +#: i2p2www/pages/site/docs/applications/embedding.html:178 msgid "Graceful Shutdown" msgstr "" -#: i2p2www/pages/site/docs/applications/embedding.html:174 +#: 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 "" -#: i2p2www/pages/site/docs/applications/embedding.html:180 +#: i2p2www/pages/site/docs/applications/embedding.html:185 msgid "Education and Donation" msgstr "" -#: i2p2www/pages/site/docs/applications/embedding.html:181 +#: 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 "" -#: i2p2www/pages/site/docs/applications/embedding.html:187 +#: i2p2www/pages/site/docs/applications/embedding.html:192 msgid "External Router Option" msgstr "" -#: i2p2www/pages/site/docs/applications/embedding.html:188 +#: 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 "" -#: i2p2www/pages/site/docs/applications/embedding.html:195 +#: i2p2www/pages/site/docs/applications/embedding.html:200 msgid "Use of other Common Services" msgstr "" -#: i2p2www/pages/site/docs/applications/embedding.html:196 +#: 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" @@ -4298,11 +4323,11 @@ msgid "" "and talk to the people who are running them to make sure it's ok." msgstr "" -#: i2p2www/pages/site/docs/applications/embedding.html:204 +#: i2p2www/pages/site/docs/applications/embedding.html:209 msgid "Time / NTP Issues" msgstr "" -#: i2p2www/pages/site/docs/applications/embedding.html:205 +#: 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. " @@ -4311,11 +4336,11 @@ msgid "" "clock is correct." msgstr "" -#: i2p2www/pages/site/docs/applications/embedding.html:213 +#: i2p2www/pages/site/docs/applications/embedding.html:218 msgid "Choose What and How you Bundle" msgstr "" -#: i2p2www/pages/site/docs/applications/embedding.html:214 +#: 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" @@ -4333,11 +4358,19 @@ msgid "" "and i2psnark, for example." msgstr "" -#: i2p2www/pages/site/docs/applications/embedding.html:228 +#: i2p2www/pages/site/docs/applications/embedding.html:233 +msgid "You may also wish to bundle a hosts.txt file." +msgstr "" + +#: i2p2www/pages/site/docs/applications/embedding.html:236 +msgid "Be sure to specify a Java 6 bootclasspath if compiling with Java 8." +msgstr "" + +#: i2p2www/pages/site/docs/applications/embedding.html:244 msgid "Datagram (DHT) considerations" msgstr "" -#: i2p2www/pages/site/docs/applications/embedding.html:229 +#: 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 " @@ -4353,32 +4386,32 @@ msgid "" "have several." msgstr "" -#: i2p2www/pages/site/docs/applications/embedding.html:242 +#: i2p2www/pages/site/docs/applications/embedding.html:258 msgid "Comarketing" msgstr "" -#: i2p2www/pages/site/docs/applications/embedding.html:243 +#: 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 "" -#: i2p2www/pages/site/docs/applications/embedding.html:249 +#: i2p2www/pages/site/docs/applications/embedding.html:265 msgid "Malware" msgstr "" -#: i2p2www/pages/site/docs/applications/embedding.html:250 +#: i2p2www/pages/site/docs/applications/embedding.html:266 msgid "" "Please don't use I2P for evil.\n" "It could cause great harm both to our network and our reputation." msgstr "" -#: i2p2www/pages/site/docs/applications/embedding.html:256 +#: i2p2www/pages/site/docs/applications/embedding.html:272 msgid "Join Us" msgstr "" -#: i2p2www/pages/site/docs/applications/embedding.html:257 +#: 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" @@ -4386,11 +4419,11 @@ msgid "" "We can help get you users, testers, translators, or even coders." msgstr "" -#: i2p2www/pages/site/docs/applications/embedding.html:265 +#: i2p2www/pages/site/docs/applications/embedding.html:281 msgid "Application Examples" msgstr "" -#: i2p2www/pages/site/docs/applications/embedding.html:266 +#: 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" @@ -4400,17 +4433,17 @@ msgid "" " and Monero." msgstr "" -#: i2p2www/pages/site/docs/applications/embedding.html:274 +#: i2p2www/pages/site/docs/applications/embedding.html:290 msgid "Code Example" msgstr "" -#: i2p2www/pages/site/docs/applications/embedding.html:275 +#: i2p2www/pages/site/docs/applications/embedding.html:291 msgid "" "None of the above actually tells you how to write your code to\n" "bundle the Java router, so following is a brief example." msgstr "" -#: i2p2www/pages/site/docs/applications/embedding.html:290 +#: 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" @@ -7274,7 +7307,6 @@ msgid "The Network Database" msgstr "" #: i2p2www/pages/site/docs/how/network-database.html:3 -#: i2p2www/pages/site/docs/transport/ntcp.html:3 msgid "October 2014" msgstr "" @@ -14528,10 +14560,6 @@ msgstr "" msgid "Configuration File Specification" msgstr "" -#: i2p2www/pages/site/docs/spec/configuration.html:3 -msgid "January 2014" -msgstr "Gennaio 2014" - #: i2p2www/pages/site/docs/spec/configuration.html:7 msgid "" "This page provides a general specification of I2P configuration files,\n" @@ -14640,65 +14668,66 @@ msgid "Configured via /configlogging in the router console." msgstr "" #: i2p2www/pages/site/docs/spec/configuration.html:112 -#: i2p2www/pages/site/docs/spec/configuration.html:142 -#: i2p2www/pages/site/docs/spec/configuration.html:154 +#: i2p2www/pages/site/docs/spec/configuration.html:156 +#: i2p2www/pages/site/docs/spec/configuration.html:168 +#: i2p2www/pages/site/docs/spec/configuration.html:198 msgid "Properties are as follows:" msgstr "" -#: i2p2www/pages/site/docs/spec/configuration.html:133 +#: i2p2www/pages/site/docs/spec/configuration.html:147 msgid "Individual Plugin" msgstr "" -#: i2p2www/pages/site/docs/spec/configuration.html:134 +#: i2p2www/pages/site/docs/spec/configuration.html:148 #, python-format msgid "See the plugin specification." msgstr "" -#: i2p2www/pages/site/docs/spec/configuration.html:139 +#: i2p2www/pages/site/docs/spec/configuration.html:153 msgid "Enable/disable for each installed plugin." msgstr "" -#: i2p2www/pages/site/docs/spec/configuration.html:150 +#: i2p2www/pages/site/docs/spec/configuration.html:164 msgid "Webapps" msgstr "Webapp" -#: i2p2www/pages/site/docs/spec/configuration.html:151 +#: i2p2www/pages/site/docs/spec/configuration.html:165 msgid "Enable/disable for each installed webapp." msgstr "" -#: i2p2www/pages/site/docs/spec/configuration.html:163 +#: i2p2www/pages/site/docs/spec/configuration.html:177 msgid "Router" msgstr "Router" -#: i2p2www/pages/site/docs/spec/configuration.html:164 +#: i2p2www/pages/site/docs/spec/configuration.html:178 msgid "Configured via /configadvanced in the router console." msgstr "" -#: i2p2www/pages/site/docs/spec/configuration.html:168 +#: i2p2www/pages/site/docs/spec/configuration.html:182 msgid "Applications" msgstr "Applicazioni" -#: i2p2www/pages/site/docs/spec/configuration.html:171 +#: i2p2www/pages/site/docs/spec/configuration.html:185 msgid "See documentation in SusiDNS." msgstr "" -#: i2p2www/pages/site/docs/spec/configuration.html:176 +#: i2p2www/pages/site/docs/spec/configuration.html:190 msgid "Configured via the application gui." msgstr "" -#: i2p2www/pages/site/docs/spec/configuration.html:181 +#: i2p2www/pages/site/docs/spec/configuration.html:195 msgid "Configured via the /i2ptunnel application in the router console." msgstr "" -#: i2p2www/pages/site/docs/spec/configuration.html:185 +#: i2p2www/pages/site/docs/spec/configuration.html:364 msgid "Router Console" msgstr "" -#: i2p2www/pages/site/docs/spec/configuration.html:186 +#: i2p2www/pages/site/docs/spec/configuration.html:365 msgid "The router console uses the router.config file." msgstr "" -#: i2p2www/pages/site/docs/spec/configuration.html:191 +#: i2p2www/pages/site/docs/spec/configuration.html:370 msgid "See post on zzz.i2p." msgstr "" @@ -15093,6 +15122,7 @@ msgstr "" #: i2p2www/pages/site/docs/spec/updates.html:204 #: i2p2www/pages/site/docs/spec/updates.html:313 +#: i2p2www/pages/site/docs/spec/updates.html:365 msgid "Goals:" msgstr "Obbiettivi: " @@ -15115,7 +15145,8 @@ msgid "One-pass signature verification and file extraction" msgstr "" #: i2p2www/pages/site/docs/spec/updates.html:222 -#: i2p2www/pages/site/docs/spec/updates.html:336 +#: i2p2www/pages/site/docs/spec/updates.html:328 +#: i2p2www/pages/site/docs/spec/updates.html:388 msgid "Specification:" msgstr "Specifiche:" @@ -15124,40 +15155,79 @@ msgid "All unused fields must be set to 0 for compatibility with future versions msgstr "" #: i2p2www/pages/site/docs/spec/updates.html:308 -msgid "SU3 News File Specification" +msgid "SU3 Reseed File Specification" msgstr "" #: i2p2www/pages/site/docs/spec/updates.html:309 -msgid "As of 0.9.17, the news is delivered in an \"su3\" file format." +msgid "As of 0.9.14, reseed data is delivered in an \"su3\" file format." msgstr "" #: i2p2www/pages/site/docs/spec/updates.html:316 -msgid "Signed news with strong signatures and trusted certificates" +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 "" -#: i2p2www/pages/site/docs/spec/updates.html:319 +#: 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 "" -#: i2p2www/pages/site/docs/spec/updates.html:322 -msgid "Standard XML format for use with standard parsers" -msgstr "" - -#: i2p2www/pages/site/docs/spec/updates.html:325 -msgid "Standard Atom format for use with standard feed readers and generators" -msgstr "" - -#: i2p2www/pages/site/docs/spec/updates.html:328 -msgid "Sanitization and verification of HTML before displaying on console" +#: i2p2www/pages/site/docs/spec/updates.html:323 +msgid "" +"Single compressed file to speed up reseeding, which was slow to fetch 200" +" files" msgstr "" #: i2p2www/pages/site/docs/spec/updates.html:331 +msgid "The file must be named \"i2pseeds.su3\"." +msgstr "" + +#: i2p2www/pages/site/docs/spec/updates.html:334 +msgid "" +"The file must be in the same directory as the router infos on the web " +"server." +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" +"and then fetch the individual router info files found in the links." +msgstr "" + +#: i2p2www/pages/site/docs/spec/updates.html:360 +msgid "SU3 News File Specification" +msgstr "" + +#: i2p2www/pages/site/docs/spec/updates.html:361 +msgid "As of 0.9.17, the news is delivered in an \"su3\" file format." +msgstr "" + +#: i2p2www/pages/site/docs/spec/updates.html:368 +msgid "Signed news with strong signatures and trusted certificates" +msgstr "" + +#: i2p2www/pages/site/docs/spec/updates.html:374 +msgid "Standard XML format for use with standard parsers" +msgstr "" + +#: i2p2www/pages/site/docs/spec/updates.html:377 +msgid "Standard Atom format for use with standard feed readers and generators" +msgstr "" + +#: i2p2www/pages/site/docs/spec/updates.html:380 +msgid "Sanitization and verification of HTML before displaying on console" +msgstr "" + +#: i2p2www/pages/site/docs/spec/updates.html:383 msgid "" "Suitable for easy implementation on Android and other platforms without " "an HTML console" msgstr "" -#: i2p2www/pages/site/docs/spec/updates.html:440 +#: 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" @@ -15750,7 +15820,7 @@ msgstr "" #: i2p2www/pages/site/docs/transport/ntcp.html:207 #: i2p2www/pages/site/docs/transport/ntcp.html:250 #: i2p2www/pages/site/docs/transport/ntcp.html:332 -#: i2p2www/pages/site/docs/transport/ntcp.html:428 +#: i2p2www/pages/site/docs/transport/ntcp.html:437 msgid "Size:" msgstr "Dimensione:" @@ -15768,7 +15838,7 @@ msgstr "" #: i2p2www/pages/site/docs/transport/ntcp.html:236 #: i2p2www/pages/site/docs/transport/ntcp.html:319 -#: i2p2www/pages/site/docs/transport/ntcp.html:397 +#: i2p2www/pages/site/docs/transport/ntcp.html:398 msgid "Notes:" msgstr "Note:" @@ -15788,7 +15858,7 @@ msgstr "" #: i2p2www/pages/site/docs/transport/ntcp.html:252 #: i2p2www/pages/site/docs/transport/ntcp.html:334 -#: i2p2www/pages/site/docs/transport/ntcp.html:430 +#: i2p2www/pages/site/docs/transport/ntcp.html:439 msgid "Unencrypted Contents:" msgstr "" @@ -15812,7 +15882,7 @@ msgstr "" #: i2p2www/pages/site/docs/transport/ntcp.html:285 #: i2p2www/pages/site/docs/transport/ntcp.html:376 -#: i2p2www/pages/site/docs/transport/ntcp.html:457 +#: i2p2www/pages/site/docs/transport/ntcp.html:466 msgid "Encrypted Contents:" msgstr "" @@ -15849,7 +15919,7 @@ msgid "Alice's 387+ byte `RouterIdentity`" msgstr "" #: i2p2www/pages/site/docs/transport/ntcp.html:366 -#: i2p2www/pages/site/docs/transport/ntcp.html:452 +#: i2p2www/pages/site/docs/transport/ntcp.html:461 msgid "0-15 bytes random data" msgstr "" @@ -15870,31 +15940,31 @@ msgid "" "of message #1) as the IV" msgstr "" -#: i2p2www/pages/site/docs/transport/ntcp.html:399 +#: i2p2www/pages/site/docs/transport/ntcp.html:400 msgid "Bob verifies the signature, and on failure, drops the connection." msgstr "" -#: i2p2www/pages/site/docs/transport/ntcp.html:402 +#: i2p2www/pages/site/docs/transport/ntcp.html:403 msgid "" "Bob may drop the connection if the clock skew with Alice is too high as " "calculated using tsA." msgstr "" -#: i2p2www/pages/site/docs/transport/ntcp.html:405 +#: 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 "" -#: i2p2www/pages/site/docs/transport/ntcp.html:421 +#: i2p2www/pages/site/docs/transport/ntcp.html:430 msgid "Message 4 (Session Confirm B)" msgstr "" -#: i2p2www/pages/site/docs/transport/ntcp.html:422 +#: i2p2www/pages/site/docs/transport/ntcp.html:431 msgid "This is a signature of the critical data. Bob sends Alice:" msgstr "" -#: i2p2www/pages/site/docs/transport/ntcp.html:446 +#: i2p2www/pages/site/docs/transport/ntcp.html:455 msgid "" "the `Signature` of the following concatenated data:\n" " X, Y, Alice's `RouterIdentity`, tsA, tsB.\n" @@ -15902,7 +15972,7 @@ msgid "" "the `SigningPublicKey` in his `RouterIdentity`" msgstr "" -#: i2p2www/pages/site/docs/transport/ntcp.html:470 +#: i2p2www/pages/site/docs/transport/ntcp.html:479 #, python-format msgid "" "Data AES encrypted using the DH " @@ -15913,21 +15983,21 @@ msgid "" "signature types" msgstr "" -#: i2p2www/pages/site/docs/transport/ntcp.html:479 +#: i2p2www/pages/site/docs/transport/ntcp.html:488 msgid "Alice verifies the signature, and on failure, drops the connection." msgstr "" -#: i2p2www/pages/site/docs/transport/ntcp.html:482 +#: 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 "" -#: i2p2www/pages/site/docs/transport/ntcp.html:497 +#: i2p2www/pages/site/docs/transport/ntcp.html:506 msgid "After Establishment" msgstr "" -#: i2p2www/pages/site/docs/transport/ntcp.html:498 +#: i2p2www/pages/site/docs/transport/ntcp.html:507 msgid "" "The connection is established, and standard or time sync messages may be " "exchanged.\n" @@ -15939,11 +16009,11 @@ msgid "" " the next IV." msgstr "" -#: i2p2www/pages/site/docs/transport/ntcp.html:507 +#: i2p2www/pages/site/docs/transport/ntcp.html:516 msgid "Check Connection Message" msgstr "" -#: i2p2www/pages/site/docs/transport/ntcp.html:508 +#: i2p2www/pages/site/docs/transport/ntcp.html:517 msgid "" "Alternately, when Bob receives a connection, it could be a\n" "check connection (perhaps prompted by Bob asking for someone\n" @@ -15953,58 +16023,58 @@ msgid "" "A check info connection will receive 256 bytes containing:" msgstr "" -#: i2p2www/pages/site/docs/transport/ntcp.html:517 +#: i2p2www/pages/site/docs/transport/ntcp.html:526 msgid "32 bytes of uninterpreted, ignored data" msgstr "" -#: i2p2www/pages/site/docs/transport/ntcp.html:518 +#: i2p2www/pages/site/docs/transport/ntcp.html:527 msgid "1 byte size" msgstr "" -#: i2p2www/pages/site/docs/transport/ntcp.html:519 +#: 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 "" -#: i2p2www/pages/site/docs/transport/ntcp.html:520 +#: i2p2www/pages/site/docs/transport/ntcp.html:529 msgid "2 byte port number that the local router was reached on" msgstr "" -#: i2p2www/pages/site/docs/transport/ntcp.html:521 +#: i2p2www/pages/site/docs/transport/ntcp.html:530 msgid "" "4 byte i2p network time as known by the remote side (seconds since the " "epoch)" msgstr "" -#: i2p2www/pages/site/docs/transport/ntcp.html:522 +#: i2p2www/pages/site/docs/transport/ntcp.html:531 msgid "uninterpreted padding data, up to byte 223" msgstr "" -#: i2p2www/pages/site/docs/transport/ntcp.html:523 +#: 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 "" -#: i2p2www/pages/site/docs/transport/ntcp.html:526 +#: i2p2www/pages/site/docs/transport/ntcp.html:535 msgid "Check connection is completely disabled as of release 0.9.12." msgstr "" -#: i2p2www/pages/site/docs/transport/ntcp.html:530 +#: i2p2www/pages/site/docs/transport/ntcp.html:539 msgid "Discussion" msgstr "Discussione " -#: i2p2www/pages/site/docs/transport/ntcp.html:531 +#: i2p2www/pages/site/docs/transport/ntcp.html:540 #, python-format msgid "Now on the NTCP Discussion Page." msgstr "" -#: i2p2www/pages/site/docs/transport/ntcp.html:537 +#: i2p2www/pages/site/docs/transport/ntcp.html:546 msgid "The maximum message size should be increased to approximately 32 KB." msgstr "" -#: i2p2www/pages/site/docs/transport/ntcp.html:541 +#: 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" @@ -16015,13 +16085,13 @@ msgid "" "to create a limited number of message sizes." msgstr "" -#: i2p2www/pages/site/docs/transport/ntcp.html:549 +#: 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 "" -#: i2p2www/pages/site/docs/transport/ntcp.html:553 +#: 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?" diff --git a/i2p2www/translations/it/LC_MESSAGES/get-involved.po b/i2p2www/translations/it/LC_MESSAGES/get-involved.po index 0c3a0fa3..7a95aec6 100644 --- a/i2p2www/translations/it/LC_MESSAGES/get-involved.po +++ b/i2p2www/translations/it/LC_MESSAGES/get-involved.po @@ -11,7 +11,7 @@ msgid "" msgstr "" "Project-Id-Version: I2P\n" "Report-Msgid-Bugs-To: http://trac.i2p2.de\n" -"POT-Creation-Date: 2014-10-22 20:13+0000\n" +"POT-Creation-Date: 2014-11-27 12:12+0000\n" "PO-Revision-Date: 2014-10-22 20:24+0000\n" "Last-Translator: str4d \n" "Language-Team: Italian " @@ -457,319 +457,52 @@ msgid "" msgstr "" #: i2p2www/pages/site/get-involved/todo.html:15 -#: i2p2www/pages/site/get-involved/todo.html:53 +#: i2p2www/pages/site/get-involved/todo.html:38 msgid "Core functionality" msgstr "" #: i2p2www/pages/site/get-involved/todo.html:15 -#: i2p2www/pages/site/get-involved/todo.html:27 -#: i2p2www/pages/site/get-involved/todo.html:51 +#: i2p2www/pages/site/get-involved/todo.html:21 +#: i2p2www/pages/site/get-involved/todo.html:36 msgid "link" msgstr "link" #: i2p2www/pages/site/get-involved/todo.html:17 -#: i2p2www/pages/site/get-involved/todo.html:56 -msgid "NAT/Firewall bridging via 1-hop restricted routes" -msgstr "" - -#: i2p2www/pages/site/get-involved/todo.html:20 -#: i2p2www/pages/site/get-involved/todo.html:129 -msgid "High degree transport layer with UDP, NBIO, or NIO" -msgstr "" - -#: i2p2www/pages/site/get-involved/todo.html:23 -#: i2p2www/pages/site/get-involved/todo.html:217 +#: i2p2www/pages/site/get-involved/todo.html:41 msgid "NetworkDB and profile tuning and ejection policy for large nets" msgstr "" -#: i2p2www/pages/site/get-involved/todo.html:27 -#: i2p2www/pages/site/get-involved/todo.html:241 +#: i2p2www/pages/site/get-involved/todo.html:21 +#: i2p2www/pages/site/get-involved/todo.html:65 msgid "Security / anonymity" msgstr "Sicurezza / anonimato" -#: i2p2www/pages/site/get-involved/todo.html:29 -#: i2p2www/pages/site/get-involved/todo.html:244 -msgid "" -"Per-hop tunnel id & new permuted TunnelVerificationStructure " -"encryption" -msgstr "" - -#: i2p2www/pages/site/get-involved/todo.html:32 -#: i2p2www/pages/site/get-involved/todo.html:294 -msgid "Strict ordering of participants within tunnels" -msgstr "" - -#: i2p2www/pages/site/get-involved/todo.html:35 -msgid "Randomly permuted tunnel lengths" -msgstr "" - -#: i2p2www/pages/site/get-involved/todo.html:38 -#: i2p2www/pages/site/get-involved/todo.html:356 +#: 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 "" -#: i2p2www/pages/site/get-involved/todo.html:41 -#: i2p2www/pages/site/get-involved/todo.html:375 +#: 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 "" -#: i2p2www/pages/site/get-involved/todo.html:44 -#: i2p2www/pages/site/get-involved/todo.html:404 +#: 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 "" -#: i2p2www/pages/site/get-involved/todo.html:47 -#: i2p2www/pages/site/get-involved/todo.html:441 +#: i2p2www/pages/site/get-involved/todo.html:32 +#: i2p2www/pages/site/get-involved/todo.html:153 msgid "Stop & go mix w/ garlics & tunnels" msgstr "" -#: i2p2www/pages/site/get-involved/todo.html:51 -#: i2p2www/pages/site/get-involved/todo.html:455 +#: i2p2www/pages/site/get-involved/todo.html:36 +#: i2p2www/pages/site/get-involved/todo.html:167 msgid "Performance" msgstr "Prestazioni" -#: i2p2www/pages/site/get-involved/todo.html:61 -msgid "Implemented in I2P 0.6.0.6" -msgstr "Implementato in I2P 0.6.0.6" - -#: i2p2www/pages/site/get-involved/todo.html:62 -msgid "" -"The functionality of allowing routers to fully participate within the " -"network \n" -"while behind firewalls and NATs that they do not control requires some " -"basic \n" -"restricted route operation (since those peers will not be able to receive" -" \n" -"inbound connections). To do this successfully, you consider peers one of" -" \n" -"two ways:" -msgstr "" - -#: i2p2www/pages/site/get-involved/todo.html:72 -msgid "" -"Peers who have reachable interfaces - these peers do not need to \n" -"do anything special" -msgstr "" - -#: i2p2www/pages/site/get-involved/todo.html:76 -msgid "" -"Peers who do not have reachable interfaces - these peers must " -"build \n" -"a tunnel pointing at them where the gateway is one of the peers they have" -" \n" -"established a connection with who has both a publicly reachable interface" -" \n" -"and who has agreed to serve as their 'introducer'." -msgstr "" - -#: i2p2www/pages/site/get-involved/todo.html:84 -msgid "" -"To do this, peers who have no IP address simply connect to a few peers, \n" -"build a tunnel through them, and publish a reference to those tunnels " -"within \n" -"their RouterInfo structure in the network database." -msgstr "" - -#: i2p2www/pages/site/get-involved/todo.html:89 -msgid "" -"When someone wants to contact any particular router, they first must get" -" \n" -"its RouterInfo from the network database, which will tell them whether " -"they \n" -"can connect directly (e.g. the peer has a publicly reachable interface) \n" -"or whether they need to contact them indirectly. Direct connections occur" -" \n" -"as normal, while indirect connections are done through one of the " -"published \n" -"tunnels." -msgstr "" - -#: i2p2www/pages/site/get-involved/todo.html:97 -msgid "" -"When a router just wants to get a message or two to a specific hidden " -"peer, \n" -"they can just use the indirect tunnel for sending the payload. However, \n" -"if the router wants to talk to the hidden peer often (for instance, as " -"part \n" -"of a tunnel), they will send a garlic routed message through the indirect" -" \n" -"tunnel to that hidden peer which unwraps to contain a message which " -"should \n" -"be sent to the originating router. That hidden peer then establishes an \n" -"outbound connection to the originating router and from then on, those two" -" \n" -"routers can talk to each other directly over that newly established " -"direct \n" -"connection." -msgstr "" - -#: i2p2www/pages/site/get-involved/todo.html:108 -msgid "" -"Of course, that only works if the originating peer can receive " -"connections \n" -"(they aren't also hidden). However, if the originating peer is hidden, " -"they \n" -"can simply direct the garlic routed message to come back to the " -"originating \n" -"peer's inbound tunnel." -msgstr "" - -#: i2p2www/pages/site/get-involved/todo.html:114 -msgid "" -"This is not meant to provide a way for a peer's IP address to be " -"concealed, \n" -"merely as a way to let people behind firewalls and NATs fully operate " -"within \n" -"the network. Concealing the peer's IP address adds a little more work, as" -" \n" -"described below." -msgstr "" - -#: i2p2www/pages/site/get-involved/todo.html:120 -msgid "" -"With this technique, any router can participate as any part of a tunnel." -" \n" -"For efficiency purposes, a hidden peer would be a bad choice for an " -"inbound \n" -"gateway, and within any given tunnel, two neighboring peers wouldn't want" -" \n" -"to be hidden. But that is not technically necessary." -msgstr "" - -#: i2p2www/pages/site/get-involved/todo.html:132 -msgid "Both UDP and NIO have been Implemented in I2P" -msgstr "Sia UDP che NIO sono stati implementati in I2P" - -#: i2p2www/pages/site/get-involved/todo.html:133 -msgid "" -"Standard TCP communication in Java generally requires blocking socket \n" -"calls, and to keep a blocked socket from hanging the entire system, those" -" \n" -"blocking calls are done on their own threads. Our current TCP transport \n" -"is implemented in a naive fashion - for each peer we are talking to, we \n" -"have one thread reading and one thread writing. The reader thread simply" -" \n" -"loops a bunch of read() calls, building I2NP messages and adding them \n" -"to our internal inbound message queue, and the writer thread pulls " -"messages \n" -"off a per-connection outbound message queue and shoves the data through \n" -"write() calls." -msgstr "" - -#: i2p2www/pages/site/get-involved/todo.html:144 -msgid "" -"We do this fairly efficiently, from a CPU perspective - at any time, \n" -"almost all of these threads are sitting idle, blocked waiting for " -"something \n" -"to do. However, each thread consumes real resources (on older Linux " -"kernels, \n" -"for instance, each thread would often be implemented as a fork()'ed " -"process). \n" -"As the network grows, the number of peers each router will want to talk \n" -"with will increase (remember, I2P is fully connected, meaning that any \n" -"given peer should know how to get a message to any other peer, and " -"restricted \n" -"route support will probably not significantly reduce the number of " -"connections \n" -"necessary). This means that with a 100,000 router network, each router \n" -"will have up to 199,998 threads just to deal with the TCP connections!" -msgstr "" - -#: i2p2www/pages/site/get-involved/todo.html:156 -msgid "" -"Obviously, that just won't work. We need to use a transport layer that \n" -"can scale. In Java, we have two main camps:" -msgstr "" - -#: i2p2www/pages/site/get-involved/todo.html:161 -#, python-format -msgid "" -"Implemented in I2P 0.6 (\"SSU\") as documented elsewhere" -msgstr "" -"Implementato in I2P 0.6.0.6 (\"SSU\") come documentato altrove" - -#: i2p2www/pages/site/get-involved/todo.html:164 -msgid "" -"Sending and receiving UDP datagrams is a connectionless operation - if \n" -"we are communicating with 100,000 peers, we simply stick the UDP packets" -" \n" -"in a queue and have a single thread pulling them off the queue and " -"shoving \n" -"them out the pipe (and to receive, have a single thread pulling in any \n" -"UDP packets received and adding them to an inbound queue)." -msgstr "" - -#: i2p2www/pages/site/get-involved/todo.html:171 -msgid "" -"However, moving to UDP means losing the benefits of TCP's ordering, " -"congestion \n" -"control, MTU discovery, etc. Implementing that code will take significant" -" \n" -"work, however I2P doesn't need it to be as strong as TCP. Specifically, \n" -"a while ago I was taking some measurements in the simulator and on the \n" -"live net, and the vast majority of messages transferred would fit easily" -" \n" -"within a single unfragmented UDP packet, and the largest of the messages" -" \n" -"would fit within 20-30 packets. As mule pointed out, TCP adds a " -"significant \n" -"overhead when dealing with so many small packets, as the ACKs are within" -" \n" -"an order of magnitude in size. With UDP, we can optimize the transport \n" -"for both efficiency and resilience by taking into account I2P's " -"particular \n" -"needs." -msgstr "" - -#: i2p2www/pages/site/get-involved/todo.html:184 -msgid "It will be a lot of work though." -msgstr "Tuttavia richiederebbe molto lavoro." - -#: i2p2www/pages/site/get-involved/todo.html:187 -msgid "NIO or NBIO" -msgstr "NIO o NBIO" - -#: i2p2www/pages/site/get-involved/todo.html:188 -msgid "NIO Implemented in I2P 0.6.1.22 (\"NTCP\")" -msgstr "NIO implementato in I2P 0.6.1.22 (\"NTCP\")" - -#: i2p2www/pages/site/get-involved/todo.html:191 -msgid "" -"In Java 1.4, a set of \"New I/O\" packages was introduced, allowing Java" -" \n" -"developers to take advantage of the operating system's nonblocking IO \n" -"capabilities - allowing you to maintain a large number of concurrent IO \n" -"operations without requiring a separate thread for each. There is much \n" -"promise with this approach, as we can scalable handle a large number of \n" -"concurrent connections and we don't have to write a mini-TCP stack with \n" -"UDP. However, the NIO packages have not proven themselves to be battle-" -"ready, \n" -"as the Freenet developer's found. In addition, requiring NIO support " -"would \n" -"mean we can't run on any of the open source JVMs like Kaffe, \n" -"as GNU/Classpath has only " -"limited \n" -"support for NIO. (note: this may not be the case anymore, as there \n" -"has been some progress on Classpath's NIO, but it is an unknown " -"quantity)" -msgstr "" - -#: i2p2www/pages/site/get-involved/todo.html:205 -#, python-format -msgid "" -"Another alternative along the same lines is the Non" -" \n" -"Blocking I/O package - essentially a cleanroom NIO implementation \n" -"(written before NIO was around). It works by using some native OS code \n" -"to do the nonblocking IO, passing off events through Java. It seems to \n" -"be working with Kaffe, though there doesn't seem to be much development \n" -"activity on it lately (likely due to 1.4's NIO deployment)." -msgstr "" - -#: i2p2www/pages/site/get-involved/todo.html:220 +#: i2p2www/pages/site/get-involved/todo.html:44 msgid "" "Within the current network database and profile management " "implementation, \n" @@ -792,152 +525,14 @@ msgid "" "code yet, since we aren't going to need it for a while." msgstr "" -#: i2p2www/pages/site/get-involved/todo.html:235 +#: 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" "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:247 -#: i2p2www/pages/site/get-involved/todo.html:331 -#, python-format -msgid "" -"Addressed in I2P 0.5 as documented elsewhere" -msgstr "" - -#: i2p2www/pages/site/get-involved/todo.html:250 -msgid "" -"Right now, if Alice builds a four hop inbound tunnel starting at Elvis, \n" -"going to Dave, then to Charlie, then Bob, and finally Alice " -"(A<--B<--C<--D<--E), \n" -"all five of them will know they are participating in tunnel \"123\", as \n" -"the messages are tagged as such. What we want to do is give each hop " -"their \n" -"own unique tunnel hop ID - Charlie will receive messages on tunnel 234 \n" -"and forward them to tunnel 876 on Bob. The intent is to prevent Bob or \n" -"Charlie from knowing that they are in Alice's tunnel, as if each hop in \n" -"the tunnel had the same tunnel ID, collusion attacks aren't much work." -msgstr "" - -#: i2p2www/pages/site/get-involved/todo.html:260 -msgid "" -"Adding a unique tunnel ID per hop isn't hard, but by itself, " -"insufficient. \n" -"If Dave and Bob are under the control of the same attacker, they wouldn't" -" \n" -"be able to tell they are in the same tunnel due to the tunnel ID, but \n" -"would be able to tell by the message bodies and verification structures \n" -"by simply comparing them. To prevent that, the tunnel must use layered \n" -"encryption along the path, both on the payload of the tunneled message \n" -"and on the verification structure (used to prevent simple tagging " -"attacks). \n" -"This requires some simple modifications to the TunnelMessage, as well \n" -"as the inclusion of per-hop secret keys delivered during tunnel creation" -" \n" -"and given to the tunnel's gateway. We must fix a maximum tunnel length \n" -"(e.g. 16 hops) and instruct the gateway to encrypt the message to each \n" -"of the 16 delivered secret keys, in reverse order, and to encrypt the \n" -"signature of the hash of the (encrypted) payload at each step. The " -"gateway \n" -"then sends that 16-step encrypted message, along with a 16-step and " -"16-wide \n" -"encrypted mapping to the first hop, which then decrypts the mapping and \n" -"the payload with their secret key, looking in the 16-wide mapping for \n" -"the entry associated with their own hop (keyed by the per-hop tunnel ID)" -" \n" -"and verifying the payload by checking it against the associated signed \n" -"hash." -msgstr "" - -#: i2p2www/pages/site/get-involved/todo.html:281 -msgid "" -"The tunnel gateway does still have more information than the other peers" -" \n" -"in the tunnel, and compromising both the gateway and a tunnel participant" -" \n" -"would allow those peers to collude, exposing the fact that they are both" -" \n" -"in the same tunnel. In addition, neighboring peers know that they are \n" -"in the same tunnel anyway, as they know who they send the message to (and" -" \n" -"with IP-based transports without restricted routes, they know who they \n" -"got it from). However, the above two techniques significantly increase \n" -"the cost of gaining meaningful samples when dealing with longer tunnels." -msgstr "" - -#: i2p2www/pages/site/get-involved/todo.html:297 -msgid "Implemented in release 0.6.2" -msgstr "Implementato nella versione 0.6.2" - -#: i2p2www/pages/site/get-involved/todo.html:300 -#, python-format -msgid "" -"As Connelly proposed to deal with the\n" -"predecessor attack (2008\n" -"update), keeping the order of peers within our tunnels consistent \n" -"(aka whenever Alice creates a tunnel with both Bob and Charlie in it, \n" -"Bob's next hop is always Charlie), we address the issue as Bob doesn't \n" -"get to substantially sample Alice's peer selection group. We may even \n" -"want to explicitly allow Bob to participate in Alice's tunnels in only \n" -"one way - receiving a message from Dave and sending it to Charlie - and \n" -"if any of those peers are not available to participate in the tunnel (due" -" \n" -"to overload, network disconnection, etc), avoid asking Bob to participate" -" \n" -"in any tunnels until they are back online." -msgstr "" - -#: i2p2www/pages/site/get-involved/todo.html:315 -msgid "" -"More analysis is necessary for revising the tunnel creation - at the \n" -"moment, we simply select and order randomly within the peer's top tier \n" -"of peers (ones with fast + high capacity)." -msgstr "" - -#: i2p2www/pages/site/get-involved/todo.html:320 -msgid "" -"Adding a strict ordering to peers in a tunnel also improves the anonymity" -" \n" -"of peers with 0-hop tunnels, as otherwise the fact that a peer's gateway" -" \n" -"is always the same would be particularly damning. However, peers with \n" -"0-hop tunnels may want to periodically use a 1-hop tunnel to simulate \n" -"the failure of a normally reliable gateway peer (so every MTBF*(tunnel \n" -"duration) minutes, use a 1-hop tunnel)." -msgstr "" - -#: i2p2www/pages/site/get-involved/todo.html:337 -msgid "" -"Without tunnel length permutation, if someone were to somehow detect that" -" \n" -"a destination had a particular number of hops, it might be able to use " -"that \n" -"information to identify the router the destination is located on, per the" -" \n" -"predecessor attack. For instance, if everyone has 2-hop tunnels, if Bob \n" -"receives a tunnel message from Charlie and forwards it to Alice, Bob " -"knows \n" -"Alice is the final router in the tunnel. If Bob were to identify what " -"destination \n" -"that tunnel served (by means of colluding with the gateway and harvesting" -" \n" -"the network database for all of the LeaseSets), he would know the router" -" \n" -"on which that destination is located (and without restricted routes, that" -" \n" -"would mean what IP address the destination is on)." -msgstr "" - -#: i2p2www/pages/site/get-involved/todo.html:349 -msgid "" -"It is to counter user behavior that tunnel lengths should be permuted, \n" -"using algorithms based on the length requested (for example, the 1/MTBF \n" -"length change for 0-hop tunnels outlined above)." -msgstr "" - -#: i2p2www/pages/site/get-involved/todo.html:359 +#: i2p2www/pages/site/get-involved/todo.html:71 msgid "" "The restricted route functionality described before was simply a " "functional \n" @@ -959,7 +554,7 @@ msgid "" "to forward it as requested." msgstr "" -#: i2p2www/pages/site/get-involved/todo.html:378 +#: i2p2www/pages/site/get-involved/todo.html:90 #, python-format msgid "" "Within the network, we will want some way to deter people from consuming" @@ -973,7 +568,7 @@ msgid "" "to make certain requests \"expensive\"." msgstr "" -#: i2p2www/pages/site/get-involved/todo.html:386 +#: 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 " @@ -991,7 +586,7 @@ msgid "" "with few resources." msgstr "" -#: i2p2www/pages/site/get-involved/todo.html:397 +#: 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" @@ -999,7 +594,7 @@ msgid "" "appropriate." msgstr "" -#: i2p2www/pages/site/get-involved/todo.html:407 +#: i2p2www/pages/site/get-involved/todo.html:119 #, python-format msgid "" "To powerful passive external observers as well as large colluding " @@ -1020,7 +615,7 @@ msgid "" "tunnel mixing strategies." msgstr "" -#: i2p2www/pages/site/get-involved/todo.html:420 +#: 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" @@ -1038,7 +633,7 @@ msgid "" "available." msgstr "" -#: i2p2www/pages/site/get-involved/todo.html:433 +#: i2p2www/pages/site/get-involved/todo.html:145 msgid "" "In addition, we may want to implement code to dynamically reroute tunnels" " \n" @@ -1048,7 +643,7 @@ msgid "" "with instructions to redefine the next-hop in the tunnel." msgstr "" -#: i2p2www/pages/site/get-involved/todo.html:444 +#: 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" @@ -1063,7 +658,7 @@ msgid "" "clove exposed includes delay instructions." msgstr "" -#: i2p2www/pages/site/get-involved/todo.html:456 +#: i2p2www/pages/site/get-involved/todo.html:168 #, python-format msgid "" "Performance related improvements are listed on the\n" @@ -4219,3 +3814,14 @@ msgstr "" "Il canale #i2p'dev su IRC o il forum" " di traduzione su %(zzz)s." + + + + + + + + + + + diff --git a/i2p2www/translations/pt_BR/LC_MESSAGES/docs.po b/i2p2www/translations/pt_BR/LC_MESSAGES/docs.po index 7ce82245..99d0f6c6 100644 --- a/i2p2www/translations/pt_BR/LC_MESSAGES/docs.po +++ b/i2p2www/translations/pt_BR/LC_MESSAGES/docs.po @@ -12,7 +12,7 @@ msgid "" msgstr "" "Project-Id-Version: I2P\n" "Report-Msgid-Bugs-To: http://trac.i2p2.de\n" -"POT-Creation-Date: 2014-11-16 02:59+0000\n" +"POT-Creation-Date: 2014-11-27 12:12+0000\n" "PO-Revision-Date: 2014-11-26 19:06+0000\n" "Last-Translator: blueboy\n" "Language-Team: Portuguese (Brazil) " @@ -31,7 +31,9 @@ msgstr "Índice da Documentação Técnica" #: i2p2www/pages/site/docs/applications/embedding.html:3 #: i2p2www/pages/site/docs/how/cryptography.html:3 #: i2p2www/pages/site/docs/protocol/i2cp.html:3 +#: i2p2www/pages/site/docs/spec/configuration.html:3 #: i2p2www/pages/site/docs/spec/updates.html:3 +#: i2p2www/pages/site/docs/transport/ntcp.html:3 msgid "November 2014" msgstr "Novembro de 2014" @@ -146,7 +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:217 +#: i2p2www/pages/site/docs/index.html:44 i2p2www/pages/site/docs/index.html:222 msgid "Embedding the router in your application" msgstr "" @@ -163,7 +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:189 +#: 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" @@ -183,27 +185,32 @@ msgstr "" msgid "Application Development Overview and Guide" msgstr "Guia e Visão Geral do Desenvolvimento de Aplicações" -#: i2p2www/pages/site/docs/index.html:72 +#: i2p2www/pages/site/docs/index.html:58 +#: i2p2www/pages/site/docs/api/i2ptunnel.html:55 +msgid "I2PTunnel Configuration" +msgstr "" + +#: i2p2www/pages/site/docs/index.html:74 msgid "SAM Protocol" msgstr "Protocolo SAM" -#: i2p2www/pages/site/docs/index.html:74 +#: i2p2www/pages/site/docs/index.html:76 msgid "SAMv2 Protocol" msgstr "Protocolo SAMv2" -#: i2p2www/pages/site/docs/index.html:76 +#: i2p2www/pages/site/docs/index.html:78 msgid "SAMv3 Protocol" msgstr "Protocolo SAMv3" -#: i2p2www/pages/site/docs/index.html:78 +#: i2p2www/pages/site/docs/index.html:80 msgid "BOB Protocol" msgstr "Protocolo BOB" -#: i2p2www/pages/site/docs/index.html:81 +#: i2p2www/pages/site/docs/index.html:83 msgid "End-to-End Transport API and Protocols" msgstr "API do transporte ponta-a-ponta e Protocolos" -#: i2p2www/pages/site/docs/index.html:82 +#: i2p2www/pages/site/docs/index.html:84 msgid "" "The end-to-end protocols used by clients for reliable and unreliable " "communication." @@ -211,33 +218,33 @@ 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:84 +#: i2p2www/pages/site/docs/index.html:86 #: i2p2www/pages/site/docs/api/streaming.html:2 msgid "Streaming Library" msgstr "Biblioteca de streamings" -#: i2p2www/pages/site/docs/index.html:86 +#: i2p2www/pages/site/docs/index.html:88 msgid "Streaming Protocol Specification" msgstr "Especificação do protocolo de streaming" -#: i2p2www/pages/site/docs/index.html:88 +#: i2p2www/pages/site/docs/index.html:90 msgid "Streaming Javadoc" msgstr "Javadoc da biblioteca de streamings" -#: i2p2www/pages/site/docs/index.html:90 +#: i2p2www/pages/site/docs/index.html:92 #: i2p2www/pages/site/docs/api/datagrams.html:2 msgid "Datagrams" msgstr "Datagramas" -#: i2p2www/pages/site/docs/index.html:92 +#: i2p2www/pages/site/docs/index.html:94 msgid "Datagram Javadoc" msgstr "Datagrama Javadoc" -#: i2p2www/pages/site/docs/index.html:95 +#: i2p2www/pages/site/docs/index.html:97 msgid "Client-to-Router Interface API and Protocol" msgstr "API e protocolo de Interface Cliente-para-Roteador" -#: i2p2www/pages/site/docs/index.html:96 +#: 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" @@ -247,54 +254,54 @@ msgstr "" "receber trafego para um roteador. Tradicionalmente usado apenas por " "aplicações Java e APIs de alto-nível." -#: i2p2www/pages/site/docs/index.html:101 +#: i2p2www/pages/site/docs/index.html:103 msgid "I2CP - I2P Control Protocol / API overview" msgstr "I2CP - Protocolo de Controle da I2P / Uma visão geral da API" -#: i2p2www/pages/site/docs/index.html:103 +#: i2p2www/pages/site/docs/index.html:105 msgid "I2CP Specification" msgstr "Especificação do I2CP" -#: i2p2www/pages/site/docs/index.html:105 +#: i2p2www/pages/site/docs/index.html:107 msgid "I2CP API Javadoc" msgstr "Javadoc da API do I2CP" -#: i2p2www/pages/site/docs/index.html:107 -#: i2p2www/pages/site/docs/index.html:136 +#: i2p2www/pages/site/docs/index.html:109 +#: i2p2www/pages/site/docs/index.html:139 msgid "Common data structures specification" msgstr "Especificação das estruturas de dados comuns" -#: i2p2www/pages/site/docs/index.html:109 -#: i2p2www/pages/site/docs/index.html:138 +#: i2p2www/pages/site/docs/index.html:111 +#: i2p2www/pages/site/docs/index.html:141 msgid "Data Structures Javadoc" msgstr "Javadoc das Estruturas de Dados" -#: i2p2www/pages/site/docs/index.html:112 +#: i2p2www/pages/site/docs/index.html:114 msgid "End-to-End Encryption" msgstr "Criptografia de ponta a ponta" -#: i2p2www/pages/site/docs/index.html:113 +#: 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" -#: i2p2www/pages/site/docs/index.html:115 +#: i2p2www/pages/site/docs/index.html:117 msgid "ElGamal/AES+SessionTag encryption" msgstr "Criptografia ElGamal/AES+SessionTag" -#: i2p2www/pages/site/docs/index.html:116 -#: i2p2www/pages/site/docs/index.html:149 +#: i2p2www/pages/site/docs/index.html:118 +#: i2p2www/pages/site/docs/index.html:152 msgid "ElGamal and AES cryptography details" msgstr "Detalhes sobre as criptografias AES e ElGamal" -#: i2p2www/pages/site/docs/index.html:119 +#: i2p2www/pages/site/docs/index.html:121 #: i2p2www/pages/site/docs/how/tech-intro.html:15 #: i2p2www/pages/site/docs/how/tech-intro.html:329 msgid "Network Database" msgstr "Banco de dados da rede" -#: i2p2www/pages/site/docs/index.html:120 +#: i2p2www/pages/site/docs/index.html:122 msgid "" "Distributed storage and retrieval of information about routers and " "clients." @@ -302,23 +309,29 @@ msgstr "" "Armazenamento distribuído e recuperação de informações relativas aos " "roteadores e clientes." -#: i2p2www/pages/site/docs/index.html:122 +#: i2p2www/pages/site/docs/index.html:124 msgid "Network database overview, details, and threat analysis" msgstr "Uma visão geral do banco de dados da rede, detalhes e análise de risco" -#: i2p2www/pages/site/docs/index.html:123 +#: i2p2www/pages/site/docs/index.html:125 msgid "Cryptographic hashes" msgstr "Hashes criptográficas" -#: i2p2www/pages/site/docs/index.html:124 +#: i2p2www/pages/site/docs/index.html:126 msgid "Cryptographic signatures" msgstr "Assinaturas criptográficas" #: i2p2www/pages/site/docs/index.html:127 +#: i2p2www/pages/site/docs/index.html:186 +#, fuzzy +msgid "Router reseed specification" +msgstr "Especificação para a construção de túneis" + +#: i2p2www/pages/site/docs/index.html:130 msgid "Router Message Protocol" msgstr "Protocolo de mensagens do roteador" -#: i2p2www/pages/site/docs/index.html:128 +#: i2p2www/pages/site/docs/index.html:131 msgid "" "I2P is a message-oriented router. The messages sent between routers are " "defined by the I2NP protocol." @@ -326,25 +339,25 @@ 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:130 +#: i2p2www/pages/site/docs/index.html:133 msgid "I2NP - I2P Network Protocol Overview" msgstr "I2NP - Uma visão geral do protocolo de rede I2P" -#: i2p2www/pages/site/docs/index.html:132 +#: i2p2www/pages/site/docs/index.html:135 msgid "I2NP Specification" msgstr "Especificação do I2NP" -#: i2p2www/pages/site/docs/index.html:134 +#: i2p2www/pages/site/docs/index.html:137 msgid "I2NP Javadoc" msgstr "Javadoc do I2NP" -#: i2p2www/pages/site/docs/index.html:141 +#: i2p2www/pages/site/docs/index.html:144 #: i2p2www/pages/site/docs/how/tech-intro.html:14 #: i2p2www/pages/site/docs/how/tech-intro.html:228 msgid "Tunnels" msgstr "Túneis" -#: i2p2www/pages/site/docs/index.html:142 +#: i2p2www/pages/site/docs/index.html:145 msgid "" "Selecting peers, requesting tunnels through those peers, and encrypting " "and routing messages through these tunnels." @@ -352,152 +365,152 @@ 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:144 +#: i2p2www/pages/site/docs/index.html:147 msgid "Peer profiling and selection" msgstr "" -#: i2p2www/pages/site/docs/index.html:145 +#: i2p2www/pages/site/docs/index.html:148 msgid "Tunnel routing overview" msgstr "Uma visão geral do roteamento via túneis" -#: i2p2www/pages/site/docs/index.html:146 +#: i2p2www/pages/site/docs/index.html:149 msgid "Garlic routing and \"garlic\" terminology" msgstr "Roteamento e terminologia \"garlic\"" -#: i2p2www/pages/site/docs/index.html:147 +#: i2p2www/pages/site/docs/index.html:150 msgid "Tunnel building and encryption" msgstr "Construção de túneis e criptografia" -#: i2p2www/pages/site/docs/index.html:148 +#: i2p2www/pages/site/docs/index.html:151 msgid "ElGamal/AES" msgstr "ElGamal/AES" -#: i2p2www/pages/site/docs/index.html:148 +#: i2p2www/pages/site/docs/index.html:151 msgid "for build request encryption" msgstr "para construir requisição de encriptação" -#: i2p2www/pages/site/docs/index.html:150 +#: i2p2www/pages/site/docs/index.html:153 msgid "Tunnel building specification" msgstr "Especificação para a construção de túneis" -#: i2p2www/pages/site/docs/index.html:151 +#: i2p2www/pages/site/docs/index.html:154 msgid "Low-level tunnel message specification" msgstr "Especificação da mensagem de túnel de baixo-nível" -#: i2p2www/pages/site/docs/index.html:152 +#: i2p2www/pages/site/docs/index.html:155 #: i2p2www/pages/site/docs/tunnels/unidirectional.html:2 msgid "Unidirectional Tunnels" msgstr "Túneis unidirecionais" -#: i2p2www/pages/site/docs/index.html:153 +#: i2p2www/pages/site/docs/index.html:156 #: i2p2www/pages/site/docs/how/peer-selection.html:299 msgid "Peer Profiling and Selection in the I2P Anonymous Network" msgstr "" -#: i2p2www/pages/site/docs/index.html:154 +#: i2p2www/pages/site/docs/index.html:157 msgid "2009 paper (pdf), not current but still generally accurate" msgstr "artigo de 2009 (pdf), desatualizado mas, em linhas gerais, ainda correto" -#: i2p2www/pages/site/docs/index.html:157 +#: i2p2www/pages/site/docs/index.html:160 msgid "Transport Layer" msgstr "Camada de transporte" -#: i2p2www/pages/site/docs/index.html:158 +#: 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" -#: i2p2www/pages/site/docs/index.html:160 +#: i2p2www/pages/site/docs/index.html:163 msgid "Transport layer overview" msgstr "Uma visão geral da camada de transporte" -#: i2p2www/pages/site/docs/index.html:162 +#: i2p2www/pages/site/docs/index.html:165 msgid "TCP-based transport overview and specification" msgstr "Especificação e visão geral do transporte baseado em TCP" -#: i2p2www/pages/site/docs/index.html:164 +#: i2p2www/pages/site/docs/index.html:167 msgid "UDP-based transport overview" msgstr "Uma visão geral do transporte baseado em UDP" -#: i2p2www/pages/site/docs/index.html:166 +#: i2p2www/pages/site/docs/index.html:169 msgid "SSU specification" msgstr "Especificação SSU" -#: i2p2www/pages/site/docs/index.html:168 +#: i2p2www/pages/site/docs/index.html:171 msgid "NTCP transport encryption" msgstr "Criptografia de transporte NTCP" -#: i2p2www/pages/site/docs/index.html:170 +#: i2p2www/pages/site/docs/index.html:173 msgid "SSU transport encryption" msgstr "Criptografia do transporte SSU" -#: i2p2www/pages/site/docs/index.html:172 +#: i2p2www/pages/site/docs/index.html:175 msgid "Transport Javadoc" msgstr "Javadoc da biblioteca de transporte" -#: i2p2www/pages/site/docs/index.html:174 +#: i2p2www/pages/site/docs/index.html:177 msgid "NTCP Javadoc" msgstr "Javadoc do NTCP" -#: i2p2www/pages/site/docs/index.html:176 +#: i2p2www/pages/site/docs/index.html:179 msgid "SSU Javadoc" msgstr "" -#: i2p2www/pages/site/docs/index.html:179 +#: i2p2www/pages/site/docs/index.html:182 msgid "Other Router Topics" msgstr "Outros tópicos sobre o roteador" -#: i2p2www/pages/site/docs/index.html:181 +#: i2p2www/pages/site/docs/index.html:184 msgid "Router software updates" msgstr "Atualizações do software do roteador" -#: i2p2www/pages/site/docs/index.html:183 +#: i2p2www/pages/site/docs/index.html:188 msgid "Native BigInteger Library" msgstr "Biblioteca BigInteger nativa" -#: i2p2www/pages/site/docs/index.html:185 +#: i2p2www/pages/site/docs/index.html:190 msgid "Time synchronization and NTP" msgstr "Sincronização de tempo e NTP" -#: i2p2www/pages/site/docs/index.html:187 +#: i2p2www/pages/site/docs/index.html:192 msgid "Performance" msgstr "Desempenho" -#: i2p2www/pages/site/docs/index.html:194 +#: i2p2www/pages/site/docs/index.html:199 msgid "Developer's Guides and Resources" msgstr "Guia para Desenvolvedores e Recursos" -#: i2p2www/pages/site/docs/index.html:196 +#: i2p2www/pages/site/docs/index.html:201 msgid "New Developer's Guide" msgstr "Guia para novos desenvolvedores" -#: i2p2www/pages/site/docs/index.html:198 +#: i2p2www/pages/site/docs/index.html:203 msgid "New Translator's Guide" msgstr "Guia para os novos tradutores" -#: i2p2www/pages/site/docs/index.html:200 +#: i2p2www/pages/site/docs/index.html:205 msgid "Monotone Guide" msgstr "Guia do Monotone" -#: i2p2www/pages/site/docs/index.html:202 +#: i2p2www/pages/site/docs/index.html:207 msgid "Developer Guidelines" msgstr "Diretrizes para os desenvolvedores" -#: i2p2www/pages/site/docs/index.html:204 +#: i2p2www/pages/site/docs/index.html:209 msgid "Javadocs on the standard internet:" msgstr "" -#: i2p2www/pages/site/docs/index.html:205 -#: i2p2www/pages/site/docs/index.html:209 #: i2p2www/pages/site/docs/index.html:210 -#: i2p2www/pages/site/docs/index.html:211 +#: i2p2www/pages/site/docs/index.html:214 +#: i2p2www/pages/site/docs/index.html:215 +#: i2p2www/pages/site/docs/index.html:216 #, python-format msgid "Server %(num)s" msgstr "Servidor %(num)s" -#: i2p2www/pages/site/docs/index.html:206 -#: i2p2www/pages/site/docs/index.html:215 +#: i2p2www/pages/site/docs/index.html:211 +#: i2p2www/pages/site/docs/index.html:220 msgid "" "Note: always verify that javadocs are current by checking the release " "number." @@ -505,66 +518,66 @@ msgstr "" "Nota: sempre verifique qual javadocs é o atual, verificando o número do " "lançamento." -#: i2p2www/pages/site/docs/index.html:208 +#: i2p2www/pages/site/docs/index.html:213 msgid "Javadocs inside I2P:" msgstr "Javadocs na I2P:" -#: i2p2www/pages/site/docs/index.html:219 +#: i2p2www/pages/site/docs/index.html:224 msgid "Ports used by I2P" msgstr "Portas usadas pela I2P" -#: i2p2www/pages/site/docs/index.html:221 +#: 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" -#: i2p2www/pages/site/docs/index.html:223 +#: i2p2www/pages/site/docs/index.html:228 msgid "Updating the wrapper manually" msgstr "Atualizando o empacotador manualmente" -#: i2p2www/pages/site/docs/index.html:225 +#: i2p2www/pages/site/docs/index.html:230 msgid "User forum" msgstr "Fórum de usuários" -#: i2p2www/pages/site/docs/index.html:227 +#: i2p2www/pages/site/docs/index.html:232 msgid "Developer forum inside I2P" msgstr "Fórum de desenvolvedores na I2P" -#: i2p2www/pages/site/docs/index.html:229 +#: i2p2www/pages/site/docs/index.html:234 msgid "Bug tracker" msgstr "Acompanhamento de falhas" -#: i2p2www/pages/site/docs/index.html:231 +#: i2p2www/pages/site/docs/index.html:236 msgid "Viewmtn inside I2P" msgstr "" -#: i2p2www/pages/site/docs/index.html:233 +#: i2p2www/pages/site/docs/index.html:238 msgid "I2P Source exported to GitHub" msgstr "Código-fonte da I2P exportado para o GitHub" -#: i2p2www/pages/site/docs/index.html:235 +#: i2p2www/pages/site/docs/index.html:240 msgid "I2P Source Git Repo inside I2P" msgstr "Repositório Git de código-fonte da I2P dentro da I2P" -#: i2p2www/pages/site/docs/index.html:237 +#: i2p2www/pages/site/docs/index.html:242 msgid "Source translation at Transifex" msgstr "Tradução do código-fonte no Transifex" -#: i2p2www/pages/site/docs/index.html:239 +#: i2p2www/pages/site/docs/index.html:244 msgid "Roadmap wiki" msgstr "Wiki do plano de ação" -#: i2p2www/pages/site/docs/index.html:241 +#: i2p2www/pages/site/docs/index.html:246 msgid "Old roadmap" msgstr "Plano de ação antigo" -#: i2p2www/pages/site/docs/index.html:241 -#: i2p2www/pages/site/docs/index.html:243 +#: i2p2www/pages/site/docs/index.html:246 +#: i2p2www/pages/site/docs/index.html:248 msgid "not current" msgstr "em desuso" -#: i2p2www/pages/site/docs/index.html:243 +#: i2p2www/pages/site/docs/index.html:248 msgid "To Do List" msgstr "Lista de tarefas por fazer" @@ -845,7 +858,7 @@ msgid "" msgstr "" #: i2p2www/pages/site/docs/naming.html:183 -#: i2p2www/pages/site/docs/spec/configuration.html:170 +#: i2p2www/pages/site/docs/spec/configuration.html:184 msgid "Addressbook" msgstr "Livro de endereços" @@ -1220,7 +1233,7 @@ msgid "" msgstr "" #: i2p2www/pages/site/docs/plugins.html:2 -#: i2p2www/pages/site/docs/spec/configuration.html:138 +#: i2p2www/pages/site/docs/spec/configuration.html:152 msgid "Plugins" msgstr "Extensões" @@ -2601,15 +2614,20 @@ msgid "" msgstr "" #: i2p2www/pages/site/docs/api/i2ptunnel.html:54 +#, fuzzy +msgid "Configuration" +msgstr "Formato do arquivo de configuração" + +#: i2p2www/pages/site/docs/api/i2ptunnel.html:58 msgid "Client Modes" msgstr "" -#: i2p2www/pages/site/docs/api/i2ptunnel.html:55 -#: i2p2www/pages/site/docs/api/i2ptunnel.html:137 +#: i2p2www/pages/site/docs/api/i2ptunnel.html:59 +#: i2p2www/pages/site/docs/api/i2ptunnel.html:141 msgid "Standard" msgstr "" -#: i2p2www/pages/site/docs/api/i2ptunnel.html:56 +#: 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" @@ -2617,7 +2635,7 @@ msgid "" " list of destinations." msgstr "" -#: i2p2www/pages/site/docs/api/i2ptunnel.html:62 +#: i2p2www/pages/site/docs/api/i2ptunnel.html:66 msgid "" "A HTTP-client tunnel. The tunnel connects to the destination specified by" " the URL\n" @@ -2625,34 +2643,34 @@ msgid "" "provided. Strips HTTP connections of the following headers:" msgstr "" -#: i2p2www/pages/site/docs/api/i2ptunnel.html:67 +#: 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 "" -#: i2p2www/pages/site/docs/api/i2ptunnel.html:75 +#: 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 "" -#: i2p2www/pages/site/docs/api/i2ptunnel.html:82 +#: 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 "" -#: i2p2www/pages/site/docs/api/i2ptunnel.html:86 +#: i2p2www/pages/site/docs/api/i2ptunnel.html:90 msgid "Outproxy:" msgstr "" -#: i2p2www/pages/site/docs/api/i2ptunnel.html:87 +#: i2p2www/pages/site/docs/api/i2ptunnel.html:91 msgid "Internal I2P use:" msgstr "" -#: i2p2www/pages/site/docs/api/i2ptunnel.html:92 +#: i2p2www/pages/site/docs/api/i2ptunnel.html:96 msgid "" "Creates a connection to a random IRC server specified by the comma " "seprated (\", \") \n" @@ -2660,43 +2678,43 @@ msgid "" "allowed due to anonymity concerns." msgstr "" -#: i2p2www/pages/site/docs/api/i2ptunnel.html:96 +#: i2p2www/pages/site/docs/api/i2ptunnel.html:100 msgid "Whitelist:" msgstr "" -#: i2p2www/pages/site/docs/api/i2ptunnel.html:111 +#: i2p2www/pages/site/docs/api/i2ptunnel.html:115 msgid "Enables using the I2P router as a SOCKS proxy." msgstr "" -#: i2p2www/pages/site/docs/api/i2ptunnel.html:116 +#: 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" "IRC client mode." msgstr "" -#: i2p2www/pages/site/docs/api/i2ptunnel.html:122 +#: 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 "" -#: i2p2www/pages/site/docs/api/i2ptunnel.html:128 +#: 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" "subscribe to a streamr server tunnel." msgstr "" -#: i2p2www/pages/site/docs/api/i2ptunnel.html:136 +#: i2p2www/pages/site/docs/api/i2ptunnel.html:140 msgid "Server Modes" msgstr "" -#: i2p2www/pages/site/docs/api/i2ptunnel.html:138 +#: i2p2www/pages/site/docs/api/i2ptunnel.html:142 msgid "Creates a destination to a local ip:port with an open TCP port." msgstr "" -#: i2p2www/pages/site/docs/api/i2ptunnel.html:143 +#: 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" @@ -2704,7 +2722,7 @@ msgid "" " such a request." msgstr "" -#: i2p2www/pages/site/docs/api/i2ptunnel.html:149 +#: 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" @@ -2713,14 +2731,14 @@ msgid "" "requests, or loopback-testing an eepsite as a diagnostic tool." msgstr "" -#: i2p2www/pages/site/docs/api/i2ptunnel.html:156 +#: i2p2www/pages/site/docs/api/i2ptunnel.html:160 msgid "" "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:162 +#: 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." @@ -3513,8 +3531,8 @@ msgstr "" #: i2p2www/pages/site/docs/how/tunnel-routing.html:255 #: i2p2www/pages/site/docs/protocol/i2cp.html:687 #: i2p2www/pages/site/docs/protocol/i2np.html:226 -#: i2p2www/pages/site/docs/spec/updates.html:438 -#: i2p2www/pages/site/docs/transport/ntcp.html:535 +#: i2p2www/pages/site/docs/spec/updates.html:488 +#: i2p2www/pages/site/docs/transport/ntcp.html:544 #: i2p2www/pages/site/docs/transport/ssu.html:554 #: i2p2www/pages/site/docs/tunnels/implementation.html:506 msgid "Future Work" @@ -4065,6 +4083,14 @@ 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)." +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" "If done wrong, it could cause real harm to our network.\n" @@ -4073,11 +4099,11 @@ msgid "" "This page discusses some general guidelines." msgstr "" -#: i2p2www/pages/site/docs/applications/embedding.html:18 +#: i2p2www/pages/site/docs/applications/embedding.html:23 msgid "Talk to us" msgstr "" -#: i2p2www/pages/site/docs/applications/embedding.html:19 +#: 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" @@ -4085,11 +4111,11 @@ msgid "" "everyone." msgstr "" -#: i2p2www/pages/site/docs/applications/embedding.html:25 +#: i2p2www/pages/site/docs/applications/embedding.html:30 msgid "Choose your router wisely" msgstr "" -#: i2p2www/pages/site/docs/applications/embedding.html:26 +#: 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" @@ -4099,19 +4125,19 @@ msgid "" "Some of the following only applies to the Java router." msgstr "" -#: i2p2www/pages/site/docs/applications/embedding.html:34 +#: i2p2www/pages/site/docs/applications/embedding.html:39 msgid "Licensing" msgstr "" -#: i2p2www/pages/site/docs/applications/embedding.html:35 +#: i2p2www/pages/site/docs/applications/embedding.html:40 msgid "Ensure you meet the license requirements of the software you are bundling." msgstr "" -#: i2p2www/pages/site/docs/applications/embedding.html:40 +#: i2p2www/pages/site/docs/applications/embedding.html:45 msgid "Verify default configuration" msgstr "" -#: i2p2www/pages/site/docs/applications/embedding.html:41 +#: i2p2www/pages/site/docs/applications/embedding.html:46 msgid "" "A correct default configuration is crucial. Most users will not change " "the defaults.\n" @@ -4120,7 +4146,7 @@ msgid "" "Override the router defaults if necessary." msgstr "" -#: i2p2www/pages/site/docs/applications/embedding.html:46 +#: i2p2www/pages/site/docs/applications/embedding.html:51 msgid "" "Some important defaults to review: Max bandwidth, tunnel quantity and " "length, max participating tunnels.\n" @@ -4128,7 +4154,7 @@ msgid "" "your app." msgstr "" -#: i2p2www/pages/site/docs/applications/embedding.html:50 +#: i2p2www/pages/site/docs/applications/embedding.html:55 msgid "" "Configure enough bandwidth and tunnels to allow your users to contribute " "to the network.\n" @@ -4138,11 +4164,11 @@ msgid "" "example." msgstr "" -#: i2p2www/pages/site/docs/applications/embedding.html:57 +#: i2p2www/pages/site/docs/applications/embedding.html:62 msgid "Participating Traffic Considerations" msgstr "" -#: i2p2www/pages/site/docs/applications/embedding.html:58 +#: 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, " @@ -4154,14 +4180,14 @@ msgid "" "tunnels." msgstr "" -#: i2p2www/pages/site/docs/applications/embedding.html:65 +#: 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" "which is helped tremendously by others building tunnels through you." msgstr "" -#: i2p2www/pages/site/docs/applications/embedding.html:69 +#: i2p2www/pages/site/docs/applications/embedding.html:74 msgid "" "Secondly, over 90% of the routers in the current network allow " "participating traffic.\n" @@ -4173,13 +4199,13 @@ msgid "" " people to enable relaying." msgstr "" -#: i2p2www/pages/site/docs/applications/embedding.html:76 +#: i2p2www/pages/site/docs/applications/embedding.html:81 msgid "" "Thirdly, participating traffic is cover traffic that helps your users' " "anonymity." msgstr "" -#: i2p2www/pages/site/docs/applications/embedding.html:79 +#: i2p2www/pages/site/docs/applications/embedding.html:84 msgid "" "We strongly discourage you from disabling participating traffic by " "default.\n" @@ -4187,11 +4213,11 @@ msgid "" "the network." msgstr "" -#: i2p2www/pages/site/docs/applications/embedding.html:85 +#: i2p2www/pages/site/docs/applications/embedding.html:90 msgid "Persistence" msgstr "" -#: i2p2www/pages/site/docs/applications/embedding.html:86 +#: 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" @@ -4201,11 +4227,11 @@ msgid "" "performance." msgstr "" -#: i2p2www/pages/site/docs/applications/embedding.html:94 +#: i2p2www/pages/site/docs/applications/embedding.html:99 msgid "Configurability" msgstr "" -#: i2p2www/pages/site/docs/applications/embedding.html:95 +#: i2p2www/pages/site/docs/applications/embedding.html:100 msgid "" "Give your users a way to change the configuration of the important " "settings.\n" @@ -4215,11 +4241,11 @@ msgid "" "IP/port may be helpful." msgstr "" -#: i2p2www/pages/site/docs/applications/embedding.html:103 +#: i2p2www/pages/site/docs/applications/embedding.html:108 msgid "Floodfill Considerations" msgstr "" -#: i2p2www/pages/site/docs/applications/embedding.html:104 +#: 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" @@ -4230,11 +4256,11 @@ msgid "" "It also depends on the typical uptime for your application." msgstr "" -#: i2p2www/pages/site/docs/applications/embedding.html:114 +#: i2p2www/pages/site/docs/applications/embedding.html:119 msgid "Reseeding" msgstr "" -#: i2p2www/pages/site/docs/applications/embedding.html:115 +#: 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 " @@ -4242,11 +4268,11 @@ msgid "" "Be aware of possible blocking by hostile governments." msgstr "" -#: i2p2www/pages/site/docs/applications/embedding.html:124 +#: i2p2www/pages/site/docs/applications/embedding.html:129 msgid "Reduce Network Resource Usage" msgstr "" -#: i2p2www/pages/site/docs/applications/embedding.html:125 +#: 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" @@ -4256,11 +4282,11 @@ msgid "" "tunnel, even in the presence of some background DHT activity." msgstr "" -#: i2p2www/pages/site/docs/applications/embedding.html:133 +#: i2p2www/pages/site/docs/applications/embedding.html:138 msgid "Updatability" msgstr "" -#: i2p2www/pages/site/docs/applications/embedding.html:134 +#: 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" @@ -4275,11 +4301,11 @@ msgid "" "which you presumably are not bundling." msgstr "" -#: i2p2www/pages/site/docs/applications/embedding.html:145 +#: i2p2www/pages/site/docs/applications/embedding.html:150 msgid "Rollout" msgstr "" -#: i2p2www/pages/site/docs/applications/embedding.html:146 +#: 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 " @@ -4295,11 +4321,11 @@ msgid "" "checklist is." msgstr "" -#: i2p2www/pages/site/docs/applications/embedding.html:158 +#: i2p2www/pages/site/docs/applications/embedding.html:163 msgid "Design for and Encourage Long Uptimes" msgstr "" -#: i2p2www/pages/site/docs/applications/embedding.html:159 +#: 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 " @@ -4308,53 +4334,53 @@ msgid "" "solution." msgstr "" -#: i2p2www/pages/site/docs/applications/embedding.html:167 +#: i2p2www/pages/site/docs/applications/embedding.html:172 msgid "Show Status" msgstr "" -#: i2p2www/pages/site/docs/applications/embedding.html:168 +#: i2p2www/pages/site/docs/applications/embedding.html:173 msgid "" "Provide some indication to the user that the application tunnels are " "ready. Encourage patience." msgstr "" -#: i2p2www/pages/site/docs/applications/embedding.html:173 +#: i2p2www/pages/site/docs/applications/embedding.html:178 msgid "Graceful Shutdown" msgstr "" -#: i2p2www/pages/site/docs/applications/embedding.html:174 +#: 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 "" -#: i2p2www/pages/site/docs/applications/embedding.html:180 +#: i2p2www/pages/site/docs/applications/embedding.html:185 msgid "Education and Donation" msgstr "" -#: i2p2www/pages/site/docs/applications/embedding.html:181 +#: 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 "" -#: i2p2www/pages/site/docs/applications/embedding.html:187 +#: i2p2www/pages/site/docs/applications/embedding.html:192 msgid "External Router Option" msgstr "" -#: i2p2www/pages/site/docs/applications/embedding.html:188 +#: 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 "" -#: i2p2www/pages/site/docs/applications/embedding.html:195 +#: i2p2www/pages/site/docs/applications/embedding.html:200 msgid "Use of other Common Services" msgstr "" -#: i2p2www/pages/site/docs/applications/embedding.html:196 +#: 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" @@ -4362,11 +4388,11 @@ msgid "" "and talk to the people who are running them to make sure it's ok." msgstr "" -#: i2p2www/pages/site/docs/applications/embedding.html:204 +#: i2p2www/pages/site/docs/applications/embedding.html:209 msgid "Time / NTP Issues" msgstr "" -#: i2p2www/pages/site/docs/applications/embedding.html:205 +#: 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. " @@ -4375,11 +4401,11 @@ msgid "" "clock is correct." msgstr "" -#: i2p2www/pages/site/docs/applications/embedding.html:213 +#: i2p2www/pages/site/docs/applications/embedding.html:218 msgid "Choose What and How you Bundle" msgstr "" -#: i2p2www/pages/site/docs/applications/embedding.html:214 +#: 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" @@ -4397,11 +4423,19 @@ msgid "" "and i2psnark, for example." msgstr "" -#: i2p2www/pages/site/docs/applications/embedding.html:228 +#: i2p2www/pages/site/docs/applications/embedding.html:233 +msgid "You may also wish to bundle a hosts.txt file." +msgstr "" + +#: i2p2www/pages/site/docs/applications/embedding.html:236 +msgid "Be sure to specify a Java 6 bootclasspath if compiling with Java 8." +msgstr "" + +#: i2p2www/pages/site/docs/applications/embedding.html:244 msgid "Datagram (DHT) considerations" msgstr "" -#: i2p2www/pages/site/docs/applications/embedding.html:229 +#: 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 " @@ -4417,32 +4451,32 @@ msgid "" "have several." msgstr "" -#: i2p2www/pages/site/docs/applications/embedding.html:242 +#: i2p2www/pages/site/docs/applications/embedding.html:258 msgid "Comarketing" msgstr "" -#: i2p2www/pages/site/docs/applications/embedding.html:243 +#: 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 "" -#: i2p2www/pages/site/docs/applications/embedding.html:249 +#: i2p2www/pages/site/docs/applications/embedding.html:265 msgid "Malware" msgstr "" -#: i2p2www/pages/site/docs/applications/embedding.html:250 +#: i2p2www/pages/site/docs/applications/embedding.html:266 msgid "" "Please don't use I2P for evil.\n" "It could cause great harm both to our network and our reputation." msgstr "" -#: i2p2www/pages/site/docs/applications/embedding.html:256 +#: i2p2www/pages/site/docs/applications/embedding.html:272 msgid "Join Us" msgstr "" -#: i2p2www/pages/site/docs/applications/embedding.html:257 +#: 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" @@ -4450,11 +4484,11 @@ msgid "" "We can help get you users, testers, translators, or even coders." msgstr "" -#: i2p2www/pages/site/docs/applications/embedding.html:265 +#: i2p2www/pages/site/docs/applications/embedding.html:281 msgid "Application Examples" msgstr "" -#: i2p2www/pages/site/docs/applications/embedding.html:266 +#: 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" @@ -4464,17 +4498,17 @@ msgid "" " and Monero." msgstr "" -#: i2p2www/pages/site/docs/applications/embedding.html:274 +#: i2p2www/pages/site/docs/applications/embedding.html:290 msgid "Code Example" msgstr "" -#: i2p2www/pages/site/docs/applications/embedding.html:275 +#: i2p2www/pages/site/docs/applications/embedding.html:291 msgid "" "None of the above actually tells you how to write your code to\n" "bundle the Java router, so following is a brief example." msgstr "" -#: i2p2www/pages/site/docs/applications/embedding.html:290 +#: 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" @@ -7340,7 +7374,6 @@ msgid "The Network Database" msgstr "" #: i2p2www/pages/site/docs/how/network-database.html:3 -#: i2p2www/pages/site/docs/transport/ntcp.html:3 msgid "October 2014" msgstr "" @@ -14594,10 +14627,6 @@ msgstr "" msgid "Configuration File Specification" msgstr "" -#: i2p2www/pages/site/docs/spec/configuration.html:3 -msgid "January 2014" -msgstr "Janeiro de 2014" - #: i2p2www/pages/site/docs/spec/configuration.html:7 msgid "" "This page provides a general specification of I2P configuration files,\n" @@ -14706,65 +14735,66 @@ msgid "Configured via /configlogging in the router console." msgstr "" #: i2p2www/pages/site/docs/spec/configuration.html:112 -#: i2p2www/pages/site/docs/spec/configuration.html:142 -#: i2p2www/pages/site/docs/spec/configuration.html:154 +#: i2p2www/pages/site/docs/spec/configuration.html:156 +#: i2p2www/pages/site/docs/spec/configuration.html:168 +#: i2p2www/pages/site/docs/spec/configuration.html:198 msgid "Properties are as follows:" msgstr "" -#: i2p2www/pages/site/docs/spec/configuration.html:133 +#: i2p2www/pages/site/docs/spec/configuration.html:147 msgid "Individual Plugin" msgstr "" -#: i2p2www/pages/site/docs/spec/configuration.html:134 +#: i2p2www/pages/site/docs/spec/configuration.html:148 #, python-format msgid "See the plugin specification." msgstr "" -#: i2p2www/pages/site/docs/spec/configuration.html:139 +#: i2p2www/pages/site/docs/spec/configuration.html:153 msgid "Enable/disable for each installed plugin." msgstr "" -#: i2p2www/pages/site/docs/spec/configuration.html:150 +#: i2p2www/pages/site/docs/spec/configuration.html:164 msgid "Webapps" msgstr "" -#: i2p2www/pages/site/docs/spec/configuration.html:151 +#: i2p2www/pages/site/docs/spec/configuration.html:165 msgid "Enable/disable for each installed webapp." msgstr "" -#: i2p2www/pages/site/docs/spec/configuration.html:163 +#: i2p2www/pages/site/docs/spec/configuration.html:177 msgid "Router" msgstr "" -#: i2p2www/pages/site/docs/spec/configuration.html:164 +#: i2p2www/pages/site/docs/spec/configuration.html:178 msgid "Configured via /configadvanced in the router console." msgstr "" -#: i2p2www/pages/site/docs/spec/configuration.html:168 +#: i2p2www/pages/site/docs/spec/configuration.html:182 msgid "Applications" msgstr "" -#: i2p2www/pages/site/docs/spec/configuration.html:171 +#: i2p2www/pages/site/docs/spec/configuration.html:185 msgid "See documentation in SusiDNS." msgstr "" -#: i2p2www/pages/site/docs/spec/configuration.html:176 +#: i2p2www/pages/site/docs/spec/configuration.html:190 msgid "Configured via the application gui." msgstr "" -#: i2p2www/pages/site/docs/spec/configuration.html:181 +#: i2p2www/pages/site/docs/spec/configuration.html:195 msgid "Configured via the /i2ptunnel application in the router console." msgstr "" -#: i2p2www/pages/site/docs/spec/configuration.html:185 +#: i2p2www/pages/site/docs/spec/configuration.html:364 msgid "Router Console" msgstr "" -#: i2p2www/pages/site/docs/spec/configuration.html:186 +#: i2p2www/pages/site/docs/spec/configuration.html:365 msgid "The router console uses the router.config file." msgstr "" -#: i2p2www/pages/site/docs/spec/configuration.html:191 +#: i2p2www/pages/site/docs/spec/configuration.html:370 msgid "See post on zzz.i2p." msgstr "" @@ -15159,6 +15189,7 @@ msgstr "" #: i2p2www/pages/site/docs/spec/updates.html:204 #: i2p2www/pages/site/docs/spec/updates.html:313 +#: i2p2www/pages/site/docs/spec/updates.html:365 msgid "Goals:" msgstr "" @@ -15181,7 +15212,8 @@ msgid "One-pass signature verification and file extraction" msgstr "" #: i2p2www/pages/site/docs/spec/updates.html:222 -#: i2p2www/pages/site/docs/spec/updates.html:336 +#: i2p2www/pages/site/docs/spec/updates.html:328 +#: i2p2www/pages/site/docs/spec/updates.html:388 msgid "Specification:" msgstr "" @@ -15190,40 +15222,80 @@ msgid "All unused fields must be set to 0 for compatibility with future versions msgstr "" #: i2p2www/pages/site/docs/spec/updates.html:308 -msgid "SU3 News File Specification" -msgstr "" +#, fuzzy +msgid "SU3 Reseed File Specification" +msgstr "Especificação para a construção de túneis" #: i2p2www/pages/site/docs/spec/updates.html:309 -msgid "As of 0.9.17, the news is delivered in an \"su3\" file format." +msgid "As of 0.9.14, reseed data is delivered in an \"su3\" file format." msgstr "" #: i2p2www/pages/site/docs/spec/updates.html:316 -msgid "Signed news with strong signatures and trusted certificates" +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 "" -#: i2p2www/pages/site/docs/spec/updates.html:319 +#: 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 "" -#: i2p2www/pages/site/docs/spec/updates.html:322 -msgid "Standard XML format for use with standard parsers" -msgstr "" - -#: i2p2www/pages/site/docs/spec/updates.html:325 -msgid "Standard Atom format for use with standard feed readers and generators" -msgstr "" - -#: i2p2www/pages/site/docs/spec/updates.html:328 -msgid "Sanitization and verification of HTML before displaying on console" +#: i2p2www/pages/site/docs/spec/updates.html:323 +msgid "" +"Single compressed file to speed up reseeding, which was slow to fetch 200" +" files" msgstr "" #: i2p2www/pages/site/docs/spec/updates.html:331 +msgid "The file must be named \"i2pseeds.su3\"." +msgstr "" + +#: i2p2www/pages/site/docs/spec/updates.html:334 +msgid "" +"The file must be in the same directory as the router infos on the web " +"server." +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" +"and then fetch the individual router info files found in the links." +msgstr "" + +#: i2p2www/pages/site/docs/spec/updates.html:360 +msgid "SU3 News File Specification" +msgstr "" + +#: i2p2www/pages/site/docs/spec/updates.html:361 +msgid "As of 0.9.17, the news is delivered in an \"su3\" file format." +msgstr "" + +#: i2p2www/pages/site/docs/spec/updates.html:368 +msgid "Signed news with strong signatures and trusted certificates" +msgstr "" + +#: i2p2www/pages/site/docs/spec/updates.html:374 +msgid "Standard XML format for use with standard parsers" +msgstr "" + +#: i2p2www/pages/site/docs/spec/updates.html:377 +msgid "Standard Atom format for use with standard feed readers and generators" +msgstr "" + +#: i2p2www/pages/site/docs/spec/updates.html:380 +msgid "Sanitization and verification of HTML before displaying on console" +msgstr "" + +#: i2p2www/pages/site/docs/spec/updates.html:383 msgid "" "Suitable for easy implementation on Android and other platforms without " "an HTML console" msgstr "" -#: i2p2www/pages/site/docs/spec/updates.html:440 +#: 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" @@ -15816,7 +15888,7 @@ msgstr "" #: i2p2www/pages/site/docs/transport/ntcp.html:207 #: i2p2www/pages/site/docs/transport/ntcp.html:250 #: i2p2www/pages/site/docs/transport/ntcp.html:332 -#: i2p2www/pages/site/docs/transport/ntcp.html:428 +#: i2p2www/pages/site/docs/transport/ntcp.html:437 msgid "Size:" msgstr "" @@ -15834,7 +15906,7 @@ msgstr "" #: i2p2www/pages/site/docs/transport/ntcp.html:236 #: i2p2www/pages/site/docs/transport/ntcp.html:319 -#: i2p2www/pages/site/docs/transport/ntcp.html:397 +#: i2p2www/pages/site/docs/transport/ntcp.html:398 msgid "Notes:" msgstr "" @@ -15854,7 +15926,7 @@ msgstr "" #: i2p2www/pages/site/docs/transport/ntcp.html:252 #: i2p2www/pages/site/docs/transport/ntcp.html:334 -#: i2p2www/pages/site/docs/transport/ntcp.html:430 +#: i2p2www/pages/site/docs/transport/ntcp.html:439 msgid "Unencrypted Contents:" msgstr "" @@ -15878,7 +15950,7 @@ msgstr "" #: i2p2www/pages/site/docs/transport/ntcp.html:285 #: i2p2www/pages/site/docs/transport/ntcp.html:376 -#: i2p2www/pages/site/docs/transport/ntcp.html:457 +#: i2p2www/pages/site/docs/transport/ntcp.html:466 msgid "Encrypted Contents:" msgstr "" @@ -15915,7 +15987,7 @@ msgid "Alice's 387+ byte `RouterIdentity`" msgstr "" #: i2p2www/pages/site/docs/transport/ntcp.html:366 -#: i2p2www/pages/site/docs/transport/ntcp.html:452 +#: i2p2www/pages/site/docs/transport/ntcp.html:461 msgid "0-15 bytes random data" msgstr "" @@ -15936,31 +16008,31 @@ msgid "" "of message #1) as the IV" msgstr "" -#: i2p2www/pages/site/docs/transport/ntcp.html:399 +#: i2p2www/pages/site/docs/transport/ntcp.html:400 msgid "Bob verifies the signature, and on failure, drops the connection." msgstr "" -#: i2p2www/pages/site/docs/transport/ntcp.html:402 +#: i2p2www/pages/site/docs/transport/ntcp.html:403 msgid "" "Bob may drop the connection if the clock skew with Alice is too high as " "calculated using tsA." msgstr "" -#: i2p2www/pages/site/docs/transport/ntcp.html:405 +#: 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 "" -#: i2p2www/pages/site/docs/transport/ntcp.html:421 +#: i2p2www/pages/site/docs/transport/ntcp.html:430 msgid "Message 4 (Session Confirm B)" msgstr "" -#: i2p2www/pages/site/docs/transport/ntcp.html:422 +#: i2p2www/pages/site/docs/transport/ntcp.html:431 msgid "This is a signature of the critical data. Bob sends Alice:" msgstr "" -#: i2p2www/pages/site/docs/transport/ntcp.html:446 +#: i2p2www/pages/site/docs/transport/ntcp.html:455 msgid "" "the `Signature` of the following concatenated data:\n" " X, Y, Alice's `RouterIdentity`, tsA, tsB.\n" @@ -15968,7 +16040,7 @@ msgid "" "the `SigningPublicKey` in his `RouterIdentity`" msgstr "" -#: i2p2www/pages/site/docs/transport/ntcp.html:470 +#: i2p2www/pages/site/docs/transport/ntcp.html:479 #, python-format msgid "" "Data AES encrypted using the DH " @@ -15979,21 +16051,21 @@ msgid "" "signature types" msgstr "" -#: i2p2www/pages/site/docs/transport/ntcp.html:479 +#: i2p2www/pages/site/docs/transport/ntcp.html:488 msgid "Alice verifies the signature, and on failure, drops the connection." msgstr "" -#: i2p2www/pages/site/docs/transport/ntcp.html:482 +#: 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 "" -#: i2p2www/pages/site/docs/transport/ntcp.html:497 +#: i2p2www/pages/site/docs/transport/ntcp.html:506 msgid "After Establishment" msgstr "" -#: i2p2www/pages/site/docs/transport/ntcp.html:498 +#: i2p2www/pages/site/docs/transport/ntcp.html:507 msgid "" "The connection is established, and standard or time sync messages may be " "exchanged.\n" @@ -16005,11 +16077,11 @@ msgid "" " the next IV." msgstr "" -#: i2p2www/pages/site/docs/transport/ntcp.html:507 +#: i2p2www/pages/site/docs/transport/ntcp.html:516 msgid "Check Connection Message" msgstr "" -#: i2p2www/pages/site/docs/transport/ntcp.html:508 +#: i2p2www/pages/site/docs/transport/ntcp.html:517 msgid "" "Alternately, when Bob receives a connection, it could be a\n" "check connection (perhaps prompted by Bob asking for someone\n" @@ -16019,58 +16091,58 @@ msgid "" "A check info connection will receive 256 bytes containing:" msgstr "" -#: i2p2www/pages/site/docs/transport/ntcp.html:517 +#: i2p2www/pages/site/docs/transport/ntcp.html:526 msgid "32 bytes of uninterpreted, ignored data" msgstr "" -#: i2p2www/pages/site/docs/transport/ntcp.html:518 +#: i2p2www/pages/site/docs/transport/ntcp.html:527 msgid "1 byte size" msgstr "" -#: i2p2www/pages/site/docs/transport/ntcp.html:519 +#: 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 "" -#: i2p2www/pages/site/docs/transport/ntcp.html:520 +#: i2p2www/pages/site/docs/transport/ntcp.html:529 msgid "2 byte port number that the local router was reached on" msgstr "" -#: i2p2www/pages/site/docs/transport/ntcp.html:521 +#: i2p2www/pages/site/docs/transport/ntcp.html:530 msgid "" "4 byte i2p network time as known by the remote side (seconds since the " "epoch)" msgstr "" -#: i2p2www/pages/site/docs/transport/ntcp.html:522 +#: i2p2www/pages/site/docs/transport/ntcp.html:531 msgid "uninterpreted padding data, up to byte 223" msgstr "" -#: i2p2www/pages/site/docs/transport/ntcp.html:523 +#: 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 "" -#: i2p2www/pages/site/docs/transport/ntcp.html:526 +#: i2p2www/pages/site/docs/transport/ntcp.html:535 msgid "Check connection is completely disabled as of release 0.9.12." msgstr "" -#: i2p2www/pages/site/docs/transport/ntcp.html:530 +#: i2p2www/pages/site/docs/transport/ntcp.html:539 msgid "Discussion" msgstr "" -#: i2p2www/pages/site/docs/transport/ntcp.html:531 +#: i2p2www/pages/site/docs/transport/ntcp.html:540 #, python-format msgid "Now on the NTCP Discussion Page." msgstr "" -#: i2p2www/pages/site/docs/transport/ntcp.html:537 +#: i2p2www/pages/site/docs/transport/ntcp.html:546 msgid "The maximum message size should be increased to approximately 32 KB." msgstr "" -#: i2p2www/pages/site/docs/transport/ntcp.html:541 +#: 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" @@ -16081,13 +16153,13 @@ msgid "" "to create a limited number of message sizes." msgstr "" -#: i2p2www/pages/site/docs/transport/ntcp.html:549 +#: 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 "" -#: i2p2www/pages/site/docs/transport/ntcp.html:553 +#: 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?" diff --git a/i2p2www/translations/pt_BR/LC_MESSAGES/get-involved.po b/i2p2www/translations/pt_BR/LC_MESSAGES/get-involved.po index dbd4a6cc..962d915f 100644 --- a/i2p2www/translations/pt_BR/LC_MESSAGES/get-involved.po +++ b/i2p2www/translations/pt_BR/LC_MESSAGES/get-involved.po @@ -10,7 +10,7 @@ msgid "" msgstr "" "Project-Id-Version: I2P\n" "Report-Msgid-Bugs-To: http://trac.i2p2.de\n" -"POT-Creation-Date: 2014-10-22 20:13+0000\n" +"POT-Creation-Date: 2014-11-27 12:12+0000\n" "PO-Revision-Date: 2014-11-26 19:44+0000\n" "Last-Translator: blueboy\n" "Language-Team: Portuguese (Brazil) " @@ -458,319 +458,52 @@ msgid "" msgstr "" #: i2p2www/pages/site/get-involved/todo.html:15 -#: i2p2www/pages/site/get-involved/todo.html:53 +#: i2p2www/pages/site/get-involved/todo.html:38 msgid "Core functionality" msgstr "Funcionalidade essencial" #: i2p2www/pages/site/get-involved/todo.html:15 -#: i2p2www/pages/site/get-involved/todo.html:27 -#: i2p2www/pages/site/get-involved/todo.html:51 +#: i2p2www/pages/site/get-involved/todo.html:21 +#: i2p2www/pages/site/get-involved/todo.html:36 msgid "link" msgstr "linque" #: i2p2www/pages/site/get-involved/todo.html:17 -#: i2p2www/pages/site/get-involved/todo.html:56 -msgid "NAT/Firewall bridging via 1-hop restricted routes" -msgstr "" - -#: i2p2www/pages/site/get-involved/todo.html:20 -#: i2p2www/pages/site/get-involved/todo.html:129 -msgid "High degree transport layer with UDP, NBIO, or NIO" -msgstr "" - -#: i2p2www/pages/site/get-involved/todo.html:23 -#: i2p2www/pages/site/get-involved/todo.html:217 +#: i2p2www/pages/site/get-involved/todo.html:41 msgid "NetworkDB and profile tuning and ejection policy for large nets" msgstr "" -#: i2p2www/pages/site/get-involved/todo.html:27 -#: i2p2www/pages/site/get-involved/todo.html:241 +#: i2p2www/pages/site/get-involved/todo.html:21 +#: i2p2www/pages/site/get-involved/todo.html:65 msgid "Security / anonymity" msgstr "Segurança / anonimato" -#: i2p2www/pages/site/get-involved/todo.html:29 -#: i2p2www/pages/site/get-involved/todo.html:244 -msgid "" -"Per-hop tunnel id & new permuted TunnelVerificationStructure " -"encryption" -msgstr "" - -#: i2p2www/pages/site/get-involved/todo.html:32 -#: i2p2www/pages/site/get-involved/todo.html:294 -msgid "Strict ordering of participants within tunnels" -msgstr "" - -#: i2p2www/pages/site/get-involved/todo.html:35 -msgid "Randomly permuted tunnel lengths" -msgstr "" - -#: i2p2www/pages/site/get-involved/todo.html:38 -#: i2p2www/pages/site/get-involved/todo.html:356 +#: 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 "" -#: i2p2www/pages/site/get-involved/todo.html:41 -#: i2p2www/pages/site/get-involved/todo.html:375 +#: 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 "" -#: i2p2www/pages/site/get-involved/todo.html:44 -#: i2p2www/pages/site/get-involved/todo.html:404 +#: 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 "" -#: i2p2www/pages/site/get-involved/todo.html:47 -#: i2p2www/pages/site/get-involved/todo.html:441 +#: i2p2www/pages/site/get-involved/todo.html:32 +#: i2p2www/pages/site/get-involved/todo.html:153 msgid "Stop & go mix w/ garlics & tunnels" msgstr "" -#: i2p2www/pages/site/get-involved/todo.html:51 -#: i2p2www/pages/site/get-involved/todo.html:455 +#: i2p2www/pages/site/get-involved/todo.html:36 +#: i2p2www/pages/site/get-involved/todo.html:167 msgid "Performance" msgstr "Desempenho" -#: i2p2www/pages/site/get-involved/todo.html:61 -msgid "Implemented in I2P 0.6.0.6" -msgstr "Implementado na versão 0.6.0.6 da I2P" - -#: i2p2www/pages/site/get-involved/todo.html:62 -msgid "" -"The functionality of allowing routers to fully participate within the " -"network \n" -"while behind firewalls and NATs that they do not control requires some " -"basic \n" -"restricted route operation (since those peers will not be able to receive" -" \n" -"inbound connections). To do this successfully, you consider peers one of" -" \n" -"two ways:" -msgstr "" - -#: i2p2www/pages/site/get-involved/todo.html:72 -msgid "" -"Peers who have reachable interfaces - these peers do not need to \n" -"do anything special" -msgstr "" - -#: i2p2www/pages/site/get-involved/todo.html:76 -msgid "" -"Peers who do not have reachable interfaces - these peers must " -"build \n" -"a tunnel pointing at them where the gateway is one of the peers they have" -" \n" -"established a connection with who has both a publicly reachable interface" -" \n" -"and who has agreed to serve as their 'introducer'." -msgstr "" - -#: i2p2www/pages/site/get-involved/todo.html:84 -msgid "" -"To do this, peers who have no IP address simply connect to a few peers, \n" -"build a tunnel through them, and publish a reference to those tunnels " -"within \n" -"their RouterInfo structure in the network database." -msgstr "" - -#: i2p2www/pages/site/get-involved/todo.html:89 -msgid "" -"When someone wants to contact any particular router, they first must get" -" \n" -"its RouterInfo from the network database, which will tell them whether " -"they \n" -"can connect directly (e.g. the peer has a publicly reachable interface) \n" -"or whether they need to contact them indirectly. Direct connections occur" -" \n" -"as normal, while indirect connections are done through one of the " -"published \n" -"tunnels." -msgstr "" - -#: i2p2www/pages/site/get-involved/todo.html:97 -msgid "" -"When a router just wants to get a message or two to a specific hidden " -"peer, \n" -"they can just use the indirect tunnel for sending the payload. However, \n" -"if the router wants to talk to the hidden peer often (for instance, as " -"part \n" -"of a tunnel), they will send a garlic routed message through the indirect" -" \n" -"tunnel to that hidden peer which unwraps to contain a message which " -"should \n" -"be sent to the originating router. That hidden peer then establishes an \n" -"outbound connection to the originating router and from then on, those two" -" \n" -"routers can talk to each other directly over that newly established " -"direct \n" -"connection." -msgstr "" - -#: i2p2www/pages/site/get-involved/todo.html:108 -msgid "" -"Of course, that only works if the originating peer can receive " -"connections \n" -"(they aren't also hidden). However, if the originating peer is hidden, " -"they \n" -"can simply direct the garlic routed message to come back to the " -"originating \n" -"peer's inbound tunnel." -msgstr "" - -#: i2p2www/pages/site/get-involved/todo.html:114 -msgid "" -"This is not meant to provide a way for a peer's IP address to be " -"concealed, \n" -"merely as a way to let people behind firewalls and NATs fully operate " -"within \n" -"the network. Concealing the peer's IP address adds a little more work, as" -" \n" -"described below." -msgstr "" - -#: i2p2www/pages/site/get-involved/todo.html:120 -msgid "" -"With this technique, any router can participate as any part of a tunnel." -" \n" -"For efficiency purposes, a hidden peer would be a bad choice for an " -"inbound \n" -"gateway, and within any given tunnel, two neighboring peers wouldn't want" -" \n" -"to be hidden. But that is not technically necessary." -msgstr "" - -#: i2p2www/pages/site/get-involved/todo.html:132 -msgid "Both UDP and NIO have been Implemented in I2P" -msgstr "UDP e NIO, ambos, foram implementados no roteador I2P" - -#: i2p2www/pages/site/get-involved/todo.html:133 -msgid "" -"Standard TCP communication in Java generally requires blocking socket \n" -"calls, and to keep a blocked socket from hanging the entire system, those" -" \n" -"blocking calls are done on their own threads. Our current TCP transport \n" -"is implemented in a naive fashion - for each peer we are talking to, we \n" -"have one thread reading and one thread writing. The reader thread simply" -" \n" -"loops a bunch of read() calls, building I2NP messages and adding them \n" -"to our internal inbound message queue, and the writer thread pulls " -"messages \n" -"off a per-connection outbound message queue and shoves the data through \n" -"write() calls." -msgstr "" - -#: i2p2www/pages/site/get-involved/todo.html:144 -msgid "" -"We do this fairly efficiently, from a CPU perspective - at any time, \n" -"almost all of these threads are sitting idle, blocked waiting for " -"something \n" -"to do. However, each thread consumes real resources (on older Linux " -"kernels, \n" -"for instance, each thread would often be implemented as a fork()'ed " -"process). \n" -"As the network grows, the number of peers each router will want to talk \n" -"with will increase (remember, I2P is fully connected, meaning that any \n" -"given peer should know how to get a message to any other peer, and " -"restricted \n" -"route support will probably not significantly reduce the number of " -"connections \n" -"necessary). This means that with a 100,000 router network, each router \n" -"will have up to 199,998 threads just to deal with the TCP connections!" -msgstr "" - -#: i2p2www/pages/site/get-involved/todo.html:156 -msgid "" -"Obviously, that just won't work. We need to use a transport layer that \n" -"can scale. In Java, we have two main camps:" -msgstr "" - -#: i2p2www/pages/site/get-involved/todo.html:161 -#, python-format -msgid "" -"Implemented in I2P 0.6 (\"SSU\") as documented elsewhere" -msgstr "" -"Implementado no lançamento da versão 0.6 da I2P (\"SSU\") como " -"documentado aqui" - -#: i2p2www/pages/site/get-involved/todo.html:164 -msgid "" -"Sending and receiving UDP datagrams is a connectionless operation - if \n" -"we are communicating with 100,000 peers, we simply stick the UDP packets" -" \n" -"in a queue and have a single thread pulling them off the queue and " -"shoving \n" -"them out the pipe (and to receive, have a single thread pulling in any \n" -"UDP packets received and adding them to an inbound queue)." -msgstr "" - -#: i2p2www/pages/site/get-involved/todo.html:171 -msgid "" -"However, moving to UDP means losing the benefits of TCP's ordering, " -"congestion \n" -"control, MTU discovery, etc. Implementing that code will take significant" -" \n" -"work, however I2P doesn't need it to be as strong as TCP. Specifically, \n" -"a while ago I was taking some measurements in the simulator and on the \n" -"live net, and the vast majority of messages transferred would fit easily" -" \n" -"within a single unfragmented UDP packet, and the largest of the messages" -" \n" -"would fit within 20-30 packets. As mule pointed out, TCP adds a " -"significant \n" -"overhead when dealing with so many small packets, as the ACKs are within" -" \n" -"an order of magnitude in size. With UDP, we can optimize the transport \n" -"for both efficiency and resilience by taking into account I2P's " -"particular \n" -"needs." -msgstr "" - -#: i2p2www/pages/site/get-involved/todo.html:184 -msgid "It will be a lot of work though." -msgstr "" - -#: i2p2www/pages/site/get-involved/todo.html:187 -msgid "NIO or NBIO" -msgstr "NIO ou NBIO" - -#: i2p2www/pages/site/get-involved/todo.html:188 -msgid "NIO Implemented in I2P 0.6.1.22 (\"NTCP\")" -msgstr "NIO foi implementado no lançamento da versão 0.6.1.22 da I2P (\"NTCP\")" - -#: i2p2www/pages/site/get-involved/todo.html:191 -msgid "" -"In Java 1.4, a set of \"New I/O\" packages was introduced, allowing Java" -" \n" -"developers to take advantage of the operating system's nonblocking IO \n" -"capabilities - allowing you to maintain a large number of concurrent IO \n" -"operations without requiring a separate thread for each. There is much \n" -"promise with this approach, as we can scalable handle a large number of \n" -"concurrent connections and we don't have to write a mini-TCP stack with \n" -"UDP. However, the NIO packages have not proven themselves to be battle-" -"ready, \n" -"as the Freenet developer's found. In addition, requiring NIO support " -"would \n" -"mean we can't run on any of the open source JVMs like Kaffe, \n" -"as GNU/Classpath has only " -"limited \n" -"support for NIO. (note: this may not be the case anymore, as there \n" -"has been some progress on Classpath's NIO, but it is an unknown " -"quantity)" -msgstr "" - -#: i2p2www/pages/site/get-involved/todo.html:205 -#, python-format -msgid "" -"Another alternative along the same lines is the Non" -" \n" -"Blocking I/O package - essentially a cleanroom NIO implementation \n" -"(written before NIO was around). It works by using some native OS code \n" -"to do the nonblocking IO, passing off events through Java. It seems to \n" -"be working with Kaffe, though there doesn't seem to be much development \n" -"activity on it lately (likely due to 1.4's NIO deployment)." -msgstr "" - -#: i2p2www/pages/site/get-involved/todo.html:220 +#: i2p2www/pages/site/get-involved/todo.html:44 msgid "" "Within the current network database and profile management " "implementation, \n" @@ -793,154 +526,14 @@ msgid "" "code yet, since we aren't going to need it for a while." msgstr "" -#: i2p2www/pages/site/get-involved/todo.html:235 +#: 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" "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:247 -#: i2p2www/pages/site/get-involved/todo.html:331 -#, python-format -msgid "" -"Addressed in I2P 0.5 as documented elsewhere" -msgstr "" -"Encaminhado no lançamento da versão 0.5 da I2P como documentado aqui" - -#: i2p2www/pages/site/get-involved/todo.html:250 -msgid "" -"Right now, if Alice builds a four hop inbound tunnel starting at Elvis, \n" -"going to Dave, then to Charlie, then Bob, and finally Alice " -"(A<--B<--C<--D<--E), \n" -"all five of them will know they are participating in tunnel \"123\", as \n" -"the messages are tagged as such. What we want to do is give each hop " -"their \n" -"own unique tunnel hop ID - Charlie will receive messages on tunnel 234 \n" -"and forward them to tunnel 876 on Bob. The intent is to prevent Bob or \n" -"Charlie from knowing that they are in Alice's tunnel, as if each hop in \n" -"the tunnel had the same tunnel ID, collusion attacks aren't much work." -msgstr "" - -#: i2p2www/pages/site/get-involved/todo.html:260 -msgid "" -"Adding a unique tunnel ID per hop isn't hard, but by itself, " -"insufficient. \n" -"If Dave and Bob are under the control of the same attacker, they wouldn't" -" \n" -"be able to tell they are in the same tunnel due to the tunnel ID, but \n" -"would be able to tell by the message bodies and verification structures \n" -"by simply comparing them. To prevent that, the tunnel must use layered \n" -"encryption along the path, both on the payload of the tunneled message \n" -"and on the verification structure (used to prevent simple tagging " -"attacks). \n" -"This requires some simple modifications to the TunnelMessage, as well \n" -"as the inclusion of per-hop secret keys delivered during tunnel creation" -" \n" -"and given to the tunnel's gateway. We must fix a maximum tunnel length \n" -"(e.g. 16 hops) and instruct the gateway to encrypt the message to each \n" -"of the 16 delivered secret keys, in reverse order, and to encrypt the \n" -"signature of the hash of the (encrypted) payload at each step. The " -"gateway \n" -"then sends that 16-step encrypted message, along with a 16-step and " -"16-wide \n" -"encrypted mapping to the first hop, which then decrypts the mapping and \n" -"the payload with their secret key, looking in the 16-wide mapping for \n" -"the entry associated with their own hop (keyed by the per-hop tunnel ID)" -" \n" -"and verifying the payload by checking it against the associated signed \n" -"hash." -msgstr "" - -#: i2p2www/pages/site/get-involved/todo.html:281 -msgid "" -"The tunnel gateway does still have more information than the other peers" -" \n" -"in the tunnel, and compromising both the gateway and a tunnel participant" -" \n" -"would allow those peers to collude, exposing the fact that they are both" -" \n" -"in the same tunnel. In addition, neighboring peers know that they are \n" -"in the same tunnel anyway, as they know who they send the message to (and" -" \n" -"with IP-based transports without restricted routes, they know who they \n" -"got it from). However, the above two techniques significantly increase \n" -"the cost of gaining meaningful samples when dealing with longer tunnels." -msgstr "" - -#: i2p2www/pages/site/get-involved/todo.html:297 -msgid "Implemented in release 0.6.2" -msgstr "Implementado no lançamento 0.6.2" - -#: i2p2www/pages/site/get-involved/todo.html:300 -#, python-format -msgid "" -"As Connelly proposed to deal with the\n" -"predecessor attack (2008\n" -"update), keeping the order of peers within our tunnels consistent \n" -"(aka whenever Alice creates a tunnel with both Bob and Charlie in it, \n" -"Bob's next hop is always Charlie), we address the issue as Bob doesn't \n" -"get to substantially sample Alice's peer selection group. We may even \n" -"want to explicitly allow Bob to participate in Alice's tunnels in only \n" -"one way - receiving a message from Dave and sending it to Charlie - and \n" -"if any of those peers are not available to participate in the tunnel (due" -" \n" -"to overload, network disconnection, etc), avoid asking Bob to participate" -" \n" -"in any tunnels until they are back online." -msgstr "" - -#: i2p2www/pages/site/get-involved/todo.html:315 -msgid "" -"More analysis is necessary for revising the tunnel creation - at the \n" -"moment, we simply select and order randomly within the peer's top tier \n" -"of peers (ones with fast + high capacity)." -msgstr "" - -#: i2p2www/pages/site/get-involved/todo.html:320 -msgid "" -"Adding a strict ordering to peers in a tunnel also improves the anonymity" -" \n" -"of peers with 0-hop tunnels, as otherwise the fact that a peer's gateway" -" \n" -"is always the same would be particularly damning. However, peers with \n" -"0-hop tunnels may want to periodically use a 1-hop tunnel to simulate \n" -"the failure of a normally reliable gateway peer (so every MTBF*(tunnel \n" -"duration) minutes, use a 1-hop tunnel)." -msgstr "" - -#: i2p2www/pages/site/get-involved/todo.html:337 -msgid "" -"Without tunnel length permutation, if someone were to somehow detect that" -" \n" -"a destination had a particular number of hops, it might be able to use " -"that \n" -"information to identify the router the destination is located on, per the" -" \n" -"predecessor attack. For instance, if everyone has 2-hop tunnels, if Bob \n" -"receives a tunnel message from Charlie and forwards it to Alice, Bob " -"knows \n" -"Alice is the final router in the tunnel. If Bob were to identify what " -"destination \n" -"that tunnel served (by means of colluding with the gateway and harvesting" -" \n" -"the network database for all of the LeaseSets), he would know the router" -" \n" -"on which that destination is located (and without restricted routes, that" -" \n" -"would mean what IP address the destination is on)." -msgstr "" - -#: i2p2www/pages/site/get-involved/todo.html:349 -msgid "" -"It is to counter user behavior that tunnel lengths should be permuted, \n" -"using algorithms based on the length requested (for example, the 1/MTBF \n" -"length change for 0-hop tunnels outlined above)." -msgstr "" - -#: i2p2www/pages/site/get-involved/todo.html:359 +#: i2p2www/pages/site/get-involved/todo.html:71 msgid "" "The restricted route functionality described before was simply a " "functional \n" @@ -962,7 +555,7 @@ msgid "" "to forward it as requested." msgstr "" -#: i2p2www/pages/site/get-involved/todo.html:378 +#: i2p2www/pages/site/get-involved/todo.html:90 #, python-format msgid "" "Within the network, we will want some way to deter people from consuming" @@ -976,7 +569,7 @@ msgid "" "to make certain requests \"expensive\"." msgstr "" -#: i2p2www/pages/site/get-involved/todo.html:386 +#: 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 " @@ -994,7 +587,7 @@ msgid "" "with few resources." msgstr "" -#: i2p2www/pages/site/get-involved/todo.html:397 +#: 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" @@ -1002,7 +595,7 @@ msgid "" "appropriate." msgstr "" -#: i2p2www/pages/site/get-involved/todo.html:407 +#: i2p2www/pages/site/get-involved/todo.html:119 #, python-format msgid "" "To powerful passive external observers as well as large colluding " @@ -1023,7 +616,7 @@ msgid "" "tunnel mixing strategies." msgstr "" -#: i2p2www/pages/site/get-involved/todo.html:420 +#: 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" @@ -1041,7 +634,7 @@ msgid "" "available." msgstr "" -#: i2p2www/pages/site/get-involved/todo.html:433 +#: i2p2www/pages/site/get-involved/todo.html:145 msgid "" "In addition, we may want to implement code to dynamically reroute tunnels" " \n" @@ -1051,7 +644,7 @@ msgid "" "with instructions to redefine the next-hop in the tunnel." msgstr "" -#: i2p2www/pages/site/get-involved/todo.html:444 +#: 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" @@ -1066,7 +659,7 @@ msgid "" "clove exposed includes delay instructions." msgstr "" -#: i2p2www/pages/site/get-involved/todo.html:456 +#: i2p2www/pages/site/get-involved/todo.html:168 #, python-format msgid "" "Performance related improvements are listed on the\n" @@ -4214,3 +3807,15 @@ msgstr "" "href=\"http://%(zzz)s/forums/14\">sessão de traduções do fórum em " "%(zzz)s." + + + + + + + + + + + + diff --git a/i2p2www/translations/ru/LC_MESSAGES/docs.po b/i2p2www/translations/ru/LC_MESSAGES/docs.po index ffeabb45..4ce36d40 100644 --- a/i2p2www/translations/ru/LC_MESSAGES/docs.po +++ b/i2p2www/translations/ru/LC_MESSAGES/docs.po @@ -14,7 +14,7 @@ msgid "" msgstr "" "Project-Id-Version: I2P\n" "Report-Msgid-Bugs-To: http://trac.i2p2.de\n" -"POT-Creation-Date: 2014-11-16 02:59+0000\n" +"POT-Creation-Date: 2014-11-27 12:12+0000\n" "PO-Revision-Date: 2014-11-16 03:02+0000\n" "Last-Translator: str4d \n" "Language-Team: Russian (Russia) " @@ -34,7 +34,9 @@ msgstr "Указатель для технической документаци #: i2p2www/pages/site/docs/applications/embedding.html:3 #: i2p2www/pages/site/docs/how/cryptography.html:3 #: i2p2www/pages/site/docs/protocol/i2cp.html:3 +#: i2p2www/pages/site/docs/spec/configuration.html:3 #: i2p2www/pages/site/docs/spec/updates.html:3 +#: i2p2www/pages/site/docs/transport/ntcp.html:3 msgid "November 2014" msgstr "" @@ -149,7 +151,7 @@ msgstr "Спецификация плагина" msgid "Managed Clients" msgstr "Управляемые клиенты" -#: i2p2www/pages/site/docs/index.html:44 i2p2www/pages/site/docs/index.html:217 +#: i2p2www/pages/site/docs/index.html:44 i2p2www/pages/site/docs/index.html:222 msgid "Embedding the router in your application" msgstr "" @@ -166,7 +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:189 +#: i2p2www/pages/site/docs/index.html:48 i2p2www/pages/site/docs/index.html:194 msgid "Configuration File Format" msgstr "Формат файла конфигурации" @@ -186,27 +188,32 @@ msgstr "" msgid "Application Development Overview and Guide" msgstr "Обзор и руководство по разработке приложений" -#: i2p2www/pages/site/docs/index.html:72 +#: i2p2www/pages/site/docs/index.html:58 +#: i2p2www/pages/site/docs/api/i2ptunnel.html:55 +msgid "I2PTunnel Configuration" +msgstr "" + +#: i2p2www/pages/site/docs/index.html:74 msgid "SAM Protocol" msgstr "Протокол SAM" -#: i2p2www/pages/site/docs/index.html:74 +#: i2p2www/pages/site/docs/index.html:76 msgid "SAMv2 Protocol" msgstr "Протокол SAMv2" -#: i2p2www/pages/site/docs/index.html:76 +#: i2p2www/pages/site/docs/index.html:78 msgid "SAMv3 Protocol" msgstr "Протокол SAMv3" -#: i2p2www/pages/site/docs/index.html:78 +#: i2p2www/pages/site/docs/index.html:80 msgid "BOB Protocol" msgstr "Протокол BOB" -#: i2p2www/pages/site/docs/index.html:81 +#: i2p2www/pages/site/docs/index.html:83 msgid "End-to-End Transport API and Protocols" msgstr "API и Протоколы Транспорта точка-точка" -#: i2p2www/pages/site/docs/index.html:82 +#: i2p2www/pages/site/docs/index.html:84 msgid "" "The end-to-end protocols used by clients for reliable and unreliable " "communication." @@ -214,33 +221,33 @@ msgstr "" "Протоколы из-конца-в-конец используются клиентами для надежного и " "ненадежного соединения." -#: i2p2www/pages/site/docs/index.html:84 +#: i2p2www/pages/site/docs/index.html:86 #: i2p2www/pages/site/docs/api/streaming.html:2 msgid "Streaming Library" msgstr "Потоковая библиотека" -#: i2p2www/pages/site/docs/index.html:86 +#: i2p2www/pages/site/docs/index.html:88 msgid "Streaming Protocol Specification" msgstr "Спецификация на потоковый протокол" -#: i2p2www/pages/site/docs/index.html:88 +#: i2p2www/pages/site/docs/index.html:90 msgid "Streaming Javadoc" msgstr "Javadoc на Потоки" -#: i2p2www/pages/site/docs/index.html:90 +#: i2p2www/pages/site/docs/index.html:92 #: i2p2www/pages/site/docs/api/datagrams.html:2 msgid "Datagrams" msgstr "Дейтаграммы" -#: i2p2www/pages/site/docs/index.html:92 +#: i2p2www/pages/site/docs/index.html:94 msgid "Datagram Javadoc" msgstr "Javadoc по Дейтаграммам" -#: i2p2www/pages/site/docs/index.html:95 +#: i2p2www/pages/site/docs/index.html:97 msgid "Client-to-Router Interface API and Protocol" msgstr "API и протокол интерфейса клиент-маршрутизатор" -#: i2p2www/pages/site/docs/index.html:96 +#: 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" @@ -250,52 +257,52 @@ msgstr "" "получения трафика с маршрутизатора.\n" "Традиционно используется только Java приложениями и высокоуровневыми API." -#: i2p2www/pages/site/docs/index.html:101 +#: i2p2www/pages/site/docs/index.html:103 msgid "I2CP - I2P Control Protocol / API overview" msgstr "Обзор I2CP - I2P Control Protocol / API" -#: i2p2www/pages/site/docs/index.html:103 +#: i2p2www/pages/site/docs/index.html:105 msgid "I2CP Specification" msgstr "Спецификация I2CP" -#: i2p2www/pages/site/docs/index.html:105 +#: i2p2www/pages/site/docs/index.html:107 msgid "I2CP API Javadoc" msgstr "Javadoc на I2CP API" -#: i2p2www/pages/site/docs/index.html:107 -#: i2p2www/pages/site/docs/index.html:136 +#: i2p2www/pages/site/docs/index.html:109 +#: i2p2www/pages/site/docs/index.html:139 msgid "Common data structures specification" msgstr "Спецификация основных структур данных" -#: i2p2www/pages/site/docs/index.html:109 -#: i2p2www/pages/site/docs/index.html:138 +#: i2p2www/pages/site/docs/index.html:111 +#: i2p2www/pages/site/docs/index.html:141 msgid "Data Structures Javadoc" msgstr "Javadoc по Структурам Данных" -#: i2p2www/pages/site/docs/index.html:112 +#: i2p2www/pages/site/docs/index.html:114 msgid "End-to-End Encryption" msgstr "Шифрование из-конца-в-конец" -#: i2p2www/pages/site/docs/index.html:113 +#: i2p2www/pages/site/docs/index.html:115 msgid "How client messages are end-to-end encrypted by the router." msgstr "Как сообщения клиентов из-конца-в-конец шифруются маршрутизатором" -#: i2p2www/pages/site/docs/index.html:115 +#: i2p2www/pages/site/docs/index.html:117 msgid "ElGamal/AES+SessionTag encryption" msgstr "Шифрование ElGamal/AES+SessionTag" -#: i2p2www/pages/site/docs/index.html:116 -#: i2p2www/pages/site/docs/index.html:149 +#: i2p2www/pages/site/docs/index.html:118 +#: i2p2www/pages/site/docs/index.html:152 msgid "ElGamal and AES cryptography details" msgstr "Подробности криптографии ElGamal и AES" -#: i2p2www/pages/site/docs/index.html:119 +#: i2p2www/pages/site/docs/index.html:121 #: i2p2www/pages/site/docs/how/tech-intro.html:15 #: i2p2www/pages/site/docs/how/tech-intro.html:329 msgid "Network Database" msgstr "Сетевая база данных" -#: i2p2www/pages/site/docs/index.html:120 +#: i2p2www/pages/site/docs/index.html:122 msgid "" "Distributed storage and retrieval of information about routers and " "clients." @@ -303,23 +310,29 @@ msgstr "" "Распределенное хранилище и получение информации о маршрутизаторах и " "клиентах." -#: i2p2www/pages/site/docs/index.html:122 +#: i2p2www/pages/site/docs/index.html:124 msgid "Network database overview, details, and threat analysis" msgstr "Обзор сетевой базы данных, подробности и анализ угроз." -#: i2p2www/pages/site/docs/index.html:123 +#: i2p2www/pages/site/docs/index.html:125 msgid "Cryptographic hashes" msgstr "Криптографические хеши" -#: i2p2www/pages/site/docs/index.html:124 +#: i2p2www/pages/site/docs/index.html:126 msgid "Cryptographic signatures" msgstr "Криптографические подписи" #: i2p2www/pages/site/docs/index.html:127 +#: i2p2www/pages/site/docs/index.html:186 +#, fuzzy +msgid "Router reseed specification" +msgstr "Спецификация протокола" + +#: i2p2www/pages/site/docs/index.html:130 msgid "Router Message Protocol" msgstr "Протокол Сообщений Маршрутизатора" -#: i2p2www/pages/site/docs/index.html:128 +#: i2p2www/pages/site/docs/index.html:131 msgid "" "I2P is a message-oriented router. The messages sent between routers are " "defined by the I2NP protocol." @@ -327,25 +340,25 @@ msgstr "" "I2P - это маршрутизатор, ориентированный на сообщения. Сообщения " "пересылаются между маршрутизаторами и описываются протоколом I2NP." -#: i2p2www/pages/site/docs/index.html:130 +#: i2p2www/pages/site/docs/index.html:133 msgid "I2NP - I2P Network Protocol Overview" msgstr "I2NP - Обзор I2P Network Protocol" -#: i2p2www/pages/site/docs/index.html:132 +#: i2p2www/pages/site/docs/index.html:135 msgid "I2NP Specification" msgstr "Спецификация I2NP" -#: i2p2www/pages/site/docs/index.html:134 +#: i2p2www/pages/site/docs/index.html:137 msgid "I2NP Javadoc" msgstr "Javadoc на I2NP" -#: i2p2www/pages/site/docs/index.html:141 +#: i2p2www/pages/site/docs/index.html:144 #: i2p2www/pages/site/docs/how/tech-intro.html:14 #: i2p2www/pages/site/docs/how/tech-intro.html:228 msgid "Tunnels" msgstr "Туннели" -#: i2p2www/pages/site/docs/index.html:142 +#: i2p2www/pages/site/docs/index.html:145 msgid "" "Selecting peers, requesting tunnels through those peers, and encrypting " "and routing messages through these tunnels." @@ -353,150 +366,150 @@ msgstr "" "Выбор узлов, запрос туннелей через эти узлы, шифрование и маршрутизация " "сообщений через эти туннели." -#: i2p2www/pages/site/docs/index.html:144 +#: i2p2www/pages/site/docs/index.html:147 msgid "Peer profiling and selection" msgstr "Профилирование и выбор узлов" -#: i2p2www/pages/site/docs/index.html:145 +#: i2p2www/pages/site/docs/index.html:148 msgid "Tunnel routing overview" msgstr "Обзор туннельной маршрутизации" -#: i2p2www/pages/site/docs/index.html:146 +#: i2p2www/pages/site/docs/index.html:149 msgid "Garlic routing and \"garlic\" terminology" msgstr "Чесночная маршрутизация и \"чесночная\" терминология" -#: i2p2www/pages/site/docs/index.html:147 +#: i2p2www/pages/site/docs/index.html:150 msgid "Tunnel building and encryption" msgstr "Постройка и шифрование туннелей" -#: i2p2www/pages/site/docs/index.html:148 +#: i2p2www/pages/site/docs/index.html:151 msgid "ElGamal/AES" msgstr "ElGamal/AES" -#: i2p2www/pages/site/docs/index.html:148 +#: i2p2www/pages/site/docs/index.html:151 msgid "for build request encryption" msgstr "для шифрования запроса на построение" -#: i2p2www/pages/site/docs/index.html:150 +#: i2p2www/pages/site/docs/index.html:153 msgid "Tunnel building specification" msgstr "Спецификация построения туннеля" -#: i2p2www/pages/site/docs/index.html:151 +#: i2p2www/pages/site/docs/index.html:154 msgid "Low-level tunnel message specification" msgstr "Спецификация низкоуровневых туннельных сообщений" -#: i2p2www/pages/site/docs/index.html:152 +#: i2p2www/pages/site/docs/index.html:155 #: i2p2www/pages/site/docs/tunnels/unidirectional.html:2 msgid "Unidirectional Tunnels" msgstr "Однонаправленные Туннели" -#: i2p2www/pages/site/docs/index.html:153 +#: i2p2www/pages/site/docs/index.html:156 #: i2p2www/pages/site/docs/how/peer-selection.html:299 msgid "Peer Profiling and Selection in the I2P Anonymous Network" msgstr "Выбор и профилирование узла в Анонимной Сети I2P" -#: i2p2www/pages/site/docs/index.html:154 +#: i2p2www/pages/site/docs/index.html:157 msgid "2009 paper (pdf), not current but still generally accurate" msgstr "Статья 2009 года (pdf), устаревшие, но в цело все еще точные" -#: i2p2www/pages/site/docs/index.html:157 +#: i2p2www/pages/site/docs/index.html:160 msgid "Transport Layer" msgstr "Транспортный Уровень" -#: i2p2www/pages/site/docs/index.html:158 +#: i2p2www/pages/site/docs/index.html:161 msgid "The protocols for direct (point-to-point) router to router communication." msgstr "Протоколы для прямой (точка-точка) связи маршрутизатор-маршрутизатор." -#: i2p2www/pages/site/docs/index.html:160 +#: i2p2www/pages/site/docs/index.html:163 msgid "Transport layer overview" msgstr "Обзор Транспортного Уровня" -#: i2p2www/pages/site/docs/index.html:162 +#: i2p2www/pages/site/docs/index.html:165 msgid "TCP-based transport overview and specification" msgstr "Обзор и спецификация транспорта на основе TCP" -#: i2p2www/pages/site/docs/index.html:164 +#: i2p2www/pages/site/docs/index.html:167 msgid "UDP-based transport overview" msgstr "Обзор транспорта на основе UDP" -#: i2p2www/pages/site/docs/index.html:166 +#: i2p2www/pages/site/docs/index.html:169 msgid "SSU specification" msgstr "Спецификация SSU" -#: i2p2www/pages/site/docs/index.html:168 +#: i2p2www/pages/site/docs/index.html:171 msgid "NTCP transport encryption" msgstr "Шифрование транспорта NTCP" -#: i2p2www/pages/site/docs/index.html:170 +#: i2p2www/pages/site/docs/index.html:173 msgid "SSU transport encryption" msgstr "Шифрование транспорта SSU" -#: i2p2www/pages/site/docs/index.html:172 +#: i2p2www/pages/site/docs/index.html:175 msgid "Transport Javadoc" msgstr "Javadoc на транспорт" -#: i2p2www/pages/site/docs/index.html:174 +#: i2p2www/pages/site/docs/index.html:177 msgid "NTCP Javadoc" msgstr "Javadoc на NTCP" -#: i2p2www/pages/site/docs/index.html:176 +#: i2p2www/pages/site/docs/index.html:179 msgid "SSU Javadoc" msgstr "Javadoc на SSU" -#: i2p2www/pages/site/docs/index.html:179 +#: i2p2www/pages/site/docs/index.html:182 msgid "Other Router Topics" msgstr "Другие Темы о Маршрутизаторе" -#: i2p2www/pages/site/docs/index.html:181 +#: i2p2www/pages/site/docs/index.html:184 msgid "Router software updates" msgstr "Обновление ПО маршрутизатора" -#: i2p2www/pages/site/docs/index.html:183 +#: i2p2www/pages/site/docs/index.html:188 msgid "Native BigInteger Library" msgstr "Нативная Библиотека BigInteger" -#: i2p2www/pages/site/docs/index.html:185 +#: i2p2www/pages/site/docs/index.html:190 msgid "Time synchronization and NTP" msgstr "Синхронизация времени и NTP" -#: i2p2www/pages/site/docs/index.html:187 +#: i2p2www/pages/site/docs/index.html:192 msgid "Performance" msgstr "Производительноть" -#: i2p2www/pages/site/docs/index.html:194 +#: i2p2www/pages/site/docs/index.html:199 msgid "Developer's Guides and Resources" msgstr "Источники и Руководства Разработчика" -#: i2p2www/pages/site/docs/index.html:196 +#: i2p2www/pages/site/docs/index.html:201 msgid "New Developer's Guide" msgstr "Руководство для Нового Разработчика" -#: i2p2www/pages/site/docs/index.html:198 +#: i2p2www/pages/site/docs/index.html:203 msgid "New Translator's Guide" msgstr "Руководство для Нового Переводчика" -#: i2p2www/pages/site/docs/index.html:200 +#: i2p2www/pages/site/docs/index.html:205 msgid "Monotone Guide" msgstr "Руководство по Monotone" -#: i2p2www/pages/site/docs/index.html:202 +#: i2p2www/pages/site/docs/index.html:207 msgid "Developer Guidelines" msgstr "Общие Указания по Разработке" -#: i2p2www/pages/site/docs/index.html:204 +#: i2p2www/pages/site/docs/index.html:209 msgid "Javadocs on the standard internet:" msgstr "Javadocs в обычном интернет:" -#: i2p2www/pages/site/docs/index.html:205 -#: i2p2www/pages/site/docs/index.html:209 #: i2p2www/pages/site/docs/index.html:210 -#: i2p2www/pages/site/docs/index.html:211 +#: i2p2www/pages/site/docs/index.html:214 +#: i2p2www/pages/site/docs/index.html:215 +#: i2p2www/pages/site/docs/index.html:216 #, python-format msgid "Server %(num)s" msgstr "Сервер %(num)s" -#: i2p2www/pages/site/docs/index.html:206 -#: i2p2www/pages/site/docs/index.html:215 +#: i2p2www/pages/site/docs/index.html:211 +#: i2p2www/pages/site/docs/index.html:220 msgid "" "Note: always verify that javadocs are current by checking the release " "number." @@ -504,64 +517,64 @@ msgstr "" "Примечание: всегда убеждайтесь в том, что все javadoc актуальны, проверяя" " номер релиза." -#: i2p2www/pages/site/docs/index.html:208 +#: i2p2www/pages/site/docs/index.html:213 msgid "Javadocs inside I2P:" msgstr "Javadocs внутри I2P:" -#: i2p2www/pages/site/docs/index.html:219 +#: i2p2www/pages/site/docs/index.html:224 msgid "Ports used by I2P" msgstr "Порты, используемые I2P:" -#: i2p2www/pages/site/docs/index.html:221 +#: i2p2www/pages/site/docs/index.html:226 msgid "Automatic updates to development builds inside I2P" msgstr "Автоматическое обновление до тестовых сборок внутри I2P" -#: i2p2www/pages/site/docs/index.html:223 +#: i2p2www/pages/site/docs/index.html:228 msgid "Updating the wrapper manually" msgstr "Ручное обновление wrapper" -#: i2p2www/pages/site/docs/index.html:225 +#: i2p2www/pages/site/docs/index.html:230 msgid "User forum" msgstr "Форум пользователей" -#: i2p2www/pages/site/docs/index.html:227 +#: i2p2www/pages/site/docs/index.html:232 msgid "Developer forum inside I2P" msgstr "Форму разработчиков внутри I2P" -#: i2p2www/pages/site/docs/index.html:229 +#: i2p2www/pages/site/docs/index.html:234 msgid "Bug tracker" msgstr "Bug tracker" -#: i2p2www/pages/site/docs/index.html:231 +#: i2p2www/pages/site/docs/index.html:236 msgid "Viewmtn inside I2P" msgstr "Viewmtn внутри I2P" -#: i2p2www/pages/site/docs/index.html:233 +#: i2p2www/pages/site/docs/index.html:238 msgid "I2P Source exported to GitHub" msgstr "I2P Source экспортированный в GitHub" -#: i2p2www/pages/site/docs/index.html:235 +#: i2p2www/pages/site/docs/index.html:240 msgid "I2P Source Git Repo inside I2P" msgstr "I2P Source Git Repo внутри I2P" -#: i2p2www/pages/site/docs/index.html:237 +#: i2p2www/pages/site/docs/index.html:242 msgid "Source translation at Transifex" msgstr "Перевод исходников на Transifex" -#: i2p2www/pages/site/docs/index.html:239 +#: i2p2www/pages/site/docs/index.html:244 msgid "Roadmap wiki" msgstr "Roadmap wiki" -#: i2p2www/pages/site/docs/index.html:241 +#: i2p2www/pages/site/docs/index.html:246 msgid "Old roadmap" msgstr "Старый roadmap" -#: i2p2www/pages/site/docs/index.html:241 -#: i2p2www/pages/site/docs/index.html:243 +#: i2p2www/pages/site/docs/index.html:246 +#: i2p2www/pages/site/docs/index.html:248 msgid "not current" msgstr "устаревшее" -#: i2p2www/pages/site/docs/index.html:243 +#: i2p2www/pages/site/docs/index.html:248 msgid "To Do List" msgstr "Список To Do" @@ -905,7 +918,7 @@ msgstr "" "Подробнее смотри ниже." #: i2p2www/pages/site/docs/naming.html:183 -#: i2p2www/pages/site/docs/spec/configuration.html:170 +#: i2p2www/pages/site/docs/spec/configuration.html:184 msgid "Addressbook" msgstr "Адресная книга" @@ -1393,7 +1406,7 @@ msgstr "" "имя не разрешается в пункт назначения." #: i2p2www/pages/site/docs/plugins.html:2 -#: i2p2www/pages/site/docs/spec/configuration.html:138 +#: i2p2www/pages/site/docs/spec/configuration.html:152 msgid "Plugins" msgstr "Плагины" @@ -3139,15 +3152,20 @@ msgid "" msgstr "" #: i2p2www/pages/site/docs/api/i2ptunnel.html:54 +#, fuzzy +msgid "Configuration" +msgstr "Формат файла конфигурации" + +#: i2p2www/pages/site/docs/api/i2ptunnel.html:58 msgid "Client Modes" msgstr "Режимы работы клиента" -#: i2p2www/pages/site/docs/api/i2ptunnel.html:55 -#: i2p2www/pages/site/docs/api/i2ptunnel.html:137 +#: i2p2www/pages/site/docs/api/i2ptunnel.html:59 +#: i2p2www/pages/site/docs/api/i2ptunnel.html:141 msgid "Standard" msgstr "Стандартный" -#: i2p2www/pages/site/docs/api/i2ptunnel.html:56 +#: 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" @@ -3155,7 +3173,7 @@ msgid "" " list of destinations." msgstr "" -#: i2p2www/pages/site/docs/api/i2ptunnel.html:62 +#: i2p2www/pages/site/docs/api/i2ptunnel.html:66 msgid "" "A HTTP-client tunnel. The tunnel connects to the destination specified by" " the URL\n" @@ -3163,34 +3181,34 @@ msgid "" "provided. Strips HTTP connections of the following headers:" msgstr "" -#: i2p2www/pages/site/docs/api/i2ptunnel.html:67 +#: 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 "" -#: i2p2www/pages/site/docs/api/i2ptunnel.html:75 +#: 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 "" -#: i2p2www/pages/site/docs/api/i2ptunnel.html:82 +#: 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 "" -#: i2p2www/pages/site/docs/api/i2ptunnel.html:86 +#: i2p2www/pages/site/docs/api/i2ptunnel.html:90 msgid "Outproxy:" msgstr "" -#: i2p2www/pages/site/docs/api/i2ptunnel.html:87 +#: i2p2www/pages/site/docs/api/i2ptunnel.html:91 msgid "Internal I2P use:" msgstr "" -#: i2p2www/pages/site/docs/api/i2ptunnel.html:92 +#: i2p2www/pages/site/docs/api/i2ptunnel.html:96 msgid "" "Creates a connection to a random IRC server specified by the comma " "seprated (\", \") \n" @@ -3198,43 +3216,43 @@ msgid "" "allowed due to anonymity concerns." msgstr "" -#: i2p2www/pages/site/docs/api/i2ptunnel.html:96 +#: i2p2www/pages/site/docs/api/i2ptunnel.html:100 msgid "Whitelist:" msgstr "Белый список:" -#: i2p2www/pages/site/docs/api/i2ptunnel.html:111 +#: i2p2www/pages/site/docs/api/i2ptunnel.html:115 msgid "Enables using the I2P router as a SOCKS proxy." msgstr "Разрешает использование I2P-маршрутизатора в качестве SOCKS-прокси." -#: i2p2www/pages/site/docs/api/i2ptunnel.html:116 +#: 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" "IRC client mode." msgstr "" -#: i2p2www/pages/site/docs/api/i2ptunnel.html:122 +#: 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 "" -#: i2p2www/pages/site/docs/api/i2ptunnel.html:128 +#: 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" "subscribe to a streamr server tunnel." msgstr "" -#: i2p2www/pages/site/docs/api/i2ptunnel.html:136 +#: i2p2www/pages/site/docs/api/i2ptunnel.html:140 msgid "Server Modes" msgstr "Режимы работы сервера" -#: i2p2www/pages/site/docs/api/i2ptunnel.html:138 +#: i2p2www/pages/site/docs/api/i2ptunnel.html:142 msgid "Creates a destination to a local ip:port with an open TCP port." msgstr "" -#: i2p2www/pages/site/docs/api/i2ptunnel.html:143 +#: 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" @@ -3242,7 +3260,7 @@ msgid "" " such a request." msgstr "" -#: i2p2www/pages/site/docs/api/i2ptunnel.html:149 +#: 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" @@ -3251,14 +3269,14 @@ msgid "" "requests, or loopback-testing an eepsite as a diagnostic tool." msgstr "" -#: i2p2www/pages/site/docs/api/i2ptunnel.html:156 +#: i2p2www/pages/site/docs/api/i2ptunnel.html:160 msgid "" "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:162 +#: 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." @@ -4051,8 +4069,8 @@ msgstr "" #: i2p2www/pages/site/docs/how/tunnel-routing.html:255 #: i2p2www/pages/site/docs/protocol/i2cp.html:687 #: i2p2www/pages/site/docs/protocol/i2np.html:226 -#: i2p2www/pages/site/docs/spec/updates.html:438 -#: i2p2www/pages/site/docs/transport/ntcp.html:535 +#: i2p2www/pages/site/docs/spec/updates.html:488 +#: i2p2www/pages/site/docs/transport/ntcp.html:544 #: i2p2www/pages/site/docs/transport/ssu.html:554 #: i2p2www/pages/site/docs/tunnels/implementation.html:506 msgid "Future Work" @@ -4603,6 +4621,14 @@ 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)." +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" "If done wrong, it could cause real harm to our network.\n" @@ -4611,11 +4637,11 @@ msgid "" "This page discusses some general guidelines." msgstr "" -#: i2p2www/pages/site/docs/applications/embedding.html:18 +#: i2p2www/pages/site/docs/applications/embedding.html:23 msgid "Talk to us" msgstr "" -#: i2p2www/pages/site/docs/applications/embedding.html:19 +#: 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" @@ -4623,11 +4649,11 @@ msgid "" "everyone." msgstr "" -#: i2p2www/pages/site/docs/applications/embedding.html:25 +#: i2p2www/pages/site/docs/applications/embedding.html:30 msgid "Choose your router wisely" msgstr "" -#: i2p2www/pages/site/docs/applications/embedding.html:26 +#: 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" @@ -4637,19 +4663,19 @@ msgid "" "Some of the following only applies to the Java router." msgstr "" -#: i2p2www/pages/site/docs/applications/embedding.html:34 +#: i2p2www/pages/site/docs/applications/embedding.html:39 msgid "Licensing" msgstr "" -#: i2p2www/pages/site/docs/applications/embedding.html:35 +#: i2p2www/pages/site/docs/applications/embedding.html:40 msgid "Ensure you meet the license requirements of the software you are bundling." msgstr "" -#: i2p2www/pages/site/docs/applications/embedding.html:40 +#: i2p2www/pages/site/docs/applications/embedding.html:45 msgid "Verify default configuration" msgstr "" -#: i2p2www/pages/site/docs/applications/embedding.html:41 +#: i2p2www/pages/site/docs/applications/embedding.html:46 msgid "" "A correct default configuration is crucial. Most users will not change " "the defaults.\n" @@ -4658,7 +4684,7 @@ msgid "" "Override the router defaults if necessary." msgstr "" -#: i2p2www/pages/site/docs/applications/embedding.html:46 +#: i2p2www/pages/site/docs/applications/embedding.html:51 msgid "" "Some important defaults to review: Max bandwidth, tunnel quantity and " "length, max participating tunnels.\n" @@ -4666,7 +4692,7 @@ msgid "" "your app." msgstr "" -#: i2p2www/pages/site/docs/applications/embedding.html:50 +#: i2p2www/pages/site/docs/applications/embedding.html:55 msgid "" "Configure enough bandwidth and tunnels to allow your users to contribute " "to the network.\n" @@ -4676,11 +4702,11 @@ msgid "" "example." msgstr "" -#: i2p2www/pages/site/docs/applications/embedding.html:57 +#: i2p2www/pages/site/docs/applications/embedding.html:62 msgid "Participating Traffic Considerations" msgstr "" -#: i2p2www/pages/site/docs/applications/embedding.html:58 +#: 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, " @@ -4692,14 +4718,14 @@ msgid "" "tunnels." msgstr "" -#: i2p2www/pages/site/docs/applications/embedding.html:65 +#: 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" "which is helped tremendously by others building tunnels through you." msgstr "" -#: i2p2www/pages/site/docs/applications/embedding.html:69 +#: i2p2www/pages/site/docs/applications/embedding.html:74 msgid "" "Secondly, over 90% of the routers in the current network allow " "participating traffic.\n" @@ -4711,13 +4737,13 @@ msgid "" " people to enable relaying." msgstr "" -#: i2p2www/pages/site/docs/applications/embedding.html:76 +#: i2p2www/pages/site/docs/applications/embedding.html:81 msgid "" "Thirdly, participating traffic is cover traffic that helps your users' " "anonymity." msgstr "" -#: i2p2www/pages/site/docs/applications/embedding.html:79 +#: i2p2www/pages/site/docs/applications/embedding.html:84 msgid "" "We strongly discourage you from disabling participating traffic by " "default.\n" @@ -4725,11 +4751,11 @@ msgid "" "the network." msgstr "" -#: i2p2www/pages/site/docs/applications/embedding.html:85 +#: i2p2www/pages/site/docs/applications/embedding.html:90 msgid "Persistence" msgstr "" -#: i2p2www/pages/site/docs/applications/embedding.html:86 +#: 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" @@ -4739,11 +4765,11 @@ msgid "" "performance." msgstr "" -#: i2p2www/pages/site/docs/applications/embedding.html:94 +#: i2p2www/pages/site/docs/applications/embedding.html:99 msgid "Configurability" msgstr "" -#: i2p2www/pages/site/docs/applications/embedding.html:95 +#: i2p2www/pages/site/docs/applications/embedding.html:100 msgid "" "Give your users a way to change the configuration of the important " "settings.\n" @@ -4753,11 +4779,11 @@ msgid "" "IP/port may be helpful." msgstr "" -#: i2p2www/pages/site/docs/applications/embedding.html:103 +#: i2p2www/pages/site/docs/applications/embedding.html:108 msgid "Floodfill Considerations" msgstr "" -#: i2p2www/pages/site/docs/applications/embedding.html:104 +#: 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" @@ -4768,11 +4794,11 @@ msgid "" "It also depends on the typical uptime for your application." msgstr "" -#: i2p2www/pages/site/docs/applications/embedding.html:114 +#: i2p2www/pages/site/docs/applications/embedding.html:119 msgid "Reseeding" msgstr "" -#: i2p2www/pages/site/docs/applications/embedding.html:115 +#: 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 " @@ -4780,11 +4806,11 @@ msgid "" "Be aware of possible blocking by hostile governments." msgstr "" -#: i2p2www/pages/site/docs/applications/embedding.html:124 +#: i2p2www/pages/site/docs/applications/embedding.html:129 msgid "Reduce Network Resource Usage" msgstr "" -#: i2p2www/pages/site/docs/applications/embedding.html:125 +#: 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" @@ -4794,11 +4820,11 @@ msgid "" "tunnel, even in the presence of some background DHT activity." msgstr "" -#: i2p2www/pages/site/docs/applications/embedding.html:133 +#: i2p2www/pages/site/docs/applications/embedding.html:138 msgid "Updatability" msgstr "" -#: i2p2www/pages/site/docs/applications/embedding.html:134 +#: 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" @@ -4813,11 +4839,11 @@ msgid "" "which you presumably are not bundling." msgstr "" -#: i2p2www/pages/site/docs/applications/embedding.html:145 +#: i2p2www/pages/site/docs/applications/embedding.html:150 msgid "Rollout" msgstr "" -#: i2p2www/pages/site/docs/applications/embedding.html:146 +#: 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 " @@ -4833,11 +4859,11 @@ msgid "" "checklist is." msgstr "" -#: i2p2www/pages/site/docs/applications/embedding.html:158 +#: i2p2www/pages/site/docs/applications/embedding.html:163 msgid "Design for and Encourage Long Uptimes" msgstr "" -#: i2p2www/pages/site/docs/applications/embedding.html:159 +#: 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 " @@ -4846,53 +4872,53 @@ msgid "" "solution." msgstr "" -#: i2p2www/pages/site/docs/applications/embedding.html:167 +#: i2p2www/pages/site/docs/applications/embedding.html:172 msgid "Show Status" msgstr "" -#: i2p2www/pages/site/docs/applications/embedding.html:168 +#: i2p2www/pages/site/docs/applications/embedding.html:173 msgid "" "Provide some indication to the user that the application tunnels are " "ready. Encourage patience." msgstr "" -#: i2p2www/pages/site/docs/applications/embedding.html:173 +#: i2p2www/pages/site/docs/applications/embedding.html:178 msgid "Graceful Shutdown" msgstr "" -#: i2p2www/pages/site/docs/applications/embedding.html:174 +#: 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 "" -#: i2p2www/pages/site/docs/applications/embedding.html:180 +#: i2p2www/pages/site/docs/applications/embedding.html:185 msgid "Education and Donation" msgstr "" -#: i2p2www/pages/site/docs/applications/embedding.html:181 +#: 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 "" -#: i2p2www/pages/site/docs/applications/embedding.html:187 +#: i2p2www/pages/site/docs/applications/embedding.html:192 msgid "External Router Option" msgstr "" -#: i2p2www/pages/site/docs/applications/embedding.html:188 +#: 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 "" -#: i2p2www/pages/site/docs/applications/embedding.html:195 +#: i2p2www/pages/site/docs/applications/embedding.html:200 msgid "Use of other Common Services" msgstr "" -#: i2p2www/pages/site/docs/applications/embedding.html:196 +#: 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" @@ -4900,11 +4926,11 @@ msgid "" "and talk to the people who are running them to make sure it's ok." msgstr "" -#: i2p2www/pages/site/docs/applications/embedding.html:204 +#: i2p2www/pages/site/docs/applications/embedding.html:209 msgid "Time / NTP Issues" msgstr "" -#: i2p2www/pages/site/docs/applications/embedding.html:205 +#: 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. " @@ -4913,11 +4939,11 @@ msgid "" "clock is correct." msgstr "" -#: i2p2www/pages/site/docs/applications/embedding.html:213 +#: i2p2www/pages/site/docs/applications/embedding.html:218 msgid "Choose What and How you Bundle" msgstr "" -#: i2p2www/pages/site/docs/applications/embedding.html:214 +#: 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" @@ -4935,11 +4961,19 @@ msgid "" "and i2psnark, for example." msgstr "" -#: i2p2www/pages/site/docs/applications/embedding.html:228 +#: i2p2www/pages/site/docs/applications/embedding.html:233 +msgid "You may also wish to bundle a hosts.txt file." +msgstr "" + +#: i2p2www/pages/site/docs/applications/embedding.html:236 +msgid "Be sure to specify a Java 6 bootclasspath if compiling with Java 8." +msgstr "" + +#: i2p2www/pages/site/docs/applications/embedding.html:244 msgid "Datagram (DHT) considerations" msgstr "" -#: i2p2www/pages/site/docs/applications/embedding.html:229 +#: 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 " @@ -4955,32 +4989,32 @@ msgid "" "have several." msgstr "" -#: i2p2www/pages/site/docs/applications/embedding.html:242 +#: i2p2www/pages/site/docs/applications/embedding.html:258 msgid "Comarketing" msgstr "" -#: i2p2www/pages/site/docs/applications/embedding.html:243 +#: 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 "" -#: i2p2www/pages/site/docs/applications/embedding.html:249 +#: i2p2www/pages/site/docs/applications/embedding.html:265 msgid "Malware" msgstr "" -#: i2p2www/pages/site/docs/applications/embedding.html:250 +#: i2p2www/pages/site/docs/applications/embedding.html:266 msgid "" "Please don't use I2P for evil.\n" "It could cause great harm both to our network and our reputation." msgstr "" -#: i2p2www/pages/site/docs/applications/embedding.html:256 +#: i2p2www/pages/site/docs/applications/embedding.html:272 msgid "Join Us" msgstr "" -#: i2p2www/pages/site/docs/applications/embedding.html:257 +#: 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" @@ -4988,11 +5022,11 @@ msgid "" "We can help get you users, testers, translators, or even coders." msgstr "" -#: i2p2www/pages/site/docs/applications/embedding.html:265 +#: i2p2www/pages/site/docs/applications/embedding.html:281 msgid "Application Examples" msgstr "" -#: i2p2www/pages/site/docs/applications/embedding.html:266 +#: 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" @@ -5002,17 +5036,17 @@ msgid "" " and Monero." msgstr "" -#: i2p2www/pages/site/docs/applications/embedding.html:274 +#: i2p2www/pages/site/docs/applications/embedding.html:290 msgid "Code Example" msgstr "" -#: i2p2www/pages/site/docs/applications/embedding.html:275 +#: i2p2www/pages/site/docs/applications/embedding.html:291 msgid "" "None of the above actually tells you how to write your code to\n" "bundle the Java router, so following is a brief example." msgstr "" -#: i2p2www/pages/site/docs/applications/embedding.html:290 +#: 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" @@ -7926,7 +7960,6 @@ msgid "The Network Database" msgstr "Сетевая база данных" #: i2p2www/pages/site/docs/how/network-database.html:3 -#: i2p2www/pages/site/docs/transport/ntcp.html:3 msgid "October 2014" msgstr "" @@ -15198,10 +15231,6 @@ msgstr "" msgid "Configuration File Specification" msgstr "" -#: i2p2www/pages/site/docs/spec/configuration.html:3 -msgid "January 2014" -msgstr "Январь 2014" - #: i2p2www/pages/site/docs/spec/configuration.html:7 msgid "" "This page provides a general specification of I2P configuration files,\n" @@ -15310,65 +15339,66 @@ msgid "Configured via /configlogging in the router console." msgstr "" #: i2p2www/pages/site/docs/spec/configuration.html:112 -#: i2p2www/pages/site/docs/spec/configuration.html:142 -#: i2p2www/pages/site/docs/spec/configuration.html:154 +#: i2p2www/pages/site/docs/spec/configuration.html:156 +#: i2p2www/pages/site/docs/spec/configuration.html:168 +#: i2p2www/pages/site/docs/spec/configuration.html:198 msgid "Properties are as follows:" msgstr "" -#: i2p2www/pages/site/docs/spec/configuration.html:133 +#: i2p2www/pages/site/docs/spec/configuration.html:147 msgid "Individual Plugin" msgstr "" -#: i2p2www/pages/site/docs/spec/configuration.html:134 +#: i2p2www/pages/site/docs/spec/configuration.html:148 #, python-format msgid "See the plugin specification." msgstr "" -#: i2p2www/pages/site/docs/spec/configuration.html:139 +#: i2p2www/pages/site/docs/spec/configuration.html:153 msgid "Enable/disable for each installed plugin." msgstr "" -#: i2p2www/pages/site/docs/spec/configuration.html:150 +#: i2p2www/pages/site/docs/spec/configuration.html:164 msgid "Webapps" msgstr "" -#: i2p2www/pages/site/docs/spec/configuration.html:151 +#: i2p2www/pages/site/docs/spec/configuration.html:165 msgid "Enable/disable for each installed webapp." msgstr "" -#: i2p2www/pages/site/docs/spec/configuration.html:163 +#: i2p2www/pages/site/docs/spec/configuration.html:177 msgid "Router" msgstr "" -#: i2p2www/pages/site/docs/spec/configuration.html:164 +#: i2p2www/pages/site/docs/spec/configuration.html:178 msgid "Configured via /configadvanced in the router console." msgstr "" -#: i2p2www/pages/site/docs/spec/configuration.html:168 +#: i2p2www/pages/site/docs/spec/configuration.html:182 msgid "Applications" msgstr "" -#: i2p2www/pages/site/docs/spec/configuration.html:171 +#: i2p2www/pages/site/docs/spec/configuration.html:185 msgid "See documentation in SusiDNS." msgstr "" -#: i2p2www/pages/site/docs/spec/configuration.html:176 +#: i2p2www/pages/site/docs/spec/configuration.html:190 msgid "Configured via the application gui." msgstr "" -#: i2p2www/pages/site/docs/spec/configuration.html:181 +#: i2p2www/pages/site/docs/spec/configuration.html:195 msgid "Configured via the /i2ptunnel application in the router console." msgstr "" -#: i2p2www/pages/site/docs/spec/configuration.html:185 +#: i2p2www/pages/site/docs/spec/configuration.html:364 msgid "Router Console" msgstr "" -#: i2p2www/pages/site/docs/spec/configuration.html:186 +#: i2p2www/pages/site/docs/spec/configuration.html:365 msgid "The router console uses the router.config file." msgstr "" -#: i2p2www/pages/site/docs/spec/configuration.html:191 +#: i2p2www/pages/site/docs/spec/configuration.html:370 msgid "See post on zzz.i2p." msgstr "" @@ -15763,6 +15793,7 @@ msgstr "" #: i2p2www/pages/site/docs/spec/updates.html:204 #: i2p2www/pages/site/docs/spec/updates.html:313 +#: i2p2www/pages/site/docs/spec/updates.html:365 msgid "Goals:" msgstr "" @@ -15785,7 +15816,8 @@ msgid "One-pass signature verification and file extraction" msgstr "" #: i2p2www/pages/site/docs/spec/updates.html:222 -#: i2p2www/pages/site/docs/spec/updates.html:336 +#: i2p2www/pages/site/docs/spec/updates.html:328 +#: i2p2www/pages/site/docs/spec/updates.html:388 msgid "Specification:" msgstr "" @@ -15794,40 +15826,80 @@ msgid "All unused fields must be set to 0 for compatibility with future versions msgstr "" #: i2p2www/pages/site/docs/spec/updates.html:308 -msgid "SU3 News File Specification" -msgstr "" +#, fuzzy +msgid "SU3 Reseed File Specification" +msgstr "Спецификация построения туннеля" #: i2p2www/pages/site/docs/spec/updates.html:309 -msgid "As of 0.9.17, the news is delivered in an \"su3\" file format." +msgid "As of 0.9.14, reseed data is delivered in an \"su3\" file format." msgstr "" #: i2p2www/pages/site/docs/spec/updates.html:316 -msgid "Signed news with strong signatures and trusted certificates" +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 "" -#: i2p2www/pages/site/docs/spec/updates.html:319 +#: 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 "" -#: i2p2www/pages/site/docs/spec/updates.html:322 -msgid "Standard XML format for use with standard parsers" -msgstr "" - -#: i2p2www/pages/site/docs/spec/updates.html:325 -msgid "Standard Atom format for use with standard feed readers and generators" -msgstr "" - -#: i2p2www/pages/site/docs/spec/updates.html:328 -msgid "Sanitization and verification of HTML before displaying on console" +#: i2p2www/pages/site/docs/spec/updates.html:323 +msgid "" +"Single compressed file to speed up reseeding, which was slow to fetch 200" +" files" msgstr "" #: i2p2www/pages/site/docs/spec/updates.html:331 +msgid "The file must be named \"i2pseeds.su3\"." +msgstr "" + +#: i2p2www/pages/site/docs/spec/updates.html:334 +msgid "" +"The file must be in the same directory as the router infos on the web " +"server." +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" +"and then fetch the individual router info files found in the links." +msgstr "" + +#: i2p2www/pages/site/docs/spec/updates.html:360 +msgid "SU3 News File Specification" +msgstr "" + +#: i2p2www/pages/site/docs/spec/updates.html:361 +msgid "As of 0.9.17, the news is delivered in an \"su3\" file format." +msgstr "" + +#: i2p2www/pages/site/docs/spec/updates.html:368 +msgid "Signed news with strong signatures and trusted certificates" +msgstr "" + +#: i2p2www/pages/site/docs/spec/updates.html:374 +msgid "Standard XML format for use with standard parsers" +msgstr "" + +#: i2p2www/pages/site/docs/spec/updates.html:377 +msgid "Standard Atom format for use with standard feed readers and generators" +msgstr "" + +#: i2p2www/pages/site/docs/spec/updates.html:380 +msgid "Sanitization and verification of HTML before displaying on console" +msgstr "" + +#: i2p2www/pages/site/docs/spec/updates.html:383 msgid "" "Suitable for easy implementation on Android and other platforms without " "an HTML console" msgstr "" -#: i2p2www/pages/site/docs/spec/updates.html:440 +#: 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" @@ -16420,7 +16492,7 @@ msgstr "" #: i2p2www/pages/site/docs/transport/ntcp.html:207 #: i2p2www/pages/site/docs/transport/ntcp.html:250 #: i2p2www/pages/site/docs/transport/ntcp.html:332 -#: i2p2www/pages/site/docs/transport/ntcp.html:428 +#: i2p2www/pages/site/docs/transport/ntcp.html:437 msgid "Size:" msgstr "Размер:" @@ -16438,7 +16510,7 @@ msgstr "" #: i2p2www/pages/site/docs/transport/ntcp.html:236 #: i2p2www/pages/site/docs/transport/ntcp.html:319 -#: i2p2www/pages/site/docs/transport/ntcp.html:397 +#: i2p2www/pages/site/docs/transport/ntcp.html:398 msgid "Notes:" msgstr "" @@ -16458,7 +16530,7 @@ msgstr "" #: i2p2www/pages/site/docs/transport/ntcp.html:252 #: i2p2www/pages/site/docs/transport/ntcp.html:334 -#: i2p2www/pages/site/docs/transport/ntcp.html:430 +#: i2p2www/pages/site/docs/transport/ntcp.html:439 msgid "Unencrypted Contents:" msgstr "" @@ -16482,7 +16554,7 @@ msgstr "" #: i2p2www/pages/site/docs/transport/ntcp.html:285 #: i2p2www/pages/site/docs/transport/ntcp.html:376 -#: i2p2www/pages/site/docs/transport/ntcp.html:457 +#: i2p2www/pages/site/docs/transport/ntcp.html:466 msgid "Encrypted Contents:" msgstr "" @@ -16519,7 +16591,7 @@ msgid "Alice's 387+ byte `RouterIdentity`" msgstr "" #: i2p2www/pages/site/docs/transport/ntcp.html:366 -#: i2p2www/pages/site/docs/transport/ntcp.html:452 +#: i2p2www/pages/site/docs/transport/ntcp.html:461 msgid "0-15 bytes random data" msgstr "" @@ -16540,31 +16612,31 @@ msgid "" "of message #1) as the IV" msgstr "" -#: i2p2www/pages/site/docs/transport/ntcp.html:399 +#: i2p2www/pages/site/docs/transport/ntcp.html:400 msgid "Bob verifies the signature, and on failure, drops the connection." msgstr "" -#: i2p2www/pages/site/docs/transport/ntcp.html:402 +#: i2p2www/pages/site/docs/transport/ntcp.html:403 msgid "" "Bob may drop the connection if the clock skew with Alice is too high as " "calculated using tsA." msgstr "" -#: i2p2www/pages/site/docs/transport/ntcp.html:405 +#: 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 "" -#: i2p2www/pages/site/docs/transport/ntcp.html:421 +#: i2p2www/pages/site/docs/transport/ntcp.html:430 msgid "Message 4 (Session Confirm B)" msgstr "" -#: i2p2www/pages/site/docs/transport/ntcp.html:422 +#: i2p2www/pages/site/docs/transport/ntcp.html:431 msgid "This is a signature of the critical data. Bob sends Alice:" msgstr "" -#: i2p2www/pages/site/docs/transport/ntcp.html:446 +#: i2p2www/pages/site/docs/transport/ntcp.html:455 msgid "" "the `Signature` of the following concatenated data:\n" " X, Y, Alice's `RouterIdentity`, tsA, tsB.\n" @@ -16572,7 +16644,7 @@ msgid "" "the `SigningPublicKey` in his `RouterIdentity`" msgstr "" -#: i2p2www/pages/site/docs/transport/ntcp.html:470 +#: i2p2www/pages/site/docs/transport/ntcp.html:479 #, python-format msgid "" "Data AES encrypted using the DH " @@ -16583,21 +16655,21 @@ msgid "" "signature types" msgstr "" -#: i2p2www/pages/site/docs/transport/ntcp.html:479 +#: i2p2www/pages/site/docs/transport/ntcp.html:488 msgid "Alice verifies the signature, and on failure, drops the connection." msgstr "" -#: i2p2www/pages/site/docs/transport/ntcp.html:482 +#: 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 "" -#: i2p2www/pages/site/docs/transport/ntcp.html:497 +#: i2p2www/pages/site/docs/transport/ntcp.html:506 msgid "After Establishment" msgstr "" -#: i2p2www/pages/site/docs/transport/ntcp.html:498 +#: i2p2www/pages/site/docs/transport/ntcp.html:507 msgid "" "The connection is established, and standard or time sync messages may be " "exchanged.\n" @@ -16609,11 +16681,11 @@ msgid "" " the next IV." msgstr "" -#: i2p2www/pages/site/docs/transport/ntcp.html:507 +#: i2p2www/pages/site/docs/transport/ntcp.html:516 msgid "Check Connection Message" msgstr "" -#: i2p2www/pages/site/docs/transport/ntcp.html:508 +#: i2p2www/pages/site/docs/transport/ntcp.html:517 msgid "" "Alternately, when Bob receives a connection, it could be a\n" "check connection (perhaps prompted by Bob asking for someone\n" @@ -16623,58 +16695,58 @@ msgid "" "A check info connection will receive 256 bytes containing:" msgstr "" -#: i2p2www/pages/site/docs/transport/ntcp.html:517 +#: i2p2www/pages/site/docs/transport/ntcp.html:526 msgid "32 bytes of uninterpreted, ignored data" msgstr "" -#: i2p2www/pages/site/docs/transport/ntcp.html:518 +#: i2p2www/pages/site/docs/transport/ntcp.html:527 msgid "1 byte size" msgstr "" -#: i2p2www/pages/site/docs/transport/ntcp.html:519 +#: 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 "" -#: i2p2www/pages/site/docs/transport/ntcp.html:520 +#: i2p2www/pages/site/docs/transport/ntcp.html:529 msgid "2 byte port number that the local router was reached on" msgstr "" -#: i2p2www/pages/site/docs/transport/ntcp.html:521 +#: i2p2www/pages/site/docs/transport/ntcp.html:530 msgid "" "4 byte i2p network time as known by the remote side (seconds since the " "epoch)" msgstr "" -#: i2p2www/pages/site/docs/transport/ntcp.html:522 +#: i2p2www/pages/site/docs/transport/ntcp.html:531 msgid "uninterpreted padding data, up to byte 223" msgstr "" -#: i2p2www/pages/site/docs/transport/ntcp.html:523 +#: 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 "" -#: i2p2www/pages/site/docs/transport/ntcp.html:526 +#: i2p2www/pages/site/docs/transport/ntcp.html:535 msgid "Check connection is completely disabled as of release 0.9.12." msgstr "" -#: i2p2www/pages/site/docs/transport/ntcp.html:530 +#: i2p2www/pages/site/docs/transport/ntcp.html:539 msgid "Discussion" msgstr "Обсуждение" -#: i2p2www/pages/site/docs/transport/ntcp.html:531 +#: i2p2www/pages/site/docs/transport/ntcp.html:540 #, python-format msgid "Now on the NTCP Discussion Page." msgstr "" -#: i2p2www/pages/site/docs/transport/ntcp.html:537 +#: i2p2www/pages/site/docs/transport/ntcp.html:546 msgid "The maximum message size should be increased to approximately 32 KB." msgstr "" -#: i2p2www/pages/site/docs/transport/ntcp.html:541 +#: 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" @@ -16685,13 +16757,13 @@ msgid "" "to create a limited number of message sizes." msgstr "" -#: i2p2www/pages/site/docs/transport/ntcp.html:549 +#: 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 "" -#: i2p2www/pages/site/docs/transport/ntcp.html:553 +#: 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?" diff --git a/i2p2www/translations/ru/LC_MESSAGES/get-involved.po b/i2p2www/translations/ru/LC_MESSAGES/get-involved.po index 22c33a9f..22b6d463 100644 --- a/i2p2www/translations/ru/LC_MESSAGES/get-involved.po +++ b/i2p2www/translations/ru/LC_MESSAGES/get-involved.po @@ -12,7 +12,7 @@ msgid "" msgstr "" "Project-Id-Version: I2P\n" "Report-Msgid-Bugs-To: http://trac.i2p2.de\n" -"POT-Creation-Date: 2014-10-22 20:13+0000\n" +"POT-Creation-Date: 2014-11-27 12:12+0000\n" "PO-Revision-Date: 2014-11-01 20:07+0000\n" "Last-Translator: yume\n" "Language-Team: Russian (Russia) " @@ -511,468 +511,56 @@ msgstr "" "Участвуй!" #: i2p2www/pages/site/get-involved/todo.html:15 -#: i2p2www/pages/site/get-involved/todo.html:53 +#: i2p2www/pages/site/get-involved/todo.html:38 msgid "Core functionality" msgstr "Основная функциональность" #: i2p2www/pages/site/get-involved/todo.html:15 -#: i2p2www/pages/site/get-involved/todo.html:27 -#: i2p2www/pages/site/get-involved/todo.html:51 +#: i2p2www/pages/site/get-involved/todo.html:21 +#: i2p2www/pages/site/get-involved/todo.html:36 msgid "link" msgstr "ссылка" #: i2p2www/pages/site/get-involved/todo.html:17 -#: i2p2www/pages/site/get-involved/todo.html:56 -msgid "NAT/Firewall bridging via 1-hop restricted routes" -msgstr "Преодоление NAT/Firewall в ограниченных маршрутах с 1 прыжком" - -#: i2p2www/pages/site/get-involved/todo.html:20 -#: i2p2www/pages/site/get-involved/todo.html:129 -msgid "High degree transport layer with UDP, NBIO, or NIO" -msgstr "Высокоуровневый маршрут с UDP, NBIO, or NIO" - -#: i2p2www/pages/site/get-involved/todo.html:23 -#: i2p2www/pages/site/get-involved/todo.html:217 +#: i2p2www/pages/site/get-involved/todo.html:41 msgid "NetworkDB and profile tuning and ejection policy for large nets" msgstr "NetworkDB, настройка профиля и политика исключения для больших сетей" -#: i2p2www/pages/site/get-involved/todo.html:27 -#: i2p2www/pages/site/get-involved/todo.html:241 +#: i2p2www/pages/site/get-involved/todo.html:21 +#: i2p2www/pages/site/get-involved/todo.html:65 msgid "Security / anonymity" msgstr "Безопасность / анонимность" -#: i2p2www/pages/site/get-involved/todo.html:29 -#: i2p2www/pages/site/get-involved/todo.html:244 -msgid "" -"Per-hop tunnel id & new permuted TunnelVerificationStructure " -"encryption" -msgstr "" -"Идентификатор туннеля для каждого прыжка & переменное шифрование " -"TunnelVerificationStructure" - -#: i2p2www/pages/site/get-involved/todo.html:32 -#: i2p2www/pages/site/get-involved/todo.html:294 -msgid "Strict ordering of participants within tunnels" -msgstr "Строгая последовательность участников в туннеле" - -#: i2p2www/pages/site/get-involved/todo.html:35 -msgid "Randomly permuted tunnel lengths" -msgstr "Случайное изменение длины туннеля" - -#: i2p2www/pages/site/get-involved/todo.html:38 -#: i2p2www/pages/site/get-involved/todo.html:356 +#: 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-прыжковые ограниченные маршруты с необязательными" " доверенными ссылками" -#: i2p2www/pages/site/get-involved/todo.html:41 -#: i2p2www/pages/site/get-involved/todo.html:375 +#: 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 "Hashcash для запросов идентификатора маршрута, пункта назначения и туннеля" -#: i2p2www/pages/site/get-involved/todo.html:44 -#: i2p2www/pages/site/get-involved/todo.html:404 +#: 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 "" "Расширенные операции над туннелем " "(пакетирование/смешивание/регулирование/изменение размера)" -#: i2p2www/pages/site/get-involved/todo.html:47 -#: i2p2www/pages/site/get-involved/todo.html:441 +#: i2p2www/pages/site/get-involved/todo.html:32 +#: i2p2www/pages/site/get-involved/todo.html:153 msgid "Stop & go mix w/ garlics & tunnels" msgstr "Задержка совместно с чесночной маршрутизацией & туннелями" -#: i2p2www/pages/site/get-involved/todo.html:51 -#: i2p2www/pages/site/get-involved/todo.html:455 +#: i2p2www/pages/site/get-involved/todo.html:36 +#: i2p2www/pages/site/get-involved/todo.html:167 msgid "Performance" msgstr "Производительность" -#: i2p2www/pages/site/get-involved/todo.html:61 -msgid "Implemented in I2P 0.6.0.6" -msgstr "Реализовано в I2P 0.6.0.6" - -#: i2p2www/pages/site/get-involved/todo.html:62 -msgid "" -"The functionality of allowing routers to fully participate within the " -"network \n" -"while behind firewalls and NATs that they do not control requires some " -"basic \n" -"restricted route operation (since those peers will not be able to receive" -" \n" -"inbound connections). To do this successfully, you consider peers one of" -" \n" -"two ways:" -msgstr "" -"Функциональность, позволяющая маршрутизатору, находящемуся за " -"брандмауэром или NAT, \n" -"которые он не контролирует, полностью взаимодействовать с сетью, " -"нуждается в некоторых основных\n" -"операциях ограниченного маршрута (т.к. эти узлы не смогут принимать \n" -"входящие подключения). Для этого мы считаем, что узлы могут быть одного\n" -"из двух возможных типов:" - -#: i2p2www/pages/site/get-involved/todo.html:72 -msgid "" -"Peers who have reachable interfaces - these peers do not need to \n" -"do anything special" -msgstr "" -"Узлы, имеющие доступные интерфейсы - этим узлам не нужно \n" -"делать ничего особенного" - -#: i2p2www/pages/site/get-involved/todo.html:76 -msgid "" -"Peers who do not have reachable interfaces - these peers must " -"build \n" -"a tunnel pointing at them where the gateway is one of the peers they have" -" \n" -"established a connection with who has both a publicly reachable interface" -" \n" -"and who has agreed to serve as their 'introducer'." -msgstr "" -"Узлы, не имеющие доступных интерфейсов - эти узлы должны построить" -" \n" -"туннель, указывающий на них, где шлюзом выступает один из узлов, с " -"которым \n" -"они установили соединение, последний должен иметь доступный для всех " -"интерфейс \n" -"и согласиться служить их 'представителем'." - -#: i2p2www/pages/site/get-involved/todo.html:84 -msgid "" -"To do this, peers who have no IP address simply connect to a few peers, \n" -"build a tunnel through them, and publish a reference to those tunnels " -"within \n" -"their RouterInfo structure in the network database." -msgstr "" -"Чтобы сделать это, узлы, у которых нет IP адреса, просто подключаются к " -"нескольким узлам, \n" -"строят туннель между ними, и публикуют ссылку на эти туннели внутри \n" -"их структуры RouterInfo в базе данных сети." - -#: i2p2www/pages/site/get-involved/todo.html:89 -msgid "" -"When someone wants to contact any particular router, they first must get" -" \n" -"its RouterInfo from the network database, which will tell them whether " -"they \n" -"can connect directly (e.g. the peer has a publicly reachable interface) \n" -"or whether they need to contact them indirectly. Direct connections occur" -" \n" -"as normal, while indirect connections are done through one of the " -"published \n" -"tunnels." -msgstr "" -"Когда кто-нибудь хочет обратиться к определенному маршрутизатору, сначала" -" он должен получить \n" -"RouterInfo этого маршрутизатора из базы данных сети, который подскажет - " -"можно ли ему \n" -"подключиться напрямую (т.к. узел имеет общедоступный интерфейс) \n" -"или нет. Прямые подключения устанавливаются\n" -"обычным способом, в то время как непрямые соединения устанавливаются " -"через один из опубликованных \n" -"туннелей." - -#: i2p2www/pages/site/get-involved/todo.html:97 -msgid "" -"When a router just wants to get a message or two to a specific hidden " -"peer, \n" -"they can just use the indirect tunnel for sending the payload. However, \n" -"if the router wants to talk to the hidden peer often (for instance, as " -"part \n" -"of a tunnel), they will send a garlic routed message through the indirect" -" \n" -"tunnel to that hidden peer which unwraps to contain a message which " -"should \n" -"be sent to the originating router. That hidden peer then establishes an \n" -"outbound connection to the originating router and from then on, those two" -" \n" -"routers can talk to each other directly over that newly established " -"direct \n" -"connection." -msgstr "" -"Когда маршрутизатор хочет доставить всего одно или два сообщения " -"определенному скрытому узлу, \n" -"он может использовать непрямой туннель для отправки трафика. Тем не " -"менее, \n" -"если маршрутизатор хочет часто общаться со скрытым узлом (например, как " -"с частью \n" -"туннеля), он отправит чесночно маршрутизированное сообщение через " -"непрямой \n" -"туннель этому скрытому узлу, которое распаковывается до сообщения, \n" -"которое должно быть послано исходному маршрутизатору. Затем этот скрытый " -"узел устанавливает \n" -"исходящее соединение с исходным маршрутизатором, и, затем, эти два " -"маршрутизатора \n" -"могут общаться друг с другом напрямую через это новое установленное \n" -"прямое соединение." - -#: i2p2www/pages/site/get-involved/todo.html:108 -msgid "" -"Of course, that only works if the originating peer can receive " -"connections \n" -"(they aren't also hidden). However, if the originating peer is hidden, " -"they \n" -"can simply direct the garlic routed message to come back to the " -"originating \n" -"peer's inbound tunnel." -msgstr "" -"Конечно, это работает только если исходный узел может принимать " -"подключения \n" -"(он не скрыт). Тем не менее, если исходный узел скрыт, он \n" -"может направить чесночно маршрутизированное сообщение обратно исходному \n" -"узлу по его входящему туннелю." - -#: i2p2www/pages/site/get-involved/todo.html:114 -msgid "" -"This is not meant to provide a way for a peer's IP address to be " -"concealed, \n" -"merely as a way to let people behind firewalls and NATs fully operate " -"within \n" -"the network. Concealing the peer's IP address adds a little more work, as" -" \n" -"described below." -msgstr "" -"Это не способ скрыть IP адреса узлов, наоборот - этот способ позволяет " -"людям \n" -"за брандмауэром или NAT полноценно пользоваться сетью. \n" -"Сокрытие IP адресов узлов добавляет немного больше работы, как\n" -"описано ниже." - -#: i2p2www/pages/site/get-involved/todo.html:120 -msgid "" -"With this technique, any router can participate as any part of a tunnel." -" \n" -"For efficiency purposes, a hidden peer would be a bad choice for an " -"inbound \n" -"gateway, and within any given tunnel, two neighboring peers wouldn't want" -" \n" -"to be hidden. But that is not technically necessary." -msgstr "" -"Таким способом любой маршрутизатор может выступать любой частью туннеля." -" \n" -"С точки зрения эффективности, скрытый узел будет плохим вариантом в " -"качестве \n" -"входящего шлюза, и внутри любого туннеля два соседних узлане захотят \n" -"быть скрытыми. Но технически это не важно." - -#: i2p2www/pages/site/get-involved/todo.html:132 -msgid "Both UDP and NIO have been Implemented in I2P" -msgstr "И UDP, и NIO были реализованы в I2P" - -#: i2p2www/pages/site/get-involved/todo.html:133 -msgid "" -"Standard TCP communication in Java generally requires blocking socket \n" -"calls, and to keep a blocked socket from hanging the entire system, those" -" \n" -"blocking calls are done on their own threads. Our current TCP transport \n" -"is implemented in a naive fashion - for each peer we are talking to, we \n" -"have one thread reading and one thread writing. The reader thread simply" -" \n" -"loops a bunch of read() calls, building I2NP messages and adding them \n" -"to our internal inbound message queue, and the writer thread pulls " -"messages \n" -"off a per-connection outbound message queue and shoves the data through \n" -"write() calls." -msgstr "" -"В Java для стандартного соединения TCP обычно требуется блокирующий вызов" -" сокета,\n" -"и, чтобы предотвратить подвисание системы этим блокированным сокетом,\n" -"эти блокирующие вызовы выполняются в их собственных потоках. Наш текущий " -"транспорт TCP\n" -"реализуется в родном виде - для каждого узла, к которому мы обращаемся,\n" -"мы имеем один поток для чтения и один для записи. Читающий поток " -"выполняет\n" -"цикл вызовов read(), строит сообщение I2NP и добавляет его \n" -"во внутреннюю очередь входящих сообщений, а записывающий поток вытягивает" -"\n" -"сообщения из очереди исходящих сообщений каждого соединения и пропихивает" -" данные \n" -"вызовом write()." - -#: i2p2www/pages/site/get-involved/todo.html:144 -msgid "" -"We do this fairly efficiently, from a CPU perspective - at any time, \n" -"almost all of these threads are sitting idle, blocked waiting for " -"something \n" -"to do. However, each thread consumes real resources (on older Linux " -"kernels, \n" -"for instance, each thread would often be implemented as a fork()'ed " -"process). \n" -"As the network grows, the number of peers each router will want to talk \n" -"with will increase (remember, I2P is fully connected, meaning that any \n" -"given peer should know how to get a message to any other peer, and " -"restricted \n" -"route support will probably not significantly reduce the number of " -"connections \n" -"necessary). This means that with a 100,000 router network, each router \n" -"will have up to 199,998 threads just to deal with the TCP connections!" -msgstr "" -"Мы делаем это довольно эффективно, с точки зрения CPU - в любой момент " -"времени \n" -"почти все эти потоки ничего не делают, блокированные в ожидании работы. \n" -"Тем не менее, каждый поток потребляет реальные системные ресурсы (на " -"старых ядрах Linux,\n" -"например, каждый поток будет реализован как fork()-нутый процесс). \n" -"С ростом сети число узлов, с которым маршрутизатор захочет общаться, \n" -"будет увеличиваться (запомните, I2P - полностью связана, это означает что" -" любой\n" -"узел должен знать как доставить сообщение любому другому узлу, и " -"поддержка \n" -"ограниченного маршрута, возможно, не существенно уменьшит число " -"необходимых\n" -" соединений). Это означает, что в сети с 100,000 маршрутизаторов, каждый " -"маршрутизатор \n" -"будет иметь 199,998 потоков только для поддержки TCP соединений!" - -#: i2p2www/pages/site/get-involved/todo.html:156 -msgid "" -"Obviously, that just won't work. We need to use a transport layer that \n" -"can scale. In Java, we have two main camps:" -msgstr "" -"Очевидно, это просто не будет работать. Мы должны использовать " -"масштабируемый \n" -"транспортный уровень. В Java у нас есть два основных лагеря:" - -#: i2p2www/pages/site/get-involved/todo.html:161 -#, python-format -msgid "" -"Implemented in I2P 0.6 (\"SSU\") as documented elsewhere" -msgstr "" -"Реализованный в I2P 0.6 (\"SSU\"), согласно описанию" - -#: i2p2www/pages/site/get-involved/todo.html:164 -msgid "" -"Sending and receiving UDP datagrams is a connectionless operation - if \n" -"we are communicating with 100,000 peers, we simply stick the UDP packets" -" \n" -"in a queue and have a single thread pulling them off the queue and " -"shoving \n" -"them out the pipe (and to receive, have a single thread pulling in any \n" -"UDP packets received and adding them to an inbound queue)." -msgstr "" -"Отправка и получение дейтаграмм UDP - это операция без установления " -"соединения - если\n" -"мы общаемся с 100,000 узлами, мы просто собираем пакеты UDP \n" -"в очередь и, имеем один поток, извлекающий их из очереди, и отправляющий" -" \n" -"их в канал соединения (и, для получения, имеем один поток принимающий " -"любые \n" -"пакеты UDP и добавляющий их во входящую очередь)." - -#: i2p2www/pages/site/get-involved/todo.html:171 -msgid "" -"However, moving to UDP means losing the benefits of TCP's ordering, " -"congestion \n" -"control, MTU discovery, etc. Implementing that code will take significant" -" \n" -"work, however I2P doesn't need it to be as strong as TCP. Specifically, \n" -"a while ago I was taking some measurements in the simulator and on the \n" -"live net, and the vast majority of messages transferred would fit easily" -" \n" -"within a single unfragmented UDP packet, and the largest of the messages" -" \n" -"would fit within 20-30 packets. As mule pointed out, TCP adds a " -"significant \n" -"overhead when dealing with so many small packets, as the ACKs are within" -" \n" -"an order of magnitude in size. With UDP, we can optimize the transport \n" -"for both efficiency and resilience by taking into account I2P's " -"particular \n" -"needs." -msgstr "" -"Тем не менее, движение в сторону UDP означает потерю преимуществ TCP: \n" -"очередности, контроля блокировок, определения MTU и т.д. Реализация этого" -" \n" -"кода - это значительная работа, тем не менее, I2P не должна быть такой же" -" устойчивой, как TCP.\n" -"Конкретно, недавно я собирал метрики в симуляторе и в живой сети, \n" -"и подавляющее большинство переданных сообщений легко уместилось бы \n" -"в одном нефрагментированном пакете UDP, а самое большое из сообщений \n" -"уместилось бы в 20-30 пакетах. Как показал mule, TCP добавляет " -"значительные \n" -"накладные расходы в случае большого количества маленьких пакетов, т.к. " -"ACK \n" -"влияют на увеличение размера. С UDP мы можем оптимизировать транспорт\n" -"и для эффективности, и для эластичности, с учетом частных потребностей " -"I2P." - -#: i2p2www/pages/site/get-involved/todo.html:184 -msgid "It will be a lot of work though." -msgstr "И все таки, предстоит выполнить много работы." - -#: i2p2www/pages/site/get-involved/todo.html:187 -msgid "NIO or NBIO" -msgstr "NIO или NBIO" - -#: i2p2www/pages/site/get-involved/todo.html:188 -msgid "NIO Implemented in I2P 0.6.1.22 (\"NTCP\")" -msgstr "NIO реализовано в I2P 0.6.1.22 (\"NTCP\")" - -#: i2p2www/pages/site/get-involved/todo.html:191 -msgid "" -"In Java 1.4, a set of \"New I/O\" packages was introduced, allowing Java" -" \n" -"developers to take advantage of the operating system's nonblocking IO \n" -"capabilities - allowing you to maintain a large number of concurrent IO \n" -"operations without requiring a separate thread for each. There is much \n" -"promise with this approach, as we can scalable handle a large number of \n" -"concurrent connections and we don't have to write a mini-TCP stack with \n" -"UDP. However, the NIO packages have not proven themselves to be battle-" -"ready, \n" -"as the Freenet developer's found. In addition, requiring NIO support " -"would \n" -"mean we can't run on any of the open source JVMs like Kaffe, \n" -"as GNU/Classpath has only " -"limited \n" -"support for NIO. (note: this may not be the case anymore, as there \n" -"has been some progress on Classpath's NIO, but it is an unknown " -"quantity)" -msgstr "" -"В Java 1.4 был представлен набор пакетов \"New I/O\", позволяющий " -"разработчикам \n" -"Java получить преимущество возможностей неблокирующих системных вызовов " -"I/O,\n" -"позволяющих выполнять большое количество конкурирующих операций \n" -"ввода/вывода, не требующих отдельного потока для каждой операции. \n" -"Это многообещающая возможность, т.к. мы можем масштабируемо работать с " -"большим количеством\n" -"конкурирующих соединений, и на не нужно писать мини-TCP стек с UDP. \n" -"Тем не менее, пакеты NIO не доказали свою боеспособность, \n" -"как было обнаружено разработчиками Freenet. Кроме того, необходимость " -"поддержки NIO \n" -"означала бы, что мы не можем запуститься на любой JVM с открытым исходным" -" кодом, как Kaffe, \n" -"т.к. только GNU/Classpath имеет" -" ограниченную \n" -"поддержку NIO. (к сведению: это может быть уже не так, так как \n" -"в Classpath'ах NIO был достигнут некоторый прогресс, но пока ничего " -"определенного)" - -#: i2p2www/pages/site/get-involved/todo.html:205 -#, python-format -msgid "" -"Another alternative along the same lines is the Non" -" \n" -"Blocking I/O package - essentially a cleanroom NIO implementation \n" -"(written before NIO was around). It works by using some native OS code \n" -"to do the nonblocking IO, passing off events through Java. It seems to \n" -"be working with Kaffe, though there doesn't seem to be much development \n" -"activity on it lately (likely due to 1.4's NIO deployment)." -msgstr "" -"Другая альтернатива по той же схеме - это пакет Non" -" \n" -"Blocking I/O - по сути подчищенная реализация NIO (написанная до " -"появления NIO). Он использует некоторый родной код OS, \n" -"чтобы выполнять неблокирующие вызовы IO, пропуская события через Java. " -"Кажется, \n" -"оно работает с Kaffe, хотя, похоже, в последнее время разработка ведется\n" -"не очень активно (вероятно, это связано с разработкой NIO 1.4)." - -#: i2p2www/pages/site/get-involved/todo.html:220 +#: i2p2www/pages/site/get-involved/todo.html:44 msgid "" "Within the current network database and profile management " "implementation, \n" @@ -1015,7 +603,7 @@ msgstr "" "иметь практического значения, т.к. в ближайшее время он не будет нам " "нужен." -#: i2p2www/pages/site/get-involved/todo.html:235 +#: 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" @@ -1024,246 +612,7 @@ msgstr "" "Как было упомянут, с ростом сети мы будем помнить об этих моментах. \n" "У нас есть над чем поработать, но мы можем отложить это на потом." -#: i2p2www/pages/site/get-involved/todo.html:247 -#: i2p2www/pages/site/get-involved/todo.html:331 -#, python-format -msgid "" -"Addressed in I2P 0.5 as documented elsewhere" -msgstr "" -"Планируется реализовать в I2P 0.5 согласно описанию" - -#: i2p2www/pages/site/get-involved/todo.html:250 -msgid "" -"Right now, if Alice builds a four hop inbound tunnel starting at Elvis, \n" -"going to Dave, then to Charlie, then Bob, and finally Alice " -"(A<--B<--C<--D<--E), \n" -"all five of them will know they are participating in tunnel \"123\", as \n" -"the messages are tagged as such. What we want to do is give each hop " -"their \n" -"own unique tunnel hop ID - Charlie will receive messages on tunnel 234 \n" -"and forward them to tunnel 876 on Bob. The intent is to prevent Bob or \n" -"Charlie from knowing that they are in Alice's tunnel, as if each hop in \n" -"the tunnel had the same tunnel ID, collusion attacks aren't much work." -msgstr "" -"Сейчас, если Alice строит входящий туннель с четырьмя отрезками, \n" -"начиная от Elvis, к Dave, затем к Charlie, затем к Bob, и, наконец, к " -"Alice \n" -"(A<--B<--C<--D<--E), то все четверо будут знать, что они " -"общаются через туннель \n" -"\"123\", как это указано в сообщении. Что мы хотим сделать, так это дать " -"каждому отрезку \n" -"уникальный ID отрезка туннеля - Chrlie получить сообщение по туннелю 234" -" \n" -"и перенаправит его в туннель 876 к Bob. Это нужно для того, чтобы Bob " -"или \n" -"Charlie не знали что они находятся в туннеле Alice - из-за того что " -"каждый прыжок \n" -"в туннеле имеет один и тот же ID туннеля, и атака сговором - collusion " -"attack - не сработает." - -#: i2p2www/pages/site/get-involved/todo.html:260 -msgid "" -"Adding a unique tunnel ID per hop isn't hard, but by itself, " -"insufficient. \n" -"If Dave and Bob are under the control of the same attacker, they wouldn't" -" \n" -"be able to tell they are in the same tunnel due to the tunnel ID, but \n" -"would be able to tell by the message bodies and verification structures \n" -"by simply comparing them. To prevent that, the tunnel must use layered \n" -"encryption along the path, both on the payload of the tunneled message \n" -"and on the verification structure (used to prevent simple tagging " -"attacks). \n" -"This requires some simple modifications to the TunnelMessage, as well \n" -"as the inclusion of per-hop secret keys delivered during tunnel creation" -" \n" -"and given to the tunnel's gateway. We must fix a maximum tunnel length \n" -"(e.g. 16 hops) and instruct the gateway to encrypt the message to each \n" -"of the 16 delivered secret keys, in reverse order, and to encrypt the \n" -"signature of the hash of the (encrypted) payload at each step. The " -"gateway \n" -"then sends that 16-step encrypted message, along with a 16-step and " -"16-wide \n" -"encrypted mapping to the first hop, which then decrypts the mapping and \n" -"the payload with their secret key, looking in the 16-wide mapping for \n" -"the entry associated with their own hop (keyed by the per-hop tunnel ID)" -" \n" -"and verifying the payload by checking it against the associated signed \n" -"hash." -msgstr "" -"Добавить уникальный ID туннеля для каждого прыжка не сложно, но этого не " -"достаточно. \n" -"Если Dave и Bob контролируются одним атакующим, они не смогут сказать \n" -"что они в одном туннеле из-за ID туннелей, но это можно выяснить по " -"содержимому сообщений \n" -"и структуре верификации, просто сравнив их. Чтобы избежать этого, туннель" -" \n" -"должен использовать слоеное шифрование на всем пути, и над содержимым " -"сообщения, \n" -"и над структурой верификации (необходимо для предотвращения простой атаки" -" по меткам - tagging attack). \n" -"Для этого необходимо немного модифицировать TunnelMessage, а также \n" -"добавить секретные ключи прыжков, отправленные во время создания туннеля," -" \n" -"и отданные шлюзу туннеля. Мы должны зафиксировать максимальную длину " -"туннеля \n" -"(например, 16 отрезков), и сказать шлюзу шифровать сообщения для каждого" -" \n" -"из 16 секретных ключей, в обратном порядке, и зашифровать \n" -"подпись хеша (шифрованного) содержимого на каждом шаге. Затем шлюз \n" -"отсылает эти 16-кратно зашифрованное сообщение, вместе с 16-кратным и " -"16-wide \n" -"зашифрованным маппингом в первый прыжок, который дешифрует маппинг и \n" -"содержимое своим секретным ключом, ищет в 16-wide маппинге " -"ассоциированную \n" -"с его прыжком информацию (по ключу ID отрезка туннеля) \n" -"и верифицирует содержимое по связанному с ним подписанному \n" -"хешу." - -#: i2p2www/pages/site/get-involved/todo.html:281 -msgid "" -"The tunnel gateway does still have more information than the other peers" -" \n" -"in the tunnel, and compromising both the gateway and a tunnel participant" -" \n" -"would allow those peers to collude, exposing the fact that they are both" -" \n" -"in the same tunnel. In addition, neighboring peers know that they are \n" -"in the same tunnel anyway, as they know who they send the message to (and" -" \n" -"with IP-based transports without restricted routes, they know who they \n" -"got it from). However, the above two techniques significantly increase \n" -"the cost of gaining meaningful samples when dealing with longer tunnels." -msgstr "" -"Шлюз туннеля все еще имеет больше информации, чем другие узлы \n" -"в туннеле, и одновременное компрометирование шлюза и участника туннеля \n" -"позволит этим узлам сговориться, раскрывая тот факт, что они оба " -"находятся \n" -"в одном туннеле. Также, в любом случае, соседние узлы знают, что они в " -"одном \n" -"и том же туннеле, поскольку они знают кому они отсылают сообщение \n" -"(и с основанным на IP транспортом без ограниченных маршрутов они знают \n" -"от кого они их получили). Тем не менее, оба описанных выше метода " -"значительно \n" -"увеличивают стоимость получения значимых образцов, когда мы имеем дело с " -"длинными туннелями." - -#: i2p2www/pages/site/get-involved/todo.html:297 -msgid "Implemented in release 0.6.2" -msgstr "Реализовано в 0.6.2" - -#: i2p2www/pages/site/get-involved/todo.html:300 -#, python-format -msgid "" -"As Connelly proposed to deal with the\n" -"predecessor attack (2008\n" -"update), keeping the order of peers within our tunnels consistent \n" -"(aka whenever Alice creates a tunnel with both Bob and Charlie in it, \n" -"Bob's next hop is always Charlie), we address the issue as Bob doesn't \n" -"get to substantially sample Alice's peer selection group. We may even \n" -"want to explicitly allow Bob to participate in Alice's tunnels in only \n" -"one way - receiving a message from Dave and sending it to Charlie - and \n" -"if any of those peers are not available to participate in the tunnel (due" -" \n" -"to overload, network disconnection, etc), avoid asking Bob to participate" -" \n" -"in any tunnels until they are back online." -msgstr "" -"Как предложил Connelly, чтобы разобраться с\n" -"атакой предшественника (обновление от 2008), сохраняя очередность узлов в " -"туннеле постоянной \n" -"(aka когда бы Alice ни создала туннель одновременно с Bob и Charlie, \n" -"следующий прыжок Bob'а всегда приведет его к Charlie), мы определяем что " -"Bob никогда \n" -"не войдет в группу выбора узлов Alice. Мы даже можем \n" -"разрешить Bob'e взаимодействовать с тунеллями Alice только \n" -"одним способом - получать сообщения от Dave и отсылать их Charlie - и \n" -"если любой из этих узлов не доступен для образования туннеля (из-за \n" -"перегрузки, обрыва связи, и т.д.), не позволять Bob'у учавствовать \n" -"в любом туннеле до тех пор, пока они не станут доступны." - -#: i2p2www/pages/site/get-involved/todo.html:315 -msgid "" -"More analysis is necessary for revising the tunnel creation - at the \n" -"moment, we simply select and order randomly within the peer's top tier \n" -"of peers (ones with fast + high capacity)." -msgstr "" -"Для пересмотра процесса создания туннеля необходим более глубокий анализ " -"- \n" -"сейчас мы просто выбираем и сортируем случайным образом верхушку списка " -"узлов (по скорости + большой вместимости)." - -#: i2p2www/pages/site/get-involved/todo.html:320 -msgid "" -"Adding a strict ordering to peers in a tunnel also improves the anonymity" -" \n" -"of peers with 0-hop tunnels, as otherwise the fact that a peer's gateway" -" \n" -"is always the same would be particularly damning. However, peers with \n" -"0-hop tunnels may want to periodically use a 1-hop tunnel to simulate \n" -"the failure of a normally reliable gateway peer (so every MTBF*(tunnel \n" -"duration) minutes, use a 1-hop tunnel)." -msgstr "" -"Введение жесткой очередности узлов в туннеле также улучшает анонимность \n" -"узлов в 0-прыжковых туннелях, тогда как, в другом случае, тот факт, что " -"шлюз узла \n" -"всегда будет одним и тем же, будет особенно губительным. Тем не менее, " -"узлы \n" -"с 0-прыжковыми туннелями периодически могут хотеть использовать " -"1-прыжковый туннель, чтобы симулировать \n" -"ошибку в обычно надежном узле (и так каждые MTBF*(длительность туннеля) \n" -"минут, используя 1-прыжковый туннель)." - -#: i2p2www/pages/site/get-involved/todo.html:337 -msgid "" -"Without tunnel length permutation, if someone were to somehow detect that" -" \n" -"a destination had a particular number of hops, it might be able to use " -"that \n" -"information to identify the router the destination is located on, per the" -" \n" -"predecessor attack. For instance, if everyone has 2-hop tunnels, if Bob \n" -"receives a tunnel message from Charlie and forwards it to Alice, Bob " -"knows \n" -"Alice is the final router in the tunnel. If Bob were to identify what " -"destination \n" -"that tunnel served (by means of colluding with the gateway and harvesting" -" \n" -"the network database for all of the LeaseSets), he would know the router" -" \n" -"on which that destination is located (and without restricted routes, that" -" \n" -"would mean what IP address the destination is on)." -msgstr "" -"Без изменения длины туннеля, если кто-то как-то обнаружит, что \n" -"до пункта назначения определенное число хопов, это может быть " -"использовано \n" -"для обнаружения местоположения маршрутизатора во время атаки " -"предшественника. \n" -"Например, если у всех есть 2-прыжковый туннель, и если Bob \n" -"получает сообщение от Charlie и пересылает его Alice, то Bob знает - \n" -"Alice - это конечный маршрутизатор в туннеле. Если Bob выяснил, куда " -"приводит \n" -"этот туннель (путем сговора со шлюзом и сбора \n" -"базы данных сети для всех LeaseSets), он узнает маршрутизатор, на которым" -" \n" -"расположен пункт назначения (и без ограниченных маршрутов это будет " -"указывать \n" -"на IP адрес пункта назначения)." - -#: i2p2www/pages/site/get-involved/todo.html:349 -msgid "" -"It is to counter user behavior that tunnel lengths should be permuted, \n" -"using algorithms based on the length requested (for example, the 1/MTBF \n" -"length change for 0-hop tunnels outlined above)." -msgstr "" -"Изменяемая длина туннелей должна противостоять поведению пользователей, \n" -"используя алгоритмы, основанные на длине (для примера, изменение \n" -"длины на 1/MTBF для 0-прыжковых туннелей, описанных выше)." - -#: i2p2www/pages/site/get-involved/todo.html:359 +#: i2p2www/pages/site/get-involved/todo.html:71 msgid "" "The restricted route functionality described before was simply a " "functional \n" @@ -1304,7 +653,7 @@ msgstr "" " \n" "с предписанием переслать его согласно запросу." -#: i2p2www/pages/site/get-involved/todo.html:378 +#: i2p2www/pages/site/get-involved/todo.html:90 #, python-format msgid "" "Within the network, we will want some way to deter people from consuming" @@ -1326,7 +675,7 @@ msgstr "" "скомпрометирует анонимность системы. Вместо этого мы хотим \n" "сделать такие запросы \"дорогостоящими\"." -#: i2p2www/pages/site/get-involved/todo.html:386 +#: 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 " @@ -1360,7 +709,7 @@ msgstr "" " \n" "с ограниченными ресурсами." -#: i2p2www/pages/site/get-involved/todo.html:397 +#: 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" @@ -1371,7 +720,7 @@ msgstr "" "для \"удорожания\" подобных запросов, и дальнейшие исследования \n" "на этом фронте являются целесообразными." -#: i2p2www/pages/site/get-involved/todo.html:407 +#: i2p2www/pages/site/get-involved/todo.html:119 #, python-format msgid "" "To powerful passive external observers as well as large colluding " @@ -1406,7 +755,7 @@ msgstr "" "этих алгоритмов, на которые мы можем опираться при реализации \n" "различных стратегий смешивания туннелей." -#: i2p2www/pages/site/get-involved/todo.html:420 +#: 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" @@ -1440,7 +789,7 @@ msgstr "" "для их туннелей, избегая выделения полосы пропускания большей, чем \n" "доступно узлу." -#: i2p2www/pages/site/get-involved/todo.html:433 +#: i2p2www/pages/site/get-involved/todo.html:145 msgid "" "In addition, we may want to implement code to dynamically reroute tunnels" " \n" @@ -1457,7 +806,7 @@ msgstr "" "узла в туннеле, \n" "с предписанием переопределить следующий прыжок в туннеле." -#: i2p2www/pages/site/get-involved/todo.html:444 +#: 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" @@ -1482,7 +831,7 @@ msgstr "" "исключением тех узлов, где \n" "зубчик подвергается добавлению инструкций по задержке." -#: i2p2www/pages/site/get-involved/todo.html:456 +#: i2p2www/pages/site/get-involved/todo.html:168 #, python-format msgid "" "Performance related improvements are listed on the\n" @@ -5811,3 +5160,10 @@ msgstr "" "Канал #i2p-dev в IRC, или форум " "перевода на %(zzz)s." + + + + + + + diff --git a/i2p2www/translations/sv/LC_MESSAGES/docs.po b/i2p2www/translations/sv/LC_MESSAGES/docs.po index d7b21d7a..9d4904d5 100644 --- a/i2p2www/translations/sv/LC_MESSAGES/docs.po +++ b/i2p2www/translations/sv/LC_MESSAGES/docs.po @@ -9,7 +9,7 @@ msgid "" msgstr "" "Project-Id-Version: I2P\n" "Report-Msgid-Bugs-To: https://trac.i2p2.de/\n" -"POT-Creation-Date: 2014-11-16 02:59+0000\n" +"POT-Creation-Date: 2014-11-27 12:12+0000\n" "PO-Revision-Date: 2013-04-27 23:10+0000\n" "Last-Translator: Martin Svensson \n" "Language-Team: Swedish (Sweden) " @@ -28,7 +28,9 @@ msgstr "" #: i2p2www/pages/site/docs/applications/embedding.html:3 #: i2p2www/pages/site/docs/how/cryptography.html:3 #: i2p2www/pages/site/docs/protocol/i2cp.html:3 +#: i2p2www/pages/site/docs/spec/configuration.html:3 #: i2p2www/pages/site/docs/spec/updates.html:3 +#: i2p2www/pages/site/docs/transport/ntcp.html:3 msgid "November 2014" msgstr "" @@ -131,7 +133,7 @@ msgstr "" msgid "Managed Clients" msgstr "" -#: i2p2www/pages/site/docs/index.html:44 i2p2www/pages/site/docs/index.html:217 +#: i2p2www/pages/site/docs/index.html:44 i2p2www/pages/site/docs/index.html:222 msgid "Embedding the router in your application" msgstr "" @@ -148,7 +150,7 @@ msgstr "" msgid "hostsdb.blockfile Format" msgstr "" -#: i2p2www/pages/site/docs/index.html:48 i2p2www/pages/site/docs/index.html:189 +#: i2p2www/pages/site/docs/index.html:48 i2p2www/pages/site/docs/index.html:194 msgid "Configuration File Format" msgstr "" @@ -166,369 +168,379 @@ msgstr "" msgid "Application Development Overview and Guide" msgstr "" -#: i2p2www/pages/site/docs/index.html:72 -msgid "SAM Protocol" +#: i2p2www/pages/site/docs/index.html:58 +#: i2p2www/pages/site/docs/api/i2ptunnel.html:55 +msgid "I2PTunnel Configuration" msgstr "" #: i2p2www/pages/site/docs/index.html:74 -msgid "SAMv2 Protocol" +msgid "SAM Protocol" msgstr "" #: i2p2www/pages/site/docs/index.html:76 -msgid "SAMv3 Protocol" +msgid "SAMv2 Protocol" msgstr "" #: i2p2www/pages/site/docs/index.html:78 +msgid "SAMv3 Protocol" +msgstr "" + +#: i2p2www/pages/site/docs/index.html:80 msgid "BOB Protocol" msgstr "" -#: i2p2www/pages/site/docs/index.html:81 +#: i2p2www/pages/site/docs/index.html:83 msgid "End-to-End Transport API and Protocols" msgstr "" -#: i2p2www/pages/site/docs/index.html:82 +#: i2p2www/pages/site/docs/index.html:84 msgid "" "The end-to-end protocols used by clients for reliable and unreliable " "communication." msgstr "" -#: i2p2www/pages/site/docs/index.html:84 +#: i2p2www/pages/site/docs/index.html:86 #: i2p2www/pages/site/docs/api/streaming.html:2 msgid "Streaming Library" msgstr "" -#: i2p2www/pages/site/docs/index.html:86 +#: i2p2www/pages/site/docs/index.html:88 msgid "Streaming Protocol Specification" msgstr "" -#: i2p2www/pages/site/docs/index.html:88 +#: i2p2www/pages/site/docs/index.html:90 msgid "Streaming Javadoc" msgstr "" -#: i2p2www/pages/site/docs/index.html:90 +#: i2p2www/pages/site/docs/index.html:92 #: i2p2www/pages/site/docs/api/datagrams.html:2 msgid "Datagrams" msgstr "" -#: i2p2www/pages/site/docs/index.html:92 +#: i2p2www/pages/site/docs/index.html:94 msgid "Datagram Javadoc" msgstr "" -#: i2p2www/pages/site/docs/index.html:95 +#: i2p2www/pages/site/docs/index.html:97 msgid "Client-to-Router Interface API and Protocol" msgstr "" -#: i2p2www/pages/site/docs/index.html:96 +#: 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" "Traditionally used only by Java applications and higher-level APIs." msgstr "" -#: i2p2www/pages/site/docs/index.html:101 +#: i2p2www/pages/site/docs/index.html:103 msgid "I2CP - I2P Control Protocol / API overview" msgstr "" -#: i2p2www/pages/site/docs/index.html:103 +#: i2p2www/pages/site/docs/index.html:105 msgid "I2CP Specification" msgstr "" -#: i2p2www/pages/site/docs/index.html:105 +#: i2p2www/pages/site/docs/index.html:107 msgid "I2CP API Javadoc" msgstr "" -#: i2p2www/pages/site/docs/index.html:107 -#: i2p2www/pages/site/docs/index.html:136 +#: i2p2www/pages/site/docs/index.html:109 +#: i2p2www/pages/site/docs/index.html:139 msgid "Common data structures specification" msgstr "" -#: i2p2www/pages/site/docs/index.html:109 -#: i2p2www/pages/site/docs/index.html:138 +#: i2p2www/pages/site/docs/index.html:111 +#: i2p2www/pages/site/docs/index.html:141 msgid "Data Structures Javadoc" msgstr "" -#: i2p2www/pages/site/docs/index.html:112 +#: i2p2www/pages/site/docs/index.html:114 msgid "End-to-End Encryption" msgstr "" -#: i2p2www/pages/site/docs/index.html:113 +#: i2p2www/pages/site/docs/index.html:115 msgid "How client messages are end-to-end encrypted by the router." msgstr "" -#: i2p2www/pages/site/docs/index.html:115 +#: i2p2www/pages/site/docs/index.html:117 msgid "ElGamal/AES+SessionTag encryption" msgstr "" -#: i2p2www/pages/site/docs/index.html:116 -#: i2p2www/pages/site/docs/index.html:149 +#: i2p2www/pages/site/docs/index.html:118 +#: i2p2www/pages/site/docs/index.html:152 msgid "ElGamal and AES cryptography details" msgstr "" -#: i2p2www/pages/site/docs/index.html:119 +#: i2p2www/pages/site/docs/index.html:121 #: i2p2www/pages/site/docs/how/tech-intro.html:15 #: i2p2www/pages/site/docs/how/tech-intro.html:329 msgid "Network Database" msgstr "" -#: i2p2www/pages/site/docs/index.html:120 +#: i2p2www/pages/site/docs/index.html:122 msgid "" "Distributed storage and retrieval of information about routers and " "clients." msgstr "" -#: i2p2www/pages/site/docs/index.html:122 +#: i2p2www/pages/site/docs/index.html:124 msgid "Network database overview, details, and threat analysis" msgstr "" -#: i2p2www/pages/site/docs/index.html:123 +#: i2p2www/pages/site/docs/index.html:125 msgid "Cryptographic hashes" msgstr "" -#: i2p2www/pages/site/docs/index.html:124 +#: i2p2www/pages/site/docs/index.html:126 msgid "Cryptographic signatures" msgstr "" #: i2p2www/pages/site/docs/index.html:127 +#: i2p2www/pages/site/docs/index.html:186 +msgid "Router reseed specification" +msgstr "" + +#: i2p2www/pages/site/docs/index.html:130 msgid "Router Message Protocol" msgstr "" -#: i2p2www/pages/site/docs/index.html:128 +#: i2p2www/pages/site/docs/index.html:131 msgid "" "I2P is a message-oriented router. The messages sent between routers are " "defined by the I2NP protocol." msgstr "" -#: i2p2www/pages/site/docs/index.html:130 +#: i2p2www/pages/site/docs/index.html:133 msgid "I2NP - I2P Network Protocol Overview" msgstr "" -#: i2p2www/pages/site/docs/index.html:132 +#: i2p2www/pages/site/docs/index.html:135 msgid "I2NP Specification" msgstr "" -#: i2p2www/pages/site/docs/index.html:134 +#: i2p2www/pages/site/docs/index.html:137 msgid "I2NP Javadoc" msgstr "" -#: i2p2www/pages/site/docs/index.html:141 +#: i2p2www/pages/site/docs/index.html:144 #: i2p2www/pages/site/docs/how/tech-intro.html:14 #: i2p2www/pages/site/docs/how/tech-intro.html:228 msgid "Tunnels" msgstr "" -#: i2p2www/pages/site/docs/index.html:142 +#: i2p2www/pages/site/docs/index.html:145 msgid "" "Selecting peers, requesting tunnels through those peers, and encrypting " "and routing messages through these tunnels." msgstr "" -#: i2p2www/pages/site/docs/index.html:144 +#: i2p2www/pages/site/docs/index.html:147 msgid "Peer profiling and selection" msgstr "" -#: i2p2www/pages/site/docs/index.html:145 +#: i2p2www/pages/site/docs/index.html:148 msgid "Tunnel routing overview" msgstr "" -#: i2p2www/pages/site/docs/index.html:146 +#: i2p2www/pages/site/docs/index.html:149 msgid "Garlic routing and \"garlic\" terminology" msgstr "" -#: i2p2www/pages/site/docs/index.html:147 +#: i2p2www/pages/site/docs/index.html:150 msgid "Tunnel building and encryption" msgstr "" -#: i2p2www/pages/site/docs/index.html:148 +#: i2p2www/pages/site/docs/index.html:151 msgid "ElGamal/AES" msgstr "" -#: i2p2www/pages/site/docs/index.html:148 +#: i2p2www/pages/site/docs/index.html:151 msgid "for build request encryption" msgstr "" -#: i2p2www/pages/site/docs/index.html:150 +#: i2p2www/pages/site/docs/index.html:153 msgid "Tunnel building specification" msgstr "" -#: i2p2www/pages/site/docs/index.html:151 +#: i2p2www/pages/site/docs/index.html:154 msgid "Low-level tunnel message specification" msgstr "" -#: i2p2www/pages/site/docs/index.html:152 +#: i2p2www/pages/site/docs/index.html:155 #: i2p2www/pages/site/docs/tunnels/unidirectional.html:2 msgid "Unidirectional Tunnels" msgstr "" -#: i2p2www/pages/site/docs/index.html:153 +#: i2p2www/pages/site/docs/index.html:156 #: i2p2www/pages/site/docs/how/peer-selection.html:299 msgid "Peer Profiling and Selection in the I2P Anonymous Network" msgstr "" -#: i2p2www/pages/site/docs/index.html:154 +#: i2p2www/pages/site/docs/index.html:157 msgid "2009 paper (pdf), not current but still generally accurate" msgstr "" -#: i2p2www/pages/site/docs/index.html:157 +#: i2p2www/pages/site/docs/index.html:160 msgid "Transport Layer" msgstr "" -#: i2p2www/pages/site/docs/index.html:158 +#: i2p2www/pages/site/docs/index.html:161 msgid "The protocols for direct (point-to-point) router to router communication." msgstr "" -#: i2p2www/pages/site/docs/index.html:160 +#: i2p2www/pages/site/docs/index.html:163 msgid "Transport layer overview" msgstr "" -#: i2p2www/pages/site/docs/index.html:162 +#: i2p2www/pages/site/docs/index.html:165 msgid "TCP-based transport overview and specification" msgstr "" -#: i2p2www/pages/site/docs/index.html:164 +#: i2p2www/pages/site/docs/index.html:167 msgid "UDP-based transport overview" msgstr "" -#: i2p2www/pages/site/docs/index.html:166 +#: i2p2www/pages/site/docs/index.html:169 msgid "SSU specification" msgstr "" -#: i2p2www/pages/site/docs/index.html:168 +#: i2p2www/pages/site/docs/index.html:171 msgid "NTCP transport encryption" msgstr "" -#: i2p2www/pages/site/docs/index.html:170 +#: i2p2www/pages/site/docs/index.html:173 msgid "SSU transport encryption" msgstr "" -#: i2p2www/pages/site/docs/index.html:172 +#: i2p2www/pages/site/docs/index.html:175 msgid "Transport Javadoc" msgstr "" -#: i2p2www/pages/site/docs/index.html:174 +#: i2p2www/pages/site/docs/index.html:177 msgid "NTCP Javadoc" msgstr "" -#: i2p2www/pages/site/docs/index.html:176 +#: i2p2www/pages/site/docs/index.html:179 msgid "SSU Javadoc" msgstr "" -#: i2p2www/pages/site/docs/index.html:179 +#: i2p2www/pages/site/docs/index.html:182 msgid "Other Router Topics" msgstr "" -#: i2p2www/pages/site/docs/index.html:181 +#: i2p2www/pages/site/docs/index.html:184 msgid "Router software updates" msgstr "" -#: i2p2www/pages/site/docs/index.html:183 +#: i2p2www/pages/site/docs/index.html:188 msgid "Native BigInteger Library" msgstr "" -#: i2p2www/pages/site/docs/index.html:185 +#: i2p2www/pages/site/docs/index.html:190 msgid "Time synchronization and NTP" msgstr "" -#: i2p2www/pages/site/docs/index.html:187 +#: i2p2www/pages/site/docs/index.html:192 msgid "Performance" msgstr "" -#: i2p2www/pages/site/docs/index.html:194 +#: i2p2www/pages/site/docs/index.html:199 msgid "Developer's Guides and Resources" msgstr "" -#: i2p2www/pages/site/docs/index.html:196 +#: i2p2www/pages/site/docs/index.html:201 msgid "New Developer's Guide" msgstr "" -#: i2p2www/pages/site/docs/index.html:198 +#: i2p2www/pages/site/docs/index.html:203 msgid "New Translator's Guide" msgstr "" -#: i2p2www/pages/site/docs/index.html:200 +#: i2p2www/pages/site/docs/index.html:205 msgid "Monotone Guide" msgstr "" -#: i2p2www/pages/site/docs/index.html:202 +#: i2p2www/pages/site/docs/index.html:207 msgid "Developer Guidelines" msgstr "" -#: i2p2www/pages/site/docs/index.html:204 +#: i2p2www/pages/site/docs/index.html:209 msgid "Javadocs on the standard internet:" msgstr "" -#: i2p2www/pages/site/docs/index.html:205 -#: i2p2www/pages/site/docs/index.html:209 #: i2p2www/pages/site/docs/index.html:210 -#: i2p2www/pages/site/docs/index.html:211 +#: i2p2www/pages/site/docs/index.html:214 +#: i2p2www/pages/site/docs/index.html:215 +#: i2p2www/pages/site/docs/index.html:216 #, python-format msgid "Server %(num)s" msgstr "" -#: i2p2www/pages/site/docs/index.html:206 -#: i2p2www/pages/site/docs/index.html:215 +#: i2p2www/pages/site/docs/index.html:211 +#: i2p2www/pages/site/docs/index.html:220 msgid "" "Note: always verify that javadocs are current by checking the release " "number." msgstr "" -#: i2p2www/pages/site/docs/index.html:208 +#: i2p2www/pages/site/docs/index.html:213 msgid "Javadocs inside I2P:" msgstr "" -#: i2p2www/pages/site/docs/index.html:219 +#: i2p2www/pages/site/docs/index.html:224 msgid "Ports used by I2P" msgstr "" -#: i2p2www/pages/site/docs/index.html:221 +#: i2p2www/pages/site/docs/index.html:226 msgid "Automatic updates to development builds inside I2P" msgstr "" -#: i2p2www/pages/site/docs/index.html:223 +#: i2p2www/pages/site/docs/index.html:228 msgid "Updating the wrapper manually" msgstr "" -#: i2p2www/pages/site/docs/index.html:225 +#: i2p2www/pages/site/docs/index.html:230 msgid "User forum" msgstr "" -#: i2p2www/pages/site/docs/index.html:227 +#: i2p2www/pages/site/docs/index.html:232 msgid "Developer forum inside I2P" msgstr "" -#: i2p2www/pages/site/docs/index.html:229 +#: i2p2www/pages/site/docs/index.html:234 msgid "Bug tracker" msgstr "" -#: i2p2www/pages/site/docs/index.html:231 +#: i2p2www/pages/site/docs/index.html:236 msgid "Viewmtn inside I2P" msgstr "" -#: i2p2www/pages/site/docs/index.html:233 +#: i2p2www/pages/site/docs/index.html:238 msgid "I2P Source exported to GitHub" msgstr "" -#: i2p2www/pages/site/docs/index.html:235 +#: i2p2www/pages/site/docs/index.html:240 msgid "I2P Source Git Repo inside I2P" msgstr "" -#: i2p2www/pages/site/docs/index.html:237 +#: i2p2www/pages/site/docs/index.html:242 msgid "Source translation at Transifex" msgstr "" -#: i2p2www/pages/site/docs/index.html:239 +#: i2p2www/pages/site/docs/index.html:244 msgid "Roadmap wiki" msgstr "" -#: i2p2www/pages/site/docs/index.html:241 +#: i2p2www/pages/site/docs/index.html:246 msgid "Old roadmap" msgstr "" -#: i2p2www/pages/site/docs/index.html:241 -#: i2p2www/pages/site/docs/index.html:243 +#: i2p2www/pages/site/docs/index.html:246 +#: i2p2www/pages/site/docs/index.html:248 msgid "not current" msgstr "" -#: i2p2www/pages/site/docs/index.html:243 +#: i2p2www/pages/site/docs/index.html:248 msgid "To Do List" msgstr "" @@ -789,7 +801,7 @@ msgid "" msgstr "" #: i2p2www/pages/site/docs/naming.html:183 -#: i2p2www/pages/site/docs/spec/configuration.html:170 +#: i2p2www/pages/site/docs/spec/configuration.html:184 msgid "Addressbook" msgstr "" @@ -1159,7 +1171,7 @@ msgid "" msgstr "" #: i2p2www/pages/site/docs/plugins.html:2 -#: i2p2www/pages/site/docs/spec/configuration.html:138 +#: i2p2www/pages/site/docs/spec/configuration.html:152 msgid "Plugins" msgstr "" @@ -2535,15 +2547,19 @@ msgid "" msgstr "" #: i2p2www/pages/site/docs/api/i2ptunnel.html:54 +msgid "Configuration" +msgstr "" + +#: i2p2www/pages/site/docs/api/i2ptunnel.html:58 msgid "Client Modes" msgstr "" -#: i2p2www/pages/site/docs/api/i2ptunnel.html:55 -#: i2p2www/pages/site/docs/api/i2ptunnel.html:137 +#: i2p2www/pages/site/docs/api/i2ptunnel.html:59 +#: i2p2www/pages/site/docs/api/i2ptunnel.html:141 msgid "Standard" msgstr "" -#: i2p2www/pages/site/docs/api/i2ptunnel.html:56 +#: 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" @@ -2551,7 +2567,7 @@ msgid "" " list of destinations." msgstr "" -#: i2p2www/pages/site/docs/api/i2ptunnel.html:62 +#: i2p2www/pages/site/docs/api/i2ptunnel.html:66 msgid "" "A HTTP-client tunnel. The tunnel connects to the destination specified by" " the URL\n" @@ -2559,34 +2575,34 @@ msgid "" "provided. Strips HTTP connections of the following headers:" msgstr "" -#: i2p2www/pages/site/docs/api/i2ptunnel.html:67 +#: 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 "" -#: i2p2www/pages/site/docs/api/i2ptunnel.html:75 +#: 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 "" -#: i2p2www/pages/site/docs/api/i2ptunnel.html:82 +#: 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 "" -#: i2p2www/pages/site/docs/api/i2ptunnel.html:86 +#: i2p2www/pages/site/docs/api/i2ptunnel.html:90 msgid "Outproxy:" msgstr "" -#: i2p2www/pages/site/docs/api/i2ptunnel.html:87 +#: i2p2www/pages/site/docs/api/i2ptunnel.html:91 msgid "Internal I2P use:" msgstr "" -#: i2p2www/pages/site/docs/api/i2ptunnel.html:92 +#: i2p2www/pages/site/docs/api/i2ptunnel.html:96 msgid "" "Creates a connection to a random IRC server specified by the comma " "seprated (\", \") \n" @@ -2594,43 +2610,43 @@ msgid "" "allowed due to anonymity concerns." msgstr "" -#: i2p2www/pages/site/docs/api/i2ptunnel.html:96 +#: i2p2www/pages/site/docs/api/i2ptunnel.html:100 msgid "Whitelist:" msgstr "" -#: i2p2www/pages/site/docs/api/i2ptunnel.html:111 +#: i2p2www/pages/site/docs/api/i2ptunnel.html:115 msgid "Enables using the I2P router as a SOCKS proxy." msgstr "" -#: i2p2www/pages/site/docs/api/i2ptunnel.html:116 +#: 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" "IRC client mode." msgstr "" -#: i2p2www/pages/site/docs/api/i2ptunnel.html:122 +#: 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 "" -#: i2p2www/pages/site/docs/api/i2ptunnel.html:128 +#: 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" "subscribe to a streamr server tunnel." msgstr "" -#: i2p2www/pages/site/docs/api/i2ptunnel.html:136 +#: i2p2www/pages/site/docs/api/i2ptunnel.html:140 msgid "Server Modes" msgstr "" -#: i2p2www/pages/site/docs/api/i2ptunnel.html:138 +#: i2p2www/pages/site/docs/api/i2ptunnel.html:142 msgid "Creates a destination to a local ip:port with an open TCP port." msgstr "" -#: i2p2www/pages/site/docs/api/i2ptunnel.html:143 +#: 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" @@ -2638,7 +2654,7 @@ msgid "" " such a request." msgstr "" -#: i2p2www/pages/site/docs/api/i2ptunnel.html:149 +#: 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" @@ -2647,14 +2663,14 @@ msgid "" "requests, or loopback-testing an eepsite as a diagnostic tool." msgstr "" -#: i2p2www/pages/site/docs/api/i2ptunnel.html:156 +#: i2p2www/pages/site/docs/api/i2ptunnel.html:160 msgid "" "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:162 +#: 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." @@ -3447,8 +3463,8 @@ msgstr "" #: i2p2www/pages/site/docs/how/tunnel-routing.html:255 #: i2p2www/pages/site/docs/protocol/i2cp.html:687 #: i2p2www/pages/site/docs/protocol/i2np.html:226 -#: i2p2www/pages/site/docs/spec/updates.html:438 -#: i2p2www/pages/site/docs/transport/ntcp.html:535 +#: i2p2www/pages/site/docs/spec/updates.html:488 +#: i2p2www/pages/site/docs/transport/ntcp.html:544 #: i2p2www/pages/site/docs/transport/ssu.html:554 #: i2p2www/pages/site/docs/tunnels/implementation.html:506 msgid "Future Work" @@ -3999,6 +4015,14 @@ 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)." +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" "If done wrong, it could cause real harm to our network.\n" @@ -4007,11 +4031,11 @@ msgid "" "This page discusses some general guidelines." msgstr "" -#: i2p2www/pages/site/docs/applications/embedding.html:18 +#: i2p2www/pages/site/docs/applications/embedding.html:23 msgid "Talk to us" msgstr "" -#: i2p2www/pages/site/docs/applications/embedding.html:19 +#: 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" @@ -4019,11 +4043,11 @@ msgid "" "everyone." msgstr "" -#: i2p2www/pages/site/docs/applications/embedding.html:25 +#: i2p2www/pages/site/docs/applications/embedding.html:30 msgid "Choose your router wisely" msgstr "" -#: i2p2www/pages/site/docs/applications/embedding.html:26 +#: 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" @@ -4033,19 +4057,19 @@ msgid "" "Some of the following only applies to the Java router." msgstr "" -#: i2p2www/pages/site/docs/applications/embedding.html:34 +#: i2p2www/pages/site/docs/applications/embedding.html:39 msgid "Licensing" msgstr "" -#: i2p2www/pages/site/docs/applications/embedding.html:35 +#: i2p2www/pages/site/docs/applications/embedding.html:40 msgid "Ensure you meet the license requirements of the software you are bundling." msgstr "" -#: i2p2www/pages/site/docs/applications/embedding.html:40 +#: i2p2www/pages/site/docs/applications/embedding.html:45 msgid "Verify default configuration" msgstr "" -#: i2p2www/pages/site/docs/applications/embedding.html:41 +#: i2p2www/pages/site/docs/applications/embedding.html:46 msgid "" "A correct default configuration is crucial. Most users will not change " "the defaults.\n" @@ -4054,7 +4078,7 @@ msgid "" "Override the router defaults if necessary." msgstr "" -#: i2p2www/pages/site/docs/applications/embedding.html:46 +#: i2p2www/pages/site/docs/applications/embedding.html:51 msgid "" "Some important defaults to review: Max bandwidth, tunnel quantity and " "length, max participating tunnels.\n" @@ -4062,7 +4086,7 @@ msgid "" "your app." msgstr "" -#: i2p2www/pages/site/docs/applications/embedding.html:50 +#: i2p2www/pages/site/docs/applications/embedding.html:55 msgid "" "Configure enough bandwidth and tunnels to allow your users to contribute " "to the network.\n" @@ -4072,11 +4096,11 @@ msgid "" "example." msgstr "" -#: i2p2www/pages/site/docs/applications/embedding.html:57 +#: i2p2www/pages/site/docs/applications/embedding.html:62 msgid "Participating Traffic Considerations" msgstr "" -#: i2p2www/pages/site/docs/applications/embedding.html:58 +#: 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, " @@ -4088,14 +4112,14 @@ msgid "" "tunnels." msgstr "" -#: i2p2www/pages/site/docs/applications/embedding.html:65 +#: 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" "which is helped tremendously by others building tunnels through you." msgstr "" -#: i2p2www/pages/site/docs/applications/embedding.html:69 +#: i2p2www/pages/site/docs/applications/embedding.html:74 msgid "" "Secondly, over 90% of the routers in the current network allow " "participating traffic.\n" @@ -4107,13 +4131,13 @@ msgid "" " people to enable relaying." msgstr "" -#: i2p2www/pages/site/docs/applications/embedding.html:76 +#: i2p2www/pages/site/docs/applications/embedding.html:81 msgid "" "Thirdly, participating traffic is cover traffic that helps your users' " "anonymity." msgstr "" -#: i2p2www/pages/site/docs/applications/embedding.html:79 +#: i2p2www/pages/site/docs/applications/embedding.html:84 msgid "" "We strongly discourage you from disabling participating traffic by " "default.\n" @@ -4121,11 +4145,11 @@ msgid "" "the network." msgstr "" -#: i2p2www/pages/site/docs/applications/embedding.html:85 +#: i2p2www/pages/site/docs/applications/embedding.html:90 msgid "Persistence" msgstr "" -#: i2p2www/pages/site/docs/applications/embedding.html:86 +#: 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" @@ -4135,11 +4159,11 @@ msgid "" "performance." msgstr "" -#: i2p2www/pages/site/docs/applications/embedding.html:94 +#: i2p2www/pages/site/docs/applications/embedding.html:99 msgid "Configurability" msgstr "" -#: i2p2www/pages/site/docs/applications/embedding.html:95 +#: i2p2www/pages/site/docs/applications/embedding.html:100 msgid "" "Give your users a way to change the configuration of the important " "settings.\n" @@ -4149,11 +4173,11 @@ msgid "" "IP/port may be helpful." msgstr "" -#: i2p2www/pages/site/docs/applications/embedding.html:103 +#: i2p2www/pages/site/docs/applications/embedding.html:108 msgid "Floodfill Considerations" msgstr "" -#: i2p2www/pages/site/docs/applications/embedding.html:104 +#: 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" @@ -4164,11 +4188,11 @@ msgid "" "It also depends on the typical uptime for your application." msgstr "" -#: i2p2www/pages/site/docs/applications/embedding.html:114 +#: i2p2www/pages/site/docs/applications/embedding.html:119 msgid "Reseeding" msgstr "" -#: i2p2www/pages/site/docs/applications/embedding.html:115 +#: 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 " @@ -4176,11 +4200,11 @@ msgid "" "Be aware of possible blocking by hostile governments." msgstr "" -#: i2p2www/pages/site/docs/applications/embedding.html:124 +#: i2p2www/pages/site/docs/applications/embedding.html:129 msgid "Reduce Network Resource Usage" msgstr "" -#: i2p2www/pages/site/docs/applications/embedding.html:125 +#: 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" @@ -4190,11 +4214,11 @@ msgid "" "tunnel, even in the presence of some background DHT activity." msgstr "" -#: i2p2www/pages/site/docs/applications/embedding.html:133 +#: i2p2www/pages/site/docs/applications/embedding.html:138 msgid "Updatability" msgstr "" -#: i2p2www/pages/site/docs/applications/embedding.html:134 +#: 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" @@ -4209,11 +4233,11 @@ msgid "" "which you presumably are not bundling." msgstr "" -#: i2p2www/pages/site/docs/applications/embedding.html:145 +#: i2p2www/pages/site/docs/applications/embedding.html:150 msgid "Rollout" msgstr "" -#: i2p2www/pages/site/docs/applications/embedding.html:146 +#: 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 " @@ -4229,11 +4253,11 @@ msgid "" "checklist is." msgstr "" -#: i2p2www/pages/site/docs/applications/embedding.html:158 +#: i2p2www/pages/site/docs/applications/embedding.html:163 msgid "Design for and Encourage Long Uptimes" msgstr "" -#: i2p2www/pages/site/docs/applications/embedding.html:159 +#: 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 " @@ -4242,53 +4266,53 @@ msgid "" "solution." msgstr "" -#: i2p2www/pages/site/docs/applications/embedding.html:167 +#: i2p2www/pages/site/docs/applications/embedding.html:172 msgid "Show Status" msgstr "" -#: i2p2www/pages/site/docs/applications/embedding.html:168 +#: i2p2www/pages/site/docs/applications/embedding.html:173 msgid "" "Provide some indication to the user that the application tunnels are " "ready. Encourage patience." msgstr "" -#: i2p2www/pages/site/docs/applications/embedding.html:173 +#: i2p2www/pages/site/docs/applications/embedding.html:178 msgid "Graceful Shutdown" msgstr "" -#: i2p2www/pages/site/docs/applications/embedding.html:174 +#: 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 "" -#: i2p2www/pages/site/docs/applications/embedding.html:180 +#: i2p2www/pages/site/docs/applications/embedding.html:185 msgid "Education and Donation" msgstr "" -#: i2p2www/pages/site/docs/applications/embedding.html:181 +#: 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 "" -#: i2p2www/pages/site/docs/applications/embedding.html:187 +#: i2p2www/pages/site/docs/applications/embedding.html:192 msgid "External Router Option" msgstr "" -#: i2p2www/pages/site/docs/applications/embedding.html:188 +#: 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 "" -#: i2p2www/pages/site/docs/applications/embedding.html:195 +#: i2p2www/pages/site/docs/applications/embedding.html:200 msgid "Use of other Common Services" msgstr "" -#: i2p2www/pages/site/docs/applications/embedding.html:196 +#: 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" @@ -4296,11 +4320,11 @@ msgid "" "and talk to the people who are running them to make sure it's ok." msgstr "" -#: i2p2www/pages/site/docs/applications/embedding.html:204 +#: i2p2www/pages/site/docs/applications/embedding.html:209 msgid "Time / NTP Issues" msgstr "" -#: i2p2www/pages/site/docs/applications/embedding.html:205 +#: 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. " @@ -4309,11 +4333,11 @@ msgid "" "clock is correct." msgstr "" -#: i2p2www/pages/site/docs/applications/embedding.html:213 +#: i2p2www/pages/site/docs/applications/embedding.html:218 msgid "Choose What and How you Bundle" msgstr "" -#: i2p2www/pages/site/docs/applications/embedding.html:214 +#: 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" @@ -4331,11 +4355,19 @@ msgid "" "and i2psnark, for example." msgstr "" -#: i2p2www/pages/site/docs/applications/embedding.html:228 +#: i2p2www/pages/site/docs/applications/embedding.html:233 +msgid "You may also wish to bundle a hosts.txt file." +msgstr "" + +#: i2p2www/pages/site/docs/applications/embedding.html:236 +msgid "Be sure to specify a Java 6 bootclasspath if compiling with Java 8." +msgstr "" + +#: i2p2www/pages/site/docs/applications/embedding.html:244 msgid "Datagram (DHT) considerations" msgstr "" -#: i2p2www/pages/site/docs/applications/embedding.html:229 +#: 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 " @@ -4351,32 +4383,32 @@ msgid "" "have several." msgstr "" -#: i2p2www/pages/site/docs/applications/embedding.html:242 +#: i2p2www/pages/site/docs/applications/embedding.html:258 msgid "Comarketing" msgstr "" -#: i2p2www/pages/site/docs/applications/embedding.html:243 +#: 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 "" -#: i2p2www/pages/site/docs/applications/embedding.html:249 +#: i2p2www/pages/site/docs/applications/embedding.html:265 msgid "Malware" msgstr "" -#: i2p2www/pages/site/docs/applications/embedding.html:250 +#: i2p2www/pages/site/docs/applications/embedding.html:266 msgid "" "Please don't use I2P for evil.\n" "It could cause great harm both to our network and our reputation." msgstr "" -#: i2p2www/pages/site/docs/applications/embedding.html:256 +#: i2p2www/pages/site/docs/applications/embedding.html:272 msgid "Join Us" msgstr "" -#: i2p2www/pages/site/docs/applications/embedding.html:257 +#: 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" @@ -4384,11 +4416,11 @@ msgid "" "We can help get you users, testers, translators, or even coders." msgstr "" -#: i2p2www/pages/site/docs/applications/embedding.html:265 +#: i2p2www/pages/site/docs/applications/embedding.html:281 msgid "Application Examples" msgstr "" -#: i2p2www/pages/site/docs/applications/embedding.html:266 +#: 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" @@ -4398,17 +4430,17 @@ msgid "" " and Monero." msgstr "" -#: i2p2www/pages/site/docs/applications/embedding.html:274 +#: i2p2www/pages/site/docs/applications/embedding.html:290 msgid "Code Example" msgstr "" -#: i2p2www/pages/site/docs/applications/embedding.html:275 +#: i2p2www/pages/site/docs/applications/embedding.html:291 msgid "" "None of the above actually tells you how to write your code to\n" "bundle the Java router, so following is a brief example." msgstr "" -#: i2p2www/pages/site/docs/applications/embedding.html:290 +#: 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" @@ -7272,7 +7304,6 @@ msgid "The Network Database" msgstr "" #: i2p2www/pages/site/docs/how/network-database.html:3 -#: i2p2www/pages/site/docs/transport/ntcp.html:3 msgid "October 2014" msgstr "" @@ -14526,10 +14557,6 @@ msgstr "" msgid "Configuration File Specification" msgstr "" -#: i2p2www/pages/site/docs/spec/configuration.html:3 -msgid "January 2014" -msgstr "" - #: i2p2www/pages/site/docs/spec/configuration.html:7 msgid "" "This page provides a general specification of I2P configuration files,\n" @@ -14638,65 +14665,66 @@ msgid "Configured via /configlogging in the router console." msgstr "" #: i2p2www/pages/site/docs/spec/configuration.html:112 -#: i2p2www/pages/site/docs/spec/configuration.html:142 -#: i2p2www/pages/site/docs/spec/configuration.html:154 +#: i2p2www/pages/site/docs/spec/configuration.html:156 +#: i2p2www/pages/site/docs/spec/configuration.html:168 +#: i2p2www/pages/site/docs/spec/configuration.html:198 msgid "Properties are as follows:" msgstr "" -#: i2p2www/pages/site/docs/spec/configuration.html:133 +#: i2p2www/pages/site/docs/spec/configuration.html:147 msgid "Individual Plugin" msgstr "" -#: i2p2www/pages/site/docs/spec/configuration.html:134 +#: i2p2www/pages/site/docs/spec/configuration.html:148 #, python-format msgid "See the plugin specification." msgstr "" -#: i2p2www/pages/site/docs/spec/configuration.html:139 +#: i2p2www/pages/site/docs/spec/configuration.html:153 msgid "Enable/disable for each installed plugin." msgstr "" -#: i2p2www/pages/site/docs/spec/configuration.html:150 +#: i2p2www/pages/site/docs/spec/configuration.html:164 msgid "Webapps" msgstr "" -#: i2p2www/pages/site/docs/spec/configuration.html:151 +#: i2p2www/pages/site/docs/spec/configuration.html:165 msgid "Enable/disable for each installed webapp." msgstr "" -#: i2p2www/pages/site/docs/spec/configuration.html:163 +#: i2p2www/pages/site/docs/spec/configuration.html:177 msgid "Router" msgstr "" -#: i2p2www/pages/site/docs/spec/configuration.html:164 +#: i2p2www/pages/site/docs/spec/configuration.html:178 msgid "Configured via /configadvanced in the router console." msgstr "" -#: i2p2www/pages/site/docs/spec/configuration.html:168 +#: i2p2www/pages/site/docs/spec/configuration.html:182 msgid "Applications" msgstr "" -#: i2p2www/pages/site/docs/spec/configuration.html:171 +#: i2p2www/pages/site/docs/spec/configuration.html:185 msgid "See documentation in SusiDNS." msgstr "" -#: i2p2www/pages/site/docs/spec/configuration.html:176 +#: i2p2www/pages/site/docs/spec/configuration.html:190 msgid "Configured via the application gui." msgstr "" -#: i2p2www/pages/site/docs/spec/configuration.html:181 +#: i2p2www/pages/site/docs/spec/configuration.html:195 msgid "Configured via the /i2ptunnel application in the router console." msgstr "" -#: i2p2www/pages/site/docs/spec/configuration.html:185 +#: i2p2www/pages/site/docs/spec/configuration.html:364 msgid "Router Console" msgstr "" -#: i2p2www/pages/site/docs/spec/configuration.html:186 +#: i2p2www/pages/site/docs/spec/configuration.html:365 msgid "The router console uses the router.config file." msgstr "" -#: i2p2www/pages/site/docs/spec/configuration.html:191 +#: i2p2www/pages/site/docs/spec/configuration.html:370 msgid "See post on zzz.i2p." msgstr "" @@ -15091,6 +15119,7 @@ msgstr "" #: i2p2www/pages/site/docs/spec/updates.html:204 #: i2p2www/pages/site/docs/spec/updates.html:313 +#: i2p2www/pages/site/docs/spec/updates.html:365 msgid "Goals:" msgstr "" @@ -15113,7 +15142,8 @@ msgid "One-pass signature verification and file extraction" msgstr "" #: i2p2www/pages/site/docs/spec/updates.html:222 -#: i2p2www/pages/site/docs/spec/updates.html:336 +#: i2p2www/pages/site/docs/spec/updates.html:328 +#: i2p2www/pages/site/docs/spec/updates.html:388 msgid "Specification:" msgstr "" @@ -15122,40 +15152,79 @@ msgid "All unused fields must be set to 0 for compatibility with future versions msgstr "" #: i2p2www/pages/site/docs/spec/updates.html:308 -msgid "SU3 News File Specification" +msgid "SU3 Reseed File Specification" msgstr "" #: i2p2www/pages/site/docs/spec/updates.html:309 -msgid "As of 0.9.17, the news is delivered in an \"su3\" file format." +msgid "As of 0.9.14, reseed data is delivered in an \"su3\" file format." msgstr "" #: i2p2www/pages/site/docs/spec/updates.html:316 -msgid "Signed news with strong signatures and trusted certificates" +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 "" -#: i2p2www/pages/site/docs/spec/updates.html:319 +#: 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 "" -#: i2p2www/pages/site/docs/spec/updates.html:322 -msgid "Standard XML format for use with standard parsers" -msgstr "" - -#: i2p2www/pages/site/docs/spec/updates.html:325 -msgid "Standard Atom format for use with standard feed readers and generators" -msgstr "" - -#: i2p2www/pages/site/docs/spec/updates.html:328 -msgid "Sanitization and verification of HTML before displaying on console" +#: i2p2www/pages/site/docs/spec/updates.html:323 +msgid "" +"Single compressed file to speed up reseeding, which was slow to fetch 200" +" files" msgstr "" #: i2p2www/pages/site/docs/spec/updates.html:331 +msgid "The file must be named \"i2pseeds.su3\"." +msgstr "" + +#: i2p2www/pages/site/docs/spec/updates.html:334 +msgid "" +"The file must be in the same directory as the router infos on the web " +"server." +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" +"and then fetch the individual router info files found in the links." +msgstr "" + +#: i2p2www/pages/site/docs/spec/updates.html:360 +msgid "SU3 News File Specification" +msgstr "" + +#: i2p2www/pages/site/docs/spec/updates.html:361 +msgid "As of 0.9.17, the news is delivered in an \"su3\" file format." +msgstr "" + +#: i2p2www/pages/site/docs/spec/updates.html:368 +msgid "Signed news with strong signatures and trusted certificates" +msgstr "" + +#: i2p2www/pages/site/docs/spec/updates.html:374 +msgid "Standard XML format for use with standard parsers" +msgstr "" + +#: i2p2www/pages/site/docs/spec/updates.html:377 +msgid "Standard Atom format for use with standard feed readers and generators" +msgstr "" + +#: i2p2www/pages/site/docs/spec/updates.html:380 +msgid "Sanitization and verification of HTML before displaying on console" +msgstr "" + +#: i2p2www/pages/site/docs/spec/updates.html:383 msgid "" "Suitable for easy implementation on Android and other platforms without " "an HTML console" msgstr "" -#: i2p2www/pages/site/docs/spec/updates.html:440 +#: 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" @@ -15748,7 +15817,7 @@ msgstr "" #: i2p2www/pages/site/docs/transport/ntcp.html:207 #: i2p2www/pages/site/docs/transport/ntcp.html:250 #: i2p2www/pages/site/docs/transport/ntcp.html:332 -#: i2p2www/pages/site/docs/transport/ntcp.html:428 +#: i2p2www/pages/site/docs/transport/ntcp.html:437 msgid "Size:" msgstr "" @@ -15766,7 +15835,7 @@ msgstr "" #: i2p2www/pages/site/docs/transport/ntcp.html:236 #: i2p2www/pages/site/docs/transport/ntcp.html:319 -#: i2p2www/pages/site/docs/transport/ntcp.html:397 +#: i2p2www/pages/site/docs/transport/ntcp.html:398 msgid "Notes:" msgstr "" @@ -15786,7 +15855,7 @@ msgstr "" #: i2p2www/pages/site/docs/transport/ntcp.html:252 #: i2p2www/pages/site/docs/transport/ntcp.html:334 -#: i2p2www/pages/site/docs/transport/ntcp.html:430 +#: i2p2www/pages/site/docs/transport/ntcp.html:439 msgid "Unencrypted Contents:" msgstr "" @@ -15810,7 +15879,7 @@ msgstr "" #: i2p2www/pages/site/docs/transport/ntcp.html:285 #: i2p2www/pages/site/docs/transport/ntcp.html:376 -#: i2p2www/pages/site/docs/transport/ntcp.html:457 +#: i2p2www/pages/site/docs/transport/ntcp.html:466 msgid "Encrypted Contents:" msgstr "" @@ -15847,7 +15916,7 @@ msgid "Alice's 387+ byte `RouterIdentity`" msgstr "" #: i2p2www/pages/site/docs/transport/ntcp.html:366 -#: i2p2www/pages/site/docs/transport/ntcp.html:452 +#: i2p2www/pages/site/docs/transport/ntcp.html:461 msgid "0-15 bytes random data" msgstr "" @@ -15868,31 +15937,31 @@ msgid "" "of message #1) as the IV" msgstr "" -#: i2p2www/pages/site/docs/transport/ntcp.html:399 +#: i2p2www/pages/site/docs/transport/ntcp.html:400 msgid "Bob verifies the signature, and on failure, drops the connection." msgstr "" -#: i2p2www/pages/site/docs/transport/ntcp.html:402 +#: i2p2www/pages/site/docs/transport/ntcp.html:403 msgid "" "Bob may drop the connection if the clock skew with Alice is too high as " "calculated using tsA." msgstr "" -#: i2p2www/pages/site/docs/transport/ntcp.html:405 +#: 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 "" -#: i2p2www/pages/site/docs/transport/ntcp.html:421 +#: i2p2www/pages/site/docs/transport/ntcp.html:430 msgid "Message 4 (Session Confirm B)" msgstr "" -#: i2p2www/pages/site/docs/transport/ntcp.html:422 +#: i2p2www/pages/site/docs/transport/ntcp.html:431 msgid "This is a signature of the critical data. Bob sends Alice:" msgstr "" -#: i2p2www/pages/site/docs/transport/ntcp.html:446 +#: i2p2www/pages/site/docs/transport/ntcp.html:455 msgid "" "the `Signature` of the following concatenated data:\n" " X, Y, Alice's `RouterIdentity`, tsA, tsB.\n" @@ -15900,7 +15969,7 @@ msgid "" "the `SigningPublicKey` in his `RouterIdentity`" msgstr "" -#: i2p2www/pages/site/docs/transport/ntcp.html:470 +#: i2p2www/pages/site/docs/transport/ntcp.html:479 #, python-format msgid "" "Data AES encrypted using the DH " @@ -15911,21 +15980,21 @@ msgid "" "signature types" msgstr "" -#: i2p2www/pages/site/docs/transport/ntcp.html:479 +#: i2p2www/pages/site/docs/transport/ntcp.html:488 msgid "Alice verifies the signature, and on failure, drops the connection." msgstr "" -#: i2p2www/pages/site/docs/transport/ntcp.html:482 +#: 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 "" -#: i2p2www/pages/site/docs/transport/ntcp.html:497 +#: i2p2www/pages/site/docs/transport/ntcp.html:506 msgid "After Establishment" msgstr "" -#: i2p2www/pages/site/docs/transport/ntcp.html:498 +#: i2p2www/pages/site/docs/transport/ntcp.html:507 msgid "" "The connection is established, and standard or time sync messages may be " "exchanged.\n" @@ -15937,11 +16006,11 @@ msgid "" " the next IV." msgstr "" -#: i2p2www/pages/site/docs/transport/ntcp.html:507 +#: i2p2www/pages/site/docs/transport/ntcp.html:516 msgid "Check Connection Message" msgstr "" -#: i2p2www/pages/site/docs/transport/ntcp.html:508 +#: i2p2www/pages/site/docs/transport/ntcp.html:517 msgid "" "Alternately, when Bob receives a connection, it could be a\n" "check connection (perhaps prompted by Bob asking for someone\n" @@ -15951,58 +16020,58 @@ msgid "" "A check info connection will receive 256 bytes containing:" msgstr "" -#: i2p2www/pages/site/docs/transport/ntcp.html:517 +#: i2p2www/pages/site/docs/transport/ntcp.html:526 msgid "32 bytes of uninterpreted, ignored data" msgstr "" -#: i2p2www/pages/site/docs/transport/ntcp.html:518 +#: i2p2www/pages/site/docs/transport/ntcp.html:527 msgid "1 byte size" msgstr "" -#: i2p2www/pages/site/docs/transport/ntcp.html:519 +#: 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 "" -#: i2p2www/pages/site/docs/transport/ntcp.html:520 +#: i2p2www/pages/site/docs/transport/ntcp.html:529 msgid "2 byte port number that the local router was reached on" msgstr "" -#: i2p2www/pages/site/docs/transport/ntcp.html:521 +#: i2p2www/pages/site/docs/transport/ntcp.html:530 msgid "" "4 byte i2p network time as known by the remote side (seconds since the " "epoch)" msgstr "" -#: i2p2www/pages/site/docs/transport/ntcp.html:522 +#: i2p2www/pages/site/docs/transport/ntcp.html:531 msgid "uninterpreted padding data, up to byte 223" msgstr "" -#: i2p2www/pages/site/docs/transport/ntcp.html:523 +#: 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 "" -#: i2p2www/pages/site/docs/transport/ntcp.html:526 +#: i2p2www/pages/site/docs/transport/ntcp.html:535 msgid "Check connection is completely disabled as of release 0.9.12." msgstr "" -#: i2p2www/pages/site/docs/transport/ntcp.html:530 +#: i2p2www/pages/site/docs/transport/ntcp.html:539 msgid "Discussion" msgstr "" -#: i2p2www/pages/site/docs/transport/ntcp.html:531 +#: i2p2www/pages/site/docs/transport/ntcp.html:540 #, python-format msgid "Now on the NTCP Discussion Page." msgstr "" -#: i2p2www/pages/site/docs/transport/ntcp.html:537 +#: i2p2www/pages/site/docs/transport/ntcp.html:546 msgid "The maximum message size should be increased to approximately 32 KB." msgstr "" -#: i2p2www/pages/site/docs/transport/ntcp.html:541 +#: 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" @@ -16013,13 +16082,13 @@ msgid "" "to create a limited number of message sizes." msgstr "" -#: i2p2www/pages/site/docs/transport/ntcp.html:549 +#: 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 "" -#: i2p2www/pages/site/docs/transport/ntcp.html:553 +#: 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?" diff --git a/i2p2www/translations/sv/LC_MESSAGES/get-involved.po b/i2p2www/translations/sv/LC_MESSAGES/get-involved.po index 210d05dd..25fb0353 100644 --- a/i2p2www/translations/sv/LC_MESSAGES/get-involved.po +++ b/i2p2www/translations/sv/LC_MESSAGES/get-involved.po @@ -9,7 +9,7 @@ msgid "" msgstr "" "Project-Id-Version: I2P\n" "Report-Msgid-Bugs-To: https://trac.i2p2.de/\n" -"POT-Creation-Date: 2014-10-22 20:13+0000\n" +"POT-Creation-Date: 2014-11-27 12:12+0000\n" "PO-Revision-Date: 2013-04-27 23:10+0000\n" "Last-Translator: Martin Svensson \n" "Language-Team: Swedish (Sweden) " @@ -399,317 +399,52 @@ msgid "" msgstr "" #: i2p2www/pages/site/get-involved/todo.html:15 -#: i2p2www/pages/site/get-involved/todo.html:53 +#: i2p2www/pages/site/get-involved/todo.html:38 msgid "Core functionality" msgstr "" #: i2p2www/pages/site/get-involved/todo.html:15 -#: i2p2www/pages/site/get-involved/todo.html:27 -#: i2p2www/pages/site/get-involved/todo.html:51 +#: i2p2www/pages/site/get-involved/todo.html:21 +#: i2p2www/pages/site/get-involved/todo.html:36 msgid "link" msgstr "" #: i2p2www/pages/site/get-involved/todo.html:17 -#: i2p2www/pages/site/get-involved/todo.html:56 -msgid "NAT/Firewall bridging via 1-hop restricted routes" -msgstr "" - -#: i2p2www/pages/site/get-involved/todo.html:20 -#: i2p2www/pages/site/get-involved/todo.html:129 -msgid "High degree transport layer with UDP, NBIO, or NIO" -msgstr "" - -#: i2p2www/pages/site/get-involved/todo.html:23 -#: i2p2www/pages/site/get-involved/todo.html:217 +#: i2p2www/pages/site/get-involved/todo.html:41 msgid "NetworkDB and profile tuning and ejection policy for large nets" msgstr "" -#: i2p2www/pages/site/get-involved/todo.html:27 -#: i2p2www/pages/site/get-involved/todo.html:241 +#: i2p2www/pages/site/get-involved/todo.html:21 +#: i2p2www/pages/site/get-involved/todo.html:65 msgid "Security / anonymity" msgstr "" -#: i2p2www/pages/site/get-involved/todo.html:29 -#: i2p2www/pages/site/get-involved/todo.html:244 -msgid "" -"Per-hop tunnel id & new permuted TunnelVerificationStructure " -"encryption" -msgstr "" - -#: i2p2www/pages/site/get-involved/todo.html:32 -#: i2p2www/pages/site/get-involved/todo.html:294 -msgid "Strict ordering of participants within tunnels" -msgstr "" - -#: i2p2www/pages/site/get-involved/todo.html:35 -msgid "Randomly permuted tunnel lengths" -msgstr "" - -#: i2p2www/pages/site/get-involved/todo.html:38 -#: i2p2www/pages/site/get-involved/todo.html:356 +#: 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 "" -#: i2p2www/pages/site/get-involved/todo.html:41 -#: i2p2www/pages/site/get-involved/todo.html:375 +#: 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 "" -#: i2p2www/pages/site/get-involved/todo.html:44 -#: i2p2www/pages/site/get-involved/todo.html:404 +#: 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 "" -#: i2p2www/pages/site/get-involved/todo.html:47 -#: i2p2www/pages/site/get-involved/todo.html:441 +#: i2p2www/pages/site/get-involved/todo.html:32 +#: i2p2www/pages/site/get-involved/todo.html:153 msgid "Stop & go mix w/ garlics & tunnels" msgstr "" -#: i2p2www/pages/site/get-involved/todo.html:51 -#: i2p2www/pages/site/get-involved/todo.html:455 +#: i2p2www/pages/site/get-involved/todo.html:36 +#: i2p2www/pages/site/get-involved/todo.html:167 msgid "Performance" msgstr "" -#: i2p2www/pages/site/get-involved/todo.html:61 -msgid "Implemented in I2P 0.6.0.6" -msgstr "" - -#: i2p2www/pages/site/get-involved/todo.html:62 -msgid "" -"The functionality of allowing routers to fully participate within the " -"network \n" -"while behind firewalls and NATs that they do not control requires some " -"basic \n" -"restricted route operation (since those peers will not be able to receive" -" \n" -"inbound connections). To do this successfully, you consider peers one of" -" \n" -"two ways:" -msgstr "" - -#: i2p2www/pages/site/get-involved/todo.html:72 -msgid "" -"Peers who have reachable interfaces - these peers do not need to \n" -"do anything special" -msgstr "" - -#: i2p2www/pages/site/get-involved/todo.html:76 -msgid "" -"Peers who do not have reachable interfaces - these peers must " -"build \n" -"a tunnel pointing at them where the gateway is one of the peers they have" -" \n" -"established a connection with who has both a publicly reachable interface" -" \n" -"and who has agreed to serve as their 'introducer'." -msgstr "" - -#: i2p2www/pages/site/get-involved/todo.html:84 -msgid "" -"To do this, peers who have no IP address simply connect to a few peers, \n" -"build a tunnel through them, and publish a reference to those tunnels " -"within \n" -"their RouterInfo structure in the network database." -msgstr "" - -#: i2p2www/pages/site/get-involved/todo.html:89 -msgid "" -"When someone wants to contact any particular router, they first must get" -" \n" -"its RouterInfo from the network database, which will tell them whether " -"they \n" -"can connect directly (e.g. the peer has a publicly reachable interface) \n" -"or whether they need to contact them indirectly. Direct connections occur" -" \n" -"as normal, while indirect connections are done through one of the " -"published \n" -"tunnels." -msgstr "" - -#: i2p2www/pages/site/get-involved/todo.html:97 -msgid "" -"When a router just wants to get a message or two to a specific hidden " -"peer, \n" -"they can just use the indirect tunnel for sending the payload. However, \n" -"if the router wants to talk to the hidden peer often (for instance, as " -"part \n" -"of a tunnel), they will send a garlic routed message through the indirect" -" \n" -"tunnel to that hidden peer which unwraps to contain a message which " -"should \n" -"be sent to the originating router. That hidden peer then establishes an \n" -"outbound connection to the originating router and from then on, those two" -" \n" -"routers can talk to each other directly over that newly established " -"direct \n" -"connection." -msgstr "" - -#: i2p2www/pages/site/get-involved/todo.html:108 -msgid "" -"Of course, that only works if the originating peer can receive " -"connections \n" -"(they aren't also hidden). However, if the originating peer is hidden, " -"they \n" -"can simply direct the garlic routed message to come back to the " -"originating \n" -"peer's inbound tunnel." -msgstr "" - -#: i2p2www/pages/site/get-involved/todo.html:114 -msgid "" -"This is not meant to provide a way for a peer's IP address to be " -"concealed, \n" -"merely as a way to let people behind firewalls and NATs fully operate " -"within \n" -"the network. Concealing the peer's IP address adds a little more work, as" -" \n" -"described below." -msgstr "" - -#: i2p2www/pages/site/get-involved/todo.html:120 -msgid "" -"With this technique, any router can participate as any part of a tunnel." -" \n" -"For efficiency purposes, a hidden peer would be a bad choice for an " -"inbound \n" -"gateway, and within any given tunnel, two neighboring peers wouldn't want" -" \n" -"to be hidden. But that is not technically necessary." -msgstr "" - -#: i2p2www/pages/site/get-involved/todo.html:132 -msgid "Both UDP and NIO have been Implemented in I2P" -msgstr "" - -#: i2p2www/pages/site/get-involved/todo.html:133 -msgid "" -"Standard TCP communication in Java generally requires blocking socket \n" -"calls, and to keep a blocked socket from hanging the entire system, those" -" \n" -"blocking calls are done on their own threads. Our current TCP transport \n" -"is implemented in a naive fashion - for each peer we are talking to, we \n" -"have one thread reading and one thread writing. The reader thread simply" -" \n" -"loops a bunch of read() calls, building I2NP messages and adding them \n" -"to our internal inbound message queue, and the writer thread pulls " -"messages \n" -"off a per-connection outbound message queue and shoves the data through \n" -"write() calls." -msgstr "" - -#: i2p2www/pages/site/get-involved/todo.html:144 -msgid "" -"We do this fairly efficiently, from a CPU perspective - at any time, \n" -"almost all of these threads are sitting idle, blocked waiting for " -"something \n" -"to do. However, each thread consumes real resources (on older Linux " -"kernels, \n" -"for instance, each thread would often be implemented as a fork()'ed " -"process). \n" -"As the network grows, the number of peers each router will want to talk \n" -"with will increase (remember, I2P is fully connected, meaning that any \n" -"given peer should know how to get a message to any other peer, and " -"restricted \n" -"route support will probably not significantly reduce the number of " -"connections \n" -"necessary). This means that with a 100,000 router network, each router \n" -"will have up to 199,998 threads just to deal with the TCP connections!" -msgstr "" - -#: i2p2www/pages/site/get-involved/todo.html:156 -msgid "" -"Obviously, that just won't work. We need to use a transport layer that \n" -"can scale. In Java, we have two main camps:" -msgstr "" - -#: i2p2www/pages/site/get-involved/todo.html:161 -#, python-format -msgid "" -"Implemented in I2P 0.6 (\"SSU\") as documented elsewhere" -msgstr "" - -#: i2p2www/pages/site/get-involved/todo.html:164 -msgid "" -"Sending and receiving UDP datagrams is a connectionless operation - if \n" -"we are communicating with 100,000 peers, we simply stick the UDP packets" -" \n" -"in a queue and have a single thread pulling them off the queue and " -"shoving \n" -"them out the pipe (and to receive, have a single thread pulling in any \n" -"UDP packets received and adding them to an inbound queue)." -msgstr "" - -#: i2p2www/pages/site/get-involved/todo.html:171 -msgid "" -"However, moving to UDP means losing the benefits of TCP's ordering, " -"congestion \n" -"control, MTU discovery, etc. Implementing that code will take significant" -" \n" -"work, however I2P doesn't need it to be as strong as TCP. Specifically, \n" -"a while ago I was taking some measurements in the simulator and on the \n" -"live net, and the vast majority of messages transferred would fit easily" -" \n" -"within a single unfragmented UDP packet, and the largest of the messages" -" \n" -"would fit within 20-30 packets. As mule pointed out, TCP adds a " -"significant \n" -"overhead when dealing with so many small packets, as the ACKs are within" -" \n" -"an order of magnitude in size. With UDP, we can optimize the transport \n" -"for both efficiency and resilience by taking into account I2P's " -"particular \n" -"needs." -msgstr "" - -#: i2p2www/pages/site/get-involved/todo.html:184 -msgid "It will be a lot of work though." -msgstr "" - -#: i2p2www/pages/site/get-involved/todo.html:187 -msgid "NIO or NBIO" -msgstr "" - -#: i2p2www/pages/site/get-involved/todo.html:188 -msgid "NIO Implemented in I2P 0.6.1.22 (\"NTCP\")" -msgstr "" - -#: i2p2www/pages/site/get-involved/todo.html:191 -msgid "" -"In Java 1.4, a set of \"New I/O\" packages was introduced, allowing Java" -" \n" -"developers to take advantage of the operating system's nonblocking IO \n" -"capabilities - allowing you to maintain a large number of concurrent IO \n" -"operations without requiring a separate thread for each. There is much \n" -"promise with this approach, as we can scalable handle a large number of \n" -"concurrent connections and we don't have to write a mini-TCP stack with \n" -"UDP. However, the NIO packages have not proven themselves to be battle-" -"ready, \n" -"as the Freenet developer's found. In addition, requiring NIO support " -"would \n" -"mean we can't run on any of the open source JVMs like Kaffe, \n" -"as GNU/Classpath has only " -"limited \n" -"support for NIO. (note: this may not be the case anymore, as there \n" -"has been some progress on Classpath's NIO, but it is an unknown " -"quantity)" -msgstr "" - -#: i2p2www/pages/site/get-involved/todo.html:205 -#, python-format -msgid "" -"Another alternative along the same lines is the Non" -" \n" -"Blocking I/O package - essentially a cleanroom NIO implementation \n" -"(written before NIO was around). It works by using some native OS code \n" -"to do the nonblocking IO, passing off events through Java. It seems to \n" -"be working with Kaffe, though there doesn't seem to be much development \n" -"activity on it lately (likely due to 1.4's NIO deployment)." -msgstr "" - -#: i2p2www/pages/site/get-involved/todo.html:220 +#: i2p2www/pages/site/get-involved/todo.html:44 msgid "" "Within the current network database and profile management " "implementation, \n" @@ -732,152 +467,14 @@ msgid "" "code yet, since we aren't going to need it for a while." msgstr "" -#: i2p2www/pages/site/get-involved/todo.html:235 +#: 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" "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:247 -#: i2p2www/pages/site/get-involved/todo.html:331 -#, python-format -msgid "" -"Addressed in I2P 0.5 as documented elsewhere" -msgstr "" - -#: i2p2www/pages/site/get-involved/todo.html:250 -msgid "" -"Right now, if Alice builds a four hop inbound tunnel starting at Elvis, \n" -"going to Dave, then to Charlie, then Bob, and finally Alice " -"(A<--B<--C<--D<--E), \n" -"all five of them will know they are participating in tunnel \"123\", as \n" -"the messages are tagged as such. What we want to do is give each hop " -"their \n" -"own unique tunnel hop ID - Charlie will receive messages on tunnel 234 \n" -"and forward them to tunnel 876 on Bob. The intent is to prevent Bob or \n" -"Charlie from knowing that they are in Alice's tunnel, as if each hop in \n" -"the tunnel had the same tunnel ID, collusion attacks aren't much work." -msgstr "" - -#: i2p2www/pages/site/get-involved/todo.html:260 -msgid "" -"Adding a unique tunnel ID per hop isn't hard, but by itself, " -"insufficient. \n" -"If Dave and Bob are under the control of the same attacker, they wouldn't" -" \n" -"be able to tell they are in the same tunnel due to the tunnel ID, but \n" -"would be able to tell by the message bodies and verification structures \n" -"by simply comparing them. To prevent that, the tunnel must use layered \n" -"encryption along the path, both on the payload of the tunneled message \n" -"and on the verification structure (used to prevent simple tagging " -"attacks). \n" -"This requires some simple modifications to the TunnelMessage, as well \n" -"as the inclusion of per-hop secret keys delivered during tunnel creation" -" \n" -"and given to the tunnel's gateway. We must fix a maximum tunnel length \n" -"(e.g. 16 hops) and instruct the gateway to encrypt the message to each \n" -"of the 16 delivered secret keys, in reverse order, and to encrypt the \n" -"signature of the hash of the (encrypted) payload at each step. The " -"gateway \n" -"then sends that 16-step encrypted message, along with a 16-step and " -"16-wide \n" -"encrypted mapping to the first hop, which then decrypts the mapping and \n" -"the payload with their secret key, looking in the 16-wide mapping for \n" -"the entry associated with their own hop (keyed by the per-hop tunnel ID)" -" \n" -"and verifying the payload by checking it against the associated signed \n" -"hash." -msgstr "" - -#: i2p2www/pages/site/get-involved/todo.html:281 -msgid "" -"The tunnel gateway does still have more information than the other peers" -" \n" -"in the tunnel, and compromising both the gateway and a tunnel participant" -" \n" -"would allow those peers to collude, exposing the fact that they are both" -" \n" -"in the same tunnel. In addition, neighboring peers know that they are \n" -"in the same tunnel anyway, as they know who they send the message to (and" -" \n" -"with IP-based transports without restricted routes, they know who they \n" -"got it from). However, the above two techniques significantly increase \n" -"the cost of gaining meaningful samples when dealing with longer tunnels." -msgstr "" - -#: i2p2www/pages/site/get-involved/todo.html:297 -msgid "Implemented in release 0.6.2" -msgstr "" - -#: i2p2www/pages/site/get-involved/todo.html:300 -#, python-format -msgid "" -"As Connelly proposed to deal with the\n" -"predecessor attack (2008\n" -"update), keeping the order of peers within our tunnels consistent \n" -"(aka whenever Alice creates a tunnel with both Bob and Charlie in it, \n" -"Bob's next hop is always Charlie), we address the issue as Bob doesn't \n" -"get to substantially sample Alice's peer selection group. We may even \n" -"want to explicitly allow Bob to participate in Alice's tunnels in only \n" -"one way - receiving a message from Dave and sending it to Charlie - and \n" -"if any of those peers are not available to participate in the tunnel (due" -" \n" -"to overload, network disconnection, etc), avoid asking Bob to participate" -" \n" -"in any tunnels until they are back online." -msgstr "" - -#: i2p2www/pages/site/get-involved/todo.html:315 -msgid "" -"More analysis is necessary for revising the tunnel creation - at the \n" -"moment, we simply select and order randomly within the peer's top tier \n" -"of peers (ones with fast + high capacity)." -msgstr "" - -#: i2p2www/pages/site/get-involved/todo.html:320 -msgid "" -"Adding a strict ordering to peers in a tunnel also improves the anonymity" -" \n" -"of peers with 0-hop tunnels, as otherwise the fact that a peer's gateway" -" \n" -"is always the same would be particularly damning. However, peers with \n" -"0-hop tunnels may want to periodically use a 1-hop tunnel to simulate \n" -"the failure of a normally reliable gateway peer (so every MTBF*(tunnel \n" -"duration) minutes, use a 1-hop tunnel)." -msgstr "" - -#: i2p2www/pages/site/get-involved/todo.html:337 -msgid "" -"Without tunnel length permutation, if someone were to somehow detect that" -" \n" -"a destination had a particular number of hops, it might be able to use " -"that \n" -"information to identify the router the destination is located on, per the" -" \n" -"predecessor attack. For instance, if everyone has 2-hop tunnels, if Bob \n" -"receives a tunnel message from Charlie and forwards it to Alice, Bob " -"knows \n" -"Alice is the final router in the tunnel. If Bob were to identify what " -"destination \n" -"that tunnel served (by means of colluding with the gateway and harvesting" -" \n" -"the network database for all of the LeaseSets), he would know the router" -" \n" -"on which that destination is located (and without restricted routes, that" -" \n" -"would mean what IP address the destination is on)." -msgstr "" - -#: i2p2www/pages/site/get-involved/todo.html:349 -msgid "" -"It is to counter user behavior that tunnel lengths should be permuted, \n" -"using algorithms based on the length requested (for example, the 1/MTBF \n" -"length change for 0-hop tunnels outlined above)." -msgstr "" - -#: i2p2www/pages/site/get-involved/todo.html:359 +#: i2p2www/pages/site/get-involved/todo.html:71 msgid "" "The restricted route functionality described before was simply a " "functional \n" @@ -899,7 +496,7 @@ msgid "" "to forward it as requested." msgstr "" -#: i2p2www/pages/site/get-involved/todo.html:378 +#: i2p2www/pages/site/get-involved/todo.html:90 #, python-format msgid "" "Within the network, we will want some way to deter people from consuming" @@ -913,7 +510,7 @@ msgid "" "to make certain requests \"expensive\"." msgstr "" -#: i2p2www/pages/site/get-involved/todo.html:386 +#: 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 " @@ -931,7 +528,7 @@ msgid "" "with few resources." msgstr "" -#: i2p2www/pages/site/get-involved/todo.html:397 +#: 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" @@ -939,7 +536,7 @@ msgid "" "appropriate." msgstr "" -#: i2p2www/pages/site/get-involved/todo.html:407 +#: i2p2www/pages/site/get-involved/todo.html:119 #, python-format msgid "" "To powerful passive external observers as well as large colluding " @@ -960,7 +557,7 @@ msgid "" "tunnel mixing strategies." msgstr "" -#: i2p2www/pages/site/get-involved/todo.html:420 +#: 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" @@ -978,7 +575,7 @@ msgid "" "available." msgstr "" -#: i2p2www/pages/site/get-involved/todo.html:433 +#: i2p2www/pages/site/get-involved/todo.html:145 msgid "" "In addition, we may want to implement code to dynamically reroute tunnels" " \n" @@ -988,7 +585,7 @@ msgid "" "with instructions to redefine the next-hop in the tunnel." msgstr "" -#: i2p2www/pages/site/get-involved/todo.html:444 +#: 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" @@ -1003,7 +600,7 @@ msgid "" "clove exposed includes delay instructions." msgstr "" -#: i2p2www/pages/site/get-involved/todo.html:456 +#: i2p2www/pages/site/get-involved/todo.html:168 #, python-format msgid "" "Performance related improvements are listed on the\n" @@ -4136,3 +3733,15 @@ msgid "" "href=\"http://%(zzz)s/forums/14\">translation forum on %(zzz)s." msgstr "" + + + + + + + + + + + + diff --git a/pots/docs.pot b/pots/docs.pot index b203c6a9..60652941 100644 --- a/pots/docs.pot +++ b/pots/docs.pot @@ -8,7 +8,7 @@ msgid "" msgstr "" "Project-Id-Version: I2P website\n" "Report-Msgid-Bugs-To: http://trac.i2p2.de\n" -"POT-Creation-Date: 2014-11-16 02:59+0000\n" +"POT-Creation-Date: 2014-11-27 12:12+0000\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language-Team: LANGUAGE \n" @@ -25,7 +25,9 @@ msgstr "" #: i2p2www/pages/site/docs/applications/embedding.html:3 #: i2p2www/pages/site/docs/how/cryptography.html:3 #: i2p2www/pages/site/docs/protocol/i2cp.html:3 +#: i2p2www/pages/site/docs/spec/configuration.html:3 #: i2p2www/pages/site/docs/spec/updates.html:3 +#: i2p2www/pages/site/docs/transport/ntcp.html:3 msgid "November 2014" msgstr "" @@ -128,7 +130,7 @@ msgstr "" msgid "Managed Clients" msgstr "" -#: i2p2www/pages/site/docs/index.html:44 i2p2www/pages/site/docs/index.html:217 +#: i2p2www/pages/site/docs/index.html:44 i2p2www/pages/site/docs/index.html:222 msgid "Embedding the router in your application" msgstr "" @@ -145,7 +147,7 @@ msgstr "" msgid "hostsdb.blockfile Format" msgstr "" -#: i2p2www/pages/site/docs/index.html:48 i2p2www/pages/site/docs/index.html:189 +#: i2p2www/pages/site/docs/index.html:48 i2p2www/pages/site/docs/index.html:194 msgid "Configuration File Format" msgstr "" @@ -163,369 +165,379 @@ msgstr "" msgid "Application Development Overview and Guide" msgstr "" -#: i2p2www/pages/site/docs/index.html:72 -msgid "SAM Protocol" +#: i2p2www/pages/site/docs/index.html:58 +#: i2p2www/pages/site/docs/api/i2ptunnel.html:55 +msgid "I2PTunnel Configuration" msgstr "" #: i2p2www/pages/site/docs/index.html:74 -msgid "SAMv2 Protocol" +msgid "SAM Protocol" msgstr "" #: i2p2www/pages/site/docs/index.html:76 -msgid "SAMv3 Protocol" +msgid "SAMv2 Protocol" msgstr "" #: i2p2www/pages/site/docs/index.html:78 +msgid "SAMv3 Protocol" +msgstr "" + +#: i2p2www/pages/site/docs/index.html:80 msgid "BOB Protocol" msgstr "" -#: i2p2www/pages/site/docs/index.html:81 +#: i2p2www/pages/site/docs/index.html:83 msgid "End-to-End Transport API and Protocols" msgstr "" -#: i2p2www/pages/site/docs/index.html:82 +#: i2p2www/pages/site/docs/index.html:84 msgid "" "The end-to-end protocols used by clients for reliable and unreliable " "communication." msgstr "" -#: i2p2www/pages/site/docs/index.html:84 +#: i2p2www/pages/site/docs/index.html:86 #: i2p2www/pages/site/docs/api/streaming.html:2 msgid "Streaming Library" msgstr "" -#: i2p2www/pages/site/docs/index.html:86 +#: i2p2www/pages/site/docs/index.html:88 msgid "Streaming Protocol Specification" msgstr "" -#: i2p2www/pages/site/docs/index.html:88 +#: i2p2www/pages/site/docs/index.html:90 msgid "Streaming Javadoc" msgstr "" -#: i2p2www/pages/site/docs/index.html:90 +#: i2p2www/pages/site/docs/index.html:92 #: i2p2www/pages/site/docs/api/datagrams.html:2 msgid "Datagrams" msgstr "" -#: i2p2www/pages/site/docs/index.html:92 +#: i2p2www/pages/site/docs/index.html:94 msgid "Datagram Javadoc" msgstr "" -#: i2p2www/pages/site/docs/index.html:95 +#: i2p2www/pages/site/docs/index.html:97 msgid "Client-to-Router Interface API and Protocol" msgstr "" -#: i2p2www/pages/site/docs/index.html:96 +#: 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" "Traditionally used only by Java applications and higher-level APIs." msgstr "" -#: i2p2www/pages/site/docs/index.html:101 +#: i2p2www/pages/site/docs/index.html:103 msgid "I2CP - I2P Control Protocol / API overview" msgstr "" -#: i2p2www/pages/site/docs/index.html:103 +#: i2p2www/pages/site/docs/index.html:105 msgid "I2CP Specification" msgstr "" -#: i2p2www/pages/site/docs/index.html:105 +#: i2p2www/pages/site/docs/index.html:107 msgid "I2CP API Javadoc" msgstr "" -#: i2p2www/pages/site/docs/index.html:107 -#: i2p2www/pages/site/docs/index.html:136 +#: i2p2www/pages/site/docs/index.html:109 +#: i2p2www/pages/site/docs/index.html:139 msgid "Common data structures specification" msgstr "" -#: i2p2www/pages/site/docs/index.html:109 -#: i2p2www/pages/site/docs/index.html:138 +#: i2p2www/pages/site/docs/index.html:111 +#: i2p2www/pages/site/docs/index.html:141 msgid "Data Structures Javadoc" msgstr "" -#: i2p2www/pages/site/docs/index.html:112 +#: i2p2www/pages/site/docs/index.html:114 msgid "End-to-End Encryption" msgstr "" -#: i2p2www/pages/site/docs/index.html:113 +#: i2p2www/pages/site/docs/index.html:115 msgid "How client messages are end-to-end encrypted by the router." msgstr "" -#: i2p2www/pages/site/docs/index.html:115 +#: i2p2www/pages/site/docs/index.html:117 msgid "ElGamal/AES+SessionTag encryption" msgstr "" -#: i2p2www/pages/site/docs/index.html:116 -#: i2p2www/pages/site/docs/index.html:149 +#: i2p2www/pages/site/docs/index.html:118 +#: i2p2www/pages/site/docs/index.html:152 msgid "ElGamal and AES cryptography details" msgstr "" -#: i2p2www/pages/site/docs/index.html:119 +#: i2p2www/pages/site/docs/index.html:121 #: i2p2www/pages/site/docs/how/tech-intro.html:15 #: i2p2www/pages/site/docs/how/tech-intro.html:329 msgid "Network Database" msgstr "" -#: i2p2www/pages/site/docs/index.html:120 +#: i2p2www/pages/site/docs/index.html:122 msgid "" "Distributed storage and retrieval of information about routers and " "clients." msgstr "" -#: i2p2www/pages/site/docs/index.html:122 +#: i2p2www/pages/site/docs/index.html:124 msgid "Network database overview, details, and threat analysis" msgstr "" -#: i2p2www/pages/site/docs/index.html:123 +#: i2p2www/pages/site/docs/index.html:125 msgid "Cryptographic hashes" msgstr "" -#: i2p2www/pages/site/docs/index.html:124 +#: i2p2www/pages/site/docs/index.html:126 msgid "Cryptographic signatures" msgstr "" #: i2p2www/pages/site/docs/index.html:127 +#: i2p2www/pages/site/docs/index.html:186 +msgid "Router reseed specification" +msgstr "" + +#: i2p2www/pages/site/docs/index.html:130 msgid "Router Message Protocol" msgstr "" -#: i2p2www/pages/site/docs/index.html:128 +#: i2p2www/pages/site/docs/index.html:131 msgid "" "I2P is a message-oriented router. The messages sent between routers are " "defined by the I2NP protocol." msgstr "" -#: i2p2www/pages/site/docs/index.html:130 +#: i2p2www/pages/site/docs/index.html:133 msgid "I2NP - I2P Network Protocol Overview" msgstr "" -#: i2p2www/pages/site/docs/index.html:132 +#: i2p2www/pages/site/docs/index.html:135 msgid "I2NP Specification" msgstr "" -#: i2p2www/pages/site/docs/index.html:134 +#: i2p2www/pages/site/docs/index.html:137 msgid "I2NP Javadoc" msgstr "" -#: i2p2www/pages/site/docs/index.html:141 +#: i2p2www/pages/site/docs/index.html:144 #: i2p2www/pages/site/docs/how/tech-intro.html:14 #: i2p2www/pages/site/docs/how/tech-intro.html:228 msgid "Tunnels" msgstr "" -#: i2p2www/pages/site/docs/index.html:142 +#: i2p2www/pages/site/docs/index.html:145 msgid "" "Selecting peers, requesting tunnels through those peers, and encrypting " "and routing messages through these tunnels." msgstr "" -#: i2p2www/pages/site/docs/index.html:144 +#: i2p2www/pages/site/docs/index.html:147 msgid "Peer profiling and selection" msgstr "" -#: i2p2www/pages/site/docs/index.html:145 +#: i2p2www/pages/site/docs/index.html:148 msgid "Tunnel routing overview" msgstr "" -#: i2p2www/pages/site/docs/index.html:146 +#: i2p2www/pages/site/docs/index.html:149 msgid "Garlic routing and \"garlic\" terminology" msgstr "" -#: i2p2www/pages/site/docs/index.html:147 +#: i2p2www/pages/site/docs/index.html:150 msgid "Tunnel building and encryption" msgstr "" -#: i2p2www/pages/site/docs/index.html:148 +#: i2p2www/pages/site/docs/index.html:151 msgid "ElGamal/AES" msgstr "" -#: i2p2www/pages/site/docs/index.html:148 +#: i2p2www/pages/site/docs/index.html:151 msgid "for build request encryption" msgstr "" -#: i2p2www/pages/site/docs/index.html:150 +#: i2p2www/pages/site/docs/index.html:153 msgid "Tunnel building specification" msgstr "" -#: i2p2www/pages/site/docs/index.html:151 +#: i2p2www/pages/site/docs/index.html:154 msgid "Low-level tunnel message specification" msgstr "" -#: i2p2www/pages/site/docs/index.html:152 +#: i2p2www/pages/site/docs/index.html:155 #: i2p2www/pages/site/docs/tunnels/unidirectional.html:2 msgid "Unidirectional Tunnels" msgstr "" -#: i2p2www/pages/site/docs/index.html:153 +#: i2p2www/pages/site/docs/index.html:156 #: i2p2www/pages/site/docs/how/peer-selection.html:299 msgid "Peer Profiling and Selection in the I2P Anonymous Network" msgstr "" -#: i2p2www/pages/site/docs/index.html:154 +#: i2p2www/pages/site/docs/index.html:157 msgid "2009 paper (pdf), not current but still generally accurate" msgstr "" -#: i2p2www/pages/site/docs/index.html:157 +#: i2p2www/pages/site/docs/index.html:160 msgid "Transport Layer" msgstr "" -#: i2p2www/pages/site/docs/index.html:158 +#: i2p2www/pages/site/docs/index.html:161 msgid "The protocols for direct (point-to-point) router to router communication." msgstr "" -#: i2p2www/pages/site/docs/index.html:160 +#: i2p2www/pages/site/docs/index.html:163 msgid "Transport layer overview" msgstr "" -#: i2p2www/pages/site/docs/index.html:162 +#: i2p2www/pages/site/docs/index.html:165 msgid "TCP-based transport overview and specification" msgstr "" -#: i2p2www/pages/site/docs/index.html:164 +#: i2p2www/pages/site/docs/index.html:167 msgid "UDP-based transport overview" msgstr "" -#: i2p2www/pages/site/docs/index.html:166 +#: i2p2www/pages/site/docs/index.html:169 msgid "SSU specification" msgstr "" -#: i2p2www/pages/site/docs/index.html:168 +#: i2p2www/pages/site/docs/index.html:171 msgid "NTCP transport encryption" msgstr "" -#: i2p2www/pages/site/docs/index.html:170 +#: i2p2www/pages/site/docs/index.html:173 msgid "SSU transport encryption" msgstr "" -#: i2p2www/pages/site/docs/index.html:172 +#: i2p2www/pages/site/docs/index.html:175 msgid "Transport Javadoc" msgstr "" -#: i2p2www/pages/site/docs/index.html:174 +#: i2p2www/pages/site/docs/index.html:177 msgid "NTCP Javadoc" msgstr "" -#: i2p2www/pages/site/docs/index.html:176 +#: i2p2www/pages/site/docs/index.html:179 msgid "SSU Javadoc" msgstr "" -#: i2p2www/pages/site/docs/index.html:179 +#: i2p2www/pages/site/docs/index.html:182 msgid "Other Router Topics" msgstr "" -#: i2p2www/pages/site/docs/index.html:181 +#: i2p2www/pages/site/docs/index.html:184 msgid "Router software updates" msgstr "" -#: i2p2www/pages/site/docs/index.html:183 +#: i2p2www/pages/site/docs/index.html:188 msgid "Native BigInteger Library" msgstr "" -#: i2p2www/pages/site/docs/index.html:185 +#: i2p2www/pages/site/docs/index.html:190 msgid "Time synchronization and NTP" msgstr "" -#: i2p2www/pages/site/docs/index.html:187 +#: i2p2www/pages/site/docs/index.html:192 msgid "Performance" msgstr "" -#: i2p2www/pages/site/docs/index.html:194 +#: i2p2www/pages/site/docs/index.html:199 msgid "Developer's Guides and Resources" msgstr "" -#: i2p2www/pages/site/docs/index.html:196 +#: i2p2www/pages/site/docs/index.html:201 msgid "New Developer's Guide" msgstr "" -#: i2p2www/pages/site/docs/index.html:198 +#: i2p2www/pages/site/docs/index.html:203 msgid "New Translator's Guide" msgstr "" -#: i2p2www/pages/site/docs/index.html:200 +#: i2p2www/pages/site/docs/index.html:205 msgid "Monotone Guide" msgstr "" -#: i2p2www/pages/site/docs/index.html:202 +#: i2p2www/pages/site/docs/index.html:207 msgid "Developer Guidelines" msgstr "" -#: i2p2www/pages/site/docs/index.html:204 +#: i2p2www/pages/site/docs/index.html:209 msgid "Javadocs on the standard internet:" msgstr "" -#: i2p2www/pages/site/docs/index.html:205 -#: i2p2www/pages/site/docs/index.html:209 #: i2p2www/pages/site/docs/index.html:210 -#: i2p2www/pages/site/docs/index.html:211 +#: i2p2www/pages/site/docs/index.html:214 +#: i2p2www/pages/site/docs/index.html:215 +#: i2p2www/pages/site/docs/index.html:216 #, python-format msgid "Server %(num)s" msgstr "" -#: i2p2www/pages/site/docs/index.html:206 -#: i2p2www/pages/site/docs/index.html:215 +#: i2p2www/pages/site/docs/index.html:211 +#: i2p2www/pages/site/docs/index.html:220 msgid "" "Note: always verify that javadocs are current by checking the release " "number." msgstr "" -#: i2p2www/pages/site/docs/index.html:208 +#: i2p2www/pages/site/docs/index.html:213 msgid "Javadocs inside I2P:" msgstr "" -#: i2p2www/pages/site/docs/index.html:219 +#: i2p2www/pages/site/docs/index.html:224 msgid "Ports used by I2P" msgstr "" -#: i2p2www/pages/site/docs/index.html:221 +#: i2p2www/pages/site/docs/index.html:226 msgid "Automatic updates to development builds inside I2P" msgstr "" -#: i2p2www/pages/site/docs/index.html:223 +#: i2p2www/pages/site/docs/index.html:228 msgid "Updating the wrapper manually" msgstr "" -#: i2p2www/pages/site/docs/index.html:225 +#: i2p2www/pages/site/docs/index.html:230 msgid "User forum" msgstr "" -#: i2p2www/pages/site/docs/index.html:227 +#: i2p2www/pages/site/docs/index.html:232 msgid "Developer forum inside I2P" msgstr "" -#: i2p2www/pages/site/docs/index.html:229 +#: i2p2www/pages/site/docs/index.html:234 msgid "Bug tracker" msgstr "" -#: i2p2www/pages/site/docs/index.html:231 +#: i2p2www/pages/site/docs/index.html:236 msgid "Viewmtn inside I2P" msgstr "" -#: i2p2www/pages/site/docs/index.html:233 +#: i2p2www/pages/site/docs/index.html:238 msgid "I2P Source exported to GitHub" msgstr "" -#: i2p2www/pages/site/docs/index.html:235 +#: i2p2www/pages/site/docs/index.html:240 msgid "I2P Source Git Repo inside I2P" msgstr "" -#: i2p2www/pages/site/docs/index.html:237 +#: i2p2www/pages/site/docs/index.html:242 msgid "Source translation at Transifex" msgstr "" -#: i2p2www/pages/site/docs/index.html:239 +#: i2p2www/pages/site/docs/index.html:244 msgid "Roadmap wiki" msgstr "" -#: i2p2www/pages/site/docs/index.html:241 +#: i2p2www/pages/site/docs/index.html:246 msgid "Old roadmap" msgstr "" -#: i2p2www/pages/site/docs/index.html:241 -#: i2p2www/pages/site/docs/index.html:243 +#: i2p2www/pages/site/docs/index.html:246 +#: i2p2www/pages/site/docs/index.html:248 msgid "not current" msgstr "" -#: i2p2www/pages/site/docs/index.html:243 +#: i2p2www/pages/site/docs/index.html:248 msgid "To Do List" msgstr "" @@ -786,7 +798,7 @@ msgid "" msgstr "" #: i2p2www/pages/site/docs/naming.html:183 -#: i2p2www/pages/site/docs/spec/configuration.html:170 +#: i2p2www/pages/site/docs/spec/configuration.html:184 msgid "Addressbook" msgstr "" @@ -1156,7 +1168,7 @@ msgid "" msgstr "" #: i2p2www/pages/site/docs/plugins.html:2 -#: i2p2www/pages/site/docs/spec/configuration.html:138 +#: i2p2www/pages/site/docs/spec/configuration.html:152 msgid "Plugins" msgstr "" @@ -2532,15 +2544,19 @@ msgid "" msgstr "" #: i2p2www/pages/site/docs/api/i2ptunnel.html:54 +msgid "Configuration" +msgstr "" + +#: i2p2www/pages/site/docs/api/i2ptunnel.html:58 msgid "Client Modes" msgstr "" -#: i2p2www/pages/site/docs/api/i2ptunnel.html:55 -#: i2p2www/pages/site/docs/api/i2ptunnel.html:137 +#: i2p2www/pages/site/docs/api/i2ptunnel.html:59 +#: i2p2www/pages/site/docs/api/i2ptunnel.html:141 msgid "Standard" msgstr "" -#: i2p2www/pages/site/docs/api/i2ptunnel.html:56 +#: 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" @@ -2548,7 +2564,7 @@ msgid "" " list of destinations." msgstr "" -#: i2p2www/pages/site/docs/api/i2ptunnel.html:62 +#: i2p2www/pages/site/docs/api/i2ptunnel.html:66 msgid "" "A HTTP-client tunnel. The tunnel connects to the destination specified by" " the URL\n" @@ -2556,34 +2572,34 @@ msgid "" "provided. Strips HTTP connections of the following headers:" msgstr "" -#: i2p2www/pages/site/docs/api/i2ptunnel.html:67 +#: 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 "" -#: i2p2www/pages/site/docs/api/i2ptunnel.html:75 +#: 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 "" -#: i2p2www/pages/site/docs/api/i2ptunnel.html:82 +#: 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 "" -#: i2p2www/pages/site/docs/api/i2ptunnel.html:86 +#: i2p2www/pages/site/docs/api/i2ptunnel.html:90 msgid "Outproxy:" msgstr "" -#: i2p2www/pages/site/docs/api/i2ptunnel.html:87 +#: i2p2www/pages/site/docs/api/i2ptunnel.html:91 msgid "Internal I2P use:" msgstr "" -#: i2p2www/pages/site/docs/api/i2ptunnel.html:92 +#: i2p2www/pages/site/docs/api/i2ptunnel.html:96 msgid "" "Creates a connection to a random IRC server specified by the comma " "seprated (\", \") \n" @@ -2591,43 +2607,43 @@ msgid "" "allowed due to anonymity concerns." msgstr "" -#: i2p2www/pages/site/docs/api/i2ptunnel.html:96 +#: i2p2www/pages/site/docs/api/i2ptunnel.html:100 msgid "Whitelist:" msgstr "" -#: i2p2www/pages/site/docs/api/i2ptunnel.html:111 +#: i2p2www/pages/site/docs/api/i2ptunnel.html:115 msgid "Enables using the I2P router as a SOCKS proxy." msgstr "" -#: i2p2www/pages/site/docs/api/i2ptunnel.html:116 +#: 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" "IRC client mode." msgstr "" -#: i2p2www/pages/site/docs/api/i2ptunnel.html:122 +#: 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 "" -#: i2p2www/pages/site/docs/api/i2ptunnel.html:128 +#: 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" "subscribe to a streamr server tunnel." msgstr "" -#: i2p2www/pages/site/docs/api/i2ptunnel.html:136 +#: i2p2www/pages/site/docs/api/i2ptunnel.html:140 msgid "Server Modes" msgstr "" -#: i2p2www/pages/site/docs/api/i2ptunnel.html:138 +#: i2p2www/pages/site/docs/api/i2ptunnel.html:142 msgid "Creates a destination to a local ip:port with an open TCP port." msgstr "" -#: i2p2www/pages/site/docs/api/i2ptunnel.html:143 +#: 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" @@ -2635,7 +2651,7 @@ msgid "" " such a request." msgstr "" -#: i2p2www/pages/site/docs/api/i2ptunnel.html:149 +#: 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" @@ -2644,14 +2660,14 @@ msgid "" "requests, or loopback-testing an eepsite as a diagnostic tool." msgstr "" -#: i2p2www/pages/site/docs/api/i2ptunnel.html:156 +#: i2p2www/pages/site/docs/api/i2ptunnel.html:160 msgid "" "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:162 +#: 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." @@ -3444,8 +3460,8 @@ msgstr "" #: i2p2www/pages/site/docs/how/tunnel-routing.html:255 #: i2p2www/pages/site/docs/protocol/i2cp.html:687 #: i2p2www/pages/site/docs/protocol/i2np.html:226 -#: i2p2www/pages/site/docs/spec/updates.html:438 -#: i2p2www/pages/site/docs/transport/ntcp.html:535 +#: i2p2www/pages/site/docs/spec/updates.html:488 +#: i2p2www/pages/site/docs/transport/ntcp.html:544 #: i2p2www/pages/site/docs/transport/ssu.html:554 #: i2p2www/pages/site/docs/tunnels/implementation.html:506 msgid "Future Work" @@ -3996,6 +4012,14 @@ 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)." +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" "If done wrong, it could cause real harm to our network.\n" @@ -4004,11 +4028,11 @@ msgid "" "This page discusses some general guidelines." msgstr "" -#: i2p2www/pages/site/docs/applications/embedding.html:18 +#: i2p2www/pages/site/docs/applications/embedding.html:23 msgid "Talk to us" msgstr "" -#: i2p2www/pages/site/docs/applications/embedding.html:19 +#: 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" @@ -4016,11 +4040,11 @@ msgid "" "everyone." msgstr "" -#: i2p2www/pages/site/docs/applications/embedding.html:25 +#: i2p2www/pages/site/docs/applications/embedding.html:30 msgid "Choose your router wisely" msgstr "" -#: i2p2www/pages/site/docs/applications/embedding.html:26 +#: 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" @@ -4030,19 +4054,19 @@ msgid "" "Some of the following only applies to the Java router." msgstr "" -#: i2p2www/pages/site/docs/applications/embedding.html:34 +#: i2p2www/pages/site/docs/applications/embedding.html:39 msgid "Licensing" msgstr "" -#: i2p2www/pages/site/docs/applications/embedding.html:35 +#: i2p2www/pages/site/docs/applications/embedding.html:40 msgid "Ensure you meet the license requirements of the software you are bundling." msgstr "" -#: i2p2www/pages/site/docs/applications/embedding.html:40 +#: i2p2www/pages/site/docs/applications/embedding.html:45 msgid "Verify default configuration" msgstr "" -#: i2p2www/pages/site/docs/applications/embedding.html:41 +#: i2p2www/pages/site/docs/applications/embedding.html:46 msgid "" "A correct default configuration is crucial. Most users will not change " "the defaults.\n" @@ -4051,7 +4075,7 @@ msgid "" "Override the router defaults if necessary." msgstr "" -#: i2p2www/pages/site/docs/applications/embedding.html:46 +#: i2p2www/pages/site/docs/applications/embedding.html:51 msgid "" "Some important defaults to review: Max bandwidth, tunnel quantity and " "length, max participating tunnels.\n" @@ -4059,7 +4083,7 @@ msgid "" "your app." msgstr "" -#: i2p2www/pages/site/docs/applications/embedding.html:50 +#: i2p2www/pages/site/docs/applications/embedding.html:55 msgid "" "Configure enough bandwidth and tunnels to allow your users to contribute " "to the network.\n" @@ -4069,11 +4093,11 @@ msgid "" "example." msgstr "" -#: i2p2www/pages/site/docs/applications/embedding.html:57 +#: i2p2www/pages/site/docs/applications/embedding.html:62 msgid "Participating Traffic Considerations" msgstr "" -#: i2p2www/pages/site/docs/applications/embedding.html:58 +#: 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, " @@ -4085,14 +4109,14 @@ msgid "" "tunnels." msgstr "" -#: i2p2www/pages/site/docs/applications/embedding.html:65 +#: 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" "which is helped tremendously by others building tunnels through you." msgstr "" -#: i2p2www/pages/site/docs/applications/embedding.html:69 +#: i2p2www/pages/site/docs/applications/embedding.html:74 msgid "" "Secondly, over 90% of the routers in the current network allow " "participating traffic.\n" @@ -4104,13 +4128,13 @@ msgid "" " people to enable relaying." msgstr "" -#: i2p2www/pages/site/docs/applications/embedding.html:76 +#: i2p2www/pages/site/docs/applications/embedding.html:81 msgid "" "Thirdly, participating traffic is cover traffic that helps your users' " "anonymity." msgstr "" -#: i2p2www/pages/site/docs/applications/embedding.html:79 +#: i2p2www/pages/site/docs/applications/embedding.html:84 msgid "" "We strongly discourage you from disabling participating traffic by " "default.\n" @@ -4118,11 +4142,11 @@ msgid "" "the network." msgstr "" -#: i2p2www/pages/site/docs/applications/embedding.html:85 +#: i2p2www/pages/site/docs/applications/embedding.html:90 msgid "Persistence" msgstr "" -#: i2p2www/pages/site/docs/applications/embedding.html:86 +#: 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" @@ -4132,11 +4156,11 @@ msgid "" "performance." msgstr "" -#: i2p2www/pages/site/docs/applications/embedding.html:94 +#: i2p2www/pages/site/docs/applications/embedding.html:99 msgid "Configurability" msgstr "" -#: i2p2www/pages/site/docs/applications/embedding.html:95 +#: i2p2www/pages/site/docs/applications/embedding.html:100 msgid "" "Give your users a way to change the configuration of the important " "settings.\n" @@ -4146,11 +4170,11 @@ msgid "" "IP/port may be helpful." msgstr "" -#: i2p2www/pages/site/docs/applications/embedding.html:103 +#: i2p2www/pages/site/docs/applications/embedding.html:108 msgid "Floodfill Considerations" msgstr "" -#: i2p2www/pages/site/docs/applications/embedding.html:104 +#: 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" @@ -4161,11 +4185,11 @@ msgid "" "It also depends on the typical uptime for your application." msgstr "" -#: i2p2www/pages/site/docs/applications/embedding.html:114 +#: i2p2www/pages/site/docs/applications/embedding.html:119 msgid "Reseeding" msgstr "" -#: i2p2www/pages/site/docs/applications/embedding.html:115 +#: 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 " @@ -4173,11 +4197,11 @@ msgid "" "Be aware of possible blocking by hostile governments." msgstr "" -#: i2p2www/pages/site/docs/applications/embedding.html:124 +#: i2p2www/pages/site/docs/applications/embedding.html:129 msgid "Reduce Network Resource Usage" msgstr "" -#: i2p2www/pages/site/docs/applications/embedding.html:125 +#: 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" @@ -4187,11 +4211,11 @@ msgid "" "tunnel, even in the presence of some background DHT activity." msgstr "" -#: i2p2www/pages/site/docs/applications/embedding.html:133 +#: i2p2www/pages/site/docs/applications/embedding.html:138 msgid "Updatability" msgstr "" -#: i2p2www/pages/site/docs/applications/embedding.html:134 +#: 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" @@ -4206,11 +4230,11 @@ msgid "" "which you presumably are not bundling." msgstr "" -#: i2p2www/pages/site/docs/applications/embedding.html:145 +#: i2p2www/pages/site/docs/applications/embedding.html:150 msgid "Rollout" msgstr "" -#: i2p2www/pages/site/docs/applications/embedding.html:146 +#: 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 " @@ -4226,11 +4250,11 @@ msgid "" "checklist is." msgstr "" -#: i2p2www/pages/site/docs/applications/embedding.html:158 +#: i2p2www/pages/site/docs/applications/embedding.html:163 msgid "Design for and Encourage Long Uptimes" msgstr "" -#: i2p2www/pages/site/docs/applications/embedding.html:159 +#: 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 " @@ -4239,53 +4263,53 @@ msgid "" "solution." msgstr "" -#: i2p2www/pages/site/docs/applications/embedding.html:167 +#: i2p2www/pages/site/docs/applications/embedding.html:172 msgid "Show Status" msgstr "" -#: i2p2www/pages/site/docs/applications/embedding.html:168 +#: i2p2www/pages/site/docs/applications/embedding.html:173 msgid "" "Provide some indication to the user that the application tunnels are " "ready. Encourage patience." msgstr "" -#: i2p2www/pages/site/docs/applications/embedding.html:173 +#: i2p2www/pages/site/docs/applications/embedding.html:178 msgid "Graceful Shutdown" msgstr "" -#: i2p2www/pages/site/docs/applications/embedding.html:174 +#: 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 "" -#: i2p2www/pages/site/docs/applications/embedding.html:180 +#: i2p2www/pages/site/docs/applications/embedding.html:185 msgid "Education and Donation" msgstr "" -#: i2p2www/pages/site/docs/applications/embedding.html:181 +#: 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 "" -#: i2p2www/pages/site/docs/applications/embedding.html:187 +#: i2p2www/pages/site/docs/applications/embedding.html:192 msgid "External Router Option" msgstr "" -#: i2p2www/pages/site/docs/applications/embedding.html:188 +#: 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 "" -#: i2p2www/pages/site/docs/applications/embedding.html:195 +#: i2p2www/pages/site/docs/applications/embedding.html:200 msgid "Use of other Common Services" msgstr "" -#: i2p2www/pages/site/docs/applications/embedding.html:196 +#: 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" @@ -4293,11 +4317,11 @@ msgid "" "and talk to the people who are running them to make sure it's ok." msgstr "" -#: i2p2www/pages/site/docs/applications/embedding.html:204 +#: i2p2www/pages/site/docs/applications/embedding.html:209 msgid "Time / NTP Issues" msgstr "" -#: i2p2www/pages/site/docs/applications/embedding.html:205 +#: 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. " @@ -4306,11 +4330,11 @@ msgid "" "clock is correct." msgstr "" -#: i2p2www/pages/site/docs/applications/embedding.html:213 +#: i2p2www/pages/site/docs/applications/embedding.html:218 msgid "Choose What and How you Bundle" msgstr "" -#: i2p2www/pages/site/docs/applications/embedding.html:214 +#: 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" @@ -4328,11 +4352,19 @@ msgid "" "and i2psnark, for example." msgstr "" -#: i2p2www/pages/site/docs/applications/embedding.html:228 +#: i2p2www/pages/site/docs/applications/embedding.html:233 +msgid "You may also wish to bundle a hosts.txt file." +msgstr "" + +#: i2p2www/pages/site/docs/applications/embedding.html:236 +msgid "Be sure to specify a Java 6 bootclasspath if compiling with Java 8." +msgstr "" + +#: i2p2www/pages/site/docs/applications/embedding.html:244 msgid "Datagram (DHT) considerations" msgstr "" -#: i2p2www/pages/site/docs/applications/embedding.html:229 +#: 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 " @@ -4348,32 +4380,32 @@ msgid "" "have several." msgstr "" -#: i2p2www/pages/site/docs/applications/embedding.html:242 +#: i2p2www/pages/site/docs/applications/embedding.html:258 msgid "Comarketing" msgstr "" -#: i2p2www/pages/site/docs/applications/embedding.html:243 +#: 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 "" -#: i2p2www/pages/site/docs/applications/embedding.html:249 +#: i2p2www/pages/site/docs/applications/embedding.html:265 msgid "Malware" msgstr "" -#: i2p2www/pages/site/docs/applications/embedding.html:250 +#: i2p2www/pages/site/docs/applications/embedding.html:266 msgid "" "Please don't use I2P for evil.\n" "It could cause great harm both to our network and our reputation." msgstr "" -#: i2p2www/pages/site/docs/applications/embedding.html:256 +#: i2p2www/pages/site/docs/applications/embedding.html:272 msgid "Join Us" msgstr "" -#: i2p2www/pages/site/docs/applications/embedding.html:257 +#: 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" @@ -4381,11 +4413,11 @@ msgid "" "We can help get you users, testers, translators, or even coders." msgstr "" -#: i2p2www/pages/site/docs/applications/embedding.html:265 +#: i2p2www/pages/site/docs/applications/embedding.html:281 msgid "Application Examples" msgstr "" -#: i2p2www/pages/site/docs/applications/embedding.html:266 +#: 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" @@ -4395,17 +4427,17 @@ msgid "" " and Monero." msgstr "" -#: i2p2www/pages/site/docs/applications/embedding.html:274 +#: i2p2www/pages/site/docs/applications/embedding.html:290 msgid "Code Example" msgstr "" -#: i2p2www/pages/site/docs/applications/embedding.html:275 +#: i2p2www/pages/site/docs/applications/embedding.html:291 msgid "" "None of the above actually tells you how to write your code to\n" "bundle the Java router, so following is a brief example." msgstr "" -#: i2p2www/pages/site/docs/applications/embedding.html:290 +#: 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" @@ -7269,7 +7301,6 @@ msgid "The Network Database" msgstr "" #: i2p2www/pages/site/docs/how/network-database.html:3 -#: i2p2www/pages/site/docs/transport/ntcp.html:3 msgid "October 2014" msgstr "" @@ -14523,10 +14554,6 @@ msgstr "" msgid "Configuration File Specification" msgstr "" -#: i2p2www/pages/site/docs/spec/configuration.html:3 -msgid "January 2014" -msgstr "" - #: i2p2www/pages/site/docs/spec/configuration.html:7 msgid "" "This page provides a general specification of I2P configuration files,\n" @@ -14635,65 +14662,66 @@ msgid "Configured via /configlogging in the router console." msgstr "" #: i2p2www/pages/site/docs/spec/configuration.html:112 -#: i2p2www/pages/site/docs/spec/configuration.html:142 -#: i2p2www/pages/site/docs/spec/configuration.html:154 +#: i2p2www/pages/site/docs/spec/configuration.html:156 +#: i2p2www/pages/site/docs/spec/configuration.html:168 +#: i2p2www/pages/site/docs/spec/configuration.html:198 msgid "Properties are as follows:" msgstr "" -#: i2p2www/pages/site/docs/spec/configuration.html:133 +#: i2p2www/pages/site/docs/spec/configuration.html:147 msgid "Individual Plugin" msgstr "" -#: i2p2www/pages/site/docs/spec/configuration.html:134 +#: i2p2www/pages/site/docs/spec/configuration.html:148 #, python-format msgid "See the plugin specification." msgstr "" -#: i2p2www/pages/site/docs/spec/configuration.html:139 +#: i2p2www/pages/site/docs/spec/configuration.html:153 msgid "Enable/disable for each installed plugin." msgstr "" -#: i2p2www/pages/site/docs/spec/configuration.html:150 +#: i2p2www/pages/site/docs/spec/configuration.html:164 msgid "Webapps" msgstr "" -#: i2p2www/pages/site/docs/spec/configuration.html:151 +#: i2p2www/pages/site/docs/spec/configuration.html:165 msgid "Enable/disable for each installed webapp." msgstr "" -#: i2p2www/pages/site/docs/spec/configuration.html:163 +#: i2p2www/pages/site/docs/spec/configuration.html:177 msgid "Router" msgstr "" -#: i2p2www/pages/site/docs/spec/configuration.html:164 +#: i2p2www/pages/site/docs/spec/configuration.html:178 msgid "Configured via /configadvanced in the router console." msgstr "" -#: i2p2www/pages/site/docs/spec/configuration.html:168 +#: i2p2www/pages/site/docs/spec/configuration.html:182 msgid "Applications" msgstr "" -#: i2p2www/pages/site/docs/spec/configuration.html:171 +#: i2p2www/pages/site/docs/spec/configuration.html:185 msgid "See documentation in SusiDNS." msgstr "" -#: i2p2www/pages/site/docs/spec/configuration.html:176 +#: i2p2www/pages/site/docs/spec/configuration.html:190 msgid "Configured via the application gui." msgstr "" -#: i2p2www/pages/site/docs/spec/configuration.html:181 +#: i2p2www/pages/site/docs/spec/configuration.html:195 msgid "Configured via the /i2ptunnel application in the router console." msgstr "" -#: i2p2www/pages/site/docs/spec/configuration.html:185 +#: i2p2www/pages/site/docs/spec/configuration.html:364 msgid "Router Console" msgstr "" -#: i2p2www/pages/site/docs/spec/configuration.html:186 +#: i2p2www/pages/site/docs/spec/configuration.html:365 msgid "The router console uses the router.config file." msgstr "" -#: i2p2www/pages/site/docs/spec/configuration.html:191 +#: i2p2www/pages/site/docs/spec/configuration.html:370 msgid "See post on zzz.i2p." msgstr "" @@ -15088,6 +15116,7 @@ msgstr "" #: i2p2www/pages/site/docs/spec/updates.html:204 #: i2p2www/pages/site/docs/spec/updates.html:313 +#: i2p2www/pages/site/docs/spec/updates.html:365 msgid "Goals:" msgstr "" @@ -15110,7 +15139,8 @@ msgid "One-pass signature verification and file extraction" msgstr "" #: i2p2www/pages/site/docs/spec/updates.html:222 -#: i2p2www/pages/site/docs/spec/updates.html:336 +#: i2p2www/pages/site/docs/spec/updates.html:328 +#: i2p2www/pages/site/docs/spec/updates.html:388 msgid "Specification:" msgstr "" @@ -15119,40 +15149,79 @@ msgid "All unused fields must be set to 0 for compatibility with future versions msgstr "" #: i2p2www/pages/site/docs/spec/updates.html:308 -msgid "SU3 News File Specification" +msgid "SU3 Reseed File Specification" msgstr "" #: i2p2www/pages/site/docs/spec/updates.html:309 -msgid "As of 0.9.17, the news is delivered in an \"su3\" file format." +msgid "As of 0.9.14, reseed data is delivered in an \"su3\" file format." msgstr "" #: i2p2www/pages/site/docs/spec/updates.html:316 -msgid "Signed news with strong signatures and trusted certificates" +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 "" -#: i2p2www/pages/site/docs/spec/updates.html:319 +#: 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 "" -#: i2p2www/pages/site/docs/spec/updates.html:322 -msgid "Standard XML format for use with standard parsers" -msgstr "" - -#: i2p2www/pages/site/docs/spec/updates.html:325 -msgid "Standard Atom format for use with standard feed readers and generators" -msgstr "" - -#: i2p2www/pages/site/docs/spec/updates.html:328 -msgid "Sanitization and verification of HTML before displaying on console" +#: i2p2www/pages/site/docs/spec/updates.html:323 +msgid "" +"Single compressed file to speed up reseeding, which was slow to fetch 200" +" files" msgstr "" #: i2p2www/pages/site/docs/spec/updates.html:331 +msgid "The file must be named \"i2pseeds.su3\"." +msgstr "" + +#: i2p2www/pages/site/docs/spec/updates.html:334 +msgid "" +"The file must be in the same directory as the router infos on the web " +"server." +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" +"and then fetch the individual router info files found in the links." +msgstr "" + +#: i2p2www/pages/site/docs/spec/updates.html:360 +msgid "SU3 News File Specification" +msgstr "" + +#: i2p2www/pages/site/docs/spec/updates.html:361 +msgid "As of 0.9.17, the news is delivered in an \"su3\" file format." +msgstr "" + +#: i2p2www/pages/site/docs/spec/updates.html:368 +msgid "Signed news with strong signatures and trusted certificates" +msgstr "" + +#: i2p2www/pages/site/docs/spec/updates.html:374 +msgid "Standard XML format for use with standard parsers" +msgstr "" + +#: i2p2www/pages/site/docs/spec/updates.html:377 +msgid "Standard Atom format for use with standard feed readers and generators" +msgstr "" + +#: i2p2www/pages/site/docs/spec/updates.html:380 +msgid "Sanitization and verification of HTML before displaying on console" +msgstr "" + +#: i2p2www/pages/site/docs/spec/updates.html:383 msgid "" "Suitable for easy implementation on Android and other platforms without " "an HTML console" msgstr "" -#: i2p2www/pages/site/docs/spec/updates.html:440 +#: 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" @@ -15745,7 +15814,7 @@ msgstr "" #: i2p2www/pages/site/docs/transport/ntcp.html:207 #: i2p2www/pages/site/docs/transport/ntcp.html:250 #: i2p2www/pages/site/docs/transport/ntcp.html:332 -#: i2p2www/pages/site/docs/transport/ntcp.html:428 +#: i2p2www/pages/site/docs/transport/ntcp.html:437 msgid "Size:" msgstr "" @@ -15763,7 +15832,7 @@ msgstr "" #: i2p2www/pages/site/docs/transport/ntcp.html:236 #: i2p2www/pages/site/docs/transport/ntcp.html:319 -#: i2p2www/pages/site/docs/transport/ntcp.html:397 +#: i2p2www/pages/site/docs/transport/ntcp.html:398 msgid "Notes:" msgstr "" @@ -15783,7 +15852,7 @@ msgstr "" #: i2p2www/pages/site/docs/transport/ntcp.html:252 #: i2p2www/pages/site/docs/transport/ntcp.html:334 -#: i2p2www/pages/site/docs/transport/ntcp.html:430 +#: i2p2www/pages/site/docs/transport/ntcp.html:439 msgid "Unencrypted Contents:" msgstr "" @@ -15807,7 +15876,7 @@ msgstr "" #: i2p2www/pages/site/docs/transport/ntcp.html:285 #: i2p2www/pages/site/docs/transport/ntcp.html:376 -#: i2p2www/pages/site/docs/transport/ntcp.html:457 +#: i2p2www/pages/site/docs/transport/ntcp.html:466 msgid "Encrypted Contents:" msgstr "" @@ -15844,7 +15913,7 @@ msgid "Alice's 387+ byte `RouterIdentity`" msgstr "" #: i2p2www/pages/site/docs/transport/ntcp.html:366 -#: i2p2www/pages/site/docs/transport/ntcp.html:452 +#: i2p2www/pages/site/docs/transport/ntcp.html:461 msgid "0-15 bytes random data" msgstr "" @@ -15865,31 +15934,31 @@ msgid "" "of message #1) as the IV" msgstr "" -#: i2p2www/pages/site/docs/transport/ntcp.html:399 +#: i2p2www/pages/site/docs/transport/ntcp.html:400 msgid "Bob verifies the signature, and on failure, drops the connection." msgstr "" -#: i2p2www/pages/site/docs/transport/ntcp.html:402 +#: i2p2www/pages/site/docs/transport/ntcp.html:403 msgid "" "Bob may drop the connection if the clock skew with Alice is too high as " "calculated using tsA." msgstr "" -#: i2p2www/pages/site/docs/transport/ntcp.html:405 +#: 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 "" -#: i2p2www/pages/site/docs/transport/ntcp.html:421 +#: i2p2www/pages/site/docs/transport/ntcp.html:430 msgid "Message 4 (Session Confirm B)" msgstr "" -#: i2p2www/pages/site/docs/transport/ntcp.html:422 +#: i2p2www/pages/site/docs/transport/ntcp.html:431 msgid "This is a signature of the critical data. Bob sends Alice:" msgstr "" -#: i2p2www/pages/site/docs/transport/ntcp.html:446 +#: i2p2www/pages/site/docs/transport/ntcp.html:455 msgid "" "the `Signature` of the following concatenated data:\n" " X, Y, Alice's `RouterIdentity`, tsA, tsB.\n" @@ -15897,7 +15966,7 @@ msgid "" "the `SigningPublicKey` in his `RouterIdentity`" msgstr "" -#: i2p2www/pages/site/docs/transport/ntcp.html:470 +#: i2p2www/pages/site/docs/transport/ntcp.html:479 #, python-format msgid "" "Data AES encrypted using the DH " @@ -15908,21 +15977,21 @@ msgid "" "signature types" msgstr "" -#: i2p2www/pages/site/docs/transport/ntcp.html:479 +#: i2p2www/pages/site/docs/transport/ntcp.html:488 msgid "Alice verifies the signature, and on failure, drops the connection." msgstr "" -#: i2p2www/pages/site/docs/transport/ntcp.html:482 +#: 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 "" -#: i2p2www/pages/site/docs/transport/ntcp.html:497 +#: i2p2www/pages/site/docs/transport/ntcp.html:506 msgid "After Establishment" msgstr "" -#: i2p2www/pages/site/docs/transport/ntcp.html:498 +#: i2p2www/pages/site/docs/transport/ntcp.html:507 msgid "" "The connection is established, and standard or time sync messages may be " "exchanged.\n" @@ -15934,11 +16003,11 @@ msgid "" " the next IV." msgstr "" -#: i2p2www/pages/site/docs/transport/ntcp.html:507 +#: i2p2www/pages/site/docs/transport/ntcp.html:516 msgid "Check Connection Message" msgstr "" -#: i2p2www/pages/site/docs/transport/ntcp.html:508 +#: i2p2www/pages/site/docs/transport/ntcp.html:517 msgid "" "Alternately, when Bob receives a connection, it could be a\n" "check connection (perhaps prompted by Bob asking for someone\n" @@ -15948,58 +16017,58 @@ msgid "" "A check info connection will receive 256 bytes containing:" msgstr "" -#: i2p2www/pages/site/docs/transport/ntcp.html:517 +#: i2p2www/pages/site/docs/transport/ntcp.html:526 msgid "32 bytes of uninterpreted, ignored data" msgstr "" -#: i2p2www/pages/site/docs/transport/ntcp.html:518 +#: i2p2www/pages/site/docs/transport/ntcp.html:527 msgid "1 byte size" msgstr "" -#: i2p2www/pages/site/docs/transport/ntcp.html:519 +#: 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 "" -#: i2p2www/pages/site/docs/transport/ntcp.html:520 +#: i2p2www/pages/site/docs/transport/ntcp.html:529 msgid "2 byte port number that the local router was reached on" msgstr "" -#: i2p2www/pages/site/docs/transport/ntcp.html:521 +#: i2p2www/pages/site/docs/transport/ntcp.html:530 msgid "" "4 byte i2p network time as known by the remote side (seconds since the " "epoch)" msgstr "" -#: i2p2www/pages/site/docs/transport/ntcp.html:522 +#: i2p2www/pages/site/docs/transport/ntcp.html:531 msgid "uninterpreted padding data, up to byte 223" msgstr "" -#: i2p2www/pages/site/docs/transport/ntcp.html:523 +#: 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 "" -#: i2p2www/pages/site/docs/transport/ntcp.html:526 +#: i2p2www/pages/site/docs/transport/ntcp.html:535 msgid "Check connection is completely disabled as of release 0.9.12." msgstr "" -#: i2p2www/pages/site/docs/transport/ntcp.html:530 +#: i2p2www/pages/site/docs/transport/ntcp.html:539 msgid "Discussion" msgstr "" -#: i2p2www/pages/site/docs/transport/ntcp.html:531 +#: i2p2www/pages/site/docs/transport/ntcp.html:540 #, python-format msgid "Now on the NTCP Discussion Page." msgstr "" -#: i2p2www/pages/site/docs/transport/ntcp.html:537 +#: i2p2www/pages/site/docs/transport/ntcp.html:546 msgid "The maximum message size should be increased to approximately 32 KB." msgstr "" -#: i2p2www/pages/site/docs/transport/ntcp.html:541 +#: 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" @@ -16010,13 +16079,13 @@ msgid "" "to create a limited number of message sizes." msgstr "" -#: i2p2www/pages/site/docs/transport/ntcp.html:549 +#: 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 "" -#: i2p2www/pages/site/docs/transport/ntcp.html:553 +#: 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?" diff --git a/pots/get-involved.pot b/pots/get-involved.pot index 9dd356ec..40797667 100644 --- a/pots/get-involved.pot +++ b/pots/get-involved.pot @@ -8,7 +8,7 @@ msgid "" msgstr "" "Project-Id-Version: I2P website\n" "Report-Msgid-Bugs-To: http://trac.i2p2.de\n" -"POT-Creation-Date: 2014-10-22 20:13+0000\n" +"POT-Creation-Date: 2014-11-27 12:12+0000\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language-Team: LANGUAGE \n" @@ -396,317 +396,52 @@ msgid "" msgstr "" #: i2p2www/pages/site/get-involved/todo.html:15 -#: i2p2www/pages/site/get-involved/todo.html:53 +#: i2p2www/pages/site/get-involved/todo.html:38 msgid "Core functionality" msgstr "" #: i2p2www/pages/site/get-involved/todo.html:15 -#: i2p2www/pages/site/get-involved/todo.html:27 -#: i2p2www/pages/site/get-involved/todo.html:51 +#: i2p2www/pages/site/get-involved/todo.html:21 +#: i2p2www/pages/site/get-involved/todo.html:36 msgid "link" msgstr "" #: i2p2www/pages/site/get-involved/todo.html:17 -#: i2p2www/pages/site/get-involved/todo.html:56 -msgid "NAT/Firewall bridging via 1-hop restricted routes" -msgstr "" - -#: i2p2www/pages/site/get-involved/todo.html:20 -#: i2p2www/pages/site/get-involved/todo.html:129 -msgid "High degree transport layer with UDP, NBIO, or NIO" -msgstr "" - -#: i2p2www/pages/site/get-involved/todo.html:23 -#: i2p2www/pages/site/get-involved/todo.html:217 +#: i2p2www/pages/site/get-involved/todo.html:41 msgid "NetworkDB and profile tuning and ejection policy for large nets" msgstr "" -#: i2p2www/pages/site/get-involved/todo.html:27 -#: i2p2www/pages/site/get-involved/todo.html:241 +#: i2p2www/pages/site/get-involved/todo.html:21 +#: i2p2www/pages/site/get-involved/todo.html:65 msgid "Security / anonymity" msgstr "" -#: i2p2www/pages/site/get-involved/todo.html:29 -#: i2p2www/pages/site/get-involved/todo.html:244 -msgid "" -"Per-hop tunnel id & new permuted TunnelVerificationStructure " -"encryption" -msgstr "" - -#: i2p2www/pages/site/get-involved/todo.html:32 -#: i2p2www/pages/site/get-involved/todo.html:294 -msgid "Strict ordering of participants within tunnels" -msgstr "" - -#: i2p2www/pages/site/get-involved/todo.html:35 -msgid "Randomly permuted tunnel lengths" -msgstr "" - -#: i2p2www/pages/site/get-involved/todo.html:38 -#: i2p2www/pages/site/get-involved/todo.html:356 +#: 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 "" -#: i2p2www/pages/site/get-involved/todo.html:41 -#: i2p2www/pages/site/get-involved/todo.html:375 +#: 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 "" -#: i2p2www/pages/site/get-involved/todo.html:44 -#: i2p2www/pages/site/get-involved/todo.html:404 +#: 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 "" -#: i2p2www/pages/site/get-involved/todo.html:47 -#: i2p2www/pages/site/get-involved/todo.html:441 +#: i2p2www/pages/site/get-involved/todo.html:32 +#: i2p2www/pages/site/get-involved/todo.html:153 msgid "Stop & go mix w/ garlics & tunnels" msgstr "" -#: i2p2www/pages/site/get-involved/todo.html:51 -#: i2p2www/pages/site/get-involved/todo.html:455 +#: i2p2www/pages/site/get-involved/todo.html:36 +#: i2p2www/pages/site/get-involved/todo.html:167 msgid "Performance" msgstr "" -#: i2p2www/pages/site/get-involved/todo.html:61 -msgid "Implemented in I2P 0.6.0.6" -msgstr "" - -#: i2p2www/pages/site/get-involved/todo.html:62 -msgid "" -"The functionality of allowing routers to fully participate within the " -"network \n" -"while behind firewalls and NATs that they do not control requires some " -"basic \n" -"restricted route operation (since those peers will not be able to receive" -" \n" -"inbound connections). To do this successfully, you consider peers one of" -" \n" -"two ways:" -msgstr "" - -#: i2p2www/pages/site/get-involved/todo.html:72 -msgid "" -"Peers who have reachable interfaces - these peers do not need to \n" -"do anything special" -msgstr "" - -#: i2p2www/pages/site/get-involved/todo.html:76 -msgid "" -"Peers who do not have reachable interfaces - these peers must " -"build \n" -"a tunnel pointing at them where the gateway is one of the peers they have" -" \n" -"established a connection with who has both a publicly reachable interface" -" \n" -"and who has agreed to serve as their 'introducer'." -msgstr "" - -#: i2p2www/pages/site/get-involved/todo.html:84 -msgid "" -"To do this, peers who have no IP address simply connect to a few peers, \n" -"build a tunnel through them, and publish a reference to those tunnels " -"within \n" -"their RouterInfo structure in the network database." -msgstr "" - -#: i2p2www/pages/site/get-involved/todo.html:89 -msgid "" -"When someone wants to contact any particular router, they first must get" -" \n" -"its RouterInfo from the network database, which will tell them whether " -"they \n" -"can connect directly (e.g. the peer has a publicly reachable interface) \n" -"or whether they need to contact them indirectly. Direct connections occur" -" \n" -"as normal, while indirect connections are done through one of the " -"published \n" -"tunnels." -msgstr "" - -#: i2p2www/pages/site/get-involved/todo.html:97 -msgid "" -"When a router just wants to get a message or two to a specific hidden " -"peer, \n" -"they can just use the indirect tunnel for sending the payload. However, \n" -"if the router wants to talk to the hidden peer often (for instance, as " -"part \n" -"of a tunnel), they will send a garlic routed message through the indirect" -" \n" -"tunnel to that hidden peer which unwraps to contain a message which " -"should \n" -"be sent to the originating router. That hidden peer then establishes an \n" -"outbound connection to the originating router and from then on, those two" -" \n" -"routers can talk to each other directly over that newly established " -"direct \n" -"connection." -msgstr "" - -#: i2p2www/pages/site/get-involved/todo.html:108 -msgid "" -"Of course, that only works if the originating peer can receive " -"connections \n" -"(they aren't also hidden). However, if the originating peer is hidden, " -"they \n" -"can simply direct the garlic routed message to come back to the " -"originating \n" -"peer's inbound tunnel." -msgstr "" - -#: i2p2www/pages/site/get-involved/todo.html:114 -msgid "" -"This is not meant to provide a way for a peer's IP address to be " -"concealed, \n" -"merely as a way to let people behind firewalls and NATs fully operate " -"within \n" -"the network. Concealing the peer's IP address adds a little more work, as" -" \n" -"described below." -msgstr "" - -#: i2p2www/pages/site/get-involved/todo.html:120 -msgid "" -"With this technique, any router can participate as any part of a tunnel." -" \n" -"For efficiency purposes, a hidden peer would be a bad choice for an " -"inbound \n" -"gateway, and within any given tunnel, two neighboring peers wouldn't want" -" \n" -"to be hidden. But that is not technically necessary." -msgstr "" - -#: i2p2www/pages/site/get-involved/todo.html:132 -msgid "Both UDP and NIO have been Implemented in I2P" -msgstr "" - -#: i2p2www/pages/site/get-involved/todo.html:133 -msgid "" -"Standard TCP communication in Java generally requires blocking socket \n" -"calls, and to keep a blocked socket from hanging the entire system, those" -" \n" -"blocking calls are done on their own threads. Our current TCP transport \n" -"is implemented in a naive fashion - for each peer we are talking to, we \n" -"have one thread reading and one thread writing. The reader thread simply" -" \n" -"loops a bunch of read() calls, building I2NP messages and adding them \n" -"to our internal inbound message queue, and the writer thread pulls " -"messages \n" -"off a per-connection outbound message queue and shoves the data through \n" -"write() calls." -msgstr "" - -#: i2p2www/pages/site/get-involved/todo.html:144 -msgid "" -"We do this fairly efficiently, from a CPU perspective - at any time, \n" -"almost all of these threads are sitting idle, blocked waiting for " -"something \n" -"to do. However, each thread consumes real resources (on older Linux " -"kernels, \n" -"for instance, each thread would often be implemented as a fork()'ed " -"process). \n" -"As the network grows, the number of peers each router will want to talk \n" -"with will increase (remember, I2P is fully connected, meaning that any \n" -"given peer should know how to get a message to any other peer, and " -"restricted \n" -"route support will probably not significantly reduce the number of " -"connections \n" -"necessary). This means that with a 100,000 router network, each router \n" -"will have up to 199,998 threads just to deal with the TCP connections!" -msgstr "" - -#: i2p2www/pages/site/get-involved/todo.html:156 -msgid "" -"Obviously, that just won't work. We need to use a transport layer that \n" -"can scale. In Java, we have two main camps:" -msgstr "" - -#: i2p2www/pages/site/get-involved/todo.html:161 -#, python-format -msgid "" -"Implemented in I2P 0.6 (\"SSU\") as documented elsewhere" -msgstr "" - -#: i2p2www/pages/site/get-involved/todo.html:164 -msgid "" -"Sending and receiving UDP datagrams is a connectionless operation - if \n" -"we are communicating with 100,000 peers, we simply stick the UDP packets" -" \n" -"in a queue and have a single thread pulling them off the queue and " -"shoving \n" -"them out the pipe (and to receive, have a single thread pulling in any \n" -"UDP packets received and adding them to an inbound queue)." -msgstr "" - -#: i2p2www/pages/site/get-involved/todo.html:171 -msgid "" -"However, moving to UDP means losing the benefits of TCP's ordering, " -"congestion \n" -"control, MTU discovery, etc. Implementing that code will take significant" -" \n" -"work, however I2P doesn't need it to be as strong as TCP. Specifically, \n" -"a while ago I was taking some measurements in the simulator and on the \n" -"live net, and the vast majority of messages transferred would fit easily" -" \n" -"within a single unfragmented UDP packet, and the largest of the messages" -" \n" -"would fit within 20-30 packets. As mule pointed out, TCP adds a " -"significant \n" -"overhead when dealing with so many small packets, as the ACKs are within" -" \n" -"an order of magnitude in size. With UDP, we can optimize the transport \n" -"for both efficiency and resilience by taking into account I2P's " -"particular \n" -"needs." -msgstr "" - -#: i2p2www/pages/site/get-involved/todo.html:184 -msgid "It will be a lot of work though." -msgstr "" - -#: i2p2www/pages/site/get-involved/todo.html:187 -msgid "NIO or NBIO" -msgstr "" - -#: i2p2www/pages/site/get-involved/todo.html:188 -msgid "NIO Implemented in I2P 0.6.1.22 (\"NTCP\")" -msgstr "" - -#: i2p2www/pages/site/get-involved/todo.html:191 -msgid "" -"In Java 1.4, a set of \"New I/O\" packages was introduced, allowing Java" -" \n" -"developers to take advantage of the operating system's nonblocking IO \n" -"capabilities - allowing you to maintain a large number of concurrent IO \n" -"operations without requiring a separate thread for each. There is much \n" -"promise with this approach, as we can scalable handle a large number of \n" -"concurrent connections and we don't have to write a mini-TCP stack with \n" -"UDP. However, the NIO packages have not proven themselves to be battle-" -"ready, \n" -"as the Freenet developer's found. In addition, requiring NIO support " -"would \n" -"mean we can't run on any of the open source JVMs like Kaffe, \n" -"as GNU/Classpath has only " -"limited \n" -"support for NIO. (note: this may not be the case anymore, as there \n" -"has been some progress on Classpath's NIO, but it is an unknown " -"quantity)" -msgstr "" - -#: i2p2www/pages/site/get-involved/todo.html:205 -#, python-format -msgid "" -"Another alternative along the same lines is the Non" -" \n" -"Blocking I/O package - essentially a cleanroom NIO implementation \n" -"(written before NIO was around). It works by using some native OS code \n" -"to do the nonblocking IO, passing off events through Java. It seems to \n" -"be working with Kaffe, though there doesn't seem to be much development \n" -"activity on it lately (likely due to 1.4's NIO deployment)." -msgstr "" - -#: i2p2www/pages/site/get-involved/todo.html:220 +#: i2p2www/pages/site/get-involved/todo.html:44 msgid "" "Within the current network database and profile management " "implementation, \n" @@ -729,152 +464,14 @@ msgid "" "code yet, since we aren't going to need it for a while." msgstr "" -#: i2p2www/pages/site/get-involved/todo.html:235 +#: 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" "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:247 -#: i2p2www/pages/site/get-involved/todo.html:331 -#, python-format -msgid "" -"Addressed in I2P 0.5 as documented elsewhere" -msgstr "" - -#: i2p2www/pages/site/get-involved/todo.html:250 -msgid "" -"Right now, if Alice builds a four hop inbound tunnel starting at Elvis, \n" -"going to Dave, then to Charlie, then Bob, and finally Alice " -"(A<--B<--C<--D<--E), \n" -"all five of them will know they are participating in tunnel \"123\", as \n" -"the messages are tagged as such. What we want to do is give each hop " -"their \n" -"own unique tunnel hop ID - Charlie will receive messages on tunnel 234 \n" -"and forward them to tunnel 876 on Bob. The intent is to prevent Bob or \n" -"Charlie from knowing that they are in Alice's tunnel, as if each hop in \n" -"the tunnel had the same tunnel ID, collusion attacks aren't much work." -msgstr "" - -#: i2p2www/pages/site/get-involved/todo.html:260 -msgid "" -"Adding a unique tunnel ID per hop isn't hard, but by itself, " -"insufficient. \n" -"If Dave and Bob are under the control of the same attacker, they wouldn't" -" \n" -"be able to tell they are in the same tunnel due to the tunnel ID, but \n" -"would be able to tell by the message bodies and verification structures \n" -"by simply comparing them. To prevent that, the tunnel must use layered \n" -"encryption along the path, both on the payload of the tunneled message \n" -"and on the verification structure (used to prevent simple tagging " -"attacks). \n" -"This requires some simple modifications to the TunnelMessage, as well \n" -"as the inclusion of per-hop secret keys delivered during tunnel creation" -" \n" -"and given to the tunnel's gateway. We must fix a maximum tunnel length \n" -"(e.g. 16 hops) and instruct the gateway to encrypt the message to each \n" -"of the 16 delivered secret keys, in reverse order, and to encrypt the \n" -"signature of the hash of the (encrypted) payload at each step. The " -"gateway \n" -"then sends that 16-step encrypted message, along with a 16-step and " -"16-wide \n" -"encrypted mapping to the first hop, which then decrypts the mapping and \n" -"the payload with their secret key, looking in the 16-wide mapping for \n" -"the entry associated with their own hop (keyed by the per-hop tunnel ID)" -" \n" -"and verifying the payload by checking it against the associated signed \n" -"hash." -msgstr "" - -#: i2p2www/pages/site/get-involved/todo.html:281 -msgid "" -"The tunnel gateway does still have more information than the other peers" -" \n" -"in the tunnel, and compromising both the gateway and a tunnel participant" -" \n" -"would allow those peers to collude, exposing the fact that they are both" -" \n" -"in the same tunnel. In addition, neighboring peers know that they are \n" -"in the same tunnel anyway, as they know who they send the message to (and" -" \n" -"with IP-based transports without restricted routes, they know who they \n" -"got it from). However, the above two techniques significantly increase \n" -"the cost of gaining meaningful samples when dealing with longer tunnels." -msgstr "" - -#: i2p2www/pages/site/get-involved/todo.html:297 -msgid "Implemented in release 0.6.2" -msgstr "" - -#: i2p2www/pages/site/get-involved/todo.html:300 -#, python-format -msgid "" -"As Connelly proposed to deal with the\n" -"predecessor attack (2008\n" -"update), keeping the order of peers within our tunnels consistent \n" -"(aka whenever Alice creates a tunnel with both Bob and Charlie in it, \n" -"Bob's next hop is always Charlie), we address the issue as Bob doesn't \n" -"get to substantially sample Alice's peer selection group. We may even \n" -"want to explicitly allow Bob to participate in Alice's tunnels in only \n" -"one way - receiving a message from Dave and sending it to Charlie - and \n" -"if any of those peers are not available to participate in the tunnel (due" -" \n" -"to overload, network disconnection, etc), avoid asking Bob to participate" -" \n" -"in any tunnels until they are back online." -msgstr "" - -#: i2p2www/pages/site/get-involved/todo.html:315 -msgid "" -"More analysis is necessary for revising the tunnel creation - at the \n" -"moment, we simply select and order randomly within the peer's top tier \n" -"of peers (ones with fast + high capacity)." -msgstr "" - -#: i2p2www/pages/site/get-involved/todo.html:320 -msgid "" -"Adding a strict ordering to peers in a tunnel also improves the anonymity" -" \n" -"of peers with 0-hop tunnels, as otherwise the fact that a peer's gateway" -" \n" -"is always the same would be particularly damning. However, peers with \n" -"0-hop tunnels may want to periodically use a 1-hop tunnel to simulate \n" -"the failure of a normally reliable gateway peer (so every MTBF*(tunnel \n" -"duration) minutes, use a 1-hop tunnel)." -msgstr "" - -#: i2p2www/pages/site/get-involved/todo.html:337 -msgid "" -"Without tunnel length permutation, if someone were to somehow detect that" -" \n" -"a destination had a particular number of hops, it might be able to use " -"that \n" -"information to identify the router the destination is located on, per the" -" \n" -"predecessor attack. For instance, if everyone has 2-hop tunnels, if Bob \n" -"receives a tunnel message from Charlie and forwards it to Alice, Bob " -"knows \n" -"Alice is the final router in the tunnel. If Bob were to identify what " -"destination \n" -"that tunnel served (by means of colluding with the gateway and harvesting" -" \n" -"the network database for all of the LeaseSets), he would know the router" -" \n" -"on which that destination is located (and without restricted routes, that" -" \n" -"would mean what IP address the destination is on)." -msgstr "" - -#: i2p2www/pages/site/get-involved/todo.html:349 -msgid "" -"It is to counter user behavior that tunnel lengths should be permuted, \n" -"using algorithms based on the length requested (for example, the 1/MTBF \n" -"length change for 0-hop tunnels outlined above)." -msgstr "" - -#: i2p2www/pages/site/get-involved/todo.html:359 +#: i2p2www/pages/site/get-involved/todo.html:71 msgid "" "The restricted route functionality described before was simply a " "functional \n" @@ -896,7 +493,7 @@ msgid "" "to forward it as requested." msgstr "" -#: i2p2www/pages/site/get-involved/todo.html:378 +#: i2p2www/pages/site/get-involved/todo.html:90 #, python-format msgid "" "Within the network, we will want some way to deter people from consuming" @@ -910,7 +507,7 @@ msgid "" "to make certain requests \"expensive\"." msgstr "" -#: i2p2www/pages/site/get-involved/todo.html:386 +#: 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 " @@ -928,7 +525,7 @@ msgid "" "with few resources." msgstr "" -#: i2p2www/pages/site/get-involved/todo.html:397 +#: 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" @@ -936,7 +533,7 @@ msgid "" "appropriate." msgstr "" -#: i2p2www/pages/site/get-involved/todo.html:407 +#: i2p2www/pages/site/get-involved/todo.html:119 #, python-format msgid "" "To powerful passive external observers as well as large colluding " @@ -957,7 +554,7 @@ msgid "" "tunnel mixing strategies." msgstr "" -#: i2p2www/pages/site/get-involved/todo.html:420 +#: 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" @@ -975,7 +572,7 @@ msgid "" "available." msgstr "" -#: i2p2www/pages/site/get-involved/todo.html:433 +#: i2p2www/pages/site/get-involved/todo.html:145 msgid "" "In addition, we may want to implement code to dynamically reroute tunnels" " \n" @@ -985,7 +582,7 @@ msgid "" "with instructions to redefine the next-hop in the tunnel." msgstr "" -#: i2p2www/pages/site/get-involved/todo.html:444 +#: 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" @@ -1000,7 +597,7 @@ msgid "" "clove exposed includes delay instructions." msgstr "" -#: i2p2www/pages/site/get-involved/todo.html:456 +#: i2p2www/pages/site/get-involved/todo.html:168 #, python-format msgid "" "Performance related improvements are listed on the\n"