i2p.i2p) has been set up to"
+" enable developers to easily set up two of the commonly-used IDEs for "
+"Java development: Eclipse and NetBeans."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/ides.html:10
+msgid ""
+"The main I2P development branches (i2p.i2p and branches from"
+" it) contain .project and .classpath Eclipse files, to enable the branch "
+"to be easily set up in Eclipse."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/ides.html:16
+msgid ""
+"Check out the I2P branch into some directory (e.g. "
+"$HOME/dev/i2p.i2p)."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/ides.html:20
+msgid ""
+"Open Eclipse and create a new Workspace, based in the directory that the "
+"I2P branch was checked out to."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/ides.html:24
+msgid ""
+"Select \"File - Import...\" and then under \"General\" select \"Existing "
+"Projects into Workspace\"."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/ides.html:28
+msgid ""
+"For \"Select root directory:\" choose the directory that the I2P branch "
+"was checked out to."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/ides.html:32
+msgid "If necessary, click \"Refresh\" to refresh the list of projects."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/ides.html:36
+msgid "Select every project in the list, and click \"Finish\"."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/ides.html:40
+msgid ""
+"Done! Your workspace should now contain all projects within the I2P "
+"branch, and their build dependencies should be correctly set up."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/ides.html:48
+msgid ""
+"The main I2P development branches (i2p.i2p and branches from"
+" it) contain NetBeans project files."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:2
+msgid "Monotone"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:4
+msgid "Monotone Guide"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:9
+msgid "Operating a Monotone client"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:11
+#: i2p2www/pages/site/get-involved/guides/monotone.html:63
+msgid "Generating Monotone keys"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:12
+msgid "Trust and initializing your repository"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:13
+#: i2p2www/pages/site/get-involved/guides/monotone.html:196
+msgid "Obtaining and deploying developers' keys"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:14
+#: i2p2www/pages/site/get-involved/guides/monotone.html:227
+msgid "Setting up trust evaluation hooks"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:15
+#: i2p2www/pages/site/get-involved/guides/monotone.html:268
+msgid ""
+"Pulling the i2p.i2p, i2p.www and "
+"i2p.syndie branches"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:16
+#: i2p2www/pages/site/get-involved/guides/monotone.html:308
+msgid "Verifying that trust evaluation works"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:17
+#: i2p2www/pages/site/get-involved/guides/monotone.html:357
+msgid "Checking out a working copy of the latest version"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:18
+#: i2p2www/pages/site/get-involved/guides/monotone.html:384
+msgid "Updating your working copy to the latest version"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:22
+#: i2p2www/pages/site/get-involved/guides/monotone.html:414
+msgid "Operating a Monotone Server"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:24
+msgid "Obtaining and deploying developers’ transport keys"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:25
+#: i2p2www/pages/site/get-involved/guides/monotone.html:424
+msgid "Granting push and pull access"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:26
+#: i2p2www/pages/site/get-involved/guides/monotone.html:469
+msgid "Running Monotone in server mode"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:27
+#: i2p2www/pages/site/get-involved/guides/monotone.html:494
+msgid "Differences under Debian GNU/Linux"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:34
+#, python-format
+msgid ""
+"This is a revised version of Complication's original\n"
+" guide detailing the use of Monotone in I2P development.\n"
+" For basic instructions see the quick-start "
+"guide."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:42
+#, python-format
+msgid ""
+"I2P has a distributed development model. The source code is replicated "
+"across\n"
+" independently administered Monotone (\"MTN\") repositories.\n"
+" Developers with commit rights are able to push their changes to the "
+"repository\n"
+" (a license agreement needs to be "
+"signed\n"
+" before commit rights are granted)."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:52
+msgid ""
+"Some of Monotone's noteworthy qualities are: distributed\n"
+" version control, cryptographic authentication, access control, its "
+"small size, having few\n"
+" dependencies, storage of projects in a compressed SQLite database file,"
+" and\n"
+" having the ability to resume interrupted synchronization attempts."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:61
+msgid "Operating a Monotone Client"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:66
+msgid ""
+"A transport key grants you the ability to push your changes to a Monotone"
+" repository server.\n"
+" In order to commit code into Monotone (in essence signing your code), a"
+" commit key is also needed.\n"
+" None of the public Monotone servers on I2P currently require a key in "
+"order to read (or pull) the source code."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:74
+msgid ""
+"Without a transport key, one cannot:\n"
+" $HOME/.monotone/keys in "
+"text files which\n"
+" are named identically to the keys. For example:"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:123
+msgid ""
+"To generate transport and commit keys, enter the following commands at a "
+"prompt:"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:133
+msgid ""
+"Monotone will prompt you for a password to protect your keys. You are "
+"very strongly encouraged to set a password\n"
+" for the commit key. Many users will leave an empty password for the "
+"transport key, especially those running a\n"
+" Monotone server."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:141
+msgid "Trust, and initializing your repository"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:145
+msgid ""
+"Monotone's security model helps to ensure that nobody can easily "
+"impersonate a developer without\n"
+" it being noticed. Since developers can make mistakes and become "
+"compromised,only manual review can\n"
+" ensure quality of code. Monotone's trust model will ensure that you "
+"read the right diffs. It does\n"
+" not replace reading diffs."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:155
+msgid ""
+"A Monotone repository is a single file (a compressed SQLite database) "
+"which contains all of the project's source code and history."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:161
+msgid ""
+"After importing the "
+"developers' keys into Monotone and\n"
+" setting up trust "
+"evaluation hooks,\n"
+" Monotone will prevent untrusted code from being checked out into your "
+"workspace.\n"
+" There are commands available to clean untrusted code from your "
+"workspace but in practice they've not been\n"
+" needed due to the push access policies in place."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:171
+msgid ""
+"A repository can hold many branches. For example, our repository holds "
+"the\n"
+" following main branches:"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:176
+msgid "The I2P router and associated programs"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:177
+msgid "The I2P project website"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:178
+msgid "Syndie, a distributed forums tool"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:183
+msgid ""
+"By convention, the I2P Monotone repository is named i2p.mtn."
+" Before pulling\n"
+" source code from servers, a database for your repository will need to "
+"be initialized.\n"
+" To initialize your local repository, change into the directory that you"
+" want the\n"
+" i2p.mtn file and branch directories to be stored and issue"
+" the following\n"
+" command:"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:199
+msgid ""
+"Keys which developers use to commit code are essential for trust "
+"evaluation in\n"
+" Monotone. The other developers' transport keys are only required for "
+"Monotone server operators.\n"
+" "
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:206
+#, python-format
+msgid ""
+"Developers' commit keys are provided GPG-signed on another page."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:212
+#, python-format
+msgid ""
+"To import developers' keys after verifying their authenticity, copy all of the keys into a new\n"
+" file. Create this file (e.g. keys.txt) in the same "
+"directory where i2p.mtn is located. Import the keys with the"
+" command:"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:222
+msgid ""
+"Note: Never add keys to "
+"$HOME/.monotone/keys manually."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:230
+msgid ""
+"The default Monotone trust policy is way too lax for our requirements: "
+"every committer is trusted by default.\n"
+" That is not acceptable for I2P development."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:237
+msgid ""
+"Change into the directory $HOME/.monotone and open "
+"the file\n"
+" monotonerc with a text editor. Copy and paste the "
+"following two functions into this file:"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:246
+msgid ""
+"The first function determines an intersection between two sets, in our "
+"case a\n"
+" revision's signers and trusted signers."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:253
+msgid ""
+"The second function determines trust in a given revision, by calling the "
+"first\n"
+" function with \"signers\" and \"trusted\" as arguments. If the "
+"intersection is\n"
+" null, the revision is not trusted. If the intersection is not empty, "
+"the\n"
+" revision is trusted. Otherwise, the revision is not trusted."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:262
+msgid ""
+"More information about Trust Evauluation Hooks can be found in the official Monotone "
+"documentation."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:271
+msgid ""
+"Enter the directory where you initialized i2p.mtn. Depending "
+"on whether you\n"
+" want only I2P sources, or also sources for the I2P website and Syndie, "
+"you can\n"
+" perform the pull operation in different ways."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:279
+msgid "If you only want I2P sources:"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:288
+msgid "If you want all branches:"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:294
+msgid ""
+"If the transfer aborts before completing sucessfully, simply repeating "
+"the pull command will resume the transfer."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:300
+msgid ""
+"Pulling in the above examples is done anonymously by specifying an empty "
+"transport key.\n"
+" If everyone pulls anonymously it will be harder for an attacker who "
+"gains control of the server\n"
+" to selectively provide some people with tampered data."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:311
+msgid "To verify that trust evaluation works:"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:315
+msgid "Make a backup of your monotonerc file."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:316
+msgid ""
+"Modify monotonerc by setting the trusted_signers "
+"variable in the following way:"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:322
+msgid ""
+"With monotonerc configured as above, Monotone will no"
+" longer trust any committers. Confirm this by changing into the\n"
+"directory where i2p.mtn was created and attempt a checkout "
+"of the I2P branch:"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:332
+msgid ""
+"A directory named i2p.i2p should not appear. You "
+"should encounter many\n"
+" error messages like:"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:349
+msgid ""
+"If you are satisfied with results, restore the backup of\n"
+" monotonerc that was created above. If you didn't create a "
+"backup\n"
+" as advised, re-read Setting up trust evaluation hooks."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:360
+msgid ""
+"If you already have a branch checked out, skip to the next\n"
+" section."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:367
+msgid ""
+"Change into the directory where i2p.mtn is located. Over "
+"there issue:"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:376
+msgid ""
+"The checkout should complete without error messages and a directory named"
+"\n"
+" i2p.i2p should appear in the current directory. "
+"Congratulations! You have\n"
+" successfully checked out the latest I2P sources, ready to be compiled."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:387
+msgid ""
+"If you haven't done this already, pull fresh code from the server to your"
+" local\n"
+" Monotone repository. To accomplish this, change into the directory "
+"where\n"
+" i2p.mtn is located and issue:\n"
+" \n"
+" - $
mtn --db=\"i2p.mtn\" -k \"\" pull 127.0.0.1:8998 "
+"i2p.i2p \n"
+"
"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:398
+msgid "Now change into your i2p.i2p directory, and over there issue:"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:407
+msgid ""
+"As long as there were no errors…Congratulations! You have "
+"successfully updated to the latest I2P sources. They\n"
+" should be ready to compile."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:416
+msgid "Obtaining and deploying developers' transport keys"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:419
+msgid ""
+"As a server operator you may want to grant push access to certain "
+"developers."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:427
+msgid "By default the Monotone server denies all access."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:433
+msgid "To grant pull access to all clients, set the following in"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:445
+msgid ""
+"No one will not be able to push code to your server without permission "
+"being explicitly granted. To grant push access:"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:451
+msgid ""
+"Add the name of the user's transport key to\n"
+"$HOME/.monotone/write-permissions, such as\n"
+"\n"
+" zzz-transport@mail.i2p\n"
+" complication-transport@mail.i2p\n"
+"
/etc/monotone/read-permissions and\n"
+" /etc/monotone/write-permissions. You'll also need to edit\n"
+" /etc/default/monotone to enable monotone to start at boot "
+"or to\n"
+" customize the host, port, or database location."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-developers.html:2
+msgid "New Developer's Guide"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-developers.html:4
+msgid ""
+"\n"
+"So you want to start work on I2P? Great!\n"
+"Here's a quick guide to getting started\n"
+"on contributing to the website or the software, doing development or "
+"creating translations."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-developers.html:9
+#, python-format
+msgid ""
+"\n"
+"Not quite ready for coding?\n"
+"Try getting involved first."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-developers.html:16
+#: i2p2www/pages/site/get-involved/guides/new-developers.html:27
+msgid "Basic study"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-developers.html:17
+#: i2p2www/pages/site/get-involved/guides/new-developers.html:41
+msgid "Getting the I2P code"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-developers.html:18
+#: i2p2www/pages/site/get-involved/guides/new-developers.html:112
+msgid "Building I2P"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-developers.html:19
+#: i2p2www/pages/site/get-involved/guides/new-developers.html:133
+msgid "Development ideas"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-developers.html:20
+#: i2p2www/pages/site/get-involved/guides/new-developers.html:141
+msgid "Making the results available"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-developers.html:21
+#: i2p2www/pages/site/get-involved/guides/new-developers.html:162
+msgid "Get to know us!"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-developers.html:22
+#: i2p2www/pages/site/get-involved/guides/new-developers.html:168
+msgid "Translations"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-developers.html:23
+#: i2p2www/pages/site/get-involved/guides/new-developers.html:174
+msgid "Tools"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-developers.html:29
+msgid ""
+"Basic development on the I2P router or the embedded applications uses "
+"Java as the main development language.\n"
+"If you don't have experience with Java, you can always have a look at Thinking in Java."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-developers.html:33
+#, python-format
+msgid ""
+"Study the how intro,\n"
+"the other \"how\" documents,\n"
+"the tech intro,\n"
+"and associated documents.\n"
+"These will give you a good overview of how I2P is structured and what "
+"different things it does."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-developers.html:43
+msgid ""
+"For development on the i2p router or the embedded applications,\n"
+"get the monotone source repository installed - short instructions:"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-developers.html:48
+msgid ""
+"Install monotone.\n"
+"Monotone is a version control system.\n"
+"We use it because it allows us to keep track of who does what changes to "
+"the source code (and for a lot of complicated things, but 'keeping track "
+"of changes' is the basic idea)."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-developers.html:53
+msgid ""
+"Skim over the monotone tutorial,"
+" to make sure you understand the concepts."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-developers.html:57
+msgid ""
+"If you want to remain anonymous, you need to do an additional step, to "
+"set up a connection to a monotone server over I2P:"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-developers.html:60
+#, python-format
+msgid ""
+"Enable the i2ptunnel client tunnel on port "
+"8998 pointing to mtn.i2p2.i2p."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-developers.html:64
+msgid ""
+"Pick a directory where you want to put all your I2P files, and create a "
+"monotone database:"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-developers.html:67
+msgid ""
+"Define the trust list by creating ~/.monotone/monotonerc (or"
+" _MTN/monotonerc in the i2p.i2p workspace) with the "
+"following contents:"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-developers.html:72
+#, python-format
+msgid ""
+"Copy and paste the developer's commit keys "
+"into a new file (e.g. keys.txt) in the same directory\n"
+" that i2p.mtn is in. Import the keys into your database "
+"with
mtn -d i2p.mtn read < keys.txt
viewmtn."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-developers.html:108
+#, python-format
+msgid ""
+"A long explanation about using monotone is available on the monotone page."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-developers.html:114
+#, python-format
+msgid ""
+"To compile the code, you need the Sun Java Development Kit 6 or higher, "
+"or equivalent JDK\n"
+"(Sun JDK 6 strongly recommended) and\n"
+"Apache ant\n"
+"version 1.7.0 or higher.\n"
+"If you go are working on the main I2P code, you can go into the i2p.i2p "
+"directory and run 'ant' to see the build options."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-developers.html:122
+msgid ""
+"To build or work on console translations, you need\n"
+"the xgettext, msgfmt, and msgmerge tools from the\n"
+"GNU gettext package."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-developers.html:128
+#, python-format
+msgid ""
+"For development on new applications,\n"
+"see the application development guide."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-developers.html:134
+#, python-format
+msgid ""
+"See zzz's TODO lists,\n"
+"this website's TODO list or\n"
+"Trac\n"
+"for ideas."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-developers.html:143
+#, python-format
+msgid ""
+"See the bottom of the licenses page "
+"for\n"
+"commit privilege requirements. You need these to put code into i2p.i2p "
+"(not required for the website!)."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-developers.html:148
+msgid "Short version of how to generate and use keys if you plan to commit:"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-developers.html:150
+msgid "use an empty passphrase"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-developers.html:151
+msgid "enter a passphrase"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-developers.html:152
+#, python-format
+msgid ""
+"send this to a mtn repo operator to get "
+"push privileges"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-developers.html:153
+#, python-format
+msgid ""
+"send this to a release manager to get "
+"commit privileges - not required for website"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-developers.html:154
+msgid "check in with this key"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-developers.html:155
+msgid "push with this key"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-developers.html:157
+#, python-format
+msgid "Long version: see the monotone page."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-developers.html:163
+#, python-format
+msgid ""
+"The developers hang around on IRC. They can be reached on the Freenode "
+"network, OFTC, and on the I2P internal networks. The usual place to look "
+"is #i2p-dev. Join the channel and say hi!\n"
+"We also have additional guidelines for regular"
+" developers."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-developers.html:169
+#, python-format
+msgid ""
+"Website and router console translators: See the New Translator's Guide\n"
+"for next steps."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-developers.html:175
+msgid ""
+"I2P is open source software that is mostly developed using open sourced\n"
+"toolkits. The I2P project recently acquired a license for the YourKit "
+"Java\n"
+"Profiler. Open source projects are eligible to receive a free license "
+"provided\n"
+"that YourKit is referenced on the project web site. Please get in touch "
+"if you\n"
+"are interested in profiling the I2P codebase."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-developers.html:183
+#, python-format
+msgid ""
+"YourKit is kindly supporting open source projects with its full-featured "
+"Java Profiler.\n"
+"YourKit, LLC is the creator of innovative and intelligent tools for "
+"profiling\n"
+"Java and .NET applications. Take a look at YourKit's leading software "
+"products:\n"
+"YourKit Java Profiler and\n"
+"YourKit .NET Profiler."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-translators.html:2
+msgid "New Translator's Guide"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-translators.html:4
+msgid "Here's a very quick guide to getting started."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-translators.html:6
+msgid "How to Translate the Website"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-translators.html:8
+#, python-format
+msgid ""
+"Translation of the website is done with .po files. The easiest way by far"
+" to\n"
+"translate the website is to sign up for an account at \n"
+"Transifex and request to join a translation"
+" team. \n"
+"Alternatively it can be done \"the old way\" as outlined below."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-translators.html:17
+#: i2p2www/pages/site/get-involved/guides/new-translators.html:82
+msgid "Preparation"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-translators.html:19
+#: i2p2www/pages/site/get-involved/guides/new-translators.html:84
+#, python-format
+msgid ""
+"Come to #i2p-dev on irc and talk to people.\n"
+"Claim the language -\n"
+"To make sure other coworkers don't bump onto the files you are working "
+"on,\n"
+"please update the translation status on this wiki "
+"page."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-translators.html:25
+#, python-format
+msgid ""
+"Follow the new developer's guide,\n"
+"Including the installation of monotone,\n"
+"checking out i2p.www branch, and generate your own monotone keys.\n"
+"It is not required that you sign a dev agreement."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-translators.html:33
+msgid ""
+"Create files:\n"
+"If the file for your language does not exist yet:"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-translators.html:38
+msgid ""
+"Run \"./extract-messages.sh\" to generate a "
+"messages.pot in the base directory.\n"
+"Edit the header of this file, then run \"./init-new-po.sh "
+"locale\" to generate the file\n"
+"i2p2www/translations/locale/LC_MESSAGES/messages.po. "
+"\"mtn add\" this file."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-translators.html:43
+msgid ""
+"Edit i2p2www/pages/global/lang.html and add a line for your "
+"language (copy an existing line)."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-translators.html:46
+msgid ""
+"Add a flag image file to i2p2www/static/images/flags/ for "
+"the menu (copy from the router)."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-translators.html:52
+msgid ""
+"Edit files:\n"
+"Edit i2p2www/translations/locale/LC_MESSAGES/messages.po.\n"
+"To work with .po files efficiently, you may wish to use POEdit"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-translators.html:58
+#: i2p2www/pages/site/get-involved/guides/new-translators.html:151
+msgid ""
+"Check in:\n"
+"\"mtn pull\", \"mtn update\". Then check in by "
+"\"mtn ci -k yourname@mail.i2p file1 file2 ...\"\n"
+"This collects the diff info of your changed file into your local repo. "
+"Then \"mtn sync mtn.i2p2.de -k yourname-transport@mail.i2p "
+"i2p.i2p\".\n"
+"This synchronizes your local repo with the repo on the target machine."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-translators.html:65
+#: i2p2www/pages/site/get-involved/guides/new-translators.html:158
+msgid "Repeat. Check in often. Don't wait until it is perfect."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-translators.html:72
+msgid "How to Translate the Router Console"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-translators.html:74
+#, python-format
+msgid ""
+"The easiest way by far to translate the router console is to sign up for "
+"an account at \n"
+"Transifex and request to join a translation"
+" team. \n"
+"Alternatively it can be done \"the old way\" as outlined below."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-translators.html:90
+#, python-format
+msgid ""
+"Follow the new developer's guide,\n"
+"including the installation of monotone and the gettext tools,\n"
+"checking out i2p.i2p branch, and generate your own monotone keys."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-translators.html:95
+msgid "Generate your own gpg key and sign the dev agreement."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-translators.html:101
+msgid ""
+"Before starting a console translation, better help translate some i2p "
+"webpages first.\n"
+"At least an i2p homepage in your language would be great."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-translators.html:106
+msgid ""
+"What to translate:\n"
+"There are about 15 files in the i2p.i2p branch that needs translation:"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-translators.html:132
+msgid ""
+"Where xx is your language code like fr/de/ch/zh/...\n"
+"There may be or may not be files with your lang code. If not, you can "
+"create your own. by copying and renaming other language files you know "
+"with your own lang code."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-translators.html:137
+msgid ""
+"Create files:\n"
+"If the file for your language does not exist yet, copy another language "
+"file to a new file foo_xx.bar for your language.\n"
+"Then \"mtn add\" the file.\n"
+"After creating a .po file, edit the headers. Then run \"ant "
+"distclean poupdate\"."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-translators.html:144
+msgid ""
+"Start to work:\n"
+"Edit the HTML files with any text editor.\n"
+"Be sure not to use an editor in HTML mode that reformats everything.\n"
+"To work with .po files efficiently, you may wish to use POEdit"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-translators.html:163
+msgid ""
+"As you can see, it's not that difficult.\n"
+"If you have questions about the meaning of the terms in the console, ask "
+"in #i2p-dev on IRC."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-translators.html:169
+msgid "FAQ"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-translators.html:171
+msgid ""
+"Q: Why do I have to install monotone, Java, jsp, learn about .po files "
+"and html, etc.? Why can't I just do a translation and email it to you?"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-translators.html:175
+msgid "A: Several reasons:"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-translators.html:178
+#, python-format
+msgid ""
+"You might be interested in translating via Transifex. Request to join a "
+"translation team here."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-translators.html:182
+msgid ""
+"We don't have anybody who has time to accept manual contributions and "
+"submit them to our source control system on your behalf. Even if we did, "
+"it doesn't scale."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-translators.html:186
+msgid ""
+"Maybe you are thinking translation is a one-step process. It isn't. You "
+"can't do it all at once. You will make mistakes. You need to test it and "
+"tweak it to make it look right before you submit it. Developers "
+"will update or add to the English text, thus requiring a translation "
+"update."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-translators.html:190
+msgid ""
+"Having translators use a source control system directly provides "
+"authentication and accountablility - we know who is doing what, and we "
+"can track changes, and revert them if necessary."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-translators.html:194
+msgid ""
+".po files are not difficult. If you don't want to work directly with "
+"them, we recommend 'poedit'."
+msgstr ""
+"I file .po non sono difficili. Se non vuoi lavorare direttamente con "
+"loro, ti raccomandiamo 'poedit'."
+
+#: i2p2www/pages/site/get-involved/guides/new-translators.html:198
+msgid ""
+"HTML files are not difficult. Just ignore the html stuff and translate "
+"the text."
+msgstr ""
+"I file HTML non sono difficili. Semplicemente ignora l'html e traduci il "
+"testo."
+
+#: i2p2www/pages/site/get-involved/guides/new-translators.html:202
+msgid ""
+"Installing and using monotone is not that difficult. Several of the "
+"translators and other contributors to I2P are non-programmers, and they "
+"use monotone regularly. Monotone is simply a source control system, it is"
+" not about \"coding\"."
+msgstr ""
+"Installare e utilizzare monotone non è così difficile. Alcuni traduttori "
+"ed altri collaboratori di I2P non sono programmatori, eppure usano "
+"monotone regolarmente. Monotone è semplicemente un sistema di controllo "
+"dei sorgenti, ma non ha nulla a che vedere con il \"coding\"."
+
+#: i2p2www/pages/site/get-involved/guides/new-translators.html:206
+msgid ""
+"Our items to translate are not \"documents\". They are html files and po "
+"files, with a specific format and character encoding (UTF-8) that must be"
+" maintained, and not corrupted by email programs or other methods of "
+"transfer."
+msgstr ""
+"I nostri oggetti di traduzione non sono \"documenti\". Sono file html e "
+"file po, con uno specifico formato e una codifica UTF-8 che deve essere "
+"mantenuta, e non corrotta, nel processo di trasferimento che sia l'email "
+"o altro."
+
+#: i2p2www/pages/site/get-involved/guides/new-translators.html:210
+msgid ""
+"We looked at 'pootle' as a front-end for translators. It didn't work "
+"well, needed an administrator, and a pootle-based process would suffer "
+"from a number of the above flaws."
+msgstr ""
+"Avevamo dato uno sguardo a 'pootple' come front-end per i traduttori. Non"
+" funzionava bene, aveva bisogno di un amministratore, e il processo "
+"pootle-based avrebbe sofferto di numerosi dei problemi di cui sopra."
+
+#: i2p2www/pages/site/get-involved/guides/new-translators.html:215
+msgid ""
+"In summary:\n"
+"Yes, we know it is somewhat of a hurdle to get started. It's really the "
+"only possible way we can do it. Give it a try, it really isn't that hard."
+msgstr ""
+"In sintesi:<\\b>\n"
+"Si, sappiamo che può essere un po' ostico partire. E' l'unico modo in cui"
+" possiamo farcela. Provaci, non è poi così difficile."
+
+#: i2p2www/pages/site/get-involved/guides/new-translators.html:220
+msgid "More Information"
+msgstr "Ulteriori Informazioni"
+
+#: i2p2www/pages/site/get-involved/guides/new-translators.html:221
+#, python-format
+msgid ""
+"The #i2p-dev channel on IRC, or the translation forum on %(zzz)s."
+msgstr ""
+"Il canale #i2p'dev su IRC o il forum"
+" di traduzione su %(zzz)s."
+
diff --git a/i2p2www/translations/it/LC_MESSAGES/priority.po b/i2p2www/translations/it/LC_MESSAGES/priority.po
new file mode 100644
index 00000000..8b419a2e
--- /dev/null
+++ b/i2p2www/translations/it/LC_MESSAGES/priority.po
@@ -0,0 +1,3476 @@
+# Italian translations for I2P.
+# Copyright (C) 2013 ORGANIZATION
+# This file is distributed under the same license as the I2P project.
+#
+# Translators:
+# coso , 2013
+# coso , 2013
+msgid ""
+msgstr ""
+"Project-Id-Version: I2P\n"
+"Report-Msgid-Bugs-To: http://trac.i2p2.de\n"
+"POT-Creation-Date: 2013-11-27 00:23+0000\n"
+"PO-Revision-Date: 2013-11-27 00:30+0000\n"
+"Last-Translator: str4d \n"
+"Language-Team: Italian "
+"(http://www.transifex.com/projects/p/I2P/language/it/)\n"
+"Plural-Forms: nplurals=2; plural=(n != 1)\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=utf-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"Generated-By: Babel 0.9.6\n"
+
+#: i2p2www/pages/blog/category.html:2
+msgid "Blog Category"
+msgstr "Categoria blog"
+
+#: i2p2www/pages/blog/category.html:4
+#, python-format
+msgid "I2P Blog ATOM Feed for Category: %(category)s"
+msgstr "Feed ATOM blog I2P per categoria: %(category)s"
+
+#: i2p2www/pages/blog/index.html:2 i2p2www/pages/blog/post.html:3
+#: i2p2www/pages/global/nav.html:95
+msgid "Blog"
+msgstr "Blog"
+
+#: i2p2www/pages/blog/index.html:4 i2p2www/pages/site/index.html:78
+msgid "I2P Blog ATOM Feed"
+msgstr "Feed ATOM blog I2P"
+
+#: i2p2www/pages/blog/index.html:17
+#, python-format
+msgid "Posted %(date)s by %(author)s"
+msgstr "Pubblicato in data %(date)s da %(author)s"
+
+#: i2p2www/pages/blog/latest.html:5
+msgid "More blog posts…"
+msgstr "Altri post del blog…"
+
+#: i2p2www/pages/blog/post.html:6
+msgid "Posted:"
+msgstr "Pubblicato:"
+
+#: i2p2www/pages/blog/post.html:7
+msgid "Author:"
+msgstr "Autore:"
+
+#: i2p2www/pages/downloads/debian.html:4
+msgid "Debian I2P Packages"
+msgstr "Pacchetti I2P di Debian"
+
+#: i2p2www/pages/downloads/debian.html:6
+msgid ""
+"The Debian packages\n"
+"have been tested and should work on x86/x86_64 platforms running:"
+msgstr ""
+"I pacchetti Debian \n"
+"sono stati testati e dovrebbero funzionare sulle piattaforme "
+"x86/x86_64 su cui gira:"
+
+#: i2p2www/pages/downloads/debian.html:11
+msgid "Ubuntu (Precise 12.04 and newer)"
+msgstr "Ubuntu (Precise 12.04 e più recenti)"
+
+#: i2p2www/pages/downloads/debian.html:13
+msgid "Debian Linux (Squeeze and newer) & kFreeBSD"
+msgstr ""
+"Debian Linux (Squeeze e più recenti) & "
+"kFreeBSD"
+
+#: i2p2www/pages/downloads/debian.html:17
+#, python-format
+msgid ""
+"The I2P packages may work on systems not listed above. Please "
+"report any issues\n"
+"with these packages on Trac at\n"
+"https://trac.i2p2.de."
+msgstr ""
+"I pacchetti I2P potrebbero funzionare su sistemi non elencati "
+"qui sopra. Riporta eventuali problemi \n"
+"con questi pacchetti su Trac all'indirizzo\n"
+"https://trac.i2p2.de."
+
+#: i2p2www/pages/downloads/debian.html:23
+msgid ""
+"Option 1: Recent versions of Ubuntu and its "
+"derivatives (Try this if you're not using Debian)"
+msgstr ""
+"Opzione 1: Versioni recenti di Ubuntu e le sue "
+"derivate (Prova questa se non usi Debian)"
+
+#: i2p2www/pages/downloads/debian.html:24
+msgid "Option 2: Debian (including Debian-derivatives)"
+msgstr "Opzione 2: Debian (incluse le derivate di Debian)"
+
+#: i2p2www/pages/downloads/debian.html:27
+msgid ""
+"Instructions for Ubuntu Precise Pangolin (and newer) and derivatives like"
+" Linux Mint & Trisquel"
+msgstr ""
+"Istruzioni per Ubuntu Precise Pangolin (e più recenti) e derivate come "
+"Linux Mint & Trisquel"
+
+#: i2p2www/pages/downloads/debian.html:28
+msgid "Adding the PPA via the command line and installing I2P"
+msgstr "Aggiunta di PPA tramite riga di comando e installazione di I2P"
+
+#: i2p2www/pages/downloads/debian.html:31
+msgid "Open a terminal and enter:"
+msgstr "Apri un terminale e inserisci:"
+
+#: i2p2www/pages/downloads/debian.html:33
+msgid ""
+"This command will add the PPA to /etc/apt/sources.list.d and fetch the\n"
+"gpg key that the repository has been signed with. The GPG key ensures\n"
+"that the packages have not been tampered with since being built."
+msgstr ""
+"Questo comando aggiungerà il PPA a /etc/apt/sources.list.d e recupererà "
+"la\n"
+"chiave gpg con cui il repository è stato firmato. La chiave GPG "
+"garantisce\n"
+"che quei pacchetti non sono stati manomessi dopo la loro compilazione."
+
+#: i2p2www/pages/downloads/debian.html:40
+msgid "Notify your package manager of the new PPA by entering:"
+msgstr "Notifica al tuo gestore di pacchetti il nuovo PPA inserendo:"
+
+#: i2p2www/pages/downloads/debian.html:42
+msgid ""
+"This command will retrieve the latest list of software from each\n"
+"repository that is enabled on your system, including the I2P PPA that\n"
+"was added with the earlier command."
+msgstr ""
+"Questo comando recupererà l'elenco di programmi più recenti da ciascun\n"
+"repository attivato sul sistema, incluso il PPA \n"
+"aggiuntio con il comando di prima."
+
+#: i2p2www/pages/downloads/debian.html:48
+msgid "You are now ready to install I2P!"
+msgstr "Adesso sei pronto per l'installazione di I2P!"
+
+#: i2p2www/pages/downloads/debian.html:52
+msgid "Adding the PPA Using Synaptic"
+msgstr "Aggiunta del PPA usando Synaptic"
+
+#: i2p2www/pages/downloads/debian.html:55
+msgid ""
+"Open Synaptic (System -> Administration -> Synaptic Package "
+"Manager)."
+msgstr ""
+"Apri Synaptic (Sistema -> amministrazione -> Gestore dei pacchetti "
+"Synaptic)."
+
+#: i2p2www/pages/downloads/debian.html:60
+msgid ""
+"Once Synaptic opens, select Repositories from the "
+"Settings menu."
+msgstr ""
+"Quando Synaptic si apre, seleziona Repository dal menu "
+"Impostazioni."
+
+#: i2p2www/pages/downloads/debian.html:65
+msgid ""
+"Click the Other Sources tab and click Add. Paste "
+"ppa:i2p-maintainers/i2p into the APT-line field and click "
+"Add Source. Click the Close button then "
+"Reload."
+msgstr ""
+"Fai clc sulla scheda Altre fonti e su Aggiungi. Incolla"
+" ppa:i2p-maintainers/i2p nel campo dedicato alla riga APT e "
+"fai clic su Aggiungi fonte. Fai clic sul pulsante "
+"Chiudi quindi su Ricarica."
+
+#: i2p2www/pages/downloads/debian.html:70
+msgid ""
+"In the Quick Filter box, type in i2p and press enter. When "
+"i2p is returned in the results list, right click "
+"i2p and select Mark for Installation. After doing "
+"so you may see a Mark additional required changes? popup. If so,"
+" click Mark then Apply."
+msgstr ""
+"Nel riquadro di filtro rapido, digita i2p e premi Invio. "
+"Quando i2p compare nell'elenco dei risultati, fai clic con "
+"il pulsante destro del mouse su i2p e seleziona "
+"Contrassegna per l'installazione. Dopo di che, potrebbe apparire"
+" un messaggio di popup Contrassegna modifiche necessarie "
+"aggiuntive?. Se capita, fai clic su Contrassegna quindi su "
+"Applica."
+
+#: i2p2www/pages/downloads/debian.html:76
+msgid ""
+"After the installation process completes you can move on to the next\n"
+"part of starting I2P and configuring "
+"it for your system."
+msgstr ""
+"Dopo il completamento della procedura di installazione, puoi passare alla"
+" sezione\n"
+"successiva per avviare I2P e "
+"configurarlo per il tuo sistema."
+
+#: i2p2www/pages/downloads/debian.html:81
+msgid "Instructions for Debian"
+msgstr "Istruzioni per Debian"
+
+#: i2p2www/pages/downloads/debian.html:85
+msgid ""
+"Note: The steps below should be performed with root access (i.e., "
+"switching\n"
+"user to root with \"su\" or by prefixing each command with \"sudo\")."
+msgstr ""
+"Nota: i punti sottostanti dovrebbe essere eseguiti con un accesso di "
+"amministratore (ad esempio, passando da utente normale\n"
+"a root con \"su\" o facendo precedere ogni comando da \"sudo\")."
+
+#: i2p2www/pages/downloads/debian.html:90
+#, python-format
+msgid "Add lines like the following to %(file)s."
+msgstr "Aggiungi linee come le seguenti a %(file)s."
+
+#: i2p2www/pages/downloads/debian.html:111
+#, python-format
+msgid ""
+"Download the key used to sign the repository"
+" and add it to apt:"
+msgstr ""
+"Scarica la chiave usata per firmare il "
+"repository e aggiungila ad apt:"
+
+#: i2p2www/pages/downloads/debian.html:118
+msgid "Notify your package manager of the new repository by entering"
+msgstr "Notifica al tuo gestore di pacchetti il nuovo repository inserendo"
+
+#: i2p2www/pages/downloads/debian.html:120
+msgid ""
+"This command will retrieve the latest list of software from every\n"
+"repository enabled on your system, including the I2P repository added in "
+"step\n"
+"1."
+msgstr ""
+"Questo comando recupererà l'elenco di programmi più recenti da ogni\n"
+"repository attivato sul sistema, incluso quello I2P aggiunto nel punto \n"
+"1."
+
+#: i2p2www/pages/downloads/debian.html:126
+msgid ""
+"You are now ready to install I2P! Installing the i2p-keyring"
+"\n"
+"package will ensure that you receive updates to the repository's GPG key."
+msgstr ""
+"Sei pronto a installare I2P! L'installazione del pacchetto i2p-"
+"keyring\n"
+"farà in modo di farti ricevere gli aggiornamenti della chiave GPG del "
+"repository."
+
+#: i2p2www/pages/downloads/debian.html:133
+msgid ""
+"After the installation process completes you can move on to the next part"
+" of starting I2P and configuring it "
+"for your system."
+msgstr ""
+"Dopo il completamento della procedura di installazione, puoi passare alla"
+" sezione successiva per avviare I2P e "
+"configurarlo per il tuo sistema."
+
+#: i2p2www/pages/downloads/debian.html:137
+#: i2p2www/pages/downloads/list.html:171
+msgid "Post-install work"
+msgstr "Post-installazione"
+
+#: i2p2www/pages/downloads/debian.html:139
+msgid ""
+"Using these I2P packages the I2P router can be started in the following\n"
+"three ways:"
+msgstr ""
+"Usando questi pacchetti I2P, il router I2P può essere arriavo nei \n"
+"tre modi che seguono:"
+
+#: i2p2www/pages/downloads/debian.html:145
+msgid ""
+""on demand" using the i2prouter script. Simply run "
+""i2prouter\n"
+"start" from a command prompt. (Note: Do "
+"not use\n"
+"sudo or run it as root!)"
+msgstr ""
+""a richiesta" usando lo script i2prouter. Ti basta eseguire "
+""i2prouter\n"
+"start" da riga di comando. (Nota: non"
+" usare\n"
+"sudo e non eseguirlo con privilegi di amministrazione!)"
+
+#: i2p2www/pages/downloads/debian.html:152
+msgid ""
+""on demand" without the java service wrapper\n"
+"(needed on non-Linux/non-x86 systems) by running \"i2prouter-"
+"nowrapper\".\n"
+"(Note: Do not\n"
+"use sudo or run it as root!)"
+msgstr ""
+""a richiesta" senza il wrapper di servizi java\n"
+"(necessario su sistemi diversi da Linux o diversi da x86) eseguendo "
+"\"i2prouter-nowrapper\".\n"
+"(Nota: strong>non/u>\n"
+"usare sudo e non eseguirlo con privilegi di amministrazione!)"
+
+#: i2p2www/pages/downloads/debian.html:160
+msgid ""
+"as a service that automatically runs when your system boots, even\n"
+"before logging in. The service can be enabled with \"dpkg-"
+"reconfigure\n"
+"i2p\" as root or using sudo. This is the recommended means of "
+"operation."
+msgstr ""
+"come servizio che viene eseguito automaticamente all'avvio del sistema, "
+"anche \n"
+"prima di effettuare l'accesso. Il servizio può essere attivato con "
+"\"dpkg-reconfigure\n"
+"i2p\" con privilegi di amministrazione o usando sudo. Questa è la "
+"modalità consigliata."
+
+#: i2p2www/pages/downloads/debian.html:168
+msgid ""
+"When installing for the first time, please remember to adjust your "
+"NAT/firewall\n"
+"if you can. The ports to forward can be found on the \n"
+"network configuration page in the router console. If guidance with "
+"respect to forwarding ports is needed,\n"
+"you may find portforward.com to be"
+" helpful."
+msgstr ""
+"Per la primissima installazione, ricorda di regolare il tuo NAT o "
+"firewall\n"
+"se puoi. Le porte da inoltrare possono essere trovate nella \n"
+"pagina di configurazione di rete nel console router. Se serve aiuto "
+"in merito al port forwarding,\n"
+"è possibile trovare qualche dritta su portforward.com."
+
+#: i2p2www/pages/downloads/debian.html:175
+msgid ""
+"Please review and adjust the bandwidth settings on the\n"
+"configuration page,\n"
+"as the default settings of 96 KB/s down / 40 KB/s up are fairly "
+"conservative."
+msgstr ""
+"Esamina e modifica le impostazioni della larghezza di banda nella\n"
+"pagina di "
+"configurazione,\n"
+"perché le impostazioni predefinite di 96 KB/s per il download e 40 KB/s "
+"per l'upload sono abbastanza conservative."
+
+#: i2p2www/pages/downloads/debian.html:181
+#: i2p2www/pages/downloads/list.html:204
+#, python-format
+msgid ""
+"If you want to reach eepsites via your browser, have a look on the browser proxy setup page for an easy "
+"howto."
+msgstr ""
+"Se vuoi raggiungere gli eepsite con il tuo browser, dai un'occhiata alla "
+"pagina impostazione proxy del browser "
+"per delle semplici istruzioni."
+
+#: i2p2www/pages/downloads/list.html:2 i2p2www/pages/downloads/select.html:12
+#: i2p2www/pages/global/nav.html:3
+msgid "Download"
+msgstr "Download"
+
+#: i2p2www/pages/downloads/list.html:9
+msgid "Download I2P"
+msgstr "Download I2P"
+
+#: i2p2www/pages/downloads/list.html:11
+msgid "Dependency"
+msgstr "Dipendenze"
+
+#: i2p2www/pages/downloads/list.html:12
+#, python-format
+msgid ""
+"\n"
+"Java Runtime 1.5 or higher.\n"
+"(Oracle Java Version 7,\n"
+"OpenJDK 7, or\n"
+"IcedTea7\n"
+" recommended,\n"
+"except Raspberry Pi: Oracle 8 Early Access,\n"
+"PowerPC: IBM SDK 7)\n"
+"
\n"
+"Determine your installed Java version here\n"
+"or type java -version at your command prompt.\n"
+msgstr ""
+"\n"
+"Java Runtime 1.5 o superiore.\n"
+"(Oracle Java versione 7,\n"
+"OpenJDK 7, o\n"
+"IcedTea7\n"
+" consigliati,\n"
+"eccetto che per il Raspberry Pi: Oracle 8 Early "
+"Access,\n"
+"PowerPC: IBM SDK 7)\n"
+"
\n"
+"Determina la versione di Java installata "
+"qui\n"
+"o digita java -version al prompt dei comandi.\n"
+
+#: i2p2www/pages/downloads/list.html:30
+msgid "Clean installs"
+msgstr "Pulisci installazioni"
+
+#: i2p2www/pages/downloads/list.html:37 i2p2www/pages/downloads/list.html:54
+#: i2p2www/pages/downloads/list.html:81 i2p2www/pages/downloads/list.html:140
+#: i2p2www/pages/downloads/list.html:269
+msgid "select alternate link"
+msgstr "seleziona un link alternativo"
+
+#: i2p2www/pages/downloads/list.html:44
+msgid "Download that file and run it."
+msgstr "Scarica il file ed eseguilo."
+
+#: i2p2www/pages/downloads/list.html:61
+#, python-format
+msgid ""
+"Download that file and double-click it (if that works) or\n"
+" type java -jar i2pinstall_%(i2pversion)s.jar in a "
+"terminal to run the\n"
+" installer.\n"
+" You may be able to right-click and select\n"
+" "Open with Java"."
+msgstr ""
+"Scarica il fil e fari doppio clic su di esso (se la cosa funziona) oppure"
+"\n"
+" digita java -jar i2pinstall_%(i2pversion)s.jar in un "
+"terminale per eseguire il\n"
+" programma di installazione.\n"
+" Potrebbe essere possibile fare clic con il pulsante destro del mouse "
+"e selezionare\n"
+" "Apri con Java"."
+
+#: i2p2www/pages/downloads/list.html:69 i2p2www/pages/downloads/list.html:96
+msgid "Command line (headless) install:"
+msgstr "Installazione da riga di comando (non interattiva):"
+
+#: i2p2www/pages/downloads/list.html:70
+#, python-format
+msgid ""
+"Download the %(i2pversion)s OSX graphical installer file above and\n"
+" run java -jar i2pinstall_%(i2pversion)s.jar -console "
+"from the command line."
+msgstr ""
+"Scarica il file del programma di installazione grafica per OSX "
+"%(i2pversion)s e\n"
+" esegui java -jar i2pinstall_%(i2pversion)s.jar -console "
+"da riga di comando."
+
+#: i2p2www/pages/downloads/list.html:88
+#, python-format
+msgid ""
+"Download that file and double-click it (if that works) or\n"
+" type java -jar i2pinstall_%(i2pversion)s.jar in a "
+"terminal to run the\n"
+" installer.\n"
+" On some platforms you may be able to right-click and select\n"
+" "Open with Java"."
+msgstr ""
+"Scarica il fil e fari doppio clic su di esso (se la cosa funziona) oppure"
+"\n"
+" digita java -jar i2pinstall_%(i2pversion)s.jar in un "
+"terminale per eseguire il\n"
+" programma di installazione.\n"
+" Su alcune piattaforme potrebbe essere possibile fare clic con il "
+"pulsante destro del mouse e selezionare\n"
+" "Apri con Java"."
+
+#: i2p2www/pages/downloads/list.html:97
+#, python-format
+msgid ""
+"Download the graphical installer file above and\n"
+" run java -jar i2pinstall_%(i2pversion)s.jar -console "
+"from the command line."
+msgstr ""
+"Scarica il file del programma di installazione grafica e\n"
+" esegui java -jar i2pinstall_%(i2pversion)s.jar -console "
+"da riga di comando."
+
+#: i2p2www/pages/downloads/list.html:107
+msgid "Packages for Debian & Ubuntu are available."
+msgstr "Sono disponibili i pacchetti per Debian & Ubuntu."
+
+#: i2p2www/pages/downloads/list.html:121
+#, python-format
+msgid ""
+"The above file is the current release build.\n"
+" The latest dev build is version %(devbuild)s, and is available from\n"
+" str4d's eepsite."
+msgstr ""
+"Il file precedente rappresenta la versione attuale.\n"
+" La build di sviluppo più recente è la versione %(devbuild)s ed è "
+"disponibile\n"
+" sull'eepsite di str4d."
+
+#: i2p2www/pages/downloads/list.html:127
+msgid ""
+"The release and dev versions of the I2P APK are not compatible, as they\n"
+" are signed by zzz and str4d respectively. Uninstall one before "
+"installing\n"
+" the other."
+msgstr ""
+"Le versioni per il pubblico e quelle di sviiluppo dell'APK di I2P non "
+"sono compatibili perché \n"
+" sono firmate rispettivamente da zzz e str4d. Disinstallane una "
+"prima di installare\n"
+" l'altra."
+
+#: i2p2www/pages/downloads/list.html:137
+msgid "Source package"
+msgstr "Pacchetto sorgente"
+
+#: i2p2www/pages/downloads/list.html:147
+#, python-format
+msgid ""
+"Alternately, you can fetch the source from monotone\n"
+" or via Git from git.repo.i2p or Github.\n"
+"
\n"
+" Run (tar xjvf i2psource_%(i2pversion)s.tar.bz2 ; cd "
+"i2p-%(i2pversion)s ; ant pkg) then either\n"
+" run the GUI installer or headless install as above."
+msgstr ""
+"In alternativa, puoi recuperare la fonte su monotone\n"
+" o tramite Git su git.repo.i2p oppure Github.\n"
+"
\n"
+" Esegui (tar xjvf i2psource_%(i2pversion)s.tar.bz2 ; cd "
+"i2p-%(i2pversion)s ; ant pkg) quindi\n"
+" esegui l'installazione grafica o l'installazione non interattiva come"
+" sopra."
+
+#: i2p2www/pages/downloads/list.html:162
+#, python-format
+msgid ""
+"The files are signed by zzz,\n"
+"whose key is here."
+msgstr ""
+"I file sono firmati da zzz,\n"
+"la cui chiave si trova qui."
+
+#: i2p2www/pages/downloads/list.html:167
+msgid ""
+"I2P can also be downloaded from our project pages on Launchpad and Google Code."
+msgstr ""
+"I2P può anche essere scaricato dalle nostre pagine del progetto su Launchpad e Google Code."
+
+#: i2p2www/pages/downloads/list.html:173
+msgid ""
+"After running the installer on windows, simply click on the \"Start I2P\""
+" button\n"
+"which will bring up the router console,\n"
+"which has further instructions."
+msgstr ""
+"Dopo aver eseguito l'installazione su Windows, fai semplicemente clic sul"
+" pulsante \"Avvia I2P\"\n"
+"che richiama la router "
+"console,\n"
+"che contiene ulteriori istruzioni."
+
+#: i2p2www/pages/downloads/list.html:179
+msgid ""
+"On Unix-like systems, I2P can be started as a service\n"
+"using the \"i2prouter\" script, located in the directory you selected for"
+" I2P.\n"
+"Changing to that directory in a console and issuing \"sh i2prouter "
+"status\"\n"
+"should tell you the router's status. The arguments \"start\", \"stop\" "
+"and \"restart\"\n"
+"control the service. The router console\n"
+"can be accessed at its usual location.\n"
+"For users on OpenSolaris and other systems for which the wrapper (i2psvc)"
+" is not supported,\n"
+"start the router with \"sh runplain.sh\" instead."
+msgstr ""
+"Sui sistemi Unix e simili, I2P può essere avviato come un servizio\n"
+"usando lo script \"i2prouter\" che si trova nella cartella che hai "
+"selezionato per I2P.\n"
+"Accedere a quella cartella in un terminale ed eseguire il comando \"sh "
+"i2prouter status\"\n"
+"dovrebbe indicarti lo stato del router. Gli argomenti \"start\", \"stop\""
+" e \"restart\"\n"
+"controllano il servizio. Puoi accedere alla router console\n"
+"nella sua posizione usuale.\n"
+"Gli utenti su OpenSolaris e altri sistemi per i quali il wrapper (i2psvc)"
+" non è supportato\n"
+"dovrebbero invece avviare il router con \"sh runplain.sh\"."
+
+#: i2p2www/pages/downloads/list.html:190
+#, python-format
+msgid ""
+"When installing for the first time, please remember to adjust your "
+"NAT/firewall\n"
+"if you can, bearing in mind the Internet-facing ports I2P uses,\n"
+"described here among other ports.\n"
+"If you have successfully opened your port to inbound TCP, also enable "
+"inbound TCP on the\n"
+"configuration page."
+msgstr ""
+"Quando lo installi per la prima volta, ricorda di regolare il tuo NAT "
+"o firewall\n"
+"se puoi, tenendo presente le porte usate da I2P per l'accesso a Internet,"
+"\n"
+"descritte qui tra le altre porte.\n"
+"Se hai aperto correttamente la porta per il traffico TCP in entrata, "
+"attiva il traffico TCP in entrata anche nella\n"
+"pagina di "
+"configurazione."
+
+#: i2p2www/pages/downloads/list.html:198
+msgid ""
+"Also, please review and adjust the bandwidth settings on the\n"
+"configuration page,\n"
+"as the default settings of 96 KBps down / 40 KBps up are fairly slow."
+msgstr ""
+"Inoltre, esamina e modifica le impostazioni della larghezza di "
+"banda nella\n"
+"pagina di "
+"configurazione,\n"
+"perché le impostazioni predefinitie di of 96 KBps per il download e 40 "
+"KBps per l'upload sono abbastanza lente."
+
+#: i2p2www/pages/downloads/list.html:208
+msgid "Updates from earlier releases:"
+msgstr "Aggiornamento da versioni precedenti:"
+
+#: i2p2www/pages/downloads/list.html:210
+msgid "Both automatic and manual upgrades are available for the release."
+msgstr ""
+"sono disponibili sia gli aggiornamenti automatici che manuali per questa "
+"versione."
+
+#: i2p2www/pages/downloads/list.html:215
+msgid "Automatic updates"
+msgstr "Aggiornamenti automatici"
+
+#: i2p2www/pages/downloads/list.html:217
+msgid ""
+"If you are running 0.7.5 or later, your router should detect the\n"
+"new release. To upgrade simply click the 'Download Update' button on your"
+" router console\n"
+"when it appears."
+msgstr ""
+"Se usi la versione 0.7.5 o successiva, il tuo router dovrebber rilevare "
+"la presenza di una \n"
+"nuova versione. Per aggiornare, fai semplicemente clic su 'Scarica "
+"aggiornamento' nel console router\n"
+"quando appare."
+
+#: i2p2www/pages/downloads/list.html:223
+msgid ""
+"Due to a bug in release 0.7.6, those whose first I2P installation was "
+"that version\n"
+"and have not upgraded manually\n"
+"may get a \"downloaded version is not greater than current version\" "
+"error,\n"
+"and should use the manual update method below."
+msgstr ""
+"A causa di un bug nella versione 0.7.6, chi ha installato I2P per la "
+"prima volta con quella versione\n"
+"e non ha aggiornato manualmente\n"
+"potrebbe ricevere un errore \"versione scaricata non maggiore di quella "
+"attuale\",\n"
+"e dovrebbe quindi usare il metodo di aggiornamento manuale qui sotto."
+
+#: i2p2www/pages/downloads/list.html:231
+#, python-format
+msgid ""
+"If you are running 0.7.4 or earlier, please see\n"
+"the 0.7.5 release notes\n"
+"for important information about how to configure your router to "
+"automatically\n"
+"receive the release."
+msgstr ""
+"Se usi la versione 0.7.4 o precedente, consulta le\n"
+"note della versione 0.7.5\n"
+"per informazioni importanti su come configurare il router per ricevere\n"
+"la versione in automatico."
+
+#: i2p2www/pages/downloads/list.html:239
+#, python-format
+msgid ""
+"If you are running 0.6.1.30 or earlier, please see\n"
+"instructions\n"
+"for important information about how to configure your router to "
+"automatically\n"
+"receive the release."
+msgstr ""
+"Se usi la versione 0.6.1.30 o precedente, consulta le\n"
+"istruzioni\n"
+"per informazioni importanti su come configurare il router per ricevere\n"
+"la versione in automatico."
+
+#: i2p2www/pages/downloads/list.html:248
+#, python-format
+msgid ""
+"If you have reconfigured your router following the instructions, you should see a link on your"
+" \n"
+" router console "
+"allowing\n"
+" you to download and install the new release by just clicking on that\n"
+" link."
+msgstr ""
+"Se hai riconfigurato il router seguendo le istruzioni, dovresti vedere un link nel \n"
+" console router che ti"
+" consente di\n"
+" scaricare e installare la nuova versione semplicemente facendo clic "
+"sul\n"
+" link."
+
+#: i2p2www/pages/downloads/list.html:256
+msgid "Alternately, you can use the manual method specified below."
+msgstr "In alternativa, puoi usare il metodo manuale come spiegato qui sotto."
+
+#: i2p2www/pages/downloads/list.html:266
+msgid "Manual updates"
+msgstr "Aggiornamenti manuali"
+
+#: i2p2www/pages/downloads/list.html:278
+msgid ""
+"Download that file to your I2P\n"
+" installation directory and rename as i2pupdate.zip.\n"
+" (alternately, you can get the source as above and run \"ant "
+"updater\", then copy the\n"
+" resulting i2pupdate.zip to your I2P installation directory). You do"
+" \n"
+" NOT need to unzip that file."
+msgstr ""
+"Scarica il file nella cartella di installazione di I2P\n"
+" e rinominalo come i2pupdate.zip.\n"
+" (in alternativa, puoi ottenere il sorgente come sopra ed eseguire "
+"\"ant updater\", quindi copiare il\n"
+" file risultante nella cartella di installazione di I2P). \n"
+" NON occorre scompattare il file."
+
+#: i2p2www/pages/downloads/list.html:287
+msgid "Click \"Restart\""
+msgstr ""
+"Fai clic su \"Riavvia\""
+
+#: i2p2www/pages/downloads/list.html:292
+msgid "Grab a cup of coffee and come back in 11 minutes"
+msgstr "Vai a bere un caffè e ritorna tra 11 minuti"
+
+#: i2p2www/pages/downloads/list.html:300
+#, python-format
+msgid ""
+"The file is signed by zzz,\n"
+"whose key is here."
+msgstr ""
+"Il file è firmato da zzz,\n"
+"la cui chiave si trova qui."
+
+#: i2p2www/pages/downloads/list.html:305
+msgid "Previous Releases"
+msgstr "Versioni precedenti"
+
+#: i2p2www/pages/downloads/list.html:307
+#, python-format
+msgid ""
+"Previous releases are available on Google "
+"Code\n"
+"and Launchpad\n"
+"and within the I2P network on %(echelon)s."
+msgstr ""
+"Le versioni precedenti sono disponibli su Google "
+"Code\n"
+"e Launchpad\n"
+", nonché sulla rete I2P all'indirizzo %(echelon)s."
+
+#: i2p2www/pages/downloads/select.html:2 i2p2www/pages/downloads/select.html:4
+msgid "Mirror selection"
+msgstr "Selezione mirror"
+
+#: i2p2www/pages/downloads/select.html:5
+msgid "File:"
+msgstr "File:"
+
+#: i2p2www/pages/downloads/select.html:10
+msgid "Any mirror"
+msgstr "Qualsiasi mirror"
+
+#: i2p2www/pages/global/bounty.html:19
+msgid ""
+"To claim the bounty the author must not be paid by other organizations\n"
+"or teams for this work (e.g. GSoC students are not valid)."
+msgstr ""
+"Per ritirare i premi, l'autore non deve essere pagato da altre "
+"organizzazioni\n"
+"o team per il lavoro svolto (per esempio, non sono valide le domande "
+"degli studenti del Google Summer of Code)."
+
+#: i2p2www/pages/global/bounty.html:29
+#, python-format
+msgid ""
+"Bounty amounts may be increased by further donations. Do\n"
+"you think these are important? Add in your "
+"donation, \n"
+"marking the amount for the %(donatename)s bounty!"
+msgstr ""
+"L'ammontare dei premi può essere aumentato da ulteriori donazioni. Credi\n"
+"siano importanti? Aggiungi la tua, \n"
+"evidenziando il valore della %(donatename)s sovvenzione!"
+
+#: i2p2www/pages/global/error_404.html:3
+msgid "Not found"
+msgstr "Non trovato"
+
+#: i2p2www/pages/global/error_404.html:9
+msgid ""
+"Yep... the resource, you were searching for, is named differently, "
+"doesn't exist or was removed."
+msgstr ""
+"Già... la risorsa che stavi cercando ha un nome diverso, non esiste "
+"oppure è stata rimossa."
+
+#: i2p2www/pages/global/error_500.html:5
+msgid "Server error"
+msgstr "Errore del server"
+
+#: i2p2www/pages/global/error_500.html:13
+msgid "500 Server error"
+msgstr "Errore del server 500"
+
+#: i2p2www/pages/global/error_500.html:17
+msgid "Umm... the server encountered some sort of error."
+msgstr "Uhm... si è verificato un qualche tipo di errore nel server."
+
+#: i2p2www/pages/global/footer.html:2
+msgid "Mirrors"
+msgstr "Mirror"
+
+#: i2p2www/pages/global/footer.html:9
+msgid "Secure"
+msgstr "Sicuro"
+
+#: i2p2www/pages/global/footer.html:16
+msgid "Misc."
+msgstr "Varie"
+
+#: i2p2www/pages/global/footer.html:19 i2p2www/pages/site/links.html:2
+msgid "Links"
+msgstr "Collegamenti"
+
+#: i2p2www/pages/global/footer.html:20
+msgid "Impressum"
+msgstr "Impressum"
+
+#: i2p2www/pages/global/footer.html:24
+msgid "T-Shirts!"
+msgstr "Magliette!"
+
+#: i2p2www/pages/global/footer.html:26
+msgid "Europe"
+msgstr "Europa"
+
+#: i2p2www/pages/global/footer.html:27
+msgid "USA"
+msgstr "Stati Uniti"
+
+#: i2p2www/pages/global/footer.html:31
+msgid "Donate"
+msgstr "Dona"
+
+#: i2p2www/pages/global/layout.html:29
+msgid "Skip navigation"
+msgstr "Salta navigazione"
+
+#: i2p2www/pages/global/layout.html:32
+msgid "I2P Logo"
+msgstr "Logo I2P"
+
+#: i2p2www/pages/global/layout.html:32 i2p2www/pages/site/index.html:3
+msgid "The Invisible Internet Project"
+msgstr "Il progetto Internet invisibile"
+
+#: i2p2www/pages/global/layout.html:56
+#, python-format
+msgid ""
+"This page was last updated in %(lastupdated)s and is accurate for router "
+"version %(accuratefor)s."
+msgstr ""
+"L'aggiornamento più recente di questa pagina risale a %(lastupdated)s e "
+"si riferisce alla versione del router %(accuratefor)s."
+
+#: i2p2www/pages/global/layout.html:60
+#, python-format
+msgid "This page was last updated in %(lastupdated)s."
+msgstr "L'aggiornamento più recente di questa pagina risale a %(lastupdated)s."
+
+#: i2p2www/pages/global/layout.html:64
+#, python-format
+msgid "This page is accurate for router version %(accuratefor)s."
+msgstr "Questa pagina si riferisce alla versione del router %(accuratefor)s."
+
+#: i2p2www/pages/global/macros:21
+msgid "Previous"
+msgstr "Precedente"
+
+#: i2p2www/pages/global/macros:36
+msgid "Next"
+msgstr "Successivo"
+
+#: i2p2www/pages/global/macros:43
+msgid "Posted in"
+msgstr "Pubblicato in"
+
+#: i2p2www/pages/global/nav.html:4
+msgid "About"
+msgstr "Informazioni su"
+
+#: i2p2www/pages/global/nav.html:6
+msgid "Introduction to I2P"
+msgstr "Introduzione a I2P"
+
+#: i2p2www/pages/global/nav.html:7
+msgid "Comparisons"
+msgstr "Confronti"
+
+#: i2p2www/pages/global/nav.html:9
+msgid "Overview of comparisons"
+msgstr "Riepilogo dei confronti"
+
+#: i2p2www/pages/global/nav.html:13
+msgid "Other anonymous networks"
+msgstr "Altre reti anonime"
+
+#: i2p2www/pages/global/nav.html:16
+msgid "Documentation"
+msgstr "Documentazione"
+
+#: i2p2www/pages/global/nav.html:18
+msgid "Documentation index"
+msgstr "Indice della documentazione"
+
+#: i2p2www/pages/global/nav.html:19
+msgid "How does it work?"
+msgstr "Come funziona?"
+
+#: i2p2www/pages/global/nav.html:21
+msgid "Gentle intro"
+msgstr "Introduzione leggera"
+
+#: i2p2www/pages/global/nav.html:22
+msgid "Tech intro"
+msgstr "Introduzione tecnica"
+
+#: i2p2www/pages/global/nav.html:23
+msgid "Threat model"
+msgstr "Modello di rischio"
+
+#: i2p2www/pages/global/nav.html:24
+msgid "Garlic routing"
+msgstr "Routing garlic"
+
+#: i2p2www/pages/global/nav.html:25
+msgid "Network database"
+msgstr "Database di rete"
+
+#: i2p2www/pages/global/nav.html:26
+msgid "Tunnel routing"
+msgstr "Routing tunnel"
+
+#: i2p2www/pages/global/nav.html:27
+msgid "Peer selection"
+msgstr "Selezione peer"
+
+#: i2p2www/pages/global/nav.html:28
+msgid "Cryptography"
+msgstr "Cifratura"
+
+#: i2p2www/pages/global/nav.html:29
+msgid "ElGamal/AES+SessionTags"
+msgstr "ElGamal/AES+SessionTags"
+
+#: i2p2www/pages/global/nav.html:32
+msgid "Specifications"
+msgstr "Specifiche"
+
+#: i2p2www/pages/global/nav.html:34
+msgid "Blockfile"
+msgstr "File di blocco"
+
+#: i2p2www/pages/global/nav.html:35
+msgid "Common structures"
+msgstr "Strutture comuni"
+
+#: i2p2www/pages/global/nav.html:36
+msgid "Configuration files"
+msgstr "File di configurazione"
+
+#: i2p2www/pages/global/nav.html:37 i2p2www/pages/global/nav.html:59
+msgid "Datagrams"
+msgstr "Datagrammi"
+
+#: i2p2www/pages/global/nav.html:38
+msgid "GeoIP files"
+msgstr "File GeoIP"
+
+#: i2p2www/pages/global/nav.html:41 i2p2www/pages/global/nav.html:91
+msgid "Plugins"
+msgstr "Plugin"
+
+#: i2p2www/pages/global/nav.html:43 i2p2www/pages/global/nav.html:57
+msgid "Streaming library"
+msgstr "Libreria di streaming"
+
+#: i2p2www/pages/global/nav.html:44
+msgid "Tunnel creation"
+msgstr "Creazione tunnel"
+
+#: i2p2www/pages/global/nav.html:45
+msgid "Tunnel messages"
+msgstr "Messaggi tunnel"
+
+#: i2p2www/pages/global/nav.html:46
+msgid "Software updates"
+msgstr "Aggiornamenti software"
+
+#: i2p2www/pages/global/nav.html:49
+msgid "API"
+msgstr "API"
+
+#: i2p2www/pages/global/nav.html:58
+msgid "Ministreaming library"
+msgstr "Libreria di ministreaming"
+
+#: i2p2www/pages/global/nav.html:63 i2p2www/pages/global/nav.html:116
+msgid "Applications"
+msgstr "Applicazioni"
+
+#: i2p2www/pages/global/nav.html:65
+msgid "Supported applications"
+msgstr "Applicazioni supportate"
+
+#: i2p2www/pages/global/nav.html:66
+msgid "Bittorrent"
+msgstr "Bittorrent"
+
+#: i2p2www/pages/global/nav.html:69
+msgid "Protocols"
+msgstr "Protocolli"
+
+#: i2p2www/pages/global/nav.html:71
+msgid "Protocol stack"
+msgstr "Stack del protocollo"
+
+#: i2p2www/pages/global/nav.html:76
+msgid "Transports"
+msgstr "Trasporti"
+
+#: i2p2www/pages/global/nav.html:78
+msgid "Transport layer overview"
+msgstr "Informazioni generali sul livello di trasporto"
+
+#: i2p2www/pages/global/nav.html:83
+msgid "Tunnels"
+msgstr "Tunnel"
+
+#: i2p2www/pages/global/nav.html:85
+msgid "Tunnel implementation"
+msgstr "Implementazione tunnel"
+
+#: i2p2www/pages/global/nav.html:86
+msgid "Unidirectional tunnels"
+msgstr "Tunnel unidirezionali"
+
+#: i2p2www/pages/global/nav.html:87
+msgid "Old implementation"
+msgstr "Implementazione precedente"
+
+#: i2p2www/pages/global/nav.html:90
+msgid "Naming and addressbook"
+msgstr "Nominativi e rubrica"
+
+#: i2p2www/pages/global/nav.html:94
+msgid "Team"
+msgstr "Squara"
+
+#: i2p2www/pages/global/nav.html:96
+msgid "Hall of Fame"
+msgstr "Galleria dei migliori"
+
+#: i2p2www/pages/global/nav.html:97
+msgid "Academic papers and peer review"
+msgstr "Saggi accademici e recensioni dei peer"
+
+#: i2p2www/pages/global/nav.html:98
+msgid "Presentations, tutorials and articles"
+msgstr "Presentazioni, tutorial e articoli"
+
+#: i2p2www/pages/global/nav.html:99
+msgid "Contact us"
+msgstr "Contattaci"
+
+#: i2p2www/pages/global/nav.html:102
+msgid "Help"
+msgstr "Aiuto"
+
+#: i2p2www/pages/global/nav.html:104
+msgid "FAQ"
+msgstr "FAQ"
+
+#: i2p2www/pages/global/nav.html:105
+msgid "How to browse I2P"
+msgstr "Come sfogliare I2P"
+
+#: i2p2www/pages/global/nav.html:106
+msgid "Glossary"
+msgstr "Glossario"
+
+#: i2p2www/pages/global/nav.html:107
+msgid "Performance"
+msgstr "Prestazioni"
+
+#: i2p2www/pages/global/nav.html:108 i2p2www/pages/site/contact.html:28
+msgid "Forums"
+msgstr "Forum"
+
+#: i2p2www/pages/global/nav.html:111
+msgid "Volunteer"
+msgstr "Volontario"
+
+#: i2p2www/pages/global/nav.html:113
+msgid "Get involved!"
+msgstr "Partecipa anche tu!"
+
+#: i2p2www/pages/global/nav.html:114
+msgid "Develop"
+msgstr "Sviluppo"
+
+#: i2p2www/pages/global/nav.html:117
+msgid "Licenses"
+msgstr "Licenze"
+
+#: i2p2www/pages/global/nav.html:118
+msgid "Release signing keys"
+msgstr "Chiavi di firma per il pubblico"
+
+#: i2p2www/pages/global/nav.html:119
+msgid "Signed keys"
+msgstr "Chiavi firmate"
+
+#: i2p2www/pages/global/nav.html:120
+msgid "Developers keys"
+msgstr "Chiavi per gli sviluppatori"
+
+#: i2p2www/pages/global/nav.html:121
+msgid "Bug tracker"
+msgstr "Tracker dei bug "
+
+#: i2p2www/pages/global/nav.html:124
+msgid "Academic research"
+msgstr "Ricerca accademica"
+
+#: i2p2www/pages/global/nav.html:125
+msgid "Open research questions"
+msgstr "Domande di ricerca aperte"
+
+#: i2p2www/pages/global/nav.html:126
+msgid "Guides"
+msgstr "Guide"
+
+#: i2p2www/pages/global/nav.html:128
+msgid "New developers"
+msgstr "Nuovi sviluppatori"
+
+#: i2p2www/pages/global/nav.html:129
+msgid "Using an IDE with I2P"
+msgstr "Utilizzo di IDE con I2P"
+
+#: i2p2www/pages/global/nav.html:130
+msgid "Developer guidelines and coding style"
+msgstr "Linee guida di sviluppo e stile di programmazione"
+
+#: i2p2www/pages/global/nav.html:131
+msgid "Monotone"
+msgstr "Monotone"
+
+#: i2p2www/pages/global/nav.html:132
+msgid "New translators"
+msgstr "Nuovi traduttori"
+
+#: i2p2www/pages/global/nav.html:135
+msgid "Bounties"
+msgstr "Premi"
+
+#: i2p2www/pages/global/nav.html:136 i2p2www/pages/meetings/index.html:2
+msgid "Meetings"
+msgstr "Riunioni"
+
+#: i2p2www/pages/global/nav.html:137
+msgid "Roadmap"
+msgstr "Roadmap"
+
+#: i2p2www/pages/global/nav.html:138
+msgid "Task list"
+msgstr "Attività"
+
+#: i2p2www/pages/global/nav.html:141
+msgid "Language"
+msgstr "Lingua"
+
+#: i2p2www/pages/meetings/index.html:4
+msgid "I2P Meetings ATOM Feed"
+msgstr "Feed ATOM riunioni I2P"
+
+#: i2p2www/pages/meetings/index.html:7
+msgid "Logs of past I2P meetings"
+msgstr "Log delle riunioni I2P precedenti"
+
+#: i2p2www/pages/meetings/index.html:9
+msgid "Meetings are currently on hold until a more suitable time can be chosen."
+msgstr ""
+"Le riunioni sono attualmente in attesa fino a quando potrà essere scelto "
+"un momento più appropriato."
+
+#: i2p2www/pages/meetings/index.html:13
+#, python-format
+msgid ""
+"If you have something to discuss, please find the developers on IRC in "
+"#i2p-dev.\n"
+"Status updates from developers are also "
+"available."
+msgstr ""
+"Se hai qulcosa da discutere, cerca gli sviluppatori su IRC nel canale "
+"#i2p-dev.\n"
+"Sono disponibili anche gli Aggiornamenti di "
+"stato degli sviluppatori."
+
+#: i2p2www/pages/meetings/show.html:2
+#, python-format
+msgid "I2P Development Meeting %(id)s"
+msgstr "Riunione di sviluppo I2P %(id)s"
+
+#: i2p2www/pages/meetings/show.html:10
+msgid "Full IRC Log"
+msgstr "Log IRC completo"
+
+#: i2p2www/pages/papers/list.html:29
+msgid "By topic"
+msgstr "Per argomento"
+
+#: i2p2www/pages/papers/list.html:35
+msgid "By date"
+msgstr "Per data"
+
+#: i2p2www/pages/papers/list.html:41
+msgid "By author"
+msgstr "Per autore"
+
+#: i2p2www/pages/papers/list.html:83
+#, python-format
+msgid ""
+"Please send new or corrected entries to\n"
+"%(email)s.
\n"
+"If you can, please format them as BibTeX; see our\n"
+"BibTeX source page for examples.
\n"
+"Remember to include URLs if possible:\n"
+"offline papers are less useful."
+msgstr ""
+"Invia voci nuove o corrette a\n"
+"%(email)s.
\n"
+"Se puoi, formattale come BibTeX; consulta la nostra\n"
+"pagina di risorse BibTeX con qualche "
+"esempio.
\n"
+"Ricorda di includere gli URL se possibile:\n"
+"i documenti offline sono meno utili."
+
+#: i2p2www/pages/site/contact.html:2
+msgid "Contact"
+msgstr "Contatto"
+
+#: i2p2www/pages/site/contact.html:4
+msgid "Email"
+msgstr ""
+
+#: i2p2www/pages/site/contact.html:11
+msgid ""
+"Our primary IRC network is the Irc2P network within I2P; a default tunnel"
+" to this network is set up with new router installs.\n"
+" We are also present on multiple standard networks like OFTC,\n"
+" EIN and Freenode.\n"
+" All I2P-related channels on all these network are linked to the main "
+"channels on Irc2P via relay bots."
+msgstr ""
+"Le nostre reti IRC principali sono la rete Irc2 presente all'interno di "
+"I2P; un tunnel predefinito a questa rete viene impostato al momento "
+"dell'installazoine di un nuovo router.\n"
+" Siamo anche prsenti su molteplici reti standard come OFTC,\n"
+" EIN e Freenode.\n"
+" Tutti i canali relativi a I2P su tutte queste reti sono collegati ai "
+"canali principali su Irc2P tramite dei bot di ripetizione."
+
+#: i2p2www/pages/site/contact.html:19
+msgid "Channel list:"
+msgstr "Elenco canali:"
+
+#: i2p2www/pages/site/contact.html:21
+msgid "General i2p discussion"
+msgstr "Discussione generali su i2p"
+
+#: i2p2www/pages/site/contact.html:22
+msgid "Offtopic"
+msgstr "Off-topic"
+
+#: i2p2www/pages/site/contact.html:23
+msgid "Development talk"
+msgstr "Conferenza di sviluppo"
+
+#: i2p2www/pages/site/contact.html:24
+msgid "Help channel"
+msgstr "Canale di aiuto"
+
+#: i2p2www/pages/site/contact.html:29
+#, python-format
+msgid ""
+"Most of the discussion about I2P's development happens on the I2P developer forum. This is usually the best"
+" place to start with inquiries, if the dev IRC channel is inactive."
+msgstr ""
+"La maggior parte delle discussioni sullo sviluppo di I2P ha luogo sul forum degli sviluppatori I2P. Questo è "
+"solitamente il miglior luogo dove cominciare a fare domande, se il canale"
+" IRC degli sviluppatori non è attivo."
+
+#: i2p2www/pages/site/contact.html:33
+msgid "Mailing lists"
+msgstr "Liste di distribuzione"
+
+#: i2p2www/pages/site/contact.html:34
+msgid ""
+"I2P does have a mailing list, but it is rarely used as the current small "
+"team of developers prefer to communicate via IRC or the developer forum. "
+"This may change in future."
+msgstr ""
+"I2P dispone di una lista di distribuzione, ma viene raramente usata "
+"perché il team di sviluppo attuale è relativamente piccolo e preferisce "
+"comunicare tramite IRC o sul forum. Questa situazione potrebbe cambiare "
+"in futuro."
+
+#: i2p2www/pages/site/contact.html:39
+msgid "Subscribing"
+msgstr "Iscrizione"
+
+#: i2p2www/pages/site/contact.html:40
+msgid ""
+"To subscribe to a mailing list, go to the list information page (linked "
+"below) and fill out the form. I2P-internal email addresses "
+"(foobar@mail.i2p) can be used."
+msgstr ""
+"Per iscriversi a una lista di distribuzione, accedi alla pagina "
+"informativa della lista (il link è indicato qui sotto) e compila il "
+"modulo. Possono essere usati indirizzi di posta elettronica interni di "
+"I2P (foobar@mail.i2p)."
+
+#: i2p2www/pages/site/contact.html:44
+msgid "Unsubscribing"
+msgstr "Annullamento dell'iscrizione"
+
+#: i2p2www/pages/site/contact.html:45
+msgid ""
+"To unsubscribe from a mailing list or edit your subscription options, go "
+"to the list information page (linked below) and enter your subscription "
+"email address."
+msgstr ""
+"Per annullare la propria iscrizione alla lista di distribuzione o "
+"modificare le opzioni di iscrizione, accedi alla pagina informativa della"
+" lista (il link è indicato qui sotto) e inserisci l'indirizzo di posta "
+"elettronica usato per iscriverti."
+
+#: i2p2www/pages/site/contact.html:49
+msgid "Lists"
+msgstr "Liste"
+
+#: i2p2www/pages/site/contact.html:52
+msgid "Archive"
+msgstr "Archivio"
+
+#: i2p2www/pages/site/contact.html:53
+msgid ""
+"General I2P discussion - anything that doesn't fit in a different list "
+"goes here."
+msgstr ""
+"Discussione generale I2P, qualunque cosa che non si adatta a una lista "
+"diversa finisce qui."
+
+#: i2p2www/pages/site/contact.html:59
+msgid ""
+"You don't like mailing lists? Then this is for you. All mailing lists are"
+" available via NNTP as well."
+msgstr ""
+"Non ti piacciono le liste di distribuzione? Allora questa opzione fa per "
+"te: tutte le liste di distribuzione sono disponibili anche tramite NNTP."
+
+#: i2p2www/pages/site/contact.html:64
+msgid "Group-List-mapping:"
+msgstr "Mappatura gruppi-liste:"
+
+#: i2p2www/pages/site/contact.html:68
+msgid "Servers:"
+msgstr "Server:"
+
+#: i2p2www/pages/site/faq.html:2
+msgid "Frequently Asked Questions"
+msgstr "Domande poste frequentemente"
+
+#: i2p2www/pages/site/faq.html:4
+msgid "Index"
+msgstr "Indice"
+
+#: i2p2www/pages/site/faq.html:7
+msgid "General"
+msgstr "Generale"
+
+#: i2p2www/pages/site/faq.html:9 i2p2www/pages/site/faq.html:51
+msgid "What systems will I2P run on?"
+msgstr "Su quali sistemi gira I2P?"
+
+#: i2p2www/pages/site/faq.html:10
+msgid "Whats an \"eepsite\" and how do I configure my browser so I can use them?"
+msgstr "Che cos'è un \"eepsite\" e come configura il browser per accedervi?"
+
+#: i2p2www/pages/site/faq.html:11 i2p2www/pages/site/faq.html:264
+msgid "My router has very few active peers, is this OK?"
+msgstr "Il mio router ha pochissimi peer attivi, è normale?"
+
+#: i2p2www/pages/site/faq.html:12 i2p2www/pages/site/faq.html:499
+msgid "What do the Active x/y numbers mean in the router console?"
+msgstr "Che cosa significano i numeri relativi a x/y attivi nel console router?"
+
+#: i2p2www/pages/site/faq.html:13 i2p2www/pages/site/faq.html:226
+msgid ""
+"My active peers / known peers / participating tunnels / connections / "
+"bandwidth vary dramatically over time! Is anything wrong?"
+msgstr ""
+"I miei peer attivi / peer conosciuti / tunnel partecipanti / connessioni "
+"/ larghezza di banda variano in modo drammatico nel tempo! C'è qualcosa "
+"che non va?"
+
+#: i2p2www/pages/site/faq.html:14 i2p2www/pages/site/faq.html:349
+msgid "Is using an outproxy safe?"
+msgstr "L'utilizzo di un outproxy è sicuro?"
+
+#: i2p2www/pages/site/faq.html:15 i2p2www/pages/site/faq.html:375
+msgid "Most of the eepsites within I2P are down?"
+msgstr "La maggior parte degli eepsite all'interno di I2P non funziona?"
+
+#: i2p2www/pages/site/faq.html:16 i2p2www/pages/site/faq.html:528
+msgid "What ports does I2P use?"
+msgstr "Quali porte usa I2P?"
+
+#: i2p2www/pages/site/faq.html:17
+msgid "Why is I2P listening for connections on port 32000?"
+msgstr "Perché I2P si mette in ascolto per le connessioni sulla porta 32000?"
+
+#: i2p2www/pages/site/faq.html:18 i2p2www/pages/site/faq.html:62
+msgid "I think I found a bug, where can I report it?"
+msgstr "Credo di aver trovare un bug, dove lo segnalo?"
+
+#: i2p2www/pages/site/faq.html:19 i2p2www/pages/site/faq.html:108
+msgid "What happened to *.i2p.net? What happened to jrandom? Is I2P dead?"
+msgstr "Che cos'è successo a *.i2p.net? Che cos'è successo a jrandom? I2P è morto?"
+
+#: i2p2www/pages/site/faq.html:20 i2p2www/pages/site/faq.html:846
+msgid "I have a question!"
+msgstr "Ho una domanda!"
+
+#: i2p2www/pages/site/faq.html:22
+msgid "Setup"
+msgstr "Impostazione"
+
+#: i2p2www/pages/site/faq.html:24 i2p2www/pages/site/faq.html:233
+msgid ""
+"My router has been up for several minutes and has zero or very few "
+"connections"
+msgstr ""
+"Il mio router è stato impostato da diversi minuti e ha zero o pochissime "
+"connessioni."
+
+#: i2p2www/pages/site/faq.html:25 i2p2www/pages/site/faq.html:391
+msgid "Why is I2P so slow?"
+msgstr "Perché I2P è così lento?"
+
+#: i2p2www/pages/site/faq.html:26 i2p2www/pages/site/faq.html:79
+msgid ""
+"I'm missing lots of hosts in my addressbook. What are some good "
+"subscription links?"
+msgstr ""
+"Mi mancano un sacco di host nella rubrica. Potete suggerirmi qualche buon"
+" link a cui iscrivermi?"
+
+#: i2p2www/pages/site/faq.html:27 i2p2www/pages/site/faq.html:384
+msgid "How do I set up my own eepsite?"
+msgstr "Come posso impostare il mio eepsite personale?"
+
+#: i2p2www/pages/site/faq.html:28 i2p2www/pages/site/faq.html:417
+msgid "Bittorrent / I2PSnark / Azureus I2P Plugin Questions?"
+msgstr "Domande sui plugin Bittorrent / I2PSnark / Azureus per I2P?"
+
+#: i2p2www/pages/site/faq.html:29 i2p2www/pages/site/faq.html:424
+msgid "How do I connect to IRC within I2P?"
+msgstr "Come mi connetto a IRC all'interno di I2P?"
+
+#: i2p2www/pages/site/faq.html:30 i2p2www/pages/site/faq.html:282
+msgid "I can't access regular Internet sites through I2P."
+msgstr "Non riesco ad accedere a siti Internet normali tramite I2P."
+
+#: i2p2www/pages/site/faq.html:31 i2p2www/pages/site/faq.html:297
+msgid "I can't access https:// or ftp:// sites through I2P."
+msgstr "Non riesco ad accedere a siti https:// o ftp:// tramite I2P."
+
+#: i2p2www/pages/site/faq.html:32 i2p2www/pages/site/faq.html:507
+msgid "Is it possible to use I2P as a SOCKS proxy?"
+msgstr "È possibile usare I2P come proxy SOCKS?"
+
+#: i2p2www/pages/site/faq.html:33 i2p2www/pages/site/faq.html:490
+msgid "How do I configure my browser?"
+msgstr "Come devo configurare il browser?"
+
+#: i2p2www/pages/site/faq.html:34 i2p2www/pages/site/faq.html:435
+msgid ""
+"How can I access the web console from my other machines or password "
+"protect it?"
+msgstr ""
+"Come posso accedere alla web console dagli altri miei computer o "
+"proteggerla con una password?"
+
+#: i2p2www/pages/site/faq.html:35 i2p2www/pages/site/faq.html:475
+msgid "How can I use applications from my other machines?"
+msgstr "Come posso usare le applicazioni dagli altri miei computer?"
+
+#: i2p2www/pages/site/faq.html:36 i2p2www/pages/site/faq.html:749
+msgid "How do I reseed manually?"
+msgstr "Come posso effettuare il reseed manualmente?"
+
+#: i2p2www/pages/site/faq.html:37 i2p2www/pages/site/faq.html:125
+msgid "My router is using too much CPU?!?"
+msgstr "Il mio router usa troppa CPU?!?"
+
+#: i2p2www/pages/site/faq.html:39
+msgid "Misconception"
+msgstr "Equivoci"
+
+#: i2p2www/pages/site/faq.html:41 i2p2www/pages/site/faq.html:367
+msgid ""
+"How do I access IRC, BitTorrent, or other services on the regular "
+"Internet?"
+msgstr ""
+"Come posso accedere a IRC, Bittorrent o altri servizi sull'Internet "
+"normale?"
+
+#: i2p2www/pages/site/faq.html:42
+msgid ""
+"Is my router an \"exit node\"(outproxy) to the regular Internet? I don't "
+"want it to be."
+msgstr ""
+"Il mio router è un \"nodo di uscita\" (outproxy) sull'Internet normale? "
+"Non voglio che lo sia."
+
+#: i2p2www/pages/site/faq.html:43 i2p2www/pages/site/faq.html:189
+msgid ""
+"I am opposed to certain types of content. How do I keep from "
+"distributing, storing, or accessing them?"
+msgstr ""
+"Sono contro a determinati tipi di contenuti. Come posso evitare di "
+"distribuirli, immagazzinarli o accedervi?"
+
+#: i2p2www/pages/site/faq.html:45
+msgid "Errors and Their Solutions"
+msgstr "Errori e relative soluzioni"
+
+#: i2p2www/pages/site/faq.html:47 i2p2www/pages/site/faq.html:785
+msgid ""
+"I'm using FreeBSD and when I start I2P I receive an error about "
+"libm.so.4!"
+msgstr ""
+"Uso FreeBSD e quando avvio I2P ricevo un errore relativo a "
+"libm.so.4!"
+
+#: i2p2www/pages/site/faq.html:48
+msgid ""
+"In wrapper.log I see an error stating Protocol family "
+"unavailable when I2P is loading"
+msgstr ""
+"Nel wrapper.log osservo un errore relativo alla "
+"famiglia di protocolli non disponibile quando I2P viene "
+"caricato"
+
+#: i2p2www/pages/site/faq.html:52 i2p2www/pages/site/faq.html:63
+#: i2p2www/pages/site/faq.html:80 i2p2www/pages/site/faq.html:109
+#: i2p2www/pages/site/faq.html:126 i2p2www/pages/site/faq.html:190
+#: i2p2www/pages/site/faq.html:227 i2p2www/pages/site/faq.html:234
+#: i2p2www/pages/site/faq.html:265 i2p2www/pages/site/faq.html:274
+#: i2p2www/pages/site/faq.html:283 i2p2www/pages/site/faq.html:298
+#: i2p2www/pages/site/faq.html:350 i2p2www/pages/site/faq.html:368
+#: i2p2www/pages/site/faq.html:376 i2p2www/pages/site/faq.html:385
+#: i2p2www/pages/site/faq.html:392 i2p2www/pages/site/faq.html:418
+#: i2p2www/pages/site/faq.html:425 i2p2www/pages/site/faq.html:436
+#: i2p2www/pages/site/faq.html:476 i2p2www/pages/site/faq.html:483
+#: i2p2www/pages/site/faq.html:491 i2p2www/pages/site/faq.html:500
+#: i2p2www/pages/site/faq.html:508 i2p2www/pages/site/faq.html:529
+#: i2p2www/pages/site/faq.html:737 i2p2www/pages/site/faq.html:750
+#: i2p2www/pages/site/faq.html:786 i2p2www/pages/site/faq.html:818
+#: i2p2www/pages/site/faq.html:847
+msgid "link"
+msgstr "collegamento"
+
+#: i2p2www/pages/site/faq.html:53
+#, python-format
+msgid ""
+"While I2P has been reported to run PCs as meagre as a low-end Pentium II "
+"with 64 MB of RAM, you'll have a much better experience on a Pentium III "
+"(or better) with 128MB of RAM (or more). A chart "
+"comparing the performance of the various JREs can be found at %(chart)s, but in short: it's at all possible, use"
+" Sun/Oracle Java or OpenJDK."
+msgstr ""
+"Sebbene ci siano riscontri di I2P funzionante su PC con basse prestazioni"
+" addirittura come i Pentium II con 64 MB di RAM, l'esperienza sarà "
+"migliore sui Pentium III (o superiori) con 128 MB di RAM (o di più). Un "
+"grafico con il confronto delle prestazioni dei "
+"vari ambienti JRE può essere repirto all'indirizzo %(chart)s, ma per dirla in breve: se possibile, "
+"usa Sun/Oracle Java o OpenJDK."
+
+#: i2p2www/pages/site/faq.html:57
+msgid ""
+"I2P has been tested on Windows, Linux, FreeBSD (see the note below), OSX, and OpenSolaris. There is work "
+"underway to bring I2P to the Android platform."
+msgstr ""
+"I2P è stato testato su Windows, Linux, FreeBSD (leggere la nota qui sotto), OSX e OpenSolaris. Esistono progetti "
+"in corso per portare I2P sulla piattaforma Android."
+
+#: i2p2www/pages/site/faq.html:65
+msgid "Here are some places, pick one or more."
+msgstr "Ecco qualche luogo, scegline uno o di più."
+
+#: i2p2www/pages/site/faq.html:71
+msgid "Discuss with the developers on IRC in #i2p-dev"
+msgstr "Discuti con gli sviluppatori su IRC nel canale #i2p-dev"
+
+#: i2p2www/pages/site/faq.html:75
+msgid "Please include relevant information from the router logs and wrapper logs."
+msgstr "Includi le relative informazioni prese dai log del router e del wrapper."
+
+#: i2p2www/pages/site/faq.html:81
+msgid ""
+"The default subscription is to http://www.i2p2.i2p/hosts.txt which is "
+"updated rarely.\n"
+"If you don't have another subscription, you may often have to use "
+"\"jump\" links which\n"
+"is annoying."
+msgstr ""
+"L'iscrizione predefinita è a http://www.i2p2.i2p/hosts.txt che viene "
+"raramente aggiornato.\n"
+"Se non disponi di un'altra iscrizione, potresti dover usare spesso i "
+"collegamenti \"jump\", il che è\n"
+"seccante."
+
+#: i2p2www/pages/site/faq.html:87
+msgid ""
+"Here are some other public addressbook subscription links. You may wish "
+"to add one or two\n"
+"to your susidns "
+"subscription list.\n"
+"You don't need to add all of them, as they sync with each other "
+"periodically.\n"
+"The links using a cgi-bin application employ various strategies to "
+"minimize\n"
+"the number of duplicate addresses delivered, so they should be more "
+"efficient.\n"
+"Note that subscribing to a hosts.txt service is an act of \"trust\", as a"
+" malicious\n"
+"subscription could give you incorrect addresses. So think about whether "
+"you\n"
+"want to trust any of these.\n"
+"The operators of these services may have various policies for listing "
+"hosts.\n"
+"Presence on this list does not imply endorsement."
+msgstr ""
+"Ecco qualche altro collegamento per la rubrica pubblica. Potresti "
+"aggioungerne uno o due\n"
+"al tuo elenco"
+" di iscrizioni susidns.\n"
+"Non c'è bisogno di aggiungerli tutti, perché si sincronizzano l'uno con "
+"l'altro periodicamente.\n"
+"I collegamenti che usano un applicazione cgi-bin application si avvalgono"
+" di svariate strategie per minimizzare\n"
+"il numero di indirizzi duplicati, per cui dovrebbero essere più "
+"efficienti.\n"
+"Ricorda che iscriversi a un servizio hosts.txt è un atto di \"fiducia\" "
+"perché un'iscrizione\n"
+"malevola potrebbe fornirti indirizzi sbagliati. Per cui rifletti se "
+"intendi\n"
+"fidarti o no.\n"
+"Gli operatori di tali servizi potrebbero avere diverse regole per gli "
+"host elencati.\n"
+"La presenza di un sito in questa lista non implica approvazione."
+
+#: i2p2www/pages/site/faq.html:110
+msgid ""
+"Jrandom was the lead developer of I2P and\n"
+"Syndie for several years.\n"
+"We do not know if or when jrandom will return.\n"
+"The *.i2p.net domains were left in a non-functioning state after a power\n"
+"outage at the hosting company."
+msgstr ""
+"Jrandom è stato lo sviluppatore capo di I2P e\n"
+"Syndie per diversi anni.\n"
+"Non sappiamo se jrandom farà ritorno o no.\n"
+"I dominii *.i2p.net sono stati lasciati in uno stato di non funzionamento"
+" dopo un blackout\n"
+"capitato all'azienda che si occupa del loro hosting."
+
+#: i2p2www/pages/site/faq.html:118
+#, python-format
+msgid ""
+"See this page for jrandom's parting message "
+"and additional information\n"
+"on the migration of *.i2p.net to this website."
+msgstr ""
+"Consulta questa pagina con il messaggio di "
+"addio di jrandom e informazioni aggiuntive\n"
+"sulla migrazione di *.i2p.net a questo sito web."
+
+#: i2p2www/pages/site/faq.html:123
+msgid "I2P remains in active development."
+msgstr "I2P rimane in attivo sviluppo."
+
+#: i2p2www/pages/site/faq.html:127
+msgid "There are many possible causes of high CPU usage. Here is a checklist:"
+msgstr ""
+"Esistono numerose possibile cause di un elevato utilizzo della CPU. Ecco "
+"un elenco di controllo:"
+
+#: i2p2www/pages/site/faq.html:132
+msgid ""
+"Try to use either OpenJDK or Sun/Oracle Java if it's available for your "
+"system. You can check \n"
+"which version of java you have installed by typing java "
+"-version at a \n"
+"command/shell prompt. Performance tends to suffer with other "
+"implementations of java."
+msgstr ""
+"Prova a usare OpenJDK oppure Java di Sun/Oracle se sono disponibili sul "
+"tuo sistema. Puoi controllare \n"
+"la versione di java installata digitando java -version al "
+"prompt dei \n"
+"comandi o in un terminale. Le prestazioni tendono a soffrire con "
+"implementazioni di java diverse."
+
+#: i2p2www/pages/site/faq.html:139
+msgid ""
+"Are you running a BitTorrent client over I2P? Try reducing the number of "
+"torrents, the bandwidth limits,\n"
+"or try turning it off completely to see if that helps."
+msgstr ""
+"Hai un client BitTorrent in esecuzione su I2P? Prova a ridurre il numero "
+"di torrent, i limiti di banda\n"
+"oppure spegnerlo completamente per vedere se aiuta a risolvere il "
+"problema."
+
+#: i2p2www/pages/site/faq.html:145
+msgid ""
+"Are your bandwidth limits set too high? It is possible that too much "
+"traffic is going through your\n"
+"I2P router and it is overloaded. Try reducing the setting for share "
+"bandwidth percentage on the configuration page."
+msgstr ""
+"I limiti della larghezza di banda sono impostati troppo in alto? È "
+"possibile che stia passando troppo traffico nel tuo\n"
+"router I2P che è quindi sovraccarico. Prova ad abbassare l'impostazione "
+"dellapercentuale di condivisione della banda nella pagina di configurazione."
+
+#: i2p2www/pages/site/faq.html:150
+msgid ""
+"Make sure that you're running the latest version of I2P to get the "
+"benefits of increased performance and bug fixes."
+msgstr ""
+"Assicurati di avere la versione più recente di I2P in esecuzione per "
+"avvantaggiarti delle prestazioni migliorate e dei problemi risolti."
+
+#: i2p2www/pages/site/faq.html:155
+msgid ""
+"Has enough memory been set aside for use by I2P? Look at the memory graph"
+" on the graphs page to see\n"
+"if the memory usage is \"pegged\"—the JVM is spending most of its "
+"time in\n"
+"garbage collection. Increase the setting "
+"wrapper.java.maxmemory in wrapper.config."
+msgstr ""
+"C'è memoria sufficiente destinata all'uso di I2P? Osserva il grafico "
+"della memoria nella pagina dei "
+"grafici per controllare se\n"
+"l'uso di memoria è \"fisso\"—la JVM passa la maggior parte del "
+"proprio tempo nell'attività di\n"
+"garbage collection. Aumenta l'impostazione "
+"wrapper.java.maxmemory in wrapper.config."
+
+#: i2p2www/pages/site/faq.html:162
+msgid ""
+"Is the CPU usage simply higher than you would like, or is it pegged at "
+"100% for a long time?\n"
+"If it's pegged, this could be a bug. Look in the logs for clues."
+msgstr ""
+"L'utilizzo della CPU è semplicemente più elevato di quanto vorresti "
+"oppure rimane fisso su 100% per un periodo di tempo molto lungo?\n"
+"Se è fisso, ciò potrebbe essere dovuto a un bug. Cerca nei log per "
+"eventuali indizi."
+
+#: i2p2www/pages/site/faq.html:168
+#, python-format
+msgid ""
+"You may be using the Java-based BigInteger library instead of the native "
+"version,\n"
+"especially if you are running on a new or unusual OS or hardware "
+"(OpenSolaris, mipsel, etc.).\n"
+"See the jbigi page for instructions on\n"
+"diagnosing, building, and testing methods."
+msgstr ""
+"Forse stai usando la libreria BigInteger basata su Java invece della "
+"versione originale,\n"
+"specialmente se stai usandoo un sistema operativo o un hardware insolito "
+"o nuovo (OpenSolaris, mipsel, ecc.).\n"
+"Consulta la pagina jbigi per istruzioni sui\n"
+"metodi di diagnosi, compilazione e collaudo."
+
+#: i2p2www/pages/site/faq.html:176
+msgid ""
+"If your native jbigi library is working fine, the biggest user of\n"
+"CPU may be routing traffic for participating tunnels. This uses CPU\n"
+"because at each hop a layer of encryption must be decoded.\n"
+"You can limit participating traffic in two ways - by reducing the\n"
+"share bandwidth on\n"
+"confignet.jsp,\n"
+"or by setting router.maxParticipatingTunnels=nnn on\n"
+"configadvanced.jsp."
+msgstr ""
+"Se la tua libreria jbigi originale funziona senza problemi, l'utente più "
+"esoso di \n"
+"CPU potrebbe instradare il traffico per i tunnel partecipanti. Questo fa "
+"uso di CPU\n"
+"perché con ciascun salto uno strato di cifratura deve essere "
+"decodificato.\n"
+"Puoi limitare il traffico partecipanti in due modi: riducendo la\n"
+"banda condivisa su\n"
+"confignet.jsp,\n"
+"oppure impostando router.maxParticipatingTunnels=nnn su\n"
+"configadvanced.jsp."
+
+#: i2p2www/pages/site/faq.html:191
+msgid ""
+"Hmm. I2P is an anonymous network, so that's a tricky one.\n"
+"I2P is designed to withstand censorship, providing a means for everyone "
+"to communicate freely. \n"
+"The best way to keep your PC free of (encrypted) traffic that you dislike"
+" is to not use I2P.\n"
+"Freedom of speech has some costs.\n"
+"But let's address your question in three parts:"
+msgstr ""
+"Uhm. I2P è una rete anonima, quindi questa è una questione complicata.\n"
+"I2P è progettato per resistere alla censura offrendo un mezzo che tutti "
+"possono usare per comunicare liberamente. \n"
+"Il modo migliore di tenere il tuo computere libero da traffico (criptato)"
+" che non è di tuo gradimento è quello di non usare affatto I2P.\n"
+"La libertà di parola ha dei costi.\n"
+"Ma vediamo di analizzare il problema dividendolo in tre parti:"
+
+#: i2p2www/pages/site/faq.html:200
+msgid ""
+"Distribution - All traffic on I2P is encrypted in multiple layers."
+" You don't know\n"
+"a message's contents, source, or destination.\n"
+"All traffic you route is internal to the I2P network, you are not an exit node (outproxy).\n"
+"Your only alternative is to refuse to route\n"
+"any traffic, by setting your share bandwidth or maximum "
+"participating tunnels to 0 (see above).\n"
+"It would be nice if you didn't do this, you should help the network by "
+"routing traffic for others.\n"
+"Over 95% of users route traffic for others."
+msgstr ""
+"Distribuzione - Tutto il traffico I2P è cifrato a strati multipli."
+" Non si può sapere \n"
+"il contenuto di un messaggio, la sua fonte e la sua destinazione.\n"
+"Tutto il traffico che indirizzi è interno alla rete I2P, tu non sei un nodo di uscita (outproxy).\n"
+"La tua unica alternativa è di rifiutare di indirizzare\n"
+"qualsivoglia traffico, impostando a 0 la larghezza di banda "
+"condivisa o il numero massimo di tunnel partecipanti (vedi sopra).\n"
+"Ti saremmo grati se evitassi di assumere un comportamento del genere, "
+"dovresti invece dare una mano alla rete indirizzando il traffico per "
+"altri.\n"
+"Più del 95% degli utenti lo fa."
+
+#: i2p2www/pages/site/faq.html:211
+msgid ""
+"Storage - I2P does not do distributed storage of content. You must"
+" be thinking of\n"
+"Freenet.\n"
+"Nobody's content is being stored on your computer by running I2P."
+msgstr ""
+"Deposito - I2P non effettua la distribuzione di depositi di "
+"contenuti. Devi pensare a \n"
+"Freenet.\n"
+"Sul tuo computer non viene depositato il contenuto di nessuno eseguendo "
+"I2P."
+
+#: i2p2www/pages/site/faq.html:218
+msgid ""
+"Access - If there are some eepsites you don't like, don't go "
+"there.\n"
+"Or, use a blocking proxy like Privoxy or some type of \"net nanny\"."
+msgstr ""
+"Accesso - Se ci sono degli eepsite che non ti piacciono, non "
+"visitarli.\n"
+"Altrimenti usa un proxy di blocco come Privoxy o qualche tipo di \"balia "
+"della rete\"."
+
+#: i2p2www/pages/site/faq.html:228
+msgid ""
+"No. This is normal.\n"
+"All routers adjust dynamically to changing network conditions and demands."
+msgstr ""
+"No. Questo è normale.Tutti i router si regolano in maniera dinamica al "
+"cambiare delle condizioni della rete e delle richieste."
+
+#: i2p2www/pages/site/faq.html:235
+msgid ""
+"You may need to reseed your I2P router. With recent versions of I2P you "
+"can go to http://localhost:7657/configreseed"
+" and click the Save Changes and Reseed Now button. If this "
+"method doesn't work—or you're using a very old version—you "
+"may need to reseed manually."
+msgstr ""
+"Potrebbe essere necessario fare il reseed del tuo router I2P. Con le "
+"versioni recenti di I2P, puoi accedere a http://localhost:7657/configreseed"
+" e fare clic sul pulsante Salva modifiche e fail il reseed "
+"adesso. Se questo metodo non funziona—o se stai usando una "
+"versione molto vecchia—potrebbe rendersi necessario fare il reseed manualmente."
+
+#: i2p2www/pages/site/faq.html:238
+msgid ""
+"The reseed URL changed a few years ago. If this is your first install and"
+" you have installed\n"
+"an old (0.6.1.30 or earlier) release, or\n"
+"you have not run I2P in a long time, you must change the URL and then\n"
+"click \"Reseed\" on the console to find other routers.\n"
+"After your router is running,\n"
+"on configadvanced.jsp,"
+"\n"
+"add the line i2p.reseedURL=http://netdb.i2p2.de/\n"
+"OR i2p.reseedURL=http://i2pdb.tin0.de/netDb/ (either should "
+"work),\n"
+"then click \"Apply\", then click the \"reseed\" link on the left."
+msgstr ""
+"L'URL del reseed cambiò qualche anno fa. Se questa è la tua prima "
+"installazione e hai installato\n"
+"auan versione vecchia (0.6.1.30 o precedente), oppure\n"
+"se non hai eseguito I2P da tanto tempo, devi cambiare l'URL e quindi\n"
+"fare clic su \"Reseed\" nella console per trovare altri router.\n"
+"Una volta che il tuo router è in esecuzione,\n"
+"in configadvanced.jsp,"
+"\n"
+"aggiungi la riga i2p.reseedURL=http://netdb.i2p2.de/\n"
+"OPPURE i2p.reseedURL=http://i2pdb.tin0.de/netDb/ (sia una che "
+"l'latra dovrebbero funzionare),\n"
+"quindi fai clic su \"Applica\", e sul link \"reseed\" sulla sinistra."
+
+#: i2p2www/pages/site/faq.html:249
+#, python-format
+msgid ""
+"This works if you are running 0.6.1.27 or later.\n"
+"If you are running release 0.6.1.31 or later, you probably don't need to "
+"do this.\n"
+"If you are running release 0.6.1.26 or earlier, either follow the\n"
+"manual reseed instructions below\n"
+"or install the latest release.\n"
+"Possible alternate method - add\n"
+"wrapper.java.additional.5=-Di2p.reseedURL=http://netdb.i2p2.de/\n"
+"to wrapper.config, shutdown the router completely, then start again, then"
+" click \"reseed\".\n"
+"Let us know if this works."
+msgstr ""
+"Questo funziona se stai eseguendo la versione 0.6.1.27 o successiva.\n"
+"Se usi la versione 0.6.1.31 o successiva, probabilmente non ti serve.\n"
+"Se stai eseguendo la versinoe 0.6.1.26 o precedente, segui le\n"
+"istruzioni per reseed manuale qui sotto\n"
+"oppure installa la versione più "
+"recente.\n"
+"Un possibile metodo alternativo - aggiungi\n"
+"wrapper.java.additional.5=-Di2p.reseedURL=http://netdb.i2p2.de/\n"
+"a wrapper.config, arresta completamente il router, quindi riavvialo e fai"
+" clic su \"reseed\".\n"
+"Facci sapere se funziona."
+
+#: i2p2www/pages/site/faq.html:260
+#, python-format
+msgid ""
+"...but you *really* should upgrade to "
+"the latest version."
+msgstr ""
+"...ma dovresti *davvero* aggiornare "
+"passando alla versione più recente."
+
+#: i2p2www/pages/site/faq.html:266
+msgid ""
+"If your router has 10 or more active peers, everything is fine. Changes "
+"in releases 0.6.1.31 and 0.6.1.32 improved the\n"
+"efficiency of the router and effectively reduced the number of active "
+"peers.\n"
+"The router should maintain connections to a few peers at all "
+"times.\n"
+"The best way to stay \"better-connected\" to the network is to share more bandwidth."
+msgstr ""
+"Se il tuo router ha 10 o più peer attivi, tutto va bene. Le modifiche "
+"nelle versioni 0.6.1.31 e 0.6.1.32 hanno migliorato\n"
+"l'efficienza del router e hanno ridotto in modo efficace il numero di "
+"peer attivi.\n"
+"Il router dovrebbe mantenere le connessioni verso pochi peer in "
+"ogni momento.\n"
+"Il modo migliore per avere una \"connessione migliore\" alla rete è di condividere più banda."
+
+#: i2p2www/pages/site/faq.html:273
+msgid ""
+"Is my router an \"exit node\" to the regular Internet? I don't want it to"
+" be."
+msgstr ""
+"Il mio router è un \"nodo di uscita\" sull'Internet normale? Non voglio "
+"che lo sia."
+
+#: i2p2www/pages/site/faq.html:275
+msgid ""
+"No. Unlike Tor,\n"
+"\"exit nodes\" or \"outproxies\" are not an inherent part of the network."
+"\n"
+"Only volunteers who set up and run separate applications will relay "
+"traffic to the regular Internet.\n"
+"There are very, very few of these."
+msgstr ""
+"No. A differenza di Tor,\n"
+"i \"nodi di uscita\" o \"outproxies\" non sono una parte intrinseca della"
+" rete.\n"
+"Solo i volontari che impostano ed eseguono applicazioni separate "
+"ripeteranno il traffico verso la rete Internet solita.\n"
+"Ne esitono pochi, anzi, pochissimi."
+
+#: i2p2www/pages/site/faq.html:284
+msgid ""
+"See above. There are very few HTTP \"outproxies\", they are not an "
+"inherent part of the network,\n"
+"and they may not be up.\n"
+"In addition, the old outproxies squid.i2p, true.i2p, and krabs.i2p have "
+"vanished.\n"
+"The only outproxy at the moment is false.i2p.\n"
+"To use it, edit your i2ptunnel "
+"settings for eepProxy\n"
+"and set your outproxy list to 'false.i2p' (only).\n"
+"Then stop and restart the eepProxy.\n"
+"If it doesn't work, the outproxy is not up. It is not I2P's fault.\n"
+"If your primary reason to use an anonymous network is to anonymously "
+"access sites\n"
+"on the regular Internet, you should probably try Tor."
+msgstr ""
+"Vedi sopra. Esistono pochissimi \"outproxy\" HTTP \"outproxies\", non "
+"fanno intrinsecamente parte della rete\n"
+"e potrebbero non funzionare.\n"
+"Inoltre, i vecchi outproxy squid.i2p, true.i2p, e krabs.i2p sono "
+"scomparsi.\n"
+"L'unico outproxy al momento è false.i2p.\n"
+"Per usarlo, modifica le tue impostazioni "
+"i2ptunnel per eepProxy\n"
+"e imposta il tuo elenco di outproxy su 'false.i2p' (only).\n"
+"Quindi interrompi e riavvia l'eepProxy.\n"
+"Se non funziona, significa che l'outproxy non funziona. Non è colpa di "
+"I2P.\n"
+"Se il motivo principale per usare una rete anonima è quello di accedere "
+"ai siti anonimamente\n"
+"sull'Internet normale, forse dovresti provare Tor."
+
+#: i2p2www/pages/site/faq.html:299
+msgid ""
+"Within I2P, there is no need for HTTPS, as all traffic is encrypted end-"
+"to-end.\n"
+"FTP is not supported for technical reasons."
+msgstr ""
+"All'interno di I2P non c'è bisogno di HTTPS perché tutto il traffico è "
+"criptato punto-a-punto.\n"
+"FTP non è supportato per motivi tecnici."
+
+#: i2p2www/pages/site/faq.html:303
+msgid ""
+"There are no FTP \"outproxies\" to the Internet—it may not even be "
+"possible to set up one.\n"
+"Any other kind of outproxy may work if it's set up with a standard "
+"tunnel. \n"
+"If you would like to set up some type of outproxy, carefully research the"
+" potential risks.\n"
+"The I2P community may or may not be able to help with the technical "
+"aspects, feel free to ask."
+msgstr ""
+"Non ci sono \"outproxy\" FTP verso Internet—potrebbe addirittura "
+"non essere possibile impostarne uno.\n"
+"Qualunque altro tipo di outproxy potrebbe funzionare se viene impostato "
+"con il tunnel standard. \n"
+"Se desideri impostare qualche tipo di outproxy, cerca con attenzione i "
+"rischi potenziali in cui potresti incorrere.\n"
+"La comunità I2P potrebbe, o non potrebbe, essere in grado di darti una "
+"mano con gli aspetti tecnici, sentiti libero di porre domande."
+
+#: i2p2www/pages/site/faq.html:309
+msgid ""
+"As explained several times above, any existing outproxy isn't a core part"
+" of the network.\n"
+"They are services run by individuals and they may or may not\n"
+"be operational at any given time."
+msgstr ""
+"Come spiegato tante volte in precedenza, qualunque outproxy esistente non"
+" fa parte della rete in quanto tale.\n"
+"Si tratta di servizi messi a disposizione da singoli individue e, come "
+"tali,\n"
+"potrebbero essere operativi o no in un dato momento."
+
+#: i2p2www/pages/site/faq.html:314
+msgid ""
+"Update: Thanks to the work of h2ik, there is an https outproxy "
+"available for use via I2P. Starting with I2P 0.8.4 the tunnel is "
+"configured out of the box.
\n"
+"In case the https outproxy is not available in your version of I2P, you "
+"can add it easily by doing the following:"
+msgstr ""
+"Aggiornamento: grazie al lavoro di h2ik, esiste un outproxy https "
+"outproxy disponibile all'uso tramite I2P. A partire dalla versione di I2P"
+" 0.8.4 il "
+"tunnel è configurato senza dover intervenire.
\n"
+"Se l'outproxy https non fosse disponibile nella tua versione di I2P, puoi"
+" aggiugerlo facilmente facendo così:"
+
+#: i2p2www/pages/site/faq.html:320
+msgid ""
+"Open i2p tunnel "
+"manager. Scroll down to the bottom."
+msgstr ""
+"Apri il gestore dei"
+" tunnel i2p. Scorri la pagina fino in fondo."
+
+#: i2p2www/pages/site/faq.html:325
+msgid ""
+"Choose CONNECT from New Client Tunnel dropdown list, click "
+"Create"
+msgstr ""
+"Scegli CONNETTI nella menu a comparsa Nuovo tunnel client, "
+"fai clic su Crea"
+
+#: i2p2www/pages/site/faq.html:330
+#, python-format
+msgid ""
+"In the new page, name and describe your new https tunnel as"
+" you like.\n"
+"The Access Point is your local port for the new https proxy "
+"recommended port's 4445.\n"
+"Outproxy should be the outproxy's .i2p address which supports "
+"https. \n"
+"See this forum post of h2ik's for the "
+"address. \n"
+"Make sure Shared Client, Delay Connect, AutoStart "
+"are checked.\n"
+"Other options should be left at the defaults. Click Save. In tunnel "
+"manger, click the Start button next to your new tunnel."
+msgstr ""
+"Nella nuova pagina, dai un nome e una descrizione al nuovo "
+"tunnel https a piacere.\n"
+"Il punto di accesso è la tua porta locale consigliata 4445 "
+"per il nuovo proxy https.\n"
+"L'outproxy dovrebbe essere l'indirizzo .i2p dell'outproxy che "
+"supporta https. \n"
+"Consulta questo articolo del forum di h2ik per "
+"l'indirizzo. \n"
+"Assicurati che siano impostate le opzioni Client condiviso, "
+"Ritarda connessione, Avvio automatico.\n"
+"Le altre opzioni dovrebbero essere lasciate sui loro valori predefiniti. "
+"Fai clic su Salva. Nel gestore dei tunnel, fai clic sul pulsante "
+"Avvia accanto al tuo nuovo tunnel."
+
+#: i2p2www/pages/site/faq.html:340
+msgid ""
+"In firefox, click through "
+"Tools>Options>Advanced>Network>Setting."
+"\n"
+"Untick Use this proxy for all protocol, set SSL proxy: to "
+"localhost:4445."
+msgstr ""
+"In Firefox, fai clic su "
+"Strumenti>Opzioni>Avanzate>Rete>Impostazione."
+"\n"
+"Togli il segno di spunta a Usa questo proxy per tutti i "
+"protocolli, imposta il proxy SSL: su localhost:4445."
+
+#: i2p2www/pages/site/faq.html:345
+msgid "Done."
+msgstr "Fine."
+
+#: i2p2www/pages/site/faq.html:351
+#, python-format
+msgid ""
+"\n"
+"This is a question that only you can answer because the correct answer "
+"depends on your behaviours, your\n"
+"threat model, and how much you trust the "
+"outproxy operator."
+msgstr ""
+"\n"
+"Questa è una domanda a cui solo tu puoi dare risposta perché quella "
+"corretta dipende dal tuo comportamento, \n"
+"dal tipo di minaccia e dal tuo livello di"
+" fiducia in cui fa funzionare l'outproxy."
+
+#: i2p2www/pages/site/faq.html:355
+msgid ""
+"Like Tor, I2P does not magically encrypt the Internet.\n"
+"You are vulnerable to snooping by the outproxy operators.\n"
+"The Tor"
+" FAQ\n"
+"does a good job of explaining this."
+msgstr ""
+"Al pari di Tor, I2P non cripta Internet con la magia.\n"
+"Sei vulnerabile ai tentativi di spionaggio messi in atto dagli operatori "
+"dell'outproxy.\n"
+"La FAQ"
+" di TOR\n"
+"offre spiegazioni adeguate a questa problematica."
+
+#: i2p2www/pages/site/faq.html:361
+#, python-format
+msgid ""
+"In addition, you may be vulnerable to collusion between the outproxy "
+"operator\n"
+"and operators of other I2P services, if you use the same tunnels "
+"(\"shared clients\").\n"
+"There is additional discussion about this on %(zzz)s."
+msgstr ""
+"Inoltre, potresti essere vulnerabile alle collusione tra l'operatore "
+"dell'outproxy e\n"
+"quelli di altri servizi I2P, se usi gli stessi tunnel (\"client "
+"condivisi\").\n"
+"Esiste una discussione aggiuntiva in merito su %(zzz)s."
+
+#: i2p2www/pages/site/faq.html:369
+msgid ""
+"Unless an outproxy has been set up for the service you want to connect "
+"to, this cannot be done.\n"
+"There are only three types of outproxies running right now: HTTP, HTTPS, "
+"and email. Note that there is not a SOCKS outproxy.\n"
+"If this type of service is required, try Tor."
+msgstr ""
+"A meno che non sia stato impostato un outproxy per il servizio a cui vuoi"
+" collegarti, non è possibile farlo.\n"
+"Ci sono solo tre tipi di outproxy in funzione al momento: HTTP, HTTPS e "
+"e-mail. Ricorda che non c'è un outproxy SOCKS.\n"
+"Se è questo il servizio che ti serve, prova Tor."
+
+#: i2p2www/pages/site/faq.html:377
+#, python-format
+msgid ""
+"If you consider every eepsite that has ever been created, yes, most of "
+"them are down.\n"
+"People and eepsites come and go.\n"
+"A good way to get started in I2P is check out a list of eepsites that are"
+" currently up.\n"
+"%(eepstatus)s tracks active eepsites."
+msgstr ""
+"Se prendi in considerazione ogni singolo eepsite che sia mai stato "
+"creato, sì, la maggior parte di essi non funziona.\n"
+"Gli utenti e gli eepsite vanno e vengono.\n"
+"Un buon modo per cominciare dentro I2P è di controllare l'elenco di "
+"eepsites attualmente attivi.\n"
+"%(eepstatus)s tiene traccia degli eepsite "
+"attivi."
+
+#: i2p2www/pages/site/faq.html:386
+msgid ""
+"Click on the Website link\n"
+"at the top of your router console for instructions."
+msgstr ""
+"Fai clic sul link Website\n"
+"in alto nella pagina del router per le istruzioni."
+
+#: i2p2www/pages/site/faq.html:393
+msgid ""
+"Why are downloads, torrents, web browsing, and everything else so slow on"
+" I2P?\n"
+"The encryption and routing within the I2P network adds a substantial "
+"amount of overhead and limits bandwidth.\n"
+"Anonymity isn't free."
+msgstr ""
+"Perché i download, i torrent, la navigazione web e tutto il resto sono "
+"così lenti su I2P?\n"
+"La cifratura e l'instradamento all'interno della rete I2P aggiungono una "
+"quantità sostanziale di informazione aggiuntiva e limitano la banda.\n"
+"L'anonimato ha il suo prezzo da pagare."
+
+#: i2p2www/pages/site/faq.html:398
+msgid ""
+"In addition, you and everybody else probably need to increase your "
+"bandwidth limits.\n"
+"Two key settings are the inbound and outbound bandwidth limiters on\n"
+"the configuration page.\n"
+"With the default settings of 32KBps you will generally get no better than"
+" 15KBps data transfer in I2PSnark.\n"
+"Increasing the settings (but keeping within your actual connection "
+"limitations)\n"
+"will increase the potential transfer rate for I2PSnark and all other "
+"applications."
+msgstr ""
+"Inoltre, sia tu che tutti gli utenti dovreste probablimente aumentare i "
+"limiti che avete impostato per la larghezza di banda.\n"
+"Le due impostazioni chiave sono i limiti di banda per il traffico in "
+"entrata e in uscita nella\n"
+"pagina di "
+"configurazione.\n"
+"Con le impostazioni predefinite di 32 KBps, di solito non si va oltre i "
+"15KBps come velocità di trasferimento in I2PSnark.\n"
+"L'aumento delle impostazioni (mantenendole entro i limiti della "
+"connessione attuale)\n"
+"farà crescere la velocità potenziale di trasferimento per I2PSnark e "
+"tutte le altre applicazioni."
+
+#: i2p2www/pages/site/faq.html:406
+msgid ""
+"Also, do you have sufficient share bandwidth configured to allow "
+"participating tunnels\n"
+"to route through your router? Believe it or not, allowing participating "
+"traffic\n"
+"keeps you well-integrated in the network and helps your own transfer "
+"speeds."
+msgstr ""
+"Come se non bastasse, disponi di sufficiente banda condivisa configurata "
+"per consentire ai tunnel coinvolti\n"
+"l'instradamento tramite il tuo router? Credici o meno, consentire il "
+"passaggi di traffico\n"
+"ti mantiene ben integrato nella rete e giova alla velocità dei tuoi "
+"trasferimenti."
+
+#: i2p2www/pages/site/faq.html:411
+#, python-format
+msgid ""
+"I2P is a work in progress. Lots of improvements and fixes are being "
+"implemented, and\n"
+"generally speaking, running the latest release will help your "
+"performance.\n"
+"If you haven't, install the latest "
+"release."
+msgstr ""
+"I lavori su I2P sono tuttora in corso. Ci sono tanti miglioramenti e "
+"risoluzoni di problemi che vengono implementati e, \n"
+"di solito, eseguire la versione più recente aiuta a migliorare le "
+"prestazioni.\n"
+"Se non l'hai già fatto, installa la "
+"versione più recente."
+
+#: i2p2www/pages/site/faq.html:419
+#, python-format
+msgid ""
+"See the\n"
+"I2P Bittorrent FAQ"
+msgstr ""
+"Consulta la\n"
+"FAQ per Bittorrent di "
+"I2P"
+
+#: i2p2www/pages/site/faq.html:426
+msgid ""
+"\n"
+"A tunnel to the main IRC server within I2P, Irc2P, is created when I2P is"
+" installed (see\n"
+"the I2PTunnel "
+"configuration page),\n"
+"and is automatically started when the I2P router starts. To connect to "
+"it, tell your IRC\n"
+"client to connect to localhost 6668. XChat-like client users"
+" can create a\n"
+"new network with the server localhost/6668 (remember to tick"
+" "Bypass\n"
+"proxy server" if you have a proxy server configured)."
+msgstr ""
+"\n"
+"Un tunnel verso il server IRC principale all'interno di I2P, Irc2P, viene"
+" creato al momento dell'installazione di I2P (consulta\n"
+"la pagina di "
+"configurazione di I2PTunnel)\n"
+"ed è avviato automaticamente quando si avvia il router I2P. Per "
+"connetterti, istruisci il tuo client\n"
+"IRC a connettersi a localhost 6668. I client simili a XCha "
+"possono creare una nuova\n"
+"rete con il server localhost/6668 (ricorda di mettere il "
+"segno di spunta sull'opzione "Bypassa\n"
+"il server proxyr" nel caso in cui tu abbia un server proxy "
+"preconfigurato)."
+
+#: i2p2www/pages/site/faq.html:437
+msgid ""
+"For security purposes, the router's admin console by default only listens"
+"\n"
+"for connections on the local interface. However, with a little hacking,\n"
+"you can make it reachable remotely:"
+msgstr ""
+"Per motivi di sicurezza, la console admin del router di default rimane in"
+" ascolto soltanto\n"
+"delle connessioni sull'interfaccia locale. Tuttavia, con qualche "
+"intervento,\n"
+"puoi fare in modo che sia accessibile da remoto:"
+
+#: i2p2www/pages/site/faq.html:445
+msgid ""
+"Open ~/.i2p/clients.config and replace
\n"
+"clientApp.0.args=7657 ::1,127.0.0.1 ./webapps/
\n"
+"with
\n"
+"clientApp.0.args=7657 0.0.0.0 ./webapps/"
+msgstr ""
+"Apri ~/.i2p/clients.config e sostituisci
\n"
+"clientApp.0.args=7657 ::1,127.0.0.1 ./webapps/
\n"
+"con
\n"
+"clientApp.0.args=7657 0.0.0.0 ./webapps/"
+
+#: i2p2www/pages/site/faq.html:453
+msgid ""
+"Go to http://localhost:7657/configui"
+"\n"
+"and add a console username and password if desired."
+msgstr ""
+"Accedi a http://localhost:7657/configui"
+"\n"
+"e aggiungi un nome utente e password per la console se vuoi."
+
+#: i2p2www/pages/site/faq.html:459
+msgid ""
+"Go to http://localhost:7657/index.jsp"
+"\n"
+"and hit \"Graceful restart\", which restarts the JVM and reloads the "
+"client applications"
+msgstr ""
+"Accedi a http://localhost:7657/index.jsp"
+"\n"
+"e fai clic su \"Riavvia garbatamente\", un'opzione che riavvia la JVM e "
+"ricaricare le applicazioni client."
+
+#: i2p2www/pages/site/faq.html:466
+msgid ""
+"After that fires up, you should now be able to reach your console "
+"remotely. Reload the router at\n"
+"http://127.0.0.1:7657 and you will be prompted for the username and "
+"password you specified in step 2\n"
+"above if your browser supports the authentication popup. Note: the\n"
+"0.0.0.0 above specifies an interface, not a network "
+"or netmask. 0.0.0.0\n"
+"means \"bind to all interfaces\", so it can be reachable on "
+"127.0.0.1:7657 as well as\n"
+"any LAN/WAN IP."
+msgstr ""
+"Dopo d che, dovresti essere in grado di raggiungere la console da remote."
+" Ricarica il router at\n"
+"http://127.0.0.1:7657 e ti sarà richiesto il nome utente e la password "
+"che indicato al punto 2\n"
+"qui sopra se il tuo browser supporta i popup di autenticazione. Nota: "
+"l'indirizzo\n"
+"0.0.0.0 qui sopra indica l'interfaccia, non la rete o"
+" il netmask. 0.0.0.0\n"
+"significa \"lega a tutte le interfacce\", per cui può essere raggiunto su"
+" 127.0.0.1:7657 e anche da qualunque indirizzo internet di\n"
+"LAN o WAN."
+
+#: i2p2www/pages/site/faq.html:477
+msgid ""
+"By default, the router I2CP interface (port 7654) binds to address "
+"127.0.0.1. To bind to 0.0.0.0, set the\n"
+"router advanced configuration option "
+"i2cp.tcp.bindAllInterfaces=true and restart."
+msgstr ""
+"Come impostazione predefinita, l'interfaccia I2CP del router (porta 7654)"
+" si lega all'indirizzo 127.0.0.1. Per legarla a 0.0.0.0, imposta "
+"l'opzione di configurazione avanzata del router su\n"
+"router advanced configuration option "
+"i2cp.tcp.bindAllInterfaces=true e riavvia."
+
+#: i2p2www/pages/site/faq.html:482
+msgid "Whats an \"eepsite\"?"
+msgstr "Cos'è un \"eepsite\"?"
+
+#: i2p2www/pages/site/faq.html:484
+msgid ""
+"An eepsite is a website that is hosted anonymously - you can access it by"
+"\n"
+"setting your web browser's HTTP proxy to use the web proxy (typically it\n"
+"listens on localhost port 4444), and browsing to the site."
+msgstr ""
+"Un eepsite è un sito web ospitato in maniera anonima: puoi accedervi\n"
+"impostando il tuo proxy HTTP del browser per usare un proxy web (che di "
+"solito è in ascolto\n"
+"su localhost port 4444) e navigando verso il sito."
+
+#: i2p2www/pages/site/faq.html:492
+#, python-format
+msgid ""
+"The proxy config for different browsers is on a \n"
+"separate page with screenshots. More advanced configs with external "
+"tools\n"
+"are possible but could introduce leaks in your setup."
+msgstr ""
+"La configurazione del proxy per browser differenti si trova su una \n"
+"pagina separata con i relativi screenshot. Sono possibili "
+"configurazioni più avanzate con strumenti esterni\n"
+"ma potrebbero introdurre delle falle nella tua impostazione."
+
+#: i2p2www/pages/site/faq.html:501
+msgid ""
+"x is the number of peers you've sent or received a message from\n"
+"successfully in the last minute, y is the number of peers seen in the "
+"last\n"
+"hour or so."
+msgstr ""
+"x è il numero di peer a cui hai inviato o da cui ha ricevuto un messaggio"
+" con successo\n"
+"nell'ultimo minuto, y è il numero di peer visti nell'ultima\n"
+"ora all'incirca."
+
+#: i2p2www/pages/site/faq.html:509
+msgid ""
+"The SOCKS proxy is working as of release 0.7.1. SOCKS 4/4a/5 are "
+"supported.\n"
+"There is no SOCKS outproxy so it is of limited use."
+msgstr ""
+"Il proxy SOCKS funziona a partire dalla versione 0.7.1. Sono supportati i"
+" SOCKS 4/4a/5.\n"
+"Non c'è alcun outproxy SOCKS per cui il suo uso è limitato."
+
+#: i2p2www/pages/site/faq.html:513
+msgid ""
+"In addition, many applications leak sensitive\n"
+"information that could identify you on the Internet. I2P only filters\n"
+"connection data, but if the program you intend to run sends this\n"
+"information as content, I2P has no way to protect your anonymity. For\n"
+"example, some mail applications will send the IP address of the machine\n"
+"they are running on to a mail server. There is no way for I2P to filter\n"
+"this, thus using I2P to 'socksify' existing applications is possible, but"
+"\n"
+"extremely dangerous."
+msgstr ""
+"Inoltre, molte applicazioni rivelano informazioni\n"
+"sensibili che potrebbero farti identificare su Internet. I2P filtra "
+"soltanto\n"
+"i dati di connessione, ma se il programma che pensi di eseguire invia "
+"tali \n"
+"informazioni come contenuti, I2P non ha modo di proteggere il tuo "
+"anonimato. \n"
+"Ad esempio, alcune applicazioni di posta elettronica invieranno al server"
+" di posta elettronica\n"
+"l'indirizzo IP del computer su cui vengono eseguite. Non c'è modo per I2P"
+" di filtrarlo,\n"
+"perciò la 'socksettizzazione' di applicazioni esistenti è possibilethis, "
+"ma\n"
+"pericolosissima."
+
+#: i2p2www/pages/site/faq.html:523
+#, python-format
+msgid ""
+"If you would like more information on the socks proxy application anyway,"
+"\n"
+"there are some helpful hints on the socks page."
+msgstr ""
+"Se desideri comunque ulteriori informazioni sull'applicazione di proxy "
+"socks,\n"
+"ecco alcuni suggerimenti utili nella pagina di "
+"socks."
+
+#: i2p2www/pages/site/faq.html:530
+msgid ""
+"Okay, here's a rundown of the default ports (everything is configurable\n"
+"through various settings, of course):"
+msgstr ""
+"Bene, ecco un riepilogo delle porte predefinite (ogni cosa è "
+"configurabileable\n"
+"tramite svariate impostazioni, ovviamente):"
+
+#: i2p2www/pages/site/faq.html:539
+msgid ""
+"Internet-facing ports\n"
+"Note: New installs as of release 0.7.8 do not use port 8887; they select "
+"a random port\n"
+"between 9000 and 31000 when the program is run for the first time.\n"
+"The selected port is shown on the router configuration page."
+msgstr ""
+"Porte per l'accesso a Internet\n"
+"Nota: le nuove installazioni a partire dalla versione 0.7.8 non usano la "
+"porta 8887, ma selezionano invece una porta casuale\n"
+"compresa tra 9000 e 31000 quando il programma viene eseguito per la prima"
+" volta.\n"
+"Tale porta è mostrata nellla pagina di configurazione"
+" del router."
+
+#: i2p2www/pages/site/faq.html:547
+msgid ""
+"Outbound UDP from the random port noted on the configuration page to "
+"arbitrary remote UDP ports, allowing replies\n"
+" "
+msgstr ""
+"UDP in uscita dalla porta casuale indicata nella pagina di configurazione"
+" verso porte UDP remote arbitrarie, per consentire le risposte\n"
+" "
+
+#: i2p2www/pages/site/faq.html:552
+msgid ""
+"Outbound TCP from random high ports to arbitrary remote TCP ports\n"
+" "
+msgstr ""
+"TCP in uscita da porte casuali alte verso porte TCP remote "
+"arbitrarie\n"
+" "
+
+#: i2p2www/pages/site/faq.html:557
+msgid ""
+"(optional, but recommended) Inbound UDP to the port noted on configuration page from "
+"arbitrary locations\n"
+" "
+msgstr ""
+"(facoltativo, ma consigliato) UDP in entrata verso la porta indicata "
+"nella pagina di "
+"configurazione da posizioni arbitrarie\n"
+" "
+
+#: i2p2www/pages/site/faq.html:562
+msgid ""
+"(optional, but recommended) Inbound TCP to the port noted on configuration page from "
+"arbitrary locations
\n"
+"Inbound TCP may be disabled on the configuration page."
+msgstr ""
+"(facoltativo, ma consigliato) TCP in entrata verso la porta indicata "
+"nella pagina di "
+"configurazione da posizioni arbitrarie\n"
+"
\n"
+"TCP in entrata potrebbe essere disattivato nella pagina di "
+"configurazione."
+
+#: i2p2www/pages/site/faq.html:568
+msgid ""
+"Outbound UDP on port 123, allowing replies
\n"
+"This is necessary for I2P's internal time sync (via SNTP - \n"
+"querying a random SNTP host in pool.ntp.org or another\n"
+"server you specify)"
+msgstr ""
+"UDP in uscita sulla porta 123, per consentire le risposte
\n"
+"Questa è necessaria per la sincronizzazione interna dell'orario in I2P "
+"(tramite SNTP - \n"
+"con query verso un host SNTP casuale sul server pool.ntp.org o u altri di"
+" tua\n"
+"impostazione)"
+
+#: i2p2www/pages/site/faq.html:579
+msgid ""
+"Local I2P ports, listening only to local connections by default,\n"
+"except where noted:"
+msgstr ""
+"Porte I2P locali, in ascolto solo delle connessioni locali come "
+"impostazione predefinita,\n"
+"eccetto dove specificato:"
+
+#: i2p2www/pages/site/faq.html:585
+msgid ""
+"1900: UPnP SSDP UDP multicast listener.\n"
+"Cannot be changed. Binds to all interfaces.\n"
+"May be disabled on confignet.jsp."
+msgstr ""
+"1900: ascolto multicast UDP SSDP UPnP.\n"
+"Non può essere cambiata. Si lega a tutte le interfacce.\n"
+"Può essere disattivata su confignet.jsp."
+
+#: i2p2www/pages/site/faq.html:592
+msgid ""
+"2827: BOB bridge, a higher level socket API for clients\n"
+"Disabled by default.\n"
+"May be enabled/disabled on configclients.jsp.\n"
+"May be changed in the bob.config file."
+msgstr ""
+"2827: BOB bridge, un'API socket di livello più alto per i client\n"
+"Disattivata per impostazione predefinita.\n"
+"Può essere attivata/disattivata su configclients.jsp.\n"
+"Può essere modificata nel file the bob.config."
+
+#: i2p2www/pages/site/faq.html:600
+msgid ""
+"4444: HTTP proxy\n"
+"May be disabled or changed on the i2ptunnel page in the router "
+"console.\n"
+"May also be configured to be bound to a specific interface or all "
+"interfaces."
+msgstr ""
+"4444: proxy HTTP\n"
+"Può essere disattivata o modificata nella pagina di i2ptunnel nel "
+"console router.\n"
+"Può anche essere configurata per legarsi a un'interfaccia specifica o a "
+"tutte le interfacce."
+
+#: i2p2www/pages/site/faq.html:607
+msgid ""
+"4445: HTTPS proxy\n"
+"May be disabled or changed on the i2ptunnel page in the router "
+"console.\n"
+"May also be configured to be bound to a specific interface or all "
+"interfaces."
+msgstr ""
+"4445: proxy HTTPS\n"
+"Può essere disattivata o modificata nella pagina di i2ptunnel nel "
+"console router.\n"
+"Può anche essere configurata per legarsi a un'interfaccia specifica o a "
+"tutte le interfacce."
+
+#: i2p2www/pages/site/faq.html:614
+msgid ""
+"6668: IRC proxy\n"
+"May be disabled or changed on the i2ptunnel page in the router "
+"console.\n"
+"May also be configured to be bound to a specific interface or all "
+"interfaces."
+msgstr ""
+"6668: proxy IRC\n"
+"Può essere disattivata o modificata nella pagina di i2ptunnel nel "
+"console router.\n"
+"Può anche essere configurata per legarsi a un'interfaccia specifica o a "
+"tutte le interfacce."
+
+#: i2p2www/pages/site/faq.html:621
+msgid ""
+"7652: UPnP HTTP TCP event listener.\n"
+"Binds to the LAN address.\n"
+"May be changed with advanced config i2np.upnp.HTTPPort=nnnn.\n"
+"May be disabled on confignet.jsp."
+msgstr ""
+"7652: ascolto degli eventi TCP HTTP UPnP.\n"
+"Si lega all'indirizzo LAN.\n"
+"Può essere cambiata con la configurazione avanzata "
+"i2np.upnp.HTTPPort=nnnn.\n"
+"Può essere disattivata su confignet.jsp."
+
+#: i2p2www/pages/site/faq.html:629
+msgid ""
+"7653: UPnP SSDP UDP search response listener.\n"
+"Binds to all interfaces.\n"
+"May be changed with advanced config i2np.upnp.SSDPPort=nnnn.\n"
+"May be disabled on confignet.jsp."
+msgstr ""
+"7653: ascolto risposta ricerca UDP SSDP UPnP.\n"
+"Si lega a tutte le interfacce.\n"
+"Può essere cambiata con la configurazione avanzata "
+"i2np.upnp.SSDPPort=nnnn.\n"
+"Può essere disattivata su confignet.jsp."
+
+#: i2p2www/pages/site/faq.html:637
+msgid ""
+"7654: I2P Client Protocol port, used by client apps.\n"
+"May be changed to a different port on\n"
+"configclients.jsp"
+"\n"
+"but this is not recommended.\n"
+"May be to bind to a different interface or all interfaces, or disabled, "
+"on\n"
+"configclients.jsp."
+msgstr ""
+"7654: porta di protocollo client I2P, usata dalle applicazione "
+"client.\n"
+"Può essere cambiata con una porta diversa su\n"
+"configclients.jsp"
+"\n"
+"ma non è consigliato.\n"
+"Può essere impostata per legarsi a una interfaccia diversa o a tutte le "
+"interfacce, oppure disattivata su\n"
+"configclients.jsp."
+
+#: i2p2www/pages/site/faq.html:647
+msgid ""
+"7655: UDP for SAM bridge, a higher level socket API for clients\n"
+"Only opened when a SAM V3 client requests a UDP session.\n"
+"May be enabled/disabled on configclients.jsp.\n"
+"May be changed in the clients.config file with the SAM command line "
+"option sam.udp.port=nnnn."
+msgstr ""
+"7655: UDP per SAM bridge, un'API socket di più alto livello per i "
+"client\n"
+"Aperta solo quando un client SAM V3 richiede una sessione UDP.\n"
+"Può essere attivata o disattivata su configclients.jsp.\n"
+"Può essere modificata nel file clients.config con l'opzione per riga di "
+"comando SAM sam.udp.port=nnnn."
+
+#: i2p2www/pages/site/faq.html:655
+msgid ""
+"7656: SAM bridge, a higher level socket API for clients\n"
+"Disabled by default for new installs as of release 0.6.5.\n"
+"May be enabled/disabled on configclients.jsp.\n"
+"May be changed in the clients.config file."
+msgstr ""
+"7656: SAM bridge, un'API socket di livello più alto per i client\n"
+"Disattivata per impostazione predefinita per le nuove installazioni a "
+"partire dalla versione 0.6.5.\n"
+"Può essere attivata/disattivata su configclients.jsp.\n"
+"Può essere modificata nel file the clients.config."
+
+#: i2p2www/pages/site/faq.html:663
+msgid ""
+"7657: Your router console\n"
+"May be disabled in the clients.config file.\n"
+"May also be configured to be bound to a specific interface or all "
+"interfaces in that file."
+msgstr ""
+"7657: il console router\n"
+"Può essere disattivata o modificata nel file clients.config.\n"
+"Può anche essere configurata per legarsi a un'interfaccia specifica o a "
+"tutte le interfacce in quel file."
+
+#: i2p2www/pages/site/faq.html:670
+msgid ""
+"7658: Your eepsite\n"
+"May be disabled in the clients.config file.\n"
+"May also be configured to be bound to a specific interface or all "
+"interfaces in the jetty.xml file."
+msgstr ""
+"7657: il console router\n"
+"Può essere disattivata o modificata nel file clients.config.\n"
+"Può anche essere configurata per legarsi a un'interfaccia specifica o a "
+"tutte le interfacce in quel file."
+
+#: i2p2www/pages/site/faq.html:677
+msgid ""
+"7659: Outgoing mail to smtp.postman.i2p\n"
+"May be disabled or changed on the i2ptunnel page in the router "
+"console.\n"
+"May also be configured to be bound to a specific interface or all "
+"interfaces."
+msgstr ""
+"7659: e-mail in uscita verso smtp.postman.i2p\n"
+"Può essere disattivata o modificata nella pagina di i2ptunnel nel "
+"console router.\n"
+"Può anche essere configurata per legarsi a un'interfaccia specifica o a "
+"tutte le interfacce."
+
+#: i2p2www/pages/site/faq.html:684
+msgid ""
+"7660: Incoming mail from pop.postman.i2p\n"
+"May be disabled or changed on the i2ptunnel page in the router "
+"console.\n"
+"May also be configured to be bound to a specific interface or all "
+"interfaces."
+msgstr ""
+"7660: e-mail in arrivo da pop.postman.i2p\n"
+"Può essere disattivata o modificata nella pagina di i2ptunnel nel "
+"console router.\n"
+"Può anche essere configurata per legarsi a un'interfaccia specifica o a "
+"tutte le interfacce."
+
+#: i2p2www/pages/site/faq.html:691
+msgid ""
+"8998: mtn.i2p2.i2p (Monotone - disabled by default)\n"
+"May be disabled or changed on the i2ptunnel page in the router "
+"console.\n"
+"May also be configured to be bound to a specific interface or all "
+"interfaces."
+msgstr ""
+"8998: mtn.i2p2.i2p (Monotone: disattivato come impostazione "
+"predefinita)\n"
+"Può essere disattivata o modificata nella pagina di i2ptunnel nel "
+"console router.\n"
+"Può anche essere configurata per legarsi a un'interfaccia specifica o a "
+"tutte le interfacce."
+
+#: i2p2www/pages/site/faq.html:698
+msgid ""
+"31000: Local connection to the wrapper control channel port.\n"
+"Outbound to 32000 only, does not listen on this port.\n"
+"Starts at 31000 and will increment until 31999 looking for a free port.\n"
+"To change, see the\n"
+"wrapper documentation.\n"
+"For more information see below."
+msgstr ""
+"31000: connessione locale alla porta del canale di controllo del "
+"wrapper.\n"
+"In uscita solo su 32000, non ascolta su tale porta.\n"
+"Parte a 31000 e incrementa fino a 31999 in cerca di una porta libera.\n"
+"Per modificarla, consulta la\n"
+"documentazione del wrapper .\n"
+"Per ulteriori informazioni, vedi più oltre."
+
+#: i2p2www/pages/site/faq.html:708
+msgid ""
+"32000: Local control channel for the service wrapper.\n"
+"To change, see the\n"
+"wrapper documentation.\n"
+"For more information see below."
+msgstr ""
+"32000: canale di controllo locale per il servizio wrapper.\n"
+"Per modificarla, consulta la\n"
+"documentazione del wrapper .\n"
+"Per ulteriori informazioni, vedi più oltre."
+
+#: i2p2www/pages/site/faq.html:720
+msgid ""
+"The local I2P ports and the I2PTunnel ports do not need to be reachable "
+"from \n"
+"remote machines, but *should* be reachable locally. You can also create"
+" \n"
+"additional ports for I2PTunnel instances via "
+"http://localhost:7657/i2ptunnel/ \n"
+"(and in turn, would need to get your firewall to allow you local access, "
+"but \n"
+"not remote access, unless desired)."
+msgstr ""
+"Non occorre che le porte I2P locali e le porte I2PTunnel siano "
+"raggiungibili \n"
+"da computer remoti, ma *dovrebbero* essere raggiungibili in locale. Puoi "
+"anche creare \n"
+"porte aggiuntive per le istanze I2PTunnel tramite "
+"http://localhost:7657/i2ptunnel/ \n"
+"(e successivamente dovrebbero riuscire a raggiungere il tuo firewall per "
+"consentire l'accesso locale, ma \n"
+"non quello da remoto, a meno di non volerlo)."
+
+#: i2p2www/pages/site/faq.html:728
+msgid ""
+"So, to summarize, nothing needs to be reachable by unsolicited remote "
+"peers, but\n"
+"if you can configure your NAT/firewall to allow inbound UDP and TCP the "
+"outbound facing port, you'll"
+"\n"
+"get better performance. You will also need to be able to send outbound "
+"UDP packets\n"
+"to arbitrary remote peers (blocking IPs randomly with something like "
+"PeerGuardian\n"
+"only hurts you - don't do it)."
+msgstr ""
+"Quindi, per riassumere, non c'è niente che debba per forza essere "
+"raggiungibile da peer remoti, ma\n"
+"puoi configurare il tuo NAT o firewall per consentire i flussi UDP e TCP "
+"in entrata per la porta verso "
+"l'esterno, otterrai \n"
+"prestazioni migliori. Dovrai anche essere in grado di inviare pacchetti "
+"UDP in uscita\n"
+"verso peer remoti (bloccare indirizzi IP a caso con qualcosa tipo "
+"PeerGuardian\n"
+"ti nuocerà e basta, non farlo)."
+
+#: i2p2www/pages/site/faq.html:736
+msgid "Why is I2P listening on port 32000?"
+msgstr "Perché I2P rimane in ascolto sulla porta 32000?"
+
+#: i2p2www/pages/site/faq.html:738
+msgid ""
+"The Tanuki java service wrapper that we use opens this port—bound "
+"to localhost—in order \n"
+"to communicate with software running inside the JVM. When the JVM is "
+"launched it is given a key \n"
+"so it can connect to the wrapper. After the JVM establishes its "
+"connection \n"
+"to the wrapper, the wrapper refuses any additional connections."
+msgstr ""
+"Il wrapper di servizio java Tanuki che usiamo apre questa porta—la "
+"lega a localhost—per poter \n"
+"comunicarecon il software in esecuzione dentro la JVM. Quando la JVM "
+"viene lanciata, le viene assegnata una chiave \n"
+"in modo da potersi collegare al wrapper. Dopo che la JVM stabilisce la "
+"propria connessione \n"
+"al wrapper, quest'ultimo rifiuta qualunque altra eventuale connessione "
+"aggiuntiva."
+
+#: i2p2www/pages/site/faq.html:744
+msgid ""
+"More information can be found in the \n"
+"wrapper documentation."
+msgstr ""
+"Ulteriori informazioni possono essere reperite nella \n"
+"documentazione del wrapper ."
+
+#: i2p2www/pages/site/faq.html:751
+msgid ""
+"An I2P router only needs to be seeded once, to join the network for the "
+"first time.\n"
+"Reseeding is nothing more than sending plain HTTP GET requests\n"
+"to fetch a directory listing and download multiple \"routerInfo\" files\n"
+"from a predefined reseed URL."
+msgstr ""
+"Il seed di un router I2P è sufficiente che avvenga una sola volta per "
+"unirsi alla rete per la prima volta.\n"
+"Il reseed non è altro che l'invio di semplici richieste HTTP GET\n"
+"per ottenere un elenco delle directory e scaricare molteplici file di "
+"\"routerInfo\"\n"
+"da un URL predefinito di reseed."
+
+#: i2p2www/pages/site/faq.html:758
+msgid ""
+"A typical symptom of a failed reseed is the \"Known\" indicator\n"
+"(on the left sidebar of the router console) displaying a very small value"
+"\n"
+"(often less than 5) which does not increase. This can occur, among other "
+"things,\n"
+"if your firewall limits outbound traffic, and blocked the reseed request."
+msgstr ""
+"Un simbolo tipico di un reseed fallito è l'indicatore \"Conosciuti\"\n"
+"(presente nella barra laterale sinistra del console router) indicante un "
+"valore molto piccolo\n"
+"(spesso inferiore a 5) che non aumenta. Ciò può verificarsi, tra le altre"
+" cose,\n"
+"se il tuo firewall limita il traffico in uscita e blocca la richiesta di "
+"reseed."
+
+#: i2p2www/pages/site/faq.html:765
+msgid "To reseed an I2P router manually, do the following:"
+msgstr "Per effettuare il reseed di un router IP2 manualmente, segui questi punti:"
+
+#: i2p2www/pages/site/faq.html:768
+msgid "Stop your I2P router"
+msgstr "Arresta il router I2P"
+
+#: i2p2www/pages/site/faq.html:771
+msgid ""
+"Open http://netdb.i2p2.de/ using a "
+"web browser"
+msgstr ""
+"Apri http://netdb.i2p2.de/ con un "
+"browser web"
+
+#: i2p2www/pages/site/faq.html:774
+msgid "Save a dozen \"routerInfo\" files to your I2P \"netDb\" directory"
+msgstr "Salva una dozzina di file \"routerInfo\" nella cartella I2P \"netDb\""
+
+#: i2p2www/pages/site/faq.html:781
+msgid "Start your I2P router"
+msgstr "Avvia il router I2P"
+
+#: i2p2www/pages/site/faq.html:788
+msgid ""
+"When trying to start the router using \"i2prouter start\", you may see "
+"output like the following:"
+msgstr ""
+"Quando provi ad avviare il router usando \"i2prouter start\", potrebbe "
+"essere visualizzato quanto segue:"
+
+#: i2p2www/pages/site/faq.html:793
+msgid ""
+"\n"
+"In order to be inclusive and try to ensure that I2P will run on as many "
+"systems \n"
+"as possible, up until I2P 0.8.9 we used a java wrapper \n"
+"compiled for FreeBSD 6.x. If you're receiving this error you most likely "
+"are missing the necessary compatibility libraries.\n"
+"These libraries may be installed by performing the following steps:"
+msgstr ""
+"\n"
+"Per essere inclusivo e cercare di assicurare che I2P sia eseguito su "
+"quanti più sistemi possibili, \n"
+"fino alla version I2P 0.8.9 abbiamo usato un wrapper java \n"
+"compilato per FreeBSD 6.x. Se ricevi questo errore, probabilmente ti "
+"mancano le librerie di compatibilità necessarie.\n"
+"Tali librerie possono essere installate seguendo questi punti:"
+
+#: i2p2www/pages/site/faq.html:801
+msgid ""
+"Switch to the root user with su or log in as "
+"root."
+msgstr ""
+"Passa all'utente amministratore con su oppure effettua il "
+"login come root."
+
+#: i2p2www/pages/site/faq.html:807
+#, python-format
+msgid ""
+"If you cannot install these compatibility libraries (or do not want to), "
+"other\n"
+"possibilities would be to compile the wrapper for your\n"
+"system, starting I2P with the runplain.sh script, or you"
+" can\n"
+"replace the wrapper with one from the source tarball."
+msgstr ""
+"Se non riesci a installare queste librerie di compatibilità (o non vuoi "
+"farlo), le altre\n"
+"possibilità a tua disposizione potrebbero esser la compilazione del "
+"wrapper per il tuo\n"
+"sistema, l'avvio di I2P con lo script runplain.sh oppure"
+" \n"
+"la sostituzione del wrapper con uno contenuto nel file sorgente compresso"
+" con tar."
+
+#: i2p2www/pages/site/faq.html:813
+msgid ""
+"For the 0.8.9 release of I2P, the wrapper was upgraded to v3.5.12 and "
+"compiled on systems running FreeBSD 7.2."
+msgstr ""
+"Per la versione 0.8.9 di I2P, il wrapper è stato aggiornata alla versione"
+" 3.5.12 e compilato su sistemi FreeBDS 7.2."
+
+#: i2p2www/pages/site/faq.html:817
+msgid ""
+"In wrapper.log I see an error that states \"Protocol "
+"family unavailable\" when loading the Router Console"
+msgstr ""
+"Nel wrapper.log osservo un errore relativo alla "
+"famiglia di protocolli non disponibile quando viene caricato"
+" il console router."
+
+#: i2p2www/pages/site/faq.html:819
+msgid ""
+"Often this error will occur with any network enabled java software on "
+"some systems that are configured to use IPv6 by default. There are a few "
+"ways to solve this:"
+msgstr ""
+"Spesso tale errore si verifica con qualunque software java abilitato per "
+"le reti su alcuni sistemi che sono configurati per l'uso di IPv6 come "
+"impostazione predefinita. Esistono alcuni modi per risolvere questo "
+"problema:"
+
+#: i2p2www/pages/site/faq.html:824
+msgid ""
+"On Linux based systems, you can echo 0 > "
+"/proc/sys/net/ipv6/bindv6only"
+msgstr ""
+"Sui sistemi basati su Linux, è possibile eseguire echo 0 > "
+"/proc/sys/net/ipv6/bindv6only"
+
+#: i2p2www/pages/site/faq.html:826
+msgid "Look for the following lines in wrapper.config."
+msgstr "Cerca le seguenti righe nel wrapper.config."
+
+#: i2p2www/pages/site/faq.html:830
+msgid ""
+"If the lines are there, uncomment them by removing the \"#\"s. If the "
+"lines are not there, add them without the \"#\"s."
+msgstr ""
+"Se tali righe esistono, rimuovi i loro simboli di commento \"#\". Se non "
+"esistono, aggiungile senza i simboli \"#\"."
+
+#: i2p2www/pages/site/faq.html:833
+msgid ""
+"Another option would be to remove the ::1 from "
+"~/.i2p/clients.config"
+msgstr ""
+"Un'altra opzione potrebbe essere quella di rimuovere ::1"
+" da ~/.i2p/clients.config"
+
+#: i2p2www/pages/site/faq.html:837
+msgid ""
+"WARNING: For any changes to wrapper.config "
+"to take effect, you must completely\n"
+"stop the router and the wrapper. Clicking Restart on your\n"
+"router console will NOT reread this file! You must\n"
+"click Shutdown, wait 11 minutes, then start I2P."
+msgstr ""
+"ATTENZIONE: perché wrapper.config abbia "
+"qualche possibilità di avere effetto, devi interrompere completamento\n"
+"il router e il wrapper. Fare clic su Riavvia nel console\n"
+"router NON eseguirà una rilettura del file! Devi\n"
+"fare clic suArresta, attendere 11 minuti, quindi avviare I2P."
+
+#: i2p2www/pages/site/faq.html:848
+#, python-format
+msgid ""
+"Great! Find us on IRC irc.freenode.net #i2p or post to\n"
+"the forum and we'll post it here (with\n"
+"the answer, hopefully)."
+msgstr ""
+"Fantastico! Ci puoi trovare su IRC all'indirizzo irc.freenode.net nel "
+"canale #i2p oppure postare sul\n"
+"forum e noi provvederemo a postare qui "
+"(con\n"
+"la risposta, si spera)."
+
+#: i2p2www/pages/site/impressum.html:4
+msgid "German laws"
+msgstr "Legislazione tedesca"
+
+#: i2p2www/pages/site/index.html:2
+msgid "I2P Anonymous Network"
+msgstr "Rete anonima I2P"
+
+#: i2p2www/pages/site/index.html:4
+msgid ""
+"Anonymous peer-to-peer distributed communication layer built with open "
+"source tools and designed to run any traditional Internet service such as"
+" email, IRC or web hosting."
+msgstr ""
+"Livello di comunicazione distribuito peer-to-peer anonimo compilato con "
+"strumenti open source e progettato per funzionare con qualunque servizio "
+"Internet come e-mail, IRC o web hosting."
+
+#: i2p2www/pages/site/index.html:7
+msgid "What does I2P do for you?"
+msgstr "Che cosa fa I2P per te?"
+
+#: i2p2www/pages/site/index.html:8
+msgid ""
+"The I2P network provides strong privacy protections for communication "
+"over the Internet. Many activities that would risk your privacy on the "
+"public Internet can be conducted anonymously inside I2P."
+msgstr ""
+"La rete I2P fornisce una forte protezione della privacy per le "
+"comunicazioni su Internet. Molte delle attività che metterebbero in "
+"pericolo la tua privacy su Internet pubblica possono essere condotte in "
+"modo anonimo all'interno di I2P."
+
+#: i2p2www/pages/site/index.html:9
+#, python-format
+msgid "Get I2P %(version)s"
+msgstr "Ottieni I2P %(version)s"
+
+#: i2p2www/pages/site/index.html:13
+msgid "What is I2P?"
+msgstr "Cos'è I2P?"
+
+#: i2p2www/pages/site/index.html:15
+msgid ""
+"I2P is an anonymous overlay network - a network within a network. It is "
+"intended to protect communication from dragnet surveillance and "
+"monitoring by third parties such as ISPs.\n"
+msgstr ""
+"I2P è una rete di copertura anonima, una rete dentro la rete. Il suo "
+"scopo è di proteggere le comunicazioni dal controllo a tappeto e dal "
+"monitoraggio di terze parti come gli ISP.\n"
+
+#: i2p2www/pages/site/index.html:18
+msgid ""
+"I2P is used by many people who care about their privacy: activists, "
+"oppressed people, journalists and whistleblowers, as well as the average "
+"person.\n"
+msgstr ""
+"I2P è usato da molte persone che ci tengono alla propria privacy: "
+"attivisti, oppressi, giornalisti e gole profonde, e anche persone "
+"normali.\n"
+
+#: i2p2www/pages/site/index.html:21
+msgid ""
+"No network can be \"perfectly anonymous\". The continued goal of I2P is "
+"to make attacks more and more difficult to mount. Its anonymity will get "
+"stronger as the size of the network increases and with ongoing academic "
+"review.\n"
+msgstr ""
+"Nessuna rete può essere \"perfettamente anonima\". L'intento continuo di "
+"I2P è di rendere gli attacchi sempre più difficili da lanciare. Il suo "
+"anonimato si rafforzerà all'aumentare delle dimensioni e degli studi "
+"accademici che verranno continuamente condotti.\n"
+
+#: i2p2www/pages/site/index.html:24
+msgid ""
+"I2P is available on desktops, embedded systems (like the Raspberry Pi) "
+"and Android phones. Help spread the word!\n"
+msgstr ""
+"I2P è disponibile per desktop, sistemi integrati (come il Raspberry Pi) e"
+" i telefonini Android. Dacci una mano con il passaparola!\n"
+
+#: i2p2www/pages/site/index.html:28
+msgid "Read more…"
+msgstr "Leggi tutto…"
+
+#: i2p2www/pages/site/index.html:33
+msgid "What can you do with I2P?"
+msgstr "Che cosa puoi fare con I2P?"
+
+#: i2p2www/pages/site/index.html:36
+#, python-format
+msgid ""
+"Email: Integrated web mail interface,"
+" plugin for serverless email."
+msgstr ""
+"Email: interfaccia web integrata per "
+"la posta elettronica, plugin per la posta elettronica senza server."
+
+#: i2p2www/pages/site/index.html:41
+#, python-format
+msgid ""
+"Web browsing: Anonymous "
+"websites, gateways to and from the public Internet."
+msgstr ""
+"Navigazione web: siti web "
+"anonimi, gateway verso e dallInternet pubblica."
+
+#: i2p2www/pages/site/index.html:46
+#, python-format
+msgid ""
+"Blogging and forums: "
+"Blogging and Syndie plugins."
+msgstr ""
+"Blog e forum: plugin "
+"per gestire blog e per Syndie."
+
+#: i2p2www/pages/site/index.html:51
+#, python-format
+msgid ""
+"Website hosting: Integrated"
+" anonymous web server."
+msgstr ""
+"Host di siti web: web "
+"server anonimo integrato."
+
+#: i2p2www/pages/site/index.html:56
+#, python-format
+msgid ""
+"Real-time chat: Instant "
+"messaging and IRC clients."
+msgstr ""
+"Chat in tempo reale: "
+"messaggistica immediata e client IRC."
+
+#: i2p2www/pages/site/index.html:61
+#, python-format
+msgid ""
+"File sharing: ED2K and "
+"Gnutella clients, integrated BitTorrent client."
+msgstr ""
+"File sharing: client ED2K e "
+"Gnutella, client BitTorrent integrato."
+
+#: i2p2www/pages/site/index.html:66
+#, python-format
+msgid ""
+"Decentralized file "
+"storage: Tahoe-LAFS distributed filesystem plugin."
+msgstr ""
+"Deposito file "
+"decentralizzato: plugin per il filesystem distribuito Tahoe-LAFS."
+
+#: i2p2www/pages/site/index.html:71
+#, python-format
+msgid "More supported applications…"
+msgstr ""
+"Altre applicazioni "
+"supportate…"
+
+#: i2p2www/pages/site/index.html:79
+msgid "News & Updates"
+msgstr "News & aggiornamenti"
+
+#: i2p2www/pages/site/links.html:4
+msgid "Recommended Links & Resources"
+msgstr "Link e risorse consigliate"
+
+#: i2p2www/pages/site/links.html:5
+#, python-format
+msgid ""
+"See also the page with\n"
+"links to presentations, videos, and tutorials about"
+" I2P."
+msgstr ""
+"\"Consulta\" anche la pagina con i\n"
+"link alle presentazioni, ai video e ai tutorial "
+"relativi ad I2P."
+
+#: i2p2www/pages/site/links.html:12
+msgid "I2P on the web"
+msgstr "I2P sul web"
+
+#: i2p2www/pages/site/links.html:20
+msgid "Friends of I2P"
+msgstr "Amici di I2P"
+
+#: i2p2www/pages/site/links.html:32
+msgid "More Projects and Documentation"
+msgstr "Altri progetti e documentazione"
+
+#: i2p2www/pages/site/links.html:42
+msgid "Press"
+msgstr "Stampa"
+
+#: i2p2www/pages/site/links.html:46
+msgid "Boards, newssite, others"
+msgstr "Bacheche, siti di notizie, altri"
+
+#: i2p2www/pages/site/links.html:50
+msgid "Very Old Stuff"
+msgstr "Materiale molto vecchio"
+
diff --git a/i2p2www/translations/it/LC_MESSAGES/research.po b/i2p2www/translations/it/LC_MESSAGES/research.po
new file mode 100644
index 00000000..63b0e1d1
--- /dev/null
+++ b/i2p2www/translations/it/LC_MESSAGES/research.po
@@ -0,0 +1,173 @@
+# Italian translations for I2P.
+# Copyright (C) 2013 ORGANIZATION
+# This file is distributed under the same license as the I2P project.
+#
+# Translators:
+# fletcherlynd , 2013
+msgid ""
+msgstr ""
+"Project-Id-Version: I2P\n"
+"Report-Msgid-Bugs-To: http://trac.i2p2.de\n"
+"POT-Creation-Date: 2013-11-21 23:32+0000\n"
+"PO-Revision-Date: 2013-11-21 23:37+0000\n"
+"Last-Translator: str4d \n"
+"Language-Team: Italian "
+"(http://www.transifex.com/projects/p/I2P/language/it/)\n"
+"Plural-Forms: nplurals=2; plural=(n != 1)\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=utf-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"Generated-By: Babel 0.9.6\n"
+
+#: i2p2www/pages/site/research/index.html:2
+msgid "Academic Research"
+msgstr "Ricerca accademica"
+
+#: i2p2www/pages/site/research/index.html:4
+msgid ""
+"Academic research and analysis of I2P is an important part of ensuring "
+"that the software and network performs as expected and is safe for users "
+"in hostile environments."
+msgstr ""
+"La ricerca e l'analisi accademica di I2P riveste un ruolo mportante per "
+"assicurarsi che le prestazioni del software e della rete siano quelle "
+"volute e gli utenti siano al riparo da ambienti ostili."
+
+#: i2p2www/pages/site/research/index.html:8
+#, python-format
+msgid ""
+"\n"
+"There is a large research community investigating a wide range of aspects"
+" of\n"
+"anonymity. For a current and comprehensive list of relevant papers, see "
+"the\n"
+"Free Haven Anonymity Bibliography.\n"
+"I2P benefits from much of the research into Tor and onion routing, but "
+"there is\n"
+"little dedicated research interest into the theory behind I2P, and the "
+"choices\n"
+"and tradeoffs that the network makes. This presents a unique opportunity "
+"for\n"
+"original research.\n"
+msgstr ""
+"\n"
+"Esiste una grande comunità di ricerca che indaga una vasta gamma di "
+"aspetti \n"
+"relativi all'anonimato. Per un elenco aggiornato e completo di documenti,"
+"\n"
+"consulta la bibliografia di Free Haven "
+"Anonymity.\n"
+"I2P si avvantaggia di molte delle ricerche relative a Tor e all'onion "
+"routing, \n"
+"ma c'è poco interesse dedicato alla ricerca nel campo della teoria alla "
+"base\n"
+"di I2P e alle scelte e ai compromessi fatti dalla rete. Questo presenta "
+"una\n"
+"opportunità di ricerca originale unica.\n"
+
+#: i2p2www/pages/site/research/index.html:18
+#, python-format
+msgid ""
+"A list of known published papers about I2P is available here."
+msgstr ""
+"Un elenco di documenti pubblicati inerenti a I2P di cui siamo a "
+"conoscenza è disponibile qui."
+
+#: i2p2www/pages/site/research/index.html:22
+msgid "Testing Attacks on I2P"
+msgstr "Collaudo degli attacchi su I2P"
+
+#: i2p2www/pages/site/research/index.html:24
+msgid ""
+"I2P can be run as a separate test network by controlling the locations "
+"that a new router reseeds from so that it only finds other test routers."
+msgstr ""
+"I2P può essere eseguita come una rete di collaudo separata controllando "
+"le posizioni da cui un nuovo router effettua il reseed in modo che trovi "
+"soltanto altri router di collaudo."
+
+#: i2p2www/pages/site/research/index.html:28
+msgid ""
+"The standard mode of operation is to have one JVM per router instance; "
+"hence running multiple copies of I2P on a single machine is inadvisable, "
+"both due to the potential resource drain and the certain port conflicts. "
+"To better facilitate setting up small test networks, I2P has a "
+"multirouter mode which enables multiple distinct routers to be run in the"
+" same JVM."
+msgstr ""
+"La modalità operativa standard è di avere una JVM per ogni istanza di "
+"router; quindi non è consigliabile eseguire copie multiple di I2P su un "
+"solo computer, sia per il potenziale assorbimento di risorse sia per i "
+"conflitti che potrebbero verificarsi su determinate porte. Per facilitare"
+" meglio l'impostazione di piccole reti di collaudo, I2P dispone di una "
+"modalità multirouter che attiva molteplici router separati da eseguire "
+"sulla stessa JVM."
+
+#: i2p2www/pages/site/research/index.html:32
+msgid ""
+"MultiRouter can be started from the i2p base directory by running the "
+"below command."
+msgstr ""
+"Il MultiRouter può essere avviato dalla cartella base di i2p eseguendo il"
+" seguente comando."
+
+#: i2p2www/pages/site/research/index.html:37
+msgid ""
+"Additionally, I2P can be started in a virtual network mode. This mode "
+"disables all transports, allowing the router to be tested in isolation "
+"without network traffic. To enable this mode, add "
+"i2p.vmCommSystem=true to the router.config before starting."
+msgstr ""
+"Inoltre, I2P può essere avviato in modalità di rete virtuale. Tale "
+"modalità disattiva tutti i trasporti, consentendo il collaudo del router "
+"in isolamento senza traffico di rete. Per attivare questa modalità, "
+"aggiungi i2p.vmCommSystem=true a router.config prima di "
+"cominciare."
+
+#: i2p2www/pages/site/research/index.html:41
+msgid "Testing the Live I2P Network"
+msgstr "Collaudo della rete I2P live"
+
+#: i2p2www/pages/site/research/index.html:43
+#, python-format
+msgid ""
+"If you are planning on conducting research on the live I2P network, "
+"please contact us before you commence your "
+"testing. While we do not discourage researchers from responsibly testing "
+"their ideas on the live network, if an attack becomes apparent and we "
+"don't have any line of communication then we will end up taking "
+"countermeasures which could interfere with the test."
+msgstr ""
+"Se stai programmando di condurre una ricerca sulla rete I2P live, contattaci prima di iniziare il collaudo. "
+"Sebbene non scoraggiamo i ricercatori dal mettere alla prova "
+"responsabilmente le loro idee sulla nostra rete live, se un attacco si "
+"manifesta e non disponiamo di alcuna linea di comunicazione finiremo con "
+"il prendere delle contromisure che potrebbero interferire con il "
+"collaudo."
+
+#: i2p2www/pages/site/research/questions.html:2
+msgid "Open research questions"
+msgstr "Domande di ricerca aperte"
+
+#: i2p2www/pages/site/research/questions.html:4
+msgid "Network database"
+msgstr ""
+
+#: i2p2www/pages/site/research/questions.html:6
+msgid "Peer selection"
+msgstr ""
+
+#: i2p2www/pages/site/research/questions.html:8
+msgid "Tunnels and Destinations"
+msgstr ""
+
+#: i2p2www/pages/site/research/questions.html:10
+msgid "Unidirectional tunnels"
+msgstr "Tunnel unidirezionali"
+
+#: i2p2www/pages/site/research/questions.html:16
+msgid "Multihoming"
+msgstr ""
+
diff --git a/i2p2www/translations/ja/LC_MESSAGES/priority.po b/i2p2www/translations/ja/LC_MESSAGES/priority.po
new file mode 100644
index 00000000..35a3f6c9
--- /dev/null
+++ b/i2p2www/translations/ja/LC_MESSAGES/priority.po
@@ -0,0 +1,2638 @@
+# Japanese translations for I2P.
+# Copyright (C) 2013 ORGANIZATION
+# This file is distributed under the same license as the I2P project.
+#
+# Translators:
+# plazmism , 2013
+msgid ""
+msgstr ""
+"Project-Id-Version: I2P\n"
+"Report-Msgid-Bugs-To: http://trac.i2p2.de\n"
+"POT-Creation-Date: 2013-11-27 00:23+0000\n"
+"PO-Revision-Date: 2013-11-27 00:30+0000\n"
+"Last-Translator: str4d \n"
+"Language-Team: Japanese "
+"(http://www.transifex.com/projects/p/I2P/language/ja/)\n"
+"Plural-Forms: nplurals=1; plural=0\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=utf-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"Generated-By: Babel 0.9.6\n"
+
+#: i2p2www/pages/blog/category.html:2
+msgid "Blog Category"
+msgstr ""
+
+#: i2p2www/pages/blog/category.html:4
+#, python-format
+msgid "I2P Blog ATOM Feed for Category: %(category)s"
+msgstr ""
+
+#: i2p2www/pages/blog/index.html:2 i2p2www/pages/blog/post.html:3
+#: i2p2www/pages/global/nav.html:95
+msgid "Blog"
+msgstr "ブログ"
+
+#: i2p2www/pages/blog/index.html:4 i2p2www/pages/site/index.html:78
+msgid "I2P Blog ATOM Feed"
+msgstr "I2P ブログ ATOMフィード"
+
+#: i2p2www/pages/blog/index.html:17
+#, python-format
+msgid "Posted %(date)s by %(author)s"
+msgstr ""
+
+#: i2p2www/pages/blog/latest.html:5
+msgid "More blog posts…"
+msgstr "その他のブログ記事hellip;"
+
+#: i2p2www/pages/blog/post.html:6
+msgid "Posted:"
+msgstr ""
+
+#: i2p2www/pages/blog/post.html:7
+msgid "Author:"
+msgstr ""
+
+#: i2p2www/pages/downloads/debian.html:4
+msgid "Debian I2P Packages"
+msgstr "Debian用 I2P パッケージ"
+
+#: i2p2www/pages/downloads/debian.html:6
+msgid ""
+"The Debian packages\n"
+"have been tested and should work on x86/x86_64 platforms running:"
+msgstr ""
+
+#: i2p2www/pages/downloads/debian.html:11
+msgid "Ubuntu (Precise 12.04 and newer)"
+msgstr ""
+
+#: i2p2www/pages/downloads/debian.html:13
+msgid "Debian Linux (Squeeze and newer) & kFreeBSD"
+msgstr ""
+
+#: i2p2www/pages/downloads/debian.html:17
+#, python-format
+msgid ""
+"The I2P packages may work on systems not listed above. Please "
+"report any issues\n"
+"with these packages on Trac at\n"
+"https://trac.i2p2.de."
+msgstr ""
+
+#: i2p2www/pages/downloads/debian.html:23
+msgid ""
+"Option 1: Recent versions of Ubuntu and its "
+"derivatives (Try this if you're not using Debian)"
+msgstr ""
+"選択肢 1: Ubuntu及びその派生 の最新のバージョン "
+"(Debianを使っていなければこれを試してください)"
+
+#: i2p2www/pages/downloads/debian.html:24
+msgid "Option 2: Debian (including Debian-derivatives)"
+msgstr ""
+
+#: i2p2www/pages/downloads/debian.html:27
+msgid ""
+"Instructions for Ubuntu Precise Pangolin (and newer) and derivatives like"
+" Linux Mint & Trisquel"
+msgstr ""
+
+#: i2p2www/pages/downloads/debian.html:28
+msgid "Adding the PPA via the command line and installing I2P"
+msgstr "コマンドライン経由でPPAを追加して、I2Pをインストールする"
+
+#: i2p2www/pages/downloads/debian.html:31
+msgid "Open a terminal and enter:"
+msgstr "ターミナルを開いて入力:"
+
+#: i2p2www/pages/downloads/debian.html:33
+msgid ""
+"This command will add the PPA to /etc/apt/sources.list.d and fetch the\n"
+"gpg key that the repository has been signed with. The GPG key ensures\n"
+"that the packages have not been tampered with since being built."
+msgstr ""
+"このコマンドは /etc/apt/sources.list.d にPPAを追加し、レポジトリが署名された GPG キー を取得します。 GPG "
+"キーはパッケージがビルドされてから改竄されていないか確認します。"
+
+#: i2p2www/pages/downloads/debian.html:40
+msgid "Notify your package manager of the new PPA by entering:"
+msgstr "入力して、新しいPPAのパッケージマネージャーを通知:"
+
+#: i2p2www/pages/downloads/debian.html:42
+msgid ""
+"This command will retrieve the latest list of software from each\n"
+"repository that is enabled on your system, including the I2P PPA that\n"
+"was added with the earlier command."
+msgstr ""
+"このコマンドは、システムで有効になっている各レポジトリから、その前のコマンドで追加された I2P PPA "
+"を含む最新のソフトウェアの一覧を取得します。"
+
+#: i2p2www/pages/downloads/debian.html:48
+msgid "You are now ready to install I2P!"
+msgstr "I2P をインストールする準備が出来ました！"
+
+#: i2p2www/pages/downloads/debian.html:52
+msgid "Adding the PPA Using Synaptic"
+msgstr "PPA に Synaptic の利用 を追加"
+
+#: i2p2www/pages/downloads/debian.html:55
+msgid ""
+"Open Synaptic (System -> Administration -> Synaptic Package "
+"Manager)."
+msgstr "Synaptic を開く (システム -> 管理 -> Synapticパッケージマネージャ)。"
+
+#: i2p2www/pages/downloads/debian.html:60
+msgid ""
+"Once Synaptic opens, select Repositories from the "
+"Settings menu."
+msgstr "Synaptic を開いて、 設定 メニューから レポジトリ を選択してください。"
+
+#: i2p2www/pages/downloads/debian.html:65
+msgid ""
+"Click the Other Sources tab and click Add. Paste "
+"ppa:i2p-maintainers/i2p into the APT-line field and click "
+"Add Source. Click the Close button then "
+"Reload."
+msgstr ""
+"その他のソースタブをクリックして、追加をクリックしてください。 ppa:i2p-"
+"maintainers/i2pを APT-line フィールドに貼り付けて、ソースを追加 をクリックしてください。"
+
+#: i2p2www/pages/downloads/debian.html:70
+msgid ""
+"In the Quick Filter box, type in i2p and press enter. When "
+"i2p is returned in the results list, right click "
+"i2p and select Mark for Installation. After doing "
+"so you may see a Mark additional required changes? popup. If so,"
+" click Mark then Apply."
+msgstr "クイックフィルタボックスで、i2pを打ち込んで、エンターを押してください。i2pが結果リストで返還された時、i2pを右クリックして、インストールのためマークを選択してください。そうした後に、さらに必要な変更をマークしますか？ポップアップが表示されます。そうなったら、マークをクリックしてから適用をクリックしてください。"
+
+#: i2p2www/pages/downloads/debian.html:76
+msgid ""
+"After the installation process completes you can move on to the next\n"
+"part of starting I2P and configuring "
+"it for your system."
+msgstr ""
+"インストールプロセスが完了した後、I2Pを始めるの\n"
+"次のパートに移動して、システムの設定ができます。"
+
+#: i2p2www/pages/downloads/debian.html:81
+msgid "Instructions for Debian"
+msgstr ""
+
+#: i2p2www/pages/downloads/debian.html:85
+msgid ""
+"Note: The steps below should be performed with root access (i.e., "
+"switching\n"
+"user to root with \"su\" or by prefixing each command with \"sudo\")."
+msgstr ""
+
+#: i2p2www/pages/downloads/debian.html:90
+#, python-format
+msgid "Add lines like the following to %(file)s."
+msgstr ""
+
+#: i2p2www/pages/downloads/debian.html:111
+#, python-format
+msgid ""
+"Download the key used to sign the repository"
+" and add it to apt:"
+msgstr ""
+
+#: i2p2www/pages/downloads/debian.html:118
+msgid "Notify your package manager of the new repository by entering"
+msgstr ""
+
+#: i2p2www/pages/downloads/debian.html:120
+msgid ""
+"This command will retrieve the latest list of software from every\n"
+"repository enabled on your system, including the I2P repository added in "
+"step\n"
+"1."
+msgstr ""
+
+#: i2p2www/pages/downloads/debian.html:126
+msgid ""
+"You are now ready to install I2P! Installing the i2p-keyring"
+"\n"
+"package will ensure that you receive updates to the repository's GPG key."
+msgstr ""
+
+#: i2p2www/pages/downloads/debian.html:133
+msgid ""
+"After the installation process completes you can move on to the next part"
+" of starting I2P and configuring it "
+"for your system."
+msgstr ""
+"インストールプロセスが完了した後、I2Pを始めるの次のパートに移動して、システムの設定ができます。"
+
+#: i2p2www/pages/downloads/debian.html:137
+#: i2p2www/pages/downloads/list.html:171
+msgid "Post-install work"
+msgstr "インストール後の作業"
+
+#: i2p2www/pages/downloads/debian.html:139
+msgid ""
+"Using these I2P packages the I2P router can be started in the following\n"
+"three ways:"
+msgstr "これら I2P のパッケージを使用して、以下の3つのやり方で、I2P ルーターを始めることができます。"
+
+#: i2p2www/pages/downloads/debian.html:145
+msgid ""
+""on demand" using the i2prouter script. Simply run "
+""i2prouter\n"
+"start" from a command prompt. (Note: Do "
+"not use\n"
+"sudo or run it as root!)"
+msgstr ""
+""要求に応じて" i2prouter スクリプトを使用してください。コマンドラインから "
+""i2prouter\n"
+"start" を走らせるだけで構いません。 (注: "
+"sudoを使用したり、rootで起動するのはやめてください！)"
+
+#: i2p2www/pages/downloads/debian.html:152
+msgid ""
+""on demand" without the java service wrapper\n"
+"(needed on non-Linux/non-x86 systems) by running \"i2prouter-"
+"nowrapper\".\n"
+"(Note: Do not\n"
+"use sudo or run it as root!)"
+msgstr ""
+""要求に応じて"\"i2prouter-nowrapper\"を走らせて、\n"
+"java "
+"サービスラッパーを無効にしてください(非Linux/非x86システムで必要)。\n"
+"(注: sudoを使用したり、rootで起動するのは\n"
+"やめてください！)"
+
+#: i2p2www/pages/downloads/debian.html:160
+msgid ""
+"as a service that automatically runs when your system boots, even\n"
+"before logging in. The service can be enabled with \"dpkg-"
+"reconfigure\n"
+"i2p\" as root or using sudo. This is the recommended means of "
+"operation."
+msgstr ""
+"システムをブートした際に、ログインする前の時点で自動的に起動するサービスとして。サービスは\n"
+"ルートとしてまたはsudoを使用して、\"dpkg-reconfigure i2p\"で有効にできます。"
+
+#: i2p2www/pages/downloads/debian.html:168
+msgid ""
+"When installing for the first time, please remember to adjust your "
+"NAT/firewall\n"
+"if you can. The ports to forward can be found on the \n"
+"network configuration page in the router console. If guidance with "
+"respect to forwarding ports is needed,\n"
+"you may find portforward.com to be"
+" helpful."
+msgstr ""
+
+#: i2p2www/pages/downloads/debian.html:175
+msgid ""
+"Please review and adjust the bandwidth settings on the\n"
+"configuration page,\n"
+"as the default settings of 96 KB/s down / 40 KB/s up are fairly "
+"conservative."
+msgstr ""
+"設定ページで、\n"
+"規定の設定である 96KB/s ダウン 40KB/s アップはかなり控えめであるので、\n"
+"帯域幅設定を確認・調整してください。"
+
+#: i2p2www/pages/downloads/debian.html:181
+#: i2p2www/pages/downloads/list.html:204
+#, python-format
+msgid ""
+"If you want to reach eepsites via your browser, have a look on the browser proxy setup page for an easy "
+"howto."
+msgstr ""
+"ブラウザ経由で eepsites に到達したい場合、簡単なやり方はブラウザのプロキシ設定ページで確認可能です。"
+
+#: i2p2www/pages/downloads/list.html:2 i2p2www/pages/downloads/select.html:12
+#: i2p2www/pages/global/nav.html:3
+msgid "Download"
+msgstr "ダウンロード"
+
+#: i2p2www/pages/downloads/list.html:9
+msgid "Download I2P"
+msgstr "I2P をダウンロード"
+
+#: i2p2www/pages/downloads/list.html:11
+msgid "Dependency"
+msgstr "依存関係"
+
+#: i2p2www/pages/downloads/list.html:12
+#, python-format
+msgid ""
+"\n"
+"Java Runtime 1.5 or higher.\n"
+"(Oracle Java Version 7,\n"
+"OpenJDK 7, or\n"
+"IcedTea7\n"
+" recommended,\n"
+"except Raspberry Pi: Oracle 8 Early Access,\n"
+"PowerPC: IBM SDK 7)\n"
+"
\n"
+"Determine your installed Java version here\n"
+"or type java -version at your command prompt.\n"
+msgstr ""
+
+#: i2p2www/pages/downloads/list.html:30
+msgid "Clean installs"
+msgstr "クリーンインストール"
+
+#: i2p2www/pages/downloads/list.html:37 i2p2www/pages/downloads/list.html:54
+#: i2p2www/pages/downloads/list.html:81 i2p2www/pages/downloads/list.html:140
+#: i2p2www/pages/downloads/list.html:269
+msgid "select alternate link"
+msgstr ""
+
+#: i2p2www/pages/downloads/list.html:44
+msgid "Download that file and run it."
+msgstr "そのファイルをダウンローして、起動させる"
+
+#: i2p2www/pages/downloads/list.html:61
+#, python-format
+msgid ""
+"Download that file and double-click it (if that works) or\n"
+" type java -jar i2pinstall_%(i2pversion)s.jar in a "
+"terminal to run the\n"
+" installer.\n"
+" You may be able to right-click and select\n"
+" "Open with Java"."
+msgstr ""
+
+#: i2p2www/pages/downloads/list.html:69 i2p2www/pages/downloads/list.html:96
+msgid "Command line (headless) install:"
+msgstr "コマンドライン (UIなし) インストール:"
+
+#: i2p2www/pages/downloads/list.html:70
+#, python-format
+msgid ""
+"Download the %(i2pversion)s OSX graphical installer file above and\n"
+" run java -jar i2pinstall_%(i2pversion)s.jar -console "
+"from the command line."
+msgstr ""
+
+#: i2p2www/pages/downloads/list.html:88
+#, python-format
+msgid ""
+"Download that file and double-click it (if that works) or\n"
+" type java -jar i2pinstall_%(i2pversion)s.jar in a "
+"terminal to run the\n"
+" installer.\n"
+" On some platforms you may be able to right-click and select\n"
+" "Open with Java"."
+msgstr ""
+"そのファイルをダウンロードして、ダブルクリック (それで動く場合) または\n"
+"ターミナルで java -jar i2pinstall_%(i2pversion)s.jar を入力して、\n"
+"インストーラーを起動。\n"
+"一部のプラットフォームでは、右クリックして\n"
+""Java で開く"を選択できる場合があります。"
+
+#: i2p2www/pages/downloads/list.html:97
+#, python-format
+msgid ""
+"Download the graphical installer file above and\n"
+" run java -jar i2pinstall_%(i2pversion)s.jar -console "
+"from the command line."
+msgstr ""
+"上のグラフィカル・インストーラーファイルをダウンロードして\n"
+"コマンドラインから java -jar i2pinstall_%(i2pversion)s.jar -console "
+"を実行してください。"
+
+#: i2p2www/pages/downloads/list.html:107
+msgid "Packages for Debian & Ubuntu are available."
+msgstr "Debian 及び Ubuntu 用パッケージが利用可能です。"
+
+#: i2p2www/pages/downloads/list.html:121
+#, python-format
+msgid ""
+"The above file is the current release build.\n"
+" The latest dev build is version %(devbuild)s, and is available from\n"
+" str4d's eepsite."
+msgstr ""
+
+#: i2p2www/pages/downloads/list.html:127
+msgid ""
+"The release and dev versions of the I2P APK are not compatible, as they\n"
+" are signed by zzz and str4d respectively. Uninstall one before "
+"installing\n"
+" the other."
+msgstr ""
+
+#: i2p2www/pages/downloads/list.html:137
+msgid "Source package"
+msgstr "ソースパッケージ"
+
+#: i2p2www/pages/downloads/list.html:147
+#, python-format
+msgid ""
+"Alternately, you can fetch the source from monotone\n"
+" or via Git from git.repo.i2p or Github.\n"
+"
\n"
+" Run (tar xjvf i2psource_%(i2pversion)s.tar.bz2 ; cd "
+"i2p-%(i2pversion)s ; ant pkg) then either\n"
+" run the GUI installer or headless install as above."
+msgstr ""
+
+#: i2p2www/pages/downloads/list.html:162
+#, python-format
+msgid ""
+"The files are signed by zzz,\n"
+"whose key is here."
+msgstr ""
+"ファイルはzzzで署名されており、\n"
+"キーの所有者はここです。"
+
+#: i2p2www/pages/downloads/list.html:167
+msgid ""
+"I2P can also be downloaded from our project pages on Launchpad and Google Code."
+msgstr ""
+"I2Pは Launchpad と Google Code "
+"のプロジェクトページからダウンロードすることもできます。"
+
+#: i2p2www/pages/downloads/list.html:173
+msgid ""
+"After running the installer on windows, simply click on the \"Start I2P\""
+" button\n"
+"which will bring up the router console,\n"
+"which has further instructions."
+msgstr ""
+"windows でインストーラーを起動した後、「I2P を始める」ボタンをクリックするだけで\n"
+"ルーター・コンソールが現れ\n"
+"さらなる指示が表示されます。"
+
+#: i2p2www/pages/downloads/list.html:179
+msgid ""
+"On Unix-like systems, I2P can be started as a service\n"
+"using the \"i2prouter\" script, located in the directory you selected for"
+" I2P.\n"
+"Changing to that directory in a console and issuing \"sh i2prouter "
+"status\"\n"
+"should tell you the router's status. The arguments \"start\", \"stop\" "
+"and \"restart\"\n"
+"control the service. The router console\n"
+"can be accessed at its usual location.\n"
+"For users on OpenSolaris and other systems for which the wrapper (i2psvc)"
+" is not supported,\n"
+"start the router with \"sh runplain.sh\" instead."
+msgstr ""
+"Unixライクなシステムでは、 I2P は I2P 用に選択したディレクトリにある\n"
+"\"i2prouter\" スクリプトを使用するサービスとして起動します。\n"
+"コンソールでそのディレクトリに変更し、 \"sh i2prouter status\" とすることで\n"
+"ルーターの状態が示されるはずです。引数 \"start\" や \"stop\" 、 \"restart\"\n"
+"はサービスをコントロールします。ルーター・コンソール\n"
+"は通常の位置でアクセスできます。\n"
+"OpenSolaris 及びラッパー (i2psvc) がサポートされていないその他のシステムのユーザーについては、代わりに \"sh "
+"runplain.sh\" でルーターを起動してください。"
+
+#: i2p2www/pages/downloads/list.html:190
+#, python-format
+msgid ""
+"When installing for the first time, please remember to adjust your "
+"NAT/firewall\n"
+"if you can, bearing in mind the Internet-facing ports I2P uses,\n"
+"described here among other ports.\n"
+"If you have successfully opened your port to inbound TCP, also enable "
+"inbound TCP on the\n"
+"configuration page."
+msgstr ""
+"初めてインストールする際は、 可能であれば、 I2P が使用するインターネッツ接続ポートを念頭に入れて\n"
+"NAT/ファイアーウォールを調整することを忘れないでください。\n"
+"他のポートの中でここで説明されています。\n"
+"正常に入力 TCP にポートを開放できたら、 設定ページでも\n"
+"入力 TCP が有効になります。"
+
+#: i2p2www/pages/downloads/list.html:198
+msgid ""
+"Also, please review and adjust the bandwidth settings on the\n"
+"configuration page,\n"
+"as the default settings of 96 KBps down / 40 KBps up are fairly slow."
+msgstr ""
+"また、設定ページにて\n"
+"規定の設定である 96KBps ダウン 40KBps アップはかなり遅いので\n"
+"帯域幅設定を確認・調整してください。"
+
+#: i2p2www/pages/downloads/list.html:208
+msgid "Updates from earlier releases:"
+msgstr "以前のリリースからアップデート:"
+
+#: i2p2www/pages/downloads/list.html:210
+msgid "Both automatic and manual upgrades are available for the release."
+msgstr "自動手動アップデート双方がこのリリースに利用できます。"
+
+#: i2p2www/pages/downloads/list.html:215
+msgid "Automatic updates"
+msgstr "自動アップデート"
+
+#: i2p2www/pages/downloads/list.html:217
+msgid ""
+"If you are running 0.7.5 or later, your router should detect the\n"
+"new release. To upgrade simply click the 'Download Update' button on your"
+" router console\n"
+"when it appears."
+msgstr "0.7.5以降を起動している場合、ルーターが新リリースを検出するはずです。アップグレードするには、表示時にただルーターコンソールの「アップデートをダウンロード」ボタンをクリックするだけで構いません。"
+
+#: i2p2www/pages/downloads/list.html:223
+msgid ""
+"Due to a bug in release 0.7.6, those whose first I2P installation was "
+"that version\n"
+"and have not upgraded manually\n"
+"may get a \"downloaded version is not greater than current version\" "
+"error,\n"
+"and should use the manual update method below."
+msgstr ""
+"リリース 0.7.6にあるバグのため、最初のI2Pのインストールがそのバージョンで\n"
+"手動でアップグレードしなかったものは\n"
+"「ダウンロードされたバージョンは現在のバージョン以降のものでありません」エラーが出る場合があり、\n"
+"以下の手動アップデート手段を使用するべきです。"
+
+#: i2p2www/pages/downloads/list.html:231
+#, python-format
+msgid ""
+"If you are running 0.7.4 or earlier, please see\n"
+"the 0.7.5 release notes\n"
+"for important information about how to configure your router to "
+"automatically\n"
+"receive the release."
+msgstr ""
+"0.7.4以前を動作中の場合、\n"
+"ルータが自動的にリリースを受け取るようにさせる\n"
+"設定方法に関する重要な情報について\n"
+"0.7.5のリリースノートをご覧ください。"
+
+#: i2p2www/pages/downloads/list.html:239
+#, python-format
+msgid ""
+"If you are running 0.6.1.30 or earlier, please see\n"
+"instructions\n"
+"for important information about how to configure your router to "
+"automatically\n"
+"receive the release."
+msgstr ""
+"0.6.1.30以前を動作中の場合、\n"
+"ルータが自動的にリリースを受け取るようにさせる\n"
+"設定方法に関する重要な情報について\n"
+"指示をご覧ください。"
+
+#: i2p2www/pages/downloads/list.html:248
+#, python-format
+msgid ""
+"If you have reconfigured your router following the instructions, you should see a link on your"
+" \n"
+" router console "
+"allowing\n"
+" you to download and install the new release by just clicking on that\n"
+" link."
+msgstr ""
+"指示に従って、ルーターを再設定した場合、ルーターコンソールでリンクをご覧になれば、\n"
+"そのリンクをクリックするだけで新リリースをダウンロードし、インストールできるようになるはずです。"
+
+#: i2p2www/pages/downloads/list.html:256
+msgid "Alternately, you can use the manual method specified below."
+msgstr "代わりに、以下で示される手動の方法を使用できます。"
+
+#: i2p2www/pages/downloads/list.html:266
+msgid "Manual updates"
+msgstr "手動アップデート"
+
+#: i2p2www/pages/downloads/list.html:278
+msgid ""
+"Download that file to your I2P\n"
+" installation directory and rename as i2pupdate.zip.\n"
+" (alternately, you can get the source as above and run \"ant "
+"updater\", then copy the\n"
+" resulting i2pupdate.zip to your I2P installation directory). You do"
+" \n"
+" NOT need to unzip that file."
+msgstr ""
+"そのファイルを I2P のインストールディレクトリに\n"
+"ダウンロードして、 i2pupdate.zip に名前を変更してください。\n"
+"(代わりに、上記のようにソースを入手して、「ant updater」を起動させてから、 I2P のインストールディレクトリにその結果できた "
+"i2pupdate.zip をコピーすることもできます)。そのファイルを解凍する必要はありません。"
+
+#: i2p2www/pages/downloads/list.html:287
+msgid "Click \"Restart\""
+msgstr "「再起動」をクリック"
+
+#: i2p2www/pages/downloads/list.html:292
+msgid "Grab a cup of coffee and come back in 11 minutes"
+msgstr "コーヒーでも飲んで、11分後戻ってきてください"
+
+#: i2p2www/pages/downloads/list.html:300
+#, python-format
+msgid ""
+"The file is signed by zzz,\n"
+"whose key is here."
+msgstr ""
+"ファイルは zzz で署名されており、\n"
+"そのキーはこちらです。"
+
+#: i2p2www/pages/downloads/list.html:305
+msgid "Previous Releases"
+msgstr "以前のリリース"
+
+#: i2p2www/pages/downloads/list.html:307
+#, python-format
+msgid ""
+"Previous releases are available on Google "
+"Code\n"
+"and Launchpad\n"
+"and within the I2P network on %(echelon)s."
+msgstr ""
+"以前のリリースは Google "
+"Code\n"
+"や Launchpad\n"
+"及び%(echelon)sの I2P ネットワーク内で入手できます。"
+
+#: i2p2www/pages/downloads/select.html:2 i2p2www/pages/downloads/select.html:4
+msgid "Mirror selection"
+msgstr "ミラー選択"
+
+#: i2p2www/pages/downloads/select.html:5
+msgid "File:"
+msgstr "ファイル:"
+
+#: i2p2www/pages/downloads/select.html:10
+msgid "Any mirror"
+msgstr "すべてのミラー"
+
+#: i2p2www/pages/global/bounty.html:19
+msgid ""
+"To claim the bounty the author must not be paid by other organizations\n"
+"or teams for this work (e.g. GSoC students are not valid)."
+msgstr ""
+"作者が、この仕事に対して他の組織やチームに支払ってもらってはならない報奨金を\n"
+"主張するには (例: GSoCの学生は有効ではありません)。"
+
+#: i2p2www/pages/global/bounty.html:29
+#, python-format
+msgid ""
+"Bounty amounts may be increased by further donations. Do\n"
+"you think these are important? Add in your "
+"donation, \n"
+"marking the amount for the %(donatename)s bounty!"
+msgstr ""
+"報奨金の額は、寄付が多ければ増えるかもしれません。\n"
+"これらが重要だと思いませんか？ 寄付を加えてください\n"
+" %(donatename)s の報奨金の額がマークされます！"
+
+#: i2p2www/pages/global/error_404.html:3
+msgid "Not found"
+msgstr "Not found"
+
+#: i2p2www/pages/global/error_404.html:9
+msgid ""
+"Yep... the resource, you were searching for, is named differently, "
+"doesn't exist or was removed."
+msgstr "あなたが探していたリソースは異なる名前であるか、存在しないか、削除されました。"
+
+#: i2p2www/pages/global/error_500.html:5
+msgid "Server error"
+msgstr "サーバーエラー"
+
+#: i2p2www/pages/global/error_500.html:13
+msgid "500 Server error"
+msgstr "500 Server error"
+
+#: i2p2www/pages/global/error_500.html:17
+msgid "Umm... the server encountered some sort of error."
+msgstr "サーバーになんらかのエラーが発生しました。"
+
+#: i2p2www/pages/global/footer.html:2
+msgid "Mirrors"
+msgstr "ミラー"
+
+#: i2p2www/pages/global/footer.html:9
+msgid "Secure"
+msgstr "安全"
+
+#: i2p2www/pages/global/footer.html:16
+msgid "Misc."
+msgstr "諸々"
+
+#: i2p2www/pages/global/footer.html:19 i2p2www/pages/site/links.html:2
+msgid "Links"
+msgstr "リンク"
+
+#: i2p2www/pages/global/footer.html:20
+msgid "Impressum"
+msgstr "奥付(Impressum)"
+
+#: i2p2www/pages/global/footer.html:24
+msgid "T-Shirts!"
+msgstr "Tシャツ！"
+
+#: i2p2www/pages/global/footer.html:26
+msgid "Europe"
+msgstr "欧州"
+
+#: i2p2www/pages/global/footer.html:27
+msgid "USA"
+msgstr "米国"
+
+#: i2p2www/pages/global/footer.html:31
+msgid "Donate"
+msgstr "寄付"
+
+#: i2p2www/pages/global/layout.html:29
+msgid "Skip navigation"
+msgstr ""
+
+#: i2p2www/pages/global/layout.html:32
+msgid "I2P Logo"
+msgstr "I2P ロゴ"
+
+#: i2p2www/pages/global/layout.html:32 i2p2www/pages/site/index.html:3
+msgid "The Invisible Internet Project"
+msgstr "不可視なインターネットプロジェクト"
+
+#: i2p2www/pages/global/layout.html:56
+#, python-format
+msgid ""
+"This page was last updated in %(lastupdated)s and is accurate for router "
+"version %(accuratefor)s."
+msgstr "このページは %(lastupdated)s に最終アップデートされ、ルーターバージョン %(accuratefor)s に正確です。"
+
+#: i2p2www/pages/global/layout.html:60
+#, python-format
+msgid "This page was last updated in %(lastupdated)s."
+msgstr "このページは %(lastupdated)s に最終アップデートされました。"
+
+#: i2p2www/pages/global/layout.html:64
+#, python-format
+msgid "This page is accurate for router version %(accuratefor)s."
+msgstr "このページはルーターバージョン %(accuratefor)s に正確です。"
+
+#: i2p2www/pages/global/macros:21
+msgid "Previous"
+msgstr ""
+
+#: i2p2www/pages/global/macros:36
+msgid "Next"
+msgstr ""
+
+#: i2p2www/pages/global/macros:43
+msgid "Posted in"
+msgstr ""
+
+#: i2p2www/pages/global/nav.html:4
+msgid "About"
+msgstr "アバウト"
+
+#: i2p2www/pages/global/nav.html:6
+msgid "Introduction to I2P"
+msgstr "I2P入門"
+
+#: i2p2www/pages/global/nav.html:7
+msgid "Comparisons"
+msgstr "対照"
+
+#: i2p2www/pages/global/nav.html:9
+msgid "Overview of comparisons"
+msgstr "対照要旨"
+
+#: i2p2www/pages/global/nav.html:13
+msgid "Other anonymous networks"
+msgstr "その他の匿名ネットワーク"
+
+#: i2p2www/pages/global/nav.html:16
+msgid "Documentation"
+msgstr "ドキュメント"
+
+#: i2p2www/pages/global/nav.html:18
+msgid "Documentation index"
+msgstr "ドキュメント 目録"
+
+#: i2p2www/pages/global/nav.html:19
+msgid "How does it work?"
+msgstr "どのように動作するのか？"
+
+#: i2p2www/pages/global/nav.html:21
+msgid "Gentle intro"
+msgstr "やさしい入門"
+
+#: i2p2www/pages/global/nav.html:22
+msgid "Tech intro"
+msgstr "技術的入門"
+
+#: i2p2www/pages/global/nav.html:23
+msgid "Threat model"
+msgstr "脅威モデル"
+
+#: i2p2www/pages/global/nav.html:24
+msgid "Garlic routing"
+msgstr "ガーリックルーティング"
+
+#: i2p2www/pages/global/nav.html:25
+msgid "Network database"
+msgstr "ネットワークデータベース"
+
+#: i2p2www/pages/global/nav.html:26
+msgid "Tunnel routing"
+msgstr "トンネルルーティング"
+
+#: i2p2www/pages/global/nav.html:27
+msgid "Peer selection"
+msgstr "ピア選択"
+
+#: i2p2www/pages/global/nav.html:28
+msgid "Cryptography"
+msgstr "暗号法"
+
+#: i2p2www/pages/global/nav.html:29
+msgid "ElGamal/AES+SessionTags"
+msgstr "ElGamal/AES+SessionTags"
+
+#: i2p2www/pages/global/nav.html:32
+msgid "Specifications"
+msgstr "仕様"
+
+#: i2p2www/pages/global/nav.html:34
+msgid "Blockfile"
+msgstr "ブロックファイル"
+
+#: i2p2www/pages/global/nav.html:35
+msgid "Common structures"
+msgstr "共通構造"
+
+#: i2p2www/pages/global/nav.html:36
+msgid "Configuration files"
+msgstr "設定ファイル"
+
+#: i2p2www/pages/global/nav.html:37 i2p2www/pages/global/nav.html:59
+msgid "Datagrams"
+msgstr "データグラム"
+
+#: i2p2www/pages/global/nav.html:38
+msgid "GeoIP files"
+msgstr ""
+
+#: i2p2www/pages/global/nav.html:41 i2p2www/pages/global/nav.html:91
+msgid "Plugins"
+msgstr "プラグイン"
+
+#: i2p2www/pages/global/nav.html:43 i2p2www/pages/global/nav.html:57
+msgid "Streaming library"
+msgstr "ストリーミングライブラリ"
+
+#: i2p2www/pages/global/nav.html:44
+msgid "Tunnel creation"
+msgstr "トンネル生成"
+
+#: i2p2www/pages/global/nav.html:45
+msgid "Tunnel messages"
+msgstr "トンネルメッセージ"
+
+#: i2p2www/pages/global/nav.html:46
+msgid "Software updates"
+msgstr "ソフトウェアアップデート"
+
+#: i2p2www/pages/global/nav.html:49
+msgid "API"
+msgstr "API"
+
+#: i2p2www/pages/global/nav.html:58
+msgid "Ministreaming library"
+msgstr "ミニストリーミングライブラリ"
+
+#: i2p2www/pages/global/nav.html:63 i2p2www/pages/global/nav.html:116
+msgid "Applications"
+msgstr "アプリケーション"
+
+#: i2p2www/pages/global/nav.html:65
+msgid "Supported applications"
+msgstr "サポートされるアプリケーション"
+
+#: i2p2www/pages/global/nav.html:66
+msgid "Bittorrent"
+msgstr "Bittorrent"
+
+#: i2p2www/pages/global/nav.html:69
+msgid "Protocols"
+msgstr "プロトコル"
+
+#: i2p2www/pages/global/nav.html:71
+msgid "Protocol stack"
+msgstr "プロトコルスタック"
+
+#: i2p2www/pages/global/nav.html:76
+msgid "Transports"
+msgstr "トランスポート"
+
+#: i2p2www/pages/global/nav.html:78
+msgid "Transport layer overview"
+msgstr "トランスポート層概観"
+
+#: i2p2www/pages/global/nav.html:83
+msgid "Tunnels"
+msgstr "トンネル"
+
+#: i2p2www/pages/global/nav.html:85
+msgid "Tunnel implementation"
+msgstr "トンネル実装"
+
+#: i2p2www/pages/global/nav.html:86
+msgid "Unidirectional tunnels"
+msgstr "単方向トンネル"
+
+#: i2p2www/pages/global/nav.html:87
+msgid "Old implementation"
+msgstr "旧実装"
+
+#: i2p2www/pages/global/nav.html:90
+msgid "Naming and addressbook"
+msgstr "名前付けとアドレスブック"
+
+#: i2p2www/pages/global/nav.html:94
+msgid "Team"
+msgstr "チーム"
+
+#: i2p2www/pages/global/nav.html:96
+msgid "Hall of Fame"
+msgstr "栄誉殿堂"
+
+#: i2p2www/pages/global/nav.html:97
+msgid "Academic papers and peer review"
+msgstr "学術論文とピアの精査"
+
+#: i2p2www/pages/global/nav.html:98
+msgid "Presentations, tutorials and articles"
+msgstr "プレゼンテーションとチュートリアル、記事"
+
+#: i2p2www/pages/global/nav.html:99
+msgid "Contact us"
+msgstr "お問い合わせ"
+
+#: i2p2www/pages/global/nav.html:102
+msgid "Help"
+msgstr "ヘルプ"
+
+#: i2p2www/pages/global/nav.html:104
+msgid "FAQ"
+msgstr "よくある質問"
+
+#: i2p2www/pages/global/nav.html:105
+msgid "How to browse I2P"
+msgstr "I2Pを閲覧するには"
+
+#: i2p2www/pages/global/nav.html:106
+msgid "Glossary"
+msgstr "用語集"
+
+#: i2p2www/pages/global/nav.html:107
+msgid "Performance"
+msgstr "パフォーマンス"
+
+#: i2p2www/pages/global/nav.html:108 i2p2www/pages/site/contact.html:28
+msgid "Forums"
+msgstr "フォーラム"
+
+#: i2p2www/pages/global/nav.html:111
+msgid "Volunteer"
+msgstr "ボランティア"
+
+#: i2p2www/pages/global/nav.html:113
+msgid "Get involved!"
+msgstr "参加しよう！"
+
+#: i2p2www/pages/global/nav.html:114
+msgid "Develop"
+msgstr "開発"
+
+#: i2p2www/pages/global/nav.html:117
+msgid "Licenses"
+msgstr "ライセンス"
+
+#: i2p2www/pages/global/nav.html:118
+msgid "Release signing keys"
+msgstr "署名キーのリリース"
+
+#: i2p2www/pages/global/nav.html:119
+msgid "Signed keys"
+msgstr "署名されるキー"
+
+#: i2p2www/pages/global/nav.html:120
+msgid "Developers keys"
+msgstr "開発者のキー"
+
+#: i2p2www/pages/global/nav.html:121
+msgid "Bug tracker"
+msgstr "バグトラッカー"
+
+#: i2p2www/pages/global/nav.html:124
+msgid "Academic research"
+msgstr "学術研究"
+
+#: i2p2www/pages/global/nav.html:125
+msgid "Open research questions"
+msgstr ""
+
+#: i2p2www/pages/global/nav.html:126
+msgid "Guides"
+msgstr "ガイド"
+
+#: i2p2www/pages/global/nav.html:128
+msgid "New developers"
+msgstr "新しい開発者"
+
+#: i2p2www/pages/global/nav.html:129
+msgid "Using an IDE with I2P"
+msgstr "I2PでIDEを使用"
+
+#: i2p2www/pages/global/nav.html:130
+msgid "Developer guidelines and coding style"
+msgstr "開発者ガイドラインとコーディングスタイル"
+
+#: i2p2www/pages/global/nav.html:131
+msgid "Monotone"
+msgstr "モノトーン"
+
+#: i2p2www/pages/global/nav.html:132
+msgid "New translators"
+msgstr "新しい翻訳者"
+
+#: i2p2www/pages/global/nav.html:135
+msgid "Bounties"
+msgstr "報奨金"
+
+#: i2p2www/pages/global/nav.html:136 i2p2www/pages/meetings/index.html:2
+msgid "Meetings"
+msgstr "会合"
+
+#: i2p2www/pages/global/nav.html:137
+msgid "Roadmap"
+msgstr "ロードマップ"
+
+#: i2p2www/pages/global/nav.html:138
+msgid "Task list"
+msgstr "タスクリスト"
+
+#: i2p2www/pages/global/nav.html:141
+msgid "Language"
+msgstr "言語"
+
+#: i2p2www/pages/meetings/index.html:4
+msgid "I2P Meetings ATOM Feed"
+msgstr "I2P会合 ATOMフィード"
+
+#: i2p2www/pages/meetings/index.html:7
+msgid "Logs of past I2P meetings"
+msgstr "過去の I2P 会合の記録"
+
+#: i2p2www/pages/meetings/index.html:9
+msgid "Meetings are currently on hold until a more suitable time can be chosen."
+msgstr ""
+
+#: i2p2www/pages/meetings/index.html:13
+#, python-format
+msgid ""
+"If you have something to discuss, please find the developers on IRC in "
+"#i2p-dev.\n"
+"Status updates from developers are also "
+"available."
+msgstr ""
+"議論したいことがあれば、IRC上の #i2p-dev にて開発者が見つかります。\n"
+"開発者からの状況更新も利用できます。"
+
+#: i2p2www/pages/meetings/show.html:2
+#, python-format
+msgid "I2P Development Meeting %(id)s"
+msgstr ""
+
+#: i2p2www/pages/meetings/show.html:10
+msgid "Full IRC Log"
+msgstr ""
+
+#: i2p2www/pages/papers/list.html:29
+msgid "By topic"
+msgstr ""
+
+#: i2p2www/pages/papers/list.html:35
+msgid "By date"
+msgstr ""
+
+#: i2p2www/pages/papers/list.html:41
+msgid "By author"
+msgstr ""
+
+#: i2p2www/pages/papers/list.html:83
+#, python-format
+msgid ""
+"Please send new or corrected entries to\n"
+"%(email)s.
\n"
+"If you can, please format them as BibTeX; see our\n"
+"BibTeX source page for examples.
\n"
+"Remember to include URLs if possible:\n"
+"offline papers are less useful."
+msgstr ""
+
+#: i2p2www/pages/site/contact.html:2
+msgid "Contact"
+msgstr "問い合わせ"
+
+#: i2p2www/pages/site/contact.html:4
+msgid "Email"
+msgstr ""
+
+#: i2p2www/pages/site/contact.html:11
+msgid ""
+"Our primary IRC network is the Irc2P network within I2P; a default tunnel"
+" to this network is set up with new router installs.\n"
+" We are also present on multiple standard networks like OFTC,\n"
+" EIN and Freenode.\n"
+" All I2P-related channels on all these network are linked to the main "
+"channels on Irc2P via relay bots."
+msgstr ""
+
+#: i2p2www/pages/site/contact.html:19
+msgid "Channel list:"
+msgstr "チャンネルリスト:"
+
+#: i2p2www/pages/site/contact.html:21
+msgid "General i2p discussion"
+msgstr "全般的な i2p の議論"
+
+#: i2p2www/pages/site/contact.html:22
+msgid "Offtopic"
+msgstr "主題から外れた話"
+
+#: i2p2www/pages/site/contact.html:23
+msgid "Development talk"
+msgstr "開発話"
+
+#: i2p2www/pages/site/contact.html:24
+msgid "Help channel"
+msgstr "チャンネルのヘルプ"
+
+#: i2p2www/pages/site/contact.html:29
+#, python-format
+msgid ""
+"Most of the discussion about I2P's development happens on the I2P developer forum. This is usually the best"
+" place to start with inquiries, if the dev IRC channel is inactive."
+msgstr ""
+"I2P の開発に関する議論のほとんどは、 I2P "
+"開発フォーラムで起こっています。ここは IRC チャンネルが機能していない場合、大抵は質問を始めるのに最高の場所です。"
+
+#: i2p2www/pages/site/contact.html:33
+msgid "Mailing lists"
+msgstr "メーリングリスト"
+
+#: i2p2www/pages/site/contact.html:34
+msgid ""
+"I2P does have a mailing list, but it is rarely used as the current small "
+"team of developers prefer to communicate via IRC or the developer forum. "
+"This may change in future."
+msgstr ""
+"I2P にはメーリングリストがありますが、現在の小規模な開発チームは IRC "
+"や開発者フォーラムを通じたコミュニケーションを好むために、めったに使われません。これは将来変更される場合があります。"
+
+#: i2p2www/pages/site/contact.html:39
+msgid "Subscribing"
+msgstr "登録"
+
+#: i2p2www/pages/site/contact.html:40
+msgid ""
+"To subscribe to a mailing list, go to the list information page (linked "
+"below) and fill out the form. I2P-internal email addresses "
+"(foobar@mail.i2p) can be used."
+msgstr ""
+"メーリングリストに登録するには、リスト情報ページ(以下にリンク)を開き、フォームを埋めてください。 I2P 内のメールアドレス "
+"(hogehoge@mail.i2p) が使用できます。"
+
+#: i2p2www/pages/site/contact.html:44
+msgid "Unsubscribing"
+msgstr "登録解除"
+
+#: i2p2www/pages/site/contact.html:45
+msgid ""
+"To unsubscribe from a mailing list or edit your subscription options, go "
+"to the list information page (linked below) and enter your subscription "
+"email address."
+msgstr "メーリングリストから登録解除まてゃ登録オプションを編集するには、リスト情報ページ(以下にリンク)を開、登録メールアドレスを入力してください。"
+
+#: i2p2www/pages/site/contact.html:49
+msgid "Lists"
+msgstr "リスト"
+
+#: i2p2www/pages/site/contact.html:52
+msgid "Archive"
+msgstr "アーカイブ"
+
+#: i2p2www/pages/site/contact.html:53
+msgid ""
+"General I2P discussion - anything that doesn't fit in a different list "
+"goes here."
+msgstr "全般的な I2P の議論―別のリストにそぐわないものはすべてここに。"
+
+#: i2p2www/pages/site/contact.html:59
+msgid ""
+"You don't like mailing lists? Then this is for you. All mailing lists are"
+" available via NNTP as well."
+msgstr "メーリングリストは好みませんか？それならこれはいかがでしょう。メーリングリストはすべてNTTP経由でも利用できます。"
+
+#: i2p2www/pages/site/contact.html:64
+msgid "Group-List-mapping:"
+msgstr "グループリストマッピング:"
+
+#: i2p2www/pages/site/contact.html:68
+msgid "Servers:"
+msgstr "サーバー:"
+
+#: i2p2www/pages/site/faq.html:2
+msgid "Frequently Asked Questions"
+msgstr "よくある質問 (FAQ)"
+
+#: i2p2www/pages/site/faq.html:4
+msgid "Index"
+msgstr "目次"
+
+#: i2p2www/pages/site/faq.html:7
+msgid "General"
+msgstr "全般"
+
+#: i2p2www/pages/site/faq.html:9 i2p2www/pages/site/faq.html:51
+msgid "What systems will I2P run on?"
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:10
+msgid "Whats an \"eepsite\" and how do I configure my browser so I can use them?"
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:11 i2p2www/pages/site/faq.html:264
+msgid "My router has very few active peers, is this OK?"
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:12 i2p2www/pages/site/faq.html:499
+msgid "What do the Active x/y numbers mean in the router console?"
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:13 i2p2www/pages/site/faq.html:226
+msgid ""
+"My active peers / known peers / participating tunnels / connections / "
+"bandwidth vary dramatically over time! Is anything wrong?"
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:14 i2p2www/pages/site/faq.html:349
+msgid "Is using an outproxy safe?"
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:15 i2p2www/pages/site/faq.html:375
+msgid "Most of the eepsites within I2P are down?"
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:16 i2p2www/pages/site/faq.html:528
+msgid "What ports does I2P use?"
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:17
+msgid "Why is I2P listening for connections on port 32000?"
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:18 i2p2www/pages/site/faq.html:62
+msgid "I think I found a bug, where can I report it?"
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:19 i2p2www/pages/site/faq.html:108
+msgid "What happened to *.i2p.net? What happened to jrandom? Is I2P dead?"
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:20 i2p2www/pages/site/faq.html:846
+msgid "I have a question!"
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:22
+msgid "Setup"
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:24 i2p2www/pages/site/faq.html:233
+msgid ""
+"My router has been up for several minutes and has zero or very few "
+"connections"
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:25 i2p2www/pages/site/faq.html:391
+msgid "Why is I2P so slow?"
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:26 i2p2www/pages/site/faq.html:79
+msgid ""
+"I'm missing lots of hosts in my addressbook. What are some good "
+"subscription links?"
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:27 i2p2www/pages/site/faq.html:384
+msgid "How do I set up my own eepsite?"
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:28 i2p2www/pages/site/faq.html:417
+msgid "Bittorrent / I2PSnark / Azureus I2P Plugin Questions?"
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:29 i2p2www/pages/site/faq.html:424
+msgid "How do I connect to IRC within I2P?"
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:30 i2p2www/pages/site/faq.html:282
+msgid "I can't access regular Internet sites through I2P."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:31 i2p2www/pages/site/faq.html:297
+msgid "I can't access https:// or ftp:// sites through I2P."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:32 i2p2www/pages/site/faq.html:507
+msgid "Is it possible to use I2P as a SOCKS proxy?"
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:33 i2p2www/pages/site/faq.html:490
+msgid "How do I configure my browser?"
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:34 i2p2www/pages/site/faq.html:435
+msgid ""
+"How can I access the web console from my other machines or password "
+"protect it?"
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:35 i2p2www/pages/site/faq.html:475
+msgid "How can I use applications from my other machines?"
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:36 i2p2www/pages/site/faq.html:749
+msgid "How do I reseed manually?"
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:37 i2p2www/pages/site/faq.html:125
+msgid "My router is using too much CPU?!?"
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:39
+msgid "Misconception"
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:41 i2p2www/pages/site/faq.html:367
+msgid ""
+"How do I access IRC, BitTorrent, or other services on the regular "
+"Internet?"
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:42
+msgid ""
+"Is my router an \"exit node\"(outproxy) to the regular Internet? I don't "
+"want it to be."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:43 i2p2www/pages/site/faq.html:189
+msgid ""
+"I am opposed to certain types of content. How do I keep from "
+"distributing, storing, or accessing them?"
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:45
+msgid "Errors and Their Solutions"
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:47 i2p2www/pages/site/faq.html:785
+msgid ""
+"I'm using FreeBSD and when I start I2P I receive an error about "
+"libm.so.4!"
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:48
+msgid ""
+"In wrapper.log I see an error stating Protocol family "
+"unavailable when I2P is loading"
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:52 i2p2www/pages/site/faq.html:63
+#: i2p2www/pages/site/faq.html:80 i2p2www/pages/site/faq.html:109
+#: i2p2www/pages/site/faq.html:126 i2p2www/pages/site/faq.html:190
+#: i2p2www/pages/site/faq.html:227 i2p2www/pages/site/faq.html:234
+#: i2p2www/pages/site/faq.html:265 i2p2www/pages/site/faq.html:274
+#: i2p2www/pages/site/faq.html:283 i2p2www/pages/site/faq.html:298
+#: i2p2www/pages/site/faq.html:350 i2p2www/pages/site/faq.html:368
+#: i2p2www/pages/site/faq.html:376 i2p2www/pages/site/faq.html:385
+#: i2p2www/pages/site/faq.html:392 i2p2www/pages/site/faq.html:418
+#: i2p2www/pages/site/faq.html:425 i2p2www/pages/site/faq.html:436
+#: i2p2www/pages/site/faq.html:476 i2p2www/pages/site/faq.html:483
+#: i2p2www/pages/site/faq.html:491 i2p2www/pages/site/faq.html:500
+#: i2p2www/pages/site/faq.html:508 i2p2www/pages/site/faq.html:529
+#: i2p2www/pages/site/faq.html:737 i2p2www/pages/site/faq.html:750
+#: i2p2www/pages/site/faq.html:786 i2p2www/pages/site/faq.html:818
+#: i2p2www/pages/site/faq.html:847
+msgid "link"
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:53
+#, python-format
+msgid ""
+"While I2P has been reported to run PCs as meagre as a low-end Pentium II "
+"with 64 MB of RAM, you'll have a much better experience on a Pentium III "
+"(or better) with 128MB of RAM (or more). A chart "
+"comparing the performance of the various JREs can be found at %(chart)s, but in short: it's at all possible, use"
+" Sun/Oracle Java or OpenJDK."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:57
+msgid ""
+"I2P has been tested on Windows, Linux, FreeBSD (see the note below), OSX, and OpenSolaris. There is work "
+"underway to bring I2P to the Android platform."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:65
+msgid "Here are some places, pick one or more."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:71
+msgid "Discuss with the developers on IRC in #i2p-dev"
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:75
+msgid "Please include relevant information from the router logs and wrapper logs."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:81
+msgid ""
+"The default subscription is to http://www.i2p2.i2p/hosts.txt which is "
+"updated rarely.\n"
+"If you don't have another subscription, you may often have to use "
+"\"jump\" links which\n"
+"is annoying."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:87
+msgid ""
+"Here are some other public addressbook subscription links. You may wish "
+"to add one or two\n"
+"to your susidns "
+"subscription list.\n"
+"You don't need to add all of them, as they sync with each other "
+"periodically.\n"
+"The links using a cgi-bin application employ various strategies to "
+"minimize\n"
+"the number of duplicate addresses delivered, so they should be more "
+"efficient.\n"
+"Note that subscribing to a hosts.txt service is an act of \"trust\", as a"
+" malicious\n"
+"subscription could give you incorrect addresses. So think about whether "
+"you\n"
+"want to trust any of these.\n"
+"The operators of these services may have various policies for listing "
+"hosts.\n"
+"Presence on this list does not imply endorsement."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:110
+msgid ""
+"Jrandom was the lead developer of I2P and\n"
+"Syndie for several years.\n"
+"We do not know if or when jrandom will return.\n"
+"The *.i2p.net domains were left in a non-functioning state after a power\n"
+"outage at the hosting company."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:118
+#, python-format
+msgid ""
+"See this page for jrandom's parting message "
+"and additional information\n"
+"on the migration of *.i2p.net to this website."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:123
+msgid "I2P remains in active development."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:127
+msgid "There are many possible causes of high CPU usage. Here is a checklist:"
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:132
+msgid ""
+"Try to use either OpenJDK or Sun/Oracle Java if it's available for your "
+"system. You can check \n"
+"which version of java you have installed by typing java "
+"-version at a \n"
+"command/shell prompt. Performance tends to suffer with other "
+"implementations of java."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:139
+msgid ""
+"Are you running a BitTorrent client over I2P? Try reducing the number of "
+"torrents, the bandwidth limits,\n"
+"or try turning it off completely to see if that helps."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:145
+msgid ""
+"Are your bandwidth limits set too high? It is possible that too much "
+"traffic is going through your\n"
+"I2P router and it is overloaded. Try reducing the setting for share "
+"bandwidth percentage on the configuration page."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:150
+msgid ""
+"Make sure that you're running the latest version of I2P to get the "
+"benefits of increased performance and bug fixes."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:155
+msgid ""
+"Has enough memory been set aside for use by I2P? Look at the memory graph"
+" on the graphs page to see\n"
+"if the memory usage is \"pegged\"—the JVM is spending most of its "
+"time in\n"
+"garbage collection. Increase the setting "
+"wrapper.java.maxmemory in wrapper.config."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:162
+msgid ""
+"Is the CPU usage simply higher than you would like, or is it pegged at "
+"100% for a long time?\n"
+"If it's pegged, this could be a bug. Look in the logs for clues."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:168
+#, python-format
+msgid ""
+"You may be using the Java-based BigInteger library instead of the native "
+"version,\n"
+"especially if you are running on a new or unusual OS or hardware "
+"(OpenSolaris, mipsel, etc.).\n"
+"See the jbigi page for instructions on\n"
+"diagnosing, building, and testing methods."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:176
+msgid ""
+"If your native jbigi library is working fine, the biggest user of\n"
+"CPU may be routing traffic for participating tunnels. This uses CPU\n"
+"because at each hop a layer of encryption must be decoded.\n"
+"You can limit participating traffic in two ways - by reducing the\n"
+"share bandwidth on\n"
+"confignet.jsp,\n"
+"or by setting router.maxParticipatingTunnels=nnn on\n"
+"configadvanced.jsp."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:191
+msgid ""
+"Hmm. I2P is an anonymous network, so that's a tricky one.\n"
+"I2P is designed to withstand censorship, providing a means for everyone "
+"to communicate freely. \n"
+"The best way to keep your PC free of (encrypted) traffic that you dislike"
+" is to not use I2P.\n"
+"Freedom of speech has some costs.\n"
+"But let's address your question in three parts:"
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:200
+msgid ""
+"Distribution - All traffic on I2P is encrypted in multiple layers."
+" You don't know\n"
+"a message's contents, source, or destination.\n"
+"All traffic you route is internal to the I2P network, you are not an exit node (outproxy).\n"
+"Your only alternative is to refuse to route\n"
+"any traffic, by setting your share bandwidth or maximum "
+"participating tunnels to 0 (see above).\n"
+"It would be nice if you didn't do this, you should help the network by "
+"routing traffic for others.\n"
+"Over 95% of users route traffic for others."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:211
+msgid ""
+"Storage - I2P does not do distributed storage of content. You must"
+" be thinking of\n"
+"Freenet.\n"
+"Nobody's content is being stored on your computer by running I2P."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:218
+msgid ""
+"Access - If there are some eepsites you don't like, don't go "
+"there.\n"
+"Or, use a blocking proxy like Privoxy or some type of \"net nanny\"."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:228
+msgid ""
+"No. This is normal.\n"
+"All routers adjust dynamically to changing network conditions and demands."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:235
+msgid ""
+"You may need to reseed your I2P router. With recent versions of I2P you "
+"can go to http://localhost:7657/configreseed"
+" and click the Save Changes and Reseed Now button. If this "
+"method doesn't work—or you're using a very old version—you "
+"may need to reseed manually."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:238
+msgid ""
+"The reseed URL changed a few years ago. If this is your first install and"
+" you have installed\n"
+"an old (0.6.1.30 or earlier) release, or\n"
+"you have not run I2P in a long time, you must change the URL and then\n"
+"click \"Reseed\" on the console to find other routers.\n"
+"After your router is running,\n"
+"on configadvanced.jsp,"
+"\n"
+"add the line i2p.reseedURL=http://netdb.i2p2.de/\n"
+"OR i2p.reseedURL=http://i2pdb.tin0.de/netDb/ (either should "
+"work),\n"
+"then click \"Apply\", then click the \"reseed\" link on the left."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:249
+#, python-format
+msgid ""
+"This works if you are running 0.6.1.27 or later.\n"
+"If you are running release 0.6.1.31 or later, you probably don't need to "
+"do this.\n"
+"If you are running release 0.6.1.26 or earlier, either follow the\n"
+"manual reseed instructions below\n"
+"or install the latest release.\n"
+"Possible alternate method - add\n"
+"wrapper.java.additional.5=-Di2p.reseedURL=http://netdb.i2p2.de/\n"
+"to wrapper.config, shutdown the router completely, then start again, then"
+" click \"reseed\".\n"
+"Let us know if this works."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:260
+#, python-format
+msgid ""
+"...but you *really* should upgrade to "
+"the latest version."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:266
+msgid ""
+"If your router has 10 or more active peers, everything is fine. Changes "
+"in releases 0.6.1.31 and 0.6.1.32 improved the\n"
+"efficiency of the router and effectively reduced the number of active "
+"peers.\n"
+"The router should maintain connections to a few peers at all "
+"times.\n"
+"The best way to stay \"better-connected\" to the network is to share more bandwidth."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:273
+msgid ""
+"Is my router an \"exit node\" to the regular Internet? I don't want it to"
+" be."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:275
+msgid ""
+"No. Unlike Tor,\n"
+"\"exit nodes\" or \"outproxies\" are not an inherent part of the network."
+"\n"
+"Only volunteers who set up and run separate applications will relay "
+"traffic to the regular Internet.\n"
+"There are very, very few of these."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:284
+msgid ""
+"See above. There are very few HTTP \"outproxies\", they are not an "
+"inherent part of the network,\n"
+"and they may not be up.\n"
+"In addition, the old outproxies squid.i2p, true.i2p, and krabs.i2p have "
+"vanished.\n"
+"The only outproxy at the moment is false.i2p.\n"
+"To use it, edit your i2ptunnel "
+"settings for eepProxy\n"
+"and set your outproxy list to 'false.i2p' (only).\n"
+"Then stop and restart the eepProxy.\n"
+"If it doesn't work, the outproxy is not up. It is not I2P's fault.\n"
+"If your primary reason to use an anonymous network is to anonymously "
+"access sites\n"
+"on the regular Internet, you should probably try Tor."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:299
+msgid ""
+"Within I2P, there is no need for HTTPS, as all traffic is encrypted end-"
+"to-end.\n"
+"FTP is not supported for technical reasons."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:303
+msgid ""
+"There are no FTP \"outproxies\" to the Internet—it may not even be "
+"possible to set up one.\n"
+"Any other kind of outproxy may work if it's set up with a standard "
+"tunnel. \n"
+"If you would like to set up some type of outproxy, carefully research the"
+" potential risks.\n"
+"The I2P community may or may not be able to help with the technical "
+"aspects, feel free to ask."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:309
+msgid ""
+"As explained several times above, any existing outproxy isn't a core part"
+" of the network.\n"
+"They are services run by individuals and they may or may not\n"
+"be operational at any given time."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:314
+msgid ""
+"Update: Thanks to the work of h2ik, there is an https outproxy "
+"available for use via I2P. Starting with I2P 0.8.4 the tunnel is "
+"configured out of the box.
\n"
+"In case the https outproxy is not available in your version of I2P, you "
+"can add it easily by doing the following:"
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:320
+msgid ""
+"Open i2p tunnel "
+"manager. Scroll down to the bottom."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:325
+msgid ""
+"Choose CONNECT from New Client Tunnel dropdown list, click "
+"Create"
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:330
+#, python-format
+msgid ""
+"In the new page, name and describe your new https tunnel as"
+" you like.\n"
+"The Access Point is your local port for the new https proxy "
+"recommended port's 4445.\n"
+"Outproxy should be the outproxy's .i2p address which supports "
+"https. \n"
+"See this forum post of h2ik's for the "
+"address. \n"
+"Make sure Shared Client, Delay Connect, AutoStart "
+"are checked.\n"
+"Other options should be left at the defaults. Click Save. In tunnel "
+"manger, click the Start button next to your new tunnel."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:340
+msgid ""
+"In firefox, click through "
+"Tools>Options>Advanced>Network>Setting."
+"\n"
+"Untick Use this proxy for all protocol, set SSL proxy: to "
+"localhost:4445."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:345
+msgid "Done."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:351
+#, python-format
+msgid ""
+"\n"
+"This is a question that only you can answer because the correct answer "
+"depends on your behaviours, your\n"
+"threat model, and how much you trust the "
+"outproxy operator."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:355
+msgid ""
+"Like Tor, I2P does not magically encrypt the Internet.\n"
+"You are vulnerable to snooping by the outproxy operators.\n"
+"The Tor"
+" FAQ\n"
+"does a good job of explaining this."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:361
+#, python-format
+msgid ""
+"In addition, you may be vulnerable to collusion between the outproxy "
+"operator\n"
+"and operators of other I2P services, if you use the same tunnels "
+"(\"shared clients\").\n"
+"There is additional discussion about this on %(zzz)s."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:369
+msgid ""
+"Unless an outproxy has been set up for the service you want to connect "
+"to, this cannot be done.\n"
+"There are only three types of outproxies running right now: HTTP, HTTPS, "
+"and email. Note that there is not a SOCKS outproxy.\n"
+"If this type of service is required, try Tor."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:377
+#, python-format
+msgid ""
+"If you consider every eepsite that has ever been created, yes, most of "
+"them are down.\n"
+"People and eepsites come and go.\n"
+"A good way to get started in I2P is check out a list of eepsites that are"
+" currently up.\n"
+"%(eepstatus)s tracks active eepsites."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:386
+msgid ""
+"Click on the Website link\n"
+"at the top of your router console for instructions."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:393
+msgid ""
+"Why are downloads, torrents, web browsing, and everything else so slow on"
+" I2P?\n"
+"The encryption and routing within the I2P network adds a substantial "
+"amount of overhead and limits bandwidth.\n"
+"Anonymity isn't free."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:398
+msgid ""
+"In addition, you and everybody else probably need to increase your "
+"bandwidth limits.\n"
+"Two key settings are the inbound and outbound bandwidth limiters on\n"
+"the configuration page.\n"
+"With the default settings of 32KBps you will generally get no better than"
+" 15KBps data transfer in I2PSnark.\n"
+"Increasing the settings (but keeping within your actual connection "
+"limitations)\n"
+"will increase the potential transfer rate for I2PSnark and all other "
+"applications."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:406
+msgid ""
+"Also, do you have sufficient share bandwidth configured to allow "
+"participating tunnels\n"
+"to route through your router? Believe it or not, allowing participating "
+"traffic\n"
+"keeps you well-integrated in the network and helps your own transfer "
+"speeds."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:411
+#, python-format
+msgid ""
+"I2P is a work in progress. Lots of improvements and fixes are being "
+"implemented, and\n"
+"generally speaking, running the latest release will help your "
+"performance.\n"
+"If you haven't, install the latest "
+"release."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:419
+#, python-format
+msgid ""
+"See the\n"
+"I2P Bittorrent FAQ"
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:426
+msgid ""
+"\n"
+"A tunnel to the main IRC server within I2P, Irc2P, is created when I2P is"
+" installed (see\n"
+"the I2PTunnel "
+"configuration page),\n"
+"and is automatically started when the I2P router starts. To connect to "
+"it, tell your IRC\n"
+"client to connect to localhost 6668. XChat-like client users"
+" can create a\n"
+"new network with the server localhost/6668 (remember to tick"
+" "Bypass\n"
+"proxy server" if you have a proxy server configured)."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:437
+msgid ""
+"For security purposes, the router's admin console by default only listens"
+"\n"
+"for connections on the local interface. However, with a little hacking,\n"
+"you can make it reachable remotely:"
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:445
+msgid ""
+"Open ~/.i2p/clients.config and replace
\n"
+"clientApp.0.args=7657 ::1,127.0.0.1 ./webapps/
\n"
+"with
\n"
+"clientApp.0.args=7657 0.0.0.0 ./webapps/"
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:453
+msgid ""
+"Go to http://localhost:7657/configui"
+"\n"
+"and add a console username and password if desired."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:459
+msgid ""
+"Go to http://localhost:7657/index.jsp"
+"\n"
+"and hit \"Graceful restart\", which restarts the JVM and reloads the "
+"client applications"
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:466
+msgid ""
+"After that fires up, you should now be able to reach your console "
+"remotely. Reload the router at\n"
+"http://127.0.0.1:7657 and you will be prompted for the username and "
+"password you specified in step 2\n"
+"above if your browser supports the authentication popup. Note: the\n"
+"0.0.0.0 above specifies an interface, not a network "
+"or netmask. 0.0.0.0\n"
+"means \"bind to all interfaces\", so it can be reachable on "
+"127.0.0.1:7657 as well as\n"
+"any LAN/WAN IP."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:477
+msgid ""
+"By default, the router I2CP interface (port 7654) binds to address "
+"127.0.0.1. To bind to 0.0.0.0, set the\n"
+"router advanced configuration option "
+"i2cp.tcp.bindAllInterfaces=true and restart."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:482
+msgid "Whats an \"eepsite\"?"
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:484
+msgid ""
+"An eepsite is a website that is hosted anonymously - you can access it by"
+"\n"
+"setting your web browser's HTTP proxy to use the web proxy (typically it\n"
+"listens on localhost port 4444), and browsing to the site."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:492
+#, python-format
+msgid ""
+"The proxy config for different browsers is on a \n"
+"separate page with screenshots. More advanced configs with external "
+"tools\n"
+"are possible but could introduce leaks in your setup."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:501
+msgid ""
+"x is the number of peers you've sent or received a message from\n"
+"successfully in the last minute, y is the number of peers seen in the "
+"last\n"
+"hour or so."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:509
+msgid ""
+"The SOCKS proxy is working as of release 0.7.1. SOCKS 4/4a/5 are "
+"supported.\n"
+"There is no SOCKS outproxy so it is of limited use."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:513
+msgid ""
+"In addition, many applications leak sensitive\n"
+"information that could identify you on the Internet. I2P only filters\n"
+"connection data, but if the program you intend to run sends this\n"
+"information as content, I2P has no way to protect your anonymity. For\n"
+"example, some mail applications will send the IP address of the machine\n"
+"they are running on to a mail server. There is no way for I2P to filter\n"
+"this, thus using I2P to 'socksify' existing applications is possible, but"
+"\n"
+"extremely dangerous."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:523
+#, python-format
+msgid ""
+"If you would like more information on the socks proxy application anyway,"
+"\n"
+"there are some helpful hints on the socks page."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:530
+msgid ""
+"Okay, here's a rundown of the default ports (everything is configurable\n"
+"through various settings, of course):"
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:539
+msgid ""
+"Internet-facing ports\n"
+"Note: New installs as of release 0.7.8 do not use port 8887; they select "
+"a random port\n"
+"between 9000 and 31000 when the program is run for the first time.\n"
+"The selected port is shown on the router configuration page."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:547
+msgid ""
+"Outbound UDP from the random port noted on the configuration page to "
+"arbitrary remote UDP ports, allowing replies\n"
+" "
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:552
+msgid ""
+"Outbound TCP from random high ports to arbitrary remote TCP ports\n"
+" "
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:557
+msgid ""
+"(optional, but recommended) Inbound UDP to the port noted on configuration page from "
+"arbitrary locations\n"
+" "
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:562
+msgid ""
+"(optional, but recommended) Inbound TCP to the port noted on configuration page from "
+"arbitrary locations
\n"
+"Inbound TCP may be disabled on the configuration page."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:568
+msgid ""
+"Outbound UDP on port 123, allowing replies
\n"
+"This is necessary for I2P's internal time sync (via SNTP - \n"
+"querying a random SNTP host in pool.ntp.org or another\n"
+"server you specify)"
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:579
+msgid ""
+"Local I2P ports, listening only to local connections by default,\n"
+"except where noted:"
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:585
+msgid ""
+"1900: UPnP SSDP UDP multicast listener.\n"
+"Cannot be changed. Binds to all interfaces.\n"
+"May be disabled on confignet.jsp."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:592
+msgid ""
+"2827: BOB bridge, a higher level socket API for clients\n"
+"Disabled by default.\n"
+"May be enabled/disabled on configclients.jsp.\n"
+"May be changed in the bob.config file."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:600
+msgid ""
+"4444: HTTP proxy\n"
+"May be disabled or changed on the i2ptunnel page in the router "
+"console.\n"
+"May also be configured to be bound to a specific interface or all "
+"interfaces."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:607
+msgid ""
+"4445: HTTPS proxy\n"
+"May be disabled or changed on the i2ptunnel page in the router "
+"console.\n"
+"May also be configured to be bound to a specific interface or all "
+"interfaces."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:614
+msgid ""
+"6668: IRC proxy\n"
+"May be disabled or changed on the i2ptunnel page in the router "
+"console.\n"
+"May also be configured to be bound to a specific interface or all "
+"interfaces."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:621
+msgid ""
+"7652: UPnP HTTP TCP event listener.\n"
+"Binds to the LAN address.\n"
+"May be changed with advanced config i2np.upnp.HTTPPort=nnnn.\n"
+"May be disabled on confignet.jsp."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:629
+msgid ""
+"7653: UPnP SSDP UDP search response listener.\n"
+"Binds to all interfaces.\n"
+"May be changed with advanced config i2np.upnp.SSDPPort=nnnn.\n"
+"May be disabled on confignet.jsp."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:637
+msgid ""
+"7654: I2P Client Protocol port, used by client apps.\n"
+"May be changed to a different port on\n"
+"configclients.jsp"
+"\n"
+"but this is not recommended.\n"
+"May be to bind to a different interface or all interfaces, or disabled, "
+"on\n"
+"configclients.jsp."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:647
+msgid ""
+"7655: UDP for SAM bridge, a higher level socket API for clients\n"
+"Only opened when a SAM V3 client requests a UDP session.\n"
+"May be enabled/disabled on configclients.jsp.\n"
+"May be changed in the clients.config file with the SAM command line "
+"option sam.udp.port=nnnn."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:655
+msgid ""
+"7656: SAM bridge, a higher level socket API for clients\n"
+"Disabled by default for new installs as of release 0.6.5.\n"
+"May be enabled/disabled on configclients.jsp.\n"
+"May be changed in the clients.config file."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:663
+msgid ""
+"7657: Your router console\n"
+"May be disabled in the clients.config file.\n"
+"May also be configured to be bound to a specific interface or all "
+"interfaces in that file."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:670
+msgid ""
+"7658: Your eepsite\n"
+"May be disabled in the clients.config file.\n"
+"May also be configured to be bound to a specific interface or all "
+"interfaces in the jetty.xml file."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:677
+msgid ""
+"7659: Outgoing mail to smtp.postman.i2p\n"
+"May be disabled or changed on the i2ptunnel page in the router "
+"console.\n"
+"May also be configured to be bound to a specific interface or all "
+"interfaces."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:684
+msgid ""
+"7660: Incoming mail from pop.postman.i2p\n"
+"May be disabled or changed on the i2ptunnel page in the router "
+"console.\n"
+"May also be configured to be bound to a specific interface or all "
+"interfaces."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:691
+msgid ""
+"8998: mtn.i2p2.i2p (Monotone - disabled by default)\n"
+"May be disabled or changed on the i2ptunnel page in the router "
+"console.\n"
+"May also be configured to be bound to a specific interface or all "
+"interfaces."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:698
+msgid ""
+"31000: Local connection to the wrapper control channel port.\n"
+"Outbound to 32000 only, does not listen on this port.\n"
+"Starts at 31000 and will increment until 31999 looking for a free port.\n"
+"To change, see the\n"
+"wrapper documentation.\n"
+"For more information see below."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:708
+msgid ""
+"32000: Local control channel for the service wrapper.\n"
+"To change, see the\n"
+"wrapper documentation.\n"
+"For more information see below."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:720
+msgid ""
+"The local I2P ports and the I2PTunnel ports do not need to be reachable "
+"from \n"
+"remote machines, but *should* be reachable locally. You can also create"
+" \n"
+"additional ports for I2PTunnel instances via "
+"http://localhost:7657/i2ptunnel/ \n"
+"(and in turn, would need to get your firewall to allow you local access, "
+"but \n"
+"not remote access, unless desired)."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:728
+msgid ""
+"So, to summarize, nothing needs to be reachable by unsolicited remote "
+"peers, but\n"
+"if you can configure your NAT/firewall to allow inbound UDP and TCP the "
+"outbound facing port, you'll"
+"\n"
+"get better performance. You will also need to be able to send outbound "
+"UDP packets\n"
+"to arbitrary remote peers (blocking IPs randomly with something like "
+"PeerGuardian\n"
+"only hurts you - don't do it)."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:736
+msgid "Why is I2P listening on port 32000?"
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:738
+msgid ""
+"The Tanuki java service wrapper that we use opens this port—bound "
+"to localhost—in order \n"
+"to communicate with software running inside the JVM. When the JVM is "
+"launched it is given a key \n"
+"so it can connect to the wrapper. After the JVM establishes its "
+"connection \n"
+"to the wrapper, the wrapper refuses any additional connections."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:744
+msgid ""
+"More information can be found in the \n"
+"wrapper documentation."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:751
+msgid ""
+"An I2P router only needs to be seeded once, to join the network for the "
+"first time.\n"
+"Reseeding is nothing more than sending plain HTTP GET requests\n"
+"to fetch a directory listing and download multiple \"routerInfo\" files\n"
+"from a predefined reseed URL."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:758
+msgid ""
+"A typical symptom of a failed reseed is the \"Known\" indicator\n"
+"(on the left sidebar of the router console) displaying a very small value"
+"\n"
+"(often less than 5) which does not increase. This can occur, among other "
+"things,\n"
+"if your firewall limits outbound traffic, and blocked the reseed request."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:765
+msgid "To reseed an I2P router manually, do the following:"
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:768
+msgid "Stop your I2P router"
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:771
+msgid ""
+"Open http://netdb.i2p2.de/ using a "
+"web browser"
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:774
+msgid "Save a dozen \"routerInfo\" files to your I2P \"netDb\" directory"
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:781
+msgid "Start your I2P router"
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:788
+msgid ""
+"When trying to start the router using \"i2prouter start\", you may see "
+"output like the following:"
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:793
+msgid ""
+"\n"
+"In order to be inclusive and try to ensure that I2P will run on as many "
+"systems \n"
+"as possible, up until I2P 0.8.9 we used a java wrapper \n"
+"compiled for FreeBSD 6.x. If you're receiving this error you most likely "
+"are missing the necessary compatibility libraries.\n"
+"These libraries may be installed by performing the following steps:"
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:801
+msgid ""
+"Switch to the root user with su or log in as "
+"root."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:807
+#, python-format
+msgid ""
+"If you cannot install these compatibility libraries (or do not want to), "
+"other\n"
+"possibilities would be to compile the wrapper for your\n"
+"system, starting I2P with the runplain.sh script, or you"
+" can\n"
+"replace the wrapper with one from the source tarball."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:813
+msgid ""
+"For the 0.8.9 release of I2P, the wrapper was upgraded to v3.5.12 and "
+"compiled on systems running FreeBSD 7.2."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:817
+msgid ""
+"In wrapper.log I see an error that states \"Protocol "
+"family unavailable\" when loading the Router Console"
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:819
+msgid ""
+"Often this error will occur with any network enabled java software on "
+"some systems that are configured to use IPv6 by default. There are a few "
+"ways to solve this:"
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:824
+msgid ""
+"On Linux based systems, you can echo 0 > "
+"/proc/sys/net/ipv6/bindv6only"
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:826
+msgid "Look for the following lines in wrapper.config."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:830
+msgid ""
+"If the lines are there, uncomment them by removing the \"#\"s. If the "
+"lines are not there, add them without the \"#\"s."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:833
+msgid ""
+"Another option would be to remove the ::1 from "
+"~/.i2p/clients.config"
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:837
+msgid ""
+"WARNING: For any changes to wrapper.config "
+"to take effect, you must completely\n"
+"stop the router and the wrapper. Clicking Restart on your\n"
+"router console will NOT reread this file! You must\n"
+"click Shutdown, wait 11 minutes, then start I2P."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:848
+#, python-format
+msgid ""
+"Great! Find us on IRC irc.freenode.net #i2p or post to\n"
+"the forum and we'll post it here (with\n"
+"the answer, hopefully)."
+msgstr ""
+
+#: i2p2www/pages/site/impressum.html:4
+msgid "German laws"
+msgstr ""
+
+#: i2p2www/pages/site/index.html:2
+msgid "I2P Anonymous Network"
+msgstr ""
+
+#: i2p2www/pages/site/index.html:4
+msgid ""
+"Anonymous peer-to-peer distributed communication layer built with open "
+"source tools and designed to run any traditional Internet service such as"
+" email, IRC or web hosting."
+msgstr ""
+
+#: i2p2www/pages/site/index.html:7
+msgid "What does I2P do for you?"
+msgstr ""
+
+#: i2p2www/pages/site/index.html:8
+msgid ""
+"The I2P network provides strong privacy protections for communication "
+"over the Internet. Many activities that would risk your privacy on the "
+"public Internet can be conducted anonymously inside I2P."
+msgstr ""
+
+#: i2p2www/pages/site/index.html:9
+#, python-format
+msgid "Get I2P %(version)s"
+msgstr ""
+
+#: i2p2www/pages/site/index.html:13
+msgid "What is I2P?"
+msgstr ""
+
+#: i2p2www/pages/site/index.html:15
+msgid ""
+"I2P is an anonymous overlay network - a network within a network. It is "
+"intended to protect communication from dragnet surveillance and "
+"monitoring by third parties such as ISPs.\n"
+msgstr ""
+
+#: i2p2www/pages/site/index.html:18
+msgid ""
+"I2P is used by many people who care about their privacy: activists, "
+"oppressed people, journalists and whistleblowers, as well as the average "
+"person.\n"
+msgstr ""
+
+#: i2p2www/pages/site/index.html:21
+msgid ""
+"No network can be \"perfectly anonymous\". The continued goal of I2P is "
+"to make attacks more and more difficult to mount. Its anonymity will get "
+"stronger as the size of the network increases and with ongoing academic "
+"review.\n"
+msgstr ""
+
+#: i2p2www/pages/site/index.html:24
+msgid ""
+"I2P is available on desktops, embedded systems (like the Raspberry Pi) "
+"and Android phones. Help spread the word!\n"
+msgstr ""
+
+#: i2p2www/pages/site/index.html:28
+msgid "Read more…"
+msgstr ""
+
+#: i2p2www/pages/site/index.html:33
+msgid "What can you do with I2P?"
+msgstr ""
+
+#: i2p2www/pages/site/index.html:36
+#, python-format
+msgid ""
+"Email: Integrated web mail interface,"
+" plugin for serverless email."
+msgstr ""
+
+#: i2p2www/pages/site/index.html:41
+#, python-format
+msgid ""
+"Web browsing: Anonymous "
+"websites, gateways to and from the public Internet."
+msgstr ""
+
+#: i2p2www/pages/site/index.html:46
+#, python-format
+msgid ""
+"Blogging and forums: "
+"Blogging and Syndie plugins."
+msgstr ""
+
+#: i2p2www/pages/site/index.html:51
+#, python-format
+msgid ""
+"Website hosting: Integrated"
+" anonymous web server."
+msgstr ""
+
+#: i2p2www/pages/site/index.html:56
+#, python-format
+msgid ""
+"Real-time chat: Instant "
+"messaging and IRC clients."
+msgstr ""
+
+#: i2p2www/pages/site/index.html:61
+#, python-format
+msgid ""
+"File sharing: ED2K and "
+"Gnutella clients, integrated BitTorrent client."
+msgstr ""
+
+#: i2p2www/pages/site/index.html:66
+#, python-format
+msgid ""
+"Decentralized file "
+"storage: Tahoe-LAFS distributed filesystem plugin."
+msgstr ""
+
+#: i2p2www/pages/site/index.html:71
+#, python-format
+msgid "More supported applications…"
+msgstr ""
+
+#: i2p2www/pages/site/index.html:79
+msgid "News & Updates"
+msgstr ""
+
+#: i2p2www/pages/site/links.html:4
+msgid "Recommended Links & Resources"
+msgstr ""
+
+#: i2p2www/pages/site/links.html:5
+#, python-format
+msgid ""
+"See also the page with\n"
+"links to presentations, videos, and tutorials about"
+" I2P."
+msgstr ""
+
+#: i2p2www/pages/site/links.html:12
+msgid "I2P on the web"
+msgstr ""
+
+#: i2p2www/pages/site/links.html:20
+msgid "Friends of I2P"
+msgstr ""
+
+#: i2p2www/pages/site/links.html:32
+msgid "More Projects and Documentation"
+msgstr ""
+
+#: i2p2www/pages/site/links.html:42
+msgid "Press"
+msgstr ""
+
+#: i2p2www/pages/site/links.html:46
+msgid "Boards, newssite, others"
+msgstr ""
+
+#: i2p2www/pages/site/links.html:50
+msgid "Very Old Stuff"
+msgstr ""
+
diff --git a/i2p2www/translations/pl/LC_MESSAGES/priority.po b/i2p2www/translations/pl/LC_MESSAGES/priority.po
new file mode 100644
index 00000000..bad10f51
--- /dev/null
+++ b/i2p2www/translations/pl/LC_MESSAGES/priority.po
@@ -0,0 +1,2550 @@
+# Polish translations for I2P.
+# Copyright (C) 2013 ORGANIZATION
+# This file is distributed under the same license as the I2P project.
+#
+# Translators:
+# Tracerneo , 2013
+msgid ""
+msgstr ""
+"Project-Id-Version: I2P\n"
+"Report-Msgid-Bugs-To: http://trac.i2p2.de\n"
+"POT-Creation-Date: 2013-11-27 00:23+0000\n"
+"PO-Revision-Date: 2013-11-27 00:30+0000\n"
+"Last-Translator: str4d \n"
+"Language-Team: Polish "
+"(http://www.transifex.com/projects/p/I2P/language/pl/)\n"
+"Plural-Forms: nplurals=3; plural=(n==1 ? 0 : n%10>=2 && n%10<=4 && "
+"(n%100<10 || n%100>=20) ? 1 : 2)\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=utf-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"Generated-By: Babel 0.9.6\n"
+
+#: i2p2www/pages/blog/category.html:2
+msgid "Blog Category"
+msgstr ""
+
+#: i2p2www/pages/blog/category.html:4
+#, python-format
+msgid "I2P Blog ATOM Feed for Category: %(category)s"
+msgstr ""
+
+#: i2p2www/pages/blog/index.html:2 i2p2www/pages/blog/post.html:3
+#: i2p2www/pages/global/nav.html:95
+msgid "Blog"
+msgstr "Blog"
+
+#: i2p2www/pages/blog/index.html:4 i2p2www/pages/site/index.html:78
+msgid "I2P Blog ATOM Feed"
+msgstr "I2P Blog ATOM Feed"
+
+#: i2p2www/pages/blog/index.html:17
+#, python-format
+msgid "Posted %(date)s by %(author)s"
+msgstr ""
+
+#: i2p2www/pages/blog/latest.html:5
+msgid "More blog posts…"
+msgstr "Więcej postów…"
+
+#: i2p2www/pages/blog/post.html:6
+msgid "Posted:"
+msgstr ""
+
+#: i2p2www/pages/blog/post.html:7
+msgid "Author:"
+msgstr "Autor:"
+
+#: i2p2www/pages/downloads/debian.html:4
+msgid "Debian I2P Packages"
+msgstr "Paczki I2P Debiana"
+
+#: i2p2www/pages/downloads/debian.html:6
+msgid ""
+"The Debian packages\n"
+"have been tested and should work on x86/x86_64 platforms running:"
+msgstr ""
+
+#: i2p2www/pages/downloads/debian.html:11
+msgid "Ubuntu (Precise 12.04 and newer)"
+msgstr ""
+
+#: i2p2www/pages/downloads/debian.html:13
+msgid "Debian Linux (Squeeze and newer) & kFreeBSD"
+msgstr ""
+
+#: i2p2www/pages/downloads/debian.html:17
+#, python-format
+msgid ""
+"The I2P packages may work on systems not listed above. Please "
+"report any issues\n"
+"with these packages on Trac at\n"
+"https://trac.i2p2.de."
+msgstr ""
+
+#: i2p2www/pages/downloads/debian.html:23
+msgid ""
+"Option 1: Recent versions of Ubuntu and its "
+"derivatives (Try this if you're not using Debian)"
+msgstr ""
+"Opcja 1: Aktualne wersje Ubuntu i pochodne "
+"(Spróbuj tego jeśli nie używasz Debiana)"
+
+#: i2p2www/pages/downloads/debian.html:24
+msgid "Option 2: Debian (including Debian-derivatives)"
+msgstr ""
+
+#: i2p2www/pages/downloads/debian.html:27
+msgid ""
+"Instructions for Ubuntu Precise Pangolin (and newer) and derivatives like"
+" Linux Mint & Trisquel"
+msgstr ""
+
+#: i2p2www/pages/downloads/debian.html:28
+msgid "Adding the PPA via the command line and installing I2P"
+msgstr "Dodawanie PPA z linii komend i instalacja I2P"
+
+#: i2p2www/pages/downloads/debian.html:31
+msgid "Open a terminal and enter:"
+msgstr "Otwórz terminal i wpisz:"
+
+#: i2p2www/pages/downloads/debian.html:33
+msgid ""
+"This command will add the PPA to /etc/apt/sources.list.d and fetch the\n"
+"gpg key that the repository has been signed with. The GPG key ensures\n"
+"that the packages have not been tampered with since being built."
+msgstr ""
+
+#: i2p2www/pages/downloads/debian.html:40
+msgid "Notify your package manager of the new PPA by entering:"
+msgstr ""
+
+#: i2p2www/pages/downloads/debian.html:42
+msgid ""
+"This command will retrieve the latest list of software from each\n"
+"repository that is enabled on your system, including the I2P PPA that\n"
+"was added with the earlier command."
+msgstr ""
+
+#: i2p2www/pages/downloads/debian.html:48
+msgid "You are now ready to install I2P!"
+msgstr ""
+
+#: i2p2www/pages/downloads/debian.html:52
+msgid "Adding the PPA Using Synaptic"
+msgstr ""
+
+#: i2p2www/pages/downloads/debian.html:55
+msgid ""
+"Open Synaptic (System -> Administration -> Synaptic Package "
+"Manager)."
+msgstr ""
+
+#: i2p2www/pages/downloads/debian.html:60
+msgid ""
+"Once Synaptic opens, select Repositories from the "
+"Settings menu."
+msgstr ""
+
+#: i2p2www/pages/downloads/debian.html:65
+msgid ""
+"Click the Other Sources tab and click Add. Paste "
+"ppa:i2p-maintainers/i2p into the APT-line field and click "
+"Add Source. Click the Close button then "
+"Reload."
+msgstr ""
+
+#: i2p2www/pages/downloads/debian.html:70
+msgid ""
+"In the Quick Filter box, type in i2p and press enter. When "
+"i2p is returned in the results list, right click "
+"i2p and select Mark for Installation. After doing "
+"so you may see a Mark additional required changes? popup. If so,"
+" click Mark then Apply."
+msgstr ""
+
+#: i2p2www/pages/downloads/debian.html:76
+msgid ""
+"After the installation process completes you can move on to the next\n"
+"part of starting I2P and configuring "
+"it for your system."
+msgstr ""
+
+#: i2p2www/pages/downloads/debian.html:81
+msgid "Instructions for Debian"
+msgstr "Instrukcje dla Debiana"
+
+#: i2p2www/pages/downloads/debian.html:85
+msgid ""
+"Note: The steps below should be performed with root access (i.e., "
+"switching\n"
+"user to root with \"su\" or by prefixing each command with \"sudo\")."
+msgstr ""
+
+#: i2p2www/pages/downloads/debian.html:90
+#, python-format
+msgid "Add lines like the following to %(file)s."
+msgstr ""
+
+#: i2p2www/pages/downloads/debian.html:111
+#, python-format
+msgid ""
+"Download the key used to sign the repository"
+" and add it to apt:"
+msgstr ""
+
+#: i2p2www/pages/downloads/debian.html:118
+msgid "Notify your package manager of the new repository by entering"
+msgstr ""
+
+#: i2p2www/pages/downloads/debian.html:120
+msgid ""
+"This command will retrieve the latest list of software from every\n"
+"repository enabled on your system, including the I2P repository added in "
+"step\n"
+"1."
+msgstr ""
+
+#: i2p2www/pages/downloads/debian.html:126
+msgid ""
+"You are now ready to install I2P! Installing the i2p-keyring"
+"\n"
+"package will ensure that you receive updates to the repository's GPG key."
+msgstr ""
+
+#: i2p2www/pages/downloads/debian.html:133
+msgid ""
+"After the installation process completes you can move on to the next part"
+" of starting I2P and configuring it "
+"for your system."
+msgstr ""
+
+#: i2p2www/pages/downloads/debian.html:137
+#: i2p2www/pages/downloads/list.html:171
+msgid "Post-install work"
+msgstr ""
+
+#: i2p2www/pages/downloads/debian.html:139
+msgid ""
+"Using these I2P packages the I2P router can be started in the following\n"
+"three ways:"
+msgstr ""
+
+#: i2p2www/pages/downloads/debian.html:145
+msgid ""
+""on demand" using the i2prouter script. Simply run "
+""i2prouter\n"
+"start" from a command prompt. (Note: Do "
+"not use\n"
+"sudo or run it as root!)"
+msgstr ""
+
+#: i2p2www/pages/downloads/debian.html:152
+msgid ""
+""on demand" without the java service wrapper\n"
+"(needed on non-Linux/non-x86 systems) by running \"i2prouter-"
+"nowrapper\".\n"
+"(Note: Do not\n"
+"use sudo or run it as root!)"
+msgstr ""
+
+#: i2p2www/pages/downloads/debian.html:160
+msgid ""
+"as a service that automatically runs when your system boots, even\n"
+"before logging in. The service can be enabled with \"dpkg-"
+"reconfigure\n"
+"i2p\" as root or using sudo. This is the recommended means of "
+"operation."
+msgstr ""
+
+#: i2p2www/pages/downloads/debian.html:168
+msgid ""
+"When installing for the first time, please remember to adjust your "
+"NAT/firewall\n"
+"if you can. The ports to forward can be found on the \n"
+"network configuration page in the router console. If guidance with "
+"respect to forwarding ports is needed,\n"
+"you may find portforward.com to be"
+" helpful."
+msgstr ""
+
+#: i2p2www/pages/downloads/debian.html:175
+msgid ""
+"Please review and adjust the bandwidth settings on the\n"
+"configuration page,\n"
+"as the default settings of 96 KB/s down / 40 KB/s up are fairly "
+"conservative."
+msgstr ""
+
+#: i2p2www/pages/downloads/debian.html:181
+#: i2p2www/pages/downloads/list.html:204
+#, python-format
+msgid ""
+"If you want to reach eepsites via your browser, have a look on the browser proxy setup page for an easy "
+"howto."
+msgstr ""
+
+#: i2p2www/pages/downloads/list.html:2 i2p2www/pages/downloads/select.html:12
+#: i2p2www/pages/global/nav.html:3
+msgid "Download"
+msgstr ""
+
+#: i2p2www/pages/downloads/list.html:9
+msgid "Download I2P"
+msgstr "Pobierz I2P"
+
+#: i2p2www/pages/downloads/list.html:11
+msgid "Dependency"
+msgstr "Zależności"
+
+#: i2p2www/pages/downloads/list.html:12
+#, python-format
+msgid ""
+"\n"
+"Java Runtime 1.5 or higher.\n"
+"(Oracle Java Version 7,\n"
+"OpenJDK 7, or\n"
+"IcedTea7\n"
+" recommended,\n"
+"except Raspberry Pi: Oracle 8 Early Access,\n"
+"PowerPC: IBM SDK 7)\n"
+"
\n"
+"Determine your installed Java version here\n"
+"or type java -version at your command prompt.\n"
+msgstr ""
+
+#: i2p2www/pages/downloads/list.html:30
+msgid "Clean installs"
+msgstr "Czyste instalacje"
+
+#: i2p2www/pages/downloads/list.html:37 i2p2www/pages/downloads/list.html:54
+#: i2p2www/pages/downloads/list.html:81 i2p2www/pages/downloads/list.html:140
+#: i2p2www/pages/downloads/list.html:269
+msgid "select alternate link"
+msgstr ""
+
+#: i2p2www/pages/downloads/list.html:44
+msgid "Download that file and run it."
+msgstr "Pobierz ten plik i uruchom go."
+
+#: i2p2www/pages/downloads/list.html:61
+#, python-format
+msgid ""
+"Download that file and double-click it (if that works) or\n"
+" type java -jar i2pinstall_%(i2pversion)s.jar in a "
+"terminal to run the\n"
+" installer.\n"
+" You may be able to right-click and select\n"
+" "Open with Java"."
+msgstr ""
+
+#: i2p2www/pages/downloads/list.html:69 i2p2www/pages/downloads/list.html:96
+msgid "Command line (headless) install:"
+msgstr "Instalacja z linii komend:"
+
+#: i2p2www/pages/downloads/list.html:70
+#, python-format
+msgid ""
+"Download the %(i2pversion)s OSX graphical installer file above and\n"
+" run java -jar i2pinstall_%(i2pversion)s.jar -console "
+"from the command line."
+msgstr ""
+
+#: i2p2www/pages/downloads/list.html:88
+#, python-format
+msgid ""
+"Download that file and double-click it (if that works) or\n"
+" type java -jar i2pinstall_%(i2pversion)s.jar in a "
+"terminal to run the\n"
+" installer.\n"
+" On some platforms you may be able to right-click and select\n"
+" "Open with Java"."
+msgstr ""
+"Pobierz ten plik i kliknij dwukrotnie (jeśl działa) lub\n"
+" wpisz java -jar i2pinstall_%(i2pversion)s.jar w "
+"terminalu, by uruchomić\n"
+" instalator.\n"
+" Na niektórych platformach może być dostępna opcja "Open with "
+"Java"\n"
+" po kliknięciu prawym przyciskiem myszy."
+
+#: i2p2www/pages/downloads/list.html:97
+#, python-format
+msgid ""
+"Download the graphical installer file above and\n"
+" run java -jar i2pinstall_%(i2pversion)s.jar -console "
+"from the command line."
+msgstr ""
+"Pobierz powyższy plik instalatora graficznego i wykonaj\n"
+" java -jar i2pinstall_%(i2pversion)s.jar -console z linii"
+" komend."
+
+#: i2p2www/pages/downloads/list.html:107
+msgid "Packages for Debian & Ubuntu are available."
+msgstr ""
+
+#: i2p2www/pages/downloads/list.html:121
+#, python-format
+msgid ""
+"The above file is the current release build.\n"
+" The latest dev build is version %(devbuild)s, and is available from\n"
+" str4d's eepsite."
+msgstr ""
+
+#: i2p2www/pages/downloads/list.html:127
+msgid ""
+"The release and dev versions of the I2P APK are not compatible, as they\n"
+" are signed by zzz and str4d respectively. Uninstall one before "
+"installing\n"
+" the other."
+msgstr ""
+
+#: i2p2www/pages/downloads/list.html:137
+msgid "Source package"
+msgstr ""
+
+#: i2p2www/pages/downloads/list.html:147
+#, python-format
+msgid ""
+"Alternately, you can fetch the source from monotone\n"
+" or via Git from git.repo.i2p or Github.\n"
+"
\n"
+" Run (tar xjvf i2psource_%(i2pversion)s.tar.bz2 ; cd "
+"i2p-%(i2pversion)s ; ant pkg) then either\n"
+" run the GUI installer or headless install as above."
+msgstr ""
+
+#: i2p2www/pages/downloads/list.html:162
+#, python-format
+msgid ""
+"The files are signed by zzz,\n"
+"whose key is here."
+msgstr ""
+
+#: i2p2www/pages/downloads/list.html:167
+msgid ""
+"I2P can also be downloaded from our project pages on Launchpad and Google Code."
+msgstr ""
+
+#: i2p2www/pages/downloads/list.html:173
+msgid ""
+"After running the installer on windows, simply click on the \"Start I2P\""
+" button\n"
+"which will bring up the router console,\n"
+"which has further instructions."
+msgstr ""
+
+#: i2p2www/pages/downloads/list.html:179
+msgid ""
+"On Unix-like systems, I2P can be started as a service\n"
+"using the \"i2prouter\" script, located in the directory you selected for"
+" I2P.\n"
+"Changing to that directory in a console and issuing \"sh i2prouter "
+"status\"\n"
+"should tell you the router's status. The arguments \"start\", \"stop\" "
+"and \"restart\"\n"
+"control the service. The router console\n"
+"can be accessed at its usual location.\n"
+"For users on OpenSolaris and other systems for which the wrapper (i2psvc)"
+" is not supported,\n"
+"start the router with \"sh runplain.sh\" instead."
+msgstr ""
+
+#: i2p2www/pages/downloads/list.html:190
+#, python-format
+msgid ""
+"When installing for the first time, please remember to adjust your "
+"NAT/firewall\n"
+"if you can, bearing in mind the Internet-facing ports I2P uses,\n"
+"described here among other ports.\n"
+"If you have successfully opened your port to inbound TCP, also enable "
+"inbound TCP on the\n"
+"configuration page."
+msgstr ""
+
+#: i2p2www/pages/downloads/list.html:198
+msgid ""
+"Also, please review and adjust the bandwidth settings on the\n"
+"configuration page,\n"
+"as the default settings of 96 KBps down / 40 KBps up are fairly slow."
+msgstr ""
+
+#: i2p2www/pages/downloads/list.html:208
+msgid "Updates from earlier releases:"
+msgstr ""
+
+#: i2p2www/pages/downloads/list.html:210
+msgid "Both automatic and manual upgrades are available for the release."
+msgstr ""
+
+#: i2p2www/pages/downloads/list.html:215
+msgid "Automatic updates"
+msgstr ""
+
+#: i2p2www/pages/downloads/list.html:217
+msgid ""
+"If you are running 0.7.5 or later, your router should detect the\n"
+"new release. To upgrade simply click the 'Download Update' button on your"
+" router console\n"
+"when it appears."
+msgstr ""
+
+#: i2p2www/pages/downloads/list.html:223
+msgid ""
+"Due to a bug in release 0.7.6, those whose first I2P installation was "
+"that version\n"
+"and have not upgraded manually\n"
+"may get a \"downloaded version is not greater than current version\" "
+"error,\n"
+"and should use the manual update method below."
+msgstr ""
+
+#: i2p2www/pages/downloads/list.html:231
+#, python-format
+msgid ""
+"If you are running 0.7.4 or earlier, please see\n"
+"the 0.7.5 release notes\n"
+"for important information about how to configure your router to "
+"automatically\n"
+"receive the release."
+msgstr ""
+
+#: i2p2www/pages/downloads/list.html:239
+#, python-format
+msgid ""
+"If you are running 0.6.1.30 or earlier, please see\n"
+"instructions\n"
+"for important information about how to configure your router to "
+"automatically\n"
+"receive the release."
+msgstr ""
+
+#: i2p2www/pages/downloads/list.html:248
+#, python-format
+msgid ""
+"If you have reconfigured your router following the instructions, you should see a link on your"
+" \n"
+" router console "
+"allowing\n"
+" you to download and install the new release by just clicking on that\n"
+" link."
+msgstr ""
+
+#: i2p2www/pages/downloads/list.html:256
+msgid "Alternately, you can use the manual method specified below."
+msgstr ""
+
+#: i2p2www/pages/downloads/list.html:266
+msgid "Manual updates"
+msgstr ""
+
+#: i2p2www/pages/downloads/list.html:278
+msgid ""
+"Download that file to your I2P\n"
+" installation directory and rename as i2pupdate.zip.\n"
+" (alternately, you can get the source as above and run \"ant "
+"updater\", then copy the\n"
+" resulting i2pupdate.zip to your I2P installation directory). You do"
+" \n"
+" NOT need to unzip that file."
+msgstr ""
+
+#: i2p2www/pages/downloads/list.html:287
+msgid "Click \"Restart\""
+msgstr ""
+
+#: i2p2www/pages/downloads/list.html:292
+msgid "Grab a cup of coffee and come back in 11 minutes"
+msgstr ""
+
+#: i2p2www/pages/downloads/list.html:300
+#, python-format
+msgid ""
+"The file is signed by zzz,\n"
+"whose key is here."
+msgstr ""
+
+#: i2p2www/pages/downloads/list.html:305
+msgid "Previous Releases"
+msgstr ""
+
+#: i2p2www/pages/downloads/list.html:307
+#, python-format
+msgid ""
+"Previous releases are available on Google "
+"Code\n"
+"and Launchpad\n"
+"and within the I2P network on %(echelon)s."
+msgstr ""
+
+#: i2p2www/pages/downloads/select.html:2 i2p2www/pages/downloads/select.html:4
+msgid "Mirror selection"
+msgstr ""
+
+#: i2p2www/pages/downloads/select.html:5
+msgid "File:"
+msgstr ""
+
+#: i2p2www/pages/downloads/select.html:10
+msgid "Any mirror"
+msgstr ""
+
+#: i2p2www/pages/global/bounty.html:19
+msgid ""
+"To claim the bounty the author must not be paid by other organizations\n"
+"or teams for this work (e.g. GSoC students are not valid)."
+msgstr ""
+
+#: i2p2www/pages/global/bounty.html:29
+#, python-format
+msgid ""
+"Bounty amounts may be increased by further donations. Do\n"
+"you think these are important? Add in your "
+"donation, \n"
+"marking the amount for the %(donatename)s bounty!"
+msgstr ""
+
+#: i2p2www/pages/global/error_404.html:3
+msgid "Not found"
+msgstr ""
+
+#: i2p2www/pages/global/error_404.html:9
+msgid ""
+"Yep... the resource, you were searching for, is named differently, "
+"doesn't exist or was removed."
+msgstr ""
+
+#: i2p2www/pages/global/error_500.html:5
+msgid "Server error"
+msgstr ""
+
+#: i2p2www/pages/global/error_500.html:13
+msgid "500 Server error"
+msgstr ""
+
+#: i2p2www/pages/global/error_500.html:17
+msgid "Umm... the server encountered some sort of error."
+msgstr ""
+
+#: i2p2www/pages/global/footer.html:2
+msgid "Mirrors"
+msgstr ""
+
+#: i2p2www/pages/global/footer.html:9
+msgid "Secure"
+msgstr ""
+
+#: i2p2www/pages/global/footer.html:16
+msgid "Misc."
+msgstr ""
+
+#: i2p2www/pages/global/footer.html:19 i2p2www/pages/site/links.html:2
+msgid "Links"
+msgstr ""
+
+#: i2p2www/pages/global/footer.html:20
+msgid "Impressum"
+msgstr ""
+
+#: i2p2www/pages/global/footer.html:24
+msgid "T-Shirts!"
+msgstr ""
+
+#: i2p2www/pages/global/footer.html:26
+msgid "Europe"
+msgstr ""
+
+#: i2p2www/pages/global/footer.html:27
+msgid "USA"
+msgstr ""
+
+#: i2p2www/pages/global/footer.html:31
+msgid "Donate"
+msgstr ""
+
+#: i2p2www/pages/global/layout.html:29
+msgid "Skip navigation"
+msgstr ""
+
+#: i2p2www/pages/global/layout.html:32
+msgid "I2P Logo"
+msgstr ""
+
+#: i2p2www/pages/global/layout.html:32 i2p2www/pages/site/index.html:3
+msgid "The Invisible Internet Project"
+msgstr ""
+
+#: i2p2www/pages/global/layout.html:56
+#, python-format
+msgid ""
+"This page was last updated in %(lastupdated)s and is accurate for router "
+"version %(accuratefor)s."
+msgstr ""
+
+#: i2p2www/pages/global/layout.html:60
+#, python-format
+msgid "This page was last updated in %(lastupdated)s."
+msgstr ""
+
+#: i2p2www/pages/global/layout.html:64
+#, python-format
+msgid "This page is accurate for router version %(accuratefor)s."
+msgstr ""
+
+#: i2p2www/pages/global/macros:21
+msgid "Previous"
+msgstr ""
+
+#: i2p2www/pages/global/macros:36
+msgid "Next"
+msgstr ""
+
+#: i2p2www/pages/global/macros:43
+msgid "Posted in"
+msgstr ""
+
+#: i2p2www/pages/global/nav.html:4
+msgid "About"
+msgstr ""
+
+#: i2p2www/pages/global/nav.html:6
+msgid "Introduction to I2P"
+msgstr "Wprowadzenie do I2P"
+
+#: i2p2www/pages/global/nav.html:7
+msgid "Comparisons"
+msgstr ""
+
+#: i2p2www/pages/global/nav.html:9
+msgid "Overview of comparisons"
+msgstr ""
+
+#: i2p2www/pages/global/nav.html:13
+msgid "Other anonymous networks"
+msgstr "Inne anonimowe sieci"
+
+#: i2p2www/pages/global/nav.html:16
+msgid "Documentation"
+msgstr "Dokumentacja"
+
+#: i2p2www/pages/global/nav.html:18
+msgid "Documentation index"
+msgstr "Indeks dokumentacji"
+
+#: i2p2www/pages/global/nav.html:19
+msgid "How does it work?"
+msgstr "Jak to działa?"
+
+#: i2p2www/pages/global/nav.html:21
+msgid "Gentle intro"
+msgstr ""
+
+#: i2p2www/pages/global/nav.html:22
+msgid "Tech intro"
+msgstr ""
+
+#: i2p2www/pages/global/nav.html:23
+msgid "Threat model"
+msgstr ""
+
+#: i2p2www/pages/global/nav.html:24
+msgid "Garlic routing"
+msgstr "Garlic routing"
+
+#: i2p2www/pages/global/nav.html:25
+msgid "Network database"
+msgstr ""
+
+#: i2p2www/pages/global/nav.html:26
+msgid "Tunnel routing"
+msgstr ""
+
+#: i2p2www/pages/global/nav.html:27
+msgid "Peer selection"
+msgstr ""
+
+#: i2p2www/pages/global/nav.html:28
+msgid "Cryptography"
+msgstr "Kryptografia"
+
+#: i2p2www/pages/global/nav.html:29
+msgid "ElGamal/AES+SessionTags"
+msgstr "ElGamal/AES+SessionTags"
+
+#: i2p2www/pages/global/nav.html:32
+msgid "Specifications"
+msgstr ""
+
+#: i2p2www/pages/global/nav.html:34
+msgid "Blockfile"
+msgstr ""
+
+#: i2p2www/pages/global/nav.html:35
+msgid "Common structures"
+msgstr ""
+
+#: i2p2www/pages/global/nav.html:36
+msgid "Configuration files"
+msgstr ""
+
+#: i2p2www/pages/global/nav.html:37 i2p2www/pages/global/nav.html:59
+msgid "Datagrams"
+msgstr ""
+
+#: i2p2www/pages/global/nav.html:38
+msgid "GeoIP files"
+msgstr ""
+
+#: i2p2www/pages/global/nav.html:41 i2p2www/pages/global/nav.html:91
+msgid "Plugins"
+msgstr ""
+
+#: i2p2www/pages/global/nav.html:43 i2p2www/pages/global/nav.html:57
+msgid "Streaming library"
+msgstr ""
+
+#: i2p2www/pages/global/nav.html:44
+msgid "Tunnel creation"
+msgstr ""
+
+#: i2p2www/pages/global/nav.html:45
+msgid "Tunnel messages"
+msgstr ""
+
+#: i2p2www/pages/global/nav.html:46
+msgid "Software updates"
+msgstr ""
+
+#: i2p2www/pages/global/nav.html:49
+msgid "API"
+msgstr "API"
+
+#: i2p2www/pages/global/nav.html:58
+msgid "Ministreaming library"
+msgstr ""
+
+#: i2p2www/pages/global/nav.html:63 i2p2www/pages/global/nav.html:116
+msgid "Applications"
+msgstr "Aplikacje"
+
+#: i2p2www/pages/global/nav.html:65
+msgid "Supported applications"
+msgstr "Wspierane aplikacje"
+
+#: i2p2www/pages/global/nav.html:66
+msgid "Bittorrent"
+msgstr "Bittorrent"
+
+#: i2p2www/pages/global/nav.html:69
+msgid "Protocols"
+msgstr "Protokoły"
+
+#: i2p2www/pages/global/nav.html:71
+msgid "Protocol stack"
+msgstr ""
+
+#: i2p2www/pages/global/nav.html:76
+msgid "Transports"
+msgstr ""
+
+#: i2p2www/pages/global/nav.html:78
+msgid "Transport layer overview"
+msgstr ""
+
+#: i2p2www/pages/global/nav.html:83
+msgid "Tunnels"
+msgstr "Tunele"
+
+#: i2p2www/pages/global/nav.html:85
+msgid "Tunnel implementation"
+msgstr "Implementacje tuneli"
+
+#: i2p2www/pages/global/nav.html:86
+msgid "Unidirectional tunnels"
+msgstr "Tunele jednokierunkowe"
+
+#: i2p2www/pages/global/nav.html:87
+msgid "Old implementation"
+msgstr ""
+
+#: i2p2www/pages/global/nav.html:90
+msgid "Naming and addressbook"
+msgstr ""
+
+#: i2p2www/pages/global/nav.html:94
+msgid "Team"
+msgstr "Zespół"
+
+#: i2p2www/pages/global/nav.html:96
+msgid "Hall of Fame"
+msgstr ""
+
+#: i2p2www/pages/global/nav.html:97
+msgid "Academic papers and peer review"
+msgstr ""
+
+#: i2p2www/pages/global/nav.html:98
+msgid "Presentations, tutorials and articles"
+msgstr ""
+
+#: i2p2www/pages/global/nav.html:99
+msgid "Contact us"
+msgstr ""
+
+#: i2p2www/pages/global/nav.html:102
+msgid "Help"
+msgstr "Pomoc"
+
+#: i2p2www/pages/global/nav.html:104
+msgid "FAQ"
+msgstr "FAQ"
+
+#: i2p2www/pages/global/nav.html:105
+msgid "How to browse I2P"
+msgstr "Jak przeglądać I2P"
+
+#: i2p2www/pages/global/nav.html:106
+msgid "Glossary"
+msgstr "Słowniczek pojęć"
+
+#: i2p2www/pages/global/nav.html:107
+msgid "Performance"
+msgstr "Wydajność"
+
+#: i2p2www/pages/global/nav.html:108 i2p2www/pages/site/contact.html:28
+msgid "Forums"
+msgstr "Forum"
+
+#: i2p2www/pages/global/nav.html:111
+msgid "Volunteer"
+msgstr ""
+
+#: i2p2www/pages/global/nav.html:113
+msgid "Get involved!"
+msgstr ""
+
+#: i2p2www/pages/global/nav.html:114
+msgid "Develop"
+msgstr ""
+
+#: i2p2www/pages/global/nav.html:117
+msgid "Licenses"
+msgstr "Licencje"
+
+#: i2p2www/pages/global/nav.html:118
+msgid "Release signing keys"
+msgstr ""
+
+#: i2p2www/pages/global/nav.html:119
+msgid "Signed keys"
+msgstr ""
+
+#: i2p2www/pages/global/nav.html:120
+msgid "Developers keys"
+msgstr ""
+
+#: i2p2www/pages/global/nav.html:121
+msgid "Bug tracker"
+msgstr ""
+
+#: i2p2www/pages/global/nav.html:124
+msgid "Academic research"
+msgstr ""
+
+#: i2p2www/pages/global/nav.html:125
+msgid "Open research questions"
+msgstr ""
+
+#: i2p2www/pages/global/nav.html:126
+msgid "Guides"
+msgstr ""
+
+#: i2p2www/pages/global/nav.html:128
+msgid "New developers"
+msgstr ""
+
+#: i2p2www/pages/global/nav.html:129
+msgid "Using an IDE with I2P"
+msgstr ""
+
+#: i2p2www/pages/global/nav.html:130
+msgid "Developer guidelines and coding style"
+msgstr ""
+
+#: i2p2www/pages/global/nav.html:131
+msgid "Monotone"
+msgstr ""
+
+#: i2p2www/pages/global/nav.html:132
+msgid "New translators"
+msgstr "Nowi tłumacze"
+
+#: i2p2www/pages/global/nav.html:135
+msgid "Bounties"
+msgstr ""
+
+#: i2p2www/pages/global/nav.html:136 i2p2www/pages/meetings/index.html:2
+msgid "Meetings"
+msgstr "Spotkania"
+
+#: i2p2www/pages/global/nav.html:137
+msgid "Roadmap"
+msgstr ""
+
+#: i2p2www/pages/global/nav.html:138
+msgid "Task list"
+msgstr ""
+
+#: i2p2www/pages/global/nav.html:141
+msgid "Language"
+msgstr "Język"
+
+#: i2p2www/pages/meetings/index.html:4
+msgid "I2P Meetings ATOM Feed"
+msgstr ""
+
+#: i2p2www/pages/meetings/index.html:7
+msgid "Logs of past I2P meetings"
+msgstr ""
+
+#: i2p2www/pages/meetings/index.html:9
+msgid "Meetings are currently on hold until a more suitable time can be chosen."
+msgstr ""
+
+#: i2p2www/pages/meetings/index.html:13
+#, python-format
+msgid ""
+"If you have something to discuss, please find the developers on IRC in "
+"#i2p-dev.\n"
+"Status updates from developers are also "
+"available."
+msgstr ""
+
+#: i2p2www/pages/meetings/show.html:2
+#, python-format
+msgid "I2P Development Meeting %(id)s"
+msgstr ""
+
+#: i2p2www/pages/meetings/show.html:10
+msgid "Full IRC Log"
+msgstr ""
+
+#: i2p2www/pages/papers/list.html:29
+msgid "By topic"
+msgstr "Wg. tematu"
+
+#: i2p2www/pages/papers/list.html:35
+msgid "By date"
+msgstr "Wg. daty"
+
+#: i2p2www/pages/papers/list.html:41
+msgid "By author"
+msgstr "Wg. autora"
+
+#: i2p2www/pages/papers/list.html:83
+#, python-format
+msgid ""
+"Please send new or corrected entries to\n"
+"%(email)s.
\n"
+"If you can, please format them as BibTeX; see our\n"
+"BibTeX source page for examples.
\n"
+"Remember to include URLs if possible:\n"
+"offline papers are less useful."
+msgstr ""
+
+#: i2p2www/pages/site/contact.html:2
+msgid "Contact"
+msgstr "Kontakt"
+
+#: i2p2www/pages/site/contact.html:4
+msgid "Email"
+msgstr ""
+
+#: i2p2www/pages/site/contact.html:11
+msgid ""
+"Our primary IRC network is the Irc2P network within I2P; a default tunnel"
+" to this network is set up with new router installs.\n"
+" We are also present on multiple standard networks like OFTC,\n"
+" EIN and Freenode.\n"
+" All I2P-related channels on all these network are linked to the main "
+"channels on Irc2P via relay bots."
+msgstr ""
+
+#: i2p2www/pages/site/contact.html:19
+msgid "Channel list:"
+msgstr "Lista kanałów:"
+
+#: i2p2www/pages/site/contact.html:21
+msgid "General i2p discussion"
+msgstr ""
+
+#: i2p2www/pages/site/contact.html:22
+msgid "Offtopic"
+msgstr ""
+
+#: i2p2www/pages/site/contact.html:23
+msgid "Development talk"
+msgstr ""
+
+#: i2p2www/pages/site/contact.html:24
+msgid "Help channel"
+msgstr "Kanał pomocy"
+
+#: i2p2www/pages/site/contact.html:29
+#, python-format
+msgid ""
+"Most of the discussion about I2P's development happens on the I2P developer forum. This is usually the best"
+" place to start with inquiries, if the dev IRC channel is inactive."
+msgstr ""
+
+#: i2p2www/pages/site/contact.html:33
+msgid "Mailing lists"
+msgstr ""
+
+#: i2p2www/pages/site/contact.html:34
+msgid ""
+"I2P does have a mailing list, but it is rarely used as the current small "
+"team of developers prefer to communicate via IRC or the developer forum. "
+"This may change in future."
+msgstr ""
+
+#: i2p2www/pages/site/contact.html:39
+msgid "Subscribing"
+msgstr ""
+
+#: i2p2www/pages/site/contact.html:40
+msgid ""
+"To subscribe to a mailing list, go to the list information page (linked "
+"below) and fill out the form. I2P-internal email addresses "
+"(foobar@mail.i2p) can be used."
+msgstr ""
+
+#: i2p2www/pages/site/contact.html:44
+msgid "Unsubscribing"
+msgstr ""
+
+#: i2p2www/pages/site/contact.html:45
+msgid ""
+"To unsubscribe from a mailing list or edit your subscription options, go "
+"to the list information page (linked below) and enter your subscription "
+"email address."
+msgstr ""
+
+#: i2p2www/pages/site/contact.html:49
+msgid "Lists"
+msgstr "Listy"
+
+#: i2p2www/pages/site/contact.html:52
+msgid "Archive"
+msgstr "Archiwum"
+
+#: i2p2www/pages/site/contact.html:53
+msgid ""
+"General I2P discussion - anything that doesn't fit in a different list "
+"goes here."
+msgstr ""
+
+#: i2p2www/pages/site/contact.html:59
+msgid ""
+"You don't like mailing lists? Then this is for you. All mailing lists are"
+" available via NNTP as well."
+msgstr ""
+
+#: i2p2www/pages/site/contact.html:64
+msgid "Group-List-mapping:"
+msgstr ""
+
+#: i2p2www/pages/site/contact.html:68
+msgid "Servers:"
+msgstr "Serwery:"
+
+#: i2p2www/pages/site/faq.html:2
+msgid "Frequently Asked Questions"
+msgstr "Najczęściej Zadawane Pytania (FAQ)"
+
+#: i2p2www/pages/site/faq.html:4
+msgid "Index"
+msgstr "Indeks"
+
+#: i2p2www/pages/site/faq.html:7
+msgid "General"
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:9 i2p2www/pages/site/faq.html:51
+msgid "What systems will I2P run on?"
+msgstr "Na jakich systemach I2P będzie działać?"
+
+#: i2p2www/pages/site/faq.html:10
+msgid "Whats an \"eepsite\" and how do I configure my browser so I can use them?"
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:11 i2p2www/pages/site/faq.html:264
+msgid "My router has very few active peers, is this OK?"
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:12 i2p2www/pages/site/faq.html:499
+msgid "What do the Active x/y numbers mean in the router console?"
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:13 i2p2www/pages/site/faq.html:226
+msgid ""
+"My active peers / known peers / participating tunnels / connections / "
+"bandwidth vary dramatically over time! Is anything wrong?"
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:14 i2p2www/pages/site/faq.html:349
+msgid "Is using an outproxy safe?"
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:15 i2p2www/pages/site/faq.html:375
+msgid "Most of the eepsites within I2P are down?"
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:16 i2p2www/pages/site/faq.html:528
+msgid "What ports does I2P use?"
+msgstr "Jakich portów używa I2P?"
+
+#: i2p2www/pages/site/faq.html:17
+msgid "Why is I2P listening for connections on port 32000?"
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:18 i2p2www/pages/site/faq.html:62
+msgid "I think I found a bug, where can I report it?"
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:19 i2p2www/pages/site/faq.html:108
+msgid "What happened to *.i2p.net? What happened to jrandom? Is I2P dead?"
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:20 i2p2www/pages/site/faq.html:846
+msgid "I have a question!"
+msgstr "Mam pytanie!"
+
+#: i2p2www/pages/site/faq.html:22
+msgid "Setup"
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:24 i2p2www/pages/site/faq.html:233
+msgid ""
+"My router has been up for several minutes and has zero or very few "
+"connections"
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:25 i2p2www/pages/site/faq.html:391
+msgid "Why is I2P so slow?"
+msgstr "Dlaczego I2P jest tak wolne?"
+
+#: i2p2www/pages/site/faq.html:26 i2p2www/pages/site/faq.html:79
+msgid ""
+"I'm missing lots of hosts in my addressbook. What are some good "
+"subscription links?"
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:27 i2p2www/pages/site/faq.html:384
+msgid "How do I set up my own eepsite?"
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:28 i2p2www/pages/site/faq.html:417
+msgid "Bittorrent / I2PSnark / Azureus I2P Plugin Questions?"
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:29 i2p2www/pages/site/faq.html:424
+msgid "How do I connect to IRC within I2P?"
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:30 i2p2www/pages/site/faq.html:282
+msgid "I can't access regular Internet sites through I2P."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:31 i2p2www/pages/site/faq.html:297
+msgid "I can't access https:// or ftp:// sites through I2P."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:32 i2p2www/pages/site/faq.html:507
+msgid "Is it possible to use I2P as a SOCKS proxy?"
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:33 i2p2www/pages/site/faq.html:490
+msgid "How do I configure my browser?"
+msgstr "Jak skonfigurować moją przeglądarkę?"
+
+#: i2p2www/pages/site/faq.html:34 i2p2www/pages/site/faq.html:435
+msgid ""
+"How can I access the web console from my other machines or password "
+"protect it?"
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:35 i2p2www/pages/site/faq.html:475
+msgid "How can I use applications from my other machines?"
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:36 i2p2www/pages/site/faq.html:749
+msgid "How do I reseed manually?"
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:37 i2p2www/pages/site/faq.html:125
+msgid "My router is using too much CPU?!?"
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:39
+msgid "Misconception"
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:41 i2p2www/pages/site/faq.html:367
+msgid ""
+"How do I access IRC, BitTorrent, or other services on the regular "
+"Internet?"
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:42
+msgid ""
+"Is my router an \"exit node\"(outproxy) to the regular Internet? I don't "
+"want it to be."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:43 i2p2www/pages/site/faq.html:189
+msgid ""
+"I am opposed to certain types of content. How do I keep from "
+"distributing, storing, or accessing them?"
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:45
+msgid "Errors and Their Solutions"
+msgstr "Błędy i ich rozwiązania"
+
+#: i2p2www/pages/site/faq.html:47 i2p2www/pages/site/faq.html:785
+msgid ""
+"I'm using FreeBSD and when I start I2P I receive an error about "
+"libm.so.4!"
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:48
+msgid ""
+"In wrapper.log I see an error stating Protocol family "
+"unavailable when I2P is loading"
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:52 i2p2www/pages/site/faq.html:63
+#: i2p2www/pages/site/faq.html:80 i2p2www/pages/site/faq.html:109
+#: i2p2www/pages/site/faq.html:126 i2p2www/pages/site/faq.html:190
+#: i2p2www/pages/site/faq.html:227 i2p2www/pages/site/faq.html:234
+#: i2p2www/pages/site/faq.html:265 i2p2www/pages/site/faq.html:274
+#: i2p2www/pages/site/faq.html:283 i2p2www/pages/site/faq.html:298
+#: i2p2www/pages/site/faq.html:350 i2p2www/pages/site/faq.html:368
+#: i2p2www/pages/site/faq.html:376 i2p2www/pages/site/faq.html:385
+#: i2p2www/pages/site/faq.html:392 i2p2www/pages/site/faq.html:418
+#: i2p2www/pages/site/faq.html:425 i2p2www/pages/site/faq.html:436
+#: i2p2www/pages/site/faq.html:476 i2p2www/pages/site/faq.html:483
+#: i2p2www/pages/site/faq.html:491 i2p2www/pages/site/faq.html:500
+#: i2p2www/pages/site/faq.html:508 i2p2www/pages/site/faq.html:529
+#: i2p2www/pages/site/faq.html:737 i2p2www/pages/site/faq.html:750
+#: i2p2www/pages/site/faq.html:786 i2p2www/pages/site/faq.html:818
+#: i2p2www/pages/site/faq.html:847
+msgid "link"
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:53
+#, python-format
+msgid ""
+"While I2P has been reported to run PCs as meagre as a low-end Pentium II "
+"with 64 MB of RAM, you'll have a much better experience on a Pentium III "
+"(or better) with 128MB of RAM (or more). A chart "
+"comparing the performance of the various JREs can be found at %(chart)s, but in short: it's at all possible, use"
+" Sun/Oracle Java or OpenJDK."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:57
+msgid ""
+"I2P has been tested on Windows, Linux, FreeBSD (see the note below), OSX, and OpenSolaris. There is work "
+"underway to bring I2P to the Android platform."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:65
+msgid "Here are some places, pick one or more."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:71
+msgid "Discuss with the developers on IRC in #i2p-dev"
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:75
+msgid "Please include relevant information from the router logs and wrapper logs."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:81
+msgid ""
+"The default subscription is to http://www.i2p2.i2p/hosts.txt which is "
+"updated rarely.\n"
+"If you don't have another subscription, you may often have to use "
+"\"jump\" links which\n"
+"is annoying."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:87
+msgid ""
+"Here are some other public addressbook subscription links. You may wish "
+"to add one or two\n"
+"to your susidns "
+"subscription list.\n"
+"You don't need to add all of them, as they sync with each other "
+"periodically.\n"
+"The links using a cgi-bin application employ various strategies to "
+"minimize\n"
+"the number of duplicate addresses delivered, so they should be more "
+"efficient.\n"
+"Note that subscribing to a hosts.txt service is an act of \"trust\", as a"
+" malicious\n"
+"subscription could give you incorrect addresses. So think about whether "
+"you\n"
+"want to trust any of these.\n"
+"The operators of these services may have various policies for listing "
+"hosts.\n"
+"Presence on this list does not imply endorsement."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:110
+msgid ""
+"Jrandom was the lead developer of I2P and\n"
+"Syndie for several years.\n"
+"We do not know if or when jrandom will return.\n"
+"The *.i2p.net domains were left in a non-functioning state after a power\n"
+"outage at the hosting company."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:118
+#, python-format
+msgid ""
+"See this page for jrandom's parting message "
+"and additional information\n"
+"on the migration of *.i2p.net to this website."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:123
+msgid "I2P remains in active development."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:127
+msgid "There are many possible causes of high CPU usage. Here is a checklist:"
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:132
+msgid ""
+"Try to use either OpenJDK or Sun/Oracle Java if it's available for your "
+"system. You can check \n"
+"which version of java you have installed by typing java "
+"-version at a \n"
+"command/shell prompt. Performance tends to suffer with other "
+"implementations of java."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:139
+msgid ""
+"Are you running a BitTorrent client over I2P? Try reducing the number of "
+"torrents, the bandwidth limits,\n"
+"or try turning it off completely to see if that helps."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:145
+msgid ""
+"Are your bandwidth limits set too high? It is possible that too much "
+"traffic is going through your\n"
+"I2P router and it is overloaded. Try reducing the setting for share "
+"bandwidth percentage on the configuration page."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:150
+msgid ""
+"Make sure that you're running the latest version of I2P to get the "
+"benefits of increased performance and bug fixes."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:155
+msgid ""
+"Has enough memory been set aside for use by I2P? Look at the memory graph"
+" on the graphs page to see\n"
+"if the memory usage is \"pegged\"—the JVM is spending most of its "
+"time in\n"
+"garbage collection. Increase the setting "
+"wrapper.java.maxmemory in wrapper.config."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:162
+msgid ""
+"Is the CPU usage simply higher than you would like, or is it pegged at "
+"100% for a long time?\n"
+"If it's pegged, this could be a bug. Look in the logs for clues."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:168
+#, python-format
+msgid ""
+"You may be using the Java-based BigInteger library instead of the native "
+"version,\n"
+"especially if you are running on a new or unusual OS or hardware "
+"(OpenSolaris, mipsel, etc.).\n"
+"See the jbigi page for instructions on\n"
+"diagnosing, building, and testing methods."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:176
+msgid ""
+"If your native jbigi library is working fine, the biggest user of\n"
+"CPU may be routing traffic for participating tunnels. This uses CPU\n"
+"because at each hop a layer of encryption must be decoded.\n"
+"You can limit participating traffic in two ways - by reducing the\n"
+"share bandwidth on\n"
+"confignet.jsp,\n"
+"or by setting router.maxParticipatingTunnels=nnn on\n"
+"configadvanced.jsp."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:191
+msgid ""
+"Hmm. I2P is an anonymous network, so that's a tricky one.\n"
+"I2P is designed to withstand censorship, providing a means for everyone "
+"to communicate freely. \n"
+"The best way to keep your PC free of (encrypted) traffic that you dislike"
+" is to not use I2P.\n"
+"Freedom of speech has some costs.\n"
+"But let's address your question in three parts:"
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:200
+msgid ""
+"Distribution - All traffic on I2P is encrypted in multiple layers."
+" You don't know\n"
+"a message's contents, source, or destination.\n"
+"All traffic you route is internal to the I2P network, you are not an exit node (outproxy).\n"
+"Your only alternative is to refuse to route\n"
+"any traffic, by setting your share bandwidth or maximum "
+"participating tunnels to 0 (see above).\n"
+"It would be nice if you didn't do this, you should help the network by "
+"routing traffic for others.\n"
+"Over 95% of users route traffic for others."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:211
+msgid ""
+"Storage - I2P does not do distributed storage of content. You must"
+" be thinking of\n"
+"Freenet.\n"
+"Nobody's content is being stored on your computer by running I2P."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:218
+msgid ""
+"Access - If there are some eepsites you don't like, don't go "
+"there.\n"
+"Or, use a blocking proxy like Privoxy or some type of \"net nanny\"."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:228
+msgid ""
+"No. This is normal.\n"
+"All routers adjust dynamically to changing network conditions and demands."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:235
+msgid ""
+"You may need to reseed your I2P router. With recent versions of I2P you "
+"can go to http://localhost:7657/configreseed"
+" and click the Save Changes and Reseed Now button. If this "
+"method doesn't work—or you're using a very old version—you "
+"may need to reseed manually."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:238
+msgid ""
+"The reseed URL changed a few years ago. If this is your first install and"
+" you have installed\n"
+"an old (0.6.1.30 or earlier) release, or\n"
+"you have not run I2P in a long time, you must change the URL and then\n"
+"click \"Reseed\" on the console to find other routers.\n"
+"After your router is running,\n"
+"on configadvanced.jsp,"
+"\n"
+"add the line i2p.reseedURL=http://netdb.i2p2.de/\n"
+"OR i2p.reseedURL=http://i2pdb.tin0.de/netDb/ (either should "
+"work),\n"
+"then click \"Apply\", then click the \"reseed\" link on the left."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:249
+#, python-format
+msgid ""
+"This works if you are running 0.6.1.27 or later.\n"
+"If you are running release 0.6.1.31 or later, you probably don't need to "
+"do this.\n"
+"If you are running release 0.6.1.26 or earlier, either follow the\n"
+"manual reseed instructions below\n"
+"or install the latest release.\n"
+"Possible alternate method - add\n"
+"wrapper.java.additional.5=-Di2p.reseedURL=http://netdb.i2p2.de/\n"
+"to wrapper.config, shutdown the router completely, then start again, then"
+" click \"reseed\".\n"
+"Let us know if this works."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:260
+#, python-format
+msgid ""
+"...but you *really* should upgrade to "
+"the latest version."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:266
+msgid ""
+"If your router has 10 or more active peers, everything is fine. Changes "
+"in releases 0.6.1.31 and 0.6.1.32 improved the\n"
+"efficiency of the router and effectively reduced the number of active "
+"peers.\n"
+"The router should maintain connections to a few peers at all "
+"times.\n"
+"The best way to stay \"better-connected\" to the network is to share more bandwidth."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:273
+msgid ""
+"Is my router an \"exit node\" to the regular Internet? I don't want it to"
+" be."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:275
+msgid ""
+"No. Unlike Tor,\n"
+"\"exit nodes\" or \"outproxies\" are not an inherent part of the network."
+"\n"
+"Only volunteers who set up and run separate applications will relay "
+"traffic to the regular Internet.\n"
+"There are very, very few of these."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:284
+msgid ""
+"See above. There are very few HTTP \"outproxies\", they are not an "
+"inherent part of the network,\n"
+"and they may not be up.\n"
+"In addition, the old outproxies squid.i2p, true.i2p, and krabs.i2p have "
+"vanished.\n"
+"The only outproxy at the moment is false.i2p.\n"
+"To use it, edit your i2ptunnel "
+"settings for eepProxy\n"
+"and set your outproxy list to 'false.i2p' (only).\n"
+"Then stop and restart the eepProxy.\n"
+"If it doesn't work, the outproxy is not up. It is not I2P's fault.\n"
+"If your primary reason to use an anonymous network is to anonymously "
+"access sites\n"
+"on the regular Internet, you should probably try Tor."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:299
+msgid ""
+"Within I2P, there is no need for HTTPS, as all traffic is encrypted end-"
+"to-end.\n"
+"FTP is not supported for technical reasons."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:303
+msgid ""
+"There are no FTP \"outproxies\" to the Internet—it may not even be "
+"possible to set up one.\n"
+"Any other kind of outproxy may work if it's set up with a standard "
+"tunnel. \n"
+"If you would like to set up some type of outproxy, carefully research the"
+" potential risks.\n"
+"The I2P community may or may not be able to help with the technical "
+"aspects, feel free to ask."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:309
+msgid ""
+"As explained several times above, any existing outproxy isn't a core part"
+" of the network.\n"
+"They are services run by individuals and they may or may not\n"
+"be operational at any given time."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:314
+msgid ""
+"Update: Thanks to the work of h2ik, there is an https outproxy "
+"available for use via I2P. Starting with I2P 0.8.4 the tunnel is "
+"configured out of the box.
\n"
+"In case the https outproxy is not available in your version of I2P, you "
+"can add it easily by doing the following:"
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:320
+msgid ""
+"Open i2p tunnel "
+"manager. Scroll down to the bottom."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:325
+msgid ""
+"Choose CONNECT from New Client Tunnel dropdown list, click "
+"Create"
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:330
+#, python-format
+msgid ""
+"In the new page, name and describe your new https tunnel as"
+" you like.\n"
+"The Access Point is your local port for the new https proxy "
+"recommended port's 4445.\n"
+"Outproxy should be the outproxy's .i2p address which supports "
+"https. \n"
+"See this forum post of h2ik's for the "
+"address. \n"
+"Make sure Shared Client, Delay Connect, AutoStart "
+"are checked.\n"
+"Other options should be left at the defaults. Click Save. In tunnel "
+"manger, click the Start button next to your new tunnel."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:340
+msgid ""
+"In firefox, click through "
+"Tools>Options>Advanced>Network>Setting."
+"\n"
+"Untick Use this proxy for all protocol, set SSL proxy: to "
+"localhost:4445."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:345
+msgid "Done."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:351
+#, python-format
+msgid ""
+"\n"
+"This is a question that only you can answer because the correct answer "
+"depends on your behaviours, your\n"
+"threat model, and how much you trust the "
+"outproxy operator."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:355
+msgid ""
+"Like Tor, I2P does not magically encrypt the Internet.\n"
+"You are vulnerable to snooping by the outproxy operators.\n"
+"The Tor"
+" FAQ\n"
+"does a good job of explaining this."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:361
+#, python-format
+msgid ""
+"In addition, you may be vulnerable to collusion between the outproxy "
+"operator\n"
+"and operators of other I2P services, if you use the same tunnels "
+"(\"shared clients\").\n"
+"There is additional discussion about this on %(zzz)s."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:369
+msgid ""
+"Unless an outproxy has been set up for the service you want to connect "
+"to, this cannot be done.\n"
+"There are only three types of outproxies running right now: HTTP, HTTPS, "
+"and email. Note that there is not a SOCKS outproxy.\n"
+"If this type of service is required, try Tor."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:377
+#, python-format
+msgid ""
+"If you consider every eepsite that has ever been created, yes, most of "
+"them are down.\n"
+"People and eepsites come and go.\n"
+"A good way to get started in I2P is check out a list of eepsites that are"
+" currently up.\n"
+"%(eepstatus)s tracks active eepsites."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:386
+msgid ""
+"Click on the Website link\n"
+"at the top of your router console for instructions."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:393
+msgid ""
+"Why are downloads, torrents, web browsing, and everything else so slow on"
+" I2P?\n"
+"The encryption and routing within the I2P network adds a substantial "
+"amount of overhead and limits bandwidth.\n"
+"Anonymity isn't free."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:398
+msgid ""
+"In addition, you and everybody else probably need to increase your "
+"bandwidth limits.\n"
+"Two key settings are the inbound and outbound bandwidth limiters on\n"
+"the configuration page.\n"
+"With the default settings of 32KBps you will generally get no better than"
+" 15KBps data transfer in I2PSnark.\n"
+"Increasing the settings (but keeping within your actual connection "
+"limitations)\n"
+"will increase the potential transfer rate for I2PSnark and all other "
+"applications."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:406
+msgid ""
+"Also, do you have sufficient share bandwidth configured to allow "
+"participating tunnels\n"
+"to route through your router? Believe it or not, allowing participating "
+"traffic\n"
+"keeps you well-integrated in the network and helps your own transfer "
+"speeds."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:411
+#, python-format
+msgid ""
+"I2P is a work in progress. Lots of improvements and fixes are being "
+"implemented, and\n"
+"generally speaking, running the latest release will help your "
+"performance.\n"
+"If you haven't, install the latest "
+"release."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:419
+#, python-format
+msgid ""
+"See the\n"
+"I2P Bittorrent FAQ"
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:426
+msgid ""
+"\n"
+"A tunnel to the main IRC server within I2P, Irc2P, is created when I2P is"
+" installed (see\n"
+"the I2PTunnel "
+"configuration page),\n"
+"and is automatically started when the I2P router starts. To connect to "
+"it, tell your IRC\n"
+"client to connect to localhost 6668. XChat-like client users"
+" can create a\n"
+"new network with the server localhost/6668 (remember to tick"
+" "Bypass\n"
+"proxy server" if you have a proxy server configured)."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:437
+msgid ""
+"For security purposes, the router's admin console by default only listens"
+"\n"
+"for connections on the local interface. However, with a little hacking,\n"
+"you can make it reachable remotely:"
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:445
+msgid ""
+"Open ~/.i2p/clients.config and replace
\n"
+"clientApp.0.args=7657 ::1,127.0.0.1 ./webapps/
\n"
+"with
\n"
+"clientApp.0.args=7657 0.0.0.0 ./webapps/"
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:453
+msgid ""
+"Go to http://localhost:7657/configui"
+"\n"
+"and add a console username and password if desired."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:459
+msgid ""
+"Go to http://localhost:7657/index.jsp"
+"\n"
+"and hit \"Graceful restart\", which restarts the JVM and reloads the "
+"client applications"
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:466
+msgid ""
+"After that fires up, you should now be able to reach your console "
+"remotely. Reload the router at\n"
+"http://127.0.0.1:7657 and you will be prompted for the username and "
+"password you specified in step 2\n"
+"above if your browser supports the authentication popup. Note: the\n"
+"0.0.0.0 above specifies an interface, not a network "
+"or netmask. 0.0.0.0\n"
+"means \"bind to all interfaces\", so it can be reachable on "
+"127.0.0.1:7657 as well as\n"
+"any LAN/WAN IP."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:477
+msgid ""
+"By default, the router I2CP interface (port 7654) binds to address "
+"127.0.0.1. To bind to 0.0.0.0, set the\n"
+"router advanced configuration option "
+"i2cp.tcp.bindAllInterfaces=true and restart."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:482
+msgid "Whats an \"eepsite\"?"
+msgstr "Czym jest \"eepsite\"?"
+
+#: i2p2www/pages/site/faq.html:484
+msgid ""
+"An eepsite is a website that is hosted anonymously - you can access it by"
+"\n"
+"setting your web browser's HTTP proxy to use the web proxy (typically it\n"
+"listens on localhost port 4444), and browsing to the site."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:492
+#, python-format
+msgid ""
+"The proxy config for different browsers is on a \n"
+"separate page with screenshots. More advanced configs with external "
+"tools\n"
+"are possible but could introduce leaks in your setup."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:501
+msgid ""
+"x is the number of peers you've sent or received a message from\n"
+"successfully in the last minute, y is the number of peers seen in the "
+"last\n"
+"hour or so."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:509
+msgid ""
+"The SOCKS proxy is working as of release 0.7.1. SOCKS 4/4a/5 are "
+"supported.\n"
+"There is no SOCKS outproxy so it is of limited use."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:513
+msgid ""
+"In addition, many applications leak sensitive\n"
+"information that could identify you on the Internet. I2P only filters\n"
+"connection data, but if the program you intend to run sends this\n"
+"information as content, I2P has no way to protect your anonymity. For\n"
+"example, some mail applications will send the IP address of the machine\n"
+"they are running on to a mail server. There is no way for I2P to filter\n"
+"this, thus using I2P to 'socksify' existing applications is possible, but"
+"\n"
+"extremely dangerous."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:523
+#, python-format
+msgid ""
+"If you would like more information on the socks proxy application anyway,"
+"\n"
+"there are some helpful hints on the socks page."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:530
+msgid ""
+"Okay, here's a rundown of the default ports (everything is configurable\n"
+"through various settings, of course):"
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:539
+msgid ""
+"Internet-facing ports\n"
+"Note: New installs as of release 0.7.8 do not use port 8887; they select "
+"a random port\n"
+"between 9000 and 31000 when the program is run for the first time.\n"
+"The selected port is shown on the router configuration page."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:547
+msgid ""
+"Outbound UDP from the random port noted on the configuration page to "
+"arbitrary remote UDP ports, allowing replies\n"
+" "
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:552
+msgid ""
+"Outbound TCP from random high ports to arbitrary remote TCP ports\n"
+" "
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:557
+msgid ""
+"(optional, but recommended) Inbound UDP to the port noted on configuration page from "
+"arbitrary locations\n"
+" "
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:562
+msgid ""
+"(optional, but recommended) Inbound TCP to the port noted on configuration page from "
+"arbitrary locations
\n"
+"Inbound TCP may be disabled on the configuration page."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:568
+msgid ""
+"Outbound UDP on port 123, allowing replies
\n"
+"This is necessary for I2P's internal time sync (via SNTP - \n"
+"querying a random SNTP host in pool.ntp.org or another\n"
+"server you specify)"
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:579
+msgid ""
+"Local I2P ports, listening only to local connections by default,\n"
+"except where noted:"
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:585
+msgid ""
+"1900: UPnP SSDP UDP multicast listener.\n"
+"Cannot be changed. Binds to all interfaces.\n"
+"May be disabled on confignet.jsp."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:592
+msgid ""
+"2827: BOB bridge, a higher level socket API for clients\n"
+"Disabled by default.\n"
+"May be enabled/disabled on configclients.jsp.\n"
+"May be changed in the bob.config file."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:600
+msgid ""
+"4444: HTTP proxy\n"
+"May be disabled or changed on the i2ptunnel page in the router "
+"console.\n"
+"May also be configured to be bound to a specific interface or all "
+"interfaces."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:607
+msgid ""
+"4445: HTTPS proxy\n"
+"May be disabled or changed on the i2ptunnel page in the router "
+"console.\n"
+"May also be configured to be bound to a specific interface or all "
+"interfaces."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:614
+msgid ""
+"6668: IRC proxy\n"
+"May be disabled or changed on the i2ptunnel page in the router "
+"console.\n"
+"May also be configured to be bound to a specific interface or all "
+"interfaces."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:621
+msgid ""
+"7652: UPnP HTTP TCP event listener.\n"
+"Binds to the LAN address.\n"
+"May be changed with advanced config i2np.upnp.HTTPPort=nnnn.\n"
+"May be disabled on confignet.jsp."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:629
+msgid ""
+"7653: UPnP SSDP UDP search response listener.\n"
+"Binds to all interfaces.\n"
+"May be changed with advanced config i2np.upnp.SSDPPort=nnnn.\n"
+"May be disabled on confignet.jsp."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:637
+msgid ""
+"7654: I2P Client Protocol port, used by client apps.\n"
+"May be changed to a different port on\n"
+"configclients.jsp"
+"\n"
+"but this is not recommended.\n"
+"May be to bind to a different interface or all interfaces, or disabled, "
+"on\n"
+"configclients.jsp."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:647
+msgid ""
+"7655: UDP for SAM bridge, a higher level socket API for clients\n"
+"Only opened when a SAM V3 client requests a UDP session.\n"
+"May be enabled/disabled on configclients.jsp.\n"
+"May be changed in the clients.config file with the SAM command line "
+"option sam.udp.port=nnnn."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:655
+msgid ""
+"7656: SAM bridge, a higher level socket API for clients\n"
+"Disabled by default for new installs as of release 0.6.5.\n"
+"May be enabled/disabled on configclients.jsp.\n"
+"May be changed in the clients.config file."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:663
+msgid ""
+"7657: Your router console\n"
+"May be disabled in the clients.config file.\n"
+"May also be configured to be bound to a specific interface or all "
+"interfaces in that file."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:670
+msgid ""
+"7658: Your eepsite\n"
+"May be disabled in the clients.config file.\n"
+"May also be configured to be bound to a specific interface or all "
+"interfaces in the jetty.xml file."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:677
+msgid ""
+"7659: Outgoing mail to smtp.postman.i2p\n"
+"May be disabled or changed on the i2ptunnel page in the router "
+"console.\n"
+"May also be configured to be bound to a specific interface or all "
+"interfaces."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:684
+msgid ""
+"7660: Incoming mail from pop.postman.i2p\n"
+"May be disabled or changed on the i2ptunnel page in the router "
+"console.\n"
+"May also be configured to be bound to a specific interface or all "
+"interfaces."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:691
+msgid ""
+"8998: mtn.i2p2.i2p (Monotone - disabled by default)\n"
+"May be disabled or changed on the i2ptunnel page in the router "
+"console.\n"
+"May also be configured to be bound to a specific interface or all "
+"interfaces."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:698
+msgid ""
+"31000: Local connection to the wrapper control channel port.\n"
+"Outbound to 32000 only, does not listen on this port.\n"
+"Starts at 31000 and will increment until 31999 looking for a free port.\n"
+"To change, see the\n"
+"wrapper documentation.\n"
+"For more information see below."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:708
+msgid ""
+"32000: Local control channel for the service wrapper.\n"
+"To change, see the\n"
+"wrapper documentation.\n"
+"For more information see below."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:720
+msgid ""
+"The local I2P ports and the I2PTunnel ports do not need to be reachable "
+"from \n"
+"remote machines, but *should* be reachable locally. You can also create"
+" \n"
+"additional ports for I2PTunnel instances via "
+"http://localhost:7657/i2ptunnel/ \n"
+"(and in turn, would need to get your firewall to allow you local access, "
+"but \n"
+"not remote access, unless desired)."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:728
+msgid ""
+"So, to summarize, nothing needs to be reachable by unsolicited remote "
+"peers, but\n"
+"if you can configure your NAT/firewall to allow inbound UDP and TCP the "
+"outbound facing port, you'll"
+"\n"
+"get better performance. You will also need to be able to send outbound "
+"UDP packets\n"
+"to arbitrary remote peers (blocking IPs randomly with something like "
+"PeerGuardian\n"
+"only hurts you - don't do it)."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:736
+msgid "Why is I2P listening on port 32000?"
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:738
+msgid ""
+"The Tanuki java service wrapper that we use opens this port—bound "
+"to localhost—in order \n"
+"to communicate with software running inside the JVM. When the JVM is "
+"launched it is given a key \n"
+"so it can connect to the wrapper. After the JVM establishes its "
+"connection \n"
+"to the wrapper, the wrapper refuses any additional connections."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:744
+msgid ""
+"More information can be found in the \n"
+"wrapper documentation."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:751
+msgid ""
+"An I2P router only needs to be seeded once, to join the network for the "
+"first time.\n"
+"Reseeding is nothing more than sending plain HTTP GET requests\n"
+"to fetch a directory listing and download multiple \"routerInfo\" files\n"
+"from a predefined reseed URL."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:758
+msgid ""
+"A typical symptom of a failed reseed is the \"Known\" indicator\n"
+"(on the left sidebar of the router console) displaying a very small value"
+"\n"
+"(often less than 5) which does not increase. This can occur, among other "
+"things,\n"
+"if your firewall limits outbound traffic, and blocked the reseed request."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:765
+msgid "To reseed an I2P router manually, do the following:"
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:768
+msgid "Stop your I2P router"
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:771
+msgid ""
+"Open http://netdb.i2p2.de/ using a "
+"web browser"
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:774
+msgid "Save a dozen \"routerInfo\" files to your I2P \"netDb\" directory"
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:781
+msgid "Start your I2P router"
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:788
+msgid ""
+"When trying to start the router using \"i2prouter start\", you may see "
+"output like the following:"
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:793
+msgid ""
+"\n"
+"In order to be inclusive and try to ensure that I2P will run on as many "
+"systems \n"
+"as possible, up until I2P 0.8.9 we used a java wrapper \n"
+"compiled for FreeBSD 6.x. If you're receiving this error you most likely "
+"are missing the necessary compatibility libraries.\n"
+"These libraries may be installed by performing the following steps:"
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:801
+msgid ""
+"Switch to the root user with su or log in as "
+"root."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:807
+#, python-format
+msgid ""
+"If you cannot install these compatibility libraries (or do not want to), "
+"other\n"
+"possibilities would be to compile the wrapper for your\n"
+"system, starting I2P with the runplain.sh script, or you"
+" can\n"
+"replace the wrapper with one from the source tarball."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:813
+msgid ""
+"For the 0.8.9 release of I2P, the wrapper was upgraded to v3.5.12 and "
+"compiled on systems running FreeBSD 7.2."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:817
+msgid ""
+"In wrapper.log I see an error that states \"Protocol "
+"family unavailable\" when loading the Router Console"
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:819
+msgid ""
+"Often this error will occur with any network enabled java software on "
+"some systems that are configured to use IPv6 by default. There are a few "
+"ways to solve this:"
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:824
+msgid ""
+"On Linux based systems, you can echo 0 > "
+"/proc/sys/net/ipv6/bindv6only"
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:826
+msgid "Look for the following lines in wrapper.config."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:830
+msgid ""
+"If the lines are there, uncomment them by removing the \"#\"s. If the "
+"lines are not there, add them without the \"#\"s."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:833
+msgid ""
+"Another option would be to remove the ::1 from "
+"~/.i2p/clients.config"
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:837
+msgid ""
+"WARNING: For any changes to wrapper.config "
+"to take effect, you must completely\n"
+"stop the router and the wrapper. Clicking Restart on your\n"
+"router console will NOT reread this file! You must\n"
+"click Shutdown, wait 11 minutes, then start I2P."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:848
+#, python-format
+msgid ""
+"Great! Find us on IRC irc.freenode.net #i2p or post to\n"
+"the forum and we'll post it here (with\n"
+"the answer, hopefully)."
+msgstr ""
+
+#: i2p2www/pages/site/impressum.html:4
+msgid "German laws"
+msgstr "Niemieckie prawo"
+
+#: i2p2www/pages/site/index.html:2
+msgid "I2P Anonymous Network"
+msgstr ""
+
+#: i2p2www/pages/site/index.html:4
+msgid ""
+"Anonymous peer-to-peer distributed communication layer built with open "
+"source tools and designed to run any traditional Internet service such as"
+" email, IRC or web hosting."
+msgstr ""
+
+#: i2p2www/pages/site/index.html:7
+msgid "What does I2P do for you?"
+msgstr ""
+
+#: i2p2www/pages/site/index.html:8
+msgid ""
+"The I2P network provides strong privacy protections for communication "
+"over the Internet. Many activities that would risk your privacy on the "
+"public Internet can be conducted anonymously inside I2P."
+msgstr ""
+
+#: i2p2www/pages/site/index.html:9
+#, python-format
+msgid "Get I2P %(version)s"
+msgstr ""
+
+#: i2p2www/pages/site/index.html:13
+msgid "What is I2P?"
+msgstr "Czym jest I2P?"
+
+#: i2p2www/pages/site/index.html:15
+msgid ""
+"I2P is an anonymous overlay network - a network within a network. It is "
+"intended to protect communication from dragnet surveillance and "
+"monitoring by third parties such as ISPs.\n"
+msgstr ""
+
+#: i2p2www/pages/site/index.html:18
+msgid ""
+"I2P is used by many people who care about their privacy: activists, "
+"oppressed people, journalists and whistleblowers, as well as the average "
+"person.\n"
+msgstr ""
+
+#: i2p2www/pages/site/index.html:21
+msgid ""
+"No network can be \"perfectly anonymous\". The continued goal of I2P is "
+"to make attacks more and more difficult to mount. Its anonymity will get "
+"stronger as the size of the network increases and with ongoing academic "
+"review.\n"
+msgstr ""
+
+#: i2p2www/pages/site/index.html:24
+msgid ""
+"I2P is available on desktops, embedded systems (like the Raspberry Pi) "
+"and Android phones. Help spread the word!\n"
+msgstr ""
+
+#: i2p2www/pages/site/index.html:28
+msgid "Read more…"
+msgstr ""
+
+#: i2p2www/pages/site/index.html:33
+msgid "What can you do with I2P?"
+msgstr ""
+
+#: i2p2www/pages/site/index.html:36
+#, python-format
+msgid ""
+"Email: Integrated web mail interface,"
+" plugin for serverless email."
+msgstr ""
+
+#: i2p2www/pages/site/index.html:41
+#, python-format
+msgid ""
+"Web browsing: Anonymous "
+"websites, gateways to and from the public Internet."
+msgstr ""
+
+#: i2p2www/pages/site/index.html:46
+#, python-format
+msgid ""
+"Blogging and forums: "
+"Blogging and Syndie plugins."
+msgstr ""
+
+#: i2p2www/pages/site/index.html:51
+#, python-format
+msgid ""
+"Website hosting: Integrated"
+" anonymous web server."
+msgstr ""
+
+#: i2p2www/pages/site/index.html:56
+#, python-format
+msgid ""
+"Real-time chat: Instant "
+"messaging and IRC clients."
+msgstr ""
+
+#: i2p2www/pages/site/index.html:61
+#, python-format
+msgid ""
+"File sharing: ED2K and "
+"Gnutella clients, integrated BitTorrent client."
+msgstr ""
+
+#: i2p2www/pages/site/index.html:66
+#, python-format
+msgid ""
+"Decentralized file "
+"storage: Tahoe-LAFS distributed filesystem plugin."
+msgstr ""
+
+#: i2p2www/pages/site/index.html:71
+#, python-format
+msgid "More supported applications…"
+msgstr ""
+
+#: i2p2www/pages/site/index.html:79
+msgid "News & Updates"
+msgstr ""
+
+#: i2p2www/pages/site/links.html:4
+msgid "Recommended Links & Resources"
+msgstr ""
+
+#: i2p2www/pages/site/links.html:5
+#, python-format
+msgid ""
+"See also the page with\n"
+"links to presentations, videos, and tutorials about"
+" I2P."
+msgstr ""
+
+#: i2p2www/pages/site/links.html:12
+msgid "I2P on the web"
+msgstr "I2P w sieci"
+
+#: i2p2www/pages/site/links.html:20
+msgid "Friends of I2P"
+msgstr ""
+
+#: i2p2www/pages/site/links.html:32
+msgid "More Projects and Documentation"
+msgstr ""
+
+#: i2p2www/pages/site/links.html:42
+msgid "Press"
+msgstr "Prasa"
+
+#: i2p2www/pages/site/links.html:46
+msgid "Boards, newssite, others"
+msgstr ""
+
+#: i2p2www/pages/site/links.html:50
+msgid "Very Old Stuff"
+msgstr ""
+
diff --git a/i2p2www/translations/pt_BR/LC_MESSAGES/about.po b/i2p2www/translations/pt_BR/LC_MESSAGES/about.po
new file mode 100644
index 00000000..edcaf078
--- /dev/null
+++ b/i2p2www/translations/pt_BR/LC_MESSAGES/about.po
@@ -0,0 +1,2205 @@
+# Portuguese (Brazil) translations for I2P.
+# Copyright (C) 2013 ORGANIZATION
+# This file is distributed under the same license as the I2P project.
+#
+# Translators:
+# blueboy, 2013
+msgid ""
+msgstr ""
+"Project-Id-Version: I2P\n"
+"Report-Msgid-Bugs-To: http://trac.i2p2.de\n"
+"POT-Creation-Date: 2013-11-21 23:32+0000\n"
+"PO-Revision-Date: 2013-11-25 22:08+0000\n"
+"Last-Translator: blueboy\n"
+"Language-Team: Portuguese (Brazil) "
+"(http://www.transifex.com/projects/p/I2P/language/pt_BR/)\n"
+"Plural-Forms: nplurals=2; plural=(n > 1)\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=utf-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"Generated-By: Babel 0.9.6\n"
+
+#: i2p2www/pages/site/about/browser-config.html:2
+msgid "Web Browser Configuration"
+msgstr "Configuração do navegador web"
+
+#: i2p2www/pages/site/about/browser-config.html:5
+msgid ""
+"Your web browser will need to be configured in order to browse eepsites "
+"and to\n"
+"utilize the outproxies available within I2P. Below are walkthroughs for "
+"some of\n"
+"the most popular browsers."
+msgstr ""
+
+#: i2p2www/pages/site/about/browser-config.html:11
+msgid "How to configure your browser"
+msgstr "Como configurar o seu navegador"
+
+#: i2p2www/pages/site/about/browser-config.html:17
+#: i2p2www/pages/site/about/browser-config.html:73
+msgid "Outproxy Terms Of Service"
+msgstr "Termos de Serviço do proxy de saída"
+
+#: i2p2www/pages/site/about/browser-config.html:22
+msgid "Internet Explorer 8 or Chrome"
+msgstr "Internet Explorer 8 ou Chrome"
+
+#: i2p2www/pages/site/about/browser-config.html:23
+msgid ""
+"In the tools menu select the \"Internet Options\" line to open the "
+"settings. In the\n"
+"settings window choose the connections tab and click on LAN settings for "
+"the\n"
+"proxy port configuration."
+msgstr ""
+
+#: i2p2www/pages/site/about/browser-config.html:28
+msgid "IE Internet Options"
+msgstr "Opções de Internet do IE"
+
+#: i2p2www/pages/site/about/browser-config.html:29
+msgid ""
+"Now set the checkmark at \"use a proxy server for your LAN\" and at the "
+"\"Bypass\n"
+"proxy server for local addresses\". With a click on Advanced-button you "
+"open the\n"
+"window to open the ports. Enter the values like on the picture, IP "
+"127.0.0.1\n"
+"and port 4444 for HTTP, port 4445 for HTTPS. With clicks on OK you save "
+"the\n"
+"settings and your browser is set to use the I2P proxy."
+msgstr ""
+
+#: i2p2www/pages/site/about/browser-config.html:36
+msgid "IE Proxy Settings"
+msgstr "Especificações de proxy no IE"
+
+#: i2p2www/pages/site/about/browser-config.html:40
+msgid ""
+"From the Tools menu, select Options to bring up the Firefox settings "
+"panel.\n"
+"Click the icon labelled Advanced, then click on the "
+"Network\n"
+"tab. In the Connections section, click on the Settings button. "
+"You'll\n"
+"see a Window like the following:"
+msgstr ""
+
+#: i2p2www/pages/site/about/browser-config.html:46
+msgid "Firefox Network Options"
+msgstr "Opções de rede no Firefox"
+
+#: i2p2www/pages/site/about/browser-config.html:47
+msgid ""
+"In the Connection Settings window, click the circle next to "
+"Manual\n"
+" proxy configuration, then enter 127.0.0.1, port 4444 in the HTTP"
+" Proxy\n"
+"field. Enter 127.0.0.1, port 4445 in the SSL Proxy field.\n"
+"Be sure to enter localhost and 127.0.0.1 into the \"No Proxy for\" box."
+msgstr ""
+
+#: i2p2www/pages/site/about/browser-config.html:53
+msgid "Firefox Proxy Settings"
+msgstr "Especificações de proxy no Firefox"
+
+#: i2p2www/pages/site/about/browser-config.html:57
+msgid ""
+"From the Settings menu, select Configure Konqueror. In "
+"the\n"
+"Web Browsing group on the left side, select Proxy Services.\n"
+"In this new window, select the option \"Manually specify the proxy "
+"settings\" and\n"
+"click the Setup box."
+msgstr ""
+
+#: i2p2www/pages/site/about/browser-config.html:63
+msgid "Konqueror Proxy Options"
+msgstr "Opções de proxy no Konqueror"
+
+#: i2p2www/pages/site/about/browser-config.html:64
+msgid ""
+"Enter 127.0.0.1 and port 4444 into the HTTP box. Enter 127.0.0.1 and port"
+" 4445 into\n"
+"HTTPS box. Click the New button in the Exceptions section. Enter"
+"\n"
+"localhost and click OK. Click the New button once more and enter"
+"\n"
+"127.0.0.1 and OK. Hit OK once more to close the configuration window."
+msgstr ""
+
+#: i2p2www/pages/site/about/browser-config.html:70
+msgid "Konqueror Proxy Ports"
+msgstr ""
+
+#: i2p2www/pages/site/about/browser-config.html:74
+msgid ""
+"Remember: I2P was not designed for creating proxies to the outer "
+"Internet.\n"
+"Instead, it is meant to be used as an internal network."
+msgstr ""
+
+#: i2p2www/pages/site/about/browser-config.html:78
+msgid ""
+"The I2P project itself does not run any proxies to the Internet. Any "
+"such proxy\n"
+"services are run by by private volunteers and could be shut down or\n"
+"unreachable at anytime."
+msgstr ""
+
+#: i2p2www/pages/site/about/browser-config.html:83
+#, python-format
+msgid ""
+"By default, I2P comes with two outproxies configured: "
+"%(http)s\n"
+"(an HTTP-only proxy) and %(https)s (an HTTPS proxy\n"
+"routed through Tor."
+msgstr ""
+
+#: i2p2www/pages/site/about/browser-config.html:88
+msgid ""
+"Both of these outproxies are configured with connection limits. This "
+"means\n"
+"that only set amount of accesses are allowed per client. Once the limit "
+"is\n"
+"reached, the client is blocked out for a timeframe of 1min/1h/1 day. Be\n"
+"respectful and do not overload these services with too many requests!"
+msgstr ""
+
+#: i2p2www/pages/site/about/browser-config.html:94
+msgid ""
+"Filtering is active on these outproxies (for example, mibbit and torrent\n"
+"tracker access is blocked). Eepsites\n"
+"that are accessible via .i2p addresses are also not allowed via the "
+"outproxies.\n"
+"As a convenience, false.i2p blocks ad servers."
+msgstr ""
+
+#: i2p2www/pages/site/about/browser-config.html:100
+msgid ""
+"Tor is good application to use"
+" as an\n"
+"outproxy to the Internet."
+msgstr ""
+
+#: i2p2www/pages/site/about/glossary.html:2
+msgid "Glossary"
+msgstr "Glossário"
+
+#: i2p2www/pages/site/about/glossary.html:4
+msgid ""
+"This page lists often-used terminology when discussing I2P and "
+"cryptography."
+msgstr ""
+"Esta página lista os termos mais usados nas discussões sobre a I2P e "
+"criptografia."
+
+#: i2p2www/pages/site/about/hall-of-fame.html:2
+msgid "Hall Of Fame"
+msgstr "Salão da Fama"
+
+#: i2p2www/pages/site/about/hall-of-fame.html:5
+msgid "I2P's Hall of Fame"
+msgstr "Salão da Fama da I2P"
+
+#: i2p2www/pages/site/about/hall-of-fame.html:6
+#, python-format
+msgid "Current balance: as of %(date)s"
+msgstr ""
+
+#: i2p2www/pages/site/about/hall-of-fame.html:9
+#: i2p2www/pages/site/about/hall-of-fame.html:47
+#: i2p2www/pages/site/about/hall-of-fame.html:173
+#: i2p2www/pages/site/about/hall-of-fame.html:174
+#: i2p2www/pages/site/about/hall-of-fame.html:175
+#: i2p2www/pages/site/about/hall-of-fame.html:176
+#: i2p2www/pages/site/about/hall-of-fame.html:178
+#: i2p2www/pages/site/about/hall-of-fame.html:179
+#: i2p2www/pages/site/about/hall-of-fame.html:180
+#: i2p2www/pages/site/about/hall-of-fame.html:183
+#: i2p2www/pages/site/about/hall-of-fame.html:184
+#: i2p2www/pages/site/about/hall-of-fame.html:185
+#: i2p2www/pages/site/about/hall-of-fame.html:188
+#: i2p2www/pages/site/about/hall-of-fame.html:189
+#: i2p2www/pages/site/about/hall-of-fame.html:190
+#: i2p2www/pages/site/about/hall-of-fame.html:191
+#: i2p2www/pages/site/about/hall-of-fame.html:192
+#: i2p2www/pages/site/about/hall-of-fame.html:193
+#: i2p2www/pages/site/about/hall-of-fame.html:194
+#: i2p2www/pages/site/about/hall-of-fame.html:195
+#: i2p2www/pages/site/about/hall-of-fame.html:196
+#: i2p2www/pages/site/about/hall-of-fame.html:197
+#: i2p2www/pages/site/about/hall-of-fame.html:198
+#: i2p2www/pages/site/about/hall-of-fame.html:199
+#: i2p2www/pages/site/about/hall-of-fame.html:200
+#: i2p2www/pages/site/about/hall-of-fame.html:203
+#: i2p2www/pages/site/about/hall-of-fame.html:204
+#: i2p2www/pages/site/about/hall-of-fame.html:205
+#: i2p2www/pages/site/about/hall-of-fame.html:206
+#: i2p2www/pages/site/about/hall-of-fame.html:207
+#: i2p2www/pages/site/about/hall-of-fame.html:208
+#: i2p2www/pages/site/about/hall-of-fame.html:210
+#: i2p2www/pages/site/about/hall-of-fame.html:211
+#: i2p2www/pages/site/about/hall-of-fame.html:214
+#: i2p2www/pages/site/about/hall-of-fame.html:215
+#: i2p2www/pages/site/about/hall-of-fame.html:216
+#: i2p2www/pages/site/about/hall-of-fame.html:217
+#: i2p2www/pages/site/about/hall-of-fame.html:218
+#: i2p2www/pages/site/about/hall-of-fame.html:220
+#: i2p2www/pages/site/about/hall-of-fame.html:221
+#: i2p2www/pages/site/about/hall-of-fame.html:222
+#: i2p2www/pages/site/about/hall-of-fame.html:223
+#: i2p2www/pages/site/about/hall-of-fame.html:224
+#: i2p2www/pages/site/about/hall-of-fame.html:225
+#: i2p2www/pages/site/about/hall-of-fame.html:227
+#: i2p2www/pages/site/about/hall-of-fame.html:228
+#: i2p2www/pages/site/about/hall-of-fame.html:229
+#: i2p2www/pages/site/about/hall-of-fame.html:230
+#: i2p2www/pages/site/about/hall-of-fame.html:232
+#: i2p2www/pages/site/about/hall-of-fame.html:233
+#: i2p2www/pages/site/about/hall-of-fame.html:234
+#: i2p2www/pages/site/about/hall-of-fame.html:235
+#: i2p2www/pages/site/about/hall-of-fame.html:236
+#: i2p2www/pages/site/about/hall-of-fame.html:239
+#: i2p2www/pages/site/about/hall-of-fame.html:240
+#: i2p2www/pages/site/about/hall-of-fame.html:241
+#: i2p2www/pages/site/about/hall-of-fame.html:242
+#: i2p2www/pages/site/about/hall-of-fame.html:244
+#: i2p2www/pages/site/about/hall-of-fame.html:245
+#: i2p2www/pages/site/about/hall-of-fame.html:246
+#: i2p2www/pages/site/about/hall-of-fame.html:248
+#: i2p2www/pages/site/about/hall-of-fame.html:249
+#: i2p2www/pages/site/about/hall-of-fame.html:250
+#: i2p2www/pages/site/about/hall-of-fame.html:251
+#: i2p2www/pages/site/about/hall-of-fame.html:253
+#: i2p2www/pages/site/about/hall-of-fame.html:254
+#: i2p2www/pages/site/about/hall-of-fame.html:255
+#: i2p2www/pages/site/about/hall-of-fame.html:256
+#: i2p2www/pages/site/about/hall-of-fame.html:257
+#: i2p2www/pages/site/about/hall-of-fame.html:263
+#: i2p2www/pages/site/about/hall-of-fame.html:266
+#: i2p2www/pages/site/about/hall-of-fame.html:267
+#: i2p2www/pages/site/about/hall-of-fame.html:268
+#: i2p2www/pages/site/about/hall-of-fame.html:269
+#: i2p2www/pages/site/about/hall-of-fame.html:270
+#: i2p2www/pages/site/about/hall-of-fame.html:272
+#: i2p2www/pages/site/about/hall-of-fame.html:273
+#: i2p2www/pages/site/about/hall-of-fame.html:274
+#: i2p2www/pages/site/about/hall-of-fame.html:279
+#: i2p2www/pages/site/about/hall-of-fame.html:280
+#: i2p2www/pages/site/about/hall-of-fame.html:281
+#: i2p2www/pages/site/about/hall-of-fame.html:282
+#: i2p2www/pages/site/about/hall-of-fame.html:283
+#: i2p2www/pages/site/about/hall-of-fame.html:284
+#: i2p2www/pages/site/about/hall-of-fame.html:285
+#: i2p2www/pages/site/about/hall-of-fame.html:286
+#: i2p2www/pages/site/about/hall-of-fame.html:287
+#: i2p2www/pages/site/about/hall-of-fame.html:288
+#: i2p2www/pages/site/about/hall-of-fame.html:290
+#: i2p2www/pages/site/about/hall-of-fame.html:291
+#: i2p2www/pages/site/about/hall-of-fame.html:301
+#: i2p2www/pages/site/about/hall-of-fame.html:302
+#: i2p2www/pages/site/about/hall-of-fame.html:303
+#: i2p2www/pages/site/about/hall-of-fame.html:304
+#: i2p2www/pages/site/about/hall-of-fame.html:305
+#: i2p2www/pages/site/about/hall-of-fame.html:306
+#: i2p2www/pages/site/about/hall-of-fame.html:307
+#: i2p2www/pages/site/about/hall-of-fame.html:308
+#: i2p2www/pages/site/about/hall-of-fame.html:309
+#: i2p2www/pages/site/about/hall-of-fame.html:310
+#: i2p2www/pages/site/about/hall-of-fame.html:311
+#: i2p2www/pages/site/about/hall-of-fame.html:312
+#: i2p2www/pages/site/about/hall-of-fame.html:313
+#: i2p2www/pages/site/about/hall-of-fame.html:314
+#: i2p2www/pages/site/about/hall-of-fame.html:315
+#: i2p2www/pages/site/about/hall-of-fame.html:316
+#: i2p2www/pages/site/about/hall-of-fame.html:317
+#: i2p2www/pages/site/about/hall-of-fame.html:318
+#: i2p2www/pages/site/about/hall-of-fame.html:319
+#: i2p2www/pages/site/about/hall-of-fame.html:320
+#: i2p2www/pages/site/about/hall-of-fame.html:321
+#: i2p2www/pages/site/about/hall-of-fame.html:325
+#: i2p2www/pages/site/about/hall-of-fame.html:326
+#: i2p2www/pages/site/about/hall-of-fame.html:327
+#: i2p2www/pages/site/about/hall-of-fame.html:328
+#: i2p2www/pages/site/about/hall-of-fame.html:329
+#: i2p2www/pages/site/about/hall-of-fame.html:330
+#: i2p2www/pages/site/about/hall-of-fame.html:331
+#: i2p2www/pages/site/about/hall-of-fame.html:333
+#: i2p2www/pages/site/about/hall-of-fame.html:334
+#: i2p2www/pages/site/about/hall-of-fame.html:335
+#: i2p2www/pages/site/about/hall-of-fame.html:336
+#: i2p2www/pages/site/about/hall-of-fame.html:337
+#: i2p2www/pages/site/about/hall-of-fame.html:338
+#: i2p2www/pages/site/about/hall-of-fame.html:339
+#: i2p2www/pages/site/about/hall-of-fame.html:340
+#: i2p2www/pages/site/about/hall-of-fame.html:341
+#: i2p2www/pages/site/about/hall-of-fame.html:344
+#: i2p2www/pages/site/about/hall-of-fame.html:345
+#: i2p2www/pages/site/about/hall-of-fame.html:346
+#: i2p2www/pages/site/about/hall-of-fame.html:347
+#: i2p2www/pages/site/about/hall-of-fame.html:348
+#: i2p2www/pages/site/about/hall-of-fame.html:350
+#: i2p2www/pages/site/about/hall-of-fame.html:352
+#: i2p2www/pages/site/about/hall-of-fame.html:353
+#: i2p2www/pages/site/about/hall-of-fame.html:354
+#: i2p2www/pages/site/about/hall-of-fame.html:355
+#: i2p2www/pages/site/about/hall-of-fame.html:356
+#: i2p2www/pages/site/about/hall-of-fame.html:357
+#: i2p2www/pages/site/about/hall-of-fame.html:358
+#: i2p2www/pages/site/about/hall-of-fame.html:360
+#: i2p2www/pages/site/about/hall-of-fame.html:361
+#: i2p2www/pages/site/about/hall-of-fame.html:362
+#: i2p2www/pages/site/about/hall-of-fame.html:363
+#: i2p2www/pages/site/about/hall-of-fame.html:364
+#: i2p2www/pages/site/about/hall-of-fame.html:365
+#: i2p2www/pages/site/about/hall-of-fame.html:366
+#: i2p2www/pages/site/about/hall-of-fame.html:367
+#: i2p2www/pages/site/about/hall-of-fame.html:368
+#: i2p2www/pages/site/about/hall-of-fame.html:369
+#: i2p2www/pages/site/about/hall-of-fame.html:370
+#: i2p2www/pages/site/about/hall-of-fame.html:371
+#: i2p2www/pages/site/about/hall-of-fame.html:372
+#: i2p2www/pages/site/about/hall-of-fame.html:373
+#: i2p2www/pages/site/about/hall-of-fame.html:375
+#: i2p2www/pages/site/about/hall-of-fame.html:376
+#: i2p2www/pages/site/about/hall-of-fame.html:377
+#: i2p2www/pages/site/about/hall-of-fame.html:380
+#: i2p2www/pages/site/about/hall-of-fame.html:381
+#: i2p2www/pages/site/about/hall-of-fame.html:384
+#: i2p2www/pages/site/about/hall-of-fame.html:385
+#: i2p2www/pages/site/about/hall-of-fame.html:387
+#: i2p2www/pages/site/about/hall-of-fame.html:388
+#: i2p2www/pages/site/about/hall-of-fame.html:401
+#: i2p2www/pages/site/about/hall-of-fame.html:402
+#: i2p2www/pages/site/about/hall-of-fame.html:403
+#: i2p2www/pages/site/about/hall-of-fame.html:404
+#: i2p2www/pages/site/about/hall-of-fame.html:405
+#: i2p2www/pages/site/about/hall-of-fame.html:406
+#: i2p2www/pages/site/about/hall-of-fame.html:407
+#: i2p2www/pages/site/about/hall-of-fame.html:408
+#: i2p2www/pages/site/about/hall-of-fame.html:409
+#: i2p2www/pages/site/about/hall-of-fame.html:410
+#: i2p2www/pages/site/about/hall-of-fame.html:411
+#: i2p2www/pages/site/about/hall-of-fame.html:412
+#: i2p2www/pages/site/about/hall-of-fame.html:413
+#: i2p2www/pages/site/about/hall-of-fame.html:414
+#: i2p2www/pages/site/about/hall-of-fame.html:415
+#: i2p2www/pages/site/about/hall-of-fame.html:416
+#: i2p2www/pages/site/about/hall-of-fame.html:417
+#: i2p2www/pages/site/about/hall-of-fame.html:418
+#: i2p2www/pages/site/about/hall-of-fame.html:419
+#: i2p2www/pages/site/about/hall-of-fame.html:420
+#: i2p2www/pages/site/about/hall-of-fame.html:421
+#: i2p2www/pages/site/about/hall-of-fame.html:422
+#: i2p2www/pages/site/about/hall-of-fame.html:423
+#: i2p2www/pages/site/about/hall-of-fame.html:424
+#: i2p2www/pages/site/about/hall-of-fame.html:425
+#: i2p2www/pages/site/about/hall-of-fame.html:426
+#: i2p2www/pages/site/about/hall-of-fame.html:427
+#: i2p2www/pages/site/about/hall-of-fame.html:428
+#: i2p2www/pages/site/about/hall-of-fame.html:429
+#: i2p2www/pages/site/about/hall-of-fame.html:430
+#: i2p2www/pages/site/about/hall-of-fame.html:431
+#: i2p2www/pages/site/about/hall-of-fame.html:432
+#: i2p2www/pages/site/about/hall-of-fame.html:433
+#: i2p2www/pages/site/about/hall-of-fame.html:434
+#: i2p2www/pages/site/about/hall-of-fame.html:435
+#: i2p2www/pages/site/about/hall-of-fame.html:437
+#: i2p2www/pages/site/about/hall-of-fame.html:438
+#: i2p2www/pages/site/about/hall-of-fame.html:439
+#: i2p2www/pages/site/about/hall-of-fame.html:440
+#: i2p2www/pages/site/about/hall-of-fame.html:441
+#: i2p2www/pages/site/about/hall-of-fame.html:442
+#: i2p2www/pages/site/about/hall-of-fame.html:443
+#: i2p2www/pages/site/about/hall-of-fame.html:444
+#: i2p2www/pages/site/about/hall-of-fame.html:446
+#: i2p2www/pages/site/about/hall-of-fame.html:447
+#: i2p2www/pages/site/about/hall-of-fame.html:448
+#: i2p2www/pages/site/about/hall-of-fame.html:450
+#: i2p2www/pages/site/about/hall-of-fame.html:451
+#: i2p2www/pages/site/about/hall-of-fame.html:452
+#: i2p2www/pages/site/about/hall-of-fame.html:453
+#: i2p2www/pages/site/about/hall-of-fame.html:454
+#: i2p2www/pages/site/about/hall-of-fame.html:456
+#: i2p2www/pages/site/about/hall-of-fame.html:459
+#: i2p2www/pages/site/about/hall-of-fame.html:460
+#: i2p2www/pages/site/about/hall-of-fame.html:461
+#: i2p2www/pages/site/about/hall-of-fame.html:462
+#: i2p2www/pages/site/about/hall-of-fame.html:463
+#: i2p2www/pages/site/about/hall-of-fame.html:464
+#: i2p2www/pages/site/about/hall-of-fame.html:465
+#: i2p2www/pages/site/about/hall-of-fame.html:466
+#: i2p2www/pages/site/about/hall-of-fame.html:467
+#: i2p2www/pages/site/about/hall-of-fame.html:468
+#: i2p2www/pages/site/about/hall-of-fame.html:469
+#: i2p2www/pages/site/about/hall-of-fame.html:470
+#: i2p2www/pages/site/about/hall-of-fame.html:471
+#: i2p2www/pages/site/about/hall-of-fame.html:472
+#: i2p2www/pages/site/about/hall-of-fame.html:474
+#: i2p2www/pages/site/about/hall-of-fame.html:475
+#: i2p2www/pages/site/about/hall-of-fame.html:476
+#: i2p2www/pages/site/about/hall-of-fame.html:478
+#: i2p2www/pages/site/about/hall-of-fame.html:481
+#: i2p2www/pages/site/about/hall-of-fame.html:482
+#: i2p2www/pages/site/about/hall-of-fame.html:483
+#: i2p2www/pages/site/about/hall-of-fame.html:484
+#: i2p2www/pages/site/about/hall-of-fame.html:485
+#: i2p2www/pages/site/about/hall-of-fame.html:486
+#: i2p2www/pages/site/about/hall-of-fame.html:487
+#: i2p2www/pages/site/about/hall-of-fame.html:488
+#: i2p2www/pages/site/about/hall-of-fame.html:489
+#: i2p2www/pages/site/about/hall-of-fame.html:490
+#: i2p2www/pages/site/about/hall-of-fame.html:491
+#: i2p2www/pages/site/about/hall-of-fame.html:492
+#: i2p2www/pages/site/about/hall-of-fame.html:493
+#: i2p2www/pages/site/about/hall-of-fame.html:494
+#: i2p2www/pages/site/about/hall-of-fame.html:495
+#: i2p2www/pages/site/about/hall-of-fame.html:496
+#: i2p2www/pages/site/about/hall-of-fame.html:497
+#: i2p2www/pages/site/about/hall-of-fame.html:498
+#: i2p2www/pages/site/about/hall-of-fame.html:499
+#: i2p2www/pages/site/about/hall-of-fame.html:501
+#: i2p2www/pages/site/about/hall-of-fame.html:502
+#: i2p2www/pages/site/about/hall-of-fame.html:503
+msgid "General fund"
+msgstr ""
+
+#: i2p2www/pages/site/about/hall-of-fame.html:10
+#: i2p2www/pages/site/about/hall-of-fame.html:12
+#: i2p2www/pages/site/about/hall-of-fame.html:14
+#: i2p2www/pages/site/about/hall-of-fame.html:20
+#, python-format
+msgid "%(euroval)s € and %(btcval)s BTC"
+msgstr ""
+
+#: i2p2www/pages/site/about/hall-of-fame.html:11
+msgid "Datastorage bounty"
+msgstr ""
+
+#: i2p2www/pages/site/about/hall-of-fame.html:13
+msgid "Native IPv6 I2P"
+msgstr ""
+
+#: i2p2www/pages/site/about/hall-of-fame.html:15
+msgid "I2PHex bounty"
+msgstr ""
+
+#: i2p2www/pages/site/about/hall-of-fame.html:16
+#: i2p2www/pages/site/about/hall-of-fame.html:18
+#: i2p2www/pages/site/about/hall-of-fame.html:22
+#, python-format
+msgid "%(euroval)s €"
+msgstr ""
+
+#: i2p2www/pages/site/about/hall-of-fame.html:17
+msgid "I2P in debian mirrors"
+msgstr "I2P nos espelhos do Debian"
+
+#: i2p2www/pages/site/about/hall-of-fame.html:19
+msgid "Bitcoin client for I2P"
+msgstr "Cliente Bitcoin para a I2P"
+
+#: i2p2www/pages/site/about/hall-of-fame.html:21
+msgid "Unit Tests for I2P router"
+msgstr ""
+
+#: i2p2www/pages/site/about/hall-of-fame.html:23
+msgid "Bounty Robert"
+msgstr ""
+
+#: i2p2www/pages/site/about/hall-of-fame.html:24
+msgid "Bounty Syndie"
+msgstr ""
+
+#: i2p2www/pages/site/about/hall-of-fame.html:25
+msgid "Bounty I2P for CCR Microtic Board"
+msgstr ""
+
+#: i2p2www/pages/site/about/hall-of-fame.html:28
+msgid "Current monthly running costs:"
+msgstr ""
+
+#: i2p2www/pages/site/about/hall-of-fame.html:39
+msgid "Big thanks go to the following people who have donated to I2P!"
+msgstr ""
+
+#: i2p2www/pages/site/about/hall-of-fame.html:40
+#, python-format
+msgid ""
+"If you have made a donation, please send an email to echelon\n"
+"with your name or nick (and optionally homepage) so we can list you here."
+msgstr ""
+
+#: i2p2www/pages/site/about/hall-of-fame.html:45
+msgid "Current monthly subscriptions:"
+msgstr ""
+
+#: i2p2www/pages/site/about/hall-of-fame.html:51
+msgid "2013 donations and costs:"
+msgstr "Custos e doações em 2013:"
+
+#: i2p2www/pages/site/about/hall-of-fame.html:170
+msgid "2012 donations and costs:"
+msgstr "Custos e doações em 2012:"
+
+#: i2p2www/pages/site/about/hall-of-fame.html:298
+msgid "2011 donations and costs:"
+msgstr "Custos e doações em 2011:"
+
+#: i2p2www/pages/site/about/hall-of-fame.html:399
+msgid "Previous to 2011 donations:"
+msgstr ""
+
+#: i2p2www/pages/site/about/intro.html:2
+msgid "Intro"
+msgstr "Introdução"
+
+#: i2p2www/pages/site/about/intro.html:4
+msgid "The Invisible Internet Project"
+msgstr "O Projeto Internet Invisível"
+
+#: i2p2www/pages/site/about/intro.html:5
+msgid ""
+"I2P is an anonymous network, exposing a simple layer that applications "
+"can \n"
+"use to anonymously and securely send messages to each other. The network "
+"itself is \n"
+"strictly message based (a la \n"
+"IP), but "
+"there is a \n"
+"library available to allow reliable streaming communication on top of it "
+"(a la \n"
+"TCP)."
+" \n"
+"All communication is end to end encrypted (in total there are four layers"
+" of \n"
+"encryption used when sending a message), and even the end points "
+"(\"destinations\") \n"
+"are cryptographic identifiers (essentially a pair of public "
+"keys)."
+msgstr ""
+
+#: i2p2www/pages/site/about/intro.html:17
+msgid "How does it work?"
+msgstr "Como funciona?"
+
+#: i2p2www/pages/site/about/intro.html:19
+#, python-format
+msgid ""
+"To anonymize the messages sent, each client application has their I2P "
+"\"router\"\n"
+"build a few inbound and outbound \"tunnels\" - a \n"
+"sequence of peers that pass messages in one direction (to and from the "
+"client, \n"
+"respectively). In turn, when a client wants to send a message to another"
+" client, \n"
+"the client passes that message out one of their outbound tunnels "
+"targeting one of the \n"
+"other client's inbound tunnels, eventually reaching the destination. "
+"Every \n"
+"participant in the network chooses the length of these tunnels, and in "
+"doing so, \n"
+"makes a tradeoff between anonymity, latency, and throughput according to "
+"their \n"
+"own needs. The result is that the number of peers relaying each end to "
+"end \n"
+"message is the absolute minimum necessary to meet both the sender's and "
+"the \n"
+"receiver's threat model."
+msgstr ""
+
+#: i2p2www/pages/site/about/intro.html:33
+#, python-format
+msgid ""
+"The first time a client wants to contact another client, they make a "
+"query \n"
+"against the fully distributed \"network \n"
+"database\" - a custom structured \n"
+"distributed hash table (DHT) based off the \n"
+" Kademlia "
+"algorithm. This is done \n"
+"to find the other client's inbound tunnels efficiently, but subsequent "
+"messages \n"
+"between them usually includes that data so no further network database "
+"lookups \n"
+"are required."
+msgstr ""
+
+#: i2p2www/pages/site/about/intro.html:44
+#, python-format
+msgid "More details about how I2P works are available."
+msgstr ""
+
+#: i2p2www/pages/site/about/intro.html:48
+msgid "What can you do with it?"
+msgstr ""
+
+#: i2p2www/pages/site/about/intro.html:50
+#, python-format
+msgid ""
+"Within the I2P network, applications are not restricted in how they can \n"
+"communicate - those that typically use UDP can make use of the base I2P \n"
+"functionality, and those that typically use TCP can use the TCP-like "
+"streaming\n"
+"library. We have a generic TCP/I2P bridge application \n"
+"(\"I2PTunnel\") that enables people to "
+"forward TCP streams\n"
+"into the I2P network as well as to receive streams out of the network and"
+" \n"
+"forward them towards a specific TCP/IP address."
+msgstr ""
+
+#: i2p2www/pages/site/about/intro.html:60
+msgid ""
+"I2PTunnel is currently used to let people run their own anonymous website"
+" \n"
+"(\"eepsite\") by running a normal webserver and pointing an I2PTunnel "
+"'server' \n"
+"at it, which people can access anonymously over I2P with a normal web "
+"browser \n"
+"by running an I2PTunnel HTTP proxy (\"eepproxy\"). In addition, we use "
+"the same \n"
+"technique to run an anonymous IRC network (where the IRC server is hosted"
+" \n"
+"anonymously, and standard IRC clients use an I2PTunnel to contact it). "
+"There \n"
+"are other application development efforts going on as well, such as one "
+"to \n"
+"build an optimized swarming file transfer application (a la \n"
+"BitTorrent), a \n"
+"distributed data store (a la Freenet / \n"
+"MNet), and a blogging system (a "
+"fully \n"
+"distributed LiveJournal), but"
+" those are \n"
+"not ready for use yet."
+msgstr ""
+
+#: i2p2www/pages/site/about/intro.html:76
+msgid ""
+"I2P is not inherently an \"outproxy\" network - the client you send a "
+"message \n"
+"to is the cryptographic identifier, not some IP address, so the message "
+"must \n"
+"be addressed to someone running I2P. However, it is possible for that "
+"client\n"
+"to be an outproxy, allowing you to anonymously make use of their Internet"
+" \n"
+"connection. To demonstrate this, the \"eepproxy\" will accept normal "
+"non-I2P \n"
+"URLs (e.g. \"http://www.i2p.net\") and forward them to a specific "
+"destination\n"
+"that runs a squid HTTP proxy,"
+" allowing \n"
+"simple anonymous browsing of the normal web. Simple outproxies like that"
+" are \n"
+"not viable in the long run for several reasons (including the cost of "
+"running \n"
+"one as well as the anonymity and security issues they introduce), but in"
+" \n"
+"certain circumstances the technique could be appropriate."
+msgstr ""
+
+#: i2p2www/pages/site/about/intro.html:90
+#, python-format
+msgid ""
+"The I2P development team is an open group, "
+"welcome to all \n"
+"who are interested in getting involved, and"
+" all of \n"
+"the code is open source. The core I2P SDK "
+"and the \n"
+"current router implementation is done in Java (currently working with "
+"both \n"
+"sun and kaffe, gcj support planned for later), and there is a \n"
+"simple socket based API for accessing the network"
+" from \n"
+"other languages (with a C library available, and both Python and Perl in"
+" \n"
+"development). The network is actively being developed and has not yet "
+"reached \n"
+"the 1.0 release, but the current roadmap "
+"describes \n"
+"our schedule."
+msgstr ""
+
+#: i2p2www/pages/site/about/media.html:2 i2p2www/pages/site/about/media.html:4
+msgid "Presentations on I2P"
+msgstr "Exposições sobre a I2P"
+
+#: i2p2www/pages/site/about/media.html:5
+#, python-format
+msgid ""
+"Following are links to presentations, videos, and tutorials about I2P. "
+"Links to research papers on I2P are available here."
+msgstr ""
+
+#: i2p2www/pages/site/about/media.html:8
+#, python-format
+msgid "To request an addition to this page, please send to %(email)s."
+msgstr ""
+
+#: i2p2www/pages/site/about/media.html:11
+msgid ""
+"\n"
+"Newest links are at the bottom of each section."
+msgstr ""
+"\n"
+"Os linques mais recentes encontram-se relacionados na parte inferior de "
+"cada seção."
+
+#: i2p2www/pages/site/about/media.html:16
+msgid "Presentations"
+msgstr "Exposições"
+
+#: i2p2www/pages/site/about/media.html:19
+#, python-format
+msgid ""
+"IIP Presentation at CodeCon\n"
+"MP3 audio\n"
+"transcript\n"
+"Lance James (0x90), February 2002."
+msgstr ""
+
+#: i2p2www/pages/site/about/media.html:27
+#, python-format
+msgid ""
+"IIP Presentation at ToorCon\n"
+"MP3 audio\n"
+"slides\n"
+"Lance James (0x90), September 2002."
+msgstr ""
+
+#: i2p2www/pages/site/about/media.html:35
+#, python-format
+msgid ""
+"To Be or I2P\n"
+"(Youtube Video)\n"
+"An introduction into anonymous communication with I2P.\n"
+"To Be or I2P (PDF presentation),\n"
+"Jens Kubieziel, 24C3 Berlin, December 28, 2007."
+msgstr ""
+
+#: i2p2www/pages/site/about/media.html:44
+#, python-format
+msgid ""
+"Video of I2P talk at Chemnitz Linux Tag,\n"
+"Lars Schimmer,\n"
+"March 14-15, 2009"
+msgstr ""
+
+#: i2p2www/pages/site/about/media.html:50
+#, python-format
+msgid ""
+"HOPE New York July 17, 2010 - Brief overview of I2P by zzz, at the end of"
+" Adrian Hong's talk\n"
+"\"Hackers for Human Rights\".\n"
+"MP3 audio"
+msgstr ""
+
+#: i2p2www/pages/site/about/media.html:56
+#, python-format
+msgid ""
+"Into the I2P Darknet: Welcome to Cipherspace\n"
+"Adrian Crenshaw. Schmoocon Firetalk, January 2011"
+msgstr ""
+
+#: i2p2www/pages/site/about/media.html:61
+#, python-format
+msgid ""
+"Using techhnology to advance liberty\n"
+"(Youtube Video)\n"
+"Eric Johnson.\n"
+"Agora I/O Unconference, March 27,"
+" 2011.\n"
+"I2P covered from 10:00 to 20:00 in the video."
+msgstr ""
+
+#: i2p2www/pages/site/about/media.html:69
+#, python-format
+msgid ""
+"The Bright side of darknets, FOSSCOMM Patras May "
+"2011"
+msgstr ""
+
+#: i2p2www/pages/site/about/media.html:73
+#, python-format
+msgid ""
+"Common Darknet Weaknesses\n"
+"(Youtube Video)\n"
+"Adrian Crenshaw, AIDE, July "
+"11-15, 2011."
+msgstr ""
+
+#: i2p2www/pages/site/about/media.html:79
+#, python-format
+msgid ""
+"I2P / Tor Workshop Notes\n"
+"Adrian Crenshaw. DEF CON 19, Las Vegas, August 6, 2011."
+msgstr ""
+
+#: i2p2www/pages/site/about/media.html:84
+#, python-format
+msgid ""
+"Cipherspaces/Darknets: An Overview Of Attack "
+"Strategies -\n"
+"DEF CON Live version (Youtube Video),\n"
+"\"Studio\" version (Youtube Video),\n"
+"Slides (ppt)\n"
+"Adrian Crenshaw. DEF CON 19, Las Vegas, August 7, 2011."
+msgstr ""
+
+#: i2p2www/pages/site/about/media.html:94
+msgid ""
+"Modern cipherspace ecosystems, 0x375 "
+"0x06 4/11/2011"
+msgstr ""
+
+#: i2p2www/pages/site/about/media.html:100
+msgid "Tutorials"
+msgstr "Tutoriais"
+
+#: i2p2www/pages/site/about/media.html:103
+#, python-format
+msgid ""
+"I2P Windows Tutorial\n"
+"(Youtube Video)\n"
+"This guide will show you how to install I2P in Windows XP.\n"
+"By Telecomix"
+msgstr ""
+
+#: i2p2www/pages/site/about/media.html:111
+#, python-format
+msgid ""
+"I2P Debian Tutorial\n"
+"(Youtube Video)\n"
+"This will guide you through how to install I2P on a Debian Linux System.\n"
+"By Telecomix"
+msgstr ""
+
+#: i2p2www/pages/site/about/media.html:119
+#, python-format
+msgid ""
+"How to set up anonymous site in I2P\n"
+"(Youtube Video)\n"
+"How to set up an anonymous web site in I2P.\n"
+"By Telecomix"
+msgstr ""
+
+#: i2p2www/pages/site/about/media.html:126
+#, python-format
+msgid ""
+"I2P Tutorial Mac OS X\n"
+"(Youtube Video)\n"
+"A tutorial on how to run i2p on Mac OS X and how to connect to "
+"irc.telecomix.i2p.\n"
+"By Telecomix"
+msgstr ""
+
+#: i2p2www/pages/site/about/media.html:133
+#, python-format
+msgid ""
+"Felix Atari explains the basic principles of I2P"
+"\n"
+"(Youtube Video)\n"
+"Agent Felix Atari of the Telecomix Crypto Munitions Bureau.\n"
+"By Telecomix"
+msgstr ""
+
+#: i2p2www/pages/site/about/media.html:140
+#, python-format
+msgid ""
+"How to get onto I2P, the anonymous P2P Darknet "
+"(Windows Install)\n"
+"(Youtube Video)\n"
+"This tutorial shows how to install and configure software needed to "
+"access I2P."
+msgstr ""
+
+#: i2p2www/pages/site/about/media.html:146
+#, python-format
+msgid ""
+"How to connect to I2P\n"
+"(Youtube Video)\n"
+"How to install I2P on Ubuntu."
+msgstr ""
+
+#: i2p2www/pages/site/about/media.html:152
+#, python-format
+msgid ""
+"Installing the I2P darknet software in Linux\n"
+"(Video)\n"
+"Adrian Crenshaw.\n"
+"January 2011"
+msgstr ""
+
+#: i2p2www/pages/site/about/media.html:159
+#, python-format
+msgid ""
+"Short garlic routing animation\n"
+"(Youtube Video)\n"
+"Adrian Crenshaw.\n"
+msgstr ""
+
+#: i2p2www/pages/site/about/media.html:167
+msgid "Articles and Interviews"
+msgstr "Artigos e Entrevistas"
+
+#: i2p2www/pages/site/about/media.html:170
+#, python-format
+msgid ""
+"0x90 Interviewed by DistributedCity\n"
+"Part 1\n"
+"Part 2\n"
+"July 26, 2002."
+msgstr ""
+
+#: i2p2www/pages/site/about/media.html:178
+#, python-format
+msgid ""
+"0x90 Interviewed by El Pais\n"
+"(original in Spanish)\n"
+"English translation\n"
+"October 31, 2002."
+msgstr ""
+
+#: i2p2www/pages/site/about/media.html:185
+#, python-format
+msgid ""
+"2003 Business Week article referencing "
+"invisiblenet"
+msgstr ""
+
+#: i2p2www/pages/site/about/media.html:189
+#, python-format
+msgid ""
+"Netzwelt.de article about being anonymous in the "
+"Internet\n"
+"(German)\n"
+"November 2007."
+msgstr ""
+
+#: i2p2www/pages/site/about/media.html:195
+#, python-format
+msgid ""
+"zzz interviewed by gulli.com\n"
+"March 2009\n"
+"German translation"
+msgstr ""
+
+#: i2p2www/pages/site/about/media.html:202
+#, python-format
+msgid ""
+"zzz interviewed on the InfoSec Daily Podcast Ep. 454 "
+"(mp3)\n"
+"August 18, 2011"
+msgstr ""
+
+#: i2p2www/pages/site/about/media.html:207
+#, python-format
+msgid ""
+"I2P - Anonymity for the Masses,\n"
+"Jonathan Cox,\n"
+"November 11, 2011."
+msgstr ""
+
+#: i2p2www/pages/site/about/media.html:213
+#, python-format
+msgid ""
+"zzz and Lance James interviewed on the InfoSec Daily "
+"Podcast Ep. 596 (mp3)\n"
+"February 16, 2012"
+msgstr ""
+
+#: i2p2www/pages/site/about/team.html:2
+msgid "Team"
+msgstr "Time"
+
+#: i2p2www/pages/site/about/team.html:4
+msgid "I2P Project Members"
+msgstr "Membros do Projeto I2P"
+
+#: i2p2www/pages/site/about/team.html:5
+#, python-format
+msgid ""
+"We are a small group of people spread around several continents, working "
+"to\n"
+"advance different aspects of the project and discussing the design of the"
+"\n"
+"network.\n"
+"Get involved!"
+msgstr ""
+
+#: i2p2www/pages/site/about/team.html:14
+msgid "Admin"
+msgstr ""
+
+#: i2p2www/pages/site/about/team.html:15
+msgid "Project Manager"
+msgstr "Gerente do Projeto"
+
+#: i2p2www/pages/site/about/team.html:17
+msgid "point of contact of last resort"
+msgstr ""
+
+#: i2p2www/pages/site/about/team.html:20
+msgid "Treasurer"
+msgstr "Tesoureiro"
+
+#: i2p2www/pages/site/about/team.html:22
+msgid "manage donations / accounts / bounties"
+msgstr ""
+
+#: i2p2www/pages/site/about/team.html:25
+msgid "PR manager"
+msgstr ""
+
+#: i2p2www/pages/site/about/team.html:27
+msgid "press contact, manages public relations and affairs"
+msgstr ""
+
+#: i2p2www/pages/site/about/team.html:30
+#, python-format
+msgid "Forum admin"
+msgstr ""
+
+#: i2p2www/pages/site/about/team.html:32
+msgid "manage the public user forum"
+msgstr "modera o fórum público de usuários"
+
+#: i2p2www/pages/site/about/team.html:35
+msgid "Mirrors admin"
+msgstr ""
+
+#: i2p2www/pages/site/about/team.html:37
+msgid "manage the project mirrors"
+msgstr ""
+
+#: i2p2www/pages/site/about/team.html:40
+#, python-format
+msgid "Monotone guru"
+msgstr ""
+
+#: i2p2www/pages/site/about/team.html:42
+msgid "manage the public monotone repositories"
+msgstr ""
+
+#: i2p2www/pages/site/about/team.html:45
+msgid "Packager; Linux"
+msgstr ""
+
+#: i2p2www/pages/site/about/team.html:47
+msgid "Linux (Debian/Ubuntu) distribution packager"
+msgstr ""
+
+#: i2p2www/pages/site/about/team.html:50
+msgid "Packager; Windows"
+msgstr ""
+
+#: i2p2www/pages/site/about/team.html:52
+msgid "Windows installer packager"
+msgstr ""
+
+#: i2p2www/pages/site/about/team.html:55
+msgid "Release Manager"
+msgstr "Reponsável pelas comunicações de lançamento"
+
+#: i2p2www/pages/site/about/team.html:57
+msgid "Builds and signs the releases"
+msgstr "Escreve e assina os comunicados de lançamento"
+
+#: i2p2www/pages/site/about/team.html:60
+msgid "Update admin"
+msgstr ""
+
+#: i2p2www/pages/site/about/team.html:62
+msgid "Monitors and recruits in-network update hosts"
+msgstr ""
+
+#: i2p2www/pages/site/about/team.html:65
+msgid "Reseed admin"
+msgstr ""
+
+#: i2p2www/pages/site/about/team.html:67
+msgid "Monitors, advises and recruits reseed hosts"
+msgstr ""
+
+#: i2p2www/pages/site/about/team.html:70
+msgid "Security expert"
+msgstr "Especialista em segurança"
+
+#: i2p2www/pages/site/about/team.html:71 i2p2www/pages/site/about/team.html:86
+#: i2p2www/pages/site/about/team.html:91 i2p2www/pages/site/about/team.html:111
+#: i2p2www/pages/site/about/team.html:148
+#: i2p2www/pages/site/about/team.html:158
+#: i2p2www/pages/site/about/team.html:163
+#: i2p2www/pages/site/about/team.html:168
+#: i2p2www/pages/site/about/team.html:173
+#: i2p2www/pages/site/about/team.html:178
+#: i2p2www/pages/site/about/team.html:211
+msgid "vacant"
+msgstr ""
+
+#: i2p2www/pages/site/about/team.html:72
+msgid "threat model / crypto expert"
+msgstr ""
+
+#: i2p2www/pages/site/about/team.html:77
+msgid "Manage the project bug tracker"
+msgstr ""
+
+#: i2p2www/pages/site/about/team.html:80
+msgid "Translation admins"
+msgstr ""
+
+#: i2p2www/pages/site/about/team.html:85
+msgid "User Advocate"
+msgstr ""
+
+#: i2p2www/pages/site/about/team.html:87
+msgid "gather, prioritize, advocate for user needs"
+msgstr ""
+
+#: i2p2www/pages/site/about/team.html:90
+msgid "Web Designer"
+msgstr ""
+
+#: i2p2www/pages/site/about/team.html:92
+msgid "manage the public project website content design"
+msgstr ""
+
+#: i2p2www/pages/site/about/team.html:95
+#, python-format
+msgid "Webserver admin"
+msgstr ""
+
+#: i2p2www/pages/site/about/team.html:97
+msgid "manage the public project webservers"
+msgstr ""
+
+#: i2p2www/pages/site/about/team.html:100
+#, python-format
+msgid "Website admin"
+msgstr ""
+
+#: i2p2www/pages/site/about/team.html:102
+msgid "manage the public project website content"
+msgstr ""
+
+#: i2p2www/pages/site/about/team.html:105
+msgid "News Admin"
+msgstr ""
+
+#: i2p2www/pages/site/about/team.html:107
+msgid "manage router console news feed"
+msgstr ""
+
+#: i2p2www/pages/site/about/team.html:110
+msgid "Director of passion"
+msgstr ""
+
+#: i2p2www/pages/site/about/team.html:112
+msgid "community motivator"
+msgstr ""
+
+#: i2p2www/pages/site/about/team.html:116
+msgid "Dev"
+msgstr ""
+
+#: i2p2www/pages/site/about/team.html:117
+msgid "Core Lead"
+msgstr ""
+
+#: i2p2www/pages/site/about/team.html:119
+msgid "lead dev for the SDK and router"
+msgstr ""
+
+#: i2p2www/pages/site/about/team.html:122
+#, python-format
+msgid "I2P mail lead"
+msgstr ""
+
+#: i2p2www/pages/site/about/team.html:124
+msgid "organize and develop the i2p mail system"
+msgstr ""
+
+#: i2p2www/pages/site/about/team.html:127
+#, python-format
+msgid "I2Host lead"
+msgstr ""
+
+#: i2p2www/pages/site/about/team.html:129
+msgid "I2Host addressbook application"
+msgstr ""
+
+#: i2p2www/pages/site/about/team.html:132
+#, python-format
+msgid "BOB lead"
+msgstr ""
+
+#: i2p2www/pages/site/about/team.html:134
+msgid "Basic Open Bridge"
+msgstr ""
+
+#: i2p2www/pages/site/about/team.html:137
+#, python-format
+msgid "I2P-Bote lead"
+msgstr ""
+
+#: i2p2www/pages/site/about/team.html:139
+msgid "I2PBote plugin"
+msgstr ""
+
+#: i2p2www/pages/site/about/team.html:142
+#, python-format
+msgid "Robert lead"
+msgstr ""
+
+#: i2p2www/pages/site/about/team.html:144
+msgid "Robert BitTorrent client"
+msgstr ""
+
+#: i2p2www/pages/site/about/team.html:147
+#, python-format
+msgid "I2Phex lead"
+msgstr ""
+
+#: i2p2www/pages/site/about/team.html:149
+msgid "I2Phex Gnutella client"
+msgstr "Cliente Gnutella I2Phex"
+
+#: i2p2www/pages/site/about/team.html:152
+#, python-format
+msgid "I2PSnark lead"
+msgstr ""
+
+#: i2p2www/pages/site/about/team.html:154
+msgid "Maintains the integrated Bittorrent client"
+msgstr ""
+
+#: i2p2www/pages/site/about/team.html:157
+#, python-format
+msgid "iMule lead"
+msgstr ""
+
+#: i2p2www/pages/site/about/team.html:159
+msgid "eMule client over I2P"
+msgstr "Cliente eMule sobre a I2P"
+
+#: i2p2www/pages/site/about/team.html:162
+#, python-format
+msgid "Syndie lead"
+msgstr ""
+
+#: i2p2www/pages/site/about/team.html:164
+msgid "Syndie development"
+msgstr ""
+
+#: i2p2www/pages/site/about/team.html:167
+msgid "Susimail lead"
+msgstr ""
+
+#: i2p2www/pages/site/about/team.html:169
+msgid "Susimail development"
+msgstr "Desenvolvimento do Susimail"
+
+#: i2p2www/pages/site/about/team.html:172
+msgid "Console"
+msgstr "Painel"
+
+#: i2p2www/pages/site/about/team.html:174
+msgid "Router console HTML/CSS design"
+msgstr ""
+
+#: i2p2www/pages/site/about/team.html:177
+msgid "SAM"
+msgstr "SAM"
+
+#: i2p2www/pages/site/about/team.html:179
+msgid "SAM maintainer"
+msgstr "Mantenedor do SAM"
+
+#: i2p2www/pages/site/about/team.html:182
+msgid "I2PCPP lead"
+msgstr ""
+
+#: i2p2www/pages/site/about/team.html:184
+msgid "C++ Router"
+msgstr ""
+
+#: i2p2www/pages/site/about/team.html:187
+msgid "Translators"
+msgstr "Tradutores"
+
+#: i2p2www/pages/site/about/team.html:188
+msgid "many many people!"
+msgstr ""
+
+#: i2p2www/pages/site/about/team.html:193
+msgid "Contributors"
+msgstr ""
+
+#: i2p2www/pages/site/about/team.html:195
+msgid "fire2pe dev, console enhancements"
+msgstr ""
+
+#: i2p2www/pages/site/about/team.html:199
+msgid "desktopgui, dijjer port"
+msgstr ""
+
+#: i2p2www/pages/site/about/team.html:203
+msgid "Debian/Ubuntu Packager and PPA maintainer"
+msgstr ""
+
+#: i2p2www/pages/site/about/team.html:207
+msgid "Routerconsole backend and UI work, website revamp, unit tests work"
+msgstr ""
+
+#: i2p2www/pages/site/about/team.html:212
+msgid "Help needed on many fronts!"
+msgstr ""
+
+#: i2p2www/pages/site/about/team.html:216
+msgid "Past contributors"
+msgstr ""
+
+#: i2p2www/pages/site/about/team.html:218
+msgid "I2PTunnel development, ministreaming library"
+msgstr ""
+
+#: i2p2www/pages/site/about/team.html:222
+msgid "Project lead, Syndie lead"
+msgstr ""
+
+#: i2p2www/pages/site/about/team.html:226
+msgid "Project lead, Syndie lead, I2Phex, support guru"
+msgstr ""
+
+#: i2p2www/pages/site/about/team.html:230
+msgid "iMule lead"
+msgstr ""
+
+#: i2p2www/pages/site/about/team.html:234
+#: i2p2www/pages/site/about/team.html:238
+#: i2p2www/pages/site/about/team.html:242
+msgid "I2Phex work"
+msgstr ""
+
+#: i2p2www/pages/site/about/team.html:246
+msgid "Python SAM library, attack simulations"
+msgstr ""
+
+#: i2p2www/pages/site/about/team.html:250
+msgid "i2pmail development"
+msgstr "Desenvolvimento do i2pmail"
+
+#: i2p2www/pages/site/about/team.html:254
+msgid "Syndie help"
+msgstr ""
+
+#: i2p2www/pages/site/about/team.html:258
+msgid "i2p mail,susimail and susidns apps"
+msgstr ""
+
+#: i2p2www/pages/site/about/team.html:262
+msgid "I2Phex (port of Phex to I2P)"
+msgstr ""
+
+#: i2p2www/pages/site/about/team.html:266
+msgid "addressbook,i2p-bt,syndie client"
+msgstr ""
+
+#: i2p2www/pages/site/about/team.html:270
+msgid "organize and develop the i2p-bt BitTorrent port"
+msgstr ""
+
+#: i2p2www/pages/site/about/team.html:274
+msgid "addressbook, i2p-bt, syndie client development"
+msgstr ""
+
+#: i2p2www/pages/site/about/team.html:278
+msgid "encryption and signature routines, I2PIM"
+msgstr ""
+
+#: i2p2www/pages/site/about/team.html:282
+msgid "SAM jython code, work on stasher (DHT) and v2v (VoI2P)"
+msgstr ""
+
+#: i2p2www/pages/site/about/team.html:286
+msgid "installer, systray, bogobot"
+msgstr ""
+
+#: i2p2www/pages/site/about/team.html:290
+msgid "jbigi development, wiki migration, doc cleanup"
+msgstr ""
+
+#: i2p2www/pages/site/about/team.html:294
+msgid "java debugging and client development on I2PTunnel and the router console"
+msgstr ""
+
+#: i2p2www/pages/site/about/team.html:298
+msgid "SAM perl module"
+msgstr ""
+
+#: i2p2www/pages/site/about/team.html:302
+msgid "i2psnark work"
+msgstr ""
+
+#: i2p2www/pages/site/about/team.html:306
+msgid "java cleanup"
+msgstr ""
+
+#: i2p2www/pages/site/about/team.html:310
+msgid "docs. wiki migration"
+msgstr ""
+
+#: i2p2www/pages/site/about/team.html:314
+msgid "translations into French"
+msgstr "traduções para o francês"
+
+#: i2p2www/pages/site/about/team.html:318
+msgid "C port of jcpuid"
+msgstr ""
+
+#: i2p2www/pages/site/about/team.html:322
+msgid "C# SAM library, pants, fortuna integration"
+msgstr ""
+
+#: i2p2www/pages/site/about/team.html:326
+msgid "libSAM"
+msgstr "libSAM"
+
+#: i2p2www/pages/site/about/team.html:330
+#: i2p2www/pages/site/about/team.html:334
+msgid "i2p-bt tracker development"
+msgstr ""
+
+#: i2p2www/pages/site/about/team.html:338
+msgid "Console and website themes"
+msgstr ""
+
+#: i2p2www/pages/site/about/team.html:368
+msgid "… and many others"
+msgstr ""
+
+#: i2p2www/pages/site/about/performance/future.html:2
+msgid "Future Performance Improvements"
+msgstr ""
+
+#: i2p2www/pages/site/about/performance/future.html:4
+msgid "August 2010"
+msgstr "Agosto de 2010"
+
+#: i2p2www/pages/site/about/performance/future.html:7
+msgid ""
+"There are a few major techniques that can be done to improve the "
+"perceived\n"
+"performance of I2P - some of the following are CPU related, others "
+"bandwidth\n"
+"related, and others still are protocol related. However, all of those\n"
+"dimensions affect the latency, throughput, and perceived performance of "
+"the\n"
+"network, as they reduce contention for scarce resources. This list is of"
+" course\n"
+"not comprehensive, but it does cover the major ones that are seen."
+msgstr ""
+
+#: i2p2www/pages/site/about/performance/future.html:15
+#: i2p2www/pages/site/about/performance/index.html:106
+#, python-format
+msgid ""
+"For past performance improvements see the \n"
+"Performance History."
+msgstr ""
+
+#: i2p2www/pages/site/about/performance/future.html:20
+msgid "Better peer profiling and selection"
+msgstr ""
+
+#: i2p2www/pages/site/about/performance/future.html:21
+#, python-format
+msgid ""
+"Probably one of the most important parts of getting faster performance "
+"will\n"
+"be improving how routers choose the peers that they build their tunnels "
+"through\n"
+"- making sure they don't use peers with slow links or ones with fast "
+"links that\n"
+"are overloaded, etc. In addition, we've got to make sure we don't expose"
+"\n"
+"ourselves to a Sybil attack\n"
+"from a powerful adversary with lots of fast machines."
+msgstr ""
+
+#: i2p2www/pages/site/about/performance/future.html:30
+msgid "Network database tuning"
+msgstr ""
+
+#: i2p2www/pages/site/about/performance/future.html:31
+msgid ""
+"We're going to want to be more efficient with the network database's "
+"healing\n"
+"and maintenance algorithms - rather than constantly explore the keyspace "
+"for new\n"
+"peers - causing a significant number of network messages and router load "
+"- we\n"
+"can slow down or even stop exploring until we detect that there's "
+"something new\n"
+"worth finding (e.g. decay the exploration rate based upon the last time "
+"someone\n"
+"gave us a reference to someone we had never heard of). We can also do "
+"some\n"
+"tuning on what we actually send - how many peers we bounce back (or even "
+"if we\n"
+"bounce back a reply), as well as how many concurrent searches we perform."
+msgstr ""
+
+#: i2p2www/pages/site/about/performance/future.html:42
+msgid "Session Tag Tuning and Improvements"
+msgstr ""
+
+#: i2p2www/pages/site/about/performance/future.html:43
+#, python-format
+msgid ""
+"The way the ElGamal/AES+SessionTag "
+"algorithm\n"
+"works is by managing a set of random one-time-use 32 byte arrays, and "
+"expiring\n"
+"them if they aren't used quickly enough. If we expire them too soon, "
+"we're\n"
+"forced to fall back on a full (expensive) ElGamal encryption, but if we "
+"don't\n"
+"expire them quickly enough, we've got to reduce their quantity so that we"
+" don't\n"
+"run out of memory (and if the recipient somehow gets corrupted and loses "
+"some\n"
+"tags, even more encryption failures may occur prior to detection). With "
+"some\n"
+"more active detection and feedback driven algorithms, we can safely and "
+"more\n"
+"efficiently tune the lifetime of the tags, replacing the ElGamal "
+"encryption with\n"
+"a trivial AES operation."
+msgstr ""
+
+#: i2p2www/pages/site/about/performance/future.html:55
+#, python-format
+msgid ""
+"Additional ideas for improving Session Tag delivery are described on the\n"
+"ElGamal/AES+SessionTag page."
+msgstr ""
+
+#: i2p2www/pages/site/about/performance/future.html:61
+msgid "Migrate sessionTag to synchronized PRNG"
+msgstr ""
+
+#: i2p2www/pages/site/about/performance/future.html:62
+#, python-format
+msgid ""
+"Right now, our ElGamal/AES+SessionTag \n"
+"algorithm works by tagging each encrypted message with a unique random \n"
+"32 byte nonce (a \"session tag\"), identifying that message as being "
+"encrypted \n"
+"with the associated AES session's key. This prevents peers from "
+"distinguishing \n"
+"messages that are part of the same session, since each message has a "
+"completely \n"
+"new random tag. To accomplish this, every few messages bundle a whole \n"
+"new set of session tags within the encrypted message itself, "
+"transparently \n"
+"delivering a way to identify future messages. We then have to keep track"
+" \n"
+"of what messages are successfully delivered so that we know what tags \n"
+"we may use."
+msgstr ""
+
+#: i2p2www/pages/site/about/performance/future.html:74
+msgid ""
+"This works fine and is fairly robust, however it is inefficient in terms"
+" \n"
+"of bandwidth usage, as it requires the delivery of these tags ahead of \n"
+"time (and not all tags may be necessary, or some may be wasted, due to \n"
+"their expiration). On average though, predelivering the session tag costs"
+" \n"
+"32 bytes per message (the size of a tag). As Taral suggested though, that"
+" \n"
+"size can be avoided by replacing the delivery of the tags with a "
+"synchronized \n"
+"PRNG - when a new session is established (through an ElGamal encrypted \n"
+"block), both sides seed a PRNG for use and generate the session tags on \n"
+"demand (with the recipient precalculating the next few possible values \n"
+"to handle out of order delivery)."
+msgstr ""
+
+#: i2p2www/pages/site/about/performance/future.html:87
+msgid "Longer lasting tunnels"
+msgstr ""
+
+#: i2p2www/pages/site/about/performance/future.html:88
+msgid ""
+"The current default tunnel duration of 10 minutes is fairly arbitrary, "
+"though\n"
+"it \"feels okay\". Once we've got tunnel healing code and more effective"
+" failure\n"
+"detection, we'll be able to more safely vary those durations, reducing "
+"the\n"
+"network and CPU load (due to expensive tunnel creation messages)."
+msgstr ""
+
+#: i2p2www/pages/site/about/performance/future.html:95
+msgid ""
+"This appears to be an easy fix for high load on the big-bandwidth "
+"routers, but\n"
+"we should not resort to it until we've tuned the tunnel building "
+"algorithms further.\n"
+"However, the 10 minute tunnel lifetime is hardcoded in quite a few "
+"places,\n"
+"so substantial effort would be required to change the duration.\n"
+"Also, it would be difficult to maintain backward compatibility with such "
+"a change."
+msgstr ""
+
+#: i2p2www/pages/site/about/performance/future.html:102
+msgid ""
+"Currently, since the network average tunnel build success rate is fairly "
+"high,\n"
+"there are no current plans to extend tunnel lifetime."
+msgstr ""
+
+#: i2p2www/pages/site/about/performance/future.html:108
+msgid "Adjust the timeouts"
+msgstr ""
+
+#: i2p2www/pages/site/about/performance/future.html:109
+msgid ""
+"Yet another of the fairly arbitrary but \"okay feeling\" things we've got"
+" are the\n"
+"current timeouts for various activities. Why do we have a 60 second "
+"\"peer\n"
+"unreachable\" timeout? Why do we try sending through a different tunnel "
+"that a\n"
+"LeaseSet advertises after 10 seconds? Why are the network database "
+"queries\n"
+"bounded by 60 or 20 second limits? Why are destinations configured to "
+"ask for a\n"
+"new set of tunnels every 10 minutes? Why do we allow 60 seconds for a "
+"peer to\n"
+"reply to our request that they join a tunnel? Why do we consider a "
+"tunnel that\n"
+"doesn't pass our test within 60 seconds \"dead\"?"
+msgstr ""
+
+#: i2p2www/pages/site/about/performance/future.html:119
+msgid ""
+"Each of those imponderables can be addressed with more adaptive code, as "
+"well\n"
+"as tunable parameters to allow for more appropriate tradeoffs between\n"
+"bandwidth, latency, and CPU usage."
+msgstr ""
+
+#: i2p2www/pages/site/about/performance/future.html:125
+msgid "Full streaming protocol improvements"
+msgstr ""
+
+#: i2p2www/pages/site/about/performance/future.html:128
+msgid ""
+"Perhaps re-enable the interactive stream profile (the \n"
+"current implementation only uses the bulk stream profile)."
+msgstr ""
+
+#: i2p2www/pages/site/about/performance/future.html:134
+msgid ""
+"Client level bandwidth limiting (in either or both directions on a "
+"stream, \n"
+"or possibly shared across multiple streams). This would be in addition to"
+" \n"
+"the router's overall bandwidth limiting, of course."
+msgstr ""
+
+#: i2p2www/pages/site/about/performance/future.html:141
+msgid ""
+"Access control lists (only allowing streams to or from certain other "
+"known \n"
+"destinations)."
+msgstr ""
+
+#: i2p2www/pages/site/about/performance/future.html:147
+msgid ""
+"Web controls and monitoring the health of the various streams, as well \n"
+"as the ability to explicitly close or throttle them."
+msgstr ""
+
+#: i2p2www/pages/site/about/performance/future.html:153
+#, python-format
+msgid ""
+"Additional ideas for improving the streaming library are described on the"
+"\n"
+"streaming library page."
+msgstr ""
+
+#: i2p2www/pages/site/about/performance/history.html:2
+msgid "Performance History"
+msgstr ""
+
+#: i2p2www/pages/site/about/performance/history.html:4
+#, python-format
+msgid ""
+"Notable performance improvements have been made using the techniques "
+"below.\n"
+"There is more to do, see the Performance "
+"page\n"
+"for current issues and thoughts."
+msgstr ""
+
+#: i2p2www/pages/site/about/performance/history.html:10
+msgid "Native math"
+msgstr ""
+
+#: i2p2www/pages/site/about/performance/history.html:11
+#: i2p2www/pages/site/about/performance/history.html:67
+#: i2p2www/pages/site/about/performance/history.html:82
+#: i2p2www/pages/site/about/performance/history.html:105
+#: i2p2www/pages/site/about/performance/history.html:133
+msgid "implemented"
+msgstr ""
+
+#: i2p2www/pages/site/about/performance/history.html:12
+#, python-format
+msgid ""
+"When I last profiled the I2P code, the vast majority of time was spent "
+"within\n"
+"one function: java.math.BigInteger's\n"
+"modPow.\n"
+"Rather than try to tune this method, we'll call out to\n"
+"GNU MP - an insanely fast math library\n"
+"(with tuned assembler for many architectures). (Editor: see\n"
+"NativeBigInteger for faster public key "
+"cryptography)"
+msgstr ""
+
+#: i2p2www/pages/site/about/performance/history.html:23
+msgid ""
+"\n"
+"ugha and duck are working on the C/JNI glue code, and the existing java "
+"code\n"
+"is already deployed with hooks for that whenever its ready. Preliminary "
+"results\n"
+"look fantastic - running the router with the native GMP modPow is "
+"providing over\n"
+"a 800% speedup in encryption performance, and the load was cut in "
+"half. This\n"
+"was just on one user's machine, and things are nowhere near ready for "
+"packaging\n"
+"and deployment, yet."
+msgstr ""
+
+#: i2p2www/pages/site/about/performance/history.html:32
+msgid "Garlic wrapping a \"reply\" LeaseSet"
+msgstr ""
+
+#: i2p2www/pages/site/about/performance/history.html:33
+msgid "implemented but needs tuning"
+msgstr ""
+
+#: i2p2www/pages/site/about/performance/history.html:34
+msgid ""
+"This algorithm tweak will only be relevant for applications that want "
+"their\n"
+"peers to reply to them (though that includes everything that uses "
+"I2PTunnel or\n"
+"mihi's ministreaming lib):"
+msgstr ""
+
+#: i2p2www/pages/site/about/performance/history.html:39
+msgid ""
+"Previously, when Alice sent Bob a message, when Bob replied he had to do "
+"a\n"
+"lookup in the network database - sending out a few requests to get "
+"Alice's\n"
+"current LeaseSet. If he already has Alice's current LeaseSet, he can "
+"instead\n"
+"just send his reply immediately - this is (part of) why it typically "
+"takes a\n"
+"little longer talking to someone the first time you connect, but "
+"subsequent\n"
+"communication is faster. Currently - for all clients - we wrap\n"
+"the sender's current LeaseSet in the garlic that is delivered to the "
+"recipient,\n"
+"so that when they go to reply, they'll always have the LeaseSet "
+"locally\n"
+"stored - completely removing any need for a network database lookup on "
+"replies.\n"
+"This trades off a large portion of the sender's bandwidth for that faster"
+" reply.\n"
+"If we didn't do this very often,\n"
+"overall network bandwidth usage would decrease, since the recipient "
+"doesn't\n"
+"have to do the network database lookup."
+msgstr ""
+
+#: i2p2www/pages/site/about/performance/history.html:54
+msgid ""
+"For unpublished LeaseSets such as \"shared clients\", this is the only "
+"way to\n"
+"get the LeaseSet to Bob. Unfortunately this bundling every time adds\n"
+"almost 100% overhead to a high-bandwidth connection, and much more to"
+"\n"
+"a connection with smaller messages."
+msgstr ""
+
+#: i2p2www/pages/site/about/performance/history.html:60
+msgid ""
+"Changes scheduled for release 0.6.2 will bundle the LeaseSet only when\n"
+"necessary, at the beginning of a connection or when the LeaseSet changes."
+"\n"
+"This will substantially reduce the total overhead of I2P messaging."
+msgstr ""
+
+#: i2p2www/pages/site/about/performance/history.html:66
+msgid "More efficient TCP rejection"
+msgstr ""
+
+#: i2p2www/pages/site/about/performance/history.html:68
+msgid ""
+"At the moment, all TCP connections do all of their peer validation after\n"
+"going through the full (expensive) Diffie-Hellman handshaking to "
+"negotiate a\n"
+"private session key. This means that if someone's clock is really wrong,"
+" or\n"
+"their NAT/firewall/etc is improperly configured (or they're just running "
+"an\n"
+"incompatible version of the router), they're going to consistently "
+"(though not\n"
+"constantly, thanks to the banlist) cause a futile expensive cryptographic"
+"\n"
+"operation on all the peers they know about. While we will want to keep "
+"some\n"
+"verification/validation within the encryption boundary, we'll want to "
+"update the\n"
+"protocol to do some of it first, so that we can reject them cleanly\n"
+"without wasting much CPU or other resources."
+msgstr ""
+
+#: i2p2www/pages/site/about/performance/history.html:81
+msgid "Adjust the tunnel testing"
+msgstr ""
+
+#: i2p2www/pages/site/about/performance/history.html:83
+msgid ""
+"Rather than going with the fairly random scheme we have now, we should "
+"use a\n"
+"more context aware algorithm for testing tunnels. e.g. if we already "
+"know its\n"
+"passing valid data correctly, there's no need to test it, while if we "
+"haven't\n"
+"seen any data through it recently, perhaps its worthwhile to throw some "
+"data its\n"
+"way. This will reduce the tunnel contention due to excess messages, as "
+"well as\n"
+"improve the speed at which we detect - and address - failing tunnels."
+msgstr ""
+
+#: i2p2www/pages/site/about/performance/history.html:92
+msgid "Persistent Tunnel / Lease Selection"
+msgstr ""
+
+#: i2p2www/pages/site/about/performance/history.html:93
+msgid ""
+"Outbound tunnel selection implemented in 0.6.1.30, inbound lease "
+"selection \n"
+"implemented in release 0.6.2."
+msgstr ""
+
+#: i2p2www/pages/site/about/performance/history.html:97
+msgid ""
+"Selecting tunnels and leases at random for every message creates a large"
+" \n"
+"incidence of out-of-order delivery, which prevents the streaming lib from"
+" \n"
+"increasing its window size as much as it could. By persisting with the \n"
+"same selections for a given connection, the transfer rate is much faster."
+msgstr ""
+
+#: i2p2www/pages/site/about/performance/history.html:104
+msgid "Compress some data structures"
+msgstr ""
+
+#: i2p2www/pages/site/about/performance/history.html:106
+msgid ""
+"The I2NP messages and the data they contain is already defined in a "
+"fairly\n"
+"compact structure, though one attribute of the RouterInfo structure is "
+"not -\n"
+"\"options\" is a plain ASCII name = value mapping. Right now, we're "
+"filling it\n"
+"with those published statistics - around 3300 bytes per peer. Trivial to"
+"\n"
+"implement GZip compression would nearly cut that to 1/3 its size, and "
+"when you\n"
+"consider how often RouterInfo structures are passed across the network, "
+"that's\n"
+"significant savings - every time a router asks another router for a "
+"networkDb\n"
+"entry that the peer doesn't have, it sends back 3-10 RouterInfo of them."
+msgstr ""
+
+#: i2p2www/pages/site/about/performance/history.html:117
+msgid "Update the ministreaming protocol"
+msgstr ""
+
+#: i2p2www/pages/site/about/performance/history.html:118
+msgid "replaced by full streaming protocol"
+msgstr ""
+
+#: i2p2www/pages/site/about/performance/history.html:119
+msgid ""
+"Currently mihi's ministreaming library has a fairly simple stream "
+"negotiation\n"
+"protocol - Alice sends Bob a SYN message, Bob replies with an ACK "
+"message, then\n"
+"Alice and Bob send each other some data, until one of them sends the "
+"other a\n"
+"CLOSE message. For long lasting connections (to an IRC server, for "
+"instance),\n"
+"that overhead is negligible, but for simple one-off request/response "
+"situations\n"
+"(an HTTP request/reply, for instance), that's more than twice as many "
+"messages as\n"
+"necessary. If, however, Alice piggybacked her first payload in with the "
+"SYN\n"
+"message, and Bob piggybacked his first reply with the ACK - and perhaps "
+"also\n"
+"included the CLOSE flag - transient streams such as HTTP requests could "
+"be\n"
+"reduced to a pair of messages, instead of the "
+"SYN+ACK+request+response+CLOSE."
+msgstr ""
+
+#: i2p2www/pages/site/about/performance/history.html:132
+msgid "Implement full streaming protocol"
+msgstr ""
+
+#: i2p2www/pages/site/about/performance/history.html:134
+msgid ""
+"The ministreaming protocol takes advantage of a poor design decision in "
+"the\n"
+"I2P client protocol (I2CP) - the exposure of \"mode=GUARANTEED\", "
+"allowing what\n"
+"would otherwise be an unreliable, best-effort, message based protocol to "
+"be used\n"
+"for reliable, blocking operation (under the covers, its still all "
+"unreliable and\n"
+"message based, with the router providing delivery guarantees by garlic "
+"wrapping\n"
+"an \"ACK\" message in with the payload, so once the data gets to the "
+"target, the\n"
+"ACK message is forwarded back to us [through tunnels, of course])."
+msgstr ""
+
+#: i2p2www/pages/site/about/performance/history.html:143
+#, python-format
+msgid ""
+"As I've said, having\n"
+"I2PTunnel (and the ministreaming lib) go this route was the best thing "
+"that\n"
+"could be done, but more efficient mechanisms are available. When we rip "
+"out the\n"
+"\"mode=GUARANTEED\" functionality, we're essentially leaving ourselves "
+"with an\n"
+"I2CP that looks like an anonymous IP layer, and as such, we'll be able to"
+"\n"
+"implement the streaming library to take advantage of the design "
+"experiences of\n"
+"the TCP layer - selective ACKs, congestion detection, nagle, etc."
+msgstr ""
+
+#: i2p2www/pages/site/about/performance/index.html:2
+msgid "Performance"
+msgstr "Desempenho"
+
+#: i2p2www/pages/site/about/performance/index.html:5
+msgid ""
+"How does I2P work, why is it slow, and why does it not use my full "
+"bandwidth?"
+msgstr ""
+
+#: i2p2www/pages/site/about/performance/index.html:7
+msgid ""
+"Probably one of the most frequent things people ask is \"how fast is "
+"I2P?\",\n"
+"and no one seems to like the answer - \"it depends\". After trying out "
+"I2P, the\n"
+"next thing they ask is \"will it get faster?\", and the answer to that is"
+" a most\n"
+"emphatic yes."
+msgstr ""
+
+#: i2p2www/pages/site/about/performance/index.html:14
+msgid ""
+"I2P is a full dynamic network. Each client is known to other nodes and "
+"tests local known nodes for reachability and capacity.\n"
+"Only reachable and capable nodes are saved to a local NetDB (This is "
+"generally only a portion of the network, around 500-1000).\n"
+"When I2P builds tunnels, it selects the best resource from this pool. For"
+" example, a small subset of 20-50 nodes are only available to build "
+"tunnels with.\n"
+"Because testing happens every minute, the pool of used nodes changes "
+"every minute.\n"
+"Each I2P node knows a different part of the net, meaning that each router"
+" has a different set of I2P nodes to be used for tunnels.\n"
+"Even if two routers have the same subset of known nodes, the tests for "
+"reachability and capacity will likely show different results, as the "
+"other routers could be under load just as one router tests, but be free "
+"if the second router tests."
+msgstr ""
+
+#: i2p2www/pages/site/about/performance/index.html:23
+msgid ""
+"The above describes why each I2P node has different nodes to build "
+"tunnels.\n"
+"Because every I2P node has a different latency and bandwith, tunnels "
+"(which are built via those nodes) have different latency and bandwidth "
+"values.\n"
+"And because every I2P node has different tunnels built, no two I2P nodes "
+"have the same tunnel sets."
+msgstr ""
+
+#: i2p2www/pages/site/about/performance/index.html:29
+msgid ""
+"A server/client is known as a \"destination\" and each destination has at"
+" least one inbound and one outbound tunnel. The default is 3 hops per "
+"tunnel.\n"
+"This adds up to 12 hops (aka 12 different I2P nodes) for a full roundtrip"
+" client-server-client."
+msgstr ""
+
+#: i2p2www/pages/site/about/performance/index.html:34
+msgid ""
+"Each data package is sent through 6 other I2P nodes until it reaches the "
+"server:"
+msgstr ""
+
+#: i2p2www/pages/site/about/performance/index.html:40
+msgid "and on way back 6 different I2P nodes:"
+msgstr ""
+
+#: i2p2www/pages/site/about/performance/index.html:47
+msgid ""
+"As most traffic on I2P (www, torrent,...) needs ack packages until new "
+"data is sent, it needs to wait until a ack package returns from the "
+"server.\n"
+"In the end: send data, wait for ack, send more data, wait for ack,..\n"
+"As the RTT (RoundTripTime) adds up from the latency of each individual "
+"I2P node and each connection on this roundtrip, it takes usually 1-3 "
+"seconds until a ack package comes back to the client.\n"
+"With some internals of TCP and I2P transport, a data package has a "
+"limited size and cannot be as large as we want it to be.\n"
+"Together these conditions set a limit of max bandwidth per tunnel of "
+"20-50 kbyte/sec.\n"
+"But if ONLY ONE hop in the tunnel has only 5 kb/sec bandwidth to spend, "
+"the whole tunnel is limited to 5 kb/sec, independent of the \n"
+"latency and other limitations."
+msgstr ""
+
+#: i2p2www/pages/site/about/performance/index.html:57
+msgid ""
+"Due to encryption used and other setups in I2P (howto built up tunnels, "
+"latency, ...) it is quite expensive in CPU time to build a tunnel. This "
+"is \n"
+"why a destination is only allowed to have a max of 6 IN and 6 OUT tunnels"
+" to transport data. With a max of 50 kb/sec per tunnel, a destination "
+"could \n"
+"use roughly 300 kb/sec traffic combined ( in reality it could be more if "
+"shorter tunnels are used with low or no anonymity available).\n"
+"Used tunnels are discarded every 10 minutes and new ones are built up.\n"
+"This change of tunnels (and sometimes clients that shutdown hard due to "
+"usage of \"shut down at once\" or situations where there is power loss) "
+"does \n"
+"sometimes break tunnels and connections, as seen on the IRC2P Network in "
+"loss of connection (ping timeout) or on when using eepget."
+msgstr ""
+
+#: i2p2www/pages/site/about/performance/index.html:66
+msgid ""
+"With a limited set of destinations and a limited set of tunnels per "
+"destination, one I2P node only uses a limited set of tunnels across other"
+" I2P nodes.\n"
+"For example, if an I2P node is \"hop1\" in the small example above, we "
+"only see 1 participating tunnel originating from the client.\n"
+"If we sum up the whole I2P network, only a rather limited number of "
+"participating tunnels could be built with a limited amount of bandwidth "
+"all together.\n"
+"If one distributes these limited numbers across the number of I2P nodes, "
+"there is only a fraction of available bandwidth/capacity available for "
+"use."
+msgstr ""
+
+#: i2p2www/pages/site/about/performance/index.html:73
+msgid ""
+"To remain anonymous one router should not be used by the whole network "
+"for building tunnels.\n"
+"If one router does act as a tunnel router for ALL I2P nodes, it becomes a"
+" very real central point of failure as well as a central point to grab "
+"IPs and data from the clients. This is not good.\n"
+"I2P attempts to spread the load across a lot of I2P nodes because of this"
+" reason."
+msgstr ""
+
+#: i2p2www/pages/site/about/performance/index.html:79
+msgid ""
+"Another point is the full mesh network. Each connection hop-hop utilizes "
+"one TCP or UDP connection on the I2P nodes. With 1000 connections, one "
+"sees \n"
+"1000 TCP connections. That is quite a lot and some home and small office "
+"routers (DSL, cable,..) only allow a small number of connections (or just"
+" go mad if you use more than X connections).\n"
+"I2P tries to limit these connections to be under 1500 per UDP and per TCP"
+" type.\n"
+"This limits the amount of traffic routed across your I2P node as well."
+msgstr ""
+
+#: i2p2www/pages/site/about/performance/index.html:86
+msgid ""
+"In summary, I2P is very complex and there is no easy way to pinpoint why "
+"your node is not used.\n"
+"If your node is reachable and has a bandwidth setting of >128 kbyte/sec "
+"shared and is reachable 24/7, it should be used after some time for "
+"participating traffic.\n"
+"If it is down in between, the testing of your I2P node done by other "
+"nodes will tell them: you are not reachable. This blocks your node for at"
+" least \n"
+"24h on other nodes. So, the other nodes which tested you as down will not"
+" use your node for 24h for building tunnels. This is why your traffic "
+"will \n"
+"be lower after a restart/shutdown for a minimum of 24h."
+msgstr ""
+
+#: i2p2www/pages/site/about/performance/index.html:94
+msgid ""
+"Also: other I2P nodes needs to know your I2P router to test it for "
+"reachability and capacity. It takes time for other nodes to get known to "
+"your node. \n"
+"It will be faster if you use I2P and build more tunnels, e.g. use a "
+"torrent or www for some time."
+msgstr ""
+
+#: i2p2www/pages/site/about/performance/index.html:99
+msgid "Performance Improvements"
+msgstr "Ganhos de desempenho"
+
+#: i2p2www/pages/site/about/performance/index.html:101
+#, python-format
+msgid ""
+"For possible future performance improvements see\n"
+"Future Performance Improvements."
+msgstr ""
+
diff --git a/i2p2www/translations/pt_BR/LC_MESSAGES/docs.po b/i2p2www/translations/pt_BR/LC_MESSAGES/docs.po
new file mode 100644
index 00000000..89c1beaf
--- /dev/null
+++ b/i2p2www/translations/pt_BR/LC_MESSAGES/docs.po
@@ -0,0 +1,16593 @@
+# Portuguese (Brazil) translations for I2P.
+# Copyright (C) 2013 ORGANIZATION
+# This file is distributed under the same license as the I2P project.
+#
+# Translators:
+# blueboy, 2013
+msgid ""
+msgstr ""
+"Project-Id-Version: I2P\n"
+"Report-Msgid-Bugs-To: http://trac.i2p2.de\n"
+"POT-Creation-Date: 2013-11-27 00:23+0000\n"
+"PO-Revision-Date: 2013-11-27 02:10+0000\n"
+"Last-Translator: blueboy\n"
+"Language-Team: Portuguese (Brazil) "
+"(http://www.transifex.com/projects/p/I2P/language/pt_BR/)\n"
+"Plural-Forms: nplurals=2; plural=(n > 1)\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=utf-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"Generated-By: Babel 0.9.6\n"
+
+#: i2p2www/pages/site/docs/index.html:2 i2p2www/pages/site/docs/index.html:25
+msgid "Index to Technical Documentation"
+msgstr "Índice da Documentação Técnica"
+
+#: i2p2www/pages/site/docs/index.html:3 i2p2www/pages/site/docs/ports.html:3
+#: i2p2www/pages/site/docs/spec/datagrams.html:3
+#: i2p2www/pages/site/docs/spec/geoip.html:3
+#: i2p2www/pages/site/docs/transport/ssu.html:3
+msgid "May 2013"
+msgstr "Maio de 2013"
+
+#: i2p2www/pages/site/docs/index.html:6
+msgid "How does I2P work"
+msgstr "Como a I2P funciona"
+
+#: i2p2www/pages/site/docs/index.html:8
+msgid "Following is an index to the technical documentation for I2P."
+msgstr "Segue um índice para a documentação técnica da I2P."
+
+#: i2p2www/pages/site/docs/index.html:12
+msgid ""
+"This index is ordered from the highest to lowest layers.\n"
+"The higher layers are for \"clients\" or applications;\n"
+"the lower layers are inside the router itself.\n"
+"The interface between applications and the router is the I2CP (I2P "
+"Control Protocol) API."
+msgstr ""
+
+#: i2p2www/pages/site/docs/index.html:19
+#, python-format
+msgid ""
+"The I2P Project is committed to maintaining accurate, current "
+"documentation.\n"
+"If you find any inaccuracies in the documents linked below, please\n"
+"enter a ticket identifying the problem."
+msgstr ""
+
+#: i2p2www/pages/site/docs/index.html:27 i2p2www/pages/site/docs/naming.html:7
+#: i2p2www/pages/site/docs/api/i2ptunnel.html:12
+#: i2p2www/pages/site/docs/api/streaming.html:6
+#: i2p2www/pages/site/docs/how/elgamal-aes.html:6
+#: i2p2www/pages/site/docs/how/network-database.html:6
+#: i2p2www/pages/site/docs/how/peer-selection.html:6
+#: i2p2www/pages/site/docs/how/tech-intro.html:13
+#: i2p2www/pages/site/docs/how/tech-intro.html:97
+#: i2p2www/pages/site/docs/spec/blockfile.html:7
+#: i2p2www/pages/site/docs/spec/configuration.html:6
+#: i2p2www/pages/site/docs/spec/geoip.html:7
+#: i2p2www/pages/site/docs/spec/updates.html:6
+#: i2p2www/pages/site/docs/tunnels/implementation.html:67
+#: i2p2www/pages/site/docs/tunnels/unidirectional.html:6
+msgid "Overview"
+msgstr "Visão geral"
+
+#: i2p2www/pages/site/docs/index.html:29
+msgid "Technical Introduction"
+msgstr "Introdução técnica"
+
+#: i2p2www/pages/site/docs/index.html:30
+msgid "A Less-Technical Introduction"
+msgstr "Uma introdução menos técnica"
+
+#: i2p2www/pages/site/docs/index.html:31
+msgid "Threat model and analysis"
+msgstr ""
+
+#: i2p2www/pages/site/docs/index.html:32
+msgid "Comparisons to other anonymous networks"
+msgstr "Comparações com outras redes anônimas"
+
+#: i2p2www/pages/site/docs/index.html:33
+msgid "Protocol stack chart"
+msgstr ""
+
+#: i2p2www/pages/site/docs/index.html:34
+msgid "Papers on I2P"
+msgstr "Publicações sobre a I2P"
+
+#: i2p2www/pages/site/docs/index.html:35
+#, python-format
+msgid ""
+"Invisible Internet Project (I2P) Project Overview"
+" August 28, 2003 (pdf)"
+msgstr ""
+
+#: i2p2www/pages/site/docs/index.html:38
+msgid "Application-Layer Topics"
+msgstr ""
+
+#: i2p2www/pages/site/docs/index.html:41 i2p2www/pages/site/docs/naming.html:2
+msgid "Naming and Addressbook"
+msgstr "Sistema de nomes e Livro de endereços"
+
+#: i2p2www/pages/site/docs/index.html:42
+msgid "Plugins Overview"
+msgstr "Extensões - Uma visão geral"
+
+#: i2p2www/pages/site/docs/index.html:43
+msgid "Plugin Specification"
+msgstr "Especificações de extensões"
+
+#: i2p2www/pages/site/docs/index.html:44
+msgid "Router software updates"
+msgstr "Atualizações do software do roteador"
+
+#: i2p2www/pages/site/docs/index.html:45
+#: i2p2www/pages/site/docs/applications/bittorrent.html:2
+msgid "Bittorrent over I2P"
+msgstr "Bittorrent sobre a I2P"
+
+#: i2p2www/pages/site/docs/index.html:46
+msgid "I2PControl Plugin API"
+msgstr ""
+
+#: i2p2www/pages/site/docs/index.html:47
+msgid "hostsdb.blockfile Format"
+msgstr "Formato hostsdb.blockfile"
+
+#: i2p2www/pages/site/docs/index.html:48 i2p2www/pages/site/docs/index.html:185
+msgid "Configuration File Format"
+msgstr "Formato do arquivo de configuração"
+
+#: i2p2www/pages/site/docs/index.html:51
+msgid "Application Layer API and Protocols"
+msgstr "API da Camada de Aplicação e Protocolos"
+
+#: i2p2www/pages/site/docs/index.html:52
+msgid ""
+"High-level, easy-to-use APIs for applications written in any language to "
+"send and receive data."
+msgstr ""
+
+#: i2p2www/pages/site/docs/index.html:54
+msgid "Application Development Overview and Guide"
+msgstr "Guia e Visão Geral do Desenvolvimento de Aplicações"
+
+#: i2p2www/pages/site/docs/index.html:72
+msgid "SAM Protocol"
+msgstr ""
+
+#: i2p2www/pages/site/docs/index.html:74
+msgid "SAMv2 Protocol"
+msgstr ""
+
+#: i2p2www/pages/site/docs/index.html:76
+msgid "SAMv3 Protocol"
+msgstr ""
+
+#: i2p2www/pages/site/docs/index.html:78
+msgid "BOB Protocol"
+msgstr ""
+
+#: i2p2www/pages/site/docs/index.html:81
+msgid "End-to-End Transport API and Protocols"
+msgstr "API do transporte ponta-a-ponta e Protocolos"
+
+#: i2p2www/pages/site/docs/index.html:82
+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/api/streaming.html:2
+msgid "Streaming Library"
+msgstr ""
+
+#: i2p2www/pages/site/docs/index.html:86
+msgid "Streaming Javadoc"
+msgstr ""
+
+#: i2p2www/pages/site/docs/index.html:88
+#: i2p2www/pages/site/docs/api/datagrams.html:2
+msgid "Datagrams"
+msgstr "Datagramas"
+
+#: i2p2www/pages/site/docs/index.html:90
+msgid "Datagram Javadoc"
+msgstr ""
+
+#: i2p2www/pages/site/docs/index.html:93
+msgid "Client-to-Router Interface API and Protocol"
+msgstr ""
+
+#: i2p2www/pages/site/docs/index.html:94
+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:99
+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:101
+msgid "I2CP Specification"
+msgstr "Especificação do I2CP"
+
+#: i2p2www/pages/site/docs/index.html:103
+msgid "I2CP API Javadoc"
+msgstr "Javadoc da API do I2CP"
+
+#: i2p2www/pages/site/docs/index.html:105
+#: i2p2www/pages/site/docs/index.html:134
+msgid "Common data structures specification"
+msgstr "Especificação das estruturas de dados comuns"
+
+#: i2p2www/pages/site/docs/index.html:107
+#: i2p2www/pages/site/docs/index.html:136
+msgid "Data Structures Javadoc"
+msgstr "Javadoc das Estruturas de Dados"
+
+#: i2p2www/pages/site/docs/index.html:110
+msgid "End-to-End Encryption"
+msgstr "Criptografia de ponta a ponta"
+
+#: i2p2www/pages/site/docs/index.html:111
+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:113
+msgid "ElGamal/AES+SessionTag encryption"
+msgstr ""
+
+#: i2p2www/pages/site/docs/index.html:114
+#: i2p2www/pages/site/docs/index.html:147
+msgid "ElGamal and AES cryptography details"
+msgstr "Detalhes sobre as criptografias AES e ElGamal"
+
+#: i2p2www/pages/site/docs/index.html:117
+#: 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:118
+msgid ""
+"Distributed storage and retrieval of information about routers and "
+"clients."
+msgstr ""
+
+#: i2p2www/pages/site/docs/index.html:120
+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:121
+msgid "Cryptographic hashes"
+msgstr "Hashes criptográficas"
+
+#: i2p2www/pages/site/docs/index.html:122
+msgid "Cryptographic signatures"
+msgstr "Assinaturas criptográficas"
+
+#: i2p2www/pages/site/docs/index.html:125
+msgid "Router Message Protocol"
+msgstr "Protocolo de mensagens do roteador"
+
+#: i2p2www/pages/site/docs/index.html:126
+msgid ""
+"I2P is a message-oriented router. The messages sent between routers are "
+"defined by the I2NP protocol."
+msgstr ""
+"A I2P é baseada em roteamento orientado-a-mensagens. As mensagens "
+"enviadas entre os roteadores são definidas pelo protocolo I2NP."
+
+#: i2p2www/pages/site/docs/index.html:128
+msgid "I2NP - I2P Network Protocol Overview"
+msgstr "I2NP - Uma visão geral do protocolo de rede I2P"
+
+#: i2p2www/pages/site/docs/index.html:130
+msgid "I2NP Specification"
+msgstr "Especificação do I2NP"
+
+#: i2p2www/pages/site/docs/index.html:132
+msgid "I2NP Javadoc"
+msgstr "Javadoc do I2NP"
+
+#: i2p2www/pages/site/docs/index.html:139
+#: 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:140
+msgid ""
+"Selecting peers, requesting tunnels through those peers, and encrypting "
+"and routing messages through these tunnels."
+msgstr ""
+"Selecionandos nós, pedindo túneis através dos nós, criptografando e "
+"roteando mensagens através desses túneis."
+
+#: i2p2www/pages/site/docs/index.html:142
+msgid "Peer profiling and selection"
+msgstr ""
+
+#: i2p2www/pages/site/docs/index.html:143
+msgid "Tunnel routing overview"
+msgstr "Uma visão geral do roteamento via túneis"
+
+#: i2p2www/pages/site/docs/index.html:144
+msgid "Garlic routing and \"garlic\" terminology"
+msgstr "Roteamento e terminologia \"garlic\""
+
+#: i2p2www/pages/site/docs/index.html:145
+msgid "Tunnel building and encryption"
+msgstr "Construção de túneis e criptografia"
+
+#: i2p2www/pages/site/docs/index.html:146
+msgid "ElGamal/AES"
+msgstr "ElGamal/AES"
+
+#: i2p2www/pages/site/docs/index.html:146
+msgid "for build request encryption"
+msgstr ""
+
+#: i2p2www/pages/site/docs/index.html:148
+msgid "Tunnel building specification"
+msgstr "Especificação para a construção de túneis"
+
+#: i2p2www/pages/site/docs/index.html:149
+msgid "Low-level tunnel message specification"
+msgstr ""
+
+#: i2p2www/pages/site/docs/index.html:150
+#: i2p2www/pages/site/docs/tunnels/unidirectional.html:2
+msgid "Unidirectional Tunnels"
+msgstr "Túneis unidirecionais"
+
+#: i2p2www/pages/site/docs/index.html:151
+#: 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:152
+msgid "2009 paper (pdf), not current but still generally accurate"
+msgstr ""
+
+#: i2p2www/pages/site/docs/index.html:155
+msgid "Transport Layer"
+msgstr "Camada de transporte"
+
+#: i2p2www/pages/site/docs/index.html:156
+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:158
+msgid "Transport layer overview"
+msgstr "Uma visão geral da camada de transporte"
+
+#: i2p2www/pages/site/docs/index.html:160
+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:162
+msgid "UDP-based transport overview"
+msgstr "Uma visão geral do transporte baseado em UDP"
+
+#: i2p2www/pages/site/docs/index.html:164
+msgid "SSU specification"
+msgstr "Especificação SSU"
+
+#: i2p2www/pages/site/docs/index.html:166
+msgid "NTCP transport encryption"
+msgstr ""
+
+#: i2p2www/pages/site/docs/index.html:168
+msgid "SSU transport encryption"
+msgstr "Criptografia do transporte SSU"
+
+#: i2p2www/pages/site/docs/index.html:170
+msgid "Transport Javadoc"
+msgstr ""
+
+#: i2p2www/pages/site/docs/index.html:172
+msgid "NTCP Javadoc"
+msgstr ""
+
+#: i2p2www/pages/site/docs/index.html:174
+msgid "SSU Javadoc"
+msgstr ""
+
+#: i2p2www/pages/site/docs/index.html:177
+msgid "Other Router Topics"
+msgstr "Outros tópicos sobre o roteador"
+
+#: i2p2www/pages/site/docs/index.html:179
+msgid "Native BigInteger Library"
+msgstr ""
+
+#: i2p2www/pages/site/docs/index.html:181
+msgid "Time synchronization and NTP"
+msgstr ""
+
+#: i2p2www/pages/site/docs/index.html:183
+msgid "Performance"
+msgstr "Desempenho"
+
+#: i2p2www/pages/site/docs/index.html:190
+msgid "Developer's Guides and Resources"
+msgstr ""
+
+#: i2p2www/pages/site/docs/index.html:192
+msgid "New Developer's Guide"
+msgstr ""
+
+#: i2p2www/pages/site/docs/index.html:194
+msgid "New Translator's Guide"
+msgstr "Guia para os novos tradutores"
+
+#: i2p2www/pages/site/docs/index.html:196
+msgid "Monotone Guide"
+msgstr "Guia do Monotone"
+
+#: i2p2www/pages/site/docs/index.html:198
+msgid "Developer Guidelines"
+msgstr "Diretrizes para os desenvolvedores"
+
+#: i2p2www/pages/site/docs/index.html:200
+msgid "Javadocs on the standard internet:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/index.html:201
+#: i2p2www/pages/site/docs/index.html:205
+#: i2p2www/pages/site/docs/index.html:206
+#: i2p2www/pages/site/docs/index.html:207
+#, python-format
+msgid "Server %(num)s"
+msgstr "Servidor %(num)s"
+
+#: i2p2www/pages/site/docs/index.html:202
+#: i2p2www/pages/site/docs/index.html:211
+msgid ""
+"Note: always verify that javadocs are current by checking the release "
+"number."
+msgstr ""
+
+#: i2p2www/pages/site/docs/index.html:204
+msgid "Javadocs inside I2P:"
+msgstr "Javadocs na I2P:"
+
+#: i2p2www/pages/site/docs/index.html:213
+msgid "Ports used by I2P"
+msgstr "Portas usadas pela I2P"
+
+#: i2p2www/pages/site/docs/index.html:215
+msgid "Automatic updates to development builds inside I2P"
+msgstr ""
+
+#: i2p2www/pages/site/docs/index.html:217
+msgid "Updating the wrapper manually"
+msgstr "Atualizando o empacotador manualmente"
+
+#: i2p2www/pages/site/docs/index.html:219
+msgid "User forum"
+msgstr "Fórum de usuários"
+
+#: i2p2www/pages/site/docs/index.html:221
+msgid "Developer forum inside I2P"
+msgstr "Fórum de desenvolvedores na I2P"
+
+#: i2p2www/pages/site/docs/index.html:223
+msgid "Bug tracker"
+msgstr ""
+
+#: i2p2www/pages/site/docs/index.html:225
+msgid "Viewmtn inside I2P"
+msgstr ""
+
+#: i2p2www/pages/site/docs/index.html:227
+msgid "I2P Source exported to GitHub"
+msgstr ""
+
+#: i2p2www/pages/site/docs/index.html:229
+msgid "I2P Source Git Repo inside I2P"
+msgstr ""
+
+#: i2p2www/pages/site/docs/index.html:231
+msgid "Source translation at Transifex"
+msgstr ""
+
+#: i2p2www/pages/site/docs/index.html:233
+msgid "Roadmap wiki"
+msgstr "Wiki do plano de ação"
+
+#: i2p2www/pages/site/docs/index.html:235
+msgid "Old roadmap"
+msgstr "Plano de ação antigo"
+
+#: i2p2www/pages/site/docs/index.html:235
+#: i2p2www/pages/site/docs/index.html:237
+msgid "not current"
+msgstr ""
+
+#: i2p2www/pages/site/docs/index.html:237
+msgid "To Do List"
+msgstr "Lista de tarefas por fazer"
+
+#: i2p2www/pages/site/docs/naming.html:3
+msgid "March 2012"
+msgstr "Março de 2012"
+
+#: i2p2www/pages/site/docs/naming.html:6
+msgid "Naming in I2P"
+msgstr "Sistema de nomes na I2P"
+
+#: i2p2www/pages/site/docs/naming.html:9
+msgid ""
+"I2P ships with a generic naming library and a base implementation \n"
+"designed to work off a local name to destination mapping, as well as an\n"
+"add-on application called the addressbook. \n"
+"I2P also supports Base32 hostnames similar to "
+"Tor's .onion addresses."
+msgstr ""
+
+#: i2p2www/pages/site/docs/naming.html:16
+msgid ""
+"The addressbook is a web-of-trust\n"
+"driven secure, distributed, and human readable naming system, sacrificing"
+" only\n"
+"the call for all human readable names to be globally unique by mandating "
+"only\n"
+"local uniqueness. While all messages in I2P are cryptographically "
+"addressed\n"
+"by their destination, different people can have local addressbook entries"
+" for\n"
+"\"Alice\" which refer to different destinations. People can still "
+"discover new\n"
+"names by importing published addressbooks of peers specified in their web"
+" of trust,\n"
+"by adding in the entries provided through a third party, or (if some "
+"people organize\n"
+"a series of published addressbooks using a first come first serve "
+"registration\n"
+"system) people can choose to treat these addressbooks as name servers, "
+"emulating\n"
+"traditional DNS."
+msgstr ""
+
+#: i2p2www/pages/site/docs/naming.html:30
+#, python-format
+msgid ""
+"NOTE: For the reasoning behind the I2P naming system, common arguments "
+"against it\n"
+"and possible alternatives see the naming"
+" discussion\n"
+"page."
+msgstr ""
+
+#: i2p2www/pages/site/docs/naming.html:37
+msgid "Naming System Components"
+msgstr "Componentes do Sistema de nomes"
+
+#: i2p2www/pages/site/docs/naming.html:39
+msgid ""
+"There is no central naming authority in I2P.\n"
+"All hostnames are local."
+msgstr ""
+
+#: i2p2www/pages/site/docs/naming.html:44
+msgid ""
+"The naming system is quite simple and most of it is implemented\n"
+"in applications external to the router, but bundled with\n"
+"the I2P distribution.\n"
+"The components are:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/naming.html:52
+msgid ""
+"The client application which does local lookups "
+"in hosts.txt\n"
+"and also takes care of the Base32 hostnames."
+msgstr ""
+
+#: i2p2www/pages/site/docs/naming.html:56
+msgid ""
+"The HTTP proxy which asks the router for "
+"lookups and points\n"
+"the user to remote jump services to assist with failed lookups."
+msgstr ""
+
+#: i2p2www/pages/site/docs/naming.html:60
+msgid ""
+"HTTP host-add forms which allow users to "
+"add hosts to their local hosts.txt"
+msgstr ""
+
+#: i2p2www/pages/site/docs/naming.html:63
+msgid ""
+"HTTP jump services which provide their own"
+" lookups and redirection."
+msgstr ""
+
+#: i2p2www/pages/site/docs/naming.html:66
+msgid ""
+"The addressbook application which merges "
+"external\n"
+"host lists, retrieved via HTTP, with the local list."
+msgstr ""
+
+#: i2p2www/pages/site/docs/naming.html:70
+msgid ""
+"The SusiDNS application which is a simple web "
+"front-end\n"
+"for addressbook configuration and viewing of the local host lists."
+msgstr ""
+
+#: i2p2www/pages/site/docs/naming.html:77
+msgid "Naming Files and Lookups"
+msgstr ""
+
+#: i2p2www/pages/site/docs/naming.html:79
+#, python-format
+msgid ""
+"All destinations in I2P are 516-byte (or longer) keys.\n"
+"(To be more precise, it is a 256-byte public key plus a 128-byte signing "
+"key\n"
+"plus a null certificate, which in Base64 representation is 516 bytes.\n"
+"Certificates are not "
+"used now,\n"
+"if they are, the keys will be longer.\n"
+"One possible use of certificates is for proof of work.)"
+msgstr ""
+
+#: i2p2www/pages/site/docs/naming.html:88
+msgid ""
+"If an application (i2ptunnel or the HTTP proxy) wishes to access\n"
+"a destination by name, the router does a very simple local lookup\n"
+"to resolve that name.\n"
+"The client application (technically, the client side of I2CP in the I2P "
+"API)\n"
+"does a linear search through three local files, in order, to\n"
+"look up host names and convert them to a 516-byte destination key:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/naming.html:103
+msgid ""
+"The lookup is case-insensitive.\n"
+"The first match is used, and conflicts are not detected.\n"
+"There is no enforcement of naming rules in lookups."
+msgstr ""
+
+#: i2p2www/pages/site/docs/naming.html:109
+#, python-format
+msgid ""
+"Lookups are cached for a few minutes.\n"
+"There is an experimental facility for real-time lookups (a la DNS) over "
+"the network within the router,\n"
+"although it is not enabled by default\n"
+"(see \"EepGet\" under Alternatives on the discussion"
+" page)."
+msgstr ""
+
+#: i2p2www/pages/site/docs/naming.html:116
+msgid "HTTP Proxy"
+msgstr ""
+
+#: i2p2www/pages/site/docs/naming.html:118
+msgid ""
+"The HTTP proxy does a lookup via the router for all hostnames ending in "
+"'.i2p'.\n"
+"Otherwise, it forwards the request to a configured HTTP outproxy.\n"
+"Thus, in practice, all HTTP (eepsite) hostnames must end in the pseudo-"
+"Top Level Domain '.i2p'."
+msgstr ""
+
+#: i2p2www/pages/site/docs/naming.html:124
+msgid ""
+"If the router fails to resolve the hostname, the HTTP proxy returns\n"
+"an error page to the user with links to several \"jump\" services.\n"
+"See below for details."
+msgstr ""
+
+#: i2p2www/pages/site/docs/naming.html:130
+#: i2p2www/pages/site/docs/spec/configuration.html:77
+msgid "Addressbook"
+msgstr "Livro de endereços"
+
+#: i2p2www/pages/site/docs/naming.html:131
+msgid "Incoming Subscriptions and Merging"
+msgstr ""
+
+#: i2p2www/pages/site/docs/naming.html:133
+msgid ""
+"The addressbook application periodically\n"
+"retrieves other users' hosts.txt files and merges\n"
+"them with the local hosts.txt, after several checks.\n"
+"Naming conflicts are resolved on a first-come first-served\n"
+"basis."
+msgstr ""
+
+#: i2p2www/pages/site/docs/naming.html:141
+msgid ""
+"Subscribing to another user's hosts.txt file involves\n"
+"giving them a certain amount of trust.\n"
+"You do not want them, for example, 'hijacking' a new site\n"
+"by quickly entering in their own key for a new site before\n"
+"passing the new host/key entry to you."
+msgstr ""
+
+#: i2p2www/pages/site/docs/naming.html:149
+msgid ""
+"For this reason, the only subscription configured by\n"
+"default is http://www.i2p2.i2p/hosts.txt,\n"
+"which contains a copy of the hosts.txt included\n"
+"in the I2P release.\n"
+"Users must configure additional subscriptions in their\n"
+"local addressbook application (via subscriptions.txt or SusiDNS)."
+msgstr ""
+
+#: i2p2www/pages/site/docs/naming.html:158
+msgid "Some other public addressbook subscription links:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/naming.html:165
+msgid ""
+"The operators of these services may have various policies for listing "
+"hosts.\n"
+"Presence on this list does not imply endorsement."
+msgstr ""
+
+#: i2p2www/pages/site/docs/naming.html:170
+#: i2p2www/pages/site/docs/naming.html:182
+msgid "Naming Rules"
+msgstr ""
+
+#: i2p2www/pages/site/docs/naming.html:171
+msgid ""
+"While there are hopefully not any technical limitations within I2P on "
+"host names,\n"
+"the addressbook enforces several restrictions on host names\n"
+"imported from subscriptions.\n"
+"It does this for basic typographical sanity and compatibility with "
+"browsers,\n"
+"and for security.\n"
+"The rules are essentially the same as those in RFC2396 Section 3.2.2.\n"
+"Any hostnames violating these rules may not be propagated\n"
+"to other routers."
+msgstr ""
+
+#: i2p2www/pages/site/docs/naming.html:186
+msgid "Names are converted to lower case on import."
+msgstr ""
+
+#: i2p2www/pages/site/docs/naming.html:190
+msgid ""
+"Names are checked for conflict with existing names in the existing "
+"userhosts.txt and hosts.txt\n"
+"(but not privatehosts.txt) after conversion to lower case."
+msgstr ""
+
+#: i2p2www/pages/site/docs/naming.html:195
+msgid "Must contain only [a-z] [0-9] '.' and '-' after conversion to lower case."
+msgstr ""
+
+#: i2p2www/pages/site/docs/naming.html:199
+msgid "Must not start with '.' or '-'."
+msgstr "Não pode começar com '.' ou '-'"
+
+#: i2p2www/pages/site/docs/naming.html:203
+msgid "Must end with '.i2p'."
+msgstr "Deve terminar com '.i2p'."
+
+#: i2p2www/pages/site/docs/naming.html:207
+msgid "67 characters maximum, including the '.i2p'."
+msgstr "No máximo 67 caractéres, incluindo o '.i2p'."
+
+#: i2p2www/pages/site/docs/naming.html:211
+msgid "Must not contain '..'."
+msgstr "Não pode conter '..'."
+
+#: i2p2www/pages/site/docs/naming.html:215
+msgid "Must not contain '.-' or '-.' (as of 0.6.1.33)."
+msgstr ""
+
+#: i2p2www/pages/site/docs/naming.html:219
+msgid "Must not contain '--' except in 'xn--' for IDN."
+msgstr ""
+
+#: i2p2www/pages/site/docs/naming.html:223
+msgid "Base32 hostnames (*.b32.i2p) are not allowed."
+msgstr "Nomes de hosts Base32 (*.b32.i2p) não são permitidos."
+
+#: i2p2www/pages/site/docs/naming.html:227
+msgid ""
+"Certain hostnames reserved for project use are not allowed\n"
+"(proxy.i2p, router.i2p, console.i2p, *.proxy.i2p, *.router.i2p, "
+"*.console.i2p, and others)"
+msgstr ""
+"Alguns nomes de hosts reservados para uso do projeto não são permitidos\n"
+"(proxy.i2p, router.i2p, console.i2p, *.proxy.i2p, *.router.i2p, "
+"*.console.i2p, and others)"
+
+#: i2p2www/pages/site/docs/naming.html:232
+msgid "Keys are checked for base64 validity."
+msgstr ""
+
+#: i2p2www/pages/site/docs/naming.html:236
+msgid ""
+"Keys are checked for conflict with existing keys in hosts.txt (but not "
+"privatehosts.txt)."
+msgstr ""
+
+#: i2p2www/pages/site/docs/naming.html:240
+msgid "Minimum key length 516 bytes."
+msgstr ""
+
+#: i2p2www/pages/site/docs/naming.html:244
+msgid "Maximum key length 616 bytes (to account for certs up to 100 bytes)."
+msgstr ""
+
+#: i2p2www/pages/site/docs/naming.html:249
+msgid ""
+"Any name received via subscription that passes all the checks is added to"
+" the local hosts.txt."
+msgstr ""
+
+#: i2p2www/pages/site/docs/naming.html:253
+msgid ""
+"Note that the '.' symbols in a host name are of no significance,\n"
+"and do not denote any actual naming or trust hierarchy.\n"
+"If the name 'host.i2p' already exists, there is nothing\n"
+"to prevent anybody from adding a name 'a.host.i2p' to their hosts.txt,\n"
+"and this name can be imported by others' addressbook.\n"
+"Methods to deny subdomains to non-domain 'owners' (certificates?),\n"
+"and the desirability and feasibility of these methods,\n"
+"are topics for future discussion."
+msgstr ""
+
+#: i2p2www/pages/site/docs/naming.html:264
+msgid ""
+"International Domain Names (IDN) also work in i2p (using punycode 'xn--' "
+"form).\n"
+"To see IDN .i2p domain names rendered correctly in Firefox's location "
+"bar,\n"
+"add 'network.IDN.whitelist.i2p (boolean) = true' in about:config."
+msgstr ""
+
+#: i2p2www/pages/site/docs/naming.html:270
+msgid ""
+"As the addressbook application does not use privatehosts.txt at all, in "
+"practice\n"
+"this file is the only place where it is appropriate to place private "
+"aliases or\n"
+"\"pet names\" for sites already in hosts.txt."
+msgstr ""
+
+#: i2p2www/pages/site/docs/naming.html:276
+msgid "Outgoing Subscriptions"
+msgstr ""
+
+#: i2p2www/pages/site/docs/naming.html:277
+msgid ""
+"Addressbook will publish the merged hosts.txt to a location\n"
+"(traditionally hosts.txt in the local eepsite's home directory) to be "
+"accessed by others\n"
+"for their subscriptions.\n"
+"This step is optional and is disabled by default."
+msgstr ""
+
+#: i2p2www/pages/site/docs/naming.html:285
+msgid ""
+"The addressbook application, together with eepget, saves the Etag and/or "
+"Last-Modified\n"
+"information returned by the web server of the subscription.\n"
+"This greatly reduces the bandwidth required, as the web server will\n"
+"return a '304 Not Modified' on the next fetch if nothing has changed."
+msgstr ""
+
+#: i2p2www/pages/site/docs/naming.html:292
+msgid ""
+"However the entire hosts.txt is downloaded if it has changed.\n"
+"See below for discussion on this issue."
+msgstr ""
+
+#: i2p2www/pages/site/docs/naming.html:297
+msgid ""
+"Hosts serving a static hosts.txt or an equivalent CGI application\n"
+"are strongly encouraged to deliver\n"
+"a Content-Length header, and either an Etag or Last-Modified header.\n"
+"Also ensure that the server delivers a '304 Not Modified' when "
+"appropriate.\n"
+"This will dramatically reduce the network bandwidth, and\n"
+"reduce chances of corruption."
+msgstr ""
+
+#: i2p2www/pages/site/docs/naming.html:306
+msgid "Host Add Services"
+msgstr ""
+
+#: i2p2www/pages/site/docs/naming.html:307
+msgid ""
+"A host add service is a simple CGI application that takes a hostname and "
+"a Base64 key as parameters\n"
+"and adds that to its local hosts.txt.\n"
+"If other routers subscribe to that hosts.txt, the new hostname/key\n"
+"will be propagated through the network."
+msgstr ""
+
+#: i2p2www/pages/site/docs/naming.html:314
+msgid ""
+"It is recommended that host add services impose, at a minimum, the "
+"restrictions imposed by the addressbook application listed above.\n"
+"Host add services may impose additional restrictions on hostnames and "
+"keys, for example:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/naming.html:319
+msgid "A limit on number of 'subdomains'."
+msgstr ""
+
+#: i2p2www/pages/site/docs/naming.html:323
+msgid "Authorization for 'subdomains' through various methods."
+msgstr ""
+
+#: i2p2www/pages/site/docs/naming.html:327
+msgid "Hashcash or signed certificates."
+msgstr ""
+
+#: i2p2www/pages/site/docs/naming.html:331
+msgid "Editorial review of host names and/or content."
+msgstr ""
+
+#: i2p2www/pages/site/docs/naming.html:335
+msgid "Categorization of hosts by content."
+msgstr ""
+
+#: i2p2www/pages/site/docs/naming.html:339
+msgid "Reservation or rejection of certain host names."
+msgstr ""
+
+#: i2p2www/pages/site/docs/naming.html:343
+msgid "Restrictions on the number of names registered in a given time period."
+msgstr ""
+
+#: i2p2www/pages/site/docs/naming.html:347
+msgid "Delays between registration and publication."
+msgstr ""
+
+#: i2p2www/pages/site/docs/naming.html:351
+msgid "Requirement that the host be up for verification."
+msgstr ""
+
+#: i2p2www/pages/site/docs/naming.html:355
+msgid "Expiration and/or revocation."
+msgstr ""
+
+#: i2p2www/pages/site/docs/naming.html:359
+msgid "IDN spoof rejection."
+msgstr ""
+
+#: i2p2www/pages/site/docs/naming.html:364
+msgid "Jump Services"
+msgstr ""
+
+#: i2p2www/pages/site/docs/naming.html:365
+msgid ""
+"A jump service is a simple CGI application that takes a hostname as a "
+"parameter\n"
+"and returns a 301 redirect to the proper URL with a "
+"?i2paddresshelper=key\n"
+"string appended.\n"
+"The HTTP proxy will interpret the appended string and\n"
+"use that key as the actual destination.\n"
+"In addition, the proxy will cache that key so the\n"
+"address helper is not necessary until restart."
+msgstr ""
+
+#: i2p2www/pages/site/docs/naming.html:375
+msgid ""
+"Note that, like with subscriptions, using a jump service\n"
+"implies a certain amount of trust, as a jump service could maliciously\n"
+"redirect a user to an incorrect destination."
+msgstr ""
+
+#: i2p2www/pages/site/docs/naming.html:381
+msgid ""
+"To provide the best service, a jump service should be subscribed to\n"
+"several hosts.txt providers so that its local host list is current."
+msgstr ""
+
+#: i2p2www/pages/site/docs/naming.html:387
+msgid ""
+"SusiDNS is simply a web interface front-end to configuring addressbook "
+"subscriptions\n"
+"and accessing the four addressbook files.\n"
+"All the real work is done by the 'addressbook' application."
+msgstr ""
+
+#: i2p2www/pages/site/docs/naming.html:393
+msgid ""
+"Currently, there is little enforcement of addressbook naming rules within"
+" SusiDNS,\n"
+"so a user may enter hostnames locally that would be rejected by\n"
+"the addressbook subscription rules."
+msgstr ""
+
+#: i2p2www/pages/site/docs/naming.html:399
+msgid "Base32 Names"
+msgstr "Nomes de Base32"
+
+#: i2p2www/pages/site/docs/naming.html:400
+msgid ""
+"I2P supports Base32 hostnames similar to Tor's .onion addresses.\n"
+"Base32 addresses are much shorter and easier to handle than the\n"
+"full 516-character Base64 Destinations or addresshelpers.\n"
+"Example: "
+"ukeu3k5oycgaauneqgtnvselmt4yemvoilkln7jpvamvfx7dnkdq.b32.i2p"
+msgstr ""
+
+#: i2p2www/pages/site/docs/naming.html:407
+msgid ""
+"In Tor, the address is 16 characters (80 bits), or half of the SHA-1 "
+"hash.\n"
+"I2P uses 52 characters (256 bits) to represent the full SHA-256 hash.\n"
+"The form is {52 chars}.b32.i2p.\n"
+"Base32 is implemented in the naming service, which queries the\n"
+"router over I2CP to lookup the LeaseSet to get the full Destination.\n"
+"Base32 lookups will only be successful when the Destination is up and "
+"publishing\n"
+"a LeaseSet.\n"
+"Because resolution may require a network database lookup, it may take "
+"significantly\n"
+"longer than a local address book lookup."
+msgstr ""
+
+#: i2p2www/pages/site/docs/naming.html:419
+msgid ""
+"Base32 addresses can be used in most places where hostnames or full "
+"destinations\n"
+"are used, however there are some exceptions where they may fail if the\n"
+"name does not immediately resolve. I2PTunnel will fail, for example, if\n"
+"the name does not resolve to a destination."
+msgstr ""
+
+#: i2p2www/pages/site/docs/plugins.html:2
+#: i2p2www/pages/site/docs/spec/configuration.html:65
+msgid "Plugins"
+msgstr "Extensões"
+
+#: i2p2www/pages/site/docs/plugins.html:3
+msgid "June 2012"
+msgstr "Junho de 2012"
+
+#: i2p2www/pages/site/docs/plugins.html:6
+msgid "I2P Plugins"
+msgstr ""
+
+#: i2p2www/pages/site/docs/plugins.html:8
+msgid "General Information"
+msgstr "Informação geral"
+
+#: i2p2www/pages/site/docs/plugins.html:9
+msgid ""
+"I2P includes a plugin architecture\n"
+"to support easy development and installation of additional software."
+msgstr ""
+
+#: i2p2www/pages/site/docs/plugins.html:14
+msgid ""
+"There are now plugins available that support distributed email, blogs, "
+"IRC\n"
+"clients, distributed file storage, wikis, and more."
+msgstr ""
+
+#: i2p2www/pages/site/docs/plugins.html:19
+msgid "Benefits to i2p users and app developers:"
+msgstr "Benefícios para os usuários da I2P e desenvolvedores de aplicações:"
+
+#: i2p2www/pages/site/docs/plugins.html:24
+msgid "Easy distribution of applications"
+msgstr ""
+
+#: i2p2www/pages/site/docs/plugins.html:28
+msgid ""
+"Allows innovation and use of additional libraries without worrying about\n"
+"increasing the size of i2pupdate.sud"
+msgstr ""
+
+#: i2p2www/pages/site/docs/plugins.html:33
+msgid ""
+"Support large or special-purpose applications that would never be bundled"
+"\n"
+"with the I2P installation"
+msgstr ""
+
+#: i2p2www/pages/site/docs/plugins.html:38
+msgid "Cryptographically signed and verified applications"
+msgstr ""
+
+#: i2p2www/pages/site/docs/plugins.html:42
+msgid "Automatic updates of applications, just like for the router"
+msgstr ""
+
+#: i2p2www/pages/site/docs/plugins.html:46
+msgid ""
+"Separate initial install and update packages, if desired, for smaller "
+"update downloads"
+msgstr ""
+
+#: i2p2www/pages/site/docs/plugins.html:50
+msgid ""
+"One-click installation of applications. No more asking users to modify\n"
+"wrapper.config or clients.config"
+msgstr ""
+
+#: i2p2www/pages/site/docs/plugins.html:55
+msgid "Isolate applications from the base $I2P installation"
+msgstr ""
+
+#: i2p2www/pages/site/docs/plugins.html:59
+msgid ""
+"Automatic compatibility checking for I2P version, Java version, Jetty\n"
+"version, and previous installed application version"
+msgstr ""
+
+#: i2p2www/pages/site/docs/plugins.html:64
+msgid "Automatic link addition in console"
+msgstr ""
+
+#: i2p2www/pages/site/docs/plugins.html:68
+msgid ""
+"Automatic startup of application, including modifying classpath, without "
+"requiring a restart"
+msgstr ""
+
+#: i2p2www/pages/site/docs/plugins.html:72
+msgid "Automatic integration and startup of webapps into console Jetty instance"
+msgstr ""
+
+#: i2p2www/pages/site/docs/plugins.html:76
+#, python-format
+msgid ""
+"Facilitate creation of 'app stores' like the one at\n"
+"%(pluginsite)s"
+msgstr ""
+
+#: i2p2www/pages/site/docs/plugins.html:81
+msgid "One-click uninstall"
+msgstr ""
+
+#: i2p2www/pages/site/docs/plugins.html:85
+msgid "Language and theme packs for the console"
+msgstr ""
+
+#: i2p2www/pages/site/docs/plugins.html:89
+msgid "Bring detailed application information to the router console"
+msgstr ""
+
+#: i2p2www/pages/site/docs/plugins.html:93
+msgid "Non-java applications also supported"
+msgstr ""
+
+#: i2p2www/pages/site/docs/plugins.html:99
+msgid "Required I2P version"
+msgstr "Versão do roteador I2P necessária"
+
+#: i2p2www/pages/site/docs/plugins.html:100
+msgid "0.7.12 or newer."
+msgstr "0.7.12 ou mais recente."
+
+#: i2p2www/pages/site/docs/plugins.html:102
+msgid "Installation"
+msgstr "Instalação"
+
+#: i2p2www/pages/site/docs/plugins.html:103
+msgid ""
+"To install and start a plugin, copy the .xpi2p install link "
+"to\n"
+"the form at the bottom of\n"
+"configclients.jsp"
+" in\n"
+"your router console and click the \"install plugin\" button. After a"
+"\n"
+"plugin is installed and started, a link to the plugin will usually appear"
+" at\n"
+"the top of your summary bar."
+msgstr ""
+
+#: i2p2www/pages/site/docs/plugins.html:112
+msgid ""
+"To update a plugin to the latest version, just click the update button on"
+"\n"
+"configclients.jsp."
+"\n"
+"There is also a button to check if the plugin has a more recent version, "
+"as\n"
+"well as a button to check for updates for all plugins. Plugins will be "
+"checked\n"
+"for updates automatically when updating to a new I2P release (not "
+"including dev\n"
+"builds)."
+msgstr ""
+
+#: i2p2www/pages/site/docs/plugins.html:122
+msgid "Development"
+msgstr "Desenvolvimento"
+
+#: i2p2www/pages/site/docs/plugins.html:123
+#, python-format
+msgid ""
+"See the latest plugin specification and "
+"the\n"
+"plugin forum on %(zzz)s."
+msgstr ""
+
+#: i2p2www/pages/site/docs/plugins.html:128
+#, python-format
+msgid ""
+"See also the sources for plugins developed by various people. Some "
+"plugins, such\n"
+"as snowman, were "
+"developed\n"
+"specifically as examples."
+msgstr ""
+
+#: i2p2www/pages/site/docs/plugins.html:134
+msgid ""
+"Developers wanted! Plugins are a great way to learn more about I2P"
+"\n"
+"or easily add some feature."
+msgstr ""
+
+#: i2p2www/pages/site/docs/plugins.html:139
+msgid "Getting Started"
+msgstr ""
+
+#: i2p2www/pages/site/docs/plugins.html:140
+#, python-format
+msgid ""
+"To create a plugin from an existing binary package you will need to get\n"
+"makeplugin.sh from the i2p.scripts branch in "
+"monotone."
+msgstr ""
+
+#: i2p2www/pages/site/docs/plugins.html:146
+msgid "Known Issues"
+msgstr "Problemas conhecidos"
+
+#: i2p2www/pages/site/docs/plugins.html:147
+msgid ""
+"Note that the router's plugin architecture does NOT currently\n"
+"provide any additional security isolation or sandboxing of plugins."
+msgstr ""
+
+#: i2p2www/pages/site/docs/plugins.html:153
+msgid ""
+"Updates of a plugin with included jars (not wars) won't be recognized if\n"
+"the plugin was already run, as it requires class loader trickery to flush"
+" the\n"
+"class cache; a full router restart is required."
+msgstr ""
+
+#: i2p2www/pages/site/docs/plugins.html:159
+msgid "The stop button may be displayed even if there is nothing to stop."
+msgstr ""
+
+#: i2p2www/pages/site/docs/plugins.html:163
+msgid ""
+"Plugins running in a separate JVM create a logs/ directory "
+"in\n"
+"$CWD."
+msgstr ""
+"Extensões rodando em Máquina Virtual Java separada criam um diretório de "
+"registros/ em\n"
+"$CWD."
+
+#: i2p2www/pages/site/docs/plugins.html:168
+msgid ""
+"No initial keys are present, except for those of jrandom and zzz (using "
+"the\n"
+"same keys as for router update), so the first key seen for a signer is\n"
+"automatically accepted—there is no signing key authority."
+msgstr ""
+
+#: i2p2www/pages/site/docs/plugins.html:174
+msgid ""
+"When deleting a plugin, the directory is not always deleted, especially "
+"on\n"
+"Windows."
+msgstr ""
+
+#: i2p2www/pages/site/docs/plugins.html:179
+msgid ""
+"Installing a plugin requiring Java 1.6 on a Java 1.5 machine will result "
+"in a\n"
+"\"plugin is corrupt\" message if pack200 compression of the plugin file "
+"is used."
+msgstr ""
+
+#: i2p2www/pages/site/docs/plugins.html:184
+msgid "Theme and translation plugins are untested."
+msgstr ""
+
+#: i2p2www/pages/site/docs/plugins.html:188
+msgid "Disabling autostart doesn't always work."
+msgstr ""
+
+#: i2p2www/pages/site/docs/ports.html:2
+msgid "Ports Used by I2P"
+msgstr "Portas usadas pela I2P"
+
+#: i2p2www/pages/site/docs/ports.html:7
+msgid ""
+"These are the ports used or reserved by I2P, including those for known "
+"plugins,\n"
+"common alternates,\n"
+"and some typical related applications."
+msgstr ""
+
+#: i2p2www/pages/site/docs/ports.html:13
+#, python-format
+msgid ""
+"Note that many of these are not enabled by default.\n"
+"There is more information in the FAQ.\n"
+"See also the documentation for individual plugins.\n"
+"Plugin authors please add any ports you use here.\n"
+"For new plugins, we recommend using the next available port\n"
+"in the 766x range."
+msgstr ""
+
+#: i2p2www/pages/site/docs/ports.html:53
+msgid "recommended spot for new plugins/applications"
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/bob.html:3
+#: i2p2www/pages/site/docs/api/datagrams.html:3
+#: i2p2www/pages/site/docs/how/garlic-routing.html:3
+#: i2p2www/pages/site/docs/protocol/index.html:3
+#: i2p2www/pages/site/docs/transport/ntcp.html:3
+msgid "August 2010"
+msgstr "Agosto de 2010"
+
+#: i2p2www/pages/site/docs/api/bob.html:5
+msgid "BOB - Basic Open Bridge"
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/bob.html:7
+msgid "Technical differences from SAM (for the better?)"
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/bob.html:9
+msgid ""
+"BOB has separate command and data channels. \n"
+"One, an application command channel socket to router to configure.\n"
+"Two, the application data sockets to/from router that carry only data.\n"
+"The command channel is only needed for making or setting the initial\n"
+"destination key, and to set the destination key to port bindings. \n"
+"All connections run in parallel."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/bob.html:18
+msgid ""
+"SAM has one connection that does everything, and you need to parse every "
+"packet."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/bob.html:22
+msgid ""
+"BOB does not hold keypair values, nor does the router.\n"
+"Your application holds the keypair values. \n"
+"This is to reduce any extra complexity in the router code, it also adds "
+"to\n"
+"your privacy."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/bob.html:29
+msgid "SAM router stores every keypair you ever make."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/bob.html:33
+msgid "Those are the important differences."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/bob.html:37
+msgid "KEYS = keypair public+private, these are BASE64"
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/bob.html:40
+msgid "KEY = public key, also BASE64"
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/bob.html:43
+msgid ""
+"ERROR as is implied returns the message \"ERROR "
+"\"+DESCRIPTION+\"\n"
+"\", where the DESCRIPTION is what went wrong."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/bob.html:46
+msgid ""
+"OK returns \"OK\", and if data is to be "
+"returned, it is on the same line. OK means the command is "
+"finished."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/bob.html:49
+msgid ""
+"DATA lines contain information that you requested. There may"
+" be multiple DATA lines per request."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/bob.html:53
+msgid ""
+"NOTE: The help command is the ONLY command that has an exception "
+"to\n"
+"the rules... it can actually return nothing! This is intentional, since\n"
+"help is a HUMAN and not an APPLICATION command."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/bob.html:59
+msgid ""
+"PLEASE NOTE:\n"
+"For CURRENT details on the commands PLEASE use the built-in help command."
+" \n"
+"Just telnet to localhost 2827 and type help and you can get full "
+"documentation on each command."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/bob.html:65
+msgid ""
+"Commands never get obsoleted or changed, however new commands do get "
+"added from time to time."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/bob.html:69
+msgid "Here are the commands we have as of this writing:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/bob.html:74
+msgid "COMMAND"
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/bob.html:74
+msgid "OPERAND"
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/bob.html:74
+msgid "RETURNS"
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/bob.html:101
+msgid ""
+"Once set up, all TCP sockets can and will block as needed, and there is "
+"no need for any \n"
+"additional messages to/from the command channel. This allows the router "
+"to pace the\n"
+"stream without exploding with OOM like SAM does as it chokes on "
+"attempting to shove \n"
+"many streams in or out one socket -- that can't scale when you have alot "
+"of connections!"
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/bob.html:108
+msgid ""
+"What is also nice about this particular interface is that writing "
+"anything to interface \n"
+"to it, is much much easier than SAM. There is no other processing to do "
+"after the set up.\n"
+"It's configuration is so simple, that very simple tools, such as nc "
+"(netcat) can be used \n"
+"to point to some application. The value there is that one could schedule "
+"up and down times \n"
+"for an application, and not have to change the application to do that, or"
+" to even have \n"
+"to stop that application. Instead, you can literally \"unplug\" the "
+"destination, and \n"
+"\"plug it in\" again. As long as the same IP/port addresses and "
+"destination keys are used \n"
+"when bringing the bridge up, the normal TCP application won't care, and "
+"won't notice.\n"
+"It will simply be fooled -- the destinations are not reachable, and that "
+"nothing is coming in."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/bob.html:120
+msgid ""
+"For the following example, we'll setup a very simple local loopback "
+"connection, \n"
+"with two destinations. Destination \"mouth\" will be the CHARGEN service "
+"from \n"
+"the INET superserver daemon. Destination \"ear\" will be a local port "
+"that you\n"
+"can telnet into, and watch the pretty ASCII test puke forth."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/bob.html:128
+msgid "EXAMPLE SESSION DIALOGUE -- simple telnet 127.0.0.1 2827 works"
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/bob.html:129
+msgid "Application"
+msgstr "Aplicação"
+
+#: i2p2www/pages/site/docs/api/bob.html:130
+msgid "BOB's Command response."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/bob.html:132
+#: i2p2www/pages/site/docs/api/bob.html:144
+#: i2p2www/pages/site/docs/api/bob.html:164
+#: i2p2www/pages/site/docs/api/bob.html:272
+#: i2p2www/pages/site/docs/api/bob.html:284
+#: i2p2www/pages/site/docs/api/bob.html:299
+msgid "FROM"
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/bob.html:132
+#: i2p2www/pages/site/docs/api/bob.html:144
+#: i2p2www/pages/site/docs/api/bob.html:164
+#: i2p2www/pages/site/docs/api/bob.html:272
+#: i2p2www/pages/site/docs/api/bob.html:284
+#: i2p2www/pages/site/docs/api/bob.html:299
+msgid "TO"
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/bob.html:132
+#: i2p2www/pages/site/docs/api/bob.html:144
+#: i2p2www/pages/site/docs/api/bob.html:164
+#: i2p2www/pages/site/docs/api/bob.html:272
+#: i2p2www/pages/site/docs/api/bob.html:284
+#: i2p2www/pages/site/docs/api/bob.html:299
+msgid "DIALOGUE"
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/bob.html:139
+msgid "MAKE NOTE OF THE ABOVE DESTINATION KEY, YOURS WILL BE DIFFERENT!"
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/bob.html:153
+msgid ""
+"At this point, there was no error, a destination with a nickname of "
+"\"mouth\" \n"
+"is set up. When you contact the destination provided, you actually "
+"connect \n"
+"to the CHARGEN service on 19/TCP."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/bob.html:159
+msgid "Now for the other half, so that we can actually contact this destination."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/bob.html:179
+msgid ""
+"Now all we need to do is telnet into 127.0.0.1, port 37337,\n"
+"send the destination key or host address from addressbook we want to "
+"contact.\n"
+"In this case, we want to contact \"mouth\", all we do is paste in the\n"
+"key and it goes."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/bob.html:186
+msgid ""
+"NOTE: The \"quit\" command in the command channel does NOT "
+"disconnect the tunnels like SAM."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/bob.html:203
+msgid "After a few virtual miles of this spew, press Control-]"
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/bob.html:215
+msgid "Here is what happened..."
+msgstr "Eis aqui o que acontece..."
+
+#: i2p2www/pages/site/docs/api/bob.html:223
+msgid "You can connect to EEPSITES too!"
+msgstr "Você também pode se conectar a EEPSITES!"
+
+#: i2p2www/pages/site/docs/api/bob.html:256
+msgid ""
+"Pretty cool isn't it? Try some other well known EEPSITES if you like, "
+"nonexistent ones, \n"
+"etc, to get a feel for what kind of output to expect in different "
+"situations. \n"
+"For the most part, it is suggested that you ignore any of the error "
+"messages. \n"
+"They would be meaningless to the application, and are only presented for "
+"human debugging."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/bob.html:263
+msgid "Let's put down our destinations now that we are all done with them."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/bob.html:267
+msgid "First, lets see what destination nicknames we have."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/bob.html:279
+msgid "Alright, there they are. First, let's remove \"mouth\"."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/bob.html:293
+msgid ""
+"Now to remove \"ear\", note that this is what happens when you type too "
+"fast,\n"
+"and shows you what typical ERROR messages looks like."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/bob.html:312
+msgid ""
+"I won't bother to show an example of the receiver end of a bridge\n"
+"because it is very simple. There are two possible settings for it, and\n"
+"it is toggled with the \"quiet\" command."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/bob.html:318
+msgid ""
+"The default is NOT quiet, and the first data to come into your\n"
+"listening socket is the destination that is making the contact. It is a\n"
+"single line consisting of the BASE64 address followed by a newline.\n"
+"Everything after that is for the application to actually consume."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/bob.html:325
+msgid ""
+"In quiet mode, think of it as a regular Internet connection. No\n"
+"extra data comes in at all. It's just as if you are plain connected to\n"
+"the regular Internet. This mode allows a form of transparency much like\n"
+"is available on the router console tunnel settings pages, so that you\n"
+"can use BOB to point a destination at a web server, for example, and\n"
+"you would not have to modify the web server at all."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/bob.html:334
+msgid ""
+"The advantage with using BOB for this is as discussed\n"
+"previously. You could schedule random uptimes for the application,\n"
+"redirect to a different machine, etc. One use of this may be something\n"
+"like wanting to try to goof up router-to-destination upness guessing.\n"
+"You could stop and start the destination with a totally different\n"
+"process to make random up and down times on services. That way you\n"
+"would only be stopping the ability to contact such a service, and not\n"
+"have to bother shutting it down and restarting it. You could redirect\n"
+"and point to a different machine on your LAN while you do updates, or\n"
+"point to a set of backup machines depending on what is running, etc,\n"
+"etc. Only your imagination limits what you could do with BOB."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/datagrams.html:6
+msgid "Datagram Overview"
+msgstr "Uma visão geral do datagrama"
+
+#: i2p2www/pages/site/docs/api/datagrams.html:7
+#, python-format
+msgid ""
+"Datagrams build upon the base I2CP to provide "
+"authenticated\n"
+"and repliable messages in a standard format. This lets applications "
+"reliably read\n"
+"the \"from\" address out of a datagram and know that the address really "
+"sent the\n"
+"message. This is necessary for some applications since the base I2P "
+"message is\n"
+"completely raw - it has no \"from\" address (unlike IP packets). In "
+"addition, the\n"
+"message and sender are authenticated by signing the payload."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/datagrams.html:16
+#, python-format
+msgid ""
+"Datagrams, like streaming library packets,\n"
+"are an application-level construct.\n"
+"These protocols are independent of the low-level transports;\n"
+"the protocols are converted to I2NP messages by the router, and\n"
+"either protocol may be carried by either transport."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/datagrams.html:25
+msgid "Application Guide"
+msgstr "Guia de aplicações"
+
+#: i2p2www/pages/site/docs/api/datagrams.html:26
+#, python-format
+msgid ""
+"Applications written in Java may use the \n"
+"datagram API,\n"
+"while applications in other languages \n"
+"can use SAM's datagram support.\n"
+"There is also limited support in i2ptunnel in the SOCKS proxy,\n"
+"the 'streamr' tunnel types, and udpTunnel classes."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/datagrams.html:37
+msgid "Datagram Length"
+msgstr "Comprimento do datagrama"
+
+#: i2p2www/pages/site/docs/api/datagrams.html:38
+msgid ""
+"The application designer should carefully consider the tradeoff of "
+"repliable vs. non-repliable\n"
+"datagrams. Also, the datagram size will affect reliability, due to tunnel"
+" fragmentation into 1KB\n"
+"tunnel messages. The more message fragments, the more likely that one of "
+"them will be dropped\n"
+"by an intermediate hop. Messages larger than a few KB are not "
+"recommended.\n"
+"Over about 10 KB, the delivery probablility drops dramatically.\n"
+"Messages over 16 KB cannot be delivered over NTCP, dropping delivery "
+"chances even more."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/datagrams.html:47
+#, python-format
+msgid ""
+"Also note that the various overheads added by lower layers, in particular"
+" asymmetric\n"
+"ElGamal/AES, place a large burden on "
+"intermittent messages\n"
+"such as used by a Kademlia-over-UDP application. The implementations are "
+"currently tuned\n"
+"for frequent traffic using the streaming library. There are a high number"
+"\n"
+"of session tags delivered, and a short session tag lifetime, for example."
+"\n"
+"There are currently no configuration parameters available within I2CP to "
+"tune\n"
+"the ElGamal Session Tag parameters."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/datagrams.html:57
+msgid "I2CP Protocol Number and Ports"
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/datagrams.html:58
+msgid ""
+"The standard I2CP protocol number for datagrams is PROTO_DATAGRAM (17).\n"
+"Applications may or may not choose to set the\n"
+"protocol in the I2CP header. It is not set by default.\n"
+"It must be set to demultiplex datagram and streaming traffic received on "
+"the same Destination."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/datagrams.html:65
+#, python-format
+msgid ""
+"As datagrams are not connection-oriented, the application may require\n"
+"port numbers to correlate datagrams with particular peers or "
+"communications sessions,\n"
+"as is traditional with UDP over IP.\n"
+"Applications may add 'from' and 'to' ports to the I2CP (gzip) header as "
+"described in\n"
+"the I2CP page."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/datagrams.html:73
+#, python-format
+msgid ""
+"There is no method within the datagram API to specify whether it is non-"
+"repliable (raw)\n"
+"or repliable. The application should be designed to expect the "
+"appropriate type.\n"
+"The I2CP protocol number or port should be used by the application to\n"
+"indicate datagram type.\n"
+"The I2CP protocol numbers PROTO_DATAGRAM (signed) and PROTO_DATAGRAM_RAW "
+"are defined in the\n"
+"I2PSession API\n"
+"for this purpose. A common design pattern in client/server datagram "
+"applications is to\n"
+"use signed datagrams for a request which includes a nonce, and use a raw "
+"datagram\n"
+"for the reply, returning the nonce from the request."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/datagrams.html:85
+#, python-format
+msgid ""
+"The protocols and ports may be set in I2CP's\n"
+"I2PSession API,\n"
+"as implemented in\n"
+"I2PSessionMuxedImpl."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/datagrams.html:93
+#: i2p2www/pages/site/docs/api/streaming.html:381
+msgid "Data Integrity"
+msgstr "Integridade dos dados"
+
+#: i2p2www/pages/site/docs/api/datagrams.html:94
+#, python-format
+msgid ""
+"Data integrity is assured by the gzip CRC-32 checksum implemented in\n"
+"the I2CP layer.\n"
+"There is no checksum field in the datagram protocol."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/datagrams.html:100
+#: i2p2www/pages/site/docs/api/streaming.html:389
+msgid "Packet Encapsulation"
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/datagrams.html:101
+#, python-format
+msgid ""
+"Each datagram is sent through I2P as a single message (or as an "
+"individual clove in a\n"
+"Garlic Message).\n"
+"Message encapsulation is implemented in the underlying\n"
+"I2CP,\n"
+"I2NP, and\n"
+"tunnel message layers.\n"
+"There is no packet delimiter mechanism or length field in the datagram "
+"protocol."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/datagrams.html:114
+#: i2p2www/pages/site/docs/spec/datagrams.html:10
+#: i2p2www/pages/site/docs/transport/ssu.html:567
+msgid "Specification"
+msgstr "Especificação"
+
+#: i2p2www/pages/site/docs/api/datagrams.html:116
+msgid "See the Datagrams Specification page."
+msgstr "Ver a página da Especificação de Datagramas."
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:4
+msgid "I2PControl - Remote Control Service"
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:5
+#, python-format
+msgid ""
+"I2P enables a JSONRPC2 interface via the plugin I2PControl.\n"
+"The aim of the interface is to provide simple way to interface with a "
+"running I2P node. A client, itoopie, has been developed in parallel.\n"
+"The JSONRPC2 implementation for the client as well as the plugin is "
+"provided by the java libraries JSON-RPC 2.0. \n"
+"A list of implementations of JSON-RPC for various languages can be found "
+"at the JSON-RPC "
+"wiki."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:12
+msgid "I2PControl is by default listening on localhost:7650"
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:14
+msgid "API, version 1."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:15
+msgid "Parameters are only provided in a named way (maps)."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:19
+msgid "JSON-RPC 2 format"
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:21
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:27
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:40
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:50
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:59
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:69
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:84
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:137
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:154
+msgid "Request:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:23
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:32
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:44
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:54
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:64
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:75
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:101
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:145
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:169
+msgid "Response:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:26
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:28
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:29
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:33
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:34
+#: i2p2www/pages/site/docs/protocol/i2cp.html:99
+#: i2p2www/pages/site/docs/protocol/i2cp.html:442
+#: i2p2www/pages/site/docs/spec/common-structures.html:16
+#: i2p2www/pages/site/docs/spec/common-structures.html:26
+#: i2p2www/pages/site/docs/spec/common-structures.html:37
+#: i2p2www/pages/site/docs/spec/common-structures.html:49
+#: i2p2www/pages/site/docs/spec/common-structures.html:64
+#: i2p2www/pages/site/docs/spec/common-structures.html:77
+#: i2p2www/pages/site/docs/spec/common-structures.html:90
+#: i2p2www/pages/site/docs/spec/common-structures.html:102
+#: i2p2www/pages/site/docs/spec/common-structures.html:114
+#: i2p2www/pages/site/docs/spec/common-structures.html:126
+#: i2p2www/pages/site/docs/spec/common-structures.html:138
+#: i2p2www/pages/site/docs/spec/common-structures.html:150
+#: i2p2www/pages/site/docs/spec/common-structures.html:162
+#: i2p2www/pages/site/docs/spec/common-structures.html:174
+#: i2p2www/pages/site/docs/spec/common-structures.html:227
+#: i2p2www/pages/site/docs/spec/common-structures.html:299
+#: i2p2www/pages/site/docs/spec/common-structures.html:348
+#: i2p2www/pages/site/docs/spec/common-structures.html:400
+#: i2p2www/pages/site/docs/spec/common-structures.html:445
+#: i2p2www/pages/site/docs/spec/common-structures.html:582
+#: i2p2www/pages/site/docs/spec/common-structures.html:638
+msgid "Description"
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:30
+msgid ""
+"Token used for authenticating every request (excluding the 'Authenticate'"
+" RPC method)"
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:38
+msgid "Implemented methods"
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:39
+msgid ""
+"Creates and returns an authentication token used for further "
+"communication."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:41
+msgid "The version of the I2PControl API used by the client."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:42
+msgid "The password used for authenticating against the remote server."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:45
+msgid "The primary I2PControl API version implemented by the server."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:46
+msgid "The token used for further communication."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:49
+msgid "Echoes the value of the echo key, used for debugging and testing."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:51
+msgid "Value will be returned in response."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:52
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:62
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:73
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:99
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:143
+msgid ""
+"Token used for authenticating the client. Is provided by the server via "
+"the 'Authenticate' RPC method."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:55
+msgid "Value of the key 'echo' in the request."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:58
+msgid ""
+"Fetches rateStat from router statManager. Creates stat if not already "
+"created."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:60
+#, python-format
+msgid ""
+"Determines which rateStat to fetch, see ratestats."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:61
+msgid "Determines which period a stat is fetched for. Measured in ms."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:65
+msgid "Returns the average value for the reuested rateStat and period."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:68
+msgid "Manages I2PControl. Ports, passwords and the like."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:70
+msgid ""
+"Sets a new listen address for I2PControl (only 127.0.0.1 and 0.0.0.0 are "
+"implemented in I2PControl currently)."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:71
+msgid ""
+"Sets a new password for I2PControl, all Authentication tokens will be "
+"revoked."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:72
+msgid "Switches which port I2PControl will listen for connections on."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:76
+msgid "Returned if address was changed"
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:77
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:78
+msgid "Returned if setting was changed"
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:79
+msgid "Returns true if any changes were made."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:80
+msgid "Returns true if any changes requiring a restart to take effect were made."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:83
+msgid "Fetches basic information about the I2P router. Uptime, version etc."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:102
+msgid "What the status of the router is."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:103
+msgid "What the uptime of the router is in ms."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:104
+msgid "What version of I2P the router is running."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:105
+msgid "The 1 second average inbound bandwidth in Bps."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:106
+msgid "The 15 second average inbound bandwidth in Bps."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:107
+msgid "The 1 second average outbound bandwidth in Bps."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:108
+msgid "The 15 second average outbound bandwidth in Bps."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:109
+msgid "What the current network status is. According to the below enum:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:128
+msgid "How many tunnels on the I2P net are we participating in."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:129
+msgid "How many peers have we communicated with recently."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:130
+msgid "How many peers are considered 'fast'."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:131
+msgid "How many peers are considered 'high capacity'."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:132
+msgid "Is the router reseeding hosts to its NetDB?"
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:133
+msgid "How many peers are known to us (listed in our NetDB)."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:136
+msgid "Manages I2P router restart/shutdown."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:138
+msgid ""
+"Initiates a router reseed, fetching peers into our NetDB from a remote "
+"host."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:139
+msgid "Restarts the router."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:140
+msgid ""
+"Restarts the router gracefully (waits for participating tunnels to "
+"expire)."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:141
+msgid "Shuts down the router."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:142
+msgid ""
+"Shuts down the router gracefully (waits for participating tunnels to "
+"expire)."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:146
+msgid "If requested, verifies that a reseed has been initiated."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:147
+msgid "If requested, verifies that a restart has been initiated."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:148
+msgid "If requested, verifies that a graceful restart has been initiated."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:149
+msgid "If requested, verifies that a shutdown has been initiated"
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:150
+msgid "If requested, verifies that a graceful shutdown has been initiated"
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:153
+msgid "Fetches or sets various network related settings. Ports, addresses etc."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:155
+msgid ""
+"What port is used for the TCP transport. If null is submitted, current "
+"setting will be returned."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:156
+msgid ""
+"What hostname is used for the TCP transport. If null is submitted, "
+"current setting will be returned."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:157
+msgid ""
+"Use automatically detected ip for TCP transport. If null is submitted, "
+"current setting will be returned."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:158
+msgid ""
+"What port is used for the UDP transport. If null is submitted, current "
+"setting will be returned."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:159
+msgid ""
+"What hostname is used for the UDP transport. If null is submitted, "
+"current setting will be returned."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:160
+msgid ""
+"Which methods should be used for detecting the ip address of the UDP "
+"transport. If null is submitted, current setting will be returned."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:161
+msgid "What ip has been detected by the UDP transport."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:162
+msgid "Is UPnP enabled. If null is submitted, current setting will be returned."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:163
+msgid ""
+"How many percent of bandwidth is usable for participating tunnels. If "
+"null is submitted, current setting will be returned."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:164
+msgid ""
+"How many KB/s of inbound bandwidth is allowed. If null is submitted, "
+"current setting will be returned."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:165
+msgid ""
+"How many KB/s of outbound bandwidth is allowed. If null is submitted, "
+"current setting will be returned."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:166
+msgid ""
+"Is laptop mode enabled (change router identity and UDP port when IP "
+"changes ). If null is submitted, current setting will be returned."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:167
+msgid ""
+"Token used for authenticating the client. Is provided by the server via "
+"the 'Authenticate' RPC method. If null is submitted, current setting will"
+" be returned."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:170
+msgid "If requested, returns the port used for the TCP transport."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:171
+msgid "If requested, returns the hostname used for the TCP transport."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:172
+msgid ""
+"If requested, returns the method used for automatically detecting ip for "
+"the TCP transport."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:173
+msgid "If requested, returns the port used for the UDP transport."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:174
+msgid "If requested, returns the hostname used for the UDP transport."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:175
+msgid ""
+"If requested, returns methods used for detecting the ip address of the "
+"UDP transport."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:176
+msgid "If requested, returns what ip has been detected by the UDP transport."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:177
+msgid "If requested, returns the UPNP setting."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:178
+msgid ""
+"If requested, returns how many percent of bandwidth is usable for "
+"participating tunnels."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:179
+msgid "If requested, returns how many KB/s of inbound bandwidth is allowed."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:180
+msgid "If requested, returns how many KB/s of outbound bandwidth is allowed."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:181
+msgid "If requested, returns the laptop mode."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:182
+msgid "Have the provided settings been saved."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:183
+msgid "Is a restart needed for the new settings to be used."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:186
+msgid "denotes an optional value."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:187
+msgid "denotes a possibly occuring return value"
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:189
+msgid "Error codes"
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:190
+msgid "Standard JSON-RPC2 error codes."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:191
+msgid "JSON parse error."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:192
+msgid "Invalid request."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:193
+msgid "Method not found."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:194
+msgid "Invalid parameters."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:195
+msgid "Internal error."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:197
+msgid "I2PControl specific error codes."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:198
+msgid "Invalid password provided."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:199
+msgid "No authentication token presented."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:200
+msgid "Authentication token doesn't exist."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:201
+msgid "The provided authentication token was expired and will be removed."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:202
+msgid ""
+"The version of the I2PControl API used wasn't specified, but is required "
+"to be specified."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:203
+msgid ""
+"The version of the I2PControl API specified is not supported by "
+"I2PControl."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2ptunnel.html:13
+#, python-format
+msgid ""
+"I2PTunnel is a tool for interfacing with and providing services on I2P.\n"
+"Destination of an I2PTunnel can be defined using a hostname,\n"
+"Base32, or a full 516-byte destination "
+"key.\n"
+"An established I2PTunnel will be available on your client machine as "
+"localhost:port.\n"
+"If you wish to provide a service on I2P network, you simply create "
+"I2PTunnel to the\n"
+"appropriate ip_address:port. A corresponding 516-byte destination key "
+"will be generated\n"
+"for the service and it will become avaliable throughout I2P.\n"
+"A web interface for I2PTunnel management is avaliable on\n"
+"localhost:7657/i2ptunnel/."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2ptunnel.html:25
+msgid "Default Services"
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2ptunnel.html:26
+msgid "Server tunnels"
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2ptunnel.html:28
+msgid ""
+"I2P Webserver - A tunnel pointed to a Jetty webserver run\n"
+"on localhost:7658 for convenient "
+"and quick hosting on I2P.\n"
+"
The document root is:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2ptunnel.html:36
+msgid "Client tunnels"
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2ptunnel.html:38
+msgid ""
+"A HTTP proxy used for browsing I2P and the regular internet anonymously "
+"through I2P. \n"
+"Browsing internet through I2P uses a random proxy specified by the "
+"\"Outproxies:\" option."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2ptunnel.html:42
+msgid "An IRC tunnel to the default anonymous IRC network, Irc2P."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2ptunnel.html:43
+#, python-format
+msgid ""
+"The anonymous monotone\n"
+"sourcecode repository for I2P"
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2ptunnel.html:47
+#, python-format
+msgid ""
+"A SMTP service provided by postman at %(postman)s"
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2ptunnel.html:50
+#, python-format
+msgid ""
+"The accompanying POP sevice of postman at %(postman)s"
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2ptunnel.html:55
+msgid "Client Modes"
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2ptunnel.html:56
+#: i2p2www/pages/site/docs/api/i2ptunnel.html:138
+msgid "Standard"
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2ptunnel.html:57
+msgid ""
+"Opens a local TCP port that connects to a service (like HTTP, FTP or "
+"SMTP) on a destination inside of I2P.\n"
+"The tunnel is directed to a random host from the comma seperated (\", \")"
+" list of destinations."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2ptunnel.html:63
+msgid ""
+"A HTTP-client tunnel. The tunnel connects to the destination specified by"
+" the URL\n"
+"in a HTTP request. Supports proxying onto internet if an outproxy is "
+"provided. Strips HTTP connections of the following headers:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2ptunnel.html:68
+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:76
+msgid ""
+"HTTP client/server tunnels are via I2Ptunnel force-enabling compression "
+"via the following http headers:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2ptunnel.html:83
+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:87
+msgid "Outproxy:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2ptunnel.html:88
+msgid "Internal I2P use:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2ptunnel.html:93
+msgid ""
+"Creates a connection to a random IRC server specified by the comma "
+"seprated (\", \") \n"
+"list of destinations. Only a whitelisted subset of IRC commands are "
+"allowed due to anonymity concerns."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2ptunnel.html:97
+msgid "Whitelist:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2ptunnel.html:112
+msgid "Enables using the I2P router as a SOCKS proxy."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2ptunnel.html:117
+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:123
+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:129
+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:137
+msgid "Server Modes"
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2ptunnel.html:139
+msgid "Creates a destination to a local ip:port with an open TCP port."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2ptunnel.html:144
+msgid ""
+"Creates a destination to a local HTTP server ip:port. Supports gzip for "
+"requests with \n"
+"Accept-encoding: x-i2p-gzip, replies with Content-encoding: x-i2p-gzip in"
+" such a request."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2ptunnel.html:150
+msgid ""
+"Functions as both a I2PTunnel HTTP Server, and a I2PTunnel HTTP client "
+"with no outproxying\n"
+"capabilities. An example application would be a web application that does"
+" client-type\n"
+"requests, or loopback-testing an eepsite as a diagnostic tool."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2ptunnel.html:157
+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:163
+msgid ""
+"A UDP-client that connects to a media server is created. The UDP-Client "
+"is coupled with a Streamr server I2PTunnel."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/ministreaming.html:2
+#: i2p2www/pages/site/docs/api/ministreaming.html:17
+msgid "Ministreaming Library"
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/ministreaming.html:5
+msgid "Note"
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/ministreaming.html:7
+#, python-format
+msgid ""
+"The ministreaming library has been enhanced and extended by the\n"
+"\"full\" streaming library.\n"
+"Ministreaming is deprecated and is incompatible with today's "
+"applications.\n"
+"The following documentation is old.\n"
+"Also note that streaming extends ministreaming in the same Java package "
+"(net.i2p.client.streaming),\n"
+"so the current API documentation contains both.\n"
+"Obsolete ministreaming classes and methods are clearly marked as "
+"deprecated in the Javadocs."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/ministreaming.html:19
+#, python-format
+msgid ""
+"\n"
+"The ministreaming library is a layer on top of the core \n"
+"I2CP that allows reliable, in order, and "
+"authenticated streams\n"
+"of messages to operate across an unreliable, unordered, and "
+"unauthenticated \n"
+"message layer. Just like the TCP to IP relationship, this streaming \n"
+"functionality has a whole series of tradeoffs and optimizations "
+"available, but\n"
+"rather than embed that functionality into the base I2P code, it has been "
+"factored\n"
+"off into its own library both to keep the TCP-esque complexities separate"
+" and to\n"
+"allow alternative optimized implementations."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/ministreaming.html:30
+#, python-format
+msgid ""
+"The ministreaming library was written by mihi as a part of his \n"
+"I2PTunnel application and then factored out"
+" and released\n"
+"under the BSD license. It is called the \"mini\"streaming library "
+"because it makes\n"
+"some simplifications in the implementation, while a more robust streaming"
+" library\n"
+"could be further optimized for operation over I2P. The two main issues "
+"with \n"
+"the ministreaming library are its use of the traditional TCP two phase \n"
+"establishment protocol and the current fixed window size of 1. The "
+"establishment\n"
+"issue is minor for long lived streams, but for short ones, such as quick "
+"HTTP\n"
+"requests, the impact can be significant. As "
+"for the window\n"
+"size, the ministreaming library doesn't maintain any ID or ordering "
+"within the \n"
+"messages sent (or include any application level ACK or SACK), so it must "
+"wait \n"
+"on average twice the time it takes to send a message before sending "
+"another."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/ministreaming.html:45
+#, python-format
+msgid ""
+"Even with those issues, the ministreaming library performs quite well in "
+"many\n"
+"situations, and its API\n"
+"is both quite simple and capable of remaining unchanged as different "
+"streaming\n"
+"implementations are introduced. The library is deployed in its own \n"
+"ministreaming.jar.\n"
+"Developers in Java who would like to use it can\n"
+"access the API directly, while developers in other languages can use it "
+"through\n"
+"SAM's streaming support."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/socks.html:4
+msgid "SOCKS and SOCKS proxies"
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/socks.html:5
+msgid ""
+"\n"
+"The SOCKS proxy is working as of release 0.7.1. SOCKS 4/4a/5 are "
+"supported.\n"
+"Enable SOCKS by creating a SOCKS client tunnel in i2ptunnel.\n"
+"Both shared-clients and non-shared are supported.\n"
+"There is no SOCKS outproxy so it is of limited use."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/socks.html:12
+#, python-format
+msgid ""
+"\n"
+"As it says on the FAQ:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/socks.html:15
+msgid ""
+"Many applications leak sensitive\n"
+"information that could identify you on the Internet. I2P only filters\n"
+"connection data, but if the program you intend to run sends this\n"
+"information as content, I2P has no way to protect your anonymity. For\n"
+"example, some mail applications will send the IP address of the machine\n"
+"they are running on to a mail server. There is no way for I2P to filter\n"
+"this, thus using I2P to 'socksify' existing applications is possible, but"
+"\n"
+"extremely dangerous."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/socks.html:25
+msgid "And quoting from a 2005 email:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/socks.html:28
+msgid ""
+"... there is a reason why human and\n"
+"others have both built and abandoned the SOCKS proxies. Forwarding\n"
+"arbitrary traffic is just plain unsafe, and it behooves us as\n"
+"developers of anonymity and security software to have the safety of\n"
+"our end users foremost in our minds."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/socks.html:36
+msgid ""
+"Hoping that we can simply strap an arbitrary client on top of I2P\n"
+"without auditing both its behavior and its exposed protocols for\n"
+"security and anonymity is naive. Pretty much *every* application\n"
+"and protocol violates anonymity, unless it was designed for it\n"
+"specifically, and even then, most of those do too. That's the\n"
+"reality. End users are better served with systems designed for\n"
+"anonymity and security. Modifying existing systems to work in\n"
+"anonymous environments is no small feat, orders of magnitude more\n"
+"work that simply using the existing I2P APIs."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/socks.html:48
+msgid ""
+"The SOCKS proxy\n"
+"supports standard addressbook names, but not Base64 destinations.\n"
+"Base32 hashes should work as of release 0.7.\n"
+"It supports outgoing connections only, i.e. an I2PTunnel Client.\n"
+"UDP support is stubbed out but not working yet.\n"
+"Outproxy selection by port number is stubbed out."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/socks.html:57
+#: i2p2www/pages/site/docs/how/tunnel-routing.html:281
+msgid "See Also"
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/socks.html:59
+#, python-format
+msgid ""
+"The notes for Meeting 81 and\n"
+"Meeting 82 in March 2004."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/socks.html:69
+msgid "If You Do Get Something Working"
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/socks.html:70
+msgid ""
+"Please let us know. And please provide substantial warnings about the\n"
+"risks of socks proxies."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/streaming.html:3
+#: i2p2www/pages/site/docs/spec/streaming.html:3
+msgid "July 2013"
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/streaming.html:8
+#, python-format
+msgid ""
+"The streaming library is technically part of the \"application\" layer,\n"
+"as it is not a core router function.\n"
+"In practice, however, it provides a vital function for almost all\n"
+"existing I2P applications, by providing a TCP-like\n"
+"streams over I2P, and allowing existing apps to be easily ported to I2P.\n"
+"The other end-to-end transport library for client communication is the\n"
+"datagram library."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/streaming.html:18
+#, python-format
+msgid ""
+"The streaming library is a layer on top of the core \n"
+"I2CP API that allows reliable, in-order, and "
+"authenticated streams\n"
+"of messages to operate across an unreliable, unordered, and "
+"unauthenticated \n"
+"message layer. Just like the TCP to IP relationship, this streaming \n"
+"functionality has a whole series of tradeoffs and optimizations "
+"available, but\n"
+"rather than embed that functionality into the base I2P code, it has been "
+"factored\n"
+"off into its own library both to keep the TCP-esque complexities separate"
+" and to\n"
+"allow alternative optimized implementations."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/streaming.html:29
+msgid ""
+"In consideration of the relatively high cost of messages, \n"
+"the streaming library's protocol for scheduling and delivering those "
+"messages has been optimized to\n"
+"allow individual messages passed to contain as much information as is "
+"available.\n"
+"For instance, a small HTTP transaction proxied through the streaming "
+"library can\n"
+"be completed in a single round trip - the first messages bundle a SYN, "
+"FIN, and\n"
+"the small HTTP request payload, and the reply bundles the SYN,\n"
+"FIN, ACK, and the HTTP response payload. While an additional\n"
+"ACK must be transmitted to tell the HTTP server that the SYN/FIN/ACK has "
+"been\n"
+"received, the local HTTP proxy can often deliver the full response to the"
+" browser \n"
+"immediately."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/streaming.html:42
+msgid ""
+"The streaming library bears much resemblance to an \n"
+"abstraction of TCP, with its sliding windows, congestion control "
+"algorithms\n"
+"(both slow start and congestion avoidance), and general packet behavior "
+"(ACK,\n"
+"SYN, FIN, RST, rto calculation, etc)."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/streaming.html:49
+msgid ""
+"The streaming library is\n"
+"a robust library\n"
+"which is optimized for operation over I2P.\n"
+"It has a one-phase setup, and\n"
+"it contains a full windowing implementation."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/streaming.html:58
+msgid "API"
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/streaming.html:60
+#, python-format
+msgid ""
+"The streaming library API provides a standard socket paradigm to Java "
+"applications.\n"
+"The lower-level I2CP API is completely hidden, "
+"except that\n"
+"applications may pass I2CP parameters "
+"through the\n"
+"streaming library, to be interpreted by I2CP."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/streaming.html:67
+#, python-format
+msgid ""
+"The standard interface to the streaming lib is for the application to use"
+" the\n"
+"I2PSocketManagerFactory to create an\n"
+"I2PSocketManager. The application then asks "
+"the\n"
+"socket manager for an I2PSession, which will "
+"cause\n"
+"a connection to the router via I2CP. The "
+"application\n"
+"can then setup connections with an I2PSocket "
+"or\n"
+"receive connections with an I2PServerSocket."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/streaming.html:82
+#, python-format
+msgid "Here are the full streaming library Javadocs."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/streaming.html:86
+msgid "For a good example of usage, see the i2psnark code."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/streaming.html:91
+msgid "Options and Defaults"
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/streaming.html:92
+#, python-format
+msgid ""
+"The options and current default values are listed below.\n"
+"Options are case-sensitive and may be set for the whole router, for a "
+"particular client, or for an individual socket on a\n"
+"per-connection basis.\n"
+"Many values are tuned for HTTP performance over typical I2P conditions. "
+"Other applications such\n"
+"as peer-to-peer services are strongly encouraged to\n"
+"modify as necessary, by setting the options and passing them via the call"
+" to\n"
+"I2PSocketManagerFactory.createManager(_i2cpHost,"
+" _i2cpPort, opts).\n"
+"Time values are in ms."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/streaming.html:103
+#, python-format
+msgid ""
+"Note that higher-layer APIs, such as SAM,\n"
+"BOB, and I2PTunnel,"
+"\n"
+"may override these defaults with their own defaults.\n"
+"Also note that many options only apply to servers listening for incoming "
+"connections."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/streaming.html:110
+msgid ""
+"As of release 0.9.1, most, but not all, options may be changed on an "
+"active socket manager or session.\n"
+"See the javadocs for details."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/streaming.html:117
+#: i2p2www/pages/site/docs/protocol/i2cp.html:94
+#: i2p2www/pages/site/docs/protocol/i2cp.html:437
+msgid "Option"
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/streaming.html:117
+#: i2p2www/pages/site/docs/protocol/i2cp.html:98
+#: i2p2www/pages/site/docs/protocol/i2cp.html:441
+msgid "Default"
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/streaming.html:117
+#: i2p2www/pages/site/docs/how/elgamal-aes.html:267
+#: i2p2www/pages/site/docs/how/peer-selection.html:282
+#: i2p2www/pages/site/docs/spec/common-structures.html:58
+#: i2p2www/pages/site/docs/spec/common-structures.html:203
+#: i2p2www/pages/site/docs/spec/common-structures.html:257
+#: i2p2www/pages/site/docs/spec/common-structures.html:340
+#: i2p2www/pages/site/docs/spec/common-structures.html:434
+#: i2p2www/pages/site/docs/spec/common-structures.html:542
+#: i2p2www/pages/site/docs/spec/common-structures.html:620
+#: i2p2www/pages/site/docs/spec/common-structures.html:722
+#: i2p2www/pages/site/docs/spec/datagrams.html:30
+#: i2p2www/pages/site/docs/spec/datagrams.html:89
+msgid "Notes"
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/streaming.html:119
+msgid ""
+"Comma- or space-separated list of Base64 peer Hashes used for either "
+"access list or blacklist."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/streaming.html:121
+#: i2p2www/pages/site/docs/api/streaming.html:127
+#: i2p2www/pages/site/docs/api/streaming.html:133
+#: i2p2www/pages/site/docs/api/streaming.html:140
+#: i2p2www/pages/site/docs/api/streaming.html:152
+#: i2p2www/pages/site/docs/api/streaming.html:163
+#: i2p2www/pages/site/docs/api/streaming.html:192
+#: i2p2www/pages/site/docs/api/streaming.html:200
+#: i2p2www/pages/site/docs/api/streaming.html:220
+#: i2p2www/pages/site/docs/api/streaming.html:237
+#: i2p2www/pages/site/docs/api/streaming.html:249
+#: i2p2www/pages/site/docs/api/streaming.html:255
+#: i2p2www/pages/site/docs/api/streaming.html:261
+#: i2p2www/pages/site/docs/api/streaming.html:275
+#: i2p2www/pages/site/docs/api/streaming.html:282
+#: i2p2www/pages/site/docs/api/streaming.html:289
+#: i2p2www/pages/site/docs/api/streaming.html:314
+#: i2p2www/pages/site/docs/api/streaming.html:321
+#: i2p2www/pages/site/docs/api/streaming.html:328
+#, python-format
+msgid "As of release %(release)s."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/streaming.html:125
+msgid "Use the access list as a whitelist for incoming connections."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/streaming.html:131
+msgid "Use the access list as a blacklist for incoming connections."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/streaming.html:145
+msgid "Whether to respond to incoming pings"
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/streaming.html:157
+msgid ""
+"Comma- or space-separated list of Base64 peer Hashes to be\n"
+"blacklisted for incoming connections to ALL destinations in the context.\n"
+"This option must be set in the context properties, NOT in the "
+"createManager() options argument.\n"
+"Note that setting this in the router context will not affect clients "
+"outside the\n"
+"router in a separate JVM and context."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/streaming.html:167
+msgid ""
+"How much transmit data (in bytes) will be accepted that hasn't been "
+"written out yet."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/streaming.html:171
+msgid ""
+"When we're in congestion avoidance, we grow the window size at the rate\n"
+"of 1/(windowSize*factor). In standard TCP, window sizes are"
+" in bytes,\n"
+"while in I2P, window sizes are in messages.\n"
+"A higher number means slower growth."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/streaming.html:178
+msgid ""
+"How long to wait after instantiating a new con \n"
+"before actually attempting to connect. If this is\n"
+"<= 0, connect immediately with no initial data. If greater than 0, "
+"wait\n"
+"until the output stream is flushed, the buffer fills, \n"
+"or that many milliseconds pass, and include any initial data with the SYN."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/streaming.html:186
+msgid ""
+"How long to block on connect, in milliseconds. Negative means "
+"indefinitely. Default is 5 minutes."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/streaming.html:190
+msgid ""
+"Whether to disable warnings in the logs when an incoming connection is "
+"rejected due to connection limits."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/streaming.html:196
+msgid ""
+"Whether to listen only for the streaming protocol.\n"
+"Setting to true will prohibit communication with Destinations earlier "
+"than release 0.7.1\n"
+"(released March 2009). Set to true if running multiple protocols on this "
+"Destination."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/streaming.html:204
+msgid ""
+"(0=noop, 1=disconnect)\n"
+"What to do on an inactivity timeout - do nothing, disconnect, or send a "
+"duplicate ack."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/streaming.html:212
+msgid ""
+"The initial value of the resend delay field in the packet header, times "
+"1000.\n"
+"Not fully implemented; see below."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/streaming.html:217
+msgid ""
+"Initial timeout\n"
+"(if no sharing data available)."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/streaming.html:224
+msgid ""
+"Initial round trip time estimate\n"
+"(if no sharing data available).\n"
+"Disabled as of release 0.9.8; uses actual RTT."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/streaming.html:230
+msgid "if no sharing data available"
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/streaming.html:230
+msgid ""
+"In standard TCP, window sizes are in bytes, while in I2P, window sizes "
+"are in messages."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/streaming.html:242
+msgid ""
+"(0 or negative value means unlimited)\n"
+"This is a total limit for incoming and outgoing combined."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/streaming.html:247
+msgid "Incoming connection limit (per peer; 0 means disabled)"
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/streaming.html:253
+#: i2p2www/pages/site/docs/api/streaming.html:259
+msgid "(per peer; 0 means disabled)"
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/streaming.html:265
+msgid "The MTU in bytes."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/streaming.html:269
+msgid "Maximum number of retransmissions before failure."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/streaming.html:273
+msgid "Incoming connection limit (all peers; 0 means disabled)"
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/streaming.html:279
+#: i2p2www/pages/site/docs/api/streaming.html:286
+msgid ""
+"(all peers; 0 means disabled)\n"
+"Use with caution as exceeding this will disable a server for a long time."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/streaming.html:295
+msgid ""
+"(2=interactive not supported)\n"
+"This doesn't currently do anything, but setting it to a value other than "
+"1 will cause an error."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/streaming.html:300
+msgid "How long to block on read, in milliseconds. Negative means indefinitely."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/streaming.html:304
+msgid ""
+"When we're in slow start, we grow the window size at the rate\n"
+"of 1/(factor). In standard TCP, window sizes are in bytes,\n"
+"while in I2P, window sizes are in messages.\n"
+"A higher number means slower growth."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/streaming.html:311
+#: i2p2www/pages/site/docs/api/streaming.html:318
+#: i2p2www/pages/site/docs/api/streaming.html:325
+msgid ""
+"Ref: RFC 2140. Floating point value.\n"
+"May be set only via context properties, not connection options."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/streaming.html:332
+msgid ""
+"How long to block on write/flush, in milliseconds. Negative means "
+"indefinitely."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/streaming.html:340
+#: i2p2www/pages/site/docs/spec/streaming.html:10
+msgid "Protocol Specification"
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/streaming.html:342
+msgid "See the Streaming Library Specification page."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/streaming.html:346
+msgid "Implementation Details"
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/streaming.html:348
+msgid "Setup"
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/streaming.html:349
+msgid ""
+"The initiator sends a packet with the SYNCHRONIZE flag set. This packet "
+"may contain the initial data as well.\n"
+"The peer replies with a packet with the SYNCHRONIZE flag set. This packet"
+" may contain the initial response data as well."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/streaming.html:354
+msgid ""
+"The initiator may send additional data packets, up to the initial window "
+"size, before receiving the SYNCHRONIZE response.\n"
+"These packets will also have the send Stream ID field set to 0.\n"
+"Recipients must buffer packets received on unknown streams for a short "
+"period of time, as they may\n"
+"arrive out of order, in advance of the SYNCHRONIZE packet."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/streaming.html:361
+msgid "MTU Selection and Negotiation"
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/streaming.html:362
+msgid ""
+"The maximum message size (also called the MTU / MRU) is negotiated to the"
+" lower value supported by\n"
+"the two peers. As tunnel messages are padded to 1KB, a poor MTU selection"
+" will lead to\n"
+"a large amount of overhead.\n"
+"The MTU is specified by the option i2p.streaming.maxMessageSize.\n"
+"The current default MTU of 1730 was chosen to fit precisely into two 1K "
+"I2NP tunnel messages,\n"
+"including overhead for the typical case."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/streaming.html:371
+msgid ""
+"The first message in a connection includes a 387 byte (typical) "
+"Destination added by the streaming layer,\n"
+"and usually a 898 byte (typical) LeaseSet, and Session keys, bundled in "
+"the Garlic message by the router.\n"
+"(The LeaseSet and Session Keys will not be bundled if an ElGamal Session "
+"was previously established).\n"
+"Therefore, the goal of fitting a complete HTTP request in a single 1KB "
+"I2NP message is not always attainable.\n"
+"However, the selection of the MTU, together with careful implementation "
+"of fragmentation\n"
+"and batching strategies in the tunnel gateway processor, are important "
+"factors in network bandwidth,\n"
+"latency, reliability, and efficiency, especially for long-lived "
+"connections."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/streaming.html:382
+#, python-format
+msgid ""
+"Data integrity is assured by the gzip CRC-32 checksum implemented in\n"
+"the I2CP layer.\n"
+"There is no checksum field in the streaming protocol."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/streaming.html:390
+#, python-format
+msgid ""
+"Each packet is sent through I2P as a single message (or as an individual "
+"clove in a\n"
+"Garlic Message). Message encapsulation "
+"is implemented\n"
+"in the underlying I2CP, I2NP, and\n"
+"tunnel message layers. There is no "
+"packet delimiter\n"
+"mechanism or payload length field in the streaming protocol."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/streaming.html:400
+msgid "Windowing"
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/streaming.html:401
+msgid ""
+"The streaming lib uses standard slow-start (exponential window growth) "
+"and congestion avoidance (linear window growth)\n"
+"phases, with exponential backoff.\n"
+"Windowing and acknowledgments use packet count, not byte count."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/streaming.html:408
+msgid "Close"
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/streaming.html:409
+msgid ""
+"Any packet, including one with the SYNCHRONIZE flag set, may have the "
+"CLOSE flag sent as well.\n"
+"The connection is not closed until the peer responds with the CLOSE flag."
+"\n"
+"CLOSE packets may contain data as well."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/streaming.html:416
+msgid "Control Block Sharing"
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/streaming.html:417
+msgid ""
+"The streaming lib supports \"TCP\" Control Block sharing.\n"
+"This shares three important streaming lib parameters\n"
+"(window size, round trip time, round trip time variance)\n"
+"across connections to the same remote peer.\n"
+"This is used for \"temporal\" sharing at connection open/close time,\n"
+"not \"ensemble\" sharing during a connection (See\n"
+"RFC 2140).\n"
+"There is a separate share per ConnectionManager (i.e. per local "
+"Destination)\n"
+"so that there is no information leakage to other Destinations on the\n"
+"same router.\n"
+"The share data for a given peer expires after a few minutes.\n"
+"The following Control Block Sharing parameters can be set per router:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/streaming.html:438
+msgid "Other Parameters"
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/streaming.html:439
+msgid ""
+"The following parameters are hardcoded, but may be of interest for "
+"analysis:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/streaming.html:458
+#: i2p2www/pages/site/docs/how/network-database.html:829
+msgid "History"
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/streaming.html:459
+msgid ""
+"The streaming library has grown organically for I2P - first mihi "
+"implemented the\n"
+"\"mini streaming library\" as part of I2PTunnel, which was limited to a "
+"window\n"
+"size of 1 message (requiring an ACK before sending the next one), and "
+"then it was\n"
+"refactored out into a generic streaming interface (mirroring TCP sockets)"
+" and the\n"
+"full streaming implementation was deployed with a sliding window protocol"
+" and \n"
+"optimizations to take into account the high bandwidth x delay product. "
+"Individual\n"
+"streams may adjust the maximum packet size and other options. The default"
+"\n"
+"message size is selected to fit precisely in two 1K I2NP tunnel messages,"
+"\n"
+"and is a reasonable tradeoff between the bandwidth costs of \n"
+"retransmitting lost messages, and the latency and overhead of multiple "
+"messages."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/streaming.html:473
+#: i2p2www/pages/site/docs/how/elgamal-aes.html:331
+#: i2p2www/pages/site/docs/how/garlic-routing.html:242
+#: i2p2www/pages/site/docs/how/network-database.html:834
+#: i2p2www/pages/site/docs/how/peer-selection.html:265
+#: i2p2www/pages/site/docs/how/tunnel-routing.html:255
+#: i2p2www/pages/site/docs/protocol/i2cp.html:646
+#: i2p2www/pages/site/docs/protocol/i2np.html:227
+#: i2p2www/pages/site/docs/spec/updates.html:280
+#: i2p2www/pages/site/docs/transport/ntcp.html:443
+#: i2p2www/pages/site/docs/transport/ssu.html:502
+#: i2p2www/pages/site/docs/tunnels/implementation.html:503
+msgid "Future Work"
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/streaming.html:474
+msgid ""
+"The behavior of the streaming library has a profound impact on\n"
+"application-level performance, and as such, is an important\n"
+"area for further analysis."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/streaming.html:480
+msgid "Additional tuning of the streaming lib parameters may be necessary."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/streaming.html:483
+#, python-format
+msgid ""
+"Another area for research is the interaction of the streaming lib with "
+"the\n"
+"NTCP and SSU transport layers.\n"
+"See the NTCP discussion page for details."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/streaming.html:488
+msgid ""
+"The interaction of the routing algorithms with the streaming lib strongly"
+" affects performance.\n"
+"In particular, random distribution of messages to multiple tunnels in a "
+"pool\n"
+"leads to a high degree of out-of-order delivery which results in smaller "
+"window\n"
+"sizes than would otherwise be the case. The router currently routes \n"
+"messages for a single from/to destination pair through a consistent set \n"
+"of tunnels, until tunnel expiration or delivery failure. The router's \n"
+"failure and tunnel selection algorithms should be reviewed for possible \n"
+"improvements."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/streaming.html:498
+msgid "The data in the first SYN packet may exceed the receiver's MTU."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/streaming.html:501
+msgid "The DELAY_REQUESTED field could be used more."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/streaming.html:504
+msgid ""
+"Duplicate initial SYNCHRONIZE packets on short-lived streams may not be "
+"recognized and removed."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/streaming.html:507
+msgid "Don't send the MTU in a retransmission."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/streaming.html:510
+msgid ""
+"Data is sent along unless the outbound window is full.\n"
+"(i.e. no-Nagle or TCP_NODELAY)\n"
+"Probably should have a configuration option for this."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/streaming.html:515
+msgid ""
+"zzz has added debug code to the streaming library to log packets in a "
+"wireshark-compatible\n"
+"(pcap) format; Use this to further analyze performance.\n"
+"The format may require enhancement to map more streaming lib parameters "
+"to TCP fields."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/streaming.html:520
+msgid ""
+"There are proposals to replace the streaming lib with standard TCP\n"
+"(or perhaps a null layer together with raw sockets).\n"
+"This would unfortunately be incompatible with the streaming lib\n"
+"but it would be good to compare the performance of the two."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/bittorrent.html:3
+#: i2p2www/pages/site/docs/spec/configuration.html:3
+msgid "September 2012"
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/bittorrent.html:7
+msgid ""
+"There are several bittorrent clients and trackers on I2P.\n"
+"As I2P addressing uses a Destination instead of an IP and port, minor\n"
+"changes are required to tracker and client software for operation on I2P."
+"\n"
+"These changes are specified below.\n"
+"Note carefully the guidelines for compatibility with older I2P clients "
+"and trackers."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/bittorrent.html:15
+msgid ""
+"This page specifies protocol details common to all clients and trackers.\n"
+"Specific clients and trackers may implement other unique features or "
+"protocols."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/bittorrent.html:20
+msgid "We welcome additional ports of client and tracker software to I2P."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/bittorrent.html:26
+msgid "Announces"
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/bittorrent.html:27
+msgid ""
+"Clients generally include a fake port=6881 parameter in the announce, for"
+" compatibility with older trackers.\n"
+"Trackers may ignore the port parameter, and should not require it."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/bittorrent.html:32
+#, python-format
+msgid ""
+"The ip parameter is the base 64 of the client's\n"
+"Destination,\n"
+"using the I2P Base 64 alphabet [A-Z][a-z][0-9]-~.\n"
+"Destinations\n"
+"are 387+ bytes, so the Base 64 is 516+ bytes.\n"
+"Clients generally append \".i2p\" to the Base 64 Destination for "
+"compatibility with older trackers.\n"
+"Trackers should not require an appended \".i2p\"."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/bittorrent.html:42
+msgid "Other parameters are the same as in standard bittorrent."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/bittorrent.html:46
+msgid ""
+"While all current Destinations for clients are exactly 387 bytes, a "
+"tracker should not\n"
+"presume that will always be so. A reasonable maximum to assume, for now, "
+"is 475 bytes.\n"
+"As the tracker must decode the Base64 to deliver compact responses (see "
+"below),\n"
+"the tracker should probably decode and reject bad Base64 when announced."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/bittorrent.html:53
+msgid ""
+"The default response type is non-compact. Clients may request a compact "
+"response with\n"
+"the parameter compact=1. A tracker may, but is not required to, return\n"
+"a compact response when requested."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/bittorrent.html:59
+msgid ""
+"Developers of new I2P clients\n"
+"are strongly encouraged to implemenent announces over their own tunnel "
+"rather than\n"
+"the HTTP client proxy at port 4444. Doing so is both more efficient and "
+"it allows\n"
+"destination enforcement by the tracker (see below)."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/bittorrent.html:66
+msgid ""
+"There are no known I2P clients or trackers that currently support UDP "
+"announce/responses."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/bittorrent.html:71
+msgid "Non-Compact Tracker Responses"
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/bittorrent.html:72
+msgid ""
+"The non-compact response is just as in standard bittorrent, with an I2P "
+"\"ip\"."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/bittorrent.html:76
+msgid ""
+"Trackers generally include a fake port key, or use the port from the "
+"announce, for compatibility with older clients.\n"
+"Clients must ignore the port parameter, and should not require it."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/bittorrent.html:81
+#, python-format
+msgid ""
+"The value of the ip key is the base 64 of the client's\n"
+"Destination, as "
+"described above.\n"
+"Trackers generally append \".i2p\" to the Base 64 Destination if it "
+"wasn't in the announce ip, for compatibility with older clients.\n"
+"Clients should not require an appended \".i2p\" in the responses."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/bittorrent.html:88
+msgid "Other response keys and values are the same as in standard bittorrent."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/bittorrent.html:94
+msgid "Compact Tracker Responses"
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/bittorrent.html:95
+#, python-format
+msgid ""
+"In the compact response, the value of the \"peers\" dictionary key is a "
+"single byte string,\n"
+"whose length is a multiple of 32 bytes.\n"
+"This string contains the concatenated\n"
+"32-byte SHA-256 Hashes\n"
+"of the binary\n"
+"Destinations\n"
+"of the peers.\n"
+"This hash must be computed by the tracker, unless destination enforcement"
+"\n"
+"(see below) is used, in which case the hash delivered in the X-I2P-"
+"DestHash\n"
+"or X-I2P-DestB32 HTTP headers may be converted to binary and stored.\n"
+"The peers key may be absent, or the peers value may be zero-length."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/bittorrent.html:109
+msgid ""
+"While compact response support is optional for both clients and trackers,"
+" it is highly\n"
+"recommended as it reduces the nominal response size by over 90%."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/bittorrent.html:116
+msgid "Destination Enforcement"
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/bittorrent.html:117
+#, python-format
+msgid ""
+"Some, but not all, I2P bittorrent clients announce over their own "
+"tunnels.\n"
+"Trackers may choose to prevent spoofing by requiring this, and verifying "
+"the\n"
+"client's\n"
+"Destination\n"
+"using HTTP headers added by the I2PTunnel HTTP Server tunnel.\n"
+"The headers are X-I2P-DestHash, X-I2P-DestB64, and X-I2P-DestB32, which "
+"are\n"
+"different formats for the same information.\n"
+"These headers cannot be spoofed by the client.\n"
+"A tracker enforcing destinations need not require the ip announce "
+"parameter at all."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/bittorrent.html:129
+msgid ""
+"As several clients use the HTTP proxy instead of their own tunnel for "
+"announces,\n"
+"destination enforcement will prevent usage by those clients unless or "
+"until\n"
+"those clients are converted to announcing over their own tunnel."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/bittorrent.html:135
+msgid ""
+"Unfortunately, as the network grows, so will the amount of maliciousness,"
+"\n"
+"so we expect that all trackers will eventually enforce destinations.\n"
+"Both tracker and client developers should anticipate it."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/bittorrent.html:143
+msgid "Announce Host Names"
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/bittorrent.html:144
+#, python-format
+msgid ""
+"Announce URL host names in torrent files generally follow the\n"
+"I2P naming standards.\n"
+"In addition to host names from address books and \".b32.i2p\" Base 32 "
+"hostnames,\n"
+"the full Base 64 Destination (with [or without?] \".i2p\" appended) "
+"should be supported.\n"
+"Non-open trackers should recognize their own host name in any of these "
+"formats."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/bittorrent.html:152
+msgid ""
+"To preserve anonymity,\n"
+"clients should generally ignore non-I2P announce URLs in torrent files."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/bittorrent.html:159
+msgid "Client Connections"
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/bittorrent.html:160
+msgid ""
+"Client-to-client connections use the standard protocol over TCP.\n"
+"There are no known I2P clients that currently support uTP communication."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/bittorrent.html:165
+#, python-format
+msgid ""
+"I2P uses 387+ byte Destinations\n"
+"for addresses, as explained above."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/bittorrent.html:170
+msgid ""
+"If the client has only the hash of the destination (such as from a "
+"compact response or PEX), it must perform a lookup\n"
+"by encoding it with Base 32, appending \".b32.i2p\", and querying the "
+"Naming Service,\n"
+"which will return the full Destination if available."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/bittorrent.html:176
+msgid ""
+"If the client has a peer's full Destination it received in a non-compact "
+"response, it should use it\n"
+"directly in the connection setup.\n"
+"Do not convert a Destination back to a Base 32 hash for lookup, this is "
+"quite inefficient."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/bittorrent.html:183
+msgid "Cross-Network Prevention"
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/bittorrent.html:184
+msgid ""
+"To preserve anonymity,\n"
+"I2P bittorrent clients generally do not support non-I2P announces or peer"
+" connections.\n"
+"I2P HTTP outproxies often block announces.\n"
+"There are no known SOCKS outproxies supporting bittorrent traffic."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/bittorrent.html:191
+msgid ""
+"To prevent usage by non-I2P clients via an HTTP inproxy, I2P trackers "
+"often\n"
+"block accesses or announces that contain an X-Forwarded-For HTTP header.\n"
+"Trackers should reject standard network announces with IPv4 or IPv6 IPs, "
+"and not deliver them in responses."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/bittorrent.html:200
+#, python-format
+msgid ""
+"I2P PEX is based on ut_pex.\n"
+"As there does not appear to be a formal specification of ut_pex "
+"available,\n"
+"it may be necessary to review the libtorrent source for assistance.\n"
+"It is an extension message, identified as \"i2p_pex\" in\n"
+"the extension "
+"handshake.\n"
+"It contains a bencoded dictionary with up to 3 keys, \"added\", "
+"\"added.f\", and \"dropped\".\n"
+"The added and dropped values are each a single byte string, whose length "
+"is a multiple of 32 bytes.\n"
+"These byte strings are the concatenated SHA-256 Hashes of the binary\n"
+"Destinations\n"
+"of the peers.\n"
+"This is the same format as the peers dictionary value in the i2p compact "
+"response format specified above.\n"
+"The added.f value, if present, is the same as in ut_pex."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/bittorrent.html:218
+msgid ""
+"DHT support is included in the i2psnark client as of version 0.9.2.\n"
+"Preliminary differences from\n"
+"BEP 5\n"
+"are described below, and are subject to change.\n"
+"Contact the I2P developers if you wish to develop a client supporting DHT."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/bittorrent.html:226
+msgid ""
+"Unlike standard DHT, I2P DHT does not use a bit in the options handshake,"
+" or the PORT message.\n"
+"It is advertised with an extension message, identified as \"i2p_dht\" in\n"
+"the extension "
+"handshake.\n"
+"It contains a bencoded dictionary with two keys, \"port\" and \"rport\", "
+"both integers."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/bittorrent.html:233
+msgid ""
+"The UDP (datagram) port listed in the compact node info is used\n"
+"to receive repliable (signed) datagrams.\n"
+"This is used for queries, except for announces.\n"
+"We call this the \"query port\".\n"
+"This is the \"port\" value from the extension message.\n"
+"Queries use I2CP protocol number 17."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/bittorrent.html:242
+msgid ""
+"In addition to that UDP port, we use a second datagram\n"
+"port equal to the query port + 1. This is used to receive\n"
+"unsigned (raw) datagrams for replies, errors, and announces.\n"
+"This port provides increased efficiency since replies\n"
+"contain tokens sent in the query, and need not be signed.\n"
+"We call this the \"response port\".\n"
+"This is the \"rport\" value from the extension message.\n"
+"It must be 1 + the query port.\n"
+"Responses and announces use I2CP protocol number 18."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/bittorrent.html:254
+msgid ""
+"Compact peer info is 32 bytes (32 byte SHA256 Hash)\n"
+"instead of 4 byte IP + 2 byte port. There is no peer port.\n"
+"In a response, the \"values\" key is a list of strings, each containing a"
+" single compact peer info."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/bittorrent.html:260
+msgid ""
+"Compact node info is 54 bytes (20 byte SHA1 Hash + 32 byte SHA256 Hash + "
+"2 byte port)\n"
+"instead of 20 byte SHA1 Hash + 4 byte IP + 2 byte port.\n"
+"In a response, the \"nodes\" key is a\n"
+"single byte string with concatenated compact node info."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/bittorrent.html:267
+msgid ""
+"Secure node ID requirement: To make various DHT attacks more difficult,\n"
+"the first 4 bytes of the Node ID must match the first 4 bytes of the "
+"destination Hash,\n"
+"and the next two bytes of the Node ID must match the next two bytes of "
+"the\n"
+"destination hash exclusive-ORed with the port."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/bittorrent.html:274
+msgid ""
+"In a torrent file,\n"
+"the trackerless torrent dictionary \"nodes\" key is TBD.\n"
+"It could be a list of\n"
+"32 byte binary strings (SHA256 Hashes) instead of a list of lists\n"
+"containing a host string and a port integer.\n"
+"Alternatives: A single byte string with concatenated hashes,\n"
+"or a list of strings alone."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/bittorrent.html:285
+#: i2p2www/pages/site/docs/how/intro.html:187
+msgid "Additional Information"
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/bittorrent.html:287
+#, python-format
+msgid ""
+"I2P bittorrent standards are generally discussed on %(zzz)s."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/bittorrent.html:290
+#, python-format
+msgid ""
+"A chart of current tracker software capabilities is also available there."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/bittorrent.html:293
+#, python-format
+msgid ""
+"The\n"
+"I2P bittorrent FAQ"
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/bittorrent.html:297
+#, python-format
+msgid "DHT on I2P discussion"
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:2
+#: i2p2www/pages/site/docs/applications/supported.html:5
+msgid "Supported Applications"
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:9
+#: i2p2www/pages/site/docs/applications/supported.html:186
+msgid "Blogging, Forums, and Wikis"
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:11
+#: i2p2www/pages/site/docs/applications/supported.html:232
+msgid "Decentralized File Storage"
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:14
+#: i2p2www/pages/site/docs/applications/supported.html:244
+msgid "Development Tools"
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:17
+#: i2p2www/pages/site/docs/applications/supported.html:246
+msgid "Version control"
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:21
+#: i2p2www/pages/site/docs/applications/supported.html:265
+msgid "Domain Naming"
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:23
+#: i2p2www/pages/site/docs/applications/supported.html:283
+msgid "Email"
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:26
+#: i2p2www/pages/site/docs/applications/supported.html:328
+msgid "File Sharing"
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:29
+#: i2p2www/pages/site/docs/applications/supported.html:330
+msgid "BitTorrent clients"
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:31
+#: i2p2www/pages/site/docs/applications/supported.html:372
+msgid "BitTorrent trackers and indexers"
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:40
+#: i2p2www/pages/site/docs/applications/supported.html:439
+msgid "Network Administration"
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:43
+#: i2p2www/pages/site/docs/applications/supported.html:441
+msgid "General-purpose socket utilities"
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:50
+#: i2p2www/pages/site/docs/applications/supported.html:482
+msgid "Real-time Chat"
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:53
+#: i2p2www/pages/site/docs/applications/supported.html:484
+msgid "Instant messaging clients"
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:55
+#: i2p2www/pages/site/docs/applications/supported.html:494
+msgid "IRC clients"
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:57
+#: i2p2www/pages/site/docs/applications/supported.html:545
+msgid "IRC servers"
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:62
+#: i2p2www/pages/site/docs/applications/supported.html:561
+msgid "Web Browsing"
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:65
+#: i2p2www/pages/site/docs/applications/supported.html:563
+msgid "Anonymous websites"
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:67
+#: i2p2www/pages/site/docs/applications/supported.html:612
+msgid "Proxy software"
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:69
+#: i2p2www/pages/site/docs/applications/supported.html:637
+msgid "Inproxies"
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:71
+#: i2p2www/pages/site/docs/applications/supported.html:669
+msgid "Outproxies"
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:76
+#: i2p2www/pages/site/docs/applications/supported.html:683
+msgid "Website Hosting"
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:79
+#: i2p2www/pages/site/docs/applications/supported.html:698
+msgid "Web servers"
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:85
+#, python-format
+msgid ""
+"This is intended to be a comprehensive listing of applications used with\n"
+"I2P. If you know of something that's missing please submit a ticket on\n"
+"Trac, and be sure to select the\n"
+"“www” component in the submission form."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:92
+msgid ""
+"\n"
+"Supported applications are tagged with one or more of the following:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:97
+#: i2p2www/pages/site/docs/applications/supported.html:279
+#: i2p2www/pages/site/docs/applications/supported.html:311
+#: i2p2www/pages/site/docs/applications/supported.html:336
+#: i2p2www/pages/site/docs/applications/supported.html:695
+msgid "bundled"
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:100
+msgid ""
+"Bundled application — I2P ships with a few officially\n"
+"supported applications that let new users take immediate advantage of\n"
+"some of I2P's more useful capabilities."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:107
+#: i2p2www/pages/site/docs/applications/supported.html:195
+#: i2p2www/pages/site/docs/applications/supported.html:208
+#: i2p2www/pages/site/docs/applications/supported.html:220
+#: i2p2www/pages/site/docs/applications/supported.html:228
+#: i2p2www/pages/site/docs/applications/supported.html:241
+#: i2p2www/pages/site/docs/applications/supported.html:292
+#: i2p2www/pages/site/docs/applications/supported.html:404
+#: i2p2www/pages/site/docs/applications/supported.html:426
+#: i2p2www/pages/site/docs/applications/supported.html:435
+#: i2p2www/pages/site/docs/applications/supported.html:523
+msgid "plugin"
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:110
+#, python-format
+msgid ""
+"Third-party plugin — I2P's plugin system provides convenient\n"
+"deployment of I2P-enabled applications and allows tighter integration\n"
+"with the router. Plugins are [reviewed by the community](http://%(plugins)s) to identify security and\n"
+"anonymity issues."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:121
+#: i2p2www/pages/site/docs/applications/supported.html:220
+#: i2p2www/pages/site/docs/applications/supported.html:228
+#: i2p2www/pages/site/docs/applications/supported.html:241
+#: i2p2www/pages/site/docs/applications/supported.html:252
+#: i2p2www/pages/site/docs/applications/supported.html:261
+#: i2p2www/pages/site/docs/applications/supported.html:324
+#: i2p2www/pages/site/docs/applications/supported.html:342
+#: i2p2www/pages/site/docs/applications/supported.html:353
+#: i2p2www/pages/site/docs/applications/supported.html:368
+#: i2p2www/pages/site/docs/applications/supported.html:414
+#: i2p2www/pages/site/docs/applications/supported.html:426
+#: i2p2www/pages/site/docs/applications/supported.html:435
+#: i2p2www/pages/site/docs/applications/supported.html:450
+#: i2p2www/pages/site/docs/applications/supported.html:456
+#: i2p2www/pages/site/docs/applications/supported.html:462
+#: i2p2www/pages/site/docs/applications/supported.html:472
+#: i2p2www/pages/site/docs/applications/supported.html:478
+#: i2p2www/pages/site/docs/applications/supported.html:490
+#: i2p2www/pages/site/docs/applications/supported.html:523
+#: i2p2www/pages/site/docs/applications/supported.html:529
+#: i2p2www/pages/site/docs/applications/supported.html:535
+#: i2p2www/pages/site/docs/applications/supported.html:541
+#: i2p2www/pages/site/docs/applications/supported.html:618
+#: i2p2www/pages/site/docs/applications/supported.html:627
+#: i2p2www/pages/site/docs/applications/supported.html:633
+#: i2p2www/pages/site/docs/applications/supported.html:695
+#: i2p2www/pages/site/docs/applications/supported.html:710
+#: i2p2www/pages/site/docs/applications/supported.html:716
+#: i2p2www/pages/site/docs/applications/supported.html:722
+#: i2p2www/pages/site/docs/applications/supported.html:728
+msgid "standalone"
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:121
+#: i2p2www/pages/site/docs/applications/supported.html:195
+#: i2p2www/pages/site/docs/applications/supported.html:202
+#: i2p2www/pages/site/docs/applications/supported.html:208
+#: i2p2www/pages/site/docs/applications/supported.html:214
+#: i2p2www/pages/site/docs/applications/supported.html:362
+#: i2p2www/pages/site/docs/applications/supported.html:386
+#: i2p2www/pages/site/docs/applications/supported.html:395
+#: i2p2www/pages/site/docs/applications/supported.html:551
+#: i2p2www/pages/site/docs/applications/supported.html:557
+msgid "standalone/mod"
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:124
+msgid ""
+"Third-party standalone application — Many standard network\n"
+"applications only require careful setup and configuration to communicate\n"
+"anonymously over I2P. These are tagged with standalone. Some\n"
+"applications, tagged with standalone/mod, require patching to\n"
+"function properly over I2P or to prevent inadvertent disclosure of\n"
+"identifying information such as the user's hostname or external IP\n"
+"address."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:135
+#: i2p2www/pages/site/docs/applications/supported.html:302
+#: i2p2www/pages/site/docs/applications/supported.html:571
+#: i2p2www/pages/site/docs/applications/supported.html:581
+#: i2p2www/pages/site/docs/applications/supported.html:590
+#: i2p2www/pages/site/docs/applications/supported.html:596
+#: i2p2www/pages/site/docs/applications/supported.html:602
+#: i2p2www/pages/site/docs/applications/supported.html:608
+#: i2p2www/pages/site/docs/applications/supported.html:649
+#: i2p2www/pages/site/docs/applications/supported.html:657
+#: i2p2www/pages/site/docs/applications/supported.html:665
+#: i2p2www/pages/site/docs/applications/supported.html:679
+msgid "service"
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:138
+msgid ""
+"Third-party essential network service — Services which on\n"
+"the I2P network are analogous to those provided on the public Internet\n"
+"by hosting providers, ISPs, and Google: eepsite indexes and jump\n"
+"services, search engines, email, DNS-style name services, hosting,\n"
+"proxies, etc. These services focus on boosting the usefulness of the\n"
+"network as a whole, and making network content more discoverable."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:148
+#: i2p2www/pages/site/docs/applications/supported.html:220
+#: i2p2www/pages/site/docs/applications/supported.html:368
+msgid "unmaintained"
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:151
+msgid ""
+"Unmaintained — This is used to tag plugins, applications,\n"
+"and services which appear to be unmaintained and may be removed from\n"
+"this listing in the future."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:159
+#, python-format
+msgid ""
+"Warning: Using an application, plugin, or service with I2P\n"
+"doesn't automatically protect your anonymity. I2P is merely a set of "
+"tools\n"
+"which can help you mitigate certain identified\n"
+"threats to anonymity. We do not and cannot make any guarantees about "
+"the\n"
+"safety of the applications, plugins, and services listed below. Most\n"
+"applications and plugins must be properly configured, and some will need "
+"to\n"
+"be patched — and even then your anonymity might not be assured. "
+"Similarly,\n"
+"services could put your anonymity at risk, either by design or through\n"
+"carelessness on their part or your own."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:171
+msgid ""
+"If you have doubts about the suitability of an application,\n"
+"plugin, or service for use with I2P, you are urged to inquire about "
+"privacy\n"
+"issues with its maintainers, to search its mailing lists and bug tracker "
+"if\n"
+"one exists, and consult trusted, knowledgeable members of the I2P\n"
+"community."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:179
+msgid ""
+"Take responsibility for your own anonymity and safety — always\n"
+"seek expert advice, educate yourself, practice good judgment, be mindful "
+"of\n"
+"disclosing personally identifying information, and don't take\n"
+"shortcuts."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:201
+msgid "Lightweight forum software."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:207
+msgid "Another lightweight blogging platform."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:213
+msgid "Most popular open source forum software."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:219
+msgid "Distributed forums software, originally developed by jrandom."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:224
+#, python-format
+msgid ""
+"A Java-based MediaWiki clone. No external database needed.\n"
+"Plugin available here."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:236
+#, python-format
+msgid ""
+"Port of the Tahoe-"
+"LAFS\n"
+"distributed file system to the I2P network. Controller plugin here."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:251
+msgid "Most popular distributed version control system."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:257
+#, python-format
+msgid ""
+"Another distributed version control system. Currently\n"
+"used in I2P development."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:269
+#, python-format
+msgid ""
+"Provides management of addressbooks, which are part of a simple,\n"
+"user-controlled I2P naming system somewhat\n"
+"analogous to the Internet's Domain Name System (DNS). Addressbooks map\n"
+"Base64 destinations to short, usually human-readable “domain” names "
+"ending\n"
+"with a .i2p suffix which the I2P router's HTTP client can resolve back to"
+"\n"
+"Base64 addresses. (Note: While Base64 destinations are globally\n"
+"unique, addressbook “domain” names only resolve to unique destinations\n"
+"locally.)"
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:288
+msgid ""
+"Serverless peer-to-peer email application using a distributed hash table\n"
+"(DHT) for secure mail storage."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:297
+msgid ""
+"Provides email service within the I2P network via @mail.i2p addresses,\n"
+"and email gateway service between the I2P network and the public Internet"
+"\n"
+"via @i2pmail.org addresses. One of the oldest continuous services on I2P."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:307
+msgid ""
+"Simple web browser-based email interface. Configured to use Postman's\n"
+"email service by default."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:316
+#, python-format
+msgid ""
+"Can be configured to use Postman's email service. See\n"
+"this comparison of MUAs,\n"
+"and configuration settings for\n"
+"SMTP and POP3."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:335
+msgid "I2P's integrated BitTorrent client."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:341
+msgid "Modified version of I2PSnark."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:347
+msgid ""
+"\n"
+"A fork of rufus that uses the Basic Open Bridge (BOB) and has many\n"
+"improvements, including using the latest wxwidgets and python. It also\n"
+"supports use of seedless if installed for trackerless torrents and\n"
+"magnet-link like fetching of torrents within I2P.\n"
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:358
+msgid ""
+"Clean, full-featured cross-platform BitTorrent client with official\n"
+"ports for several GUI toolkits."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:367
+msgid "Has a plugin providing I2P support."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:374
+#, python-format
+msgid ""
+"For a detailed feature comparison of I2P-enabled trackers/indexers, see\n"
+"here."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:382
+msgid ""
+"The code that powered one of the first major tracker/indexer sites on the"
+"\n"
+"Internet. Patched for I2P."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:391
+#, python-format
+msgid ""
+"Lightweight tracker/indexer. I2P mod available in the i2p.opentracker\n"
+"branch of the I2P Monotone repository."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:400
+#, python-format
+msgid ""
+"zzz's Java-based open tracker. More info\n"
+"here."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:413
+msgid "I2P port of the aMule ED2K client."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:422
+#, python-format
+msgid ""
+"Port of the Phex Gnutella "
+"client. Website\n"
+"for plugin version here."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:431
+#, python-format
+msgid ""
+"Cache for Gnutella peers on I2P. Website for plugin version\n"
+"here."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:446
+msgid ""
+"Unix standard tool for socket relaying. Several clones, ports, and forks\n"
+"have appeared over the years."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:455
+msgid "Like netcat but more powerful."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:461
+msgid ""
+"Proxy providing simple, transparent SOCKS-ification of network "
+"applications."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:471
+msgid ""
+"Most popular implementation of the Secure Shell (SSH) protocol and "
+"related tools."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:477
+msgid "Open source Secure Shell (SSH) client for Windows."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:489
+msgid "IM client with multiple incarnations."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:496
+msgid ""
+"Many IRC clients leak identifying information to servers or other\n"
+"clients, so I2P's IRC and SOCKS IRC client tunnels filter certain inbound"
+"\n"
+"and outbound messages to scrub data such as LAN IP addresses, external IP"
+"\n"
+"addresses, local hostnames, and the name and version of the IRC client. "
+"Two\n"
+"message types in particular, DCC and CTCP, can't be sufficiently "
+"anonymized\n"
+"without changes to the protocols or to IRC client/server code, so they "
+"are\n"
+"completely blocked, except for CTCP ACTION (the message emitted by the\n"
+"/me command) which isn't inherently dangerous."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:507
+msgid ""
+"I2P's IRC filtering may not cover every possible leak — users should also"
+"\n"
+"check if their client is sending their real name or local username. "
+"Packet\n"
+"sniffers such as Wireshark are\n"
+"useful here. Eliminating remaining leaks may be as simple as changing the"
+"\n"
+"client's default configuration. If that doesn't help, inform the I2P\n"
+"developers; they may be able to solve it via additional filtering."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:519
+#, python-format
+msgid ""
+"Small Java-based IRC client. Plugin available here."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:528
+msgid "Cross-platform graphical IRC client."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:534
+msgid "Unixy terminal-based IRC client."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:540
+msgid "Another Unixy terminal-based IRC client."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:550
+msgid "IRC server developed from scratch."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:556
+msgid "Most popular IRC server."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:568
+msgid ""
+"Any website hosted anonymously on I2P, reachable through the I2P router's"
+" HTTP proxy."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:576
+msgid ""
+"Distributed anonymous websites hosted\n"
+"using Tahoe-LAFS-I2P, currently only reachable with Tahoe-LAFS-I2P\n"
+"clients or through the Tahoe-LAFS-I2P HTTP proxy."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:586
+#, python-format
+msgid ""
+"Website for sponge's jump service.\n"
+"Source code available."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:595
+msgid "Another jump service."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:601
+msgid "Dynamically updated eepsite index."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:607
+#, python-format
+msgid "Website for zzz's jump service."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:617
+msgid "SOCKS-enabled caching web proxy with basic filtering capabilities."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:623
+msgid ""
+"Privacy-focused non-caching web proxy with advanced filtering\n"
+"capabilities. Excels at removing ads and other junk."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:632
+msgid "Venerable caching web proxy."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:639
+msgid "Gateways allowing users on the public Internet to access eepsites."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:646
+#, python-format
+msgid "tino's inproxy on the public Internet."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:654
+#: i2p2www/pages/site/docs/applications/supported.html:662
+msgid "Another inproxy on the public Internet."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:671
+msgid ""
+"Gateways allowing I2P users to access content hosted on the public "
+"Internet."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:678
+msgid "Publicly advertised outproxy running Squid, located in Germany."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:688
+msgid ""
+"Lightweight web server and Java servlet container. I2P is tightly\n"
+"integrated with a bundled copy of Jetty which by default is configured to"
+"\n"
+"host the user's eepsite. The "
+"bundled\n"
+"Jetty also serves the I2P router console and web applications bundled "
+"with\n"
+"I2P."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:700
+msgid ""
+"In addition to Jetty, any web server should function over I2P without\n"
+"modification so long as it's HTTP-compliant. Some web servers known to\n"
+"currently serve content on the I2P network are:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:709
+msgid "Most popular web server on the public WWW."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:715
+msgid "Web server and Java servlet container. More features than Jetty."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:721
+msgid "Fast lightweight web server."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:727
+msgid "High-performance lightweight web server."
+msgstr ""
+
+#: i2p2www/pages/site/docs/discussions/naming.html:2
+msgid "Naming discussion"
+msgstr ""
+
+#: i2p2www/pages/site/docs/discussions/naming.html:4
+#, python-format
+msgid ""
+"NOTE: The following is a discussion of the reasons behind the I2P naming "
+"system,\n"
+"common arguments and possible alternatives.\n"
+"See the naming page for current documentation."
+msgstr ""
+
+#: i2p2www/pages/site/docs/discussions/naming.html:10
+msgid "Discarded alternatives"
+msgstr ""
+
+#: i2p2www/pages/site/docs/discussions/naming.html:12
+msgid ""
+"Naming within I2P has been an oft-debated topic since the very beginning "
+"with\n"
+"advocates across the spectrum of possibilities. However, given I2P's "
+"inherent\n"
+"demand for secure communication and decentralized operation, the "
+"traditional\n"
+"DNS-style naming system is clearly out, as are \"majority rules\" voting "
+"systems."
+msgstr ""
+
+#: i2p2www/pages/site/docs/discussions/naming.html:19
+msgid ""
+"I2P does not promote the use of DNS-like services though, as the damage "
+"done\n"
+"by hijacking a site can be tremendous - and insecure destinations have no"
+"\n"
+"value. DNSsec itself still falls back on registrars and certificate "
+"authorities,\n"
+"while with I2P, requests sent to a destination cannot be intercepted or "
+"the reply\n"
+"spoofed, as they are encrypted to the destination's public keys, and a "
+"destination\n"
+"itself is just a pair of public keys and a certificate. DNS-style "
+"systems on the\n"
+"other hand allow any of the name servers on the lookup path to mount "
+"simple denial\n"
+"of service and spoofing attacks. Adding on a certificate authenticating "
+"the\n"
+"responses as signed by some centralized certificate authority would "
+"address many of\n"
+"the hostile nameserver issues but would leave open replay attacks as well"
+" as \n"
+"hostile certificate authority attacks."
+msgstr ""
+
+#: i2p2www/pages/site/docs/discussions/naming.html:33
+msgid ""
+"Voting style naming is dangerous as well, especially given the "
+"effectiveness of\n"
+"Sybil attacks in anonymous systems - the attacker can simply create an "
+"arbitrarily\n"
+"high number of peers and \"vote\" with each to take over a given name. "
+"Proof-of-work\n"
+"methods can be used to make identity non-free, but as the network grows "
+"the load\n"
+"required to contact everyone to conduct online voting is implausible, or "
+"if the\n"
+"full network is not queried, different sets of answers may be reachable."
+msgstr ""
+
+#: i2p2www/pages/site/docs/discussions/naming.html:42
+msgid ""
+"As with the Internet however, I2P is keeping the design and operation of "
+"a \n"
+"naming system out of the (IP-like) communication layer. The bundled "
+"naming library\n"
+"includes a simple service provider interface which alternate naming systems can\n"
+"plug into, allowing end users to drive what sort of naming tradeoffs they"
+" prefer."
+msgstr ""
+
+#: i2p2www/pages/site/docs/discussions/naming.html:50
+msgid ""
+"See also Names: "
+"Decentralized, Secure, Human-Meaningful: Choose Two."
+msgstr ""
+
+#: i2p2www/pages/site/docs/discussions/naming.html:55
+msgid "(adapted from a post in the old Syndie, November 26, 2005)"
+msgstr ""
+
+#: i2p2www/pages/site/docs/discussions/naming.html:58
+msgid ""
+"Q:\n"
+"What to do if some hosts \n"
+"do not agree on one address and if some addresses are working, others are"
+" not? \n"
+"Who is the right source of a name?"
+msgstr ""
+
+#: i2p2www/pages/site/docs/discussions/naming.html:64
+msgid ""
+"A:\n"
+"You don't. This is actually a critical difference between names on I2P "
+"and how \n"
+"DNS works - names in I2P are human readable, secure, but not globally"
+" \n"
+"unique. This is by design, and an inherent part of our need for "
+"security."
+msgstr ""
+
+#: i2p2www/pages/site/docs/discussions/naming.html:70
+msgid ""
+"If I could somehow convince you to change the destination associated with"
+" some \n"
+"name, I'd successfully \"take over\" the site, and under no circumstances"
+" is that \n"
+"acceptable. Instead, what we do is make names locally unique: "
+"they are \n"
+"what you use to call a site, just as how you can call things "
+"whatever \n"
+"you want when you add them to your browser's bookmarks, or your IM "
+"client's \n"
+"buddy list. Who you call \"Boss\" may be who someone else calls "
+"\"Sally\"."
+msgstr ""
+
+#: i2p2www/pages/site/docs/discussions/naming.html:78
+msgid "Names will not, ever, be securely human readable and globally unique."
+msgstr ""
+
+#: i2p2www/pages/site/docs/discussions/naming.html:83
+msgid ""
+"The following from zzz is a review of several common\n"
+"complaints about I2P's naming system."
+msgstr ""
+
+#: i2p2www/pages/site/docs/discussions/naming.html:89
+msgid ""
+"Inefficiency:\n"
+"The whole hosts.txt is downloaded (if it has changed, since eepget uses "
+"the etag and last-modified headers).\n"
+"It's about 400K right now for almost 800 hosts."
+msgstr ""
+
+#: i2p2www/pages/site/docs/discussions/naming.html:94
+msgid ""
+"True, but this isn't a lot of traffic in the context of i2p, which is "
+"itself wildly inefficient\n"
+"(floodfill databases, huge encryption overhead and padding, garlic "
+"routing, etc.).\n"
+"If you downloaded a hosts.txt file from someone every 12 hours it "
+"averages out to about 10 bytes/sec."
+msgstr ""
+
+#: i2p2www/pages/site/docs/discussions/naming.html:99
+msgid ""
+"As is usually the case in i2p, there is a fundamental tradeoff here "
+"between anonymity and efficiency.\n"
+"Some would say that using the etag and last-modified headers is hazardous"
+" because it exposes when you\n"
+"last requested the data.\n"
+"Others have suggested asking for specific keys only (similar to what jump"
+" services do, but\n"
+"in a more automated fashion), possibly at a further cost in anonymity."
+msgstr ""
+
+#: i2p2www/pages/site/docs/discussions/naming.html:106
+#, python-format
+msgid ""
+"Possible improvements would be a replacement or supplement to addressbook"
+" (see %(i2host)sp),\n"
+"or something simple like subscribing to http://example.i2p/cgi-"
+"bin/recenthosts.cgi rather than http://example.i2p/hosts.txt.\n"
+"If a hypothetical recenthosts.cgi distributed all hosts from the last 24 "
+"hours, for example,\n"
+"that could be both more efficient and more anonymous than the current "
+"hosts.txt with last-modified and etag."
+msgstr ""
+
+#: i2p2www/pages/site/docs/discussions/naming.html:112
+#, python-format
+msgid ""
+"A sample implementation is on stats.i2p at\n"
+"%(url)s.\n"
+"This script returns an Etag with a timestamp.\n"
+"When a request comes in with the If-None-Match etag,\n"
+"the script ONLY returns new hosts since that timestamp, or 304 Not "
+"Modified if there are none.\n"
+"In this way, the script efficiently returns only the hosts the subscriber"
+"\n"
+"does not know about, in an addressbook-compatible manner."
+msgstr ""
+
+#: i2p2www/pages/site/docs/discussions/naming.html:121
+msgid ""
+"So the inefficiency is not a big issue and there are several ways to "
+"improve things without\n"
+"radical change."
+msgstr ""
+
+#: i2p2www/pages/site/docs/discussions/naming.html:127
+msgid ""
+"Not Scalable:\n"
+"The 400K hosts.txt (with linear search) isn't that big at the moment and\n"
+"we can probably grow by 10x or 100x before it's a problem."
+msgstr ""
+
+#: i2p2www/pages/site/docs/discussions/naming.html:132
+msgid ""
+"As far as network traffic see above.\n"
+"But unless you're going to do a slow real-time query over the network for"
+"\n"
+"a key, you need to have the whole set of keys stored locally, at a cost "
+"of about 500 bytes per key."
+msgstr ""
+
+#: i2p2www/pages/site/docs/discussions/naming.html:139
+msgid ""
+"Requires configuration and \"trust\":\n"
+"Out-of-the-box addressbook is only subscribed to "
+"http://www.i2p2.i2p/hosts.txt, which is rarely updated,\n"
+"leading to poor new-user experience."
+msgstr ""
+
+#: i2p2www/pages/site/docs/discussions/naming.html:144
+msgid ""
+"This is very much intentional. jrandom wants a user to \"trust\" a "
+"hosts.txt\n"
+"provider, and as he likes to say, \"trust is not a boolean\".\n"
+"The configuration step attempts to force users to think about issues of "
+"trust in an anonymous network."
+msgstr ""
+
+#: i2p2www/pages/site/docs/discussions/naming.html:149
+msgid ""
+"As another example, the \"Eepsite Unknown\" error page in the HTTP Proxy\n"
+"lists some jump services, but doesn't \"recommend\" any one in "
+"particular,\n"
+"and it's up to the user to pick one (or not).\n"
+"jrandom would say we trust the listed providers enough to list them but "
+"not enough to\n"
+"automatically go fetch the key from them."
+msgstr ""
+
+#: i2p2www/pages/site/docs/discussions/naming.html:156
+msgid ""
+"How successful this is, I'm not sure.\n"
+"But there must be some sort of hierarchy of trust for the naming system.\n"
+"To treat everyone equally may increase the risk of hijacking."
+msgstr ""
+
+#: i2p2www/pages/site/docs/discussions/naming.html:163
+msgid "It isn't DNS"
+msgstr ""
+
+#: i2p2www/pages/site/docs/discussions/naming.html:166
+msgid ""
+"Unfortunately real-time lookups over i2p would significantly slow down "
+"web browsing."
+msgstr ""
+
+#: i2p2www/pages/site/docs/discussions/naming.html:169
+msgid ""
+"Also, DNS is based on lookups with limited caching and time-to-live, "
+"while i2p\n"
+"keys are permanent."
+msgstr ""
+
+#: i2p2www/pages/site/docs/discussions/naming.html:173
+msgid "Sure, we could make it work, but why? It's a bad fit."
+msgstr ""
+
+#: i2p2www/pages/site/docs/discussions/naming.html:178
+msgid ""
+"Not reliable:\n"
+"It depends on specific servers for addressbook subscriptions."
+msgstr ""
+
+#: i2p2www/pages/site/docs/discussions/naming.html:182
+msgid ""
+"Yes it depends on a few servers that you have configured.\n"
+"Within i2p, servers and services come and go.\n"
+"Any other centralized system (for example DNS root servers) would\n"
+"have the same problem. A completely decentralized system (everybody is "
+"authoritative)\n"
+"is possible by implementing an \"everybody is a root DNS server\" "
+"solution, or by\n"
+"something even simpler, like a script that adds everybody in your "
+"hosts.txt to your addressbook."
+msgstr ""
+
+#: i2p2www/pages/site/docs/discussions/naming.html:190
+msgid ""
+"People advocating all-authoritative solutions generally haven't thought "
+"through\n"
+"the issues of conflicts and hijacking, however."
+msgstr ""
+
+#: i2p2www/pages/site/docs/discussions/naming.html:196
+msgid ""
+"Awkward, not real-time:\n"
+"It's a patchwork of hosts.txt providers, key-add web form providers, jump"
+" service providers,\n"
+"eepsite status reporters.\n"
+"Jump servers and subscriptions are a pain, it should just work like DNS."
+msgstr ""
+
+#: i2p2www/pages/site/docs/discussions/naming.html:202
+msgid "See the reliability and trust sections."
+msgstr ""
+
+#: i2p2www/pages/site/docs/discussions/naming.html:207
+msgid ""
+"So, in summary, the current system is not horribly broken, inefficient, "
+"or un-scalable,\n"
+"and proposals to \"just use DNS\" aren't well thought-through."
+msgstr ""
+
+#: i2p2www/pages/site/docs/discussions/naming.html:212
+msgid "Alternatives"
+msgstr ""
+
+#: i2p2www/pages/site/docs/discussions/naming.html:213
+msgid ""
+"The I2P source contains several pluggable naming systems and supports "
+"configuration options\n"
+"to enable experimentation with naming systems."
+msgstr ""
+
+#: i2p2www/pages/site/docs/discussions/naming.html:218
+msgid ""
+"Meta - calls two or more other naming systems in order.\n"
+"By default, calls PetName then HostsTxt."
+msgstr ""
+
+#: i2p2www/pages/site/docs/discussions/naming.html:222
+msgid ""
+"PetName - Looks up in a petnames.txt file.\n"
+"The format for this file is NOT the same as hosts.txt."
+msgstr ""
+
+#: i2p2www/pages/site/docs/discussions/naming.html:226
+msgid "HostsTxt - Looks up in the following files, in order:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/discussions/naming.html:234
+msgid ""
+"AddressDB - Each host is listed in a separate file in a addressDb/"
+" directory."
+msgstr ""
+
+#: i2p2www/pages/site/docs/discussions/naming.html:237
+msgid ""
+"Eepget - does an HTTP lookup request from an external\n"
+"server - must be stacked after the HostsTxt lookup with Meta.\n"
+"This could augment or replace the jump system.\n"
+"Includes in-memory caching."
+msgstr ""
+
+#: i2p2www/pages/site/docs/discussions/naming.html:243
+msgid ""
+"Exec - calls an external program for lookup, allows\n"
+"additional experimentation in lookup schemes, independent of java.\n"
+"Can be used after HostsTxt or as the sole naming system.\n"
+"Includes in-memory caching."
+msgstr ""
+
+#: i2p2www/pages/site/docs/discussions/naming.html:249
+msgid "Dummy - used as a fallback for Base64 names, otherwise fails."
+msgstr ""
+
+#: i2p2www/pages/site/docs/discussions/naming.html:253
+msgid ""
+"The current naming system can be changed with the advanced config option "
+"'i2p.naming.impl'\n"
+"(restart required).\n"
+"See core/java/src/net/i2p/client/naming for details."
+msgstr ""
+
+#: i2p2www/pages/site/docs/discussions/naming.html:258
+msgid ""
+"Any new system should be stacked with HostsTxt, or should\n"
+"implement local storage and/or the addressbook subscription functions, "
+"since addressbook\n"
+"only knows about the hosts.txt files and format."
+msgstr ""
+
+#: i2p2www/pages/site/docs/discussions/naming.html:264
+msgid "Certificates"
+msgstr ""
+
+#: i2p2www/pages/site/docs/discussions/naming.html:265
+msgid ""
+"I2P destinations contain a certificate, however at the moment that "
+"certificate\n"
+"is always null.\n"
+"With a null certificate, base64 destinations are always 516 bytes ending "
+"in \"AAAA\",\n"
+"and this is checked in the addressbook merge mechanism, and possibly "
+"other places.\n"
+"Also, there is no method available to generate a certificate or add it to"
+" a\n"
+"destination. So these will have to be updated to implement certificates."
+msgstr ""
+
+#: i2p2www/pages/site/docs/discussions/naming.html:273
+#, python-format
+msgid ""
+"One possible use of certificates is for proof of work."
+msgstr ""
+
+#: i2p2www/pages/site/docs/discussions/naming.html:276
+msgid ""
+"Another is for \"subdomains\" (in quotes because there is really no such "
+"thing,\n"
+"i2p uses a flat naming system) to be signed by the 2nd level domain's "
+"keys."
+msgstr ""
+
+#: i2p2www/pages/site/docs/discussions/naming.html:280
+msgid ""
+"With any certificate implementation must come the method for verifying "
+"the\n"
+"certificates.\n"
+"Presumably this would happen in the addressbook merge code.\n"
+"Is there a method for multiple types of certificates, or multiple "
+"certificates?"
+msgstr ""
+
+#: i2p2www/pages/site/docs/discussions/naming.html:286
+msgid ""
+"Adding on a certificate authenticating the\n"
+"responses as signed by some centralized certificate authority would "
+"address many of\n"
+"the hostile nameserver issues but would leave open replay attacks as well"
+" as \n"
+"hostile certificate authority attacks."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/cryptography.html:2
+msgid "Low-level Cryptography Details"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/cryptography.html:3
+#: i2p2www/pages/site/docs/spec/common-structures.html:3
+msgid "November 2013"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/cryptography.html:6
+msgid "This page specifies the low-level details of the cryptography in I2P."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/cryptography.html:10
+#, python-format
+msgid ""
+"There are a handful of cryptographic algorithms in use within I2P, but we"
+" have\n"
+"reduced them to a bare minimum to deal with our needs - one symmetric "
+"algorithm\n"
+"one asymmetric algorithm, one signing algorithm, and one hashing "
+"algorithm. However, \n"
+"we do combine them in some particular ways to provide message integrity "
+"(rather than\n"
+"relying on a MAC). In addition, as much as we hate doing anything new in"
+" regards to \n"
+"cryptography, we can't seem to find a reference discussing (or even "
+"naming) the \n"
+"technique used in ElGamal/AES+SessionTag "
+"(but we're sure others have done it)."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/cryptography.html:20
+msgid "ElGamal encryption"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/cryptography.html:22
+msgid ""
+"\n"
+"ElGamal is used for asymmetric encryption.\n"
+"ElGamal is used in several places in I2P:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/cryptography.html:27
+#, python-format
+msgid ""
+"To encrypt router-to-router Tunnel Build "
+"Messages"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/cryptography.html:30
+#, python-format
+msgid ""
+"For end-to-end (destination-to-destination) encryption as a part of ElGamal/AES+SessionTag\n"
+"using the encryption key in the LeaseSet"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/cryptography.html:34
+#: i2p2www/pages/site/docs/how/cryptography.html:189
+#, python-format
+msgid ""
+"For encryption of some netDb stores and "
+"queries sent to floodfill routers\n"
+"as a part of ElGamal/AES+SessionTag\n"
+"(destination-to-router or router-to-router)."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/cryptography.html:41
+msgid ""
+"We use common primes for 2048 ElGamal encryption and decryption, as given"
+" by IETF RFC-3526.\n"
+"We currently only use ElGamal to encrypt the IV and session key in a "
+"single block, followed by the \n"
+"AES encrypted payload using that key and IV."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/cryptography.html:47
+msgid "The unencrypted ElGamal contains:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/cryptography.html:64
+msgid ""
+"The H(data) is the SHA256 of the data that is encrypted in the ElGamal "
+"block,\n"
+"and is preceded by a nonzero byte. \n"
+"This byte could be random, but as implemented it is always 0xFF.\n"
+"It could possibly be used for flags in the future.\n"
+"The data encrypted in the block may be up to 222 bytes long.\n"
+"As the encrypted data may contain a substantial number of zeros if the\n"
+"cleartext is smaller than 222 bytes, it is recommended that higher layers"
+" pad\n"
+"the cleartext to 222 bytes with random data.\n"
+"Total length: typically 255 bytes."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/cryptography.html:76
+msgid "The encrypted ElGamal contains:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/cryptography.html:102
+msgid ""
+"Each encrypted part is prepended with zeros to a size of exactly 257 "
+"bytes.\n"
+"Total length: 514 bytes.\n"
+"In typical usage, higher layers pad the cleartext data to 222 bytes,\n"
+"resulting in an unencrypted block of 255 bytes.\n"
+"This is encoded as two 256-byte encrypted parts,\n"
+"and there is a single byte of zero padding before each part at this layer."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/cryptography.html:111
+#, python-format
+msgid "See the ElGamal code."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/cryptography.html:115
+msgid ""
+"The shared prime is the \n"
+"[Oakley prime "
+"for 2048 bit keys]"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/cryptography.html:122
+msgid "or as a hexadecimal value:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/cryptography.html:138
+msgid "Using 2 as the generator."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/cryptography.html:142
+msgid "Short Exponent"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/cryptography.html:143
+#, python-format
+msgid ""
+"While the standard exponent size is 2048 bits (256 bytes) and the I2P\n"
+"PrivateKey\n"
+"is a full 256 bytes,\n"
+"we use the short exponent size of 226 bits (28.25 bytes).\n"
+"This should be safe for use with the Oakley primes, per\n"
+"On Diffie-Hellman Key Agreement with Short Exponents "
+"- van Oorschot, Weiner\n"
+"at EuroCrypt 96, and crypto++'s "
+"benchmarks.\n"
+"Benchmarks originally at %(oldbenchmarks)s (now dead),\n"
+"rescued from the wayback machine,"
+" dated Apr 23, 2008."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/cryptography.html:158
+#, python-format
+msgid ""
+"Also, Koshiba & Kurosawa: Short Exponent Diffie-"
+"Hellman Problems (PKC 2004, LNCS 2947, pp. 173-186)\n"
+"(full text on Google Books) apparently "
+"supports this, according to\n"
+"this sci.crypt thread.\n"
+"The remainder of the PrivateKey is padded with zeroes."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/cryptography.html:167
+#: i2p2www/pages/site/docs/how/cryptography.html:264
+#: i2p2www/pages/site/docs/how/cryptography.html:343
+#: i2p2www/pages/site/docs/how/cryptography.html:382
+msgid "Obsolescence"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/cryptography.html:168
+msgid ""
+"The vulnerability of the network to an ElGamal attack and the impact of "
+"transitioning to a longer bit length is to be studied.\n"
+"It may be quite difficult to make any change backward-compatible."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/cryptography.html:176
+msgid "AES is used for symmetric encryption, in several cases:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/cryptography.html:181
+msgid "For transport encryption after DH key exchange"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/cryptography.html:185
+#, python-format
+msgid ""
+"For end-to-end (destination-to-destination) encryption as a part of ElGamal/AES+SessionTag"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/cryptography.html:195
+#, python-format
+msgid ""
+"For encryption of periodic tunnel "
+"test messages sent from the router to itself, through its own "
+"tunnels."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/cryptography.html:200
+#, python-format
+msgid ""
+"We use AES with 256 bit keys and 128 bit blocks in CBC mode.\n"
+"The padding used is specified in IETF RFC-2313 "
+"(PKCS#5 1.5, section 8.1 (for block type 02)).\n"
+"In this case, padding exists of pseudorandomly generated octets to match "
+"16 byte blocks.\n"
+"Specifically, see [the CBC code] and the "
+"Cryptix AES\n"
+"[implementation], as well as the padding, found"
+" in the\n"
+"ElGamalAESEngine.getPadding function."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/cryptography.html:265
+msgid ""
+"The vulnerability of the network to an AES attack and the impact of "
+"transitioning to a longer bit length is to be studied.\n"
+"It may be quite difficult to make any change backward-compatible."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/cryptography.html:270
+#: i2p2www/pages/site/docs/how/cryptography.html:362
+#: i2p2www/pages/site/docs/how/cryptography.html:388
+#: i2p2www/pages/site/docs/how/cryptography.html:456
+#: i2p2www/pages/site/docs/how/garlic-routing.html:281
+#: i2p2www/pages/site/docs/how/peer-selection.html:296
+msgid "References"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/cryptography.html:273
+msgid "Feb. 7, 2006 Status Notes"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/cryptography.html:280
+#, python-format
+msgid ""
+"Signatures are generated and verified with 1024 bit DSA (L=1024, N=160), "
+"as implemented in\n"
+"[DSAEngine].\n"
+"DSA was chosen because it is much faster for signatures than ElGamal."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/cryptography.html:286
+msgid "The DSA constants"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/cryptography.html:337
+#, python-format
+msgid ""
+"The Signing Public"
+" Key is 1024 bits.\n"
+"The Signing "
+"Private Key is 160 bits."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/cryptography.html:344
+#, python-format
+msgid ""
+"NIST 800-57\n"
+"recommends a minimum of (L=2048, N=224) for usage beyond 2010.\n"
+"This may be mitigated somewhat by the \"cryptoperiod\", or lifespan of a "
+"given key."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/cryptography.html:350
+msgid ""
+"The prime number was chosen in 2003,\n"
+"and the person that chose the number (TheCrypto) is currently no longer "
+"an I2P developer.\n"
+"As such, we do not know if the prime chosen is a 'strong prime'.\n"
+"If a larger prime is chosen for future purposes, this should be a strong "
+"prime, and we will document the construction process."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/cryptography.html:357
+msgid ""
+"The vulnerability of the network to a DSA attack and the impact of "
+"transitioning to longer keys is to be studied.\n"
+"It may be quite difficult to make any change backward-compatible."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/cryptography.html:365
+#: i2p2www/pages/site/docs/how/cryptography.html:367
+#, python-format
+msgid "Meeting %(num)s"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/cryptography.html:369
+msgid "Choosing the constants"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/cryptography.html:377
+#, python-format
+msgid ""
+"Hashes within I2P are plain old SHA256, as implemented in\n"
+"[SHA256Generator]"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/cryptography.html:383
+msgid ""
+"The vulnerability of the network to a SHA-256 attack and the impact of "
+"transitioning to a longer hash is to be studied.\n"
+"It may be quite difficult to make any change backward-compatible."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/cryptography.html:394
+msgid "Transports"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/cryptography.html:395
+msgid ""
+"At the lowest protocol layer,\n"
+"point-to-point inter-router communication is protected by the transport "
+"layer security.\n"
+"Both transports use 256 byte (2048 bit) Diffie-Hellman key exchange\n"
+"using\n"
+"the same shared prime and generator as specified "
+"above for ElGamal,\n"
+"followed by symmetric AES encryption as described above.\n"
+"This provides\n"
+"perfect "
+"forward secrecy\n"
+"on the transport links."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/cryptography.html:407
+msgid "NTCP connections"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/cryptography.html:409
+#, python-format
+msgid ""
+"NTCP connections are negotiated with a 2048 Diffie-Hellman "
+"implementation,\n"
+"using the router's identity to proceed with a station to station "
+"agreement, followed by\n"
+"some encrypted protocol specific fields, with all subsequent data "
+"encrypted with AES\n"
+"(as above).\n"
+"The primary reason to do the DH negotiation instead of using ElGamalAES+SessionTag is that it provides '(perfect) "
+"forward secrecy', while ElGamalAES+SessionTag does not."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/cryptography.html:417
+msgid ""
+"In order to migrate to a more standardized implementation (TLS/SSL or "
+"even SSH), the following issues must be addressed:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/cryptography.html:421
+msgid ""
+"Can we somehow reestablish sessions securely (ala session tags) or do we "
+"need to do full negotiation each time?"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/cryptography.html:424
+msgid ""
+"Can we simplify/avoid the x509 or other certificate formats and use our "
+"own RouterInfo structure (which \n"
+"contains the ElGamal and DSA keys)?"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/cryptography.html:429
+#, python-format
+msgid "See the NTCP specification for details."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/cryptography.html:433
+msgid "UDP connections"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/cryptography.html:434
+msgid ""
+"SSU (the UDP transport) encrypts each packet with AES256/CBC with both an"
+" explicit IV and MAC \n"
+"(HMAC-MD5-128) after agreeing upon an ephemeral session key through a "
+"2048 bit \n"
+"Diffie-Hellman exchange, station-to-station authentication with the other"
+" \n"
+"router's DSA key, plus each network message has their own hash for local "
+"integrity \n"
+"checking."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/cryptography.html:442
+#, python-format
+msgid "See the SSU specification for details."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/cryptography.html:446
+#, python-format
+msgid ""
+"WARNING - I2P's HMAC-MD5-128 used in SSU is apparently non-standard.\n"
+"Apparently, an early version of SSU used HMAC-SHA256, and then it was "
+"switched\n"
+"to MD5-128 for performance reasons, but left the 32-byte buffer size "
+"intact.\n"
+"See HMACGenerator.java and\n"
+"the 2005-07-05 status notes\n"
+"for details."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/elgamal-aes.html:2
+msgid "ElGamal/AES + SessionTag Encryption"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/elgamal-aes.html:3
+msgid "February 2011"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/elgamal-aes.html:7
+msgid "ElGamal/AES+SessionTags is used for end-to-end encryption."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/elgamal-aes.html:11
+msgid ""
+"As an unreliable, unordered, message based system, I2P uses a simple "
+"combination \n"
+"of asymmetric and symmetric encryption algorithms to provide data "
+"confidentiality \n"
+"and integrity to garlic messages. As a whole, the combination is referred"
+" \n"
+"to as ElGamal/AES+SessionTags, but that is an excessively verbose way to "
+"describe \n"
+"the use of 2048bit ElGamal, AES256, SHA256, and 32 byte nonces."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/elgamal-aes.html:19
+#: i2p2www/pages/site/docs/how/tech-intro.html:512
+msgid ""
+"The first time a router wants to encrypt a garlic message to another "
+"router, \n"
+"they encrypt the keying material for an AES256 session key with ElGamal "
+"and \n"
+"append the AES256/CBC encrypted payload after that encrypted ElGamal "
+"block. \n"
+"In addition to the encrypted payload, the AES encrypted section contains "
+"the \n"
+"payload length, the SHA256 hash of the unencrypted payload, as well as a "
+"number \n"
+"of \"session tags\" - random 32 byte nonces. The next time the sender "
+"wants \n"
+"to encrypt a garlic message to another router, rather than ElGamal "
+"encrypt \n"
+"a new session key they simply pick one of the previously delivered "
+"session \n"
+"tags and AES encrypt the payload like before, using the session key used "
+"with \n"
+"that session tag, prepended with the session tag itself. When a router "
+"receives \n"
+"a garlic encrypted message, they check the first 32 bytes to see if it "
+"matches \n"
+"an available session tag - if it does, they simply AES decrypt the "
+"message, \n"
+"but if it does not, they ElGamal decrypt the first block."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/elgamal-aes.html:35
+#: i2p2www/pages/site/docs/how/tech-intro.html:528
+msgid ""
+"Each session tag can be used only once so as to prevent internal "
+"adversaries \n"
+"from unnecessarily correlating different messages as being between the "
+"same \n"
+"routers. The sender of an ElGamal/AES+SessionTag encrypted message "
+"chooses \n"
+"when and how many tags to deliver, prestocking the recipient with enough "
+"tags \n"
+"to cover a volley of messages. Garlic messages may detect the successful "
+"tag \n"
+"delivery by bundling a small additional message as a clove (a \"delivery "
+"status \n"
+"message\") - when the garlic message arrives at the intended recipient "
+"and \n"
+"is decrypted successfully, this small delivery status message is one of "
+"the \n"
+"cloves exposed and has instructions for the recipient to send the clove "
+"back \n"
+"to the original sender (through an inbound tunnel, of course). When the "
+"original \n"
+"sender receives this delivery status message, they know that the session "
+"tags \n"
+"bundled in the garlic message were successfully delivered."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/elgamal-aes.html:50
+msgid ""
+"Session tags themselves have a short lifetime, after which they are \n"
+"discarded if not used. In addition, the quantity stored for each key is "
+"limited, \n"
+"as are the number of keys themselves - if too many arrive, either new or "
+"old \n"
+"messages may be dropped. The sender keeps track whether messages using "
+"session \n"
+"tags are getting through, and if there isn't sufficient communication it "
+"may \n"
+"drop the ones previously assumed to be properly delivered, reverting back"
+" \n"
+"to the full expensive ElGamal encryption.\n"
+"A session will continue to exist until all its tags are exhausted or "
+"expire."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/elgamal-aes.html:61
+msgid ""
+"Sessions are unidirectional. Tags are delivered from Alice to Bob,\n"
+"and Alice then uses the tags, one by one, in subsequent messages to Bob."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/elgamal-aes.html:66
+msgid ""
+"Sessions may be established between Destinations, between Routers, or\n"
+"between a Router and a Destination.\n"
+"Each Router and Destination maintains its own Session Key Manager to\n"
+"keep track of Session Keys and Session Tags.\n"
+"Separate Session Key Managers prevents correlation of multiple "
+"Destinations\n"
+"to each other or a Router by adversaries."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/elgamal-aes.html:77
+msgid "Message Reception"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/elgamal-aes.html:78
+msgid ""
+"Each message received has one of two\n"
+"the two possible conditions:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/elgamal-aes.html:84
+msgid ""
+"It is part of an existing session and contains a Session Tag and an AES "
+"encrypted block"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/elgamal-aes.html:85
+msgid "It is for a new session and contains both ElGamal and AES encrypted blocks"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/elgamal-aes.html:88
+msgid ""
+"When a router receives a message, it will first assume it is from\n"
+"an existing session and attempt to look up the Session Tag and decrypt "
+"the following data using AES.\n"
+"If that fails, it will assume it is for a new session and attempt to\n"
+"decrypt it using ElGamal."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/elgamal-aes.html:97
+msgid "New Session Message Specification"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/elgamal-aes.html:98
+msgid ""
+"A New Session ElGamal Message contains two parts, an encrypted ElGamal "
+"block\n"
+"and an encrypted AES block."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/elgamal-aes.html:103
+msgid "The encrypted message contains:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/elgamal-aes.html:127
+msgid "ElGamal Block"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/elgamal-aes.html:128
+msgid "The encrypted ElGamal Block is always 514 bytes long."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/elgamal-aes.html:132
+msgid "The unencrypted ElGamal data is 222 bytes long, containing:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/elgamal-aes.html:164
+#, python-format
+msgid ""
+"The 32-byte\n"
+"Session Key\n"
+"is the identifier for the session.\n"
+"The 32-byte Pre-IV will be used to generate the IV for the AES block that"
+" follows;\n"
+"the IV is the first 16 bytes of the SHA-256 Hash of the Pre-IV."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/elgamal-aes.html:172
+#, python-format
+msgid ""
+"The 222 byte payload is encrypted\n"
+"using ElGamal\n"
+"and the encrypted block is 514 bytes long.\n"
+""
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/elgamal-aes.html:179
+msgid "AES Block"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/elgamal-aes.html:180
+msgid "The unencrypted data in the AES block contains the following:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/elgamal-aes.html:224
+#, python-format
+msgid "2-byte Integer, 0-200"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/elgamal-aes.html:228
+#, python-format
+msgid ""
+"That many 32-byte Session Tags"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/elgamal-aes.html:232
+#, python-format
+msgid "4-byte Integer"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/elgamal-aes.html:236
+#, python-format
+msgid ""
+"The 32-byte SHA256 Hash of"
+" the payload"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/elgamal-aes.html:240
+msgid "A one-byte value. Normally == 0. If == 0x01, a Session Key follows"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/elgamal-aes.html:244
+#, python-format
+msgid ""
+"A 32-byte Session "
+"Key,\n"
+" to replace the old key, and is only present if preceding"
+" flag is 0x01"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/elgamal-aes.html:249
+msgid "the data"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/elgamal-aes.html:251
+msgid ""
+"Random data to a multiple of 16 bytes for the total length.\n"
+" May contain more than the minimum required padding."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/elgamal-aes.html:256
+msgid "Minimum length: 48 bytes"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/elgamal-aes.html:260
+#, python-format
+msgid ""
+"The data is then AES Encrypted,\n"
+"using the session key and IV (calculated from the pre-IV) from the "
+"ElGamal section.\n"
+"The encrypted AES Block length is variable but is always a multiple of 16"
+" bytes.\n"
+""
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/elgamal-aes.html:269
+#, python-format
+msgid ""
+"Actual max payload length, and max block length, is less than 64 KB; see "
+"the I2NP Overview."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/elgamal-aes.html:272
+msgid "New Session Key is currently unused and is never present."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/elgamal-aes.html:277
+msgid "Existing Session Message Specification"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/elgamal-aes.html:278
+msgid ""
+"The session tags delivered successfully are remembered for a \n"
+"brief period (15 minutes currently) until they are used or discarded.\n"
+"A tag is used by packaging one in an Existing Session Message that\n"
+"contains only an AES encrypted block, and is not preceded by an\n"
+"ElGamal block."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/elgamal-aes.html:286
+msgid ""
+"The existing session message is\n"
+"as follows:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/elgamal-aes.html:309
+#, python-format
+msgid ""
+"A 32-byte Session "
+"Tag\n"
+" previously delivered in an AES block"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/elgamal-aes.html:314
+msgid "As specified above."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/elgamal-aes.html:318
+msgid ""
+"The session tag also serves as\n"
+"the pre-IV. The IV is the first 16 bytes of the SHA-256 Hash of the "
+"sessionTag."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/elgamal-aes.html:323
+msgid ""
+"To decode a message from an existing session, a router looks up the "
+"Session Tag to find an\n"
+"associated Session Key. If the Session Tag is found, the AES block is "
+"decrypted using the associated Session Key.\n"
+"If the tag is not found, the message is assumed to be a New Session Message."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/elgamal-aes.html:332
+msgid ""
+"There are many possible areas to tune the Session Key Manager's "
+"algorithms;\n"
+"some may interact with the streaming library behavior, or have "
+"significant\n"
+"impact on overall performance."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/elgamal-aes.html:338
+msgid ""
+"Delivery of too many tags at one time may impose substantial overhead for"
+" brief streaming connections\n"
+"or datagrams, and increase the chance of message loss.\n"
+"We currently deliver 40 tags at a time (1280 bytes).\n"
+"32 (1024 bytes) may be better for tunnel fragmentation."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/elgamal-aes.html:345
+msgid ""
+"A few tags could be delivered in each of several messages, or lots of "
+"tags all at once."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/elgamal-aes.html:349
+msgid ""
+"It is also important to study and tune\n"
+"the low-tag thresholds at which more tags are sent."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/elgamal-aes.html:354
+msgid ""
+"The number of tags delivered could depend on message size, keeping in "
+"mind\n"
+"the eventual padding to 1KB at the tunnel message layer."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/elgamal-aes.html:359
+msgid ""
+"Clients could send an estimate of session lifetime to the router, as an "
+"advisory\n"
+"on the number of tags required."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/elgamal-aes.html:364
+msgid ""
+"Delivery of too few tags causes the router to fall back to an expensive "
+"ElGamal encryption."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/elgamal-aes.html:368
+msgid ""
+"The router may assume delivery of Session Tags, or await acknowledgement "
+"before using them;\n"
+"there are tradeoffs for each strategy."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/elgamal-aes.html:373
+msgid ""
+"For very brief messages, almost the full 222 bytes of the pre-IV and "
+"padding fields in the ElGamal block\n"
+"could be used for the entire message, instead of establishing a session."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/elgamal-aes.html:378
+msgid ""
+"Evaluate padding strategy; currently we pad to a minimum of 128 bytes.\n"
+"Would be better to add a few tags to small messages than pad."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/elgamal-aes.html:383
+msgid ""
+"Perhaps things could be more efficient if the Session Tag system was "
+"bidirectional,\n"
+"so tags delivered in the 'forward' path could be used in the 'reverse' "
+"path,\n"
+"thus avoiding ElGamal in the initial response.\n"
+"The router currently plays some tricks like this when sending\n"
+"tunnel test messages to itself."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/elgamal-aes.html:391
+#, python-format
+msgid ""
+"Change from Session Tags to\n"
+"a synchronized PRNG."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/elgamal-aes.html:396
+#, python-format
+msgid ""
+"Several of these ideas may require a new I2NP message type, or\n"
+"set a flag in the\n"
+"Delivery Instructions,\n"
+"or set a magic number in the first few bytes of the Session Key field\n"
+"and accept a small risk of the random Session Key matching the magic "
+"number."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/garlic-routing.html:2
+msgid "Garlic Routing"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/garlic-routing.html:6
+msgid "Garlic Routing and \"Garlic\" Terminology"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/garlic-routing.html:7
+msgid ""
+"The terms \"garlic routing\" and \"garlic encryption\" are often used "
+"rather loosely when referring to I2P's technology.\n"
+"Here, we explain the history of the terms, the various meanings, and\n"
+"the usage of \"garlic\" methods in I2P."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/garlic-routing.html:13
+msgid ""
+"\"Garlic routing\" was first coined by\n"
+"Michael J. Freedman\n"
+"in Roger Dingledine's Free Haven \n"
+"Master's thesis "
+"Section 8.1.1 (June 2000), as derived from \n"
+"Onion Routing."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/garlic-routing.html:21
+msgid ""
+"\"Garlic\" may have been used originally by I2P developers because I2P "
+"implements a form of\n"
+"bundling as Freedman describes, or simply to emphasize general "
+"differences from Tor.\n"
+"The specific reasoning may be lost to history.\n"
+"Generally, when referring to I2P, the term \"garlic\" may mean one of "
+"three things:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/garlic-routing.html:28
+#: i2p2www/pages/site/docs/how/garlic-routing.html:39
+msgid "Layered Encryption"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/garlic-routing.html:29
+msgid "Bundling multiple messages together"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/garlic-routing.html:30
+#: i2p2www/pages/site/docs/how/garlic-routing.html:96
+msgid "ElGamal/AES Encryption"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/garlic-routing.html:33
+msgid ""
+"Unfortunately, I2P's usage of \"garlic\" terminology over the past seven "
+"years has not always been precise; therefore the reader is\n"
+"cautioned when encountering the term.\n"
+"Hopefully, the explanation below will make things clear."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/garlic-routing.html:40
+msgid ""
+"Onion routing is a technique for building paths, or tunnels, through a "
+"series of peers,\n"
+"and then using that tunnel.\n"
+"Messages are repeatedly encrypted by the originator, and then decrypted "
+"by each hop.\n"
+"During the building phase, only the routing instructions for the next hop"
+" are exposed to each peer.\n"
+"During the operating phase, messages are passed through the tunnel, and "
+"the\n"
+"message and its routing instructions are only exposed to the endpoint of "
+"the tunnel."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/garlic-routing.html:49
+#, python-format
+msgid ""
+"This is similar to the way Mixmaster\n"
+"(see network comparisons) sends messages "
+"- taking a message, encrypting it\n"
+"to the recipient's public key, taking that encrypted message and "
+"encrypting\n"
+"it (along with instructions specifying the next hop), and then taking "
+"that\n"
+"resulting encrypted message and so on, until it has one layer of "
+"encryption\n"
+"per hop along the path."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/garlic-routing.html:58
+msgid ""
+"In this sense, \"garlic routing\" as a general concept is identical to "
+"\"onion routing\".\n"
+"As implemented in I2P, of course, there are several differences from the "
+"implementation in Tor; see below.\n"
+"Even so, there are substantial similarities such that I2P benefits from a"
+"\n"
+"large amount of"
+" academic research on onion routing,\n"
+"Tor, and similar "
+"mixnets."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/garlic-routing.html:67
+msgid "Bundling Multiple Messages"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/garlic-routing.html:68
+msgid ""
+"Michael Freedman defined \"garlic routing\" as an extension to onion "
+"routing,\n"
+"in which multiple messages are bundled together.\n"
+"He called each message a \"bulb\".\n"
+"All the messages, each with its own delivery instructions, are exposed at"
+" the\n"
+"endpoint.\n"
+"This allows the efficient bundling of an onion routing \"reply block\" "
+"with the original message."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/garlic-routing.html:77
+msgid ""
+"This concept is implemented in I2P, as described below.\n"
+"Our term for garlic \"bulbs\" is \"cloves\".\n"
+"Any number of messages can be\n"
+"contained, instead of just a single message.\n"
+"This is a significant distinction from the onion routing implemented in "
+"Tor.\n"
+"However, it is only one of many major architectural differences between "
+"I2P and Tor;\n"
+"perhaps it is not, by itself, enough to justify a change in terminology."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/garlic-routing.html:87
+msgid ""
+"Another difference\n"
+"from the method described by Freedman\n"
+"is that the path is unidirectional - there is no \"turning point\" as "
+"seen in onion routing\n"
+"or mixmaster reply blocks, which greatly simplifies the algorithm and "
+"allows for more flexible\n"
+"and reliable delivery."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/garlic-routing.html:97
+#, python-format
+msgid ""
+"In some cases, \"garlic encryption\" may simply mean\n"
+"ElGamal/AES+SessionTag encryption\n"
+"(without multiple layers)."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/garlic-routing.html:105
+msgid "\"Garlic\" Methods in I2P"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/garlic-routing.html:106
+msgid ""
+"Now that we've defined various \"garlic\" terms, we can say that\n"
+"I2P uses garlic routing, bundling and encryption in three places:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/garlic-routing.html:111
+msgid "For building and routing through tunnels (layered encryption)"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/garlic-routing.html:112
+msgid ""
+"For determining the success or failure of end to end message delivery "
+"(bundling)"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/garlic-routing.html:113
+msgid ""
+"For publishing some network database entries (dampening the probability "
+"of a successful traffic analysis attack) (ElGamal/AES)"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/garlic-routing.html:116
+msgid ""
+"There are also significant ways that this technique can be used to "
+"improve the performance of the network, \n"
+"exploiting transport latency/throughput tradeoffs, and branching data "
+"through redundant paths to increase reliability."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/garlic-routing.html:122
+msgid "Tunnel Building and Routing"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/garlic-routing.html:123
+msgid ""
+"In I2P, tunnels are unidirectional. Each party builds two tunnels,\n"
+"one for outbound and one for inbound traffic.\n"
+"Therefore, four tunnels are required for a single round-trip message and "
+"reply."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/garlic-routing.html:129
+#, python-format
+msgid ""
+"Tunnels are built, and then used, with layered encryption.\n"
+"This is described on the\n"
+"tunnel implementation page.\n"
+"Tunnel building details are defined on\n"
+"this page.\n"
+"We use\n"
+"ElGamal/AES+SessionTag for the encryption."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/garlic-routing.html:141
+#, python-format
+msgid ""
+"Tunnels are a general-purpose mechanism to transport all\n"
+"I2NP messages, and\n"
+"Garlic Messages are not used to "
+"build tunnels.\n"
+"We do not bundle multiple\n"
+"I2NP messages into a single\n"
+"Garlic Message for unwrapping at "
+"the outbound tunnel endpoint;\n"
+"the tunnel encryption is sufficient."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/garlic-routing.html:152
+msgid "End-to-End Message Bundling"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/garlic-routing.html:153
+#, python-format
+msgid ""
+"At the layer above tunnels, I2P delivers end-to-end messages between\n"
+"Destinations.\n"
+"Just as within a single tunnel, we use\n"
+"ElGamal/AES+SessionTag for the encryption."
+"\n"
+"Each client message as delivered to the router through the\n"
+"I2CP interface becomes a single\n"
+"Garlic Clove\n"
+"with its own\n"
+"Delivery Instructions,\n"
+"inside a\n"
+"Garlic Message.\n"
+"Delivery Instructions may specify a Destination, Router, or Tunnel."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/garlic-routing.html:172
+msgid ""
+"Generally, a Garlic Message will contain only one clove.\n"
+"However, the router will periodically bundle two additional\n"
+"cloves in the Garlic Message:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/garlic-routing.html:177
+msgid "Garlic Message Cloves"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/garlic-routing.html:180
+#, python-format
+msgid ""
+"A\n"
+"Delivery Status Message,\n"
+"with\n"
+"Delivery Instructions\n"
+"specifying that it be sent back to the originating router as an "
+"acknowledgment.\n"
+"This is similar to the \"reply block\" or \"reply onion\"\n"
+"described in the references.\n"
+"It is used for determining the success or failure of end to end message "
+"delivery.\n"
+"The originating router may, upon failure to receive the Delivery Status "
+"Message\n"
+"within the expected time period, modify the routing to the far-end "
+"Destination,\n"
+"or take other actions."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/garlic-routing.html:194
+#, python-format
+msgid ""
+"A\n"
+"Database Store Message,\n"
+"containing a\n"
+"LeaseSet\n"
+"for the originating Destination, with\n"
+"Delivery Instructions\n"
+"specifying the far-end destination's router.\n"
+"By periodically bundling a LeaseSet, the router ensures that the far-end "
+"will be able\n"
+"to maintain communications.\n"
+"Otherwise the far-end would have to query a floodfill router for the "
+"network database entry,\n"
+"and all LeaseSets would have to be published to the network database, as "
+"explained on the\n"
+"network database page."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/garlic-routing.html:213
+#, python-format
+msgid ""
+"In the current implementation, the Delivery Status and Database Store "
+"Messages\n"
+"are bundled when the local LeaseSet changes, when additional\n"
+"Session Tags\n"
+"are delivered, or if the messages have not been bundled in the previous "
+"minute."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/garlic-routing.html:220
+msgid ""
+"Obviously, the additional messages are currently bundled for specific "
+"purposes,\n"
+"and not part of a general-purpose routing scheme."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/garlic-routing.html:226
+msgid "Storage to the Floodfill Network Database"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/garlic-routing.html:227
+#, python-format
+msgid ""
+"As explained on the\n"
+"network database page,\n"
+"local\n"
+"LeaseSets\n"
+"are sent to floodfill routers in a\n"
+"Database Store Message\n"
+"wrapped in a\n"
+"Garlic Message\n"
+"so it is not visible to the tunnel's outbound gateway."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/garlic-routing.html:243
+#, python-format
+msgid ""
+"The Garlic Message mechanism is very flexible and provides a structure "
+"for\n"
+"implementing many types of mixnet delivery methods.\n"
+"Together with the unused delay option in the\n"
+"tunnel message Delivery "
+"Instructions,\n"
+"a wide spectrum of batching, delay, mixing, and routing strategies are "
+"possible."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/garlic-routing.html:251
+msgid ""
+"In particular, there is potential for much more flexibility at the "
+"outbound tunnel endpoint.\n"
+"Messages could possibly be routed from there to one of several tunnels\n"
+"(thus minimizing point-to-point connections), or multicast to several "
+"tunnels\n"
+"for redundancy, or streaming audio and video."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/garlic-routing.html:258
+msgid ""
+"Such experiments may conflict with the need to ensure security and "
+"anonymity, such\n"
+"as limiting certain routing paths, restricting the types of I2NP messages"
+" that may\n"
+"be forwarded along various paths, and enforcing certain message "
+"expiration times."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/garlic-routing.html:264
+#, python-format
+msgid ""
+"As a part of\n"
+"ElGamal/AES encryption,\n"
+"a garlic message contains a sender\n"
+"specified amount of padding data, allowing the sender to take active "
+"countermeasures \n"
+"against traffic analysis.\n"
+"This is not currently used, beyond the requirement to pad to a multiple "
+"of 16 bytes."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/garlic-routing.html:273
+#, python-format
+msgid ""
+"Encryption of additional messages to and from the\n"
+"floodfill routers."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/garlic-routing.html:283
+msgid ""
+"The term garlic routing was first coined in Roger Dingledine's Free Haven"
+" \n"
+"Master's thesis "
+"(June 2000),\n"
+"see Section 8.1.1 authored by\n"
+"Michael J. Freedman."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/garlic-routing.html:290
+msgid "Onion router publications"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/garlic-routing.html:292
+msgid "Onion Routing on Wikipedia"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/garlic-routing.html:294
+msgid "Garlic Routing on Wikipedia"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/garlic-routing.html:296
+#, python-format
+msgid ""
+"I2P Meeting 58 (2003) discussing the "
+"implementation of garlic routing"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/garlic-routing.html:302
+msgid "Free Haven publications"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/garlic-routing.html:304
+msgid ""
+"Onion routing was first described in Hiding Routing Information\n"
+"by David M. Goldschlag, Michael G. Reed, and Paul F. Syverson in 1996."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/intro.html:2
+msgid "A Gentle Introduction"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/intro.html:5
+msgid "A Gentle Introduction to How I2P Works"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/intro.html:7
+msgid ""
+"I2P is a project to build, deploy, and maintain a network supporting "
+"secure and anonymous\n"
+"communication. People using I2P are in control of the tradeoffs between "
+"anonymity, reliability,\n"
+"bandwidth usage, and latency. There is no central point in the network on"
+" which pressure can be\n"
+"exerted to compromise the integrity, security, or anonymity of the "
+"system. The network supports\n"
+"dynamic reconfiguration in response to various attacks, and has been "
+"designed to make use of\n"
+"additional resources as they become available. Of course, all aspects of "
+"the network are open and\n"
+"freely available."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/intro.html:17
+msgid ""
+"Unlike many other anonymizing networks, I2P doesn't try to provide "
+"anonymity by hiding the\n"
+"originator of some communication and not the recipient, or the other way "
+"around. I2P is designed to\n"
+"allow peers using I2P to communicate with each other anonymously — "
+"both sender and recipient\n"
+"are unidentifiable to each other as well as to third parties. For "
+"example, today there are both\n"
+"in-I2P web sites (allowing anonymous publishing / hosting) as well as "
+"HTTP proxies to the normal web\n"
+"(allowing anonymous web browsing). Having the ability to run servers "
+"within I2P is essential, as it\n"
+"is quite likely that any outbound proxies to the normal Internet will be "
+"monitored, disabled, or\n"
+"even taken over to attempt more malicious attacks."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/intro.html:28
+#, python-format
+msgid ""
+"The network itself is message oriented - it is essentially a secure and "
+"anonymous IP layer, where\n"
+"messages are addressed to cryptographic keys (Destinations) and can be "
+"significantly larger than IP\n"
+"packets. Some example uses of the network include \"eepsites\" "
+"(webservers hosting normal web\n"
+"applications within I2P), a BitTorrent client (\"I2PSnark\"), or a "
+"distributed data store. With the\n"
+"help of the I2PTunnel application, we are "
+"able to stream traditional\n"
+"TCP/IP applications over I2P, such as SSH, IRC, a squid proxy, and even "
+"streaming audio. Most people\n"
+"will not use I2P directly, or even need to know they're using it. Instead"
+" their view will be of one\n"
+"of the I2P enabled applications, or perhaps as a little controller app to"
+" turn on and off various\n"
+"proxies to enable the anonymizing functionality."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/intro.html:40
+#, python-format
+msgid ""
+"An essential part of designing, developing, and testing an anonymizing "
+"network is to define the threat model, since there is no such thing "
+"as \"true\" anonymity, just\n"
+"increasingly expensive costs to identify someone. Briefly, I2P's intent "
+"is to allow people to\n"
+"communicate in arbitrarily hostile environments by providing good "
+"anonymity, mixed in with\n"
+"sufficient cover traffic provided by the activity of people who require "
+"less anonymity. This way,\n"
+"some users can avoid detection by a very powerful adversary, while others"
+" will try to evade a weaker\n"
+"entity, all on the same network, where each one's messages are "
+"essentially indistinguishable\n"
+"from the others."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/intro.html:51
+msgid "Why?"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/intro.html:52
+#, python-format
+msgid ""
+"There are a multitude of reasons why we need a system to support "
+"anonymous communication, and\n"
+"everyone has their own personal rationale. There are many other\n"
+"efforts working on finding ways to provide varying degrees of "
+"anonymity to people through the\n"
+"Internet, but we could not find any that met our needs or threat model."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/intro.html:59
+msgid "How?"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/intro.html:61
+#, python-format
+msgid ""
+"The network at a glance is made up of a set of nodes (\"routers\") with a"
+" number of unidirectional\n"
+"inbound and outbound virtual paths (\"tunnels\", as outlined on the tunnel routing page). Each router is "
+"identified by a cryptographic RouterIdentity which is\n"
+"typically long lived. These routers communicate with each other through "
+"existing transport\n"
+"mechanisms (TCP, UDP, etc), passing various messages. Client applications"
+" have their own\n"
+"cryptographic identifier (\"Destination\") which enables it to send and "
+"receive messages. These\n"
+"clients can connect to any router and authorize the temporary allocation "
+"(\"lease\") of some tunnels\n"
+"that will be used for sending and receiving messages through the network."
+" I2P has its own internal\n"
+"network database (using a modification of the "
+"Kademlia algorithm) for\n"
+"distributing routing and contact information securely."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/intro.html:74
+msgid "Network topology example"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/intro.html:76
+msgid ""
+"In the above, Alice, Bob, Charlie, and Dave are all running routers with "
+"a single Destination on\n"
+"their local router. They each have a pair of 2-hop inbound tunnels per "
+"destination (labeled 1, 2, 3,\n"
+"4, 5 and 6), and a small subset of each of those router's outbound tunnel"
+" pool is shown with 2-hop\n"
+"outbound tunnels. For simplicity, Charlie's inbound tunnels and Dave's "
+"outbound tunnels are not\n"
+"shown, nor are the rest of each router's outbound tunnel pool (typically "
+"stocked with a few tunnels\n"
+"at a time). When Alice and Bob talk to each other, Alice sends a message "
+"out one of her (pink)\n"
+"outbound tunnels targeting one of Bob's (green) inbound tunnels (tunnel 3"
+" or 4). She knows to send\n"
+"to those tunnels on the correct router by querying the network database, "
+"which is constantly updated\n"
+"as new leases are authorized and old ones expire."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/intro.html:88
+#, python-format
+msgid ""
+"If Bob wants to reply to Alice, he simply goes through the same process -"
+" send a message out one of\n"
+"his outbound tunnels targeting one of Alice's inbound tunnels (tunnel 1 "
+"or 2). To make things\n"
+"easier, most messages sent between Alice and Bob are garlic\n"
+"wrapped, bundling the sender's own current lease information so that the "
+"recipient can reply\n"
+"immediately without having to look in the network database for the "
+"current data."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/intro.html:96
+#, python-format
+msgid ""
+"To deal with a wide range of attacks, I2P is fully distributed with no "
+"centralized resources - and\n"
+"hence there are no directory servers keeping statistics regarding the "
+"performance and reliability of\n"
+"routers within the network. As such, each router must keep and maintain "
+"profiles of various routers\n"
+"and is responsible for selecting appropriate peers to meet the anonymity,"
+" performance, and\n"
+"reliability needs of the users, as described in the peer selection\n"
+"page."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/intro.html:105
+#, python-format
+msgid ""
+"The network itself makes use of a significant number of cryptographic\n"
+"techniques and algorithms - a full laundry list includes 2048bit "
+"ElGamal encryption, 256bit AES\n"
+"in CBC mode with PKCS#5 padding, 1024bit DSA signatures, SHA256 hashes, "
+"2048bit Diffie-Hellman\n"
+"negotiated connections with station to station authentication, and ElGamal / AES+SessionTag."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/intro.html:113
+msgid ""
+"Content sent over I2P is encrypted through three layers garlic encryption"
+" (used to verify the\n"
+"delivery of the message to the recipient), tunnel encryption (all "
+"messages passing through a tunnel\n"
+"is encrypted by the tunnel gateway to the tunnel endpoint), and inter "
+"router transport layer\n"
+"encryption (e.g. the TCP transport uses AES256 with ephemeral keys)."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/intro.html:120
+msgid ""
+"End-to-end (I2CP) encryption (client application to server application) "
+"was disabled in I2P release\n"
+"0.6; end-to-end (garlic) encryption (I2P client router to I2P server "
+"router) from Alice's router \"a\"\n"
+"to Bob's router \"h\" remains. Notice the different use of terms! All "
+"data from a to h is end-to-end\n"
+"encrypted, but the I2CP connection between the I2P router and the "
+"applications is not end-to-end\n"
+"encrypted! A and h are the routers of Alice and Bob, while Alice and Bob "
+"in following chart are the\n"
+"applications running atop of I2P."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/intro.html:129
+msgid "End to end layered encryption"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/intro.html:131
+#, python-format
+msgid ""
+"The specific use of these algorithms are outlined elsewhere."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/intro.html:135
+msgid ""
+"The two main mechanisms for allowing people who need strong anonymity to "
+"use the network are\n"
+"explicitly delayed garlic routed messages and more comprehensive tunnels "
+"to include support for\n"
+"pooling and mixing messages. These are currently planned for release 3.0,"
+" but garlic routed messages\n"
+"with no delays and FIFO tunnels are currently in place. Additionally, the"
+" 2.0 release will allow\n"
+"people to set up and operate behind restricted routes (perhaps with "
+"trusted peers), as well as the\n"
+"deployment of more flexible and anonymous transports."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/intro.html:144
+#, python-format
+msgid ""
+"Some questions have been raised with regards to the scalability of I2P, "
+"and reasonably so. There\n"
+"will certainly be more analysis over time, but peer lookup and "
+"integration should be bounded by\n"
+"O(log(N)) due to the network "
+"database's algorithm, while end\n"
+"to end messages should be O(1) (scale free), since messages "
+"go out K hops through the\n"
+"outbound tunnel and another K hops through the inbound tunnel, with K no "
+"longer than 3. The size of\n"
+"the network (N) bears no impact."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/intro.html:153
+msgid "When?"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/intro.html:154
+#, python-format
+msgid ""
+"I2P initially began in Feb 2003 as a proposed modification to Freenet to allow it to use "
+"alternate transports, such as JMS, then grew into its own as an\n"
+"'anonCommFramework' in April 2003, turning into I2P in July, with code "
+"being written in earnest\n"
+"starting in August '03. I2P is currently under development, following the"
+" roadmap."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/intro.html:164
+msgid "Who?"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/intro.html:165
+#, python-format
+msgid ""
+"We have a small team spread around several "
+"continents, working to advance\n"
+"different aspects of the project. We are very open to other developers "
+"who want to get involved and\n"
+"anyone else who would like to contribute in other ways, such as "
+"critiques, peer review, testing,\n"
+"writing I2P enabled applications, or documentation. The entire system is "
+"open source - the router\n"
+"and most of the SDK are outright public domain with some BSD and Cryptix "
+"licensed code, while some\n"
+"applications like I2PTunnel and I2PSnark are GPL. Almost everything is "
+"written in Java (1.5+),\n"
+"though some third party applications are being written in Python and "
+"other languages. The code works\n"
+"on Sun Java SE and other Java Virtual"
+" Machines."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/intro.html:176
+msgid "Where?"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/intro.html:177
+#, python-format
+msgid ""
+"Anyone interested should join us on the IRC channel #i2p (hosted "
+"concurrently on irc.freenode.net,\n"
+"irc.postman.i2p, irc.freshcoffee.i2p, irc.welterde.i2p and "
+"irc.einirc.de). There are currently no\n"
+"scheduled development meetings, however archives"
+" are available."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/intro.html:183
+#, python-format
+msgid "The current source is available in monotone."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/intro.html:188
+#, python-format
+msgid "See the Index to Technical Documentation."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:2
+msgid "The Network Database"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:3
+#: i2p2www/pages/site/docs/spec/updates.html:3
+msgid "October 2013"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:8
+msgid ""
+"I2P's netDb is a specialized distributed database, containing \n"
+"just two types of data - router contact information (RouterInfos) "
+"and destination contact\n"
+"information (LeaseSets). Each piece of data is signed by the "
+"appropriate party and verified\n"
+"by anyone who uses or stores it. In addition, the data has liveliness "
+"information\n"
+"within it, allowing irrelevant entries to be dropped, newer entries to "
+"replace\n"
+"older ones, and protection against certain classes of attack."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:17
+msgid ""
+"The netDb is distributed with a simple technique called \"floodfill\",\n"
+"where a subset of all routers, called \"floodfill routers\", maintains "
+"the distributed database."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:25
+msgid ""
+"When an I2P router wants to contact another router, they need to know "
+"some \n"
+"key pieces of data - all of which are bundled up and signed by the router"
+" into\n"
+"a structure called the \"RouterInfo\", which is distributed with the "
+"SHA256 of the router's identity\n"
+"as the key. The structure itself contains:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:32
+msgid ""
+"The router's identity (a 2048bit ElGamal encryption key, a 1024bit DSA "
+"signing key, and a certificate)"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:33
+msgid ""
+"The contact addresses at which it can be reached (e.g. TCP: example.org "
+"port 4108)"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:34
+msgid "When this was published"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:35
+msgid "A set of arbitrary text options"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:36
+msgid "The signature of the above, generated by the identity's DSA signing key"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:39
+msgid ""
+"The following text options, while not strictly required, are expected\n"
+"to be present:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:45
+msgid ""
+"Capabilities flags - used to indicate floodfill participation, "
+"approximate bandwidth, and perceived reachability"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:48
+msgid "The core library version, always the same as the router version"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:51
+msgid ""
+"Basic network compatibility - A router will refuse to communicate with a "
+"peer having a different netId"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:54
+msgid "Used to determine compatibility with newer features and messages"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:57
+msgid ""
+"Always sent as 90m, for compatibility with an older scheme where routers "
+"published their actual uptime,\n"
+"and only sent tunnel requests to peers whose was more than 60m"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:62
+msgid ""
+"These values are used by other routers for basic decisions.\n"
+"Should we connect to this router? Should we attempt to route a tunnel "
+"through this router?\n"
+"The bandwidth capability flag, in particular, is used only to determine "
+"whether\n"
+"the router meets a minimum threshold for routing tunnels.\n"
+"Above the minimum threshold, the advertised bandwidth is not used or "
+"trusted anywhere\n"
+"in the router, except for display in the user interface and for debugging"
+" and network analysis."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:72
+#, python-format
+msgid ""
+"Additional text options include\n"
+"a small number of statistics about the router's health, which are "
+"aggregated by\n"
+"sites such as %(stats)s\n"
+"for network performance analysis and debugging.\n"
+"These statistics were chosen to provide data crucial to the developers,\n"
+"such as tunnel build success rates, while balancing the need for such "
+"data\n"
+"with the side-effects that could result from revealing this data.\n"
+"Current statistics are limited to:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:83
+msgid "Client and exploratory tunnel build success, reject, and timeout rates"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:84
+msgid "1 hour average number of participating tunnels"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:87
+msgid ""
+"The data published can be seen in the router's user interface,\n"
+"but is not used or trusted within the router.\n"
+"As the network has matured, we have gradually removed most of the "
+"published\n"
+"statistics to improve anonymity, and we plan to remove more in future "
+"releases."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:95
+msgid "RouterInfo specification"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:98
+msgid "RouterInfo Javadoc"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:101
+msgid "RouterInfo Expiration"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:102
+msgid ""
+"RouterInfos have no set expiration time.\n"
+"Each router is free to maintain its own local policy to trade off the "
+"frequency of RouterInfo lookups\n"
+"with memory or disk usage.\n"
+"In the current implementation, there are the following general policies:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:109
+msgid ""
+"There is no expiration during the first hour of uptime, as the persistent"
+" stored data may be old."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:112
+msgid "There is no expiration if there are 25 or less RouterInfos."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:115
+msgid ""
+"As the number of local RouterInfos grows, the expiration time shrinks, in"
+" an attempt to maintain\n"
+"a reasonable number RouterInfos. The expiration time with less than 120 "
+"routers is 72 hours,\n"
+"while expiration time with 300 routers is around 30 hours."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:120
+#, python-format
+msgid ""
+"RouterInfos containing SSU introducers expire in "
+"about an hour, as\n"
+"the introducer list expires in about that time."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:124
+msgid ""
+"Floodfills use a short expiration time (1 hour) for all local "
+"RouterInfos, as valid RouterInfos will\n"
+"be frequently republished to them."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:130
+msgid "RouterInfo Persistent Storage"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:132
+msgid ""
+"RouterInfos are periodically written to disk so that they are available "
+"after a restart."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:139
+msgid ""
+"The second piece of data distributed in the netDb is a \"LeaseSet\" - "
+"documenting\n"
+"a group of tunnel entry points (leases) for a particular client "
+"destination.\n"
+"Each of these leases specify the following information:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:145
+msgid "The tunnel gateway router (by specifying its identity)"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:146
+msgid "The tunnel ID on that router to send messages with (a 4 byte number)"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:147
+msgid "When that tunnel will expire."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:149
+msgid ""
+"The LeaseSet itself is stored in the netDb under\n"
+"the key derived from the SHA256 of the destination."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:154
+msgid "In addition to these leases, the LeaseSet includes:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:158
+msgid ""
+"The destination itself (a 2048bit ElGamal encryption key, 1024bit DSA "
+"signing key and a certificate)"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:159
+msgid ""
+"Additional encryption public key: used for end-to-end encryption of "
+"garlic messages"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:160
+msgid ""
+"Additional signing public key: intended for LeaseSet revocation, but is "
+"currently unused."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:161
+msgid ""
+"Signature of all the LeaseSet data, to make sure the Destination "
+"published the LeaseSet."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:165
+msgid "Lease specification"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:167
+msgid "LeaseSet specification"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:170
+msgid "Lease Javadoc"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:172
+msgid "LeaseSet Javadoc"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:176
+msgid "Unpublished LeaseSets"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:177
+msgid ""
+"A LeaseSet for a destination used only for outgoing connections is "
+"unpublished.\n"
+"It is never sent for publication to a floodfill router.\n"
+"\"Client\" tunnels, such as those for web browsing and IRC clients, are "
+"unpublished.\n"
+"Servers will still be able to send messages back to those unpublished "
+"destinations,\n"
+"because of I2NP storage messages."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:187
+msgid "Revoked LeaseSets"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:188
+msgid ""
+"A LeaseSet may be revoked by publishing a new LeaseSet with zero "
+"leases.\n"
+"Revocations must be signed by the additional signing key in the LeaseSet."
+"\n"
+"Revocations are not fully implemented, and it is unclear if they have any"
+" practical use.\n"
+"This is the only planned use for that signing key, so it is currently "
+"unused."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:195
+msgid "Encrypted LeaseSets"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:196
+msgid ""
+"In an encrypted LeaseSet, all Leases are encrypted with a separate"
+" DSA key.\n"
+"The leases may only be decoded, and thus the destination may only be "
+"contacted,\n"
+"by those with the key.\n"
+"There is no flag or other direct indication that the LeaseSet is "
+"encrypted.\n"
+"Encrypted LeaseSets are not widely used, and it is a topic for future "
+"work to\n"
+"research whether the user interface and implementation of encrypted "
+"LeaseSets could be improved."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:205
+msgid "LeaseSet Expiration"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:206
+msgid ""
+"All Leases (tunnels) are valid for 10 minutes; therefore, a LeaseSet "
+"expires\n"
+"10 minutes after the earliest creation time of all its Leases."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:211
+msgid "LeaseSet Persistent Storage"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:212
+msgid ""
+"There is no persistent storage of LeaseSet data since they expire so "
+"quickly."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:217
+msgid "Bootstrapping"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:218
+msgid ""
+"The netDb is decentralized, however you do need at\n"
+"least one reference to a peer so that the integration process\n"
+"ties you in. This is accomplished by \"reseeding\" your router with the "
+"RouterInfo\n"
+"of an active peer - specifically, by retrieving their "
+"routerInfo-$hash.dat\n"
+"file and storing it in your netDb/ directory. Anyone can "
+"provide\n"
+"you with those files - you can even provide them to others by exposing "
+"your own\n"
+"netDb directory. To simplify the process,\n"
+"volunteers publish their netDb directories (or a subset) on the regular "
+"(non-i2p) network,\n"
+"and the URLs of these directories are hardcoded in I2P.\n"
+"When the router starts up for the first time, it automatically fetches "
+"from\n"
+"one of these URLs, selected at random."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:232
+msgid "Floodfill"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:233
+msgid ""
+"The floodfill netDb is a simple distributed storage mechanism.\n"
+"The storage algorithm is simple: send the data to the closest peer that "
+"has advertised itself\n"
+"as a floodfill router. Then wait 10 seconds, pick another floodfill "
+"router and ask them \n"
+"for the entry to be sent, verifying its proper insertion / distribution. "
+"If the \n"
+"verification peer doesn't reply, or they don't have the entry, the sender"
+" \n"
+"repeats the process. When the peer in the floodfill netDb receives a "
+"netDb \n"
+"store from a peer not in the floodfill netDb, they send it to a subset of"
+" the floodfill netDb-peers.\n"
+"The peers selected are the ones closest (according to the XOR-metric) to a specific key."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:244
+msgid ""
+"Determining who is part of the floodfill netDb is trivial - it is exposed"
+" in each \n"
+"router's published routerInfo as a capability."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:249
+msgid ""
+"Floodfills have no central authority and do not form a \"consensus\" -\n"
+"they only implement a simple DHT overlay."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:256
+msgid "Floodfill Router Opt-in"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:258
+msgid ""
+"Unlike Tor, where the directory servers are hardcoded and trusted,\n"
+"and operated by known entities,\n"
+"the members of the I2P floodfill peer set need not be trusted, and\n"
+"change over time."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:265
+msgid ""
+"To increase reliability of the netDb, and minimize the impact\n"
+"of netDb traffic on a router, floodfill is automatically enabled\n"
+"only on routers that are configured with high bandwidth limits.\n"
+"Routers with high bandwidth limits (which must be manually configured,\n"
+"as the default is much lower) are presumed to be on lower-latency\n"
+"connections, and are more likely to be available 24/7.\n"
+"The current minimum share bandwidth for a floodfill router is 128 "
+"KBytes/sec."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:275
+msgid ""
+"In addition, a router must pass several additional tests for health\n"
+"(outbound message queue time, job lag, etc.) before floodfill operation "
+"is\n"
+"automatically enabled."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:281
+msgid ""
+"With the current rules for automatic opt-in, approximately 6% of\n"
+"the routers in the network are floodfill routers."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:286
+msgid ""
+"While some peers are manually configured to be floodfill,\n"
+"others are simply high-bandwidth routers who automatically volunteer\n"
+"when the number of floodfill peers drops below a threshold.\n"
+"This prevents any long-term network damage from losing most or all\n"
+"floodfills to an attack.\n"
+"In turn, these peers will un-floodfill themselves when there are\n"
+"too many floodfills outstanding."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:296
+msgid "Floodfill Router Roles"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:297
+msgid ""
+"A floodfill router's only services that are in addition to those of non-"
+"floodfill routers\n"
+"are in accepting netDb stores and responding to netDb queries.\n"
+"Since they are generally high-bandwidth, they are more likely to "
+"participate in a high number of tunnels\n"
+"(i.e. be a \"relay\" for others), but this is not directly related to "
+"their distributed database services."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:305
+msgid "Kademlia Closeness Metric"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:306
+msgid ""
+"The netDb uses a simple Kademlia-style XOR metric to determine closeness."
+"\n"
+"The SHA256 hash of the key being looked up or stored is XOR-ed with\n"
+"the hash of the router in question to determine closeness.\n"
+"A modification to this algorithm is done to increase the costs of Sybil attacks.\n"
+"Instead of the SHA256 hash of the key being looked up of stored, the "
+"SHA256 hash is taken\n"
+"of the 32-byte binary key appended with the UTC date represented as an "
+"8-byte ASCII string yyyyMMdd, i.e. SHA256(key + yyyyMMdd).\n"
+"This is called the \"routing key\", and it changes every day at midnight "
+"UTC.\n"
+"The daily transformation of the DHT is sometimes called \"keyspace "
+"rotation\",\n"
+"although it isn't strictly a rotation."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:318
+msgid ""
+"Routing keys are never sent on-the-wire in any I2NP message, they are "
+"only used locally for\n"
+"determination of distance."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:325
+msgid "Storage, Verification, and Lookup Mechanics"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:327
+msgid "RouterInfo Storage to Peers"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:328
+#, python-format
+msgid ""
+"I2NP DatabaseStoreMessages containing the local "
+"RouterInfo are exchanged with peers\n"
+"as a part of the initialization of a NTCP\n"
+"or SSU transport connection."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:335
+msgid "LeaseSet Storage to Peers"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:336
+#, python-format
+msgid ""
+"I2NP DatabaseStoreMessages containing the local "
+"LeaseSet are periodically exchanged with peers\n"
+"by bundling them in a garlic message along with normal traffic from the "
+"related Destination.\n"
+"This allows an initial response, and later responses, to be sent to an "
+"appropriate Lease,\n"
+"without requiring any LeaseSet lookups, or requiring the communicating "
+"Destinations to have published LeaseSets at all."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:344
+msgid ""
+"The DatabaseStoreMessage should be sent to the floodfill that is closest\n"
+"to the current routing key for the RouterInfo or LeaseSet being stored.\n"
+"Currently, the closest floodfill is found by a search in the local "
+"database.\n"
+"Even if that floodfill is not actually closest, it will flood it "
+"\"closer\" by\n"
+"sending it to multiple other floodfills.\n"
+"This provides a high degree of fault-tolerance."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:353
+msgid ""
+"In traditional Kademlia, a peer would do a \"find-closest\" search before"
+" inserting\n"
+"an item in the DHT to the closest target. As the verify operation will "
+"tend to\n"
+"discover closer floodfills if they are present, a router will quickly "
+"improve\n"
+"its knowledge of the DHT \"neighborhood\" for the RouterInfo and "
+"LeaseSets it regularly publishes.\n"
+"While I2NP does not define a \"find-closest\" message, if it becomes "
+"necessary,\n"
+"a router may simply do an iterative search for a key with the least "
+"significant bit flipped\n"
+"(i.e. key ^ 0x01) until no closer peers are received in the "
+"DatabaseSearchReplyMessages.\n"
+"This ensures that the true closest peer will be found even if a more-"
+"distant peer had\n"
+"the netdb item."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:366
+msgid "RouterInfo Storage to Floodfills"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:367
+#, python-format
+msgid ""
+"A router publishes its own RouterInfo by directly connecting to a "
+"floodfill router\n"
+"and sending it a I2NP DatabaseStoreMessage\n"
+"with a nonzero Reply Token. The message is not end-to-end garlic "
+"encrypted,\n"
+"as this is a direct connection, so there are no intervening routers\n"
+"(and no need to hide this data anyway).\n"
+"The floodfill router replies with a\n"
+"I2NP DeliveryStatusMessage,\n"
+"with the Message ID set to the value of the Reply Token."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:381
+msgid "LeaseSet Storage to Floodfills"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:382
+msgid ""
+"Storage of LeaseSets is much more sensitive than for RouterInfos, as a "
+"router\n"
+"must take care that the LeaseSet cannot be associated with the router."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:387
+#, python-format
+msgid ""
+"A router publishes a local LeaseSet by\n"
+"sending a I2NP DatabaseStoreMessage\n"
+"with a nonzero Reply Token over an outbound client tunnel for that "
+"Destination.\n"
+"The message is end-to-end garlic encrypted using the Destination's "
+"Session Key Manager,\n"
+"to hide the message from the tunnel's outbound endpoint.\n"
+"The floodfill router replies with a\n"
+"I2NP DeliveryStatusMessage,\n"
+"with the Message ID set to the value of the Reply Token.\n"
+"This message is sent back to one of the client's inbound tunnels."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:400
+msgid "Flooding"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:401
+#, python-format
+msgid ""
+"After a floodfill router receives a DatabaseStoreMessage containing a\n"
+"valid RouterInfo or LeaseSet which is newer than that previously stored "
+"in its\n"
+"local NetDb, it \"floods\" it.\n"
+"To flood a NetDb entry, it looks up several (currently %(floodsize)s) "
+"floodfill routers closest to the routing key\n"
+"of the NetDb entry. (The routing key is the SHA256 Hash of the "
+"RouterIdentity or Destination with the date (yyyyMMdd) appended.)\n"
+"By flooding to those closest to the key, not closest to itself, the "
+"floodfill ensures that the storage\n"
+"gets to the right place, even if the storing router did not have good "
+"knowledge of the\n"
+"DHT \"neighborhood\" for the routing key."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:412
+#, python-format
+msgid ""
+"The floodfill then directly connects to each of those peers\n"
+"and sends it a I2NP DatabaseStoreMessage\n"
+"with a zero Reply Token. The message is not end-to-end garlic encrypted,\n"
+"as this is a direct connection, so there are no intervening routers\n"
+"(and no need to hide this data anyway).\n"
+"The other routers do not reply or re-flood, as the Reply Token is zero."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:422
+msgid "RouterInfo and LeaseSet Lookup"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:423
+#, python-format
+msgid ""
+"The I2NP DatabaseLookupMessage is used to "
+"request a netdb entry from a floodfill router.\n"
+"Lookups are sent out one of the router's outbound exploratory tunnels.\n"
+"The replies are specified to return via one of the router's inbound "
+"exploratory tunnels."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:429
+msgid ""
+"Lookups are generally sent to the two \"good\" (the connection doesn't "
+"fail) floodfill routers closest to the requested key, in parallel."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:433
+#, python-format
+msgid ""
+"If the key is found locally by the floodfill router, it responds with a\n"
+"I2NP DatabaseStoreMessage.\n"
+"If the key is not found locally by the floodfill router, it responds with"
+" a\n"
+"I2NP DatabaseSearchReplyMessage\n"
+"containing a list of other floodfill routers close to the key."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:441
+msgid ""
+"LeaseSet lookups are garlic encrypted end-to-end as of release 0.9.5.\n"
+"RouterInfo lookups are not encrypted and thus are vulnerable to snooping "
+"by the outbound endpoint\n"
+"(OBEP) of the client tunnel. This is due to the expense of the ElGamal "
+"encryption.\n"
+"RouterInfo lookup encryption may be enabled in a future release."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:448
+msgid ""
+"As of release 0.9.7, replies to a LeaseSet lookup (a DatabaseStoreMessage"
+" or a DatabaseSearchReplyMessage)\n"
+"will be encrypted by including the session key and tag in the lookup.\n"
+"This hides the reply from the inbound gateway (IBGW) of the reply tunnel."
+"\n"
+"Responses to RouterInfo lookups will be encrypted if we enable the lookup"
+" encryption."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:455
+#, python-format
+msgid ""
+"(Reference: Hashing it out in Public Sections "
+"2.2-2.3 for terms below in italics)"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:459
+msgid ""
+"Due to the relatively small size of the network and the flooding "
+"redundancy of 8x,\n"
+"lookups are usually O(1) rather than O(log n) --\n"
+"a router is highly likely to know a floodfill router close enough to the "
+"key to get the answer on the first try.\n"
+"In releases prior to 0.8.9, routers used a lookup redundancy of two\n"
+"(that is, two lookups were performed in parallel to different peers), and"
+"\n"
+"neither recursive nor iterative routing for lookups was "
+"implemented.\n"
+"Queries were sent through multiple routes simultaneously\n"
+"to reduce the chance of query failure."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:470
+msgid ""
+"As of release 0.8.9, iterative lookups are implemented with no "
+"lookup redundancy.\n"
+"This is a more efficient and reliable lookup that will work much better\n"
+"when not all floodfill peers are known, and it removes a serious\n"
+"limitation to network growth. As the network grows and each router knows "
+"only a small\n"
+"subset of the floodfill peers, lookups will become O(log n).\n"
+"Even if the peer does not return references closer to the key, the lookup"
+" continues with\n"
+"the next-closest peer, for added robustness, and to prevent a malicious "
+"floodfill from\n"
+"black-holing a part of the key space. Lookups continue until a total "
+"lookup timeout is reached,\n"
+"or the maximum number of peers is queried."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:482
+msgid ""
+"Node IDs are verifiable in that we use the router hash "
+"directly as both the node ID and the Kademlia key.\n"
+"Incorrect responses that are not closer to the search key are generally "
+"ignored.\n"
+"Given the current size of the network, a router has\n"
+"detailed knowledge of the neighborhood of the destination ID space."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:491
+msgid "RouterInfo Storage Verification"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:492
+#, python-format
+msgid ""
+"Note: RouterInfo verification is disabled as of release 0.9.7.1 to "
+"prevent\n"
+"the attack described in the paper\n"
+"Practical Attacks Against the I2P Network.\n"
+"It is not clear if verification can be redesigned to be done safely."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:499
+msgid ""
+"To verify a storage was successful, a router simply waits about 10 "
+"seconds,\n"
+"then sends a lookup to another floodfill router close to the key\n"
+"(but not the one the store was sent to).\n"
+"Lookups sent out one of the router's outbound exploratory tunnels.\n"
+"Lookups are end-to-end garlic encrypted to prevent snooping by the "
+"outbound endpoint(OBEP)."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:507
+msgid "LeaseSet Storage Verification"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:508
+msgid ""
+"To verify a storage was successful, a router simply waits about 10 "
+"seconds,\n"
+"then sends a lookup to another floodfill router close to the key\n"
+"(but not the one the store was sent to).\n"
+"Lookups sent out one of the outbound client tunnels for the destination "
+"of the LeaseSet being verified.\n"
+"To prevent snooping by the OBEP of the outbound tunnel,\n"
+"lookups are end-to-end garlic encrypted.\n"
+"The replies are specified to return via one of the client's inbound "
+"tunnels."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:518
+msgid ""
+"As of release 0.9.7, replies for both RouterInfo and LeaseSet lookups (a "
+"DatabaseStoreMessage or a DatabaseSearchReplyMessage)\n"
+"will be encrypted,\n"
+"to hide the reply from the inbound gateway (IBGW) of the reply tunnel."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:526
+msgid "Exploration"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:527
+#, python-format
+msgid ""
+"Exploration is a special form of netdb lookup, where a router "
+"attempts to learn about\n"
+"new routers.\n"
+"It does this by sending a floodfill router a I2NP DatabaseLookupMessage, looking for a random "
+"key.\n"
+"As this lookup will fail, the floodfill would normally respond with a\n"
+"I2NP DatabaseSearchReplyMessage containing "
+"hashes of floodfill routers close to the key.\n"
+"This would not be helpful, as the requesting router probably already "
+"knows those floodfills,\n"
+"and it would be impractical to add ALL floodfill routers to the \"don't "
+"include\" field of the lookup.\n"
+"For an exploration query, the requesting router adds a router hash of all"
+" zeros to the\n"
+"\"don't include\" field of the DatabaseLookupMessage.\n"
+"The floodfill will then respond only with non-floodfill routers close to "
+"the requested key."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:541
+msgid "Notes on Lookup Responses"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:542
+msgid ""
+"The response to a lookup request is either a Database Store Message (on "
+"success) or a\n"
+"Database Search Reply Message (on failure). The DSRM contains a 'from' "
+"router hash field\n"
+"to indicate the source of the reply; the DSM does not.\n"
+"The DSRM 'from' field is unauthenticated and may be spoofed or invalid.\n"
+"There are no other response tags. Therefore, when making multiple "
+"requests in parallel, it is\n"
+"difficult to monitor the performance of the various floodfill routers."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:552
+msgid "MultiHoming"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:554
+msgid ""
+"Destinations may be hosted on multiple routers simultaneously, by using "
+"the same\n"
+"private and public keys (traditionally stored in eepPriv.dat files).\n"
+"As both instances will periodically publish their signed LeaseSets to the"
+" floodfill peers,\n"
+"the most recently published LeaseSet will be returned to a peer "
+"requesting a database lookup.\n"
+"As LeaseSets have (at most) a 10 minute lifetime, should a particular "
+"instance go down,\n"
+"the outage will be 10 minutes at most, and generally much less than that."
+"\n"
+"The multihoming function has been verified and is in use by several "
+"services on the network."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:564
+msgid "Threat Analysis"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:565
+#, python-format
+msgid ""
+"Also discussed on the threat model "
+"page."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:569
+msgid ""
+"A hostile user may attempt to harm the network by\n"
+"creating one or more floodfill routers and crafting them to offer\n"
+"bad, slow, or no responses.\n"
+"Some scenarios are discussed below."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:576
+msgid "General Mitigation Through Growth"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:577
+#, python-format
+msgid ""
+"There are currently around %(ffcount)s floodfill routers in the network.\n"
+"Most of the following attacks will become more difficult, or have less "
+"impact,\n"
+"as the network size and number of floodfill routers increase."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:584
+msgid "General Mitigation Through Redundancy"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:585
+#, python-format
+msgid ""
+"Via flooding, all netdb entries are stored on the %(floodsize)s floodfill"
+" routers closest to the key."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:590
+msgid "Forgeries"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:591
+msgid ""
+"All netdb entries are signed by their creators, so no router may forge a\n"
+"RouterInfo or LeaseSet."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:596
+msgid "Slow or Unresponsive"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:597
+#, python-format
+msgid ""
+"Each router maintains an expanded set of statistics in the\n"
+"peer profile for each floodfill router,"
+"\n"
+"covering various quality metrics for that peer.\n"
+"The set includes:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:604
+msgid "Average response time"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:605
+msgid "Percentage of queries answered with the data requested"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:606
+msgid "Percentage of stores that were successfully verified"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:607
+msgid "Last successful store"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:608
+msgid "Last successful lookup"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:609
+msgid "Last response"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:612
+msgid ""
+"Each time a router needs to make a determination on which floodfill "
+"router is closest to a key,\n"
+"it uses these metrics to determine which floodfill routers are \"good\".\n"
+"The methods, and thresholds, used to determine \"goodness\" are "
+"relatively new, and\n"
+"are subject to further analysis and improvement.\n"
+"While a completely unresponsive router will quickly be identified and "
+"avoided,\n"
+"routers that are only sometimes malicious may be much harder to deal with."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:622
+msgid "Sybil Attack (Full Keyspace)"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:623
+#, python-format
+msgid ""
+"An attacker may mount a Sybil attack\n"
+"by creating a large number of floodfill routers spread throughout the "
+"keyspace."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:628
+#, python-format
+msgid ""
+"(In a related example, a researcher recently created a\n"
+"large number of Tor relays.)\n"
+"If successful, this could be an effective DOS attack on the entire "
+"network."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:634
+msgid ""
+"If the floodfills are not sufficiently misbehaving to be marked as "
+"\"bad\" using the peer profile\n"
+"metrics described above, this is a difficult scenario to handle.\n"
+"Tor's response can be much more nimble in the relay case, as the "
+"suspicious relays\n"
+"can be manually removed from the consensus.\n"
+"Some possible responses for the I2P network are listed below, however "
+"none of them is completely satisfactory:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:642
+msgid ""
+"Compile a list of bad router hashes or IPs, and announce the list through"
+" various means\n"
+"(console news, website, forum, etc.); users would have to manually "
+"download the list and\n"
+"add it to their local \"blacklist\"."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:647
+msgid ""
+"Ask everyone in the network to enable floodfill manually (fight Sybil "
+"with more Sybil)"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:648
+msgid "Release a new software version that includes the hardcoded \"bad\" list"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:649
+msgid ""
+"Release a new software version that improves the peer profile metrics and"
+" thresholds,\n"
+"in an attempt to automatically identify the \"bad\" peers."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:653
+msgid ""
+"Add software that disqualifies floodfills if too many of them are in a "
+"single IP block"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:654
+msgid ""
+"Implement an automatic subscription-based blacklist controlled by a "
+"single individual or group.\n"
+"This would essentially implement a portion of the Tor \"consensus\" "
+"model.\n"
+"Unfortunately it would also give a single individual or group the power "
+"to\n"
+"block participation of any particular router or IP in the network,\n"
+"or even to completely shutdown or destroy the entire network."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:663
+msgid "This attack becomes more difficult as the network size grows."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:669
+msgid "Sybil Attack (Partial Keyspace)"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:670
+#, python-format
+msgid ""
+"An attacker may mount a Sybil attack\n"
+"by creating a small number (8-15) of floodfill routers clustered closely "
+"in the keyspace,\n"
+"and distribute the RouterInfos for these routers widely.\n"
+"Then, all lookups and stores for a key in that keyspace would be directed"
+"\n"
+"to one of the attacker's routers.\n"
+"If successful, this could be an effective DOS attack on a particular "
+"eepsite, for example."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:679
+msgid ""
+"As the keyspace is indexed by the cryptographic (SHA256) Hash of the key,"
+"\n"
+"an attacker must use a brute-force method to repeatedly generate router "
+"hashes\n"
+"until he has enough that are sufficiently close to the key.\n"
+"The amount of computational power required for this, which is dependent "
+"on network\n"
+"size, is unknown."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:687
+msgid ""
+"As a partial defense against this attack,\n"
+"the algorithm used to determine Kademlia \"closeness\" varies over time.\n"
+"Rather than using the Hash of the key (i.e. H(k)) to determine closeness,"
+"\n"
+"we use the Hash of the key appended with the current date string, i.e. "
+"H(k + YYYYMMDD).\n"
+"A function called the \"routing key generator\" does this, which "
+"transforms the original key into a \"routing key\".\n"
+"In other words, the entire netdb keyspace \"rotates\" every day at UTC "
+"midnight.\n"
+"Any partial-keyspace attack would have to be regenerated every day, for\n"
+"after the rotation, the attacking routers would no longer be close\n"
+"to the target key, or to each other."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:699
+msgid ""
+"This attack becomes more difficult as the network size grows.\n"
+"However, recent research demonstrates that the keyspace rotation is not "
+"particularly effective.\n"
+"An attacker can precompute numerous router hashes in advance,\n"
+"and only a few routers are sufficient to \"eclipse\" a portion\n"
+"of the keyspace within a half hour after rotation."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:707
+msgid ""
+"One consequence of daily keyspace rotation is that the distributed "
+"network database\n"
+"may become unreliable for a few minutes after the rotation --\n"
+"lookups will fail because the new \"closest\" router has not received a "
+"store yet.\n"
+"The extent of the issue, and methods for mitigation\n"
+"(for example netdb \"handoffs\" at midnight)\n"
+"are a topic for further study."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:717
+msgid "Bootstrap Attacks"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:718
+msgid ""
+"An attacker could attempt to boot new routers into an isolated\n"
+"or majority-controlled network by taking over a reseed website,\n"
+"or tricking the developers into adding his reseed website\n"
+"to the hardcoded list in the router."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:725
+msgid "Several defenses are possible, and most of these are planned:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:729
+msgid ""
+"Disallow fallback from HTTPS to HTTP for reseeding.\n"
+"A MITM attacker could simply block HTTPS, then respond to the HTTP."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:733
+msgid ""
+"Changing the reseed task to fetch a subset of RouterInfos from\n"
+"each of several reseed sites rather than using only a single site"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:737
+msgid ""
+"Creating an out-of-network reseed monitoring service that\n"
+"periodically polls reseed websites and verifies that the\n"
+"data are not stale or inconsistent with other views of the network"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:742
+msgid "Bundling reseed data in the installer"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:745
+msgid "Query Capture"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:746
+#, python-format
+msgid ""
+"See also lookup\n"
+"(Reference: Hashing it out in Public Sections "
+"2.2-2.3 for terms below in italics)"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:751
+msgid ""
+"Similar to a bootstrap attack, an attacker using a floodfill router could"
+" attempt to \"steer\"\n"
+"peers to a subset of routers controlled by him by returning their "
+"references."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:756
+msgid ""
+"This is unlikely to work via exploration, because exploration is a low-"
+"frequency task.\n"
+"Routers acquire a majority of their peer references through normal tunnel"
+" building activity.\n"
+"Exploration results are generally limited to a few router hashes,\n"
+"and each exploration query is directed to a random floodfill router."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:763
+#, python-format
+msgid ""
+"As of release 0.8.9, iterative lookups are implemented.\n"
+"For floodfill router references returned in a\n"
+"I2NP DatabaseSearchReplyMessage\n"
+"response to a lookup,\n"
+"these references are followed if they are closer (or the next closest) to"
+" the lookup key.\n"
+"The requesting router does not trust that the references are\n"
+"closer to the key (i.e. they are verifiably correct.\n"
+"The lookup also does not stop when no closer key is found, but continues "
+"by querying the\n"
+"next-closet node, until the timeout or maximum number of queries is "
+"reached.\n"
+"This prevents a malicious floodfill from black-holing a part of the key "
+"space.\n"
+"Also, the daily keyspace rotation requires an attacker to regenerate a "
+"router info\n"
+"within the desired key space region.\n"
+"This design ensures that the query capture attack described in\n"
+"Hashing it out in Public\n"
+"is much more difficult."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:782
+msgid "DHT-Based Relay Selection"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:783
+#, python-format
+msgid "(Reference: Hashing it out in Public Section 3)"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:787
+#, python-format
+msgid ""
+"This doesn't have much to do with floodfill, but see\n"
+"the peer selection page\n"
+"for a discussion of the vulnerabilities of peer selection for tunnels."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:793
+msgid "Information Leaks"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:794
+#, python-format
+msgid ""
+"(Reference: In Search of an Anonymous and Secure "
+"Lookup Section 3)"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:798
+#, python-format
+msgid ""
+"This paper addresses weaknesses in the \"Finger Table\" DHT lookups used "
+"by Torsk and NISAN.\n"
+"At first glance, these do not appear to apply to I2P. First, the use of "
+"DHT by Torsk and NISAN\n"
+"is significantly different from that in I2P. Second, I2P's network "
+"database lookups are only\n"
+"loosely correlated to the peer "
+"selection and\n"
+"tunnel building processes; only "
+"previously-known peers\n"
+"are used for tunnels.\n"
+"Also, peer selection is unrelated to any notion of DHT key-closeness."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:809
+msgid ""
+"Some of this may actually be more interesting when the I2P network gets "
+"much larger.\n"
+"Right now, each router knows a large proportion of the network, so "
+"looking up a particular\n"
+"Router Info in the network database is not strongly indicative of a "
+"future intent to use\n"
+"that router in a tunnel. Perhaps when the network is 100 times larger, "
+"the lookup may be\n"
+"more correlative. Of course, a larger network makes a Sybil attack that "
+"much harder."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:817
+#, python-format
+msgid ""
+"However, the general issue of DHT information leakage in I2P needs "
+"further investigation.\n"
+"The floodfill routers are in a position to observe queries and gather "
+"information.\n"
+"Certainly, at a level of f = 0.2 (20% malicious nodes, as "
+"specifed in the paper)\n"
+"we expect that many of the Sybil threats we describe\n"
+"(here,\n"
+"here and\n"
+"here)\n"
+"become problematic for several reasons."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:831
+msgid "Moved to the netdb discussion page"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:835
+msgid "End-to-end encryption of additional netDb lookups and responses."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:839
+msgid "Better methods for tracking lookup responses."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/peer-selection.html:2
+msgid "Peer Profiling and Selection"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/peer-selection.html:3
+msgid "July 2010"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/peer-selection.html:8
+msgid "Peer Profiling"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/peer-selection.html:10
+#, python-format
+msgid ""
+"Peer profiling is the process of collecting data based on the "
+"observed performance\n"
+"of other routers or peers, and classifying those peers into groups.\n"
+"Profiling does not use any claimed performance data published by "
+"the peer itself\n"
+"in the network database."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/peer-selection.html:17
+msgid "Profiles are used for two purposes:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/peer-selection.html:19
+msgid "Selecting peers to relay our traffic through, which is discussed below"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/peer-selection.html:20
+#, python-format
+msgid ""
+"Choosing peers from the set of floodfill routers to use for network "
+"database storage and queries,\n"
+"which is discussed on the network database page"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/peer-selection.html:27
+#: i2p2www/pages/site/docs/how/peer-selection.html:187
+#: i2p2www/pages/site/docs/tunnels/implementation.html:286
+msgid "Peer Selection"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/peer-selection.html:28
+msgid ""
+"Peer selection is the process of choosing which routers\n"
+"on the network we want to relay our messages to go through (which peers "
+"will we \n"
+"ask to join our tunnels). To accomplish this, we keep track of how each\n"
+"peer performs (the peer's \"profile\") and use that data to estimate how"
+" \n"
+"fast they are, how often they will be able to accept our requests, and \n"
+"whether they seem to be overloaded or otherwise unable to perform what\n"
+"they agree to reliably."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/peer-selection.html:38
+#, python-format
+msgid ""
+"Unlike some other anonymous networks, in I2P,\n"
+"claimed bandwidth is untrusted and is only used to avoid those "
+"peers\n"
+"advertising very low bandwidth insufficient for routing tunnels.\n"
+"All peer selection is done through profiling.\n"
+"This prevents simple attacks based on peers claiming high bandwidth\n"
+"in order to capture large numbers of tunnels.\n"
+"It also makes\n"
+"timing attacks\n"
+"more difficult."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/peer-selection.html:50
+msgid ""
+"Peer selection is done quite frequently, as a router may maintain a large"
+" number\n"
+"of client and exploratory tunnels, and a tunnel lifetime is only 10 "
+"minutes."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/peer-selection.html:56
+msgid "Further Information"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/peer-selection.html:57
+#, python-format
+msgid ""
+"For more information see the paper\n"
+"Peer Profiling and Selection in the I2P Anonymous "
+"Network\n"
+"presented at PET-CON 2009.1.\n"
+"See below for notes on minor changes since the "
+"paper was published."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/peer-selection.html:65
+msgid "Profiles"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/peer-selection.html:66
+#, python-format
+msgid ""
+"Each peer has a set of data points collected about them, including "
+"statistics \n"
+"about how long it takes for them to reply to a network database query, "
+"how \n"
+"often their tunnels fail, and how many new peers they are able to "
+"introduce \n"
+"us to, as well as simple data points such as when we last heard from them"
+" or\n"
+"when the last communication error occurred. The specific data points "
+"gathered\n"
+"can be found in the code."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/peer-selection.html:75
+msgid ""
+"Profiles are fairly small, a few KB. To control memory usage, the profile"
+" expiration time\n"
+"lessens as the number of profiles grows.\n"
+"Profiles are kept in memory until router shutdown, when they are written "
+"to disk.\n"
+"At startup, the profiles are read so the router need not reinitialize all"
+" profiles,\n"
+"thus allowing a router to quickly re-integrate into the network after "
+"startup."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/peer-selection.html:85
+msgid "Peer Summaries"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/peer-selection.html:86
+msgid ""
+"While the profiles themselves can be considered a summary of a peer's \n"
+"performance, to allow for effective peer selection we break each summary "
+"down \n"
+"into four simple values, representing the peer's speed, its capacity, how"
+" well \n"
+"integrated into the network it is, and whether it is failing."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/peer-selection.html:93
+msgid "Speed"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/peer-selection.html:94
+msgid ""
+"The speed calculation\n"
+"simply goes through the profile and estimates how much data we can\n"
+"send or receive on a single tunnel through the peer in a minute. For "
+"this estimate it just looks at\n"
+"performance in the previous minute."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/peer-selection.html:101
+msgid "Capacity"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/peer-selection.html:102
+msgid ""
+"The capacity calculation\n"
+"simply goes through the profile and estimates how many tunnels the peer\n"
+"would agree to participate in over a given time period. For this "
+"estimate it looks at \n"
+"how many tunnel build requests\n"
+"the peer has accepted, rejected, and dropped, and how many\n"
+"of the agreed-to tunnels later failed.\n"
+"While the calculation is time-weighted so that recent activity counts "
+"more than later activity,\n"
+"statistics up to 48 hours old may be included."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/peer-selection.html:113
+msgid ""
+"Recognizing and avoiding unreliable and unreachable\n"
+"peers is critically important.\n"
+"Unfortunately, as the tunnel building and testing require the "
+"participation of several peers,\n"
+"it is difficult to positively identify the cause of a dropped build "
+"request or test failure.\n"
+"The router assigns a probability of failure to each of the\n"
+"peers, and uses that probability in the capacity calculation.\n"
+"Drops and test failures are weighted much higher than rejections."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/peer-selection.html:123
+msgid "Peer organization"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/peer-selection.html:124
+msgid ""
+"As mentioned above, we drill through each peer's profile to come up with "
+"a \n"
+"few key calculations, and based upon those, we organize each peer into "
+"three\n"
+"groups - fast, high capacity, and standard."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/peer-selection.html:130
+msgid "The groupings are not mutually exclusive, nor are they unrelated:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/peer-selection.html:134
+msgid ""
+"A peer is considered \"high capacity\" if its capacity calculation meets "
+"or \n"
+"exceeds the median of all peers."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/peer-selection.html:138
+msgid ""
+"A peer is considered \"fast\" if they are already \"high capacity\" and "
+"their \n"
+"speed calculation meets or exceeds the median of all peers."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/peer-selection.html:142
+msgid "A peer is considered \"standard\" if it is not \"high capacity\""
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/peer-selection.html:145
+#, python-format
+msgid ""
+"These groupings are implemented in the router's\n"
+"ProfileOrganizer."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/peer-selection.html:150
+msgid "Group size limits"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/peer-selection.html:151
+msgid "The size of the groups may be limited."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/peer-selection.html:156
+msgid ""
+"The fast group is limited to 30 peers.\n"
+"If there would be more, only the ones with the highest speed rating are "
+"placed in the group."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/peer-selection.html:160
+msgid ""
+"The high capacity group is limited to 75 peers (including the fast group)"
+"\n"
+"If there would be more, only the ones with the highest capacity rating "
+"are placed in the group."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/peer-selection.html:164
+msgid ""
+"The standard group has no fixed limit, but is somewhat smaller than the "
+"number of RouterInfos\n"
+"stored in the local network database.\n"
+"On an active router in today's network, there may be about 1000 "
+"RouterInfos and 500 peer profiles\n"
+"(including those in the fast and high capacity groups)"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/peer-selection.html:172
+msgid "Recalculation and Stability"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/peer-selection.html:173
+msgid ""
+"Summaries are recalculated, and peers are resorted into groups, every 45 "
+"seconds."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/peer-selection.html:177
+msgid ""
+"The groups tend to be fairly stable, that is, there is not much \"churn\""
+" in the rankings\n"
+"at each recalculation.\n"
+"Peers in the fast and high capacity groups get more tunnels build through"
+" them, which increases their speed and capacity ratings,\n"
+"which reinforces their presence in the group."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/peer-selection.html:188
+msgid "The router selects peers from the above groups to build tunnels through."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/peer-selection.html:193
+msgid "Peer Selection for Client Tunnels"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/peer-selection.html:194
+msgid ""
+"Client tunnels are used for application traffic, such as for HTTP proxies"
+" and web servers."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/peer-selection.html:198
+msgid ""
+"To reduce the susceptibility to some attacks,\n"
+"and increase performance,\n"
+"peers for building client tunnels are chosen randomly from the smallest "
+"group, which is the \"fast\" group.\n"
+"There is no bias toward selecting peers that were previously participants"
+" in a tunnel for the same client."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/peer-selection.html:206
+msgid "Peer Selection for Exploratory Tunnels"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/peer-selection.html:207
+msgid ""
+"Exploratory tunnels are used for router administrative purposes, such as "
+"network database traffic\n"
+"and testing client tunnels.\n"
+"Exploratory tunnels are also used to contact previously unconnected "
+"routers, which is why\n"
+"they are called \"exploratory\".\n"
+"These tunnels are usually low-bandwidth."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/peer-selection.html:215
+msgid ""
+"Peers for building exploratory tunnels are generally chosen randomly from"
+" the standard group.\n"
+"If the success rate of these build attempts is low compared to the client"
+" tunnel build success rate,\n"
+"the router will select a weighted average of peers randomly from the high"
+" capacity group instead.\n"
+"This helps maintain a satisfactory build success rate even when network "
+"performance is poor.\n"
+"There is no bias toward selecting peers that were previously participants"
+" in an exploratory tunnel."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/peer-selection.html:223
+msgid ""
+"As the standard group includes a very large subset of all peers the "
+"router knows about,\n"
+"exploratory tunnels are essentially built through a random selection of "
+"all peers,\n"
+"until the build success rate becomes too low."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/peer-selection.html:231
+msgid "Restrictions"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/peer-selection.html:232
+msgid ""
+"To prevent some simple attacks, and for performance, there are the "
+"following restrictions:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/peer-selection.html:236
+msgid "Two peers from the same /16 IP space may not be in the same tunnel."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/peer-selection.html:239
+msgid ""
+"A peer may participate in a maximum of 33% of all tunnels created by "
+"the router."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/peer-selection.html:242
+msgid "Peers with extremely low bandwidth are not used."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/peer-selection.html:245
+msgid "Peers for which a recent connection attempt failed are not used."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/peer-selection.html:252
+msgid "Peer Ordering in Tunnels"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/peer-selection.html:253
+#, python-format
+msgid ""
+"Peers are ordered within tunnels to\n"
+"to deal with the predecessor attack\n"
+"(2008 update).\n"
+"More information is on the tunnel "
+"page."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/peer-selection.html:268
+msgid "Continue to analyze an tune speed and capacity calculations as necessary"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/peer-selection.html:271
+msgid ""
+"Implement a more aggressive ejection strategy if necessary to control "
+"memory usage as the network grows"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/peer-selection.html:274
+msgid "Evaluate group size limits"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/peer-selection.html:277
+msgid "Use GeoIP data to include or exclude certain peers, if configured"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/peer-selection.html:283
+#, python-format
+msgid ""
+"For those reading the paper\n"
+"Peer Profiling and Selection in the I2P Anonymous "
+"Network,\n"
+"please keep in mind the following minor changes in I2P since the paper's "
+"publication:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/peer-selection.html:289
+msgid "The Integration calculation is still not used"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/peer-selection.html:290
+msgid "In the paper, \"groups\" are called \"tiers\""
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/peer-selection.html:291
+msgid "The \"Failing\" tier is no longer used"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/peer-selection.html:292
+msgid "The \"Not Failing\" tier is now named \"Standard\""
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/peer-selection.html:301
+msgid "One Cell Enough"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/peer-selection.html:303
+msgid "Tor Entry Guards"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/peer-selection.html:305
+msgid "Murdoch 2007 Paper"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/peer-selection.html:307
+msgid "Tune-up for Tor"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/peer-selection.html:309
+msgid "Low-resource Routing Attacks Against Tor"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:2
+msgid "Introducing I2P"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:5
+msgid "I2P: A scalable framework for anonymous communication"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:7
+msgid "Table of Contents"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:9
+#: i2p2www/pages/site/docs/how/tech-intro.html:24
+#: i2p2www/pages/site/docs/transport/ssu.html:278
+msgid "Introduction"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:11
+msgid "I2P Operation"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:16
+#: i2p2www/pages/site/docs/how/tech-intro.html:401
+msgid "Transport protocols"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:17
+#: i2p2www/pages/site/docs/how/tech-intro.html:458
+msgid "Cryptography"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:25
+msgid ""
+"I2P is a scalable, self organizing, resilient packet switched anonymous \n"
+"network layer, upon which any number of different anonymity or security "
+"conscious \n"
+"applications can operate. Each of these applications may make their own "
+"anonymity, \n"
+"latency, and throughput tradeoffs without worrying about the proper "
+"implementation \n"
+"of a free route mixnet, allowing them to blend their activity with the "
+"larger \n"
+"anonymity set of users already running on top of I2P."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:34
+msgid ""
+"Applications available already provide the full range of typical Internet"
+" activities -\n"
+"anonymous web browsing, web hosting, chat, file sharing, e-mail,\n"
+"blogging and content syndication, newsgroups, as well as several other "
+"applications under development."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:40
+msgid "Web browsing: using any existing browser that supports using a proxy."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:41
+msgid "Chat: IRC, Jabber, I2P-Messenger."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:42
+msgid ""
+"File sharing: I2PSnark, Robert, iMule, \n"
+"I2Phex, PyBit, I2P-bt\n"
+"and others."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:47
+msgid ""
+"E-mail: susimail and I2P-Bote."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:48
+msgid ""
+"Blog: using e.g. the pebble plugin or the distributed blogging software "
+"Syndie."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:49
+msgid ""
+"Distributed Data Store: Save your data redundantly in the Tahoe-LAFS "
+"cloud over I2P."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:50
+msgid "Newsgroups: using any newsgroup reader that supports using a proxy."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:53
+msgid ""
+"Unlike web sites hosted within content distribution networks like Freenet \n"
+"or GNUnet, the services "
+"hosted on \n"
+"I2P are fully interactive - there are traditional web-style search "
+"engines, \n"
+"bulletin boards, blogs you can comment on, database driven sites, and "
+"bridges \n"
+"to query static systems like Freenet without needing to install it "
+"locally."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:61
+msgid ""
+"With all of these anonymity enabled applications, I2P takes on the role \n"
+"of the message oriented middleware - applications say that they want to "
+"send \n"
+"some data to a cryptographic identifier (a \"destination\") and I2P takes"
+" care \n"
+"of making sure it gets there securely and anonymously. I2P also bundles a"
+" \n"
+"simple streaming library to allow I2P's "
+"anonymous \n"
+"best-effort messages to transfer as reliable, in-order streams, "
+"transparently \n"
+"offering a TCP based congestion control algorithm tuned for the high "
+"bandwidth \n"
+"delay product of the network. While there have been several simple SOCKS "
+"proxies \n"
+"available to tie existing applications into the network, their value has "
+"been \n"
+"limited as nearly every application routinely exposes what, in an "
+"anonymous \n"
+"context, is sensitive information. The only safe way to go is to fully "
+"audit \n"
+"an application to ensure proper operation and to assist in that we "
+"provide \n"
+"a series of APIs in various languages which can be used to make the most "
+"out \n"
+"of the network."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:78
+#, python-format
+msgid ""
+"I2P is not a research project - academic, commercial, or governmental, "
+"but \n"
+"is instead an engineering effort aimed at doing whatever is necessary to "
+"provide \n"
+"a sufficient level of anonymity to those who need it. It has been in "
+"active \n"
+"development since early 2003 with one full time developer and a dedicated"
+" \n"
+"group of part time contributors from all over the world. All of the work "
+"done \n"
+"on I2P is open source and freely available on the website, \n"
+"with the majority of the code released outright into the public domain, "
+"though \n"
+"making use of a few cryptographic routines under BSD-style licenses. The "
+"people \n"
+"working on I2P do not control what people release client applications "
+"under, \n"
+"and there are several GPL'ed applications available (I2PTunnel, \n"
+"susimail, I2PSnark, I2P-"
+"Bote, \n"
+"I2Phex and others.).\n"
+"Funding for I2P comes entirely from "
+"donations,\n"
+"and does not receive any tax breaks in any jurisdiction at this time,\n"
+"as many of the developers are themselves anonymous."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:96
+msgid "Operation"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:98
+msgid ""
+"To understand I2P's operation, it is essential to understand a few key "
+"concepts. \n"
+"First, I2P makes a strict separation between the software participating "
+"in \n"
+"the network (a \"router\") and the anonymous endpoints (\"destinations\")"
+" associated \n"
+"with individual applications. The fact that someone is running I2P is not"
+" \n"
+"usually a secret. What is hidden is information on what the user is "
+"doing, \n"
+"if anything at all, as well as what router a particular destination is "
+"connected \n"
+"to. End users will typically have several local destinations on their "
+"router \n"
+"- for instance, one proxying in to IRC servers, another supporting the "
+"user's \n"
+"anonymous webserver (\"eepsite\"), another for an I2Phex instance, "
+"another for \n"
+"torrents, etc."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:111
+msgid ""
+"Another critical concept to understand is the \"tunnel\".\n"
+"A tunnel is a directed path through an explicitly selected list of "
+"routers.\n"
+"Layered encryption is used, so each of the routers can only decrypt a "
+"single layer.\n"
+"The decrypted information contains the IP of the next router, along with\n"
+"the encrypted information to be forwarded.\n"
+"Each tunnel has a starting point (the first router, also known as "
+"\"gateway\")\n"
+"and an end point. Messages can be sent only in one way. To send messages "
+"back,\n"
+"another tunnel is required."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:122
+#: i2p2www/pages/site/docs/tunnels/implementation.html:105
+msgid "Inbound and outbound tunnel schematic"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:124
+msgid "Figure 1: Two types of tunnels exist: inbound and outbound."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:127
+msgid ""
+"Two types of tunnels exist:\n"
+"\"outbound\" tunnels send messages away from the tunnel creator,\n"
+"while \"inbound\" tunnels bring messages to the tunnel creator.\n"
+"Combining these two tunnels allows users to send messages to each other.\n"
+"The sender (\"Alice\" in the above image) sets up an outbound tunnel,\n"
+"while the receiver (\"Bob\" in the above image) creates an inbound "
+"tunnel.\n"
+"The gateway of an inbound tunnel can receive messages from any other user"
+"\n"
+"and will send them on until the endpoint (\"Bob\").\n"
+"The endpoint of the outbound tunnel will need to send the message\n"
+"on to the gateway of the inbound tunnel.\n"
+"To do this, the sender (\"Alice\") adds instructions to her encrypted "
+"message.\n"
+"Once the endpoint of the outbound tunnel decrypts the message,\n"
+"it will have instructions to forward the message to the correct\n"
+"inbound gateway (the gateway to \"Bob\")."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:144
+msgid ""
+"A third critical concept to understand is I2P's \"network "
+"database\" (or \"netDb\") \n"
+"- a pair of algorithms used to share network metadata. The two types of "
+"metadata \n"
+"carried are \"routerInfo\" and \"leaseSets\" - the "
+"routerInfo gives routers the \n"
+"data necessary for contacting a particular router (their public keys, "
+"transport \n"
+"addresses, etc), while the leaseSet gives routers the information "
+"necessary \n"
+"for contacting a particular destination. A leaseSet contains a number of "
+"\"leases\".\n"
+"Each of this leases specifies a tunnel gateway, which allows reaching a "
+"specific destination.\n"
+"The full information contained in a lease:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:155
+msgid "Inbound gateway for a tunnel that allows reaching a specific destination."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:156
+msgid "Time when a tunnel expires."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:157
+msgid ""
+"Pair of public keys to be able to encrypt messages (to send through the "
+"tunnel and reach the destination)."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:159
+msgid ""
+"Routers themselves send their routerInfo to the netDb directly, while "
+"leaseSets are sent through outbound tunnels\n"
+"(leaseSets need to be sent anonymously, to avoid correlating a router "
+"with his leaseSets)."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:164
+msgid ""
+"We can combine the above concepts to build successful connections in the "
+"network."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:168
+msgid ""
+"To build up her own inbound and outbound tunnels, Alice does a lookup in "
+"the netDb to collect routerInfo.\n"
+"This way, she gathers lists of peers she can use as hops in her tunnels.\n"
+"She can then send a build message to the first hop, requesting the "
+"construction of a tunnel and asking\n"
+"that router to send the construction message onward, until the tunnel has"
+" been constructed."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:175
+msgid "Request information on other routers"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:177
+msgid "Build tunnel using router information"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:179
+msgid "Figure 2: Router information is used to build tunnels."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:182
+msgid ""
+"When Alice wants to send a message to Bob, she first does a lookup in the"
+" \n"
+"netDb to find Bob's leaseSet, giving her his current inbound tunnel "
+"gateways. \n"
+"She then picks one of her outbound tunnels and sends the message down it "
+"with \n"
+"instructions for the outbound tunnel's endpoint to forward the message on"
+" \n"
+"to one of Bob's inbound tunnel gateways. When the outbound tunnel "
+"endpoint \n"
+"receives those instructions, it forwards the message as requested, and "
+"when \n"
+"Bob's inbound tunnel gateway receives it, it is forwarded down the tunnel"
+" \n"
+"to Bob's router. If Alice wants Bob to be able to reply to the message, "
+"she \n"
+"needs to transmit her own destination explicitly as part of the message "
+"itself.\n"
+"This can be done by introducing a higher-level layer, which is done in "
+"the\n"
+"streaming library.\n"
+"Alice may also cut down on the response time by bundling her most \n"
+"recent LeaseSet with the message so that Bob doesn't need to do a netDb "
+"lookup \n"
+"for it when he wants to reply, but this is optional."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:199
+msgid "Connect tunnels using LeaseSets"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:199
+msgid "Connect tunnels using leaseSets"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:201
+msgid "Figure 3: LeaseSets are used to connect outbound and inbound tunnels."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:204
+msgid ""
+"While the tunnels themselves have layered encryption to prevent "
+"unauthorized \n"
+"disclosure to peers inside the network (as the transport layer itself "
+"does \n"
+"to prevent unauthorized disclosure to peers outside the network), it is "
+"necessary \n"
+"to add an additional end to end layer of encryption to hide the message "
+"from \n"
+"the outbound tunnel endpoint and the inbound tunnel gateway. This \"garlic \n"
+"encryption\" lets Alice's router wrap up multiple messages into a "
+"single \n"
+"\"garlic message\", encrypted to a particular public key so that "
+"intermediary \n"
+"peers cannot determine either how many messages are within the garlic, "
+"what \n"
+"those messages say, or where those individual cloves are destined. For "
+"typical \n"
+"end to end communication between Alice and Bob, the garlic will be "
+"encrypted \n"
+"to the public key published in Bob's leaseSet, allowing the message to be"
+" \n"
+"encrypted without giving out the public key to Bob's own router."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:219
+msgid ""
+"Another important fact to keep in mind is that I2P is entirely message "
+"based \n"
+"and that some messages may be lost along the way. Applications using I2P "
+"can \n"
+"use the message oriented interfaces and take care of their own congestion"
+" \n"
+"control and reliability needs, but most would be best served by reusing "
+"the \n"
+"provided streaming library to view I2P as "
+"a streams \n"
+"based network."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:229
+msgid ""
+"Both inbound and outbound tunnels work along similar principles.\n"
+"The tunnel gateway accumulates a number of tunnel messages, eventually "
+"preprocessing \n"
+"them into something for tunnel delivery. Next, the gateway encrypts that "
+"preprocessed \n"
+"data and forwards it to the first hop. That peer and subsequent tunnel "
+"participants \n"
+"add on a layer of encryption after verifying that it isn't a duplicate "
+"before \n"
+"forward it on to the next peer. Eventually, the message arrives at the "
+"endpoint \n"
+"where the messages are split out again and forwarded on as requested. The"
+" \n"
+"difference arises in what the tunnel's creator does - for inbound "
+"tunnels, \n"
+"the creator is the endpoint and they simply decrypt all of the layers "
+"added, \n"
+"while for outbound tunnels, the creator is the gateway and they pre-"
+"decrypt \n"
+"all of the layers so that after all of the layers of per-hop encryption "
+"are \n"
+"added, the message arrives in the clear at the tunnel endpoint."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:244
+msgid ""
+"The choice of specific peers to pass on messages as well as their "
+"particular \n"
+"ordering is important to understanding both I2P's anonymity and "
+"performance \n"
+"characteristics. While the network database (below) has its own criteria "
+"for \n"
+"picking what peers to query and store entries on, tunnel creators may use"
+" any peers \n"
+"in the network in any order (and even any number of times) in a single "
+"tunnel. \n"
+"If perfect latency and capacity data were globally known, selection and "
+"ordering \n"
+"would be driven by the particular needs of the client in tandem with "
+"their \n"
+"threat model. Unfortunately, latency and capacity data is not trivial to "
+"gather \n"
+"anonymously, and depending upon untrusted peers to provide this "
+"information \n"
+"has its own serious anonymity implications."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:257
+msgid ""
+"From an anonymity perspective, the simplest technique would be to pick "
+"peers \n"
+"randomly from the entire network, order them randomly and use those peers"
+" \n"
+"in that order for all eternity. From a performance perspective, the "
+"simplest \n"
+"technique would be to pick the fastest peers with the necessary spare "
+"capacity, \n"
+"spreading the load across different peers to handle transparent failover,"
+" \n"
+"and to rebuild the tunnel whenever capacity information changes. While "
+"the \n"
+"former is both brittle and inefficient, the later requires inaccessible "
+"information \n"
+"and offers insufficient anonymity. I2P is instead working on offering a "
+"range \n"
+"of peer selection strategies, coupled with anonymity aware measurement "
+"code \n"
+"to organize the peers by their profiles."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:270
+msgid ""
+"As a base, I2P is constantly profiling the peers with which it interacts"
+" \n"
+"with by measuring their indirect behavior - for instance, when a peer "
+"responds \n"
+"to a netDb lookup in 1.3 seconds, that round trip latency is recorded in "
+"the \n"
+"profiles for all of the routers involved in the two tunnels (inbound and "
+"outbound) \n"
+"through which the request and response passed, as well as the queried "
+"peer's \n"
+"profile. Direct measurement, such as transport layer latency or "
+"congestion, \n"
+"is not used as part of the profile, as it can be manipulated and "
+"associated \n"
+"with the measuring router, exposing them to trivial attacks. While "
+"gathering \n"
+"these profiles, a series of calculations are run on each to summarize its"
+" \n"
+"performance - its latency, capacity to handle lots of activity, whether "
+"they \n"
+"are currently overloaded, and how well integrated into the network they "
+"seem \n"
+"to be. These calculations are then compared for active peers to organize "
+"the \n"
+"routers into four tiers - fast and high capacity, high capacity, not "
+"failing, \n"
+"and failing. The thresholds for those tiers are determined dynamically, "
+"and \n"
+"while they currently use fairly simple algorithms, alternatives exist."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:288
+msgid ""
+"Using this profile data, the simplest reasonable peer selection strategy"
+" \n"
+"is to pick peers randomly from the top tier (fast and high capacity), and"
+" \n"
+"this is currently deployed for client tunnels. Exploratory tunnels (used "
+"for \n"
+"netDb and tunnel management) pick peers randomly from the \"not failing\""
+" tier \n"
+"(which includes routers in 'better' tiers as well), allowing the peer to "
+"sample \n"
+"routers more widely, in effect optimizing the peer selection through "
+"randomized \n"
+"hill climbing. These strategies alone do however leak information "
+"regarding \n"
+"the peers in the router's top tier through predecessor and netDb "
+"harvesting \n"
+"attacks. In turn, several alternatives exist which, while not balancing "
+"the \n"
+"load as evenly, will address the attacks mounted by particular classes of"
+" \n"
+"adversaries."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:302
+msgid ""
+"By picking a random key and ordering the peers according to their XOR "
+"distance \n"
+"from it, the information leaked is reduced in predecessor and harvesting "
+"attacks \n"
+"according to the peers' failure rate and the tier's churn. Another simple"
+" \n"
+"strategy for dealing with netDb harvesting attacks is to simply fix the "
+"inbound \n"
+"tunnel gateway(s) yet randomize the peers further on in the tunnels. To "
+"deal \n"
+"with predecessor attacks for adversaries which the client contacts, the "
+"outbound \n"
+"tunnel endpoints would also remain fixed. The selection of which peer to "
+"fix \n"
+"on the most exposed point would of course need to have a limit to the "
+"duration, \n"
+"as all peers fail eventually, so it could either be reactively adjusted "
+"or \n"
+"proactively avoided to mimic a measured mean time between failures of "
+"other \n"
+"routers. These two strategies can in turn be combined, using a fixed "
+"exposed \n"
+"peer and an XOR based ordering within the tunnels themselves. A more "
+"rigid \n"
+"strategy would fix the exact peers and ordering of a potential tunnel, "
+"only \n"
+"using individual peers if all of them agree to participate in the same "
+"way \n"
+"each time. This varies from the XOR based ordering in that the "
+"predecessor \n"
+"and successor of each peer is always the same, while the XOR only makes "
+"sure \n"
+"their order doesn't change."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:322
+#, python-format
+msgid ""
+"As mentioned before, I2P currently (release 0.8) includes the tiered \n"
+"random strategy above, with XOR-based ordering. A \n"
+"more detailed discussion of the mechanics involved in tunnel operation, "
+"management, \n"
+"and peer selection can be found in the tunnel "
+"spec."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:330
+#, python-format
+msgid ""
+"As mentioned earlier, I2P's netDb works to share the network's metadata.\n"
+"This is detailed in the network database page,\n"
+"but a basic explanation is available below."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:336
+msgid ""
+"A percentage of I2P users are appointed as 'floodfill peers'.\n"
+"Currently, I2P installations that have a lot of bandwidth and are fast "
+"enough,\n"
+"will appoint themselves as floodfill as soon as the number of existing "
+"floodfill routers\n"
+"drops too low."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:343
+#, python-format
+msgid ""
+"Other I2P routers will store their data and lookup data by sending simple"
+" 'store' and 'lookup' queries to the floodfills.\n"
+"If a floodfill router receives a 'store' query, it will spread the "
+"information to other floodfill routers\n"
+"using the Kademlia "
+"algorithm.\n"
+"The 'lookup' queries currently function differently, to avoid an "
+"important\n"
+"security issue.\n"
+"When a lookup is done, the floodfill router will not forward the lookup "
+"to other peers,\n"
+"but will always answer by itself (if it has the requested data)."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:353
+msgid "Two types of information are stored in the network database."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:357
+msgid ""
+"A RouterInfo stores information on a specific I2P router and how "
+"to contact it"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:358
+msgid ""
+"A LeaseSet stores information on a specific destination (e.g. I2P "
+"website, e-mail server...)"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:360
+msgid ""
+"All of this information is signed by the publishing party and verified by"
+" any I2P router using or storing the information.\n"
+"In addition, the data contains timing information, to avoid storage of "
+"old entries and possible attacks.\n"
+"This is also why I2P bundles the necessary code for maintaining the "
+"correct time, occasionally querying some SNTP servers \n"
+"(the pool.ntp.org round robin by"
+" default)\n"
+"and detecting skew between routers at the transport layer."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:368
+msgid "Some additional remarks are also important."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:373
+msgid "Unpublished and encrypted leasesets:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:374
+msgid ""
+"One could only want specific people to be able to reach a destination.\n"
+"This is possible by not publishing the destination in the netDb. You will"
+" however have to transmit the destination by other means.\n"
+"An alternative are the 'encrypted leaseSets'. These leaseSets can only be"
+" decoded by people with access to the decryption key."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:381
+msgid "Bootstrapping:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:382
+msgid ""
+"Bootstrapping the netDb is quite simple. Once a router manages to receive"
+" a single routerInfo of a reachable peer,\n"
+"it can query that router for references to other routers in the network.\n"
+"Currently, a number of users post their routerInfo files to a website to "
+"make this information available.\n"
+"I2P automatically connects to one of these websites to gather routerInfo "
+"files and bootstrap."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:390
+msgid "Lookup scalability:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:391
+msgid ""
+"Lookups in the I2P network are not forwarded to other netDb routers.\n"
+"Currently, this is not a major problem, since the network is not very "
+"large.\n"
+"However, as the network grows, not all routerInfo and leaseSet files will"
+" be present\n"
+"on each netDb router. This will cause a deterioration of the percentage "
+"of successful lookups.\n"
+"Because of this, refinements to the netDb will be done in the next "
+"releases."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:402
+msgid ""
+"Communication between routers needs to provide confidentiality and "
+"integrity \n"
+"against external adversaries while authenticating that the router "
+"contacted \n"
+"is the one who should receive a given message. The particulars of how "
+"routers \n"
+"communicate with other routers aren't critical - three separate protocols"
+" \n"
+"have been used at different points to provide those bare necessities."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:410
+#, python-format
+msgid ""
+"I2P started with a TCP-based protocol which \n"
+"has since been disabled. Then, to accommodate the need for high degree "
+"communication \n"
+"(as a number of routers will end up speaking with many others), I2P moved"
+" \n"
+"from a TCP based transport to a UDP-based one - "
+"\"Secure \n"
+"Semireliable UDP\", or \"SSU\"."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:418
+#, python-format
+msgid "As described in the SSU spec:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:422
+msgid ""
+"The goal of this protocol is to provide secure, authenticated, \n"
+"semireliable and unordered message delivery, exposing only a minimal "
+"amount \n"
+"of data easily discernible to third parties. It should support high "
+"degree \n"
+"communication as well as TCP-friendly congestion control and may include"
+" \n"
+"PMTU detection. It should be capable of efficiently moving bulk data at "
+"rates \n"
+"sufficient for home users. In addition, it should support techniques for "
+"addressing \n"
+"network obstacles, like most NATs or firewalls."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:432
+#, python-format
+msgid ""
+"Following the introduction of SSU, after issues with congestion collapse"
+" \n"
+"appeared, a new NIO-based TCP transport called NTCP \n"
+"was implemented. It is enabled by default for outbound connections only. "
+"Those \n"
+"who configure their NAT/firewall to allow inbound connections and specify"
+" \n"
+"the external host and port (dyndns/etc is ok) on /config.jsp can receive "
+"inbound \n"
+"connections. As NTCP is NIO based, so it doesn't suffer from the 1 thread"
+" \n"
+"per connection issues of the old TCP transport."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:442
+msgid ""
+"I2P supports multiple transports simultaneously. A particular transport \n"
+"for an outbound connection is selected with \"bids\". Each transport bids"
+" for \n"
+"the connection and the relative value of these bids assigns the priority."
+" \n"
+"Transports may reply with different bids, depending on whether there is "
+"already \n"
+"an established connection to the peer."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:450
+#, python-format
+msgid ""
+"The current implementation ranks NTCP as the highest-priority transport \n"
+"for outbound connections in most situations. SSU is enabled for both "
+"outbound \n"
+"and inbound connections. Your firewall and your I2P router must be "
+"configured \n"
+"to allow inbound NTCP connections. For further information see the NTCP \n"
+"page."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:459
+msgid ""
+"A bare minimum set of cryptographic primitives are combined together to \n"
+"provide I2P's layered defenses against a variety of adversaries. At the "
+"lowest \n"
+"level, inter router communication is protected by the transport layer "
+"security \n"
+"- SSU encrypts each packet with AES256/CBC with both an explicit IV and "
+"MAC \n"
+"(HMAC-MD5-128) after agreeing upon an ephemeral session key through a "
+"2048bit \n"
+"Diffie-Hellman exchange, station-to-station authentication with the other"
+" \n"
+"router's DSA key, plus each network message has their own hash for local "
+"integrity \n"
+"checking. Tunnel messages passed over the "
+"transports \n"
+"have their own layered AES256/CBC encryption with an explicit IV and "
+"verified \n"
+"at the tunnel endpoint with an additional SHA256 hash. Various other "
+"messages \n"
+"are passed along inside \"garlic messages\", which are encrypted with "
+"ElGamal/AES+SessionTags \n"
+"(explained below)."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:474
+msgid "Garlic messages"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:475
+msgid ""
+"Garlic messages are an extension of \"onion\" layered encryption, "
+"allowing \n"
+"the contents of a single message to contain multiple \"cloves\" - fully "
+"formed \n"
+"messages alongside their own instructions for delivery. Messages are "
+"wrapped \n"
+"into a garlic message whenever the message would otherwise be passing in "
+"cleartext \n"
+"through a peer who should not have access to the information - for "
+"instance, \n"
+"when a router wants to ask another router to participate in a tunnel, "
+"they \n"
+"wrap the request inside a garlic, encrypt that garlic to the receiving "
+"router's \n"
+"2048bit ElGamal public key, and forward it through a tunnel. Another "
+"example \n"
+"is when a client wants to send a message to a destination - the sender's "
+"router \n"
+"will wrap up that data message (alongside some other messages) into a "
+"garlic, \n"
+"encrypt that garlic to the 2048bit ElGamal public key published in the "
+"recipient's \n"
+"leaseSet, and forward it through the appropriate tunnels."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:490
+msgid ""
+"The \"instructions\" attached to each clove inside the encryption layer "
+"includes \n"
+"the ability to request that the clove be forwarded locally, to a remote "
+"router, \n"
+"or to a remote tunnel on a remote router. There are fields in those "
+"instructions \n"
+"allowing a peer to request that the delivery be delayed until a certain "
+"time \n"
+"or condition has been met, though they won't be honored until the nontrivial \n"
+"delays are deployed. It is possible to explicitly route garlic "
+"messages \n"
+"any number of hops without building tunnels, or even to reroute tunnel "
+"messages \n"
+"by wrapping them in garlic messages and forwarding them a number of hops "
+"prior \n"
+"to delivering them to the next hop in the tunnel, but those techniques "
+"are \n"
+"not currently used in the existing implementation."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:503
+msgid "Session tags"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:504
+msgid ""
+"As an unreliable, unordered, message based system, I2P uses a simple "
+"combination \n"
+"of asymmetric and symmetric encryption algorithms to provide data "
+"confidentiality \n"
+"and integrity to garlic messages. As a whole, the combination is referred"
+" \n"
+"to as ElGamal/AES+SessionTags, but that is an excessively verbose way to "
+"describe \n"
+"the simple use of 2048bit ElGamal, AES256, SHA256 and 32 byte nonces."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:543
+msgid ""
+"Session tags themselves have a very short lifetime, after which they are"
+" \n"
+"discarded if not used. In addition, the quantity stored for each key is "
+"limited, \n"
+"as are the number of keys themselves - if too many arrive, either new or "
+"old \n"
+"messages may be dropped. The sender keeps track whether messages using "
+"session \n"
+"tags are getting through, and if there isn't sufficient communication it "
+"may \n"
+"drop the ones previously assumed to be properly delivered, reverting back"
+" \n"
+"to the full expensive ElGamal encryption."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:553
+msgid ""
+"One alternative is to transmit only a single session tag, and from that,"
+" \n"
+"seed a deterministic PRNG for determining what tags to use or expect. By "
+"keeping \n"
+"this PRNG roughly synchronized between the sender and recipient (the "
+"recipient \n"
+"precomputes a window of the next e.g. 50 tags), the overhead of "
+"periodically \n"
+"bundling a large number of tags is removed, allowing more options in the "
+"space/time \n"
+"tradeoff, and perhaps reducing the number of ElGamal encryptions "
+"necessary. \n"
+"However, it would depend upon the strength of the PRNG to provide the "
+"necessary \n"
+"cover against internal adversaries, though perhaps by limiting the amount"
+" \n"
+"of times each PRNG is used, any weaknesses can be minimized. At the "
+"moment, \n"
+"there are no immediate plans to move towards these synchronized PRNGs."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:566
+msgid "Future"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:567
+msgid ""
+"While I2P is currently functional and sufficient for many scenarios, "
+"there \n"
+"are several areas which require further improvement to meet the needs of "
+"those \n"
+"facing more powerful adversaries as well as substantial user experience "
+"optimization."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:573
+msgid "Restricted route operation"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:574
+msgid ""
+"I2P is an overlay network designed to be run on top of a functional "
+"packet \n"
+"switched network, exploiting the end to end principle to offer anonymity "
+"and \n"
+"security. While the Internet no longer fully embraces the end to end "
+"principle\n"
+"(due to the usage of NAT), \n"
+"I2P does require a substantial portion of the network to be reachable - "
+"there \n"
+"may be a number of peers along the edges running using restricted routes,"
+" \n"
+"but I2P does not include an appropriate routing algorithm for the "
+"degenerate \n"
+"case where most peers are unreachable. It would, however work on top of a"
+" \n"
+"network employing such an algorithm."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:586
+msgid ""
+"Restricted route operation, where there are limits to what peers are "
+"reachable \n"
+"directly, has several different functional and anonymity implications, "
+"dependent \n"
+"upon how the restricted routes are handled. At the most basic level, "
+"restricted \n"
+"routes exist when a peer is behind a NAT or firewall which does not allow"
+" \n"
+"inbound connections. This was largely addressed in I2P 0.6.0.6 by "
+"integrating \n"
+"distributed hole punching into the transport layer, allowing people "
+"behind \n"
+"most NATs and firewalls to receive unsolicited connections without any "
+"configuration. \n"
+"However, this does not limit the exposure of the peer's IP address to "
+"routers \n"
+"inside the network, as they can simply get introduced to the peer through"
+" \n"
+"the published introducer."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:599
+msgid ""
+"Beyond the functional handling of restricted routes, there are two levels"
+" \n"
+"of restricted operation that can be used to limit the exposure of one's "
+"IP \n"
+"address - using router-specific tunnels for communication, and offering "
+"'client \n"
+"routers'. For the former, routers can either build a new pool of tunnels "
+"or \n"
+"reuse their exploratory pool, publishing the inbound gateways to some of "
+"them \n"
+"as part of their routerInfo in place of their transport addresses. When a"
+" \n"
+"peer wants to get in touch with them, they see those tunnel gateways in "
+"the \n"
+"netDb and simply send the relevant message to them through one of the "
+"published \n"
+"tunnels. If the peer behind the restricted route wants to reply, it may "
+"do \n"
+"so either directly (if they are willing to expose their IP to the peer) "
+"or \n"
+"indirectly through their outbound tunnels. When the routers that the peer"
+" \n"
+"has direct connections to want to reach it (to forward tunnel messages, "
+"for \n"
+"instance), they simply prioritize their direct connection over the "
+"published \n"
+"tunnel gateway. The concept of 'client routers' simply extends the "
+"restricted \n"
+"route by not publishing any router addresses. Such a router would not "
+"even \n"
+"need to publish their routerInfo in the netDb, merely providing their "
+"self \n"
+"signed routerInfo to the peers that it contacts (necessary to pass the "
+"router's \n"
+"public keys). Both levels of restricted route operation are planned for "
+"I2P \n"
+"2.0."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:621
+msgid ""
+"There are tradeoffs for those behind restricted routes, as they would "
+"likely \n"
+"participate in other people's tunnels less frequently, and the routers "
+"which \n"
+"they are connected to would be able to infer traffic patterns that would "
+"not \n"
+"otherwise be exposed. On the other hand, if the cost of that exposure is "
+"less \n"
+"than the cost of an IP being made available, it may be worthwhile. This, "
+"of \n"
+"course, assumes that the peers that the router behind a restricted route "
+"contacts \n"
+"are not hostile - either the network is large enough that the probability"
+" \n"
+"of using a hostile peer to get connected is small enough, or trusted (and"
+" \n"
+"perhaps temporary) peers are used instead."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:633
+msgid "Variable latency"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:634
+msgid ""
+"Even though the bulk of I2P's initial efforts have been on low latency "
+"communication, \n"
+"it was designed with variable latency services in mind from the "
+"beginning. \n"
+"At the most basic level, applications running on top of I2P can offer the"
+" \n"
+"anonymity of medium and high latency communication while still blending "
+"their \n"
+"traffic patterns in with low latency traffic. Internally though, I2P can "
+"offer \n"
+"its own medium and high latency communication through the garlic "
+"encryption \n"
+"- specifying that the message should be sent after a certain delay, at a "
+"certain \n"
+"time, after a certain number of messages have passed, or another mix "
+"strategy. \n"
+"With the layered encryption, only the router that the clove exposed the "
+"delay \n"
+"request would know that the message requires high latency, allowing the "
+"traffic \n"
+"to blend in further with the low latency traffic. Once the transmission "
+"precondition \n"
+"is met, the router holding on to the clove (which itself would likely be "
+"a \n"
+"garlic message) simply forwards it as requested - to a router, to a "
+"tunnel, \n"
+"or, most likely, to a remote client destination."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:651
+msgid ""
+"There are a substantial number of ways to exploit this capacity for high"
+" \n"
+"latency comm in I2P, but for the moment, doing so has been scheduled for "
+"the \n"
+"I2P 3.0 release. In the meantime, those requiring the anonymity that high"
+" \n"
+"latency comm can offer should look towards the application layer to "
+"provide \n"
+"it."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:659
+msgid "Open questions"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:661
+msgid "How to get rid of the timing constraint?"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:662
+msgid "Can we deal with the sessionTags more efficiently?"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:663
+msgid ""
+"What, if any, batching/mixing strategies should be made available on the "
+"tunnels?"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:664
+msgid ""
+"What other tunnel peer selection and ordering strategies should be "
+"available?"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:667
+msgid "Similar systems"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:669
+msgid ""
+"I2P's architecture builds on the concepts of message oriented middleware,"
+" \n"
+"the topology of DHTs, the anonymity and cryptography of free route "
+"mixnets, \n"
+"and the adaptability of packet switched networking. The value comes not "
+"from \n"
+"novel concepts of algorithms though, but from careful engineering "
+"combining \n"
+"the research results of existing systems and papers. While there are a "
+"few \n"
+"similar efforts worth reviewing, both for technical and functional "
+"comparisons, \n"
+"two in particular are pulled out here - Tor and Freenet."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:679
+#, python-format
+msgid "See also the Network Comparisons Page."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:684
+#: i2p2www/pages/site/docs/how/tech-intro.html:749
+msgid "website"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:686
+msgid ""
+"At first glance, Tor and I2P have many functional and anonymity related \n"
+"similarities. While I2P's development began before we were aware of the "
+"early \n"
+"stage efforts on Tor, many of the lessons of the original onion routing "
+"and \n"
+"ZKS efforts were integrated into I2P's design. Rather than building an "
+"essentially \n"
+"trusted, centralized system with directory servers, I2P has a self "
+"organizing \n"
+"network database with each peer taking on the responsibility of profiling"
+" \n"
+"other routers to determine how best to exploit available resources. "
+"Another \n"
+"key difference is that while both I2P and Tor use layered and ordered "
+"paths \n"
+"(tunnels and circuits/streams), I2P is fundamentally a packet switched "
+"network, \n"
+"while Tor is fundamentally a circuit switched one, allowing I2P to "
+"transparently \n"
+"route around congestion or other network failures, operate redundant "
+"pathways, \n"
+"and load balance the data across available resources. While Tor offers "
+"the \n"
+"useful outproxy functionality by offering integrated outproxy discovery "
+"and \n"
+"selection, I2P leaves such application layer decisions up to applications"
+" \n"
+"running on top of I2P - in fact, I2P has even externalized the TCP-like "
+"streaming \n"
+"library itself to the application layer, allowing developers to "
+"experiment \n"
+"with different strategies, exploiting their domain specific knowledge to "
+"offer \n"
+"better performance."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:707
+msgid ""
+"From an anonymity perspective, there is much similarity when the core "
+"networks \n"
+"are compared. However, there are a few key differences. When dealing with"
+" \n"
+"an internal adversary or most external adversaries, I2P's simplex tunnels"
+" \n"
+"expose half as much traffic data than would be exposed with Tor's duplex "
+"circuits \n"
+"by simply looking at the flows themselves - an HTTP request and response "
+"would \n"
+"follow the same path in Tor, while in I2P the packets making up the "
+"request \n"
+"would go out through one or more outbound tunnels and the packets making "
+"up \n"
+"the response would come back through one or more different inbound "
+"tunnels. \n"
+"While I2P's peer selection and ordering strategies should sufficiently "
+"address \n"
+"predecessor attacks, should a switch to bidirectional tunnels be "
+"necessary,\n"
+"we could simply build an inbound and outbound tunnel along the same "
+"routers."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:721
+msgid ""
+"Another anonymity issue comes up in Tor's use of telescopic tunnel "
+"creation, \n"
+"as simple packet counting and timing measurements as the cells in a "
+"circuit \n"
+"pass through an adversary's node exposes statistical information "
+"regarding \n"
+"where the adversary is within the circuit. I2P's unidirectional tunnel "
+"creation \n"
+"with a single message so that this data is not exposed. Protecting the "
+"position \n"
+"in a tunnel is important, as an adversary would otherwise be able to "
+"mount \n"
+"a series of powerful predecessor, intersection, and traffic confirmation "
+"attacks."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:731
+msgid ""
+"Tor's support for a second tier of \"onion proxies\" does offer a non-"
+"trivial \n"
+"degree of anonymity while requiring a low cost of entry, while I2P will "
+"not \n"
+"offer this topology until 2.0."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:737
+msgid ""
+"On the whole, Tor and I2P complement each other in their focus - Tor "
+"works \n"
+"towards offering high speed anonymous Internet outproxying, while I2P "
+"works \n"
+"towards offering a decentralized resilient network in itself. In theory, "
+"both \n"
+"can be used to achieve both purposes, but given limited development "
+"resources, \n"
+"they both have their strengths and weaknesses. The I2P developers have "
+"considered \n"
+"the steps necessary to modify Tor to take advantage of I2P's design, but "
+"concerns \n"
+"of Tor's viability under resource scarcity suggest that I2P's packet "
+"switching \n"
+"architecture will be able to exploit scarce resources more effectively."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:751
+msgid ""
+"Freenet played a large part in the initial stages of I2P's design - "
+"giving \n"
+"proof to the viability of a vibrant pseudonymous community completely "
+"contained \n"
+"within the network, demonstrating that the dangers inherent in outproxies"
+" \n"
+"could be avoided. The first seed of I2P began as a replacement "
+"communication \n"
+"layer for Freenet, attempting to factor out the complexities of a "
+"scalable, \n"
+"anonymous and secure point to point communication from the complexities "
+"of \n"
+"a censorship resistant distributed data store. Over time however, some of"
+" \n"
+"the anonymity and scalability issues inherent in Freenet's algorithms "
+"made \n"
+"it clear that I2P's focus should stay strictly on providing a generic "
+"anonymous \n"
+"communication layer, rather than as a component of Freenet. Over the "
+"years, \n"
+"the Freenet developers have come to see the weaknesses in the older "
+"design, \n"
+"prompting them to suggest that they will require a \"premix\" layer to "
+"offer \n"
+"substantial anonymity. In other words, Freenet needs to run on top of a "
+"mixnet \n"
+"such as I2P or Tor, with \"client nodes\" requesting and publishing data "
+"through \n"
+"the mixnet to the \"server nodes\" which then fetch and store the data "
+"according \n"
+"to Freenet's heuristic distributed data storage algorithms."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:770
+msgid ""
+"Freenet's functionality is very complementary to I2P's, as Freenet "
+"natively \n"
+"provides many of the tools for operating medium and high latency systems,"
+" \n"
+"while I2P natively provides the low latency mix network suitable for "
+"offering \n"
+"adequate anonymity. The logic of separating the mixnet from the "
+"censorship-\n"
+"resistant distributed data store still seems self-evident from an "
+"engineering, \n"
+"anonymity, security, and resource allocation perspective, so hopefully "
+"the \n"
+"Freenet team will pursue efforts in that direction, if not simply reusing"
+" \n"
+"(or helping to improve, as necessary) existing mixnets like I2P or Tor."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:781
+msgid ""
+"It is worth mentioning that there has recently been discussion and work \n"
+"by the Freenet developers on a \"globally scalable darknet\" using "
+"restricted \n"
+"routes between peers of various trust. While insufficient information has"
+" \n"
+"been made publicly available regarding how such a system would operate "
+"for \n"
+"a full review, from what has been said the anonymity and scalability "
+"claims \n"
+"seem highly dubious. In particular, the appropriateness for use in "
+"hostile \n"
+"regimes against state level adversaries has been tremendously overstated,"
+" \n"
+"and any analysis on the implications of resource scarcity upon the "
+"scalability \n"
+"of the network has seemingly been avoided. Further questions regarding "
+"susceptibility \n"
+"to traffic analysis, trust and other topics do exist, but a more in-depth"
+" \n"
+"review of this \"globally scalable darknet\" will have to wait until the "
+"Freenet \n"
+"team makes more information available."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:797
+msgid ""
+"I2P itself doesn't really do much - it simply sends messages to remote "
+"destinations \n"
+"and receives messages targeting local destinations - most of the "
+"interesting \n"
+"work goes on at the layers above it. By itself, I2P could be seen as an "
+"anonymous \n"
+"and secure IP layer, and the bundled streaming"
+" library \n"
+"as an implementation of an anonymous and secure TCP layer on top of it. "
+"Beyond \n"
+"that, I2PTunnel exposes a generic TCP "
+"proxying \n"
+"system for either getting into or out of the I2P network, plus a variety "
+"of \n"
+"network applications provide further functionality for end users."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:808
+msgid "Streaming library"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:809
+msgid ""
+"The I2P streaming library can be viewed as a generic streaming interface "
+"(mirroring TCP sockets),\n"
+"and the implementation supports a sliding "
+"window protocol\n"
+"with several optimizations, to take into account the high delay over I2P."
+"\n"
+"Individual streams may adjust the maximum packet size and \n"
+"other options, though the default of 4KB compressed seems a reasonable "
+"tradeoff \n"
+"between the bandwidth costs of retransmitting lost messages and the "
+"latency \n"
+"of multiple messages."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:819
+msgid ""
+"In addition, in consideration of the relatively high cost of subsequent \n"
+"messages, the streaming library's protocol for scheduling and delivering "
+"messages \n"
+"has been optimized to allow individual messages passed to contain as much"
+" \n"
+"information as is available. For instance, a small HTTP transaction "
+"proxied \n"
+"through the streaming library can be completed in a single round trip - "
+"the \n"
+"first message bundles a SYN, FIN and the small payload (an HTTP request "
+"typically \n"
+"fits) and the reply bundles the SYN, FIN, ACK and the small payload (many"
+" \n"
+"HTTP responses fit). While an additional ACK must be transmitted to tell "
+"the \n"
+"HTTP server that the SYN/FIN/ACK has been received, the local HTTP proxy "
+"can \n"
+"deliver the full response to the browser immediately."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:832
+msgid ""
+"On the whole, however, the streaming library bears much resemblance to an"
+" \n"
+"abstraction of TCP, with its sliding windows, congestion control "
+"algorithms \n"
+"(both slow start and congestion avoidance), and general packet behavior "
+"(ACK, \n"
+"SYN, FIN, RST, etc)."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:839
+msgid "Naming library and addressbook"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:840
+#, python-format
+msgid ""
+"For more information see the Naming and "
+"Addressbook page."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:844
+#: i2p2www/pages/site/docs/how/tech-intro.html:918
+#: i2p2www/pages/site/docs/how/tech-intro.html:965
+#: i2p2www/pages/site/docs/how/tech-intro.html:997
+#: i2p2www/pages/site/docs/how/tech-intro.html:1005
+#: i2p2www/pages/site/docs/how/tech-intro.html:1013
+#: i2p2www/pages/site/docs/how/tech-intro.html:1023
+#: i2p2www/pages/site/docs/how/tech-intro.html:1031
+#: i2p2www/pages/site/docs/how/tech-intro.html:1053
+#, python-format
+msgid "Developed by: %(dev)s"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:846
+msgid ""
+"Naming within I2P has been an oft-debated topic since the very beginning"
+" \n"
+"with advocates across the spectrum of possibilities. However, given I2P's"
+" \n"
+"inherent demand for secure communication and decentralized operation, the"
+" \n"
+"traditional DNS-style naming system is clearly out, as are \"majority "
+"rules\" \n"
+"voting systems. Instead, I2P ships with a generic naming library and a "
+"base \n"
+"implementation designed to work off a local name to destination mapping, "
+"as \n"
+"well as an optional add-on application called the \"addressbook\". The "
+"addressbook \n"
+"is a web-of-trust-driven secure, distributed, and human readable naming "
+"system, \n"
+"sacrificing only the call for all human readable names to be globally "
+"unique \n"
+"by mandating only local uniqueness. While all messages in I2P are "
+"cryptographically \n"
+"addressed by their destination, different people can have local "
+"addressbook \n"
+"entries for \"Alice\" which refer to different destinations. People can "
+"still \n"
+"discover new names by importing published addressbooks of peers specified"
+" \n"
+"in their web of trust, by adding in the entries provided through a third "
+"party, \n"
+"or (if some people organize a series of published addressbooks using a "
+"first \n"
+"come first serve registration system) people can choose to treat these "
+"addressbooks \n"
+"as name servers, emulating traditional DNS."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:866
+msgid ""
+"I2P does not promote the use of DNS-like services though, as the damage \n"
+"done by hijacking a site can be tremendous - and insecure destinations "
+"have \n"
+"no value. DNSsec itself still falls back on registrars and certificate "
+"authorities, \n"
+"while with I2P, requests sent to a destination cannot be intercepted or "
+"the \n"
+"reply spoofed, as they are encrypted to the destination's public keys, "
+"and \n"
+"a destination itself is just a pair of public keys and a certificate. "
+"DNS-style \n"
+"systems on the other hand allow any of the name servers on the lookup "
+"path \n"
+"to mount simple denial of service and spoofing attacks. Adding on a "
+"certificate \n"
+"authenticating the responses as signed by some centralized certificate "
+"authority \n"
+"would address many of the hostile nameserver issues but would leave open "
+"replay \n"
+"attacks as well as hostile certificate authority attacks."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:880
+msgid ""
+"Voting style naming is dangerous as well, especially given the "
+"effectiveness \n"
+"of Sybil attacks in anonymous systems - the attacker can simply create an"
+" \n"
+"arbitrarily high number of peers and \"vote\" with each to take over a "
+"given \n"
+"name. Proof-of-work methods can be used to make identity non-free, but as"
+" \n"
+"the network grows the load required to contact everyone to conduct online"
+" \n"
+"voting is implausible, or if the full network is not queried, different "
+"sets \n"
+"of answers may be reachable."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:890
+msgid ""
+"As with the Internet however, I2P is keeping the design and operation of"
+" \n"
+"a naming system out of the (IP-like) communication layer. The bundled "
+"naming \n"
+"library includes a simple service provider interface which alternate "
+"naming \n"
+"systems can plug into, allowing end users to drive what sort of naming "
+"tradeoffs \n"
+"they prefer."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:899
+msgid ""
+"The old Syndie bundled with I2P has been replaced by the new Syndie which"
+"\n"
+"is distributed separately. For more information see the Syndie\n"
+"pages."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:905
+msgid ""
+"Syndie is a safe, anonymous blogging / content publication / content "
+"aggregation \n"
+"system. It lets you create information, share it with others, and read "
+"posts \n"
+"from those you're interested in, all while taking into consideration your"
+" \n"
+"needs for security and anonymity. Rather than building its own content "
+"distribution \n"
+"network, Syndie is designed to run on top of existing networks, "
+"syndicating \n"
+"content through eepsites, Tor hidden services, Freenet freesites, normal "
+"websites, \n"
+"usenet newsgroups, email lists, RSS feeds, etc. Data published with "
+"Syndie \n"
+"is done so as to offer pseudonymous authentication to anyone reading or "
+"archiving \n"
+"it."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:920
+msgid ""
+"I2PTunnel is probably I2P's most popular and versatile client "
+"application, \n"
+"allowing generic proxying both into and out of the I2P network. I2PTunnel"
+" \n"
+"can be viewed as four separate proxying applications - a \"client\" which"
+" receives \n"
+"inbound TCP connections and forwards them to a given I2P destination, an "
+"\"httpclient\" \n"
+"(aka \"eepproxy\") which acts like an HTTP proxy and forwards the "
+"requests to \n"
+"the appropriate I2P destination (after querying the naming service if "
+"necessary), \n"
+"a \"server\" which receives inbound I2P streaming connections on a "
+"destination \n"
+"and forwards them to a given TCP host+port, and an \"httpserver\" which "
+"extends \n"
+"the \"server\" by parsing the HTTP request and responses to allow safer "
+"operation. \n"
+"There is an additional \"socksclient\" application, but its use is not "
+"encouraged \n"
+"for reasons previously mentioned."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:934
+msgid ""
+"I2P itself is not an outproxy network - the anonymity and security "
+"concerns \n"
+"inherent in a mix net which forwards data into and out of the mix have "
+"kept \n"
+"I2P's design focused on providing an anonymous network which capable of "
+"meeting \n"
+"the user's needs without requiring external resources. However, the "
+"I2PTunnel \n"
+"\"httpclient\" application offers a hook for outproxying - if the "
+"hostname requested \n"
+"doesn't end in \".i2p\", it picks a random destination from a user-"
+"provided \n"
+"set of outproxies and forwards the request to them. These destinations "
+"are \n"
+"simply I2PTunnel \"server\" instances run by volunteers who have "
+"explicitly \n"
+"chosen to run outproxies - no one is an outproxy by default, and running "
+"an \n"
+"outproxy doesn't automatically tell other people to proxy through you. "
+"While \n"
+"outproxies do have inherent weaknesses, they offer a simple proof of "
+"concept \n"
+"for using I2P and provide some functionality under a threat model which "
+"may \n"
+"be sufficient for some users."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:950
+msgid ""
+"I2PTunnel enables most of the applications in use. An \"httpserver\" "
+"pointing \n"
+"at a webserver lets anyone run their own anonymous website (or "
+"\"eepsite\") \n"
+"- a webserver is bundled with I2P for this purpose, but any webserver can"
+" \n"
+"be used. Anyone may run a \"client\" pointing at one of the anonymously "
+"hosted \n"
+"IRC servers, each of which are running a \"server\" pointing at their "
+"local \n"
+"IRCd and communicating between IRCds over their own \"client\" tunnels. "
+"End \n"
+"users also have \"client\" tunnels pointing at I2Pmail's \n"
+"POP3 and SMTP destinations (which in turn are simply \"server\" instances"
+" pointing \n"
+"at POP3 and SMTP servers), as well as \"client\" tunnels pointing at "
+"I2P's CVS \n"
+"server, allowing anonymous development. At times people have even run "
+"\"client\" \n"
+"proxies to access the \"server\" instances pointing at an NNTP server."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:967
+msgid ""
+"i2p-bt is a port of the mainline python BitTorrent client to run both the"
+" \n"
+"tracker and peer communication over I2P. Tracker requests are forwarded "
+"through \n"
+"the eepproxy to eepsites specified in the torrent file while tracker "
+"responses \n"
+"refer to peers by their destination explicitly, allowing i2p-bt to open "
+"up \n"
+"a streaming lib connection to query them "
+"for \n"
+"blocks."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:976
+msgid ""
+"In addition to i2p-bt, a port of bytemonsoon has been made to I2P, making"
+" \n"
+"a few modifications as necessary to strip any anonymity-compromising "
+"information \n"
+"from the application and to take into consideration the fact that IPs "
+"cannot \n"
+"be used for identifying peers."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:984
+msgid ""
+"I2PSnark developed: jrandom, et al, ported from mjw's Snark client"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:990
+msgid ""
+"Bundled with the I2P install, I2PSnark offers a simple anonymous "
+"BitTorrent \n"
+"client with multitorrent capabilities, exposing all of the functionality "
+"through \n"
+"a plain HTML web interface."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:999
+#, python-format
+msgid ""
+"Robert is a Bittorrent client written in Python.\n"
+"It is hosted on http://%(bob)s/Robert.html "
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:1007
+#, python-format
+msgid ""
+"PyBit is a Bittorrent client written in Python.\n"
+"It is hosted on %(pybit)s "
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:1015
+msgid ""
+"I2Phex is a fairly direct port of the Phex Gnutella filesharing client to"
+" \n"
+"run entirely on top of I2P. While it has disabled some of Phex's "
+"functionality, \n"
+"such as integration with Gnutella webcaches, the basic file sharing and "
+"chatting \n"
+"system is fully functional."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:1025
+msgid ""
+"iMule is a fairly direct port of the aMule filesharing client \n"
+"running entirely inside I2P."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:1033
+#, python-format
+msgid ""
+"I2Pmail is more a service than an application - postman offers both "
+"internal \n"
+"and external email with POP3 and SMTP service through I2PTunnel instances"
+" \n"
+"accessing a series of components developed with mastiejaner, allowing "
+"people \n"
+"to use their preferred mail clients to send and receive mail "
+"pseudonymously. \n"
+"However, as most mail clients expose substantial identifying information,"
+" \n"
+"I2P bundles susi23's web based susimail client which has been built "
+"specifically \n"
+"with I2P's anonymity needs in mind. The I2Pmail/mail.i2p service offers "
+"transparent \n"
+"virus filtering as well as denial of service prevention with hashcash "
+"augmented \n"
+"quotas. In addition, each user has control of their batching strategy "
+"prior \n"
+"to delivery through the mail.i2p outproxies, which are separate from the "
+"mail.i2p \n"
+"SMTP and POP3 servers - both the outproxies and inproxies communicate "
+"with \n"
+"the mail.i2p SMTP and POP3 servers through I2P itself, so compromising "
+"those \n"
+"non-anonymous locations does not give access to the mail accounts or "
+"activity \n"
+"patterns of the user. At the moment the developers work on a "
+"decentralized \n"
+"mailsystem, called \"v2mail\". More information can be found on the "
+"eepsite \n"
+"%(postman)s."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:1055
+msgid ""
+"I2P-Bote is a distributed e-mail application. It does not use the "
+"traditional\n"
+"e-mail concept of sending an e-mail to a server and retrieving it from a "
+"server.\n"
+"Instead, it uses a Kademlia Distributed Hash Table to store mails.\n"
+"One user can push a mail into the DHT, while another can request the "
+"e-mail from the DHT.\n"
+"And all the mails sent within the I2P-Bote network are automatically "
+"encrypted end-to-end.
\n"
+"Furthermore, I2P-Bote offers a remailer function on top of I2P, for "
+"increased high-latency anonymity."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:1065
+msgid ""
+"I2P-Messenger is an end-to-end encrypted serverless communication "
+"application.\n"
+"For communication between two users, they need to give each other their "
+"destination keys, to allow the other to connect.\n"
+"It supports file transfer and has a search for other users, based on "
+"Seedless."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:2
+msgid "I2P's Threat Model"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:3
+msgid "November 2010"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:7
+msgid "low"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:8
+msgid "medium"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:9
+msgid "high"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:34
+msgid "Damage Potential"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:35
+msgid "Reliability"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:36
+msgid "Exploitability"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:37
+msgid "Affected Users"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:38
+msgid "Discoverability"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:39
+msgid "Severity"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:40
+#: i2p2www/pages/site/docs/protocol/i2np.html:94
+msgid "Priority"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:45
+msgid "What do we mean by \"anonymous\"?"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:47
+msgid ""
+"Your level of anonymity can be described as \"how hard it is for someone\n"
+"to find out information you don't want them to know?\" - who you are, "
+"where\n"
+"you are located, who you communicate with, or even when you communicate."
+" \n"
+"\"Perfect\" anonymity is not a useful concept here - software will not "
+"make \n"
+"you indistinguishable from people that don't use computers or who are not"
+" on\n"
+"the Internet. Instead, we are working to provide sufficient anonymity to"
+" meet the\n"
+"real needs of whomever we can - from those simply browsing websites, to "
+"those exchanging\n"
+"data, to those fearful of discovery by powerful organizations or states."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:58
+msgid ""
+"The question of whether I2P provides sufficient anonymity for your \n"
+"particular needs is a hard one, but this page will hopefully assist in \n"
+"answering that question by exploring how I2P operates under various "
+"attacks\n"
+"so that you may decide whether it meets your needs."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:65
+msgid ""
+"We welcome further research and analysis on I2P's resistance to the "
+"threats described below.\n"
+"More review of existing literature (much of it focused on Tor) and "
+"original\n"
+"work focused on I2P is needed."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:71
+msgid "Network Topology Summary"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:72
+#, python-format
+msgid ""
+"I2P builds off the ideas of many other \n"
+"systems, but a few key points should be kept in"
+" mind when \n"
+"reviewing related literature:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:78
+msgid ""
+"I2P is a free route mixnet - the message creator explicitly "
+"defines the\n"
+"path that messages will be sent out (the outbound tunnel), and the "
+"message \n"
+"recipient explicitly defines the path that messages will be received on "
+"(the\n"
+"inbound tunnel)."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:84
+msgid ""
+"I2P has no official entry and exit points - all peers fully "
+"participate in the \n"
+"mix, and there are no network layer in- or out-proxies (however, at the \n"
+"application layer, a few proxies do exist)"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:89
+msgid ""
+"I2P is fully distributed - there are no central controls or "
+"authorities.\n"
+"One could modify some routers to operate mix cascades (building tunnels "
+"and giving\n"
+"out the keys necessary to control the forwarding at the tunnel endpoint) "
+"or directory \n"
+"based profiling and selection, all without breaking compatibility with "
+"the rest of \n"
+"the network, but doing so is of course not necessary (and may even harm "
+"one's\n"
+"anonymity)."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:99
+#, python-format
+msgid ""
+"We have documented plans to implement nontrivial delays\n"
+"and batching strategies \n"
+"whose existence is only known to the particular hop or tunnel gateway "
+"that \n"
+"receives the message, allowing a mostly low latency mixnet to provide "
+"cover \n"
+"traffic for higher latency communication (e.g. email).\n"
+"However we are aware that significant delays are required to provide "
+"meaningful\n"
+"protection, and that implementation of such delays will be a significant "
+"challenge.\n"
+"It is not clear at this time whether we will actually implement these "
+"delay features."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:110
+msgid ""
+"In theory, routers along the message path may inject an \n"
+"arbitrary number of hops before forwarding the message to the next peer, "
+"though\n"
+"the current implementation does not."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:117
+msgid "The Threat Model"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:118
+msgid ""
+"I2P design started in 2003, not long after the advent of\n"
+"[Onion Routing],\n"
+"[Freenet], and\n"
+"[Tor].\n"
+"Our design benefits substantially from the research published around that"
+" time.\n"
+"I2P uses several onion routing techniques, so we continue to benefit\n"
+"from the significant academic interest in Tor."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:128
+msgid ""
+"Taking from the attacks and analysis put forth in the \n"
+"anonymity "
+"literature (largely \n"
+"Traffic Analysis: "
+"Protocols, Attacks, Design \n"
+"Issues and Open Problems), the following briefly describes a wide "
+"variety \n"
+"of attacks as well as many of I2Ps defenses. We update\n"
+"this list to include new attacks as they are identified."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:137
+msgid ""
+"Included are some attacks that may be unique to I2P.\n"
+"We do not have good answers for all these attacks, however\n"
+"we continue to do research and improve our defenses."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:143
+msgid ""
+"In addition, many of these attacks are significantly easier than\n"
+"they should be, due to the modest size of the current network.\n"
+"While we are aware of some limitations that need to be addressed,\n"
+"I2P is designed to support hundreds of thousands, or millions, of\n"
+"participants.\n"
+"As we continue to spread the word and grow the network,\n"
+"these attacks will become much harder."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:153
+#, python-format
+msgid ""
+"The\n"
+"network comparisons and\n"
+"\"garlic\" terminology pages may also "
+"be helpful\n"
+"to review."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:182
+msgid "Index of Attacks"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:184
+#: i2p2www/pages/site/docs/how/threat-model.html:204
+msgid "Brute force attacks"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:185
+#: i2p2www/pages/site/docs/how/threat-model.html:248
+msgid "Timing attacks"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:186
+#: i2p2www/pages/site/docs/how/threat-model.html:285
+msgid "Intersection attacks"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:187
+#: i2p2www/pages/site/docs/how/threat-model.html:365
+msgid "Denial of service attacks"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:188
+#: i2p2www/pages/site/docs/how/threat-model.html:464
+msgid "Tagging attacks"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:189
+#: i2p2www/pages/site/docs/how/threat-model.html:482
+msgid "Partitioning attacks"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:190
+#: i2p2www/pages/site/docs/how/threat-model.html:522
+msgid "Predecessor attacks"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:191
+#: i2p2www/pages/site/docs/how/threat-model.html:567
+msgid "Harvesting attacks"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:192
+#: i2p2www/pages/site/docs/how/threat-model.html:614
+msgid "Identification Through Traffic Analysis"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:193
+#: i2p2www/pages/site/docs/how/threat-model.html:674
+msgid "Sybil attacks"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:194
+#: i2p2www/pages/site/docs/how/threat-model.html:723
+msgid "Buddy Exhaustion attacks"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:195
+#: i2p2www/pages/site/docs/how/threat-model.html:748
+msgid "Cryptographic attacks"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:196
+msgid "Floodfill attacks"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:197
+#: i2p2www/pages/site/docs/how/threat-model.html:809
+msgid "Other Network Database attacks"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:198
+msgid "Attacks on centralized resources"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:199
+#: i2p2www/pages/site/docs/how/threat-model.html:875
+msgid "Development attacks"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:200
+msgid "Implementation attacks"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:201
+#: i2p2www/pages/site/docs/how/threat-model.html:959
+msgid "Other Defenses"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:208
+msgid ""
+"A brute force attack can be mounted by a global passive or active "
+"adversary, \n"
+"watching all the messages pass between all of the nodes and attempting to"
+" correlate\n"
+"which message follows which path. Mounting this attack against I2P "
+"should be \n"
+"nontrivial, as all peers in the network are frequently sending messages "
+"(both\n"
+"end to end and network maintenance messages), plus an end to end message "
+"changes\n"
+"size and data along its path. In addition, the external adversary does "
+"not have\n"
+"access to the messages either, as inter-router communication is both "
+"encrypted\n"
+"and streamed (making two 1024 byte messages indistinguishable from one "
+"2048 byte\n"
+"message)."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:220
+msgid ""
+"However, a powerful attacker can use brute force to detect trends - if "
+"they \n"
+"can send 5GB to an I2P destination and monitor everyone's network "
+"connection,\n"
+"they can eliminate all peers who did not receive 5GB of data. Techniques"
+" to \n"
+"defeat this attack exist, but may be prohibitively expensive (see: \n"
+"Tarzan's "
+"mimics\n"
+"or constant rate traffic). Most users are not concerned with this "
+"attack, as \n"
+"the cost of mounting it are extreme (and often require illegal activity)."
+" \n"
+"However, the attack is still possible, for example by an observer at\n"
+"a large ISP or an Internet exchange point.\n"
+"Those who want to defend against it \n"
+"would want to take appropriate countermeasures, such as\n"
+"setting low bandwidth limits, and using unpublished or encrypted "
+"leasesets for eepsites.\n"
+"Other countermeasures, such as nontrivial delays and restricted routes, "
+"are\n"
+"not currently implemented."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:237
+#, python-format
+msgid ""
+"As a partial defense against a single router or group of routers trying "
+"to route all the network's traffic,\n"
+"routers contain limits as to how many tunnels can be routed through a "
+"single peer.\n"
+"As the network grows, these limits are subject to further adjustment.\n"
+"Other mechanisms for peer rating, selection and avoidance\n"
+"are discussed on the\n"
+"peer selection page."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:252
+msgid ""
+"I2P's messages are unidirectional and do not necessarily imply that a "
+"reply\n"
+"will be sent. However, applications on top of I2P will most likely have\n"
+"recognizable patterns within the frequency of their messages - for "
+"instance, an \n"
+"HTTP request will be a small message with a large sequence of reply "
+"messages \n"
+"containing the HTTP response. Using this data as well as a broad view of"
+" the \n"
+"network topology, an attacker may be able to disqualify some links as "
+"being too \n"
+"slow to have passed the message along."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:262
+msgid ""
+"This sort of attack is powerful, but its applicability to I2P is non "
+"obvious,\n"
+"as the variation on message delays due to queuing, message processing, "
+"and \n"
+"throttling will often meet or exceed the time of passing a message along "
+"a \n"
+"single link - even when the attacker knows that a reply will be sent as "
+"soon as\n"
+"the message is received. There are some scenarios which will expose "
+"fairly \n"
+"automatic replies though - the streaming library does (with the SYN+ACK) "
+"as does the \n"
+"message mode of guaranteed delivery (with the "
+"DataMessage+DeliveryStatusMessage)."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:272
+#, python-format
+msgid ""
+"Without protocol scrubbing or higher latency, global active adversaries "
+"can \n"
+"gain substantial information. As such, people concerned with these "
+"attacks could\n"
+"increase the latency (using nontrivial "
+"delays or \n"
+"batching strategies), include protocol "
+"scrubbing, or\n"
+"other advanced tunnel routing techniques,\n"
+"but these are unimplemented in I2P."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:281
+#, python-format
+msgid ""
+"References: Low-Resource Routing Attacks Against "
+"Anonymous Systems"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:289
+msgid ""
+"Intersection attacks against low latency systems are extremely powerful -"
+"\n"
+"periodically make contact with the target and keep track of what peers "
+"are on\n"
+"the network. Over time, as node churn occurs the attacker will gain \n"
+"significant information about the target by simply intersecting the sets "
+"of\n"
+"peers that are online when a message successfully goes through. The cost"
+" of \n"
+"this attack is significant as the network grows, but may be feasible in "
+"some\n"
+"scenarios."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:299
+#, python-format
+msgid ""
+"In summary, if an attacker is at both ends of your tunnel at the same "
+"time,\n"
+"he may be successful.\n"
+"I2P does not have a full defense to this for low latency communication.\n"
+"This is an inherent weakness of low-latency onion routing.\n"
+"Tor provides a similar disclaimer."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:307
+msgid "Partial defenses implemented in I2P:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:311
+#, python-format
+msgid "strict ordering of peers"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:314
+#, python-format
+msgid ""
+"peer profiling and selection from a "
+"small group that changes slowly"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:317
+msgid "Limits on the number of tunnels routed through a single peer"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:320
+msgid ""
+"Prevention of peers from the same /16 IP range from being members of a "
+"single tunnel"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:323
+msgid ""
+"For eepsites or other hosted services, we support\n"
+"simultaneous hosting on multiple routers, or\n"
+"multihoming"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:330
+msgid ""
+"Even in total, these defenses are not a complete solution.\n"
+"Also, we have made some design choices that may significantly increase "
+"our vulnerability:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:335
+msgid "We do not use low-bandwidth \"guard nodes\""
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:338
+msgid ""
+"We use tunnel pools comprised of several tunnels, and traffic can shift "
+"from tunnel to tunnel."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:341
+msgid "Tunnels are not long-lived; new tunnels are built every 10 minutes."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:344
+msgid ""
+"Tunnel lengths are configurable.\n"
+"While 3-hop tunnels are recommended for full protection, several "
+"applications and\n"
+"services use 2-hop tunnels by default."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:351
+#, python-format
+msgid ""
+"In the future, it could\n"
+"for peers who can afford significant delays (per nontrivial\n"
+"delays and batching strategies). "
+"In addition,\n"
+"this is only relevant for destinations that other people know about - a "
+"private\n"
+"group whose destination is only known to trusted peers does not have to "
+"worry,\n"
+"as an adversary can't \"ping\" them to mount the attack."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:360
+#, python-format
+msgid "Reference: One Cell Enough"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:367
+msgid ""
+"There are a whole slew of denial of service attacks available against "
+"I2P,\n"
+"each with different costs and consequences:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:373
+msgid ""
+"Greedy user attack: This is simply\n"
+"people trying to consume significantly more resources than they are \n"
+"willing to contribute. The defense against this is:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:379
+#, python-format
+msgid ""
+"Set defaults so that most users provide resources to the network.\n"
+"In I2P, users route traffic by default. In sharp distinction to\n"
+"other networks,\n"
+"over 95% of I2P users relay traffic for others."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:385
+msgid ""
+"Provide easy configuration options so that users may increase their\n"
+"contribution (share percentage) to the network. Display easy-to-"
+"understand\n"
+"metrics such as \"share ratio\" so that users may see what they are "
+"contributing."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:390
+msgid ""
+"Maintain a strong community with blogs, forums, IRC, and other means of "
+"communication."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:397
+#, python-format
+msgid ""
+"Starvation attack: A hostile user may attempt to harm the network "
+"by\n"
+"creating a significant number of peers in the network who are not "
+"identified as\n"
+"being under control of the same entity (as with Sybil). These nodes then"
+" \n"
+"decide not to provide any resources to the network, causing existing "
+"peers \n"
+"to search through a larger network database or request more tunnels than"
+" \n"
+"should be necessary. \n"
+"Alternatively, the nodes may provide intermittent service by periodically"
+"\n"
+"dropping selected traffic, or refusing connections to certain peers.\n"
+"This behavior may be indistinguishable from that of a heavily-loaded or "
+"failing node.\n"
+"I2P addresses these issues by maintaining profiles on the \n"
+"peers, attempting to identify underperforming ones and simply ignoring \n"
+"them, or using them rarely.\n"
+"We have significantly enhanced the\n"
+"ability to recognize and avoid troublesome peers; however there are still"
+"\n"
+"significant efforts required in this area."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:417
+#, python-format
+msgid ""
+"Flooding attack: A hostile user may attempt to flood the network,\n"
+"a peer, a destination, or a tunnel. Network and peer flooding is "
+"possible,\n"
+"and I2P does nothing to prevent standard IP layer flooding. The flooding"
+" of\n"
+"a destination with messages by sending a large number to the target's "
+"various\n"
+"inbound tunnel gateways is possible, but the destination will know this "
+"both\n"
+"by the contents of the message and because the tunnel's tests will fail."
+" The\n"
+"same goes for flooding just a single tunnel. I2P has no defenses for a "
+"network\n"
+"flooding attack. For a destination and tunnel flooding attack, the "
+"target\n"
+"identifies which tunnels are unresponsive and builds new ones. New code "
+"could\n"
+"also be written to add even more tunnels if the client wishes to handle "
+"the\n"
+"larger load. If, on the other hand, the load is more than the client can"
+"\n"
+"deal with, they can instruct the tunnels to throttle the number of "
+"messages or\n"
+"bytes they should pass on (once the advanced tunnel\n"
+"operation is implemented)."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:436
+msgid ""
+"CPU load attack: There are currently some methods for people to \n"
+"remotely request that a peer perform some cryptographically expensive \n"
+"operation, and a hostile attacker could use these to flood that peer with"
+"\n"
+"a large number of them in an attempt to overload the CPU. Both using "
+"good \n"
+"engineering practices and potentially requiring nontrivial certificates \n"
+"(e.g. HashCash) to be attached to these expensive requests should "
+"mitigate\n"
+"the issue, though there may be room for an attacker to exploit various\n"
+"bugs in the implementation."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:449
+#, python-format
+msgid ""
+"Floodfill DOS attack: A hostile user may attempt to harm the "
+"network by\n"
+"becoming a floodfill router. The current defenses against unreliable,\n"
+"intermittent, or malicious floodfill routers are poor.\n"
+"A floodfill router may provide bad or no response to lookups, and\n"
+"it may also interfere with inter-floodfill communication.\n"
+"Some defenses and\n"
+"peer profiling are implemented,\n"
+"however there is much more to do.\n"
+"For more information see the\n"
+"network database page."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:468
+#, python-format
+msgid ""
+"Tagging attacks - modifying a message so that it can later be identified"
+" \n"
+"further along the path - are by themselves impossible in I2P, as messages"
+" \n"
+"passed through tunnels are signed. However, if an attacker is the "
+"inbound \n"
+"tunnel gateway as well as a participant further along in that tunnel, "
+"with\n"
+"collusion they can identify the fact that they are in the same tunnel "
+"(and \n"
+"prior to adding unique hop ids and "
+"other updates,\n"
+"colluding peers within the same tunnel can recognize that fact without "
+"any \n"
+"effort). An attacker in an outbound tunnel and any part of an inbound "
+"tunnel cannot \n"
+"collude however, as the tunnel encryption pads and modifies the data "
+"separately\n"
+"for the inbound and outbound tunnels. External attackers cannot do "
+"anything,\n"
+"as the links are encrypted and messages signed."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:486
+msgid ""
+"Partitioning attacks - finding ways to segregate (technically or "
+"analytically)\n"
+"the peers in a network - are important to keep in mind when dealing with "
+"a \n"
+"powerful adversary, since the size of the network plays a key role in "
+"determining\n"
+"your anonymity. Technical partitioning by cutting links between peers to"
+" create\n"
+"fragmented networks is addressed by I2P's built in network database, "
+"which \n"
+"maintains statistics about various peers so as to allow any existing "
+"connections\n"
+"to other fragmented sections to be exploited so as to heal the network. "
+"However,\n"
+"if the attacker does disconnect all links to uncontrolled peers, "
+"essentially\n"
+"isolating the target, no amount of network database healing will fix it."
+" At\n"
+"that point, the only thing the router can hope to do is notice that a "
+"significant\n"
+"number of previously reliable peers have become unavailable and alert the"
+" client\n"
+"that it is temporarily disconnected (this detection code is not "
+"implemented at\n"
+"the moment)."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:502
+#, python-format
+msgid ""
+"Partitioning the network analytically by looking for differences in how "
+"routers \n"
+"and destinations behave and grouping them accordingly is also a very "
+"powerful\n"
+"attack. For instance, an attacker harvesting"
+" the network\n"
+"database will know when a particular destination has 5 inbound tunnels in"
+" their\n"
+"LeaseSet while others have only 2 or 3, allowing the adversary to "
+"potentially \n"
+"partition clients by the number of tunnels selected. Another partition "
+"is \n"
+"possible when dealing with the nontrivial "
+"delays and \n"
+"batching strategies, as the tunnel "
+"gateways and the\n"
+"particular hops with non-zero delays will likely stand out. However, "
+"this data\n"
+"is only exposed to those specific hops, so to partition effectively on "
+"that \n"
+"matter, the attacker would need to control a significant portion of the "
+"network\n"
+"(and still that would only be a probabilistic partition, as they wouldn't"
+" know\n"
+"which other tunnels or messages have those delays)."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:518
+#, python-format
+msgid ""
+"Also discussed on the network database "
+"page (bootstrap attack)."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:526
+msgid ""
+"The predecessor attack is passively gathering statistics in an attempt to"
+" see\n"
+"what peers are 'close' to the destination by participating in their "
+"tunnels and\n"
+"keeping track of the previous or next hop (for outbound or inbound "
+"tunnels, \n"
+"respectively). Over time, using a perfectly random sample of peers and "
+"random\n"
+"ordering, an attacker would be able to see which peer shows up as "
+"'closer' \n"
+"statistically more than the rest, and that peer would in turn be where "
+"the\n"
+"target is located."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:536
+#, python-format
+msgid ""
+"I2P avoids this in four ways: first, the peers selected to participate in"
+"\n"
+"tunnels are not randomly sampled throughout the network - they are "
+"derived from\n"
+"the peer selection algorithm which "
+"breaks them\n"
+"into tiers. Second, with strict "
+"ordering of peers\n"
+"in a tunnel, the fact that a peer shows up more frequently does not mean "
+"they're\n"
+"the source. Third, with permuted "
+"tunnel length\n"
+"(not enabled by default)\n"
+"even 0 hop tunnels can provide plausible deniability as the occasional \n"
+"variation of the gateway will look like normal tunnels. Fourth, with \n"
+"restricted routes "
+"(unimplemented), only the peer with\n"
+"a restricted connection to the target will ever contact the target, while"
+" \n"
+"attackers will merely run into that gateway."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:553
+#, python-format
+msgid ""
+"The current tunnel build method\n"
+"was specifically designed to combat the predecessor attack.\n"
+"See also the intersection attack."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:559
+#, python-format
+msgid ""
+"References: %(pdf2008)s\n"
+"which is an update to the 2004 predecessor attack paper\n"
+"%(pdf2004)s."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:571
+msgid ""
+"\"Harvesting\" means compiling a list of users running I2P.\n"
+"It can be used for legal attacks and to help\n"
+"other attacks by simply running a peer, seeing who it connects to, and \n"
+"harvesting whatever references to other peers it can find."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:578
+msgid ""
+"I2P itself is not designed with effective defenses against\n"
+"this attack, since there is the distributed network database \n"
+"containing just this information.\n"
+"The following factors make the attack somewhat harder in practice:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:585
+msgid ""
+"Network growth will make it more difficult to obtain a given proportion "
+"of the network"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:588
+msgid "Floodfill routers implement query limits as DOS protection"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:591
+msgid ""
+"\"Hidden mode\", which prevents a router from publishing its information "
+"to the netDb,\n"
+"(but also prevents it from relaying data) is not widely used now but "
+"could be."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:597
+#, python-format
+msgid ""
+"In future implementations,\n"
+"basic and \n"
+"comprehensive restricted "
+"routes,\n"
+"this attack loses much of its power, as the \"hidden\" peers do not "
+"publish their\n"
+"contact addresses in the network database - only the tunnels through "
+"which \n"
+"they can be reached (as well as their public keys, etc)."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:606
+msgid ""
+"In the future, routers could use GeoIP to identify if they are in a "
+"particular\n"
+"country where identification as an I2P node would be risky.\n"
+"In that case, the router could automatically enable hidden mode, or\n"
+"enact other restricted route methods."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:618
+#, python-format
+msgid ""
+"By inspecting the traffic into and out of a router, a malicious ISP\n"
+"or state-level firewall could identify that a computer is running I2P.\n"
+"As discussed above, I2P is not specifically "
+"designed\n"
+"to hide that a computer is running I2P. However, several design decisions"
+" made\n"
+"in the design of the\n"
+"transport layer and protocols\n"
+"make it somewhat difficult to identify I2P traffic:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:628
+msgid "Random port selection"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:631
+msgid "Point-to-Point Encryption of all traffic"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:634
+msgid ""
+"DH key exchange with no protocol bytes or other unencrypted constant "
+"fields"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:637
+#, python-format
+msgid ""
+"Simultaneous use of both\n"
+"TCP and\n"
+"UDP transports.\n"
+"UDP may be much harder for some Deep Packet Inspection (DPI) equipment to"
+" track."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:645
+msgid ""
+"In the near future, we plan to directly address traffic analysis issues "
+"by further obfuscation of I2P transport protocols, possibly including:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:649
+msgid ""
+"Padding at the transport layer to random lengths, especially during the "
+"connection handshake"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:652
+msgid ""
+"Study of packet size distribution signatures, and additional padding as "
+"necessary"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:655
+msgid ""
+"Development of additional transport methods that mimic SSL or other "
+"common protocols"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:658
+msgid ""
+"Review of padding strategies at higher layers to see how they affect "
+"packet sizes at the transport layer"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:661
+msgid ""
+"Review of methods implemented by various state-level firewalls to block "
+"Tor"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:664
+msgid "Working directly with DPI and obfuscation experts"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:669
+#, python-format
+msgid ""
+"Reference: Breaking and Improving Protocol "
+"Obfuscation"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:678
+msgid ""
+"Sybil describes a category of attacks where the adversary creates "
+"arbitrarily\n"
+"large numbers of colluding nodes and uses the increased numbers to help \n"
+"mounting other attacks. For instance, if an attacker is in a network "
+"where peers\n"
+"are selected randomly and they want an 80% chance to be one of those "
+"peers, they\n"
+"simply create five times the number of nodes that are in the network and "
+"roll \n"
+"the dice. When identity is free, Sybil can be a very potent technique "
+"for a \n"
+"powerful adversary. The primary technique to address this is simply to "
+"make \n"
+"identity 'non free' - Tarzan\n"
+"(among others) uses the fact that IP addresses are limited, while \n"
+"IIP used \n"
+"HashCash to 'charge' for "
+"creating a new\n"
+"identity. We currently have not implemented any particular technique to "
+"address\n"
+"Sybil, but do include placeholder certificates in the router's and \n"
+"destination's data structures which can contain a HashCash certificate of"
+" \n"
+"appropriate value when necessary (or some other certificate proving "
+"scarcity)."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:696
+msgid "Requiring HashCash Certificates in various places has two major problems:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:700
+msgid "Maintaining backward compatibility"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:703
+msgid ""
+"The classic HashCash problem -\n"
+"selecting HashCash values that are meaningful proofs of work on high-end "
+"machines,\n"
+"while still being feasible on low-end machines such as mobile devices."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:710
+msgid ""
+"Various limitations on the number of routers in a given IP range restrict"
+"\n"
+"the vulnerability to attackers that don't have the ability to put "
+"machines\n"
+"in several IP blocks.\n"
+"However, this is not a meaningful defense against a powerful adversary."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:717
+#, python-format
+msgid ""
+"See the network database page\n"
+"for more Sybil discussion."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:727
+#, python-format
+msgid ""
+"(Reference: In Search of an Anonymouns and Secure "
+"Lookup Section 5.2)"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:731
+#, python-format
+msgid ""
+"By refusing to accept or forward tunnel build requests, except to a "
+"colluding peer, a router could ensure\n"
+"that a tunnel is formed wholly from its set of colluding routers.\n"
+"The chances of success are enhanced if there is a large number of "
+"colluding routers,\n"
+"i.e. a Sybil attack.\n"
+"This is somewhat mitigated by our\n"
+"peer profiling methods used to monitor "
+"the performance\n"
+"of peers.\n"
+"However, this is a powerful attack as the number of routers approaches\n"
+"f = 0.2, or 20% malicious nodes, as specifed in the paper.\n"
+"The malicous routers could also maintain connections to the target router"
+" and provide\n"
+"excellent forwarding bandwidth for traffic over those connections, in an "
+"attempt\n"
+"to manipulate the profiles managed by the target and appear attractive.\n"
+"Further research and defenses may be necessary."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:752
+#, python-format
+msgid ""
+"We use strong cryptography with long keys, and\n"
+"we assume the security of the industry-standard cryptographic primitives "
+"used in I2P, as documented\n"
+"on the low-level cryptography page. \n"
+"Security features include the immediate detection of \n"
+"altered messages along the path, the inability to decrypt messages not "
+"addressed to you,\n"
+"and defense against man-in-the-middle attacks.\n"
+"The key sizes chosen in 2003 were quite conservative at the time, and are"
+" still longer than\n"
+"those used in other anonymity "
+"networks.\n"
+"We don't think the current key lengths are our biggest weakness,\n"
+"especially for traditional, non-state-level adversaries;\n"
+"bugs and the small size of the network are much more worrisome.\n"
+"Of course, all cryptographic algorithms eventually become obsolete due to"
+"\n"
+"the advent of faster processors, cryptographic research, and advancements"
+" in\n"
+"methods such as rainbow tables, clusters of video game hardware, etc.\n"
+"Unfortunately, I2P was not designed with easy mechanisms to lengthen keys"
+" or change\n"
+"shared secret values while maintaining backward compatibility."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:771
+#, python-format
+msgid ""
+"Upgrading the various data structures and protocols to support longer "
+"keys\n"
+"will have to be tackled eventually, and this will be a\n"
+"major undertaking, just as it will be "
+"for \n"
+"others.\n"
+"Hopefully, through careful planning, we can minimize the disruption, and\n"
+"implement mechanisms to make it easier for future transitions."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:780
+msgid ""
+"In the future, several I2P protocols and data structures\n"
+"support securely padding messages to arbitrary sizes, so messages could "
+"be made constant\n"
+"size or garlic messages could be modified randomly so that some cloves "
+"appear to contain\n"
+"more subcloves than they actually do. At the moment, however, garlic, "
+"tunnel, and \n"
+"end to end messages include simple random padding."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:790
+msgid "Floodfill Anonymity attacks"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:794
+#, python-format
+msgid ""
+"In addition to the floodfill DOS attacks described\n"
+"above, floodfill routers are uniquely positioned\n"
+"to learn about network participants, due to their role\n"
+"in the netDb, and the high frequency of communication with those "
+"participants.\n"
+"This is somewhat mitigated because floodfill routers only manage a "
+"portion\n"
+"of the total keyspace, and the keyspace rotates daily, as explained \n"
+"on the network database page.\n"
+"The specific mechanisms by which routers communicate with floodfills have"
+" been\n"
+"carefully designed.\n"
+"However, these threats should be studied further.\n"
+"The specific potential threats and corresponding defenses are a topic for"
+" future research."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:810
+#, python-format
+msgid ""
+"A hostile user may attempt to harm the network by\n"
+"creating one or more floodfill routers and crafting them to offer\n"
+"bad, slow, or no responses.\n"
+"Several scenarios are discussed on the\n"
+"network database page."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:820
+msgid "Central Resource Attacks"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:824
+msgid ""
+"There are a few centralized or limited resources (some inside I2P, some "
+"not)\n"
+"that could be attacked or used as a vector for attacks.\n"
+"The absence of jrandom starting November 2007, followed by the loss of "
+"the i2p.net hosting service in January 2008,\n"
+"highlighted numerous centralized resources in the development and "
+"operation of the I2P network,\n"
+"most of which are now distributed.\n"
+"Attacks on externally-reachable resources mainly affect the ability of "
+"new users to find us,\n"
+"not the operation of the network itself."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:834
+#, python-format
+msgid ""
+"The website is mirrored and uses DNS round-robin"
+" for external public access."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:837
+#, python-format
+msgid ""
+"Routers now support multiple external reseed "
+"locations,\n"
+"however more reseed hosts may be needed, and the handling of unreliable "
+"or malicious\n"
+"reseed hosts may need improvement."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:842
+msgid ""
+"Routers now support multiple update file locations.\n"
+"A malicious update host could feed a huge file, need to limit the size."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:846
+msgid "Routers now support multiple default trusted update signers."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:849
+msgid ""
+"Routers now better handle multiple unreliable "
+"floodfill peers.\n"
+"Malicious floodfills needs more study."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:853
+#, python-format
+msgid ""
+"The code is now stored in a distributed source "
+"control system."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:856
+msgid ""
+"Routers rely on a single news host, but there is a hardcoded backup URL "
+"pointing to a different host.\n"
+"A malicious news host could feed a huge file, need to limit the size."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:860
+#, python-format
+msgid ""
+"Naming system services, including addressbook "
+"subscription providers, add-host services,\n"
+"and jump services, could be malicious. Substantial protections for "
+"subscriptions were implemented\n"
+"in release 0.6.1.31, with additional enhancements in subsequent releases."
+"\n"
+"However, all naming services require some measure of trust, see\n"
+"the naming page for details."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:867
+msgid ""
+"We remain reliant on the DNS service for i2p2.de, losing this would cause"
+" substantial\n"
+"disruption in our ability to attract new users,\n"
+"and would shrink the network (in the short-to-medium term), just as the "
+"loss of i2p.net did."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:879
+msgid ""
+"These attacks aren't directly on the network, but instead go after its "
+"development team \n"
+"by either introducing legal hurdles on anyone contributing to the "
+"development\n"
+"of the software, or by using whatever means are available to get the "
+"developers to \n"
+"subvert the software. Traditional technical measures cannot defeat these"
+" attacks, and\n"
+"if someone threatened the life or livelihood of a developer (or even just"
+" issuing a \n"
+"court order along with a gag order, under threat of prison), we would "
+"have a big problem."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:888
+msgid "However, two techniques help defend against these attacks:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:892
+#, python-format
+msgid ""
+"All components of the network must be open source to enable inspection, "
+"verification, \n"
+"modification, and improvement. If a developer is compromised, once it is"
+" noticed \n"
+"the community should demand explanation and cease to accept that "
+"developer's work.\n"
+"All checkins to our distributed source control "
+"system\n"
+"are cryptographically signed, and the release packagers use a trust-list "
+"system\n"
+"to restrict modifications to those previously approved."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:900
+#, python-format
+msgid ""
+"Development over the network itself, allowing developers to stay "
+"anonymous but still \n"
+"secure the development process. All I2P development can occur through "
+"I2P - using\n"
+"a distributed source control system,\n"
+"a distributed source control system, IRC chat,\n"
+"public web servers,\n"
+"discussion forums (forum.i2p), and the software distribution sites,\n"
+"all available within I2P."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:911
+msgid ""
+"We also maintain relationships with various organizations that offer "
+"legal advice,\n"
+"should any defense be necessary."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:916
+msgid "Implementation attacks (bugs)"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:920
+msgid ""
+"Try as we might, most nontrivial applications include errors in the "
+"design or \n"
+"implementation, and I2P is no exception. There may be bugs that could be"
+" exploited to \n"
+"attack the anonymity or security of the communication running over I2P in"
+" unexpected \n"
+"ways. To help withstand attacks against the design or protocols in use, "
+"we publish \n"
+"all designs and documentation and solicit review and criticism with \n"
+"the hope that many eyes will improve the system.\n"
+"We do not believe in\n"
+"security through "
+"obscurity."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:931
+msgid ""
+"In addition, the code is being \n"
+"treated the same way, with little aversion towards reworking or throwing "
+"out \n"
+"something that isn't meeting the needs of the software system (including "
+"ease of \n"
+"modification). Documentation for the design and implementation of the "
+"network and \n"
+"the software components are an essential part of security, as without "
+"them it is \n"
+"unlikely that developers would be willing to spend the time to learn the "
+"software \n"
+"enough to identify shortcomings and bugs."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:941
+msgid ""
+"Our software is likely, in particular, to contain bugs related to denial "
+"of service\n"
+"through out-of-memory errors (OOMs), cross-site-scripting (XSS) issues "
+"in the router console,\n"
+"and other vulnerabilities to non-standard inputs via the various "
+"protocols."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:947
+#, python-format
+msgid ""
+"I2P is still a small network with a small development community and "
+"almost no\n"
+"interest from academic or research groups.\n"
+"Therefore we lack the analysis that\n"
+"other anonymity networks\n"
+"may have received. We continue to recruit people to\n"
+"get involved and help."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:960
+msgid "Blocklists"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:961
+msgid ""
+"To some extent, I2P could be enhanced to avoid peers operating at IP "
+"addresses\n"
+"listed in a blocklist. Several blocklists are commonly available in "
+"standard formats,\n"
+"listing anti-P2P organizations, potential state-level adversaries, and "
+"others."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:967
+msgid ""
+"To the extent that active peers actually do show up in the actual "
+"blocklist,\n"
+"blocking by only a subset of peers would tend to segment the network,\n"
+"exacerbate reachability problems, and decrease overall reliability.\n"
+"Therefore we would want to agree on a particular blocklist and\n"
+"enable it by default."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:975
+msgid ""
+"Blocklists are only a part (perhaps a small part) of an array of defenses"
+"\n"
+"against maliciousness.\n"
+"In large part the profiling system does a good job of measuring\n"
+"router behavior so that we don't need to trust anything in netDb.\n"
+"However there is more that can be done. For each of the areas in the\n"
+"list above there are improvements we can make in detecting badness."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:984
+msgid ""
+"If a blocklist is hosted at a central location with automatic updates\n"
+"the network is vulnerable to a\n"
+"central resource attack.\n"
+"Automatic subscription to a list gives the list provider the power to "
+"shut\n"
+"the i2p network down. Completely."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:992
+msgid ""
+"Currently, a default blocklist is distributed with our software,\n"
+"listing only the IPs of past DOS sources.\n"
+"There is no automatic update mechanism.\n"
+"Should a particular IP range implement serious attacks on the I2P "
+"network,\n"
+"we would have to ask people to update their blocklist manually through\n"
+"out-of-band mechanisms such as forums, blogs, etc."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tunnel-routing.html:2
+#: i2p2www/pages/site/docs/how/tunnel-routing.html:6
+msgid "Tunnel Overview"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tunnel-routing.html:3
+#: i2p2www/pages/site/docs/tunnels/unidirectional.html:3
+msgid "July 2011"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tunnel-routing.html:7
+msgid ""
+"This page contains an overview of I2P tunnel terminology and operation, "
+"with\n"
+"links to more technical pages, details, and specifications."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tunnel-routing.html:12
+#, python-format
+msgid ""
+"As briefly explained in the introduction, I2P "
+"builds virtual \"tunnels\" -\n"
+"temporary and unidirectional paths through a sequence of routers. These"
+" \n"
+"tunnels are classified as either inbound tunnels (where everything \n"
+"given to it goes towards the creator of the tunnel) or outbound tunnels\n"
+"(where the tunnel creator shoves messages away from them). When Alice\n"
+"wants to send a message to Bob, she will (typically) send it out one of\n"
+"her existing outbound tunnels with instructions for that tunnel's "
+"endpoint\n"
+"to forward it to the gateway router for one of Bob's current inbound \n"
+"tunnels, which in turn passes it to Bob."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tunnel-routing.html:25
+msgid "Alice connecting through her outbound tunnel to Bob via his inbound tunnel"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tunnel-routing.html:27
+msgid "Outbound Gateway"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tunnel-routing.html:28
+msgid "Outbound Participant"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tunnel-routing.html:29
+#: i2p2www/pages/site/docs/tunnels/implementation.html:131
+msgid "Outbound Endpoint"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tunnel-routing.html:30
+#: i2p2www/pages/site/docs/tunnels/implementation.html:140
+msgid "Inbound Gateway"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tunnel-routing.html:31
+msgid "Inbound Participant"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tunnel-routing.html:32
+msgid "Inbound Endpoint"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tunnel-routing.html:36
+msgid "Tunnel vocabulary"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tunnel-routing.html:38
+#, python-format
+msgid ""
+"Tunnel gateway - the first router in a tunnel. For inbound "
+"tunnels,\n"
+"this is the one mentioned in the LeaseSet published in the\n"
+"network database. For outbound tunnels, the\n"
+"gateway is the originating router. (e.g. both A and D above)"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tunnel-routing.html:44
+msgid ""
+"Tunnel endpoint - the last router in a tunnel. (e.g. both C and F"
+" above)"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tunnel-routing.html:45
+msgid ""
+"Tunnel participant - all routers in a tunnel except for the "
+"gateway or\n"
+"endpoint (e.g. both B and E above)"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tunnel-routing.html:49
+msgid ""
+"n-Hop tunnel - a tunnel with a specific number of inter-router "
+"jumps, e.g.:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tunnel-routing.html:51
+msgid "0-hop tunnel - a tunnel where the gateway is also the endpoint"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tunnel-routing.html:52
+msgid ""
+"1-hop tunnel - a tunnel where the gateway talks directly to the "
+"endpoint"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tunnel-routing.html:53
+msgid ""
+"2-(or more)-hop tunnel - a tunnel where there is at least one "
+"intermediate\n"
+"tunnel participant. (the above diagram includes two 2-hop tunnels - one\n"
+"outbound from Alice, one inbound to Bob)"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tunnel-routing.html:60
+#, python-format
+msgid ""
+"Tunnel ID - A 4 "
+"byte integer\n"
+"different for each hop in a tunnel, and unique among all tunnels on a "
+"router.\n"
+"Chosen randomly by the tunnel creator."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tunnel-routing.html:67
+msgid "Tunnel Build Information"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tunnel-routing.html:68
+#, python-format
+msgid ""
+"Routers performing the three roles (gateway, participant, endpoint) are "
+"given\n"
+"different pieces of data in the initial\n"
+"Tunnel Build Message\n"
+"to accomplish their tasks:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tunnel-routing.html:75
+msgid "The tunnel gateway gets:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tunnel-routing.html:77
+#: i2p2www/pages/site/docs/how/tunnel-routing.html:97
+#, python-format
+msgid ""
+"tunnel encryption key - an AES private key for "
+"encrypting\n"
+"messages and instructions to the next hop"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tunnel-routing.html:81
+#: i2p2www/pages/site/docs/how/tunnel-routing.html:101
+#, python-format
+msgid ""
+"tunnel IV key - an AES private key for "
+"double-encrypting\n"
+"the IV to the next hop"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tunnel-routing.html:85
+#: i2p2www/pages/site/docs/how/tunnel-routing.html:105
+#, python-format
+msgid ""
+"reply key - an AES public key for "
+"encrypting\n"
+"the reply to the tunnel build request"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tunnel-routing.html:89
+#: i2p2www/pages/site/docs/how/tunnel-routing.html:109
+msgid ""
+"reply IV - the IV for encrypting the reply to the tunnel build "
+"request"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tunnel-routing.html:90
+msgid "tunnel id - 4 byte integer (inbound gateways only)"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tunnel-routing.html:91
+msgid ""
+"next hop - what router is the next one in the path (unless this is"
+" a 0-hop tunnel, and the gateway is also the endpoint)"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tunnel-routing.html:92
+#: i2p2www/pages/site/docs/how/tunnel-routing.html:112
+msgid "next tunnel id - The tunnel ID on the next hop"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tunnel-routing.html:95
+msgid "All intermediate tunnel participants get:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tunnel-routing.html:110
+msgid "tunnel id - 4 byte integer"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tunnel-routing.html:111
+msgid "next hop - what router is the next one in the path"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tunnel-routing.html:115
+msgid "The tunnel endpoint gets:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tunnel-routing.html:117
+#, python-format
+msgid ""
+"tunnel encryption key - an AES private key for "
+"encrypting\n"
+"messages and instructions to the the endpoint (itself)"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tunnel-routing.html:121
+#, python-format
+msgid ""
+"tunnel IV key - an AES private key for "
+"double-encrypting\n"
+"the IV to the endpoint (itself)"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tunnel-routing.html:125
+#, python-format
+msgid ""
+"reply key - an AES public key for "
+"encrypting\n"
+"the reply to the tunnel build request (outbound endpoints only)"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tunnel-routing.html:129
+msgid ""
+"reply IV - the IV for encrypting the reply to the tunnel build "
+"request (outbound endpoints only)"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tunnel-routing.html:130
+msgid "tunnel id - 4 byte integer (outbound endpoints only)"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tunnel-routing.html:131
+msgid ""
+"reply router - the inbound gateway of the tunnel to send the reply"
+" through (outbound endpoints only)"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tunnel-routing.html:132
+msgid ""
+"reply tunnel id - The tunnel ID of the reply router (outbound "
+"endpoints only)"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tunnel-routing.html:137
+#, python-format
+msgid ""
+"Details are in the\n"
+"tunnel creation specification."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tunnel-routing.html:142
+msgid "Tunnel pooling"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tunnel-routing.html:143
+#, python-format
+msgid ""
+"Several tunnels for a particular purpose may be grouped into a \"tunnel "
+"pool\",\n"
+"as described in the\n"
+"tunnel specification.\n"
+"This provides redundancy and additional bandwidth.\n"
+"The pools used by the router itself are called \"exploratory tunnels\".\n"
+"The pools used by applications are called \"client tunnels\"."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tunnel-routing.html:154
+msgid "Tunnel length"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tunnel-routing.html:155
+#, python-format
+msgid ""
+"As mentioned above, each client requests that their router provide "
+"tunnels to\n"
+"include at least a certain number of hops.\n"
+"The decision as to how many routers\n"
+"to have in one's outbound and inbound tunnels has an important effect "
+"upon the\n"
+"latency, throughput, reliability, and anonymity provided by I2P - the "
+"more peers\n"
+"that messages have to go through, the longer it takes to get there and "
+"the more\n"
+"likely that one of those routers will fail prematurely. The less routers"
+" in a\n"
+"tunnel, the easier it is for an adversary to mount traffic analysis "
+"attacks and\n"
+"pierce someone's anonymity.\n"
+"Tunnel lengths are specified by clients via\n"
+"I2CP options.\n"
+"The maximum number of hops in a tunnel is 7."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tunnel-routing.html:171
+msgid "0-hop tunnels"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tunnel-routing.html:172
+msgid ""
+"With no remote routers in a tunnel, the user has very basic plausible\n"
+"deniability (since no one knows for sure that the peer that sent them the"
+"\n"
+"message wasn't simply just forwarding it on as part of the tunnel). "
+"However, it\n"
+"would be fairly easy to mount a statistical analysis attack and notice "
+"that\n"
+"messages targeting a specific destination are always sent through a "
+"single\n"
+"gateway. Statistical analysis against outbound 0-hop tunnels are more "
+"complex,\n"
+"but could show similar information (though would be slightly harder to "
+"mount)."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tunnel-routing.html:182
+msgid "1-hop tunnels"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tunnel-routing.html:183
+#, python-format
+msgid ""
+"With only one remote router in a tunnel, the user has both plausible\n"
+"deniability and basic anonymity, as long as they are not up against an "
+"internal\n"
+"adversary (as described on threat model)."
+" However,\n"
+"if the adversary ran a sufficient number of routers such that the single "
+"remote\n"
+"router in the tunnel is often one of those compromised ones, they would "
+"be able\n"
+"to mount the above statistical traffic analysis attack."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tunnel-routing.html:192
+msgid "2-hop tunnels"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tunnel-routing.html:193
+msgid ""
+"With two or more remote routers in a tunnel, the costs of mounting the "
+"traffic\n"
+"analysis attack increases, since many remote routers would have to be "
+"compromised\n"
+"to mount it."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tunnel-routing.html:199
+msgid "3-hop (or more) tunnels"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tunnel-routing.html:200
+#, python-format
+msgid ""
+"To reduce the susceptibility to some attacks,\n"
+"3 or more hops are recommended for the highest level of protection.\n"
+"Recent studies\n"
+"also conclude that more than 3 hops does not provide additional "
+"protection."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tunnel-routing.html:208
+msgid "Tunnel default lengths"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tunnel-routing.html:209
+#, python-format
+msgid ""
+"The router uses 2-hop tunnels by default for its exploratory tunnels.\n"
+"Client tunnel defaults are set by the application, using\n"
+"I2CP options.\n"
+"Most applications use 2 or 3 hops as their default."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tunnel-routing.html:218
+msgid "Tunnel testing"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tunnel-routing.html:219
+#, python-format
+msgid ""
+"All tunnels are periodically tested by their creator by sending a\n"
+"DeliveryStatusMessage out an outbound tunnel and bound for another "
+"inbound tunnel\n"
+"(testing both tunnels at once). If either fails a number of consecutive "
+"tests, it is marked as no longer\n"
+"functional. If it was used for a client's inbound tunnel, a new leaseSet\n"
+"is created.\n"
+"Tunnel test failures are also reflected in the\n"
+"capacity rating in the peer "
+"profile."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tunnel-routing.html:230
+msgid "Tunnel creation"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tunnel-routing.html:231
+#, python-format
+msgid ""
+"Tunnel creation is handled by garlic "
+"routing\n"
+"a Tunnel Build Message to a router, requesting that they participate in "
+"the\n"
+"tunnel (providing them with all of the appropriate information, as above,"
+" along\n"
+"with a certificate, which right now is a 'null' cert, but will support "
+"hashcash\n"
+"or other non-free certificates when necessary).\n"
+"That router forwards the message to the next hop in the tunnel.\n"
+"Details are in the\n"
+"tunnel creation specification."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tunnel-routing.html:245
+#, python-format
+msgid ""
+"Multi-layer encryption is handled by garlic"
+" encryption\n"
+"of tunnel messages.\n"
+"Details are in the\n"
+"tunnel specification.\n"
+"The IV of each hop is encrypted with a separate key as explained there."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tunnel-routing.html:257
+msgid ""
+"Other tunnel test techniques could be used, such as\n"
+"garlic wrapping a number of tests into cloves, testing individual tunnel\n"
+"participants separately, etc."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tunnel-routing.html:263
+msgid "Move to 3-hop exploratory tunnels defaults."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tunnel-routing.html:267
+msgid ""
+"In a distant future release,\n"
+"options specifying the pooling, mixing, and chaff generation settings may"
+" be implemented."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tunnel-routing.html:272
+msgid ""
+"In a distant future release,\n"
+"limits on the quantity and size of messages allowed during the\n"
+"tunnel's lifetime may be implemented (e.g. no more than 300 messages or\n"
+"1MB per minute)."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tunnel-routing.html:284
+#: i2p2www/pages/site/docs/tunnels/unidirectional.html:15
+msgid "Tunnel specification"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tunnel-routing.html:286
+#: i2p2www/pages/site/docs/tunnels/unidirectional.html:17
+msgid "Tunnel creation specification"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tunnel-routing.html:288
+msgid "Unidirectional tunnels"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tunnel-routing.html:290
+msgid "Tunnel message specification"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tunnel-routing.html:292
+msgid "Garlic routing"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tunnel-routing.html:294
+msgid "ElGamal/AES+SessionTag"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tunnel-routing.html:296
+msgid "I2CP options"
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2cp.html:3
+msgid "November 2012"
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2cp.html:6
+msgid ""
+"The I2P Client Protocol (I2CP) exposes a strong separation of concerns "
+"between\n"
+"the router and any client that wishes to communicate over the network. "
+"It enables\n"
+"secure and asynchronous messaging by sending and receiving messages over "
+"a \n"
+"single TCP socket, yet never exposing any private keys and authenticating"
+" itself\n"
+"to the router only through signatures. With I2CP, a client application "
+"tells the\n"
+"router who they are (their \"destination\"), what anonymity, reliability,"
+" and \n"
+"latency tradeoffs to make, and where to send messages. In turn the "
+"router uses\n"
+"I2CP to tell the client when any messages have arrived, and to request "
+"authorization\n"
+"for some tunnels to be used."
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2cp.html:18
+#, python-format
+msgid ""
+"The protocol itself has only been implemented in Java, to provide the\n"
+"Client SDK.\n"
+"This SDK is exposed in the i2p.jar package, which implements the client-"
+"side of I2CP.\n"
+"Clients should never need to access the router.jar package, which "
+"contains the\n"
+"router itself and the router-side of I2CP."
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2cp.html:26
+#, python-format
+msgid ""
+"While implementing the client side of I2CP in a non-Java language is "
+"certainly feasible,\n"
+"a non-Java client would also have to implement the\n"
+"streaming library for TCP-style "
+"connections.\n"
+"Together, implementing I2CP and the streaming library would be a sizable "
+"task."
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2cp.html:33
+#, python-format
+msgid ""
+"Applications can take advantage of the base I2CP plus the \n"
+"streaming and datagram libraries\n"
+"by using the Simple Anonymous Messaging or BOB protocols,\n"
+"which do not require clients to deal with any sort of cryptography.\n"
+"Also, clients may access the network by one of several proxies -\n"
+"HTTP, CONNECT, and SOCKS 4/4a/5.\n"
+"Alternatively, Java clients may access those libraries in "
+"ministreaming.jar and streaming.jar.\n"
+"So there are several options for both Java and non-Java applications."
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2cp.html:45
+#, python-format
+msgid ""
+"Client-side end-to-end encryption (encrypting the data over the I2CP "
+"connection)\n"
+"was disabled in I2P release 0.6,\n"
+"leaving in place the ElGamal/AES end-to-end "
+"encryption\n"
+"which is implemented in the router.\n"
+"The only cryptography that client libraries must still implement is\n"
+"DSA public/private key signing\n"
+"for LeaseSets and\n"
+"Session Configurations, and"
+" management of those keys."
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2cp.html:58
+msgid ""
+"In a standard I2P installation, port 7654 is used by external java "
+"clients to communicate\n"
+"with the local router via I2CP.\n"
+"By default, the router binds to address 127.0.0.1. To bind to 0.0.0.0, "
+"set the\n"
+"router advanced configuration option "
+"i2cp.tcp.bindAllInterfaces=true and restart.\n"
+"Clients in the same JVM as the router pass messages directly to the "
+"router\n"
+"through an internal JVM interface."
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2cp.html:67
+msgid "I2CP Protocol Specification"
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2cp.html:68
+#, python-format
+msgid "Now on the I2CP Specification page."
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2cp.html:73
+msgid "I2CP Initialization"
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2cp.html:74
+#, python-format
+msgid ""
+"When a client connects to the router, it first sends a single protocol "
+"version byte (0x2A).\n"
+"Then it sends a GetDate Message and "
+"waits for the SetDate Message "
+"response.\n"
+"Next, it sends a CreateSession "
+"Message containing the session configuration.\n"
+"It next awaits a RequestLeaseSet"
+" Message from the router, indicating that inbound tunnels\n"
+"have been built, and responds with a CreateLeaseSetMessage containing the"
+" signed LeaseSet.\n"
+"The client may now initiate or receive connections from other I2P "
+"destinations."
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2cp.html:83
+msgid "I2CP Options"
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2cp.html:84
+#, python-format
+msgid ""
+"The following options are traditionally passed to the router via\n"
+"a SessionConfig contained "
+"in a CreateSession Message or "
+"a ReconfigureSession "
+"Message."
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2cp.html:90
+msgid "Router-side Options"
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2cp.html:95
+#: i2p2www/pages/site/docs/protocol/i2cp.html:438
+msgid "As Of Release"
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2cp.html:96
+#: i2p2www/pages/site/docs/protocol/i2cp.html:439
+msgid "Recommended Arguments"
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2cp.html:97
+#: i2p2www/pages/site/docs/protocol/i2cp.html:440
+msgid "Allowable Range"
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2cp.html:105
+#: i2p2www/pages/site/docs/protocol/i2cp.html:118
+#: i2p2www/pages/site/docs/protocol/i2cp.html:127
+#: i2p2www/pages/site/docs/protocol/i2cp.html:136
+#: i2p2www/pages/site/docs/protocol/i2cp.html:145
+#: i2p2www/pages/site/docs/protocol/i2cp.html:160
+#: i2p2www/pages/site/docs/protocol/i2cp.html:175
+#: i2p2www/pages/site/docs/protocol/i2cp.html:184
+#: i2p2www/pages/site/docs/protocol/i2cp.html:232
+#: i2p2www/pages/site/docs/protocol/i2cp.html:244
+#: i2p2www/pages/site/docs/protocol/i2cp.html:256
+#, python-format
+msgid "number from %(from)s to %(to)s"
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2cp.html:106
+#: i2p2www/pages/site/docs/protocol/i2cp.html:128
+#: i2p2www/pages/site/docs/protocol/i2cp.html:137
+#: i2p2www/pages/site/docs/protocol/i2cp.html:146
+#: i2p2www/pages/site/docs/protocol/i2cp.html:161
+#: i2p2www/pages/site/docs/protocol/i2cp.html:233
+#: i2p2www/pages/site/docs/protocol/i2cp.html:245
+#: i2p2www/pages/site/docs/protocol/i2cp.html:257
+#: i2p2www/pages/site/docs/protocol/i2cp.html:530
+#, python-format
+msgid "%(from)s to %(to)s"
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2cp.html:108
+msgid ""
+"Number of tunnels in.\n"
+"Limit was increased from 6 to 16 in release 0.9; however, numbers higher "
+"than 6 are not\n"
+"currently recommended, as this is untested and is incompatible with older"
+" releases."
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2cp.html:119
+#: i2p2www/pages/site/docs/protocol/i2cp.html:176
+#: i2p2www/pages/site/docs/protocol/i2cp.html:185
+msgid "No limit"
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2cp.html:121
+msgid "Number of tunnels out"
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2cp.html:130
+msgid "Length of tunnels in"
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2cp.html:139
+msgid "Length of tunnels out"
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2cp.html:148
+msgid ""
+"Random amount to add or subtract to the length of tunnels in.\n"
+"A positive number x means add a random amount from 0 to x inclusive.\n"
+"A negative number -x means add a random amount from -x to x inclusive.\n"
+"The router will limit the total length of the tunnel to 0 to 7 inclusive."
+"\n"
+"The default variance was 1 prior to release 0.7.6."
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2cp.html:163
+msgid ""
+"Random amount to add or subtract to the length of tunnels out.\n"
+"A positive number x means add a random amount from 0 to x inclusive.\n"
+"A negative number -x means add a random amount from -x to x inclusive.\n"
+"The router will limit the total length of the tunnel to 0 to 7 inclusive."
+"\n"
+"The default variance was 1 prior to release 0.7.6."
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2cp.html:178
+msgid "Number of redundant fail-over for tunnels in"
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2cp.html:187
+msgid "Number of redundant fail-over for tunnels out"
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2cp.html:196
+msgid ""
+"Name of tunnel - generally used in routerconsole, which will\n"
+"use the first few characters of the Base64 hash of the destination by "
+"default."
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2cp.html:208
+msgid "Name of tunnel - generally ignored unless inbound.nickname is unset."
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2cp.html:217
+msgid "If incoming zero hop tunnel is allowed"
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2cp.html:226
+msgid "If outgoing zero hop tunnel is allowed"
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2cp.html:235
+#: i2p2www/pages/site/docs/protocol/i2cp.html:247
+msgid ""
+"Number of IP bytes to match to determine if\n"
+"two routers should not be in the same tunnel. 0 to disable."
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2cp.html:259
+msgid ""
+"Priority adjustment for outbound messages.\n"
+"Higher is higher priority."
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2cp.html:271
+msgid "Should generally be set to true for clients and false for servers"
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2cp.html:280
+msgid ""
+"Guaranteed is disabled;\n"
+"None implemented in 0.8.1; the streaming lib default is None as of 0.8.1,"
+" the client side default is None as of 0.9.4"
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2cp.html:292
+#: i2p2www/pages/site/docs/protocol/i2cp.html:571
+msgid ""
+"If true, the router just sends the MessagePayload instead\n"
+"of sending a MessageStatus and awaiting a ReceiveMessageBegin."
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2cp.html:304
+msgid ""
+"Comma-separated list of Base 64 Hashes of peers to build tunnels through;"
+" for debugging only"
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2cp.html:313
+#: i2p2www/pages/site/docs/protocol/i2cp.html:325
+msgid ""
+"For authorization, if required by the router.\n"
+"If the client is running in the same JVM as a router, this option is not "
+"required."
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2cp.html:337
+msgid ""
+"Number of ElGamal/AES Session Tags to send at a time.\n"
+"For clients with relatively low bandwidth per-client-pair (IRC, some UDP "
+"apps), this may be set lower."
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2cp.html:349
+msgid ""
+"Minimum number of ElGamal/AES Session Tags before we send more.\n"
+"Recommended: approximately tagsToSend * 2/3"
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2cp.html:361
+msgid ""
+"Set to false to disable ever bundling a reply LeaseSet.\n"
+"For clients that do not publish their LeaseSet, this option must be true\n"
+"for any reply to be possible. \"true\" is also recommended for multihomed"
+" servers\n"
+"with long connection times."
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2cp.html:368
+msgid ""
+"Setting to \"false\" may save significant outbound bandwidth, especially "
+"if\n"
+"the client is configured with a large number of inbound tunnels (Leases)."
+"\n"
+"If replies are still required, this may shift the bandwidth burden to\n"
+"the far-end client and the floodfill.\n"
+"There are several cases where \"false\" may be appropriate:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2cp.html:376
+msgid "Unidirectional communication, no reply required"
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2cp.html:377
+msgid "LeaseSet is published and higher reply latency is acceptable"
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2cp.html:378
+msgid ""
+"LeaseSet is published, client is a \"server\", all connections are "
+"inbound\n"
+"so the connecting far-end destination obviously has the leaseset already."
+"\n"
+"Connections are either short, or it is acceptable for latency on a long-"
+"lived\n"
+"connection to temporarily increase while the other end re-fetches the "
+"LeaseSet\n"
+"after expiration.\n"
+"HTTP servers may fit these requirements."
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2cp.html:396
+msgid ""
+"Any other options prefixed with \"inbound.\" are stored\n"
+"in the \"unknown options\" properties of the inbound tunnel pool's "
+"settings."
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2cp.html:408
+msgid ""
+"Any other options prefixed with \"outbound.\" are stored\n"
+"in the \"unknown options\" properties of the outbound tunnel pool's "
+"settings."
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2cp.html:415
+msgid ""
+"Note: Large quantity, length, or variance settings may cause significant "
+"performance or reliability problems."
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2cp.html:419
+msgid ""
+"Note: As of release 0.7.7, option names and values must use UTF-8 "
+"encoding.\n"
+"This is primarily useful for nicknames.\n"
+"Prior to that release, options with multi-byte characters were corrupted."
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2cp.html:425
+msgid ""
+"The following options are interpreted on the client side,\n"
+"and will be interpreted if passed to the I2PSession via the "
+"I2PClient.createSession() call.\n"
+"The streaming lib should also pass these options through to I2CP.\n"
+"Other implementations may have different defaults."
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2cp.html:433
+msgid "Client-side Options"
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2cp.html:451
+msgid ""
+"Router hostname.\n"
+"If the client is running in the same JVM as a router, this option is "
+"ignored, and the client connects to that router internally."
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2cp.html:463
+msgid ""
+"Router I2CP port.\n"
+"If the client is running in the same JVM as a router, this option is "
+"ignored, and the client connects to that router internally."
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2cp.html:475
+msgid ""
+"Connect to the router using SSL.\n"
+"If the client is running in the same JVM as a router, this option is "
+"ignored, and the client connects to that router internally."
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2cp.html:487
+msgid "Gzip outbound data"
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2cp.html:496
+msgid "Reduce tunnel quantity when idle"
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2cp.html:505
+msgid "Close I2P session when idle"
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2cp.html:512
+#: i2p2www/pages/site/docs/protocol/i2cp.html:521
+#, python-format
+msgid "%(num)s minimum"
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2cp.html:514
+msgid "(ms) Idle time required (default 20 minutes, minimum 5 minutes)"
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2cp.html:523
+msgid "(ms) Idle time required (default 30 minutes)"
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2cp.html:532
+msgid "Tunnel quantity when reduced (applies to both inbound and outbound)"
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2cp.html:541
+msgid "Encrypt the lease"
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2cp.html:550
+msgid "Base64 SessionKey (44 characters)"
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2cp.html:559
+msgid ""
+"Guaranteed is disabled;\n"
+"None implemented in 0.8.1; None is the default as of 0.9.4"
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2cp.html:578
+msgid ""
+"Note: All arguments, including numbers, are strings. True/false values "
+"are case-insensitive strings.\n"
+"Anything other than case-insensitive \"true\" is interpreted as false.\n"
+"All option names are case-sensitive."
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2cp.html:584
+msgid "I2CP Payload Data Format and Multiplexing"
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2cp.html:585
+#, python-format
+msgid ""
+"The end-to-end messages handled by I2CP (i.e. the data sent by the client"
+" in a\n"
+"SendMessageMessage\n"
+"and received by the client in a\n"
+"MessagePayloadMessage)\n"
+"are gzipped with a standard 10-byte gzip\n"
+"header beginning with 0x1F 0x8B 0x08 as\n"
+"specified by RFC "
+"1952.\n"
+"As of release 0.7.1, I2P uses ignored portions of the gzip header to "
+"include\n"
+"protocol, from-port, and to-port information, thus supporting streaming "
+"and\n"
+"datagrams on the same destination, and allowing query/response using "
+"datagrams\n"
+"to work reliably in the presence of multiple channels."
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2cp.html:599
+msgid ""
+"The gzip function cannot be completely turned off, however setting "
+"i2cp.gzip=false\n"
+"turns the gzip effort setting to 0, which may save a little CPU."
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2cp.html:605
+#: i2p2www/pages/site/docs/protocol/i2np.html:33
+msgid "Bytes"
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2cp.html:606
+msgid "Content"
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2cp.html:611
+msgid "Gzip header"
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2cp.html:616
+msgid "Gzip flags"
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2cp.html:621
+msgid "I2P Source port (Gzip mtime)"
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2cp.html:626
+msgid "I2P Destination port (Gzip mtime)"
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2cp.html:631
+msgid "Gzip xflags"
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2cp.html:636
+msgid "I2P Protocol (6 = Streaming, 17 = Datagram, 18 = Raw Datagrams) (Gzip OS)"
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2cp.html:640
+msgid ""
+"Data integrity is verified with the standard gzip CRC-32 as\n"
+"specified by RFC 1952."
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2cp.html:648
+msgid "Implement I2CP and the streaming library in another programming language."
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2cp.html:652
+msgid "Is the initial Get Date / Set Date handshake required?"
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2cp.html:656
+msgid ""
+"The current authorization mechanism could be modified to use hashed "
+"passwords."
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2cp.html:660
+msgid ""
+"Private Keys are included in the Create Lease Set message,\n"
+"are they really required? Revocation is unimplemented."
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2cp.html:665
+#, python-format
+msgid ""
+"Some improvements may be able to use messages previously defined but not "
+"implemented.\n"
+"For reference, here is the\n"
+"I2CP Protocol Specification Version 0.9\n"
+"(PDF) dated August 28, 2003.\n"
+"That document also references the\n"
+"Common Data Structures Specification Version 0.9."
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2np.html:3
+msgid "June 2013"
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2np.html:6
+msgid "I2P Network Protocol"
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2np.html:7
+msgid ""
+"The I2P Network Protocol (I2NP),\n"
+"which is sandwiched between I2CP and the various I2P transport protocols,"
+" manages the\n"
+"routing and mixing of messages between routers, as well as the selection "
+"of what\n"
+"transports to use when communicating with a peer for which there are "
+"multiple\n"
+"common transports supported."
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2np.html:15
+msgid "I2NP Definition"
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2np.html:16
+msgid ""
+"I2NP (I2P Network Protocol) messages can be used for one-hop, router-to-"
+"router, point-to-point messages.\n"
+"By encrypting and wrapping messages in other messages, they can be sent "
+"in a secure way\n"
+"through multiple hops to the ultimate destination.\n"
+"Priority is only used locally at the origin, i.e. when queuing for "
+"outbound delivery."
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2np.html:23
+#, python-format
+msgid ""
+"The priorities listed below may not be current and are subject to change."
+"\n"
+"See the OutNetMessage Javadocs\n"
+"for the current priority settings.\n"
+"Priority queueing implementation may vary."
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2np.html:30
+msgid "Message Format"
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2np.html:33
+#: i2p2www/pages/site/docs/spec/streaming.html:35
+msgid "Field"
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2np.html:34
+msgid "Unique ID"
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2np.html:35
+msgid "Expiration"
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2np.html:36
+#: i2p2www/pages/site/docs/protocol/i2np.html:93
+msgid "Payload Length"
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2np.html:37
+msgid "Checksum"
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2np.html:38
+msgid "Payload"
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2np.html:41
+#, python-format
+msgid ""
+"While the maximum payload size is nominally 64KB, the size is further "
+"constrained by the\n"
+"method of fragmenting I2NP messages into multiple 1KB tunnel messages as "
+"described on\n"
+"the tunnel implementation page.\n"
+"The maximum number of fragments is 64, and the message may not be "
+"perfectly aligned,\n"
+"So the message must nominally fit in 63 fragments."
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2np.html:49
+msgid ""
+"The maximum size of an initial fragment is 956 bytes (assuming TUNNEL "
+"delivery mode);\n"
+"the maximum size of a follow-on fragment is 996 bytes.\n"
+"Therefore the maximum size is approximately 956 + (62 * 996) = 62708 "
+"bytes, or 61.2 KB."
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2np.html:55
+msgid ""
+"In addition, the transports may have additional restrictions.\n"
+"NTCP currently limits to 16KB - 6 = 16378 bytes but this will be "
+"increased in a future release.\n"
+"The SSU limit is approximately 32 KB."
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2np.html:61
+msgid ""
+"Note that these are not the limits for datagrams that the client sees, as"
+" the\n"
+"router may bundle a reply leaseset and/or session tags together with the "
+"client message\n"
+"in a garlic message. The leaseset and tags together may add about 5.5KB.\n"
+"Therefore the current datagram limit is about 10KB. This limit will be\n"
+"increased in a future release."
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2np.html:69
+msgid "Message Types"
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2np.html:70
+msgid ""
+"Higher-numbered priority is higher priority.\n"
+"The majority of traffic is TunnelDataMessages (priority 400),\n"
+"so anything above 400 is essentially high priority, and\n"
+"anything below is low priority.\n"
+"Note also that many of the messages are generally routed\n"
+"through exploratory tunnels, not client tunnels, and\n"
+"therefore may not be in the same queue unless the\n"
+"first hops happen to be on the same peer."
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2np.html:81
+msgid ""
+"Also, not all message types are sent unencrypted.\n"
+"For example, when testing a tunnel, the router wraps a\n"
+"DeliveryStatusMessage, which is wrapped in a GarlicMessage,\n"
+"which is wrapped in a DataMessage."
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2np.html:91
+msgid "Message"
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2np.html:92
+msgid "Type"
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2np.html:95
+msgid "Comments"
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2np.html:103
+msgid "May vary"
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2np.html:109
+msgid ""
+"Size is 65 + 32*(number of hashes) where typically, the hashes for\n"
+"three floodfill routers are returned."
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2np.html:118
+msgid "Varies"
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2np.html:120
+msgid ""
+"Priority may vary.\n"
+"Size is 898 bytes for a typical 2-lease leaseSet.\n"
+"RouterInfo structures are compressed, and size varies; however\n"
+"there is a continuing effort to reduce the amount of data published in a "
+"RouterInfo\n"
+"as we approach release 1.0."
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2np.html:134
+msgid "Priority may vary on a per-destination basis"
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2np.html:144
+msgid ""
+"Used for message replies, and for testing tunnels - generally wrapped in "
+"a GarlicMessage"
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2np.html:152
+msgid ""
+"Generally wrapped in a DataMessage -\n"
+"but when unwrapped, given a priority of 100 by the forwarding router"
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2np.html:179
+msgid ""
+"The most common message. Priority for tunnel participants, outbound "
+"endpoints, and inbound gateways was\n"
+"reduced to 200 as of release 0.6.1.33.\n"
+"Outbound gateway messages (i.e. those originated locally) remains at 400."
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2np.html:199
+msgid "Shorter TunnelBuildMessage as of 0.7.12"
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2np.html:207
+msgid "Shorter TunnelBuildReplyMessage as of 0.7.12"
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2np.html:210
+#, python-format
+msgid "Others listed in 2003 Spec"
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2np.html:216
+msgid "Obsolete, Unused"
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2np.html:220
+msgid "Full Protocol Specification"
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2np.html:221
+#, python-format
+msgid ""
+"On the I2NP Specification page.\n"
+"See also the\n"
+"Common Data Structure Specification "
+"page."
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2np.html:228
+msgid ""
+"It isn't clear whether the current priority scheme is generally "
+"effective,\n"
+"and whether the priorities for various messages should be adjusted "
+"further.\n"
+"This is a topic for further research, analysis and testing."
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/index.html:2
+msgid "Protocol Stack"
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/index.html:7
+#, python-format
+msgid ""
+"Here is the protocol stack for I2P.\n"
+"See also the Index to Technical Documentation."
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/index.html:12
+msgid ""
+"Each of the layers in the stack provides extra capabilities.\n"
+"The capabilities are listed below, starting at the bottom of the protocol"
+" stack."
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/index.html:18
+msgid "Internet Layer:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/index.html:20
+msgid ""
+"IP: Internet Protocol, allow addressing hosts on the regular internet and"
+" routing packets across the internet using best-effort delivery."
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/index.html:23
+msgid "Transport Layer:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/index.html:25
+msgid ""
+"TCP: Transmission Control Protocol, allow reliable, in-order delivery of "
+"packets across the internet."
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/index.html:27
+msgid ""
+"UDP: User Datagram Protocol, allow unreliable, out-of-order delivery of "
+"packets across the internet."
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/index.html:30
+msgid ""
+"I2P Transport Layer: provide encrypted connections between 2 I2P "
+"routers. These are not anonymous yet, this is strictly a hop-to-hop "
+"connection.\n"
+"Two protocols are implemented to provide these capabilities. NTCP builds "
+"on top of TCP, while SSU uses UDP."
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/index.html:35
+msgid "NIO-based TCP"
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/index.html:37
+msgid "Secure Semi-reliable UDP"
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/index.html:40
+msgid "I2P Tunnel Layer: provide full encrypted tunnel connections."
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/index.html:42
+#, python-format
+msgid ""
+"Tunnel messages: tunnel messages are "
+"large messages containing encrypted I2NP (see below) messages and "
+"encrypted instructions for their delivery.\n"
+"The encryption is layered. The first hop will decrypt the tunnel message "
+"and read a part. Another part can still be encrypted (with another key),"
+"\n"
+"so it will be forwarded."
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/index.html:48
+#, python-format
+msgid ""
+"I2NP messages: I2P Network Protocol messages are"
+" used to pass messages through multiple routers. These I2NP messages are "
+"combined in tunnel messages."
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/index.html:53
+msgid ""
+"I2P Garlic Layer: provide encrypted and anonymous end-to-end I2P "
+"message delivery."
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/index.html:55
+#, python-format
+msgid ""
+"I2NP messages: I2P Network Protocol messages are"
+" wrapped in each other and used to ensure encryption between two tunnels "
+"and are passed along from source to destination, keeping both anonymous."
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/index.html:61
+msgid ""
+"The following layers are strictly speaking no longer part of the I2P "
+"Protocol stack, they are not part of the core 'I2P router' functionality."
+"\n"
+"However, each of these layers adds additional functionality, to allow "
+"applications simple and convenient I2P usage."
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/index.html:67
+msgid ""
+"I2P Client Layer: allow any client to use I2P functionality, "
+"without requiring the direct use of the router API."
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/index.html:69
+#, python-format
+msgid ""
+"I2CP: I2P Client Protocol, allows secure and "
+"asynchronous messaging over I2P by communicating messages over the I2CP "
+"TCP socket."
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/index.html:74
+msgid ""
+"I2P End-to-end Transport Layer: allow TCP- or UDP-like "
+"functionality on top of I2P."
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/index.html:76
+#, python-format
+msgid ""
+"Streaming Library: an implementation of "
+"TCP-like streams over I2P. This allows easier porting of existing "
+"applications to I2P."
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/index.html:80
+#, python-format
+msgid ""
+"Datagram Library: an implementation of UDP-"
+"like messages over I2P. This allows easier porting of existing "
+"applications to I2P."
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/index.html:85
+msgid ""
+"I2P Application Interface Layer: additional (optional) libraries "
+"allowing easier implementations on top of I2P."
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/index.html:93
+msgid "I2P Application Proxy Layer: proxy systems."
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/index.html:95
+#, python-format
+msgid "HTTP Client/Server, IRC Client, SOCKS, Streamr"
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/index.html:99
+msgid ""
+"Finally, what could be considered the 'I2P application layer', is "
+"a large number of applications on top of I2P.\n"
+"We can order this based on the I2P stack layer they use."
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/index.html:104
+msgid "Streaming/datagram applications: i2psnark, Syndie, i2phex..."
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/index.html:105
+msgid "SAM/BOB applications: IMule, i2p-bt, i2prufus, Robert..."
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/index.html:106
+#, python-format
+msgid ""
+"Other I2P applications: Syndie, EepGet, plugins..."
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/index.html:107
+msgid ""
+"Regular applications: Jetty, Apache, Monotone, CVS, browsers, "
+"e-mail..."
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/index.html:111
+msgid "I2P Network stack"
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/index.html:113
+msgid "Figure 1: The layers in the I2P Network stack."
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/index.html:118
+msgid "Note: SAM/SAMv2 can use both the streaming lib and datagrams."
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/blockfile.html:2
+msgid "I2P Blockfile Specification"
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/blockfile.html:3
+msgid "January 2012"
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/blockfile.html:6
+msgid "Blockfile and Hosts Database Specification"
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/blockfile.html:8
+#, python-format
+msgid ""
+"This document specifies\n"
+"the I2P blockfile file format\n"
+"and the tables in the hostsdb.blockfile used by the Blockfile Naming Service."
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/blockfile.html:14
+msgid ""
+"The blockfile provides fast Destination lookup in a compact format. While"
+" the blockfile page overhead is substantial,\n"
+"the destinations are stored in binary rather than in Base 64 as in the "
+"hosts.txt format.\n"
+"In addition, the blockfile provides the capability of arbitrary metadata "
+"storage\n"
+"(such as added date, source, and comments) for each entry.\n"
+"The metadata may be used in the future to provide advanced addressbook "
+"features.\n"
+"The blockfile storage requirement is a modest increase over the hosts.txt"
+" format, and the blockfile provides\n"
+"approximately 10x reduction in lookup times."
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/blockfile.html:24
+#, python-format
+msgid ""
+"A blockfile is simply on-disk storage of multiple sorted maps (key-value "
+"pairs),\n"
+"implemented as skiplists.\n"
+"The blockfile format is adopted from the\n"
+"Metanotion Blockfile Database.\n"
+"First we will define the file format, then the use of that format by the "
+"BlockfileNamingService."
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/blockfile.html:32
+msgid "Blockfile Format"
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/blockfile.html:33
+msgid ""
+"The original blockfile spec was modified to add magic numbers to each "
+"page.\n"
+"The file is structured in 1024-byte pages. Pages are numbered starting "
+"from 1.\n"
+"The \"superblock\" is always at page 1, i.e. starting at byte 0 in the "
+"file.\n"
+"The metaindex skiplist is always at page 2, i.e. starting at byte 1024 in"
+" the file."
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/blockfile.html:40
+msgid ""
+"All 2-byte integer values are unsigned.\n"
+"All 4-byte integer values (page numbers) are signed and negative values "
+"are illegal."
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/blockfile.html:45
+msgid ""
+"The database is designed to be opened and accessed by a single thread.\n"
+"The BlockfileNamingService provides synchronization."
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/blockfile.html:50
+msgid "Superblock format:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/blockfile.html:65
+msgid "Skip list block page format:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/blockfile.html:80
+msgid ""
+"Skip level block page format is as follows.\n"
+"All levels have a span. Not all spans have levels."
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/blockfile.html:95
+msgid ""
+"Skip span block page format is as follows.\n"
+"Key/value structures are sorted by key within each span and across all "
+"spans.\n"
+"Key/value structures are sorted by key within each span.\n"
+"Spans other than the first span may not be empty."
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/blockfile.html:112
+msgid "Span Continuation block page format:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/blockfile.html:123
+msgid ""
+"Key/value structure format is as follows.\n"
+"Key and value lengths must not be split across pages, i.e. all 4 bytes "
+"must be on the same page.\n"
+"If there is not enough room the last 1-3 bytes of a page are unused and "
+"the lengths will\n"
+"be at offset 8 in the continuation page.\n"
+"Key and value data may be split across pages.\n"
+"Max key and value lengths are 65535 bytes."
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/blockfile.html:139
+msgid "Free list block page format:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/blockfile.html:151
+msgid "Free page block format:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/blockfile.html:160
+msgid ""
+"The metaindex (located at page 2) is a mapping of US-ASCII strings to "
+"4-byte integers.\n"
+"The key is the name of the skiplist and the value is the page index of "
+"the skiplist."
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/blockfile.html:165
+msgid "Blockfile Naming Service Tables"
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/blockfile.html:166
+msgid ""
+"The tables created and used by the BlockfileNamingService are as follows."
+"\n"
+"The maximum number of entries per span is 16."
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/blockfile.html:171
+msgid "Properties Skiplist"
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/blockfile.html:172
+#, python-format
+msgid ""
+"%(INFO)s is the master database skiplist with String/Properties key/value"
+" entries containing only one entry:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/blockfile.html:184
+msgid "Reverse Lookup Skiplist"
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/blockfile.html:185
+#, python-format
+msgid ""
+"%(REVERSE)s is the reverse lookup skiplist with Integer/Properties "
+"key/value entries\n"
+" (as of database version 2):"
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/blockfile.html:199
+msgid "hosts.txt, userhosts.txt, and privatehosts.txt Skiplists"
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/blockfile.html:200
+msgid ""
+"For each host database, there is a skiplist containing\n"
+"the hosts for that database.\n"
+"The keys/values in these skiplists are as follows:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/blockfile.html:211
+msgid "The DestEntry Properties typically contains:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/blockfile.html:220
+msgid "Hostname keys are stored in lower-case and always end in \".i2p\"."
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/common-structures.html:2
+msgid "Common structure Specification"
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/common-structures.html:6
+msgid "Data types Specification"
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/common-structures.html:7
+#, python-format
+msgid ""
+"This document describes some data types common to all I2P protocols, like"
+"\n"
+"I2NP, I2CP,\n"
+"SSU, etc."
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/common-structures.html:17
+msgid "Represents a non-negative integer.\n"
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/common-structures.html:20
+#: i2p2www/pages/site/docs/spec/common-structures.html:31
+#: i2p2www/pages/site/docs/spec/common-structures.html:41
+#: i2p2www/pages/site/docs/spec/common-structures.html:54
+#: i2p2www/pages/site/docs/spec/common-structures.html:69
+#: i2p2www/pages/site/docs/spec/common-structures.html:82
+#: i2p2www/pages/site/docs/spec/common-structures.html:94
+#: i2p2www/pages/site/docs/spec/common-structures.html:106
+#: i2p2www/pages/site/docs/spec/common-structures.html:118
+#: i2p2www/pages/site/docs/spec/common-structures.html:130
+#: i2p2www/pages/site/docs/spec/common-structures.html:142
+#: i2p2www/pages/site/docs/spec/common-structures.html:154
+#: i2p2www/pages/site/docs/spec/common-structures.html:166
+#: i2p2www/pages/site/docs/spec/common-structures.html:178
+#: i2p2www/pages/site/docs/spec/common-structures.html:231
+#: i2p2www/pages/site/docs/spec/common-structures.html:303
+#: i2p2www/pages/site/docs/spec/common-structures.html:352
+#: i2p2www/pages/site/docs/spec/common-structures.html:404
+#: i2p2www/pages/site/docs/spec/common-structures.html:451
+#: i2p2www/pages/site/docs/spec/common-structures.html:586
+#: i2p2www/pages/site/docs/spec/common-structures.html:643
+#: i2p2www/pages/site/docs/spec/streaming.html:35
+msgid "Contents"
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/common-structures.html:21
+msgid "1 to 8 bytes in network byte order representing an unsigned integer\n"
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/common-structures.html:27
+msgid ""
+"The number of milliseconds since midnight on January 1, 1970 in the GMT "
+"timezone.\n"
+"If the number is 0, the date is undefined or null.\n"
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/common-structures.html:32
+msgid "8 byte Integer\n"
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/common-structures.html:38
+msgid "Represents a UTF-8 encoded string.\n"
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/common-structures.html:42
+msgid ""
+"1 or more bytes where the first byte is the number of bytes (not "
+"characters!)\n"
+"in the string and the remaining 0-255 bytes are the non-null terminated "
+"UTF-8 encoded character array.\n"
+"Length limit is 255 bytes (not characters). Length may be 0.\n"
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/common-structures.html:50
+msgid ""
+"A boolean value, supporting null/unknown representation\n"
+"0=false, 1=true, 2=unknown/null\n"
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/common-structures.html:55
+msgid "1 byte Integer\n"
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/common-structures.html:59
+msgid "Deprecated - unused\n"
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/common-structures.html:65
+#, python-format
+msgid ""
+"This structure is used in ElGamal encryption, representing only the "
+"exponent, not the primes, which are constant and defined in\n"
+"the cryptography specification.\n"
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/common-structures.html:70
+#: i2p2www/pages/site/docs/spec/common-structures.html:83
+msgid "256 bytes\n"
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/common-structures.html:78
+#, python-format
+msgid ""
+"This structure is used in ElGamal decryption, representing only the "
+"exponent, not the primes which are constant and defined in\n"
+"the cryptography specification.\n"
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/common-structures.html:91
+msgid "This structure is used for AES256 encryption and decryption.\n"
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/common-structures.html:95
+#: i2p2www/pages/site/docs/spec/common-structures.html:143
+#: i2p2www/pages/site/docs/spec/common-structures.html:155
+msgid "32 bytes\n"
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/common-structures.html:103
+#, python-format
+msgid ""
+"This structure is used for verifying DSA signatures.\n"
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/common-structures.html:107
+msgid "128 bytes\n"
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/common-structures.html:115
+#, python-format
+msgid ""
+"This structure is used for creating DSA signatures.\n"
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/common-structures.html:119
+msgid "20 bytes\n"
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/common-structures.html:127
+#, python-format
+msgid ""
+"This structure represents the DSA "
+"signature of some data.\n"
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/common-structures.html:131
+msgid "40 bytes\n"
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/common-structures.html:139
+msgid "Represents the SHA256 of some data.\n"
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/common-structures.html:151
+msgid "A random number\n"
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/common-structures.html:163
+msgid "Defines an identifier that is unique to each router in a tunnel.\n"
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/common-structures.html:167
+msgid "4 byte Integer\n"
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/common-structures.html:175
+msgid ""
+"A certificate is a container for various receipts or proof of works used "
+"throughout the I2P network.\n"
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/common-structures.html:179
+msgid ""
+"1 byte Integer specifying certificate type,"
+" followed by a 2 Integer specifying the "
+"size of the certificate payload, then that many bytes.\n"
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/common-structures.html:205
+msgid ""
+"For Router Identities, the "
+"Certificate is always NULL, no others are currently implemented."
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/common-structures.html:209
+#, python-format
+msgid ""
+"For Garlic Cloves, the "
+"Certificate is always NULL, no others are currently implemented."
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/common-structures.html:213
+#, python-format
+msgid ""
+"For Garlic Messages, the Certificate "
+"is always NULL, no others are currently implemented."
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/common-structures.html:217
+msgid ""
+"For Destinations, the Certificate may"
+" be non-NULL,\n"
+"however non-NULL certs are not widely used, and any checking is left to "
+"the application-level."
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/common-structures.html:228
+msgid "A set of key/value mappings or properties\n"
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/common-structures.html:232
+msgid "A 2-byte size Integer followed by a series of String=String; pairs\n"
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/common-structures.html:259
+msgid ""
+"The encoding isn't optimal - we either need the '=' and ';' characters, "
+"or the string lengths, but not both"
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/common-structures.html:263
+msgid ""
+"Some documentation says that the strings may not include '=' or ';' but "
+"this encoding supports them"
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/common-structures.html:267
+msgid ""
+"Strings are defined to be UTF-8 but in the current implementation, I2CP "
+"uses UTF-8 but I2NP does not.\n"
+"For example,\n"
+"UTF-8 strings in a RouterInfo options mapping in a I2NP Database Store "
+"Message will be corrupted."
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/common-structures.html:273
+msgid ""
+"Mappings contained in I2NP messages (i.e. in a RouterAddress or "
+"RouterInfo)\n"
+"must be sorted by key so that the signature will be invariant."
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/common-structures.html:278
+#, python-format
+msgid ""
+"Mappings contained in an I2CP "
+"SessionConfig\n"
+"must be sorted by key so that the signature will be invariant."
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/common-structures.html:283
+msgid ""
+"Key and value string length limits are 255 bytes (not characters) each, "
+"plus the length byte. Length byte may be 0."
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/common-structures.html:287
+msgid ""
+"Total length limit is 65535 bytes, plus the 2 byte size field, or 65537 "
+"total."
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/common-structures.html:296
+msgid "Common structure specification"
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/common-structures.html:300
+msgid "Defines the way to uniquely identify a particular router\n"
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/common-structures.html:304
+msgid ""
+"PublicKey followed by SigningPublicKey and then a Certificate\n"
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/common-structures.html:341
+msgid ""
+"The certificate for a RouterIdentity is currently unused and is always "
+"NULL."
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/common-structures.html:349
+msgid ""
+"A Destination defines a particular endpoint to which messages can be "
+"directed for secure delivery.\n"
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/common-structures.html:353
+msgid ""
+"PublicKey followed by a SigningPublicKey and then a Certificate\n"
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/common-structures.html:401
+msgid ""
+"Defines the authorization for a particular tunnel to receive messages "
+"targeting a Destination.\n"
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/common-structures.html:405
+msgid ""
+"SHA256 Hash of the\n"
+"RouterIdentity of the gateway "
+"router, then the TunnelId, and finally an "
+"end Date\n"
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/common-structures.html:436
+msgid "Total size: 44 bytes"
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/common-structures.html:446
+msgid ""
+"Contains all of the currently authorized Leases for a particular Destination, the PublicKey to which garlic messages can be "
+"encrypted,\n"
+"and then the public key that can "
+"be used to revoke this particular version of the structure. The LeaseSet is one of the two structures "
+"stored in the network database(\n"
+"the other being RouterInfo), and is "
+"keyed under the SHA256 of the contained Destination.\n"
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/common-structures.html:452
+msgid ""
+"Destination, followed by a PublicKey for encryption, then a SigningPublicKey which can be used to"
+" revoke this version of the LeaseSet,\n"
+"then a 1 byte Integer specifying how many "
+"Lease structures are in the set, followed "
+"by the actual Lease structures and finally "
+"a Signature of the previous\n"
+"bytes signed by the Destination's SigningPrivateKey"
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/common-structures.html:544
+msgid ""
+"The public key of the destination was used for the old i2cp-to-i2cp "
+"encryption\n"
+"which was disabled in version 0.6, it is currently unused."
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/common-structures.html:549
+#, python-format
+msgid ""
+"The encryption key is used for end-to-end ElGamal/AES+SessionTag encryption.\n"
+"It is currently generated anew at every router startup, it is not "
+"persistent."
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/common-structures.html:554
+msgid ""
+"The signature may be verified using the signing public key of the "
+"destination."
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/common-structures.html:558
+msgid ""
+"The signing_key is currently unused. It was intended for LeaseSet "
+"revocation, which is unimplemented.\n"
+"It is currently generated anew at every router startup, it is not "
+"persistent."
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/common-structures.html:562
+msgid ""
+"The earliest expiration of all the Leases is treated as the timestamp or "
+"version of the LeaseSet.\n"
+"Routers will generally not accept a store of a LeaseSet unless it is "
+"\"newer\" than the current one.\n"
+"Take care when publishing a new LeaseSet where the oldest Lease is the "
+"same as the oldest Lease\n"
+"in the previous LeaseSet. The publishing router should generally "
+"increment the expiration\n"
+"of the oldest Lease by at least 1 ms in that case."
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/common-structures.html:569
+msgid ""
+"Prior to release 0.9.7, when included in a DatabaseStore Message sent by "
+"the originating router,\n"
+"the router set all the published leases' expirations to the same value, "
+"that of the\n"
+"earliest lease. As of release 0.9.7, the router publishes the actual "
+"lease expiration for each lease.\n"
+"This is an implementation detail and not part of the structures "
+"specification."
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/common-structures.html:583
+msgid ""
+"This structure defines the means to contact a router through a transport "
+"protocol.\n"
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/common-structures.html:587
+msgid ""
+"1 byte Integer defining the relative cost "
+"of using the address, where 0 is free and 255 is expensive, followed by "
+"the expiration Date after which the address "
+"should not be used, or if null, the address never expires.\n"
+"After that comes a String defining the "
+"transport protocol this router address uses. Finally there is a Mapping containing all of the transport "
+"specific options necessary to establish the connection, such as\n"
+"IP address, port number, email address, URL, etc.\n"
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/common-structures.html:622
+msgid "Cost is typically 5 or 6 for SSU, and 10 or 11 for NTCP."
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/common-structures.html:626
+msgid ""
+"Expiration is currently unused, always null (all zeroes)).\n"
+"As of release 0.9.3, the expiration is assumed zero and not stored, so "
+"any non-zero expiration\n"
+"will fail in the RouterInfo signature verification.\n"
+"Implementing expiration (or another use for these bytes) will be a "
+"backwards-incompatible change."
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/common-structures.html:639
+msgid ""
+"Defines all of the data that a router wants to publish for the network to"
+" see. The RouterInfo is one of two "
+"structures stored in the network database(the other being LeaseSet, and is keyed under the SHA256 of"
+"\n"
+"the contained RouterIdentity.\n"
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/common-structures.html:644
+msgid ""
+"RouterIdentity followed by the Date, when the entry was published\n"
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/common-structures.html:723
+msgid ""
+"The peer_size Integer may be followed by a list of that many router "
+"hashes.\n"
+"This is currently unused. It was intended for a form of restricted "
+"routes, which is unimplemented.\n"
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/common-structures.html:728
+msgid ""
+"The signature may be verified using the signing public key of the "
+"router_ident.\n"
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/common-structures.html:736
+#, python-format
+msgid ""
+"Defined in the Tunnel Message "
+"Specification.\n"
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/configuration.html:2
+msgid "Configuration File Specification"
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/configuration.html:7
+msgid ""
+"This page provides a general specification of I2P configuration files,\n"
+"used by the router and various applications.\n"
+"It also gives an overview of the information contained in the various "
+"files,\n"
+"and links to detailed documentation where available."
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/configuration.html:15
+msgid "General Format"
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/configuration.html:16
+#, python-format
+msgid ""
+"An I2P configuration file is formatted as specified in\n"
+"Java Properties\n"
+"with the following exceptions:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/configuration.html:22
+msgid "Encoding must be UTF-8"
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/configuration.html:23
+msgid ""
+"Does not use or recognize any escapes, including '\\', so lines may not "
+"be continued"
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/configuration.html:24
+msgid "'#' or ';' starts a comment, but '!' does not"
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/configuration.html:25
+msgid ""
+"'#' starts a comment in any position but ';' must be in column 1 to start"
+" a comment"
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/configuration.html:26
+msgid "Leading and trailing whitespace is not trimmed on keys"
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/configuration.html:27
+msgid "Leading and trailing whitespace is trimmed on values"
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/configuration.html:28
+msgid "'=' is the only key-termination character (not ':' or whitespace)"
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/configuration.html:29
+msgid ""
+"Lines without '=' are ignored. It does not store the key with a value of "
+"\"\""
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/configuration.html:30
+msgid ""
+"As there are no escapes, keys may not contain '#', '=', or '\n"
+"', or start with ';'"
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/configuration.html:31
+msgid ""
+"As there are no escapes, values may not contain '#' or '\n"
+"', or start or end with '\r"
+"' or whitespace"
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/configuration.html:34
+msgid ""
+"The file need not be sorted, but most applications do sort by key when\n"
+"writing to the file, for ease of reading and manual editing."
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/configuration.html:39
+#, python-format
+msgid ""
+"Reads and writes are implemented in\n"
+"DataHelper loadProps() and storeProps().\n"
+"Note that the file format is significantly different than the\n"
+"serialized format for I2P protocols specified in\n"
+"Mapping."
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/configuration.html:48
+msgid "Core library and router"
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/configuration.html:50
+msgid "Clients"
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/configuration.html:51
+msgid "Configured via /configclients in the router console."
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/configuration.html:55
+msgid "Logger"
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/configuration.html:56
+msgid "Configured via /configlogging in the router console."
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/configuration.html:60
+msgid "Individual Plugin"
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/configuration.html:61
+#, python-format
+msgid "See the plugin specification."
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/configuration.html:66
+msgid "Enable/disable for each installed plugin."
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/configuration.html:70
+msgid "Router"
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/configuration.html:71
+msgid "Configured via /configadvanced in the router console."
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/configuration.html:75
+msgid "Applications"
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/configuration.html:78
+msgid "See documentation in SusiDNS."
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/configuration.html:83
+msgid "Configured via the application gui."
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/configuration.html:88
+msgid "Configured via the /i2ptunnel application in the router console."
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/configuration.html:92
+msgid "Router Console"
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/configuration.html:93
+msgid "The router console uses the router.config file."
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/configuration.html:98
+msgid "See post on zzz.i2p."
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/datagrams.html:2
+msgid "Datagram Specification"
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/datagrams.html:6
+msgid "See the Datagrams page for an overview of the Datagrams API."
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/datagrams.html:12
+msgid "Non-Repliable Datagrams"
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/datagrams.html:13
+msgid ""
+"Non-repliable datagrams have no 'from' address and are not authenticated."
+"\n"
+"They are also called \"raw\" datagrams.\n"
+"Strictly speaking, they are not \"datagrams\" at all, they are just raw "
+"data.\n"
+"They are not handled by the datagram API.\n"
+"However, SAM and the I2PTunnel classes support \"raw datagrams\"."
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/datagrams.html:21
+msgid "Format"
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/datagrams.html:31
+#, python-format
+msgid ""
+"The practical length is limited by lower layers of protocols - the\n"
+"tunnel message spec\n"
+"limits messages to about 61.2 KB and the\n"
+"transports\n"
+"currently limit messages to about 32 KB, although this may be raised in "
+"the future."
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/datagrams.html:40
+msgid "Repliable Datagrams"
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/datagrams.html:41
+msgid ""
+"Repliable datagrams contain a 'from' address and a signature. These add "
+"427 bytes of overhead."
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/datagrams.html:91
+#, python-format
+msgid ""
+"The practical length is limited by lower layers of protocols - the\n"
+"transports\n"
+"currently limit messages to about 32 KB, so the data length here is "
+"limited to about\n"
+"31.5 KB."
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/datagrams.html:97
+msgid "See important notes above about the reliability of large datagrams."
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/geoip.html:2
+msgid "GeoIP File Specification"
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/geoip.html:8
+msgid ""
+"This page specifies the format of the various GeoIP files,\n"
+"used by the router to look up a country for an IP."
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/geoip.html:14
+msgid "Country Name (countries.txt) Format"
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/geoip.html:15
+msgid ""
+"This format is easily generated from data files available from many "
+"public sources.\n"
+"For example:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/geoip.html:33
+msgid "IPv4 (geoip.txt) Format"
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/geoip.html:34
+msgid ""
+"This format is borrowed from Tor and is easily generated from data files "
+"available from many public sources.\n"
+"For example:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/geoip.html:54
+msgid "IPv6 (geoipv6.dat.gz) Format"
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/geoip.html:55
+msgid ""
+"This is a compressed binary format designed for I2P.\n"
+"The file is gzipped. Ungzipped format:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/geoip.html:71
+msgid "NOTES:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/streaming.html:2
+msgid "Streaming Library Specification"
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/streaming.html:6
+msgid "See the Streaming page for an overview of the Streaming Library."
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/streaming.html:11
+msgid "Packet Format"
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/streaming.html:12
+msgid "The format of a single packet in the streaming protocol is:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/streaming.html:35
+msgid "Length"
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/streaming.html:83
+msgid "Flags and Option Data Fields"
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/streaming.html:84
+msgid ""
+"The flags field above specifies some metadata about the packet, and in\n"
+"turn may require certain additional data to be included. The flags are\n"
+"as follows. Any data structures specified must be added to the options "
+"area\n"
+"in the given order."
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/updates.html:2
+msgid "I2P Software Update Specification"
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/updates.html:7
+msgid ""
+"I2P uses a simple, yet secure, system for automated software update.\n"
+"The router console periodically pulls a news file from a configurable I2P"
+" URL.\n"
+"There is a hardcoded backup URL pointing to the project website, in case\n"
+"the default project news host goes down."
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/updates.html:14
+msgid ""
+"The contents of the news file are displayed on the home page of the "
+"router console.\n"
+"In addition, the news file contains the most recent version number of the"
+" software.\n"
+"If the version is higher than the router's version number, it will\n"
+"display an indication to the user that an update is available."
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/updates.html:21
+msgid ""
+"The router may optionally download, or download and install, the new "
+"version\n"
+"if configured to do so."
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/updates.html:26
+msgid "News File Specification"
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/updates.html:27
+msgid "The news.xml file may contain the following elements:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/updates.html:35
+msgid ""
+"Parameters in the i2p.release entry are as follows.\n"
+"All keys are case-insensitive. All values must be enclosed in double "
+"quotes."
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/updates.html:73
+msgid ""
+"The elements may be included inside XML comments to prevent "
+"interpretation by browsers.\n"
+"The i2p.release element and version are required. All others are "
+"optional.\n"
+"NOTE: Due to parser limitations an entire element must be on a single "
+"line."
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/updates.html:80
+msgid "Update File Specification"
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/updates.html:81
+msgid ""
+"As of release 0.9.9, the signed update file, named i2pupdate.su3, will\n"
+"use the \"su3\" file format specified below.\n"
+"Approved release signers will use 4096-bit RSA keys.\n"
+"The X.509 public key certificates for these signers are distributed in "
+"the router installation packages.\n"
+"The updates may contain certificates for new, approved signers, and/or "
+"contain\n"
+"a list of certificates to delete for revocation."
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/updates.html:91
+msgid "Old Update File Specification"
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/updates.html:92
+msgid "This format is obsolte as of release 0.9.9."
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/updates.html:95
+msgid ""
+"The signed update file, traditionally named i2pupdate.sud,\n"
+"is simply a zip file with a prepended 56 byte header.\n"
+"The header contains:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/updates.html:101
+#, python-format
+msgid ""
+"A 40-byte DSA "
+"signature"
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/updates.html:104
+msgid "A 16-byte I2P version in UTF-8, padded with trailing zeroes if necessary"
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/updates.html:109
+#, python-format
+msgid ""
+"The signature covers only the zip archive - not the prepended version.\n"
+"The signature must match one of the DSA public keys "
+"configured into the router,\n"
+"which has a hardcoded default list of keys of the current project release"
+" managers."
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/updates.html:115
+msgid ""
+"For version comparison purposes, version fields contain [0-9]*, field "
+"separators are\n"
+"'-', '_', and '.', and all other characters are ignored."
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/updates.html:120
+msgid ""
+"As of version 0.8.8, the version must also be specified as a zip file "
+"comment in UTF-8,\n"
+"without the trailing zeroes.\n"
+"The updating router verifes that the version in the header (not covered "
+"by the signature)\n"
+"matches the version in the zip file comment, which is covered by the "
+"signature.\n"
+"This prevents spoofing of the version number in the header."
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/updates.html:128
+msgid "Download and Installation"
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/updates.html:129
+msgid ""
+"The router first downloads the header of the update file from one in a "
+"configurable list of I2P URLs,\n"
+"using the built-in HTTP client and proxy,\n"
+"and checks that the version is newer.\n"
+"This prevents the problem of update hosts that do not have the latest "
+"file.\n"
+"The router then downloads the full update file.\n"
+"The router verifies that the update file version is newer before "
+"installation.\n"
+"It also, of course, verifies the signature, and\n"
+"verifes that the zip file comment matches the header version, as "
+"explained above."
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/updates.html:140
+msgid "The zip file is extracted in the base $I2P installation directory."
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/updates.html:144
+msgid ""
+"As of release 0.7.12, the router supports Pack200 decompression.\n"
+"Files inside the zip archive with a .jar.pack or .war.pack suffix\n"
+"are transparently decompressed to a .jar or .war file.\n"
+"Update files containing .pack files are traditionally named with a '.su2'"
+" suffix.\n"
+"Pack200 shrinks the update files by about 60%."
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/updates.html:152
+msgid ""
+"As of release 0.8.7, the router will delete the libjbigi.so and "
+"libjcpuid.so files\n"
+"if the zip archive contains a lib/jbigi.jar file, so that the new files "
+"will\n"
+"be extracted from jbigi.jar."
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/updates.html:158
+msgid ""
+"As of release 0.8.12, if the zip archive contains a file deletelist.txt, "
+"the router will\n"
+"delete the files listed there. The format is:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/updates.html:163
+msgid "One file name per line"
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/updates.html:164
+msgid ""
+"All file names are relative to the installation directory; no absolute "
+"file names allowed, no files starting with \"..\""
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/updates.html:165
+msgid "Comments start with '#'"
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/updates.html:168
+msgid "The router will then delete the deletelist.txt file."
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/updates.html:173
+msgid "New \"su3\" Update File Specification"
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/updates.html:175
+msgid ""
+"This specification is used for router updates and reseed data as of "
+"release 0.9.9."
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/updates.html:179
+msgid "Issues with the previous .sud/.su2 format:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/updates.html:181
+msgid "No magic number or flags"
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/updates.html:184
+msgid "No way to specify compression, pack200 or not, or signing algo"
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/updates.html:187
+msgid ""
+"Version is not covered by signature, so it is enforced by requiring it\n"
+"to be in the zip file comment (for router files) or in the plugin.config\n"
+"file (for plugins)"
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/updates.html:192
+msgid "Signer not specified so verifier must try all known keys"
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/updates.html:195
+msgid "Signature-before-data format requires two passes to generate file"
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/updates.html:201
+msgid "Goals:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/updates.html:204
+msgid "Fix above problems"
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/updates.html:207
+msgid "Migrate to more secure signature algorithm"
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/updates.html:210
+msgid ""
+"Keep version info in same format and offset for compatibility with\n"
+"existing version checkers"
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/updates.html:216
+msgid "Specification:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/updates.html:275
+msgid "All unused fields must be set to 0 for compatibility with future versions."
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/updates.html:282
+msgid ""
+"The network will eventually grow too large for update over HTTP.\n"
+"The built-in BitTorrent client, i2psnark, may be used as a distributed "
+"update method.\n"
+"This development effort is ongoing and should be completed by late 2013."
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/updates.html:287
+msgid ""
+"The router update mechanism is part of the web router console.\n"
+"There is currently no provision for updates of an embedded router lacking"
+" the router console."
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/index.html:2
+msgid "Transport Overview"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/index.html:3
+msgid "April 2013"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/index.html:6
+msgid "Transports in I2P"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/index.html:8
+msgid ""
+"A \"transport\" in I2P is a method for direct, point-to-point "
+"communication\n"
+"between two routers.\n"
+"Transports must provide confidentiality and integrity \n"
+"against external adversaries while authenticating that the router "
+"contacted \n"
+"is the one who should receive a given message."
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/index.html:16
+msgid ""
+"I2P supports multiple transports simultaneously.\n"
+"There are two transports currently implemented:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/index.html:21
+#, python-format
+msgid "NTCP, a Java New I/O (NIO) TCP transport"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/index.html:22
+#, python-format
+msgid " SSU, or Secure Semireliable UDP"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/index.html:25
+msgid ""
+"Each provides a \"connection\" paradigm, with authentication,\n"
+"flow control, acknowledgments and retransmission."
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/index.html:31
+msgid "Transport Services"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/index.html:33
+msgid "The transport subsystem in I2P provides the following services:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/index.html:37
+msgid ""
+"Maintain a set of router addresses, one or more for each transport,\n"
+"that the router publishes as its global contact information (the "
+"RouterInfo)"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/index.html:41
+msgid "Selection of the best transport for each outgoing message"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/index.html:42
+msgid "Queueing of outbound messages by priority"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/index.html:43
+msgid ""
+"Bandwidth limiting, both outbound and inbound, according to router "
+"configuration"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/index.html:44
+msgid "Setup and teardown of transport connections"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/index.html:45
+msgid "Encryption of point-to-point communications"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/index.html:46
+msgid ""
+"Maintenance of connection limits for each transport, implementation of "
+"various thresholds for these limits,\n"
+"and communication of threshold status to the router so it may make "
+"operational changes based on the status"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/index.html:50
+msgid "Firewall port opening using UPnP (Universal Plug and Play)"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/index.html:51
+msgid "Cooperative NAT/Firewall traversal"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/index.html:52
+msgid ""
+"Local IP detection by various methods, including UPnP, inspection of "
+"incoming connections, and enumeration of network devices"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/index.html:53
+msgid ""
+"Coordination of firewall status and local IP, and changes to either, "
+"among the transports"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/index.html:54
+#: i2p2www/pages/site/docs/transport/ssu.html:32
+msgid ""
+"Communication of firewall status and local IP, and changes to either, to "
+"the router and the user interface"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/index.html:55
+msgid ""
+"Determination of a consensus clock, which is used to periodically update "
+"the router's clock, as a backup for NTP"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/index.html:56
+msgid ""
+"Maintenance of status for each peer, including whether it is connected, "
+"whether it was recently connected,\n"
+"and whether it was reachable in the last attempt"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/index.html:60
+msgid "Qualification of valid IP addresses according to a local rule set"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/index.html:61
+msgid ""
+"Honoring the automated and manual lists of banned peers maintained by the"
+" router,\n"
+"and refusing outbound and inbound connections to those peers"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/index.html:68
+msgid "Transport Addresses"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/index.html:70
+msgid ""
+"The transport subsystem maintains a set of router addresses, each of "
+"which lists a transport method, IP, and port.\n"
+"These addresses constitute the advertised contact points, and are "
+"published by the router to the network database."
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/index.html:75
+msgid "Typical scenarios are:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/index.html:77
+msgid ""
+"A router has no published addresses, so it is considered \"hidden\" and "
+"cannot receive incoming connections"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/index.html:78
+#, python-format
+msgid ""
+"A router is firewalled, and therefore publishes an SSU address which "
+"contains a list of cooperating\n"
+"peers or \"introducers\" who will assist in NAT traversal (see the SSU spec for details)"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/index.html:82
+msgid ""
+"A router is not firewalled or its NAT ports are open; it publishes both "
+"NTCP and SSU addresses containing\n"
+"directly-accessible IP and ports."
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/index.html:88
+msgid "Transport Selection"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/index.html:90
+#, python-format
+msgid ""
+"The transport system delivers I2NP messages. The"
+" transport selected for any message is\n"
+"independent of the upper-layer protocols and contents (router or client "
+"messages, whether an external application was using\n"
+"TCP or UDP to connect to I2P, whether the upper layer was using\n"
+"the streaming library\n"
+"streaming\n"
+"or\n"
+"datagrams,\n"
+"datagrams\n"
+"etc.)."
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/index.html:104
+msgid ""
+"For each outgoing message, the transport system solicits \"bids\" from "
+"each transport.\n"
+"The transport bidding the lowest (best) value wins the bid and receives "
+"the message for delivery.\n"
+"A transport may refuse to bid."
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/index.html:110
+msgid "Whether a transport bids, and with what value, depend on numerous factors:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/index.html:114
+msgid "Configuration of transport preferences"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/index.html:115
+msgid "Whether the transport is already connected to the peer"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/index.html:116
+msgid ""
+"The number of current connections compared to various connection limit "
+"thresholds"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/index.html:117
+msgid "Whether recent connection attempts to the peer have failed"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/index.html:118
+msgid ""
+"The size of the message, as different transports have different size "
+"limits"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/index.html:119
+msgid ""
+"Whether the peer can accept incoming connections for that transport, as "
+"advertised in its RouterInfo"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/index.html:120
+msgid "Whether the connection would be indirect (requiring introducers) or direct"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/index.html:121
+msgid "The peer's transport preference, as advertised in its RouterInfo"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/index.html:124
+msgid ""
+"In general, the bid values are selected so that two routers are only "
+"connected by a single transport\n"
+"at any one time. However, this is not a requirement."
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/index.html:131
+msgid "New Transports and Future Work"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/index.html:133
+msgid "Additional transports may be developed, including:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/index.html:138
+msgid "A TLS/SSH look-alike transport"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/index.html:139
+msgid ""
+"An \"indirect\" transport for routers that are not reachable by all other"
+" routers (one form of \"restricted routes\")"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/index.html:142
+#, python-format
+msgid ""
+"IPv6: The existing transports must be enhanced to support multiple "
+"addresses within a single transport,\n"
+"including IPV6 addresses. Currently, a transport may only advertise a "
+"single IPV4 address.\n"
+"See this thread for discussion."
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/index.html:148
+msgid ""
+"Work continues on adjusting default connection limits for each transport."
+"\n"
+"I2P is designed as a \"mesh network\", where it is assumed that any "
+"router can connect to any other router.\n"
+"This assumption may be broken by routers that have exceeded their "
+"connection limits, and by\n"
+"routers that are behind restrictive state firewalls (restricted routes)."
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/index.html:155
+msgid ""
+"The current connection limits are higher for SSU than for NTCP, based on "
+"the assumption that\n"
+"the memory requirements for an NTCP connection are higher than that for "
+"SSU.\n"
+"However, as NTCP buffers are partially in the kernel and SSU buffers are "
+"on the Java heap,\n"
+"that assumption is difficult to verify."
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/index.html:162
+#, python-format
+msgid ""
+"Analyze Breaking and Improving Protocol "
+"Obfuscation\n"
+"and see how transport-layer padding may improve things."
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:6
+msgid "NTCP (NIO-based TCP)"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:8
+#, python-format
+msgid ""
+"NTCP is one of two transports currently "
+"implemented in I2P.\n"
+"The other is SSU.\n"
+"NTCP is a Java NIO-based transport introduced in I2P release 0.6.1.22.\n"
+"Java NIO (new I/O) does not suffer from the 1 thread per connection "
+"issues of the old TCP transport."
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:15
+msgid ""
+"By default, NTCP uses the IP/Port\n"
+"auto-detected by SSU. When enabled on config.jsp,\n"
+"SSU will notify/restart NTCP when the external address changes\n"
+"or when the firewall status changes.\n"
+"Now you can enable inbound TCP without a static IP or dyndns service."
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:23
+msgid ""
+"The NTCP code within I2P is relatively lightweight (1/4 the size of the "
+"SSU code)\n"
+"because it uses the underlying Java TCP transport for reliable delivery."
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:29
+msgid "NTCP Protocol Specification"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:31
+msgid "Standard Message Format"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:32
+msgid ""
+"After establishment,\n"
+"the NTCP transport sends individual I2NP messages, with a simple "
+"checksum.\n"
+"The unencrypted message is encoded as follows:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:42
+msgid ""
+"The data is then AES/256/CBC encrypted. The session key for the "
+"encryption\n"
+"is negotiated during establishment (using Diffie-Hellman 2048 bit).\n"
+"The establishment between two routers is implemented in the "
+"EstablishState class\n"
+"and detailed below.\n"
+"The IV for AES/256/CBC encryption is the last 16 bytes of the previous "
+"encrypted message."
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:50
+msgid ""
+"0-15 bytes of padding are required to bring the total message length\n"
+"(including the six size and checksum bytes) to a multiple of 16.\n"
+"The maximum message size is currently 16 KB.\n"
+"Therefore the maximum data size is currently 16 KB - 6, or 16378 bytes.\n"
+"The minimum data size is 1."
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:58
+msgid "Time Sync Message Format"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:59
+msgid ""
+"One special case is a metadata message where the sizeof(data) is 0. In\n"
+"that case, the unencrypted message is encoded as:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:70
+msgid ""
+"Total length: 16 bytes. The time sync message is sent at approximately 15"
+" minute intervals.\n"
+"The message is encrypted just as standard messages are."
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:76
+msgid "Checksums"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:77
+#, python-format
+msgid ""
+"The standard and time sync messages use the Adler-32 checksum\n"
+"as defined in the ZLIB Specification."
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:83
+msgid "Establishment Sequence"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:84
+msgid ""
+"In the establish state, there is a 4-phase message sequence to exchange "
+"DH keys and signatures.\n"
+"In the first two messages there is a 2048-bit Diffie Hellman exchange.\n"
+"Then, DSA signatures of the critical data are exchanged to confirm the "
+"connection."
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:98
+msgid "Legend:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:99
+msgid "256 byte DH public keys"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:103
+msgid "timestamps (4 bytes, seconds since epoch)"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:104
+msgid "32 byte Session key"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:105
+msgid "2 byte size of Alice identity to follow"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:108
+msgid "DH Key Exchange"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:109
+#, python-format
+msgid ""
+"The initial 2048-bit DH key exchange\n"
+"uses the same shared prime (p) and generator (g) as that used for I2P's\n"
+"ElGamal encryption."
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:115
+msgid ""
+"The DH key exchange consists of a number of steps, displayed below.\n"
+"The mapping between these steps and the messages sent between I2P "
+"routers,\n"
+"is marked in bold."
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:121
+msgid ""
+"Alice generates a secret 226-bit integer x. She then calculates X ="
+" g^x mod p."
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:122
+msgid "Alice sends X to Bob (Message 1)."
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:123
+msgid ""
+"Bob generates a secret 226-bit integer y. He then calculates Y = "
+"g^y mod p."
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:124
+msgid "Bob sends Y to Alice.(Message 2)"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:125
+msgid "Alice can now compute sessionKey = Y^x mod p."
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:126
+msgid "Bob can now compute sessionKey = X^y mod p."
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:127
+msgid ""
+"Both Alice and Bob now have a shared key sessionKey = g^(x*y) mod "
+"p."
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:129
+msgid ""
+"The sessionKey is then used to exchange identities in Message 3 "
+"and Message 4."
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:133
+msgid "Message 1 (Session Request)"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:134
+#, python-format
+msgid ""
+"This is the DH request. Alice already has Bob's\n"
+"Router "
+"Identity,\n"
+"IP address, and port, as contained in his\n"
+"Router Info,\n"
+"which was published to the\n"
+"network database.\n"
+"Alice sends Bob:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:147
+#: i2p2www/pages/site/docs/transport/ntcp.html:190
+#: i2p2www/pages/site/docs/transport/ntcp.html:270
+#: i2p2www/pages/site/docs/transport/ntcp.html:353
+msgid "Size:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:149
+msgid "Contents:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:167
+msgid "256 byte X from Diffie Hellman"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:169
+#, python-format
+msgid ""
+"SHA256 Hash(X) xored with SHA256 Hash(Bob's Router Identity)"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:176
+#: i2p2www/pages/site/docs/transport/ntcp.html:257
+#: i2p2www/pages/site/docs/transport/ntcp.html:334
+msgid "Notes:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:177
+msgid ""
+"Bob verifies HXxorHI using his own router hash. If it does not verify,\n"
+"Alice has contacted the wrong router, and Bob drops the connection."
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:183
+msgid "Message 2 (Session Created)"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:184
+msgid "This is the DH reply. Bob sends Alice:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:192
+#: i2p2www/pages/site/docs/transport/ntcp.html:272
+#: i2p2www/pages/site/docs/transport/ntcp.html:355
+msgid "Unencrypted Contents:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:214
+#: i2p2www/pages/site/docs/transport/ntcp.html:248
+msgid "256 byte Y from Diffie Hellman"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:216
+msgid "SHA256 Hash(X concatenated with Y)"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:219
+#: i2p2www/pages/site/docs/transport/ntcp.html:304
+msgid "4 byte timestamp (seconds since the epoch)"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:221
+msgid "12 bytes random data"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:226
+#: i2p2www/pages/site/docs/transport/ntcp.html:316
+#: i2p2www/pages/site/docs/transport/ntcp.html:383
+msgid "Encrypted Contents:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:250
+#, python-format
+msgid ""
+"48 bytes AES encrypted using the DH "
+"session key and\n"
+" the last 16 bytes of Y as the IV"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:258
+msgid ""
+"Alice may drop the connection if the clock skew with Bob is too high as "
+"calculated using tsB."
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:263
+msgid "Message 3 (Session Confirm A)"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:264
+msgid ""
+"This contains Alice's router identity, and a DSA signature of the "
+"critical data. Alice sends Bob:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:298
+msgid "2 byte size of Alice's router identity to follow (should always be 387)"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:300
+#, python-format
+msgid ""
+"Alice's 387 byte Router Identity"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:306
+msgid "15 bytes random data"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:308
+#, python-format
+msgid ""
+"the 40 byte DSA "
+"signature of the following concatenated data:\n"
+" X, Y, Bob's Router Identity, "
+"tsA, tsB.\n"
+" Alice signs it with the private signing "
+"key associated with the public signing "
+"key in her Router Identity"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:326
+#, python-format
+msgid ""
+"448 bytes AES encrypted using the DH"
+" session key and\n"
+" the last 16 bytes of HXxorHI (i.e., the last 16 bytes "
+"of message #1) as the IV"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:336
+msgid "Bob verifies the signature, and on failure, drops the connection."
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:339
+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:346
+msgid "Message 4 (Session Confirm B)"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:347
+msgid "This is a DSA signature of the critical data. Bob sends Alice:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:372
+#, python-format
+msgid ""
+"the 40 byte DSA "
+"signature of the following concatenated data:\n"
+" X, Y, Alice's Router Identity, "
+"tsA, tsB.\n"
+" Bob signs it with the private signing "
+"key associated with the public signing "
+"key in his Router Identity"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:378
+msgid "8 bytes random data"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:393
+#, python-format
+msgid ""
+"48 bytes AES encrypted using the DH "
+"session key and\n"
+" the last 16 bytes of the encrypted contents of message "
+"#2 as the IV"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:401
+msgid "Alice verifies the signature, and on failure, drops the connection."
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:408
+msgid "After Establishment"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:409
+msgid ""
+"The connection is established, and standard or time sync messages may be "
+"exchanged.\n"
+"All subsequent messages are AES encrypted using the negotiated DH session"
+" key.\n"
+"Alice will use the last 16 bytes of the encrypted contents of message #3 "
+"as the next IV.\n"
+"Bob will use the last 16 bytes of the encrypted contents of message #4 as"
+" the next IV."
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:418
+msgid "Check Connection Message"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:419
+msgid ""
+"Alternately, when Bob receives a connection, it could be a\n"
+"check connection (perhaps prompted by Bob asking for someone\n"
+"to verify his listener).\n"
+"Check Connection is not currently used.\n"
+"However, for the record, check connections are formatted as follows.\n"
+"A check info connection will receive 256 bytes containing:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:428
+msgid "32 bytes of uninterpreted, ignored data"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:429
+msgid "1 byte size"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:430
+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:431
+msgid "2 byte port number that the local router was reached on"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:432
+msgid ""
+"4 byte i2p network time as known by the remote side (seconds since the "
+"epoch)"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:433
+msgid "uninterpreted padding data, up to byte 223"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:434
+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:438
+msgid "Discussion"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:439
+#, python-format
+msgid "Now on the NTCP Discussion Page."
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:445
+msgid "The maximum message size should be increased to approximately 32 KB."
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:449
+msgid ""
+"A set of fixed packet sizes may be appropriate to further hide the data \n"
+"fragmentation to external adversaries, but the tunnel, garlic, and end to"
+" \n"
+"end padding should be sufficient for most needs until then.\n"
+"However, there is currently no provision for padding beyond the next "
+"16-byte boundary,\n"
+"to create a limited number of message sizes."
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:457
+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:461
+msgid ""
+"Can the establishment messages be randomly padded somehow, to frustrate\n"
+"identification of I2P traffic based on initial packet sizes?"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:466
+msgid "Review and possibly disable 'check connection'"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ssu.html:2
+msgid "SSU Transport"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ssu.html:6
+msgid "Secure Semireliable UDP"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ssu.html:9
+#, python-format
+msgid ""
+"SSU (also called \"UDP\" in much of the I2P documentation and user "
+"interfaces)\n"
+"is one of two transports currently "
+"implemented in I2P.\n"
+"The other is NTCP."
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ssu.html:15
+msgid ""
+"SSU is the newer of the two transports,\n"
+"introduced in I2P release 0.6.\n"
+"In a standard I2P installation, the router uses both NTCP and SSU for "
+"outbound connections."
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ssu.html:21
+msgid "SSU Services"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ssu.html:23
+msgid ""
+"Like the NTCP transport, SSU provides reliable, encrypted, connection-"
+"oriented, point-to-point data transport.\n"
+"Unique to SSU, it also provides IP detection and NAT traversal services, "
+"including:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ssu.html:29
+msgid ""
+"Cooperative NAT/Firewall traversal using introducers"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ssu.html:30
+msgid ""
+"Local IP detection by inspection of incoming packets and peer testing"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ssu.html:31
+msgid ""
+"Communication of firewall status and local IP, and changes to either to "
+"NTCP"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ssu.html:36
+msgid "Protocol Details"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ssu.html:38
+msgid "Congestion control"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ssu.html:40
+msgid ""
+"SSU's need for only semireliable delivery, TCP-friendly operation,\n"
+"and the capacity for high throughput allows a great deal of latitude in\n"
+"congestion control. The congestion control algorithm outlined below is\n"
+"meant to be both efficient in bandwidth as well as simple to implement."
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ssu.html:47
+msgid ""
+"Packets are scheduled according to the router's policy, taking care\n"
+"not to exceed the router's outbound capacity or to exceed the measured \n"
+"capacity of the remote peer. The measured capacity operates along the\n"
+"lines of TCP's slow start and congestion avoidance, with additive "
+"increases\n"
+"to the sending capacity and multiplicative decreases in face of "
+"congestion.\n"
+"Unlike for TCP, routers may give up on some messages after\n"
+"a given period or number of retransmissions while continuing to transmit"
+" \n"
+"other messages."
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ssu.html:58
+msgid ""
+"The congestion detection techniques vary from TCP as well, since each \n"
+"message has its own unique and nonsequential identifier, and each message"
+"\n"
+"has a limited size - at most, 32KB. To efficiently transmit this "
+"feedback\n"
+"to the sender, the receiver periodically includes a list of fully ACKed \n"
+"message identifiers and may also include bitfields for partially received"
+"\n"
+"messages, where each bit represents the reception of a fragment. If \n"
+"duplicate fragments arrive, the message should be ACKed again, or if the\n"
+"message has still not been fully received, the bitfield should be \n"
+"retransmitted with any new updates."
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ssu.html:70
+msgid ""
+"The current implementation does not pad the packets to\n"
+"any particular size, but instead just places a single message fragment "
+"into\n"
+"a packet and sends it off (careful not to exceed the MTU)."
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ssu.html:77
+msgid ""
+"As of router version 0.8.12,\n"
+"two MTU values are used for IPv4: 620 and 1484.\n"
+"The MTU value is adjusted based on the percentage of packets that are "
+"retransmitted."
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ssu.html:83
+msgid ""
+"For both MTU values, it is desirable that (MTU % 16) == 12, so that\n"
+"the payload portion after the 28-byte IP/UDP header is a multiple of\n"
+"16 bytes, for encryption purposes."
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ssu.html:89
+msgid ""
+"For the small MTU value, it is desirable to pack a 2646-byte\n"
+"Variable Tunnel Build Message efficiently into multiple packets;\n"
+"with a 620-byte MTU, it fits into 5 packets with nicely."
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ssu.html:95
+msgid ""
+"Based on measurements, 1492 fits nearly all reasonably small I2NP "
+"messages\n"
+"(larger I2NP messages may be up to 1900 to 4500 bytes, which isn't going "
+"to fit\n"
+"into a live network MTU anyway)."
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ssu.html:101
+msgid ""
+"The MTU values were 608 and 1492 for releases 0.8.9 - 0.8.11.\n"
+"The large MTU was 1350 prior to release 0.8.9."
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ssu.html:106
+msgid ""
+"The maximum receive packet size\n"
+"is 1571 bytes as of release 0.8.12.\n"
+"For releases 0.8.9 - 0.8.11 it was 1535 bytes.\n"
+"Prior to release 0.8.9 it was 2048 bytes."
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ssu.html:113
+msgid ""
+"As of release 0.9.2, if a router's network interface MTU is less than "
+"1484,\n"
+"it will publish that in the network database, and other routers should\n"
+"honor that when a connection is established."
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ssu.html:119
+msgid ""
+"For IPv6, the minimum MTU is 1280. The IPv6 IP/UDP header is 48 bytes,\n"
+"so we use an MTU where (MTN % 16 == 0), which is true for 1280."
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ssu.html:124
+msgid "Message Size Limits"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ssu.html:125
+msgid ""
+"While the maximum message size is nominally 32KB, the practical\n"
+"limit differs. The protocol limits the number of fragments to 7 bits, or "
+"128.\n"
+"The current implementation, however, limits each message to a maximum of "
+"64 fragments,\n"
+"which is sufficient for 64 * 534 = 33.3 KB when using the 608 MTU.\n"
+"Due to overhead for bundled LeaseSets and session keys, the practical "
+"limit\n"
+"at the application level is about 6KB lower, or about 26KB.\n"
+"Further work is necessary to raise the UDP transport limit above 32KB.\n"
+"For connections using the larger MTU, larger messages are possible."
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ssu.html:136
+msgid "Keys"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ssu.html:138
+msgid ""
+"All encryption used is AES256/CBC with 32 byte keys and 16 byte IVs.\n"
+"The MAC and session keys are negotiated as part of the DH exchange, used\n"
+"for the HMAC and encryption, respectively. Prior to the DH exchange, \n"
+"the publicly knowable introKey is used for the MAC and encryption."
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ssu.html:145
+msgid ""
+"When using the introKey, both the initial message and any subsequent\n"
+"reply use the introKey of the responder (Bob) - the responder does \n"
+"not need to know the introKey of the requester (Alice). The DSA \n"
+"signing key used by Bob should already be known to Alice when she \n"
+"contacts him, though Alice's DSA key may not already be known by \n"
+"Bob."
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ssu.html:154
+msgid ""
+"Upon receiving a message, the receiver checks the \"from\" IP address and"
+" port\n"
+"with all established sessions - if there are matches,\n"
+"that session's MAC keys are tested in the HMAC. If none\n"
+"of those verify or if there are no matching IP addresses, the \n"
+"receiver tries their introKey in the MAC. If that does not verify,\n"
+"the packet is dropped. If it does verify, it is interpreted \n"
+"according to the message type, though if the receiver is overloaded,\n"
+"it may be dropped anyway."
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ssu.html:165
+msgid ""
+"If Alice and Bob have an established session, but Alice loses the \n"
+"keys for some reason and she wants to contact Bob, she may at any \n"
+"time simply establish a new session through the SessionRequest and\n"
+"related messages. If Bob has lost the key but Alice does not know\n"
+"that, she will first attempt to prod him to reply, by sending a \n"
+"DataMessage with the wantReply flag set, and if Bob continually \n"
+"fails to reply, she will assume the key is lost and reestablish a \n"
+"new one."
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ssu.html:176
+#, python-format
+msgid ""
+"For the DH key agreement,\n"
+"RFC3526 2048bit\n"
+"MODP group (#14) is used:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ssu.html:186
+#, python-format
+msgid ""
+"These are the same p and g used for I2P's\n"
+"ElGamal encryption."
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ssu.html:191
+msgid "Replay prevention"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ssu.html:193
+msgid ""
+"Replay prevention at the SSU layer occurs by rejecting packets \n"
+"with exceedingly old timestamps or those which reuse an IV. To\n"
+"detect duplicate IVs, a sequence of Bloom filters are employed to\n"
+"\"decay\" periodically so that only recently added IVs are detected."
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ssu.html:200
+msgid ""
+"The messageIds used in DataMessages are defined at layers above\n"
+"the SSU transport and are passed through transparently. These IDs\n"
+"are not in any particular order - in fact, they are likely to be\n"
+"entirely random. The SSU layer makes no attempt at messageId \n"
+"replay prevention - higher layers should take that into account."
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ssu.html:208
+msgid "Addressing"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ssu.html:210
+msgid ""
+"To contact an SSU peer, one of two sets of information is necessary:\n"
+"a direct address, for when the peer is publicly reachable, or an\n"
+"indirect address, for using a third party to introduce the peer.\n"
+"There is no restriction on the number of addresses a peer may have."
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ssu.html:222
+msgid ""
+"Each of the addresses may also expose a series of options - special\n"
+"capabilities of that particular peer. For a list of available\n"
+"capabilities, see below."
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ssu.html:228
+#, python-format
+msgid ""
+"The addresses, options, and capabilities are published in the network database."
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ssu.html:233
+msgid "Direct Session Establishment"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ssu.html:234
+msgid ""
+"Direct session establishment is used when no third party is required for "
+"NAT traversal.\n"
+"The message sequence is as follows:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ssu.html:239
+msgid "Connection establishment (direct)"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ssu.html:240
+msgid "Alice connects directly to Bob."
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ssu.html:254
+#, python-format
+msgid ""
+"After the SessionConfirmed message is received, Bob sends a small\n"
+"DeliveryStatus message\n"
+"as a confirmation.\n"
+"In this message, the 4-byte message ID is set to a random number, and the"
+"\n"
+"8-byte \"arrival time\" is set to the current network-wide ID, which is 2"
+"\n"
+"(i.e. 0x0000000000000002)."
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ssu.html:263
+#, python-format
+msgid ""
+"After the status message is sent, the peers exchange\n"
+"DatabaseStore messages\n"
+"containing their\n"
+"RouterInfos."
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ssu.html:271
+msgid ""
+"It does not appear that the type of the status message or its contents "
+"matters.\n"
+"It was originally added becasue the DatabaseStore message was delayed\n"
+"several seconds; since the store is now sent immediately, perhaps\n"
+"the status message can be eliminated."
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ssu.html:280
+msgid ""
+"Introduction keys are delivered through an external channel \n"
+"(the network database, where they are identical to the router Hash for "
+"now)\n"
+"and must be used when establishing a session key. For the indirect\n"
+"address, the peer must first contact the relayhost and ask them for\n"
+"an introduction to the peer known at that relayhost under the given\n"
+"tag. If possible, the relayhost sends a message to the addressed\n"
+"peer telling them to contact the requesting peer, and also gives \n"
+"the requesting peer the IP and port on which the addressed peer is\n"
+"located. In addition, the peer establishing the connection must \n"
+"already know the public keys of the peer they are connecting to (but\n"
+"not necessary to any intermediary relay peer)."
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ssu.html:294
+msgid ""
+"Indirect session establishment by means of a third party introduction\n"
+"is necessary for efficient NAT traversal. Charlie, a router behind a\n"
+"NAT or firewall which does not allow unsolicited inbound UDP packets,\n"
+"first contacts a few peers, choosing some to serve as introducers. Each\n"
+"of these peers (Bob, Bill, Betty, etc) provide Charlie with an "
+"introduction\n"
+"tag - a 4 byte random number - which he then makes available to the "
+"public\n"
+"as methods of contacting him. Alice, a router who has Charlie's "
+"published\n"
+"contact methods, first sends a RelayRequest packet to one or more of the"
+" \n"
+"introducers, asking each to introduce her to Charlie (offering the \n"
+"introduction tag to identify Charlie). Bob then forwards a RelayIntro\n"
+"packet to Charlie including Alice's public IP and port number, then sends"
+"\n"
+"Alice back a RelayResponse packet containing Charlie's public IP and port"
+"\n"
+"number. When Charlie receives the RelayIntro packet, he sends off a "
+"small\n"
+"random packet to Alice's IP and port (poking a hole in his NAT/firewall),"
+"\n"
+"and when Alice receives Bob's RelayResponse packet, she begins a new \n"
+"full direction session establishment with the specified IP and port."
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ssu.html:321
+msgid "Connection establishment (indirect using an introducer)"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ssu.html:323
+msgid "Alice first connects to introducer Bob, who relays the request to Charlie."
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ssu.html:341
+msgid ""
+"After the hole punch, the session is established between Alice and "
+"Charlie as in a direct establishment."
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ssu.html:352
+msgid "Peer testing"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ssu.html:354
+msgid ""
+"The automation of collaborative reachability testing for peers is\n"
+"enabled by a sequence of PeerTest messages. With its proper \n"
+"execution, a peer will be able to determine their own reachability\n"
+"and may update its behavior accordingly. The testing process is \n"
+"quite simple:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ssu.html:373
+msgid ""
+"Each of the PeerTest messages carry a nonce identifying the\n"
+"test series itself, as initialized by Alice. If Alice doesn't \n"
+"get a particular message that she expects, she will retransmit\n"
+"accordingly, and based upon the data received or the messages\n"
+"missing, she will know her reachability. The various end states\n"
+"that may be reached are as follows:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ssu.html:383
+msgid ""
+"If she doesn't receive a response from Bob, she will retransmit\n"
+"up to a certain number of times, but if no response ever arrives,\n"
+"she will know that her firewall or NAT is somehow misconfigured, \n"
+"rejecting all inbound UDP packets even in direct response to an\n"
+"outbound packet. Alternately, Bob may be down or unable to get \n"
+"Charlie to reply."
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ssu.html:392
+msgid ""
+"If Alice doesn't receive a PeerTest message with the \n"
+"expected nonce from a third party (Charlie), she will retransmit\n"
+"her initial request to Bob up to a certain number of times, even\n"
+"if she has received Bob's reply already. If Charlie's first message \n"
+"still doesn't get through but Bob's does, she knows that she is\n"
+"behind a NAT or firewall that is rejecting unsolicited connection\n"
+"attempts and that port forwarding is not operating properly (the\n"
+"IP and port that Bob offered up should be forwarded)."
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ssu.html:403
+msgid ""
+"If Alice receives Bob's PeerTest message and both of Charlie's\n"
+"PeerTest messages but the enclosed IP and port numbers in Bob's \n"
+"and Charlie's second messages don't match, she knows that she is \n"
+"behind a symmetric NAT, rewriting all of her outbound packets with\n"
+"different 'from' ports for each peer contacted. She will need to\n"
+"explicitly forward a port and always have that port exposed for \n"
+"remote connectivity, ignoring further port discovery."
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ssu.html:413
+msgid ""
+"If Alice receives Charlie's first message but not his second,\n"
+"she will retransmit her PeerTest message to Charlie up to a \n"
+"certain number of times, but if no response is received she knows\n"
+"that Charlie is either confused or no longer online."
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ssu.html:421
+msgid ""
+"Alice should choose Bob arbitrarily from known peers who seem\n"
+"to be capable of participating in peer tests. Bob in turn should\n"
+"choose Charlie arbitrarily from peers that he knows who seem to be\n"
+"capable of participating in peer tests and who are on a different\n"
+"IP from both Bob and Alice. If the first error condition occurs\n"
+"(Alice doesn't get PeerTest messages from Bob), Alice may decide\n"
+"to designate a new peer as Bob and try again with a different nonce."
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ssu.html:431
+msgid ""
+"Alice's introduction key is included in all of the PeerTest \n"
+"messages so that she doesn't need to already have an established\n"
+"session with Bob and so that Charlie can contact her without knowing\n"
+"any additional information. Alice may go on to establish a session\n"
+"with either Bob or Charlie, but it is not required."
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ssu.html:449
+msgid "Transmission window, ACKs and Retransmissions"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ssu.html:450
+#, python-format
+msgid ""
+"The DATA message may contain ACKs of full messages and\n"
+"partial ACKs of individual fragments of a message. See\n"
+"the data message section of\n"
+"the protocol specification page\n"
+"for details."
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ssu.html:458
+#, python-format
+msgid ""
+"The details of windowing, ACK, and retransmission strategies are not "
+"specified\n"
+"here. See the Java code for the current implementation.\n"
+"During the establishment phase, and for peer testing, routers\n"
+"should implement exponential backoff for retransmission.\n"
+"For an established connection, routers should implement\n"
+"an adjustable transmission window, RTT estimate and timeout, similar to "
+"TCP\n"
+"or streaming.\n"
+"See the code for initial, min and max parameters."
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ssu.html:470
+msgid "Security"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ssu.html:471
+msgid ""
+"UDP source addresses may, of course, be spoofed.\n"
+"Additionally, the IPs and ports contained inside specific\n"
+"SSU messages (RelayRequest, RelayResponse, RelayIntro, PeerTest)\n"
+"may not be legitimate.\n"
+"Also, certain actions and responses may need to be rate-limited."
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ssu.html:479
+msgid ""
+"The details of validation are not specified\n"
+"here. Implementers should add defenses where appropriate."
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ssu.html:485
+msgid "Peer capabilities"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ssu.html:489
+msgid ""
+"If the peer address contains the 'B' capability, that means \n"
+"they are willing and able to participate in peer tests as\n"
+"a 'Bob' or 'Charlie'."
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ssu.html:495
+msgid ""
+"If the peer address contains the 'C' capability, that means\n"
+"they are willing and able to serve as an introducer - serving\n"
+"as a Bob for an otherwise unreachable Alice."
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ssu.html:504
+msgid ""
+"Analysis of current SSU performance, including assessment of window size "
+"adjustment\n"
+"and other parameters, and adjustment of the protocol implementation to "
+"improve\n"
+"performance, is a topic for future work."
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ssu.html:510
+msgid ""
+"The current implementation repeatedly sends acknowledgments for the same "
+"packets,\n"
+"which unnecessarily increases overhead."
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ssu.html:515
+msgid ""
+"The default small MTU value of 620 should be analyzed and possibly "
+"increased.\n"
+"The current MTU adjustment strategy should be evaluated.\n"
+"Does a streaming lib 1730-byte packet fit in 3 small SSU packets? "
+"Probably not."
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ssu.html:521
+msgid "The protocol should be extended to exchange MTUs during the setup."
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ssu.html:525
+msgid "Rekeying is currently unimplemented and may never be."
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ssu.html:529
+msgid ""
+"The potential use of the 'challenge' fields in RelayIntro and "
+"RelayResponse,\n"
+"and use of the padding field in SessionRequest and SessionCreated, is "
+"undocumented."
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ssu.html:534
+msgid ""
+"Instead of a single fragment per packet, a more efficient\n"
+"strategy may be to bundle multiple message fragments into the same "
+"packet,\n"
+"so long as it doesn't exceed the MTU."
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ssu.html:540
+msgid ""
+"A set of fixed packet sizes may be appropriate to further hide the data \n"
+"fragmentation to external adversaries, but the tunnel, garlic, and end to"
+" \n"
+"end padding should be sufficient for most needs until then."
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ssu.html:546
+msgid ""
+"Why are introduction keys the same as the router hash, should it be "
+"changed, would there be any benefit?"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ssu.html:550
+msgid "Capacities appear to be unused."
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ssu.html:554
+msgid ""
+"Signed-on times in SessionCreated and SessionConfirmed appear to be "
+"unused or unverified."
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ssu.html:559
+msgid "Implementation Diagram"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ssu.html:560
+msgid ""
+"This diagram\n"
+"should accurately reflect the current implementation, however there may "
+"be small differences."
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ssu.html:568
+msgid "Now on the SSU specification page"
+msgstr ""
+
+#: i2p2www/pages/site/docs/tunnels/implementation.html:2
+msgid "Tunnel Implementation"
+msgstr ""
+
+#: i2p2www/pages/site/docs/tunnels/implementation.html:3
+msgid "October 2010"
+msgstr ""
+
+#: i2p2www/pages/site/docs/tunnels/implementation.html:7
+msgid "This page documents the current tunnel implementation."
+msgstr ""
+
+#: i2p2www/pages/site/docs/tunnels/implementation.html:9
+msgid "Tunnel overview"
+msgstr ""
+
+#: i2p2www/pages/site/docs/tunnels/implementation.html:11
+msgid ""
+"Within I2P, messages are passed in one direction through a virtual\n"
+"tunnel of peers, using whatever means are available to pass the \n"
+"message on to the next hop. Messages arrive at the tunnel's \n"
+" gateway, get bundled up and/or fragmented into fixed-size tunnel "
+"messages, \n"
+"and are forwarded on to the next hop in the tunnel, which processes and "
+"verifies\n"
+"the validity of the message and sends it on to the next hop, and so on, "
+"until\n"
+"it reaches the tunnel endpoint. That endpoint takes the messages\n"
+"bundled up by the gateway and forwards them as instructed - either\n"
+"to another router, to another tunnel on another router, or locally."
+msgstr ""
+
+#: i2p2www/pages/site/docs/tunnels/implementation.html:23
+msgid ""
+"Tunnels all work the same, but can be segmented into two different\n"
+"groups - inbound tunnels and outbound tunnels. The inbound tunnels\n"
+"have an untrusted gateway which passes messages down towards the \n"
+"tunnel creator, which serves as the tunnel endpoint. For outbound \n"
+"tunnels, the tunnel creator serves as the gateway, passing messages\n"
+"out to the remote endpoint."
+msgstr ""
+
+#: i2p2www/pages/site/docs/tunnels/implementation.html:32
+msgid ""
+"The tunnel's creator selects exactly which peers will participate\n"
+"in the tunnel, and provides each with the necessary configuration\n"
+"data. They may have any number of hops.\n"
+"It is the intent to make\n"
+"it hard for either participants or third parties to determine the length "
+"of \n"
+"a tunnel, or even for colluding participants to determine whether they "
+"are a\n"
+"part of the same tunnel at all (barring the situation where colluding "
+"peers are\n"
+"next to each other in the tunnel)."
+msgstr ""
+
+#: i2p2www/pages/site/docs/tunnels/implementation.html:43
+msgid ""
+"In practice, a series of tunnel pools are used for different\n"
+"purposes - each local client destination has its own set of inbound\n"
+"tunnels and outbound tunnels, configured to meet its anonymity and\n"
+"performance needs. In addition, the router itself maintains a series\n"
+"of pools for participating in the network database and for managing\n"
+"the tunnels themselves."
+msgstr ""
+
+#: i2p2www/pages/site/docs/tunnels/implementation.html:52
+msgid ""
+"I2P is an inherently packet switched network, even with these \n"
+"tunnels, allowing it to take advantage of multiple tunnels running \n"
+"in parallel, increasing resilience and balancing load. Outside of\n"
+"the core I2P layer, there is an optional end to end streaming library \n"
+"available for client applications, exposing TCP-esque operation,\n"
+"including message reordering, retransmission, congestion control, etc."
+msgstr ""
+
+#: i2p2www/pages/site/docs/tunnels/implementation.html:61
+#, python-format
+msgid ""
+"An overview of I2P tunnel terminology is\n"
+"on the tunnel overview page."
+msgstr ""
+
+#: i2p2www/pages/site/docs/tunnels/implementation.html:66
+msgid "Tunnel Operation (Message Processing)"
+msgstr ""
+
+#: i2p2www/pages/site/docs/tunnels/implementation.html:69
+#, python-format
+msgid ""
+"After a tunnel is built, I2NP messages are "
+"processed and passed through it.\n"
+"Tunnel operation has four distinct processes, taken on by various \n"
+"peers in the tunnel."
+msgstr ""
+
+#: i2p2www/pages/site/docs/tunnels/implementation.html:75
+msgid ""
+"First, the tunnel gateway accumulates a number\n"
+"of I2NP messages and preprocesses them into tunnel messages for\n"
+"delivery."
+msgstr ""
+
+#: i2p2www/pages/site/docs/tunnels/implementation.html:80
+msgid ""
+"Next, that gateway encrypts that preprocessed data, then\n"
+"forwards it to the first hop."
+msgstr ""
+
+#: i2p2www/pages/site/docs/tunnels/implementation.html:84
+msgid ""
+"That peer, and subsequent tunnel \n"
+"participants, unwrap a layer of the encryption, verifying that it isn't\n"
+"a duplicate, then forward it on to the next peer."
+msgstr ""
+
+#: i2p2www/pages/site/docs/tunnels/implementation.html:89
+msgid ""
+"Eventually, the tunnel messages arrive at the endpoint where the I2NP "
+"messages\n"
+"originally bundled by the gateway are reassembled and forwarded on as \n"
+"requested."
+msgstr ""
+
+#: i2p2www/pages/site/docs/tunnels/implementation.html:96
+msgid ""
+"Intermediate tunnel participants do not know whether they are in an\n"
+"inbound or an outbound tunnel; they always \"encrypt\" for the next hop.\n"
+"Therefore, we take advantage of symmetric AES encryption\n"
+"to \"decrypt\" at the outbound tunnel gateway,\n"
+"so that the plaintext is revealed at the outbound endpoint."
+msgstr ""
+
+#: i2p2www/pages/site/docs/tunnels/implementation.html:110
+msgid "Role"
+msgstr ""
+
+#: i2p2www/pages/site/docs/tunnels/implementation.html:111
+msgid "Preprocessing"
+msgstr ""
+
+#: i2p2www/pages/site/docs/tunnels/implementation.html:112
+msgid "Encryption Operation"
+msgstr ""
+
+#: i2p2www/pages/site/docs/tunnels/implementation.html:113
+msgid "Postprocessing"
+msgstr ""
+
+#: i2p2www/pages/site/docs/tunnels/implementation.html:117
+msgid "Outbound Gateway (Creator)"
+msgstr ""
+
+#: i2p2www/pages/site/docs/tunnels/implementation.html:118
+#: i2p2www/pages/site/docs/tunnels/implementation.html:141
+msgid "Fragment, Batch, and Pad"
+msgstr ""
+
+#: i2p2www/pages/site/docs/tunnels/implementation.html:119
+msgid "Iteratively encrypt (using decryption operations)"
+msgstr ""
+
+#: i2p2www/pages/site/docs/tunnels/implementation.html:120
+#: i2p2www/pages/site/docs/tunnels/implementation.html:127
+#: i2p2www/pages/site/docs/tunnels/implementation.html:143
+#: i2p2www/pages/site/docs/tunnels/implementation.html:150
+msgid "Forward to next hop"
+msgstr ""
+
+#: i2p2www/pages/site/docs/tunnels/implementation.html:124
+#: i2p2www/pages/site/docs/tunnels/implementation.html:147
+msgid "Participant"
+msgstr ""
+
+#: i2p2www/pages/site/docs/tunnels/implementation.html:126
+msgid "Decrypt (using an encryption operation)"
+msgstr ""
+
+#: i2p2www/pages/site/docs/tunnels/implementation.html:133
+msgid "Decrypt (using an encryption operation) to reveal plaintext tunnel message"
+msgstr ""
+
+#: i2p2www/pages/site/docs/tunnels/implementation.html:134
+msgid "Reassemble Fragments, Forward as instructed to Inbound Gateway or Router"
+msgstr ""
+
+#: i2p2www/pages/site/docs/tunnels/implementation.html:142
+#: i2p2www/pages/site/docs/tunnels/implementation.html:149
+msgid "Encrypt"
+msgstr ""
+
+#: i2p2www/pages/site/docs/tunnels/implementation.html:154
+msgid "Inbound Endpoint (Creator)"
+msgstr ""
+
+#: i2p2www/pages/site/docs/tunnels/implementation.html:156
+msgid "Iteratively decrypt to reveal plaintext tunnel message"
+msgstr ""
+
+#: i2p2www/pages/site/docs/tunnels/implementation.html:157
+msgid "Reassemble Fragments, Receive data"
+msgstr ""
+
+#: i2p2www/pages/site/docs/tunnels/implementation.html:163
+msgid "Gateway Processing"
+msgstr ""
+
+#: i2p2www/pages/site/docs/tunnels/implementation.html:164
+msgid "Message Preprocessing"
+msgstr ""
+
+#: i2p2www/pages/site/docs/tunnels/implementation.html:166
+#, python-format
+msgid ""
+"A tunnel gateway's function is to fragment and pack\n"
+"I2NP messages into fixed-size\n"
+"tunnel messages\n"
+"and encrypt the tunnel messages.\n"
+"Tunnel messages contain the following:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/tunnels/implementation.html:174
+msgid "A 4 byte Tunnel ID"
+msgstr ""
+
+#: i2p2www/pages/site/docs/tunnels/implementation.html:175
+msgid "A 16 byte IV (initialization vector)"
+msgstr ""
+
+#: i2p2www/pages/site/docs/tunnels/implementation.html:176
+msgid "A checksum"
+msgstr ""
+
+#: i2p2www/pages/site/docs/tunnels/implementation.html:177
+msgid "Padding, if necessary"
+msgstr ""
+
+#: i2p2www/pages/site/docs/tunnels/implementation.html:178
+msgid "One or more { delivery instruction, I2NP message fragment } pairs"
+msgstr ""
+
+#: i2p2www/pages/site/docs/tunnels/implementation.html:181
+msgid ""
+"Tunnel IDs are 4 byte numbers used at each hop - participants know what\n"
+"tunnel ID to listen for messages with and what tunnel ID they should be "
+"forwarded\n"
+"on as to the next hop, and each hop chooses the tunnel ID which they "
+"receive messages\n"
+"on. Tunnels themselves are short-lived (10 minutes).\n"
+"Even if subsequent tunnels are built using the same sequence of \n"
+"peers, each hop's tunnel ID will change."
+msgstr ""
+
+#: i2p2www/pages/site/docs/tunnels/implementation.html:190
+msgid ""
+"To prevent adversaries from tagging the messages along the path by "
+"adjusting\n"
+"the message size, all tunnel messages are a fixed 1024 bytes in size. To"
+" accommodate \n"
+"larger I2NP messages as well as to support smaller ones more efficiently,"
+" the\n"
+"gateway splits up the larger I2NP messages into fragments contained "
+"within each\n"
+"tunnel message. The endpoint will attempt to rebuild the I2NP message "
+"from the\n"
+"fragments for a short period of time, but will discard them as necessary."
+msgstr ""
+
+#: i2p2www/pages/site/docs/tunnels/implementation.html:199
+#, python-format
+msgid ""
+"Details are in the\n"
+"tunnel message specification."
+msgstr ""
+
+#: i2p2www/pages/site/docs/tunnels/implementation.html:205
+msgid "Gateway Encryption"
+msgstr ""
+
+#: i2p2www/pages/site/docs/tunnels/implementation.html:207
+msgid ""
+"After the preprocessing of messages into a padded payload, the gateway "
+"builds\n"
+"a random 16 byte IV value, iteratively encrypting it and the tunnel "
+"message as\n"
+"necessary, and forwards the tuple {tunnelID, IV, encrypted tunnel "
+"message} to the next hop."
+msgstr ""
+
+#: i2p2www/pages/site/docs/tunnels/implementation.html:213
+msgid ""
+"How encryption at the gateway is done depends on whether the tunnel is an"
+"\n"
+"inbound or an outbound tunnel. For inbound tunnels, they simply select a"
+" random\n"
+"IV, postprocessing and updating it to generate the IV for the gateway and"
+" using \n"
+"that IV along side their own layer key to encrypt the preprocessed data."
+" For outbound \n"
+"tunnels they must iteratively decrypt the (unencrypted) IV and "
+"preprocessed \n"
+"data with the IV and layer keys for all hops in the tunnel. The result "
+"of the outbound\n"
+"tunnel encryption is that when each peer encrypts it, the endpoint will "
+"recover \n"
+"the initial preprocessed data."
+msgstr ""
+
+#: i2p2www/pages/site/docs/tunnels/implementation.html:225
+msgid "Participant Processing"
+msgstr ""
+
+#: i2p2www/pages/site/docs/tunnels/implementation.html:227
+msgid ""
+"When a peer receives a tunnel message, it checks that the message came "
+"from\n"
+"the same previous hop as before (initialized when the first message comes"
+" through\n"
+"the tunnel). If the previous peer is a different router, or if the "
+"message has\n"
+"already been seen, the message is dropped. The participant then encrypts"
+" the \n"
+"received IV with AES256/ECB using their IV key to determine the current "
+"IV, uses \n"
+"that IV with the participant's layer key to encrypt the data, encrypts "
+"the \n"
+"current IV with AES256/ECB using their IV key again, then forwards the "
+"tuple \n"
+"{nextTunnelId, nextIV, encryptedData} to the next hop. This double "
+"encryption\n"
+"of the IV (both before and after use) help address a certain class of\n"
+"confirmation attacks."
+msgstr ""
+
+#: i2p2www/pages/site/docs/tunnels/implementation.html:240
+msgid ""
+"Duplicate message detection is handled by a decaying Bloom filter on "
+"message\n"
+"IVs. Each router maintains a single Bloom filter to contain the XOR of "
+"the IV and\n"
+"the first block of the message received for all of the tunnels it is "
+"participating\n"
+"in, modified to drop seen entries after 10-20 minutes (when the tunnels "
+"will have\n"
+"expired). The size of the bloom filter and the parameters used are "
+"sufficient to\n"
+"more than saturate the router's network connection with a negligible "
+"chance of \n"
+"false positive. The unique value fed into the Bloom filter is the XOR of"
+" the IV \n"
+"and the first block so as to prevent nonsequential colluding peers in the"
+" tunnel \n"
+"from tagging a message by resending it with the IV and first block "
+"switched."
+msgstr ""
+
+#: i2p2www/pages/site/docs/tunnels/implementation.html:253
+msgid "Endpoint Processing"
+msgstr ""
+
+#: i2p2www/pages/site/docs/tunnels/implementation.html:255
+msgid ""
+"After receiving and validating a tunnel message at the last hop in the "
+"tunnel,\n"
+"how the endpoint recovers the data encoded by the gateway depends upon "
+"whether \n"
+"the tunnel is an inbound or an outbound tunnel. For outbound tunnels, "
+"the \n"
+"endpoint encrypts the message with its layer key just like any other "
+"participant, \n"
+"exposing the preprocessed data. For inbound tunnels, the endpoint is "
+"also the \n"
+"tunnel creator so they can merely iteratively decrypt the IV and message,"
+" using the \n"
+"layer and IV keys of each step in reverse order."
+msgstr ""
+
+#: i2p2www/pages/site/docs/tunnels/implementation.html:265
+msgid ""
+"At this point, the tunnel endpoint has the preprocessed data sent by the "
+"gateway,\n"
+"which it may then parse out into the included I2NP messages and forwards "
+"them as\n"
+"requested in their delivery instructions."
+msgstr ""
+
+#: i2p2www/pages/site/docs/tunnels/implementation.html:272
+msgid "Tunnel Building"
+msgstr ""
+
+#: i2p2www/pages/site/docs/tunnels/implementation.html:274
+msgid ""
+"When building a tunnel, the creator must send a request with the "
+"necessary\n"
+"configuration data to each of the hops and wait for all of them to agree "
+"before\n"
+"enabling the tunnel. The requests are encrypted so that only the peers "
+"who need\n"
+"to know a piece of information (such as the tunnel layer or IV key) has "
+"that\n"
+"data. In addition, only the tunnel creator will have access to the "
+"peer's\n"
+"reply. There are three important dimensions to keep in mind when "
+"producing\n"
+"the tunnels: what peers are used (and where), how the requests are sent "
+"(and \n"
+"replies received), and how they are maintained."
+msgstr ""
+
+#: i2p2www/pages/site/docs/tunnels/implementation.html:288
+msgid ""
+"Beyond the two types of tunnels - inbound and outbound - there are two "
+"styles\n"
+"of peer selection used for different tunnels - exploratory and client.\n"
+"Exploratory tunnels are used for both network database maintenance and "
+"tunnel\n"
+"maintenance, while client tunnels are used for end to end client messages."
+msgstr ""
+
+#: i2p2www/pages/site/docs/tunnels/implementation.html:296
+msgid "Exploratory tunnel peer selection"
+msgstr ""
+
+#: i2p2www/pages/site/docs/tunnels/implementation.html:298
+msgid ""
+"Exploratory tunnels are built out of a random selection of peers from a "
+"subset\n"
+"of the network. The particular subset varies on the local router and on "
+"what their\n"
+"tunnel routing needs are. In general, the exploratory tunnels are built "
+"out of\n"
+"randomly selected peers who are in the peer's \"not failing but active\" "
+"profile\n"
+"category. The secondary purpose of the tunnels, beyond merely tunnel "
+"routing,\n"
+"is to find underutilized high capacity peers so that they can be promoted"
+" for\n"
+"use in client tunnels."
+msgstr ""
+
+#: i2p2www/pages/site/docs/tunnels/implementation.html:308
+#, python-format
+msgid ""
+"Exploratory peer selection is discussed further on the\n"
+"Peer Profiling and Selection page."
+msgstr ""
+
+#: i2p2www/pages/site/docs/tunnels/implementation.html:314
+msgid "Client tunnel peer selection"
+msgstr ""
+
+#: i2p2www/pages/site/docs/tunnels/implementation.html:316
+msgid ""
+"Client tunnels are built with a more stringent set of requirements - the "
+"local\n"
+"router will select peers out of its \"fast and high capacity\" profile "
+"category so\n"
+"that performance and reliability will meet the needs of the client "
+"application.\n"
+"However, there are several important details beyond that basic selection "
+"that \n"
+"should be adhered to, depending upon the client's anonymity needs."
+msgstr ""
+
+#: i2p2www/pages/site/docs/tunnels/implementation.html:324
+#, python-format
+msgid ""
+"Client peer selection is discussed further on the\n"
+"Peer Profiling and Selection page."
+msgstr ""
+
+#: i2p2www/pages/site/docs/tunnels/implementation.html:329
+msgid "Peer Ordering within Tunnels"
+msgstr ""
+
+#: i2p2www/pages/site/docs/tunnels/implementation.html:331
+#, python-format
+msgid ""
+"Peers are ordered within tunnels to deal with the\n"
+"predecessor attack\n"
+"(2008 update)."
+msgstr ""
+
+#: i2p2www/pages/site/docs/tunnels/implementation.html:338
+msgid ""
+"To frustrate the predecessor \n"
+"attack, the tunnel selection keeps the peers selected in a strict order -"
+"\n"
+"if A, B, and C are in a tunnel for a particular tunnel pool, the hop "
+"after A is always B, and the hop after\n"
+"B is always C."
+msgstr ""
+
+#: i2p2www/pages/site/docs/tunnels/implementation.html:345
+msgid ""
+"Ordering is implemented by generating a random 32-byte key for each\n"
+"tunnel pool at startup.\n"
+"Peers should not be able to guess the ordering, or an attacker could\n"
+"craft two router hashes far apart to maximize the chance of being at both"
+"\n"
+"ends of a tunnel.\n"
+"Peers are sorted by XOR distance of the\n"
+"SHA256 Hash of (the peer's hash concatenated with the random key) from "
+"the random key"
+msgstr ""
+
+#: i2p2www/pages/site/docs/tunnels/implementation.html:360
+msgid ""
+"Because each tunnel pool uses a different random key, ordering is "
+"consistent\n"
+"within a single pool but not between different pools.\n"
+"New keys are generated at each router restart."
+msgstr ""
+
+#: i2p2www/pages/site/docs/tunnels/implementation.html:367
+msgid "Request delivery"
+msgstr ""
+
+#: i2p2www/pages/site/docs/tunnels/implementation.html:369
+#, python-format
+msgid ""
+"A multi-hop tunnel is built using a single build message which is "
+"repeatedly\n"
+"decrypted and forwarded. In the terminology of\n"
+"Hashing it out in Public,\n"
+"this is \"non-interactive\" telescopic tunnel building."
+msgstr ""
+
+#: i2p2www/pages/site/docs/tunnels/implementation.html:376
+#, python-format
+msgid ""
+"This tunnel request preparation, delivery, and response method is\n"
+"designed to reduce the number of\n"
+"predecessors exposed, cuts the number of messages transmitted, verifies "
+"proper\n"
+"connectivity, and avoids the message counting attack of traditional "
+"telescopic\n"
+"tunnel creation.\n"
+"(This method, which sends messages to extend a tunnel through the "
+"already-established\n"
+"part of the tunnel, is termed \"interactive\" telescopic tunnel building "
+"in\n"
+"the \"Hashing it out\" paper.)"
+msgstr ""
+
+#: i2p2www/pages/site/docs/tunnels/implementation.html:387
+#, python-format
+msgid ""
+"The details of tunnel request and response messages, and their "
+"encryption,\n"
+"are specified here."
+msgstr ""
+
+#: i2p2www/pages/site/docs/tunnels/implementation.html:392
+msgid ""
+"Peers may reject tunnel creation requests for a variety of reasons, "
+"though\n"
+"a series of four increasingly severe rejections are known: probabilistic "
+"rejection\n"
+"(due to approaching the router's capacity, or in response to a flood of "
+"requests), \n"
+"transient overload, bandwidth overload, and critical failure. When "
+"received, \n"
+"those four are interpreted by the tunnel creator to help adjust their "
+"profile of\n"
+"the router in question."
+msgstr ""
+
+#: i2p2www/pages/site/docs/tunnels/implementation.html:401
+#, python-format
+msgid ""
+"For more information on peer profiling, see the\n"
+"Peer Profiling and Selection page."
+msgstr ""
+
+#: i2p2www/pages/site/docs/tunnels/implementation.html:407
+msgid "Tunnel Pools"
+msgstr ""
+
+#: i2p2www/pages/site/docs/tunnels/implementation.html:409
+#, python-format
+msgid ""
+"To allow efficient operation, the router maintains a series of tunnel "
+"pools,\n"
+"each managing a group of tunnels used for a specific purpose with their "
+"own\n"
+"configuration. When a tunnel is needed for that purpose, the router "
+"selects one\n"
+"out of the appropriate pool at random. Overall, there are two "
+"exploratory tunnel\n"
+"pools - one inbound and one outbound - each using the router's default "
+"configuration.\n"
+"In addition, there is a pair of pools for each local destination -\n"
+"one inbound and one outbound tunnel pool. Those pools use the "
+"configuration specified\n"
+"when the local destination connects to the router via I2CP, or the router's defaults if\n"
+"not specified."
+msgstr ""
+
+#: i2p2www/pages/site/docs/tunnels/implementation.html:421
+#, python-format
+msgid ""
+"Each pool has within its configuration a few key settings, defining how "
+"many\n"
+"tunnels to keep active, how many backup tunnels to maintain in case of "
+"failure,\n"
+"how long the tunnels should be, whether those\n"
+"lengths should be randomized, as \n"
+"well as any of the other settings allowed when configuring individual "
+"tunnels.\n"
+"Configuration options are specified on the I2CP "
+"page."
+msgstr ""
+
+#: i2p2www/pages/site/docs/tunnels/implementation.html:431
+msgid "Tunnel Lengths and Defaults"
+msgstr ""
+
+#: i2p2www/pages/site/docs/tunnels/implementation.html:433
+msgid "On the tunnel overview page"
+msgstr ""
+
+#: i2p2www/pages/site/docs/tunnels/implementation.html:435
+msgid "Anticipatory Build Strategy and Priority"
+msgstr ""
+
+#: i2p2www/pages/site/docs/tunnels/implementation.html:437
+msgid ""
+"Tunnel building is expensive, and tunnels expire a fixed time after they "
+"are built.\n"
+"However, when a pool that runs out of tunnels, the Destination is "
+"essentially dead.\n"
+"In addition, tunnel build success rate may vary greatly with both local "
+"and global\n"
+"network conditions.\n"
+"Therefore, it is important to maintain an anticipatory, adaptive build "
+"strategy\n"
+"to ensure that new tunnels are successfully built before they are needed,"
+"\n"
+"without building an excess of tunnels, building them too soon,\n"
+"or consuming too much CPU or bandwidth creating and sending the encrypted"
+" build messages."
+msgstr ""
+
+#: i2p2www/pages/site/docs/tunnels/implementation.html:448
+msgid ""
+"For each tuple {exploratory/client, in/out, length, length variance}\n"
+"the router maintains statistics on the time required for a successful\n"
+"tunnel build.\n"
+"Using these statistics, it calculates how long before a tunnel's "
+"expiration\n"
+"it should start attempting to build a replacement.\n"
+"As the expiration time approaches without a successful replacement,\n"
+"it starts multiple build attempts in parallel, and then\n"
+"will increase the number of parallel attempts if necessary."
+msgstr ""
+
+#: i2p2www/pages/site/docs/tunnels/implementation.html:459
+msgid ""
+"To cap bandwidth and CPU usage,\n"
+"the router also limits the maximum number of build attempts outstanding\n"
+"across all pools.\n"
+"Critical builds (those for exploratory tunnels, and for pools that have\n"
+"run out of tunnels) are prioritized."
+msgstr ""
+
+#: i2p2www/pages/site/docs/tunnels/implementation.html:468
+msgid "Tunnel Message Throttling"
+msgstr ""
+
+#: i2p2www/pages/site/docs/tunnels/implementation.html:470
+msgid ""
+"Even though the tunnels within I2P bear a resemblance to a circuit "
+"switched\n"
+"network, everything within I2P is strictly message based - tunnels are "
+"merely\n"
+"accounting tricks to help organize the delivery of messages. No "
+"assumptions are\n"
+"made regarding reliability or ordering of messages, and retransmissions "
+"are left\n"
+"to higher levels (e.g. I2P's client layer streaming library). This "
+"allows I2P\n"
+"to take advantage of throttling techniques available to both packet "
+"switched and\n"
+"circuit switched networks. For instance, each router may keep track of "
+"the \n"
+"moving average of how much data each tunnel is using, combine that with "
+"all of \n"
+"the averages used by other tunnels the router is participating in, and be"
+" able\n"
+"to accept or reject additional tunnel participation requests based on its"
+" \n"
+"capacity and utilization. On the other hand, each router can simply drop"
+" \n"
+"messages that are beyond its capacity, exploiting the research used on "
+"the \n"
+"normal Internet."
+msgstr ""
+
+#: i2p2www/pages/site/docs/tunnels/implementation.html:486
+msgid ""
+"In the current implementation, routers implement a\n"
+"weighted random early discard (WRED) strategy.\n"
+"For all participating routers (internal participant, inbound gateway, and"
+" outbound endpoint),\n"
+"the router will start randomly dropping a portion of messages as the\n"
+"bandwidth limits are approached.\n"
+"As traffic gets closer to, or exceeds, the limits, more messages are "
+"dropped.\n"
+"For an internal participant, all messages are fragmented and padded and "
+"therefore are the same size.\n"
+"At the inbound gateway and outbound endpoint, however, the dropping "
+"decision is made\n"
+"on the full (coalesced) message, and the message size is taken into "
+"account.\n"
+"Larger messages are more likely to be dropped.\n"
+"Also, messages are more likely to be dropped at the outbound endpoint "
+"than the inbound gateway,\n"
+"as those messages are not as \"far along\" in their journey and thus the "
+"network cost of\n"
+"dropping those messages is lower."
+msgstr ""
+
+#: i2p2www/pages/site/docs/tunnels/implementation.html:504
+msgid "Mixing/batching"
+msgstr ""
+
+#: i2p2www/pages/site/docs/tunnels/implementation.html:506
+msgid ""
+"What strategies could be used at the gateway and at each hop for "
+"delaying,\n"
+"reordering, rerouting, or padding messages? To what extent should this "
+"be done\n"
+"automatically, how much should be configured as a per tunnel or per hop "
+"setting,\n"
+"and how should the tunnel's creator (and in turn, user) control this "
+"operation?\n"
+"All of this is left as unknown, to be worked out for a distant future "
+"release."
+msgstr ""
+
+#: i2p2www/pages/site/docs/tunnels/implementation.html:515
+msgid "Padding"
+msgstr ""
+
+#: i2p2www/pages/site/docs/tunnels/implementation.html:516
+msgid ""
+"The padding strategies can be used on a variety of levels, addressing the"
+"\n"
+"exposure of message size information to different adversaries.\n"
+"The current fixed tunnel message size is 1024 bytes. Within this "
+"however, the fragmented\n"
+"messages themselves are not padded by the tunnel at all, though for end "
+"to end \n"
+"messages, they may be padded as part of the garlic wrapping."
+msgstr ""
+
+#: i2p2www/pages/site/docs/tunnels/implementation.html:526
+msgid ""
+"WRED strategies have a significant impact on end-to-end performance,\n"
+"and prevention of network congestion collapse.\n"
+"The current WRED strategy should be carefully evaluated and improved."
+msgstr ""
+
+#: i2p2www/pages/site/docs/tunnels/old-implementation.html:2
+msgid "Old Tunnel Implementation"
+msgstr ""
+
+#: i2p2www/pages/site/docs/tunnels/old-implementation.html:5
+#, python-format
+msgid ""
+"Note: Obsolete - NOT used! Replaced in 0.6.1.10 - see here for the current implementation"
+msgstr ""
+
+#: i2p2www/pages/site/docs/tunnels/unidirectional.html:7
+msgid ""
+"This page describes the origins and design of I2P's unidirectional "
+"tunnels.\n"
+"For further infomrmation see:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/tunnels/unidirectional.html:13
+msgid "Tunnel overview page"
+msgstr ""
+
+#: i2p2www/pages/site/docs/tunnels/unidirectional.html:19
+msgid "Tunnel design discussion"
+msgstr ""
+
+#: i2p2www/pages/site/docs/tunnels/unidirectional.html:21
+msgid "Peer selection"
+msgstr ""
+
+#: i2p2www/pages/site/docs/tunnels/unidirectional.html:23
+msgid "Meeting 125 (~13:12-13:30)"
+msgstr ""
+
+#: i2p2www/pages/site/docs/tunnels/unidirectional.html:28
+msgid "Review"
+msgstr ""
+
+#: i2p2www/pages/site/docs/tunnels/unidirectional.html:30
+msgid ""
+"While we aren't aware of any published research on the advantages of \n"
+"unidirecdtional tunnels,\n"
+"they appear to make it harder to detect a \n"
+"request/response pattern, which is quite possible to detect over a \n"
+"bidirectional tunnel.\n"
+"Several apps and protocols, notably HTTP,\n"
+"do transfer data in such manner. Having the traffic follow the same \n"
+"route to its destination and back could make it easier for an \n"
+"attacker who has only timing and traffic volume data to infer the path a"
+" \n"
+"tunnel is taking.\n"
+"Having the response come back along a different path arguably \n"
+"makes it harder."
+msgstr ""
+
+#: i2p2www/pages/site/docs/tunnels/unidirectional.html:45
+msgid ""
+"When dealing with \n"
+"an internal adversary or most external adversaries, I2P's undirectional "
+"tunnels\n"
+"expose half as much traffic data than would be exposed with bidirectional"
+" circuits\n"
+"by simply looking at the flows themselves - an HTTP request and response "
+"would \n"
+"follow the same path in Tor, while in I2P the packets making up the "
+"request \n"
+"would go out through one or more outbound tunnels and the packets making "
+"up \n"
+"the response would come back through one or more different inbound "
+"tunnels."
+msgstr ""
+
+#: i2p2www/pages/site/docs/tunnels/unidirectional.html:55
+msgid ""
+"The strategy of using two separate tunnels for inbound and outbound\n"
+"communication is not the only technique available, and it does have "
+"anonymity\n"
+"implications. On the positive side, by using separate tunnels it lessens"
+" the\n"
+"traffic data exposed for analysis to participants in a tunnel - for "
+"instance,\n"
+"peers in an outbound tunnel from a web browser would only see the traffic"
+" of\n"
+"an HTTP GET, while the peers in an inbound tunnel would see the payload \n"
+"delivered along the tunnel. With bidirectional tunnels, all participants"
+" would\n"
+"have access to the fact that e.g. 1KB was sent in one direction, then "
+"100KB\n"
+"in the other. On the negative side, using unidirectional tunnels means "
+"that\n"
+"there are two sets of peers which need to be profiled and accounted for, "
+"and\n"
+"additional care must be taken to address the increased speed of "
+"predecessor\n"
+"attacks. The tunnel pooling and building process\n"
+"(peer selection and ordering strategies)\n"
+"should minimize the worries of the predecessor attack."
+msgstr ""
+
+#: i2p2www/pages/site/docs/tunnels/unidirectional.html:73
+msgid "Anonymity"
+msgstr ""
+
+#: i2p2www/pages/site/docs/tunnels/unidirectional.html:75
+#, python-format
+msgid ""
+"A recent paper by Hermann and Grothoff\n"
+"declared that I2P's unidirectional tunnels \"seems to be a bad design "
+"decision\"."
+msgstr ""
+
+#: i2p2www/pages/site/docs/tunnels/unidirectional.html:80
+msgid ""
+"The paper's main point is that\n"
+"deanonymizations on unidirectional tunnels take a longer time, which is "
+"an \n"
+"advantage, but that an attacker can be more certain in the unidirectional"
+" case. \n"
+"Therefore, the paper claims it isn't an advantage at all, but a "
+"disadvantage, at least\n"
+"with long-living eepsites."
+msgstr ""
+
+#: i2p2www/pages/site/docs/tunnels/unidirectional.html:88
+msgid ""
+"This conclusion is not fully supported by the paper. Unidirectional "
+"tunnels clearly \n"
+"mitigate other attacks and it's not clear how to trade off the risk of "
+"the \n"
+"attack in the paper\n"
+"with attacks on a bidirectional tunnel architecture."
+msgstr ""
+
+#: i2p2www/pages/site/docs/tunnels/unidirectional.html:95
+msgid ""
+"This conclusion is based on an arbitrary certainty vs. time weighting \n"
+"(tradeoff) that may not be applicable in all cases. For \n"
+"example, somebody could make a list of possible IPs then issue subpoenas "
+"to \n"
+"each. Or the attacker could DDoS each in turn and via a simple \n"
+"intersection attack see if the eepsite goes down or is slowed down. So "
+"close \n"
+"may be good enough, or time may be more important."
+msgstr ""
+
+#: i2p2www/pages/site/docs/tunnels/unidirectional.html:104
+msgid ""
+"The conclusion is based on a specific weighting of the importance of "
+"certainty \n"
+"vs. time, and that weighting may be wrong, and it's definitely debatable,"
+" \n"
+"especially in a real world with subpoenas, search warrants, and other "
+"methods \n"
+"available for final confirmation."
+msgstr ""
+
+#: i2p2www/pages/site/docs/tunnels/unidirectional.html:111
+msgid ""
+"A full analysis of the tradeoffs of unidirectional vs. bidirectional \n"
+"tunnels is clearly outside the scope of the paper, and has not been done"
+" \n"
+"elsewhere. For example, how does this attack compare to the numerous "
+"possible \n"
+"timing attacks published about onion-routed networks? Clearly the authors"
+" have not\n"
+"done that analysis, if it's even possible to do it\n"
+"effectively."
+msgstr ""
+
+#: i2p2www/pages/site/docs/tunnels/unidirectional.html:120
+msgid ""
+"Tor uses bidirectional tunnels and has had a lot of academic review. I2P"
+" \n"
+"uses unidirectional tunnels and has had very little review. Does the lack"
+" of a \n"
+"research paper defending unidirectional tunnels mean that it is a poor "
+"design \n"
+"choice, or just that it needs more study? Timing attacks and \n"
+"distributed attacks are difficult to defend against in both I2P and Tor. "
+"The \n"
+"design intent (see references above) was that unidirectional tunnels are "
+"more \n"
+"resistant to timing attacks. However, the paper presents a somewhat "
+"different type of timing \n"
+"attack. Is this attack, innovative as it is, sufficient to label I2P's \n"
+"tunnel architecture (and thus I2P as a whole) a \"bad design\", and by \n"
+"implication clearly inferior to Tor, or is it just a design alternative "
+"that \n"
+"clearly needs further investigation and analysis? There are several other"
+" reasons \n"
+"to consider I2P currently inferior to Tor and other projects (small "
+"network \n"
+"size, lack of funding, lack of review) but is unidirectional tunnels "
+"really a \n"
+"reason?"
+msgstr ""
+
+#: i2p2www/pages/site/docs/tunnels/unidirectional.html:137
+msgid ""
+"In summary, \"bad design decision\" is apparently (since the paper does\n"
+"not label bidirectional tunnels \"bad\") shorthand for \"unidirectional \n"
+"tunnels are unequivocally inferior to bidirectional tunnels\", yet this \n"
+"conclusion is not supported by the paper."
+msgstr ""
+
diff --git a/i2p2www/translations/pt_BR/LC_MESSAGES/get-involved.po b/i2p2www/translations/pt_BR/LC_MESSAGES/get-involved.po
new file mode 100644
index 00000000..4f82af13
--- /dev/null
+++ b/i2p2www/translations/pt_BR/LC_MESSAGES/get-involved.po
@@ -0,0 +1,4091 @@
+# Portuguese (Brazil) translations for I2P.
+# Copyright (C) 2013 ORGANIZATION
+# This file is distributed under the same license as the I2P project.
+#
+# Translators:
+# blueboy, 2013
+msgid ""
+msgstr ""
+"Project-Id-Version: I2P\n"
+"Report-Msgid-Bugs-To: http://trac.i2p2.de\n"
+"POT-Creation-Date: 2013-11-21 23:32+0000\n"
+"PO-Revision-Date: 2013-11-24 17:31+0000\n"
+"Last-Translator: blueboy\n"
+"Language-Team: Portuguese (Brazil) "
+"(http://www.transifex.com/projects/p/I2P/language/pt_BR/)\n"
+"Plural-Forms: nplurals=2; plural=(n > 1)\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=utf-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"Generated-By: Babel 0.9.6\n"
+
+#: i2p2www/pages/site/get-involved/donate.html:2
+#: i2p2www/pages/site/get-involved/index.html:77
+msgid "Donate"
+msgstr "Faça uma doação"
+
+#: i2p2www/pages/site/get-involved/donate.html:4
+msgid ""
+"Thank you for your interest in contributing to I2P!\n"
+"The details of how you\n"
+"can make your contribution are provided below."
+msgstr ""
+"Obrigado pela disposição em contribuir com a I2P! Os detalhes de como "
+"fazer uma doação são fornecidos abaixo."
+
+#: i2p2www/pages/site/get-involved/donate.html:11
+#: i2p2www/pages/site/get-involved/donate.html:27
+#, python-format
+msgid ""
+"As of %(date)s, eche|on has been running a\n"
+"%(cointype)s account for the I2P project.\n"
+"If you'd like to donate using %(cointype)s, just transfer your\n"
+"desired amount of coins to the account %(account)s\n"
+"and leave eche|on a note if you'd like your donation to be\n"
+"mentioned on the I2P webpage."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/donate.html:22
+#: i2p2www/pages/site/get-involved/donate.html:38
+msgid "For easy usage, use the QR code below!"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/donate.html:44
+#, python-format
+msgid "You can donate direct via PayPal to the account \"%(account)s\"."
+msgstr ""
+"Você pode fazer uma doação diretamente via PayPal para a conta "
+"\"%(account)s\"."
+
+#: i2p2www/pages/site/get-involved/donate.html:50
+msgid "One time donation:"
+msgstr "Doe uma única vez:"
+
+#: i2p2www/pages/site/get-involved/donate.html:64
+msgid "Donate 10 €/month for 12 months:"
+msgstr "Doe 10 €/mês por 12 meses:"
+
+#: i2p2www/pages/site/get-involved/donate.html:72
+#: i2p2www/pages/site/get-involved/donate.html:84
+#: i2p2www/pages/site/get-involved/donate.html:96
+#: i2p2www/pages/site/get-involved/donate.html:108
+msgid "I2P donation "
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/donate.html:78
+msgid "Donate 20 €/month for 12 months:"
+msgstr "Doe 20 €/mês por 12 meses:"
+
+#: i2p2www/pages/site/get-involved/donate.html:90
+msgid "Donate 30 €/month for 12 months:"
+msgstr "Doe 30 €/mês por 12 meses:"
+
+#: i2p2www/pages/site/get-involved/donate.html:102
+msgid "Donate 50 €/month for 12 months:"
+msgstr "Doe 50 €/mês por 12 meses:"
+
+#: i2p2www/pages/site/get-involved/donate.html:117
+msgid "Flattr this"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/donate.html:122
+msgid ""
+"If you want to keep more or less anonymous, the option to send money via "
+"mail is also available. But it is less secure\n"
+"as the envelope can be lost on the way to us."
+msgstr ""
+"Se você quer manter-se mais ou menos anônimo, enviar dinheiro via correio"
+" é também uma opção. Mas é menos seguro, haja visto que o envelope pode "
+"ser extraviado."
+
+#: i2p2www/pages/site/get-involved/donate.html:126
+#, python-format
+msgid ""
+"If you'd like to donate via snail mail, send an email to %(email)s\n"
+" and you'll receive an email with instructions detailing how to proceed."
+msgstr ""
+"Se preferir doar via snail mail, envie um email para %(email)s que lhe enviaremos um email com instruções "
+"detalhando como proceder."
+
+#: i2p2www/pages/site/get-involved/donate.html:131
+#, python-format
+msgid ""
+"In the meantime, feel free to take a look at the generous donations that "
+"have been\n"
+"given in support of the I2P Project at the hall of fame."
+msgstr ""
+"Por ora, sinta-se livre para dar uma olhada nas generosas doações que "
+"foram dadas em apoio ao projeto I2P no salão "
+"da fama."
+
+#: i2p2www/pages/site/get-involved/index.html:2
+msgid "Get Involved!"
+msgstr "Envolva-se!"
+
+#: i2p2www/pages/site/get-involved/index.html:4
+msgid "We need your help!"
+msgstr "Nós precisamos da sua ajuda!"
+
+#: i2p2www/pages/site/get-involved/index.html:5
+msgid ""
+"To get involved, please feel free to join us on the #i2p IRC channel (on\n"
+"irc.freenode.net, or within I2P on irc.freshcoffee.i2p or "
+"irc.postman.i2p)."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/index.html:9
+#, python-format
+msgid ""
+"If you're interested in joining our team, please"
+" get in\n"
+"touch as we're always looking for eager contributors!"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/index.html:13
+msgid ""
+"We need help in many areas, and you don't need to know Java to "
+"contribute!\n"
+"Here's a list to help you get started!"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/index.html:18
+msgid "Spread the Word!"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/index.html:19
+msgid ""
+"Tell people about I2P on forums, blogs, and comments to articles.\n"
+"Fix up the Wikipedia article about I2P in your language.\n"
+"Tell your friends."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/index.html:24
+msgid "Testing"
+msgstr "Testando"
+
+#: i2p2www/pages/site/get-involved/index.html:25
+#, python-format
+msgid ""
+"Run the latest builds from monotone\n"
+"and report results on #i2p or as bugs on Trac."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/index.html:30
+msgid "Documentation"
+msgstr "Documentação"
+
+#: i2p2www/pages/site/get-involved/index.html:31
+msgid ""
+"Help fix the parts of the website that are outdated or incomplete.\n"
+"Translate pages into other languages."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/index.html:35
+msgid "Pictures"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/index.html:36
+msgid "Make some more pictures, fix the old ones on the website"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/index.html:39
+msgid "Content"
+msgstr "Conteúdo"
+
+#: i2p2www/pages/site/get-involved/index.html:40
+msgid "Make an eepsite! Add some content! Contribute to the community!"
+msgstr "Faça um eepsite! Adicione algum conteúdo! Contribua com a comunidade!"
+
+#: i2p2www/pages/site/get-involved/index.html:43
+msgid "Services"
+msgstr "Serviços"
+
+#: i2p2www/pages/site/get-involved/index.html:44
+msgid ""
+"Run a service on an eepsite. It could be a proxy, a forum, a tracker,\n"
+"a naming service, a search engine, an eepsite monitor... many of these\n"
+"aren't that hard."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/index.html:49
+msgid "Applications"
+msgstr "Aplicações"
+
+#: i2p2www/pages/site/get-involved/index.html:50
+#, python-format
+msgid ""
+"Write or port applications for I2P! There's some guidelines and\n"
+"a list of ideas on the applications page."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/index.html:54
+msgid "Coding"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/index.html:55
+#, python-format
+msgid ""
+"There's plenty to do if you know Java or are ready to learn.\n"
+"Check for open tickets on Trac\n"
+"or the TODO list on %(zzz)s for\n"
+"some ideas on where to start.\n"
+"See the new developer's guide for details."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/index.html:64
+msgid "Translation"
+msgstr "Tradução"
+
+#: i2p2www/pages/site/get-involved/index.html:65
+#, python-format
+msgid ""
+"Help translate the website and the software into your language.\n"
+"See the new translator's guide for details."
+msgstr ""
+"Ajude-nos a traduzir o website e o software para o seu idioma.\n"
+"Veja o guia para novos tradutores para "
+"detalhes."
+
+#: i2p2www/pages/site/get-involved/index.html:69
+msgid "Analysis"
+msgstr "Análise"
+
+#: i2p2www/pages/site/get-involved/index.html:70
+#, python-format
+msgid ""
+"Study or test the code to look for vulnerabilities.\n"
+"Both anonymity vulnerabilities from the various\n"
+"threat models,\n"
+"and DOS and other weaknesses due to securities holes,\n"
+"need researching."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/roadmap.html:2
+msgid "Roadmap"
+msgstr "Plano de ação"
+
+#: i2p2www/pages/site/get-involved/roadmap.html:7
+msgid ""
+"Include some seed data in the distribution so a central reseed location "
+"isn't required?"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/roadmap.html:10
+#, python-format
+msgid ""
+"Reachability Mapping / handle peers partially reachable / enhanced restricted routes"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/roadmap.html:13
+msgid "Improve help pages and website"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/roadmap.html:14
+msgid "More translations"
+msgstr "Mais traduções"
+
+#: i2p2www/pages/site/get-involved/roadmap.html:15
+msgid "SSU disconnect message"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/roadmap.html:16
+msgid "Iterative floodfill lookups"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/roadmap.html:21
+msgid "Full review of anonymity issues and other vulnerabilities"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/roadmap.html:22
+msgid ""
+"Reduce memory usage, remove debugging overhead, make it run better on "
+"slow and embedded machines"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/roadmap.html:25
+msgid "Docs"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/roadmap.html:30
+msgid "Full restricted routes"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/roadmap.html:35
+msgid "Tunnel mixing and padding"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/roadmap.html:36
+msgid "User defined message delays"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/roadmap.html:39
+#, python-format
+msgid ""
+"Please see the TODO list for more detailed info "
+"about some of these tasks."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/todo.html:2
+msgid "To Do List"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/todo.html:4
+msgid "I2P Project Targets"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/todo.html:5
+#, python-format
+msgid ""
+"Below is a more detailed (yet still incomplete) discussion of the major "
+"areas\n"
+"of future development on the core I2P network, spanning the plausibly "
+"planned\n"
+"releases. This does not include stego transports, porting to wireless "
+"devices,\n"
+"or tools to secure the local machine, nor does it include client "
+"applications\n"
+"that will be essential in I2P's success. There are probably other things "
+"that\n"
+"will come up, especially as I2P gets more peer review, but these are the "
+"main\n"
+"'big things'. See also the roadmap. Want to "
+"help?\n"
+"Get involved!"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/todo.html:16
+#: i2p2www/pages/site/get-involved/todo.html:54
+msgid "Core functionality"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/todo.html:16
+#: i2p2www/pages/site/get-involved/todo.html:28
+#: i2p2www/pages/site/get-involved/todo.html:52
+msgid "link"
+msgstr "linque"
+
+#: i2p2www/pages/site/get-involved/todo.html:18
+#: i2p2www/pages/site/get-involved/todo.html:57
+msgid "NAT/Firewall bridging via 1-hop restricted routes"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/todo.html:21
+#: i2p2www/pages/site/get-involved/todo.html:130
+msgid "High degree transport layer with UDP, NBIO, or NIO"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/todo.html:24
+#: i2p2www/pages/site/get-involved/todo.html:218
+msgid "NetworkDB and profile tuning and ejection policy for large nets"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/todo.html:28
+#: i2p2www/pages/site/get-involved/todo.html:242
+msgid "Security / anonymity"
+msgstr "Segurança / anonimato"
+
+#: i2p2www/pages/site/get-involved/todo.html:30
+#: i2p2www/pages/site/get-involved/todo.html:245
+msgid ""
+"Per-hop tunnel id & new permuted TunnelVerificationStructure "
+"encryption"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/todo.html:33
+#: i2p2www/pages/site/get-involved/todo.html:295
+msgid "Strict ordering of participants within tunnels"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/todo.html:36
+msgid "Randomly permuted tunnel lengths"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/todo.html:39
+#: i2p2www/pages/site/get-involved/todo.html:357
+msgid "Full blown n-hop restricted routes with optional trusted links"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/todo.html:42
+#: i2p2www/pages/site/get-involved/todo.html:376
+msgid "Hashcash for routerIdentity, destination, and tunnel request"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/todo.html:45
+#: i2p2www/pages/site/get-involved/todo.html:405
+msgid "Advanced tunnel operation (batching/mixing/throttling/padding)"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/todo.html:48
+#: i2p2www/pages/site/get-involved/todo.html:442
+msgid "Stop & go mix w/ garlics & tunnels"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/todo.html:52
+#: i2p2www/pages/site/get-involved/todo.html:456
+msgid "Performance"
+msgstr "Desempenho"
+
+#: i2p2www/pages/site/get-involved/todo.html:62
+msgid "Implemented in I2P 0.6.0.6"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/todo.html:63
+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:73
+msgid ""
+"Peers who have reachable interfaces - these peers do not need to \n"
+"do anything special"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/todo.html:77
+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:85
+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:90
+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:98
+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:109
+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:115
+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:121
+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:133
+msgid "Both UDP and NIO have been Implemented in I2P"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/todo.html:134
+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:145
+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:157
+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:162
+#, python-format
+msgid ""
+"Implemented in I2P 0.6 (\"SSU\") as documented elsewhere"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/todo.html:165
+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:172
+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:185
+msgid "It will be a lot of work though."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/todo.html:188
+msgid "NIO or NBIO"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/todo.html:189
+msgid "NIO Implemented in I2P 0.6.1.22 (\"NTCP\")"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/todo.html:192
+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:206
+#, 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:221
+msgid ""
+"Within the current network database and profile management "
+"implementation, \n"
+"we have taken the liberty of some practical shortcuts. For instance, we \n"
+"don't have the code to drop peer references from the K-buckets, as we \n"
+"don't have enough peers to even plausibly fill any of them, so instead, \n"
+"we just keep the peers in whatever bucket is appropriate. Another example"
+" \n"
+"deals with the peer profiles - the memory required to maintain each "
+"peer's \n"
+"profile is small enough that we can keep thousands of full blown profiles"
+" \n"
+"in memory without problems. While we have the capacity to use trimmed \n"
+"down profiles (which we can maintain 100s of thousands in memory), we \n"
+"don't have any code to deal with moving a profile from a \"minimal "
+"profile\" \n"
+"to a \"full profile\", a \"full profile\" to a \"minimal profile\", or to"
+" simply \n"
+"eject a profile altogether. It just wouldn't be practical to write that \n"
+"code yet, since we aren't going to need it for a while."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/todo.html:236
+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:248
+#: i2p2www/pages/site/get-involved/todo.html:332
+#, python-format
+msgid ""
+"Addressed in I2P 0.5 as documented elsewhere"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/todo.html:251
+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:261
+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:282
+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:298
+msgid "Implemented in release 0.6.2"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/todo.html:301
+#, 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:316
+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:321
+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:338
+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:350
+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:360
+msgid ""
+"The restricted route functionality described before was simply a "
+"functional \n"
+"issue - how to let peers who would not otherwise be able to communicate \n"
+"do so. However, the concept of allowing restricted routes includes "
+"additional \n"
+"capabilities. For instance, if a router absolutely cannot risk "
+"communicating \n"
+"directly with any untrusted peers, they can set up trusted links through"
+" \n"
+"those peers, using them to both send and receive all of its messages. \n"
+"Those hidden peers who want to be completely isolated would also refuse \n"
+"to connect to peers who attempt to get them to (as demonstrated by the \n"
+"garlic routing technique outlined before) - they can simply take the "
+"garlic \n"
+"clove that has a request for delivery to a particular peer and tunnel \n"
+"route that message out one of the hidden peer's trusted links with "
+"instructions \n"
+"to forward it as requested."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/todo.html:379
+#, python-format
+msgid ""
+"Within the network, we will want some way to deter people from consuming"
+" \n"
+"too many resources or from creating so many peers to mount a Sybil \n"
+"attack. Traditional techniques such as having a peer see who is "
+"requesting \n"
+"a resource or running a peer aren't appropriate for use within I2P, as \n"
+"doing so would compromise the anonymity of the system. Instead, we want \n"
+"to make certain requests \"expensive\"."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/todo.html:387
+msgid ""
+"Hashcash is one technique that \n"
+"we can use to anonymously increase the \"cost\" of doing certain "
+"activities, \n"
+"such as creating a new router identity (done only once on installation),"
+" \n"
+"creating a new destination (done only once when creating a service), or \n"
+"requesting that a peer participate in a tunnel (done often, perhaps 2-300"
+" \n"
+"times per hour). We don't know the \"correct\" cost of each type of "
+"certificate \n"
+"yet, but with some research and experimentation, we could set a base "
+"level \n"
+"that is sufficiently expensive while not an excessive burden for people \n"
+"with few resources."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/todo.html:398
+msgid ""
+"There are a few other algorithms that we can explore for making those \n"
+"requests for resources \"nonfree\", and further research on that front is"
+" \n"
+"appropriate."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/todo.html:408
+#, python-format
+msgid ""
+"To powerful passive external observers as well as large colluding "
+"internal \n"
+"observers, standard tunnel routing is vulnerable to traffic analysis "
+"attacks \n"
+"- simply watching the size and frequency of messages being passed between"
+" \n"
+"routers. To defend against these, we will want to essentially turn some \n"
+"of the tunnels into its own mix cascade - delaying messages received at \n"
+"the gateway and passing them in batches, reordering them as necessary, \n"
+"and injecting dummy messages (indistinguishable from other \"real\" "
+"tunnel \n"
+"messages by peers in the path). There has been a significant amount of \n"
+"research \n"
+"on these algorithms that we can lean on prior to implementing the various"
+" \n"
+"tunnel mixing strategies."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/todo.html:421
+msgid ""
+"In addition to the anonymity aspects of more varied tunnel operation, \n"
+"there is a functional dimension as well. Each peer only has a certain \n"
+"amount of data they can route for the network, and to keep any particular"
+" \n"
+"tunnel from consuming an unreasonable portion of that bandwidth, they \n"
+"will want to include some throttles on the tunnel. For instance, a tunnel"
+" \n"
+"may be configured to throttle itself after passing 600 messages (1 per \n"
+"second), 2.4MB (4KBps), or exceeding some moving average (8KBps for the \n"
+"last minute). Excess messages may be delayed or summarily dropped. With \n"
+"this sort of throttling, peers can provide ATM-like QoS support for their"
+" \n"
+"tunnels, refusing to agree to allocate more bandwidth than the peer has \n"
+"available."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/todo.html:434
+msgid ""
+"In addition, we may want to implement code to dynamically reroute tunnels"
+" \n"
+"to avoid failed peers or to inject additional hops into the path. This \n"
+"can be done by garlic routing a message to any particular peer in a "
+"tunnel \n"
+"with instructions to redefine the next-hop in the tunnel."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/todo.html:445
+msgid ""
+"Beyond the per-tunnel batching and mixing strategy, there are further \n"
+"capabilities for protecting against powerful attackers, such as allowing"
+" \n"
+"each step in a garlic routed path to define a delay or window in which \n"
+"it should be forwarded on. This would enable protections against the long"
+" \n"
+"term intersection attack, as a peer could send a message that looks "
+"perfectly \n"
+"standard to most peers that pass it along, except at any peers where the"
+" \n"
+"clove exposed includes delay instructions."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/todo.html:457
+#, python-format
+msgid ""
+"Performance related improvements are listed on the\n"
+"Performance page."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/arabic-trans.html:2
+msgid "Bounty Arabic translation of webpage and router console"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/arabic-trans.html:3
+#: i2p2www/pages/site/get-involved/bounties/index.html:119
+msgid "Arabic translation"
+msgstr "Tradução para o árabe"
+
+#: i2p2www/pages/site/get-involved/bounties/arabic-trans.html:6
+msgid ""
+"To improve I2P usage and attract more people\n"
+"into I2P echelon set out this bounty for translation\n"
+"of the I2P web page and I2P router console into Arabic."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/arabic-trans.html:12
+#: i2p2www/pages/site/get-involved/bounties/russian-trans.html:12
+msgid "This bounty is set into 2 subparts:"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/arabic-trans.html:14
+#: i2p2www/pages/site/get-involved/bounties/russian-trans.html:14
+msgid "Part 1 is translation of the webpage."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/arabic-trans.html:17
+msgid ""
+"For collecting the bounty of 20 BTC you need to translate the following "
+"pages:"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/arabic-trans.html:25
+msgid "This job was done by hamada and the bounty of 20 BTC was paid to hamada."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/arabic-trans.html:27
+msgid ""
+"Part 2 is the translation of the router console. The router console was\n"
+"partly translated and the bounty of 80 BTC was paid to hamada."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/arabic-trans.html:34
+msgid "Judge is echelon."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/btc-client.html:2
+msgid "Bounty creating a I2P native Bitcoin client"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/btc-client.html:3
+msgid "BTC I2P native client"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/btc-client.html:6
+msgid ""
+"For a future of I2P and attract more people\n"
+"into I2P this bounty is to create a I2P native Bitcoin client. \n"
+"It should integrate with other client via the I2P network and via "
+"gateways to\n"
+"the existant bitcoin network."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/btc-client.html:15
+msgid "Judge is psychonaut who donated the first 30 € to this bounty."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/datastore.html:2
+msgid "Bounty datastorage"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/datastore.html:3
+msgid "datastore"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/datastore.html:6
+msgid ""
+"To improve I2P's usage and to be independent of routers \n"
+"online status we want a datastorage as a extension to I2P.\n"
+"Like in Freenet the datastorage should be distributed and every\n"
+"participating node should be able to configure his options.\n"
+"The files should be saved in chunks and at least 2-3 times to\n"
+"obtain redundancy. Usage of storage space should be auto balanced.\n"
+"As it is a extra application, it should work flawless within I2P and\n"
+"cooperate nice with the I2P router. Maybe a integration within the\n"
+"webpage/router could be done."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/datastore.html:17
+msgid ""
+"This bounty cooperates with the 2 other bounties \"frost for I2P\" and \n"
+"\"eepsites in datastorage\"."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/datastore.html:21
+msgid ""
+"The frost for I2P datastorage bounty is paid for a frost like program \n"
+"with which files/messages are stored into database and got from database."
+"\n"
+"It needs to work with a GUI."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/datastore.html:26
+msgid ""
+"The eepsite served out of I2P datastorage extends a I2P router to send\n"
+"out eepsites out of the I2P datastorage. All files for eepsites need to "
+"be\n"
+"saved inside of datastorage and are taken from it.\n"
+"Extension:\n"
+"For better integration all datastorage participants could serve that "
+"eepsite."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/datastore.html:36
+msgid ""
+"For bounties to be declared done and paid, we need the program AND the "
+"source.\n"
+"Source and code need to be licensed under a free license (free to change "
+"and \n"
+"free to distribute)."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/deb-pack.html:2
+msgid "Bounty I2P package in Debian and Ubuntu mirrors"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/deb-pack.html:3
+msgid "I2P Ubuntu/Debian package"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/deb-pack.html:6
+msgid ""
+"For the future of I2P and in order to attract more people\n"
+"to I2P, this bounty was set for including an I2P package into the Ubuntu "
+"and Debian \n"
+"archive mirrors.\n"
+"To claim this bounty, the I2P router package needs to be available from\n"
+"Ubuntu and Debian archive mirrors and Debian bug \n"
+"448638 \n"
+"needs to be closed successfully."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/i2phex.html:2
+msgid "Bounty I2PHex code implementation"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/i2phex.html:3
+msgid "i2phex code implementation"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/i2phex.html:6
+msgid ""
+"To improve I2P usage and attract more people\n"
+"into I2PHex P2P ArneBab setout the bounty for implementing actual\n"
+"Phex code onto I2PHex."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/index.html:2
+msgid "Bounties"
+msgstr "Prêmios"
+
+#: i2p2www/pages/site/get-involved/bounties/index.html:5
+msgid "Bounties for I2P"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/index.html:6
+msgid ""
+"While we always gratefully accept any contributions of code, \n"
+"documentation, and the like, there are other ways to help I2P move \n"
+"forward. As with any open source project, our goals would be achieved "
+"more \n"
+"rapidly if we were able to support all of our contributors to work on \n"
+"I2P full time. However, as with any open source project, that's not a \n"
+"possibility. Instead, we are making use of a bounty system, whereby \n"
+"anyone can get support for working on something that people want \n"
+"implemented, and people who want to contribute to I2P can be assured that"
+" \n"
+"their support goes to what they care about."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/index.html:18
+msgid ""
+"We are also keeping open the ability for people who want to support I2P \n"
+"but don't have strong feelings about the bounties available. Those "
+"people\n"
+"can simply put their trust in the I2P team to do what we feel is best by\n"
+"donating to a catch-all general fund that will be used as deemed \n"
+"necessary - allocated to various bounties, covering incidentals (hosting,"
+" \n"
+"etc), and the like."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/index.html:27
+msgid "Current bounties"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/index.html:30
+#: i2p2www/pages/site/get-involved/bounties/index.html:92
+#: i2p2www/pages/site/get-involved/bounties/index.html:105
+msgid "Name"
+msgstr "Nome"
+
+#: i2p2www/pages/site/get-involved/bounties/index.html:30
+#: i2p2www/pages/site/get-involved/bounties/index.html:92
+#: i2p2www/pages/site/get-involved/bounties/index.html:105
+msgid "Status"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/index.html:30
+#: i2p2www/pages/site/get-involved/bounties/index.html:92
+msgid "Judge"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/index.html:30
+#: i2p2www/pages/site/get-involved/bounties/index.html:92
+msgid "Dev"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/index.html:30
+#: i2p2www/pages/site/get-involved/bounties/index.html:92
+msgid "Bounty"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/index.html:32
+msgid "Frost for I2P datastorage"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/index.html:33
+#: i2p2www/pages/site/get-involved/bounties/index.html:40
+#: i2p2www/pages/site/get-involved/bounties/index.html:47
+#: i2p2www/pages/site/get-involved/bounties/index.html:54
+#: i2p2www/pages/site/get-involved/bounties/index.html:75
+#: i2p2www/pages/site/get-involved/bounties/index.html:82
+msgid "Proposal in development"
+msgstr "Propostas em desenvolvimento"
+
+#: i2p2www/pages/site/get-involved/bounties/index.html:35
+#: i2p2www/pages/site/get-involved/bounties/index.html:42
+#: i2p2www/pages/site/get-involved/bounties/index.html:49
+#: i2p2www/pages/site/get-involved/bounties/index.html:56
+#: i2p2www/pages/site/get-involved/bounties/index.html:77
+#: i2p2www/pages/site/get-involved/bounties/index.html:97
+msgid "vacant"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/index.html:39
+msgid "Eepsites served out of I2P datastorage"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/index.html:46
+msgid "Backporting Phex code onto I2PHex"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/index.html:53
+msgid "I2P package in Debian and Ubuntu mirrors"
+msgstr "Pacote I2P nos repositórios do Debian e do Ubuntu"
+
+#: i2p2www/pages/site/get-involved/bounties/index.html:60
+msgid "Bitcoin client for I2P"
+msgstr "Cliente Bitcoin para a I2P"
+
+#: i2p2www/pages/site/get-involved/bounties/index.html:61
+msgid "Done, phase of verification"
+msgstr "Feito. Em fase de verificação."
+
+#: i2p2www/pages/site/get-involved/bounties/index.html:67
+msgid "Unit tests and Multi-router Simulation"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/index.html:68
+msgid "Partly done, partly in work, partly still open"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/index.html:89
+msgid "Hold bounties, set on hold due to jrandom AWOL and missing funding"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/index.html:94
+msgid "Bundling bounties"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/index.html:95
+msgid "Proposed"
+msgstr "Proposto"
+
+#: i2p2www/pages/site/get-involved/bounties/index.html:102
+msgid "Claimed bounties"
+msgstr "Prêmios reivindicados"
+
+#: i2p2www/pages/site/get-involved/bounties/index.html:105
+msgid "Dev team"
+msgstr "Time de desenvolvedores"
+
+#: i2p2www/pages/site/get-involved/bounties/index.html:107
+msgid "Make I2P IPv6 native"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/index.html:114
+msgid "Setting up a SILC server"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/index.html:124
+msgid "Datastore over I2P"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/index.html:129
+#: i2p2www/pages/site/get-involved/bounties/russian-trans.html:3
+msgid "Russian translation"
+msgstr "Tradução para o russo"
+
+#: i2p2www/pages/site/get-involved/bounties/index.html:134
+msgid "Swarming file transfer"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/index.html:139
+msgid "Streaming library window size"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/index.html:144
+msgid "IRC connect time monitor"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/index.html:149
+msgid "Unit tests (part 1)"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/index.html:161
+msgid ""
+"Dev lists anyone who may already be working on the bounty - collaboration"
+" is\n"
+"preferred, so if you're interested in working on it, please contact one "
+"of the\n"
+"people listed!"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/ipv6.html:2
+msgid "Bounty I2P IPv6 native"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/ipv6.html:3
+msgid "native IPv6 I2P"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/ipv6.html:6
+msgid ""
+"For a future of I2P and attract more people\n"
+"into I2P I withdrawal the vuze bounty and offer a IPv6 bounty.\n"
+"To claim this bounty, the I2P router needs to run full on native\n"
+"IPv6 connections like it does on IPv4."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/ipv6.html:17
+#: i2p2www/pages/site/get-involved/bounties/vuze-plugin.html:20
+msgid ""
+"For bounties to be declared done and paid, we need the plugin AND the "
+"source.\n"
+"Source and code need to be licensed under a free license (free to change "
+"and \n"
+"free to distribute)."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/netdb.html:2
+msgid "NetDB Backend"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/netdb.html:3
+msgid "netDB backend"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/netdb.html:7
+msgid ""
+"The current NetDB implementation (namely the FloodFill system)\n"
+"needs to be extended with another backend to improve reliability,\n"
+"reduce attack surface and solve the scalability issue for the \n"
+"coming years."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/netdb.html:14
+msgid ""
+"A solution likely based on a DHT will be investigated and \n"
+"finally implemented."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/russian-trans.html:2
+msgid "Bounty russian translation of webpage and router console"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/russian-trans.html:6
+msgid ""
+"To improve I2P usage and attract more people\n"
+"into I2P a anonymous donator set out the bounty for translation\n"
+"of the I2P web page and I2P router console into russian language."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/russian-trans.html:17
+msgid ""
+"For collecting the bounty of $115 USD you need to translate the following"
+" pages:"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/russian-trans.html:30
+msgid ""
+"Part 2 is the translation of the router console. The whole router console"
+" needs\n"
+"to be translated to collect the bounty of $115 USD."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/russian-trans.html:37
+msgid "Judge is the russian donor."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/silc.html:2
+msgid "Bounty migrate I2P IRC to SILC"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/silc.html:3
+msgid "I2P silc server"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/silc.html:7
+msgid ""
+"For a future of I2P and attract more people\n"
+"into I2P this bounty is to setup and host a I2P SILC server. \n"
+"This will allow people to send files over their messaging servers and "
+"have intrinsic security built into the protocol."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/silc.html:12
+msgid ""
+"A silc server needs to be set up and run for at least 3 month time to get"
+" payed. \n"
+"A second server should be set up, to."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/silc.html:16
+msgid ""
+"Bounty was withdrawn and money donated to returningnovice and general "
+"fund."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/silc.html:22
+msgid "Judge is An Anonymous Secret Society, society@mail.i2p."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/syndie-2012.html:2
+#: i2p2www/pages/site/get-involved/bounties/syndie-2012.html:3
+msgid "Syndie development"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/syndie-2012.html:7
+msgid ""
+"Beside of I2P we want to encourage users\n"
+"to care more about anonymity and security. As I2P is a low \n"
+"latency network with its natural limits, the software SYNDIE\n"
+"can overcome some of these limits and provide better anonymity\n"
+"for people who really need it."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/syndie-2012.html:14
+msgid ""
+"For our bad sake the syndie project was out of development for \n"
+"quite a long time yet (5 years). To get a fresh and new built \n"
+"with needed bugfixes we set out this bounty. Also syndie needs\n"
+"some enhancements and a better GUI for users to work with it.\n"
+"Current bounty sum is 50 Bitcoin."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/syndie-2012.html:22
+msgid ""
+"The latest Syndie coding rally did improve the situation of the\n"
+"Syndie package dramatically. A new Syndie package with bugfixes\n"
+"was created and made available on different webpages.\n"
+"As a result of this work, the bounty sum was reduced and\n"
+"the withdrawn money moved to the IPv6 bounty."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:2
+msgid "Bounty unittests"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:3
+msgid "unit test"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:7
+msgid ""
+"To improve I2P's maintainability, we want to have a solid set of\n"
+"automated unit tests for the critical code. While we do have some\n"
+"unit tests at the moment, they are ad-hoc and partly unfinished. \n"
+"This bounty is for someone to check the existing tests and move over\n"
+"old ones to jUnit, automate their execution, extend them to provide \n"
+"better code coverage, and publish the report online. Its a massive \n"
+"effort, but can be broken down into phases, listed below (phase 2 \n"
+"must occur first, but further phases may happen in any order).\n"
+"As this needs some reading of code, it is the best start point for\n"
+"new devs to get a good overview of I2P code and coding. A good job\n"
+"for college students, interns or anyone who is just interested."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:20
+msgid ""
+"Take care! Jobs and bounties shuffled a bit!\n"
+"Phase 6,7 and 8 are still open!"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:26
+#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:40
+#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:55
+#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:66
+#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:77
+#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:88
+#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:101
+#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:112
+#, python-format
+msgid "Phase %(phase)s:"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:27
+msgid "CI jenkins and IRC bot"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:28
+#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:42
+#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:57
+#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:68
+#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:79
+#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:90
+#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:103
+#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:114
+#, python-format
+msgid "Bounty: %(euro)s €"
+msgstr "Prêmio: %(euro)s €"
+
+#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:29
+msgid "server runs and this section is blocked"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:31
+msgid ""
+"To collect this bounty, a continuous integration server (Jenkins,\n"
+"old name was Hudson) must be set up and a connected IRC bot needs \n"
+"to set up in the channel #i2p-dev on IRC2p network to print out\n"
+"results of build tests.
\n"
+"The server needs to be run long term."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:41
+msgid "Check existing SDK tests"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:43
+#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:69
+msgid "paid to str4d"
+msgstr "pago a str4d"
+
+#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:45
+#, python-format
+msgid ""
+"To collect this bounty, the existing SDK tests must be checked \n"
+"and made to work again. The need to be integrated into the ant \n"
+"build scripts (\"ant test\"), and tied in with a code coverage tool (e.g."
+" \n"
+"Clover). The ant script\n"
+"must be capable of generating test status results as a web page, \n"
+"which will be published online."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:56
+msgid "SDK test coverage"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:58
+#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:80
+msgid "paid to unittests dev team"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:60
+msgid ""
+"To collect this bounty, the automated unit tests of the SDK \n"
+"(i2p/core/java/src) must work again."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:67
+msgid "Router test migration"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:71
+msgid ""
+"As with phase 2, the existing unit tests for the router must be\n"
+"moved over to the automated system."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:78
+msgid "Router test coverage"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:82
+msgid ""
+"To collect this bounty, the automated unit tests of the router \n"
+"(i2p/router/java/src) must work again."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:89
+msgid "Streaming lib tests"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:94
+msgid ""
+"To collect this bounty, a new set of unit tests must meet a \n"
+"measured code coverage of 90% of the streaming lib \n"
+"(i2p/apps/ministreaming/ and i2p/apps/streaming/)."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:102
+msgid "Unit tests coverage"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:106
+msgid ""
+"To collect this bounty, all above unit tests must meet the 100%\n"
+"coverage marker (except for log statements)."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:113
+msgid "MultiRouter simulation"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:115
+msgid "will be split in more sub-tasks"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:117
+msgid ""
+"To collect this bounty, the existing in-memory multi-router\n"
+"simulation must be checked, made work again and extend to simulate\n"
+"lots of routers in memory on a single machine. This bounty will\n"
+"be split in more fine grained subworks."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:126
+msgid ""
+"Judge on all these works is the donor and donor decides if a phase is\n"
+"called succesfull done and money can be paid."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/vuze-plugin.html:2
+msgid "Bounty I2P vuze plugin"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/vuze-plugin.html:3
+msgid "vuze plugin"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/vuze-plugin.html:6
+msgid ""
+"To improve I2P usage and attract more people\n"
+"into I2P torrent P2P I setout the bounty for a working I2P vuze\n"
+"plugin.\n"
+"The plugin needs to be official and submitted to vuze for publication\n"
+"on their webpage/repository for plugins.\n"
+"It should be easy to install and configured, work smooth and flawless.\n"
+"Configuration should be friendly to starters and made easy to be "
+"anonymous.\n"
+"It should work with *.b32.i2p destinations as with signed (516++ bits) \n"
+"destinations."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:2
+msgid "Application Development"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:3
+msgid "May 2013"
+msgstr "Maio de 2013"
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:6
+msgid "Application Development Guide"
+msgstr "Guia para o desenvolvimento de aplicativos"
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:8
+msgid "Contents"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:10
+#: i2p2www/pages/site/get-involved/develop/applications.html:16
+msgid "Why write I2P-specific code?"
+msgstr "Por que escrever código especificamente para a I2P?"
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:11
+#: i2p2www/pages/site/get-involved/develop/applications.html:102
+msgid "Important concepts"
+msgstr "Conceitos importantes"
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:12
+#: i2p2www/pages/site/get-involved/develop/applications.html:190
+msgid "Development options"
+msgstr "Opções de desenvolvimento"
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:13
+#: i2p2www/pages/site/get-involved/develop/applications.html:303
+msgid "Start developing - a simple guide"
+msgstr "Comece a desenvolver - um guia simples"
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:18
+#, python-format
+msgid ""
+"There are multiple ways to use applications in I2P.\n"
+"Using I2PTunnel,\n"
+"you can use regular applications without needing to program explicit I2P "
+"support.\n"
+"This is very effective for client-server scenario's,\n"
+"where you need to connect to a single website.\n"
+"You can simply create a tunnel using I2PTunnel to connect to that "
+"website, as shown in Figure 1."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:26
+msgid ""
+"If your application is distributed, it will require connections to a "
+"large amount of peers.\n"
+"Using I2PTunnel, you will need to create a new tunnel for each peer you "
+"want to contact,\n"
+"as shown in Figure 2.\n"
+"This process can of course be automated, but running a lot of I2PTunnel "
+"instances creates a large amount of overhead.\n"
+"In addition, with many protocols you will need to force everyone to \n"
+"use the same set of ports for all peers - e.g. if you want to reliably "
+"run DCC \n"
+"chat, everyone needs to agree that port 10001 is Alice, port 10002 is "
+"Bob, port \n"
+"10003 is Charlie, and so on, since the protocol includes TCP/IP specific "
+"information\n"
+"(host and port)."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:37
+msgid ""
+"General network applications often send a lot of additional data that "
+"could be used to identify users.\n"
+"Hostnames, port numbers, time zones, character sets, etc. are often sent "
+"without informing the user.\n"
+"As such, designing the network protocol specifically with anonymity in "
+"mind\n"
+"can avoid compromising user identities."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:43
+msgid ""
+"There are also efficiency considerations to review when determining how "
+"to \n"
+"interact on top of I2P. The streaming library and things built on top of"
+" it\n"
+"operate with handshakes similar to TCP, while the core I2P protocols "
+"(I2NP and I2CP)\n"
+"are strictly message based (like UDP or in some instances raw IP). The "
+"important\n"
+"distinction is that with I2P, communication is operating over a long fat "
+"network - \n"
+"each end to end message will have nontrivial latencies, but may contain "
+"payloads \n"
+"of up to several KB. An application that needs a simple request and "
+"response can get rid\n"
+"of any state and drop the latency incurred by the startup and teardown "
+"handshakes\n"
+"by using (best effort) datagrams without having to worry about MTU "
+"detection or \n"
+"fragmentation of messages."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:57
+#: i2p2www/pages/site/get-involved/develop/applications.html:59
+msgid ""
+"Creating a server-client connection using I2PTunnel only requires "
+"creating a single tunnel."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:59
+msgid "Figure 1:"
+msgstr "Figura 1:"
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:64
+#: i2p2www/pages/site/get-involved/develop/applications.html:66
+msgid ""
+"Setting up connections for a peer-to-peer applications requires a very "
+"large amount of tunnels."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:66
+msgid "Figure 2:"
+msgstr "Figura 2:"
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:70
+msgid "In summary, a number of reasons to write I2P-specific code:"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:74
+msgid ""
+"Creating a large amount of I2PTunnel instances consumes a non-trivial "
+"amount of resources,\n"
+"which is problematic for distributed applications (a new tunnel is "
+"required for each peer)."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:78
+msgid ""
+"General network protocols often send a lot of additional data that can be"
+" used to identify users.\n"
+"Programming specifically for I2P allows the creation of a network "
+"protocol\n"
+"that does not leak such information, keeping users anonymous and secure."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:83
+msgid ""
+"Network protocols designed for use on the regular internet can be "
+"inefficient\n"
+"on I2P, which is a network with a much higher latency."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:90
+#, python-format
+msgid ""
+"I2P supports a standard plugins interface for"
+" developers\n"
+"so that applications may be easily integrated and distributed."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:96
+msgid ""
+"Applications written in Java and accessible/runnable\n"
+"using an HTML interface via the standard webapps/app.war\n"
+"may be considered for inclusion in the i2p distribution."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:104
+msgid "There are a few changes that require adjusting to when using I2P:"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:108
+msgid "Destination ~= host+port"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:110
+msgid ""
+"An application running on I2P sends messages from and receives messages "
+"to a\n"
+"unique cryptographically secure end point - a \"destination\". In TCP or"
+" UDP\n"
+"terms, a destination could (largely) be considered the equivalent of a "
+"hostname\n"
+"plus port number pair, though there are a few differences."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:118
+msgid ""
+"An I2P destination itself is a cryptographic construct - all data sent to"
+" one is \n"
+"encrypted as if there were universal deployment of IPsec with the "
+"(anonymized)\n"
+"location of the end point signed as if there were universal deployment of"
+" DNSSEC."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:123
+msgid ""
+"I2P destinations are mobile identifiers - they can be moved from one I2P "
+"router\n"
+"to another (or it can even \"multihome\" - operate on multiple routers at"
+"\n"
+"once). This is quite different from the TCP or UDP world where a single "
+"end point (port)\n"
+"must stay on a single host."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:130
+msgid ""
+"I2P destinations are ugly and large - behind the scenes, they contain a "
+"2048 bit ElGamal\n"
+"public key for encryption, a 1024 bit DSA public key for signing, and a "
+"variable size \n"
+"certificate, which may contain proof of work or blinded data."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:135
+#, python-format
+msgid ""
+"There are existing ways to refer to these large and ugly destinations by "
+"short\n"
+"and pretty names (e.g. \"irc.duck.i2p\"), but those techniques do not "
+"guarantee\n"
+"globally uniqueness (since they're stored locally in a database on each "
+"person's machine)\n"
+"and the current mechanism is not especially scalable nor secure (updates "
+"to the host list are\n"
+"managed using \"subscriptions\" to naming services).\n"
+"There may be some secure, human readable, scalable, and globally \n"
+"unique, naming system some day, but applications shouldn't depend upon it"
+" being in place,\n"
+"since there are those who don't think such a beast is possible.\n"
+"Further information on the naming system is "
+"available."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:149
+#, python-format
+msgid ""
+"While most applications do not need to distinguish protocols and ports,\n"
+"I2P does support them. Complex applications may specify a "
+"protocol,\n"
+"from port, and to port, on a per-message basis, to multiplex traffic on\n"
+"a single destination.\n"
+"See the datagram page for details.\n"
+"Simple applications operate by listening for \"all protocols\" on \"all "
+"ports\" of a destination."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:158
+msgid "Anonymity and confidentiality"
+msgstr "Anonimato e confidencialidade"
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:160
+msgid ""
+"I2P has transparent end to end encryption\n"
+"and authentication for all data passed over the network - if Bob sends to"
+" Alice's destination,\n"
+"only Alice's destination can receive it, and if Bob is using the "
+"datagrams or streaming \n"
+"library, Alice knows for certain that Bob's destination is the one who "
+"sent the data."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:167
+msgid ""
+"Of course, I2P transparently anonymizes the\n"
+"data sent between Alice and Bob, but it does nothing to anonymize the "
+"content of what they\n"
+"send. For instance, if Alice sends Bob a form with her full name, "
+"government IDs, and \n"
+"credit card numbers, there is nothing I2P can do. As such, protocols and"
+" applications should \n"
+"keep in mind what information they are trying to protect and what "
+"information they are willing\n"
+"to expose."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:176
+msgid "I2P datagrams can be up to several KB"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:178
+#, python-format
+msgid ""
+"Applications that use I2P datagrams (either raw or repliable ones) can "
+"essentially be thought\n"
+"of in terms of UDP - the datagrams are unordered, best effort, and "
+"connectionless - but unlike\n"
+"UDP, applications don't need to worry about MTU detection and can simply "
+"fire off large datagrams.\n"
+"While the upper limit is nominally 32 KB, the message is fragmented for "
+"transport, thus dropping\n"
+"the reliability of the whole. Datagrams over about 10 KB are not "
+"currently recommended.\n"
+"See the datagram page for details.\n"
+"For many applications, 10 KB of data is sufficient for an\n"
+"entire request or response, allowing them to transparently operate in I2P"
+" as a UDP-like \n"
+"application without having to write fragmentation, resends, etc."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:192
+msgid ""
+"There are several means of sending data over I2P, each with their own "
+"pros and cons.\n"
+"The streaming lib is the recommended interface, used by the majority of "
+"I2P applications."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:197
+msgid "Streaming Lib"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:198
+#, python-format
+msgid ""
+"The full streaming library is now the "
+"standard\n"
+"interface. It allows programming using TCP-like sockets, as explained in "
+"the Streaming development guide."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:204
+#, python-format
+msgid ""
+"BOB is the Basic Open Bridge,\n"
+"allowing an application in any language to make streaming connections \n"
+"to and from I2P. At this point in time it lacks UDP support, but UDP "
+"support\n"
+"is planned in the near future. BOB also contains several tools, such as \n"
+"destination key generation, and verification that an address conforms to"
+" \n"
+"I2P specifications. Up to date info and applications that use BOB can be"
+" \n"
+"found at this eepsite."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:217
+msgid "SAM is not recommended. SAM V2 is okay, SAM V3 is recommended."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:218
+#, python-format
+msgid ""
+"SAM is the Simple Anonymous Messaging protocol, "
+"allowing an\n"
+"application written in any language to talk to a SAM bridge through a "
+"plain TCP socket and have\n"
+"that bridge multiplex all of its I2P traffic, transparently coordinating "
+"the encryption/decryption\n"
+"and event based handling. SAM supports three styles of operation:"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:225
+msgid ""
+"streams, for when Alice and Bob want to send data to each other reliably "
+"and in order"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:228
+msgid ""
+"repliable datagrams, for when Alice wants to send Bob a message that Bob "
+"can reply to"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:231
+msgid ""
+"raw datagrams, for when Alice wants to squeeze the most bandwidth and "
+"performance as possible,\n"
+"and Bob doesn't care whether the data's sender is authenticated or not "
+"(e.g. the data transferred\n"
+"is self authenticating)"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:237
+msgid ""
+"SAM V3 aims at the same goal as SAM and SAM V2, but does not require\n"
+"multiplexing/demultiplexing. Each I2P stream is handled by its own socket"
+" between the application\n"
+"and the SAM bridge. Besides, datagrams can be sent and received by the "
+"application through datagram\n"
+"communications with the SAM bridge."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:244
+#, python-format
+msgid ""
+"SAM V2 is a new version used by imule\n"
+"that fixes some of the problems in SAM.\n"
+"
\n"
+"SAM V3 is used by imule since version 1.4.0."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:252
+msgid ""
+"The I2PTunnel application allows applications to build specific TCP-like "
+"tunnels to peers \n"
+"by creating either I2PTunnel 'client' applications (which listen on a "
+"specific port and connect\n"
+"to a specific I2P destination whenever a socket to that port is opened) "
+"or I2PTunnel 'server'\n"
+"applications (which listen to a specific I2P destination and whenever it "
+"gets a new I2P \n"
+"connection it outproxies to a specific TCP host/port). These streams are"
+" 8-bit clean, and are\n"
+"authenticated and secured through the same streaming library that SAM "
+"uses, but there is a \n"
+"nontrivial overhead involved with creating multiple unique I2PTunnel "
+"instances, since each have\n"
+"their own unique I2P destination and their own set of tunnels, keys, etc."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:264
+msgid ""
+"I2P supports a SOCKS V4 and V5 proxy.\n"
+"Outbound connections work well. Inbound (server) and UDP functionality "
+"may be incomplete\n"
+"and untested."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:271
+msgid "Removed"
+msgstr "Removido"
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:272
+msgid ""
+"There used to be a simple \"ministreaming\" library,\n"
+"but now ministreaming.jar contains only the interfaces for the full "
+"streaming library."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:277
+msgid "Datagrams"
+msgstr "Datagramas"
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:278
+msgid "Recommended for UDP-like applications"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:279
+#, python-format
+msgid ""
+"The Datagram library allows sending UDP-"
+"like packets.\n"
+"It's possible to use:"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:284
+msgid "Repliable datagrams"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:285
+msgid "Raw datagrams"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:289
+msgid "Not recommended"
+msgstr "Não recomendado"
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:290
+#, python-format
+msgid ""
+"I2CP itself is a language independent protocol, "
+"but to implement an I2CP library \n"
+"in something other than Java there is a significant amount of code to be "
+"written (encryption routines, \n"
+"object marshalling, asynchronous message handling, etc). While someone "
+"could write an I2CP library in \n"
+"C or something else, it would most likely be more useful to use the C SAM"
+" library instead."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:297
+msgid "Web Applications"
+msgstr "Aplicações para a Web"
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:298
+msgid ""
+"I2P comes with the Jetty webserver, and configuring to use the Apache "
+"server instead is straightforward.\n"
+"Any standard web app technology should work."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:304
+msgid ""
+"Developing using I2P requires a working I2P installation and a "
+"development environment of your own choice.\n"
+"If you are using Java, you can start development with the streaming library or datagram library.\n"
+"Using another programming language, SAM or BOB can be used."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:310
+msgid "Developing with the streaming library"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:312
+msgid ""
+"The following example shows how to create TCP-like client and server "
+"applications\n"
+"using the streaming library."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:317
+msgid "This will require the following libraries in your classpath:"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:321
+msgid "The streaming library itself"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:322
+msgid "Factory and interfaces for the streaming library"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:323
+msgid "Standard I2P classes, data structures, API, and utilities"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:326
+msgid ""
+"Network communication requires the usage of I2P network sockets.\n"
+"To demonstrate this, we will create an application where a client can "
+"send text messages to a server,\n"
+"who will print the messages and send them back to the client. In other "
+"words, the server will function as an echo."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:331
+msgid ""
+"We will start by initializing the server application. This requires "
+"getting an I2PSocketManager\n"
+"and creating an I2PServerSocket.\n"
+"We will not provide the I2PSocketManagerFactory with the saved keys for "
+"an existing Destination,\n"
+"so it will create a new Destination for us.\n"
+"So we will ask the I2PSocketManager for an I2PSession, so we can find out"
+" the Destination that\n"
+"was created, as we will need to copy and paste that information later so "
+"the client can connect to us."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:362
+msgid "Code example 1: initializing the server application."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:364
+msgid ""
+"Once we have an I2PServerSocket, we can create I2PSocket instances to "
+"accept connections from clients.\n"
+"In this example, we will create a single I2PSocket instance, that can "
+"only handle one client at a time.\n"
+"A real server would have to be able to handle multiple clients.\n"
+"To do this, multiple I2PSocket instances would have to be created, each "
+"in separate threads.\n"
+"Once we have created the I2PSocket instance, we read data, print it and "
+"send it back to the client.\n"
+"The bold code is the new code we add."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:448
+msgid "Code example 2: accepting connections from clients and handling messages."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:452
+msgid ""
+"When you run the above server code, it should print something like this "
+"(but without the line endings, it should just be\n"
+"one huge block of characters):"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:466
+msgid ""
+"This is the base64-representation of the server Destination. The client "
+"will need this string to reach the server."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:470
+msgid ""
+"Now, we will create the client application. Again, a number of steps are "
+"required for initialization.\n"
+"Again, we will need to start by getting an I2PSocketManager.\n"
+"We won't use an I2PSession and an I2PServerSocket this time.\n"
+"Instead, we will use the server Destination string to start our "
+"connection.\n"
+"We will ask the user for the Destination string, and create an I2PSocket "
+"using this string.\n"
+"Once we have an I2PSocket, we can start sending and receiving data to and"
+" from the server."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:554
+msgid ""
+"Code example 3: starting the client and connecting it to the server "
+"application."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:556
+msgid ""
+"Finally, you can run both the server and the client application.\n"
+"First, start the server application. It will print a Destination string "
+"(like shown above).\n"
+"Next, start the client application. When it requests a Destination "
+"string, you can enter the string printed by the server.\n"
+"The client will then send 'Hello I2P!' (along with a newline) to the "
+"server, who will print the message and send it back to the client."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:562
+msgid "Congratulations, you have successfully communicated over I2P!"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:566
+msgid "Existing Applications"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:567
+msgid "Contact us if you would like to contribute."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:588
+msgid "Application Ideas"
+msgstr "Idéias para aplicativos"
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:590
+msgid "NNTP server - there have been some in the past, none at the moment"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:593
+msgid ""
+"Jabber server - there have been some in the past, and there is one at the"
+" moment, with access to the public internet"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:596
+msgid "PGP Key server and/or proxy"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:599
+msgid ""
+"Content Distribution / DHT applications - resurrect feedspace,\n"
+"port dijjer, look for alternatives"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:603
+msgid "Help out with Syndie development"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:606
+msgid ""
+"Web-based applications - The sky is the limit for hosting web-server-"
+"based\n"
+"applications such as blogs, pastebins, storage, tracking, feeds, etc.\n"
+"Any web or CGI technology such as Perl, PHP, Python, or Ruby will work."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:611
+msgid ""
+"Resurrect some old apps, several previously in the i2p source package -\n"
+"bogobot, pants, proxyscript, q, stasher, socks proxy, i2ping, feedspace"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/developers-keys.html:2
+msgid "I2P Developer's MTN Keys"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/developers-keys.html:4
+msgid "MTN Keys"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/developers-keys.html:5
+msgid ""
+"Monotone servers used by the I2P project require two types of keys to be "
+"used."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/developers-keys.html:9
+msgid ""
+"Commit Keys to sign changes checked-in to the "
+"respository; and"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/developers-keys.html:10
+msgid ""
+"Transport Keys to push changes to remote "
+"servers."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/developers-keys.html:13
+#, python-format
+msgid ""
+"Everyone that uses Monotone to checkout the I2P codebase will need to\n"
+"import the\n"
+"developer commit keys, but only Monotone \n"
+"server operators will need to import the transport keys."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/developers-keys.html:20
+msgid "Developer Commit keys"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/developers-keys.html:255
+msgid "Developer Transport Keys"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/developers-keys.html:256
+#, python-format
+msgid ""
+"Note: Transport keys are only needed for setting up a\n"
+"Monotone server."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/license-agreements.html:2
+msgid "License Agreements"
+msgstr "Acordos de Licença"
+
+#: i2p2www/pages/site/get-involved/develop/license-agreements.html:5
+#, python-format
+msgid "For more information see the licenses page."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/license-agreements.html:8
+msgid ""
+"Following is a monotonerc file defining the current trust list.\n"
+"Developers must use this file in ~/.monotone/monotonerc or\n"
+"_MTN/montonerc in their i2p.i2p workspace."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/license-agreements.html:17
+msgid "Agreements"
+msgstr "Acordos"
+
+#: i2p2www/pages/site/get-involved/develop/licenses.html:2
+#: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:115
+msgid "Licenses"
+msgstr "Licenças"
+
+#: i2p2www/pages/site/get-involved/develop/licenses.html:4
+msgid "I2P Software Licenses"
+msgstr "I2P - Licenças de software"
+
+#: i2p2www/pages/site/get-involved/develop/licenses.html:5
+#, python-format
+msgid ""
+"As required by our\n"
+"threat model (among other reasons), the \n"
+"software developed to support the anonymous communication \n"
+"network we call I2P must be freely available, open source, \n"
+"and user modifiable. To meet these criteria, we make use of\n"
+"a variety of legal and software engineering techniques so\n"
+"as to remove as many barriers to entry for those considering\n"
+"making use of or contributing to the I2P effort."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/licenses.html:16
+msgid ""
+"While the information below may be more confusing than just simply \n"
+"stating \"I2P is BSD\", \"I2P is GPL\", or \"I2P is public domain\",\n"
+"the short answer to the question \"How is I2P licensed?\" is this:"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/licenses.html:22
+msgid "All software bundled in the I2P distributions will allow:"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/licenses.html:24
+msgid "use without fee"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/licenses.html:25
+msgid ""
+"use with no restrictions on how, when, where, why, or by whom is running "
+"it"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/licenses.html:26
+msgid "access to the source code without fee"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/licenses.html:27
+msgid "modifications to the source"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/licenses.html:30
+msgid ""
+"Most of the software guarantees much more - the ability of anyone "
+"to \n"
+"distribute the modified source however they choose. However, not all of "
+"the \n"
+"software bundled provides this freedom - the GPL restricts the ability of"
+" \n"
+"developers who wish to integrate I2P with their own applications that are"
+" not \n"
+"themselves open source applications. While we applaud the noble goals of"
+" \n"
+"increasing the resources in the commons, I2P is best served by removing "
+"any\n"
+"barriers that stand in the way of its adoption - if a developer "
+"considering whether\n"
+"they can integrate I2P with their application has to stop and check with "
+"their lawyer,\n"
+"or conduct a code audit to make sure their own source can be released as "
+"GPL-compatible,\n"
+"we lose out."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/licenses.html:43
+msgid "Component licenses"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/licenses.html:44
+msgid ""
+"The I2P distribution contains several resources, reflecting the "
+"partitioning of \n"
+"the source code into components. Each component has its own license, "
+"which all \n"
+"developers who contribute to it agree to - either by explicitly declaring"
+" the release\n"
+"of code committed under a license compatible with that component, or by "
+"implicitly\n"
+"releasing the code committed under the component's primary license. Each"
+" of these \n"
+"components has a lead developer who has the final say as to what license "
+"is compatible\n"
+"with the component's primary license, and the I2P project manager has the"
+" final say as\n"
+"to what licenses meet the above four guarantees for inclusion in the I2P "
+"distribution."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/licenses.html:57
+msgid "Component"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/licenses.html:58
+msgid "Source path"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/licenses.html:59
+msgid "Resource"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/licenses.html:60
+msgid "Primary license"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/licenses.html:61
+msgid "Alternate licenses"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/licenses.html:62
+msgid "Lead developer"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/licenses.html:271
+msgid "GPL + java exception"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/licenses.html:272
+#, python-format
+msgid ""
+"While it may be redundant, just for clarity the\n"
+"GPL'ed code included within\n"
+"I2PTunnel and other apps must be released under the GPL with an "
+"additional \"exception\"\n"
+"explicitly authorizing the use of Java's standard libraries:"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/licenses.html:288
+msgid ""
+"All source code under each component will by default be licensed under "
+"the\n"
+"primary license, unless marked otherwise in the code. All of the above "
+"is\n"
+"summary of the license terms - please see the specific license for the "
+"component\n"
+"or source code in question for authoritative terms. Component source "
+"locations and\n"
+"resource packaging may be changed if the repository is reorganized."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/licenses.html:296
+msgid "Commit privileges"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/licenses.html:297
+#, python-format
+msgid ""
+"Developers may push changes to a distributed monotone repository if you\n"
+"receive permission from the person running that repository.\n"
+"See the Monotone Page for details."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/licenses.html:303
+msgid ""
+"However, to have changes included in a release, developers\n"
+"must be trusted by the release manager (currently zzz).\n"
+"In addition, they must explicitly agree with the above terms to be "
+"trusted.\n"
+"That means that they must send one of the release managers a signed "
+"message affirming that:"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/licenses.html:310
+msgid ""
+"Unless marked otherwise, all code I commit is implicitly licensed under\n"
+"the component's primary license"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/licenses.html:314
+msgid ""
+"If specified in the source, the code may be explicitly licensed under one"
+"\n"
+"of the component's alternate licenses"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/licenses.html:318
+msgid ""
+"I have the right to release the code I commit under the terms I\n"
+"am committing it"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/licenses.html:324
+#, python-format
+msgid ""
+"If anyone is aware of any instances where the above conditions are not "
+"met,\n"
+"please contact the component lead and/or an I2P release manager with "
+"further\n"
+"information.\n"
+"See developers' license agreements."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/release-signing-key.html:2
+msgid "Release Signing Key"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/release-signing-key.html:4
+msgid "Releases 0.7.6 and later are signed by zzz. His public key is:"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/release-signing-key.html:40
+msgid ""
+"Releases 0.6.1.31 through 0.7.5 were signed by Complication. His public "
+"key is:"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/signed-keys.html:2
+msgid "Signed Developer Keys"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/signed-keys.html:4
+msgid ""
+"Keys for zzz, Complication and welterde are provided clearsigned. The key"
+" for jrandom must be\n"
+"verified differently, since he's away, and only left a binary detached\n"
+"signature for his key."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/signed-keys.html:10
+#: i2p2www/pages/site/get-involved/develop/signed-keys.html:16
+msgid "Monotone keys for zzz"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/signed-keys.html:11
+#: i2p2www/pages/site/get-involved/develop/signed-keys.html:47
+msgid "Monotone keys for welterde"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/signed-keys.html:12
+#: i2p2www/pages/site/get-involved/develop/signed-keys.html:79
+msgid "Monotone keys for Complication"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/signed-keys.html:13
+#: i2p2www/pages/site/get-involved/develop/signed-keys.html:114
+msgid "Monotone keys for jrandom"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/signed-keys.html:14
+#: i2p2www/pages/site/get-involved/develop/signed-keys.html:169
+msgid "Others"
+msgstr "Outros"
+
+#: i2p2www/pages/site/get-involved/develop/signed-keys.html:17
+msgid ""
+"Tip: To find zzz's GPG key, on his eepsite locate the key "
+"`0xA76E0BED`, with\n"
+"the name `zzz@mail.i2p` and the fingerprint `4456 EBBE C805 63FE 57E6 "
+"B310 4155\n"
+"76BA A76E 0BED`."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/signed-keys.html:49
+msgid ""
+"Tip: To find welterde's GPG key, on public keyservers locate the "
+"key\n"
+"`0x62E011A1`, with the name `welterde@arcor.de` and the fingerprint `6720"
+" FD81\n"
+"3872 6DFC 6016 64D1 EBBC 0374 62E0 11A1`."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/signed-keys.html:81
+msgid ""
+"Tip: To find Complication's GPG key, on his eepsite locate the key"
+"\n"
+"`0x79FCCE33`, with the name `complication@mail.i2p` and the fingerprint "
+"`73CF\n"
+"2862 87A7 E7D2 19FF DB66 FA1D FC6B 79FC CE33`."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/signed-keys.html:116
+msgid ""
+"Tip: To find jrandom's GPG key for Syndie releases, on public "
+"keyservers locate\n"
+"the key `0x393F2DF9`, with the name `syndie-dist-key@i2p.net` and the\n"
+"fingerprint `AE89 D080 0E85 72F0 B777 B2ED C2FA 68C0 393F 2DF9`."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/signed-keys.html:122
+msgid ""
+"Jrandom had to leave unexpectedly in the end of 2007. His commit key was\n"
+"deployed in the Syndie Monotone repository, in a file named `mtn-"
+"committers`.\n"
+"That file also had a GPG signature, `mtn-committers.sig`, but it was a "
+"binary\n"
+"detached signature. I am going to supply both files in GPG ASCII-armoured"
+" form\n"
+"below."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/signed-keys.html:130
+msgid ""
+"First, the file `mtn-committers` containing jrandom's Monotone key. Save "
+"as\n"
+"`mtn-committers.asc` and unpack it using `gpg --output mtn-committers "
+"--dearmor\n"
+"mtn-committers.asc`:"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/signed-keys.html:151
+msgid ""
+"Now the file `mtn-committers.sig`, containing the GPG signature. Save as\n"
+"`mtn-committers.sig.asc` and unpack it using `gpg --output mtn-"
+"committers.sig\n"
+"--dearmor mtn-committers.sig.asc`. Use it to verify the above supplied\n"
+"`mtn-committers` file:"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/signed-keys.html:170
+#, python-format
+msgid ""
+"Some of the developers have included their Monotone keys in their signed license agreement."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:2
+msgid "Developer Guidelines and Coding Style"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:4
+#, python-format
+msgid "Read the new developers guide first."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:8
+msgid "Basic Guidelines and Coding Style"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:10
+msgid ""
+"Most of the following should be common sense for anybody who has worked "
+"on open source or in a commercial\n"
+"programming envrionment.\n"
+"The following applies mostly to the main development branch i2p.i2p.\n"
+"Guidelines for other branches, plugins, and external apps may be "
+"substantially different;\n"
+"check with the appropriate developer for guidance."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:18
+msgid "Community"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:20
+msgid ""
+"Please don't just \"write code\". If you can, participate in other "
+"development activities, including:\n"
+"development discussions and support on IRC, zzz.i2p, and forum.i2p; "
+"testing;\n"
+"bug reporting and responses; documentation; code reviews; etc."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:25
+msgid ""
+"Active devs should be available periodically on IRC #i2p-dev.\n"
+"Be aware of the current release cycle.\n"
+"Adhere to release milestones such as feature freeze, tag freeze, and\n"
+"the checkin deadline for a release."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:35
+msgid ""
+"Have a basic understanding of distributed source control systems, even if"
+" you haven't\n"
+"used monotone before. Ask for help if you need it.\n"
+"Once pushed, checkins are forever, there is no undo. Please be careful.\n"
+"If you have not used monotone before, start with baby steps.\n"
+"Check in some small changes and see how it goes."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:42
+msgid ""
+"Test your changes before checking them in.\n"
+"If you prefer the checkin-before-test development model,\n"
+"use your own development branch (e.g. i2p.i2p.yourname.test)\n"
+"and propagate back to i2p.i2p once it is working well.\n"
+"Do not break the build. Do not cause regressions.\n"
+"In case you do (it happens), please do not vanish for a long period after"
+"\n"
+"you push your change."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:51
+msgid ""
+"If your change is non-trivial, or you want people to test it and need "
+"good test reports\n"
+"to know whether your change was tested or not, add a checkin comment to "
+"history.txt\n"
+"and increment the build revision in RouterVersion.java."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:56
+msgid ""
+"Ensure that you have the latest monotonerc file in _MTN.\n"
+"Do not check in on top of untrusted revisions."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:60
+msgid ""
+"Ensure that you pull the latest revision before you check in.\n"
+"If you inadvertently diverge, merge and push as soon as possible.\n"
+"Don't routinely make others merge for you.\n"
+"Yes, we know that monotone says you should push and then merge,\n"
+"but in our experience, in-workspace merge works just as well as in-"
+"database merge,\n"
+"without creating a merge revision."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:68
+msgid ""
+"Do not check in major changes into the main i2p.i2p branch late in the "
+"release cycle.\n"
+"If a project will take you more than a couple days, create your own "
+"branch in monotone\n"
+"and do the development there so you do not block releases."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:75
+msgid "Coding Style"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:77
+msgid ""
+"Coding style throughout most of the code is 4-spaces for indentation. Do "
+"not use tabs.\n"
+"Do not reformat code. If your IDE or editor wants to reformat everything,"
+" get control of it.\n"
+"Yes, we know 4 spaces is a pain, but perhaps you can configure your "
+"editor appropriately.\n"
+"In some places, the coding style is different.\n"
+"Use common sense. Emulate the style in the file you are modifying."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:84
+msgid ""
+"New classes and methods require at least brief javadocs. Add @since "
+"release-number."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:87
+msgid ""
+"Classes in core/ (i2p.jar) and portions of i2ptunnel are part of our "
+"official API.\n"
+"There are several out-of-tree plugins and other applications that rely on"
+" this API.\n"
+"Be careful not to make any changes that break compatibility.\n"
+"Don't add methods to the API unless they are of general utility.\n"
+"Javadocs for API methods should be clear and complete.\n"
+"If you add or change the API, also update the documentation on the "
+"website (i2p.www branch)."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:95
+msgid ""
+"Tag strings for translation where appropriate.\n"
+"Don't change existing tagged strings unless really necessary, as it will "
+"break existing translations.\n"
+"Do not add or change tagged strings after the \"tag freeze\" in the "
+"release cycle so that\n"
+"translators have a chance to update before the release."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:101
+msgid ""
+"Use generics and concurrent classes where possible. I2P is a highly "
+"multi-threaded application."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:104
+msgid ""
+"We require Java 6 to build but only Java 5 to run I2P.\n"
+"Do not use Java 6 classes or methods without handling the class not found"
+" exceptions\n"
+"and providing alternate Java 5 code. See classes in net.i2p.util for "
+"examples."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:109
+msgid ""
+"Explicitly convert between primitive types and classes;\n"
+"don't rely on autoboxing/unboxing."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:117
+msgid ""
+"Only check in code that you wrote yourself.\n"
+"Before checking in any code or library jars from other sources,\n"
+"justify why it is necessary,\n"
+"verify the license is compatible,\n"
+"and obtain approval from the lead developer."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:124
+msgid ""
+"For any images checked in from external sources,\n"
+"it is your responsibility to first verify the license is compatible.\n"
+"Include the license and source information in the checkin comment."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:131
+msgid "Bugs"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:133
+#, python-format
+msgid ""
+"Managing Trac tickets is everybody's job, please help.\n"
+"Monitor %(trac)s for tickets you have been assigned or can help with.\n"
+"Assign, categorize, comment on, fix, or close tickets if you can."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:138
+msgid ""
+"Close a ticket when you think you've fixed it.\n"
+"We don't have a test department to verify and close tickets.\n"
+"If you arent sure you fixed it, close it and add a note saying\n"
+"\"I think I fixed it, please test and reopen if it's still broken\".\n"
+"Add a comment with the dev build number or revision and set\n"
+"the milestone to the next release."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/ides.html:2
+msgid "Using an IDE with I2P"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/ides.html:4
+msgid ""
+"The main I2P development branch (i2p.i2p) has been set up to"
+" enable developers to easily set up two of the commonly-used IDEs for "
+"Java development: Eclipse and NetBeans."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/ides.html:10
+msgid ""
+"The main I2P development branches (i2p.i2p and branches from"
+" it) contain .project and .classpath Eclipse files, to enable the branch "
+"to be easily set up in Eclipse."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/ides.html:16
+msgid ""
+"Check out the I2P branch into some directory (e.g. "
+"$HOME/dev/i2p.i2p)."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/ides.html:20
+msgid ""
+"Open Eclipse and create a new Workspace, based in the directory that the "
+"I2P branch was checked out to."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/ides.html:24
+msgid ""
+"Select \"File - Import...\" and then under \"General\" select \"Existing "
+"Projects into Workspace\"."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/ides.html:28
+msgid ""
+"For \"Select root directory:\" choose the directory that the I2P branch "
+"was checked out to."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/ides.html:32
+msgid "If necessary, click \"Refresh\" to refresh the list of projects."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/ides.html:36
+msgid "Select every project in the list, and click \"Finish\"."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/ides.html:40
+msgid ""
+"Done! Your workspace should now contain all projects within the I2P "
+"branch, and their build dependencies should be correctly set up."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/ides.html:48
+msgid ""
+"The main I2P development branches (i2p.i2p and branches from"
+" it) contain NetBeans project files."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:2
+msgid "Monotone"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:4
+msgid "Monotone Guide"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:9
+msgid "Operating a Monotone client"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:11
+#: i2p2www/pages/site/get-involved/guides/monotone.html:63
+msgid "Generating Monotone keys"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:12
+msgid "Trust and initializing your repository"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:13
+#: i2p2www/pages/site/get-involved/guides/monotone.html:196
+msgid "Obtaining and deploying developers' keys"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:14
+#: i2p2www/pages/site/get-involved/guides/monotone.html:227
+msgid "Setting up trust evaluation hooks"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:15
+#: i2p2www/pages/site/get-involved/guides/monotone.html:268
+msgid ""
+"Pulling the i2p.i2p, i2p.www and "
+"i2p.syndie branches"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:16
+#: i2p2www/pages/site/get-involved/guides/monotone.html:308
+msgid "Verifying that trust evaluation works"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:17
+#: i2p2www/pages/site/get-involved/guides/monotone.html:357
+msgid "Checking out a working copy of the latest version"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:18
+#: i2p2www/pages/site/get-involved/guides/monotone.html:384
+msgid "Updating your working copy to the latest version"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:22
+#: i2p2www/pages/site/get-involved/guides/monotone.html:414
+msgid "Operating a Monotone Server"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:24
+msgid "Obtaining and deploying developers’ transport keys"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:25
+#: i2p2www/pages/site/get-involved/guides/monotone.html:424
+msgid "Granting push and pull access"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:26
+#: i2p2www/pages/site/get-involved/guides/monotone.html:469
+msgid "Running Monotone in server mode"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:27
+#: i2p2www/pages/site/get-involved/guides/monotone.html:494
+msgid "Differences under Debian GNU/Linux"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:34
+#, python-format
+msgid ""
+"This is a revised version of Complication's original\n"
+" guide detailing the use of Monotone in I2P development.\n"
+" For basic instructions see the quick-start "
+"guide."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:42
+#, python-format
+msgid ""
+"I2P has a distributed development model. The source code is replicated "
+"across\n"
+" independently administered Monotone (\"MTN\") repositories.\n"
+" Developers with commit rights are able to push their changes to the "
+"repository\n"
+" (a license agreement needs to be "
+"signed\n"
+" before commit rights are granted)."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:52
+msgid ""
+"Some of Monotone's noteworthy qualities are: distributed\n"
+" version control, cryptographic authentication, access control, its "
+"small size, having few\n"
+" dependencies, storage of projects in a compressed SQLite database file,"
+" and\n"
+" having the ability to resume interrupted synchronization attempts."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:61
+msgid "Operating a Monotone Client"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:66
+msgid ""
+"A transport key grants you the ability to push your changes to a Monotone"
+" repository server.\n"
+" In order to commit code into Monotone (in essence signing your code), a"
+" commit key is also needed.\n"
+" None of the public Monotone servers on I2P currently require a key in "
+"order to read (or pull) the source code."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:74
+msgid ""
+"Without a transport key, one cannot:\n"
+" \n"
+" - pull code from a server which doesn't allow global read "
+"access
\n"
+" - push code to any server
\n"
+" - run a Monotone server
\n"
+"
"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:85
+msgid ""
+"Without a commit key, one cannot:\n"
+" \n"
+" - commit any code
\n"
+"
"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:94
+msgid ""
+"If you only intend to retrieve code from MTN, feel free to skip to the\n"
+" next section. "
+"If you want\n"
+" to generate keys, read the following."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:102
+msgid ""
+"By convention keys are named like an e-mail addresses, but a "
+"corresponding e-mail\n"
+" address does not need to exist. For example, your keys might be named:"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:113
+msgid ""
+"Monotone stores keys under $HOME/.monotone/keys in "
+"text files which\n"
+" are named identically to the keys. For example:"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:123
+msgid ""
+"To generate transport and commit keys, enter the following commands at a "
+"prompt:"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:133
+msgid ""
+"Monotone will prompt you for a password to protect your keys. You are "
+"very strongly encouraged to set a password\n"
+" for the commit key. Many users will leave an empty password for the "
+"transport key, especially those running a\n"
+" Monotone server."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:141
+msgid "Trust, and initializing your repository"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:145
+msgid ""
+"Monotone's security model helps to ensure that nobody can easily "
+"impersonate a developer without\n"
+" it being noticed. Since developers can make mistakes and become "
+"compromised,only manual review can\n"
+" ensure quality of code. Monotone's trust model will ensure that you "
+"read the right diffs. It does\n"
+" not replace reading diffs."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:155
+msgid ""
+"A Monotone repository is a single file (a compressed SQLite database) "
+"which contains all of the project's source code and history."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:161
+msgid ""
+"After importing the "
+"developers' keys into Monotone and\n"
+" setting up trust "
+"evaluation hooks,\n"
+" Monotone will prevent untrusted code from being checked out into your "
+"workspace.\n"
+" There are commands available to clean untrusted code from your "
+"workspace but in practice they've not been\n"
+" needed due to the push access policies in place."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:171
+msgid ""
+"A repository can hold many branches. For example, our repository holds "
+"the\n"
+" following main branches:"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:176
+msgid "The I2P router and associated programs"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:177
+msgid "The I2P project website"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:178
+msgid "Syndie, a distributed forums tool"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:183
+msgid ""
+"By convention, the I2P Monotone repository is named i2p.mtn."
+" Before pulling\n"
+" source code from servers, a database for your repository will need to "
+"be initialized.\n"
+" To initialize your local repository, change into the directory that you"
+" want the\n"
+" i2p.mtn file and branch directories to be stored and issue"
+" the following\n"
+" command:"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:199
+msgid ""
+"Keys which developers use to commit code are essential for trust "
+"evaluation in\n"
+" Monotone. The other developers' transport keys are only required for "
+"Monotone server operators.\n"
+" "
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:206
+#, python-format
+msgid ""
+"Developers' commit keys are provided GPG-signed on another page."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:212
+#, python-format
+msgid ""
+"To import developers' keys after verifying their authenticity, copy all of the keys into a new\n"
+" file. Create this file (e.g. keys.txt) in the same "
+"directory where i2p.mtn is located. Import the keys with the"
+" command:"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:222
+msgid ""
+"Note: Never add keys to "
+"$HOME/.monotone/keys manually."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:230
+msgid ""
+"The default Monotone trust policy is way too lax for our requirements: "
+"every committer is trusted by default.\n"
+" That is not acceptable for I2P development."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:237
+msgid ""
+"Change into the directory $HOME/.monotone and open "
+"the file\n"
+" monotonerc with a text editor. Copy and paste the "
+"following two functions into this file:"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:246
+msgid ""
+"The first function determines an intersection between two sets, in our "
+"case a\n"
+" revision's signers and trusted signers."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:253
+msgid ""
+"The second function determines trust in a given revision, by calling the "
+"first\n"
+" function with \"signers\" and \"trusted\" as arguments. If the "
+"intersection is\n"
+" null, the revision is not trusted. If the intersection is not empty, "
+"the\n"
+" revision is trusted. Otherwise, the revision is not trusted."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:262
+msgid ""
+"More information about Trust Evauluation Hooks can be found in the official Monotone "
+"documentation."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:271
+msgid ""
+"Enter the directory where you initialized i2p.mtn. Depending "
+"on whether you\n"
+" want only I2P sources, or also sources for the I2P website and Syndie, "
+"you can\n"
+" perform the pull operation in different ways."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:279
+msgid "If you only want I2P sources:"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:288
+msgid "If you want all branches:"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:294
+msgid ""
+"If the transfer aborts before completing sucessfully, simply repeating "
+"the pull command will resume the transfer."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:300
+msgid ""
+"Pulling in the above examples is done anonymously by specifying an empty "
+"transport key.\n"
+" If everyone pulls anonymously it will be harder for an attacker who "
+"gains control of the server\n"
+" to selectively provide some people with tampered data."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:311
+msgid "To verify that trust evaluation works:"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:315
+msgid "Make a backup of your monotonerc file."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:316
+msgid ""
+"Modify monotonerc by setting the trusted_signers "
+"variable in the following way:"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:322
+msgid ""
+"With monotonerc configured as above, Monotone will no"
+" longer trust any committers. Confirm this by changing into the\n"
+"directory where i2p.mtn was created and attempt a checkout "
+"of the I2P branch:"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:332
+msgid ""
+"A directory named i2p.i2p should not appear. You "
+"should encounter many\n"
+" error messages like:"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:349
+msgid ""
+"If you are satisfied with results, restore the backup of\n"
+" monotonerc that was created above. If you didn't create a "
+"backup\n"
+" as advised, re-read Setting up trust evaluation hooks."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:360
+msgid ""
+"If you already have a branch checked out, skip to the next\n"
+" section."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:367
+msgid ""
+"Change into the directory where i2p.mtn is located. Over "
+"there issue:"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:376
+msgid ""
+"The checkout should complete without error messages and a directory named"
+"\n"
+" i2p.i2p should appear in the current directory. "
+"Congratulations! You have\n"
+" successfully checked out the latest I2P sources, ready to be compiled."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:387
+msgid ""
+"If you haven't done this already, pull fresh code from the server to your"
+" local\n"
+" Monotone repository. To accomplish this, change into the directory "
+"where\n"
+" i2p.mtn is located and issue:\n"
+" \n"
+" - $
mtn --db=\"i2p.mtn\" -k \"\" pull 127.0.0.1:8998 "
+"i2p.i2p \n"
+"
"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:398
+msgid "Now change into your i2p.i2p directory, and over there issue:"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:407
+msgid ""
+"As long as there were no errors…Congratulations! You have "
+"successfully updated to the latest I2P sources. They\n"
+" should be ready to compile."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:416
+msgid "Obtaining and deploying developers' transport keys"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:419
+msgid ""
+"As a server operator you may want to grant push access to certain "
+"developers."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:427
+msgid "By default the Monotone server denies all access."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:433
+msgid "To grant pull access to all clients, set the following in"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:445
+msgid ""
+"No one will not be able to push code to your server without permission "
+"being explicitly granted. To grant push access:"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:451
+msgid ""
+"Add the name of the user's transport key to\n"
+"$HOME/.monotone/write-permissions, such as\n"
+"\n"
+" zzz-transport@mail.i2p\n"
+" complication-transport@mail.i2p\n"
+"
/etc/monotone/read-permissions and\n"
+" /etc/monotone/write-permissions. You'll also need to edit\n"
+" /etc/default/monotone to enable monotone to start at boot "
+"or to\n"
+" customize the host, port, or database location."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-developers.html:2
+msgid "New Developer's Guide"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-developers.html:4
+msgid ""
+"\n"
+"So you want to start work on I2P? Great!\n"
+"Here's a quick guide to getting started\n"
+"on contributing to the website or the software, doing development or "
+"creating translations."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-developers.html:9
+#, python-format
+msgid ""
+"\n"
+"Not quite ready for coding?\n"
+"Try getting involved first."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-developers.html:16
+#: i2p2www/pages/site/get-involved/guides/new-developers.html:27
+msgid "Basic study"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-developers.html:17
+#: i2p2www/pages/site/get-involved/guides/new-developers.html:41
+msgid "Getting the I2P code"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-developers.html:18
+#: i2p2www/pages/site/get-involved/guides/new-developers.html:112
+msgid "Building I2P"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-developers.html:19
+#: i2p2www/pages/site/get-involved/guides/new-developers.html:133
+msgid "Development ideas"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-developers.html:20
+#: i2p2www/pages/site/get-involved/guides/new-developers.html:141
+msgid "Making the results available"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-developers.html:21
+#: i2p2www/pages/site/get-involved/guides/new-developers.html:162
+msgid "Get to know us!"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-developers.html:22
+#: i2p2www/pages/site/get-involved/guides/new-developers.html:168
+msgid "Translations"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-developers.html:23
+#: i2p2www/pages/site/get-involved/guides/new-developers.html:174
+msgid "Tools"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-developers.html:29
+msgid ""
+"Basic development on the I2P router or the embedded applications uses "
+"Java as the main development language.\n"
+"If you don't have experience with Java, you can always have a look at Thinking in Java."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-developers.html:33
+#, python-format
+msgid ""
+"Study the how intro,\n"
+"the other \"how\" documents,\n"
+"the tech intro,\n"
+"and associated documents.\n"
+"These will give you a good overview of how I2P is structured and what "
+"different things it does."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-developers.html:43
+msgid ""
+"For development on the i2p router or the embedded applications,\n"
+"get the monotone source repository installed - short instructions:"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-developers.html:48
+msgid ""
+"Install monotone.\n"
+"Monotone is a version control system.\n"
+"We use it because it allows us to keep track of who does what changes to "
+"the source code (and for a lot of complicated things, but 'keeping track "
+"of changes' is the basic idea)."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-developers.html:53
+msgid ""
+"Skim over the monotone tutorial,"
+" to make sure you understand the concepts."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-developers.html:57
+msgid ""
+"If you want to remain anonymous, you need to do an additional step, to "
+"set up a connection to a monotone server over I2P:"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-developers.html:60
+#, python-format
+msgid ""
+"Enable the i2ptunnel client tunnel on port "
+"8998 pointing to mtn.i2p2.i2p."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-developers.html:64
+msgid ""
+"Pick a directory where you want to put all your I2P files, and create a "
+"monotone database:"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-developers.html:67
+msgid ""
+"Define the trust list by creating ~/.monotone/monotonerc (or"
+" _MTN/monotonerc in the i2p.i2p workspace) with the "
+"following contents:"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-developers.html:72
+#, python-format
+msgid ""
+"Copy and paste the developer's commit keys "
+"into a new file (e.g. keys.txt) in the same directory\n"
+" that i2p.mtn is in. Import the keys into your database "
+"with
mtn -d i2p.mtn read < keys.txt
viewmtn."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-developers.html:108
+#, python-format
+msgid ""
+"A long explanation about using monotone is available on the monotone page."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-developers.html:114
+#, python-format
+msgid ""
+"To compile the code, you need the Sun Java Development Kit 6 or higher, "
+"or equivalent JDK\n"
+"(Sun JDK 6 strongly recommended) and\n"
+"Apache ant\n"
+"version 1.7.0 or higher.\n"
+"If you go are working on the main I2P code, you can go into the i2p.i2p "
+"directory and run 'ant' to see the build options."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-developers.html:122
+msgid ""
+"To build or work on console translations, you need\n"
+"the xgettext, msgfmt, and msgmerge tools from the\n"
+"GNU gettext package."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-developers.html:128
+#, python-format
+msgid ""
+"For development on new applications,\n"
+"see the application development guide."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-developers.html:134
+#, python-format
+msgid ""
+"See zzz's TODO lists,\n"
+"this website's TODO list or\n"
+"Trac\n"
+"for ideas."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-developers.html:143
+#, python-format
+msgid ""
+"See the bottom of the licenses page "
+"for\n"
+"commit privilege requirements. You need these to put code into i2p.i2p "
+"(not required for the website!)."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-developers.html:148
+msgid "Short version of how to generate and use keys if you plan to commit:"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-developers.html:150
+msgid "use an empty passphrase"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-developers.html:151
+msgid "enter a passphrase"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-developers.html:152
+#, python-format
+msgid ""
+"send this to a mtn repo operator to get "
+"push privileges"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-developers.html:153
+#, python-format
+msgid ""
+"send this to a release manager to get "
+"commit privileges - not required for website"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-developers.html:154
+msgid "check in with this key"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-developers.html:155
+msgid "push with this key"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-developers.html:157
+#, python-format
+msgid "Long version: see the monotone page."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-developers.html:163
+#, python-format
+msgid ""
+"The developers hang around on IRC. They can be reached on the Freenode "
+"network, OFTC, and on the I2P internal networks. The usual place to look "
+"is #i2p-dev. Join the channel and say hi!\n"
+"We also have additional guidelines for regular"
+" developers."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-developers.html:169
+#, python-format
+msgid ""
+"Website and router console translators: See the New Translator's Guide\n"
+"for next steps."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-developers.html:175
+msgid ""
+"I2P is open source software that is mostly developed using open sourced\n"
+"toolkits. The I2P project recently acquired a license for the YourKit "
+"Java\n"
+"Profiler. Open source projects are eligible to receive a free license "
+"provided\n"
+"that YourKit is referenced on the project web site. Please get in touch "
+"if you\n"
+"are interested in profiling the I2P codebase."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-developers.html:183
+#, python-format
+msgid ""
+"YourKit is kindly supporting open source projects with its full-featured "
+"Java Profiler.\n"
+"YourKit, LLC is the creator of innovative and intelligent tools for "
+"profiling\n"
+"Java and .NET applications. Take a look at YourKit's leading software "
+"products:\n"
+"YourKit Java Profiler and\n"
+"YourKit .NET Profiler."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-translators.html:2
+msgid "New Translator's Guide"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-translators.html:4
+msgid "Here's a very quick guide to getting started."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-translators.html:6
+msgid "How to Translate the Website"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-translators.html:8
+#, python-format
+msgid ""
+"Translation of the website is done with .po files. The easiest way by far"
+" to\n"
+"translate the website is to sign up for an account at \n"
+"Transifex and request to join a translation"
+" team. \n"
+"Alternatively it can be done \"the old way\" as outlined below."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-translators.html:17
+#: i2p2www/pages/site/get-involved/guides/new-translators.html:82
+msgid "Preparation"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-translators.html:19
+#: i2p2www/pages/site/get-involved/guides/new-translators.html:84
+#, python-format
+msgid ""
+"Come to #i2p-dev on irc and talk to people.\n"
+"Claim the language -\n"
+"To make sure other coworkers don't bump onto the files you are working "
+"on,\n"
+"please update the translation status on this wiki "
+"page."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-translators.html:25
+#, python-format
+msgid ""
+"Follow the new developer's guide,\n"
+"Including the installation of monotone,\n"
+"checking out i2p.www branch, and generate your own monotone keys.\n"
+"It is not required that you sign a dev agreement."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-translators.html:33
+msgid ""
+"Create files:\n"
+"If the file for your language does not exist yet:"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-translators.html:38
+msgid ""
+"Run \"./extract-messages.sh\" to generate a "
+"messages.pot in the base directory.\n"
+"Edit the header of this file, then run \"./init-new-po.sh "
+"locale\" to generate the file\n"
+"i2p2www/translations/locale/LC_MESSAGES/messages.po. "
+"\"mtn add\" this file."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-translators.html:43
+msgid ""
+"Edit i2p2www/pages/global/lang.html and add a line for your "
+"language (copy an existing line)."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-translators.html:46
+msgid ""
+"Add a flag image file to i2p2www/static/images/flags/ for "
+"the menu (copy from the router)."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-translators.html:52
+msgid ""
+"Edit files:\n"
+"Edit i2p2www/translations/locale/LC_MESSAGES/messages.po.\n"
+"To work with .po files efficiently, you may wish to use POEdit"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-translators.html:58
+#: i2p2www/pages/site/get-involved/guides/new-translators.html:151
+msgid ""
+"Check in:\n"
+"\"mtn pull\", \"mtn update\". Then check in by "
+"\"mtn ci -k yourname@mail.i2p file1 file2 ...\"\n"
+"This collects the diff info of your changed file into your local repo. "
+"Then \"mtn sync mtn.i2p2.de -k yourname-transport@mail.i2p "
+"i2p.i2p\".\n"
+"This synchronizes your local repo with the repo on the target machine."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-translators.html:65
+#: i2p2www/pages/site/get-involved/guides/new-translators.html:158
+msgid "Repeat. Check in often. Don't wait until it is perfect."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-translators.html:72
+msgid "How to Translate the Router Console"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-translators.html:74
+#, python-format
+msgid ""
+"The easiest way by far to translate the router console is to sign up for "
+"an account at \n"
+"Transifex and request to join a translation"
+" team. \n"
+"Alternatively it can be done \"the old way\" as outlined below."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-translators.html:90
+#, python-format
+msgid ""
+"Follow the new developer's guide,\n"
+"including the installation of monotone and the gettext tools,\n"
+"checking out i2p.i2p branch, and generate your own monotone keys."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-translators.html:95
+msgid "Generate your own gpg key and sign the dev agreement."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-translators.html:101
+msgid ""
+"Before starting a console translation, better help translate some i2p "
+"webpages first.\n"
+"At least an i2p homepage in your language would be great."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-translators.html:106
+msgid ""
+"What to translate:\n"
+"There are about 15 files in the i2p.i2p branch that needs translation:"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-translators.html:132
+msgid ""
+"Where xx is your language code like fr/de/ch/zh/...\n"
+"There may be or may not be files with your lang code. If not, you can "
+"create your own. by copying and renaming other language files you know "
+"with your own lang code."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-translators.html:137
+msgid ""
+"Create files:\n"
+"If the file for your language does not exist yet, copy another language "
+"file to a new file foo_xx.bar for your language.\n"
+"Then \"mtn add\" the file.\n"
+"After creating a .po file, edit the headers. Then run \"ant "
+"distclean poupdate\"."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-translators.html:144
+msgid ""
+"Start to work:\n"
+"Edit the HTML files with any text editor.\n"
+"Be sure not to use an editor in HTML mode that reformats everything.\n"
+"To work with .po files efficiently, you may wish to use POEdit"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-translators.html:163
+msgid ""
+"As you can see, it's not that difficult.\n"
+"If you have questions about the meaning of the terms in the console, ask "
+"in #i2p-dev on IRC."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-translators.html:169
+msgid "FAQ"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-translators.html:171
+msgid ""
+"Q: Why do I have to install monotone, Java, jsp, learn about .po files "
+"and html, etc.? Why can't I just do a translation and email it to you?"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-translators.html:175
+msgid "A: Several reasons:"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-translators.html:178
+#, python-format
+msgid ""
+"You might be interested in translating via Transifex. Request to join a "
+"translation team here."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-translators.html:182
+msgid ""
+"We don't have anybody who has time to accept manual contributions and "
+"submit them to our source control system on your behalf. Even if we did, "
+"it doesn't scale."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-translators.html:186
+msgid ""
+"Maybe you are thinking translation is a one-step process. It isn't. You "
+"can't do it all at once. You will make mistakes. You need to test it and "
+"tweak it to make it look right before you submit it. Developers "
+"will update or add to the English text, thus requiring a translation "
+"update."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-translators.html:190
+msgid ""
+"Having translators use a source control system directly provides "
+"authentication and accountablility - we know who is doing what, and we "
+"can track changes, and revert them if necessary."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-translators.html:194
+msgid ""
+".po files are not difficult. If you don't want to work directly with "
+"them, we recommend 'poedit'."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-translators.html:198
+msgid ""
+"HTML files are not difficult. Just ignore the html stuff and translate "
+"the text."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-translators.html:202
+msgid ""
+"Installing and using monotone is not that difficult. Several of the "
+"translators and other contributors to I2P are non-programmers, and they "
+"use monotone regularly. Monotone is simply a source control system, it is"
+" not about \"coding\"."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-translators.html:206
+msgid ""
+"Our items to translate are not \"documents\". They are html files and po "
+"files, with a specific format and character encoding (UTF-8) that must be"
+" maintained, and not corrupted by email programs or other methods of "
+"transfer."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-translators.html:210
+msgid ""
+"We looked at 'pootle' as a front-end for translators. It didn't work "
+"well, needed an administrator, and a pootle-based process would suffer "
+"from a number of the above flaws."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-translators.html:215
+msgid ""
+"In summary:\n"
+"Yes, we know it is somewhat of a hurdle to get started. It's really the "
+"only possible way we can do it. Give it a try, it really isn't that hard."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-translators.html:220
+msgid "More Information"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-translators.html:221
+#, python-format
+msgid ""
+"The #i2p-dev channel on IRC, or the translation forum on %(zzz)s."
+msgstr ""
+
diff --git a/i2p2www/translations/pt_BR/LC_MESSAGES/priority.po b/i2p2www/translations/pt_BR/LC_MESSAGES/priority.po
new file mode 100644
index 00000000..aa6bf9c6
--- /dev/null
+++ b/i2p2www/translations/pt_BR/LC_MESSAGES/priority.po
@@ -0,0 +1,2541 @@
+# Portuguese (Brazil) translations for I2P.
+# Copyright (C) 2013 ORGANIZATION
+# This file is distributed under the same license as the I2P project.
+#
+# Translators:
+# blueboy, 2013
+msgid ""
+msgstr ""
+"Project-Id-Version: I2P\n"
+"Report-Msgid-Bugs-To: http://trac.i2p2.de\n"
+"POT-Creation-Date: 2013-11-27 00:23+0000\n"
+"PO-Revision-Date: 2013-11-27 02:30+0000\n"
+"Last-Translator: blueboy\n"
+"Language-Team: Portuguese (Brazil) "
+"(http://www.transifex.com/projects/p/I2P/language/pt_BR/)\n"
+"Plural-Forms: nplurals=2; plural=(n > 1)\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=utf-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"Generated-By: Babel 0.9.6\n"
+
+#: i2p2www/pages/blog/category.html:2
+msgid "Blog Category"
+msgstr ""
+
+#: i2p2www/pages/blog/category.html:4
+#, python-format
+msgid "I2P Blog ATOM Feed for Category: %(category)s"
+msgstr ""
+
+#: i2p2www/pages/blog/index.html:2 i2p2www/pages/blog/post.html:3
+#: i2p2www/pages/global/nav.html:95
+msgid "Blog"
+msgstr "Blogue"
+
+#: i2p2www/pages/blog/index.html:4 i2p2www/pages/site/index.html:78
+msgid "I2P Blog ATOM Feed"
+msgstr "Feed ATOM do Blog da I2P"
+
+#: i2p2www/pages/blog/index.html:17
+#, python-format
+msgid "Posted %(date)s by %(author)s"
+msgstr ""
+
+#: i2p2www/pages/blog/latest.html:5
+msgid "More blog posts…"
+msgstr ""
+
+#: i2p2www/pages/blog/post.html:6
+msgid "Posted:"
+msgstr ""
+
+#: i2p2www/pages/blog/post.html:7
+msgid "Author:"
+msgstr ""
+
+#: i2p2www/pages/downloads/debian.html:4
+msgid "Debian I2P Packages"
+msgstr "Pacotes da I2P no Debian"
+
+#: i2p2www/pages/downloads/debian.html:6
+msgid ""
+"The Debian packages\n"
+"have been tested and should work on x86/x86_64 platforms running:"
+msgstr ""
+
+#: i2p2www/pages/downloads/debian.html:11
+msgid "Ubuntu (Precise 12.04 and newer)"
+msgstr ""
+
+#: i2p2www/pages/downloads/debian.html:13
+msgid "Debian Linux (Squeeze and newer) & kFreeBSD"
+msgstr ""
+
+#: i2p2www/pages/downloads/debian.html:17
+#, python-format
+msgid ""
+"The I2P packages may work on systems not listed above. Please "
+"report any issues\n"
+"with these packages on Trac at\n"
+"https://trac.i2p2.de."
+msgstr ""
+
+#: i2p2www/pages/downloads/debian.html:23
+msgid ""
+"Option 1: Recent versions of Ubuntu and its "
+"derivatives (Try this if you're not using Debian)"
+msgstr ""
+"Opção 1: Versões recentes do Ubuntu e derivados "
+"(Tente isto se você não está usando o Debian)"
+
+#: i2p2www/pages/downloads/debian.html:24
+msgid "Option 2: Debian (including Debian-derivatives)"
+msgstr ""
+
+#: i2p2www/pages/downloads/debian.html:27
+msgid ""
+"Instructions for Ubuntu Precise Pangolin (and newer) and derivatives like"
+" Linux Mint & Trisquel"
+msgstr ""
+
+#: i2p2www/pages/downloads/debian.html:28
+msgid "Adding the PPA via the command line and installing I2P"
+msgstr "Adicionando o PPA via linha de comando e instalando a I2P"
+
+#: i2p2www/pages/downloads/debian.html:31
+msgid "Open a terminal and enter:"
+msgstr "Abra um terminal e digite:"
+
+#: i2p2www/pages/downloads/debian.html:33
+msgid ""
+"This command will add the PPA to /etc/apt/sources.list.d and fetch the\n"
+"gpg key that the repository has been signed with. The GPG key ensures\n"
+"that the packages have not been tampered with since being built."
+msgstr ""
+
+#: i2p2www/pages/downloads/debian.html:40
+msgid "Notify your package manager of the new PPA by entering:"
+msgstr ""
+
+#: i2p2www/pages/downloads/debian.html:42
+msgid ""
+"This command will retrieve the latest list of software from each\n"
+"repository that is enabled on your system, including the I2P PPA that\n"
+"was added with the earlier command."
+msgstr ""
+
+#: i2p2www/pages/downloads/debian.html:48
+msgid "You are now ready to install I2P!"
+msgstr "Você já está pronto para instalar a I2P!"
+
+#: i2p2www/pages/downloads/debian.html:52
+msgid "Adding the PPA Using Synaptic"
+msgstr "Adicionando o PPA usando o Synaptic"
+
+#: i2p2www/pages/downloads/debian.html:55
+msgid ""
+"Open Synaptic (System -> Administration -> Synaptic Package "
+"Manager)."
+msgstr ""
+
+#: i2p2www/pages/downloads/debian.html:60
+msgid ""
+"Once Synaptic opens, select Repositories from the "
+"Settings menu."
+msgstr ""
+
+#: i2p2www/pages/downloads/debian.html:65
+msgid ""
+"Click the Other Sources tab and click Add. Paste "
+"ppa:i2p-maintainers/i2p into the APT-line field and click "
+"Add Source. Click the Close button then "
+"Reload."
+msgstr ""
+
+#: i2p2www/pages/downloads/debian.html:70
+msgid ""
+"In the Quick Filter box, type in i2p and press enter. When "
+"i2p is returned in the results list, right click "
+"i2p and select Mark for Installation. After doing "
+"so you may see a Mark additional required changes? popup. If so,"
+" click Mark then Apply."
+msgstr ""
+
+#: i2p2www/pages/downloads/debian.html:76
+msgid ""
+"After the installation process completes you can move on to the next\n"
+"part of starting I2P and configuring "
+"it for your system."
+msgstr ""
+
+#: i2p2www/pages/downloads/debian.html:81
+msgid "Instructions for Debian"
+msgstr ""
+
+#: i2p2www/pages/downloads/debian.html:85
+msgid ""
+"Note: The steps below should be performed with root access (i.e., "
+"switching\n"
+"user to root with \"su\" or by prefixing each command with \"sudo\")."
+msgstr ""
+
+#: i2p2www/pages/downloads/debian.html:90
+#, python-format
+msgid "Add lines like the following to %(file)s."
+msgstr ""
+
+#: i2p2www/pages/downloads/debian.html:111
+#, python-format
+msgid ""
+"Download the key used to sign the repository"
+" and add it to apt:"
+msgstr ""
+
+#: i2p2www/pages/downloads/debian.html:118
+msgid "Notify your package manager of the new repository by entering"
+msgstr ""
+
+#: i2p2www/pages/downloads/debian.html:120
+msgid ""
+"This command will retrieve the latest list of software from every\n"
+"repository enabled on your system, including the I2P repository added in "
+"step\n"
+"1."
+msgstr ""
+
+#: i2p2www/pages/downloads/debian.html:126
+msgid ""
+"You are now ready to install I2P! Installing the i2p-keyring"
+"\n"
+"package will ensure that you receive updates to the repository's GPG key."
+msgstr ""
+
+#: i2p2www/pages/downloads/debian.html:133
+msgid ""
+"After the installation process completes you can move on to the next part"
+" of starting I2P and configuring it "
+"for your system."
+msgstr ""
+
+#: i2p2www/pages/downloads/debian.html:137
+#: i2p2www/pages/downloads/list.html:171
+msgid "Post-install work"
+msgstr "Trabalho pós-instalação"
+
+#: i2p2www/pages/downloads/debian.html:139
+msgid ""
+"Using these I2P packages the I2P router can be started in the following\n"
+"three ways:"
+msgstr ""
+
+#: i2p2www/pages/downloads/debian.html:145
+msgid ""
+""on demand" using the i2prouter script. Simply run "
+""i2prouter\n"
+"start" from a command prompt. (Note: Do "
+"not use\n"
+"sudo or run it as root!)"
+msgstr ""
+
+#: i2p2www/pages/downloads/debian.html:152
+msgid ""
+""on demand" without the java service wrapper\n"
+"(needed on non-Linux/non-x86 systems) by running \"i2prouter-"
+"nowrapper\".\n"
+"(Note: Do not\n"
+"use sudo or run it as root!)"
+msgstr ""
+
+#: i2p2www/pages/downloads/debian.html:160
+msgid ""
+"as a service that automatically runs when your system boots, even\n"
+"before logging in. The service can be enabled with \"dpkg-"
+"reconfigure\n"
+"i2p\" as root or using sudo. This is the recommended means of "
+"operation."
+msgstr ""
+
+#: i2p2www/pages/downloads/debian.html:168
+msgid ""
+"When installing for the first time, please remember to adjust your "
+"NAT/firewall\n"
+"if you can. The ports to forward can be found on the \n"
+"network configuration page in the router console. If guidance with "
+"respect to forwarding ports is needed,\n"
+"you may find portforward.com to be"
+" helpful."
+msgstr ""
+
+#: i2p2www/pages/downloads/debian.html:175
+msgid ""
+"Please review and adjust the bandwidth settings on the\n"
+"configuration page,\n"
+"as the default settings of 96 KB/s down / 40 KB/s up are fairly "
+"conservative."
+msgstr ""
+
+#: i2p2www/pages/downloads/debian.html:181
+#: i2p2www/pages/downloads/list.html:204
+#, python-format
+msgid ""
+"If you want to reach eepsites via your browser, have a look on the browser proxy setup page for an easy "
+"howto."
+msgstr ""
+
+#: i2p2www/pages/downloads/list.html:2 i2p2www/pages/downloads/select.html:12
+#: i2p2www/pages/global/nav.html:3
+msgid "Download"
+msgstr "Baixar"
+
+#: i2p2www/pages/downloads/list.html:9
+msgid "Download I2P"
+msgstr "Baixar I2P"
+
+#: i2p2www/pages/downloads/list.html:11
+msgid "Dependency"
+msgstr "Dependências"
+
+#: i2p2www/pages/downloads/list.html:12
+#, python-format
+msgid ""
+"\n"
+"Java Runtime 1.5 or higher.\n"
+"(Oracle Java Version 7,\n"
+"OpenJDK 7, or\n"
+"IcedTea7\n"
+" recommended,\n"
+"except Raspberry Pi: Oracle 8 Early Access,\n"
+"PowerPC: IBM SDK 7)\n"
+"
\n"
+"Determine your installed Java version here\n"
+"or type java -version at your command prompt.\n"
+msgstr ""
+
+#: i2p2www/pages/downloads/list.html:30
+msgid "Clean installs"
+msgstr ""
+
+#: i2p2www/pages/downloads/list.html:37 i2p2www/pages/downloads/list.html:54
+#: i2p2www/pages/downloads/list.html:81 i2p2www/pages/downloads/list.html:140
+#: i2p2www/pages/downloads/list.html:269
+msgid "select alternate link"
+msgstr ""
+
+#: i2p2www/pages/downloads/list.html:44
+msgid "Download that file and run it."
+msgstr "Baixar e executar o arquivo."
+
+#: i2p2www/pages/downloads/list.html:61
+#, python-format
+msgid ""
+"Download that file and double-click it (if that works) or\n"
+" type java -jar i2pinstall_%(i2pversion)s.jar in a "
+"terminal to run the\n"
+" installer.\n"
+" You may be able to right-click and select\n"
+" "Open with Java"."
+msgstr ""
+
+#: i2p2www/pages/downloads/list.html:69 i2p2www/pages/downloads/list.html:96
+msgid "Command line (headless) install:"
+msgstr ""
+
+#: i2p2www/pages/downloads/list.html:70
+#, python-format
+msgid ""
+"Download the %(i2pversion)s OSX graphical installer file above and\n"
+" run java -jar i2pinstall_%(i2pversion)s.jar -console "
+"from the command line."
+msgstr ""
+
+#: i2p2www/pages/downloads/list.html:88
+#, python-format
+msgid ""
+"Download that file and double-click it (if that works) or\n"
+" type java -jar i2pinstall_%(i2pversion)s.jar in a "
+"terminal to run the\n"
+" installer.\n"
+" On some platforms you may be able to right-click and select\n"
+" "Open with Java"."
+msgstr ""
+
+#: i2p2www/pages/downloads/list.html:97
+#, python-format
+msgid ""
+"Download the graphical installer file above and\n"
+" run java -jar i2pinstall_%(i2pversion)s.jar -console "
+"from the command line."
+msgstr ""
+
+#: i2p2www/pages/downloads/list.html:107
+msgid "Packages for Debian & Ubuntu are available."
+msgstr "Pacotes para Debian & Ubuntu estão disponíveis."
+
+#: i2p2www/pages/downloads/list.html:121
+#, python-format
+msgid ""
+"The above file is the current release build.\n"
+" The latest dev build is version %(devbuild)s, and is available from\n"
+" str4d's eepsite."
+msgstr ""
+
+#: i2p2www/pages/downloads/list.html:127
+msgid ""
+"The release and dev versions of the I2P APK are not compatible, as they\n"
+" are signed by zzz and str4d respectively. Uninstall one before "
+"installing\n"
+" the other."
+msgstr ""
+
+#: i2p2www/pages/downloads/list.html:137
+msgid "Source package"
+msgstr ""
+
+#: i2p2www/pages/downloads/list.html:147
+#, python-format
+msgid ""
+"Alternately, you can fetch the source from monotone\n"
+" or via Git from git.repo.i2p or Github.\n"
+"
\n"
+" Run (tar xjvf i2psource_%(i2pversion)s.tar.bz2 ; cd "
+"i2p-%(i2pversion)s ; ant pkg) then either\n"
+" run the GUI installer or headless install as above."
+msgstr ""
+
+#: i2p2www/pages/downloads/list.html:162
+#, python-format
+msgid ""
+"The files are signed by zzz,\n"
+"whose key is here."
+msgstr ""
+
+#: i2p2www/pages/downloads/list.html:167
+msgid ""
+"I2P can also be downloaded from our project pages on Launchpad and Google Code."
+msgstr ""
+
+#: i2p2www/pages/downloads/list.html:173
+msgid ""
+"After running the installer on windows, simply click on the \"Start I2P\""
+" button\n"
+"which will bring up the router console,\n"
+"which has further instructions."
+msgstr ""
+
+#: i2p2www/pages/downloads/list.html:179
+msgid ""
+"On Unix-like systems, I2P can be started as a service\n"
+"using the \"i2prouter\" script, located in the directory you selected for"
+" I2P.\n"
+"Changing to that directory in a console and issuing \"sh i2prouter "
+"status\"\n"
+"should tell you the router's status. The arguments \"start\", \"stop\" "
+"and \"restart\"\n"
+"control the service. The router console\n"
+"can be accessed at its usual location.\n"
+"For users on OpenSolaris and other systems for which the wrapper (i2psvc)"
+" is not supported,\n"
+"start the router with \"sh runplain.sh\" instead."
+msgstr ""
+
+#: i2p2www/pages/downloads/list.html:190
+#, python-format
+msgid ""
+"When installing for the first time, please remember to adjust your "
+"NAT/firewall\n"
+"if you can, bearing in mind the Internet-facing ports I2P uses,\n"
+"described here among other ports.\n"
+"If you have successfully opened your port to inbound TCP, also enable "
+"inbound TCP on the\n"
+"configuration page."
+msgstr ""
+
+#: i2p2www/pages/downloads/list.html:198
+msgid ""
+"Also, please review and adjust the bandwidth settings on the\n"
+"configuration page,\n"
+"as the default settings of 96 KBps down / 40 KBps up are fairly slow."
+msgstr ""
+
+#: i2p2www/pages/downloads/list.html:208
+msgid "Updates from earlier releases:"
+msgstr "Atualizações de lançamentos anteriores:"
+
+#: i2p2www/pages/downloads/list.html:210
+msgid "Both automatic and manual upgrades are available for the release."
+msgstr ""
+
+#: i2p2www/pages/downloads/list.html:215
+msgid "Automatic updates"
+msgstr "Atualizações automáticas"
+
+#: i2p2www/pages/downloads/list.html:217
+msgid ""
+"If you are running 0.7.5 or later, your router should detect the\n"
+"new release. To upgrade simply click the 'Download Update' button on your"
+" router console\n"
+"when it appears."
+msgstr ""
+
+#: i2p2www/pages/downloads/list.html:223
+msgid ""
+"Due to a bug in release 0.7.6, those whose first I2P installation was "
+"that version\n"
+"and have not upgraded manually\n"
+"may get a \"downloaded version is not greater than current version\" "
+"error,\n"
+"and should use the manual update method below."
+msgstr ""
+
+#: i2p2www/pages/downloads/list.html:231
+#, python-format
+msgid ""
+"If you are running 0.7.4 or earlier, please see\n"
+"the 0.7.5 release notes\n"
+"for important information about how to configure your router to "
+"automatically\n"
+"receive the release."
+msgstr ""
+
+#: i2p2www/pages/downloads/list.html:239
+#, python-format
+msgid ""
+"If you are running 0.6.1.30 or earlier, please see\n"
+"instructions\n"
+"for important information about how to configure your router to "
+"automatically\n"
+"receive the release."
+msgstr ""
+
+#: i2p2www/pages/downloads/list.html:248
+#, python-format
+msgid ""
+"If you have reconfigured your router following the instructions, you should see a link on your"
+" \n"
+" router console "
+"allowing\n"
+" you to download and install the new release by just clicking on that\n"
+" link."
+msgstr ""
+
+#: i2p2www/pages/downloads/list.html:256
+msgid "Alternately, you can use the manual method specified below."
+msgstr ""
+
+#: i2p2www/pages/downloads/list.html:266
+msgid "Manual updates"
+msgstr "Atualizações manuais"
+
+#: i2p2www/pages/downloads/list.html:278
+msgid ""
+"Download that file to your I2P\n"
+" installation directory and rename as i2pupdate.zip.\n"
+" (alternately, you can get the source as above and run \"ant "
+"updater\", then copy the\n"
+" resulting i2pupdate.zip to your I2P installation directory). You do"
+" \n"
+" NOT need to unzip that file."
+msgstr ""
+
+#: i2p2www/pages/downloads/list.html:287
+msgid "Click \"Restart\""
+msgstr ""
+"Clique em \"Reiniciar\""
+
+#: i2p2www/pages/downloads/list.html:292
+msgid "Grab a cup of coffee and come back in 11 minutes"
+msgstr ""
+
+#: i2p2www/pages/downloads/list.html:300
+#, python-format
+msgid ""
+"The file is signed by zzz,\n"
+"whose key is here."
+msgstr ""
+
+#: i2p2www/pages/downloads/list.html:305
+msgid "Previous Releases"
+msgstr "Lançamentos anteriores"
+
+#: i2p2www/pages/downloads/list.html:307
+#, python-format
+msgid ""
+"Previous releases are available on Google "
+"Code\n"
+"and Launchpad\n"
+"and within the I2P network on %(echelon)s."
+msgstr ""
+
+#: i2p2www/pages/downloads/select.html:2 i2p2www/pages/downloads/select.html:4
+msgid "Mirror selection"
+msgstr "Seleção do espelho"
+
+#: i2p2www/pages/downloads/select.html:5
+msgid "File:"
+msgstr "Arquivo:"
+
+#: i2p2www/pages/downloads/select.html:10
+msgid "Any mirror"
+msgstr "Qualquer espelho"
+
+#: i2p2www/pages/global/bounty.html:19
+msgid ""
+"To claim the bounty the author must not be paid by other organizations\n"
+"or teams for this work (e.g. GSoC students are not valid)."
+msgstr ""
+
+#: i2p2www/pages/global/bounty.html:29
+#, python-format
+msgid ""
+"Bounty amounts may be increased by further donations. Do\n"
+"you think these are important? Add in your "
+"donation, \n"
+"marking the amount for the %(donatename)s bounty!"
+msgstr ""
+
+#: i2p2www/pages/global/error_404.html:3
+msgid "Not found"
+msgstr "Não encontrado"
+
+#: i2p2www/pages/global/error_404.html:9
+msgid ""
+"Yep... the resource, you were searching for, is named differently, "
+"doesn't exist or was removed."
+msgstr ""
+
+#: i2p2www/pages/global/error_500.html:5
+msgid "Server error"
+msgstr "Erro de servidor"
+
+#: i2p2www/pages/global/error_500.html:13
+msgid "500 Server error"
+msgstr "Erro de servidor 500"
+
+#: i2p2www/pages/global/error_500.html:17
+msgid "Umm... the server encountered some sort of error."
+msgstr ""
+
+#: i2p2www/pages/global/footer.html:2
+msgid "Mirrors"
+msgstr "Espelhos"
+
+#: i2p2www/pages/global/footer.html:9
+msgid "Secure"
+msgstr "Seguro"
+
+#: i2p2www/pages/global/footer.html:16
+msgid "Misc."
+msgstr ""
+
+#: i2p2www/pages/global/footer.html:19 i2p2www/pages/site/links.html:2
+msgid "Links"
+msgstr "Linques"
+
+#: i2p2www/pages/global/footer.html:20
+msgid "Impressum"
+msgstr "Imprenta"
+
+#: i2p2www/pages/global/footer.html:24
+msgid "T-Shirts!"
+msgstr "Camisetas!"
+
+#: i2p2www/pages/global/footer.html:26
+msgid "Europe"
+msgstr "Europa"
+
+#: i2p2www/pages/global/footer.html:27
+msgid "USA"
+msgstr "EUA"
+
+#: i2p2www/pages/global/footer.html:31
+msgid "Donate"
+msgstr "Faça uma doação"
+
+#: i2p2www/pages/global/layout.html:29
+msgid "Skip navigation"
+msgstr ""
+
+#: i2p2www/pages/global/layout.html:32
+msgid "I2P Logo"
+msgstr "Logo da I2P"
+
+#: i2p2www/pages/global/layout.html:32 i2p2www/pages/site/index.html:3
+msgid "The Invisible Internet Project"
+msgstr "Projeto Internet Invisível"
+
+#: i2p2www/pages/global/layout.html:56
+#, python-format
+msgid ""
+"This page was last updated in %(lastupdated)s and is accurate for router "
+"version %(accuratefor)s."
+msgstr ""
+
+#: i2p2www/pages/global/layout.html:60
+#, python-format
+msgid "This page was last updated in %(lastupdated)s."
+msgstr "Esta página foi atualizada pela última vez em %(lastupdated)s."
+
+#: i2p2www/pages/global/layout.html:64
+#, python-format
+msgid "This page is accurate for router version %(accuratefor)s."
+msgstr ""
+
+#: i2p2www/pages/global/macros:21
+msgid "Previous"
+msgstr ""
+
+#: i2p2www/pages/global/macros:36
+msgid "Next"
+msgstr ""
+
+#: i2p2www/pages/global/macros:43
+msgid "Posted in"
+msgstr ""
+
+#: i2p2www/pages/global/nav.html:4
+msgid "About"
+msgstr "Sobre"
+
+#: i2p2www/pages/global/nav.html:6
+msgid "Introduction to I2P"
+msgstr "Introdução à I2P"
+
+#: i2p2www/pages/global/nav.html:7
+msgid "Comparisons"
+msgstr "Comparações"
+
+#: i2p2www/pages/global/nav.html:9
+msgid "Overview of comparisons"
+msgstr "Uma visão geral das comparações"
+
+#: i2p2www/pages/global/nav.html:13
+msgid "Other anonymous networks"
+msgstr "Outras redes anônimas"
+
+#: i2p2www/pages/global/nav.html:16
+msgid "Documentation"
+msgstr "Documentação"
+
+#: i2p2www/pages/global/nav.html:18
+msgid "Documentation index"
+msgstr "Índice da documentação"
+
+#: i2p2www/pages/global/nav.html:19
+msgid "How does it work?"
+msgstr "Como funciona?"
+
+#: i2p2www/pages/global/nav.html:21
+msgid "Gentle intro"
+msgstr "Introdução amigável"
+
+#: i2p2www/pages/global/nav.html:22
+msgid "Tech intro"
+msgstr "Introdução técnica"
+
+#: i2p2www/pages/global/nav.html:23
+msgid "Threat model"
+msgstr "Modelo de risco"
+
+#: i2p2www/pages/global/nav.html:24
+msgid "Garlic routing"
+msgstr "Roteamento \"garlic\""
+
+#: i2p2www/pages/global/nav.html:25
+msgid "Network database"
+msgstr "Banco de dados da rede"
+
+#: i2p2www/pages/global/nav.html:26
+msgid "Tunnel routing"
+msgstr "Roteamento via túneis"
+
+#: i2p2www/pages/global/nav.html:27
+msgid "Peer selection"
+msgstr ""
+
+#: i2p2www/pages/global/nav.html:28
+msgid "Cryptography"
+msgstr "Criptografia"
+
+#: i2p2www/pages/global/nav.html:29
+msgid "ElGamal/AES+SessionTags"
+msgstr ""
+
+#: i2p2www/pages/global/nav.html:32
+msgid "Specifications"
+msgstr "Especificações"
+
+#: i2p2www/pages/global/nav.html:34
+msgid "Blockfile"
+msgstr ""
+
+#: i2p2www/pages/global/nav.html:35
+msgid "Common structures"
+msgstr "Estruturas comuns"
+
+#: i2p2www/pages/global/nav.html:36
+msgid "Configuration files"
+msgstr "Arquivos de configuração"
+
+#: i2p2www/pages/global/nav.html:37 i2p2www/pages/global/nav.html:59
+msgid "Datagrams"
+msgstr "Datagramas"
+
+#: i2p2www/pages/global/nav.html:38
+msgid "GeoIP files"
+msgstr ""
+
+#: i2p2www/pages/global/nav.html:41 i2p2www/pages/global/nav.html:91
+msgid "Plugins"
+msgstr "Extensões"
+
+#: i2p2www/pages/global/nav.html:43 i2p2www/pages/global/nav.html:57
+msgid "Streaming library"
+msgstr ""
+
+#: i2p2www/pages/global/nav.html:44
+msgid "Tunnel creation"
+msgstr "Criação de túneis"
+
+#: i2p2www/pages/global/nav.html:45
+msgid "Tunnel messages"
+msgstr ""
+
+#: i2p2www/pages/global/nav.html:46
+msgid "Software updates"
+msgstr "Atualização do software"
+
+#: i2p2www/pages/global/nav.html:49
+msgid "API"
+msgstr "API"
+
+#: i2p2www/pages/global/nav.html:58
+msgid "Ministreaming library"
+msgstr ""
+
+#: i2p2www/pages/global/nav.html:63 i2p2www/pages/global/nav.html:116
+msgid "Applications"
+msgstr "Aplicações"
+
+#: i2p2www/pages/global/nav.html:65
+msgid "Supported applications"
+msgstr "Aplicações suportadas"
+
+#: i2p2www/pages/global/nav.html:66
+msgid "Bittorrent"
+msgstr "Bittorrent"
+
+#: i2p2www/pages/global/nav.html:69
+msgid "Protocols"
+msgstr "Protocolos"
+
+#: i2p2www/pages/global/nav.html:71
+msgid "Protocol stack"
+msgstr ""
+
+#: i2p2www/pages/global/nav.html:76
+msgid "Transports"
+msgstr ""
+
+#: i2p2www/pages/global/nav.html:78
+msgid "Transport layer overview"
+msgstr "Uma visão geral da camada de transporte"
+
+#: i2p2www/pages/global/nav.html:83
+msgid "Tunnels"
+msgstr "Túneis"
+
+#: i2p2www/pages/global/nav.html:85
+msgid "Tunnel implementation"
+msgstr "Implementação de túneis"
+
+#: i2p2www/pages/global/nav.html:86
+msgid "Unidirectional tunnels"
+msgstr "Túneis unidirecionais"
+
+#: i2p2www/pages/global/nav.html:87
+msgid "Old implementation"
+msgstr "Implementação antiga"
+
+#: i2p2www/pages/global/nav.html:90
+msgid "Naming and addressbook"
+msgstr "Sistema de nomes e livro de endereços"
+
+#: i2p2www/pages/global/nav.html:94
+msgid "Team"
+msgstr "Time"
+
+#: i2p2www/pages/global/nav.html:96
+msgid "Hall of Fame"
+msgstr "Salão da Fama"
+
+#: i2p2www/pages/global/nav.html:97
+msgid "Academic papers and peer review"
+msgstr "Publicações acadêmicas e revisão por pares"
+
+#: i2p2www/pages/global/nav.html:98
+msgid "Presentations, tutorials and articles"
+msgstr "Exposições, tutoriais e artigos"
+
+#: i2p2www/pages/global/nav.html:99
+msgid "Contact us"
+msgstr "Contacte-nos"
+
+#: i2p2www/pages/global/nav.html:102
+msgid "Help"
+msgstr "Ajuda"
+
+#: i2p2www/pages/global/nav.html:104
+msgid "FAQ"
+msgstr "Perguntas Frequentes"
+
+#: i2p2www/pages/global/nav.html:105
+msgid "How to browse I2P"
+msgstr "Como navegar na I2P"
+
+#: i2p2www/pages/global/nav.html:106
+msgid "Glossary"
+msgstr "Glossário"
+
+#: i2p2www/pages/global/nav.html:107
+msgid "Performance"
+msgstr "Desempenho"
+
+#: i2p2www/pages/global/nav.html:108 i2p2www/pages/site/contact.html:28
+msgid "Forums"
+msgstr "Fóruns"
+
+#: i2p2www/pages/global/nav.html:111
+msgid "Volunteer"
+msgstr "Voluntários"
+
+#: i2p2www/pages/global/nav.html:113
+msgid "Get involved!"
+msgstr "Envolva-se!"
+
+#: i2p2www/pages/global/nav.html:114
+msgid "Develop"
+msgstr "Desenvolver"
+
+#: i2p2www/pages/global/nav.html:117
+msgid "Licenses"
+msgstr "Licenças"
+
+#: i2p2www/pages/global/nav.html:118
+msgid "Release signing keys"
+msgstr ""
+
+#: i2p2www/pages/global/nav.html:119
+msgid "Signed keys"
+msgstr "Chaves assinadas"
+
+#: i2p2www/pages/global/nav.html:120
+msgid "Developers keys"
+msgstr "Chaves dos desenvolvedores"
+
+#: i2p2www/pages/global/nav.html:121
+msgid "Bug tracker"
+msgstr ""
+
+#: i2p2www/pages/global/nav.html:124
+msgid "Academic research"
+msgstr "Pesquisa acadêmica"
+
+#: i2p2www/pages/global/nav.html:125
+msgid "Open research questions"
+msgstr ""
+
+#: i2p2www/pages/global/nav.html:126
+msgid "Guides"
+msgstr "Guias"
+
+#: i2p2www/pages/global/nav.html:128
+msgid "New developers"
+msgstr "Novos desenvolvedores"
+
+#: i2p2www/pages/global/nav.html:129
+msgid "Using an IDE with I2P"
+msgstr ""
+
+#: i2p2www/pages/global/nav.html:130
+msgid "Developer guidelines and coding style"
+msgstr ""
+
+#: i2p2www/pages/global/nav.html:131
+msgid "Monotone"
+msgstr "Monotone"
+
+#: i2p2www/pages/global/nav.html:132
+msgid "New translators"
+msgstr "Novos tradutores"
+
+#: i2p2www/pages/global/nav.html:135
+msgid "Bounties"
+msgstr "Prêmios"
+
+#: i2p2www/pages/global/nav.html:136 i2p2www/pages/meetings/index.html:2
+msgid "Meetings"
+msgstr "Encontros"
+
+#: i2p2www/pages/global/nav.html:137
+msgid "Roadmap"
+msgstr "Plano de ação"
+
+#: i2p2www/pages/global/nav.html:138
+msgid "Task list"
+msgstr "Lista de tarefas"
+
+#: i2p2www/pages/global/nav.html:141
+msgid "Language"
+msgstr "Idioma"
+
+#: i2p2www/pages/meetings/index.html:4
+msgid "I2P Meetings ATOM Feed"
+msgstr ""
+
+#: i2p2www/pages/meetings/index.html:7
+msgid "Logs of past I2P meetings"
+msgstr "I2P - Atas de encontros passados"
+
+#: i2p2www/pages/meetings/index.html:9
+msgid "Meetings are currently on hold until a more suitable time can be chosen."
+msgstr ""
+
+#: i2p2www/pages/meetings/index.html:13
+#, python-format
+msgid ""
+"If you have something to discuss, please find the developers on IRC in "
+"#i2p-dev.\n"
+"Status updates from developers are also "
+"available."
+msgstr ""
+
+#: i2p2www/pages/meetings/show.html:2
+#, python-format
+msgid "I2P Development Meeting %(id)s"
+msgstr ""
+
+#: i2p2www/pages/meetings/show.html:10
+msgid "Full IRC Log"
+msgstr ""
+
+#: i2p2www/pages/papers/list.html:29
+msgid "By topic"
+msgstr ""
+
+#: i2p2www/pages/papers/list.html:35
+msgid "By date"
+msgstr ""
+
+#: i2p2www/pages/papers/list.html:41
+msgid "By author"
+msgstr ""
+
+#: i2p2www/pages/papers/list.html:83
+#, python-format
+msgid ""
+"Please send new or corrected entries to\n"
+"%(email)s.
\n"
+"If you can, please format them as BibTeX; see our\n"
+"BibTeX source page for examples.
\n"
+"Remember to include URLs if possible:\n"
+"offline papers are less useful."
+msgstr ""
+
+#: i2p2www/pages/site/contact.html:2
+msgid "Contact"
+msgstr "Contato"
+
+#: i2p2www/pages/site/contact.html:4
+msgid "Email"
+msgstr ""
+
+#: i2p2www/pages/site/contact.html:11
+msgid ""
+"Our primary IRC network is the Irc2P network within I2P; a default tunnel"
+" to this network is set up with new router installs.\n"
+" We are also present on multiple standard networks like OFTC,\n"
+" EIN and Freenode.\n"
+" All I2P-related channels on all these network are linked to the main "
+"channels on Irc2P via relay bots."
+msgstr ""
+
+#: i2p2www/pages/site/contact.html:19
+msgid "Channel list:"
+msgstr "Lista de canais:"
+
+#: i2p2www/pages/site/contact.html:21
+msgid "General i2p discussion"
+msgstr "I2P - Discussão geral"
+
+#: i2p2www/pages/site/contact.html:22
+msgid "Offtopic"
+msgstr ""
+
+#: i2p2www/pages/site/contact.html:23
+msgid "Development talk"
+msgstr ""
+
+#: i2p2www/pages/site/contact.html:24
+msgid "Help channel"
+msgstr "Canal de ajuda"
+
+#: i2p2www/pages/site/contact.html:29
+#, python-format
+msgid ""
+"Most of the discussion about I2P's development happens on the I2P developer forum. This is usually the best"
+" place to start with inquiries, if the dev IRC channel is inactive."
+msgstr ""
+
+#: i2p2www/pages/site/contact.html:33
+msgid "Mailing lists"
+msgstr ""
+
+#: i2p2www/pages/site/contact.html:34
+msgid ""
+"I2P does have a mailing list, but it is rarely used as the current small "
+"team of developers prefer to communicate via IRC or the developer forum. "
+"This may change in future."
+msgstr ""
+
+#: i2p2www/pages/site/contact.html:39
+msgid "Subscribing"
+msgstr ""
+
+#: i2p2www/pages/site/contact.html:40
+msgid ""
+"To subscribe to a mailing list, go to the list information page (linked "
+"below) and fill out the form. I2P-internal email addresses "
+"(foobar@mail.i2p) can be used."
+msgstr ""
+
+#: i2p2www/pages/site/contact.html:44
+msgid "Unsubscribing"
+msgstr ""
+
+#: i2p2www/pages/site/contact.html:45
+msgid ""
+"To unsubscribe from a mailing list or edit your subscription options, go "
+"to the list information page (linked below) and enter your subscription "
+"email address."
+msgstr ""
+
+#: i2p2www/pages/site/contact.html:49
+msgid "Lists"
+msgstr "Listas"
+
+#: i2p2www/pages/site/contact.html:52
+msgid "Archive"
+msgstr "Arquivo"
+
+#: i2p2www/pages/site/contact.html:53
+msgid ""
+"General I2P discussion - anything that doesn't fit in a different list "
+"goes here."
+msgstr ""
+
+#: i2p2www/pages/site/contact.html:59
+msgid ""
+"You don't like mailing lists? Then this is for you. All mailing lists are"
+" available via NNTP as well."
+msgstr ""
+
+#: i2p2www/pages/site/contact.html:64
+msgid "Group-List-mapping:"
+msgstr ""
+
+#: i2p2www/pages/site/contact.html:68
+msgid "Servers:"
+msgstr "Servidores:"
+
+#: i2p2www/pages/site/faq.html:2
+msgid "Frequently Asked Questions"
+msgstr "Perguntas Frequentes"
+
+#: i2p2www/pages/site/faq.html:4
+msgid "Index"
+msgstr "Índice"
+
+#: i2p2www/pages/site/faq.html:7
+msgid "General"
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:9 i2p2www/pages/site/faq.html:51
+msgid "What systems will I2P run on?"
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:10
+msgid "Whats an \"eepsite\" and how do I configure my browser so I can use them?"
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:11 i2p2www/pages/site/faq.html:264
+msgid "My router has very few active peers, is this OK?"
+msgstr "Meu roteador possui pouquíssimos nós ativos. Tudo bem?"
+
+#: i2p2www/pages/site/faq.html:12 i2p2www/pages/site/faq.html:499
+msgid "What do the Active x/y numbers mean in the router console?"
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:13 i2p2www/pages/site/faq.html:226
+msgid ""
+"My active peers / known peers / participating tunnels / connections / "
+"bandwidth vary dramatically over time! Is anything wrong?"
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:14 i2p2www/pages/site/faq.html:349
+msgid "Is using an outproxy safe?"
+msgstr "É seguro usar proxies de saída?"
+
+#: i2p2www/pages/site/faq.html:15 i2p2www/pages/site/faq.html:375
+msgid "Most of the eepsites within I2P are down?"
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:16 i2p2www/pages/site/faq.html:528
+msgid "What ports does I2P use?"
+msgstr "Quais portas a I2P usa?"
+
+#: i2p2www/pages/site/faq.html:17
+msgid "Why is I2P listening for connections on port 32000?"
+msgstr "Por que a I2P está esperando por conexões na porta 32000?"
+
+#: i2p2www/pages/site/faq.html:18 i2p2www/pages/site/faq.html:62
+msgid "I think I found a bug, where can I report it?"
+msgstr "Acho que encontrei uma falha. Onde posso reportá-la?"
+
+#: i2p2www/pages/site/faq.html:19 i2p2www/pages/site/faq.html:108
+msgid "What happened to *.i2p.net? What happened to jrandom? Is I2P dead?"
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:20 i2p2www/pages/site/faq.html:846
+msgid "I have a question!"
+msgstr "Tenho uma questão!"
+
+#: i2p2www/pages/site/faq.html:22
+msgid "Setup"
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:24 i2p2www/pages/site/faq.html:233
+msgid ""
+"My router has been up for several minutes and has zero or very few "
+"connections"
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:25 i2p2www/pages/site/faq.html:391
+msgid "Why is I2P so slow?"
+msgstr "Por que a I2P é tão lenta?"
+
+#: i2p2www/pages/site/faq.html:26 i2p2www/pages/site/faq.html:79
+msgid ""
+"I'm missing lots of hosts in my addressbook. What are some good "
+"subscription links?"
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:27 i2p2www/pages/site/faq.html:384
+msgid "How do I set up my own eepsite?"
+msgstr "Como faço para ter meu próprio eepsite?"
+
+#: i2p2www/pages/site/faq.html:28 i2p2www/pages/site/faq.html:417
+msgid "Bittorrent / I2PSnark / Azureus I2P Plugin Questions?"
+msgstr "Alguma questão sobre as extensões Bittorrent / I2PSnark / Azureus I2P?"
+
+#: i2p2www/pages/site/faq.html:29 i2p2www/pages/site/faq.html:424
+msgid "How do I connect to IRC within I2P?"
+msgstr "Como faço para me conectar ao IRC dentro da I2P?"
+
+#: i2p2www/pages/site/faq.html:30 i2p2www/pages/site/faq.html:282
+msgid "I can't access regular Internet sites through I2P."
+msgstr "Não consigo acessar os sites comuns da Internet através da I2P."
+
+#: i2p2www/pages/site/faq.html:31 i2p2www/pages/site/faq.html:297
+msgid "I can't access https:// or ftp:// sites through I2P."
+msgstr "Não consigo acessar endereços https:// ou ftp:// através da I2P."
+
+#: i2p2www/pages/site/faq.html:32 i2p2www/pages/site/faq.html:507
+msgid "Is it possible to use I2P as a SOCKS proxy?"
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:33 i2p2www/pages/site/faq.html:490
+msgid "How do I configure my browser?"
+msgstr "Como faço para configurar o meu navegador?"
+
+#: i2p2www/pages/site/faq.html:34 i2p2www/pages/site/faq.html:435
+msgid ""
+"How can I access the web console from my other machines or password "
+"protect it?"
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:35 i2p2www/pages/site/faq.html:475
+msgid "How can I use applications from my other machines?"
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:36 i2p2www/pages/site/faq.html:749
+msgid "How do I reseed manually?"
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:37 i2p2www/pages/site/faq.html:125
+msgid "My router is using too much CPU?!?"
+msgstr "Meu roteador está exigindo muito da CPU?!?!"
+
+#: i2p2www/pages/site/faq.html:39
+msgid "Misconception"
+msgstr "Equívocos"
+
+#: i2p2www/pages/site/faq.html:41 i2p2www/pages/site/faq.html:367
+msgid ""
+"How do I access IRC, BitTorrent, or other services on the regular "
+"Internet?"
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:42
+msgid ""
+"Is my router an \"exit node\"(outproxy) to the regular Internet? I don't "
+"want it to be."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:43 i2p2www/pages/site/faq.html:189
+msgid ""
+"I am opposed to certain types of content. How do I keep from "
+"distributing, storing, or accessing them?"
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:45
+msgid "Errors and Their Solutions"
+msgstr "Erros e suas soluções"
+
+#: i2p2www/pages/site/faq.html:47 i2p2www/pages/site/faq.html:785
+msgid ""
+"I'm using FreeBSD and when I start I2P I receive an error about "
+"libm.so.4!"
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:48
+msgid ""
+"In wrapper.log I see an error stating Protocol family "
+"unavailable when I2P is loading"
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:52 i2p2www/pages/site/faq.html:63
+#: i2p2www/pages/site/faq.html:80 i2p2www/pages/site/faq.html:109
+#: i2p2www/pages/site/faq.html:126 i2p2www/pages/site/faq.html:190
+#: i2p2www/pages/site/faq.html:227 i2p2www/pages/site/faq.html:234
+#: i2p2www/pages/site/faq.html:265 i2p2www/pages/site/faq.html:274
+#: i2p2www/pages/site/faq.html:283 i2p2www/pages/site/faq.html:298
+#: i2p2www/pages/site/faq.html:350 i2p2www/pages/site/faq.html:368
+#: i2p2www/pages/site/faq.html:376 i2p2www/pages/site/faq.html:385
+#: i2p2www/pages/site/faq.html:392 i2p2www/pages/site/faq.html:418
+#: i2p2www/pages/site/faq.html:425 i2p2www/pages/site/faq.html:436
+#: i2p2www/pages/site/faq.html:476 i2p2www/pages/site/faq.html:483
+#: i2p2www/pages/site/faq.html:491 i2p2www/pages/site/faq.html:500
+#: i2p2www/pages/site/faq.html:508 i2p2www/pages/site/faq.html:529
+#: i2p2www/pages/site/faq.html:737 i2p2www/pages/site/faq.html:750
+#: i2p2www/pages/site/faq.html:786 i2p2www/pages/site/faq.html:818
+#: i2p2www/pages/site/faq.html:847
+msgid "link"
+msgstr "linque"
+
+#: i2p2www/pages/site/faq.html:53
+#, python-format
+msgid ""
+"While I2P has been reported to run PCs as meagre as a low-end Pentium II "
+"with 64 MB of RAM, you'll have a much better experience on a Pentium III "
+"(or better) with 128MB of RAM (or more). A chart "
+"comparing the performance of the various JREs can be found at %(chart)s, but in short: it's at all possible, use"
+" Sun/Oracle Java or OpenJDK."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:57
+msgid ""
+"I2P has been tested on Windows, Linux, FreeBSD (see the note below), OSX, and OpenSolaris. There is work "
+"underway to bring I2P to the Android platform."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:65
+msgid "Here are some places, pick one or more."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:71
+msgid "Discuss with the developers on IRC in #i2p-dev"
+msgstr "Dialogue com os desenvolvedores via IRC em #i2p-dev"
+
+#: i2p2www/pages/site/faq.html:75
+msgid "Please include relevant information from the router logs and wrapper logs."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:81
+msgid ""
+"The default subscription is to http://www.i2p2.i2p/hosts.txt which is "
+"updated rarely.\n"
+"If you don't have another subscription, you may often have to use "
+"\"jump\" links which\n"
+"is annoying."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:87
+msgid ""
+"Here are some other public addressbook subscription links. You may wish "
+"to add one or two\n"
+"to your susidns "
+"subscription list.\n"
+"You don't need to add all of them, as they sync with each other "
+"periodically.\n"
+"The links using a cgi-bin application employ various strategies to "
+"minimize\n"
+"the number of duplicate addresses delivered, so they should be more "
+"efficient.\n"
+"Note that subscribing to a hosts.txt service is an act of \"trust\", as a"
+" malicious\n"
+"subscription could give you incorrect addresses. So think about whether "
+"you\n"
+"want to trust any of these.\n"
+"The operators of these services may have various policies for listing "
+"hosts.\n"
+"Presence on this list does not imply endorsement."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:110
+msgid ""
+"Jrandom was the lead developer of I2P and\n"
+"Syndie for several years.\n"
+"We do not know if or when jrandom will return.\n"
+"The *.i2p.net domains were left in a non-functioning state after a power\n"
+"outage at the hosting company."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:118
+#, python-format
+msgid ""
+"See this page for jrandom's parting message "
+"and additional information\n"
+"on the migration of *.i2p.net to this website."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:123
+msgid "I2P remains in active development."
+msgstr "O projeto I2P encontra-se em desenvolvimento."
+
+#: i2p2www/pages/site/faq.html:127
+msgid "There are many possible causes of high CPU usage. Here is a checklist:"
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:132
+msgid ""
+"Try to use either OpenJDK or Sun/Oracle Java if it's available for your "
+"system. You can check \n"
+"which version of java you have installed by typing java "
+"-version at a \n"
+"command/shell prompt. Performance tends to suffer with other "
+"implementations of java."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:139
+msgid ""
+"Are you running a BitTorrent client over I2P? Try reducing the number of "
+"torrents, the bandwidth limits,\n"
+"or try turning it off completely to see if that helps."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:145
+msgid ""
+"Are your bandwidth limits set too high? It is possible that too much "
+"traffic is going through your\n"
+"I2P router and it is overloaded. Try reducing the setting for share "
+"bandwidth percentage on the configuration page."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:150
+msgid ""
+"Make sure that you're running the latest version of I2P to get the "
+"benefits of increased performance and bug fixes."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:155
+msgid ""
+"Has enough memory been set aside for use by I2P? Look at the memory graph"
+" on the graphs page to see\n"
+"if the memory usage is \"pegged\"—the JVM is spending most of its "
+"time in\n"
+"garbage collection. Increase the setting "
+"wrapper.java.maxmemory in wrapper.config."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:162
+msgid ""
+"Is the CPU usage simply higher than you would like, or is it pegged at "
+"100% for a long time?\n"
+"If it's pegged, this could be a bug. Look in the logs for clues."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:168
+#, python-format
+msgid ""
+"You may be using the Java-based BigInteger library instead of the native "
+"version,\n"
+"especially if you are running on a new or unusual OS or hardware "
+"(OpenSolaris, mipsel, etc.).\n"
+"See the jbigi page for instructions on\n"
+"diagnosing, building, and testing methods."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:176
+msgid ""
+"If your native jbigi library is working fine, the biggest user of\n"
+"CPU may be routing traffic for participating tunnels. This uses CPU\n"
+"because at each hop a layer of encryption must be decoded.\n"
+"You can limit participating traffic in two ways - by reducing the\n"
+"share bandwidth on\n"
+"confignet.jsp,\n"
+"or by setting router.maxParticipatingTunnels=nnn on\n"
+"configadvanced.jsp."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:191
+msgid ""
+"Hmm. I2P is an anonymous network, so that's a tricky one.\n"
+"I2P is designed to withstand censorship, providing a means for everyone "
+"to communicate freely. \n"
+"The best way to keep your PC free of (encrypted) traffic that you dislike"
+" is to not use I2P.\n"
+"Freedom of speech has some costs.\n"
+"But let's address your question in three parts:"
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:200
+msgid ""
+"Distribution - All traffic on I2P is encrypted in multiple layers."
+" You don't know\n"
+"a message's contents, source, or destination.\n"
+"All traffic you route is internal to the I2P network, you are not an exit node (outproxy).\n"
+"Your only alternative is to refuse to route\n"
+"any traffic, by setting your share bandwidth or maximum "
+"participating tunnels to 0 (see above).\n"
+"It would be nice if you didn't do this, you should help the network by "
+"routing traffic for others.\n"
+"Over 95% of users route traffic for others."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:211
+msgid ""
+"Storage - I2P does not do distributed storage of content. You must"
+" be thinking of\n"
+"Freenet.\n"
+"Nobody's content is being stored on your computer by running I2P."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:218
+msgid ""
+"Access - If there are some eepsites you don't like, don't go "
+"there.\n"
+"Or, use a blocking proxy like Privoxy or some type of \"net nanny\"."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:228
+msgid ""
+"No. This is normal.\n"
+"All routers adjust dynamically to changing network conditions and demands."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:235
+msgid ""
+"You may need to reseed your I2P router. With recent versions of I2P you "
+"can go to http://localhost:7657/configreseed"
+" and click the Save Changes and Reseed Now button. If this "
+"method doesn't work—or you're using a very old version—you "
+"may need to reseed manually."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:238
+msgid ""
+"The reseed URL changed a few years ago. If this is your first install and"
+" you have installed\n"
+"an old (0.6.1.30 or earlier) release, or\n"
+"you have not run I2P in a long time, you must change the URL and then\n"
+"click \"Reseed\" on the console to find other routers.\n"
+"After your router is running,\n"
+"on configadvanced.jsp,"
+"\n"
+"add the line i2p.reseedURL=http://netdb.i2p2.de/\n"
+"OR i2p.reseedURL=http://i2pdb.tin0.de/netDb/ (either should "
+"work),\n"
+"then click \"Apply\", then click the \"reseed\" link on the left."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:249
+#, python-format
+msgid ""
+"This works if you are running 0.6.1.27 or later.\n"
+"If you are running release 0.6.1.31 or later, you probably don't need to "
+"do this.\n"
+"If you are running release 0.6.1.26 or earlier, either follow the\n"
+"manual reseed instructions below\n"
+"or install the latest release.\n"
+"Possible alternate method - add\n"
+"wrapper.java.additional.5=-Di2p.reseedURL=http://netdb.i2p2.de/\n"
+"to wrapper.config, shutdown the router completely, then start again, then"
+" click \"reseed\".\n"
+"Let us know if this works."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:260
+#, python-format
+msgid ""
+"...but you *really* should upgrade to "
+"the latest version."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:266
+msgid ""
+"If your router has 10 or more active peers, everything is fine. Changes "
+"in releases 0.6.1.31 and 0.6.1.32 improved the\n"
+"efficiency of the router and effectively reduced the number of active "
+"peers.\n"
+"The router should maintain connections to a few peers at all "
+"times.\n"
+"The best way to stay \"better-connected\" to the network is to share more bandwidth."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:273
+msgid ""
+"Is my router an \"exit node\" to the regular Internet? I don't want it to"
+" be."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:275
+msgid ""
+"No. Unlike Tor,\n"
+"\"exit nodes\" or \"outproxies\" are not an inherent part of the network."
+"\n"
+"Only volunteers who set up and run separate applications will relay "
+"traffic to the regular Internet.\n"
+"There are very, very few of these."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:284
+msgid ""
+"See above. There are very few HTTP \"outproxies\", they are not an "
+"inherent part of the network,\n"
+"and they may not be up.\n"
+"In addition, the old outproxies squid.i2p, true.i2p, and krabs.i2p have "
+"vanished.\n"
+"The only outproxy at the moment is false.i2p.\n"
+"To use it, edit your i2ptunnel "
+"settings for eepProxy\n"
+"and set your outproxy list to 'false.i2p' (only).\n"
+"Then stop and restart the eepProxy.\n"
+"If it doesn't work, the outproxy is not up. It is not I2P's fault.\n"
+"If your primary reason to use an anonymous network is to anonymously "
+"access sites\n"
+"on the regular Internet, you should probably try Tor."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:299
+msgid ""
+"Within I2P, there is no need for HTTPS, as all traffic is encrypted end-"
+"to-end.\n"
+"FTP is not supported for technical reasons."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:303
+msgid ""
+"There are no FTP \"outproxies\" to the Internet—it may not even be "
+"possible to set up one.\n"
+"Any other kind of outproxy may work if it's set up with a standard "
+"tunnel. \n"
+"If you would like to set up some type of outproxy, carefully research the"
+" potential risks.\n"
+"The I2P community may or may not be able to help with the technical "
+"aspects, feel free to ask."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:309
+msgid ""
+"As explained several times above, any existing outproxy isn't a core part"
+" of the network.\n"
+"They are services run by individuals and they may or may not\n"
+"be operational at any given time."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:314
+msgid ""
+"Update: Thanks to the work of h2ik, there is an https outproxy "
+"available for use via I2P. Starting with I2P 0.8.4 the tunnel is "
+"configured out of the box.
\n"
+"In case the https outproxy is not available in your version of I2P, you "
+"can add it easily by doing the following:"
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:320
+msgid ""
+"Open i2p tunnel "
+"manager. Scroll down to the bottom."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:325
+msgid ""
+"Choose CONNECT from New Client Tunnel dropdown list, click "
+"Create"
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:330
+#, python-format
+msgid ""
+"In the new page, name and describe your new https tunnel as"
+" you like.\n"
+"The Access Point is your local port for the new https proxy "
+"recommended port's 4445.\n"
+"Outproxy should be the outproxy's .i2p address which supports "
+"https. \n"
+"See this forum post of h2ik's for the "
+"address. \n"
+"Make sure Shared Client, Delay Connect, AutoStart "
+"are checked.\n"
+"Other options should be left at the defaults. Click Save. In tunnel "
+"manger, click the Start button next to your new tunnel."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:340
+msgid ""
+"In firefox, click through "
+"Tools>Options>Advanced>Network>Setting."
+"\n"
+"Untick Use this proxy for all protocol, set SSL proxy: to "
+"localhost:4445."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:345
+msgid "Done."
+msgstr "Feito."
+
+#: i2p2www/pages/site/faq.html:351
+#, python-format
+msgid ""
+"\n"
+"This is a question that only you can answer because the correct answer "
+"depends on your behaviours, your\n"
+"threat model, and how much you trust the "
+"outproxy operator."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:355
+msgid ""
+"Like Tor, I2P does not magically encrypt the Internet.\n"
+"You are vulnerable to snooping by the outproxy operators.\n"
+"The Tor"
+" FAQ\n"
+"does a good job of explaining this."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:361
+#, python-format
+msgid ""
+"In addition, you may be vulnerable to collusion between the outproxy "
+"operator\n"
+"and operators of other I2P services, if you use the same tunnels "
+"(\"shared clients\").\n"
+"There is additional discussion about this on %(zzz)s."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:369
+msgid ""
+"Unless an outproxy has been set up for the service you want to connect "
+"to, this cannot be done.\n"
+"There are only three types of outproxies running right now: HTTP, HTTPS, "
+"and email. Note that there is not a SOCKS outproxy.\n"
+"If this type of service is required, try Tor."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:377
+#, python-format
+msgid ""
+"If you consider every eepsite that has ever been created, yes, most of "
+"them are down.\n"
+"People and eepsites come and go.\n"
+"A good way to get started in I2P is check out a list of eepsites that are"
+" currently up.\n"
+"%(eepstatus)s tracks active eepsites."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:386
+msgid ""
+"Click on the Website link\n"
+"at the top of your router console for instructions."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:393
+msgid ""
+"Why are downloads, torrents, web browsing, and everything else so slow on"
+" I2P?\n"
+"The encryption and routing within the I2P network adds a substantial "
+"amount of overhead and limits bandwidth.\n"
+"Anonymity isn't free."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:398
+msgid ""
+"In addition, you and everybody else probably need to increase your "
+"bandwidth limits.\n"
+"Two key settings are the inbound and outbound bandwidth limiters on\n"
+"the configuration page.\n"
+"With the default settings of 32KBps you will generally get no better than"
+" 15KBps data transfer in I2PSnark.\n"
+"Increasing the settings (but keeping within your actual connection "
+"limitations)\n"
+"will increase the potential transfer rate for I2PSnark and all other "
+"applications."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:406
+msgid ""
+"Also, do you have sufficient share bandwidth configured to allow "
+"participating tunnels\n"
+"to route through your router? Believe it or not, allowing participating "
+"traffic\n"
+"keeps you well-integrated in the network and helps your own transfer "
+"speeds."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:411
+#, python-format
+msgid ""
+"I2P is a work in progress. Lots of improvements and fixes are being "
+"implemented, and\n"
+"generally speaking, running the latest release will help your "
+"performance.\n"
+"If you haven't, install the latest "
+"release."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:419
+#, python-format
+msgid ""
+"See the\n"
+"I2P Bittorrent FAQ"
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:426
+msgid ""
+"\n"
+"A tunnel to the main IRC server within I2P, Irc2P, is created when I2P is"
+" installed (see\n"
+"the I2PTunnel "
+"configuration page),\n"
+"and is automatically started when the I2P router starts. To connect to "
+"it, tell your IRC\n"
+"client to connect to localhost 6668. XChat-like client users"
+" can create a\n"
+"new network with the server localhost/6668 (remember to tick"
+" "Bypass\n"
+"proxy server" if you have a proxy server configured)."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:437
+msgid ""
+"For security purposes, the router's admin console by default only listens"
+"\n"
+"for connections on the local interface. However, with a little hacking,\n"
+"you can make it reachable remotely:"
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:445
+msgid ""
+"Open ~/.i2p/clients.config and replace
\n"
+"clientApp.0.args=7657 ::1,127.0.0.1 ./webapps/
\n"
+"with
\n"
+"clientApp.0.args=7657 0.0.0.0 ./webapps/"
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:453
+msgid ""
+"Go to http://localhost:7657/configui"
+"\n"
+"and add a console username and password if desired."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:459
+msgid ""
+"Go to http://localhost:7657/index.jsp"
+"\n"
+"and hit \"Graceful restart\", which restarts the JVM and reloads the "
+"client applications"
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:466
+msgid ""
+"After that fires up, you should now be able to reach your console "
+"remotely. Reload the router at\n"
+"http://127.0.0.1:7657 and you will be prompted for the username and "
+"password you specified in step 2\n"
+"above if your browser supports the authentication popup. Note: the\n"
+"0.0.0.0 above specifies an interface, not a network "
+"or netmask. 0.0.0.0\n"
+"means \"bind to all interfaces\", so it can be reachable on "
+"127.0.0.1:7657 as well as\n"
+"any LAN/WAN IP."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:477
+msgid ""
+"By default, the router I2CP interface (port 7654) binds to address "
+"127.0.0.1. To bind to 0.0.0.0, set the\n"
+"router advanced configuration option "
+"i2cp.tcp.bindAllInterfaces=true and restart."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:482
+msgid "Whats an \"eepsite\"?"
+msgstr "O que é um \"eepsite\"?"
+
+#: i2p2www/pages/site/faq.html:484
+msgid ""
+"An eepsite is a website that is hosted anonymously - you can access it by"
+"\n"
+"setting your web browser's HTTP proxy to use the web proxy (typically it\n"
+"listens on localhost port 4444), and browsing to the site."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:492
+#, python-format
+msgid ""
+"The proxy config for different browsers is on a \n"
+"separate page with screenshots. More advanced configs with external "
+"tools\n"
+"are possible but could introduce leaks in your setup."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:501
+msgid ""
+"x is the number of peers you've sent or received a message from\n"
+"successfully in the last minute, y is the number of peers seen in the "
+"last\n"
+"hour or so."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:509
+msgid ""
+"The SOCKS proxy is working as of release 0.7.1. SOCKS 4/4a/5 are "
+"supported.\n"
+"There is no SOCKS outproxy so it is of limited use."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:513
+msgid ""
+"In addition, many applications leak sensitive\n"
+"information that could identify you on the Internet. I2P only filters\n"
+"connection data, but if the program you intend to run sends this\n"
+"information as content, I2P has no way to protect your anonymity. For\n"
+"example, some mail applications will send the IP address of the machine\n"
+"they are running on to a mail server. There is no way for I2P to filter\n"
+"this, thus using I2P to 'socksify' existing applications is possible, but"
+"\n"
+"extremely dangerous."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:523
+#, python-format
+msgid ""
+"If you would like more information on the socks proxy application anyway,"
+"\n"
+"there are some helpful hints on the socks page."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:530
+msgid ""
+"Okay, here's a rundown of the default ports (everything is configurable\n"
+"through various settings, of course):"
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:539
+msgid ""
+"Internet-facing ports\n"
+"Note: New installs as of release 0.7.8 do not use port 8887; they select "
+"a random port\n"
+"between 9000 and 31000 when the program is run for the first time.\n"
+"The selected port is shown on the router configuration page."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:547
+msgid ""
+"Outbound UDP from the random port noted on the configuration page to "
+"arbitrary remote UDP ports, allowing replies\n"
+" "
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:552
+msgid ""
+"Outbound TCP from random high ports to arbitrary remote TCP ports\n"
+" "
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:557
+msgid ""
+"(optional, but recommended) Inbound UDP to the port noted on configuration page from "
+"arbitrary locations\n"
+" "
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:562
+msgid ""
+"(optional, but recommended) Inbound TCP to the port noted on configuration page from "
+"arbitrary locations
\n"
+"Inbound TCP may be disabled on the configuration page."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:568
+msgid ""
+"Outbound UDP on port 123, allowing replies
\n"
+"This is necessary for I2P's internal time sync (via SNTP - \n"
+"querying a random SNTP host in pool.ntp.org or another\n"
+"server you specify)"
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:579
+msgid ""
+"Local I2P ports, listening only to local connections by default,\n"
+"except where noted:"
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:585
+msgid ""
+"1900: UPnP SSDP UDP multicast listener.\n"
+"Cannot be changed. Binds to all interfaces.\n"
+"May be disabled on confignet.jsp."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:592
+msgid ""
+"2827: BOB bridge, a higher level socket API for clients\n"
+"Disabled by default.\n"
+"May be enabled/disabled on configclients.jsp.\n"
+"May be changed in the bob.config file."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:600
+msgid ""
+"4444: HTTP proxy\n"
+"May be disabled or changed on the i2ptunnel page in the router "
+"console.\n"
+"May also be configured to be bound to a specific interface or all "
+"interfaces."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:607
+msgid ""
+"4445: HTTPS proxy\n"
+"May be disabled or changed on the i2ptunnel page in the router "
+"console.\n"
+"May also be configured to be bound to a specific interface or all "
+"interfaces."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:614
+msgid ""
+"6668: IRC proxy\n"
+"May be disabled or changed on the i2ptunnel page in the router "
+"console.\n"
+"May also be configured to be bound to a specific interface or all "
+"interfaces."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:621
+msgid ""
+"7652: UPnP HTTP TCP event listener.\n"
+"Binds to the LAN address.\n"
+"May be changed with advanced config i2np.upnp.HTTPPort=nnnn.\n"
+"May be disabled on confignet.jsp."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:629
+msgid ""
+"7653: UPnP SSDP UDP search response listener.\n"
+"Binds to all interfaces.\n"
+"May be changed with advanced config i2np.upnp.SSDPPort=nnnn.\n"
+"May be disabled on confignet.jsp."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:637
+msgid ""
+"7654: I2P Client Protocol port, used by client apps.\n"
+"May be changed to a different port on\n"
+"configclients.jsp"
+"\n"
+"but this is not recommended.\n"
+"May be to bind to a different interface or all interfaces, or disabled, "
+"on\n"
+"configclients.jsp."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:647
+msgid ""
+"7655: UDP for SAM bridge, a higher level socket API for clients\n"
+"Only opened when a SAM V3 client requests a UDP session.\n"
+"May be enabled/disabled on configclients.jsp.\n"
+"May be changed in the clients.config file with the SAM command line "
+"option sam.udp.port=nnnn."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:655
+msgid ""
+"7656: SAM bridge, a higher level socket API for clients\n"
+"Disabled by default for new installs as of release 0.6.5.\n"
+"May be enabled/disabled on configclients.jsp.\n"
+"May be changed in the clients.config file."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:663
+msgid ""
+"7657: Your router console\n"
+"May be disabled in the clients.config file.\n"
+"May also be configured to be bound to a specific interface or all "
+"interfaces in that file."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:670
+msgid ""
+"7658: Your eepsite\n"
+"May be disabled in the clients.config file.\n"
+"May also be configured to be bound to a specific interface or all "
+"interfaces in the jetty.xml file."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:677
+msgid ""
+"7659: Outgoing mail to smtp.postman.i2p\n"
+"May be disabled or changed on the i2ptunnel page in the router "
+"console.\n"
+"May also be configured to be bound to a specific interface or all "
+"interfaces."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:684
+msgid ""
+"7660: Incoming mail from pop.postman.i2p\n"
+"May be disabled or changed on the i2ptunnel page in the router "
+"console.\n"
+"May also be configured to be bound to a specific interface or all "
+"interfaces."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:691
+msgid ""
+"8998: mtn.i2p2.i2p (Monotone - disabled by default)\n"
+"May be disabled or changed on the i2ptunnel page in the router "
+"console.\n"
+"May also be configured to be bound to a specific interface or all "
+"interfaces."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:698
+msgid ""
+"31000: Local connection to the wrapper control channel port.\n"
+"Outbound to 32000 only, does not listen on this port.\n"
+"Starts at 31000 and will increment until 31999 looking for a free port.\n"
+"To change, see the\n"
+"wrapper documentation.\n"
+"For more information see below."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:708
+msgid ""
+"32000: Local control channel for the service wrapper.\n"
+"To change, see the\n"
+"wrapper documentation.\n"
+"For more information see below."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:720
+msgid ""
+"The local I2P ports and the I2PTunnel ports do not need to be reachable "
+"from \n"
+"remote machines, but *should* be reachable locally. You can also create"
+" \n"
+"additional ports for I2PTunnel instances via "
+"http://localhost:7657/i2ptunnel/ \n"
+"(and in turn, would need to get your firewall to allow you local access, "
+"but \n"
+"not remote access, unless desired)."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:728
+msgid ""
+"So, to summarize, nothing needs to be reachable by unsolicited remote "
+"peers, but\n"
+"if you can configure your NAT/firewall to allow inbound UDP and TCP the "
+"outbound facing port, you'll"
+"\n"
+"get better performance. You will also need to be able to send outbound "
+"UDP packets\n"
+"to arbitrary remote peers (blocking IPs randomly with something like "
+"PeerGuardian\n"
+"only hurts you - don't do it)."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:736
+msgid "Why is I2P listening on port 32000?"
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:738
+msgid ""
+"The Tanuki java service wrapper that we use opens this port—bound "
+"to localhost—in order \n"
+"to communicate with software running inside the JVM. When the JVM is "
+"launched it is given a key \n"
+"so it can connect to the wrapper. After the JVM establishes its "
+"connection \n"
+"to the wrapper, the wrapper refuses any additional connections."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:744
+msgid ""
+"More information can be found in the \n"
+"wrapper documentation."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:751
+msgid ""
+"An I2P router only needs to be seeded once, to join the network for the "
+"first time.\n"
+"Reseeding is nothing more than sending plain HTTP GET requests\n"
+"to fetch a directory listing and download multiple \"routerInfo\" files\n"
+"from a predefined reseed URL."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:758
+msgid ""
+"A typical symptom of a failed reseed is the \"Known\" indicator\n"
+"(on the left sidebar of the router console) displaying a very small value"
+"\n"
+"(often less than 5) which does not increase. This can occur, among other "
+"things,\n"
+"if your firewall limits outbound traffic, and blocked the reseed request."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:765
+msgid "To reseed an I2P router manually, do the following:"
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:768
+msgid "Stop your I2P router"
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:771
+msgid ""
+"Open http://netdb.i2p2.de/ using a "
+"web browser"
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:774
+msgid "Save a dozen \"routerInfo\" files to your I2P \"netDb\" directory"
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:781
+msgid "Start your I2P router"
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:788
+msgid ""
+"When trying to start the router using \"i2prouter start\", you may see "
+"output like the following:"
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:793
+msgid ""
+"\n"
+"In order to be inclusive and try to ensure that I2P will run on as many "
+"systems \n"
+"as possible, up until I2P 0.8.9 we used a java wrapper \n"
+"compiled for FreeBSD 6.x. If you're receiving this error you most likely "
+"are missing the necessary compatibility libraries.\n"
+"These libraries may be installed by performing the following steps:"
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:801
+msgid ""
+"Switch to the root user with su or log in as "
+"root."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:807
+#, python-format
+msgid ""
+"If you cannot install these compatibility libraries (or do not want to), "
+"other\n"
+"possibilities would be to compile the wrapper for your\n"
+"system, starting I2P with the runplain.sh script, or you"
+" can\n"
+"replace the wrapper with one from the source tarball."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:813
+msgid ""
+"For the 0.8.9 release of I2P, the wrapper was upgraded to v3.5.12 and "
+"compiled on systems running FreeBSD 7.2."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:817
+msgid ""
+"In wrapper.log I see an error that states \"Protocol "
+"family unavailable\" when loading the Router Console"
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:819
+msgid ""
+"Often this error will occur with any network enabled java software on "
+"some systems that are configured to use IPv6 by default. There are a few "
+"ways to solve this:"
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:824
+msgid ""
+"On Linux based systems, you can echo 0 > "
+"/proc/sys/net/ipv6/bindv6only"
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:826
+msgid "Look for the following lines in wrapper.config."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:830
+msgid ""
+"If the lines are there, uncomment them by removing the \"#\"s. If the "
+"lines are not there, add them without the \"#\"s."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:833
+msgid ""
+"Another option would be to remove the ::1 from "
+"~/.i2p/clients.config"
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:837
+msgid ""
+"WARNING: For any changes to wrapper.config "
+"to take effect, you must completely\n"
+"stop the router and the wrapper. Clicking Restart on your\n"
+"router console will NOT reread this file! You must\n"
+"click Shutdown, wait 11 minutes, then start I2P."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:848
+#, python-format
+msgid ""
+"Great! Find us on IRC irc.freenode.net #i2p or post to\n"
+"the forum and we'll post it here (with\n"
+"the answer, hopefully)."
+msgstr ""
+
+#: i2p2www/pages/site/impressum.html:4
+msgid "German laws"
+msgstr ""
+
+#: i2p2www/pages/site/index.html:2
+msgid "I2P Anonymous Network"
+msgstr ""
+
+#: i2p2www/pages/site/index.html:4
+msgid ""
+"Anonymous peer-to-peer distributed communication layer built with open "
+"source tools and designed to run any traditional Internet service such as"
+" email, IRC or web hosting."
+msgstr ""
+
+#: i2p2www/pages/site/index.html:7
+msgid "What does I2P do for you?"
+msgstr ""
+
+#: i2p2www/pages/site/index.html:8
+msgid ""
+"The I2P network provides strong privacy protections for communication "
+"over the Internet. Many activities that would risk your privacy on the "
+"public Internet can be conducted anonymously inside I2P."
+msgstr ""
+
+#: i2p2www/pages/site/index.html:9
+#, python-format
+msgid "Get I2P %(version)s"
+msgstr ""
+
+#: i2p2www/pages/site/index.html:13
+msgid "What is I2P?"
+msgstr ""
+
+#: i2p2www/pages/site/index.html:15
+msgid ""
+"I2P is an anonymous overlay network - a network within a network. It is "
+"intended to protect communication from dragnet surveillance and "
+"monitoring by third parties such as ISPs.\n"
+msgstr ""
+
+#: i2p2www/pages/site/index.html:18
+msgid ""
+"I2P is used by many people who care about their privacy: activists, "
+"oppressed people, journalists and whistleblowers, as well as the average "
+"person.\n"
+msgstr ""
+
+#: i2p2www/pages/site/index.html:21
+msgid ""
+"No network can be \"perfectly anonymous\". The continued goal of I2P is "
+"to make attacks more and more difficult to mount. Its anonymity will get "
+"stronger as the size of the network increases and with ongoing academic "
+"review.\n"
+msgstr ""
+
+#: i2p2www/pages/site/index.html:24
+msgid ""
+"I2P is available on desktops, embedded systems (like the Raspberry Pi) "
+"and Android phones. Help spread the word!\n"
+msgstr ""
+
+#: i2p2www/pages/site/index.html:28
+msgid "Read more…"
+msgstr ""
+
+#: i2p2www/pages/site/index.html:33
+msgid "What can you do with I2P?"
+msgstr ""
+
+#: i2p2www/pages/site/index.html:36
+#, python-format
+msgid ""
+"Email: Integrated web mail interface,"
+" plugin for serverless email."
+msgstr ""
+
+#: i2p2www/pages/site/index.html:41
+#, python-format
+msgid ""
+"Web browsing: Anonymous "
+"websites, gateways to and from the public Internet."
+msgstr ""
+
+#: i2p2www/pages/site/index.html:46
+#, python-format
+msgid ""
+"Blogging and forums: "
+"Blogging and Syndie plugins."
+msgstr ""
+
+#: i2p2www/pages/site/index.html:51
+#, python-format
+msgid ""
+"Website hosting: Integrated"
+" anonymous web server."
+msgstr ""
+
+#: i2p2www/pages/site/index.html:56
+#, python-format
+msgid ""
+"Real-time chat: Instant "
+"messaging and IRC clients."
+msgstr ""
+
+#: i2p2www/pages/site/index.html:61
+#, python-format
+msgid ""
+"File sharing: ED2K and "
+"Gnutella clients, integrated BitTorrent client."
+msgstr ""
+
+#: i2p2www/pages/site/index.html:66
+#, python-format
+msgid ""
+"Decentralized file "
+"storage: Tahoe-LAFS distributed filesystem plugin."
+msgstr ""
+
+#: i2p2www/pages/site/index.html:71
+#, python-format
+msgid "More supported applications…"
+msgstr ""
+
+#: i2p2www/pages/site/index.html:79
+msgid "News & Updates"
+msgstr ""
+
+#: i2p2www/pages/site/links.html:4
+msgid "Recommended Links & Resources"
+msgstr ""
+
+#: i2p2www/pages/site/links.html:5
+#, python-format
+msgid ""
+"See also the page with\n"
+"links to presentations, videos, and tutorials about"
+" I2P."
+msgstr ""
+
+#: i2p2www/pages/site/links.html:12
+msgid "I2P on the web"
+msgstr ""
+
+#: i2p2www/pages/site/links.html:20
+msgid "Friends of I2P"
+msgstr ""
+
+#: i2p2www/pages/site/links.html:32
+msgid "More Projects and Documentation"
+msgstr ""
+
+#: i2p2www/pages/site/links.html:42
+msgid "Press"
+msgstr ""
+
+#: i2p2www/pages/site/links.html:46
+msgid "Boards, newssite, others"
+msgstr ""
+
+#: i2p2www/pages/site/links.html:50
+msgid "Very Old Stuff"
+msgstr ""
+
diff --git a/i2p2www/translations/ro/LC_MESSAGES/comparison.po b/i2p2www/translations/ro/LC_MESSAGES/comparison.po
new file mode 100644
index 00000000..3a837f3e
--- /dev/null
+++ b/i2p2www/translations/ro/LC_MESSAGES/comparison.po
@@ -0,0 +1,872 @@
+# Romanian translations for I2P.
+# Copyright (C) 2013 ORGANIZATION
+# This file is distributed under the same license as the I2P project.
+#
+# Translators:
+msgid ""
+msgstr ""
+"Project-Id-Version: I2P\n"
+"Report-Msgid-Bugs-To: http://trac.i2p2.de\n"
+"POT-Creation-Date: 2013-10-26 22:39+0000\n"
+"PO-Revision-Date: 2013-11-12 14:08+0000\n"
+"Last-Translator: polearnik \n"
+"Language-Team: Romanian "
+"(http://www.transifex.com/projects/p/I2P/language/ro/)\n"
+"Plural-Forms: nplurals=3; "
+"plural=(n==1?0:(((n%100>19)||((n%100==0)&&(n!=0)))?2:1))\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=utf-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"Generated-By: Babel 0.9.6\n"
+
+#: i2p2www/pages/site/comparison/freenet.html:2
+msgid "I2P Compared to Freenet"
+msgstr "I2P in comparatie cu Freenet"
+
+#: i2p2www/pages/site/comparison/freenet.html:8
+msgid ""
+"Freenet is a fully distributed, peer to peer anonymous publishing "
+"network, offering \n"
+"secure ways to store data, as well as some approaches attempting to "
+"address the loads\n"
+"of a flash flood. While Freenet is designed as a distributed data store,"
+" people have\n"
+"built applications on top of it to do more generic anonymous "
+"communication, such as \n"
+"static websites and message boards."
+msgstr ""
+"Freenet este o rețea de publicare anonima distribuita pe deplin, egal la "
+"egal , oferind metode sigure de a stoca date, precum și încearcă să facă "
+"fata inundărilor de trafic. În timp ce Freenet este conceput ca un "
+"depozit de date distribuite, persoane au construit aplicații pentru a "
+"face comunicarea anonimă mai generice, cum ar fi site-uri web statice și "
+"forumuri."
+
+#: i2p2www/pages/site/comparison/freenet.html:16
+#, python-format
+msgid ""
+"Compared to I2P, Freenet offers some substantial benefits - it is a "
+"distributed data\n"
+"store, while I2P is not, allowing people to retrieve the content "
+"published by others \n"
+"even when the publisher is no longer online. In addition, it should be "
+"able to \n"
+"distribute popular data fairly efficiently. I2P itself does not and will"
+" not provide \n"
+"this functionality. On the other hand, there is overlap for users who "
+"simply want to \n"
+"communicate with each other anonymously through websites, message boards,"
+" file sharing\n"
+"programs, etc. There have also been some attempts to develop a "
+"distributed data \n"
+"store to run on top of I2P,\n"
+"(most recently a port of Tahoe-LAFS)\n"
+"but nothing is yet ready for general use."
+msgstr ""
+"Comparativ cu I2P, Freenet oferă unele avantaje substanțiale - este un "
+"depozit de date distribuite, în timp ce I2P nu este, permite oamenilor "
+"pentru a prelua conținutul publicat de către alte persoane, chiar atunci "
+"când editorul nu mai este on-line. În plus, ar trebui să fie în măsură de"
+" a distribui date populare destul de eficient. I2P în sine nu are și nu "
+"va oferi această funcționalitate. Pe de altă parte, există o suprapunere "
+"utilizatorilor care doar să comunice unul cu celălalt anonim prin "
+"intermediul site-uri, forumuri, programe de file sharing, etc asemenea, "
+"au existat câteva tentative de a elabora un magazin de date distribuite "
+"pentru a rula pe partea de sus a I2P, (cel mai recent un port de Tahoe-LAFS ), dar nimic nu este inca gata "
+"pentru uz general."
+
+#: i2p2www/pages/site/comparison/freenet.html:29
+msgid ""
+"However, even ignoring any implementations issues, there are some "
+"concerns \n"
+"about Freenet's algorithms from both a scalability and anonymity "
+"perspective, owing \n"
+"largely to Freenet's heuristic driven routing. The interactions of "
+"various techniques \n"
+"certainly may successfully deter various attacks, and perhaps some "
+"aspects of the \n"
+"routing algorithms will provide the hoped for scalability. "
+"Unfortunately, not much\n"
+"analysis of the algorithms involved has resulted in positive results, but"
+" there is still\n"
+"hope. At the very least, Freenet does provide substantial anonymity "
+"against an attacker\n"
+"who does not have the resources necessary to analyze it further."
+msgstr ""
+"Cu toate acestea, chiar și ignorând orice probleme implementării, există "
+"unele preocupări cu privire algoritmi Freenet scalabilitate și de "
+"perspectivă anonimata, datorită în mare parte la euristica Freenet "
+"condusa de rutare. Interacțiunile de diferite tehnici de siguranță pot "
+"descuraja cu succes diferite atacuri, și, probabil, unele aspecte ale "
+"algoritmilor de rutare va oferi sperat pentru scalabilitate. Din păcate, "
+"analiza nu demult a algoritmilor implicate a dus la rezultate pozitive, "
+"dar încă mai există speranță. Cel puțin, Freenet nu oferă anonimatul "
+"substanțial față de un atacator care nu are resursele necesare pentru a "
+"analiza în continuare."
+
+#: i2p2www/pages/site/comparison/index.html:2
+msgid "Comparing I2P to other projects"
+msgstr "I2P in comparatie cu alte proiecte"
+
+#: i2p2www/pages/site/comparison/index.html:4
+msgid ""
+"There are a great many other applications and projects working on "
+"anonymous \n"
+"communication and I2P has been inspired by much of their efforts. This "
+"is not \n"
+"a comprehensive list of anonymity resources - both freehaven's \n"
+"Anonymity "
+"Bibliography\n"
+"and GNUnet's related "
+"projects\n"
+"serve that purpose well. That said, a few systems stand out for further\n"
+"comparison. The following have individual comparison pages:"
+msgstr ""
+"Există o mulțime de alte aplicații și proiecte ce lucrează asupra "
+"comunicării anonimă și I2P a fost inspirat de o mare parte a eforturilor "
+"lor. Aceasta nu este o listă completă a resurselor de anonimat - Bibliografie "
+"Anonimatului și de GNUnet proiecte legate de servesc acestui scop. Asa spus, câteva "
+"sisteme se disting prin comparație continua. Următoarele pagini au "
+"comparații individuale :"
+
+#: i2p2www/pages/site/comparison/index.html:20
+#, python-format
+msgid ""
+"The following are discussed on the other "
+"networks page:"
+msgstr ""
+"Următoarele sunt discutate pe paginaalte "
+"retele: "
+
+#: i2p2www/pages/site/comparison/index.html:32
+#, python-format
+msgid ""
+"The content of this page is subject to update, discussion and dispute, "
+"and we welcome comments and additions.\n"
+"You may contribute an analysis by entering a new "
+"ticket on Trac."
+msgstr ""
+"Conținutul acestei pagini este subiectul actualizarii, discuții și "
+"dispute, și observații și completări sunt binevenite. Puteți contribui o "
+"analiză prin introducerea unui bilet nou pe Trac "
+"."
+
+#: i2p2www/pages/site/comparison/other-networks.html:2
+msgid "I2P Compared to Other Anonymous Networks"
+msgstr "I2P Comparativ cu alte rețele anonime"
+
+#: i2p2www/pages/site/comparison/other-networks.html:5
+msgid "The following networks are discussed on this page."
+msgstr "Urmatoarele rețele sunt discutate pe aceasta pagina."
+
+#: i2p2www/pages/site/comparison/other-networks.html:16
+#, python-format
+msgid ""
+"Most of the following sections are fairly old, and may not be accurate.\n"
+"For an overview of available comparisons, see the\n"
+"main network comparisons page.\n"
+"You may contribute an analysis by entering a\n"
+"new ticket on Trac."
+msgstr ""
+"Cele mai multe dintre următoarele secțiuni sunt destul de vechi, și ar "
+"putea să nu fie exacte. Pentru o privire de ansamblu asupra comparații "
+"disponibile, a se vedea href=\"%(comparison)s\"> pagina principală "
+"comparații rețea . Puteți contribui o analiză prin introducerea unui"
+" bilet nou pe Trac ."
+
+#: i2p2www/pages/site/comparison/other-networks.html:29
+#, python-format
+msgid ""
+"Morphmix and Tarzan are both fully distributed, peer to peer networks of"
+" \n"
+"anonymizing proxies, allowing people to tunnel out through the low "
+"latency \n"
+"mix network. Morphmix includes some very interesting collusion detection"
+" \n"
+"algorithms and Sybil defenses, while Tarzan makes use of the scarcity of "
+"IP\n"
+"addresses to accomplish the same. The two primary differences between \n"
+"these systems and I2P are related to I2P's threat model \n"
+"and their out-proxy design (as opposed to providing both sender and "
+"receiver \n"
+"anonymity). There is source code available to both systems, but we are "
+"not aware \n"
+"of their use outside of academic environments."
+msgstr ""
+"Morphmix și Tarzan sunt ambele complet distribuite , de tip peer-to-peer "
+"rețelele de proxy-uri anonime, care permit oamenilor să tunel prin "
+"intermediul rețelei de amestec scăzut latență. Morphmix include unele "
+"algoritmi foarte interesante de detectare a comploturilor și apărare "
+"Sybil, în timp ce Tarzan face uz de deficitul de adrese IP pentru a "
+"realiza aceasta. Cele două diferențe principale între aceste sisteme și "
+"I2P sunt legate de modelul amenințare I2P "
+" și proiectarea lor de-proxy (spre deosebire de a oferi atât "
+"anonimare expeditorului și receptorului). Există un cod sursă disponibil "
+"pentru ambele sisteme, dar noi nu sunt constienti de utilizarea lor în "
+"afara mediilor academice."
+
+#: i2p2www/pages/site/comparison/other-networks.html:153
+#, python-format
+msgid ""
+"\n"
+"Mixminion and Mixmaster are networks to support anonymous email against a"
+" very\n"
+"powerful adversary.\n"
+"High-latency messaging applications running on top of I2P\n"
+"(for example Syndie or I2PBote)\n"
+"may perhaps prove adequate to meet the threat\n"
+"model of those adversaries, while running in parallel along side the "
+"needs of low latency users, to provide\n"
+"a significantly larger anonymity set.\n"
+"High-latency support within the I2P router itself may or may not be added"
+" in a distant future release.\n"
+"It is too early to say if I2P will meet the needs of users requiring "
+"extreme protection for email."
+msgstr ""
+"Mixminion și Mixmaster sunt rețele de suport e-mail anonim împotriva unui"
+" adversar foarte puternic. Aplicații high-latență de mesagerie care "
+"rulează pe partea de sus a I2P (de exemplu, "
+"Syndie sau I2PBote) se poate dovedi, probabil, suficient pentru a "
+"satisface modelul amenințarea acestor adversari, în timp ce rulează în "
+"paralel de-a lungul partea de nevoile utilizatorilor latență redusă, "
+"pentru a oferi un set de anonimat semnificativ mai mare. Suport de înaltă"
+" latență în router-ul I2P în sine poate sau nu poate fi adăugat într-un "
+"comunicat viitor îndepărtat. Este prea devreme pentru a spune dacă I2P va"
+" satisface nevoile utilizatorilor care necesită protecție extrem de "
+"e-mail."
+
+#: i2p2www/pages/site/comparison/other-networks.html:165
+msgid ""
+"As with Tor and Onion Routing, \n"
+"both Mixminion and Mixmaster take the directory based approach as well."
+msgstr ""
+"Ca și în cazul Tor și ceapa de rutare, atât Mixminion și Mixmaster ia o "
+"abordare bazată pe directorul "
+
+#: i2p2www/pages/site/comparison/other-networks.html:175
+#, python-format
+msgid ""
+"JAP (Java Anonymous Proxy) is a network of mix cascades for anonymizing "
+"web requests,\n"
+"and as such it has a few centralized nodes (participants in the cascade) "
+"that blend\n"
+"and mix requests from clients through the sequence of nodes (the cascade)"
+" before \n"
+"proxying out onto the web. The scope, threat model, and security is "
+"substantially \n"
+"different from I2P, but for those who don't require significant anonymity"
+" but still\n"
+"are not satisfied with an Anonymizer-like service, JAP is worth "
+"reviewing. One\n"
+"caution to note is that anyone under the jurisdiction of the German "
+"courts may want\n"
+"to take care, as the German Federal Bureau of Criminal Investigation "
+"(FBCI) has \n"
+"successfully mounted an \n"
+"attack \n"
+"on the network. Even though the method of this attack was later found to"
+" be illegal \n"
+"in the German courts, the fact that the data was successfully collected "
+"is the \n"
+"concern. Courts change their minds based upon circumstance, and this is "
+"evidence that \n"
+"if a government body or intelligence agency wanted to, they could gather "
+"the data, even \n"
+"if it may be found inadmissible in some courts later)"
+msgstr ""
+"JAP ( Java Proxy Anonim ) este o rețea de cascade de amestece pentru "
+"anonimizarea cererilor de web , și , ca atare, are câteva noduri "
+"centralizate ( participanții la cascada ), care amesteca cereri de la "
+"clienti prin secvența de noduri (cascadă ) înainte de proxy de pe web . "
+"Domeniul de aplicare , modelul de amenințare , si siguranța este "
+"substanțial diferită de I2P , dar pentru cei care nu au nevoie de "
+"anonimat semnificativ , dar încă nu sunt mulțumit cu un Anonymizer - cum "
+"ar fi serviciu , JAP este în valoare de revizuire . O remarcare de "
+"prudenta este faptul că oricine sub jurisdicția instanțelor germane ar "
+"putea dori să aibă grijă , ca Biroul Federal German de Investigații "
+"Penale ( FBCI ) a montat cu succes un atac < /a> pe "
+"rețea . Chiar dacă metoda a acestui atac a fost ulterior dovedit a fi "
+"ilegal în instanțele germane , faptul că datele au fost colectate cu "
+"succes . Instanțele schimba mintea lor bazate pe situație , iar acest "
+"lucru este o dovadă că în cazul în care un organism guvernamental sau "
+"agenția de informații a vrut , ar putea aduna date , chiar dacă acesta "
+"poate fi găsite inadmisibile în unele instanțe mai târziu )\n"
+
+#: i2p2www/pages/site/comparison/other-networks.html:197
+#, python-format
+msgid ""
+"Both of these systems work through the same basic \n"
+"antnet routing, providing some degree of\n"
+"anonymity based on the threat model of providing plausible deniability "
+"against a simple \n"
+"non-colluding adversary. With the antnet routing, they first either do a"
+" random walk or a \n"
+"broadcast search to find some peer with the data or identity desired, and"
+" then use a feedback\n"
+"algorithm to optimize that found path. This works well for applications "
+"that merely want to know \n"
+"what other people around them have to offer - \"How are y'all doing\" vs."
+" \"Hey Alice, how are you\" - \n"
+"you basically get a local cluster of nodes that can share files with and "
+"maintain some degree of \n"
+"anonymity (though you don't have much control over who is in that group "
+"of peers)."
+msgstr ""
+"Ambele din aceste sisteme funcționează prin aceeași baza antnet de rutare, oferind un anumit grad de "
+"anonimat bazat pe modelul amenințarea de a oferi negare plauzibilă față "
+"de un simplu adversar non-conspiră. Cu rutare antnet, ei în primul rând, "
+"fie fac o plimbare aleatoare sau o căutare difuzata a găsit unii "
+"utilizatori cu datele de identitate sau dorite, iar apoi folosiți un "
+"algoritm de feedback pentru a optimiza această cale gasita. Aceasta "
+"funcționează bine pentru aplicații care pur și simplu doresc să știe ce "
+"alți oameni din jurul lor au de oferit - \"Cum voi face\" vs \"Hei Alice,"
+" ce mai faci\" - veți obține de fapt un grup local, de noduri, care pot "
+"partaja fișiere cu și menține un anumit grad de anonimat (dacă nu aveți "
+"mai mult control asupra cine este în acel grup de colegii)."
+
+#: i2p2www/pages/site/comparison/other-networks.html:209
+msgid ""
+"However, the algorithm does not scale well at all - if the application "
+"wants to speak with a \n"
+"particular peer it ends up doing a broadcast search or random walk "
+"(though if they are lucky enough\n"
+"for that to succeed, the antnet routing should optimize that found "
+"connection). This means that \n"
+"while these networks can work great at small scales, they are not "
+"suitable for large networks where\n"
+"someone wants to get in touch with another specific peer. That does not "
+"mean that there is no \n"
+"value in these systems, just that their applicability is limited to "
+"situations where their \n"
+"particular issues can be addressed."
+msgstr ""
+"Cu toate acestea, algoritmul nu scaleaza de bine la toate - în cazul în "
+"care cererea vrea să vorbească cu un anumit utilizator se termină prin a "
+"face o emisiune de căutare sau de mers aleator (deși, dacă acestea sunt "
+"suficient de norocos pentru a reuși, de rutare antnet ar trebui să "
+"optimizeze găsirea conexiunii). Acest lucru înseamnă că, în timp ce "
+"aceste rețele pot lucra bine la solzi mici, ele nu sunt potrivite pentru "
+"retele mari în cazul în care cineva vrea să intre în contact cu un alt "
+"inter pares. Asta nu înseamnă că nu există nicio valoare în aceste "
+"sisteme, doar că aplicabilitatea lor este limitată la situațiile în care "
+"problemele lor specifice pot fi abordate."
+
+#: i2p2www/pages/site/comparison/other-networks.html:220
+#, python-format
+msgid ""
+"This was a closed-source network targeted at Iranian users.\n"
+"Tor did a good writeup on what to look for in a "
+"circumvention tool.\n"
+"Suffice it to say that being closed source and publicly targeting a "
+"specific country are not good ideas.\n"
+"I2P is, of course, open source. However, that source, and our\n"
+"technical documentation, need much more review."
+msgstr ""
+"Aceasta a fost o rețea închisă-source destinata utilizatorilor iraniene. "
+"Tor a făcut o writeup bun asupra a ceea ce să "
+"caute într-un instrument de eludare . Este suficient să spunem că "
+"este o sursa închisă și care vizează în mod public o anumită țară nu sunt"
+" idei bune. I2P este, desigur, sursă deschisă. Cu toate acestea, această "
+"sursă, și documentația noastră tehnice , are "
+"nevoie de mult mai multa revizuire."
+
+#: i2p2www/pages/site/comparison/other-networks.html:229
+msgid "Paid VPN Services"
+msgstr "Servicii VPN platite"
+
+#: i2p2www/pages/site/comparison/other-networks.html:230
+#: i2p2www/pages/site/comparison/other-networks.html:236
+#, python-format
+msgid ""
+"You may contribute an analysis by entering a\n"
+"new ticket on Trac."
+msgstr ""
+"Puteți contribui o analiză prin introducerea unui "
+"bilet nou pe Trac ."
+
+#: i2p2www/pages/site/comparison/other-networks.html:235
+msgid "Others"
+msgstr "Alții"
+
+#: i2p2www/pages/site/comparison/tor.html:2
+msgid "I2P Compared to Tor"
+msgstr "I2P in comparatie cu Tor"
+
+#: i2p2www/pages/site/comparison/tor.html:8
+#, python-format
+msgid ""
+"Tor and Onion Routing are both anonymizing proxy networks, \n"
+"allowing people to tunnel out through their low latency mix \n"
+"network. The two primary differences between Tor / \n"
+"Onion-Routing and I2P are again related to differences in \n"
+"the threat model and the out-proxy design (though Tor\n"
+"supports hidden services as well). In addition, Tor\n"
+"takes the directory-based approach - providing a \n"
+"centralized point to manage the overall 'view' of the \n"
+"network, as well as gather and report statistics, as \n"
+"opposed to I2P's distributed network \n"
+"database and peer selection."
+msgstr ""
+"Tor și Onion Routing sunt rețele anonime proxy, permițând oamenilor să "
+"tuneleze prin intermediul rețelei de amestec latență scăzuta. Cele două "
+"diferențe principale între Tor/onion-routing și I2P sunt în legătură cu"
+" diferențele de model-amenințare și de design de-proxy (deși Tor acceptă "
+"servicii ascunse, de asemenea). În plus, Tor are abordarea directorului "
+"bazat - pe oferirea unui punct centralizat de gestionare a \"vederii\" "
+"generale a rețelei, precum și adunarea și raportarea statistici, spre "
+"deosebire de I2P distribuita Baza de date "
+"rețea și selecție egal la egal ."
+
+#: i2p2www/pages/site/comparison/tor.html:22
+msgid ""
+"The I2P/Tor outproxy functionality does have a few \n"
+"substantial weaknesses against certain attackers - \n"
+"once the communication leaves the mixnet, global passive\n"
+"adversaries can more easily mount traffic analysis. In \n"
+"addition, the outproxies have access to the cleartext \n"
+"of the data transferred in both directions, and \n"
+"outproxies are prone to abuse, along with all of the \n"
+"other security issues we've come to know and love with \n"
+"normal Internet traffic."
+msgstr ""
+"Funcționalitatea outproxy I2P/Tor are câteva puncte slabe importante "
+"împotriva unor agresori - odata comunicarea părăsește mixnet, adversarea "
+"pasiva la nivel mondial se poate mai ușor monta analiza traficului. În "
+"plus, outproxies au acces la textul datelor transferate în ambele "
+"direcții, și outproxies sunt predispuse la abuz, împreună cu toate "
+"celelalte probleme de securitate le-am venit să-l cunoastem cu trafic "
+"normal din Internet."
+
+#: i2p2www/pages/site/comparison/tor.html:34
+msgid ""
+"However, many people don't need to worry about those \n"
+"situations, as they are outside their threat model. It\n"
+"is, also, outside I2P's (formal) functional scope (if people want\n"
+"to build outproxy functionality on top of an anonymous\n"
+"communication layer, they can). In fact, some I2P users\n"
+"currently take advantage of Tor to outproxy."
+msgstr ""
+"Cu toate acestea, majoritatea persoanelor nu trebuie să faca griji cu "
+"privire la aceste situații, deoarece acestea sunt în afara modelului lor "
+"de amenințare. Este, de asemenea, în afara (formal) domeniul de aplicare "
+"funcțională I2P lui (în cazul în care oamenii doresc să construiască "
+"funcționalitate outproxy pe partea de sus a unui strat de comunicare "
+"anonimă, ei pot). De fapt, unii utilizatori de I2P în prezent profita de"
+" Tor la outproxy."
+
+#: i2p2www/pages/site/comparison/tor.html:48
+msgid "Comparison of Tor and I2P Terminology"
+msgstr "Compararea cu Tor și I2P terminologie"
+
+#: i2p2www/pages/site/comparison/tor.html:49
+msgid ""
+"While Tor and I2P are similar in many ways, much of the terminology is "
+"different."
+msgstr ""
+"În timp ce Tor și I2P sunt similare în multe feluri, o mare parte din "
+"terminologie este diferita."
+
+#: i2p2www/pages/site/comparison/tor.html:54
+msgid "Cell"
+msgstr "Celulă"
+
+#: i2p2www/pages/site/comparison/tor.html:54
+msgid "Message"
+msgstr "Mesaj"
+
+#: i2p2www/pages/site/comparison/tor.html:55
+msgid "Client"
+msgstr "Client"
+
+#: i2p2www/pages/site/comparison/tor.html:55
+msgid "Router or Client"
+msgstr "Router sau Client"
+
+#: i2p2www/pages/site/comparison/tor.html:56
+msgid "Circuit"
+msgstr "Circuit"
+
+#: i2p2www/pages/site/comparison/tor.html:56
+msgid "Tunnel"
+msgstr "Tunel"
+
+#: i2p2www/pages/site/comparison/tor.html:57
+msgid "Directory"
+msgstr "Dosar"
+
+#: i2p2www/pages/site/comparison/tor.html:57
+msgid "NetDb"
+msgstr "NetDB"
+
+#: i2p2www/pages/site/comparison/tor.html:58
+msgid "Directory Server"
+msgstr "Server de directoare"
+
+#: i2p2www/pages/site/comparison/tor.html:58
+msgid "Floodfill Router"
+msgstr "Floodfill Router"
+
+#: i2p2www/pages/site/comparison/tor.html:59
+msgid "Entry Guards"
+msgstr "Gărzile de intrare"
+
+#: i2p2www/pages/site/comparison/tor.html:59
+msgid "Fast Peers"
+msgstr "Utilizatori rapizi"
+
+#: i2p2www/pages/site/comparison/tor.html:60
+msgid "Entry Node"
+msgstr "Nod de intrare"
+
+#: i2p2www/pages/site/comparison/tor.html:60
+msgid "Inproxy"
+msgstr "Inproxy"
+
+#: i2p2www/pages/site/comparison/tor.html:61
+msgid "Exit Node"
+msgstr "Nod de ieșire "
+
+#: i2p2www/pages/site/comparison/tor.html:61
+msgid "Outproxy"
+msgstr "Outproxy"
+
+#: i2p2www/pages/site/comparison/tor.html:62
+msgid "Hidden Service"
+msgstr "Serviciul ascuns"
+
+#: i2p2www/pages/site/comparison/tor.html:62
+msgid "Eepsite or Destination"
+msgstr "Eepsite sau Destinatie"
+
+#: i2p2www/pages/site/comparison/tor.html:63
+msgid "Hidden Service Descriptor"
+msgstr "Descriptor de serviciu ascuns"
+
+#: i2p2www/pages/site/comparison/tor.html:63
+msgid "LeaseSet"
+msgstr "LeaseSet"
+
+#: i2p2www/pages/site/comparison/tor.html:64
+msgid "Introduction point"
+msgstr "Punct de introducere"
+
+#: i2p2www/pages/site/comparison/tor.html:64
+msgid "Inbound Gateway"
+msgstr "Gateway intrare"
+
+#: i2p2www/pages/site/comparison/tor.html:65
+msgid "Node"
+msgstr "Nod"
+
+#: i2p2www/pages/site/comparison/tor.html:65
+#: i2p2www/pages/site/comparison/tor.html:67
+#: i2p2www/pages/site/comparison/tor.html:70
+msgid "Router"
+msgstr "Ruter"
+
+#: i2p2www/pages/site/comparison/tor.html:66
+msgid "Onion Proxy"
+msgstr "Proxy ceapa"
+
+#: i2p2www/pages/site/comparison/tor.html:66
+msgid "I2PTunnel Client (more or less)"
+msgstr "I2PTunnel client (mai multi sau mai puțini)"
+
+#: i2p2www/pages/site/comparison/tor.html:67
+msgid "Relay"
+msgstr "Intermediere"
+
+#: i2p2www/pages/site/comparison/tor.html:68
+msgid "Rendezvous Point"
+msgstr "Punct de rendezvous"
+
+#: i2p2www/pages/site/comparison/tor.html:68
+msgid "somewhat like Inbound Gateway + Outbound Endpoint"
+msgstr "oarecum ca Gateway intrare + Endpoint ieșire"
+
+#: i2p2www/pages/site/comparison/tor.html:69
+msgid "Router Descriptor"
+msgstr "Descriptor ruter"
+
+#: i2p2www/pages/site/comparison/tor.html:69
+msgid "RouterInfo"
+msgstr "RouterInfo"
+
+#: i2p2www/pages/site/comparison/tor.html:70
+msgid "Server"
+msgstr "Server"
+
+#: i2p2www/pages/site/comparison/tor.html:73
+msgid "Benefits of Tor over I2P"
+msgstr "Beneficiile Tor peste I2P"
+
+#: i2p2www/pages/site/comparison/tor.html:76
+msgid ""
+"Much bigger user base; much more visibility in the academic and hacker "
+"communities; benefits from\n"
+"formal studies of anonymity, resistance, and performance;\n"
+"has a non-anonymous, visible, university-based leader"
+msgstr ""
+"Baza mult mai mare de utilizatori; vizibilitate mult mai multa în "
+"comunitățile academice și hacker, beneficiaza de studii formale de "
+"anonimat, rezistenta, și de performanță, vizibila, liderul non-anonim "
+"universitate pe baza de"
+
+#: i2p2www/pages/site/comparison/tor.html:82
+msgid "Has already solved some scaling issues I2P has yet to address"
+msgstr ""
+"S-au rezolvat deja unele probleme de scalare I2P a fost încă pentru "
+"adresare"
+
+#: i2p2www/pages/site/comparison/tor.html:83
+msgid "Has significant funding"
+msgstr "Are fonduri semnificative"
+
+#: i2p2www/pages/site/comparison/tor.html:84
+msgid "Has more developers, including several that are funded"
+msgstr "Are mai multe dezvoltatori, inclusiv câteva care sunt finanțate"
+
+#: i2p2www/pages/site/comparison/tor.html:86
+msgid ""
+"More resistant to state-level blocking due to TLS transport layer and "
+"bridges\n"
+"(I2P has proposals for \"full restricted routes\" but these are not yet "
+"implemented)"
+msgstr ""
+"Mai rezistent la blocarea din cauza stratului transport TLS și poduri "
+"(I2P are propuneri pentru \"rute restricționate complete\", dar acestea "
+"încă nu sunt puse în aplicare )"
+
+#: i2p2www/pages/site/comparison/tor.html:91
+msgid "Big enough that it has had to adapt to blocking and DOS attempts"
+msgstr ""
+"Suficient de mare pentru că a trebuit să se adapteze la blocarea și DOS "
+"încercări"
+
+#: i2p2www/pages/site/comparison/tor.html:92
+msgid "Designed and optimized for exit traffic, with a large number of exit nodes"
+msgstr ""
+"Concepute și optimizate pentru traficul de ieșire, cu un număr mare de "
+"noduri de ieșire"
+
+#: i2p2www/pages/site/comparison/tor.html:94
+msgid ""
+"Better documentation, has formal papers and specifications,\n"
+"better website, many more translations"
+msgstr ""
+"Documentația mai bună, are acte oficiale și specificațiile, site-ul mai "
+"bun, mult mai multe traduceri"
+
+#: i2p2www/pages/site/comparison/tor.html:99
+msgid "More efficient with memory usage"
+msgstr "Mai eficienta utilizarea memoriei"
+
+#: i2p2www/pages/site/comparison/tor.html:100
+msgid "Tor client nodes have very low bandwidth overhead"
+msgstr "Nodurile client Tor au foarte putin trafic overhead"
+
+#: i2p2www/pages/site/comparison/tor.html:102
+msgid ""
+"Centralized control reduces the complexity at each\n"
+"node and can efficiently address Sybil attacks"
+msgstr ""
+"Control centralizat reduce complexitatea de la fiecare nod și poate "
+"răspunde în mod eficient atacuri Sybil"
+
+#: i2p2www/pages/site/comparison/tor.html:108
+msgid ""
+"A core of high capacity nodes provides higher\n"
+"throughput and lower latency"
+msgstr ""
+"O bază de noduri de mare capacitate oferă transfer mai mare și latență "
+"mai mică"
+
+#: i2p2www/pages/site/comparison/tor.html:113
+msgid "C, not Java (ewww)"
+msgstr "C, nu este Java (ewww)"
+
+#: i2p2www/pages/site/comparison/tor.html:116
+msgid "Benefits of I2P over Tor"
+msgstr "Beneficiile I2P peste Tor"
+
+#: i2p2www/pages/site/comparison/tor.html:118
+msgid ""
+"Designed and optimized for hidden services, which are much faster than in"
+" Tor"
+msgstr ""
+"Concepute și optimizate pentru serviciile ascunse, care sunt mult mai "
+"rapide decât în Tor"
+
+#: i2p2www/pages/site/comparison/tor.html:119
+msgid "Fully distributed and self organizing"
+msgstr "Complet distribuit și de auto organizare"
+
+#: i2p2www/pages/site/comparison/tor.html:121
+msgid ""
+"Peers are selected by continuously profiling and ranking performance,\n"
+"rather than trusting claimed capacity"
+msgstr ""
+"Colegii sunt selectate de către profilare continua si clasament de "
+"performanță, mai degrabă decât încredere în capacitatea de a pretins"
+
+#: i2p2www/pages/site/comparison/tor.html:127
+msgid ""
+"Floodfill peers (\"directory servers\") are varying and untrusted,\n"
+"rather than hardcoded"
+msgstr ""
+"Colegii Floodfill (\"serverele director\") sunt diferiti și nu sunt de "
+"încredere, mai degrabă decât codate"
+
+#: i2p2www/pages/site/comparison/tor.html:132
+msgid "Small enough that it hasn't been blocked or DOSed much, or at all"
+msgstr ""
+"Suficient de mici pentru că sa nu fie blocati sau administrati demult, "
+"sau deloc"
+
+#: i2p2www/pages/site/comparison/tor.html:133
+msgid "Peer-to-peer friendly"
+msgstr "Peer-to-peer prietenos"
+
+#: i2p2www/pages/site/comparison/tor.html:134
+msgid "Packet switched instead of circuit switched"
+msgstr "Comutarea pachetelor în loc de comutarea circuitelor"
+
+#: i2p2www/pages/site/comparison/tor.html:137
+msgid ""
+"implicit transparent load balancing of messages \n"
+"across multiple peers, rather than a single path"
+msgstr ""
+"balansare incarcarii implicita si transparentă a mesajelor pe mai multe "
+"colegii, mai des decât o singură cale"
+
+#: i2p2www/pages/site/comparison/tor.html:143
+msgid ""
+"resilience vs. failures by running multiple \n"
+"tunnels in parallel, plus rotating tunnels"
+msgstr ""
+"rezistența vs eșecurile prin rularea mai multor tuneluri în paralel, plus"
+" tuneluri rotative"
+
+#: i2p2www/pages/site/comparison/tor.html:149
+msgid ""
+"scale each client's connections at O(1) instead \n"
+"of O(N) (Alice has e.g. 2 inbound tunnels that are \n"
+"used by all of the peers Alice is talking with, \n"
+"rather than a circuit for each)"
+msgstr ""
+"scala conexiuni ale fiecărui client la O (1) în loc de O (N) (Alice de "
+"exemplu are 2 tuneluri de intrare care sunt utilizate de către toti "
+"colegi cu care Alice converseaza , mai degrabă decât un circuit pentru "
+"fiecare)"
+
+#: i2p2www/pages/site/comparison/tor.html:159
+msgid ""
+"Unidirectional tunnels instead of bidirectional\n"
+"circuits, doubling the number of nodes a peer has to\n"
+"compromise to get the same information."
+msgstr ""
+"Tuneluri unidirecționale în loc de circuite bidirecționale, dublarea "
+"numărului de noduri colegilor trebuie să facă un compromis pentru a "
+"obține aceleași informații."
+
+#: i2p2www/pages/site/comparison/tor.html:166
+msgid ""
+"Protection against detecting client activity, even\n"
+"when an attacker is participating in the tunnel, as\n"
+"tunnels are used for more than simply passing end \n"
+"to end messages (e.g. netDb, tunnel management, \n"
+"tunnel testing)"
+msgstr ""
+"Protecția împotriva detectarii de activitate clientului, chiar și atunci "
+"când un atacator participă la tunel, așa cum tuneluri sunt folosite "
+"pentru mai multe decât pur și simplu trecerea intr-un capăt mesaje finali"
+" (de exemplu netDb, managementul tunel, tunel"
+
+#: i2p2www/pages/site/comparison/tor.html:175
+msgid ""
+"Tunnels in I2P are short lived, decreasing the number\n"
+"of samples that an attacker can use to mount an \n"
+"active attack with, unlike circuits in Tor, which are\n"
+"typically long lived."
+msgstr ""
+"Tunelurile din I2P sunt de scurtă durată, scăderea numărului de probe "
+"care un atacator poate folosi pentru a monta un atac activ , spre "
+"deosebire de circuite din Tor, care de obicei au viata lunga."
+
+#: i2p2www/pages/site/comparison/tor.html:183
+msgid ""
+"I2P APIs are designed specifically for anonymity and\n"
+"security, while SOCKS is designed for functionality."
+msgstr ""
+"I2P API-uri sunt proiectate special pentru anonimatul și securitate, în "
+"timp ce SOCKS este proiectat pentru funcționalitate."
+
+#: i2p2www/pages/site/comparison/tor.html:188
+msgid "Essentially all peers participate in routing for others"
+msgstr "În esență, toți colegii participa la rutare pentru alții"
+
+#: i2p2www/pages/site/comparison/tor.html:190
+msgid ""
+"The bandwidth overhead of being a full peer is low, \n"
+"while in Tor, while client nodes don't require much\n"
+"bandwidth, they don't fully participate in the mixnet."
+msgstr ""
+"Overhead de bandă a utilizatorului este scăzut, decit în Tor, în timp ce "
+"nodurile client nu necesită mai mult de lățime de bandă, ele nu participă"
+" pe deplin la mixnet."
+
+#: i2p2www/pages/site/comparison/tor.html:196
+msgid "Integrated automatic update mechanism"
+msgstr "Mecanism integrat de actualizare automată"
+
+#: i2p2www/pages/site/comparison/tor.html:197
+msgid "Both TCP and UDP transports"
+msgstr "Atât TCP cit și UDP transporturi"
+
+#: i2p2www/pages/site/comparison/tor.html:198
+msgid "Java, not C (ewww)"
+msgstr "Java nu e C (ewww)"
+
+#: i2p2www/pages/site/comparison/tor.html:201
+msgid "Other potential benefits of I2P but not yet implemented"
+msgstr "Alte beneficii ale I2P dar neimplementate încă"
+
+#: i2p2www/pages/site/comparison/tor.html:202
+msgid "...and may never be implemented, so don't count on them!"
+msgstr "... și posibil sa nu fie puse în aplicare, astfel încât nu conta pe ei!"
+
+#: i2p2www/pages/site/comparison/tor.html:205
+msgid ""
+"Defense vs. message count analysis by garlic wrapping \n"
+"multiple messages"
+msgstr ""
+"Apărare vs analiza numărului de mesaje de ambalaj usturoi invelite mai "
+"multe mesaje"
+
+#: i2p2www/pages/site/comparison/tor.html:211
+msgid ""
+"Defense vs. long term intersection by adding delays \n"
+"at various hops (where the delays are not discernible\n"
+"by other hops)"
+msgstr ""
+"Apărare vs intersecție pe termen lung prin adăugarea de întârzieri la "
+"diferite hamei (în cazul în care întârzierile nu sunt perceptibile prin "
+"alte hamei)"
+
+#: i2p2www/pages/site/comparison/tor.html:218
+msgid ""
+"Various mixing strategies at the tunnel level (e.g.\n"
+"create a tunnel that will handle 500 messages / minute,\n"
+"where the endpoint will inject dummy messages if there\n"
+"are insufficient messages, etc)"
+msgstr ""
+"Diverse strategii de amestecare la nivel tunel (de exemplu, a crea un "
+"tunel care se va ocupa 500 de mesaje / minut, în cazul în care obiectivul"
+" va injecta mesaje false dacă există mesaje insuficiente, etc)"
+
diff --git a/i2p2www/translations/ro/LC_MESSAGES/priority.po b/i2p2www/translations/ro/LC_MESSAGES/priority.po
new file mode 100644
index 00000000..dae7b2b2
--- /dev/null
+++ b/i2p2www/translations/ro/LC_MESSAGES/priority.po
@@ -0,0 +1,3316 @@
+# Romanian translations for I2P.
+# Copyright (C) 2013 ORGANIZATION
+# This file is distributed under the same license as the I2P project.
+#
+# Translators:
+# Admin , 2013
+# oper2 , 2013
+msgid ""
+msgstr ""
+"Project-Id-Version: I2P\n"
+"Report-Msgid-Bugs-To: http://trac.i2p2.de\n"
+"POT-Creation-Date: 2013-11-27 00:23+0000\n"
+"PO-Revision-Date: 2013-12-05 12:53+0000\n"
+"Last-Translator: polearnik \n"
+"Language-Team: Romanian "
+"(http://www.transifex.com/projects/p/I2P/language/ro/)\n"
+"Plural-Forms: nplurals=3; "
+"plural=(n==1?0:(((n%100>19)||((n%100==0)&&(n!=0)))?2:1))\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=utf-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"Generated-By: Babel 0.9.6\n"
+
+#: i2p2www/pages/blog/category.html:2
+msgid "Blog Category"
+msgstr "Categorie blog"
+
+#: i2p2www/pages/blog/category.html:4
+#, python-format
+msgid "I2P Blog ATOM Feed for Category: %(category)s"
+msgstr ""
+
+#: i2p2www/pages/blog/index.html:2 i2p2www/pages/blog/post.html:3
+#: i2p2www/pages/global/nav.html:95
+msgid "Blog"
+msgstr "Blog"
+
+#: i2p2www/pages/blog/index.html:4 i2p2www/pages/site/index.html:78
+msgid "I2P Blog ATOM Feed"
+msgstr "I2P Blog ATOM Feed"
+
+#: i2p2www/pages/blog/index.html:17
+#, python-format
+msgid "Posted %(date)s by %(author)s"
+msgstr "Postat %(date)s de %(author)s "
+
+#: i2p2www/pages/blog/latest.html:5
+msgid "More blog posts…"
+msgstr "Mai multe posturi-blog …"
+
+#: i2p2www/pages/blog/post.html:6
+msgid "Posted:"
+msgstr "Postat:"
+
+#: i2p2www/pages/blog/post.html:7
+msgid "Author:"
+msgstr "Autor:"
+
+#: i2p2www/pages/downloads/debian.html:4
+msgid "Debian I2P Packages"
+msgstr "Pachet I2P Debian"
+
+#: i2p2www/pages/downloads/debian.html:6
+msgid ""
+"The Debian packages\n"
+"have been tested and should work on x86/x86_64 platforms running:"
+msgstr ""
+"Pachetele Debian au fost testate și ar trebui sa lucreze pe "
+"platforme x86/x86_64:"
+
+#: i2p2www/pages/downloads/debian.html:11
+msgid "Ubuntu (Precise 12.04 and newer)"
+msgstr "Ubuntu (exact 12.04 si mai nou)"
+
+#: i2p2www/pages/downloads/debian.html:13
+msgid "Debian Linux (Squeeze and newer) & kFreeBSD"
+msgstr ""
+"Debian Linux (Squeeze si mai recent) & "
+"kFreeBSD"
+
+#: i2p2www/pages/downloads/debian.html:17
+#, python-format
+msgid ""
+"The I2P packages may work on systems not listed above. Please "
+"report any issues\n"
+"with these packages on Trac at\n"
+"https://trac.i2p2.de."
+msgstr ""
+"Pachetele I2P pot sa lucreze si pe sisteme ce nu sunt enumerate "
+"mai sus.Vă rugăm să raportați orice probleme cu aceste pachete peTracpe\n"
+"https://%(trac)s."
+
+#: i2p2www/pages/downloads/debian.html:23
+msgid ""
+"Option 1: Recent versions of Ubuntu and its "
+"derivatives (Try this if you're not using Debian)"
+msgstr ""
+"Optiune 1:Versiunile recente Ubuntu si derivatii "
+"ei (Incercati daca nu folositi Debian)"
+
+#: i2p2www/pages/downloads/debian.html:24
+msgid "Option 2: Debian (including Debian-derivatives)"
+msgstr "Optiune 2: Debian (inclusiv Debian-derivati)"
+
+#: i2p2www/pages/downloads/debian.html:27
+msgid ""
+"Instructions for Ubuntu Precise Pangolin (and newer) and derivatives like"
+" Linux Mint & Trisquel"
+msgstr ""
+"Instructii pentru Ubuntu Precise Pangolin( si mai nou) si derivatii de "
+"tip Linux Mint"
+
+#: i2p2www/pages/downloads/debian.html:28
+msgid "Adding the PPA via the command line and installing I2P"
+msgstr "Adaugati PPA prin linia de comanda si instalati I2P"
+
+#: i2p2www/pages/downloads/debian.html:31
+msgid "Open a terminal and enter:"
+msgstr "Deschideti terminal si introduceti:"
+
+#: i2p2www/pages/downloads/debian.html:33
+msgid ""
+"This command will add the PPA to /etc/apt/sources.list.d and fetch the\n"
+"gpg key that the repository has been signed with. The GPG key ensures\n"
+"that the packages have not been tampered with since being built."
+msgstr ""
+"Această comandă va adăuga PPA la / etc / apt / sources.list.d și adu\n"
+"cheia GPG cu care depozitul a fost semnat . Cheia GPG asigură\n"
+"că pachetele nu au fost falsificate de cand au fost construite."
+
+#: i2p2www/pages/downloads/debian.html:40
+msgid "Notify your package manager of the new PPA by entering:"
+msgstr "Anunta managerul de pachete despre nout PPA prin introducerea:"
+
+#: i2p2www/pages/downloads/debian.html:42
+msgid ""
+"This command will retrieve the latest list of software from each\n"
+"repository that is enabled on your system, including the I2P PPA that\n"
+"was added with the earlier command."
+msgstr ""
+"Această comandă va prelua cea mai recentă listă a software-ului de la "
+"fiecare\n"
+"depozit, care este activat pe sistemul dumneavoastră, inclusiv I2P PPA "
+"care\n"
+"se adaugă cu comanda anterioară."
+
+#: i2p2www/pages/downloads/debian.html:48
+msgid "You are now ready to install I2P!"
+msgstr "Acum sunteți gata să instalați I2P!"
+
+#: i2p2www/pages/downloads/debian.html:52
+msgid "Adding the PPA Using Synaptic"
+msgstr "Adăugarea PPA Folosind Synaptic"
+
+#: i2p2www/pages/downloads/debian.html:55
+msgid ""
+"Open Synaptic (System -> Administration -> Synaptic Package "
+"Manager)."
+msgstr ""
+"Deshideti Synaptic (Sistem -> Administrarea -> managerul de pachete"
+" Synaptic )."
+
+#: i2p2www/pages/downloads/debian.html:60
+msgid ""
+"Once Synaptic opens, select Repositories from the "
+"Settings menu."
+msgstr ""
+"După ce se deschide Synaptic, selectați Depozitele din meniu"
+" Setări ."
+
+#: i2p2www/pages/downloads/debian.html:65
+msgid ""
+"Click the Other Sources tab and click Add. Paste "
+"ppa:i2p-maintainers/i2p into the APT-line field and click "
+"Add Source. Click the Close button then "
+"Reload."
+msgstr ""
+"clic pe fila alte surse si clic Adauga Lipeste "
+"ppa:i2p-maintainers/i2p in cimp APT-linie si clicAdauga "
+"sursaclic pe butonul Inchide mai apoi restartati."
+
+#: i2p2www/pages/downloads/debian.html:70
+msgid ""
+"In the Quick Filter box, type in i2p and press enter. When "
+"i2p is returned in the results list, right click "
+"i2p and select Mark for Installation. After doing "
+"so you may see a Mark additional required changes? popup. If so,"
+" click Mark then Apply."
+msgstr ""
+"In caseta filtru rapid, tapati in i2p si apasati "
+"enter.Cindi2p returnat în lista de rezultate, faceți clic "
+"dreapta i2p si selectatiMarcheaza pentru instalare."
+" Dupa aceasta puteti vedea pop-up cu textul: Marcheaza modificările "
+"necesare suplimentare? Dacă este așa clic Marcheaza apoi "
+"Aplica."
+
+#: i2p2www/pages/downloads/debian.html:76
+msgid ""
+"After the installation process completes you can move on to the next\n"
+"part of starting I2P and configuring "
+"it for your system."
+msgstr ""
+"După ce procesul de instalare se încheie puteți trece la\n"
+"următoarea parte din start I2P și "
+"configurarea-l pentru sistemul dvs.."
+
+#: i2p2www/pages/downloads/debian.html:81
+msgid "Instructions for Debian"
+msgstr "Instrucțiuni pentru Debian"
+
+#: i2p2www/pages/downloads/debian.html:85
+msgid ""
+"Note: The steps below should be performed with root access (i.e., "
+"switching\n"
+"user to root with \"su\" or by prefixing each command with \"sudo\")."
+msgstr ""
+"Note:Pașii de mai jos ar trebui să fie efectuate cu acces root (de "
+"exemplu, de comutare\n"
+"utilizatorului la root cu \"su\" sau prin prefixarea fiecare comandă cu "
+"\"sudo\")."
+
+#: i2p2www/pages/downloads/debian.html:90
+#, python-format
+msgid "Add lines like the following to %(file)s."
+msgstr "Adauga linii, cum ar fi cele ce urmează la %(fisier) s ."
+
+#: i2p2www/pages/downloads/debian.html:111
+#, python-format
+msgid ""
+"Download the key used to sign the repository"
+" and add it to apt:"
+msgstr ""
+"Descărcați cheia utilizată pentru a semna "
+"depozit și adăugați-l în apt:"
+
+#: i2p2www/pages/downloads/debian.html:118
+msgid "Notify your package manager of the new repository by entering"
+msgstr "Anunta managerul de pachete despre depozit nou prin introducerea"
+
+#: i2p2www/pages/downloads/debian.html:120
+msgid ""
+"This command will retrieve the latest list of software from every\n"
+"repository enabled on your system, including the I2P repository added in "
+"step\n"
+"1."
+msgstr ""
+"Această comandă va prelua cea mai recentă listă a software-ului de la "
+"fiecare\n"
+"depozit, care este activat pe sistemul dumneavoastră, inclusiv I2P "
+"depozit \n"
+"adăugat in pasul 1."
+
+#: i2p2www/pages/downloads/debian.html:126
+msgid ""
+"You are now ready to install I2P! Installing the i2p-keyring"
+"\n"
+"package will ensure that you receive updates to the repository's GPG key."
+msgstr ""
+"Acum sunteți gata să instalați I2P! Instalarea I2P-keyring pachetul va asigura că veți primi actualizări la cheie GPG "
+"depozitului."
+
+#: i2p2www/pages/downloads/debian.html:133
+msgid ""
+"After the installation process completes you can move on to the next part"
+" of starting I2P and configuring it "
+"for your system."
+msgstr ""
+"După ce procesul de instalare se încheie puteți trece la următoarea parte"
+" din start I2P și configurarea pentru "
+"sistemul dvs.."
+
+#: i2p2www/pages/downloads/debian.html:137
+#: i2p2www/pages/downloads/list.html:171
+msgid "Post-install work"
+msgstr "Actiunile dupa instalare"
+
+#: i2p2www/pages/downloads/debian.html:139
+msgid ""
+"Using these I2P packages the I2P router can be started in the following\n"
+"three ways:"
+msgstr ""
+"Folosind aceste pachete I2P router I2P poate fi pornit în următoarele\n"
+"trei moduri:"
+
+#: i2p2www/pages/downloads/debian.html:145
+msgid ""
+""on demand" using the i2prouter script. Simply run "
+""i2prouter\n"
+"start" from a command prompt. (Note: Do "
+"not use\n"
+"sudo or run it as root!)"
+msgstr ""
+""la cerere" folositi i2prouter script. Porniti "
+""i2prouter\n"
+"start" din linia de comanda. (Note: "
+"nu folositi\n"
+"sudo sau porniti de la root!)"
+
+#: i2p2www/pages/downloads/debian.html:152
+msgid ""
+""on demand" without the java service wrapper\n"
+"(needed on non-Linux/non-x86 systems) by running \"i2prouter-"
+"nowrapper\".\n"
+"(Note: Do not\n"
+"use sudo or run it as root!)"
+msgstr ""
+""la cerere" fără java service wrapper\n"
+"(necesare pe sisteme non-Linux/non-x86 ) prin rularea \"i2prouter-"
+"nowrapper\".\n"
+"(Nota: Nu\n"
+"folositi sudo sau porniti-l de la root!)"
+
+#: i2p2www/pages/downloads/debian.html:160
+msgid ""
+"as a service that automatically runs when your system boots, even\n"
+"before logging in. The service can be enabled with \"dpkg-"
+"reconfigure\n"
+"i2p\" as root or using sudo. This is the recommended means of "
+"operation."
+msgstr ""
+"ca un serviciu care ruleaza automat la incarcarea sistemului, chiar\n"
+"înainte de a vă autentifica. Serviciul poate fi activat cu \" dpkg-"
+"reconfigure\n"
+"I2P \"ca root sau utilizind sudo. Acesta este mijlocul "
+"recomandat de funcționare."
+
+#: i2p2www/pages/downloads/debian.html:168
+msgid ""
+"When installing for the first time, please remember to adjust your "
+"NAT/firewall\n"
+"if you can. The ports to forward can be found on the \n"
+"network configuration page in the router console. If guidance with "
+"respect to forwarding ports is needed,\n"
+"you may find portforward.com to be"
+" helpful."
+msgstr ""
+"Când instalați pentru prima dată, vă rugăm să nu uitați setati "
+"NAT/firewall daca puteti.Porturile pentru inaintare pot fi gasite "
+"în pagina de configurare a "
+"rețeleidin consola router.Dacă este nevoie de îndrumare în ceea ce "
+"privește porturile de inaintare,ajutorul puteți găsi la portforward.com"
+
+#: i2p2www/pages/downloads/debian.html:175
+msgid ""
+"Please review and adjust the bandwidth settings on the\n"
+"configuration page,\n"
+"as the default settings of 96 KB/s down / 40 KB/s up are fairly "
+"conservative."
+msgstr ""
+"Rugam sa examinati si adaptati setările de lățime de bandăpe \n"
+"pagina de configurare \n"
+"deoarece setări implicite de 96 KB / s download / 40 KB / upload sunt "
+"destul de conservatoare"
+
+#: i2p2www/pages/downloads/debian.html:181
+#: i2p2www/pages/downloads/list.html:204
+#, python-format
+msgid ""
+"If you want to reach eepsites via your browser, have a look on the browser proxy setup page for an easy "
+"howto."
+msgstr ""
+"Dacă doriți să ajungă la eepsites prin intermediul browser-ul "
+"dvs.,aruncati o privire pe pagina configurarea proxy browser-ului pentru un "
+"ghid simplu"
+
+#: i2p2www/pages/downloads/list.html:2 i2p2www/pages/downloads/select.html:12
+#: i2p2www/pages/global/nav.html:3
+msgid "Download"
+msgstr "Descarca"
+
+#: i2p2www/pages/downloads/list.html:9
+msgid "Download I2P"
+msgstr "Descarcă I2P"
+
+#: i2p2www/pages/downloads/list.html:11
+msgid "Dependency"
+msgstr "Dependență"
+
+#: i2p2www/pages/downloads/list.html:12
+#, python-format
+msgid ""
+"\n"
+"Java Runtime 1.5 or higher.\n"
+"(Oracle Java Version 7,\n"
+"OpenJDK 7, or\n"
+"IcedTea7\n"
+" recommended,\n"
+"except Raspberry Pi: Oracle 8 Early Access,\n"
+"PowerPC: IBM SDK 7)\n"
+"
\n"
+"Determine your installed Java version here\n"
+"or type java -version at your command prompt.\n"
+msgstr ""
+"Java Runtime 1.5 sau mai recent. (Oracle Java "
+"Versiunea 7, OpenJDK 7, or IcedTea7 recomendat, exceptind Raspberry Pi: Oracle 8 Early Access, PowerPC: IBM SDK 7)
Determinați versiunea de Java instalata aici "
+"sau tapati java -version in terminal "
+
+#: i2p2www/pages/downloads/list.html:30
+msgid "Clean installs"
+msgstr "Instalarea curata"
+
+#: i2p2www/pages/downloads/list.html:37 i2p2www/pages/downloads/list.html:54
+#: i2p2www/pages/downloads/list.html:81 i2p2www/pages/downloads/list.html:140
+#: i2p2www/pages/downloads/list.html:269
+msgid "select alternate link"
+msgstr "selectați link-ul alternativ"
+
+#: i2p2www/pages/downloads/list.html:44
+msgid "Download that file and run it."
+msgstr "Descărca acest fișier și rulați-l."
+
+#: i2p2www/pages/downloads/list.html:61
+#, python-format
+msgid ""
+"Download that file and double-click it (if that works) or\n"
+" type java -jar i2pinstall_%(i2pversion)s.jar in a "
+"terminal to run the\n"
+" installer.\n"
+" You may be able to right-click and select\n"
+" "Open with Java"."
+msgstr ""
+"Descărca acest fișier și dublu-clic (în cazul în care funcționează) sau\n"
+"tapati java -jar i2pinstall_%(i2pversion)s.jarin terminal "
+"pentru a porni instalator.\n"
+"Ați putea să faceți clic dreapta și selectați\n"
+""deschide cu Java"."
+
+#: i2p2www/pages/downloads/list.html:69 i2p2www/pages/downloads/list.html:96
+msgid "Command line (headless) install:"
+msgstr "Instalare prin linie de comandă (headless) :"
+
+#: i2p2www/pages/downloads/list.html:70
+#, python-format
+msgid ""
+"Download the %(i2pversion)s OSX graphical installer file above and\n"
+" run java -jar i2pinstall_%(i2pversion)s.jar -console "
+"from the command line."
+msgstr ""
+"Descarcă %(i2pversion)s OSX fișierul de instalare grafica de mai sus si\n"
+"porneste java -jar i2pinstall_%(i2pversion)s.jar -console in"
+" linie de comanda."
+
+#: i2p2www/pages/downloads/list.html:88
+#, python-format
+msgid ""
+"Download that file and double-click it (if that works) or\n"
+" type java -jar i2pinstall_%(i2pversion)s.jar in a "
+"terminal to run the\n"
+" installer.\n"
+" On some platforms you may be able to right-click and select\n"
+" "Open with Java"."
+msgstr ""
+"Descărca acest fișier și dublu-clic (în cazul în care funcționează) sau\n"
+"tapati java -jar i2pinstall_%(i2pversion)s.jarin terminal "
+"pentru a porni instalator.\n"
+"Ați putea să faceți clic dreapta și selectați\n"
+""deschide cu Java"."
+
+#: i2p2www/pages/downloads/list.html:97
+#, python-format
+msgid ""
+"Download the graphical installer file above and\n"
+" run java -jar i2pinstall_%(i2pversion)s.jar -console "
+"from the command line."
+msgstr ""
+"Descarcă fișierul de instalare grafica de mai sus si\n"
+"porneste java -jar i2pinstall_%(i2pversion)s.jar -console in"
+" linie de comanda."
+
+#: i2p2www/pages/downloads/list.html:107
+msgid "Packages for Debian & Ubuntu are available."
+msgstr "Sunt disponbile pachete pentru Debian &Ubuntu"
+
+#: i2p2www/pages/downloads/list.html:121
+#, python-format
+msgid ""
+"The above file is the current release build.\n"
+" The latest dev build is version %(devbuild)s, and is available from\n"
+" str4d's eepsite."
+msgstr ""
+
+#: i2p2www/pages/downloads/list.html:127
+msgid ""
+"The release and dev versions of the I2P APK are not compatible, as they\n"
+" are signed by zzz and str4d respectively. Uninstall one before "
+"installing\n"
+" the other."
+msgstr ""
+"Release-ul și dev versiuni ale I2P APK nu sunt compatibile, deoarece\n"
+" sunt semnate de către zzz și str4d respectiv. Dezinstalati-le "
+"înainte de a instala\n"
+" celălalt."
+
+#: i2p2www/pages/downloads/list.html:137
+msgid "Source package"
+msgstr "sursă pachete"
+
+#: i2p2www/pages/downloads/list.html:147
+#, python-format
+msgid ""
+"Alternately, you can fetch the source from monotone\n"
+" or via Git from git.repo.i2p or Github.\n"
+"
\n"
+" Run (tar xjvf i2psource_%(i2pversion)s.tar.bz2 ; cd "
+"i2p-%(i2pversion)s ; ant pkg) then either\n"
+" run the GUI installer or headless install as above."
+msgstr ""
+"Alternativ, puteți descărca sursă din monotone\n"
+" sau prin Git din git.repo.i2p sau Github.\n"
+"
\n"
+" Porniti (tar xjvf i2psource_%(i2pversion)s.tar.bz2 ; cd "
+"i2p-%(i2pversion)s ; ant pkg) atunci \n"
+" rulati programul de instalare GUI sau de instalare fără cap ca mai "
+"sus"
+
+#: i2p2www/pages/downloads/list.html:162
+#, python-format
+msgid ""
+"The files are signed by zzz,\n"
+"whose key is here."
+msgstr ""
+"Fișierele sunt semnate de către zzz,\n"
+" al cărui cheie este aici."
+
+#: i2p2www/pages/downloads/list.html:167
+msgid ""
+"I2P can also be downloaded from our project pages on Launchpad and Google Code."
+msgstr ""
+"I2P poate fi descărcat de pe paginile noastre proiectului pe Launchpad si Google Code."
+
+#: i2p2www/pages/downloads/list.html:173
+msgid ""
+"After running the installer on windows, simply click on the \"Start I2P\""
+" button\n"
+"which will bring up the router console,\n"
+"which has further instructions."
+msgstr ""
+"După rularea instalarii pe Windows, pur și simplu faceți clic pe butonul "
+"\"Start I2P\"\n"
+"care va aduce la a href=\"http://localhost:7657/index.jsp\">consola "
+"router,\n"
+"unde gasiti instrucțiuni suplimentare."
+
+#: i2p2www/pages/downloads/list.html:179
+msgid ""
+"On Unix-like systems, I2P can be started as a service\n"
+"using the \"i2prouter\" script, located in the directory you selected for"
+" I2P.\n"
+"Changing to that directory in a console and issuing \"sh i2prouter "
+"status\"\n"
+"should tell you the router's status. The arguments \"start\", \"stop\" "
+"and \"restart\"\n"
+"control the service. The router console\n"
+"can be accessed at its usual location.\n"
+"For users on OpenSolaris and other systems for which the wrapper (i2psvc)"
+" is not supported,\n"
+"start the router with \"sh runplain.sh\" instead."
+msgstr ""
+"Pe sistemele Unix, I2P poate fi pornit ca un serviciu\n"
+"folosind scriptul \"i2prouter\", situat în directorul selectat pentru "
+"I2P.\n"
+"Treceti in aceasta mapa în consolă și comanda \"sh stare i2prouter\"\n"
+"ar trebui să vă spuna statutul a router-ului. Argumentele \"start\", "
+"\"stop\" și \"restart\"\n"
+"controleaza serviciu. consola"
+" router \n"
+"poate fi accesat prin metoda obisnuita\n"
+"Pentru utilizatorii de OpenSolaris și alte sisteme pentru care nu este "
+"acceptat wrapper (i2psvc),\n"
+"startati router-ul cu comanda \"sh runplain.sh\"."
+
+#: i2p2www/pages/downloads/list.html:190
+#, python-format
+msgid ""
+"When installing for the first time, please remember to adjust your "
+"NAT/firewall\n"
+"if you can, bearing in mind the Internet-facing ports I2P uses,\n"
+"described here among other ports.\n"
+"If you have successfully opened your port to inbound TCP, also enable "
+"inbound TCP on the\n"
+"configuration page."
+msgstr ""
+"Când instalați pentru prima dată, vă rugăm să nu uitați să adaptati "
+"NAT / firewall \n"
+"dacă reusiti, ținând cont de porturile Internet-pe care le utilizeaza "
+"I2P,\n"
+"descris aici printre alte porturi.\n"
+"Dacă ați deschis cu succes portul de intrare TCP, permiteti, de asemenea,"
+" TCP intrare pe\n"
+"pagina de configurare."
+
+#: i2p2www/pages/downloads/list.html:198
+msgid ""
+"Also, please review and adjust the bandwidth settings on the\n"
+"configuration page,\n"
+"as the default settings of 96 KBps down / 40 KBps up are fairly slow."
+msgstr ""
+"Rugam sa examinati si adaptati setările de lățime de bandăpe \n"
+"pagina de configurare \n"
+"deoarece setări implicite de 96 KB / s download / 40 KB / upload sunt "
+"destul de lente"
+
+#: i2p2www/pages/downloads/list.html:208
+msgid "Updates from earlier releases:"
+msgstr "Actualizare de la versiunile anterioare:"
+
+#: i2p2www/pages/downloads/list.html:210
+msgid "Both automatic and manual upgrades are available for the release."
+msgstr "Ambele upgrade-uri automate și manuale sunt disponibile pentru release."
+
+#: i2p2www/pages/downloads/list.html:215
+msgid "Automatic updates"
+msgstr "Actualizări automate"
+
+#: i2p2www/pages/downloads/list.html:217
+msgid ""
+"If you are running 0.7.5 or later, your router should detect the\n"
+"new release. To upgrade simply click the 'Download Update' button on your"
+" router console\n"
+"when it appears."
+msgstr ""
+"Dacă se execută 0.7.5 sau mai noi, router-ul ar trebui să detecteze\n"
+"noua versiune. Pentru a face upgrade pur și simplu faceți clic pe butonul"
+" \"Actualizare Descarca\" pe consola router\n"
+"atunci când apare."
+
+#: i2p2www/pages/downloads/list.html:223
+msgid ""
+"Due to a bug in release 0.7.6, those whose first I2P installation was "
+"that version\n"
+"and have not upgraded manually\n"
+"may get a \"downloaded version is not greater than current version\" "
+"error,\n"
+"and should use the manual update method below."
+msgstr ""
+"Din cauza unui bug în versiune 0.7.6, cele ale caror prima I2P instalare "
+"a fost aceasta versiunea\n"
+"și nu au actualizat manual\n"
+"se poate obține o eroare \"versiune descărcat nu este mai mare decât "
+"versiunea curentă\" ,\n"
+"și ar trebui să folosească metoda de actualizarea manuală de mai jos."
+
+#: i2p2www/pages/downloads/list.html:231
+#, python-format
+msgid ""
+"If you are running 0.7.4 or earlier, please see\n"
+"the 0.7.5 release notes\n"
+"for important information about how to configure your router to "
+"automatically\n"
+"receive the release."
+msgstr ""
+"Dacă se execută 0.7.4 sau anterioară, vă rugăm să consultați 0.7.5 note de publicare pentru informații "
+"importante despre modul de configurare a router-ul pentru primire "
+"automata a publicarii."
+
+#: i2p2www/pages/downloads/list.html:239
+#, python-format
+msgid ""
+"If you are running 0.6.1.30 or earlier, please see\n"
+"instructions\n"
+"for important information about how to configure your router to "
+"automatically\n"
+"receive the release."
+msgstr ""
+"Dacă se execută 0.6.1.30 sau anterioară, vă rugăm să consultați instructiuni pentru informații importante "
+"despre modul de configurare a router-ul pentru primire automata a "
+"publicarii."
+
+#: i2p2www/pages/downloads/list.html:248
+#, python-format
+msgid ""
+"If you have reconfigured your router following the instructions, you should see a link on your"
+" \n"
+" router console "
+"allowing\n"
+" you to download and install the new release by just clicking on that\n"
+" link."
+msgstr ""
+"Dacă ați reconfigurat router-ul ca urmarind instructiunilear trebui să vedeți un link "
+"pe dvs.\n"
+"consola "
+"routerpermițând să descărcați și să instalați noua versiune de "
+"doar clic pe acel link."
+
+#: i2p2www/pages/downloads/list.html:256
+msgid "Alternately, you can use the manual method specified below."
+msgstr ""
+"Alternativ, aveți posibilitatea să utilizați metoda manuală specificate "
+"mai jos."
+
+#: i2p2www/pages/downloads/list.html:266
+msgid "Manual updates"
+msgstr "Actualizările manuale"
+
+#: i2p2www/pages/downloads/list.html:278
+msgid ""
+"Download that file to your I2P\n"
+" installation directory and rename as i2pupdate.zip.\n"
+" (alternately, you can get the source as above and run \"ant "
+"updater\", then copy the\n"
+" resulting i2pupdate.zip to your I2P installation directory). You do"
+" \n"
+" NOT need to unzip that file."
+msgstr ""
+"Descărca acest fișier pentru I2P dvs. in mapa de instalare "
+"șiredenumiti ca i2pupdate.zip\n"
+"(Alternativ, puteți obține sursa ca mai sus și a porni \"ant Updater\", "
+"apoi copiați i2pupdate.zip la directorul de instalare I2P). NU este "
+"nevoie pentru a dezarhiva acest fișier."
+
+#: i2p2www/pages/downloads/list.html:287
+msgid "Click \"Restart\""
+msgstr ""
+"Faceti clic pe \"Restart\""
+
+#: i2p2www/pages/downloads/list.html:292
+msgid "Grab a cup of coffee and come back in 11 minutes"
+msgstr "Serviti o ceașcă cu cafea și reveniti înapoi în 11 minute"
+
+#: i2p2www/pages/downloads/list.html:300
+#, python-format
+msgid ""
+"The file is signed by zzz,\n"
+"whose key is here."
+msgstr ""
+"Fișierul este semnat de către zzz,\n"
+" al cărui cheie este aici."
+
+#: i2p2www/pages/downloads/list.html:305
+msgid "Previous Releases"
+msgstr "Versiune precedent"
+
+#: i2p2www/pages/downloads/list.html:307
+#, python-format
+msgid ""
+"Previous releases are available on Google "
+"Code\n"
+"and Launchpad\n"
+"and within the I2P network on %(echelon)s."
+msgstr ""
+"Versiune anterioara este disponibila Google "
+"Code\n"
+"si pe Launchpad\n"
+"si in retea i2p %(echelon)s."
+
+#: i2p2www/pages/downloads/select.html:2 i2p2www/pages/downloads/select.html:4
+msgid "Mirror selection"
+msgstr "Alegerea serverului alternativ"
+
+#: i2p2www/pages/downloads/select.html:5
+msgid "File:"
+msgstr "Fişier:"
+
+#: i2p2www/pages/downloads/select.html:10
+msgid "Any mirror"
+msgstr "Orice server alternativ"
+
+#: i2p2www/pages/global/bounty.html:19
+msgid ""
+"To claim the bounty the author must not be paid by other organizations\n"
+"or teams for this work (e.g. GSoC students are not valid)."
+msgstr ""
+"Pentru a pretinde recompense autorul nu trebuie să fie plătit de către "
+"alte organizații\n"
+"sau echipe pentru acest lucru (de exemplu, elevi GSoC nu sunt valabile)."
+
+#: i2p2www/pages/global/bounty.html:29
+#, python-format
+msgid ""
+"Bounty amounts may be increased by further donations. Do\n"
+"you think these are important? Add in your "
+"donation, \n"
+"marking the amount for the %(donatename)s bounty!"
+msgstr ""
+"Sumele de recompense poate fi majorat prin donatii suplimentare.\n"
+"Credeti ca este important?Adauga in donatia ta"
+"\n"
+"alegeti suma pentru recompense %(donatename)s"
+
+#: i2p2www/pages/global/error_404.html:3
+msgid "Not found"
+msgstr "Nu s-a găsit"
+
+#: i2p2www/pages/global/error_404.html:9
+msgid ""
+"Yep... the resource, you were searching for, is named differently, "
+"doesn't exist or was removed."
+msgstr ""
+"Da ... resursa, le cautati, este numită în mod diferit, nu există sau a "
+"fost eliminata."
+
+#: i2p2www/pages/global/error_500.html:5
+msgid "Server error"
+msgstr "Eroare server"
+
+#: i2p2www/pages/global/error_500.html:13
+msgid "500 Server error"
+msgstr "500 Eroare server"
+
+#: i2p2www/pages/global/error_500.html:17
+msgid "Umm... the server encountered some sort of error."
+msgstr "Hmm ... Serverul a întâlnit ceva greutăți."
+
+#: i2p2www/pages/global/footer.html:2
+msgid "Mirrors"
+msgstr "Servere alternative"
+
+#: i2p2www/pages/global/footer.html:9
+msgid "Secure"
+msgstr "Sigur"
+
+#: i2p2www/pages/global/footer.html:16
+msgid "Misc."
+msgstr "Diverse"
+
+#: i2p2www/pages/global/footer.html:19 i2p2www/pages/site/links.html:2
+msgid "Links"
+msgstr "Linkuri"
+
+#: i2p2www/pages/global/footer.html:20
+msgid "Impressum"
+msgstr "Impressum"
+
+#: i2p2www/pages/global/footer.html:24
+msgid "T-Shirts!"
+msgstr "Tricouri!"
+
+#: i2p2www/pages/global/footer.html:26
+msgid "Europe"
+msgstr "Europa"
+
+#: i2p2www/pages/global/footer.html:27
+msgid "USA"
+msgstr "SUA"
+
+#: i2p2www/pages/global/footer.html:31
+msgid "Donate"
+msgstr "Donează"
+
+#: i2p2www/pages/global/layout.html:29
+msgid "Skip navigation"
+msgstr "Treci peste navigare"
+
+#: i2p2www/pages/global/layout.html:32
+msgid "I2P Logo"
+msgstr "Logo I2P "
+
+#: i2p2www/pages/global/layout.html:32 i2p2www/pages/site/index.html:3
+msgid "The Invisible Internet Project"
+msgstr "Proiectul Internet Invizibil"
+
+#: i2p2www/pages/global/layout.html:56
+#, python-format
+msgid ""
+"This page was last updated in %(lastupdated)s and is accurate for router "
+"version %(accuratefor)s."
+msgstr ""
+"Această pagină a fost actualizat ultima dată în %(lastupdated)s și este "
+"corecta pentru versiunea %(accuratefor)s."
+
+#: i2p2www/pages/global/layout.html:60
+#, python-format
+msgid "This page was last updated in %(lastupdated)s."
+msgstr "Această pagină a fost actualizat ultima dată în %(lastupdated)s ."
+
+#: i2p2www/pages/global/layout.html:64
+#, python-format
+msgid "This page is accurate for router version %(accuratefor)s."
+msgstr "Această pagină este corecta pentru versiunea router %(accuratefor)s."
+
+#: i2p2www/pages/global/macros:21
+msgid "Previous"
+msgstr "înapoi"
+
+#: i2p2www/pages/global/macros:36
+msgid "Next"
+msgstr "Înainte"
+
+#: i2p2www/pages/global/macros:43
+msgid "Posted in"
+msgstr "Postat în"
+
+#: i2p2www/pages/global/nav.html:4
+msgid "About"
+msgstr "Despre"
+
+#: i2p2www/pages/global/nav.html:6
+msgid "Introduction to I2P"
+msgstr "Introducere în I2P"
+
+#: i2p2www/pages/global/nav.html:7
+msgid "Comparisons"
+msgstr "Comparații"
+
+#: i2p2www/pages/global/nav.html:9
+msgid "Overview of comparisons"
+msgstr "Prezentare generală a comparațiilor"
+
+#: i2p2www/pages/global/nav.html:13
+msgid "Other anonymous networks"
+msgstr "Alte rețele anonime"
+
+#: i2p2www/pages/global/nav.html:16
+msgid "Documentation"
+msgstr "Documentație"
+
+#: i2p2www/pages/global/nav.html:18
+msgid "Documentation index"
+msgstr "Pagina de start a documentației"
+
+#: i2p2www/pages/global/nav.html:19
+msgid "How does it work?"
+msgstr "Cum functioneaza?"
+
+#: i2p2www/pages/global/nav.html:21
+msgid "Gentle intro"
+msgstr "Gentle introducere "
+
+#: i2p2www/pages/global/nav.html:22
+msgid "Tech intro"
+msgstr "tehnologie introducere"
+
+#: i2p2www/pages/global/nav.html:23
+msgid "Threat model"
+msgstr "Modelul pericolului"
+
+#: i2p2www/pages/global/nav.html:24
+msgid "Garlic routing"
+msgstr "Rutare de usturoi "
+
+#: i2p2www/pages/global/nav.html:25
+msgid "Network database"
+msgstr "Baza de date rețelei"
+
+#: i2p2www/pages/global/nav.html:26
+msgid "Tunnel routing"
+msgstr "rutare tunelurilor"
+
+#: i2p2www/pages/global/nav.html:27
+msgid "Peer selection"
+msgstr "Selecție utilizatorului"
+
+#: i2p2www/pages/global/nav.html:28
+msgid "Cryptography"
+msgstr "Criptografie"
+
+#: i2p2www/pages/global/nav.html:29
+msgid "ElGamal/AES+SessionTags"
+msgstr "ElGamal/AES+SessionTags"
+
+#: i2p2www/pages/global/nav.html:32
+msgid "Specifications"
+msgstr "Specificații"
+
+#: i2p2www/pages/global/nav.html:34
+msgid "Blockfile"
+msgstr "Blockfile"
+
+#: i2p2www/pages/global/nav.html:35
+msgid "Common structures"
+msgstr "Structuri comune"
+
+#: i2p2www/pages/global/nav.html:36
+msgid "Configuration files"
+msgstr "Fișiere de configurare"
+
+#: i2p2www/pages/global/nav.html:37 i2p2www/pages/global/nav.html:59
+msgid "Datagrams"
+msgstr "Datagramele"
+
+#: i2p2www/pages/global/nav.html:38
+msgid "GeoIP files"
+msgstr "Fișiere GeoIP"
+
+#: i2p2www/pages/global/nav.html:41 i2p2www/pages/global/nav.html:91
+msgid "Plugins"
+msgstr "Module"
+
+#: i2p2www/pages/global/nav.html:43 i2p2www/pages/global/nav.html:57
+msgid "Streaming library"
+msgstr "biblioteca Streaming"
+
+#: i2p2www/pages/global/nav.html:44
+msgid "Tunnel creation"
+msgstr "Crearea tunelului"
+
+#: i2p2www/pages/global/nav.html:45
+msgid "Tunnel messages"
+msgstr "Mesajele tunelului"
+
+#: i2p2www/pages/global/nav.html:46
+msgid "Software updates"
+msgstr "Actualizări software"
+
+#: i2p2www/pages/global/nav.html:49
+msgid "API"
+msgstr "API"
+
+#: i2p2www/pages/global/nav.html:58
+msgid "Ministreaming library"
+msgstr "biblioteca MiniStreaming"
+
+#: i2p2www/pages/global/nav.html:63 i2p2www/pages/global/nav.html:116
+msgid "Applications"
+msgstr "Aplicații"
+
+#: i2p2www/pages/global/nav.html:65
+msgid "Supported applications"
+msgstr "Aplicații acceptate"
+
+#: i2p2www/pages/global/nav.html:66
+msgid "Bittorrent"
+msgstr "Bittorrent"
+
+#: i2p2www/pages/global/nav.html:69
+msgid "Protocols"
+msgstr "Protocoale"
+
+#: i2p2www/pages/global/nav.html:71
+msgid "Protocol stack"
+msgstr "Stiva de protocoale"
+
+#: i2p2www/pages/global/nav.html:76
+msgid "Transports"
+msgstr "Transporturi"
+
+#: i2p2www/pages/global/nav.html:78
+msgid "Transport layer overview"
+msgstr "Prezentare generală stratului de transport"
+
+#: i2p2www/pages/global/nav.html:83
+msgid "Tunnels"
+msgstr "Tuneluri"
+
+#: i2p2www/pages/global/nav.html:85
+msgid "Tunnel implementation"
+msgstr "Implementarea tunel"
+
+#: i2p2www/pages/global/nav.html:86
+msgid "Unidirectional tunnels"
+msgstr "Tuneluri unidirecționale"
+
+#: i2p2www/pages/global/nav.html:87
+msgid "Old implementation"
+msgstr "Implementare veche"
+
+#: i2p2www/pages/global/nav.html:90
+msgid "Naming and addressbook"
+msgstr "Denumirea și Agenda"
+
+#: i2p2www/pages/global/nav.html:94
+msgid "Team"
+msgstr "Echipa"
+
+#: i2p2www/pages/global/nav.html:96
+msgid "Hall of Fame"
+msgstr "Sala de faimă"
+
+#: i2p2www/pages/global/nav.html:97
+msgid "Academic papers and peer review"
+msgstr "Lucrări academice și evaluarea utilizatorilor"
+
+#: i2p2www/pages/global/nav.html:98
+msgid "Presentations, tutorials and articles"
+msgstr "Prezentări, tutoriale și articole"
+
+#: i2p2www/pages/global/nav.html:99
+msgid "Contact us"
+msgstr "Contactează-ne"
+
+#: i2p2www/pages/global/nav.html:102
+msgid "Help"
+msgstr "Ajutor"
+
+#: i2p2www/pages/global/nav.html:104
+msgid "FAQ"
+msgstr "FAQ"
+
+#: i2p2www/pages/global/nav.html:105
+msgid "How to browse I2P"
+msgstr "Cum de a naviga I2P"
+
+#: i2p2www/pages/global/nav.html:106
+msgid "Glossary"
+msgstr "Glosar"
+
+#: i2p2www/pages/global/nav.html:107
+msgid "Performance"
+msgstr "Performanță"
+
+#: i2p2www/pages/global/nav.html:108 i2p2www/pages/site/contact.html:28
+msgid "Forums"
+msgstr "Forumuri"
+
+#: i2p2www/pages/global/nav.html:111
+msgid "Volunteer"
+msgstr "Voluntar"
+
+#: i2p2www/pages/global/nav.html:113
+msgid "Get involved!"
+msgstr "Implicaţi-vă!"
+
+#: i2p2www/pages/global/nav.html:114
+msgid "Develop"
+msgstr "Developează"
+
+#: i2p2www/pages/global/nav.html:117
+msgid "Licenses"
+msgstr "Licențe"
+
+#: i2p2www/pages/global/nav.html:118
+msgid "Release signing keys"
+msgstr "Eliberarea cheilor de semnare"
+
+#: i2p2www/pages/global/nav.html:119
+msgid "Signed keys"
+msgstr "Chei semnate"
+
+#: i2p2www/pages/global/nav.html:120
+msgid "Developers keys"
+msgstr "Cheile dezvoltatorilor"
+
+#: i2p2www/pages/global/nav.html:121
+msgid "Bug tracker"
+msgstr "Bug tracker"
+
+#: i2p2www/pages/global/nav.html:124
+msgid "Academic research"
+msgstr "Cercetare academică"
+
+#: i2p2www/pages/global/nav.html:125
+msgid "Open research questions"
+msgstr "întrebări de cercetare deschise"
+
+#: i2p2www/pages/global/nav.html:126
+msgid "Guides"
+msgstr "Ghiduri"
+
+#: i2p2www/pages/global/nav.html:128
+msgid "New developers"
+msgstr "Dezvoltatorii noi"
+
+#: i2p2www/pages/global/nav.html:129
+msgid "Using an IDE with I2P"
+msgstr "Folosiți un IDE cu I2P"
+
+#: i2p2www/pages/global/nav.html:130
+msgid "Developer guidelines and coding style"
+msgstr "Ghidul dezvoltatorului și stilul de programare"
+
+#: i2p2www/pages/global/nav.html:131
+msgid "Monotone"
+msgstr "Monotone"
+
+#: i2p2www/pages/global/nav.html:132
+msgid "New translators"
+msgstr "Noi traducători"
+
+#: i2p2www/pages/global/nav.html:135
+msgid "Bounties"
+msgstr "Recompensele"
+
+#: i2p2www/pages/global/nav.html:136 i2p2www/pages/meetings/index.html:2
+msgid "Meetings"
+msgstr "Ședințe"
+
+#: i2p2www/pages/global/nav.html:137
+msgid "Roadmap"
+msgstr "Foaia de parcurs"
+
+#: i2p2www/pages/global/nav.html:138
+msgid "Task list"
+msgstr "Listă de sarcini"
+
+#: i2p2www/pages/global/nav.html:141
+msgid "Language"
+msgstr "Limba"
+
+#: i2p2www/pages/meetings/index.html:4
+msgid "I2P Meetings ATOM Feed"
+msgstr ""
+
+#: i2p2www/pages/meetings/index.html:7
+msgid "Logs of past I2P meetings"
+msgstr "Jurnalele întâlnirilor I2P trecute"
+
+#: i2p2www/pages/meetings/index.html:9
+msgid "Meetings are currently on hold until a more suitable time can be chosen."
+msgstr ""
+"Ședințele sunt în prezent în așteptare până la alegerea datei mai "
+"potrivite."
+
+#: i2p2www/pages/meetings/index.html:13
+#, python-format
+msgid ""
+"If you have something to discuss, please find the developers on IRC in "
+"#i2p-dev.\n"
+"Status updates from developers are also "
+"available."
+msgstr ""
+"Dacă aveți ceva de discutat, puteți să găsiți dezvoltatorii pe canalul "
+"IRC în #i2p-dev.\n"
+"Actualizări de stare sunt disponibile de la"
+" dezvoltatori"
+
+#: i2p2www/pages/meetings/show.html:2
+#, python-format
+msgid "I2P Development Meeting %(id)s"
+msgstr "Intilnirea de dezvoltare a I2P %(id)s"
+
+#: i2p2www/pages/meetings/show.html:10
+msgid "Full IRC Log"
+msgstr "IRC jurnal complet"
+
+#: i2p2www/pages/papers/list.html:29
+msgid "By topic"
+msgstr "După subiect"
+
+#: i2p2www/pages/papers/list.html:35
+msgid "By date"
+msgstr "după dată"
+
+#: i2p2www/pages/papers/list.html:41
+msgid "By author"
+msgstr "De autor"
+
+#: i2p2www/pages/papers/list.html:83
+#, python-format
+msgid ""
+"Please send new or corrected entries to\n"
+"%(email)s.
\n"
+"If you can, please format them as BibTeX; see our\n"
+"BibTeX source page for examples.
\n"
+"Remember to include URLs if possible:\n"
+"offline papers are less useful."
+msgstr ""
+"Vă rugăm să trimiteți intrări noi sau corectate la\n"
+"%(email)s.
\n"
+"Dacă se poate, vă rugăm să formatați-le ca BibTeX; vezi\n"
+"Pagina sursă BibTeX pentru exemple.
\n"
+"Nu uitați să includeți URL-uri, dacă este posibil\n"
+"lucrări offline, sunt mai puțin utile."
+
+#: i2p2www/pages/site/contact.html:2
+msgid "Contact"
+msgstr "Contact"
+
+#: i2p2www/pages/site/contact.html:4
+msgid "Email"
+msgstr "Email"
+
+#: i2p2www/pages/site/contact.html:11
+msgid ""
+"Our primary IRC network is the Irc2P network within I2P; a default tunnel"
+" to this network is set up with new router installs.\n"
+" We are also present on multiple standard networks like OFTC,\n"
+" EIN and Freenode.\n"
+" All I2P-related channels on all these network are linked to the main "
+"channels on Irc2P via relay bots."
+msgstr ""
+"Rețeaua noastră principala de IRC este rețeaua Irc2P în I2P, un tunel "
+"implicit pentru această rețea este configurat cu instalarea noua a "
+"router-ului. Suntem, de asemenea, prezenți în mai multe rețele "
+"standard, cum ar fiOFTC, EIN siFreenode. Toate canalele I2P legate "
+"privire la toate aceste rețele sunt legate de principalele canale pe "
+"Irc2P prin intermediul roboții releu."
+
+#: i2p2www/pages/site/contact.html:19
+msgid "Channel list:"
+msgstr "Listă de canale"
+
+#: i2p2www/pages/site/contact.html:21
+msgid "General i2p discussion"
+msgstr "Discuții generale I2P "
+
+#: i2p2www/pages/site/contact.html:22
+msgid "Offtopic"
+msgstr "Offtopic"
+
+#: i2p2www/pages/site/contact.html:23
+msgid "Development talk"
+msgstr "Convorbiri despre dezvoltare"
+
+#: i2p2www/pages/site/contact.html:24
+msgid "Help channel"
+msgstr "Canal pentru ajutor"
+
+#: i2p2www/pages/site/contact.html:29
+#, python-format
+msgid ""
+"Most of the discussion about I2P's development happens on the I2P developer forum. This is usually the best"
+" place to start with inquiries, if the dev IRC channel is inactive."
+msgstr ""
+"Majoritatea discutiilor despre dezvoltarea I2P se intimpla pe I2P forumul dezvoltatorilor.Acesta este, de "
+"obicei, cel mai bun loc pentru a începe cu întrebări, dacă canalul dev "
+"IRC este inactiv."
+
+#: i2p2www/pages/site/contact.html:33
+msgid "Mailing lists"
+msgstr "Liste de discuții"
+
+#: i2p2www/pages/site/contact.html:34
+msgid ""
+"I2P does have a mailing list, but it is rarely used as the current small "
+"team of developers prefer to communicate via IRC or the developer forum. "
+"This may change in future."
+msgstr ""
+"I2P are o listă de corespondență, dar este foarte rar folosit deaoarece "
+"echipa mica de dezvoltatori preferă să comunice prin IRC sau forum. Acest"
+" lucru se poate schimba în viitor."
+
+#: i2p2www/pages/site/contact.html:39
+msgid "Subscribing"
+msgstr "Abonează"
+
+#: i2p2www/pages/site/contact.html:40
+msgid ""
+"To subscribe to a mailing list, go to the list information page (linked "
+"below) and fill out the form. I2P-internal email addresses "
+"(foobar@mail.i2p) can be used."
+msgstr ""
+"Pentru a vă abona la o listă de corespondență, mergeți la pagina de "
+"informații lista (legate de mai jos) și completați formularul.Pot fi "
+"utilizate adrese de e-mail I2P-interne (foobar@mail.i2p) ."
+
+#: i2p2www/pages/site/contact.html:44
+msgid "Unsubscribing"
+msgstr "Dezabonează"
+
+#: i2p2www/pages/site/contact.html:45
+msgid ""
+"To unsubscribe from a mailing list or edit your subscription options, go "
+"to the list information page (linked below) and enter your subscription "
+"email address."
+msgstr ""
+"Pentru a vă dezabona de la o listă de corespondență sau modifica "
+"opțiunile de abonament, du-te la pagina de informații lista (legate de "
+"mai jos) și introduceți adresa dumneavoastră de abonare."
+
+#: i2p2www/pages/site/contact.html:49
+msgid "Lists"
+msgstr "Liste"
+
+#: i2p2www/pages/site/contact.html:52
+msgid "Archive"
+msgstr "Arhivă"
+
+#: i2p2www/pages/site/contact.html:53
+msgid ""
+"General I2P discussion - anything that doesn't fit in a different list "
+"goes here."
+msgstr ""
+"Discutie I2P generala- ceva care nu se încadrează într-o altă listă merge"
+" aici."
+
+#: i2p2www/pages/site/contact.html:59
+msgid ""
+"You don't like mailing lists? Then this is for you. All mailing lists are"
+" available via NNTP as well."
+msgstr ""
+"Nu-ți place listele de discuții? Atunci acest lucru este pentru tine. "
+"Toate listele de discuții sunt de asemenea disponibile prin NNTP."
+
+#: i2p2www/pages/site/contact.html:64
+msgid "Group-List-mapping:"
+msgstr ""
+
+#: i2p2www/pages/site/contact.html:68
+msgid "Servers:"
+msgstr "Servere:"
+
+#: i2p2www/pages/site/faq.html:2
+msgid "Frequently Asked Questions"
+msgstr "Întrebări frecvente"
+
+#: i2p2www/pages/site/faq.html:4
+msgid "Index"
+msgstr "Index"
+
+#: i2p2www/pages/site/faq.html:7
+msgid "General"
+msgstr "General"
+
+#: i2p2www/pages/site/faq.html:9 i2p2www/pages/site/faq.html:51
+msgid "What systems will I2P run on?"
+msgstr "Pe ce sisteme va rula I2P ?"
+
+#: i2p2www/pages/site/faq.html:10
+msgid "Whats an \"eepsite\" and how do I configure my browser so I can use them?"
+msgstr ""
+"Ce este un \"eepsite\" și cum pot configura browser-ul meu, pentru ca "
+"sa-l pot folosi ?"
+
+#: i2p2www/pages/site/faq.html:11 i2p2www/pages/site/faq.html:264
+msgid "My router has very few active peers, is this OK?"
+msgstr "Router-ul meu are foarte puține colegii activi, e bine?"
+
+#: i2p2www/pages/site/faq.html:12 i2p2www/pages/site/faq.html:499
+msgid "What do the Active x/y numbers mean in the router console?"
+msgstr "Ce înseamnă în consola router numere active x/y ?"
+
+#: i2p2www/pages/site/faq.html:13 i2p2www/pages/site/faq.html:226
+msgid ""
+"My active peers / known peers / participating tunnels / connections / "
+"bandwidth vary dramatically over time! Is anything wrong?"
+msgstr ""
+"Colegii mei activi / colegii cunoscuți / tunele / conexiuni / lățime de "
+"bandă participante variaza foarte mult ! Este ceva în neregulă?"
+
+#: i2p2www/pages/site/faq.html:14 i2p2www/pages/site/faq.html:349
+msgid "Is using an outproxy safe?"
+msgstr "Folosirea unui outproxy este sigur?"
+
+#: i2p2www/pages/site/faq.html:15 i2p2www/pages/site/faq.html:375
+msgid "Most of the eepsites within I2P are down?"
+msgstr "Cele mai multe dintre eepsites în I2P nu sunt disponibile?"
+
+#: i2p2www/pages/site/faq.html:16 i2p2www/pages/site/faq.html:528
+msgid "What ports does I2P use?"
+msgstr "Ce porturi folosește I2P?"
+
+#: i2p2www/pages/site/faq.html:17
+msgid "Why is I2P listening for connections on port 32000?"
+msgstr "De ce I2P ascultă pentru conexiuni pe portul 32000?"
+
+#: i2p2www/pages/site/faq.html:18 i2p2www/pages/site/faq.html:62
+msgid "I think I found a bug, where can I report it?"
+msgstr "Cred că am găsit un bug, unde pot raporta?"
+
+#: i2p2www/pages/site/faq.html:19 i2p2www/pages/site/faq.html:108
+msgid "What happened to *.i2p.net? What happened to jrandom? Is I2P dead?"
+msgstr "Ce sa întâmplat cu *. I2p.net? Ce sa întâmplat cu jrandom? Este I2P mort?"
+
+#: i2p2www/pages/site/faq.html:20 i2p2www/pages/site/faq.html:846
+msgid "I have a question!"
+msgstr "Am o intrebare!"
+
+#: i2p2www/pages/site/faq.html:22
+msgid "Setup"
+msgstr "Configurare"
+
+#: i2p2www/pages/site/faq.html:24 i2p2www/pages/site/faq.html:233
+msgid ""
+"My router has been up for several minutes and has zero or very few "
+"connections"
+msgstr ""
+"Router-ul meu a fost pornit pentru câteva minute și are conexiuni la zero"
+" sau foarte puține"
+
+#: i2p2www/pages/site/faq.html:25 i2p2www/pages/site/faq.html:391
+msgid "Why is I2P so slow?"
+msgstr "De ce I2P este atât de lent?"
+
+#: i2p2www/pages/site/faq.html:26 i2p2www/pages/site/faq.html:79
+msgid ""
+"I'm missing lots of hosts in my addressbook. What are some good "
+"subscription links?"
+msgstr ""
+"Îmi lipsește o mulțime de hosturi în Agenda mea. Care sunt link-uri bune "
+"de abonament?"
+
+#: i2p2www/pages/site/faq.html:27 i2p2www/pages/site/faq.html:384
+msgid "How do I set up my own eepsite?"
+msgstr "Cum pot configura propriul meu eepsite?"
+
+#: i2p2www/pages/site/faq.html:28 i2p2www/pages/site/faq.html:417
+msgid "Bittorrent / I2PSnark / Azureus I2P Plugin Questions?"
+msgstr "Bittorrent / I2PSnark / Azureus I2P Plugin intrebari?"
+
+#: i2p2www/pages/site/faq.html:29 i2p2www/pages/site/faq.html:424
+msgid "How do I connect to IRC within I2P?"
+msgstr "Cum ma pot conecta la IRC în I2P?"
+
+#: i2p2www/pages/site/faq.html:30 i2p2www/pages/site/faq.html:282
+msgid "I can't access regular Internet sites through I2P."
+msgstr "Eu nu pot accesa site-uri din internet prin I2P."
+
+#: i2p2www/pages/site/faq.html:31 i2p2www/pages/site/faq.html:297
+msgid "I can't access https:// or ftp:// sites through I2P."
+msgstr "Eu nu pot accesa site-uri https:// sau ftp:// prin I2P."
+
+#: i2p2www/pages/site/faq.html:32 i2p2www/pages/site/faq.html:507
+msgid "Is it possible to use I2P as a SOCKS proxy?"
+msgstr "Este posibil să se utilizeze I2P ca un proxy SOCKS?"
+
+#: i2p2www/pages/site/faq.html:33 i2p2www/pages/site/faq.html:490
+msgid "How do I configure my browser?"
+msgstr "Cum pot configura browser-ul meu?"
+
+#: i2p2www/pages/site/faq.html:34 i2p2www/pages/site/faq.html:435
+msgid ""
+"How can I access the web console from my other machines or password "
+"protect it?"
+msgstr "Cum pot accesa consola web de la alte mașini sau proteja prin parola "
+
+#: i2p2www/pages/site/faq.html:35 i2p2www/pages/site/faq.html:475
+msgid "How can I use applications from my other machines?"
+msgstr "Cum pot utiliza aplicații de la alte calculatoare?"
+
+#: i2p2www/pages/site/faq.html:36 i2p2www/pages/site/faq.html:749
+msgid "How do I reseed manually?"
+msgstr "Cum pot reseedui manual?"
+
+#: i2p2www/pages/site/faq.html:37 i2p2www/pages/site/faq.html:125
+msgid "My router is using too much CPU?!?"
+msgstr "Router-ul meu utilizează prea mult CPU?!?"
+
+#: i2p2www/pages/site/faq.html:39
+msgid "Misconception"
+msgstr "Neînțelegere"
+
+#: i2p2www/pages/site/faq.html:41 i2p2www/pages/site/faq.html:367
+msgid ""
+"How do I access IRC, BitTorrent, or other services on the regular "
+"Internet?"
+msgstr "Cum pot accesa IRC, BitTorrent, sau alte servicii de pe Internet obișnuit?"
+
+#: i2p2www/pages/site/faq.html:42
+msgid ""
+"Is my router an \"exit node\"(outproxy) to the regular Internet? I don't "
+"want it to be."
+msgstr ""
+"Este oare router-ul meu un \"nod de ieșire\" (outproxy) la Internet "
+"obișnuit? Nu vreau să fie."
+
+#: i2p2www/pages/site/faq.html:43 i2p2www/pages/site/faq.html:189
+msgid ""
+"I am opposed to certain types of content. How do I keep from "
+"distributing, storing, or accessing them?"
+msgstr ""
+"Mă opun la anumite tipuri de conținut. Cum pot ține de la distribuirea, "
+"stocarea, accesarea lor?"
+
+#: i2p2www/pages/site/faq.html:45
+msgid "Errors and Their Solutions"
+msgstr "Erorile și soluțiile lor"
+
+#: i2p2www/pages/site/faq.html:47 i2p2www/pages/site/faq.html:785
+msgid ""
+"I'm using FreeBSD and when I start I2P I receive an error about "
+"libm.so.4!"
+msgstr ""
+"Folosesc FreeBSD și atunci când pornesc I2P primesc o eroare cu privire "
+"la libm.so.4 !"
+
+#: i2p2www/pages/site/faq.html:48
+msgid ""
+"In wrapper.log I see an error stating Protocol family "
+"unavailable when I2P is loading"
+msgstr ""
+"În wrapper.log văd o eroare Protocol family "
+"unavailable când se încarcă I2P"
+
+#: i2p2www/pages/site/faq.html:52 i2p2www/pages/site/faq.html:63
+#: i2p2www/pages/site/faq.html:80 i2p2www/pages/site/faq.html:109
+#: i2p2www/pages/site/faq.html:126 i2p2www/pages/site/faq.html:190
+#: i2p2www/pages/site/faq.html:227 i2p2www/pages/site/faq.html:234
+#: i2p2www/pages/site/faq.html:265 i2p2www/pages/site/faq.html:274
+#: i2p2www/pages/site/faq.html:283 i2p2www/pages/site/faq.html:298
+#: i2p2www/pages/site/faq.html:350 i2p2www/pages/site/faq.html:368
+#: i2p2www/pages/site/faq.html:376 i2p2www/pages/site/faq.html:385
+#: i2p2www/pages/site/faq.html:392 i2p2www/pages/site/faq.html:418
+#: i2p2www/pages/site/faq.html:425 i2p2www/pages/site/faq.html:436
+#: i2p2www/pages/site/faq.html:476 i2p2www/pages/site/faq.html:483
+#: i2p2www/pages/site/faq.html:491 i2p2www/pages/site/faq.html:500
+#: i2p2www/pages/site/faq.html:508 i2p2www/pages/site/faq.html:529
+#: i2p2www/pages/site/faq.html:737 i2p2www/pages/site/faq.html:750
+#: i2p2www/pages/site/faq.html:786 i2p2www/pages/site/faq.html:818
+#: i2p2www/pages/site/faq.html:847
+msgid "link"
+msgstr "link"
+
+#: i2p2www/pages/site/faq.html:53
+#, python-format
+msgid ""
+"While I2P has been reported to run PCs as meagre as a low-end Pentium II "
+"with 64 MB of RAM, you'll have a much better experience on a Pentium III "
+"(or better) with 128MB of RAM (or more). A chart "
+"comparing the performance of the various JREs can be found at %(chart)s, but in short: it's at all possible, use"
+" Sun/Oracle Java or OpenJDK."
+msgstr ""
+"În timp ce I2P poate fi pornita la PC-uri slabe ca de ex. un low-end "
+"Pentium II, cu 64 MB de RAM, veti avea o performanta mult mai bună pe un "
+"Pentium III (sau mai performant), cu 128 MB de RAM (sau mai mult).A grafic care compară performanța a diferitelor JRE "
+"pot fi găsite la %(chart)s, dar pe scurt: e "
+"posibil, folositi Sun / Oracle Java sau OpenJDK."
+
+#: i2p2www/pages/site/faq.html:57
+msgid ""
+"I2P has been tested on Windows, Linux, FreeBSD (see the note below), OSX, and OpenSolaris. There is work "
+"underway to bring I2P to the Android platform."
+msgstr ""
+"I2P a fost testat pe Windows, Linux, FreeBSD (vezi notade mai jos),OSX,si OpenSolaris.I2P pentru "
+"platforma Android este în curs de desfășurare"
+
+#: i2p2www/pages/site/faq.html:65
+msgid "Here are some places, pick one or more."
+msgstr "Iata cateva locuri, alege una sau mai multe."
+
+#: i2p2www/pages/site/faq.html:71
+msgid "Discuss with the developers on IRC in #i2p-dev"
+msgstr "Discutați cu dezvoltatorii pe IRC la # I2P-dev"
+
+#: i2p2www/pages/site/faq.html:75
+msgid "Please include relevant information from the router logs and wrapper logs."
+msgstr ""
+"Vă rugăm să includeți informații relevante din jurnalele router și "
+"jurnalele wrapper."
+
+#: i2p2www/pages/site/faq.html:81
+msgid ""
+"The default subscription is to http://www.i2p2.i2p/hosts.txt which is "
+"updated rarely.\n"
+"If you don't have another subscription, you may often have to use "
+"\"jump\" links which\n"
+"is annoying."
+msgstr ""
+"Abonamentul implicit este http://www.i2p2.i2p/hosts.txt care este "
+"actualizat foarte rar.Dacă nu aveți încă un abonament, va trebui de multe"
+" ori să utilizeze \"sarituri\" de link-uri ce este destul de enervant."
+
+#: i2p2www/pages/site/faq.html:87
+msgid ""
+"Here are some other public addressbook subscription links. You may wish "
+"to add one or two\n"
+"to your susidns "
+"subscription list.\n"
+"You don't need to add all of them, as they sync with each other "
+"periodically.\n"
+"The links using a cgi-bin application employ various strategies to "
+"minimize\n"
+"the number of duplicate addresses delivered, so they should be more "
+"efficient.\n"
+"Note that subscribing to a hosts.txt service is an act of \"trust\", as a"
+" malicious\n"
+"subscription could give you incorrect addresses. So think about whether "
+"you\n"
+"want to trust any of these.\n"
+"The operators of these services may have various policies for listing "
+"hosts.\n"
+"Presence on this list does not imply endorsement."
+msgstr ""
+"Iată câteva alte link-uri de abonament din agenda publică. Poate veți "
+"dori să adăugați una sau două\n"
+"la lista de "
+"abonamente susidns.\n"
+"Nu aveți nevoie să adăugați toate acestea, așa cum ele se sincronizeaza "
+"intre ele periodic.\n"
+"Link-urile folosite de o aplicație CGI-bin folosesc diferite strategii "
+"pentru a minimiza\n"
+"numărul din adrese duplicate livrate, astfel încât acestea ar trebui să "
+"fie mai eficiente.\n"
+"Rețineți că abonarea la un serviciu Hosts.txt este un act de "
+"\"încredere\", ca un malware\n"
+"abonamentar pot să vă dee adrese incorecte. Deci, gândiți dacă\n"
+"doriti să aveti încredere in oricare dintre acestea.\n"
+"Operatorii acestor servicii pot avea diferite politici pentru gazde "
+"listare.\n"
+"Prezența pe această listă nu implică aprobarea."
+
+#: i2p2www/pages/site/faq.html:110
+msgid ""
+"Jrandom was the lead developer of I2P and\n"
+"Syndie for several years.\n"
+"We do not know if or when jrandom will return.\n"
+"The *.i2p.net domains were left in a non-functioning state after a power\n"
+"outage at the hosting company."
+msgstr ""
+"Jrandom a fost dezvoltator al I2P și\n"
+" Syndie pentru mai mulți ani.\n"
+"Noi nu știm dacă sau când jrandom va reveni.\n"
+"*. Domenii i2p.net s-au lăsat într-o stare non-functionare dupa o cadere "
+"de tensiune la compania de găzduire."
+
+#: i2p2www/pages/site/faq.html:118
+#, python-format
+msgid ""
+"See this page for jrandom's parting message "
+"and additional information\n"
+"on the migration of *.i2p.net to this website."
+msgstr ""
+"Vezi această pagină pentru mesajul de "
+"despărțire jrandom și informații suplimentare\n"
+"cu privire la migrația din *. i2p.net la acest site"
+" ."
+
+#: i2p2www/pages/site/faq.html:123
+msgid "I2P remains in active development."
+msgstr "I2P rămâne în dezvoltare activă."
+
+#: i2p2www/pages/site/faq.html:127
+msgid "There are many possible causes of high CPU usage. Here is a checklist:"
+msgstr ""
+"Există mai multe cauze posibile de utilizare inalta a procesorului. Aici "
+"este o listă:"
+
+#: i2p2www/pages/site/faq.html:132
+msgid ""
+"Try to use either OpenJDK or Sun/Oracle Java if it's available for your "
+"system. You can check \n"
+"which version of java you have installed by typing java "
+"-version at a \n"
+"command/shell prompt. Performance tends to suffer with other "
+"implementations of java."
+msgstr ""
+"Încercați să utilizați OpenJDK sau Sun / Oracle Java dacă este "
+"disponibilă pentru sistemul dvs. Puteți verifica\n"
+"ce versiune de Java ați instalat prin taparea comenzii java "
+"-version , \n"
+"in linie de comandă .Altfel performanță va suferi cu alte implementari de"
+" Java."
+
+#: i2p2www/pages/site/faq.html:139
+msgid ""
+"Are you running a BitTorrent client over I2P? Try reducing the number of "
+"torrents, the bandwidth limits,\n"
+"or try turning it off completely to see if that helps."
+msgstr ""
+"Este pornit client BitTorrent in retea I2P? Încercați să reduceți "
+"numărul de torente, limitele de lățime de bandă,\n"
+"sau încercați să opriți-l complet pentru a vedea dacă, daca vă ajută."
+
+#: i2p2www/pages/site/faq.html:145
+msgid ""
+"Are your bandwidth limits set too high? It is possible that too much "
+"traffic is going through your\n"
+"I2P router and it is overloaded. Try reducing the setting for share "
+"bandwidth percentage on the configuration page."
+msgstr ""
+"Sunt oare limitele de lățime de bandă prea mare? Este posibil ca prea "
+"mult trafic trece prin intermediul I2P router dvs.care este "
+"supraîncărcat. Încercați să reduceți setarea procentajului lățimii "
+"de bandă pe pagina de "
+"configurație."
+
+#: i2p2www/pages/site/faq.html:150
+msgid ""
+"Make sure that you're running the latest version of I2P to get the "
+"benefits of increased performance and bug fixes."
+msgstr ""
+"Asigurați-vă că rulați cea mai recentă versiune a I2P pentru a obține "
+"beneficii de performanță crescuta și repararea bug-urilor."
+
+#: i2p2www/pages/site/faq.html:155
+msgid ""
+"Has enough memory been set aside for use by I2P? Look at the memory graph"
+" on the graphs page to see\n"
+"if the memory usage is \"pegged\"—the JVM is spending most of its "
+"time in\n"
+"garbage collection. Increase the setting "
+"wrapper.java.maxmemory in wrapper.config."
+msgstr ""
+"A fost stabilita memorie suficientă pentru a fi utilizate de către I2P? "
+"Uită-te la graficul de memorie pe pagina de grafice În cazul "
+"în care utilizarea memoriei este \"legata\" — -JVM petrece "
+"majoritatea timpului în colectarea gunoiului. Măriți setarea "
+"wrapper.java.maxmemory în wrapper.config ."
+
+#: i2p2www/pages/site/faq.html:162
+msgid ""
+"Is the CPU usage simply higher than you would like, or is it pegged at "
+"100% for a long time?\n"
+"If it's pegged, this could be a bug. Look in the logs for clues."
+msgstr ""
+"Este oare utilizarea procesorului pur și simplu mai mare decât ar dori, "
+"sau este la 100% pentru o perioadă lungă de timp?\n"
+"Dacă este legat, acest lucru ar putea fi un bug. Uită-te în jurnalele "
+"pentru indicii."
+
+#: i2p2www/pages/site/faq.html:168
+#, python-format
+msgid ""
+"You may be using the Java-based BigInteger library instead of the native "
+"version,\n"
+"especially if you are running on a new or unusual OS or hardware "
+"(OpenSolaris, mipsel, etc.).\n"
+"See the jbigi page for instructions on\n"
+"diagnosing, building, and testing methods."
+msgstr ""
+"Ați putea fi folosi Java bazate pe biblioteca BigInteger în loc de "
+"versiunea nativa,\n"
+"mai ales dacă se execută pe un sistem de operare sau hardware nou sau "
+"neobișnuit (OpenSolaris, Mipsel, etc).\n"
+"Vezi jbigi pagina pentru instrucțiuni privind"
+"\n"
+"diagnosticarea, construirea, și metode de testare."
+
+#: i2p2www/pages/site/faq.html:176
+msgid ""
+"If your native jbigi library is working fine, the biggest user of\n"
+"CPU may be routing traffic for participating tunnels. This uses CPU\n"
+"because at each hop a layer of encryption must be decoded.\n"
+"You can limit participating traffic in two ways - by reducing the\n"
+"share bandwidth on\n"
+"confignet.jsp,\n"
+"or by setting router.maxParticipatingTunnels=nnn on\n"
+"configadvanced.jsp."
+msgstr ""
+"Dacă biblioteca nativă jbigi lucreaza bine, cel mai mare utilizator de\n"
+"CPU poate fi rutarea de trafic pentru tuneluri participante. Acesta "
+"utilizează CPU\n"
+"deoarece la fiecare hamei trebuie decodificat un strat de criptare.\n"
+"Puteți limita participarea trafic în două moduri - prin reducerea\n"
+"cota de lățime de bandă pe\n"
+" confignet.jsp ,\n"
+"sau prin stabilirea router.maxParticipatingTunnels = nnn pe\n"
+" configadvanced.jsp "
+".\n"
+
+#: i2p2www/pages/site/faq.html:191
+msgid ""
+"Hmm. I2P is an anonymous network, so that's a tricky one.\n"
+"I2P is designed to withstand censorship, providing a means for everyone "
+"to communicate freely. \n"
+"The best way to keep your PC free of (encrypted) traffic that you dislike"
+" is to not use I2P.\n"
+"Freedom of speech has some costs.\n"
+"But let's address your question in three parts:"
+msgstr ""
+"Hmm. I2P este o rețea anonimă, astfel încât este si complicată.\n"
+"I2P este proiectat să reziste cenzurii, oferind un mijloc pentru toată "
+"lumea de a comunica liber.\n"
+"Cel mai bun mod de a menține PC-ul liber de trafic (criptat) care nu va "
+"place este de a nu utiliza I2P.\n"
+"Libertatea de exprimare are unele costuri.\n"
+"Dar haideți să vă răspundem la întrebare în trei părți:"
+
+#: i2p2www/pages/site/faq.html:200
+msgid ""
+"Distribution - All traffic on I2P is encrypted in multiple layers."
+" You don't know\n"
+"a message's contents, source, or destination.\n"
+"All traffic you route is internal to the I2P network, you are not an exit node (outproxy).\n"
+"Your only alternative is to refuse to route\n"
+"any traffic, by setting your share bandwidth or maximum "
+"participating tunnels to 0 (see above).\n"
+"It would be nice if you didn't do this, you should help the network by "
+"routing traffic for others.\n"
+"Over 95% of users route traffic for others."
+msgstr ""
+" Distribuție - Tot traficul pe I2P este criptat in mai multe "
+"straturi. Tu nu stii\n"
+"conținutul unui mesaj, sursa, sau destinație.\n"
+"Tot traficul din cale este intern la rețeaua I2P, nu sunteți un nod de ieșire (outproxy).\n"
+"Singura ta alternativa este de a refuza să trasezi\n"
+" orice trafic, prin setarea latimii de banda parte sau tuneluri "
+"maxime participante la 0 (vezi mai sus).\n"
+"Ar fi frumos, dacă sa nu faceti acest lucru, ar trebui să ajutati rețeaua"
+" de rutare de trafic pentru alții.\n"
+"Peste 95% d37in utilizatorii transmit trafic de rută pentru alții.\n"
+
+#: i2p2www/pages/site/faq.html:211
+msgid ""
+"Storage - I2P does not do distributed storage of content. You must"
+" be thinking of\n"
+"Freenet.\n"
+"Nobody's content is being stored on your computer by running I2P."
+msgstr ""
+" stocare - I2P nu face distributie de stocare conținutului. "
+"Altfel trebuie să va gânditi la\n"
+" Freenet .\n"
+"La rularea I2P Conținutul nimănui nu este stocat pe computerul dvs.."
+
+#: i2p2www/pages/site/faq.html:218
+msgid ""
+"Access - If there are some eepsites you don't like, don't go "
+"there.\n"
+"Or, use a blocking proxy like Privoxy or some type of \"net nanny\"."
+msgstr ""
+" Acces - Dacă există unele eepsites care nu vă plac, nu le "
+"vizitați.\n"
+"Sau, folosiți un proxy de blocare ca de ex. Privoxy sau un anumit tip de "
+"\"Net Nanny\"."
+
+#: i2p2www/pages/site/faq.html:228
+msgid ""
+"No. This is normal.\n"
+"All routers adjust dynamically to changing network conditions and demands."
+msgstr ""
+"Nu. Acest lucru este normal.\n"
+"Toate routerele se adapteaza dinamic la schimbarea cerințelor și "
+"condițiilor de rețea ."
+
+#: i2p2www/pages/site/faq.html:235
+msgid ""
+"You may need to reseed your I2P router. With recent versions of I2P you "
+"can go to http://localhost:7657/configreseed"
+" and click the Save Changes and Reseed Now button. If this "
+"method doesn't work—or you're using a very old version—you "
+"may need to reseed manually."
+msgstr ""
+"Posibil să aveți nevoie pentru a reseedui router-ul I2P. Cu versiuni "
+"recente ale I2P puteți merge la http://localhost:7657/configreseedși"
+" faceți clic pe Salvați modificările și reseedui acumDacă "
+"această metodă nu funcționează— sau in cazul in care utilizați o "
+"versiune foarte veche, este posibil să trebuiască să reseedui manual ."
+
+#: i2p2www/pages/site/faq.html:238
+msgid ""
+"The reseed URL changed a few years ago. If this is your first install and"
+" you have installed\n"
+"an old (0.6.1.30 or earlier) release, or\n"
+"you have not run I2P in a long time, you must change the URL and then\n"
+"click \"Reseed\" on the console to find other routers.\n"
+"After your router is running,\n"
+"on configadvanced.jsp,"
+"\n"
+"add the line i2p.reseedURL=http://netdb.i2p2.de/\n"
+"OR i2p.reseedURL=http://i2pdb.tin0.de/netDb/ (either should "
+"work),\n"
+"then click \"Apply\", then click the \"reseed\" link on the left."
+msgstr ""
+"URL-ul reseed este schimbat acum câțiva ani. Dacă aceasta este prima "
+"instalare și ați instalat\n"
+"un vechi (0.6.1.30 sau anterioara) release, sau\n"
+"nu ați rulat I2P într-o lungă perioadă de timp, trebuie să modificați "
+"URL-ul și apoi\n"
+"faceți clic pe \"reseedui\" pe consola pentru a găsiți alte routere.\n"
+"După ce router-ul se execută,\n"
+" configadvanced.jsp "
+",\n"
+"adăugați linia i2p.reseedURL = http://netdb.i2p2.de/ \n"
+"SAU i2p.reseedURL = http://i2pdb.tin0.de/netDb/ (oricare ar "
+"trebui să funcționeze),\n"
+"apoi faceți clic pe \"Apply\", apoi faceți clic pe linkul \"reseed\" din "
+"stanga."
+
+#: i2p2www/pages/site/faq.html:249
+#, python-format
+msgid ""
+"This works if you are running 0.6.1.27 or later.\n"
+"If you are running release 0.6.1.31 or later, you probably don't need to "
+"do this.\n"
+"If you are running release 0.6.1.26 or earlier, either follow the\n"
+"manual reseed instructions below\n"
+"or install the latest release.\n"
+"Possible alternate method - add\n"
+"wrapper.java.additional.5=-Di2p.reseedURL=http://netdb.i2p2.de/\n"
+"to wrapper.config, shutdown the router completely, then start again, then"
+" click \"reseed\".\n"
+"Let us know if this works."
+msgstr ""
+"Aceasta funcționează dacă ati pornit versiunea 0.6.1.27 sau ulterioara.\n"
+"Dacă ati pornit versiunea 0.6.1.31 sau ulterioara, probabil că nu trebuie"
+" să faci asta.\n"
+"Dacă ati pornit versiunea 0.6.1.26 sau anterioara, urmați\n"
+" instrucțiuni manual de reseedui de mai "
+"jos\n"
+"sau instalați versiune recentă .\n"
+"Metodă alternativă posibila - adăugați\n"
+" wrapper.java.additional.5 =-Di2p.reseedURL = http://netdb.i2p2.de/ "
+"\n"
+"la wrapper.config, opriti router-ul complet, apoi porniti din nou, apoi "
+"faceți clic pe \"reseedui\".\n"
+"Să ne dati de știre dacă acest lucru funcționează.\n"
+
+#: i2p2www/pages/site/faq.html:260
+#, python-format
+msgid ""
+"...but you *really* should upgrade to "
+"the latest version."
+msgstr ""
+"... dar Dvs *chiar* trebuie să reinnoiti "
+" pina la ultima versiune."
+
+#: i2p2www/pages/site/faq.html:266
+msgid ""
+"If your router has 10 or more active peers, everything is fine. Changes "
+"in releases 0.6.1.31 and 0.6.1.32 improved the\n"
+"efficiency of the router and effectively reduced the number of active "
+"peers.\n"
+"The router should maintain connections to a few peers at all "
+"times.\n"
+"The best way to stay \"better-connected\" to the network is to share more bandwidth."
+msgstr ""
+"Dacă routerul dvs. are 10 sau mai multe colegii activi, totul este bine. "
+"Modificări în versiuni 0.6.1.31 și 0.6.1.32 au îmbunătățit\n"
+"eficiența router-ului și în mod eficient a redus numărul de colegii "
+"activi.\n"
+" Router-ul ar trebui menține conexiuni la câteva colegii în orice"
+" moment.\n"
+"Cel mai bun mod de a rămâne \"mai bine-conectat\" la rețea este de a cota lățimea de bandă mai larga ."
+
+#: i2p2www/pages/site/faq.html:273
+msgid ""
+"Is my router an \"exit node\" to the regular Internet? I don't want it to"
+" be."
+msgstr ""
+"Este oare router-ul meu un \"nod de ieșire\" la Internet obișnuit? Nu "
+"vreau să fie."
+
+#: i2p2www/pages/site/faq.html:275
+msgid ""
+"No. Unlike Tor,\n"
+"\"exit nodes\" or \"outproxies\" are not an inherent part of the network."
+"\n"
+"Only volunteers who set up and run separate applications will relay "
+"traffic to the regular Internet.\n"
+"There are very, very few of these."
+msgstr ""
+"Nu. Spre deosebire de Tor ,"
+"\n"
+"\"noduri de ieșire\" sau \"outproxies\" nu sunt o parte inerentă a "
+"rețelei.\n"
+"Numai voluntari care au înființat și ruleaza aplicații separate dau acces"
+" traficului de releu la Internet regulat.\n"
+"Există foarte, foarte puține dintre acestea."
+
+#: i2p2www/pages/site/faq.html:284
+msgid ""
+"See above. There are very few HTTP \"outproxies\", they are not an "
+"inherent part of the network,\n"
+"and they may not be up.\n"
+"In addition, the old outproxies squid.i2p, true.i2p, and krabs.i2p have "
+"vanished.\n"
+"The only outproxy at the moment is false.i2p.\n"
+"To use it, edit your i2ptunnel "
+"settings for eepProxy\n"
+"and set your outproxy list to 'false.i2p' (only).\n"
+"Then stop and restart the eepProxy.\n"
+"If it doesn't work, the outproxy is not up. It is not I2P's fault.\n"
+"If your primary reason to use an anonymous network is to anonymously "
+"access sites\n"
+"on the regular Internet, you should probably try Tor."
+msgstr ""
+"Vezi mai sus. Există foarte puține HTTP \"outproxies\", ele nu sunt o "
+"parte inerentă a rețelei, și pot să nu fie în sus. În plus, squid.i2p "
+"outproxies vechi, true.i2p, și krabs.i2p au dispărut.Outproxy în acest "
+"moment este numai false.i2p. Pentru a o folosi, modifica setările "
+"i2ptunnel "
+" pentru eepProxy și a stabilit lista de outproxy la \"false.i2p\" "
+"(numai). Apoi, opriți și reporniți eepProxy. În cazul în care nu "
+"funcționează, outproxy nu este pornit. Nu este vina I2P. În cazul în care"
+" motivul principal de a utiliza rețea anonima este de a accesa site-uri "
+"de anonim pe Internet regulat, ar trebui să încercați, probabil Tor ."
+
+#: i2p2www/pages/site/faq.html:299
+msgid ""
+"Within I2P, there is no need for HTTPS, as all traffic is encrypted end-"
+"to-end.\n"
+"FTP is not supported for technical reasons."
+msgstr ""
+"In cadrul I2P, nu este nevoie pentru HTTPS, ca tot traficul este criptat "
+"end-to-end. FTP nu este acceptat din motive tehnice."
+
+#: i2p2www/pages/site/faq.html:303
+msgid ""
+"There are no FTP \"outproxies\" to the Internet—it may not even be "
+"possible to set up one.\n"
+"Any other kind of outproxy may work if it's set up with a standard "
+"tunnel. \n"
+"If you would like to set up some type of outproxy, carefully research the"
+" potential risks.\n"
+"The I2P community may or may not be able to help with the technical "
+"aspects, feel free to ask."
+msgstr ""
+"Nu există FTP \"outproxies\" la Internet, aceasta nu este posibil de "
+"realizat. Orice alt tip de outproxy poate lucra dacă este configurat cu "
+"un tunel standard. Dacă doriți să creati un anumit tip de outproxy, "
+"cercetati cu atenție riscurile potențiale. Comunitatea I2P poate sau nu "
+"poate fi capabila de a ajuta cu aspectele tehnice, nu ezitați să "
+"întrebați."
+
+#: i2p2www/pages/site/faq.html:309
+msgid ""
+"As explained several times above, any existing outproxy isn't a core part"
+" of the network.\n"
+"They are services run by individuals and they may or may not\n"
+"be operational at any given time."
+msgstr ""
+"Așa cum sa explicat de mai multe ori de mai sus, orice outproxy existent "
+"nu este o parte esențială a rețelei. Acestea sunt servicii exploatate de "
+"către persoane fizice și acestea pot sau nu pot fi disponibile la un "
+"moment dat."
+
+#: i2p2www/pages/site/faq.html:314
+msgid ""
+"Update: Thanks to the work of h2ik, there is an https outproxy "
+"available for use via I2P. Starting with I2P 0.8.4 the tunnel is "
+"configured out of the box.
\n"
+"In case the https outproxy is not available in your version of I2P, you "
+"can add it easily by doing the following:"
+msgstr ""
+" Actualizare : Grație muncii de h2ik, există un https outproxy "
+"disponibile pentru utilizare, prin intermediul I2P. Începând cu I2P 0.8.4"
+" tunel "
+"este configurat de la inceput.
În cazul în care https outproxy nu "
+"este disponibil în versiunea de I2P, puteți adăuga cu ușurință si de a "
+"face următoarele:"
+
+#: i2p2www/pages/site/faq.html:320
+msgid ""
+"Open i2p tunnel "
+"manager. Scroll down to the bottom."
+msgstr ""
+"Deschide I2P "
+"manager de tunel . Derulați în jos la partea de jos."
+
+#: i2p2www/pages/site/faq.html:325
+msgid ""
+"Choose CONNECT from New Client Tunnel dropdown list, click "
+"Create"
+msgstr ""
+"Alegeți CONNECT de la New Client Tunnel listă "
+"verticală, faceți clic pe Creare "
+
+#: i2p2www/pages/site/faq.html:330
+#, python-format
+msgid ""
+"In the new page, name and describe your new https tunnel as"
+" you like.\n"
+"The Access Point is your local port for the new https proxy "
+"recommended port's 4445.\n"
+"Outproxy should be the outproxy's .i2p address which supports "
+"https. \n"
+"See this forum post of h2ik's for the "
+"address. \n"
+"Make sure Shared Client, Delay Connect, AutoStart "
+"are checked.\n"
+"Other options should be left at the defaults. Click Save. In tunnel "
+"manger, click the Start button next to your new tunnel."
+msgstr ""
+"În noua pagină, nume și descrie tunel nou https cum "
+"doriți. Access Point este portul local pentru noul https proxy "
+"recomandat portul 4445 . Outproxy ar trebui să fie "
+"adresa outproxy . I2P care sprijină https. A se vedea acest post forum de"
+" h2ik "
+"pentru adresa. Asigurați-vă că Client comun , Delay Connect "
+", AutoStart sunt verificate. Alte opțiuni ar trebui să fie"
+" lăsate la valorile implicite. Faceți clic pe Salvare. În manager de "
+"tunele, faceți clic pe Start butonul de lângă noul tunel."
+
+#: i2p2www/pages/site/faq.html:340
+msgid ""
+"In firefox, click through "
+"Tools>Options>Advanced>Network>Setting."
+"\n"
+"Untick Use this proxy for all protocol, set SSL proxy: to "
+"localhost:4445."
+msgstr ""
+"În Firefox, faceți clic pe Tools Opțiuni avansata "
+" rețea Setarea . Debifați Utilizați acest "
+"proxy pentru toate protocol , stabilit proxy SSL: la "
+"localhost: 4445."
+
+#: i2p2www/pages/site/faq.html:345
+msgid "Done."
+msgstr "Gata."
+
+#: i2p2www/pages/site/faq.html:351
+#, python-format
+msgid ""
+"\n"
+"This is a question that only you can answer because the correct answer "
+"depends on your behaviours, your\n"
+"threat model, and how much you trust the "
+"outproxy operator."
+msgstr ""
+"Aceasta este o întrebare pe care numai puteți răspunde, deoarece "
+"răspunsul corect depinde de comportamentul dvs., modelul amenințare , și cât de mult aveți "
+"încredere operatorului outproxy."
+
+#: i2p2www/pages/site/faq.html:355
+msgid ""
+"Like Tor, I2P does not magically encrypt the Internet.\n"
+"You are vulnerable to snooping by the outproxy operators.\n"
+"The Tor"
+" FAQ\n"
+"does a good job of explaining this."
+msgstr ""
+"Ca si Tor, I2P nu cripteaza magic Internet. Sunteti vulnerabili la "
+"snooping de către operatorii outproxy. "
+" Tor FAQ face o treabă bună de a explica acest lucru."
+
+#: i2p2www/pages/site/faq.html:361
+#, python-format
+msgid ""
+"In addition, you may be vulnerable to collusion between the outproxy "
+"operator\n"
+"and operators of other I2P services, if you use the same tunnels "
+"(\"shared clients\").\n"
+"There is additional discussion about this on %(zzz)s."
+msgstr ""
+"În plus, s-ar putea fi vulnerabile la înțelegeri secrete între operatorul"
+" outproxy și operatorii de alte servicii I2P, dacă utilizați aceleași "
+"tuneluri (\"clienți comune\"). Există discuții suplimentare cu privire la"
+" acest lucru pe % (zzz) s ."
+
+#: i2p2www/pages/site/faq.html:369
+msgid ""
+"Unless an outproxy has been set up for the service you want to connect "
+"to, this cannot be done.\n"
+"There are only three types of outproxies running right now: HTTP, HTTPS, "
+"and email. Note that there is not a SOCKS outproxy.\n"
+"If this type of service is required, try Tor."
+msgstr ""
+"Cu excepția cazului cînd outproxy a fost creat pentru serviciul pe care "
+"doriți să vă conectați, acest lucru nu poate fi făcut. Există doar trei "
+"tipuri de outproxies ce rulează chiar acum: HTTP, HTTPS, și e-mail. "
+"Rețineți că nu există o outproxy SOCKS. În cazul în care este necesar "
+"acest tip de serviciu, încercați "
+" Tor ."
+
+#: i2p2www/pages/site/faq.html:377
+#, python-format
+msgid ""
+"If you consider every eepsite that has ever been created, yes, most of "
+"them are down.\n"
+"People and eepsites come and go.\n"
+"A good way to get started in I2P is check out a list of eepsites that are"
+" currently up.\n"
+"%(eepstatus)s tracks active eepsites."
+msgstr ""
+"Dacă luați în considerare fiecare eepsite care a fost vreodata creat, da,"
+" cele mai multe dintre ele sunt inaccesibile. Oamenii și eepsites vin și "
+"pleacă. O modalitate buna de a începe în I2P este să verificați o listă "
+"de eepsites care sunt în prezent accesibile. % "
+"(eepstatus)s eepsite-uri active."
+
+#: i2p2www/pages/site/faq.html:386
+msgid ""
+"Click on the Website link\n"
+"at the top of your router console for instructions."
+msgstr ""
+"Faceți clic pe site-ul link în "
+"partea de sus a consolei router pentru instrucțiuni."
+
+#: i2p2www/pages/site/faq.html:393
+msgid ""
+"Why are downloads, torrents, web browsing, and everything else so slow on"
+" I2P?\n"
+"The encryption and routing within the I2P network adds a substantial "
+"amount of overhead and limits bandwidth.\n"
+"Anonymity isn't free."
+msgstr ""
+"De ce sunt descărcări, torenți, navigarea pe web, și orice altceva atât "
+"de lent pe I2P? Criptarea și rutare în cadrul rețelei I2P adaugă o sumă "
+"substanțială de lățime de bandă deasupra capului și limite. Anonimatul nu"
+" este gratuit."
+
+#: i2p2www/pages/site/faq.html:398
+msgid ""
+"In addition, you and everybody else probably need to increase your "
+"bandwidth limits.\n"
+"Two key settings are the inbound and outbound bandwidth limiters on\n"
+"the configuration page.\n"
+"With the default settings of 32KBps you will generally get no better than"
+" 15KBps data transfer in I2PSnark.\n"
+"Increasing the settings (but keeping within your actual connection "
+"limitations)\n"
+"will increase the potential transfer rate for I2PSnark and all other "
+"applications."
+msgstr ""
+"În plus, probabil că tu și toți ceilalți au nevoie pentru a crește "
+"limitele lățimii de bandă. Două setări cheie sunt pe inbound și "
+"outbound limitatoarele de lățime de bandă pagina de configurare . "
+"Cu setările implicite de 32kbps, în general, veți obține nimic mai bun "
+"decât transfer de date 15KBps în I2PSnark. Creșterea setărilor (dar cu "
+"menținerea în limitele de conectare reale) va crește rata de transfer "
+"potențial pentru I2PSnark și toate celelalte aplicații."
+
+#: i2p2www/pages/site/faq.html:406
+msgid ""
+"Also, do you have sufficient share bandwidth configured to allow "
+"participating tunnels\n"
+"to route through your router? Believe it or not, allowing participating "
+"traffic\n"
+"keeps you well-integrated in the network and helps your own transfer "
+"speeds."
+msgstr ""
+"De asemenea, aveti lățimea de bandă suficienta pentru configurat pentru "
+"a permite tuneluri participa la traseu prin intermediul router-ul? "
+"Credeti sau nu, permițându-trafic participante vă ține bine integrat în "
+"rețea și ajută la propriile viteze de transfer."
+
+#: i2p2www/pages/site/faq.html:411
+#, python-format
+msgid ""
+"I2P is a work in progress. Lots of improvements and fixes are being "
+"implemented, and\n"
+"generally speaking, running the latest release will help your "
+"performance.\n"
+"If you haven't, install the latest "
+"release."
+msgstr ""
+"I2P este o lucrare în curs de desfășurare. O mulțime de îmbunătățiri și "
+"remedierile sunt implementate, și, în general vorbind, care rulează cea "
+"mai recentă versiune va ajuta la performanta ta. Dacă nu aveți, instalați cea mai recentă versiune ."
+
+#: i2p2www/pages/site/faq.html:419
+#, python-format
+msgid ""
+"See the\n"
+"I2P Bittorrent FAQ"
+msgstr ""
+"Vedeti I2P Bittorrent "
+"FAQ"
+
+#: i2p2www/pages/site/faq.html:426
+msgid ""
+"\n"
+"A tunnel to the main IRC server within I2P, Irc2P, is created when I2P is"
+" installed (see\n"
+"the I2PTunnel "
+"configuration page),\n"
+"and is automatically started when the I2P router starts. To connect to "
+"it, tell your IRC\n"
+"client to connect to localhost 6668. XChat-like client users"
+" can create a\n"
+"new network with the server localhost/6668 (remember to tick"
+" "Bypass\n"
+"proxy server" if you have a proxy server configured)."
+msgstr ""
+"Un tunel la serverul principal IRC în I2P, Irc2P, este creat atunci când "
+"este instalat I2P (a se vedea pagina de configurare "
+"I2PTunnel ), și este pornit automat atunci când router-ul I2P "
+"starteaza. Pentru a vă conecta la ea, spune clientului tau de IRC să se "
+"conecteze la localhost:6668 . Utilizatorii de client-Xchat"
+" ca poate crea o nouă rețea cu serverul localhost:6668 "
+"(nu uitați să bifați \"server proxy Bypass\" dacă aveți un server proxy "
+"configurat)."
+
+#: i2p2www/pages/site/faq.html:437
+msgid ""
+"For security purposes, the router's admin console by default only listens"
+"\n"
+"for connections on the local interface. However, with a little hacking,\n"
+"you can make it reachable remotely:"
+msgstr ""
+"Din motive de securitate, consola admin a router-ului implicit ascultă "
+"numai interfata locala pentru conexiuni. Cu toate acestea, cu un pic de "
+"hacking, puteți face accesibil aceasta de la distanță:"
+
+#: i2p2www/pages/site/faq.html:445
+msgid ""
+"Open ~/.i2p/clients.config and replace
\n"
+"clientApp.0.args=7657 ::1,127.0.0.1 ./webapps/
\n"
+"with
\n"
+"clientApp.0.args=7657 0.0.0.0 ./webapps/"
+msgstr ""
+"Deschide ~/.i2p/clients.config și înlocuiți
"
+"clientApp.0.args=7657 ::1,127.0.0.1 ./webapps/
cu
clientApp.0.args=7657 0.0.0.0 ./webapps/"
+
+#: i2p2www/pages/site/faq.html:453
+msgid ""
+"Go to http://localhost:7657/configui"
+"\n"
+"and add a console username and password if desired."
+msgstr ""
+"Du-te la "
+"http://localhost:7657/configui și adăugați un nume de utilizator și"
+" o parolă, dacă doriti."
+
+#: i2p2www/pages/site/faq.html:459
+msgid ""
+"Go to http://localhost:7657/index.jsp"
+"\n"
+"and hit \"Graceful restart\", which restarts the JVM and reloads the "
+"client applications"
+msgstr ""
+"Du-te la "
+"http://localhost:7657/index.jsp și apasati \"Restart grațios\", "
+"care repornește JVM și reîncarcă aplicații client"
+
+#: i2p2www/pages/site/faq.html:466
+msgid ""
+"After that fires up, you should now be able to reach your console "
+"remotely. Reload the router at\n"
+"http://127.0.0.1:7657 and you will be prompted for the username and "
+"password you specified in step 2\n"
+"above if your browser supports the authentication popup. Note: the\n"
+"0.0.0.0 above specifies an interface, not a network "
+"or netmask. 0.0.0.0\n"
+"means \"bind to all interfaces\", so it can be reachable on "
+"127.0.0.1:7657 as well as\n"
+"any LAN/WAN IP."
+msgstr ""
+"După ce porniti, ar trebui să fie acum posibilitatea de a ajunge la "
+"consola de la distanță. Reîncarcă router la http://127.0.0.1:7657 și vi "
+"se va cere numele de utilizator și parola pe care ați specificat în "
+"pasul 2 de mai sus în cazul în care browser-ul acceptă pop-up de "
+"autentificare. Notă: 0.0.0.0 de mai sus specifica o "
+"interfață, nu o rețea sau netmask. 0.0.0.0 înseamnă \"se leaga de "
+"toate interfetele\", astfel încât să poată fi accesibile pe "
+"127.0.0.1:7657 precum și orice IP LAN/WAN."
+
+#: i2p2www/pages/site/faq.html:477
+msgid ""
+"By default, the router I2CP interface (port 7654) binds to address "
+"127.0.0.1. To bind to 0.0.0.0, set the\n"
+"router advanced configuration option "
+"i2cp.tcp.bindAllInterfaces=true and restart."
+msgstr ""
+"În mod implicit, interfața I2CP router (port 7654) se leaga la adresa "
+"127.0.0.1. Pentru a lega la 0.0.0.0, setati opțiunea de configurarea "
+"avansata i2cp.tcp.bindAllInterfaces = true și restartati."
+
+#: i2p2www/pages/site/faq.html:482
+msgid "Whats an \"eepsite\"?"
+msgstr "Ce este un \"eepsite\"?"
+
+#: i2p2www/pages/site/faq.html:484
+msgid ""
+"An eepsite is a website that is hosted anonymously - you can access it by"
+"\n"
+"setting your web browser's HTTP proxy to use the web proxy (typically it\n"
+"listens on localhost port 4444), and browsing to the site."
+msgstr ""
+"Un eepsite este un site web care este găzduit anonim - îl puteți accesa "
+"prin setarea proxy HTTP browser-ul web pentru folosirea proxy-ul web (de "
+"obicei, se ascultă pe localhost portul 4444), și navigati site-ul."
+
+#: i2p2www/pages/site/faq.html:492
+#, python-format
+msgid ""
+"The proxy config for different browsers is on a \n"
+"separate page with screenshots. More advanced configs with external "
+"tools\n"
+"are possible but could introduce leaks in your setup."
+msgstr ""
+"Configurare proxy pentru diferite browsere este pe o pagină separată cu capturi de ecran. "
+"Configurarea mai avansata cu instrumente externe sunt posibil, dar ar "
+"putea introduce scurgeri de informații în configurarea."
+
+#: i2p2www/pages/site/faq.html:501
+msgid ""
+"x is the number of peers you've sent or received a message from\n"
+"successfully in the last minute, y is the number of peers seen in the "
+"last\n"
+"hour or so."
+msgstr ""
+"x este numărul de parteneri care le-ați trimis sau primit un mesaj de "
+"succes în ultimul minut, y este numărul de colegii văzut în ultima oră "
+"sau cam asa ceva."
+
+#: i2p2www/pages/site/faq.html:509
+msgid ""
+"The SOCKS proxy is working as of release 0.7.1. SOCKS 4/4a/5 are "
+"supported.\n"
+"There is no SOCKS outproxy so it is of limited use."
+msgstr ""
+"Proxy-ul SOCKS lucrează din release 0.7.1. SOCKS 4/4a/5 sunt acceptate. "
+"Nu există nici o SOCKS outproxy asa ca este de o utilitate limitată."
+
+#: i2p2www/pages/site/faq.html:513
+msgid ""
+"In addition, many applications leak sensitive\n"
+"information that could identify you on the Internet. I2P only filters\n"
+"connection data, but if the program you intend to run sends this\n"
+"information as content, I2P has no way to protect your anonymity. For\n"
+"example, some mail applications will send the IP address of the machine\n"
+"they are running on to a mail server. There is no way for I2P to filter\n"
+"this, thus using I2P to 'socksify' existing applications is possible, but"
+"\n"
+"extremely dangerous."
+msgstr ""
+"În plus, multe aplicații scurg informații sensibile ce poate sa va "
+"identifice pe Internet. I2P doar filtreaza date de conectare, dar dacă "
+"programul pe care intenționați să rulați trimite această informație ca "
+"conținut, I2P nu are nici o modalitate de a proteja anonimatul. De "
+"exemplu, unele aplicații de e-mail va trimite adresa IP a aparatului în "
+"care se execută pe un server de mail. Nu există nici o cale pentru I2P a "
+"filtra acest lucru, folosind astfel I2P la \"socksify\" aplicațiile "
+"existente este posibilă, dar extrem de periculos."
+
+#: i2p2www/pages/site/faq.html:523
+#, python-format
+msgid ""
+"If you would like more information on the socks proxy application anyway,"
+"\n"
+"there are some helpful hints on the socks page."
+msgstr ""
+"Dacă doriți mai multe informații cu privire la aplicarea proxy socks, "
+"oricum, există câteva sfaturi utile pe pagina "
+"socks "
+
+#: i2p2www/pages/site/faq.html:530
+msgid ""
+"Okay, here's a rundown of the default ports (everything is configurable\n"
+"through various settings, of course):"
+msgstr ""
+"Okay, aici este o trecere in revista a porturilor implicite (totul este "
+"configurabil prin diverse setari, desigur):"
+
+#: i2p2www/pages/site/faq.html:539
+msgid ""
+"Internet-facing ports\n"
+"Note: New installs as of release 0.7.8 do not use port 8887; they select "
+"a random port\n"
+"between 9000 and 31000 when the program is run for the first time.\n"
+"The selected port is shown on the router configuration page."
+msgstr ""
+" porturi cu care se confruntă de internet Notă: Noi instalari a "
+"release-ului 0.7.8 nu folosesc portul 8887, se alege un port aleator "
+"între 9000 și 31000, atunci când programul este rulat pentru prima dată. "
+"Portul selectat este afișat pe pagina de configurare a "
+"router. "
+
+#: i2p2www/pages/site/faq.html:547
+msgid ""
+"Outbound UDP from the random port noted on the configuration page to "
+"arbitrary remote UDP ports, allowing replies\n"
+" "
+msgstr ""
+" ieșire UDP la portul aleatoriu menționat pe pagina de configurare "
+"pentru porturi UDP arbitrare si îndepărtate , permițând răspunsuri "
+
+#: i2p2www/pages/site/faq.html:552
+msgid ""
+"Outbound TCP from random high ports to arbitrary remote TCP ports\n"
+" "
+msgstr ""
+" ieșire TCP de la porturile aleatorii ridicate la porturi TCP "
+"arbitrare si îndepărtate "
+
+#: i2p2www/pages/site/faq.html:557
+msgid ""
+"(optional, but recommended) Inbound UDP to the port noted on configuration page from "
+"arbitrary locations\n"
+" "
+msgstr ""
+" (optional, dar recomandat) Inbound UDP la portul notat pe pagina de configurare "
+"din mai multe locatii arbitrare "
+
+#: i2p2www/pages/site/faq.html:562
+msgid ""
+"(optional, but recommended) Inbound TCP to the port noted on configuration page from "
+"arbitrary locations
\n"
+"Inbound TCP may be disabled on the configuration page."
+msgstr ""
+" (optional, dar recomandat) Inbound TCP la portul notat pe pagina de configurare "
+"din mai multe locatii arbitrare
Inbound TCP poate fi "
+"dezactivat pe pagina de "
+"configurare . "
+
+#: i2p2www/pages/site/faq.html:568
+msgid ""
+"Outbound UDP on port 123, allowing replies
\n"
+"This is necessary for I2P's internal time sync (via SNTP - \n"
+"querying a random SNTP host in pool.ntp.org or another\n"
+"server you specify)"
+msgstr ""
+" ieșire UDP pe portul 123, permițând răspunsuri
Acest lucru"
+" este necesar pentru timpul intern sincronizare I2P lui (prin SNTP - "
+"interogarea o serie aleator SNTP în pool.ntp.org sau un alt server le "
+"specificați)"
+
+#: i2p2www/pages/site/faq.html:579
+msgid ""
+"Local I2P ports, listening only to local connections by default,\n"
+"except where noted:"
+msgstr ""
+"porturi locale I2P , asculta doar la conexiuni locale în mod "
+"implicit, cu excepția cazului în care a remarcat:"
+
+#: i2p2www/pages/site/faq.html:585
+msgid ""
+"1900: UPnP SSDP UDP multicast listener.\n"
+"Cannot be changed. Binds to all interfaces.\n"
+"May be disabled on confignet.jsp."
+msgstr ""
+" 1900: UPnP SSDP UDP multicast ascultător. nu poate fi "
+"schimbat. Se leaga de toate interfețele. Pot fi dezactivate la confignet.jsp "
+
+#: i2p2www/pages/site/faq.html:592
+msgid ""
+"2827: BOB bridge, a higher level socket API for clients\n"
+"Disabled by default.\n"
+"May be enabled/disabled on configclients.jsp.\n"
+"May be changed in the bob.config file."
+msgstr ""
+" 2827: pod BOB, un nivel mai ridicat socket API pentru clienti "
+" Dezactivat implicit. Poate fi activat / dezactivat pe configclients.jsp . Pot fi modificate în fișierul bob.config. "
+
+#: i2p2www/pages/site/faq.html:600
+msgid ""
+"4444: HTTP proxy\n"
+"May be disabled or changed on the i2ptunnel page in the router "
+"console.\n"
+"May also be configured to be bound to a specific interface or all "
+"interfaces."
+msgstr ""
+"4444: proxy HTTP pot fi dezactivate sau modificate pe pagina "
+"i2ptunnel în consola router. Poate fi, de asemenea, configurate pentru a "
+"fi legat de o interfață specifică sau toate interfețele. "
+
+#: i2p2www/pages/site/faq.html:607
+msgid ""
+"4445: HTTPS proxy\n"
+"May be disabled or changed on the i2ptunnel page in the router "
+"console.\n"
+"May also be configured to be bound to a specific interface or all "
+"interfaces."
+msgstr ""
+"4445: proxy HTTP pot fi dezactivate sau modificate pe pagina "
+"i2ptunnel în consola router. Poate fi, de asemenea, configurate pentru a "
+"fi legat de o interfață specifică sau toate interfețele. "
+
+#: i2p2www/pages/site/faq.html:614
+msgid ""
+"6668: IRC proxy\n"
+"May be disabled or changed on the i2ptunnel page in the router "
+"console.\n"
+"May also be configured to be bound to a specific interface or all "
+"interfaces."
+msgstr ""
+"4444: proxy HTTP pot fi dezactivate sau modificate pe pagina "
+"i2ptunnel în consola router. Poate fi, de asemenea, configurate pentru a "
+"fi legat de o interfață specifică sau toate interfețele. "
+
+#: i2p2www/pages/site/faq.html:621
+msgid ""
+"7652: UPnP HTTP TCP event listener.\n"
+"Binds to the LAN address.\n"
+"May be changed with advanced config i2np.upnp.HTTPPort=nnnn.\n"
+"May be disabled on confignet.jsp."
+msgstr ""
+" 7652: UPnP HTTP TCP eveniment ascultător. Leagă la adresa "
+"LAN. Pot fi modificate cu config avansat i2np.upnp.HTTPPort = nnnn. Pot "
+"fi dezactivate pe 7653: UPnP SSDP UDP search response listener.\n"
+"Binds to all interfaces.\n"
+"May be changed with advanced config i2np.upnp.SSDPPort=nnnn.\n"
+"May be disabled on confignet.jsp."
+msgstr ""
+" 7652: UPnP SSDP UDP cautare raspunsului ascultătorului. "
+"Leagă la adresa LAN. Pot fi modificate cu config avansat "
+"i2np.upnp.HTTPPort = nnnn. Pot fi dezactivate pe 7654: I2P Client Protocol port, used by client apps.\n"
+"May be changed to a different port on\n"
+"configclients.jsp"
+"\n"
+"but this is not recommended.\n"
+"May be to bind to a different interface or all interfaces, or disabled, "
+"on\n"
+"configclients.jsp."
+msgstr ""
+" 7654: I2P Protocol Client port, utilizat de aplicații client. "
+" poate fi schimbat la un alt port de pe configclients.jsp , dar acest lucru nu este recomandat. Ar putea fi de a lega de o "
+"interfață diferit sau toate interfețele, sau cu handicap, pe configclients.jsp ."
+" "
+
+#: i2p2www/pages/site/faq.html:647
+msgid ""
+"7655: UDP for SAM bridge, a higher level socket API for clients\n"
+"Only opened when a SAM V3 client requests a UDP session.\n"
+"May be enabled/disabled on configclients.jsp.\n"
+"May be changed in the clients.config file with the SAM command line "
+"option sam.udp.port=nnnn."
+msgstr ""
+"7655: UDP pentru pod SAM, un nivel mai ridicat socket API pentru "
+"clienti deschis doar atunci când un client SAM V3 solicită o sesiune "
+"UDP. Poate fi activat / dezactivat pe configclients.jsp . Pot fi modificate în fisierul clients.config cu opțiunea de linie de "
+"comandă SAM sam.udp.port = nnnn. "
+
+#: i2p2www/pages/site/faq.html:655
+msgid ""
+"7656: SAM bridge, a higher level socket API for clients\n"
+"Disabled by default for new installs as of release 0.6.5.\n"
+"May be enabled/disabled on configclients.jsp.\n"
+"May be changed in the clients.config file."
+msgstr ""
+"7656: pod BOB, un nivel mai ridicat socket API pentru clienti "
+"Dezactivat implicit. Poate fi activat / dezactivat pe configclients.jsp . Pot fi modificate în fișierul bob.config. "
+
+#: i2p2www/pages/site/faq.html:663
+msgid ""
+"7657: Your router console\n"
+"May be disabled in the clients.config file.\n"
+"May also be configured to be bound to a specific interface or all "
+"interfaces in that file."
+msgstr ""
+" 7657: consola router poate fi dezactivată în fișierul "
+"clients.config. Poate fi, de asemenea, configurate pentru a fi legat de o"
+" interfață specifică sau toate interfețele în acel fisier. "
+
+#: i2p2www/pages/site/faq.html:670
+msgid ""
+"7658: Your eepsite\n"
+"May be disabled in the clients.config file.\n"
+"May also be configured to be bound to a specific interface or all "
+"interfaces in the jetty.xml file."
+msgstr ""
+" 7658: Eepsite poate fi dezactivată în fișierul "
+"clients.config. Poate fi, de asemenea, configurate pentru a fi legat de o"
+" interfață specifică sau toate interfețele în acel fisier. "
+
+#: i2p2www/pages/site/faq.html:677
+msgid ""
+"7659: Outgoing mail to smtp.postman.i2p\n"
+"May be disabled or changed on the i2ptunnel page in the router "
+"console.\n"
+"May also be configured to be bound to a specific interface or all "
+"interfaces."
+msgstr ""
+"6668: proxy IRC pot fi dezactivate sau modificate pe pagina "
+"i2ptunnel în consola router. Poate fi, de asemenea, configurate pentru a "
+"fi legat de o interfață specifică sau toate interfețele. "
+
+#: i2p2www/pages/site/faq.html:684
+msgid ""
+"7660: Incoming mail from pop.postman.i2p\n"
+"May be disabled or changed on the i2ptunnel page in the router "
+"console.\n"
+"May also be configured to be bound to a specific interface or all "
+"interfaces."
+msgstr ""
+"7659: E-mail primite de la pop.postman.i2p pot fi dezactivate "
+"sau modificate pe pagina i2ptunnel în consola router. Poate fi, de "
+"asemenea, configurate pentru a fi legat de o interfață specifică sau "
+"toate interfețele. "
+
+#: i2p2www/pages/site/faq.html:691
+msgid ""
+"8998: mtn.i2p2.i2p (Monotone - disabled by default)\n"
+"May be disabled or changed on the i2ptunnel page in the router "
+"console.\n"
+"May also be configured to be bound to a specific interface or all "
+"interfaces."
+msgstr ""
+"7659: mtn.i2p2.i2p (Monotone - dezactivată în mod implicit) pot"
+" fi dezactivate sau modificate pe pagina i2ptunnel în consola router. "
+"Poate fi, de asemenea, configurate pentru a fi legat de o interfață "
+"specifică sau toate interfețele. "
+
+#: i2p2www/pages/site/faq.html:698
+msgid ""
+"31000: Local connection to the wrapper control channel port.\n"
+"Outbound to 32000 only, does not listen on this port.\n"
+"Starts at 31000 and will increment until 31999 looking for a free port.\n"
+"To change, see the\n"
+"wrapper documentation.\n"
+"For more information see below."
+msgstr ""
+" 31000: conexiune locală la portul canal de control înveliș. "
+"ieșire la 32000 numai, nu asculta pe acest port. Incepind de la 31000 și "
+"va incrementa până la 31999 în căutarea unui port liber. Pentru a "
+"schimba, consultați "
+"documentația înveliș . Pentru mai multe informații, consultați mai jos . "
+
+#: i2p2www/pages/site/faq.html:708
+msgid ""
+"32000: Local control channel for the service wrapper.\n"
+"To change, see the\n"
+"wrapper documentation.\n"
+"For more information see below."
+msgstr ""
+" 32000: canal de control local pentru ambalajul de servicii. "
+"Pentru a schimba, consultați documentația înveliș . Pentru mai multe informații, "
+"consultați mai jos . "
+
+#: i2p2www/pages/site/faq.html:720
+msgid ""
+"The local I2P ports and the I2PTunnel ports do not need to be reachable "
+"from \n"
+"remote machines, but *should* be reachable locally. You can also create"
+" \n"
+"additional ports for I2PTunnel instances via "
+"http://localhost:7657/i2ptunnel/ \n"
+"(and in turn, would need to get your firewall to allow you local access, "
+"but \n"
+"not remote access, unless desired)."
+msgstr ""
+" porturi locale I2P și porturile I2PTunnel nu trebuie să fie accesibile "
+"de la mașini la distanță, dar *ar trebui să fie accesibile* la nivel "
+"local. Puteți crea, de asemenea, porturi suplimentare pentru cazuri "
+"I2PTunnel prin http://localhost:7657/i2ptunnel/ (și, la rândul său, ar fi"
+" nevoie pentru a obține firewall-ul pentru a vă permite accesul local, "
+"dar nu acces de la distanță, dacă se dorește)."
+
+#: i2p2www/pages/site/faq.html:728
+msgid ""
+"So, to summarize, nothing needs to be reachable by unsolicited remote "
+"peers, but\n"
+"if you can configure your NAT/firewall to allow inbound UDP and TCP the "
+"outbound facing port, you'll"
+"\n"
+"get better performance. You will also need to be able to send outbound "
+"UDP packets\n"
+"to arbitrary remote peers (blocking IPs randomly with something like "
+"PeerGuardian\n"
+"only hurts you - don't do it)."
+msgstr ""
+"Deci, pentru a rezuma, nimic nu trebuie să fie accesibil de parteneri "
+"îndepărtate nesolicitate, dar dacă puteți configura NAT / firewall pentru"
+" a permite intrarea UDP și TCP outbound port de iesire , veți obține o "
+"performanță mai bună. Veți avea nevoie, de asemenea, să fiti în măsură de"
+" a trimite pachete UDP de ieșire cu colegii îndepărtate arbitrare "
+"(blocarea IP-uri la intamplare cu ceva de genul PeerGuardian numai tu "
+"doare - nu fa)."
+
+#: i2p2www/pages/site/faq.html:736
+msgid "Why is I2P listening on port 32000?"
+msgstr "De ce I2P asculta pe portul 32000?"
+
+#: i2p2www/pages/site/faq.html:738
+msgid ""
+"The Tanuki java service wrapper that we use opens this port—bound "
+"to localhost—in order \n"
+"to communicate with software running inside the JVM. When the JVM is "
+"launched it is given a key \n"
+"so it can connect to the wrapper. After the JVM establishes its "
+"connection \n"
+"to the wrapper, the wrapper refuses any additional connections."
+msgstr ""
+"ambalajul serviciu Tanuki java pe care le folosim se deschide acest "
+"port— legat la localhost, în scopul de a comunica cu software-ul "
+"care rulează în interiorul JVM. Când JVM este lansat este data o cheie, "
+"astfel se poate conecta la înveliș. După JVM stabilește conexiunea la "
+"înveliș, învelișul refuză orice conexiuni suplimentare."
+
+#: i2p2www/pages/site/faq.html:744
+msgid ""
+"More information can be found in the \n"
+"wrapper documentation."
+msgstr ""
+"Mai multe informații pot fi găsite în "
+"documentația înveliș ."
+
+#: i2p2www/pages/site/faq.html:751
+msgid ""
+"An I2P router only needs to be seeded once, to join the network for the "
+"first time.\n"
+"Reseeding is nothing more than sending plain HTTP GET requests\n"
+"to fetch a directory listing and download multiple \"routerInfo\" files\n"
+"from a predefined reseed URL."
+msgstr ""
+"Un router I2P trebuie doar să fie seedat o dată, să se alăture rețelei "
+"pentru prima dată. Reseedare este nu mai mult decât trimiterea cererilor "
+"GET HTTP simplu să-i aducă un director listare și descărca mai multe "
+"fișiere \"routerInfo\" de la un URL reseed predefinit."
+
+#: i2p2www/pages/site/faq.html:758
+msgid ""
+"A typical symptom of a failed reseed is the \"Known\" indicator\n"
+"(on the left sidebar of the router console) displaying a very small value"
+"\n"
+"(often less than 5) which does not increase. This can occur, among other "
+"things,\n"
+"if your firewall limits outbound traffic, and blocked the reseed request."
+msgstr ""
+"Un simptom tipic ca reseed nu a reușit este indicatorul \"necunoscut\"(pe"
+" bara laterală stânga a consolei router) afișează o valoare foarte mică "
+"(de multe ori mai puțin de 5), care nu crește. Acest lucru poate avea "
+"loc, printre altele, în cazul în care limitele de firewall la ieșire de "
+"trafic, și a blocat cererea reseed."
+
+#: i2p2www/pages/site/faq.html:765
+msgid "To reseed an I2P router manually, do the following:"
+msgstr "Pentru a reseedui manual un router I2P, efectuați următoarele:"
+
+#: i2p2www/pages/site/faq.html:768
+msgid "Stop your I2P router"
+msgstr "Opri router-ul I2P"
+
+#: i2p2www/pages/site/faq.html:771
+msgid ""
+"Open http://netdb.i2p2.de/ using a "
+"web browser"
+msgstr ""
+"Deschideti http://netdb.i2p2.de/ "
+"folosind web browser"
+
+#: i2p2www/pages/site/faq.html:774
+msgid "Save a dozen \"routerInfo\" files to your I2P \"netDb\" directory"
+msgstr "Salvați zeci de fișiere \"routerInfo\" la \"netDb\" directorul I2P"
+
+#: i2p2www/pages/site/faq.html:781
+msgid "Start your I2P router"
+msgstr "Opriti router-ul I2P"
+
+#: i2p2www/pages/site/faq.html:788
+msgid ""
+"When trying to start the router using \"i2prouter start\", you may see "
+"output like the following:"
+msgstr ""
+"Când încercati de a porni router, folosind \"start i2prouter\", este "
+"posibil să vedeți ieșire, cum ar fi următoarele:"
+
+#: i2p2www/pages/site/faq.html:793
+msgid ""
+"\n"
+"In order to be inclusive and try to ensure that I2P will run on as many "
+"systems \n"
+"as possible, up until I2P 0.8.9 we used a java wrapper \n"
+"compiled for FreeBSD 6.x. If you're receiving this error you most likely "
+"are missing the necessary compatibility libraries.\n"
+"These libraries may be installed by performing the following steps:"
+msgstr ""
+"Pentru a fi inclusiv și să încerce să se asigure că I2P va rula pe cât "
+"posibil mai multe sisteme , până I2P 0.8.9 am folosit un java înveliș compilat"
+" pentru FreeBSD 6.x. Dacă primiți această eroare cel mai probabil lipsesc"
+" bibliotecile de compatibilitate necesare. Aceste biblioteci pot fi "
+"instalate prin executarea următoarelor etape:"
+
+#: i2p2www/pages/site/faq.html:801
+msgid ""
+"Switch to the root user with su or log in as "
+"root."
+msgstr ""
+"Comutați la utilizatorul root cu su sau autentificați-vă "
+"ca root ."
+
+#: i2p2www/pages/site/faq.html:807
+#, python-format
+msgid ""
+"If you cannot install these compatibility libraries (or do not want to), "
+"other\n"
+"possibilities would be to compile the wrapper for your\n"
+"system, starting I2P with the runplain.sh script, or you"
+" can\n"
+"replace the wrapper with one from the source tarball."
+msgstr ""
+"Dacă nu se poate instala aceste biblioteci de compatibilitate (sau nu "
+"doriti), alte posibilități ar fi să compileze înveliș pentru sistemul dvs. , începând I2P cu "
+"runplain.sh script, sau puteți înlocui cu un înveliș din "
+"pachetul cu sursa."
+
+#: i2p2www/pages/site/faq.html:813
+msgid ""
+"For the 0.8.9 release of I2P, the wrapper was upgraded to v3.5.12 and "
+"compiled on systems running FreeBSD 7.2."
+msgstr ""
+"Pentru release 0.8.9 de I2P, ambalajul a fost actualizat la v3.5.12 și "
+"compilate pe sisteme care rulează FreeBSD 7.2."
+
+#: i2p2www/pages/site/faq.html:817
+msgid ""
+"In wrapper.log I see an error that states \"Protocol "
+"family unavailable\" when loading the Router Console"
+msgstr ""
+"În wrapper.log văd o eroare Protocol family "
+"unavailable când se încarcă Consola router"
+
+#: i2p2www/pages/site/faq.html:819
+msgid ""
+"Often this error will occur with any network enabled java software on "
+"some systems that are configured to use IPv6 by default. There are a few "
+"ways to solve this:"
+msgstr ""
+"Adesea, această eroare va avea loc cu orice software java cu rețea "
+"activata pe unele sisteme care sunt configurate pentru a utiliza IPv6 în "
+"mod implicit. Există câteva moduri de a rezolva acest lucru:"
+
+#: i2p2www/pages/site/faq.html:824
+msgid ""
+"On Linux based systems, you can echo 0 > "
+"/proc/sys/net/ipv6/bindv6only"
+msgstr ""
+"Pe sistemele bazate pe Linux, puteți echo 0> / "
+"proc/sys/net/ipv6/bindv6only "
+
+#: i2p2www/pages/site/faq.html:826
+msgid "Look for the following lines in wrapper.config."
+msgstr "Uita-te la următoarele linii în wrapper.config ."
+
+#: i2p2www/pages/site/faq.html:830
+msgid ""
+"If the lines are there, uncomment them by removing the \"#\"s. If the "
+"lines are not there, add them without the \"#\"s."
+msgstr ""
+"În cazul în care liniile sunt acolo, le decomentați prin eliminarea "
+"\"#\". În cazul în care liniile nu sunt acolo, adăugați-le fără \"#\"."
+
+#: i2p2www/pages/site/faq.html:833
+msgid ""
+"Another option would be to remove the ::1 from "
+"~/.i2p/clients.config"
+msgstr ""
+"O altă opțiune ar fi pentru a elimina ::1 de la ~"
+" /.i2p/clients.config "
+
+#: i2p2www/pages/site/faq.html:837
+msgid ""
+"WARNING: For any changes to wrapper.config "
+"to take effect, you must completely\n"
+"stop the router and the wrapper. Clicking Restart on your\n"
+"router console will NOT reread this file! You must\n"
+"click Shutdown, wait 11 minutes, then start I2P."
+msgstr ""
+" AVERTISMENT : Pentru orice modificare a "
+"wrapper.config să aibă efect, trebuie să opriți complet router-"
+"ul și ambalajul. Clic Restart pe consola ta router-ul nu va "
+"reciti acest fisier! Trebuie să faceți clic Shutdown , si sa "
+"asteaptati 11 minute, apoi porniti I2P."
+
+#: i2p2www/pages/site/faq.html:848
+#, python-format
+msgid ""
+"Great! Find us on IRC irc.freenode.net #i2p or post to\n"
+"the forum and we'll post it here (with\n"
+"the answer, hopefully)."
+msgstr ""
+"Grozav! Găsiți-ne pe IRC irc.freenode.net #I2P sau postati pe forum și vom posta aici (cu "
+"răspunsuri, sperăm )."
+
+#: i2p2www/pages/site/impressum.html:4
+msgid "German laws"
+msgstr "legile germane"
+
+#: i2p2www/pages/site/index.html:2
+msgid "I2P Anonymous Network"
+msgstr "I2P rețea anonima"
+
+#: i2p2www/pages/site/index.html:4
+msgid ""
+"Anonymous peer-to-peer distributed communication layer built with open "
+"source tools and designed to run any traditional Internet service such as"
+" email, IRC or web hosting."
+msgstr ""
+"Strat anonim de comunicare peer-to-peer distribuit construit cu "
+"instrumente open source și proiectat pentru a rula orice serviciu "
+"tradițional de Internet, cum ar fi e-mail, IRC sau web hosting."
+
+#: i2p2www/pages/site/index.html:7
+msgid "What does I2P do for you?"
+msgstr "Ce face I2P pentru tine?"
+
+#: i2p2www/pages/site/index.html:8
+msgid ""
+"The I2P network provides strong privacy protections for communication "
+"over the Internet. Many activities that would risk your privacy on the "
+"public Internet can be conducted anonymously inside I2P."
+msgstr ""
+"Rețeaua I2P ofera protectie a confidentialitatii puternice de comunicare "
+"pe Internet. Multe activități care ar risca intimitatea pe internet "
+"publice pot fi efectuate în mod anonim în interiorul I2P."
+
+#: i2p2www/pages/site/index.html:9
+#, python-format
+msgid "Get I2P %(version)s"
+msgstr "Ia I2P %(version)i"
+
+#: i2p2www/pages/site/index.html:13
+msgid "What is I2P?"
+msgstr "Ce este I2P?"
+
+#: i2p2www/pages/site/index.html:15
+msgid ""
+"I2P is an anonymous overlay network - a network within a network. It is "
+"intended to protect communication from dragnet surveillance and "
+"monitoring by third parties such as ISPs.\n"
+msgstr ""
+"I2P este o rețea de acoperire anonim - o rețea într-o rețea. Acesta este "
+"destinat să protejeze comunicare de supraveghere năvod și monitorizarea "
+"de către părtea a treia, cum ar fi furnizorii de servicii Internet."
+
+#: i2p2www/pages/site/index.html:18
+msgid ""
+"I2P is used by many people who care about their privacy: activists, "
+"oppressed people, journalists and whistleblowers, as well as the average "
+"person.\n"
+msgstr ""
+"I2P este folosit de mai multe persoane care au grija de intimitatea lor: "
+"activiști, oameni oprimați, jurnaliști și avertizorii de integritate, "
+"precum și de o persoană obișnuită."
+
+#: i2p2www/pages/site/index.html:21
+msgid ""
+"No network can be \"perfectly anonymous\". The continued goal of I2P is "
+"to make attacks more and more difficult to mount. Its anonymity will get "
+"stronger as the size of the network increases and with ongoing academic "
+"review.\n"
+msgstr ""
+"Nici o rețea nu poate fi \"perfect anonima\". Scopul continuat de I2P "
+"este de a face cit mai multe atacuri și mai greu de montat. Anonimatul "
+"acesteia va deveni mai puternic in timp ce dimensiunea rețelei va crește "
+"și cu revizuirea academica în curs de desfășurare."
+
+#: i2p2www/pages/site/index.html:24
+msgid ""
+"I2P is available on desktops, embedded systems (like the Raspberry Pi) "
+"and Android phones. Help spread the word!\n"
+msgstr ""
+"I2P este disponibil pe desktop-uri, sisteme integrate (cum ar fi "
+"Raspberry Pi) și telefoanele Android. Ajuta la răspândirea!"
+
+#: i2p2www/pages/site/index.html:28
+msgid "Read more…"
+msgstr "Citește mai mult…"
+
+#: i2p2www/pages/site/index.html:33
+msgid "What can you do with I2P?"
+msgstr "Ce se poate face cu I2P?"
+
+#: i2p2www/pages/site/index.html:36
+#, python-format
+msgid ""
+"Email: Integrated web mail interface,"
+" plugin for serverless email."
+msgstr ""
+"Email:Interfață integrată ul web, "
+"plugin pentru e-mail fara server."
+
+#: i2p2www/pages/site/index.html:41
+#, python-format
+msgid ""
+"Web browsing: Anonymous "
+"websites, gateways to and from the public Internet."
+msgstr ""
+"Web browsing:Site-uri anonime,"
+" gateway-uri către cele publice din Internet."
+
+#: i2p2www/pages/site/index.html:46
+#, python-format
+msgid ""
+"Blogging and forums: "
+"Blogging and Syndie plugins."
+msgstr ""
+"Blogging-ul și "
+"forumuri: Blogging-ul și plugin-uri Syndie."
+
+#: i2p2www/pages/site/index.html:51
+#, python-format
+msgid ""
+"Website hosting: Integrated"
+" anonymous web server."
+msgstr ""
+"Website hosting:Server "
+"integrat web anonim."
+
+#: i2p2www/pages/site/index.html:56
+#, python-format
+msgid ""
+"Real-time chat: Instant "
+"messaging and IRC clients."
+msgstr ""
+"Real-time chat:Mesagerie "
+"instant si clientii IRC."
+
+#: i2p2www/pages/site/index.html:61
+#, python-format
+msgid ""
+"File sharing: ED2K and "
+"Gnutella clients, integrated BitTorrent client."
+msgstr ""
+"File sharing:Ed2k și Gnutella "
+"clienti, client BitTorrent integrat ."
+
+#: i2p2www/pages/site/index.html:66
+#, python-format
+msgid ""
+"Decentralized file "
+"storage: Tahoe-LAFS distributed filesystem plugin."
+msgstr ""
+"Stocarea "
+"descentralizata de fișiere: Tahoe-LAFS sistem distribuit de fișiere "
+"plugin."
+
+#: i2p2www/pages/site/index.html:71
+#, python-format
+msgid "More supported applications…"
+msgstr ""
+"Mai multe aplicatii "
+"suportate…"
+
+#: i2p2www/pages/site/index.html:79
+msgid "News & Updates"
+msgstr "Noutati & Actualizari"
+
+#: i2p2www/pages/site/links.html:4
+msgid "Recommended Links & Resources"
+msgstr "Link-uri & Resurse recomandate"
+
+#: i2p2www/pages/site/links.html:5
+#, python-format
+msgid ""
+"See also the page with\n"
+"links to presentations, videos, and tutorials about"
+" I2P."
+msgstr ""
+"A se vedea, de asemenea, pagina cu link-uri la "
+"prezentari, clipuri video, și tutoriale despre I2P . "
+
+#: i2p2www/pages/site/links.html:12
+msgid "I2P on the web"
+msgstr "I2P pe web"
+
+#: i2p2www/pages/site/links.html:20
+msgid "Friends of I2P"
+msgstr "Prietenii I2P"
+
+#: i2p2www/pages/site/links.html:32
+msgid "More Projects and Documentation"
+msgstr "Mai multe proiecte și Documentatie"
+
+#: i2p2www/pages/site/links.html:42
+msgid "Press"
+msgstr "Apasă"
+
+#: i2p2www/pages/site/links.html:46
+msgid "Boards, newssite, others"
+msgstr "Panouri, saituri cu noutati, altele"
+
+#: i2p2www/pages/site/links.html:50
+msgid "Very Old Stuff"
+msgstr ""
+
diff --git a/i2p2www/translations/ro/LC_MESSAGES/research.po b/i2p2www/translations/ro/LC_MESSAGES/research.po
new file mode 100644
index 00000000..408c4adf
--- /dev/null
+++ b/i2p2www/translations/ro/LC_MESSAGES/research.po
@@ -0,0 +1,163 @@
+# Romanian translations for I2P.
+# Copyright (C) 2013 ORGANIZATION
+# This file is distributed under the same license as the I2P project.
+#
+# Translators:
+# polearnik , 2013
+msgid ""
+msgstr ""
+"Project-Id-Version: I2P\n"
+"Report-Msgid-Bugs-To: http://trac.i2p2.de\n"
+"POT-Creation-Date: 2013-11-21 23:32+0000\n"
+"PO-Revision-Date: 2013-12-05 12:55+0000\n"
+"Last-Translator: polearnik \n"
+"Language-Team: Romanian "
+"(http://www.transifex.com/projects/p/I2P/language/ro/)\n"
+"Plural-Forms: nplurals=3; "
+"plural=(n==1?0:(((n%100>19)||((n%100==0)&&(n!=0)))?2:1))\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=utf-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"Generated-By: Babel 0.9.6\n"
+
+#: i2p2www/pages/site/research/index.html:2
+msgid "Academic Research"
+msgstr "Cercetarea academica"
+
+#: i2p2www/pages/site/research/index.html:4
+msgid ""
+"Academic research and analysis of I2P is an important part of ensuring "
+"that the software and network performs as expected and is safe for users "
+"in hostile environments."
+msgstr ""
+"Cercetări și analize a I2P este o parte importantă de a asigura că "
+"software-ul și rețeaua efectuează cum era de așteptat și este sigura "
+"pentru utilizatori în medii ostile."
+
+#: i2p2www/pages/site/research/index.html:8
+#, python-format
+msgid ""
+"\n"
+"There is a large research community investigating a wide range of aspects"
+" of\n"
+"anonymity. For a current and comprehensive list of relevant papers, see "
+"the\n"
+"Free Haven Anonymity Bibliography.\n"
+"I2P benefits from much of the research into Tor and onion routing, but "
+"there is\n"
+"little dedicated research interest into the theory behind I2P, and the "
+"choices\n"
+"and tradeoffs that the network makes. This presents a unique opportunity "
+"for\n"
+"original research.\n"
+msgstr ""
+"Exista o comunitate larga de cercetare ca re investighează o gama larga "
+"de aspecte de anonimitate.Pentru o listă curentă și completă a "
+"documentelor relevante puteti vedeaBibliografie "
+"gratuita adăpostului anonimatBeneficiile I2P reies din cercetările "
+"rețelei Tor și onion-rutarii,dar exista si mici cercetări dedicate "
+"teorie I2P, alegerilor și compromise rețelei "
+
+#: i2p2www/pages/site/research/index.html:18
+#, python-format
+msgid ""
+"A list of known published papers about I2P is available here."
+msgstr ""
+"O listă de lucrări cunoscute publicate despre I2P este disponibilaaici."
+
+#: i2p2www/pages/site/research/index.html:22
+msgid "Testing Attacks on I2P"
+msgstr "Testarea atacurilor pe I2P"
+
+#: i2p2www/pages/site/research/index.html:24
+msgid ""
+"I2P can be run as a separate test network by controlling the locations "
+"that a new router reseeds from so that it only finds other test routers."
+msgstr ""
+"I2P poate fi rulat ca o rețea de testare separată prin controlul "
+"locațiilor pe care router-ul găsește doar alte routere de testare."
+
+#: i2p2www/pages/site/research/index.html:28
+msgid ""
+"The standard mode of operation is to have one JVM per router instance; "
+"hence running multiple copies of I2P on a single machine is inadvisable, "
+"both due to the potential resource drain and the certain port conflicts. "
+"To better facilitate setting up small test networks, I2P has a "
+"multirouter mode which enables multiple distinct routers to be run in the"
+" same JVM."
+msgstr ""
+"Modul standard de funcționare este de a avea un JVM pentru fiecare "
+"instanță router; prin urmare,este recomandabil de difuzat mai multe "
+"copii ale I2P pe o singură mașină , atât din cauza scurgerii de resurse "
+"potențiale și a unor conflicte de port. Pentru a facilita crearea mai "
+"buna de rețele-test mici, I2P are un mod de multirouter care permite mai "
+"multor routere distincte de a fi rulate în aceiași JVM."
+
+#: i2p2www/pages/site/research/index.html:32
+msgid ""
+"MultiRouter can be started from the i2p base directory by running the "
+"below command."
+msgstr ""
+"MultiRouter poate fi pornit de la directorul de baza I2P prin rularea "
+"comenzii de mai jos."
+
+#: i2p2www/pages/site/research/index.html:37
+msgid ""
+"Additionally, I2P can be started in a virtual network mode. This mode "
+"disables all transports, allowing the router to be tested in isolation "
+"without network traffic. To enable this mode, add "
+"i2p.vmCommSystem=true to the router.config before starting."
+msgstr ""
+"În plus, I2P poate fi pornit într-un mod special - rețea virtuală. Acest "
+"mod dezactivează toate transporturile, care permite router-ul să fie "
+"testat în mod izolat, fără trafic din rețea. Pentru a activa acest mod, "
+"adaugati i2p.vmCommSystem = true în router.config înainte "
+"de a începe."
+
+#: i2p2www/pages/site/research/index.html:41
+msgid "Testing the Live I2P Network"
+msgstr "Testarea I2P rețelei Live"
+
+#: i2p2www/pages/site/research/index.html:43
+#, python-format
+msgid ""
+"If you are planning on conducting research on the live I2P network, "
+"please contact us before you commence your "
+"testing. While we do not discourage researchers from responsibly testing "
+"their ideas on the live network, if an attack becomes apparent and we "
+"don't have any line of communication then we will end up taking "
+"countermeasures which could interfere with the test."
+msgstr ""
+"Dacă planificați efectuarea cercetărilor de rețea I2P , vă rugăm să contactați-ne înainte de a începe testarea "
+"sa. In timp ce noi nu descurajam cercetatori de la testarea responsabila "
+"a ideilor lor cu privire la rețeaua de viu, în cazul în care un atac "
+"devine evident și nu avem nici o linie de comunicare, atunci vom sfârși "
+"prin luarea contramăsurilor care ar putea interfera cu testul."
+
+#: i2p2www/pages/site/research/questions.html:2
+msgid "Open research questions"
+msgstr "întrebări de cercetare deschise"
+
+#: i2p2www/pages/site/research/questions.html:4
+msgid "Network database"
+msgstr "Baza de date a rețelei"
+
+#: i2p2www/pages/site/research/questions.html:6
+msgid "Peer selection"
+msgstr "Selectarea partenerului"
+
+#: i2p2www/pages/site/research/questions.html:8
+msgid "Tunnels and Destinations"
+msgstr "Tuneluri și Destinații"
+
+#: i2p2www/pages/site/research/questions.html:10
+msgid "Unidirectional tunnels"
+msgstr "Tuneluri unidirecționale"
+
+#: i2p2www/pages/site/research/questions.html:16
+msgid "Multihoming"
+msgstr "Multihoming"
+
diff --git a/i2p2www/translations/ru_RU/LC_MESSAGES/docs.po b/i2p2www/translations/ru_RU/LC_MESSAGES/docs.po
new file mode 100644
index 00000000..23009632
--- /dev/null
+++ b/i2p2www/translations/ru_RU/LC_MESSAGES/docs.po
@@ -0,0 +1,17134 @@
+# Russian (Russia) translations for I2P.
+# Copyright (C) 2013 ORGANIZATION
+# This file is distributed under the same license as the I2P project.
+#
+# Translators:
+# sassy , 2013
+# TrackIt , 2013
+msgid ""
+msgstr ""
+"Project-Id-Version: I2P\n"
+"Report-Msgid-Bugs-To: http://trac.i2p2.de\n"
+"POT-Creation-Date: 2013-11-27 00:23+0000\n"
+"PO-Revision-Date: 2013-12-06 11:16+0000\n"
+"Last-Translator: sassy \n"
+"Language-Team: Russian (Russia) "
+"(http://www.transifex.com/projects/p/I2P/language/ru_RU/)\n"
+"Plural-Forms: nplurals=3; plural=(n%10==1 && n%100!=11 ? 0 : n%10>=2 && "
+"n%10<=4 && (n%100<10 || n%100>=20) ? 1 : 2)\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=utf-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"Generated-By: Babel 0.9.6\n"
+
+#: i2p2www/pages/site/docs/index.html:2 i2p2www/pages/site/docs/index.html:25
+msgid "Index to Technical Documentation"
+msgstr "Указатель для Технической Документации"
+
+#: i2p2www/pages/site/docs/index.html:3 i2p2www/pages/site/docs/ports.html:3
+#: i2p2www/pages/site/docs/spec/datagrams.html:3
+#: i2p2www/pages/site/docs/spec/geoip.html:3
+#: i2p2www/pages/site/docs/transport/ssu.html:3
+msgid "May 2013"
+msgstr "Май 2013"
+
+#: i2p2www/pages/site/docs/index.html:6
+msgid "How does I2P work"
+msgstr "Как работает I2P"
+
+#: i2p2www/pages/site/docs/index.html:8
+msgid "Following is an index to the technical documentation for I2P."
+msgstr "Далее приведен указатель для технической документации по I2P."
+
+#: i2p2www/pages/site/docs/index.html:12
+msgid ""
+"This index is ordered from the highest to lowest layers.\n"
+"The higher layers are for \"clients\" or applications;\n"
+"the lower layers are inside the router itself.\n"
+"The interface between applications and the router is the I2CP (I2P "
+"Control Protocol) API."
+msgstr ""
+"Указатель упорядочен от высших до низших уровней.\n"
+"Верхние уровни для \"клиентов\" или приложений;\n"
+"нижние уровни для внутренней части маршрутизатора.\n"
+"Интерфейсом между приложениями и маршрутизатором служит I2CP (I2P Control"
+" Protocol) API."
+
+#: i2p2www/pages/site/docs/index.html:19
+#, python-format
+msgid ""
+"The I2P Project is committed to maintaining accurate, current "
+"documentation.\n"
+"If you find any inaccuracies in the documents linked below, please\n"
+"enter a ticket identifying the problem."
+msgstr ""
+
+#: i2p2www/pages/site/docs/index.html:27 i2p2www/pages/site/docs/naming.html:7
+#: i2p2www/pages/site/docs/api/i2ptunnel.html:12
+#: i2p2www/pages/site/docs/api/streaming.html:6
+#: i2p2www/pages/site/docs/how/elgamal-aes.html:6
+#: i2p2www/pages/site/docs/how/network-database.html:6
+#: i2p2www/pages/site/docs/how/peer-selection.html:6
+#: i2p2www/pages/site/docs/how/tech-intro.html:13
+#: i2p2www/pages/site/docs/how/tech-intro.html:97
+#: i2p2www/pages/site/docs/spec/blockfile.html:7
+#: i2p2www/pages/site/docs/spec/configuration.html:6
+#: i2p2www/pages/site/docs/spec/geoip.html:7
+#: i2p2www/pages/site/docs/spec/updates.html:6
+#: i2p2www/pages/site/docs/tunnels/implementation.html:67
+#: i2p2www/pages/site/docs/tunnels/unidirectional.html:6
+msgid "Overview"
+msgstr "Обзор"
+
+#: i2p2www/pages/site/docs/index.html:29
+msgid "Technical Introduction"
+msgstr "Техническое Вступление"
+
+#: i2p2www/pages/site/docs/index.html:30
+msgid "A Less-Technical Introduction"
+msgstr "Менее Техническое Вступление"
+
+#: i2p2www/pages/site/docs/index.html:31
+msgid "Threat model and analysis"
+msgstr "Модель угроз и анализ"
+
+#: i2p2www/pages/site/docs/index.html:32
+msgid "Comparisons to other anonymous networks"
+msgstr "Сравнение с другими анонимными сетями"
+
+#: i2p2www/pages/site/docs/index.html:33
+msgid "Protocol stack chart"
+msgstr "Схема стека протокола"
+
+#: i2p2www/pages/site/docs/index.html:34
+msgid "Papers on I2P"
+msgstr "Статьи о I2P"
+
+#: i2p2www/pages/site/docs/index.html:35
+#, python-format
+msgid ""
+"Invisible Internet Project (I2P) Project Overview"
+" August 28, 2003 (pdf)"
+msgstr ""
+"Обзор Проекта Invisible Internet Project (I2P) "
+"Август 28, 2003 (pdf)"
+
+#: i2p2www/pages/site/docs/index.html:38
+msgid "Application-Layer Topics"
+msgstr "Темы Уровня Приложений"
+
+#: i2p2www/pages/site/docs/index.html:41 i2p2www/pages/site/docs/naming.html:2
+msgid "Naming and Addressbook"
+msgstr "Именование и Адресная Книга"
+
+#: i2p2www/pages/site/docs/index.html:42
+msgid "Plugins Overview"
+msgstr "Обзор Плагинов"
+
+#: i2p2www/pages/site/docs/index.html:43
+msgid "Plugin Specification"
+msgstr "Спецификация Плагина"
+
+#: i2p2www/pages/site/docs/index.html:44
+msgid "Router software updates"
+msgstr "Обновление ПО маршрутизатора"
+
+#: i2p2www/pages/site/docs/index.html:45
+#: i2p2www/pages/site/docs/applications/bittorrent.html:2
+msgid "Bittorrent over I2P"
+msgstr "Bittorrent через I2P"
+
+#: i2p2www/pages/site/docs/index.html:46
+msgid "I2PControl Plugin API"
+msgstr "I2PControl Plugin API"
+
+#: i2p2www/pages/site/docs/index.html:47
+msgid "hostsdb.blockfile Format"
+msgstr "Формат hostsdb.blockfile "
+
+#: i2p2www/pages/site/docs/index.html:48 i2p2www/pages/site/docs/index.html:185
+msgid "Configuration File Format"
+msgstr "Формат Файла Конфигурации"
+
+#: i2p2www/pages/site/docs/index.html:51
+msgid "Application Layer API and Protocols"
+msgstr "API и Протоколы Уровня Приложений"
+
+#: i2p2www/pages/site/docs/index.html:52
+msgid ""
+"High-level, easy-to-use APIs for applications written in any language to "
+"send and receive data."
+msgstr ""
+"Высокоуровневые, доступные API для приложений, написанных на любом языке,"
+" для отправки и получения данных."
+
+#: i2p2www/pages/site/docs/index.html:54
+msgid "Application Development Overview and Guide"
+msgstr "Обзор и Руководство по Разработке Приложений"
+
+#: i2p2www/pages/site/docs/index.html:72
+msgid "SAM Protocol"
+msgstr "Протокол SAM"
+
+#: i2p2www/pages/site/docs/index.html:74
+msgid "SAMv2 Protocol"
+msgstr "Протокол SAMv2"
+
+#: i2p2www/pages/site/docs/index.html:76
+msgid "SAMv3 Protocol"
+msgstr "Протокол SAMv3"
+
+#: i2p2www/pages/site/docs/index.html:78
+msgid "BOB Protocol"
+msgstr "Протокол BOB"
+
+#: i2p2www/pages/site/docs/index.html:81
+msgid "End-to-End Transport API and Protocols"
+msgstr "API и Протоколы Транспорта точка-точка"
+
+#: i2p2www/pages/site/docs/index.html:82
+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/api/streaming.html:2
+msgid "Streaming Library"
+msgstr "Потоковая Библиотека"
+
+#: i2p2www/pages/site/docs/index.html:86
+msgid "Streaming Javadoc"
+msgstr "Javadoc на Потоки"
+
+#: i2p2www/pages/site/docs/index.html:88
+#: i2p2www/pages/site/docs/api/datagrams.html:2
+msgid "Datagrams"
+msgstr "Дейтаграммы"
+
+#: i2p2www/pages/site/docs/index.html:90
+msgid "Datagram Javadoc"
+msgstr "Javadoc по Дейтаграммам"
+
+#: i2p2www/pages/site/docs/index.html:93
+msgid "Client-to-Router Interface API and Protocol"
+msgstr "API и Протокол Интерфейса Клиент-Маршрутизатор"
+
+#: i2p2www/pages/site/docs/index.html:94
+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 ""
+"Низкоуровневый API используется для клиентов (приложений) для отправка и "
+"получения трафика с маршрутизатора.\n"
+"Традиционно используется только Java приложениями и высокоуровневыми API."
+
+#: i2p2www/pages/site/docs/index.html:99
+msgid "I2CP - I2P Control Protocol / API overview"
+msgstr "Обзор I2CP - I2P Control Protocol / API"
+
+#: i2p2www/pages/site/docs/index.html:101
+msgid "I2CP Specification"
+msgstr "Спецификация I2CP"
+
+#: i2p2www/pages/site/docs/index.html:103
+msgid "I2CP API Javadoc"
+msgstr "Javadoc на I2CP API"
+
+#: i2p2www/pages/site/docs/index.html:105
+#: i2p2www/pages/site/docs/index.html:134
+msgid "Common data structures specification"
+msgstr "Спецификация основных структур данных"
+
+#: i2p2www/pages/site/docs/index.html:107
+#: i2p2www/pages/site/docs/index.html:136
+msgid "Data Structures Javadoc"
+msgstr "Javadoc по Структурам Данных"
+
+#: i2p2www/pages/site/docs/index.html:110
+msgid "End-to-End Encryption"
+msgstr "Шифрование из-конца-в-конец"
+
+#: i2p2www/pages/site/docs/index.html:111
+msgid "How client messages are end-to-end encrypted by the router."
+msgstr "Как сообщения клиентов из-конца-в-конец шифруются маршрутизатором"
+
+#: i2p2www/pages/site/docs/index.html:113
+msgid "ElGamal/AES+SessionTag encryption"
+msgstr "Шифрование ElGamal/AES+SessionTag"
+
+#: i2p2www/pages/site/docs/index.html:114
+#: i2p2www/pages/site/docs/index.html:147
+msgid "ElGamal and AES cryptography details"
+msgstr "Подробности криптографии ElGamal и AES"
+
+#: i2p2www/pages/site/docs/index.html:117
+#: 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:118
+msgid ""
+"Distributed storage and retrieval of information about routers and "
+"clients."
+msgstr ""
+"Распределенное хранилище и получение информации о маршрутизаторах и "
+"клиентах."
+
+#: i2p2www/pages/site/docs/index.html:120
+msgid "Network database overview, details, and threat analysis"
+msgstr "Обзор сетевой базы данных, подробности и анализ угроз."
+
+#: i2p2www/pages/site/docs/index.html:121
+msgid "Cryptographic hashes"
+msgstr "Криптографические хеши"
+
+#: i2p2www/pages/site/docs/index.html:122
+msgid "Cryptographic signatures"
+msgstr "Криптографические подписи"
+
+#: i2p2www/pages/site/docs/index.html:125
+msgid "Router Message Protocol"
+msgstr "Протокол Сообщений Маршрутизатора"
+
+#: i2p2www/pages/site/docs/index.html:126
+msgid ""
+"I2P is a message-oriented router. The messages sent between routers are "
+"defined by the I2NP protocol."
+msgstr ""
+"I2P - это маршрутизатор, ориентированный на сообщения. Сообщения "
+"пересылаются между маршрутизаторами и описываются протоколом I2NP."
+
+#: i2p2www/pages/site/docs/index.html:128
+msgid "I2NP - I2P Network Protocol Overview"
+msgstr "I2NP - Обзор I2P Network Protocol"
+
+#: i2p2www/pages/site/docs/index.html:130
+msgid "I2NP Specification"
+msgstr "Спецификация I2NP"
+
+#: i2p2www/pages/site/docs/index.html:132
+msgid "I2NP Javadoc"
+msgstr "Javadoc на I2NP"
+
+#: i2p2www/pages/site/docs/index.html:139
+#: 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:140
+msgid ""
+"Selecting peers, requesting tunnels through those peers, and encrypting "
+"and routing messages through these tunnels."
+msgstr ""
+"Выбор узлов, запрос туннелей через эти узлы, шифрование и маршрутизация "
+"сообщений через эти туннели."
+
+#: i2p2www/pages/site/docs/index.html:142
+msgid "Peer profiling and selection"
+msgstr "Профилирование и выбор узлов"
+
+#: i2p2www/pages/site/docs/index.html:143
+msgid "Tunnel routing overview"
+msgstr "Обзор туннельной маршрутизации"
+
+#: i2p2www/pages/site/docs/index.html:144
+msgid "Garlic routing and \"garlic\" terminology"
+msgstr "Чесночная маршрутизация и \"чесночная\" терминология"
+
+#: i2p2www/pages/site/docs/index.html:145
+msgid "Tunnel building and encryption"
+msgstr "Постройка и шифрование туннелей"
+
+#: i2p2www/pages/site/docs/index.html:146
+msgid "ElGamal/AES"
+msgstr "ElGamal/AES"
+
+#: i2p2www/pages/site/docs/index.html:146
+msgid "for build request encryption"
+msgstr "для шифрования запроса на построение"
+
+#: i2p2www/pages/site/docs/index.html:148
+msgid "Tunnel building specification"
+msgstr "Спецификация построения туннеля"
+
+#: i2p2www/pages/site/docs/index.html:149
+msgid "Low-level tunnel message specification"
+msgstr "Спецификация низкоуровневых туннельных сообщений"
+
+#: i2p2www/pages/site/docs/index.html:150
+#: i2p2www/pages/site/docs/tunnels/unidirectional.html:2
+msgid "Unidirectional Tunnels"
+msgstr "Однонаправленные Туннели"
+
+#: i2p2www/pages/site/docs/index.html:151
+#: 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:152
+msgid "2009 paper (pdf), not current but still generally accurate"
+msgstr "Статья 2009 года (pdf), устаревшие, но в цело все еще точные"
+
+#: i2p2www/pages/site/docs/index.html:155
+msgid "Transport Layer"
+msgstr "Транспортный Уровень"
+
+#: i2p2www/pages/site/docs/index.html:156
+msgid "The protocols for direct (point-to-point) router to router communication."
+msgstr "Протоколы для прямой (точка-точка) связи маршрутизатор-маршрутизатор."
+
+#: i2p2www/pages/site/docs/index.html:158
+msgid "Transport layer overview"
+msgstr "Обзор Транспортного Уровня"
+
+#: i2p2www/pages/site/docs/index.html:160
+msgid "TCP-based transport overview and specification"
+msgstr "Обзор и спецификация транспорта на основе TCP"
+
+#: i2p2www/pages/site/docs/index.html:162
+msgid "UDP-based transport overview"
+msgstr "Обзор транспорта на основе UDP"
+
+#: i2p2www/pages/site/docs/index.html:164
+msgid "SSU specification"
+msgstr "Спецификация SSU"
+
+#: i2p2www/pages/site/docs/index.html:166
+msgid "NTCP transport encryption"
+msgstr "Шифрование транспорта NTCP"
+
+#: i2p2www/pages/site/docs/index.html:168
+msgid "SSU transport encryption"
+msgstr "Шифрование транспорта SSU"
+
+#: i2p2www/pages/site/docs/index.html:170
+msgid "Transport Javadoc"
+msgstr "Javadoc на транспорт"
+
+#: i2p2www/pages/site/docs/index.html:172
+msgid "NTCP Javadoc"
+msgstr "Javadoc на NTCP"
+
+#: i2p2www/pages/site/docs/index.html:174
+msgid "SSU Javadoc"
+msgstr "Javadoc на SSU"
+
+#: i2p2www/pages/site/docs/index.html:177
+msgid "Other Router Topics"
+msgstr "Другие Темы о Маршрутизаторе"
+
+#: i2p2www/pages/site/docs/index.html:179
+msgid "Native BigInteger Library"
+msgstr "Нативная Библиотека BigInteger"
+
+#: i2p2www/pages/site/docs/index.html:181
+msgid "Time synchronization and NTP"
+msgstr "Синхронизация времени и NTP"
+
+#: i2p2www/pages/site/docs/index.html:183
+msgid "Performance"
+msgstr "Производительноть"
+
+#: i2p2www/pages/site/docs/index.html:190
+msgid "Developer's Guides and Resources"
+msgstr "Источники и Руководства Разработчика"
+
+#: i2p2www/pages/site/docs/index.html:192
+msgid "New Developer's Guide"
+msgstr "Руководство для Нового Разработчика"
+
+#: i2p2www/pages/site/docs/index.html:194
+msgid "New Translator's Guide"
+msgstr "Руководство для Нового Переводчика"
+
+#: i2p2www/pages/site/docs/index.html:196
+msgid "Monotone Guide"
+msgstr "Руководство по Monotone"
+
+#: i2p2www/pages/site/docs/index.html:198
+msgid "Developer Guidelines"
+msgstr "Общие Указания по Разработке"
+
+#: i2p2www/pages/site/docs/index.html:200
+msgid "Javadocs on the standard internet:"
+msgstr "Javadocs в обычном интернет:"
+
+#: i2p2www/pages/site/docs/index.html:201
+#: i2p2www/pages/site/docs/index.html:205
+#: i2p2www/pages/site/docs/index.html:206
+#: i2p2www/pages/site/docs/index.html:207
+#, python-format
+msgid "Server %(num)s"
+msgstr "Сервер %(num)s"
+
+#: i2p2www/pages/site/docs/index.html:202
+#: i2p2www/pages/site/docs/index.html:211
+msgid ""
+"Note: always verify that javadocs are current by checking the release "
+"number."
+msgstr ""
+"Примечание: всегда убеждайтесь в том, что все javadoc актуальны, проверяя"
+" номер релиза."
+
+#: i2p2www/pages/site/docs/index.html:204
+msgid "Javadocs inside I2P:"
+msgstr "Javadocs внутри I2P:"
+
+#: i2p2www/pages/site/docs/index.html:213
+msgid "Ports used by I2P"
+msgstr "Порты, используемые I2P:"
+
+#: i2p2www/pages/site/docs/index.html:215
+msgid "Automatic updates to development builds inside I2P"
+msgstr "Автоматическое обновление до тестовых сборок внутри I2P"
+
+#: i2p2www/pages/site/docs/index.html:217
+msgid "Updating the wrapper manually"
+msgstr "Ручное обновление wrapper"
+
+#: i2p2www/pages/site/docs/index.html:219
+msgid "User forum"
+msgstr "Форум пользователей"
+
+#: i2p2www/pages/site/docs/index.html:221
+msgid "Developer forum inside I2P"
+msgstr "Форму разработчиков внутри I2P"
+
+#: i2p2www/pages/site/docs/index.html:223
+msgid "Bug tracker"
+msgstr "Bug tracker"
+
+#: i2p2www/pages/site/docs/index.html:225
+msgid "Viewmtn inside I2P"
+msgstr "Viewmtn внутри I2P"
+
+#: i2p2www/pages/site/docs/index.html:227
+msgid "I2P Source exported to GitHub"
+msgstr "I2P Source экспортированный в GitHub"
+
+#: i2p2www/pages/site/docs/index.html:229
+msgid "I2P Source Git Repo inside I2P"
+msgstr "I2P Source Git Repo внутри I2P"
+
+#: i2p2www/pages/site/docs/index.html:231
+msgid "Source translation at Transifex"
+msgstr "Перевод исходников и Transifex"
+
+#: i2p2www/pages/site/docs/index.html:233
+msgid "Roadmap wiki"
+msgstr "Roadmap wiki"
+
+#: i2p2www/pages/site/docs/index.html:235
+msgid "Old roadmap"
+msgstr "Старый roadmap"
+
+#: i2p2www/pages/site/docs/index.html:235
+#: i2p2www/pages/site/docs/index.html:237
+msgid "not current"
+msgstr "устаревшее"
+
+#: i2p2www/pages/site/docs/index.html:237
+msgid "To Do List"
+msgstr "Список To Do"
+
+#: i2p2www/pages/site/docs/naming.html:3
+msgid "March 2012"
+msgstr "Март 2012"
+
+#: i2p2www/pages/site/docs/naming.html:6
+msgid "Naming in I2P"
+msgstr "Именование в I2P"
+
+#: i2p2www/pages/site/docs/naming.html:9
+msgid ""
+"I2P ships with a generic naming library and a base implementation \n"
+"designed to work off a local name to destination mapping, as well as an\n"
+"add-on application called the addressbook. \n"
+"I2P also supports Base32 hostnames similar to "
+"Tor's .onion addresses."
+msgstr ""
+"I2P поставляется с общей библиотекой именования, основное ее применение \n"
+"рассчитано на отображение локальных имен на пункты назначения, также "
+"поставляется \n"
+"дополнительное приложение addressbook. \n"
+"Также I2P поддерживает Base32 hostnames, похожие "
+"на адреса .onion Tor'а."
+
+#: i2p2www/pages/site/docs/naming.html:16
+msgid ""
+"The addressbook is a web-of-trust\n"
+"driven secure, distributed, and human readable naming system, sacrificing"
+" only\n"
+"the call for all human readable names to be globally unique by mandating "
+"only\n"
+"local uniqueness. While all messages in I2P are cryptographically "
+"addressed\n"
+"by their destination, different people can have local addressbook entries"
+" for\n"
+"\"Alice\" which refer to different destinations. People can still "
+"discover new\n"
+"names by importing published addressbooks of peers specified in their web"
+" of trust,\n"
+"by adding in the entries provided through a third party, or (if some "
+"people organize\n"
+"a series of published addressbooks using a first come first serve "
+"registration\n"
+"system) people can choose to treat these addressbooks as name servers, "
+"emulating\n"
+"traditional DNS."
+msgstr ""
+"\"Адресная книга\" - это сеть доверия, представляющая собой \n"
+"безопасную, распределенную, удобочитаемую систему имен, \n"
+"в которой взамен глобальной уникальности имен гарантируется \n"
+"только локальная уникальность. Не смотря на то что все сообщения в I2P "
+"криптографически адресуются \n"
+"по их пункту назначения, у разных людей могут быть записи в локальной "
+"адресной книге для \n"
+"\"Alice\", указывающие на разные пункты назначения. Также люди могу "
+"узнавать о новых именах, \n"
+"импортируя опубликованные адресные книги узлов, перечисленных в их сети "
+"доверия, \n"
+"добавляя новые записи предоставленные третьей стороной, или (если кто-то "
+"организует \n"
+"серию опубликованных адресных книг, используя систему регистрации первый "
+"пришел первый \n"
+"обслужен) люди могут использовать эти адресные книги в качестве серверов "
+"имен, эмулирующих \n"
+"традиционные DNS."
+
+#: i2p2www/pages/site/docs/naming.html:30
+#, python-format
+msgid ""
+"NOTE: For the reasoning behind the I2P naming system, common arguments "
+"against it\n"
+"and possible alternatives see the naming"
+" discussion\n"
+"page."
+msgstr ""
+"Примечание: Обоснование системы именования I2P, общие доводы против нее \n"
+"и возможные альтернативы вы можете увидеть на странице \n"
+"обсуждения именования"
+
+#: i2p2www/pages/site/docs/naming.html:37
+msgid "Naming System Components"
+msgstr "Компоненты Системы Имен"
+
+#: i2p2www/pages/site/docs/naming.html:39
+msgid ""
+"There is no central naming authority in I2P.\n"
+"All hostnames are local."
+msgstr ""
+"Не существует централизованной системы авторизации имен в I2P.\n"
+"Все имена узлов являются локальными."
+
+#: i2p2www/pages/site/docs/naming.html:44
+msgid ""
+"The naming system is quite simple and most of it is implemented\n"
+"in applications external to the router, but bundled with\n"
+"the I2P distribution.\n"
+"The components are:"
+msgstr ""
+"Система имен довольно проста и большей частью представлена \n"
+"внешними, по отношению к маршрутизатору, приложениями, но поставляющимися"
+" с \n"
+"дистрибутивом I2P.\n"
+"Эти компоненты:"
+
+#: i2p2www/pages/site/docs/naming.html:52
+msgid ""
+"The client application which does local lookups "
+"in hosts.txt\n"
+"and also takes care of the Base32 hostnames."
+msgstr ""
+"Клиентское приложение, выполняющее локальный "
+"поиск по hosts.txt,\n"
+"и обслуживающее Base32 имена узлов."
+
+#: i2p2www/pages/site/docs/naming.html:56
+msgid ""
+"The HTTP proxy which asks the router for "
+"lookups and points\n"
+"the user to remote jump services to assist with failed lookups."
+msgstr ""
+"HTTP proxy, которое запрашивает поиск у "
+"маршрутизатора, и направляет\n"
+"пользователя в службы удаленных переходов в случае ошибок поиска."
+
+#: i2p2www/pages/site/docs/naming.html:60
+msgid ""
+"HTTP host-add forms which allow users to "
+"add hosts to their local hosts.txt"
+msgstr ""
+"HTTP формы добавления узлов, позволяющие "
+"пользователям добавлять узлы в их локальный hosts.txt"
+
+#: i2p2www/pages/site/docs/naming.html:63
+msgid ""
+"HTTP jump services which provide their own"
+" lookups and redirection."
+msgstr ""
+"HTTP службы переходов, предоставляющие "
+"собственный поиск и перенаправление."
+
+#: i2p2www/pages/site/docs/naming.html:66
+msgid ""
+"The addressbook application which merges "
+"external\n"
+"host lists, retrieved via HTTP, with the local list."
+msgstr ""
+"Приложение адресная книга, выполняющая "
+"слияние внешних\n"
+"списков узлов, полученных по HTTP, с локальным списком."
+
+#: i2p2www/pages/site/docs/naming.html:70
+msgid ""
+"The SusiDNS application which is a simple web "
+"front-end\n"
+"for addressbook configuration and viewing of the local host lists."
+msgstr ""
+"Приложение SusiDNS, являющееся простым веб "
+"интерфейсом \n"
+"для настройки адресной книги и просмотра локального списка узлов."
+
+#: i2p2www/pages/site/docs/naming.html:77
+msgid "Naming Files and Lookups"
+msgstr "Файлы Имен и Поиск"
+
+#: i2p2www/pages/site/docs/naming.html:79
+#, python-format
+msgid ""
+"All destinations in I2P are 516-byte (or longer) keys.\n"
+"(To be more precise, it is a 256-byte public key plus a 128-byte signing "
+"key\n"
+"plus a null certificate, which in Base64 representation is 516 bytes.\n"
+"Certificates are not "
+"used now,\n"
+"if they are, the keys will be longer.\n"
+"One possible use of certificates is for proof of work.)"
+msgstr ""
+"Все пункты назначения в I2P - это ключи по 516-байт (или больше). \n"
+"(Если быть более точным, то это публичный ключ 256-байт плюс ключ подписи"
+" 128-байт \n"
+"плюс нулевой сертификат, длина которого в виде Base64 составляет 516 "
+"байт. \n"
+"Сертификаты сейчас не "
+"используются, \n"
+"если будут, то длина ключа будет больше. \n"
+"Сертификаты можно использовать для подтверждения работы.)"
+
+#: i2p2www/pages/site/docs/naming.html:88
+msgid ""
+"If an application (i2ptunnel or the HTTP proxy) wishes to access\n"
+"a destination by name, the router does a very simple local lookup\n"
+"to resolve that name.\n"
+"The client application (technically, the client side of I2CP in the I2P "
+"API)\n"
+"does a linear search through three local files, in order, to\n"
+"look up host names and convert them to a 516-byte destination key:"
+msgstr ""
+"Если приложение (i2ptunnel или HTTP прокси) хочет обратиться к \n"
+"пункту назначения по имени, то маршрутизатор выполняет очень \n"
+"простой локальный поиск для разрешения этого имени. \n"
+"Клиентское приложение (технически, I2CP сторона клиента в I2P API) \n"
+"выполняет последовательный поиск по трем локальным файлам, \n"
+"чтобы найти имя узла и преобразовать его в 516-байт ключа пункта "
+"назначения:"
+
+#: i2p2www/pages/site/docs/naming.html:103
+msgid ""
+"The lookup is case-insensitive.\n"
+"The first match is used, and conflicts are not detected.\n"
+"There is no enforcement of naming rules in lookups."
+msgstr ""
+"Поиск зависит от регистра.\n"
+"Используется первое вхождение, конфликты не обнаруживаются. \n"
+"Нет никаких правил приоритетов именования при поиске."
+
+#: i2p2www/pages/site/docs/naming.html:109
+#, python-format
+msgid ""
+"Lookups are cached for a few minutes.\n"
+"There is an experimental facility for real-time lookups (a la DNS) over "
+"the network within the router,\n"
+"although it is not enabled by default\n"
+"(see \"EepGet\" under Alternatives on the discussion"
+" page)."
+msgstr ""
+"Результаты поиска кешируются на несколько минут. \n"
+"Есть экспериментальная возможность поиска в реальном времени (а ля DNS) "
+"по сети через маршрутизатор, \n"
+"хотя она по умолчанию отключена \n"
+"(смотри \"EepGet\" в разделе Альтернативы на странице "
+"обсуждения)."
+
+#: i2p2www/pages/site/docs/naming.html:116
+msgid "HTTP Proxy"
+msgstr "HTTP Прокси"
+
+#: i2p2www/pages/site/docs/naming.html:118
+msgid ""
+"The HTTP proxy does a lookup via the router for all hostnames ending in "
+"'.i2p'.\n"
+"Otherwise, it forwards the request to a configured HTTP outproxy.\n"
+"Thus, in practice, all HTTP (eepsite) hostnames must end in the pseudo-"
+"Top Level Domain '.i2p'."
+msgstr ""
+"HTTP прокси выполняет поиск через маршрутизатор для всех имен узлов, "
+"заканчивающихся на '.i2p'. \n"
+"Либо перенаправляет запрос на настроенный внешний HTTP прокси. \n"
+"Т.о., на практике, все имена узлов HTTP (eepsite) должны заканчиваться на"
+" псевдо Домен Верхнего Уровня '.i2p'."
+
+#: i2p2www/pages/site/docs/naming.html:124
+msgid ""
+"If the router fails to resolve the hostname, the HTTP proxy returns\n"
+"an error page to the user with links to several \"jump\" services.\n"
+"See below for details."
+msgstr ""
+"Если маршрутизатор не может разрешить имя узла, то HTTP прокси возвращает"
+" \n"
+"пользователю страницу с ошибкой и ссылками на несколько служб "
+"\"переходов\". \n"
+"Подробнее смотри ниже."
+
+#: i2p2www/pages/site/docs/naming.html:130
+#: i2p2www/pages/site/docs/spec/configuration.html:77
+msgid "Addressbook"
+msgstr "Адресная книга"
+
+#: i2p2www/pages/site/docs/naming.html:131
+msgid "Incoming Subscriptions and Merging"
+msgstr "Входящие Подписки и Слияние"
+
+#: i2p2www/pages/site/docs/naming.html:133
+msgid ""
+"The addressbook application periodically\n"
+"retrieves other users' hosts.txt files and merges\n"
+"them with the local hosts.txt, after several checks.\n"
+"Naming conflicts are resolved on a first-come first-served\n"
+"basis."
+msgstr ""
+"Приложение адресной книги периодически \n"
+"запрашивает файлы hosts.txt других пользователей и, после нескольких \n"
+"проверок, производит их слияние с локальным hosts.txt. \n"
+"Конфликты имен разрешаются по принципу первый пришел - \n"
+"первый обслужен."
+
+#: i2p2www/pages/site/docs/naming.html:141
+msgid ""
+"Subscribing to another user's hosts.txt file involves\n"
+"giving them a certain amount of trust.\n"
+"You do not want them, for example, 'hijacking' a new site\n"
+"by quickly entering in their own key for a new site before\n"
+"passing the new host/key entry to you."
+msgstr ""
+"Подписка на файл hosts.txt другого пользователя означает, \n"
+"что мы ему доверяем в этой части отношений.\n"
+"Вы не хотите чтобы он, к примеру, 'взломал' новый сайт, \n"
+"быстро введя свой ключ для нового сайта до того как \n"
+"передать новую пару узел/ключ вам."
+
+#: i2p2www/pages/site/docs/naming.html:149
+msgid ""
+"For this reason, the only subscription configured by\n"
+"default is http://www.i2p2.i2p/hosts.txt,\n"
+"which contains a copy of the hosts.txt included\n"
+"in the I2P release.\n"
+"Users must configure additional subscriptions in their\n"
+"local addressbook application (via subscriptions.txt or SusiDNS)."
+msgstr ""
+"По этой причине единственная подписка, настроенная \n"
+"по умолчанию - это http://www.i2p2.i2p/hosts.txt, \n"
+"она содержит копию hosts.txt, включенного \n"
+"в релиз I2P. \n"
+"Пользователи должны настроить дополнительные подписки в своем \n"
+"локальном приложении адресной книги (в subscriptions.txt или SusiDNS)."
+
+#: i2p2www/pages/site/docs/naming.html:158
+msgid "Some other public addressbook subscription links:"
+msgstr "Ссылки на некоторые другие подписки публичных адресных книг:"
+
+#: i2p2www/pages/site/docs/naming.html:165
+msgid ""
+"The operators of these services may have various policies for listing "
+"hosts.\n"
+"Presence on this list does not imply endorsement."
+msgstr ""
+"У операторов этих служб могут быть различные политики для просмотра "
+"списка узлов. \n"
+"В соответствии с этим, список может быть не ободрен."
+
+#: i2p2www/pages/site/docs/naming.html:170
+#: i2p2www/pages/site/docs/naming.html:182
+msgid "Naming Rules"
+msgstr "Правила Именования"
+
+#: i2p2www/pages/site/docs/naming.html:171
+msgid ""
+"While there are hopefully not any technical limitations within I2P on "
+"host names,\n"
+"the addressbook enforces several restrictions on host names\n"
+"imported from subscriptions.\n"
+"It does this for basic typographical sanity and compatibility with "
+"browsers,\n"
+"and for security.\n"
+"The rules are essentially the same as those in RFC2396 Section 3.2.2.\n"
+"Any hostnames violating these rules may not be propagated\n"
+"to other routers."
+msgstr ""
+"К счастью, нет никаких технических ограничений на имена узлов в I2P, но \n"
+"адресная книга накладывает некоторые ограничения на имена узлов, \n"
+"импортированные из подписок. \n"
+"Это делается для соблюдения основных правил именования, совместимости с "
+"браузерами и \n"
+"с целью безопасности.\n"
+"Эти правила в сущности такие же, как описанные в Разделе 3.2.2 RFC2396. \n"
+"Любые имена узлов, нарушающие эти правила, не должны распространятся \n"
+"на другие маршрутизаторы."
+
+#: i2p2www/pages/site/docs/naming.html:186
+msgid "Names are converted to lower case on import."
+msgstr "При импорте имена приводятся к нижнему регистру."
+
+#: i2p2www/pages/site/docs/naming.html:190
+msgid ""
+"Names are checked for conflict with existing names in the existing "
+"userhosts.txt and hosts.txt\n"
+"(but not privatehosts.txt) after conversion to lower case."
+msgstr ""
+"После приведения к нижнему регистру имена проверяются на конфликты с "
+"имеющимися \n"
+"именами в userhosts.txt и hosts.txt (но не в privatehosts.txt)."
+
+#: i2p2www/pages/site/docs/naming.html:195
+msgid "Must contain only [a-z] [0-9] '.' and '-' after conversion to lower case."
+msgstr ""
+"После приведения к нижнему регистру должны содержать только [a-z] [0-9] "
+"'.' и '-'."
+
+#: i2p2www/pages/site/docs/naming.html:199
+msgid "Must not start with '.' or '-'."
+msgstr "Не должны начинаться с '.' или '-'."
+
+#: i2p2www/pages/site/docs/naming.html:203
+msgid "Must end with '.i2p'."
+msgstr "Должны оканчиваться на '.i2p'."
+
+#: i2p2www/pages/site/docs/naming.html:207
+msgid "67 characters maximum, including the '.i2p'."
+msgstr "Максимум 67 символов, включая '.i2p'."
+
+#: i2p2www/pages/site/docs/naming.html:211
+msgid "Must not contain '..'."
+msgstr "Не должны содержать '..'."
+
+#: i2p2www/pages/site/docs/naming.html:215
+msgid "Must not contain '.-' or '-.' (as of 0.6.1.33)."
+msgstr "Не должны содержать '.-' или '-.' (как в 0.6.1.33)."
+
+#: i2p2www/pages/site/docs/naming.html:219
+msgid "Must not contain '--' except in 'xn--' for IDN."
+msgstr "Не должны содержать '--', исключение - 'xn--' для IDN."
+
+#: i2p2www/pages/site/docs/naming.html:223
+msgid "Base32 hostnames (*.b32.i2p) are not allowed."
+msgstr "Base32 имена узлов (*.b32.i2p) не допускаются."
+
+#: i2p2www/pages/site/docs/naming.html:227
+msgid ""
+"Certain hostnames reserved for project use are not allowed\n"
+"(proxy.i2p, router.i2p, console.i2p, *.proxy.i2p, *.router.i2p, "
+"*.console.i2p, and others)"
+msgstr ""
+"Определенные имена узлов, зарезервированые для использования проектом, не"
+" допускаются \n"
+"(proxy.i2p, router.i2p, console.i2p, *.proxy.i2p, *.router.i2p, "
+"*.console.i2p, и другие)"
+
+#: i2p2www/pages/site/docs/naming.html:232
+msgid "Keys are checked for base64 validity."
+msgstr "Ключи проверяются на соответствие base64."
+
+#: i2p2www/pages/site/docs/naming.html:236
+msgid ""
+"Keys are checked for conflict with existing keys in hosts.txt (but not "
+"privatehosts.txt)."
+msgstr ""
+"Ключи проверяются на конфликты с существующими ключами в hosts.txt (но не"
+" в privatehosts.txt)."
+
+#: i2p2www/pages/site/docs/naming.html:240
+msgid "Minimum key length 516 bytes."
+msgstr "Минимальный размер ключа 516 байт."
+
+#: i2p2www/pages/site/docs/naming.html:244
+msgid "Maximum key length 616 bytes (to account for certs up to 100 bytes)."
+msgstr "Максимальный размер ключа 616 байт (для нужд сертификатов до 100 байт)."
+
+#: i2p2www/pages/site/docs/naming.html:249
+msgid ""
+"Any name received via subscription that passes all the checks is added to"
+" the local hosts.txt."
+msgstr ""
+"Каждое имя, полученное по подписке и прошедшее все проверки, добавляется "
+"в локальный hosts.txt."
+
+#: i2p2www/pages/site/docs/naming.html:253
+msgid ""
+"Note that the '.' symbols in a host name are of no significance,\n"
+"and do not denote any actual naming or trust hierarchy.\n"
+"If the name 'host.i2p' already exists, there is nothing\n"
+"to prevent anybody from adding a name 'a.host.i2p' to their hosts.txt,\n"
+"and this name can be imported by others' addressbook.\n"
+"Methods to deny subdomains to non-domain 'owners' (certificates?),\n"
+"and the desirability and feasibility of these methods,\n"
+"are topics for future discussion."
+msgstr ""
+"Учтите, что символ '.' в имени узла не имеет особого смысла, \n"
+"И не говорит о фактической иерархии имен или доверия. \n"
+"Если имя 'host.i2p' уже существует, ничто не мешает \n"
+"кому-нибудь добавить имя 'a.host.i2p' в свой hosts.txt, \n"
+"и это имя может быть импортировано в другие адресные книги. \n"
+"Методы запрета заведения субдоменов не \"владельцами\" домена "
+"(сертификата?), \n"
+"целесообразность и осуществимость этих методов это \n"
+"предмет для будущих обсуждений."
+
+#: i2p2www/pages/site/docs/naming.html:264
+msgid ""
+"International Domain Names (IDN) also work in i2p (using punycode 'xn--' "
+"form).\n"
+"To see IDN .i2p domain names rendered correctly in Firefox's location "
+"bar,\n"
+"add 'network.IDN.whitelist.i2p (boolean) = true' in about:config."
+msgstr ""
+"Также в I2P работают интернационализованные доменные имена (IDN) "
+"(используя форму punycode 'xn--').\n"
+"Чтобы IDN имена домена .i2p корректно отображались в адресной строке "
+"Firefox,\n"
+"добавьте 'network.IDN.whitelist.i2p (boolean) = true' в about:config."
+
+#: i2p2www/pages/site/docs/naming.html:270
+msgid ""
+"As the addressbook application does not use privatehosts.txt at all, in "
+"practice\n"
+"this file is the only place where it is appropriate to place private "
+"aliases or\n"
+"\"pet names\" for sites already in hosts.txt."
+msgstr ""
+"Поскольку приложение адресной книги совсем не использует "
+"privatehosts.txt, то на практике \n"
+"этот файл - единственно верное место, куда стоит поместить личные "
+"синонимы или \n"
+"\"клички\" для сайтов, которые уже есть в hosts.txt."
+
+#: i2p2www/pages/site/docs/naming.html:276
+msgid "Outgoing Subscriptions"
+msgstr "Исходящие Подписки"
+
+#: i2p2www/pages/site/docs/naming.html:277
+msgid ""
+"Addressbook will publish the merged hosts.txt to a location\n"
+"(traditionally hosts.txt in the local eepsite's home directory) to be "
+"accessed by others\n"
+"for their subscriptions.\n"
+"This step is optional and is disabled by default."
+msgstr ""
+"Адресная книга публикует объединенный hosts.txt с местоположении \n"
+"(традиционно это hosts.txt в домашней директории локального eepsite), "
+"доступном другим \n"
+"по их подпискам. \n"
+"Этот шаг необязателен и по умолчанию отключен."
+
+#: i2p2www/pages/site/docs/naming.html:285
+msgid ""
+"The addressbook application, together with eepget, saves the Etag and/or "
+"Last-Modified\n"
+"information returned by the web server of the subscription.\n"
+"This greatly reduces the bandwidth required, as the web server will\n"
+"return a '304 Not Modified' on the next fetch if nothing has changed."
+msgstr ""
+"Приложение адресной книги, совместно с eepget, сохраняет Etag и/или "
+"информацию о \n"
+"последнем изменении, полученную веб сервером по подписке. \n"
+"Это существенно снижает требования к полосе пропускания, т.к. веб сервер"
+" \n"
+"вернет '304 Not Modified' при следующем получении, если изменений не было."
+
+#: i2p2www/pages/site/docs/naming.html:292
+msgid ""
+"However the entire hosts.txt is downloaded if it has changed.\n"
+"See below for discussion on this issue."
+msgstr ""
+"Тем не менее, содержимое hosts.txt загружается, если он был изменен. \n"
+"Обсуждение этой темы смотри ниже."
+
+#: i2p2www/pages/site/docs/naming.html:297
+msgid ""
+"Hosts serving a static hosts.txt or an equivalent CGI application\n"
+"are strongly encouraged to deliver\n"
+"a Content-Length header, and either an Etag or Last-Modified header.\n"
+"Also ensure that the server delivers a '304 Not Modified' when "
+"appropriate.\n"
+"This will dramatically reduce the network bandwidth, and\n"
+"reduce chances of corruption."
+msgstr ""
+"Узлу, обслуживающему статичный hosts.txt, или эквивалентному приложению "
+"CGI \n"
+"настоятельно рекомендуется отправлять \n"
+"заголовок Content-Length, либо Etag или заголовок Last-Modified. \n"
+"Убедитесь также, что сервер по необходимости выдает '304 Not Modified'. \n"
+"Это существенно уменьшить пропускную способность сети, и \n"
+"уменьшит вероятность повреждения."
+
+#: i2p2www/pages/site/docs/naming.html:306
+msgid "Host Add Services"
+msgstr "Службы Добавления Узла"
+
+#: i2p2www/pages/site/docs/naming.html:307
+msgid ""
+"A host add service is a simple CGI application that takes a hostname and "
+"a Base64 key as parameters\n"
+"and adds that to its local hosts.txt.\n"
+"If other routers subscribe to that hosts.txt, the new hostname/key\n"
+"will be propagated through the network."
+msgstr ""
+"Служба добавления узла это простое приложение CGI, которое принимает имя "
+"узла и Base64 ключ в качестве параметров, \n"
+"и добавляет их в локальный hosts.txt. \n"
+"Если другие маршрутизаторы подписаны на этот hosts.txt, то новая пара имя"
+" узла/ключ \n"
+"будет передана по сети."
+
+#: i2p2www/pages/site/docs/naming.html:314
+msgid ""
+"It is recommended that host add services impose, at a minimum, the "
+"restrictions imposed by the addressbook application listed above.\n"
+"Host add services may impose additional restrictions on hostnames and "
+"keys, for example:"
+msgstr ""
+"На службу добавления узла, как минимум, рекомендуется наложить "
+"ограничения, совпадающие с ограничениями \n"
+"приложения адресной книги, описанными выше. \n"
+"На службу добавления узла могут быть наложены дополнительные ограничения "
+"на имя узла и ключ, например:"
+
+#: i2p2www/pages/site/docs/naming.html:319
+msgid "A limit on number of 'subdomains'."
+msgstr "Ограничение количества 'поддоменов'."
+
+#: i2p2www/pages/site/docs/naming.html:323
+msgid "Authorization for 'subdomains' through various methods."
+msgstr "Различные методы авторизации для 'поддоменов'."
+
+#: i2p2www/pages/site/docs/naming.html:327
+msgid "Hashcash or signed certificates."
+msgstr "Hashcash или подписанные сертификаты."
+
+#: i2p2www/pages/site/docs/naming.html:331
+msgid "Editorial review of host names and/or content."
+msgstr "Экспертная оценка имен узлов и/или содержимого."
+
+#: i2p2www/pages/site/docs/naming.html:335
+msgid "Categorization of hosts by content."
+msgstr "Категоризация узлов по содержимому."
+
+#: i2p2www/pages/site/docs/naming.html:339
+msgid "Reservation or rejection of certain host names."
+msgstr "Резервирование или исключение определенных имен узлов."
+
+#: i2p2www/pages/site/docs/naming.html:343
+msgid "Restrictions on the number of names registered in a given time period."
+msgstr "Ограничение количества имен регистрируемых за определенный период времени."
+
+#: i2p2www/pages/site/docs/naming.html:347
+msgid "Delays between registration and publication."
+msgstr "Задержка между регистрацией и публикацией."
+
+#: i2p2www/pages/site/docs/naming.html:351
+msgid "Requirement that the host be up for verification."
+msgstr "Необходимость доступности узла для его верификации."
+
+#: i2p2www/pages/site/docs/naming.html:355
+msgid "Expiration and/or revocation."
+msgstr "Истечение срока и/или аннулирование."
+
+#: i2p2www/pages/site/docs/naming.html:359
+msgid "IDN spoof rejection."
+msgstr "Предотвращение IDN-спуфинга."
+
+#: i2p2www/pages/site/docs/naming.html:364
+msgid "Jump Services"
+msgstr "Службы перехода"
+
+#: i2p2www/pages/site/docs/naming.html:365
+msgid ""
+"A jump service is a simple CGI application that takes a hostname as a "
+"parameter\n"
+"and returns a 301 redirect to the proper URL with a "
+"?i2paddresshelper=key\n"
+"string appended.\n"
+"The HTTP proxy will interpret the appended string and\n"
+"use that key as the actual destination.\n"
+"In addition, the proxy will cache that key so the\n"
+"address helper is not necessary until restart."
+msgstr ""
+"Служба перехода это простое CGI приложение, которое получает имя узла в "
+"качестве параметра, \n"
+"и возвращает перенаправление 301 на правильный URL с добавлением строки \n"
+"?i2paddresshelper=key. \n"
+"HTTP прокси интерпретирует добавленную строку и \n"
+"использует этот ключ как актуальный пункт назначения. \n"
+"Кроме того, прокси кеширует этот ключ, так что \n"
+"address helper не нужен до перезапуска."
+
+#: i2p2www/pages/site/docs/naming.html:375
+msgid ""
+"Note that, like with subscriptions, using a jump service\n"
+"implies a certain amount of trust, as a jump service could maliciously\n"
+"redirect a user to an incorrect destination."
+msgstr ""
+"Учтите, что как и с подписками, использование службы перехода \n"
+"требует части доверия, так как служба перехода может злонамеренно \n"
+"перенаправить пользователя в некорректный пункт назначения."
+
+#: i2p2www/pages/site/docs/naming.html:381
+msgid ""
+"To provide the best service, a jump service should be subscribed to\n"
+"several hosts.txt providers so that its local host list is current."
+msgstr ""
+"Для предоставления лучшего уровня сервиса служба перехода должна быть "
+"подписана на \n"
+"несколько провайдеров hosts.txt, т.о. локальный список узлов будет "
+"актуальным."
+
+#: i2p2www/pages/site/docs/naming.html:387
+msgid ""
+"SusiDNS is simply a web interface front-end to configuring addressbook "
+"subscriptions\n"
+"and accessing the four addressbook files.\n"
+"All the real work is done by the 'addressbook' application."
+msgstr ""
+"SusiDNS это просто веб-интерфейс для настройки подписок адресной книги\n"
+"и для доступа к четырем ее файлам. \n"
+"Вся настоящая работа выполняется приложением 'адресная книга'."
+
+#: i2p2www/pages/site/docs/naming.html:393
+msgid ""
+"Currently, there is little enforcement of addressbook naming rules within"
+" SusiDNS,\n"
+"so a user may enter hostnames locally that would be rejected by\n"
+"the addressbook subscription rules."
+msgstr ""
+"На данный момент в SusiDNS реализовано мало правил ограничения именования"
+" адресной книги, \n"
+"так что пользователь может локально ввести имя узла, которое будет "
+"отвергнуто \n"
+"в соответствии с правилами подписки адресной книги."
+
+#: i2p2www/pages/site/docs/naming.html:399
+msgid "Base32 Names"
+msgstr "Base32 Имена"
+
+#: i2p2www/pages/site/docs/naming.html:400
+msgid ""
+"I2P supports Base32 hostnames similar to Tor's .onion addresses.\n"
+"Base32 addresses are much shorter and easier to handle than the\n"
+"full 516-character Base64 Destinations or addresshelpers.\n"
+"Example: "
+"ukeu3k5oycgaauneqgtnvselmt4yemvoilkln7jpvamvfx7dnkdq.b32.i2p"
+msgstr ""
+"I2P поддерживает Base32 имена узлов по аналогии с .onion адресами Tor. \n"
+"Base32 адреса гораздо короче и их проще обрабатывать, чем \n"
+"полные 516-символьные Base64 пункты назначения или addresshelper-ы. \n"
+"Пример: "
+"ukeu3k5oycgaauneqgtnvselmt4yemvoilkln7jpvamvfx7dnkdq.b32.i2p"
+
+#: i2p2www/pages/site/docs/naming.html:407
+msgid ""
+"In Tor, the address is 16 characters (80 bits), or half of the SHA-1 "
+"hash.\n"
+"I2P uses 52 characters (256 bits) to represent the full SHA-256 hash.\n"
+"The form is {52 chars}.b32.i2p.\n"
+"Base32 is implemented in the naming service, which queries the\n"
+"router over I2CP to lookup the LeaseSet to get the full Destination.\n"
+"Base32 lookups will only be successful when the Destination is up and "
+"publishing\n"
+"a LeaseSet.\n"
+"Because resolution may require a network database lookup, it may take "
+"significantly\n"
+"longer than a local address book lookup."
+msgstr ""
+"В Tor - адрес это 16 символов (80 бит), или половина хеша SHA-1. \n"
+"I2P использует 52 символа (256 бит) для представления полного хеша "
+"SHA-256. \n"
+"В форме {52 символа}.b32.i2p. \n"
+"Base32 реализовано в службе имен, которая опрашивает \n"
+"маршрутизатор через I2CP для поиска LeaseSet, чтобы получить полный адрес"
+" пункта назначения. \n"
+"Поиск Base32 будет успешен только в том случае, если пункт назначения "
+"доступен и опубликовал \n"
+"LeaseSet. \n"
+"Из-за того что для разрешения имени может потребоваться поиск в сетевой "
+"базе данных, это может занять \n"
+"гораздо больше времени, чем локальный поиск по адресной книге."
+
+#: i2p2www/pages/site/docs/naming.html:419
+msgid ""
+"Base32 addresses can be used in most places where hostnames or full "
+"destinations\n"
+"are used, however there are some exceptions where they may fail if the\n"
+"name does not immediately resolve. I2PTunnel will fail, for example, if\n"
+"the name does not resolve to a destination."
+msgstr ""
+"Base32 адреса могут быть использованы в большинстве случаев, где "
+"используются имена узлов \n"
+"или полные пункты назначения, тем не менее есть несколько исключений, "
+"когда это может вызвать ошибку, если \n"
+"имя не может быть преобразовано в адрес. Например, в I2PTunnel возникнет "
+"ошибка, если \n"
+"имя не разрешается в пункт назначения."
+
+#: i2p2www/pages/site/docs/plugins.html:2
+#: i2p2www/pages/site/docs/spec/configuration.html:65
+msgid "Plugins"
+msgstr "Плагины"
+
+#: i2p2www/pages/site/docs/plugins.html:3
+msgid "June 2012"
+msgstr "Июни 2012"
+
+#: i2p2www/pages/site/docs/plugins.html:6
+msgid "I2P Plugins"
+msgstr "Плагины I2P"
+
+#: i2p2www/pages/site/docs/plugins.html:8
+msgid "General Information"
+msgstr "Основная информация"
+
+#: i2p2www/pages/site/docs/plugins.html:9
+msgid ""
+"I2P includes a plugin architecture\n"
+"to support easy development and installation of additional software."
+msgstr ""
+"В I2P имеется архитектура плагинов \n"
+"для поддержки легкой разработки и установки дополнительного ПО."
+
+#: i2p2www/pages/site/docs/plugins.html:14
+msgid ""
+"There are now plugins available that support distributed email, blogs, "
+"IRC\n"
+"clients, distributed file storage, wikis, and more."
+msgstr ""
+"Уже сейчас доступны плагины с поддержкой распределенной электронной "
+"почты, блогов, \n"
+"клиентов IRC, распределенного хранилища файлов, wiki и др."
+
+#: i2p2www/pages/site/docs/plugins.html:19
+msgid "Benefits to i2p users and app developers:"
+msgstr "Преимущества для пользователей I2P и разработчиков ПО:"
+
+#: i2p2www/pages/site/docs/plugins.html:24
+msgid "Easy distribution of applications"
+msgstr "Простое распространение приложений"
+
+#: i2p2www/pages/site/docs/plugins.html:28
+msgid ""
+"Allows innovation and use of additional libraries without worrying about\n"
+"increasing the size of i2pupdate.sud"
+msgstr ""
+"Позволяет использовать инновации и дополнительные библиотеки, не "
+"беспокоясь об \n"
+"увеличении размера i2pupdate.sud"
+
+#: i2p2www/pages/site/docs/plugins.html:33
+msgid ""
+"Support large or special-purpose applications that would never be bundled"
+"\n"
+"with the I2P installation"
+msgstr ""
+"Поддержка больших или специализированных приложений, которые никогда не "
+"будут связаны \n"
+"с установкой I2P"
+
+#: i2p2www/pages/site/docs/plugins.html:38
+msgid "Cryptographically signed and verified applications"
+msgstr "Криптографически подписанные и проверенные приложения"
+
+#: i2p2www/pages/site/docs/plugins.html:42
+msgid "Automatic updates of applications, just like for the router"
+msgstr "Автоматическое обновление приложений, совсем как для маршрутизатора"
+
+#: i2p2www/pages/site/docs/plugins.html:46
+msgid ""
+"Separate initial install and update packages, if desired, for smaller "
+"update downloads"
+msgstr ""
+"Отдельные начальная установка и пакеты обновлений, по желанию, для "
+"уменьшения размера загружаемых обновлений"
+
+#: i2p2www/pages/site/docs/plugins.html:50
+msgid ""
+"One-click installation of applications. No more asking users to modify\n"
+"wrapper.config or clients.config"
+msgstr ""
+"Установка приложений в один клик. Не спрашивая пользователей об изменении"
+" \n"
+"wrapper.config или clients.config"
+
+#: i2p2www/pages/site/docs/plugins.html:55
+msgid "Isolate applications from the base $I2P installation"
+msgstr "Изолирование приложений от базовой установки $I2P"
+
+#: i2p2www/pages/site/docs/plugins.html:59
+msgid ""
+"Automatic compatibility checking for I2P version, Java version, Jetty\n"
+"version, and previous installed application version"
+msgstr ""
+"Автоматическая проверка совместимости с версией I2P, Java, Jetty \n"
+"и предыдущей установленной версией приложения"
+
+#: i2p2www/pages/site/docs/plugins.html:64
+msgid "Automatic link addition in console"
+msgstr "Автоматическое добавление ссылки в консоли"
+
+#: i2p2www/pages/site/docs/plugins.html:68
+msgid ""
+"Automatic startup of application, including modifying classpath, without "
+"requiring a restart"
+msgstr ""
+"Автоматический запуск приложения, включая модификацию classpath без "
+"необходимости перезапуска"
+
+#: i2p2www/pages/site/docs/plugins.html:72
+msgid "Automatic integration and startup of webapps into console Jetty instance"
+msgstr ""
+"Автоматическая интеграция и запуск веб-приложения в консольном экземпляре"
+" Jetty"
+
+#: i2p2www/pages/site/docs/plugins.html:76
+#, python-format
+msgid ""
+"Facilitate creation of 'app stores' like the one at\n"
+"%(pluginsite)s"
+msgstr ""
+"Облегченное создание 'app stores', как для \n"
+"%(pluginsite)s"
+
+#: i2p2www/pages/site/docs/plugins.html:81
+msgid "One-click uninstall"
+msgstr "Удаление в один клик"
+
+#: i2p2www/pages/site/docs/plugins.html:85
+msgid "Language and theme packs for the console"
+msgstr "Языковые пакеты и темы для консоли"
+
+#: i2p2www/pages/site/docs/plugins.html:89
+msgid "Bring detailed application information to the router console"
+msgstr "Вывод детализированной информации от приложения в консоль маршрутизатора"
+
+#: i2p2www/pages/site/docs/plugins.html:93
+msgid "Non-java applications also supported"
+msgstr "Также поддерживаются не-Java приложения"
+
+#: i2p2www/pages/site/docs/plugins.html:99
+msgid "Required I2P version"
+msgstr "Требуемая версия I2P"
+
+#: i2p2www/pages/site/docs/plugins.html:100
+msgid "0.7.12 or newer."
+msgstr "0.7.12 или новее."
+
+#: i2p2www/pages/site/docs/plugins.html:102
+msgid "Installation"
+msgstr "Установка"
+
+#: i2p2www/pages/site/docs/plugins.html:103
+msgid ""
+"To install and start a plugin, copy the .xpi2p install link "
+"to\n"
+"the form at the bottom of\n"
+"configclients.jsp"
+" in\n"
+"your router console and click the \"install plugin\" button. After a"
+"\n"
+"plugin is installed and started, a link to the plugin will usually appear"
+" at\n"
+"the top of your summary bar."
+msgstr ""
+"Чтобы установить и запустить плагин, скопируйте ссылку на установщик "
+".xpi2p в \n"
+"форму внизу \n"
+"configclients.jsp"
+" в \n"
+"консоли вашего маршрутизатора и нажмите кнопку \"install plugin\". "
+"После \n"
+"установки и запуска плагина ссылка на него обычно появляется вверху \n"
+"вашей строки состояния."
+
+#: i2p2www/pages/site/docs/plugins.html:112
+msgid ""
+"To update a plugin to the latest version, just click the update button on"
+"\n"
+"configclients.jsp."
+"\n"
+"There is also a button to check if the plugin has a more recent version, "
+"as\n"
+"well as a button to check for updates for all plugins. Plugins will be "
+"checked\n"
+"for updates automatically when updating to a new I2P release (not "
+"including dev\n"
+"builds)."
+msgstr ""
+"Чтобы обновить плагин до последней версии, просто нажмите кнопку "
+"обновления в \n"
+"configclients.jsp."
+" \n"
+"Также есть кнопка для проверки актуальности версии плагина, как и \n"
+"кнопка проверки наличия обновления для плагина. Проверка наличия "
+"обновлений для\n"
+"плагинов будет выполнена при обновлении I2P до нового релиза (за "
+"исключением \n"
+"тестовых сборок)."
+
+#: i2p2www/pages/site/docs/plugins.html:122
+msgid "Development"
+msgstr "Разработка"
+
+#: i2p2www/pages/site/docs/plugins.html:123
+#, python-format
+msgid ""
+"See the latest plugin specification and "
+"the\n"
+"plugin forum on %(zzz)s."
+msgstr ""
+"Смотри актуальную спецификацию плагинов и\n"
+"форум о плагинах на %(zzz)s."
+
+#: i2p2www/pages/site/docs/plugins.html:128
+#, python-format
+msgid ""
+"See also the sources for plugins developed by various people. Some "
+"plugins, such\n"
+"as snowman, were "
+"developed\n"
+"specifically as examples."
+msgstr ""
+"Также смотри исходники плагинов, разработанных другими людьми. Некоторые "
+"плагины, такие\n"
+"как snowman, были "
+"разработаны\n"
+"специально в качестве примеров."
+
+#: i2p2www/pages/site/docs/plugins.html:134
+msgid ""
+"Developers wanted! Plugins are a great way to learn more about I2P"
+"\n"
+"or easily add some feature."
+msgstr ""
+"Разыскиваются разработчики! Плагины это замечательная возможность "
+"узнать больше о I2P,\n"
+"или легко добавить новую возможность."
+
+#: i2p2www/pages/site/docs/plugins.html:139
+msgid "Getting Started"
+msgstr "С чего начать"
+
+#: i2p2www/pages/site/docs/plugins.html:140
+#, python-format
+msgid ""
+"To create a plugin from an existing binary package you will need to get\n"
+"makeplugin.sh from the i2p.scripts branch in "
+"monotone."
+msgstr ""
+"Чтобы сделать плагин из имеющегося исполняемого пакета вам понадобится \n"
+"makeplugin.sh из ветки i2p.scripts в monotone."
+
+#: i2p2www/pages/site/docs/plugins.html:146
+msgid "Known Issues"
+msgstr "Известные проблемы"
+
+#: i2p2www/pages/site/docs/plugins.html:147
+msgid ""
+"Note that the router's plugin architecture does NOT currently\n"
+"provide any additional security isolation or sandboxing of plugins."
+msgstr ""
+"Учтите, что архитектура плагинов маршрутизатора на данный момент "
+"НЕ \n"
+"предоставляет дополнительную изоляцию безопасности или запуск плагинов в "
+"песочнице."
+
+#: i2p2www/pages/site/docs/plugins.html:153
+msgid ""
+"Updates of a plugin with included jars (not wars) won't be recognized if\n"
+"the plugin was already run, as it requires class loader trickery to flush"
+" the\n"
+"class cache; a full router restart is required."
+msgstr ""
+"Обновление плагина с jar-файлами (но не war) не будет распознано, если \n"
+"плагин уже запущен, т.к. для этого требуется, чтобы загрузчик классов "
+"сбросил \n"
+"кэш классов; необходим полный перезапуск маршрутизатора."
+
+#: i2p2www/pages/site/docs/plugins.html:159
+msgid "The stop button may be displayed even if there is nothing to stop."
+msgstr "Кнопка остановки может отображаться, даже если останавливать нечего."
+
+#: i2p2www/pages/site/docs/plugins.html:163
+msgid ""
+"Plugins running in a separate JVM create a logs/ directory "
+"in\n"
+"$CWD."
+msgstr ""
+"Плагины, запущенные в отдельном JVM, создают директорию "
+"logs/ в \n"
+"$CWD."
+
+#: i2p2www/pages/site/docs/plugins.html:168
+msgid ""
+"No initial keys are present, except for those of jrandom and zzz (using "
+"the\n"
+"same keys as for router update), so the first key seen for a signer is\n"
+"automatically accepted—there is no signing key authority."
+msgstr ""
+"Нет никаких первоначальных ключей, за исключением ключей jrandom и zzz "
+"(используются \n"
+"те же ключи, что и для обновления маршрутизатора), так что первый ключ, "
+"доступный для подписания, \n"
+"автоматически принимается—авторизация подписывающих ключей "
+"отсутствует."
+
+#: i2p2www/pages/site/docs/plugins.html:174
+msgid ""
+"When deleting a plugin, the directory is not always deleted, especially "
+"on\n"
+"Windows."
+msgstr ""
+"При удалении плагина директории не всегда удаляются, особенно в \n"
+"Windows."
+
+#: i2p2www/pages/site/docs/plugins.html:179
+msgid ""
+"Installing a plugin requiring Java 1.6 on a Java 1.5 machine will result "
+"in a\n"
+"\"plugin is corrupt\" message if pack200 compression of the plugin file "
+"is used."
+msgstr ""
+"При установке плагинов, требующих Java 1.6, на машине с Java 1.5 "
+"возникнет \n"
+"сообщение \"plugin is corrupt\", если используется pack200 сжатие плагина."
+
+#: i2p2www/pages/site/docs/plugins.html:184
+msgid "Theme and translation plugins are untested."
+msgstr "Темы и плагины переводов не тестируются."
+
+#: i2p2www/pages/site/docs/plugins.html:188
+msgid "Disabling autostart doesn't always work."
+msgstr "Отключение автоматического запуска не всегда срабатывает."
+
+#: i2p2www/pages/site/docs/ports.html:2
+msgid "Ports Used by I2P"
+msgstr "Порты, используемые I2P"
+
+#: i2p2www/pages/site/docs/ports.html:7
+msgid ""
+"These are the ports used or reserved by I2P, including those for known "
+"plugins,\n"
+"common alternates,\n"
+"and some typical related applications."
+msgstr ""
+"Ниже приведены порты, используемые или зарезервированные под нужды I2P, "
+"включая порты для \n"
+"известных плагинов, общих альтернатив \n"
+"и некоторых типичных связанных приложений."
+
+#: i2p2www/pages/site/docs/ports.html:13
+#, python-format
+msgid ""
+"Note that many of these are not enabled by default.\n"
+"There is more information in the FAQ.\n"
+"See also the documentation for individual plugins.\n"
+"Plugin authors please add any ports you use here.\n"
+"For new plugins, we recommend using the next available port\n"
+"in the 766x range."
+msgstr ""
+"Учтите, что многие из них не задействованы по умолчанию. \n"
+"Больше информации есть в FAQ. \n"
+"Также смотри документацию по конкретным плагинам. \n"
+"Авторы плагинов, пожалуйста, добавляйте сюда все используемые порты. \n"
+"Для новых плагинов мы рекомендуем использовать следующий доступный порт \n"
+"из диапазона 766x."
+
+#: i2p2www/pages/site/docs/ports.html:53
+msgid "recommended spot for new plugins/applications"
+msgstr "рекомендованный диапазон для новых плагинов/приложений"
+
+#: i2p2www/pages/site/docs/api/bob.html:3
+#: i2p2www/pages/site/docs/api/datagrams.html:3
+#: i2p2www/pages/site/docs/how/garlic-routing.html:3
+#: i2p2www/pages/site/docs/protocol/index.html:3
+#: i2p2www/pages/site/docs/transport/ntcp.html:3
+msgid "August 2010"
+msgstr "Август 2010"
+
+#: i2p2www/pages/site/docs/api/bob.html:5
+msgid "BOB - Basic Open Bridge"
+msgstr "BOB - Basic Open Bridge"
+
+#: i2p2www/pages/site/docs/api/bob.html:7
+msgid "Technical differences from SAM (for the better?)"
+msgstr "Технические отличия от SAM (для улучшения?)"
+
+#: i2p2www/pages/site/docs/api/bob.html:9
+msgid ""
+"BOB has separate command and data channels. \n"
+"One, an application command channel socket to router to configure.\n"
+"Two, the application data sockets to/from router that carry only data.\n"
+"The command channel is only needed for making or setting the initial\n"
+"destination key, and to set the destination key to port bindings. \n"
+"All connections run in parallel."
+msgstr ""
+"BOB имеет раздельные каналы для команд и данных. \n"
+"Один - сокет канала команд приложения к маршрутизатору для настройки. \n"
+"Второй - сокеты данных приложения к/от маршрутизатора, только для "
+"передачи данных. \n"
+"Канал команд нужен только для создания или задания начального ключа "
+"пункта назначения, \n"
+"и для установки связи ключа пункта назначения и порта. \n"
+"Все соединения запускаются параллельно."
+
+#: i2p2www/pages/site/docs/api/bob.html:18
+msgid ""
+"SAM has one connection that does everything, and you need to parse every "
+"packet."
+msgstr ""
+"В SAM все выполняется через одно соединение, и вам приходится разбирать "
+"каждый пакет."
+
+#: i2p2www/pages/site/docs/api/bob.html:22
+msgid ""
+"BOB does not hold keypair values, nor does the router.\n"
+"Your application holds the keypair values. \n"
+"This is to reduce any extra complexity in the router code, it also adds "
+"to\n"
+"your privacy."
+msgstr ""
+"BOB не хранит значений пары ключей, как и маршрутизатор. \n"
+"Ваше приложение хранит значения пары ключей. \n"
+"Это сделано для уменьшения сложности кода маршрутизатор, \n"
+"это также добавляет вам приватности."
+
+#: i2p2www/pages/site/docs/api/bob.html:29
+msgid "SAM router stores every keypair you ever make."
+msgstr "Маршрутизатор SAM хранит все пары ключей когда либо созданные вами."
+
+#: i2p2www/pages/site/docs/api/bob.html:33
+msgid "Those are the important differences."
+msgstr "И это самые важные отличия."
+
+#: i2p2www/pages/site/docs/api/bob.html:37
+msgid "KEYS = keypair public+private, these are BASE64"
+msgstr "KEYS = пара ключей public+private, в виде BASE64"
+
+#: i2p2www/pages/site/docs/api/bob.html:40
+msgid "KEY = public key, also BASE64"
+msgstr "KEY = public ключ, также BASE64"
+
+#: i2p2www/pages/site/docs/api/bob.html:43
+msgid ""
+"ERROR as is implied returns the message \"ERROR "
+"\"+DESCRIPTION+\"\n"
+"\", where the DESCRIPTION is what went wrong."
+msgstr ""
+"ERROR как и предполагается, возвращает сообщение "
+"\"ERROR \"+DESCRIPTION+\"\n"
+"\", где DESCRIPTION это описание проблемы."
+
+#: i2p2www/pages/site/docs/api/bob.html:46
+msgid ""
+"OK returns \"OK\", and if data is to be "
+"returned, it is on the same line. OK means the command is "
+"finished."
+msgstr ""
+"OK возвращает \"OK\", и если есть возвращаемые "
+"данные, они буду расположены в этой же строке. OK означает, "
+"что команда выполнена."
+
+#: i2p2www/pages/site/docs/api/bob.html:49
+msgid ""
+"DATA lines contain information that you requested. There may"
+" be multiple DATA lines per request."
+msgstr ""
+"Строка DATA содержит информацию, которую вы запросили. Может"
+" быть несколько строк DATA на один запрос."
+
+#: i2p2www/pages/site/docs/api/bob.html:53
+msgid ""
+"NOTE: The help command is the ONLY command that has an exception "
+"to\n"
+"the rules... it can actually return nothing! This is intentional, since\n"
+"help is a HUMAN and not an APPLICATION command."
+msgstr ""
+"Примечание: Команда help - ЕДИНСТВЕННАЯ команда, для которой есть "
+"исключения из\n"
+"правил... Она может ничего не возвращать! Это сделано намеренно, "
+"поскольку \n"
+"help это команда для ЧЕЛОВЕКА, а не для ПРИЛОЖЕНИЯ."
+
+#: i2p2www/pages/site/docs/api/bob.html:59
+msgid ""
+"PLEASE NOTE:\n"
+"For CURRENT details on the commands PLEASE use the built-in help command."
+" \n"
+"Just telnet to localhost 2827 and type help and you can get full "
+"documentation on each command."
+msgstr ""
+"ПОЖАЛУЙСТА УЧТИТЕ:\n"
+"Для получения АКТУАЛЬНЫХ подробностей по командам ПОЖАЛУЙСТА используйте "
+"встроенную команду help.\n"
+"Просто подключитесь по telnet к localhost 2827 и введите help, и вы "
+"получите полную документацию по каждой команде."
+
+#: i2p2www/pages/site/docs/api/bob.html:65
+msgid ""
+"Commands never get obsoleted or changed, however new commands do get "
+"added from time to time."
+msgstr ""
+"Команды никогда не устаревают и не изменяются, тем не менее, новые "
+"команды время от времени появляются."
+
+#: i2p2www/pages/site/docs/api/bob.html:69
+msgid "Here are the commands we have as of this writing:"
+msgstr "Вот список команд, которые имеются на момент написания страницы:"
+
+#: i2p2www/pages/site/docs/api/bob.html:74
+msgid "COMMAND"
+msgstr "КОМАНДА"
+
+#: i2p2www/pages/site/docs/api/bob.html:74
+msgid "OPERAND"
+msgstr "ОПЕРАНД"
+
+#: i2p2www/pages/site/docs/api/bob.html:74
+msgid "RETURNS"
+msgstr "ВОЗВРАЩАЕТ"
+
+#: i2p2www/pages/site/docs/api/bob.html:101
+msgid ""
+"Once set up, all TCP sockets can and will block as needed, and there is "
+"no need for any \n"
+"additional messages to/from the command channel. This allows the router "
+"to pace the\n"
+"stream without exploding with OOM like SAM does as it chokes on "
+"attempting to shove \n"
+"many streams in or out one socket -- that can't scale when you have alot "
+"of connections!"
+msgstr ""
+"После установки все необходимые TCP сокеты могут и будут заблокированы, и"
+" нет необходимости в \n"
+"дополнительных сообщениях в/из канал команд. Это позволяет маршрутизатору"
+" проходить \n"
+"поток без разрыва с OOM, в отличие от SAM, который захлебывается при "
+"попытке впихнуть \n"
+"несколько потоков в или из одного сокета -- это не поддается "
+"масштабированию при наличии большого числа подключений!"
+
+#: i2p2www/pages/site/docs/api/bob.html:108
+msgid ""
+"What is also nice about this particular interface is that writing "
+"anything to interface \n"
+"to it, is much much easier than SAM. There is no other processing to do "
+"after the set up.\n"
+"It's configuration is so simple, that very simple tools, such as nc "
+"(netcat) can be used \n"
+"to point to some application. The value there is that one could schedule "
+"up and down times \n"
+"for an application, and not have to change the application to do that, or"
+" to even have \n"
+"to stop that application. Instead, you can literally \"unplug\" the "
+"destination, and \n"
+"\"plug it in\" again. As long as the same IP/port addresses and "
+"destination keys are used \n"
+"when bringing the bridge up, the normal TCP application won't care, and "
+"won't notice.\n"
+"It will simply be fooled -- the destinations are not reachable, and that "
+"nothing is coming in."
+msgstr ""
+"Есть еще одна замечательная вещь в этом специфическом интерфейсе - "
+"написать что угодно, подключающееся к нему, \n"
+"намного проще, чем к SAM. Не нужно делать ничего дополнительного после "
+"установки. \n"
+"Его настройка настолько проста, что любое просто средство, как например "
+"nc (netcat), можно использовать \n"
+"для указания на какое-то приложение. Смысле в том, что можно "
+"запланировать время запуска и остановки \n"
+"приложения, и для этого не нужно изменять его, или, даже, \n"
+"останавливать это приложение. Вместо этого вы можете буквально \"вынуть\""
+" пункт назначения, и \n"
+"\"вставить\" снова. Поскольку для восстановления моста используются та же"
+" пара IP/порт и ключи, \n"
+"то обычному приложению это не важно, и оно не будет даже об этом знать. \n"
+"Оно просто будет обмануто -- пункт назначения недоступен, и ничего не "
+"поступает на вход."
+
+#: i2p2www/pages/site/docs/api/bob.html:120
+msgid ""
+"For the following example, we'll setup a very simple local loopback "
+"connection, \n"
+"with two destinations. Destination \"mouth\" will be the CHARGEN service "
+"from \n"
+"the INET superserver daemon. Destination \"ear\" will be a local port "
+"that you\n"
+"can telnet into, and watch the pretty ASCII test puke forth."
+msgstr ""
+"В следующем примере мы установим очень простое закольцованное локальное "
+"подключение \n"
+"с двумя пунктами назначения. Пунктом \"mouth\" будет служба CHARGEN \n"
+"демона суперсервера INET. Пунктом \"ear\" будет локальный порт, к "
+"которому \n"
+"вы можете подключиться по telnet и увидеть забавный тест с символами "
+"ASCII."
+
+#: i2p2www/pages/site/docs/api/bob.html:128
+msgid "EXAMPLE SESSION DIALOGUE -- simple telnet 127.0.0.1 2827 works"
+msgstr "ПРИМЕР ДИАЛОГА СЕССИИ -- простой telnet 127.0.0.1 2827 работает"
+
+#: i2p2www/pages/site/docs/api/bob.html:129
+msgid "Application"
+msgstr "Приложени"
+
+#: i2p2www/pages/site/docs/api/bob.html:130
+msgid "BOB's Command response."
+msgstr "Ответ команда от BOB"
+
+#: i2p2www/pages/site/docs/api/bob.html:132
+#: i2p2www/pages/site/docs/api/bob.html:144
+#: i2p2www/pages/site/docs/api/bob.html:164
+#: i2p2www/pages/site/docs/api/bob.html:272
+#: i2p2www/pages/site/docs/api/bob.html:284
+#: i2p2www/pages/site/docs/api/bob.html:299
+msgid "FROM"
+msgstr "ОТ"
+
+#: i2p2www/pages/site/docs/api/bob.html:132
+#: i2p2www/pages/site/docs/api/bob.html:144
+#: i2p2www/pages/site/docs/api/bob.html:164
+#: i2p2www/pages/site/docs/api/bob.html:272
+#: i2p2www/pages/site/docs/api/bob.html:284
+#: i2p2www/pages/site/docs/api/bob.html:299
+msgid "TO"
+msgstr "К"
+
+#: i2p2www/pages/site/docs/api/bob.html:132
+#: i2p2www/pages/site/docs/api/bob.html:144
+#: i2p2www/pages/site/docs/api/bob.html:164
+#: i2p2www/pages/site/docs/api/bob.html:272
+#: i2p2www/pages/site/docs/api/bob.html:284
+#: i2p2www/pages/site/docs/api/bob.html:299
+msgid "DIALOGUE"
+msgstr "ДИАЛОГ"
+
+#: i2p2www/pages/site/docs/api/bob.html:139
+msgid "MAKE NOTE OF THE ABOVE DESTINATION KEY, YOURS WILL BE DIFFERENT!"
+msgstr "ОБРАТИТЕ ВНИМАНИЕ НА КЛЮЧ НАЗНАЧЕНИЯ ВЫШЕ, ВАШ БУДЕТ ДРУГИМ!"
+
+#: i2p2www/pages/site/docs/api/bob.html:153
+msgid ""
+"At this point, there was no error, a destination with a nickname of "
+"\"mouth\" \n"
+"is set up. When you contact the destination provided, you actually "
+"connect \n"
+"to the CHARGEN service on 19/TCP."
+msgstr ""
+"Пока что ошибки не было, пункт назначения с именем \"mouth\" \n"
+"установлен. Когда вы подключаетесь к указанному пункту, вы на самом деле"
+" \n"
+"соединяетесь со службой CHARGEN на порту 19/TCP."
+
+#: i2p2www/pages/site/docs/api/bob.html:159
+msgid "Now for the other half, so that we can actually contact this destination."
+msgstr ""
+"А теперь вторая половина, мы на самом деле подключаемся к пункту "
+"назначения."
+
+#: i2p2www/pages/site/docs/api/bob.html:179
+msgid ""
+"Now all we need to do is telnet into 127.0.0.1, port 37337,\n"
+"send the destination key or host address from addressbook we want to "
+"contact.\n"
+"In this case, we want to contact \"mouth\", all we do is paste in the\n"
+"key and it goes."
+msgstr ""
+"Все что нам теперь осталось сделать - подключиться по telnet к 127.0.0.1 "
+"на порт 37337, отправить ключ пункта назначения или адрес узла из "
+"адресной книги, к которому мы хотим подключиться. \n"
+"В нашем случае, мы хотим подключиться к \"mouth\", мы вставляем \n"
+"ключ и понеслась."
+
+#: i2p2www/pages/site/docs/api/bob.html:186
+msgid ""
+"NOTE: The \"quit\" command in the command channel does NOT "
+"disconnect the tunnels like SAM."
+msgstr ""
+"ПРИМЕЧАНИЕ: Команда \"quit\" в канале команд НЕ выполняет разрыв "
+"соединения туннелей, как это делает SAM."
+
+#: i2p2www/pages/site/docs/api/bob.html:203
+msgid "After a few virtual miles of this spew, press Control-]"
+msgstr ""
+"После пары виртуальных километров этой отрыжки нажмите "
+"Control-]"
+
+#: i2p2www/pages/site/docs/api/bob.html:215
+msgid "Here is what happened..."
+msgstr "И вот что произошло..."
+
+#: i2p2www/pages/site/docs/api/bob.html:223
+msgid "You can connect to EEPSITES too!"
+msgstr "Также вы не можете подключиться к EEPSITE!"
+
+#: i2p2www/pages/site/docs/api/bob.html:256
+msgid ""
+"Pretty cool isn't it? Try some other well known EEPSITES if you like, "
+"nonexistent ones, \n"
+"etc, to get a feel for what kind of output to expect in different "
+"situations. \n"
+"For the most part, it is suggested that you ignore any of the error "
+"messages. \n"
+"They would be meaningless to the application, and are only presented for "
+"human debugging."
+msgstr ""
+"Прикольно, правда? Если хотите, попробуйте другие известные EEPSITE, "
+"несуществующие, \n"
+"и т.д., чтобы понять что можно ожидать на выходе в различных ситуациях. \n"
+"По большей части предполагается что вы игнорируете любые сообщения об "
+"ошибках. \n"
+"Они будут бессмысленными для приложения, и выводятся только для отладки "
+"человеком."
+
+#: i2p2www/pages/site/docs/api/bob.html:263
+msgid "Let's put down our destinations now that we are all done with them."
+msgstr ""
+"Давайте теперь отключим наши пункты назначения, т.к. мы уже с ними "
+"закончили."
+
+#: i2p2www/pages/site/docs/api/bob.html:267
+msgid "First, lets see what destination nicknames we have."
+msgstr "Для начала посмотрим какие имена пунктов у нас есть."
+
+#: i2p2www/pages/site/docs/api/bob.html:279
+msgid "Alright, there they are. First, let's remove \"mouth\"."
+msgstr "Отлично, вот и они. Сначала давайте уберем \"mouth\"."
+
+#: i2p2www/pages/site/docs/api/bob.html:293
+msgid ""
+"Now to remove \"ear\", note that this is what happens when you type too "
+"fast,\n"
+"and shows you what typical ERROR messages looks like."
+msgstr ""
+"Теперь уберем \"ear\", и вот что происходит когда вы печатаете слишком "
+"быстро, \n"
+"также вы увидите как выглядят типичные сообщения об ОШИБКАХ."
+
+#: i2p2www/pages/site/docs/api/bob.html:312
+msgid ""
+"I won't bother to show an example of the receiver end of a bridge\n"
+"because it is very simple. There are two possible settings for it, and\n"
+"it is toggled with the \"quiet\" command."
+msgstr ""
+"Я не стану показывать пример получателя моста, \n"
+"потому что это слишком просто. Для него есть два доступных режима, \n"
+"и они переключаются командой \"quiet\"."
+
+#: i2p2www/pages/site/docs/api/bob.html:318
+msgid ""
+"The default is NOT quiet, and the first data to come into your\n"
+"listening socket is the destination that is making the contact. It is a\n"
+"single line consisting of the BASE64 address followed by a newline.\n"
+"Everything after that is for the application to actually consume."
+msgstr ""
+"По умолчанию этот режим отключен, и первые данные, которые приходят на \n"
+"ваш слушающий сокет - это пункт назначения, который к вам подключается. \n"
+"Это одна строка, состоящая из BASE64 адреса, оканчивающаяся переводом "
+"строки. \n"
+"Все остальное после нее предназначено для обработки приложением."
+
+#: i2p2www/pages/site/docs/api/bob.html:325
+msgid ""
+"In quiet mode, think of it as a regular Internet connection. No\n"
+"extra data comes in at all. It's just as if you are plain connected to\n"
+"the regular Internet. This mode allows a form of transparency much like\n"
+"is available on the router console tunnel settings pages, so that you\n"
+"can use BOB to point a destination at a web server, for example, and\n"
+"you would not have to modify the web server at all."
+msgstr ""
+"Тихий режим можете себе представить в виде обычного интернет подключения."
+" \n"
+"Никаких дополнительных данных не приходит вовсе. Просто как будто вы "
+"подключились \n"
+"к обычному интернету. Этот режим предоставляет такую же форму "
+"прозрачности, какая \n"
+"доступна на странице настроек туннеля консоли маршрутизатора, и поэтому "
+"вы \n"
+"можете использовать BOB, например, для указания пункта назначения на "
+"веб-сервере, \n"
+"и вам совсем не нужно изменять веб-сервер."
+
+#: i2p2www/pages/site/docs/api/bob.html:334
+msgid ""
+"The advantage with using BOB for this is as discussed\n"
+"previously. You could schedule random uptimes for the application,\n"
+"redirect to a different machine, etc. One use of this may be something\n"
+"like wanting to try to goof up router-to-destination upness guessing.\n"
+"You could stop and start the destination with a totally different\n"
+"process to make random up and down times on services. That way you\n"
+"would only be stopping the ability to contact such a service, and not\n"
+"have to bother shutting it down and restarting it. You could redirect\n"
+"and point to a different machine on your LAN while you do updates, or\n"
+"point to a set of backup machines depending on what is running, etc,\n"
+"etc. Only your imagination limits what you could do with BOB."
+msgstr ""
+"Преимущества использования BOB, как описано ранее. \n"
+"Вы можете запланировать произвольное время работы приложения, \n"
+"перенаправить а другую машину, и т.п. Одним из применений этого может "
+"быть \n"
+"желание попробовать испортить оценку доступности канала "
+"\"маршрутизатор\"-\"пункт назначения\". \n"
+"Вы можете опускать и поднимать пункт назначения совершенно другим \n"
+"способом, чтобы выполнять произвольную остановку и запуск службы. Таким "
+"методом вы \n"
+"будете только отключать возможность подключения к такой службе, и не "
+"будете \n"
+"вынуждены останавливать и перезапускать ее. Вы можете перенаправить \n"
+"или указать на другую машину в вашей LAN пока вы выполняете обновление, \n"
+"или указать на набор запасных машин, в зависимости от того что запущено, "
+"и т.д. \n"
+"Ваши возможности взаимодействия с BOB ограничены только вашим "
+"воображением."
+
+#: i2p2www/pages/site/docs/api/datagrams.html:6
+msgid "Datagram Overview"
+msgstr "Обзор Дейтаграмм"
+
+#: i2p2www/pages/site/docs/api/datagrams.html:7
+#, python-format
+msgid ""
+"Datagrams build upon the base I2CP to provide "
+"authenticated\n"
+"and repliable messages in a standard format. This lets applications "
+"reliably read\n"
+"the \"from\" address out of a datagram and know that the address really "
+"sent the\n"
+"message. This is necessary for some applications since the base I2P "
+"message is\n"
+"completely raw - it has no \"from\" address (unlike IP packets). In "
+"addition, the\n"
+"message and sender are authenticated by signing the payload."
+msgstr ""
+"Дейтаграммы строятся на основе I2CP, и "
+"предоставляют аутентифицированные \n"
+"сообщения в стандартном формате, на которые можно ответить. Это позволяет"
+" приложениям читать \n"
+"достоверный адрес \"От\" в дейтаграмме, и узнать с какого адреса на самом"
+" деле \n"
+"отправлено сообщение. Это важно для некоторых приложений, поскольку "
+"базовое сообщение I2P \n"
+"не форматировано - в нем нет адреса \"от\" (как это есть в IP). Кроме "
+"того, \n"
+"сообщение и отправитель аутентифицируются по подписи на данных."
+
+#: i2p2www/pages/site/docs/api/datagrams.html:16
+#, python-format
+msgid ""
+"Datagrams, like streaming library packets,\n"
+"are an application-level construct.\n"
+"These protocols are independent of the low-level transports;\n"
+"the protocols are converted to I2NP messages by the router, and\n"
+"either protocol may be carried by either transport."
+msgstr ""
+"Дейтаграммы, как и пакеты потоковой "
+"библиотеки,\n"
+"являются конструкциями уровня приложения.\n"
+"Эти протоколы не зависят от низкоуровневого транспорта;\n"
+"протоколы конвертируются маршрутизатором в сообщения I2NP, \n"
+"каждый протокол может передаваться любым транспортом."
+
+#: i2p2www/pages/site/docs/api/datagrams.html:25
+msgid "Application Guide"
+msgstr "Руководство по Приложениям"
+
+#: i2p2www/pages/site/docs/api/datagrams.html:26
+#, python-format
+msgid ""
+"Applications written in Java may use the \n"
+"datagram API,\n"
+"while applications in other languages \n"
+"can use SAM's datagram support.\n"
+"There is also limited support in i2ptunnel in the SOCKS proxy,\n"
+"the 'streamr' tunnel types, and udpTunnel classes."
+msgstr ""
+"Приложения, написанные на Java, могут использовать \n"
+"API дейтаграмм, \n"
+"приложения на других языках \n"
+"могут использовать поддержку дейтаграмм SAM'а. \n"
+"Также есть ограниченная поддержка в i2ptunnel в SOCKS proxy, \n"
+"'streamr' типы туннеля и классы udpTunnel."
+
+#: i2p2www/pages/site/docs/api/datagrams.html:37
+msgid "Datagram Length"
+msgstr "Длина Дейтаграммы"
+
+#: i2p2www/pages/site/docs/api/datagrams.html:38
+msgid ""
+"The application designer should carefully consider the tradeoff of "
+"repliable vs. non-repliable\n"
+"datagrams. Also, the datagram size will affect reliability, due to tunnel"
+" fragmentation into 1KB\n"
+"tunnel messages. The more message fragments, the more likely that one of "
+"them will be dropped\n"
+"by an intermediate hop. Messages larger than a few KB are not "
+"recommended.\n"
+"Over about 10 KB, the delivery probablility drops dramatically.\n"
+"Messages over 16 KB cannot be delivered over NTCP, dropping delivery "
+"chances even more."
+msgstr ""
+"Проектировщик приложения должен хорошо понимать разницу между "
+"дейтаграммами с ответом \n"
+"и без оных. Также, размер дейтаграммы влияет на надежность, в виду "
+"фрагментации туннелем \n"
+"сообщений по 1 КБ. Чем больше сообщение фрагментируется, тем более "
+"вероятно, что одно из них будет потеряно \n"
+"на промежуточном прыжке. Сообщения размером более нескольких КБ не "
+"рекомендованы для использования. \n"
+"При размере более 10 КБ доставка, возможно, сильно ухудшится. \n"
+"Сообщения более 16 КБ не могут быть доставлены по NTCP, шансы сбоя "
+"доставки сильно увеличиваются."
+
+#: i2p2www/pages/site/docs/api/datagrams.html:47
+#, python-format
+msgid ""
+"Also note that the various overheads added by lower layers, in particular"
+" asymmetric\n"
+"ElGamal/AES, place a large burden on "
+"intermittent messages\n"
+"such as used by a Kademlia-over-UDP application. The implementations are "
+"currently tuned\n"
+"for frequent traffic using the streaming library. There are a high number"
+"\n"
+"of session tags delivered, and a short session tag lifetime, for example."
+"\n"
+"There are currently no configuration parameters available within I2CP to "
+"tune\n"
+"the ElGamal Session Tag parameters."
+msgstr ""
+"Также учитывайте, что различные накладные расходы добавляются на более "
+"низких уровнях, в ассиметричном \n"
+"алгоритме ElGamal/AES, они создают большую"
+" нагрузку на прерывистые сообщения, \n"
+"как в приложении Kademlia-over-UDP. Сейчас реализация отлажена \n"
+"для часто встречающегося трафика с использованием потоковой библиотеки. "
+"Например, доставлено \n"
+"большое количество меток сессии и время жизни меток сессии мало. \n"
+"Сейчас нет конфигурации, доступной в I2CP, для настройки \n"
+"параметров меток сессии ElGamal."
+
+#: i2p2www/pages/site/docs/api/datagrams.html:57
+msgid "I2CP Protocol Number and Ports"
+msgstr "Номер Протокола I2CP и Порты"
+
+#: i2p2www/pages/site/docs/api/datagrams.html:58
+msgid ""
+"The standard I2CP protocol number for datagrams is PROTO_DATAGRAM (17).\n"
+"Applications may or may not choose to set the\n"
+"protocol in the I2CP header. It is not set by default.\n"
+"It must be set to demultiplex datagram and streaming traffic received on "
+"the same Destination."
+msgstr ""
+"Стандартный номер протокола I2CP для дейтаграмм - PROTO_DATAGRAM (17). \n"
+"Приложения могут указывать или не указывать протокол \n"
+"в заголовке I2CP. По умолчанию он не указан. \n"
+"Его нужно указать для демультиплексирования дейтаграммы и потокового "
+"трафика, полученных на одном пункте назначения."
+
+#: i2p2www/pages/site/docs/api/datagrams.html:65
+#, python-format
+msgid ""
+"As datagrams are not connection-oriented, the application may require\n"
+"port numbers to correlate datagrams with particular peers or "
+"communications sessions,\n"
+"as is traditional with UDP over IP.\n"
+"Applications may add 'from' and 'to' ports to the I2CP (gzip) header as "
+"described in\n"
+"the I2CP page."
+msgstr ""
+"Поскольку дейтаграммы не ориентированы на соединение, приложению может \n"
+"понадобиться номер порта для сопоставления дейтаграмм от определенных "
+"узлов или сессий подключения, \n"
+"как и в традиционном UDP над IP. \n"
+"Приложения могут добавить порты 'от' и 'к' в заголовок I2CP (gzip), как "
+"это описано на \n"
+"странице I2CP."
+
+#: i2p2www/pages/site/docs/api/datagrams.html:73
+#, python-format
+msgid ""
+"There is no method within the datagram API to specify whether it is non-"
+"repliable (raw)\n"
+"or repliable. The application should be designed to expect the "
+"appropriate type.\n"
+"The I2CP protocol number or port should be used by the application to\n"
+"indicate datagram type.\n"
+"The I2CP protocol numbers PROTO_DATAGRAM (signed) and PROTO_DATAGRAM_RAW "
+"are defined in the\n"
+"I2PSession API\n"
+"for this purpose. A common design pattern in client/server datagram "
+"applications is to\n"
+"use signed datagrams for a request which includes a nonce, and use a raw "
+"datagram\n"
+"for the reply, returning the nonce from the request."
+msgstr ""
+"В API дейтаграмм нет возможности указать является ли она безответной "
+"(raw) \n"
+"или с возможностью ответа. Приложение должно быть само определять "
+"правильный тип. \n"
+"Номер протокола I2CP или порт могут быть использованы приложением \n"
+"для определения типа дейтаграммы. \n"
+"Для этой цели в I2PSession API \n"
+"определены номера протокола I2CP - PROTO_DATAGRAM (подписанная) и "
+"PROTO_DATAGRAM_RAW. Общим принципом в приложениях клиент/сервер с "
+"дейтаграммами является \n"
+"использование подписанных дейтаграмм для запросов, которые содержат некие"
+" данные, и raw дейтаграммы \n"
+"для ответа, с обратной отправкой тех данных из запроса."
+
+#: i2p2www/pages/site/docs/api/datagrams.html:85
+#, python-format
+msgid ""
+"The protocols and ports may be set in I2CP's\n"
+"I2PSession API,\n"
+"as implemented in\n"
+"I2PSessionMuxedImpl."
+msgstr ""
+"Протоколы и порты могут быть настроены в \n"
+"I2PSession API I2CP, \n"
+"как это реализовано в \n"
+"I2PSessionMuxedImpl."
+
+#: i2p2www/pages/site/docs/api/datagrams.html:93
+#: i2p2www/pages/site/docs/api/streaming.html:381
+msgid "Data Integrity"
+msgstr "Целостность данных"
+
+#: i2p2www/pages/site/docs/api/datagrams.html:94
+#, python-format
+msgid ""
+"Data integrity is assured by the gzip CRC-32 checksum implemented in\n"
+"the I2CP layer.\n"
+"There is no checksum field in the datagram protocol."
+msgstr ""
+"Целостность данных, гарантируемая проверкой gzip суммы CRC-32, "
+"реализована на \n"
+"уровне I2CP. \n"
+"В протоколе дейтаграмм нет поля с проверочной суммой."
+
+#: i2p2www/pages/site/docs/api/datagrams.html:100
+#: i2p2www/pages/site/docs/api/streaming.html:389
+msgid "Packet Encapsulation"
+msgstr "Инкапсуляция пакета"
+
+#: i2p2www/pages/site/docs/api/datagrams.html:101
+#, python-format
+msgid ""
+"Each datagram is sent through I2P as a single message (or as an "
+"individual clove in a\n"
+"Garlic Message).\n"
+"Message encapsulation is implemented in the underlying\n"
+"I2CP,\n"
+"I2NP, and\n"
+"tunnel message layers.\n"
+"There is no packet delimiter mechanism or length field in the datagram "
+"protocol."
+msgstr ""
+"Каждая дейтаграмма отправляется через I2P как отдельное сообщение (или "
+"отдельный зубчик в\n"
+"Чесночном Сообщении).\n"
+"Инкапсуляция сообщения реализована в нижележащих уровнях \n"
+"I2CP,\n"
+"I2NP и \n"
+"туннельном сообщении.\n"
+"В протоколе дейтаграмм нет механизма разделения пакетов или поля длины."
+
+#: i2p2www/pages/site/docs/api/datagrams.html:114
+#: i2p2www/pages/site/docs/spec/datagrams.html:10
+#: i2p2www/pages/site/docs/transport/ssu.html:567
+msgid "Specification"
+msgstr "Спецификация"
+
+#: i2p2www/pages/site/docs/api/datagrams.html:116
+msgid "See the Datagrams Specification page."
+msgstr "Смотри страницу Спецификации Дейтаграмм."
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:4
+msgid "I2PControl - Remote Control Service"
+msgstr "I2PControl - Служба Удаленного Управления"
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:5
+#, python-format
+msgid ""
+"I2P enables a JSONRPC2 interface via the plugin I2PControl.\n"
+"The aim of the interface is to provide simple way to interface with a "
+"running I2P node. A client, itoopie, has been developed in parallel.\n"
+"The JSONRPC2 implementation for the client as well as the plugin is "
+"provided by the java libraries JSON-RPC 2.0. \n"
+"A list of implementations of JSON-RPC for various languages can be found "
+"at the JSON-RPC "
+"wiki."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:12
+msgid "I2PControl is by default listening on localhost:7650"
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:14
+msgid "API, version 1."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:15
+msgid "Parameters are only provided in a named way (maps)."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:19
+msgid "JSON-RPC 2 format"
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:21
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:27
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:40
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:50
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:59
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:69
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:84
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:137
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:154
+msgid "Request:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:23
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:32
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:44
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:54
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:64
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:75
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:101
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:145
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:169
+msgid "Response:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:26
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:28
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:29
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:33
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:34
+#: i2p2www/pages/site/docs/protocol/i2cp.html:99
+#: i2p2www/pages/site/docs/protocol/i2cp.html:442
+#: i2p2www/pages/site/docs/spec/common-structures.html:16
+#: i2p2www/pages/site/docs/spec/common-structures.html:26
+#: i2p2www/pages/site/docs/spec/common-structures.html:37
+#: i2p2www/pages/site/docs/spec/common-structures.html:49
+#: i2p2www/pages/site/docs/spec/common-structures.html:64
+#: i2p2www/pages/site/docs/spec/common-structures.html:77
+#: i2p2www/pages/site/docs/spec/common-structures.html:90
+#: i2p2www/pages/site/docs/spec/common-structures.html:102
+#: i2p2www/pages/site/docs/spec/common-structures.html:114
+#: i2p2www/pages/site/docs/spec/common-structures.html:126
+#: i2p2www/pages/site/docs/spec/common-structures.html:138
+#: i2p2www/pages/site/docs/spec/common-structures.html:150
+#: i2p2www/pages/site/docs/spec/common-structures.html:162
+#: i2p2www/pages/site/docs/spec/common-structures.html:174
+#: i2p2www/pages/site/docs/spec/common-structures.html:227
+#: i2p2www/pages/site/docs/spec/common-structures.html:299
+#: i2p2www/pages/site/docs/spec/common-structures.html:348
+#: i2p2www/pages/site/docs/spec/common-structures.html:400
+#: i2p2www/pages/site/docs/spec/common-structures.html:445
+#: i2p2www/pages/site/docs/spec/common-structures.html:582
+#: i2p2www/pages/site/docs/spec/common-structures.html:638
+msgid "Description"
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:30
+msgid ""
+"Token used for authenticating every request (excluding the 'Authenticate'"
+" RPC method)"
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:38
+msgid "Implemented methods"
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:39
+msgid ""
+"Creates and returns an authentication token used for further "
+"communication."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:41
+msgid "The version of the I2PControl API used by the client."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:42
+msgid "The password used for authenticating against the remote server."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:45
+msgid "The primary I2PControl API version implemented by the server."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:46
+msgid "The token used for further communication."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:49
+msgid "Echoes the value of the echo key, used for debugging and testing."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:51
+msgid "Value will be returned in response."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:52
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:62
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:73
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:99
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:143
+msgid ""
+"Token used for authenticating the client. Is provided by the server via "
+"the 'Authenticate' RPC method."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:55
+msgid "Value of the key 'echo' in the request."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:58
+msgid ""
+"Fetches rateStat from router statManager. Creates stat if not already "
+"created."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:60
+#, python-format
+msgid ""
+"Determines which rateStat to fetch, see ratestats."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:61
+msgid "Determines which period a stat is fetched for. Measured in ms."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:65
+msgid "Returns the average value for the reuested rateStat and period."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:68
+msgid "Manages I2PControl. Ports, passwords and the like."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:70
+msgid ""
+"Sets a new listen address for I2PControl (only 127.0.0.1 and 0.0.0.0 are "
+"implemented in I2PControl currently)."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:71
+msgid ""
+"Sets a new password for I2PControl, all Authentication tokens will be "
+"revoked."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:72
+msgid "Switches which port I2PControl will listen for connections on."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:76
+msgid "Returned if address was changed"
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:77
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:78
+msgid "Returned if setting was changed"
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:79
+msgid "Returns true if any changes were made."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:80
+msgid "Returns true if any changes requiring a restart to take effect were made."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:83
+msgid "Fetches basic information about the I2P router. Uptime, version etc."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:102
+msgid "What the status of the router is."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:103
+msgid "What the uptime of the router is in ms."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:104
+msgid "What version of I2P the router is running."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:105
+msgid "The 1 second average inbound bandwidth in Bps."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:106
+msgid "The 15 second average inbound bandwidth in Bps."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:107
+msgid "The 1 second average outbound bandwidth in Bps."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:108
+msgid "The 15 second average outbound bandwidth in Bps."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:109
+msgid "What the current network status is. According to the below enum:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:128
+msgid "How many tunnels on the I2P net are we participating in."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:129
+msgid "How many peers have we communicated with recently."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:130
+msgid "How many peers are considered 'fast'."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:131
+msgid "How many peers are considered 'high capacity'."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:132
+msgid "Is the router reseeding hosts to its NetDB?"
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:133
+msgid "How many peers are known to us (listed in our NetDB)."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:136
+msgid "Manages I2P router restart/shutdown."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:138
+msgid ""
+"Initiates a router reseed, fetching peers into our NetDB from a remote "
+"host."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:139
+msgid "Restarts the router."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:140
+msgid ""
+"Restarts the router gracefully (waits for participating tunnels to "
+"expire)."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:141
+msgid "Shuts down the router."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:142
+msgid ""
+"Shuts down the router gracefully (waits for participating tunnels to "
+"expire)."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:146
+msgid "If requested, verifies that a reseed has been initiated."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:147
+msgid "If requested, verifies that a restart has been initiated."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:148
+msgid "If requested, verifies that a graceful restart has been initiated."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:149
+msgid "If requested, verifies that a shutdown has been initiated"
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:150
+msgid "If requested, verifies that a graceful shutdown has been initiated"
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:153
+msgid "Fetches or sets various network related settings. Ports, addresses etc."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:155
+msgid ""
+"What port is used for the TCP transport. If null is submitted, current "
+"setting will be returned."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:156
+msgid ""
+"What hostname is used for the TCP transport. If null is submitted, "
+"current setting will be returned."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:157
+msgid ""
+"Use automatically detected ip for TCP transport. If null is submitted, "
+"current setting will be returned."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:158
+msgid ""
+"What port is used for the UDP transport. If null is submitted, current "
+"setting will be returned."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:159
+msgid ""
+"What hostname is used for the UDP transport. If null is submitted, "
+"current setting will be returned."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:160
+msgid ""
+"Which methods should be used for detecting the ip address of the UDP "
+"transport. If null is submitted, current setting will be returned."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:161
+msgid "What ip has been detected by the UDP transport."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:162
+msgid "Is UPnP enabled. If null is submitted, current setting will be returned."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:163
+msgid ""
+"How many percent of bandwidth is usable for participating tunnels. If "
+"null is submitted, current setting will be returned."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:164
+msgid ""
+"How many KB/s of inbound bandwidth is allowed. If null is submitted, "
+"current setting will be returned."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:165
+msgid ""
+"How many KB/s of outbound bandwidth is allowed. If null is submitted, "
+"current setting will be returned."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:166
+msgid ""
+"Is laptop mode enabled (change router identity and UDP port when IP "
+"changes ). If null is submitted, current setting will be returned."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:167
+msgid ""
+"Token used for authenticating the client. Is provided by the server via "
+"the 'Authenticate' RPC method. If null is submitted, current setting will"
+" be returned."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:170
+msgid "If requested, returns the port used for the TCP transport."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:171
+msgid "If requested, returns the hostname used for the TCP transport."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:172
+msgid ""
+"If requested, returns the method used for automatically detecting ip for "
+"the TCP transport."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:173
+msgid "If requested, returns the port used for the UDP transport."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:174
+msgid "If requested, returns the hostname used for the UDP transport."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:175
+msgid ""
+"If requested, returns methods used for detecting the ip address of the "
+"UDP transport."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:176
+msgid "If requested, returns what ip has been detected by the UDP transport."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:177
+msgid "If requested, returns the UPNP setting."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:178
+msgid ""
+"If requested, returns how many percent of bandwidth is usable for "
+"participating tunnels."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:179
+msgid "If requested, returns how many KB/s of inbound bandwidth is allowed."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:180
+msgid "If requested, returns how many KB/s of outbound bandwidth is allowed."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:181
+msgid "If requested, returns the laptop mode."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:182
+msgid "Have the provided settings been saved."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:183
+msgid "Is a restart needed for the new settings to be used."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:186
+msgid "denotes an optional value."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:187
+msgid "denotes a possibly occuring return value"
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:189
+msgid "Error codes"
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:190
+msgid "Standard JSON-RPC2 error codes."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:191
+msgid "JSON parse error."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:192
+msgid "Invalid request."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:193
+msgid "Method not found."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:194
+msgid "Invalid parameters."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:195
+msgid "Internal error."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:197
+msgid "I2PControl specific error codes."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:198
+msgid "Invalid password provided."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:199
+msgid "No authentication token presented."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:200
+msgid "Authentication token doesn't exist."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:201
+msgid "The provided authentication token was expired and will be removed."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:202
+msgid ""
+"The version of the I2PControl API used wasn't specified, but is required "
+"to be specified."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:203
+msgid ""
+"The version of the I2PControl API specified is not supported by "
+"I2PControl."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2ptunnel.html:13
+#, python-format
+msgid ""
+"I2PTunnel is a tool for interfacing with and providing services on I2P.\n"
+"Destination of an I2PTunnel can be defined using a hostname,\n"
+"Base32, or a full 516-byte destination "
+"key.\n"
+"An established I2PTunnel will be available on your client machine as "
+"localhost:port.\n"
+"If you wish to provide a service on I2P network, you simply create "
+"I2PTunnel to the\n"
+"appropriate ip_address:port. A corresponding 516-byte destination key "
+"will be generated\n"
+"for the service and it will become avaliable throughout I2P.\n"
+"A web interface for I2PTunnel management is avaliable on\n"
+"localhost:7657/i2ptunnel/."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2ptunnel.html:25
+msgid "Default Services"
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2ptunnel.html:26
+msgid "Server tunnels"
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2ptunnel.html:28
+msgid ""
+"I2P Webserver - A tunnel pointed to a Jetty webserver run\n"
+"on localhost:7658 for convenient "
+"and quick hosting on I2P.\n"
+"
The document root is:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2ptunnel.html:36
+msgid "Client tunnels"
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2ptunnel.html:38
+msgid ""
+"A HTTP proxy used for browsing I2P and the regular internet anonymously "
+"through I2P. \n"
+"Browsing internet through I2P uses a random proxy specified by the "
+"\"Outproxies:\" option."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2ptunnel.html:42
+msgid "An IRC tunnel to the default anonymous IRC network, Irc2P."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2ptunnel.html:43
+#, python-format
+msgid ""
+"The anonymous monotone\n"
+"sourcecode repository for I2P"
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2ptunnel.html:47
+#, python-format
+msgid ""
+"A SMTP service provided by postman at %(postman)s"
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2ptunnel.html:50
+#, python-format
+msgid ""
+"The accompanying POP sevice of postman at %(postman)s"
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2ptunnel.html:55
+msgid "Client Modes"
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2ptunnel.html:56
+#: i2p2www/pages/site/docs/api/i2ptunnel.html:138
+msgid "Standard"
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2ptunnel.html:57
+msgid ""
+"Opens a local TCP port that connects to a service (like HTTP, FTP or "
+"SMTP) on a destination inside of I2P.\n"
+"The tunnel is directed to a random host from the comma seperated (\", \")"
+" list of destinations."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2ptunnel.html:63
+msgid ""
+"A HTTP-client tunnel. The tunnel connects to the destination specified by"
+" the URL\n"
+"in a HTTP request. Supports proxying onto internet if an outproxy is "
+"provided. Strips HTTP connections of the following headers:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2ptunnel.html:68
+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:76
+msgid ""
+"HTTP client/server tunnels are via I2Ptunnel force-enabling compression "
+"via the following http headers:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2ptunnel.html:83
+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:87
+msgid "Outproxy:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2ptunnel.html:88
+msgid "Internal I2P use:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2ptunnel.html:93
+msgid ""
+"Creates a connection to a random IRC server specified by the comma "
+"seprated (\", \") \n"
+"list of destinations. Only a whitelisted subset of IRC commands are "
+"allowed due to anonymity concerns."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2ptunnel.html:97
+msgid "Whitelist:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2ptunnel.html:112
+msgid "Enables using the I2P router as a SOCKS proxy."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2ptunnel.html:117
+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:123
+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:129
+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:137
+msgid "Server Modes"
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2ptunnel.html:139
+msgid "Creates a destination to a local ip:port with an open TCP port."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2ptunnel.html:144
+msgid ""
+"Creates a destination to a local HTTP server ip:port. Supports gzip for "
+"requests with \n"
+"Accept-encoding: x-i2p-gzip, replies with Content-encoding: x-i2p-gzip in"
+" such a request."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2ptunnel.html:150
+msgid ""
+"Functions as both a I2PTunnel HTTP Server, and a I2PTunnel HTTP client "
+"with no outproxying\n"
+"capabilities. An example application would be a web application that does"
+" client-type\n"
+"requests, or loopback-testing an eepsite as a diagnostic tool."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2ptunnel.html:157
+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:163
+msgid ""
+"A UDP-client that connects to a media server is created. The UDP-Client "
+"is coupled with a Streamr server I2PTunnel."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/ministreaming.html:2
+#: i2p2www/pages/site/docs/api/ministreaming.html:17
+msgid "Ministreaming Library"
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/ministreaming.html:5
+msgid "Note"
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/ministreaming.html:7
+#, python-format
+msgid ""
+"The ministreaming library has been enhanced and extended by the\n"
+"\"full\" streaming library.\n"
+"Ministreaming is deprecated and is incompatible with today's "
+"applications.\n"
+"The following documentation is old.\n"
+"Also note that streaming extends ministreaming in the same Java package "
+"(net.i2p.client.streaming),\n"
+"so the current API documentation contains both.\n"
+"Obsolete ministreaming classes and methods are clearly marked as "
+"deprecated in the Javadocs."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/ministreaming.html:19
+#, python-format
+msgid ""
+"\n"
+"The ministreaming library is a layer on top of the core \n"
+"I2CP that allows reliable, in order, and "
+"authenticated streams\n"
+"of messages to operate across an unreliable, unordered, and "
+"unauthenticated \n"
+"message layer. Just like the TCP to IP relationship, this streaming \n"
+"functionality has a whole series of tradeoffs and optimizations "
+"available, but\n"
+"rather than embed that functionality into the base I2P code, it has been "
+"factored\n"
+"off into its own library both to keep the TCP-esque complexities separate"
+" and to\n"
+"allow alternative optimized implementations."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/ministreaming.html:30
+#, python-format
+msgid ""
+"The ministreaming library was written by mihi as a part of his \n"
+"I2PTunnel application and then factored out"
+" and released\n"
+"under the BSD license. It is called the \"mini\"streaming library "
+"because it makes\n"
+"some simplifications in the implementation, while a more robust streaming"
+" library\n"
+"could be further optimized for operation over I2P. The two main issues "
+"with \n"
+"the ministreaming library are its use of the traditional TCP two phase \n"
+"establishment protocol and the current fixed window size of 1. The "
+"establishment\n"
+"issue is minor for long lived streams, but for short ones, such as quick "
+"HTTP\n"
+"requests, the impact can be significant. As "
+"for the window\n"
+"size, the ministreaming library doesn't maintain any ID or ordering "
+"within the \n"
+"messages sent (or include any application level ACK or SACK), so it must "
+"wait \n"
+"on average twice the time it takes to send a message before sending "
+"another."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/ministreaming.html:45
+#, python-format
+msgid ""
+"Even with those issues, the ministreaming library performs quite well in "
+"many\n"
+"situations, and its API\n"
+"is both quite simple and capable of remaining unchanged as different "
+"streaming\n"
+"implementations are introduced. The library is deployed in its own \n"
+"ministreaming.jar.\n"
+"Developers in Java who would like to use it can\n"
+"access the API directly, while developers in other languages can use it "
+"through\n"
+"SAM's streaming support."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/socks.html:4
+msgid "SOCKS and SOCKS proxies"
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/socks.html:5
+msgid ""
+"\n"
+"The SOCKS proxy is working as of release 0.7.1. SOCKS 4/4a/5 are "
+"supported.\n"
+"Enable SOCKS by creating a SOCKS client tunnel in i2ptunnel.\n"
+"Both shared-clients and non-shared are supported.\n"
+"There is no SOCKS outproxy so it is of limited use."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/socks.html:12
+#, python-format
+msgid ""
+"\n"
+"As it says on the FAQ:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/socks.html:15
+msgid ""
+"Many applications leak sensitive\n"
+"information that could identify you on the Internet. I2P only filters\n"
+"connection data, but if the program you intend to run sends this\n"
+"information as content, I2P has no way to protect your anonymity. For\n"
+"example, some mail applications will send the IP address of the machine\n"
+"they are running on to a mail server. There is no way for I2P to filter\n"
+"this, thus using I2P to 'socksify' existing applications is possible, but"
+"\n"
+"extremely dangerous."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/socks.html:25
+msgid "And quoting from a 2005 email:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/socks.html:28
+msgid ""
+"... there is a reason why human and\n"
+"others have both built and abandoned the SOCKS proxies. Forwarding\n"
+"arbitrary traffic is just plain unsafe, and it behooves us as\n"
+"developers of anonymity and security software to have the safety of\n"
+"our end users foremost in our minds."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/socks.html:36
+msgid ""
+"Hoping that we can simply strap an arbitrary client on top of I2P\n"
+"without auditing both its behavior and its exposed protocols for\n"
+"security and anonymity is naive. Pretty much *every* application\n"
+"and protocol violates anonymity, unless it was designed for it\n"
+"specifically, and even then, most of those do too. That's the\n"
+"reality. End users are better served with systems designed for\n"
+"anonymity and security. Modifying existing systems to work in\n"
+"anonymous environments is no small feat, orders of magnitude more\n"
+"work that simply using the existing I2P APIs."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/socks.html:48
+msgid ""
+"The SOCKS proxy\n"
+"supports standard addressbook names, but not Base64 destinations.\n"
+"Base32 hashes should work as of release 0.7.\n"
+"It supports outgoing connections only, i.e. an I2PTunnel Client.\n"
+"UDP support is stubbed out but not working yet.\n"
+"Outproxy selection by port number is stubbed out."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/socks.html:57
+#: i2p2www/pages/site/docs/how/tunnel-routing.html:281
+msgid "See Also"
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/socks.html:59
+#, python-format
+msgid ""
+"The notes for Meeting 81 and\n"
+"Meeting 82 in March 2004."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/socks.html:69
+msgid "If You Do Get Something Working"
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/socks.html:70
+msgid ""
+"Please let us know. And please provide substantial warnings about the\n"
+"risks of socks proxies."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/streaming.html:3
+#: i2p2www/pages/site/docs/spec/streaming.html:3
+msgid "July 2013"
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/streaming.html:8
+#, python-format
+msgid ""
+"The streaming library is technically part of the \"application\" layer,\n"
+"as it is not a core router function.\n"
+"In practice, however, it provides a vital function for almost all\n"
+"existing I2P applications, by providing a TCP-like\n"
+"streams over I2P, and allowing existing apps to be easily ported to I2P.\n"
+"The other end-to-end transport library for client communication is the\n"
+"datagram library."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/streaming.html:18
+#, python-format
+msgid ""
+"The streaming library is a layer on top of the core \n"
+"I2CP API that allows reliable, in-order, and "
+"authenticated streams\n"
+"of messages to operate across an unreliable, unordered, and "
+"unauthenticated \n"
+"message layer. Just like the TCP to IP relationship, this streaming \n"
+"functionality has a whole series of tradeoffs and optimizations "
+"available, but\n"
+"rather than embed that functionality into the base I2P code, it has been "
+"factored\n"
+"off into its own library both to keep the TCP-esque complexities separate"
+" and to\n"
+"allow alternative optimized implementations."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/streaming.html:29
+msgid ""
+"In consideration of the relatively high cost of messages, \n"
+"the streaming library's protocol for scheduling and delivering those "
+"messages has been optimized to\n"
+"allow individual messages passed to contain as much information as is "
+"available.\n"
+"For instance, a small HTTP transaction proxied through the streaming "
+"library can\n"
+"be completed in a single round trip - the first messages bundle a SYN, "
+"FIN, and\n"
+"the small HTTP request payload, and the reply bundles the SYN,\n"
+"FIN, ACK, and the HTTP response payload. While an additional\n"
+"ACK must be transmitted to tell the HTTP server that the SYN/FIN/ACK has "
+"been\n"
+"received, the local HTTP proxy can often deliver the full response to the"
+" browser \n"
+"immediately."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/streaming.html:42
+msgid ""
+"The streaming library bears much resemblance to an \n"
+"abstraction of TCP, with its sliding windows, congestion control "
+"algorithms\n"
+"(both slow start and congestion avoidance), and general packet behavior "
+"(ACK,\n"
+"SYN, FIN, RST, rto calculation, etc)."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/streaming.html:49
+msgid ""
+"The streaming library is\n"
+"a robust library\n"
+"which is optimized for operation over I2P.\n"
+"It has a one-phase setup, and\n"
+"it contains a full windowing implementation."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/streaming.html:58
+msgid "API"
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/streaming.html:60
+#, python-format
+msgid ""
+"The streaming library API provides a standard socket paradigm to Java "
+"applications.\n"
+"The lower-level I2CP API is completely hidden, "
+"except that\n"
+"applications may pass I2CP parameters "
+"through the\n"
+"streaming library, to be interpreted by I2CP."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/streaming.html:67
+#, python-format
+msgid ""
+"The standard interface to the streaming lib is for the application to use"
+" the\n"
+"I2PSocketManagerFactory to create an\n"
+"I2PSocketManager. The application then asks "
+"the\n"
+"socket manager for an I2PSession, which will "
+"cause\n"
+"a connection to the router via I2CP. The "
+"application\n"
+"can then setup connections with an I2PSocket "
+"or\n"
+"receive connections with an I2PServerSocket."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/streaming.html:82
+#, python-format
+msgid "Here are the full streaming library Javadocs."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/streaming.html:86
+msgid "For a good example of usage, see the i2psnark code."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/streaming.html:91
+msgid "Options and Defaults"
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/streaming.html:92
+#, python-format
+msgid ""
+"The options and current default values are listed below.\n"
+"Options are case-sensitive and may be set for the whole router, for a "
+"particular client, or for an individual socket on a\n"
+"per-connection basis.\n"
+"Many values are tuned for HTTP performance over typical I2P conditions. "
+"Other applications such\n"
+"as peer-to-peer services are strongly encouraged to\n"
+"modify as necessary, by setting the options and passing them via the call"
+" to\n"
+"I2PSocketManagerFactory.createManager(_i2cpHost,"
+" _i2cpPort, opts).\n"
+"Time values are in ms."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/streaming.html:103
+#, python-format
+msgid ""
+"Note that higher-layer APIs, such as SAM,\n"
+"BOB, and I2PTunnel,"
+"\n"
+"may override these defaults with their own defaults.\n"
+"Also note that many options only apply to servers listening for incoming "
+"connections."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/streaming.html:110
+msgid ""
+"As of release 0.9.1, most, but not all, options may be changed on an "
+"active socket manager or session.\n"
+"See the javadocs for details."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/streaming.html:117
+#: i2p2www/pages/site/docs/protocol/i2cp.html:94
+#: i2p2www/pages/site/docs/protocol/i2cp.html:437
+msgid "Option"
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/streaming.html:117
+#: i2p2www/pages/site/docs/protocol/i2cp.html:98
+#: i2p2www/pages/site/docs/protocol/i2cp.html:441
+msgid "Default"
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/streaming.html:117
+#: i2p2www/pages/site/docs/how/elgamal-aes.html:267
+#: i2p2www/pages/site/docs/how/peer-selection.html:282
+#: i2p2www/pages/site/docs/spec/common-structures.html:58
+#: i2p2www/pages/site/docs/spec/common-structures.html:203
+#: i2p2www/pages/site/docs/spec/common-structures.html:257
+#: i2p2www/pages/site/docs/spec/common-structures.html:340
+#: i2p2www/pages/site/docs/spec/common-structures.html:434
+#: i2p2www/pages/site/docs/spec/common-structures.html:542
+#: i2p2www/pages/site/docs/spec/common-structures.html:620
+#: i2p2www/pages/site/docs/spec/common-structures.html:722
+#: i2p2www/pages/site/docs/spec/datagrams.html:30
+#: i2p2www/pages/site/docs/spec/datagrams.html:89
+msgid "Notes"
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/streaming.html:119
+msgid ""
+"Comma- or space-separated list of Base64 peer Hashes used for either "
+"access list or blacklist."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/streaming.html:121
+#: i2p2www/pages/site/docs/api/streaming.html:127
+#: i2p2www/pages/site/docs/api/streaming.html:133
+#: i2p2www/pages/site/docs/api/streaming.html:140
+#: i2p2www/pages/site/docs/api/streaming.html:152
+#: i2p2www/pages/site/docs/api/streaming.html:163
+#: i2p2www/pages/site/docs/api/streaming.html:192
+#: i2p2www/pages/site/docs/api/streaming.html:200
+#: i2p2www/pages/site/docs/api/streaming.html:220
+#: i2p2www/pages/site/docs/api/streaming.html:237
+#: i2p2www/pages/site/docs/api/streaming.html:249
+#: i2p2www/pages/site/docs/api/streaming.html:255
+#: i2p2www/pages/site/docs/api/streaming.html:261
+#: i2p2www/pages/site/docs/api/streaming.html:275
+#: i2p2www/pages/site/docs/api/streaming.html:282
+#: i2p2www/pages/site/docs/api/streaming.html:289
+#: i2p2www/pages/site/docs/api/streaming.html:314
+#: i2p2www/pages/site/docs/api/streaming.html:321
+#: i2p2www/pages/site/docs/api/streaming.html:328
+#, python-format
+msgid "As of release %(release)s."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/streaming.html:125
+msgid "Use the access list as a whitelist for incoming connections."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/streaming.html:131
+msgid "Use the access list as a blacklist for incoming connections."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/streaming.html:145
+msgid "Whether to respond to incoming pings"
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/streaming.html:157
+msgid ""
+"Comma- or space-separated list of Base64 peer Hashes to be\n"
+"blacklisted for incoming connections to ALL destinations in the context.\n"
+"This option must be set in the context properties, NOT in the "
+"createManager() options argument.\n"
+"Note that setting this in the router context will not affect clients "
+"outside the\n"
+"router in a separate JVM and context."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/streaming.html:167
+msgid ""
+"How much transmit data (in bytes) will be accepted that hasn't been "
+"written out yet."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/streaming.html:171
+msgid ""
+"When we're in congestion avoidance, we grow the window size at the rate\n"
+"of 1/(windowSize*factor). In standard TCP, window sizes are"
+" in bytes,\n"
+"while in I2P, window sizes are in messages.\n"
+"A higher number means slower growth."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/streaming.html:178
+msgid ""
+"How long to wait after instantiating a new con \n"
+"before actually attempting to connect. If this is\n"
+"<= 0, connect immediately with no initial data. If greater than 0, "
+"wait\n"
+"until the output stream is flushed, the buffer fills, \n"
+"or that many milliseconds pass, and include any initial data with the SYN."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/streaming.html:186
+msgid ""
+"How long to block on connect, in milliseconds. Negative means "
+"indefinitely. Default is 5 minutes."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/streaming.html:190
+msgid ""
+"Whether to disable warnings in the logs when an incoming connection is "
+"rejected due to connection limits."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/streaming.html:196
+msgid ""
+"Whether to listen only for the streaming protocol.\n"
+"Setting to true will prohibit communication with Destinations earlier "
+"than release 0.7.1\n"
+"(released March 2009). Set to true if running multiple protocols on this "
+"Destination."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/streaming.html:204
+msgid ""
+"(0=noop, 1=disconnect)\n"
+"What to do on an inactivity timeout - do nothing, disconnect, or send a "
+"duplicate ack."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/streaming.html:212
+msgid ""
+"The initial value of the resend delay field in the packet header, times "
+"1000.\n"
+"Not fully implemented; see below."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/streaming.html:217
+msgid ""
+"Initial timeout\n"
+"(if no sharing data available)."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/streaming.html:224
+msgid ""
+"Initial round trip time estimate\n"
+"(if no sharing data available).\n"
+"Disabled as of release 0.9.8; uses actual RTT."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/streaming.html:230
+msgid "if no sharing data available"
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/streaming.html:230
+msgid ""
+"In standard TCP, window sizes are in bytes, while in I2P, window sizes "
+"are in messages."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/streaming.html:242
+msgid ""
+"(0 or negative value means unlimited)\n"
+"This is a total limit for incoming and outgoing combined."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/streaming.html:247
+msgid "Incoming connection limit (per peer; 0 means disabled)"
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/streaming.html:253
+#: i2p2www/pages/site/docs/api/streaming.html:259
+msgid "(per peer; 0 means disabled)"
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/streaming.html:265
+msgid "The MTU in bytes."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/streaming.html:269
+msgid "Maximum number of retransmissions before failure."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/streaming.html:273
+msgid "Incoming connection limit (all peers; 0 means disabled)"
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/streaming.html:279
+#: i2p2www/pages/site/docs/api/streaming.html:286
+msgid ""
+"(all peers; 0 means disabled)\n"
+"Use with caution as exceeding this will disable a server for a long time."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/streaming.html:295
+msgid ""
+"(2=interactive not supported)\n"
+"This doesn't currently do anything, but setting it to a value other than "
+"1 will cause an error."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/streaming.html:300
+msgid "How long to block on read, in milliseconds. Negative means indefinitely."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/streaming.html:304
+msgid ""
+"When we're in slow start, we grow the window size at the rate\n"
+"of 1/(factor). In standard TCP, window sizes are in bytes,\n"
+"while in I2P, window sizes are in messages.\n"
+"A higher number means slower growth."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/streaming.html:311
+#: i2p2www/pages/site/docs/api/streaming.html:318
+#: i2p2www/pages/site/docs/api/streaming.html:325
+msgid ""
+"Ref: RFC 2140. Floating point value.\n"
+"May be set only via context properties, not connection options."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/streaming.html:332
+msgid ""
+"How long to block on write/flush, in milliseconds. Negative means "
+"indefinitely."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/streaming.html:340
+#: i2p2www/pages/site/docs/spec/streaming.html:10
+msgid "Protocol Specification"
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/streaming.html:342
+msgid "See the Streaming Library Specification page."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/streaming.html:346
+msgid "Implementation Details"
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/streaming.html:348
+msgid "Setup"
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/streaming.html:349
+msgid ""
+"The initiator sends a packet with the SYNCHRONIZE flag set. This packet "
+"may contain the initial data as well.\n"
+"The peer replies with a packet with the SYNCHRONIZE flag set. This packet"
+" may contain the initial response data as well."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/streaming.html:354
+msgid ""
+"The initiator may send additional data packets, up to the initial window "
+"size, before receiving the SYNCHRONIZE response.\n"
+"These packets will also have the send Stream ID field set to 0.\n"
+"Recipients must buffer packets received on unknown streams for a short "
+"period of time, as they may\n"
+"arrive out of order, in advance of the SYNCHRONIZE packet."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/streaming.html:361
+msgid "MTU Selection and Negotiation"
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/streaming.html:362
+msgid ""
+"The maximum message size (also called the MTU / MRU) is negotiated to the"
+" lower value supported by\n"
+"the two peers. As tunnel messages are padded to 1KB, a poor MTU selection"
+" will lead to\n"
+"a large amount of overhead.\n"
+"The MTU is specified by the option i2p.streaming.maxMessageSize.\n"
+"The current default MTU of 1730 was chosen to fit precisely into two 1K "
+"I2NP tunnel messages,\n"
+"including overhead for the typical case."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/streaming.html:371
+msgid ""
+"The first message in a connection includes a 387 byte (typical) "
+"Destination added by the streaming layer,\n"
+"and usually a 898 byte (typical) LeaseSet, and Session keys, bundled in "
+"the Garlic message by the router.\n"
+"(The LeaseSet and Session Keys will not be bundled if an ElGamal Session "
+"was previously established).\n"
+"Therefore, the goal of fitting a complete HTTP request in a single 1KB "
+"I2NP message is not always attainable.\n"
+"However, the selection of the MTU, together with careful implementation "
+"of fragmentation\n"
+"and batching strategies in the tunnel gateway processor, are important "
+"factors in network bandwidth,\n"
+"latency, reliability, and efficiency, especially for long-lived "
+"connections."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/streaming.html:382
+#, python-format
+msgid ""
+"Data integrity is assured by the gzip CRC-32 checksum implemented in\n"
+"the I2CP layer.\n"
+"There is no checksum field in the streaming protocol."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/streaming.html:390
+#, python-format
+msgid ""
+"Each packet is sent through I2P as a single message (or as an individual "
+"clove in a\n"
+"Garlic Message). Message encapsulation "
+"is implemented\n"
+"in the underlying I2CP, I2NP, and\n"
+"tunnel message layers. There is no "
+"packet delimiter\n"
+"mechanism or payload length field in the streaming protocol."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/streaming.html:400
+msgid "Windowing"
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/streaming.html:401
+msgid ""
+"The streaming lib uses standard slow-start (exponential window growth) "
+"and congestion avoidance (linear window growth)\n"
+"phases, with exponential backoff.\n"
+"Windowing and acknowledgments use packet count, not byte count."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/streaming.html:408
+msgid "Close"
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/streaming.html:409
+msgid ""
+"Any packet, including one with the SYNCHRONIZE flag set, may have the "
+"CLOSE flag sent as well.\n"
+"The connection is not closed until the peer responds with the CLOSE flag."
+"\n"
+"CLOSE packets may contain data as well."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/streaming.html:416
+msgid "Control Block Sharing"
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/streaming.html:417
+msgid ""
+"The streaming lib supports \"TCP\" Control Block sharing.\n"
+"This shares three important streaming lib parameters\n"
+"(window size, round trip time, round trip time variance)\n"
+"across connections to the same remote peer.\n"
+"This is used for \"temporal\" sharing at connection open/close time,\n"
+"not \"ensemble\" sharing during a connection (See\n"
+"RFC 2140).\n"
+"There is a separate share per ConnectionManager (i.e. per local "
+"Destination)\n"
+"so that there is no information leakage to other Destinations on the\n"
+"same router.\n"
+"The share data for a given peer expires after a few minutes.\n"
+"The following Control Block Sharing parameters can be set per router:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/streaming.html:438
+msgid "Other Parameters"
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/streaming.html:439
+msgid ""
+"The following parameters are hardcoded, but may be of interest for "
+"analysis:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/streaming.html:458
+#: i2p2www/pages/site/docs/how/network-database.html:829
+msgid "History"
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/streaming.html:459
+msgid ""
+"The streaming library has grown organically for I2P - first mihi "
+"implemented the\n"
+"\"mini streaming library\" as part of I2PTunnel, which was limited to a "
+"window\n"
+"size of 1 message (requiring an ACK before sending the next one), and "
+"then it was\n"
+"refactored out into a generic streaming interface (mirroring TCP sockets)"
+" and the\n"
+"full streaming implementation was deployed with a sliding window protocol"
+" and \n"
+"optimizations to take into account the high bandwidth x delay product. "
+"Individual\n"
+"streams may adjust the maximum packet size and other options. The default"
+"\n"
+"message size is selected to fit precisely in two 1K I2NP tunnel messages,"
+"\n"
+"and is a reasonable tradeoff between the bandwidth costs of \n"
+"retransmitting lost messages, and the latency and overhead of multiple "
+"messages."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/streaming.html:473
+#: i2p2www/pages/site/docs/how/elgamal-aes.html:331
+#: i2p2www/pages/site/docs/how/garlic-routing.html:242
+#: i2p2www/pages/site/docs/how/network-database.html:834
+#: i2p2www/pages/site/docs/how/peer-selection.html:265
+#: i2p2www/pages/site/docs/how/tunnel-routing.html:255
+#: i2p2www/pages/site/docs/protocol/i2cp.html:646
+#: i2p2www/pages/site/docs/protocol/i2np.html:227
+#: i2p2www/pages/site/docs/spec/updates.html:280
+#: i2p2www/pages/site/docs/transport/ntcp.html:443
+#: i2p2www/pages/site/docs/transport/ssu.html:502
+#: i2p2www/pages/site/docs/tunnels/implementation.html:503
+msgid "Future Work"
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/streaming.html:474
+msgid ""
+"The behavior of the streaming library has a profound impact on\n"
+"application-level performance, and as such, is an important\n"
+"area for further analysis."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/streaming.html:480
+msgid "Additional tuning of the streaming lib parameters may be necessary."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/streaming.html:483
+#, python-format
+msgid ""
+"Another area for research is the interaction of the streaming lib with "
+"the\n"
+"NTCP and SSU transport layers.\n"
+"See the NTCP discussion page for details."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/streaming.html:488
+msgid ""
+"The interaction of the routing algorithms with the streaming lib strongly"
+" affects performance.\n"
+"In particular, random distribution of messages to multiple tunnels in a "
+"pool\n"
+"leads to a high degree of out-of-order delivery which results in smaller "
+"window\n"
+"sizes than would otherwise be the case. The router currently routes \n"
+"messages for a single from/to destination pair through a consistent set \n"
+"of tunnels, until tunnel expiration or delivery failure. The router's \n"
+"failure and tunnel selection algorithms should be reviewed for possible \n"
+"improvements."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/streaming.html:498
+msgid "The data in the first SYN packet may exceed the receiver's MTU."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/streaming.html:501
+msgid "The DELAY_REQUESTED field could be used more."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/streaming.html:504
+msgid ""
+"Duplicate initial SYNCHRONIZE packets on short-lived streams may not be "
+"recognized and removed."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/streaming.html:507
+msgid "Don't send the MTU in a retransmission."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/streaming.html:510
+msgid ""
+"Data is sent along unless the outbound window is full.\n"
+"(i.e. no-Nagle or TCP_NODELAY)\n"
+"Probably should have a configuration option for this."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/streaming.html:515
+msgid ""
+"zzz has added debug code to the streaming library to log packets in a "
+"wireshark-compatible\n"
+"(pcap) format; Use this to further analyze performance.\n"
+"The format may require enhancement to map more streaming lib parameters "
+"to TCP fields."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/streaming.html:520
+msgid ""
+"There are proposals to replace the streaming lib with standard TCP\n"
+"(or perhaps a null layer together with raw sockets).\n"
+"This would unfortunately be incompatible with the streaming lib\n"
+"but it would be good to compare the performance of the two."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/bittorrent.html:3
+#: i2p2www/pages/site/docs/spec/configuration.html:3
+msgid "September 2012"
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/bittorrent.html:7
+msgid ""
+"There are several bittorrent clients and trackers on I2P.\n"
+"As I2P addressing uses a Destination instead of an IP and port, minor\n"
+"changes are required to tracker and client software for operation on I2P."
+"\n"
+"These changes are specified below.\n"
+"Note carefully the guidelines for compatibility with older I2P clients "
+"and trackers."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/bittorrent.html:15
+msgid ""
+"This page specifies protocol details common to all clients and trackers.\n"
+"Specific clients and trackers may implement other unique features or "
+"protocols."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/bittorrent.html:20
+msgid "We welcome additional ports of client and tracker software to I2P."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/bittorrent.html:26
+msgid "Announces"
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/bittorrent.html:27
+msgid ""
+"Clients generally include a fake port=6881 parameter in the announce, for"
+" compatibility with older trackers.\n"
+"Trackers may ignore the port parameter, and should not require it."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/bittorrent.html:32
+#, python-format
+msgid ""
+"The ip parameter is the base 64 of the client's\n"
+"Destination,\n"
+"using the I2P Base 64 alphabet [A-Z][a-z][0-9]-~.\n"
+"Destinations\n"
+"are 387+ bytes, so the Base 64 is 516+ bytes.\n"
+"Clients generally append \".i2p\" to the Base 64 Destination for "
+"compatibility with older trackers.\n"
+"Trackers should not require an appended \".i2p\"."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/bittorrent.html:42
+msgid "Other parameters are the same as in standard bittorrent."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/bittorrent.html:46
+msgid ""
+"While all current Destinations for clients are exactly 387 bytes, a "
+"tracker should not\n"
+"presume that will always be so. A reasonable maximum to assume, for now, "
+"is 475 bytes.\n"
+"As the tracker must decode the Base64 to deliver compact responses (see "
+"below),\n"
+"the tracker should probably decode and reject bad Base64 when announced."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/bittorrent.html:53
+msgid ""
+"The default response type is non-compact. Clients may request a compact "
+"response with\n"
+"the parameter compact=1. A tracker may, but is not required to, return\n"
+"a compact response when requested."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/bittorrent.html:59
+msgid ""
+"Developers of new I2P clients\n"
+"are strongly encouraged to implemenent announces over their own tunnel "
+"rather than\n"
+"the HTTP client proxy at port 4444. Doing so is both more efficient and "
+"it allows\n"
+"destination enforcement by the tracker (see below)."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/bittorrent.html:66
+msgid ""
+"There are no known I2P clients or trackers that currently support UDP "
+"announce/responses."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/bittorrent.html:71
+msgid "Non-Compact Tracker Responses"
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/bittorrent.html:72
+msgid ""
+"The non-compact response is just as in standard bittorrent, with an I2P "
+"\"ip\"."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/bittorrent.html:76
+msgid ""
+"Trackers generally include a fake port key, or use the port from the "
+"announce, for compatibility with older clients.\n"
+"Clients must ignore the port parameter, and should not require it."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/bittorrent.html:81
+#, python-format
+msgid ""
+"The value of the ip key is the base 64 of the client's\n"
+"Destination, as "
+"described above.\n"
+"Trackers generally append \".i2p\" to the Base 64 Destination if it "
+"wasn't in the announce ip, for compatibility with older clients.\n"
+"Clients should not require an appended \".i2p\" in the responses."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/bittorrent.html:88
+msgid "Other response keys and values are the same as in standard bittorrent."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/bittorrent.html:94
+msgid "Compact Tracker Responses"
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/bittorrent.html:95
+#, python-format
+msgid ""
+"In the compact response, the value of the \"peers\" dictionary key is a "
+"single byte string,\n"
+"whose length is a multiple of 32 bytes.\n"
+"This string contains the concatenated\n"
+"32-byte SHA-256 Hashes\n"
+"of the binary\n"
+"Destinations\n"
+"of the peers.\n"
+"This hash must be computed by the tracker, unless destination enforcement"
+"\n"
+"(see below) is used, in which case the hash delivered in the X-I2P-"
+"DestHash\n"
+"or X-I2P-DestB32 HTTP headers may be converted to binary and stored.\n"
+"The peers key may be absent, or the peers value may be zero-length."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/bittorrent.html:109
+msgid ""
+"While compact response support is optional for both clients and trackers,"
+" it is highly\n"
+"recommended as it reduces the nominal response size by over 90%."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/bittorrent.html:116
+msgid "Destination Enforcement"
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/bittorrent.html:117
+#, python-format
+msgid ""
+"Some, but not all, I2P bittorrent clients announce over their own "
+"tunnels.\n"
+"Trackers may choose to prevent spoofing by requiring this, and verifying "
+"the\n"
+"client's\n"
+"Destination\n"
+"using HTTP headers added by the I2PTunnel HTTP Server tunnel.\n"
+"The headers are X-I2P-DestHash, X-I2P-DestB64, and X-I2P-DestB32, which "
+"are\n"
+"different formats for the same information.\n"
+"These headers cannot be spoofed by the client.\n"
+"A tracker enforcing destinations need not require the ip announce "
+"parameter at all."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/bittorrent.html:129
+msgid ""
+"As several clients use the HTTP proxy instead of their own tunnel for "
+"announces,\n"
+"destination enforcement will prevent usage by those clients unless or "
+"until\n"
+"those clients are converted to announcing over their own tunnel."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/bittorrent.html:135
+msgid ""
+"Unfortunately, as the network grows, so will the amount of maliciousness,"
+"\n"
+"so we expect that all trackers will eventually enforce destinations.\n"
+"Both tracker and client developers should anticipate it."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/bittorrent.html:143
+msgid "Announce Host Names"
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/bittorrent.html:144
+#, python-format
+msgid ""
+"Announce URL host names in torrent files generally follow the\n"
+"I2P naming standards.\n"
+"In addition to host names from address books and \".b32.i2p\" Base 32 "
+"hostnames,\n"
+"the full Base 64 Destination (with [or without?] \".i2p\" appended) "
+"should be supported.\n"
+"Non-open trackers should recognize their own host name in any of these "
+"formats."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/bittorrent.html:152
+msgid ""
+"To preserve anonymity,\n"
+"clients should generally ignore non-I2P announce URLs in torrent files."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/bittorrent.html:159
+msgid "Client Connections"
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/bittorrent.html:160
+msgid ""
+"Client-to-client connections use the standard protocol over TCP.\n"
+"There are no known I2P clients that currently support uTP communication."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/bittorrent.html:165
+#, python-format
+msgid ""
+"I2P uses 387+ byte Destinations\n"
+"for addresses, as explained above."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/bittorrent.html:170
+msgid ""
+"If the client has only the hash of the destination (such as from a "
+"compact response or PEX), it must perform a lookup\n"
+"by encoding it with Base 32, appending \".b32.i2p\", and querying the "
+"Naming Service,\n"
+"which will return the full Destination if available."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/bittorrent.html:176
+msgid ""
+"If the client has a peer's full Destination it received in a non-compact "
+"response, it should use it\n"
+"directly in the connection setup.\n"
+"Do not convert a Destination back to a Base 32 hash for lookup, this is "
+"quite inefficient."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/bittorrent.html:183
+msgid "Cross-Network Prevention"
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/bittorrent.html:184
+msgid ""
+"To preserve anonymity,\n"
+"I2P bittorrent clients generally do not support non-I2P announces or peer"
+" connections.\n"
+"I2P HTTP outproxies often block announces.\n"
+"There are no known SOCKS outproxies supporting bittorrent traffic."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/bittorrent.html:191
+msgid ""
+"To prevent usage by non-I2P clients via an HTTP inproxy, I2P trackers "
+"often\n"
+"block accesses or announces that contain an X-Forwarded-For HTTP header.\n"
+"Trackers should reject standard network announces with IPv4 or IPv6 IPs, "
+"and not deliver them in responses."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/bittorrent.html:200
+#, python-format
+msgid ""
+"I2P PEX is based on ut_pex.\n"
+"As there does not appear to be a formal specification of ut_pex "
+"available,\n"
+"it may be necessary to review the libtorrent source for assistance.\n"
+"It is an extension message, identified as \"i2p_pex\" in\n"
+"the extension "
+"handshake.\n"
+"It contains a bencoded dictionary with up to 3 keys, \"added\", "
+"\"added.f\", and \"dropped\".\n"
+"The added and dropped values are each a single byte string, whose length "
+"is a multiple of 32 bytes.\n"
+"These byte strings are the concatenated SHA-256 Hashes of the binary\n"
+"Destinations\n"
+"of the peers.\n"
+"This is the same format as the peers dictionary value in the i2p compact "
+"response format specified above.\n"
+"The added.f value, if present, is the same as in ut_pex."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/bittorrent.html:218
+msgid ""
+"DHT support is included in the i2psnark client as of version 0.9.2.\n"
+"Preliminary differences from\n"
+"BEP 5\n"
+"are described below, and are subject to change.\n"
+"Contact the I2P developers if you wish to develop a client supporting DHT."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/bittorrent.html:226
+msgid ""
+"Unlike standard DHT, I2P DHT does not use a bit in the options handshake,"
+" or the PORT message.\n"
+"It is advertised with an extension message, identified as \"i2p_dht\" in\n"
+"the extension "
+"handshake.\n"
+"It contains a bencoded dictionary with two keys, \"port\" and \"rport\", "
+"both integers."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/bittorrent.html:233
+msgid ""
+"The UDP (datagram) port listed in the compact node info is used\n"
+"to receive repliable (signed) datagrams.\n"
+"This is used for queries, except for announces.\n"
+"We call this the \"query port\".\n"
+"This is the \"port\" value from the extension message.\n"
+"Queries use I2CP protocol number 17."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/bittorrent.html:242
+msgid ""
+"In addition to that UDP port, we use a second datagram\n"
+"port equal to the query port + 1. This is used to receive\n"
+"unsigned (raw) datagrams for replies, errors, and announces.\n"
+"This port provides increased efficiency since replies\n"
+"contain tokens sent in the query, and need not be signed.\n"
+"We call this the \"response port\".\n"
+"This is the \"rport\" value from the extension message.\n"
+"It must be 1 + the query port.\n"
+"Responses and announces use I2CP protocol number 18."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/bittorrent.html:254
+msgid ""
+"Compact peer info is 32 bytes (32 byte SHA256 Hash)\n"
+"instead of 4 byte IP + 2 byte port. There is no peer port.\n"
+"In a response, the \"values\" key is a list of strings, each containing a"
+" single compact peer info."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/bittorrent.html:260
+msgid ""
+"Compact node info is 54 bytes (20 byte SHA1 Hash + 32 byte SHA256 Hash + "
+"2 byte port)\n"
+"instead of 20 byte SHA1 Hash + 4 byte IP + 2 byte port.\n"
+"In a response, the \"nodes\" key is a\n"
+"single byte string with concatenated compact node info."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/bittorrent.html:267
+msgid ""
+"Secure node ID requirement: To make various DHT attacks more difficult,\n"
+"the first 4 bytes of the Node ID must match the first 4 bytes of the "
+"destination Hash,\n"
+"and the next two bytes of the Node ID must match the next two bytes of "
+"the\n"
+"destination hash exclusive-ORed with the port."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/bittorrent.html:274
+msgid ""
+"In a torrent file,\n"
+"the trackerless torrent dictionary \"nodes\" key is TBD.\n"
+"It could be a list of\n"
+"32 byte binary strings (SHA256 Hashes) instead of a list of lists\n"
+"containing a host string and a port integer.\n"
+"Alternatives: A single byte string with concatenated hashes,\n"
+"or a list of strings alone."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/bittorrent.html:285
+#: i2p2www/pages/site/docs/how/intro.html:187
+msgid "Additional Information"
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/bittorrent.html:287
+#, python-format
+msgid ""
+"I2P bittorrent standards are generally discussed on %(zzz)s."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/bittorrent.html:290
+#, python-format
+msgid ""
+"A chart of current tracker software capabilities is also available there."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/bittorrent.html:293
+#, python-format
+msgid ""
+"The\n"
+"I2P bittorrent FAQ"
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/bittorrent.html:297
+#, python-format
+msgid "DHT on I2P discussion"
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:2
+#: i2p2www/pages/site/docs/applications/supported.html:5
+msgid "Supported Applications"
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:9
+#: i2p2www/pages/site/docs/applications/supported.html:186
+msgid "Blogging, Forums, and Wikis"
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:11
+#: i2p2www/pages/site/docs/applications/supported.html:232
+msgid "Decentralized File Storage"
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:14
+#: i2p2www/pages/site/docs/applications/supported.html:244
+msgid "Development Tools"
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:17
+#: i2p2www/pages/site/docs/applications/supported.html:246
+msgid "Version control"
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:21
+#: i2p2www/pages/site/docs/applications/supported.html:265
+msgid "Domain Naming"
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:23
+#: i2p2www/pages/site/docs/applications/supported.html:283
+msgid "Email"
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:26
+#: i2p2www/pages/site/docs/applications/supported.html:328
+msgid "File Sharing"
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:29
+#: i2p2www/pages/site/docs/applications/supported.html:330
+msgid "BitTorrent clients"
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:31
+#: i2p2www/pages/site/docs/applications/supported.html:372
+msgid "BitTorrent trackers and indexers"
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:40
+#: i2p2www/pages/site/docs/applications/supported.html:439
+msgid "Network Administration"
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:43
+#: i2p2www/pages/site/docs/applications/supported.html:441
+msgid "General-purpose socket utilities"
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:50
+#: i2p2www/pages/site/docs/applications/supported.html:482
+msgid "Real-time Chat"
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:53
+#: i2p2www/pages/site/docs/applications/supported.html:484
+msgid "Instant messaging clients"
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:55
+#: i2p2www/pages/site/docs/applications/supported.html:494
+msgid "IRC clients"
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:57
+#: i2p2www/pages/site/docs/applications/supported.html:545
+msgid "IRC servers"
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:62
+#: i2p2www/pages/site/docs/applications/supported.html:561
+msgid "Web Browsing"
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:65
+#: i2p2www/pages/site/docs/applications/supported.html:563
+msgid "Anonymous websites"
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:67
+#: i2p2www/pages/site/docs/applications/supported.html:612
+msgid "Proxy software"
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:69
+#: i2p2www/pages/site/docs/applications/supported.html:637
+msgid "Inproxies"
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:71
+#: i2p2www/pages/site/docs/applications/supported.html:669
+msgid "Outproxies"
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:76
+#: i2p2www/pages/site/docs/applications/supported.html:683
+msgid "Website Hosting"
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:79
+#: i2p2www/pages/site/docs/applications/supported.html:698
+msgid "Web servers"
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:85
+#, python-format
+msgid ""
+"This is intended to be a comprehensive listing of applications used with\n"
+"I2P. If you know of something that's missing please submit a ticket on\n"
+"Trac, and be sure to select the\n"
+"“www” component in the submission form."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:92
+msgid ""
+"\n"
+"Supported applications are tagged with one or more of the following:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:97
+#: i2p2www/pages/site/docs/applications/supported.html:279
+#: i2p2www/pages/site/docs/applications/supported.html:311
+#: i2p2www/pages/site/docs/applications/supported.html:336
+#: i2p2www/pages/site/docs/applications/supported.html:695
+msgid "bundled"
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:100
+msgid ""
+"Bundled application — I2P ships with a few officially\n"
+"supported applications that let new users take immediate advantage of\n"
+"some of I2P's more useful capabilities."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:107
+#: i2p2www/pages/site/docs/applications/supported.html:195
+#: i2p2www/pages/site/docs/applications/supported.html:208
+#: i2p2www/pages/site/docs/applications/supported.html:220
+#: i2p2www/pages/site/docs/applications/supported.html:228
+#: i2p2www/pages/site/docs/applications/supported.html:241
+#: i2p2www/pages/site/docs/applications/supported.html:292
+#: i2p2www/pages/site/docs/applications/supported.html:404
+#: i2p2www/pages/site/docs/applications/supported.html:426
+#: i2p2www/pages/site/docs/applications/supported.html:435
+#: i2p2www/pages/site/docs/applications/supported.html:523
+msgid "plugin"
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:110
+#, python-format
+msgid ""
+"Third-party plugin — I2P's plugin system provides convenient\n"
+"deployment of I2P-enabled applications and allows tighter integration\n"
+"with the router. Plugins are [reviewed by the community](http://%(plugins)s) to identify security and\n"
+"anonymity issues."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:121
+#: i2p2www/pages/site/docs/applications/supported.html:220
+#: i2p2www/pages/site/docs/applications/supported.html:228
+#: i2p2www/pages/site/docs/applications/supported.html:241
+#: i2p2www/pages/site/docs/applications/supported.html:252
+#: i2p2www/pages/site/docs/applications/supported.html:261
+#: i2p2www/pages/site/docs/applications/supported.html:324
+#: i2p2www/pages/site/docs/applications/supported.html:342
+#: i2p2www/pages/site/docs/applications/supported.html:353
+#: i2p2www/pages/site/docs/applications/supported.html:368
+#: i2p2www/pages/site/docs/applications/supported.html:414
+#: i2p2www/pages/site/docs/applications/supported.html:426
+#: i2p2www/pages/site/docs/applications/supported.html:435
+#: i2p2www/pages/site/docs/applications/supported.html:450
+#: i2p2www/pages/site/docs/applications/supported.html:456
+#: i2p2www/pages/site/docs/applications/supported.html:462
+#: i2p2www/pages/site/docs/applications/supported.html:472
+#: i2p2www/pages/site/docs/applications/supported.html:478
+#: i2p2www/pages/site/docs/applications/supported.html:490
+#: i2p2www/pages/site/docs/applications/supported.html:523
+#: i2p2www/pages/site/docs/applications/supported.html:529
+#: i2p2www/pages/site/docs/applications/supported.html:535
+#: i2p2www/pages/site/docs/applications/supported.html:541
+#: i2p2www/pages/site/docs/applications/supported.html:618
+#: i2p2www/pages/site/docs/applications/supported.html:627
+#: i2p2www/pages/site/docs/applications/supported.html:633
+#: i2p2www/pages/site/docs/applications/supported.html:695
+#: i2p2www/pages/site/docs/applications/supported.html:710
+#: i2p2www/pages/site/docs/applications/supported.html:716
+#: i2p2www/pages/site/docs/applications/supported.html:722
+#: i2p2www/pages/site/docs/applications/supported.html:728
+msgid "standalone"
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:121
+#: i2p2www/pages/site/docs/applications/supported.html:195
+#: i2p2www/pages/site/docs/applications/supported.html:202
+#: i2p2www/pages/site/docs/applications/supported.html:208
+#: i2p2www/pages/site/docs/applications/supported.html:214
+#: i2p2www/pages/site/docs/applications/supported.html:362
+#: i2p2www/pages/site/docs/applications/supported.html:386
+#: i2p2www/pages/site/docs/applications/supported.html:395
+#: i2p2www/pages/site/docs/applications/supported.html:551
+#: i2p2www/pages/site/docs/applications/supported.html:557
+msgid "standalone/mod"
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:124
+msgid ""
+"Third-party standalone application — Many standard network\n"
+"applications only require careful setup and configuration to communicate\n"
+"anonymously over I2P. These are tagged with standalone. Some\n"
+"applications, tagged with standalone/mod, require patching to\n"
+"function properly over I2P or to prevent inadvertent disclosure of\n"
+"identifying information such as the user's hostname or external IP\n"
+"address."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:135
+#: i2p2www/pages/site/docs/applications/supported.html:302
+#: i2p2www/pages/site/docs/applications/supported.html:571
+#: i2p2www/pages/site/docs/applications/supported.html:581
+#: i2p2www/pages/site/docs/applications/supported.html:590
+#: i2p2www/pages/site/docs/applications/supported.html:596
+#: i2p2www/pages/site/docs/applications/supported.html:602
+#: i2p2www/pages/site/docs/applications/supported.html:608
+#: i2p2www/pages/site/docs/applications/supported.html:649
+#: i2p2www/pages/site/docs/applications/supported.html:657
+#: i2p2www/pages/site/docs/applications/supported.html:665
+#: i2p2www/pages/site/docs/applications/supported.html:679
+msgid "service"
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:138
+msgid ""
+"Third-party essential network service — Services which on\n"
+"the I2P network are analogous to those provided on the public Internet\n"
+"by hosting providers, ISPs, and Google: eepsite indexes and jump\n"
+"services, search engines, email, DNS-style name services, hosting,\n"
+"proxies, etc. These services focus on boosting the usefulness of the\n"
+"network as a whole, and making network content more discoverable."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:148
+#: i2p2www/pages/site/docs/applications/supported.html:220
+#: i2p2www/pages/site/docs/applications/supported.html:368
+msgid "unmaintained"
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:151
+msgid ""
+"Unmaintained — This is used to tag plugins, applications,\n"
+"and services which appear to be unmaintained and may be removed from\n"
+"this listing in the future."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:159
+#, python-format
+msgid ""
+"Warning: Using an application, plugin, or service with I2P\n"
+"doesn't automatically protect your anonymity. I2P is merely a set of "
+"tools\n"
+"which can help you mitigate certain identified\n"
+"threats to anonymity. We do not and cannot make any guarantees about "
+"the\n"
+"safety of the applications, plugins, and services listed below. Most\n"
+"applications and plugins must be properly configured, and some will need "
+"to\n"
+"be patched — and even then your anonymity might not be assured. "
+"Similarly,\n"
+"services could put your anonymity at risk, either by design or through\n"
+"carelessness on their part or your own."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:171
+msgid ""
+"If you have doubts about the suitability of an application,\n"
+"plugin, or service for use with I2P, you are urged to inquire about "
+"privacy\n"
+"issues with its maintainers, to search its mailing lists and bug tracker "
+"if\n"
+"one exists, and consult trusted, knowledgeable members of the I2P\n"
+"community."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:179
+msgid ""
+"Take responsibility for your own anonymity and safety — always\n"
+"seek expert advice, educate yourself, practice good judgment, be mindful "
+"of\n"
+"disclosing personally identifying information, and don't take\n"
+"shortcuts."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:201
+msgid "Lightweight forum software."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:207
+msgid "Another lightweight blogging platform."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:213
+msgid "Most popular open source forum software."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:219
+msgid "Distributed forums software, originally developed by jrandom."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:224
+#, python-format
+msgid ""
+"A Java-based MediaWiki clone. No external database needed.\n"
+"Plugin available here."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:236
+#, python-format
+msgid ""
+"Port of the Tahoe-"
+"LAFS\n"
+"distributed file system to the I2P network. Controller plugin here."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:251
+msgid "Most popular distributed version control system."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:257
+#, python-format
+msgid ""
+"Another distributed version control system. Currently\n"
+"used in I2P development."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:269
+#, python-format
+msgid ""
+"Provides management of addressbooks, which are part of a simple,\n"
+"user-controlled I2P naming system somewhat\n"
+"analogous to the Internet's Domain Name System (DNS). Addressbooks map\n"
+"Base64 destinations to short, usually human-readable “domain” names "
+"ending\n"
+"with a .i2p suffix which the I2P router's HTTP client can resolve back to"
+"\n"
+"Base64 addresses. (Note: While Base64 destinations are globally\n"
+"unique, addressbook “domain” names only resolve to unique destinations\n"
+"locally.)"
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:288
+msgid ""
+"Serverless peer-to-peer email application using a distributed hash table\n"
+"(DHT) for secure mail storage."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:297
+msgid ""
+"Provides email service within the I2P network via @mail.i2p addresses,\n"
+"and email gateway service between the I2P network and the public Internet"
+"\n"
+"via @i2pmail.org addresses. One of the oldest continuous services on I2P."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:307
+msgid ""
+"Simple web browser-based email interface. Configured to use Postman's\n"
+"email service by default."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:316
+#, python-format
+msgid ""
+"Can be configured to use Postman's email service. See\n"
+"this comparison of MUAs,\n"
+"and configuration settings for\n"
+"SMTP and POP3."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:335
+msgid "I2P's integrated BitTorrent client."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:341
+msgid "Modified version of I2PSnark."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:347
+msgid ""
+"\n"
+"A fork of rufus that uses the Basic Open Bridge (BOB) and has many\n"
+"improvements, including using the latest wxwidgets and python. It also\n"
+"supports use of seedless if installed for trackerless torrents and\n"
+"magnet-link like fetching of torrents within I2P.\n"
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:358
+msgid ""
+"Clean, full-featured cross-platform BitTorrent client with official\n"
+"ports for several GUI toolkits."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:367
+msgid "Has a plugin providing I2P support."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:374
+#, python-format
+msgid ""
+"For a detailed feature comparison of I2P-enabled trackers/indexers, see\n"
+"here."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:382
+msgid ""
+"The code that powered one of the first major tracker/indexer sites on the"
+"\n"
+"Internet. Patched for I2P."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:391
+#, python-format
+msgid ""
+"Lightweight tracker/indexer. I2P mod available in the i2p.opentracker\n"
+"branch of the I2P Monotone repository."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:400
+#, python-format
+msgid ""
+"zzz's Java-based open tracker. More info\n"
+"here."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:413
+msgid "I2P port of the aMule ED2K client."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:422
+#, python-format
+msgid ""
+"Port of the Phex Gnutella "
+"client. Website\n"
+"for plugin version here."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:431
+#, python-format
+msgid ""
+"Cache for Gnutella peers on I2P. Website for plugin version\n"
+"here."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:446
+msgid ""
+"Unix standard tool for socket relaying. Several clones, ports, and forks\n"
+"have appeared over the years."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:455
+msgid "Like netcat but more powerful."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:461
+msgid ""
+"Proxy providing simple, transparent SOCKS-ification of network "
+"applications."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:471
+msgid ""
+"Most popular implementation of the Secure Shell (SSH) protocol and "
+"related tools."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:477
+msgid "Open source Secure Shell (SSH) client for Windows."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:489
+msgid "IM client with multiple incarnations."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:496
+msgid ""
+"Many IRC clients leak identifying information to servers or other\n"
+"clients, so I2P's IRC and SOCKS IRC client tunnels filter certain inbound"
+"\n"
+"and outbound messages to scrub data such as LAN IP addresses, external IP"
+"\n"
+"addresses, local hostnames, and the name and version of the IRC client. "
+"Two\n"
+"message types in particular, DCC and CTCP, can't be sufficiently "
+"anonymized\n"
+"without changes to the protocols or to IRC client/server code, so they "
+"are\n"
+"completely blocked, except for CTCP ACTION (the message emitted by the\n"
+"/me command) which isn't inherently dangerous."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:507
+msgid ""
+"I2P's IRC filtering may not cover every possible leak — users should also"
+"\n"
+"check if their client is sending their real name or local username. "
+"Packet\n"
+"sniffers such as Wireshark are\n"
+"useful here. Eliminating remaining leaks may be as simple as changing the"
+"\n"
+"client's default configuration. If that doesn't help, inform the I2P\n"
+"developers; they may be able to solve it via additional filtering."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:519
+#, python-format
+msgid ""
+"Small Java-based IRC client. Plugin available here."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:528
+msgid "Cross-platform graphical IRC client."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:534
+msgid "Unixy terminal-based IRC client."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:540
+msgid "Another Unixy terminal-based IRC client."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:550
+msgid "IRC server developed from scratch."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:556
+msgid "Most popular IRC server."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:568
+msgid ""
+"Any website hosted anonymously on I2P, reachable through the I2P router's"
+" HTTP proxy."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:576
+msgid ""
+"Distributed anonymous websites hosted\n"
+"using Tahoe-LAFS-I2P, currently only reachable with Tahoe-LAFS-I2P\n"
+"clients or through the Tahoe-LAFS-I2P HTTP proxy."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:586
+#, python-format
+msgid ""
+"Website for sponge's jump service.\n"
+"Source code available."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:595
+msgid "Another jump service."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:601
+msgid "Dynamically updated eepsite index."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:607
+#, python-format
+msgid "Website for zzz's jump service."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:617
+msgid "SOCKS-enabled caching web proxy with basic filtering capabilities."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:623
+msgid ""
+"Privacy-focused non-caching web proxy with advanced filtering\n"
+"capabilities. Excels at removing ads and other junk."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:632
+msgid "Venerable caching web proxy."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:639
+msgid "Gateways allowing users on the public Internet to access eepsites."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:646
+#, python-format
+msgid "tino's inproxy on the public Internet."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:654
+#: i2p2www/pages/site/docs/applications/supported.html:662
+msgid "Another inproxy on the public Internet."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:671
+msgid ""
+"Gateways allowing I2P users to access content hosted on the public "
+"Internet."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:678
+msgid "Publicly advertised outproxy running Squid, located in Germany."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:688
+msgid ""
+"Lightweight web server and Java servlet container. I2P is tightly\n"
+"integrated with a bundled copy of Jetty which by default is configured to"
+"\n"
+"host the user's eepsite. The "
+"bundled\n"
+"Jetty also serves the I2P router console and web applications bundled "
+"with\n"
+"I2P."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:700
+msgid ""
+"In addition to Jetty, any web server should function over I2P without\n"
+"modification so long as it's HTTP-compliant. Some web servers known to\n"
+"currently serve content on the I2P network are:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:709
+msgid "Most popular web server on the public WWW."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:715
+msgid "Web server and Java servlet container. More features than Jetty."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:721
+msgid "Fast lightweight web server."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:727
+msgid "High-performance lightweight web server."
+msgstr ""
+
+#: i2p2www/pages/site/docs/discussions/naming.html:2
+msgid "Naming discussion"
+msgstr ""
+
+#: i2p2www/pages/site/docs/discussions/naming.html:4
+#, python-format
+msgid ""
+"NOTE: The following is a discussion of the reasons behind the I2P naming "
+"system,\n"
+"common arguments and possible alternatives.\n"
+"See the naming page for current documentation."
+msgstr ""
+
+#: i2p2www/pages/site/docs/discussions/naming.html:10
+msgid "Discarded alternatives"
+msgstr ""
+
+#: i2p2www/pages/site/docs/discussions/naming.html:12
+msgid ""
+"Naming within I2P has been an oft-debated topic since the very beginning "
+"with\n"
+"advocates across the spectrum of possibilities. However, given I2P's "
+"inherent\n"
+"demand for secure communication and decentralized operation, the "
+"traditional\n"
+"DNS-style naming system is clearly out, as are \"majority rules\" voting "
+"systems."
+msgstr ""
+
+#: i2p2www/pages/site/docs/discussions/naming.html:19
+msgid ""
+"I2P does not promote the use of DNS-like services though, as the damage "
+"done\n"
+"by hijacking a site can be tremendous - and insecure destinations have no"
+"\n"
+"value. DNSsec itself still falls back on registrars and certificate "
+"authorities,\n"
+"while with I2P, requests sent to a destination cannot be intercepted or "
+"the reply\n"
+"spoofed, as they are encrypted to the destination's public keys, and a "
+"destination\n"
+"itself is just a pair of public keys and a certificate. DNS-style "
+"systems on the\n"
+"other hand allow any of the name servers on the lookup path to mount "
+"simple denial\n"
+"of service and spoofing attacks. Adding on a certificate authenticating "
+"the\n"
+"responses as signed by some centralized certificate authority would "
+"address many of\n"
+"the hostile nameserver issues but would leave open replay attacks as well"
+" as \n"
+"hostile certificate authority attacks."
+msgstr ""
+
+#: i2p2www/pages/site/docs/discussions/naming.html:33
+msgid ""
+"Voting style naming is dangerous as well, especially given the "
+"effectiveness of\n"
+"Sybil attacks in anonymous systems - the attacker can simply create an "
+"arbitrarily\n"
+"high number of peers and \"vote\" with each to take over a given name. "
+"Proof-of-work\n"
+"methods can be used to make identity non-free, but as the network grows "
+"the load\n"
+"required to contact everyone to conduct online voting is implausible, or "
+"if the\n"
+"full network is not queried, different sets of answers may be reachable."
+msgstr ""
+
+#: i2p2www/pages/site/docs/discussions/naming.html:42
+msgid ""
+"As with the Internet however, I2P is keeping the design and operation of "
+"a \n"
+"naming system out of the (IP-like) communication layer. The bundled "
+"naming library\n"
+"includes a simple service provider interface which alternate naming systems can\n"
+"plug into, allowing end users to drive what sort of naming tradeoffs they"
+" prefer."
+msgstr ""
+
+#: i2p2www/pages/site/docs/discussions/naming.html:50
+msgid ""
+"See also Names: "
+"Decentralized, Secure, Human-Meaningful: Choose Two."
+msgstr ""
+
+#: i2p2www/pages/site/docs/discussions/naming.html:55
+msgid "(adapted from a post in the old Syndie, November 26, 2005)"
+msgstr ""
+
+#: i2p2www/pages/site/docs/discussions/naming.html:58
+msgid ""
+"Q:\n"
+"What to do if some hosts \n"
+"do not agree on one address and if some addresses are working, others are"
+" not? \n"
+"Who is the right source of a name?"
+msgstr ""
+
+#: i2p2www/pages/site/docs/discussions/naming.html:64
+msgid ""
+"A:\n"
+"You don't. This is actually a critical difference between names on I2P "
+"and how \n"
+"DNS works - names in I2P are human readable, secure, but not globally"
+" \n"
+"unique. This is by design, and an inherent part of our need for "
+"security."
+msgstr ""
+
+#: i2p2www/pages/site/docs/discussions/naming.html:70
+msgid ""
+"If I could somehow convince you to change the destination associated with"
+" some \n"
+"name, I'd successfully \"take over\" the site, and under no circumstances"
+" is that \n"
+"acceptable. Instead, what we do is make names locally unique: "
+"they are \n"
+"what you use to call a site, just as how you can call things "
+"whatever \n"
+"you want when you add them to your browser's bookmarks, or your IM "
+"client's \n"
+"buddy list. Who you call \"Boss\" may be who someone else calls "
+"\"Sally\"."
+msgstr ""
+
+#: i2p2www/pages/site/docs/discussions/naming.html:78
+msgid "Names will not, ever, be securely human readable and globally unique."
+msgstr ""
+
+#: i2p2www/pages/site/docs/discussions/naming.html:83
+msgid ""
+"The following from zzz is a review of several common\n"
+"complaints about I2P's naming system."
+msgstr ""
+
+#: i2p2www/pages/site/docs/discussions/naming.html:89
+msgid ""
+"Inefficiency:\n"
+"The whole hosts.txt is downloaded (if it has changed, since eepget uses "
+"the etag and last-modified headers).\n"
+"It's about 400K right now for almost 800 hosts."
+msgstr ""
+
+#: i2p2www/pages/site/docs/discussions/naming.html:94
+msgid ""
+"True, but this isn't a lot of traffic in the context of i2p, which is "
+"itself wildly inefficient\n"
+"(floodfill databases, huge encryption overhead and padding, garlic "
+"routing, etc.).\n"
+"If you downloaded a hosts.txt file from someone every 12 hours it "
+"averages out to about 10 bytes/sec."
+msgstr ""
+
+#: i2p2www/pages/site/docs/discussions/naming.html:99
+msgid ""
+"As is usually the case in i2p, there is a fundamental tradeoff here "
+"between anonymity and efficiency.\n"
+"Some would say that using the etag and last-modified headers is hazardous"
+" because it exposes when you\n"
+"last requested the data.\n"
+"Others have suggested asking for specific keys only (similar to what jump"
+" services do, but\n"
+"in a more automated fashion), possibly at a further cost in anonymity."
+msgstr ""
+
+#: i2p2www/pages/site/docs/discussions/naming.html:106
+#, python-format
+msgid ""
+"Possible improvements would be a replacement or supplement to addressbook"
+" (see %(i2host)sp),\n"
+"or something simple like subscribing to http://example.i2p/cgi-"
+"bin/recenthosts.cgi rather than http://example.i2p/hosts.txt.\n"
+"If a hypothetical recenthosts.cgi distributed all hosts from the last 24 "
+"hours, for example,\n"
+"that could be both more efficient and more anonymous than the current "
+"hosts.txt with last-modified and etag."
+msgstr ""
+
+#: i2p2www/pages/site/docs/discussions/naming.html:112
+#, python-format
+msgid ""
+"A sample implementation is on stats.i2p at\n"
+"%(url)s.\n"
+"This script returns an Etag with a timestamp.\n"
+"When a request comes in with the If-None-Match etag,\n"
+"the script ONLY returns new hosts since that timestamp, or 304 Not "
+"Modified if there are none.\n"
+"In this way, the script efficiently returns only the hosts the subscriber"
+"\n"
+"does not know about, in an addressbook-compatible manner."
+msgstr ""
+
+#: i2p2www/pages/site/docs/discussions/naming.html:121
+msgid ""
+"So the inefficiency is not a big issue and there are several ways to "
+"improve things without\n"
+"radical change."
+msgstr ""
+
+#: i2p2www/pages/site/docs/discussions/naming.html:127
+msgid ""
+"Not Scalable:\n"
+"The 400K hosts.txt (with linear search) isn't that big at the moment and\n"
+"we can probably grow by 10x or 100x before it's a problem."
+msgstr ""
+
+#: i2p2www/pages/site/docs/discussions/naming.html:132
+msgid ""
+"As far as network traffic see above.\n"
+"But unless you're going to do a slow real-time query over the network for"
+"\n"
+"a key, you need to have the whole set of keys stored locally, at a cost "
+"of about 500 bytes per key."
+msgstr ""
+
+#: i2p2www/pages/site/docs/discussions/naming.html:139
+msgid ""
+"Requires configuration and \"trust\":\n"
+"Out-of-the-box addressbook is only subscribed to "
+"http://www.i2p2.i2p/hosts.txt, which is rarely updated,\n"
+"leading to poor new-user experience."
+msgstr ""
+
+#: i2p2www/pages/site/docs/discussions/naming.html:144
+msgid ""
+"This is very much intentional. jrandom wants a user to \"trust\" a "
+"hosts.txt\n"
+"provider, and as he likes to say, \"trust is not a boolean\".\n"
+"The configuration step attempts to force users to think about issues of "
+"trust in an anonymous network."
+msgstr ""
+
+#: i2p2www/pages/site/docs/discussions/naming.html:149
+msgid ""
+"As another example, the \"Eepsite Unknown\" error page in the HTTP Proxy\n"
+"lists some jump services, but doesn't \"recommend\" any one in "
+"particular,\n"
+"and it's up to the user to pick one (or not).\n"
+"jrandom would say we trust the listed providers enough to list them but "
+"not enough to\n"
+"automatically go fetch the key from them."
+msgstr ""
+
+#: i2p2www/pages/site/docs/discussions/naming.html:156
+msgid ""
+"How successful this is, I'm not sure.\n"
+"But there must be some sort of hierarchy of trust for the naming system.\n"
+"To treat everyone equally may increase the risk of hijacking."
+msgstr ""
+
+#: i2p2www/pages/site/docs/discussions/naming.html:163
+msgid "It isn't DNS"
+msgstr ""
+
+#: i2p2www/pages/site/docs/discussions/naming.html:166
+msgid ""
+"Unfortunately real-time lookups over i2p would significantly slow down "
+"web browsing."
+msgstr ""
+
+#: i2p2www/pages/site/docs/discussions/naming.html:169
+msgid ""
+"Also, DNS is based on lookups with limited caching and time-to-live, "
+"while i2p\n"
+"keys are permanent."
+msgstr ""
+
+#: i2p2www/pages/site/docs/discussions/naming.html:173
+msgid "Sure, we could make it work, but why? It's a bad fit."
+msgstr ""
+
+#: i2p2www/pages/site/docs/discussions/naming.html:178
+msgid ""
+"Not reliable:\n"
+"It depends on specific servers for addressbook subscriptions."
+msgstr ""
+
+#: i2p2www/pages/site/docs/discussions/naming.html:182
+msgid ""
+"Yes it depends on a few servers that you have configured.\n"
+"Within i2p, servers and services come and go.\n"
+"Any other centralized system (for example DNS root servers) would\n"
+"have the same problem. A completely decentralized system (everybody is "
+"authoritative)\n"
+"is possible by implementing an \"everybody is a root DNS server\" "
+"solution, or by\n"
+"something even simpler, like a script that adds everybody in your "
+"hosts.txt to your addressbook."
+msgstr ""
+
+#: i2p2www/pages/site/docs/discussions/naming.html:190
+msgid ""
+"People advocating all-authoritative solutions generally haven't thought "
+"through\n"
+"the issues of conflicts and hijacking, however."
+msgstr ""
+
+#: i2p2www/pages/site/docs/discussions/naming.html:196
+msgid ""
+"Awkward, not real-time:\n"
+"It's a patchwork of hosts.txt providers, key-add web form providers, jump"
+" service providers,\n"
+"eepsite status reporters.\n"
+"Jump servers and subscriptions are a pain, it should just work like DNS."
+msgstr ""
+
+#: i2p2www/pages/site/docs/discussions/naming.html:202
+msgid "See the reliability and trust sections."
+msgstr ""
+
+#: i2p2www/pages/site/docs/discussions/naming.html:207
+msgid ""
+"So, in summary, the current system is not horribly broken, inefficient, "
+"or un-scalable,\n"
+"and proposals to \"just use DNS\" aren't well thought-through."
+msgstr ""
+
+#: i2p2www/pages/site/docs/discussions/naming.html:212
+msgid "Alternatives"
+msgstr ""
+
+#: i2p2www/pages/site/docs/discussions/naming.html:213
+msgid ""
+"The I2P source contains several pluggable naming systems and supports "
+"configuration options\n"
+"to enable experimentation with naming systems."
+msgstr ""
+
+#: i2p2www/pages/site/docs/discussions/naming.html:218
+msgid ""
+"Meta - calls two or more other naming systems in order.\n"
+"By default, calls PetName then HostsTxt."
+msgstr ""
+
+#: i2p2www/pages/site/docs/discussions/naming.html:222
+msgid ""
+"PetName - Looks up in a petnames.txt file.\n"
+"The format for this file is NOT the same as hosts.txt."
+msgstr ""
+
+#: i2p2www/pages/site/docs/discussions/naming.html:226
+msgid "HostsTxt - Looks up in the following files, in order:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/discussions/naming.html:234
+msgid ""
+"AddressDB - Each host is listed in a separate file in a addressDb/"
+" directory."
+msgstr ""
+
+#: i2p2www/pages/site/docs/discussions/naming.html:237
+msgid ""
+"Eepget - does an HTTP lookup request from an external\n"
+"server - must be stacked after the HostsTxt lookup with Meta.\n"
+"This could augment or replace the jump system.\n"
+"Includes in-memory caching."
+msgstr ""
+
+#: i2p2www/pages/site/docs/discussions/naming.html:243
+msgid ""
+"Exec - calls an external program for lookup, allows\n"
+"additional experimentation in lookup schemes, independent of java.\n"
+"Can be used after HostsTxt or as the sole naming system.\n"
+"Includes in-memory caching."
+msgstr ""
+
+#: i2p2www/pages/site/docs/discussions/naming.html:249
+msgid "Dummy - used as a fallback for Base64 names, otherwise fails."
+msgstr ""
+
+#: i2p2www/pages/site/docs/discussions/naming.html:253
+msgid ""
+"The current naming system can be changed with the advanced config option "
+"'i2p.naming.impl'\n"
+"(restart required).\n"
+"See core/java/src/net/i2p/client/naming for details."
+msgstr ""
+
+#: i2p2www/pages/site/docs/discussions/naming.html:258
+msgid ""
+"Any new system should be stacked with HostsTxt, or should\n"
+"implement local storage and/or the addressbook subscription functions, "
+"since addressbook\n"
+"only knows about the hosts.txt files and format."
+msgstr ""
+
+#: i2p2www/pages/site/docs/discussions/naming.html:264
+msgid "Certificates"
+msgstr ""
+
+#: i2p2www/pages/site/docs/discussions/naming.html:265
+msgid ""
+"I2P destinations contain a certificate, however at the moment that "
+"certificate\n"
+"is always null.\n"
+"With a null certificate, base64 destinations are always 516 bytes ending "
+"in \"AAAA\",\n"
+"and this is checked in the addressbook merge mechanism, and possibly "
+"other places.\n"
+"Also, there is no method available to generate a certificate or add it to"
+" a\n"
+"destination. So these will have to be updated to implement certificates."
+msgstr ""
+
+#: i2p2www/pages/site/docs/discussions/naming.html:273
+#, python-format
+msgid ""
+"One possible use of certificates is for proof of work."
+msgstr ""
+
+#: i2p2www/pages/site/docs/discussions/naming.html:276
+msgid ""
+"Another is for \"subdomains\" (in quotes because there is really no such "
+"thing,\n"
+"i2p uses a flat naming system) to be signed by the 2nd level domain's "
+"keys."
+msgstr ""
+
+#: i2p2www/pages/site/docs/discussions/naming.html:280
+msgid ""
+"With any certificate implementation must come the method for verifying "
+"the\n"
+"certificates.\n"
+"Presumably this would happen in the addressbook merge code.\n"
+"Is there a method for multiple types of certificates, or multiple "
+"certificates?"
+msgstr ""
+
+#: i2p2www/pages/site/docs/discussions/naming.html:286
+msgid ""
+"Adding on a certificate authenticating the\n"
+"responses as signed by some centralized certificate authority would "
+"address many of\n"
+"the hostile nameserver issues but would leave open replay attacks as well"
+" as \n"
+"hostile certificate authority attacks."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/cryptography.html:2
+msgid "Low-level Cryptography Details"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/cryptography.html:3
+#: i2p2www/pages/site/docs/spec/common-structures.html:3
+msgid "November 2013"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/cryptography.html:6
+msgid "This page specifies the low-level details of the cryptography in I2P."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/cryptography.html:10
+#, python-format
+msgid ""
+"There are a handful of cryptographic algorithms in use within I2P, but we"
+" have\n"
+"reduced them to a bare minimum to deal with our needs - one symmetric "
+"algorithm\n"
+"one asymmetric algorithm, one signing algorithm, and one hashing "
+"algorithm. However, \n"
+"we do combine them in some particular ways to provide message integrity "
+"(rather than\n"
+"relying on a MAC). In addition, as much as we hate doing anything new in"
+" regards to \n"
+"cryptography, we can't seem to find a reference discussing (or even "
+"naming) the \n"
+"technique used in ElGamal/AES+SessionTag "
+"(but we're sure others have done it)."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/cryptography.html:20
+msgid "ElGamal encryption"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/cryptography.html:22
+msgid ""
+"\n"
+"ElGamal is used for asymmetric encryption.\n"
+"ElGamal is used in several places in I2P:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/cryptography.html:27
+#, python-format
+msgid ""
+"To encrypt router-to-router Tunnel Build "
+"Messages"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/cryptography.html:30
+#, python-format
+msgid ""
+"For end-to-end (destination-to-destination) encryption as a part of ElGamal/AES+SessionTag\n"
+"using the encryption key in the LeaseSet"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/cryptography.html:34
+#: i2p2www/pages/site/docs/how/cryptography.html:189
+#, python-format
+msgid ""
+"For encryption of some netDb stores and "
+"queries sent to floodfill routers\n"
+"as a part of ElGamal/AES+SessionTag\n"
+"(destination-to-router or router-to-router)."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/cryptography.html:41
+msgid ""
+"We use common primes for 2048 ElGamal encryption and decryption, as given"
+" by IETF RFC-3526.\n"
+"We currently only use ElGamal to encrypt the IV and session key in a "
+"single block, followed by the \n"
+"AES encrypted payload using that key and IV."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/cryptography.html:47
+msgid "The unencrypted ElGamal contains:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/cryptography.html:64
+msgid ""
+"The H(data) is the SHA256 of the data that is encrypted in the ElGamal "
+"block,\n"
+"and is preceded by a nonzero byte. \n"
+"This byte could be random, but as implemented it is always 0xFF.\n"
+"It could possibly be used for flags in the future.\n"
+"The data encrypted in the block may be up to 222 bytes long.\n"
+"As the encrypted data may contain a substantial number of zeros if the\n"
+"cleartext is smaller than 222 bytes, it is recommended that higher layers"
+" pad\n"
+"the cleartext to 222 bytes with random data.\n"
+"Total length: typically 255 bytes."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/cryptography.html:76
+msgid "The encrypted ElGamal contains:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/cryptography.html:102
+msgid ""
+"Each encrypted part is prepended with zeros to a size of exactly 257 "
+"bytes.\n"
+"Total length: 514 bytes.\n"
+"In typical usage, higher layers pad the cleartext data to 222 bytes,\n"
+"resulting in an unencrypted block of 255 bytes.\n"
+"This is encoded as two 256-byte encrypted parts,\n"
+"and there is a single byte of zero padding before each part at this layer."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/cryptography.html:111
+#, python-format
+msgid "See the ElGamal code."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/cryptography.html:115
+msgid ""
+"The shared prime is the \n"
+"[Oakley prime "
+"for 2048 bit keys]"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/cryptography.html:122
+msgid "or as a hexadecimal value:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/cryptography.html:138
+msgid "Using 2 as the generator."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/cryptography.html:142
+msgid "Short Exponent"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/cryptography.html:143
+#, python-format
+msgid ""
+"While the standard exponent size is 2048 bits (256 bytes) and the I2P\n"
+"PrivateKey\n"
+"is a full 256 bytes,\n"
+"we use the short exponent size of 226 bits (28.25 bytes).\n"
+"This should be safe for use with the Oakley primes, per\n"
+"On Diffie-Hellman Key Agreement with Short Exponents "
+"- van Oorschot, Weiner\n"
+"at EuroCrypt 96, and crypto++'s "
+"benchmarks.\n"
+"Benchmarks originally at %(oldbenchmarks)s (now dead),\n"
+"rescued from the wayback machine,"
+" dated Apr 23, 2008."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/cryptography.html:158
+#, python-format
+msgid ""
+"Also, Koshiba & Kurosawa: Short Exponent Diffie-"
+"Hellman Problems (PKC 2004, LNCS 2947, pp. 173-186)\n"
+"(full text on Google Books) apparently "
+"supports this, according to\n"
+"this sci.crypt thread.\n"
+"The remainder of the PrivateKey is padded with zeroes."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/cryptography.html:167
+#: i2p2www/pages/site/docs/how/cryptography.html:264
+#: i2p2www/pages/site/docs/how/cryptography.html:343
+#: i2p2www/pages/site/docs/how/cryptography.html:382
+msgid "Obsolescence"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/cryptography.html:168
+msgid ""
+"The vulnerability of the network to an ElGamal attack and the impact of "
+"transitioning to a longer bit length is to be studied.\n"
+"It may be quite difficult to make any change backward-compatible."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/cryptography.html:176
+msgid "AES is used for symmetric encryption, in several cases:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/cryptography.html:181
+msgid "For transport encryption after DH key exchange"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/cryptography.html:185
+#, python-format
+msgid ""
+"For end-to-end (destination-to-destination) encryption as a part of ElGamal/AES+SessionTag"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/cryptography.html:195
+#, python-format
+msgid ""
+"For encryption of periodic tunnel "
+"test messages sent from the router to itself, through its own "
+"tunnels."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/cryptography.html:200
+#, python-format
+msgid ""
+"We use AES with 256 bit keys and 128 bit blocks in CBC mode.\n"
+"The padding used is specified in IETF RFC-2313 "
+"(PKCS#5 1.5, section 8.1 (for block type 02)).\n"
+"In this case, padding exists of pseudorandomly generated octets to match "
+"16 byte blocks.\n"
+"Specifically, see [the CBC code] and the "
+"Cryptix AES\n"
+"[implementation], as well as the padding, found"
+" in the\n"
+"ElGamalAESEngine.getPadding function."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/cryptography.html:265
+msgid ""
+"The vulnerability of the network to an AES attack and the impact of "
+"transitioning to a longer bit length is to be studied.\n"
+"It may be quite difficult to make any change backward-compatible."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/cryptography.html:270
+#: i2p2www/pages/site/docs/how/cryptography.html:362
+#: i2p2www/pages/site/docs/how/cryptography.html:388
+#: i2p2www/pages/site/docs/how/cryptography.html:456
+#: i2p2www/pages/site/docs/how/garlic-routing.html:281
+#: i2p2www/pages/site/docs/how/peer-selection.html:296
+msgid "References"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/cryptography.html:273
+msgid "Feb. 7, 2006 Status Notes"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/cryptography.html:280
+#, python-format
+msgid ""
+"Signatures are generated and verified with 1024 bit DSA (L=1024, N=160), "
+"as implemented in\n"
+"[DSAEngine].\n"
+"DSA was chosen because it is much faster for signatures than ElGamal."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/cryptography.html:286
+msgid "The DSA constants"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/cryptography.html:337
+#, python-format
+msgid ""
+"The Signing Public"
+" Key is 1024 bits.\n"
+"The Signing "
+"Private Key is 160 bits."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/cryptography.html:344
+#, python-format
+msgid ""
+"NIST 800-57\n"
+"recommends a minimum of (L=2048, N=224) for usage beyond 2010.\n"
+"This may be mitigated somewhat by the \"cryptoperiod\", or lifespan of a "
+"given key."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/cryptography.html:350
+msgid ""
+"The prime number was chosen in 2003,\n"
+"and the person that chose the number (TheCrypto) is currently no longer "
+"an I2P developer.\n"
+"As such, we do not know if the prime chosen is a 'strong prime'.\n"
+"If a larger prime is chosen for future purposes, this should be a strong "
+"prime, and we will document the construction process."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/cryptography.html:357
+msgid ""
+"The vulnerability of the network to a DSA attack and the impact of "
+"transitioning to longer keys is to be studied.\n"
+"It may be quite difficult to make any change backward-compatible."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/cryptography.html:365
+#: i2p2www/pages/site/docs/how/cryptography.html:367
+#, python-format
+msgid "Meeting %(num)s"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/cryptography.html:369
+msgid "Choosing the constants"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/cryptography.html:377
+#, python-format
+msgid ""
+"Hashes within I2P are plain old SHA256, as implemented in\n"
+"[SHA256Generator]"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/cryptography.html:383
+msgid ""
+"The vulnerability of the network to a SHA-256 attack and the impact of "
+"transitioning to a longer hash is to be studied.\n"
+"It may be quite difficult to make any change backward-compatible."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/cryptography.html:394
+msgid "Transports"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/cryptography.html:395
+msgid ""
+"At the lowest protocol layer,\n"
+"point-to-point inter-router communication is protected by the transport "
+"layer security.\n"
+"Both transports use 256 byte (2048 bit) Diffie-Hellman key exchange\n"
+"using\n"
+"the same shared prime and generator as specified "
+"above for ElGamal,\n"
+"followed by symmetric AES encryption as described above.\n"
+"This provides\n"
+"perfect "
+"forward secrecy\n"
+"on the transport links."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/cryptography.html:407
+msgid "NTCP connections"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/cryptography.html:409
+#, python-format
+msgid ""
+"NTCP connections are negotiated with a 2048 Diffie-Hellman "
+"implementation,\n"
+"using the router's identity to proceed with a station to station "
+"agreement, followed by\n"
+"some encrypted protocol specific fields, with all subsequent data "
+"encrypted with AES\n"
+"(as above).\n"
+"The primary reason to do the DH negotiation instead of using ElGamalAES+SessionTag is that it provides '(perfect) "
+"forward secrecy ', while ElGamalAES+SessionTag does not."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/cryptography.html:417
+msgid ""
+"In order to migrate to a more standardized implementation (TLS/SSL or "
+"even SSH), the following issues must be addressed:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/cryptography.html:421
+msgid ""
+"Can we somehow reestablish sessions securely (ala session tags) or do we "
+"need to do full negotiation each time?"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/cryptography.html:424
+msgid ""
+"Can we simplify/avoid the x509 or other certificate formats and use our "
+"own RouterInfo structure (which \n"
+"contains the ElGamal and DSA keys)?"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/cryptography.html:429
+#, python-format
+msgid "See the NTCP specification for details."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/cryptography.html:433
+msgid "UDP connections"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/cryptography.html:434
+msgid ""
+"SSU (the UDP transport) encrypts each packet with AES256/CBC with both an"
+" explicit IV and MAC \n"
+"(HMAC-MD5-128) after agreeing upon an ephemeral session key through a "
+"2048 bit \n"
+"Diffie-Hellman exchange, station-to-station authentication with the other"
+" \n"
+"router's DSA key, plus each network message has their own hash for local "
+"integrity \n"
+"checking."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/cryptography.html:442
+#, python-format
+msgid "See the SSU specification for details."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/cryptography.html:446
+#, python-format
+msgid ""
+"WARNING - I2P's HMAC-MD5-128 used in SSU is apparently non-standard.\n"
+"Apparently, an early version of SSU used HMAC-SHA256, and then it was "
+"switched\n"
+"to MD5-128 for performance reasons, but left the 32-byte buffer size "
+"intact.\n"
+"See HMACGenerator.java and\n"
+"the 2005-07-05 status notes\n"
+"for details."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/elgamal-aes.html:2
+msgid "ElGamal/AES + SessionTag Encryption"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/elgamal-aes.html:3
+msgid "February 2011"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/elgamal-aes.html:7
+msgid "ElGamal/AES+SessionTags is used for end-to-end encryption."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/elgamal-aes.html:11
+msgid ""
+"As an unreliable, unordered, message based system, I2P uses a simple "
+"combination \n"
+"of asymmetric and symmetric encryption algorithms to provide data "
+"confidentiality \n"
+"and integrity to garlic messages. As a whole, the combination is referred"
+" \n"
+"to as ElGamal/AES+SessionTags, but that is an excessively verbose way to "
+"describe \n"
+"the use of 2048bit ElGamal, AES256, SHA256, and 32 byte nonces."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/elgamal-aes.html:19
+#: i2p2www/pages/site/docs/how/tech-intro.html:512
+msgid ""
+"The first time a router wants to encrypt a garlic message to another "
+"router, \n"
+"they encrypt the keying material for an AES256 session key with ElGamal "
+"and \n"
+"append the AES256/CBC encrypted payload after that encrypted ElGamal "
+"block. \n"
+"In addition to the encrypted payload, the AES encrypted section contains "
+"the \n"
+"payload length, the SHA256 hash of the unencrypted payload, as well as a "
+"number \n"
+"of \"session tags\" - random 32 byte nonces. The next time the sender "
+"wants \n"
+"to encrypt a garlic message to another router, rather than ElGamal "
+"encrypt \n"
+"a new session key they simply pick one of the previously delivered "
+"session \n"
+"tags and AES encrypt the payload like before, using the session key used "
+"with \n"
+"that session tag, prepended with the session tag itself. When a router "
+"receives \n"
+"a garlic encrypted message, they check the first 32 bytes to see if it "
+"matches \n"
+"an available session tag - if it does, they simply AES decrypt the "
+"message, \n"
+"but if it does not, they ElGamal decrypt the first block."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/elgamal-aes.html:35
+#: i2p2www/pages/site/docs/how/tech-intro.html:528
+msgid ""
+"Each session tag can be used only once so as to prevent internal "
+"adversaries \n"
+"from unnecessarily correlating different messages as being between the "
+"same \n"
+"routers. The sender of an ElGamal/AES+SessionTag encrypted message "
+"chooses \n"
+"when and how many tags to deliver, prestocking the recipient with enough "
+"tags \n"
+"to cover a volley of messages. Garlic messages may detect the successful "
+"tag \n"
+"delivery by bundling a small additional message as a clove (a \"delivery "
+"status \n"
+"message\") - when the garlic message arrives at the intended recipient "
+"and \n"
+"is decrypted successfully, this small delivery status message is one of "
+"the \n"
+"cloves exposed and has instructions for the recipient to send the clove "
+"back \n"
+"to the original sender (through an inbound tunnel, of course). When the "
+"original \n"
+"sender receives this delivery status message, they know that the session "
+"tags \n"
+"bundled in the garlic message were successfully delivered."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/elgamal-aes.html:50
+msgid ""
+"Session tags themselves have a short lifetime, after which they are \n"
+"discarded if not used. In addition, the quantity stored for each key is "
+"limited, \n"
+"as are the number of keys themselves - if too many arrive, either new or "
+"old \n"
+"messages may be dropped. The sender keeps track whether messages using "
+"session \n"
+"tags are getting through, and if there isn't sufficient communication it "
+"may \n"
+"drop the ones previously assumed to be properly delivered, reverting back"
+" \n"
+"to the full expensive ElGamal encryption.\n"
+"A session will continue to exist until all its tags are exhausted or "
+"expire."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/elgamal-aes.html:61
+msgid ""
+"Sessions are unidirectional. Tags are delivered from Alice to Bob,\n"
+"and Alice then uses the tags, one by one, in subsequent messages to Bob."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/elgamal-aes.html:66
+msgid ""
+"Sessions may be established between Destinations, between Routers, or\n"
+"between a Router and a Destination.\n"
+"Each Router and Destination maintains its own Session Key Manager to\n"
+"keep track of Session Keys and Session Tags.\n"
+"Separate Session Key Managers prevents correlation of multiple "
+"Destinations\n"
+"to each other or a Router by adversaries."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/elgamal-aes.html:77
+msgid "Message Reception"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/elgamal-aes.html:78
+msgid ""
+"Each message received has one of two\n"
+"the two possible conditions:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/elgamal-aes.html:84
+msgid ""
+"It is part of an existing session and contains a Session Tag and an AES "
+"encrypted block"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/elgamal-aes.html:85
+msgid "It is for a new session and contains both ElGamal and AES encrypted blocks"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/elgamal-aes.html:88
+msgid ""
+"When a router receives a message, it will first assume it is from\n"
+"an existing session and attempt to look up the Session Tag and decrypt "
+"the following data using AES.\n"
+"If that fails, it will assume it is for a new session and attempt to\n"
+"decrypt it using ElGamal."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/elgamal-aes.html:97
+msgid "New Session Message Specification"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/elgamal-aes.html:98
+msgid ""
+"A New Session ElGamal Message contains two parts, an encrypted ElGamal "
+"block\n"
+"and an encrypted AES block."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/elgamal-aes.html:103
+msgid "The encrypted message contains:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/elgamal-aes.html:127
+msgid "ElGamal Block"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/elgamal-aes.html:128
+msgid "The encrypted ElGamal Block is always 514 bytes long."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/elgamal-aes.html:132
+msgid "The unencrypted ElGamal data is 222 bytes long, containing:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/elgamal-aes.html:164
+#, python-format
+msgid ""
+"The 32-byte\n"
+"Session Key\n"
+"is the identifier for the session.\n"
+"The 32-byte Pre-IV will be used to generate the IV for the AES block that"
+" follows;\n"
+"the IV is the first 16 bytes of the SHA-256 Hash of the Pre-IV."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/elgamal-aes.html:172
+#, python-format
+msgid ""
+"The 222 byte payload is encrypted\n"
+"using ElGamal\n"
+"and the encrypted block is 514 bytes long.\n"
+""
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/elgamal-aes.html:179
+msgid "AES Block"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/elgamal-aes.html:180
+msgid "The unencrypted data in the AES block contains the following:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/elgamal-aes.html:224
+#, python-format
+msgid "2-byte Integer, 0-200"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/elgamal-aes.html:228
+#, python-format
+msgid ""
+"That many 32-byte Session Tags"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/elgamal-aes.html:232
+#, python-format
+msgid "4-byte Integer"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/elgamal-aes.html:236
+#, python-format
+msgid ""
+"The 32-byte SHA256 Hash of"
+" the payload"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/elgamal-aes.html:240
+msgid "A one-byte value. Normally == 0. If == 0x01, a Session Key follows"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/elgamal-aes.html:244
+#, python-format
+msgid ""
+"A 32-byte Session "
+"Key,\n"
+" to replace the old key, and is only present if preceding"
+" flag is 0x01"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/elgamal-aes.html:249
+msgid "the data"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/elgamal-aes.html:251
+msgid ""
+"Random data to a multiple of 16 bytes for the total length.\n"
+" May contain more than the minimum required padding."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/elgamal-aes.html:256
+msgid "Minimum length: 48 bytes"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/elgamal-aes.html:260
+#, python-format
+msgid ""
+"The data is then AES Encrypted,\n"
+"using the session key and IV (calculated from the pre-IV) from the "
+"ElGamal section.\n"
+"The encrypted AES Block length is variable but is always a multiple of 16"
+" bytes.\n"
+""
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/elgamal-aes.html:269
+#, python-format
+msgid ""
+"Actual max payload length, and max block length, is less than 64 KB; see "
+"the I2NP Overview."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/elgamal-aes.html:272
+msgid "New Session Key is currently unused and is never present."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/elgamal-aes.html:277
+msgid "Existing Session Message Specification"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/elgamal-aes.html:278
+msgid ""
+"The session tags delivered successfully are remembered for a \n"
+"brief period (15 minutes currently) until they are used or discarded.\n"
+"A tag is used by packaging one in an Existing Session Message that\n"
+"contains only an AES encrypted block, and is not preceded by an\n"
+"ElGamal block."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/elgamal-aes.html:286
+msgid ""
+"The existing session message is\n"
+"as follows:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/elgamal-aes.html:309
+#, python-format
+msgid ""
+"A 32-byte Session "
+"Tag\n"
+" previously delivered in an AES block"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/elgamal-aes.html:314
+msgid "As specified above."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/elgamal-aes.html:318
+msgid ""
+"The session tag also serves as\n"
+"the pre-IV. The IV is the first 16 bytes of the SHA-256 Hash of the "
+"sessionTag."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/elgamal-aes.html:323
+msgid ""
+"To decode a message from an existing session, a router looks up the "
+"Session Tag to find an\n"
+"associated Session Key. If the Session Tag is found, the AES block is "
+"decrypted using the associated Session Key.\n"
+"If the tag is not found, the message is assumed to be a New Session Message."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/elgamal-aes.html:332
+msgid ""
+"There are many possible areas to tune the Session Key Manager's "
+"algorithms;\n"
+"some may interact with the streaming library behavior, or have "
+"significant\n"
+"impact on overall performance."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/elgamal-aes.html:338
+msgid ""
+"Delivery of too many tags at one time may impose substantial overhead for"
+" brief streaming connections\n"
+"or datagrams, and increase the chance of message loss.\n"
+"We currently deliver 40 tags at a time (1280 bytes).\n"
+"32 (1024 bytes) may be better for tunnel fragmentation."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/elgamal-aes.html:345
+msgid ""
+"A few tags could be delivered in each of several messages, or lots of "
+"tags all at once."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/elgamal-aes.html:349
+msgid ""
+"It is also important to study and tune\n"
+"the low-tag thresholds at which more tags are sent."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/elgamal-aes.html:354
+msgid ""
+"The number of tags delivered could depend on message size, keeping in "
+"mind\n"
+"the eventual padding to 1KB at the tunnel message layer."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/elgamal-aes.html:359
+msgid ""
+"Clients could send an estimate of session lifetime to the router, as an "
+"advisory\n"
+"on the number of tags required."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/elgamal-aes.html:364
+msgid ""
+"Delivery of too few tags causes the router to fall back to an expensive "
+"ElGamal encryption."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/elgamal-aes.html:368
+msgid ""
+"The router may assume delivery of Session Tags, or await acknowledgement "
+"before using them;\n"
+"there are tradeoffs for each strategy."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/elgamal-aes.html:373
+msgid ""
+"For very brief messages, almost the full 222 bytes of the pre-IV and "
+"padding fields in the ElGamal block\n"
+"could be used for the entire message, instead of establishing a session."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/elgamal-aes.html:378
+msgid ""
+"Evaluate padding strategy; currently we pad to a minimum of 128 bytes.\n"
+"Would be better to add a few tags to small messages than pad."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/elgamal-aes.html:383
+msgid ""
+"Perhaps things could be more efficient if the Session Tag system was "
+"bidirectional,\n"
+"so tags delivered in the 'forward' path could be used in the 'reverse' "
+"path,\n"
+"thus avoiding ElGamal in the initial response.\n"
+"The router currently plays some tricks like this when sending\n"
+"tunnel test messages to itself."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/elgamal-aes.html:391
+#, python-format
+msgid ""
+"Change from Session Tags to\n"
+"a synchronized PRNG."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/elgamal-aes.html:396
+#, python-format
+msgid ""
+"Several of these ideas may require a new I2NP message type, or\n"
+"set a flag in the\n"
+"Delivery Instructions,\n"
+"or set a magic number in the first few bytes of the Session Key field\n"
+"and accept a small risk of the random Session Key matching the magic "
+"number."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/garlic-routing.html:2
+msgid "Garlic Routing"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/garlic-routing.html:6
+msgid "Garlic Routing and \"Garlic\" Terminology"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/garlic-routing.html:7
+msgid ""
+"The terms \"garlic routing\" and \"garlic encryption\" are often used "
+"rather loosely when referring to I2P's technology.\n"
+"Here, we explain the history of the terms, the various meanings, and\n"
+"the usage of \"garlic\" methods in I2P."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/garlic-routing.html:13
+msgid ""
+"\"Garlic routing\" was first coined by\n"
+"Michael J. Freedman\n"
+"in Roger Dingledine's Free Haven \n"
+"Master's thesis "
+"Section 8.1.1 (June 2000), as derived from \n"
+"Onion Routing."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/garlic-routing.html:21
+msgid ""
+"\"Garlic\" may have been used originally by I2P developers because I2P "
+"implements a form of\n"
+"bundling as Freedman describes, or simply to emphasize general "
+"differences from Tor.\n"
+"The specific reasoning may be lost to history.\n"
+"Generally, when referring to I2P, the term \"garlic\" may mean one of "
+"three things:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/garlic-routing.html:28
+#: i2p2www/pages/site/docs/how/garlic-routing.html:39
+msgid "Layered Encryption"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/garlic-routing.html:29
+msgid "Bundling multiple messages together"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/garlic-routing.html:30
+#: i2p2www/pages/site/docs/how/garlic-routing.html:96
+msgid "ElGamal/AES Encryption"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/garlic-routing.html:33
+msgid ""
+"Unfortunately, I2P's usage of \"garlic\" terminology over the past seven "
+"years has not always been precise; therefore the reader is\n"
+"cautioned when encountering the term.\n"
+"Hopefully, the explanation below will make things clear."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/garlic-routing.html:40
+msgid ""
+"Onion routing is a technique for building paths, or tunnels, through a "
+"series of peers,\n"
+"and then using that tunnel.\n"
+"Messages are repeatedly encrypted by the originator, and then decrypted "
+"by each hop.\n"
+"During the building phase, only the routing instructions for the next hop"
+" are exposed to each peer.\n"
+"During the operating phase, messages are passed through the tunnel, and "
+"the\n"
+"message and its routing instructions are only exposed to the endpoint of "
+"the tunnel."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/garlic-routing.html:49
+#, python-format
+msgid ""
+"This is similar to the way Mixmaster\n"
+"(see network comparisons) sends messages "
+"- taking a message, encrypting it\n"
+"to the recipient's public key, taking that encrypted message and "
+"encrypting\n"
+"it (along with instructions specifying the next hop), and then taking "
+"that\n"
+"resulting encrypted message and so on, until it has one layer of "
+"encryption\n"
+"per hop along the path."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/garlic-routing.html:58
+msgid ""
+"In this sense, \"garlic routing\" as a general concept is identical to "
+"\"onion routing\".\n"
+"As implemented in I2P, of course, there are several differences from the "
+"implementation in Tor; see below.\n"
+"Even so, there are substantial similarities such that I2P benefits from a"
+"\n"
+"large amount of"
+" academic research on onion routing,\n"
+"Tor, and similar "
+"mixnets."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/garlic-routing.html:67
+msgid "Bundling Multiple Messages"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/garlic-routing.html:68
+msgid ""
+"Michael Freedman defined \"garlic routing\" as an extension to onion "
+"routing,\n"
+"in which multiple messages are bundled together.\n"
+"He called each message a \"bulb\".\n"
+"All the messages, each with its own delivery instructions, are exposed at"
+" the\n"
+"endpoint.\n"
+"This allows the efficient bundling of an onion routing \"reply block\" "
+"with the original message."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/garlic-routing.html:77
+msgid ""
+"This concept is implemented in I2P, as described below.\n"
+"Our term for garlic \"bulbs\" is \"cloves\".\n"
+"Any number of messages can be\n"
+"contained, instead of just a single message.\n"
+"This is a significant distinction from the onion routing implemented in "
+"Tor.\n"
+"However, it is only one of many major architectural differences between "
+"I2P and Tor;\n"
+"perhaps it is not, by itself, enough to justify a change in terminology."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/garlic-routing.html:87
+msgid ""
+"Another difference\n"
+"from the method described by Freedman\n"
+"is that the path is unidirectional - there is no \"turning point\" as "
+"seen in onion routing\n"
+"or mixmaster reply blocks, which greatly simplifies the algorithm and "
+"allows for more flexible\n"
+"and reliable delivery."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/garlic-routing.html:97
+#, python-format
+msgid ""
+"In some cases, \"garlic encryption\" may simply mean\n"
+"ElGamal/AES+SessionTag encryption\n"
+"(without multiple layers)."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/garlic-routing.html:105
+msgid "\"Garlic\" Methods in I2P"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/garlic-routing.html:106
+msgid ""
+"Now that we've defined various \"garlic\" terms, we can say that\n"
+"I2P uses garlic routing, bundling and encryption in three places:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/garlic-routing.html:111
+msgid "For building and routing through tunnels (layered encryption)"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/garlic-routing.html:112
+msgid ""
+"For determining the success or failure of end to end message delivery "
+"(bundling)"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/garlic-routing.html:113
+msgid ""
+"For publishing some network database entries (dampening the probability "
+"of a successful traffic analysis attack) (ElGamal/AES)"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/garlic-routing.html:116
+msgid ""
+"There are also significant ways that this technique can be used to "
+"improve the performance of the network, \n"
+"exploiting transport latency/throughput tradeoffs, and branching data "
+"through redundant paths to increase reliability."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/garlic-routing.html:122
+msgid "Tunnel Building and Routing"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/garlic-routing.html:123
+msgid ""
+"In I2P, tunnels are unidirectional. Each party builds two tunnels,\n"
+"one for outbound and one for inbound traffic.\n"
+"Therefore, four tunnels are required for a single round-trip message and "
+"reply."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/garlic-routing.html:129
+#, python-format
+msgid ""
+"Tunnels are built, and then used, with layered encryption.\n"
+"This is described on the\n"
+"tunnel implementation page.\n"
+"Tunnel building details are defined on\n"
+"this page.\n"
+"We use\n"
+"ElGamal/AES+SessionTag for the encryption."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/garlic-routing.html:141
+#, python-format
+msgid ""
+"Tunnels are a general-purpose mechanism to transport all\n"
+"I2NP messages, and\n"
+"Garlic Messages are not used to "
+"build tunnels.\n"
+"We do not bundle multiple\n"
+"I2NP messages into a single\n"
+"Garlic Message for unwrapping at "
+"the outbound tunnel endpoint;\n"
+"the tunnel encryption is sufficient."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/garlic-routing.html:152
+msgid "End-to-End Message Bundling"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/garlic-routing.html:153
+#, python-format
+msgid ""
+"At the layer above tunnels, I2P delivers end-to-end messages between\n"
+"Destinations.\n"
+"Just as within a single tunnel, we use\n"
+"ElGamal/AES+SessionTag for the encryption."
+"\n"
+"Each client message as delivered to the router through the\n"
+"I2CP interface becomes a single\n"
+"Garlic Clove\n"
+"with its own\n"
+"Delivery Instructions,\n"
+"inside a\n"
+"Garlic Message.\n"
+"Delivery Instructions may specify a Destination, Router, or Tunnel."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/garlic-routing.html:172
+msgid ""
+"Generally, a Garlic Message will contain only one clove.\n"
+"However, the router will periodically bundle two additional\n"
+"cloves in the Garlic Message:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/garlic-routing.html:177
+msgid "Garlic Message Cloves"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/garlic-routing.html:180
+#, python-format
+msgid ""
+"A\n"
+"Delivery Status Message,\n"
+"with\n"
+"Delivery Instructions\n"
+"specifying that it be sent back to the originating router as an "
+"acknowledgment.\n"
+"This is similar to the \"reply block\" or \"reply onion\"\n"
+"described in the references.\n"
+"It is used for determining the success or failure of end to end message "
+"delivery.\n"
+"The originating router may, upon failure to receive the Delivery Status "
+"Message\n"
+"within the expected time period, modify the routing to the far-end "
+"Destination,\n"
+"or take other actions."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/garlic-routing.html:194
+#, python-format
+msgid ""
+"A\n"
+"Database Store Message,\n"
+"containing a\n"
+"LeaseSet\n"
+"for the originating Destination, with\n"
+"Delivery Instructions\n"
+"specifying the far-end destination's router.\n"
+"By periodically bundling a LeaseSet, the router ensures that the far-end "
+"will be able\n"
+"to maintain communications.\n"
+"Otherwise the far-end would have to query a floodfill router for the "
+"network database entry,\n"
+"and all LeaseSets would have to be published to the network database, as "
+"explained on the\n"
+"network database page."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/garlic-routing.html:213
+#, python-format
+msgid ""
+"In the current implementation, the Delivery Status and Database Store "
+"Messages\n"
+"are bundled when the local LeaseSet changes, when additional\n"
+"Session Tags\n"
+"are delivered, or if the messages have not been bundled in the previous "
+"minute."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/garlic-routing.html:220
+msgid ""
+"Obviously, the additional messages are currently bundled for specific "
+"purposes,\n"
+"and not part of a general-purpose routing scheme."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/garlic-routing.html:226
+msgid "Storage to the Floodfill Network Database"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/garlic-routing.html:227
+#, python-format
+msgid ""
+"As explained on the\n"
+"network database page,\n"
+"local\n"
+"LeaseSets\n"
+"are sent to floodfill routers in a\n"
+"Database Store Message\n"
+"wrapped in a\n"
+"Garlic Message\n"
+"so it is not visible to the tunnel's outbound gateway."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/garlic-routing.html:243
+#, python-format
+msgid ""
+"The Garlic Message mechanism is very flexible and provides a structure "
+"for\n"
+"implementing many types of mixnet delivery methods.\n"
+"Together with the unused delay option in the\n"
+"tunnel message Delivery "
+"Instructions,\n"
+"a wide spectrum of batching, delay, mixing, and routing strategies are "
+"possible."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/garlic-routing.html:251
+msgid ""
+"In particular, there is potential for much more flexibility at the "
+"outbound tunnel endpoint.\n"
+"Messages could possibly be routed from there to one of several tunnels\n"
+"(thus minimizing point-to-point connections), or multicast to several "
+"tunnels\n"
+"for redundancy, or streaming audio and video."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/garlic-routing.html:258
+msgid ""
+"Such experiments may conflict with the need to ensure security and "
+"anonymity, such\n"
+"as limiting certain routing paths, restricting the types of I2NP messages"
+" that may\n"
+"be forwarded along various paths, and enforcing certain message "
+"expiration times."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/garlic-routing.html:264
+#, python-format
+msgid ""
+"As a part of\n"
+"ElGamal/AES encryption,\n"
+"a garlic message contains a sender\n"
+"specified amount of padding data, allowing the sender to take active "
+"countermeasures \n"
+"against traffic analysis.\n"
+"This is not currently used, beyond the requirement to pad to a multiple "
+"of 16 bytes."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/garlic-routing.html:273
+#, python-format
+msgid ""
+"Encryption of additional messages to and from the\n"
+"floodfill routers."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/garlic-routing.html:283
+msgid ""
+"The term garlic routing was first coined in Roger Dingledine's Free Haven"
+" \n"
+"Master's thesis "
+"(June 2000),\n"
+"see Section 8.1.1 authored by\n"
+"Michael J. Freedman."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/garlic-routing.html:290
+msgid "Onion router publications"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/garlic-routing.html:292
+msgid "Onion Routing on Wikipedia"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/garlic-routing.html:294
+msgid "Garlic Routing on Wikipedia"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/garlic-routing.html:296
+#, python-format
+msgid ""
+"I2P Meeting 58 (2003) discussing the "
+"implementation of garlic routing"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/garlic-routing.html:302
+msgid "Free Haven publications"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/garlic-routing.html:304
+msgid ""
+"Onion routing was first described in Hiding Routing Information\n"
+"by David M. Goldschlag, Michael G. Reed, and Paul F. Syverson in 1996."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/intro.html:2
+msgid "A Gentle Introduction"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/intro.html:5
+msgid "A Gentle Introduction to How I2P Works"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/intro.html:7
+msgid ""
+"I2P is a project to build, deploy, and maintain a network supporting "
+"secure and anonymous\n"
+"communication. People using I2P are in control of the tradeoffs between "
+"anonymity, reliability,\n"
+"bandwidth usage, and latency. There is no central point in the network on"
+" which pressure can be\n"
+"exerted to compromise the integrity, security, or anonymity of the "
+"system. The network supports\n"
+"dynamic reconfiguration in response to various attacks, and has been "
+"designed to make use of\n"
+"additional resources as they become available. Of course, all aspects of "
+"the network are open and\n"
+"freely available."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/intro.html:17
+msgid ""
+"Unlike many other anonymizing networks, I2P doesn't try to provide "
+"anonymity by hiding the\n"
+"originator of some communication and not the recipient, or the other way "
+"around. I2P is designed to\n"
+"allow peers using I2P to communicate with each other anonymously — "
+"both sender and recipient\n"
+"are unidentifiable to each other as well as to third parties. For "
+"example, today there are both\n"
+"in-I2P web sites (allowing anonymous publishing / hosting) as well as "
+"HTTP proxies to the normal web\n"
+"(allowing anonymous web browsing). Having the ability to run servers "
+"within I2P is essential, as it\n"
+"is quite likely that any outbound proxies to the normal Internet will be "
+"monitored, disabled, or\n"
+"even taken over to attempt more malicious attacks."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/intro.html:28
+#, python-format
+msgid ""
+"The network itself is message oriented - it is essentially a secure and "
+"anonymous IP layer, where\n"
+"messages are addressed to cryptographic keys (Destinations) and can be "
+"significantly larger than IP\n"
+"packets. Some example uses of the network include \"eepsites\" "
+"(webservers hosting normal web\n"
+"applications within I2P), a BitTorrent client (\"I2PSnark\"), or a "
+"distributed data store. With the\n"
+"help of the I2PTunnel application, we are "
+"able to stream traditional\n"
+"TCP/IP applications over I2P, such as SSH, IRC, a squid proxy, and even "
+"streaming audio. Most people\n"
+"will not use I2P directly, or even need to know they're using it. Instead"
+" their view will be of one\n"
+"of the I2P enabled applications, or perhaps as a little controller app to"
+" turn on and off various\n"
+"proxies to enable the anonymizing functionality."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/intro.html:40
+#, python-format
+msgid ""
+"An essential part of designing, developing, and testing an anonymizing "
+"network is to define the threat model , since there is no such thing "
+"as \"true\" anonymity, just\n"
+"increasingly expensive costs to identify someone. Briefly, I2P's intent "
+"is to allow people to\n"
+"communicate in arbitrarily hostile environments by providing good "
+"anonymity, mixed in with\n"
+"sufficient cover traffic provided by the activity of people who require "
+"less anonymity. This way,\n"
+"some users can avoid detection by a very powerful adversary, while others"
+" will try to evade a weaker\n"
+"entity, all on the same network, where each one's messages are "
+"essentially indistinguishable\n"
+"from the others."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/intro.html:51
+msgid "Why?"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/intro.html:52
+#, python-format
+msgid ""
+"There are a multitude of reasons why we need a system to support "
+"anonymous communication, and\n"
+"everyone has their own personal rationale. There are many other\n"
+"efforts working on finding ways to provide varying degrees of "
+"anonymity to people through the\n"
+"Internet, but we could not find any that met our needs or threat model."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/intro.html:59
+msgid "How?"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/intro.html:61
+#, python-format
+msgid ""
+"The network at a glance is made up of a set of nodes (\"routers\") with a"
+" number of unidirectional\n"
+"inbound and outbound virtual paths (\"tunnels\", as outlined on the tunnel routing page). Each router is "
+"identified by a cryptographic RouterIdentity which is\n"
+"typically long lived. These routers communicate with each other through "
+"existing transport\n"
+"mechanisms (TCP, UDP, etc), passing various messages. Client applications"
+" have their own\n"
+"cryptographic identifier (\"Destination\") which enables it to send and "
+"receive messages. These\n"
+"clients can connect to any router and authorize the temporary allocation "
+"(\"lease\") of some tunnels\n"
+"that will be used for sending and receiving messages through the network."
+" I2P has its own internal\n"
+"network database (using a modification of the "
+"Kademlia algorithm) for\n"
+"distributing routing and contact information securely."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/intro.html:74
+msgid "Network topology example"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/intro.html:76
+msgid ""
+"In the above, Alice, Bob, Charlie, and Dave are all running routers with "
+"a single Destination on\n"
+"their local router. They each have a pair of 2-hop inbound tunnels per "
+"destination (labeled 1, 2, 3,\n"
+"4, 5 and 6), and a small subset of each of those router's outbound tunnel"
+" pool is shown with 2-hop\n"
+"outbound tunnels. For simplicity, Charlie's inbound tunnels and Dave's "
+"outbound tunnels are not\n"
+"shown, nor are the rest of each router's outbound tunnel pool (typically "
+"stocked with a few tunnels\n"
+"at a time). When Alice and Bob talk to each other, Alice sends a message "
+"out one of her (pink)\n"
+"outbound tunnels targeting one of Bob's (green) inbound tunnels (tunnel 3"
+" or 4). She knows to send\n"
+"to those tunnels on the correct router by querying the network database, "
+"which is constantly updated\n"
+"as new leases are authorized and old ones expire."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/intro.html:88
+#, python-format
+msgid ""
+"If Bob wants to reply to Alice, he simply goes through the same process -"
+" send a message out one of\n"
+"his outbound tunnels targeting one of Alice's inbound tunnels (tunnel 1 "
+"or 2). To make things\n"
+"easier, most messages sent between Alice and Bob are garlic\n"
+"wrapped, bundling the sender's own current lease information so that the "
+"recipient can reply\n"
+"immediately without having to look in the network database for the "
+"current data."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/intro.html:96
+#, python-format
+msgid ""
+"To deal with a wide range of attacks, I2P is fully distributed with no "
+"centralized resources - and\n"
+"hence there are no directory servers keeping statistics regarding the "
+"performance and reliability of\n"
+"routers within the network. As such, each router must keep and maintain "
+"profiles of various routers\n"
+"and is responsible for selecting appropriate peers to meet the anonymity,"
+" performance, and\n"
+"reliability needs of the users, as described in the peer selection\n"
+"page."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/intro.html:105
+#, python-format
+msgid ""
+"The network itself makes use of a significant number of cryptographic\n"
+"techniques and algorithms - a full laundry list includes 2048bit "
+"ElGamal encryption, 256bit AES\n"
+"in CBC mode with PKCS#5 padding, 1024bit DSA signatures, SHA256 hashes, "
+"2048bit Diffie-Hellman\n"
+"negotiated connections with station to station authentication, and ElGamal / AES+SessionTag."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/intro.html:113
+msgid ""
+"Content sent over I2P is encrypted through three layers garlic encryption"
+" (used to verify the\n"
+"delivery of the message to the recipient), tunnel encryption (all "
+"messages passing through a tunnel\n"
+"is encrypted by the tunnel gateway to the tunnel endpoint), and inter "
+"router transport layer\n"
+"encryption (e.g. the TCP transport uses AES256 with ephemeral keys)."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/intro.html:120
+msgid ""
+"End-to-end (I2CP) encryption (client application to server application) "
+"was disabled in I2P release\n"
+"0.6; end-to-end (garlic) encryption (I2P client router to I2P server "
+"router) from Alice's router \"a\"\n"
+"to Bob's router \"h\" remains. Notice the different use of terms! All "
+"data from a to h is end-to-end\n"
+"encrypted, but the I2CP connection between the I2P router and the "
+"applications is not end-to-end\n"
+"encrypted! A and h are the routers of Alice and Bob, while Alice and Bob "
+"in following chart are the\n"
+"applications running atop of I2P."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/intro.html:129
+msgid "End to end layered encryption"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/intro.html:131
+#, python-format
+msgid ""
+"The specific use of these algorithms are outlined elsewhere."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/intro.html:135
+msgid ""
+"The two main mechanisms for allowing people who need strong anonymity to "
+"use the network are\n"
+"explicitly delayed garlic routed messages and more comprehensive tunnels "
+"to include support for\n"
+"pooling and mixing messages. These are currently planned for release 3.0,"
+" but garlic routed messages\n"
+"with no delays and FIFO tunnels are currently in place. Additionally, the"
+" 2.0 release will allow\n"
+"people to set up and operate behind restricted routes (perhaps with "
+"trusted peers), as well as the\n"
+"deployment of more flexible and anonymous transports."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/intro.html:144
+#, python-format
+msgid ""
+"Some questions have been raised with regards to the scalability of I2P, "
+"and reasonably so. There\n"
+"will certainly be more analysis over time, but peer lookup and "
+"integration should be bounded by\n"
+"O(log(N)) due to the network "
+"database's algorithm, while end\n"
+"to end messages should be O(1) (scale free), since messages "
+"go out K hops through the\n"
+"outbound tunnel and another K hops through the inbound tunnel, with K no "
+"longer than 3. The size of\n"
+"the network (N) bears no impact."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/intro.html:153
+msgid "When?"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/intro.html:154
+#, python-format
+msgid ""
+"I2P initially began in Feb 2003 as a proposed modification to Freenet to allow it to use "
+"alternate transports, such as JMS , then grew into its own as an\n"
+"'anonCommFramework' in April 2003, turning into I2P in July, with code "
+"being written in earnest\n"
+"starting in August '03. I2P is currently under development, following the"
+" roadmap."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/intro.html:164
+msgid "Who?"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/intro.html:165
+#, python-format
+msgid ""
+"We have a small team spread around several "
+"continents, working to advance\n"
+"different aspects of the project. We are very open to other developers "
+"who want to get involved and\n"
+"anyone else who would like to contribute in other ways, such as "
+"critiques, peer review, testing,\n"
+"writing I2P enabled applications, or documentation. The entire system is "
+"open source - the router\n"
+"and most of the SDK are outright public domain with some BSD and Cryptix "
+"licensed code, while some\n"
+"applications like I2PTunnel and I2PSnark are GPL. Almost everything is "
+"written in Java (1.5+),\n"
+"though some third party applications are being written in Python and "
+"other languages. The code works\n"
+"on Sun Java SE and other Java Virtual"
+" Machines."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/intro.html:176
+msgid "Where?"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/intro.html:177
+#, python-format
+msgid ""
+"Anyone interested should join us on the IRC channel #i2p (hosted "
+"concurrently on irc.freenode.net,\n"
+"irc.postman.i2p, irc.freshcoffee.i2p, irc.welterde.i2p and "
+"irc.einirc.de). There are currently no\n"
+"scheduled development meetings, however archives"
+" are available."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/intro.html:183
+#, python-format
+msgid "The current source is available in monotone."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/intro.html:188
+#, python-format
+msgid "See the Index to Technical Documentation."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:2
+msgid "The Network Database"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:3
+#: i2p2www/pages/site/docs/spec/updates.html:3
+msgid "October 2013"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:8
+msgid ""
+"I2P's netDb is a specialized distributed database, containing \n"
+"just two types of data - router contact information (RouterInfos) "
+"and destination contact\n"
+"information (LeaseSets). Each piece of data is signed by the "
+"appropriate party and verified\n"
+"by anyone who uses or stores it. In addition, the data has liveliness "
+"information\n"
+"within it, allowing irrelevant entries to be dropped, newer entries to "
+"replace\n"
+"older ones, and protection against certain classes of attack."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:17
+msgid ""
+"The netDb is distributed with a simple technique called \"floodfill\",\n"
+"where a subset of all routers, called \"floodfill routers\", maintains "
+"the distributed database."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:25
+msgid ""
+"When an I2P router wants to contact another router, they need to know "
+"some \n"
+"key pieces of data - all of which are bundled up and signed by the router"
+" into\n"
+"a structure called the \"RouterInfo\", which is distributed with the "
+"SHA256 of the router's identity\n"
+"as the key. The structure itself contains:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:32
+msgid ""
+"The router's identity (a 2048bit ElGamal encryption key, a 1024bit DSA "
+"signing key, and a certificate)"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:33
+msgid ""
+"The contact addresses at which it can be reached (e.g. TCP: example.org "
+"port 4108)"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:34
+msgid "When this was published"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:35
+msgid "A set of arbitrary text options"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:36
+msgid "The signature of the above, generated by the identity's DSA signing key"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:39
+msgid ""
+"The following text options, while not strictly required, are expected\n"
+"to be present:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:45
+msgid ""
+"Capabilities flags - used to indicate floodfill participation, "
+"approximate bandwidth, and perceived reachability"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:48
+msgid "The core library version, always the same as the router version"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:51
+msgid ""
+"Basic network compatibility - A router will refuse to communicate with a "
+"peer having a different netId"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:54
+msgid "Used to determine compatibility with newer features and messages"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:57
+msgid ""
+"Always sent as 90m, for compatibility with an older scheme where routers "
+"published their actual uptime,\n"
+"and only sent tunnel requests to peers whose was more than 60m"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:62
+msgid ""
+"These values are used by other routers for basic decisions.\n"
+"Should we connect to this router? Should we attempt to route a tunnel "
+"through this router?\n"
+"The bandwidth capability flag, in particular, is used only to determine "
+"whether\n"
+"the router meets a minimum threshold for routing tunnels.\n"
+"Above the minimum threshold, the advertised bandwidth is not used or "
+"trusted anywhere\n"
+"in the router, except for display in the user interface and for debugging"
+" and network analysis."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:72
+#, python-format
+msgid ""
+"Additional text options include\n"
+"a small number of statistics about the router's health, which are "
+"aggregated by\n"
+"sites such as %(stats)s\n"
+"for network performance analysis and debugging.\n"
+"These statistics were chosen to provide data crucial to the developers,\n"
+"such as tunnel build success rates, while balancing the need for such "
+"data\n"
+"with the side-effects that could result from revealing this data.\n"
+"Current statistics are limited to:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:83
+msgid "Client and exploratory tunnel build success, reject, and timeout rates"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:84
+msgid "1 hour average number of participating tunnels"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:87
+msgid ""
+"The data published can be seen in the router's user interface,\n"
+"but is not used or trusted within the router.\n"
+"As the network has matured, we have gradually removed most of the "
+"published\n"
+"statistics to improve anonymity, and we plan to remove more in future "
+"releases."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:95
+msgid "RouterInfo specification"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:98
+msgid "RouterInfo Javadoc"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:101
+msgid "RouterInfo Expiration"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:102
+msgid ""
+"RouterInfos have no set expiration time.\n"
+"Each router is free to maintain its own local policy to trade off the "
+"frequency of RouterInfo lookups\n"
+"with memory or disk usage.\n"
+"In the current implementation, there are the following general policies:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:109
+msgid ""
+"There is no expiration during the first hour of uptime, as the persistent"
+" stored data may be old."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:112
+msgid "There is no expiration if there are 25 or less RouterInfos."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:115
+msgid ""
+"As the number of local RouterInfos grows, the expiration time shrinks, in"
+" an attempt to maintain\n"
+"a reasonable number RouterInfos. The expiration time with less than 120 "
+"routers is 72 hours,\n"
+"while expiration time with 300 routers is around 30 hours."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:120
+#, python-format
+msgid ""
+"RouterInfos containing SSU introducers expire in "
+"about an hour, as\n"
+"the introducer list expires in about that time."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:124
+msgid ""
+"Floodfills use a short expiration time (1 hour) for all local "
+"RouterInfos, as valid RouterInfos will\n"
+"be frequently republished to them."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:130
+msgid "RouterInfo Persistent Storage"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:132
+msgid ""
+"RouterInfos are periodically written to disk so that they are available "
+"after a restart."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:139
+msgid ""
+"The second piece of data distributed in the netDb is a \"LeaseSet\" - "
+"documenting\n"
+"a group of tunnel entry points (leases) for a particular client "
+"destination.\n"
+"Each of these leases specify the following information:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:145
+msgid "The tunnel gateway router (by specifying its identity)"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:146
+msgid "The tunnel ID on that router to send messages with (a 4 byte number)"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:147
+msgid "When that tunnel will expire."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:149
+msgid ""
+"The LeaseSet itself is stored in the netDb under\n"
+"the key derived from the SHA256 of the destination."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:154
+msgid "In addition to these leases, the LeaseSet includes:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:158
+msgid ""
+"The destination itself (a 2048bit ElGamal encryption key, 1024bit DSA "
+"signing key and a certificate)"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:159
+msgid ""
+"Additional encryption public key: used for end-to-end encryption of "
+"garlic messages"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:160
+msgid ""
+"Additional signing public key: intended for LeaseSet revocation, but is "
+"currently unused."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:161
+msgid ""
+"Signature of all the LeaseSet data, to make sure the Destination "
+"published the LeaseSet."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:165
+msgid "Lease specification"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:167
+msgid "LeaseSet specification"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:170
+msgid "Lease Javadoc"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:172
+msgid "LeaseSet Javadoc"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:176
+msgid "Unpublished LeaseSets"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:177
+msgid ""
+"A LeaseSet for a destination used only for outgoing connections is "
+"unpublished.\n"
+"It is never sent for publication to a floodfill router.\n"
+"\"Client\" tunnels, such as those for web browsing and IRC clients, are "
+"unpublished.\n"
+"Servers will still be able to send messages back to those unpublished "
+"destinations,\n"
+"because of I2NP storage messages."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:187
+msgid "Revoked LeaseSets"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:188
+msgid ""
+"A LeaseSet may be revoked by publishing a new LeaseSet with zero "
+"leases.\n"
+"Revocations must be signed by the additional signing key in the LeaseSet."
+"\n"
+"Revocations are not fully implemented, and it is unclear if they have any"
+" practical use.\n"
+"This is the only planned use for that signing key, so it is currently "
+"unused."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:195
+msgid "Encrypted LeaseSets"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:196
+msgid ""
+"In an encrypted LeaseSet, all Leases are encrypted with a separate"
+" DSA key.\n"
+"The leases may only be decoded, and thus the destination may only be "
+"contacted,\n"
+"by those with the key.\n"
+"There is no flag or other direct indication that the LeaseSet is "
+"encrypted.\n"
+"Encrypted LeaseSets are not widely used, and it is a topic for future "
+"work to\n"
+"research whether the user interface and implementation of encrypted "
+"LeaseSets could be improved."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:205
+msgid "LeaseSet Expiration"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:206
+msgid ""
+"All Leases (tunnels) are valid for 10 minutes; therefore, a LeaseSet "
+"expires\n"
+"10 minutes after the earliest creation time of all its Leases."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:211
+msgid "LeaseSet Persistent Storage"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:212
+msgid ""
+"There is no persistent storage of LeaseSet data since they expire so "
+"quickly."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:217
+msgid "Bootstrapping"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:218
+msgid ""
+"The netDb is decentralized, however you do need at\n"
+"least one reference to a peer so that the integration process\n"
+"ties you in. This is accomplished by \"reseeding\" your router with the "
+"RouterInfo\n"
+"of an active peer - specifically, by retrieving their "
+"routerInfo-$hash.dat\n"
+"file and storing it in your netDb/ directory. Anyone can "
+"provide\n"
+"you with those files - you can even provide them to others by exposing "
+"your own\n"
+"netDb directory. To simplify the process,\n"
+"volunteers publish their netDb directories (or a subset) on the regular "
+"(non-i2p) network,\n"
+"and the URLs of these directories are hardcoded in I2P.\n"
+"When the router starts up for the first time, it automatically fetches "
+"from\n"
+"one of these URLs, selected at random."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:232
+msgid "Floodfill"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:233
+msgid ""
+"The floodfill netDb is a simple distributed storage mechanism.\n"
+"The storage algorithm is simple: send the data to the closest peer that "
+"has advertised itself\n"
+"as a floodfill router. Then wait 10 seconds, pick another floodfill "
+"router and ask them \n"
+"for the entry to be sent, verifying its proper insertion / distribution. "
+"If the \n"
+"verification peer doesn't reply, or they don't have the entry, the sender"
+" \n"
+"repeats the process. When the peer in the floodfill netDb receives a "
+"netDb \n"
+"store from a peer not in the floodfill netDb, they send it to a subset of"
+" the floodfill netDb-peers.\n"
+"The peers selected are the ones closest (according to the XOR-metric) to a specific key."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:244
+msgid ""
+"Determining who is part of the floodfill netDb is trivial - it is exposed"
+" in each \n"
+"router's published routerInfo as a capability."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:249
+msgid ""
+"Floodfills have no central authority and do not form a \"consensus\" -\n"
+"they only implement a simple DHT overlay."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:256
+msgid "Floodfill Router Opt-in"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:258
+msgid ""
+"Unlike Tor, where the directory servers are hardcoded and trusted,\n"
+"and operated by known entities,\n"
+"the members of the I2P floodfill peer set need not be trusted, and\n"
+"change over time."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:265
+msgid ""
+"To increase reliability of the netDb, and minimize the impact\n"
+"of netDb traffic on a router, floodfill is automatically enabled\n"
+"only on routers that are configured with high bandwidth limits.\n"
+"Routers with high bandwidth limits (which must be manually configured,\n"
+"as the default is much lower) are presumed to be on lower-latency\n"
+"connections, and are more likely to be available 24/7.\n"
+"The current minimum share bandwidth for a floodfill router is 128 "
+"KBytes/sec."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:275
+msgid ""
+"In addition, a router must pass several additional tests for health\n"
+"(outbound message queue time, job lag, etc.) before floodfill operation "
+"is\n"
+"automatically enabled."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:281
+msgid ""
+"With the current rules for automatic opt-in, approximately 6% of\n"
+"the routers in the network are floodfill routers."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:286
+msgid ""
+"While some peers are manually configured to be floodfill,\n"
+"others are simply high-bandwidth routers who automatically volunteer\n"
+"when the number of floodfill peers drops below a threshold.\n"
+"This prevents any long-term network damage from losing most or all\n"
+"floodfills to an attack.\n"
+"In turn, these peers will un-floodfill themselves when there are\n"
+"too many floodfills outstanding."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:296
+msgid "Floodfill Router Roles"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:297
+msgid ""
+"A floodfill router's only services that are in addition to those of non-"
+"floodfill routers\n"
+"are in accepting netDb stores and responding to netDb queries.\n"
+"Since they are generally high-bandwidth, they are more likely to "
+"participate in a high number of tunnels\n"
+"(i.e. be a \"relay\" for others), but this is not directly related to "
+"their distributed database services."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:305
+msgid "Kademlia Closeness Metric"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:306
+msgid ""
+"The netDb uses a simple Kademlia-style XOR metric to determine closeness."
+"\n"
+"The SHA256 hash of the key being looked up or stored is XOR-ed with\n"
+"the hash of the router in question to determine closeness.\n"
+"A modification to this algorithm is done to increase the costs of Sybil attacks.\n"
+"Instead of the SHA256 hash of the key being looked up of stored, the "
+"SHA256 hash is taken\n"
+"of the 32-byte binary key appended with the UTC date represented as an "
+"8-byte ASCII string yyyyMMdd, i.e. SHA256(key + yyyyMMdd).\n"
+"This is called the \"routing key\", and it changes every day at midnight "
+"UTC.\n"
+"The daily transformation of the DHT is sometimes called \"keyspace "
+"rotation\",\n"
+"although it isn't strictly a rotation."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:318
+msgid ""
+"Routing keys are never sent on-the-wire in any I2NP message, they are "
+"only used locally for\n"
+"determination of distance."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:325
+msgid "Storage, Verification, and Lookup Mechanics"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:327
+msgid "RouterInfo Storage to Peers"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:328
+#, python-format
+msgid ""
+"I2NP DatabaseStoreMessages containing the local "
+"RouterInfo are exchanged with peers\n"
+"as a part of the initialization of a NTCP\n"
+"or SSU transport connection."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:335
+msgid "LeaseSet Storage to Peers"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:336
+#, python-format
+msgid ""
+"I2NP DatabaseStoreMessages containing the local "
+"LeaseSet are periodically exchanged with peers\n"
+"by bundling them in a garlic message along with normal traffic from the "
+"related Destination.\n"
+"This allows an initial response, and later responses, to be sent to an "
+"appropriate Lease,\n"
+"without requiring any LeaseSet lookups, or requiring the communicating "
+"Destinations to have published LeaseSets at all."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:344
+msgid ""
+"The DatabaseStoreMessage should be sent to the floodfill that is closest\n"
+"to the current routing key for the RouterInfo or LeaseSet being stored.\n"
+"Currently, the closest floodfill is found by a search in the local "
+"database.\n"
+"Even if that floodfill is not actually closest, it will flood it "
+"\"closer\" by\n"
+"sending it to multiple other floodfills.\n"
+"This provides a high degree of fault-tolerance."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:353
+msgid ""
+"In traditional Kademlia, a peer would do a \"find-closest\" search before"
+" inserting\n"
+"an item in the DHT to the closest target. As the verify operation will "
+"tend to\n"
+"discover closer floodfills if they are present, a router will quickly "
+"improve\n"
+"its knowledge of the DHT \"neighborhood\" for the RouterInfo and "
+"LeaseSets it regularly publishes.\n"
+"While I2NP does not define a \"find-closest\" message, if it becomes "
+"necessary,\n"
+"a router may simply do an iterative search for a key with the least "
+"significant bit flipped\n"
+"(i.e. key ^ 0x01) until no closer peers are received in the "
+"DatabaseSearchReplyMessages.\n"
+"This ensures that the true closest peer will be found even if a more-"
+"distant peer had\n"
+"the netdb item."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:366
+msgid "RouterInfo Storage to Floodfills"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:367
+#, python-format
+msgid ""
+"A router publishes its own RouterInfo by directly connecting to a "
+"floodfill router\n"
+"and sending it a I2NP DatabaseStoreMessage\n"
+"with a nonzero Reply Token. The message is not end-to-end garlic "
+"encrypted,\n"
+"as this is a direct connection, so there are no intervening routers\n"
+"(and no need to hide this data anyway).\n"
+"The floodfill router replies with a\n"
+"I2NP DeliveryStatusMessage,\n"
+"with the Message ID set to the value of the Reply Token."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:381
+msgid "LeaseSet Storage to Floodfills"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:382
+msgid ""
+"Storage of LeaseSets is much more sensitive than for RouterInfos, as a "
+"router\n"
+"must take care that the LeaseSet cannot be associated with the router."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:387
+#, python-format
+msgid ""
+"A router publishes a local LeaseSet by\n"
+"sending a I2NP DatabaseStoreMessage\n"
+"with a nonzero Reply Token over an outbound client tunnel for that "
+"Destination.\n"
+"The message is end-to-end garlic encrypted using the Destination's "
+"Session Key Manager,\n"
+"to hide the message from the tunnel's outbound endpoint.\n"
+"The floodfill router replies with a\n"
+"I2NP DeliveryStatusMessage,\n"
+"with the Message ID set to the value of the Reply Token.\n"
+"This message is sent back to one of the client's inbound tunnels."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:400
+msgid "Flooding"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:401
+#, python-format
+msgid ""
+"After a floodfill router receives a DatabaseStoreMessage containing a\n"
+"valid RouterInfo or LeaseSet which is newer than that previously stored "
+"in its\n"
+"local NetDb, it \"floods\" it.\n"
+"To flood a NetDb entry, it looks up several (currently %(floodsize)s) "
+"floodfill routers closest to the routing key\n"
+"of the NetDb entry. (The routing key is the SHA256 Hash of the "
+"RouterIdentity or Destination with the date (yyyyMMdd) appended.)\n"
+"By flooding to those closest to the key, not closest to itself, the "
+"floodfill ensures that the storage\n"
+"gets to the right place, even if the storing router did not have good "
+"knowledge of the\n"
+"DHT \"neighborhood\" for the routing key."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:412
+#, python-format
+msgid ""
+"The floodfill then directly connects to each of those peers\n"
+"and sends it a I2NP DatabaseStoreMessage\n"
+"with a zero Reply Token. The message is not end-to-end garlic encrypted,\n"
+"as this is a direct connection, so there are no intervening routers\n"
+"(and no need to hide this data anyway).\n"
+"The other routers do not reply or re-flood, as the Reply Token is zero."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:422
+msgid "RouterInfo and LeaseSet Lookup"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:423
+#, python-format
+msgid ""
+"The I2NP DatabaseLookupMessage is used to "
+"request a netdb entry from a floodfill router.\n"
+"Lookups are sent out one of the router's outbound exploratory tunnels.\n"
+"The replies are specified to return via one of the router's inbound "
+"exploratory tunnels."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:429
+msgid ""
+"Lookups are generally sent to the two \"good\" (the connection doesn't "
+"fail) floodfill routers closest to the requested key, in parallel."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:433
+#, python-format
+msgid ""
+"If the key is found locally by the floodfill router, it responds with a\n"
+"I2NP DatabaseStoreMessage.\n"
+"If the key is not found locally by the floodfill router, it responds with"
+" a\n"
+"I2NP DatabaseSearchReplyMessage\n"
+"containing a list of other floodfill routers close to the key."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:441
+msgid ""
+"LeaseSet lookups are garlic encrypted end-to-end as of release 0.9.5.\n"
+"RouterInfo lookups are not encrypted and thus are vulnerable to snooping "
+"by the outbound endpoint\n"
+"(OBEP) of the client tunnel. This is due to the expense of the ElGamal "
+"encryption.\n"
+"RouterInfo lookup encryption may be enabled in a future release."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:448
+msgid ""
+"As of release 0.9.7, replies to a LeaseSet lookup (a DatabaseStoreMessage"
+" or a DatabaseSearchReplyMessage)\n"
+"will be encrypted by including the session key and tag in the lookup.\n"
+"This hides the reply from the inbound gateway (IBGW) of the reply tunnel."
+"\n"
+"Responses to RouterInfo lookups will be encrypted if we enable the lookup"
+" encryption."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:455
+#, python-format
+msgid ""
+"(Reference: Hashing it out in Public Sections "
+"2.2-2.3 for terms below in italics)"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:459
+msgid ""
+"Due to the relatively small size of the network and the flooding "
+"redundancy of 8x,\n"
+"lookups are usually O(1) rather than O(log n) --\n"
+"a router is highly likely to know a floodfill router close enough to the "
+"key to get the answer on the first try.\n"
+"In releases prior to 0.8.9, routers used a lookup redundancy of two\n"
+"(that is, two lookups were performed in parallel to different peers), and"
+"\n"
+"neither recursive nor iterative routing for lookups was "
+"implemented.\n"
+"Queries were sent through multiple routes simultaneously\n"
+"to reduce the chance of query failure."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:470
+msgid ""
+"As of release 0.8.9, iterative lookups are implemented with no "
+"lookup redundancy.\n"
+"This is a more efficient and reliable lookup that will work much better\n"
+"when not all floodfill peers are known, and it removes a serious\n"
+"limitation to network growth. As the network grows and each router knows "
+"only a small\n"
+"subset of the floodfill peers, lookups will become O(log n).\n"
+"Even if the peer does not return references closer to the key, the lookup"
+" continues with\n"
+"the next-closest peer, for added robustness, and to prevent a malicious "
+"floodfill from\n"
+"black-holing a part of the key space. Lookups continue until a total "
+"lookup timeout is reached,\n"
+"or the maximum number of peers is queried."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:482
+msgid ""
+"Node IDs are verifiable in that we use the router hash "
+"directly as both the node ID and the Kademlia key.\n"
+"Incorrect responses that are not closer to the search key are generally "
+"ignored.\n"
+"Given the current size of the network, a router has\n"
+"detailed knowledge of the neighborhood of the destination ID space."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:491
+msgid "RouterInfo Storage Verification"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:492
+#, python-format
+msgid ""
+"Note: RouterInfo verification is disabled as of release 0.9.7.1 to "
+"prevent\n"
+"the attack described in the paper\n"
+"Practical Attacks Against the I2P Network.\n"
+"It is not clear if verification can be redesigned to be done safely."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:499
+msgid ""
+"To verify a storage was successful, a router simply waits about 10 "
+"seconds,\n"
+"then sends a lookup to another floodfill router close to the key\n"
+"(but not the one the store was sent to).\n"
+"Lookups sent out one of the router's outbound exploratory tunnels.\n"
+"Lookups are end-to-end garlic encrypted to prevent snooping by the "
+"outbound endpoint(OBEP)."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:507
+msgid "LeaseSet Storage Verification"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:508
+msgid ""
+"To verify a storage was successful, a router simply waits about 10 "
+"seconds,\n"
+"then sends a lookup to another floodfill router close to the key\n"
+"(but not the one the store was sent to).\n"
+"Lookups sent out one of the outbound client tunnels for the destination "
+"of the LeaseSet being verified.\n"
+"To prevent snooping by the OBEP of the outbound tunnel,\n"
+"lookups are end-to-end garlic encrypted.\n"
+"The replies are specified to return via one of the client's inbound "
+"tunnels."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:518
+msgid ""
+"As of release 0.9.7, replies for both RouterInfo and LeaseSet lookups (a "
+"DatabaseStoreMessage or a DatabaseSearchReplyMessage)\n"
+"will be encrypted,\n"
+"to hide the reply from the inbound gateway (IBGW) of the reply tunnel."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:526
+msgid "Exploration"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:527
+#, python-format
+msgid ""
+"Exploration is a special form of netdb lookup, where a router "
+"attempts to learn about\n"
+"new routers.\n"
+"It does this by sending a floodfill router a I2NP DatabaseLookupMessage, looking for a random "
+"key.\n"
+"As this lookup will fail, the floodfill would normally respond with a\n"
+"I2NP DatabaseSearchReplyMessage containing "
+"hashes of floodfill routers close to the key.\n"
+"This would not be helpful, as the requesting router probably already "
+"knows those floodfills,\n"
+"and it would be impractical to add ALL floodfill routers to the \"don't "
+"include\" field of the lookup.\n"
+"For an exploration query, the requesting router adds a router hash of all"
+" zeros to the\n"
+"\"don't include\" field of the DatabaseLookupMessage.\n"
+"The floodfill will then respond only with non-floodfill routers close to "
+"the requested key."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:541
+msgid "Notes on Lookup Responses"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:542
+msgid ""
+"The response to a lookup request is either a Database Store Message (on "
+"success) or a\n"
+"Database Search Reply Message (on failure). The DSRM contains a 'from' "
+"router hash field\n"
+"to indicate the source of the reply; the DSM does not.\n"
+"The DSRM 'from' field is unauthenticated and may be spoofed or invalid.\n"
+"There are no other response tags. Therefore, when making multiple "
+"requests in parallel, it is\n"
+"difficult to monitor the performance of the various floodfill routers."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:552
+msgid "MultiHoming"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:554
+msgid ""
+"Destinations may be hosted on multiple routers simultaneously, by using "
+"the same\n"
+"private and public keys (traditionally stored in eepPriv.dat files).\n"
+"As both instances will periodically publish their signed LeaseSets to the"
+" floodfill peers,\n"
+"the most recently published LeaseSet will be returned to a peer "
+"requesting a database lookup.\n"
+"As LeaseSets have (at most) a 10 minute lifetime, should a particular "
+"instance go down,\n"
+"the outage will be 10 minutes at most, and generally much less than that."
+"\n"
+"The multihoming function has been verified and is in use by several "
+"services on the network."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:564
+msgid "Threat Analysis"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:565
+#, python-format
+msgid ""
+"Also discussed on the threat model "
+"page."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:569
+msgid ""
+"A hostile user may attempt to harm the network by\n"
+"creating one or more floodfill routers and crafting them to offer\n"
+"bad, slow, or no responses.\n"
+"Some scenarios are discussed below."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:576
+msgid "General Mitigation Through Growth"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:577
+#, python-format
+msgid ""
+"There are currently around %(ffcount)s floodfill routers in the network.\n"
+"Most of the following attacks will become more difficult, or have less "
+"impact,\n"
+"as the network size and number of floodfill routers increase."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:584
+msgid "General Mitigation Through Redundancy"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:585
+#, python-format
+msgid ""
+"Via flooding, all netdb entries are stored on the %(floodsize)s floodfill"
+" routers closest to the key."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:590
+msgid "Forgeries"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:591
+msgid ""
+"All netdb entries are signed by their creators, so no router may forge a\n"
+"RouterInfo or LeaseSet."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:596
+msgid "Slow or Unresponsive"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:597
+#, python-format
+msgid ""
+"Each router maintains an expanded set of statistics in the\n"
+"peer profile for each floodfill router,"
+"\n"
+"covering various quality metrics for that peer.\n"
+"The set includes:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:604
+msgid "Average response time"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:605
+msgid "Percentage of queries answered with the data requested"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:606
+msgid "Percentage of stores that were successfully verified"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:607
+msgid "Last successful store"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:608
+msgid "Last successful lookup"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:609
+msgid "Last response"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:612
+msgid ""
+"Each time a router needs to make a determination on which floodfill "
+"router is closest to a key,\n"
+"it uses these metrics to determine which floodfill routers are \"good\".\n"
+"The methods, and thresholds, used to determine \"goodness\" are "
+"relatively new, and\n"
+"are subject to further analysis and improvement.\n"
+"While a completely unresponsive router will quickly be identified and "
+"avoided,\n"
+"routers that are only sometimes malicious may be much harder to deal with."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:622
+msgid "Sybil Attack (Full Keyspace)"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:623
+#, python-format
+msgid ""
+"An attacker may mount a Sybil attack\n"
+"by creating a large number of floodfill routers spread throughout the "
+"keyspace."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:628
+#, python-format
+msgid ""
+"(In a related example, a researcher recently created a\n"
+"large number of Tor relays.)\n"
+"If successful, this could be an effective DOS attack on the entire "
+"network."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:634
+msgid ""
+"If the floodfills are not sufficiently misbehaving to be marked as "
+"\"bad\" using the peer profile\n"
+"metrics described above, this is a difficult scenario to handle.\n"
+"Tor's response can be much more nimble in the relay case, as the "
+"suspicious relays\n"
+"can be manually removed from the consensus.\n"
+"Some possible responses for the I2P network are listed below, however "
+"none of them is completely satisfactory:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:642
+msgid ""
+"Compile a list of bad router hashes or IPs, and announce the list through"
+" various means\n"
+"(console news, website, forum, etc.); users would have to manually "
+"download the list and\n"
+"add it to their local \"blacklist\"."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:647
+msgid ""
+"Ask everyone in the network to enable floodfill manually (fight Sybil "
+"with more Sybil)"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:648
+msgid "Release a new software version that includes the hardcoded \"bad\" list"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:649
+msgid ""
+"Release a new software version that improves the peer profile metrics and"
+" thresholds,\n"
+"in an attempt to automatically identify the \"bad\" peers."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:653
+msgid ""
+"Add software that disqualifies floodfills if too many of them are in a "
+"single IP block"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:654
+msgid ""
+"Implement an automatic subscription-based blacklist controlled by a "
+"single individual or group.\n"
+"This would essentially implement a portion of the Tor \"consensus\" "
+"model.\n"
+"Unfortunately it would also give a single individual or group the power "
+"to\n"
+"block participation of any particular router or IP in the network,\n"
+"or even to completely shutdown or destroy the entire network."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:663
+msgid "This attack becomes more difficult as the network size grows."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:669
+msgid "Sybil Attack (Partial Keyspace)"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:670
+#, python-format
+msgid ""
+"An attacker may mount a Sybil attack\n"
+"by creating a small number (8-15) of floodfill routers clustered closely "
+"in the keyspace,\n"
+"and distribute the RouterInfos for these routers widely.\n"
+"Then, all lookups and stores for a key in that keyspace would be directed"
+"\n"
+"to one of the attacker's routers.\n"
+"If successful, this could be an effective DOS attack on a particular "
+"eepsite, for example."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:679
+msgid ""
+"As the keyspace is indexed by the cryptographic (SHA256) Hash of the key,"
+"\n"
+"an attacker must use a brute-force method to repeatedly generate router "
+"hashes\n"
+"until he has enough that are sufficiently close to the key.\n"
+"The amount of computational power required for this, which is dependent "
+"on network\n"
+"size, is unknown."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:687
+msgid ""
+"As a partial defense against this attack,\n"
+"the algorithm used to determine Kademlia \"closeness\" varies over time.\n"
+"Rather than using the Hash of the key (i.e. H(k)) to determine closeness,"
+"\n"
+"we use the Hash of the key appended with the current date string, i.e. "
+"H(k + YYYYMMDD).\n"
+"A function called the \"routing key generator\" does this, which "
+"transforms the original key into a \"routing key\".\n"
+"In other words, the entire netdb keyspace \"rotates\" every day at UTC "
+"midnight.\n"
+"Any partial-keyspace attack would have to be regenerated every day, for\n"
+"after the rotation, the attacking routers would no longer be close\n"
+"to the target key, or to each other."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:699
+msgid ""
+"This attack becomes more difficult as the network size grows.\n"
+"However, recent research demonstrates that the keyspace rotation is not "
+"particularly effective.\n"
+"An attacker can precompute numerous router hashes in advance,\n"
+"and only a few routers are sufficient to \"eclipse\" a portion\n"
+"of the keyspace within a half hour after rotation."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:707
+msgid ""
+"One consequence of daily keyspace rotation is that the distributed "
+"network database\n"
+"may become unreliable for a few minutes after the rotation --\n"
+"lookups will fail because the new \"closest\" router has not received a "
+"store yet.\n"
+"The extent of the issue, and methods for mitigation\n"
+"(for example netdb \"handoffs\" at midnight)\n"
+"are a topic for further study."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:717
+msgid "Bootstrap Attacks"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:718
+msgid ""
+"An attacker could attempt to boot new routers into an isolated\n"
+"or majority-controlled network by taking over a reseed website,\n"
+"or tricking the developers into adding his reseed website\n"
+"to the hardcoded list in the router."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:725
+msgid "Several defenses are possible, and most of these are planned:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:729
+msgid ""
+"Disallow fallback from HTTPS to HTTP for reseeding.\n"
+"A MITM attacker could simply block HTTPS, then respond to the HTTP."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:733
+msgid ""
+"Changing the reseed task to fetch a subset of RouterInfos from\n"
+"each of several reseed sites rather than using only a single site"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:737
+msgid ""
+"Creating an out-of-network reseed monitoring service that\n"
+"periodically polls reseed websites and verifies that the\n"
+"data are not stale or inconsistent with other views of the network"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:742
+msgid "Bundling reseed data in the installer"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:745
+msgid "Query Capture"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:746
+#, python-format
+msgid ""
+"See also lookup\n"
+"(Reference: Hashing it out in Public Sections "
+"2.2-2.3 for terms below in italics)"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:751
+msgid ""
+"Similar to a bootstrap attack, an attacker using a floodfill router could"
+" attempt to \"steer\"\n"
+"peers to a subset of routers controlled by him by returning their "
+"references."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:756
+msgid ""
+"This is unlikely to work via exploration, because exploration is a low-"
+"frequency task.\n"
+"Routers acquire a majority of their peer references through normal tunnel"
+" building activity.\n"
+"Exploration results are generally limited to a few router hashes,\n"
+"and each exploration query is directed to a random floodfill router."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:763
+#, python-format
+msgid ""
+"As of release 0.8.9, iterative lookups are implemented.\n"
+"For floodfill router references returned in a\n"
+"I2NP DatabaseSearchReplyMessage\n"
+"response to a lookup,\n"
+"these references are followed if they are closer (or the next closest) to"
+" the lookup key.\n"
+"The requesting router does not trust that the references are\n"
+"closer to the key (i.e. they are verifiably correct.\n"
+"The lookup also does not stop when no closer key is found, but continues "
+"by querying the\n"
+"next-closet node, until the timeout or maximum number of queries is "
+"reached.\n"
+"This prevents a malicious floodfill from black-holing a part of the key "
+"space.\n"
+"Also, the daily keyspace rotation requires an attacker to regenerate a "
+"router info\n"
+"within the desired key space region.\n"
+"This design ensures that the query capture attack described in\n"
+"Hashing it out in Public\n"
+"is much more difficult."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:782
+msgid "DHT-Based Relay Selection"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:783
+#, python-format
+msgid "(Reference: Hashing it out in Public Section 3)"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:787
+#, python-format
+msgid ""
+"This doesn't have much to do with floodfill, but see\n"
+"the peer selection page\n"
+"for a discussion of the vulnerabilities of peer selection for tunnels."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:793
+msgid "Information Leaks"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:794
+#, python-format
+msgid ""
+"(Reference: In Search of an Anonymous and Secure "
+"Lookup Section 3)"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:798
+#, python-format
+msgid ""
+"This paper addresses weaknesses in the \"Finger Table\" DHT lookups used "
+"by Torsk and NISAN.\n"
+"At first glance, these do not appear to apply to I2P. First, the use of "
+"DHT by Torsk and NISAN\n"
+"is significantly different from that in I2P. Second, I2P's network "
+"database lookups are only\n"
+"loosely correlated to the peer "
+"selection and\n"
+"tunnel building processes; only "
+"previously-known peers\n"
+"are used for tunnels.\n"
+"Also, peer selection is unrelated to any notion of DHT key-closeness."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:809
+msgid ""
+"Some of this may actually be more interesting when the I2P network gets "
+"much larger.\n"
+"Right now, each router knows a large proportion of the network, so "
+"looking up a particular\n"
+"Router Info in the network database is not strongly indicative of a "
+"future intent to use\n"
+"that router in a tunnel. Perhaps when the network is 100 times larger, "
+"the lookup may be\n"
+"more correlative. Of course, a larger network makes a Sybil attack that "
+"much harder."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:817
+#, python-format
+msgid ""
+"However, the general issue of DHT information leakage in I2P needs "
+"further investigation.\n"
+"The floodfill routers are in a position to observe queries and gather "
+"information.\n"
+"Certainly, at a level of f = 0.2 (20% malicious nodes, as "
+"specifed in the paper)\n"
+"we expect that many of the Sybil threats we describe\n"
+"(here,\n"
+"here and\n"
+"here)\n"
+"become problematic for several reasons."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:831
+msgid "Moved to the netdb discussion page"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:835
+msgid "End-to-end encryption of additional netDb lookups and responses."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:839
+msgid "Better methods for tracking lookup responses."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/peer-selection.html:2
+msgid "Peer Profiling and Selection"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/peer-selection.html:3
+msgid "July 2010"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/peer-selection.html:8
+msgid "Peer Profiling"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/peer-selection.html:10
+#, python-format
+msgid ""
+"Peer profiling is the process of collecting data based on the "
+"observed performance\n"
+"of other routers or peers, and classifying those peers into groups.\n"
+"Profiling does not use any claimed performance data published by "
+"the peer itself\n"
+"in the network database."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/peer-selection.html:17
+msgid "Profiles are used for two purposes:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/peer-selection.html:19
+msgid "Selecting peers to relay our traffic through, which is discussed below"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/peer-selection.html:20
+#, python-format
+msgid ""
+"Choosing peers from the set of floodfill routers to use for network "
+"database storage and queries,\n"
+"which is discussed on the network database page"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/peer-selection.html:27
+#: i2p2www/pages/site/docs/how/peer-selection.html:187
+#: i2p2www/pages/site/docs/tunnels/implementation.html:286
+msgid "Peer Selection"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/peer-selection.html:28
+msgid ""
+"Peer selection is the process of choosing which routers\n"
+"on the network we want to relay our messages to go through (which peers "
+"will we \n"
+"ask to join our tunnels). To accomplish this, we keep track of how each\n"
+"peer performs (the peer's \"profile\") and use that data to estimate how"
+" \n"
+"fast they are, how often they will be able to accept our requests, and \n"
+"whether they seem to be overloaded or otherwise unable to perform what\n"
+"they agree to reliably."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/peer-selection.html:38
+#, python-format
+msgid ""
+"Unlike some other anonymous networks, in I2P,\n"
+"claimed bandwidth is untrusted and is only used to avoid those "
+"peers\n"
+"advertising very low bandwidth insufficient for routing tunnels.\n"
+"All peer selection is done through profiling.\n"
+"This prevents simple attacks based on peers claiming high bandwidth\n"
+"in order to capture large numbers of tunnels.\n"
+"It also makes\n"
+"timing attacks\n"
+"more difficult."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/peer-selection.html:50
+msgid ""
+"Peer selection is done quite frequently, as a router may maintain a large"
+" number\n"
+"of client and exploratory tunnels, and a tunnel lifetime is only 10 "
+"minutes."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/peer-selection.html:56
+msgid "Further Information"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/peer-selection.html:57
+#, python-format
+msgid ""
+"For more information see the paper\n"
+"Peer Profiling and Selection in the I2P Anonymous "
+"Network\n"
+"presented at PET-CON 2009.1.\n"
+"See below for notes on minor changes since the "
+"paper was published."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/peer-selection.html:65
+msgid "Profiles"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/peer-selection.html:66
+#, python-format
+msgid ""
+"Each peer has a set of data points collected about them, including "
+"statistics \n"
+"about how long it takes for them to reply to a network database query, "
+"how \n"
+"often their tunnels fail, and how many new peers they are able to "
+"introduce \n"
+"us to, as well as simple data points such as when we last heard from them"
+" or\n"
+"when the last communication error occurred. The specific data points "
+"gathered\n"
+"can be found in the code."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/peer-selection.html:75
+msgid ""
+"Profiles are fairly small, a few KB. To control memory usage, the profile"
+" expiration time\n"
+"lessens as the number of profiles grows.\n"
+"Profiles are kept in memory until router shutdown, when they are written "
+"to disk.\n"
+"At startup, the profiles are read so the router need not reinitialize all"
+" profiles,\n"
+"thus allowing a router to quickly re-integrate into the network after "
+"startup."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/peer-selection.html:85
+msgid "Peer Summaries"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/peer-selection.html:86
+msgid ""
+"While the profiles themselves can be considered a summary of a peer's \n"
+"performance, to allow for effective peer selection we break each summary "
+"down \n"
+"into four simple values, representing the peer's speed, its capacity, how"
+" well \n"
+"integrated into the network it is, and whether it is failing."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/peer-selection.html:93
+msgid "Speed"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/peer-selection.html:94
+msgid ""
+"The speed calculation\n"
+"simply goes through the profile and estimates how much data we can\n"
+"send or receive on a single tunnel through the peer in a minute. For "
+"this estimate it just looks at\n"
+"performance in the previous minute."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/peer-selection.html:101
+msgid "Capacity"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/peer-selection.html:102
+msgid ""
+"The capacity calculation\n"
+"simply goes through the profile and estimates how many tunnels the peer\n"
+"would agree to participate in over a given time period. For this "
+"estimate it looks at \n"
+"how many tunnel build requests\n"
+"the peer has accepted, rejected, and dropped, and how many\n"
+"of the agreed-to tunnels later failed.\n"
+"While the calculation is time-weighted so that recent activity counts "
+"more than later activity,\n"
+"statistics up to 48 hours old may be included."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/peer-selection.html:113
+msgid ""
+"Recognizing and avoiding unreliable and unreachable\n"
+"peers is critically important.\n"
+"Unfortunately, as the tunnel building and testing require the "
+"participation of several peers,\n"
+"it is difficult to positively identify the cause of a dropped build "
+"request or test failure.\n"
+"The router assigns a probability of failure to each of the\n"
+"peers, and uses that probability in the capacity calculation.\n"
+"Drops and test failures are weighted much higher than rejections."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/peer-selection.html:123
+msgid "Peer organization"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/peer-selection.html:124
+msgid ""
+"As mentioned above, we drill through each peer's profile to come up with "
+"a \n"
+"few key calculations, and based upon those, we organize each peer into "
+"three\n"
+"groups - fast, high capacity, and standard."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/peer-selection.html:130
+msgid "The groupings are not mutually exclusive, nor are they unrelated:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/peer-selection.html:134
+msgid ""
+"A peer is considered \"high capacity\" if its capacity calculation meets "
+"or \n"
+"exceeds the median of all peers."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/peer-selection.html:138
+msgid ""
+"A peer is considered \"fast\" if they are already \"high capacity\" and "
+"their \n"
+"speed calculation meets or exceeds the median of all peers."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/peer-selection.html:142
+msgid "A peer is considered \"standard\" if it is not \"high capacity\""
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/peer-selection.html:145
+#, python-format
+msgid ""
+"These groupings are implemented in the router's\n"
+"ProfileOrganizer."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/peer-selection.html:150
+msgid "Group size limits"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/peer-selection.html:151
+msgid "The size of the groups may be limited."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/peer-selection.html:156
+msgid ""
+"The fast group is limited to 30 peers.\n"
+"If there would be more, only the ones with the highest speed rating are "
+"placed in the group."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/peer-selection.html:160
+msgid ""
+"The high capacity group is limited to 75 peers (including the fast group)"
+"\n"
+"If there would be more, only the ones with the highest capacity rating "
+"are placed in the group."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/peer-selection.html:164
+msgid ""
+"The standard group has no fixed limit, but is somewhat smaller than the "
+"number of RouterInfos\n"
+"stored in the local network database.\n"
+"On an active router in today's network, there may be about 1000 "
+"RouterInfos and 500 peer profiles\n"
+"(including those in the fast and high capacity groups)"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/peer-selection.html:172
+msgid "Recalculation and Stability"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/peer-selection.html:173
+msgid ""
+"Summaries are recalculated, and peers are resorted into groups, every 45 "
+"seconds."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/peer-selection.html:177
+msgid ""
+"The groups tend to be fairly stable, that is, there is not much \"churn\""
+" in the rankings\n"
+"at each recalculation.\n"
+"Peers in the fast and high capacity groups get more tunnels build through"
+" them, which increases their speed and capacity ratings,\n"
+"which reinforces their presence in the group."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/peer-selection.html:188
+msgid "The router selects peers from the above groups to build tunnels through."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/peer-selection.html:193
+msgid "Peer Selection for Client Tunnels"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/peer-selection.html:194
+msgid ""
+"Client tunnels are used for application traffic, such as for HTTP proxies"
+" and web servers."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/peer-selection.html:198
+msgid ""
+"To reduce the susceptibility to some attacks,\n"
+"and increase performance,\n"
+"peers for building client tunnels are chosen randomly from the smallest "
+"group, which is the \"fast\" group.\n"
+"There is no bias toward selecting peers that were previously participants"
+" in a tunnel for the same client."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/peer-selection.html:206
+msgid "Peer Selection for Exploratory Tunnels"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/peer-selection.html:207
+msgid ""
+"Exploratory tunnels are used for router administrative purposes, such as "
+"network database traffic\n"
+"and testing client tunnels.\n"
+"Exploratory tunnels are also used to contact previously unconnected "
+"routers, which is why\n"
+"they are called \"exploratory\".\n"
+"These tunnels are usually low-bandwidth."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/peer-selection.html:215
+msgid ""
+"Peers for building exploratory tunnels are generally chosen randomly from"
+" the standard group.\n"
+"If the success rate of these build attempts is low compared to the client"
+" tunnel build success rate,\n"
+"the router will select a weighted average of peers randomly from the high"
+" capacity group instead.\n"
+"This helps maintain a satisfactory build success rate even when network "
+"performance is poor.\n"
+"There is no bias toward selecting peers that were previously participants"
+" in an exploratory tunnel."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/peer-selection.html:223
+msgid ""
+"As the standard group includes a very large subset of all peers the "
+"router knows about,\n"
+"exploratory tunnels are essentially built through a random selection of "
+"all peers,\n"
+"until the build success rate becomes too low."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/peer-selection.html:231
+msgid "Restrictions"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/peer-selection.html:232
+msgid ""
+"To prevent some simple attacks, and for performance, there are the "
+"following restrictions:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/peer-selection.html:236
+msgid "Two peers from the same /16 IP space may not be in the same tunnel."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/peer-selection.html:239
+msgid ""
+"A peer may participate in a maximum of 33% of all tunnels created by "
+"the router."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/peer-selection.html:242
+msgid "Peers with extremely low bandwidth are not used."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/peer-selection.html:245
+msgid "Peers for which a recent connection attempt failed are not used."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/peer-selection.html:252
+msgid "Peer Ordering in Tunnels"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/peer-selection.html:253
+#, python-format
+msgid ""
+"Peers are ordered within tunnels to\n"
+"to deal with the predecessor attack\n"
+"(2008 update).\n"
+"More information is on the tunnel "
+"page."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/peer-selection.html:268
+msgid "Continue to analyze an tune speed and capacity calculations as necessary"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/peer-selection.html:271
+msgid ""
+"Implement a more aggressive ejection strategy if necessary to control "
+"memory usage as the network grows"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/peer-selection.html:274
+msgid "Evaluate group size limits"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/peer-selection.html:277
+msgid "Use GeoIP data to include or exclude certain peers, if configured"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/peer-selection.html:283
+#, python-format
+msgid ""
+"For those reading the paper\n"
+"Peer Profiling and Selection in the I2P Anonymous "
+"Network,\n"
+"please keep in mind the following minor changes in I2P since the paper's "
+"publication:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/peer-selection.html:289
+msgid "The Integration calculation is still not used"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/peer-selection.html:290
+msgid "In the paper, \"groups\" are called \"tiers\""
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/peer-selection.html:291
+msgid "The \"Failing\" tier is no longer used"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/peer-selection.html:292
+msgid "The \"Not Failing\" tier is now named \"Standard\""
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/peer-selection.html:301
+msgid "One Cell Enough"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/peer-selection.html:303
+msgid "Tor Entry Guards"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/peer-selection.html:305
+msgid "Murdoch 2007 Paper"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/peer-selection.html:307
+msgid "Tune-up for Tor"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/peer-selection.html:309
+msgid "Low-resource Routing Attacks Against Tor"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:2
+msgid "Introducing I2P"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:5
+msgid "I2P: A scalable framework for anonymous communication"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:7
+msgid "Table of Contents"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:9
+#: i2p2www/pages/site/docs/how/tech-intro.html:24
+#: i2p2www/pages/site/docs/transport/ssu.html:278
+msgid "Introduction"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:11
+msgid "I2P Operation"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:16
+#: i2p2www/pages/site/docs/how/tech-intro.html:401
+msgid "Transport protocols"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:17
+#: i2p2www/pages/site/docs/how/tech-intro.html:458
+msgid "Cryptography"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:25
+msgid ""
+"I2P is a scalable, self organizing, resilient packet switched anonymous \n"
+"network layer, upon which any number of different anonymity or security "
+"conscious \n"
+"applications can operate. Each of these applications may make their own "
+"anonymity, \n"
+"latency, and throughput tradeoffs without worrying about the proper "
+"implementation \n"
+"of a free route mixnet, allowing them to blend their activity with the "
+"larger \n"
+"anonymity set of users already running on top of I2P."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:34
+msgid ""
+"Applications available already provide the full range of typical Internet"
+" activities -\n"
+"anonymous web browsing, web hosting, chat, file sharing, e-mail,\n"
+"blogging and content syndication, newsgroups, as well as several other "
+"applications under development."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:40
+msgid "Web browsing: using any existing browser that supports using a proxy."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:41
+msgid "Chat: IRC, Jabber, I2P-Messenger."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:42
+msgid ""
+"File sharing: I2PSnark, Robert, iMule, \n"
+"I2Phex, PyBit, I2P-bt\n"
+"and others."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:47
+msgid ""
+"E-mail: susimail and I2P-Bote."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:48
+msgid ""
+"Blog: using e.g. the pebble plugin or the distributed blogging software "
+"Syndie."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:49
+msgid ""
+"Distributed Data Store: Save your data redundantly in the Tahoe-LAFS "
+"cloud over I2P."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:50
+msgid "Newsgroups: using any newsgroup reader that supports using a proxy."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:53
+msgid ""
+"Unlike web sites hosted within content distribution networks like Freenet \n"
+"or GNUnet, the services "
+"hosted on \n"
+"I2P are fully interactive - there are traditional web-style search "
+"engines, \n"
+"bulletin boards, blogs you can comment on, database driven sites, and "
+"bridges \n"
+"to query static systems like Freenet without needing to install it "
+"locally."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:61
+msgid ""
+"With all of these anonymity enabled applications, I2P takes on the role \n"
+"of the message oriented middleware - applications say that they want to "
+"send \n"
+"some data to a cryptographic identifier (a \"destination\") and I2P takes"
+" care \n"
+"of making sure it gets there securely and anonymously. I2P also bundles a"
+" \n"
+"simple streaming library to allow I2P's "
+"anonymous \n"
+"best-effort messages to transfer as reliable, in-order streams, "
+"transparently \n"
+"offering a TCP based congestion control algorithm tuned for the high "
+"bandwidth \n"
+"delay product of the network. While there have been several simple SOCKS "
+"proxies \n"
+"available to tie existing applications into the network, their value has "
+"been \n"
+"limited as nearly every application routinely exposes what, in an "
+"anonymous \n"
+"context, is sensitive information. The only safe way to go is to fully "
+"audit \n"
+"an application to ensure proper operation and to assist in that we "
+"provide \n"
+"a series of APIs in various languages which can be used to make the most "
+"out \n"
+"of the network."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:78
+#, python-format
+msgid ""
+"I2P is not a research project - academic, commercial, or governmental, "
+"but \n"
+"is instead an engineering effort aimed at doing whatever is necessary to "
+"provide \n"
+"a sufficient level of anonymity to those who need it. It has been in "
+"active \n"
+"development since early 2003 with one full time developer and a dedicated"
+" \n"
+"group of part time contributors from all over the world. All of the work "
+"done \n"
+"on I2P is open source and freely available on the website, \n"
+"with the majority of the code released outright into the public domain, "
+"though \n"
+"making use of a few cryptographic routines under BSD-style licenses. The "
+"people \n"
+"working on I2P do not control what people release client applications "
+"under, \n"
+"and there are several GPL'ed applications available (I2PTunnel, \n"
+"susimail, I2PSnark, I2P-"
+"Bote, \n"
+"I2Phex and others.).\n"
+"Funding for I2P comes entirely from "
+"donations,\n"
+"and does not receive any tax breaks in any jurisdiction at this time,\n"
+"as many of the developers are themselves anonymous."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:96
+msgid "Operation"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:98
+msgid ""
+"To understand I2P's operation, it is essential to understand a few key "
+"concepts. \n"
+"First, I2P makes a strict separation between the software participating "
+"in \n"
+"the network (a \"router\") and the anonymous endpoints (\"destinations\")"
+" associated \n"
+"with individual applications. The fact that someone is running I2P is not"
+" \n"
+"usually a secret. What is hidden is information on what the user is "
+"doing, \n"
+"if anything at all, as well as what router a particular destination is "
+"connected \n"
+"to. End users will typically have several local destinations on their "
+"router \n"
+"- for instance, one proxying in to IRC servers, another supporting the "
+"user's \n"
+"anonymous webserver (\"eepsite\"), another for an I2Phex instance, "
+"another for \n"
+"torrents, etc."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:111
+msgid ""
+"Another critical concept to understand is the \"tunnel\".\n"
+"A tunnel is a directed path through an explicitly selected list of "
+"routers.\n"
+"Layered encryption is used, so each of the routers can only decrypt a "
+"single layer.\n"
+"The decrypted information contains the IP of the next router, along with\n"
+"the encrypted information to be forwarded.\n"
+"Each tunnel has a starting point (the first router, also known as "
+"\"gateway\")\n"
+"and an end point. Messages can be sent only in one way. To send messages "
+"back,\n"
+"another tunnel is required."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:122
+#: i2p2www/pages/site/docs/tunnels/implementation.html:105
+msgid "Inbound and outbound tunnel schematic"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:124
+msgid "Figure 1: Two types of tunnels exist: inbound and outbound."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:127
+msgid ""
+"Two types of tunnels exist:\n"
+"\"outbound\" tunnels send messages away from the tunnel creator,\n"
+"while \"inbound\" tunnels bring messages to the tunnel creator.\n"
+"Combining these two tunnels allows users to send messages to each other.\n"
+"The sender (\"Alice\" in the above image) sets up an outbound tunnel,\n"
+"while the receiver (\"Bob\" in the above image) creates an inbound "
+"tunnel.\n"
+"The gateway of an inbound tunnel can receive messages from any other user"
+"\n"
+"and will send them on until the endpoint (\"Bob\").\n"
+"The endpoint of the outbound tunnel will need to send the message\n"
+"on to the gateway of the inbound tunnel.\n"
+"To do this, the sender (\"Alice\") adds instructions to her encrypted "
+"message.\n"
+"Once the endpoint of the outbound tunnel decrypts the message,\n"
+"it will have instructions to forward the message to the correct\n"
+"inbound gateway (the gateway to \"Bob\")."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:144
+msgid ""
+"A third critical concept to understand is I2P's \"network "
+"database\" (or \"netDb\") \n"
+"- a pair of algorithms used to share network metadata. The two types of "
+"metadata \n"
+"carried are \"routerInfo\" and \"leaseSets\" - the "
+"routerInfo gives routers the \n"
+"data necessary for contacting a particular router (their public keys, "
+"transport \n"
+"addresses, etc), while the leaseSet gives routers the information "
+"necessary \n"
+"for contacting a particular destination. A leaseSet contains a number of "
+"\"leases\".\n"
+"Each of this leases specifies a tunnel gateway, which allows reaching a "
+"specific destination.\n"
+"The full information contained in a lease:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:155
+msgid "Inbound gateway for a tunnel that allows reaching a specific destination."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:156
+msgid "Time when a tunnel expires."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:157
+msgid ""
+"Pair of public keys to be able to encrypt messages (to send through the "
+"tunnel and reach the destination)."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:159
+msgid ""
+"Routers themselves send their routerInfo to the netDb directly, while "
+"leaseSets are sent through outbound tunnels\n"
+"(leaseSets need to be sent anonymously, to avoid correlating a router "
+"with his leaseSets)."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:164
+msgid ""
+"We can combine the above concepts to build successful connections in the "
+"network."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:168
+msgid ""
+"To build up her own inbound and outbound tunnels, Alice does a lookup in "
+"the netDb to collect routerInfo.\n"
+"This way, she gathers lists of peers she can use as hops in her tunnels.\n"
+"She can then send a build message to the first hop, requesting the "
+"construction of a tunnel and asking\n"
+"that router to send the construction message onward, until the tunnel has"
+" been constructed."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:175
+msgid "Request information on other routers"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:177
+msgid "Build tunnel using router information"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:179
+msgid "Figure 2: Router information is used to build tunnels."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:182
+msgid ""
+"When Alice wants to send a message to Bob, she first does a lookup in the"
+" \n"
+"netDb to find Bob's leaseSet, giving her his current inbound tunnel "
+"gateways. \n"
+"She then picks one of her outbound tunnels and sends the message down it "
+"with \n"
+"instructions for the outbound tunnel's endpoint to forward the message on"
+" \n"
+"to one of Bob's inbound tunnel gateways. When the outbound tunnel "
+"endpoint \n"
+"receives those instructions, it forwards the message as requested, and "
+"when \n"
+"Bob's inbound tunnel gateway receives it, it is forwarded down the tunnel"
+" \n"
+"to Bob's router. If Alice wants Bob to be able to reply to the message, "
+"she \n"
+"needs to transmit her own destination explicitly as part of the message "
+"itself.\n"
+"This can be done by introducing a higher-level layer, which is done in "
+"the\n"
+"streaming library.\n"
+"Alice may also cut down on the response time by bundling her most \n"
+"recent LeaseSet with the message so that Bob doesn't need to do a netDb "
+"lookup \n"
+"for it when he wants to reply, but this is optional."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:199
+msgid "Connect tunnels using LeaseSets"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:199
+msgid "Connect tunnels using leaseSets"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:201
+msgid "Figure 3: LeaseSets are used to connect outbound and inbound tunnels."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:204
+msgid ""
+"While the tunnels themselves have layered encryption to prevent "
+"unauthorized \n"
+"disclosure to peers inside the network (as the transport layer itself "
+"does \n"
+"to prevent unauthorized disclosure to peers outside the network), it is "
+"necessary \n"
+"to add an additional end to end layer of encryption to hide the message "
+"from \n"
+"the outbound tunnel endpoint and the inbound tunnel gateway. This \"garlic \n"
+"encryption\" lets Alice's router wrap up multiple messages into a "
+"single \n"
+"\"garlic message\", encrypted to a particular public key so that "
+"intermediary \n"
+"peers cannot determine either how many messages are within the garlic, "
+"what \n"
+"those messages say, or where those individual cloves are destined. For "
+"typical \n"
+"end to end communication between Alice and Bob, the garlic will be "
+"encrypted \n"
+"to the public key published in Bob's leaseSet, allowing the message to be"
+" \n"
+"encrypted without giving out the public key to Bob's own router."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:219
+msgid ""
+"Another important fact to keep in mind is that I2P is entirely message "
+"based \n"
+"and that some messages may be lost along the way. Applications using I2P "
+"can \n"
+"use the message oriented interfaces and take care of their own congestion"
+" \n"
+"control and reliability needs, but most would be best served by reusing "
+"the \n"
+"provided streaming library to view I2P as "
+"a streams \n"
+"based network."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:229
+msgid ""
+"Both inbound and outbound tunnels work along similar principles.\n"
+"The tunnel gateway accumulates a number of tunnel messages, eventually "
+"preprocessing \n"
+"them into something for tunnel delivery. Next, the gateway encrypts that "
+"preprocessed \n"
+"data and forwards it to the first hop. That peer and subsequent tunnel "
+"participants \n"
+"add on a layer of encryption after verifying that it isn't a duplicate "
+"before \n"
+"forward it on to the next peer. Eventually, the message arrives at the "
+"endpoint \n"
+"where the messages are split out again and forwarded on as requested. The"
+" \n"
+"difference arises in what the tunnel's creator does - for inbound "
+"tunnels, \n"
+"the creator is the endpoint and they simply decrypt all of the layers "
+"added, \n"
+"while for outbound tunnels, the creator is the gateway and they pre-"
+"decrypt \n"
+"all of the layers so that after all of the layers of per-hop encryption "
+"are \n"
+"added, the message arrives in the clear at the tunnel endpoint."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:244
+msgid ""
+"The choice of specific peers to pass on messages as well as their "
+"particular \n"
+"ordering is important to understanding both I2P's anonymity and "
+"performance \n"
+"characteristics. While the network database (below) has its own criteria "
+"for \n"
+"picking what peers to query and store entries on, tunnel creators may use"
+" any peers \n"
+"in the network in any order (and even any number of times) in a single "
+"tunnel. \n"
+"If perfect latency and capacity data were globally known, selection and "
+"ordering \n"
+"would be driven by the particular needs of the client in tandem with "
+"their \n"
+"threat model. Unfortunately, latency and capacity data is not trivial to "
+"gather \n"
+"anonymously, and depending upon untrusted peers to provide this "
+"information \n"
+"has its own serious anonymity implications."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:257
+msgid ""
+"From an anonymity perspective, the simplest technique would be to pick "
+"peers \n"
+"randomly from the entire network, order them randomly and use those peers"
+" \n"
+"in that order for all eternity. From a performance perspective, the "
+"simplest \n"
+"technique would be to pick the fastest peers with the necessary spare "
+"capacity, \n"
+"spreading the load across different peers to handle transparent failover,"
+" \n"
+"and to rebuild the tunnel whenever capacity information changes. While "
+"the \n"
+"former is both brittle and inefficient, the later requires inaccessible "
+"information \n"
+"and offers insufficient anonymity. I2P is instead working on offering a "
+"range \n"
+"of peer selection strategies, coupled with anonymity aware measurement "
+"code \n"
+"to organize the peers by their profiles."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:270
+msgid ""
+"As a base, I2P is constantly profiling the peers with which it interacts"
+" \n"
+"with by measuring their indirect behavior - for instance, when a peer "
+"responds \n"
+"to a netDb lookup in 1.3 seconds, that round trip latency is recorded in "
+"the \n"
+"profiles for all of the routers involved in the two tunnels (inbound and "
+"outbound) \n"
+"through which the request and response passed, as well as the queried "
+"peer's \n"
+"profile. Direct measurement, such as transport layer latency or "
+"congestion, \n"
+"is not used as part of the profile, as it can be manipulated and "
+"associated \n"
+"with the measuring router, exposing them to trivial attacks. While "
+"gathering \n"
+"these profiles, a series of calculations are run on each to summarize its"
+" \n"
+"performance - its latency, capacity to handle lots of activity, whether "
+"they \n"
+"are currently overloaded, and how well integrated into the network they "
+"seem \n"
+"to be. These calculations are then compared for active peers to organize "
+"the \n"
+"routers into four tiers - fast and high capacity, high capacity, not "
+"failing, \n"
+"and failing. The thresholds for those tiers are determined dynamically, "
+"and \n"
+"while they currently use fairly simple algorithms, alternatives exist."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:288
+msgid ""
+"Using this profile data, the simplest reasonable peer selection strategy"
+" \n"
+"is to pick peers randomly from the top tier (fast and high capacity), and"
+" \n"
+"this is currently deployed for client tunnels. Exploratory tunnels (used "
+"for \n"
+"netDb and tunnel management) pick peers randomly from the \"not failing\""
+" tier \n"
+"(which includes routers in 'better' tiers as well), allowing the peer to "
+"sample \n"
+"routers more widely, in effect optimizing the peer selection through "
+"randomized \n"
+"hill climbing. These strategies alone do however leak information "
+"regarding \n"
+"the peers in the router's top tier through predecessor and netDb "
+"harvesting \n"
+"attacks. In turn, several alternatives exist which, while not balancing "
+"the \n"
+"load as evenly, will address the attacks mounted by particular classes of"
+" \n"
+"adversaries."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:302
+msgid ""
+"By picking a random key and ordering the peers according to their XOR "
+"distance \n"
+"from it, the information leaked is reduced in predecessor and harvesting "
+"attacks \n"
+"according to the peers' failure rate and the tier's churn. Another simple"
+" \n"
+"strategy for dealing with netDb harvesting attacks is to simply fix the "
+"inbound \n"
+"tunnel gateway(s) yet randomize the peers further on in the tunnels. To "
+"deal \n"
+"with predecessor attacks for adversaries which the client contacts, the "
+"outbound \n"
+"tunnel endpoints would also remain fixed. The selection of which peer to "
+"fix \n"
+"on the most exposed point would of course need to have a limit to the "
+"duration, \n"
+"as all peers fail eventually, so it could either be reactively adjusted "
+"or \n"
+"proactively avoided to mimic a measured mean time between failures of "
+"other \n"
+"routers. These two strategies can in turn be combined, using a fixed "
+"exposed \n"
+"peer and an XOR based ordering within the tunnels themselves. A more "
+"rigid \n"
+"strategy would fix the exact peers and ordering of a potential tunnel, "
+"only \n"
+"using individual peers if all of them agree to participate in the same "
+"way \n"
+"each time. This varies from the XOR based ordering in that the "
+"predecessor \n"
+"and successor of each peer is always the same, while the XOR only makes "
+"sure \n"
+"their order doesn't change."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:322
+#, python-format
+msgid ""
+"As mentioned before, I2P currently (release 0.8) includes the tiered \n"
+"random strategy above, with XOR-based ordering. A \n"
+"more detailed discussion of the mechanics involved in tunnel operation, "
+"management, \n"
+"and peer selection can be found in the tunnel "
+"spec."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:330
+#, python-format
+msgid ""
+"As mentioned earlier, I2P's netDb works to share the network's metadata.\n"
+"This is detailed in the network database page,\n"
+"but a basic explanation is available below."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:336
+msgid ""
+"A percentage of I2P users are appointed as 'floodfill peers'.\n"
+"Currently, I2P installations that have a lot of bandwidth and are fast "
+"enough,\n"
+"will appoint themselves as floodfill as soon as the number of existing "
+"floodfill routers\n"
+"drops too low."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:343
+#, python-format
+msgid ""
+"Other I2P routers will store their data and lookup data by sending simple"
+" 'store' and 'lookup' queries to the floodfills.\n"
+"If a floodfill router receives a 'store' query, it will spread the "
+"information to other floodfill routers\n"
+"using the Kademlia "
+"algorithm.\n"
+"The 'lookup' queries currently function differently, to avoid an "
+"important\n"
+"security issue.\n"
+"When a lookup is done, the floodfill router will not forward the lookup "
+"to other peers,\n"
+"but will always answer by itself (if it has the requested data)."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:353
+msgid "Two types of information are stored in the network database."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:357
+msgid ""
+"A RouterInfo stores information on a specific I2P router and how "
+"to contact it"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:358
+msgid ""
+"A LeaseSet stores information on a specific destination (e.g. I2P "
+"website, e-mail server...)"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:360
+msgid ""
+"All of this information is signed by the publishing party and verified by"
+" any I2P router using or storing the information.\n"
+"In addition, the data contains timing information, to avoid storage of "
+"old entries and possible attacks.\n"
+"This is also why I2P bundles the necessary code for maintaining the "
+"correct time, occasionally querying some SNTP servers \n"
+"(the pool.ntp.org round robin by"
+" default)\n"
+"and detecting skew between routers at the transport layer."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:368
+msgid "Some additional remarks are also important."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:373
+msgid "Unpublished and encrypted leasesets:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:374
+msgid ""
+"One could only want specific people to be able to reach a destination.\n"
+"This is possible by not publishing the destination in the netDb. You will"
+" however have to transmit the destination by other means.\n"
+"An alternative are the 'encrypted leaseSets'. These leaseSets can only be"
+" decoded by people with access to the decryption key."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:381
+msgid "Bootstrapping:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:382
+msgid ""
+"Bootstrapping the netDb is quite simple. Once a router manages to receive"
+" a single routerInfo of a reachable peer,\n"
+"it can query that router for references to other routers in the network.\n"
+"Currently, a number of users post their routerInfo files to a website to "
+"make this information available.\n"
+"I2P automatically connects to one of these websites to gather routerInfo "
+"files and bootstrap."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:390
+msgid "Lookup scalability:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:391
+msgid ""
+"Lookups in the I2P network are not forwarded to other netDb routers.\n"
+"Currently, this is not a major problem, since the network is not very "
+"large.\n"
+"However, as the network grows, not all routerInfo and leaseSet files will"
+" be present\n"
+"on each netDb router. This will cause a deterioration of the percentage "
+"of successful lookups.\n"
+"Because of this, refinements to the netDb will be done in the next "
+"releases."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:402
+msgid ""
+"Communication between routers needs to provide confidentiality and "
+"integrity \n"
+"against external adversaries while authenticating that the router "
+"contacted \n"
+"is the one who should receive a given message. The particulars of how "
+"routers \n"
+"communicate with other routers aren't critical - three separate protocols"
+" \n"
+"have been used at different points to provide those bare necessities."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:410
+#, python-format
+msgid ""
+"I2P started with a TCP-based protocol which \n"
+"has since been disabled. Then, to accommodate the need for high degree "
+"communication \n"
+"(as a number of routers will end up speaking with many others), I2P moved"
+" \n"
+"from a TCP based transport to a UDP-based one - "
+"\"Secure \n"
+"Semireliable UDP\", or \"SSU\"."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:418
+#, python-format
+msgid "As described in the SSU spec:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:422
+msgid ""
+"The goal of this protocol is to provide secure, authenticated, \n"
+"semireliable and unordered message delivery, exposing only a minimal "
+"amount \n"
+"of data easily discernible to third parties. It should support high "
+"degree \n"
+"communication as well as TCP-friendly congestion control and may include"
+" \n"
+"PMTU detection. It should be capable of efficiently moving bulk data at "
+"rates \n"
+"sufficient for home users. In addition, it should support techniques for "
+"addressing \n"
+"network obstacles, like most NATs or firewalls."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:432
+#, python-format
+msgid ""
+"Following the introduction of SSU, after issues with congestion collapse"
+" \n"
+"appeared, a new NIO-based TCP transport called NTCP \n"
+"was implemented. It is enabled by default for outbound connections only. "
+"Those \n"
+"who configure their NAT/firewall to allow inbound connections and specify"
+" \n"
+"the external host and port (dyndns/etc is ok) on /config.jsp can receive "
+"inbound \n"
+"connections. As NTCP is NIO based, so it doesn't suffer from the 1 thread"
+" \n"
+"per connection issues of the old TCP transport."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:442
+msgid ""
+"I2P supports multiple transports simultaneously. A particular transport \n"
+"for an outbound connection is selected with \"bids\". Each transport bids"
+" for \n"
+"the connection and the relative value of these bids assigns the priority."
+" \n"
+"Transports may reply with different bids, depending on whether there is "
+"already \n"
+"an established connection to the peer."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:450
+#, python-format
+msgid ""
+"The current implementation ranks NTCP as the highest-priority transport \n"
+"for outbound connections in most situations. SSU is enabled for both "
+"outbound \n"
+"and inbound connections. Your firewall and your I2P router must be "
+"configured \n"
+"to allow inbound NTCP connections. For further information see the NTCP \n"
+"page."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:459
+msgid ""
+"A bare minimum set of cryptographic primitives are combined together to \n"
+"provide I2P's layered defenses against a variety of adversaries. At the "
+"lowest \n"
+"level, inter router communication is protected by the transport layer "
+"security \n"
+"- SSU encrypts each packet with AES256/CBC with both an explicit IV and "
+"MAC \n"
+"(HMAC-MD5-128) after agreeing upon an ephemeral session key through a "
+"2048bit \n"
+"Diffie-Hellman exchange, station-to-station authentication with the other"
+" \n"
+"router's DSA key, plus each network message has their own hash for local "
+"integrity \n"
+"checking. Tunnel messages passed over the "
+"transports \n"
+"have their own layered AES256/CBC encryption with an explicit IV and "
+"verified \n"
+"at the tunnel endpoint with an additional SHA256 hash. Various other "
+"messages \n"
+"are passed along inside \"garlic messages\", which are encrypted with "
+"ElGamal/AES+SessionTags \n"
+"(explained below)."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:474
+msgid "Garlic messages"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:475
+msgid ""
+"Garlic messages are an extension of \"onion\" layered encryption, "
+"allowing \n"
+"the contents of a single message to contain multiple \"cloves\" - fully "
+"formed \n"
+"messages alongside their own instructions for delivery. Messages are "
+"wrapped \n"
+"into a garlic message whenever the message would otherwise be passing in "
+"cleartext \n"
+"through a peer who should not have access to the information - for "
+"instance, \n"
+"when a router wants to ask another router to participate in a tunnel, "
+"they \n"
+"wrap the request inside a garlic, encrypt that garlic to the receiving "
+"router's \n"
+"2048bit ElGamal public key, and forward it through a tunnel. Another "
+"example \n"
+"is when a client wants to send a message to a destination - the sender's "
+"router \n"
+"will wrap up that data message (alongside some other messages) into a "
+"garlic, \n"
+"encrypt that garlic to the 2048bit ElGamal public key published in the "
+"recipient's \n"
+"leaseSet, and forward it through the appropriate tunnels."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:490
+msgid ""
+"The \"instructions\" attached to each clove inside the encryption layer "
+"includes \n"
+"the ability to request that the clove be forwarded locally, to a remote "
+"router, \n"
+"or to a remote tunnel on a remote router. There are fields in those "
+"instructions \n"
+"allowing a peer to request that the delivery be delayed until a certain "
+"time \n"
+"or condition has been met, though they won't be honored until the nontrivial \n"
+"delays are deployed. It is possible to explicitly route garlic "
+"messages \n"
+"any number of hops without building tunnels, or even to reroute tunnel "
+"messages \n"
+"by wrapping them in garlic messages and forwarding them a number of hops "
+"prior \n"
+"to delivering them to the next hop in the tunnel, but those techniques "
+"are \n"
+"not currently used in the existing implementation."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:503
+msgid "Session tags"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:504
+msgid ""
+"As an unreliable, unordered, message based system, I2P uses a simple "
+"combination \n"
+"of asymmetric and symmetric encryption algorithms to provide data "
+"confidentiality \n"
+"and integrity to garlic messages. As a whole, the combination is referred"
+" \n"
+"to as ElGamal/AES+SessionTags, but that is an excessively verbose way to "
+"describe \n"
+"the simple use of 2048bit ElGamal, AES256, SHA256 and 32 byte nonces."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:543
+msgid ""
+"Session tags themselves have a very short lifetime, after which they are"
+" \n"
+"discarded if not used. In addition, the quantity stored for each key is "
+"limited, \n"
+"as are the number of keys themselves - if too many arrive, either new or "
+"old \n"
+"messages may be dropped. The sender keeps track whether messages using "
+"session \n"
+"tags are getting through, and if there isn't sufficient communication it "
+"may \n"
+"drop the ones previously assumed to be properly delivered, reverting back"
+" \n"
+"to the full expensive ElGamal encryption."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:553
+msgid ""
+"One alternative is to transmit only a single session tag, and from that,"
+" \n"
+"seed a deterministic PRNG for determining what tags to use or expect. By "
+"keeping \n"
+"this PRNG roughly synchronized between the sender and recipient (the "
+"recipient \n"
+"precomputes a window of the next e.g. 50 tags), the overhead of "
+"periodically \n"
+"bundling a large number of tags is removed, allowing more options in the "
+"space/time \n"
+"tradeoff, and perhaps reducing the number of ElGamal encryptions "
+"necessary. \n"
+"However, it would depend upon the strength of the PRNG to provide the "
+"necessary \n"
+"cover against internal adversaries, though perhaps by limiting the amount"
+" \n"
+"of times each PRNG is used, any weaknesses can be minimized. At the "
+"moment, \n"
+"there are no immediate plans to move towards these synchronized PRNGs."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:566
+msgid "Future"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:567
+msgid ""
+"While I2P is currently functional and sufficient for many scenarios, "
+"there \n"
+"are several areas which require further improvement to meet the needs of "
+"those \n"
+"facing more powerful adversaries as well as substantial user experience "
+"optimization."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:573
+msgid "Restricted route operation"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:574
+msgid ""
+"I2P is an overlay network designed to be run on top of a functional "
+"packet \n"
+"switched network, exploiting the end to end principle to offer anonymity "
+"and \n"
+"security. While the Internet no longer fully embraces the end to end "
+"principle\n"
+"(due to the usage of NAT), \n"
+"I2P does require a substantial portion of the network to be reachable - "
+"there \n"
+"may be a number of peers along the edges running using restricted routes,"
+" \n"
+"but I2P does not include an appropriate routing algorithm for the "
+"degenerate \n"
+"case where most peers are unreachable. It would, however work on top of a"
+" \n"
+"network employing such an algorithm."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:586
+msgid ""
+"Restricted route operation, where there are limits to what peers are "
+"reachable \n"
+"directly, has several different functional and anonymity implications, "
+"dependent \n"
+"upon how the restricted routes are handled. At the most basic level, "
+"restricted \n"
+"routes exist when a peer is behind a NAT or firewall which does not allow"
+" \n"
+"inbound connections. This was largely addressed in I2P 0.6.0.6 by "
+"integrating \n"
+"distributed hole punching into the transport layer, allowing people "
+"behind \n"
+"most NATs and firewalls to receive unsolicited connections without any "
+"configuration. \n"
+"However, this does not limit the exposure of the peer's IP address to "
+"routers \n"
+"inside the network, as they can simply get introduced to the peer through"
+" \n"
+"the published introducer."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:599
+msgid ""
+"Beyond the functional handling of restricted routes, there are two levels"
+" \n"
+"of restricted operation that can be used to limit the exposure of one's "
+"IP \n"
+"address - using router-specific tunnels for communication, and offering "
+"'client \n"
+"routers'. For the former, routers can either build a new pool of tunnels "
+"or \n"
+"reuse their exploratory pool, publishing the inbound gateways to some of "
+"them \n"
+"as part of their routerInfo in place of their transport addresses. When a"
+" \n"
+"peer wants to get in touch with them, they see those tunnel gateways in "
+"the \n"
+"netDb and simply send the relevant message to them through one of the "
+"published \n"
+"tunnels. If the peer behind the restricted route wants to reply, it may "
+"do \n"
+"so either directly (if they are willing to expose their IP to the peer) "
+"or \n"
+"indirectly through their outbound tunnels. When the routers that the peer"
+" \n"
+"has direct connections to want to reach it (to forward tunnel messages, "
+"for \n"
+"instance), they simply prioritize their direct connection over the "
+"published \n"
+"tunnel gateway. The concept of 'client routers' simply extends the "
+"restricted \n"
+"route by not publishing any router addresses. Such a router would not "
+"even \n"
+"need to publish their routerInfo in the netDb, merely providing their "
+"self \n"
+"signed routerInfo to the peers that it contacts (necessary to pass the "
+"router's \n"
+"public keys). Both levels of restricted route operation are planned for "
+"I2P \n"
+"2.0."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:621
+msgid ""
+"There are tradeoffs for those behind restricted routes, as they would "
+"likely \n"
+"participate in other people's tunnels less frequently, and the routers "
+"which \n"
+"they are connected to would be able to infer traffic patterns that would "
+"not \n"
+"otherwise be exposed. On the other hand, if the cost of that exposure is "
+"less \n"
+"than the cost of an IP being made available, it may be worthwhile. This, "
+"of \n"
+"course, assumes that the peers that the router behind a restricted route "
+"contacts \n"
+"are not hostile - either the network is large enough that the probability"
+" \n"
+"of using a hostile peer to get connected is small enough, or trusted (and"
+" \n"
+"perhaps temporary) peers are used instead."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:633
+msgid "Variable latency"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:634
+msgid ""
+"Even though the bulk of I2P's initial efforts have been on low latency "
+"communication, \n"
+"it was designed with variable latency services in mind from the "
+"beginning. \n"
+"At the most basic level, applications running on top of I2P can offer the"
+" \n"
+"anonymity of medium and high latency communication while still blending "
+"their \n"
+"traffic patterns in with low latency traffic. Internally though, I2P can "
+"offer \n"
+"its own medium and high latency communication through the garlic "
+"encryption \n"
+"- specifying that the message should be sent after a certain delay, at a "
+"certain \n"
+"time, after a certain number of messages have passed, or another mix "
+"strategy. \n"
+"With the layered encryption, only the router that the clove exposed the "
+"delay \n"
+"request would know that the message requires high latency, allowing the "
+"traffic \n"
+"to blend in further with the low latency traffic. Once the transmission "
+"precondition \n"
+"is met, the router holding on to the clove (which itself would likely be "
+"a \n"
+"garlic message) simply forwards it as requested - to a router, to a "
+"tunnel, \n"
+"or, most likely, to a remote client destination."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:651
+msgid ""
+"There are a substantial number of ways to exploit this capacity for high"
+" \n"
+"latency comm in I2P, but for the moment, doing so has been scheduled for "
+"the \n"
+"I2P 3.0 release. In the meantime, those requiring the anonymity that high"
+" \n"
+"latency comm can offer should look towards the application layer to "
+"provide \n"
+"it."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:659
+msgid "Open questions"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:661
+msgid "How to get rid of the timing constraint?"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:662
+msgid "Can we deal with the sessionTags more efficiently?"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:663
+msgid ""
+"What, if any, batching/mixing strategies should be made available on the "
+"tunnels?"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:664
+msgid ""
+"What other tunnel peer selection and ordering strategies should be "
+"available?"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:667
+msgid "Similar systems"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:669
+msgid ""
+"I2P's architecture builds on the concepts of message oriented middleware,"
+" \n"
+"the topology of DHTs, the anonymity and cryptography of free route "
+"mixnets, \n"
+"and the adaptability of packet switched networking. The value comes not "
+"from \n"
+"novel concepts of algorithms though, but from careful engineering "
+"combining \n"
+"the research results of existing systems and papers. While there are a "
+"few \n"
+"similar efforts worth reviewing, both for technical and functional "
+"comparisons, \n"
+"two in particular are pulled out here - Tor and Freenet."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:679
+#, python-format
+msgid "See also the Network Comparisons Page."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:684
+#: i2p2www/pages/site/docs/how/tech-intro.html:749
+msgid "website"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:686
+msgid ""
+"At first glance, Tor and I2P have many functional and anonymity related \n"
+"similarities. While I2P's development began before we were aware of the "
+"early \n"
+"stage efforts on Tor, many of the lessons of the original onion routing "
+"and \n"
+"ZKS efforts were integrated into I2P's design. Rather than building an "
+"essentially \n"
+"trusted, centralized system with directory servers, I2P has a self "
+"organizing \n"
+"network database with each peer taking on the responsibility of profiling"
+" \n"
+"other routers to determine how best to exploit available resources. "
+"Another \n"
+"key difference is that while both I2P and Tor use layered and ordered "
+"paths \n"
+"(tunnels and circuits/streams), I2P is fundamentally a packet switched "
+"network, \n"
+"while Tor is fundamentally a circuit switched one, allowing I2P to "
+"transparently \n"
+"route around congestion or other network failures, operate redundant "
+"pathways, \n"
+"and load balance the data across available resources. While Tor offers "
+"the \n"
+"useful outproxy functionality by offering integrated outproxy discovery "
+"and \n"
+"selection, I2P leaves such application layer decisions up to applications"
+" \n"
+"running on top of I2P - in fact, I2P has even externalized the TCP-like "
+"streaming \n"
+"library itself to the application layer, allowing developers to "
+"experiment \n"
+"with different strategies, exploiting their domain specific knowledge to "
+"offer \n"
+"better performance."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:707
+msgid ""
+"From an anonymity perspective, there is much similarity when the core "
+"networks \n"
+"are compared. However, there are a few key differences. When dealing with"
+" \n"
+"an internal adversary or most external adversaries, I2P's simplex tunnels"
+" \n"
+"expose half as much traffic data than would be exposed with Tor's duplex "
+"circuits \n"
+"by simply looking at the flows themselves - an HTTP request and response "
+"would \n"
+"follow the same path in Tor, while in I2P the packets making up the "
+"request \n"
+"would go out through one or more outbound tunnels and the packets making "
+"up \n"
+"the response would come back through one or more different inbound "
+"tunnels. \n"
+"While I2P's peer selection and ordering strategies should sufficiently "
+"address \n"
+"predecessor attacks, should a switch to bidirectional tunnels be "
+"necessary,\n"
+"we could simply build an inbound and outbound tunnel along the same "
+"routers."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:721
+msgid ""
+"Another anonymity issue comes up in Tor's use of telescopic tunnel "
+"creation, \n"
+"as simple packet counting and timing measurements as the cells in a "
+"circuit \n"
+"pass through an adversary's node exposes statistical information "
+"regarding \n"
+"where the adversary is within the circuit. I2P's unidirectional tunnel "
+"creation \n"
+"with a single message so that this data is not exposed. Protecting the "
+"position \n"
+"in a tunnel is important, as an adversary would otherwise be able to "
+"mount \n"
+"a series of powerful predecessor, intersection, and traffic confirmation "
+"attacks."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:731
+msgid ""
+"Tor's support for a second tier of \"onion proxies\" does offer a non-"
+"trivial \n"
+"degree of anonymity while requiring a low cost of entry, while I2P will "
+"not \n"
+"offer this topology until 2.0."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:737
+msgid ""
+"On the whole, Tor and I2P complement each other in their focus - Tor "
+"works \n"
+"towards offering high speed anonymous Internet outproxying, while I2P "
+"works \n"
+"towards offering a decentralized resilient network in itself. In theory, "
+"both \n"
+"can be used to achieve both purposes, but given limited development "
+"resources, \n"
+"they both have their strengths and weaknesses. The I2P developers have "
+"considered \n"
+"the steps necessary to modify Tor to take advantage of I2P's design, but "
+"concerns \n"
+"of Tor's viability under resource scarcity suggest that I2P's packet "
+"switching \n"
+"architecture will be able to exploit scarce resources more effectively."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:751
+msgid ""
+"Freenet played a large part in the initial stages of I2P's design - "
+"giving \n"
+"proof to the viability of a vibrant pseudonymous community completely "
+"contained \n"
+"within the network, demonstrating that the dangers inherent in outproxies"
+" \n"
+"could be avoided. The first seed of I2P began as a replacement "
+"communication \n"
+"layer for Freenet, attempting to factor out the complexities of a "
+"scalable, \n"
+"anonymous and secure point to point communication from the complexities "
+"of \n"
+"a censorship resistant distributed data store. Over time however, some of"
+" \n"
+"the anonymity and scalability issues inherent in Freenet's algorithms "
+"made \n"
+"it clear that I2P's focus should stay strictly on providing a generic "
+"anonymous \n"
+"communication layer, rather than as a component of Freenet. Over the "
+"years, \n"
+"the Freenet developers have come to see the weaknesses in the older "
+"design, \n"
+"prompting them to suggest that they will require a \"premix\" layer to "
+"offer \n"
+"substantial anonymity. In other words, Freenet needs to run on top of a "
+"mixnet \n"
+"such as I2P or Tor, with \"client nodes\" requesting and publishing data "
+"through \n"
+"the mixnet to the \"server nodes\" which then fetch and store the data "
+"according \n"
+"to Freenet's heuristic distributed data storage algorithms."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:770
+msgid ""
+"Freenet's functionality is very complementary to I2P's, as Freenet "
+"natively \n"
+"provides many of the tools for operating medium and high latency systems,"
+" \n"
+"while I2P natively provides the low latency mix network suitable for "
+"offering \n"
+"adequate anonymity. The logic of separating the mixnet from the "
+"censorship-\n"
+"resistant distributed data store still seems self-evident from an "
+"engineering, \n"
+"anonymity, security, and resource allocation perspective, so hopefully "
+"the \n"
+"Freenet team will pursue efforts in that direction, if not simply reusing"
+" \n"
+"(or helping to improve, as necessary) existing mixnets like I2P or Tor."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:781
+msgid ""
+"It is worth mentioning that there has recently been discussion and work \n"
+"by the Freenet developers on a \"globally scalable darknet\" using "
+"restricted \n"
+"routes between peers of various trust. While insufficient information has"
+" \n"
+"been made publicly available regarding how such a system would operate "
+"for \n"
+"a full review, from what has been said the anonymity and scalability "
+"claims \n"
+"seem highly dubious. In particular, the appropriateness for use in "
+"hostile \n"
+"regimes against state level adversaries has been tremendously overstated,"
+" \n"
+"and any analysis on the implications of resource scarcity upon the "
+"scalability \n"
+"of the network has seemingly been avoided. Further questions regarding "
+"susceptibility \n"
+"to traffic analysis, trust and other topics do exist, but a more in-depth"
+" \n"
+"review of this \"globally scalable darknet\" will have to wait until the "
+"Freenet \n"
+"team makes more information available."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:797
+msgid ""
+"I2P itself doesn't really do much - it simply sends messages to remote "
+"destinations \n"
+"and receives messages targeting local destinations - most of the "
+"interesting \n"
+"work goes on at the layers above it. By itself, I2P could be seen as an "
+"anonymous \n"
+"and secure IP layer, and the bundled streaming"
+" library \n"
+"as an implementation of an anonymous and secure TCP layer on top of it. "
+"Beyond \n"
+"that, I2PTunnel exposes a generic TCP "
+"proxying \n"
+"system for either getting into or out of the I2P network, plus a variety "
+"of \n"
+"network applications provide further functionality for end users."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:808
+msgid "Streaming library"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:809
+msgid ""
+"The I2P streaming library can be viewed as a generic streaming interface "
+"(mirroring TCP sockets),\n"
+"and the implementation supports a sliding "
+"window protocol\n"
+"with several optimizations, to take into account the high delay over I2P."
+"\n"
+"Individual streams may adjust the maximum packet size and \n"
+"other options, though the default of 4KB compressed seems a reasonable "
+"tradeoff \n"
+"between the bandwidth costs of retransmitting lost messages and the "
+"latency \n"
+"of multiple messages."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:819
+msgid ""
+"In addition, in consideration of the relatively high cost of subsequent \n"
+"messages, the streaming library's protocol for scheduling and delivering "
+"messages \n"
+"has been optimized to allow individual messages passed to contain as much"
+" \n"
+"information as is available. For instance, a small HTTP transaction "
+"proxied \n"
+"through the streaming library can be completed in a single round trip - "
+"the \n"
+"first message bundles a SYN, FIN and the small payload (an HTTP request "
+"typically \n"
+"fits) and the reply bundles the SYN, FIN, ACK and the small payload (many"
+" \n"
+"HTTP responses fit). While an additional ACK must be transmitted to tell "
+"the \n"
+"HTTP server that the SYN/FIN/ACK has been received, the local HTTP proxy "
+"can \n"
+"deliver the full response to the browser immediately."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:832
+msgid ""
+"On the whole, however, the streaming library bears much resemblance to an"
+" \n"
+"abstraction of TCP, with its sliding windows, congestion control "
+"algorithms \n"
+"(both slow start and congestion avoidance), and general packet behavior "
+"(ACK, \n"
+"SYN, FIN, RST, etc)."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:839
+msgid "Naming library and addressbook"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:840
+#, python-format
+msgid ""
+"For more information see the Naming and "
+"Addressbook page."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:844
+#: i2p2www/pages/site/docs/how/tech-intro.html:918
+#: i2p2www/pages/site/docs/how/tech-intro.html:965
+#: i2p2www/pages/site/docs/how/tech-intro.html:997
+#: i2p2www/pages/site/docs/how/tech-intro.html:1005
+#: i2p2www/pages/site/docs/how/tech-intro.html:1013
+#: i2p2www/pages/site/docs/how/tech-intro.html:1023
+#: i2p2www/pages/site/docs/how/tech-intro.html:1031
+#: i2p2www/pages/site/docs/how/tech-intro.html:1053
+#, python-format
+msgid "Developed by: %(dev)s"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:846
+msgid ""
+"Naming within I2P has been an oft-debated topic since the very beginning"
+" \n"
+"with advocates across the spectrum of possibilities. However, given I2P's"
+" \n"
+"inherent demand for secure communication and decentralized operation, the"
+" \n"
+"traditional DNS-style naming system is clearly out, as are \"majority "
+"rules\" \n"
+"voting systems. Instead, I2P ships with a generic naming library and a "
+"base \n"
+"implementation designed to work off a local name to destination mapping, "
+"as \n"
+"well as an optional add-on application called the \"addressbook\". The "
+"addressbook \n"
+"is a web-of-trust-driven secure, distributed, and human readable naming "
+"system, \n"
+"sacrificing only the call for all human readable names to be globally "
+"unique \n"
+"by mandating only local uniqueness. While all messages in I2P are "
+"cryptographically \n"
+"addressed by their destination, different people can have local "
+"addressbook \n"
+"entries for \"Alice\" which refer to different destinations. People can "
+"still \n"
+"discover new names by importing published addressbooks of peers specified"
+" \n"
+"in their web of trust, by adding in the entries provided through a third "
+"party, \n"
+"or (if some people organize a series of published addressbooks using a "
+"first \n"
+"come first serve registration system) people can choose to treat these "
+"addressbooks \n"
+"as name servers, emulating traditional DNS."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:866
+msgid ""
+"I2P does not promote the use of DNS-like services though, as the damage \n"
+"done by hijacking a site can be tremendous - and insecure destinations "
+"have \n"
+"no value. DNSsec itself still falls back on registrars and certificate "
+"authorities, \n"
+"while with I2P, requests sent to a destination cannot be intercepted or "
+"the \n"
+"reply spoofed, as they are encrypted to the destination's public keys, "
+"and \n"
+"a destination itself is just a pair of public keys and a certificate. "
+"DNS-style \n"
+"systems on the other hand allow any of the name servers on the lookup "
+"path \n"
+"to mount simple denial of service and spoofing attacks. Adding on a "
+"certificate \n"
+"authenticating the responses as signed by some centralized certificate "
+"authority \n"
+"would address many of the hostile nameserver issues but would leave open "
+"replay \n"
+"attacks as well as hostile certificate authority attacks."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:880
+msgid ""
+"Voting style naming is dangerous as well, especially given the "
+"effectiveness \n"
+"of Sybil attacks in anonymous systems - the attacker can simply create an"
+" \n"
+"arbitrarily high number of peers and \"vote\" with each to take over a "
+"given \n"
+"name. Proof-of-work methods can be used to make identity non-free, but as"
+" \n"
+"the network grows the load required to contact everyone to conduct online"
+" \n"
+"voting is implausible, or if the full network is not queried, different "
+"sets \n"
+"of answers may be reachable."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:890
+msgid ""
+"As with the Internet however, I2P is keeping the design and operation of"
+" \n"
+"a naming system out of the (IP-like) communication layer. The bundled "
+"naming \n"
+"library includes a simple service provider interface which alternate "
+"naming \n"
+"systems can plug into, allowing end users to drive what sort of naming "
+"tradeoffs \n"
+"they prefer."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:899
+msgid ""
+"The old Syndie bundled with I2P has been replaced by the new Syndie which"
+"\n"
+"is distributed separately. For more information see the Syndie\n"
+"pages."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:905
+msgid ""
+"Syndie is a safe, anonymous blogging / content publication / content "
+"aggregation \n"
+"system. It lets you create information, share it with others, and read "
+"posts \n"
+"from those you're interested in, all while taking into consideration your"
+" \n"
+"needs for security and anonymity. Rather than building its own content "
+"distribution \n"
+"network, Syndie is designed to run on top of existing networks, "
+"syndicating \n"
+"content through eepsites, Tor hidden services, Freenet freesites, normal "
+"websites, \n"
+"usenet newsgroups, email lists, RSS feeds, etc. Data published with "
+"Syndie \n"
+"is done so as to offer pseudonymous authentication to anyone reading or "
+"archiving \n"
+"it."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:920
+msgid ""
+"I2PTunnel is probably I2P's most popular and versatile client "
+"application, \n"
+"allowing generic proxying both into and out of the I2P network. I2PTunnel"
+" \n"
+"can be viewed as four separate proxying applications - a \"client\" which"
+" receives \n"
+"inbound TCP connections and forwards them to a given I2P destination, an "
+"\"httpclient\" \n"
+"(aka \"eepproxy\") which acts like an HTTP proxy and forwards the "
+"requests to \n"
+"the appropriate I2P destination (after querying the naming service if "
+"necessary), \n"
+"a \"server\" which receives inbound I2P streaming connections on a "
+"destination \n"
+"and forwards them to a given TCP host+port, and an \"httpserver\" which "
+"extends \n"
+"the \"server\" by parsing the HTTP request and responses to allow safer "
+"operation. \n"
+"There is an additional \"socksclient\" application, but its use is not "
+"encouraged \n"
+"for reasons previously mentioned."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:934
+msgid ""
+"I2P itself is not an outproxy network - the anonymity and security "
+"concerns \n"
+"inherent in a mix net which forwards data into and out of the mix have "
+"kept \n"
+"I2P's design focused on providing an anonymous network which capable of "
+"meeting \n"
+"the user's needs without requiring external resources. However, the "
+"I2PTunnel \n"
+"\"httpclient\" application offers a hook for outproxying - if the "
+"hostname requested \n"
+"doesn't end in \".i2p\", it picks a random destination from a user-"
+"provided \n"
+"set of outproxies and forwards the request to them. These destinations "
+"are \n"
+"simply I2PTunnel \"server\" instances run by volunteers who have "
+"explicitly \n"
+"chosen to run outproxies - no one is an outproxy by default, and running "
+"an \n"
+"outproxy doesn't automatically tell other people to proxy through you. "
+"While \n"
+"outproxies do have inherent weaknesses, they offer a simple proof of "
+"concept \n"
+"for using I2P and provide some functionality under a threat model which "
+"may \n"
+"be sufficient for some users."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:950
+msgid ""
+"I2PTunnel enables most of the applications in use. An \"httpserver\" "
+"pointing \n"
+"at a webserver lets anyone run their own anonymous website (or "
+"\"eepsite\") \n"
+"- a webserver is bundled with I2P for this purpose, but any webserver can"
+" \n"
+"be used. Anyone may run a \"client\" pointing at one of the anonymously "
+"hosted \n"
+"IRC servers, each of which are running a \"server\" pointing at their "
+"local \n"
+"IRCd and communicating between IRCds over their own \"client\" tunnels. "
+"End \n"
+"users also have \"client\" tunnels pointing at I2Pmail's \n"
+"POP3 and SMTP destinations (which in turn are simply \"server\" instances"
+" pointing \n"
+"at POP3 and SMTP servers), as well as \"client\" tunnels pointing at "
+"I2P's CVS \n"
+"server, allowing anonymous development. At times people have even run "
+"\"client\" \n"
+"proxies to access the \"server\" instances pointing at an NNTP server."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:967
+msgid ""
+"i2p-bt is a port of the mainline python BitTorrent client to run both the"
+" \n"
+"tracker and peer communication over I2P. Tracker requests are forwarded "
+"through \n"
+"the eepproxy to eepsites specified in the torrent file while tracker "
+"responses \n"
+"refer to peers by their destination explicitly, allowing i2p-bt to open "
+"up \n"
+"a streaming lib connection to query them "
+"for \n"
+"blocks."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:976
+msgid ""
+"In addition to i2p-bt, a port of bytemonsoon has been made to I2P, making"
+" \n"
+"a few modifications as necessary to strip any anonymity-compromising "
+"information \n"
+"from the application and to take into consideration the fact that IPs "
+"cannot \n"
+"be used for identifying peers."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:984
+msgid ""
+"I2PSnark developed: jrandom, et al, ported from mjw 's Snark client"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:990
+msgid ""
+"Bundled with the I2P install, I2PSnark offers a simple anonymous "
+"BitTorrent \n"
+"client with multitorrent capabilities, exposing all of the functionality "
+"through \n"
+"a plain HTML web interface."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:999
+#, python-format
+msgid ""
+"Robert is a Bittorrent client written in Python.\n"
+"It is hosted on http://%(bob)s/Robert.html "
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:1007
+#, python-format
+msgid ""
+"PyBit is a Bittorrent client written in Python.\n"
+"It is hosted on %(pybit)s "
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:1015
+msgid ""
+"I2Phex is a fairly direct port of the Phex Gnutella filesharing client to"
+" \n"
+"run entirely on top of I2P. While it has disabled some of Phex's "
+"functionality, \n"
+"such as integration with Gnutella webcaches, the basic file sharing and "
+"chatting \n"
+"system is fully functional."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:1025
+msgid ""
+"iMule is a fairly direct port of the aMule filesharing client \n"
+"running entirely inside I2P."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:1033
+#, python-format
+msgid ""
+"I2Pmail is more a service than an application - postman offers both "
+"internal \n"
+"and external email with POP3 and SMTP service through I2PTunnel instances"
+" \n"
+"accessing a series of components developed with mastiejaner, allowing "
+"people \n"
+"to use their preferred mail clients to send and receive mail "
+"pseudonymously. \n"
+"However, as most mail clients expose substantial identifying information,"
+" \n"
+"I2P bundles susi23's web based susimail client which has been built "
+"specifically \n"
+"with I2P's anonymity needs in mind. The I2Pmail/mail.i2p service offers "
+"transparent \n"
+"virus filtering as well as denial of service prevention with hashcash "
+"augmented \n"
+"quotas. In addition, each user has control of their batching strategy "
+"prior \n"
+"to delivery through the mail.i2p outproxies, which are separate from the "
+"mail.i2p \n"
+"SMTP and POP3 servers - both the outproxies and inproxies communicate "
+"with \n"
+"the mail.i2p SMTP and POP3 servers through I2P itself, so compromising "
+"those \n"
+"non-anonymous locations does not give access to the mail accounts or "
+"activity \n"
+"patterns of the user. At the moment the developers work on a "
+"decentralized \n"
+"mailsystem, called \"v2mail\". More information can be found on the "
+"eepsite \n"
+"%(postman)s."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:1055
+msgid ""
+"I2P-Bote is a distributed e-mail application. It does not use the "
+"traditional\n"
+"e-mail concept of sending an e-mail to a server and retrieving it from a "
+"server.\n"
+"Instead, it uses a Kademlia Distributed Hash Table to store mails.\n"
+"One user can push a mail into the DHT, while another can request the "
+"e-mail from the DHT.\n"
+"And all the mails sent within the I2P-Bote network are automatically "
+"encrypted end-to-end.
\n"
+"Furthermore, I2P-Bote offers a remailer function on top of I2P, for "
+"increased high-latency anonymity."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:1065
+msgid ""
+"I2P-Messenger is an end-to-end encrypted serverless communication "
+"application.\n"
+"For communication between two users, they need to give each other their "
+"destination keys, to allow the other to connect.\n"
+"It supports file transfer and has a search for other users, based on "
+"Seedless."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:2
+msgid "I2P's Threat Model"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:3
+msgid "November 2010"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:7
+msgid "low"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:8
+msgid "medium"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:9
+msgid "high"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:34
+msgid "Damage Potential"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:35
+msgid "Reliability"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:36
+msgid "Exploitability"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:37
+msgid "Affected Users"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:38
+msgid "Discoverability"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:39
+msgid "Severity"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:40
+#: i2p2www/pages/site/docs/protocol/i2np.html:94
+msgid "Priority"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:45
+msgid "What do we mean by \"anonymous\"?"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:47
+msgid ""
+"Your level of anonymity can be described as \"how hard it is for someone\n"
+"to find out information you don't want them to know?\" - who you are, "
+"where\n"
+"you are located, who you communicate with, or even when you communicate."
+" \n"
+"\"Perfect\" anonymity is not a useful concept here - software will not "
+"make \n"
+"you indistinguishable from people that don't use computers or who are not"
+" on\n"
+"the Internet. Instead, we are working to provide sufficient anonymity to"
+" meet the\n"
+"real needs of whomever we can - from those simply browsing websites, to "
+"those exchanging\n"
+"data, to those fearful of discovery by powerful organizations or states."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:58
+msgid ""
+"The question of whether I2P provides sufficient anonymity for your \n"
+"particular needs is a hard one, but this page will hopefully assist in \n"
+"answering that question by exploring how I2P operates under various "
+"attacks\n"
+"so that you may decide whether it meets your needs."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:65
+msgid ""
+"We welcome further research and analysis on I2P's resistance to the "
+"threats described below.\n"
+"More review of existing literature (much of it focused on Tor) and "
+"original\n"
+"work focused on I2P is needed."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:71
+msgid "Network Topology Summary"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:72
+#, python-format
+msgid ""
+"I2P builds off the ideas of many other \n"
+"systems, but a few key points should be kept in"
+" mind when \n"
+"reviewing related literature:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:78
+msgid ""
+"I2P is a free route mixnet - the message creator explicitly "
+"defines the\n"
+"path that messages will be sent out (the outbound tunnel), and the "
+"message \n"
+"recipient explicitly defines the path that messages will be received on "
+"(the\n"
+"inbound tunnel)."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:84
+msgid ""
+"I2P has no official entry and exit points - all peers fully "
+"participate in the \n"
+"mix, and there are no network layer in- or out-proxies (however, at the \n"
+"application layer, a few proxies do exist)"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:89
+msgid ""
+"I2P is fully distributed - there are no central controls or "
+"authorities.\n"
+"One could modify some routers to operate mix cascades (building tunnels "
+"and giving\n"
+"out the keys necessary to control the forwarding at the tunnel endpoint) "
+"or directory \n"
+"based profiling and selection, all without breaking compatibility with "
+"the rest of \n"
+"the network, but doing so is of course not necessary (and may even harm "
+"one's\n"
+"anonymity)."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:99
+#, python-format
+msgid ""
+"We have documented plans to implement nontrivial delays\n"
+"and batching strategies \n"
+"whose existence is only known to the particular hop or tunnel gateway "
+"that \n"
+"receives the message, allowing a mostly low latency mixnet to provide "
+"cover \n"
+"traffic for higher latency communication (e.g. email).\n"
+"However we are aware that significant delays are required to provide "
+"meaningful\n"
+"protection, and that implementation of such delays will be a significant "
+"challenge.\n"
+"It is not clear at this time whether we will actually implement these "
+"delay features."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:110
+msgid ""
+"In theory, routers along the message path may inject an \n"
+"arbitrary number of hops before forwarding the message to the next peer, "
+"though\n"
+"the current implementation does not."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:117
+msgid "The Threat Model"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:118
+msgid ""
+"I2P design started in 2003, not long after the advent of\n"
+"[Onion Routing],\n"
+"[Freenet], and\n"
+"[Tor].\n"
+"Our design benefits substantially from the research published around that"
+" time.\n"
+"I2P uses several onion routing techniques, so we continue to benefit\n"
+"from the significant academic interest in Tor."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:128
+msgid ""
+"Taking from the attacks and analysis put forth in the \n"
+"anonymity "
+"literature (largely \n"
+"Traffic Analysis: "
+"Protocols, Attacks, Design \n"
+"Issues and Open Problems), the following briefly describes a wide "
+"variety \n"
+"of attacks as well as many of I2Ps defenses. We update\n"
+"this list to include new attacks as they are identified."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:137
+msgid ""
+"Included are some attacks that may be unique to I2P.\n"
+"We do not have good answers for all these attacks, however\n"
+"we continue to do research and improve our defenses."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:143
+msgid ""
+"In addition, many of these attacks are significantly easier than\n"
+"they should be, due to the modest size of the current network.\n"
+"While we are aware of some limitations that need to be addressed,\n"
+"I2P is designed to support hundreds of thousands, or millions, of\n"
+"participants.\n"
+"As we continue to spread the word and grow the network,\n"
+"these attacks will become much harder."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:153
+#, python-format
+msgid ""
+"The\n"
+"network comparisons and\n"
+"\"garlic\" terminology pages may also "
+"be helpful\n"
+"to review."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:182
+msgid "Index of Attacks"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:184
+#: i2p2www/pages/site/docs/how/threat-model.html:204
+msgid "Brute force attacks"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:185
+#: i2p2www/pages/site/docs/how/threat-model.html:248
+msgid "Timing attacks"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:186
+#: i2p2www/pages/site/docs/how/threat-model.html:285
+msgid "Intersection attacks"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:187
+#: i2p2www/pages/site/docs/how/threat-model.html:365
+msgid "Denial of service attacks"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:188
+#: i2p2www/pages/site/docs/how/threat-model.html:464
+msgid "Tagging attacks"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:189
+#: i2p2www/pages/site/docs/how/threat-model.html:482
+msgid "Partitioning attacks"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:190
+#: i2p2www/pages/site/docs/how/threat-model.html:522
+msgid "Predecessor attacks"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:191
+#: i2p2www/pages/site/docs/how/threat-model.html:567
+msgid "Harvesting attacks"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:192
+#: i2p2www/pages/site/docs/how/threat-model.html:614
+msgid "Identification Through Traffic Analysis"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:193
+#: i2p2www/pages/site/docs/how/threat-model.html:674
+msgid "Sybil attacks"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:194
+#: i2p2www/pages/site/docs/how/threat-model.html:723
+msgid "Buddy Exhaustion attacks"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:195
+#: i2p2www/pages/site/docs/how/threat-model.html:748
+msgid "Cryptographic attacks"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:196
+msgid "Floodfill attacks"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:197
+#: i2p2www/pages/site/docs/how/threat-model.html:809
+msgid "Other Network Database attacks"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:198
+msgid "Attacks on centralized resources"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:199
+#: i2p2www/pages/site/docs/how/threat-model.html:875
+msgid "Development attacks"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:200
+msgid "Implementation attacks"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:201
+#: i2p2www/pages/site/docs/how/threat-model.html:959
+msgid "Other Defenses"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:208
+msgid ""
+"A brute force attack can be mounted by a global passive or active "
+"adversary, \n"
+"watching all the messages pass between all of the nodes and attempting to"
+" correlate\n"
+"which message follows which path. Mounting this attack against I2P "
+"should be \n"
+"nontrivial, as all peers in the network are frequently sending messages "
+"(both\n"
+"end to end and network maintenance messages), plus an end to end message "
+"changes\n"
+"size and data along its path. In addition, the external adversary does "
+"not have\n"
+"access to the messages either, as inter-router communication is both "
+"encrypted\n"
+"and streamed (making two 1024 byte messages indistinguishable from one "
+"2048 byte\n"
+"message)."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:220
+msgid ""
+"However, a powerful attacker can use brute force to detect trends - if "
+"they \n"
+"can send 5GB to an I2P destination and monitor everyone's network "
+"connection,\n"
+"they can eliminate all peers who did not receive 5GB of data. Techniques"
+" to \n"
+"defeat this attack exist, but may be prohibitively expensive (see: \n"
+"Tarzan's "
+"mimics\n"
+"or constant rate traffic). Most users are not concerned with this "
+"attack, as \n"
+"the cost of mounting it are extreme (and often require illegal activity)."
+" \n"
+"However, the attack is still possible, for example by an observer at\n"
+"a large ISP or an Internet exchange point.\n"
+"Those who want to defend against it \n"
+"would want to take appropriate countermeasures, such as\n"
+"setting low bandwidth limits, and using unpublished or encrypted "
+"leasesets for eepsites.\n"
+"Other countermeasures, such as nontrivial delays and restricted routes, "
+"are\n"
+"not currently implemented."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:237
+#, python-format
+msgid ""
+"As a partial defense against a single router or group of routers trying "
+"to route all the network's traffic,\n"
+"routers contain limits as to how many tunnels can be routed through a "
+"single peer.\n"
+"As the network grows, these limits are subject to further adjustment.\n"
+"Other mechanisms for peer rating, selection and avoidance\n"
+"are discussed on the\n"
+"peer selection page."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:252
+msgid ""
+"I2P's messages are unidirectional and do not necessarily imply that a "
+"reply\n"
+"will be sent. However, applications on top of I2P will most likely have\n"
+"recognizable patterns within the frequency of their messages - for "
+"instance, an \n"
+"HTTP request will be a small message with a large sequence of reply "
+"messages \n"
+"containing the HTTP response. Using this data as well as a broad view of"
+" the \n"
+"network topology, an attacker may be able to disqualify some links as "
+"being too \n"
+"slow to have passed the message along."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:262
+msgid ""
+"This sort of attack is powerful, but its applicability to I2P is non "
+"obvious,\n"
+"as the variation on message delays due to queuing, message processing, "
+"and \n"
+"throttling will often meet or exceed the time of passing a message along "
+"a \n"
+"single link - even when the attacker knows that a reply will be sent as "
+"soon as\n"
+"the message is received. There are some scenarios which will expose "
+"fairly \n"
+"automatic replies though - the streaming library does (with the SYN+ACK) "
+"as does the \n"
+"message mode of guaranteed delivery (with the "
+"DataMessage+DeliveryStatusMessage)."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:272
+#, python-format
+msgid ""
+"Without protocol scrubbing or higher latency, global active adversaries "
+"can \n"
+"gain substantial information. As such, people concerned with these "
+"attacks could\n"
+"increase the latency (using nontrivial "
+"delays or \n"
+"batching strategies), include protocol "
+"scrubbing, or\n"
+"other advanced tunnel routing techniques,\n"
+"but these are unimplemented in I2P."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:281
+#, python-format
+msgid ""
+"References: Low-Resource Routing Attacks Against "
+"Anonymous Systems"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:289
+msgid ""
+"Intersection attacks against low latency systems are extremely powerful -"
+"\n"
+"periodically make contact with the target and keep track of what peers "
+"are on\n"
+"the network. Over time, as node churn occurs the attacker will gain \n"
+"significant information about the target by simply intersecting the sets "
+"of\n"
+"peers that are online when a message successfully goes through. The cost"
+" of \n"
+"this attack is significant as the network grows, but may be feasible in "
+"some\n"
+"scenarios."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:299
+#, python-format
+msgid ""
+"In summary, if an attacker is at both ends of your tunnel at the same "
+"time,\n"
+"he may be successful.\n"
+"I2P does not have a full defense to this for low latency communication.\n"
+"This is an inherent weakness of low-latency onion routing.\n"
+"Tor provides a similar disclaimer."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:307
+msgid "Partial defenses implemented in I2P:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:311
+#, python-format
+msgid "strict ordering of peers"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:314
+#, python-format
+msgid ""
+"peer profiling and selection from a "
+"small group that changes slowly"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:317
+msgid "Limits on the number of tunnels routed through a single peer"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:320
+msgid ""
+"Prevention of peers from the same /16 IP range from being members of a "
+"single tunnel"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:323
+msgid ""
+"For eepsites or other hosted services, we support\n"
+"simultaneous hosting on multiple routers, or\n"
+"multihoming"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:330
+msgid ""
+"Even in total, these defenses are not a complete solution.\n"
+"Also, we have made some design choices that may significantly increase "
+"our vulnerability:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:335
+msgid "We do not use low-bandwidth \"guard nodes\""
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:338
+msgid ""
+"We use tunnel pools comprised of several tunnels, and traffic can shift "
+"from tunnel to tunnel."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:341
+msgid "Tunnels are not long-lived; new tunnels are built every 10 minutes."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:344
+msgid ""
+"Tunnel lengths are configurable.\n"
+"While 3-hop tunnels are recommended for full protection, several "
+"applications and\n"
+"services use 2-hop tunnels by default."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:351
+#, python-format
+msgid ""
+"In the future, it could\n"
+"for peers who can afford significant delays (per nontrivial\n"
+"delays and batching strategies). "
+"In addition,\n"
+"this is only relevant for destinations that other people know about - a "
+"private\n"
+"group whose destination is only known to trusted peers does not have to "
+"worry,\n"
+"as an adversary can't \"ping\" them to mount the attack."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:360
+#, python-format
+msgid "Reference: One Cell Enough"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:367
+msgid ""
+"There are a whole slew of denial of service attacks available against "
+"I2P,\n"
+"each with different costs and consequences:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:373
+msgid ""
+"Greedy user attack: This is simply\n"
+"people trying to consume significantly more resources than they are \n"
+"willing to contribute. The defense against this is:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:379
+#, python-format
+msgid ""
+"Set defaults so that most users provide resources to the network.\n"
+"In I2P, users route traffic by default. In sharp distinction to\n"
+"other networks,\n"
+"over 95% of I2P users relay traffic for others."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:385
+msgid ""
+"Provide easy configuration options so that users may increase their\n"
+"contribution (share percentage) to the network. Display easy-to-"
+"understand\n"
+"metrics such as \"share ratio\" so that users may see what they are "
+"contributing."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:390
+msgid ""
+"Maintain a strong community with blogs, forums, IRC, and other means of "
+"communication."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:397
+#, python-format
+msgid ""
+"Starvation attack: A hostile user may attempt to harm the network "
+"by\n"
+"creating a significant number of peers in the network who are not "
+"identified as\n"
+"being under control of the same entity (as with Sybil). These nodes then"
+" \n"
+"decide not to provide any resources to the network, causing existing "
+"peers \n"
+"to search through a larger network database or request more tunnels than"
+" \n"
+"should be necessary. \n"
+"Alternatively, the nodes may provide intermittent service by periodically"
+"\n"
+"dropping selected traffic, or refusing connections to certain peers.\n"
+"This behavior may be indistinguishable from that of a heavily-loaded or "
+"failing node.\n"
+"I2P addresses these issues by maintaining profiles on the \n"
+"peers, attempting to identify underperforming ones and simply ignoring \n"
+"them, or using them rarely.\n"
+"We have significantly enhanced the\n"
+"ability to recognize and avoid troublesome peers; however there are still"
+"\n"
+"significant efforts required in this area."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:417
+#, python-format
+msgid ""
+"Flooding attack: A hostile user may attempt to flood the network,\n"
+"a peer, a destination, or a tunnel. Network and peer flooding is "
+"possible,\n"
+"and I2P does nothing to prevent standard IP layer flooding. The flooding"
+" of\n"
+"a destination with messages by sending a large number to the target's "
+"various\n"
+"inbound tunnel gateways is possible, but the destination will know this "
+"both\n"
+"by the contents of the message and because the tunnel's tests will fail."
+" The\n"
+"same goes for flooding just a single tunnel. I2P has no defenses for a "
+"network\n"
+"flooding attack. For a destination and tunnel flooding attack, the "
+"target\n"
+"identifies which tunnels are unresponsive and builds new ones. New code "
+"could\n"
+"also be written to add even more tunnels if the client wishes to handle "
+"the\n"
+"larger load. If, on the other hand, the load is more than the client can"
+"\n"
+"deal with, they can instruct the tunnels to throttle the number of "
+"messages or\n"
+"bytes they should pass on (once the advanced tunnel\n"
+"operation is implemented)."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:436
+msgid ""
+"CPU load attack: There are currently some methods for people to \n"
+"remotely request that a peer perform some cryptographically expensive \n"
+"operation, and a hostile attacker could use these to flood that peer with"
+"\n"
+"a large number of them in an attempt to overload the CPU. Both using "
+"good \n"
+"engineering practices and potentially requiring nontrivial certificates \n"
+"(e.g. HashCash) to be attached to these expensive requests should "
+"mitigate\n"
+"the issue, though there may be room for an attacker to exploit various\n"
+"bugs in the implementation."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:449
+#, python-format
+msgid ""
+"Floodfill DOS attack: A hostile user may attempt to harm the "
+"network by\n"
+"becoming a floodfill router. The current defenses against unreliable,\n"
+"intermittent, or malicious floodfill routers are poor.\n"
+"A floodfill router may provide bad or no response to lookups, and\n"
+"it may also interfere with inter-floodfill communication.\n"
+"Some defenses and\n"
+"peer profiling are implemented,\n"
+"however there is much more to do.\n"
+"For more information see the\n"
+"network database page."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:468
+#, python-format
+msgid ""
+"Tagging attacks - modifying a message so that it can later be identified"
+" \n"
+"further along the path - are by themselves impossible in I2P, as messages"
+" \n"
+"passed through tunnels are signed. However, if an attacker is the "
+"inbound \n"
+"tunnel gateway as well as a participant further along in that tunnel, "
+"with\n"
+"collusion they can identify the fact that they are in the same tunnel "
+"(and \n"
+"prior to adding unique hop ids and "
+"other updates,\n"
+"colluding peers within the same tunnel can recognize that fact without "
+"any \n"
+"effort). An attacker in an outbound tunnel and any part of an inbound "
+"tunnel cannot \n"
+"collude however, as the tunnel encryption pads and modifies the data "
+"separately\n"
+"for the inbound and outbound tunnels. External attackers cannot do "
+"anything,\n"
+"as the links are encrypted and messages signed."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:486
+msgid ""
+"Partitioning attacks - finding ways to segregate (technically or "
+"analytically)\n"
+"the peers in a network - are important to keep in mind when dealing with "
+"a \n"
+"powerful adversary, since the size of the network plays a key role in "
+"determining\n"
+"your anonymity. Technical partitioning by cutting links between peers to"
+" create\n"
+"fragmented networks is addressed by I2P's built in network database, "
+"which \n"
+"maintains statistics about various peers so as to allow any existing "
+"connections\n"
+"to other fragmented sections to be exploited so as to heal the network. "
+"However,\n"
+"if the attacker does disconnect all links to uncontrolled peers, "
+"essentially\n"
+"isolating the target, no amount of network database healing will fix it."
+" At\n"
+"that point, the only thing the router can hope to do is notice that a "
+"significant\n"
+"number of previously reliable peers have become unavailable and alert the"
+" client\n"
+"that it is temporarily disconnected (this detection code is not "
+"implemented at\n"
+"the moment)."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:502
+#, python-format
+msgid ""
+"Partitioning the network analytically by looking for differences in how "
+"routers \n"
+"and destinations behave and grouping them accordingly is also a very "
+"powerful\n"
+"attack. For instance, an attacker harvesting"
+" the network\n"
+"database will know when a particular destination has 5 inbound tunnels in"
+" their\n"
+"LeaseSet while others have only 2 or 3, allowing the adversary to "
+"potentially \n"
+"partition clients by the number of tunnels selected. Another partition "
+"is \n"
+"possible when dealing with the nontrivial "
+"delays and \n"
+"batching strategies, as the tunnel "
+"gateways and the\n"
+"particular hops with non-zero delays will likely stand out. However, "
+"this data\n"
+"is only exposed to those specific hops, so to partition effectively on "
+"that \n"
+"matter, the attacker would need to control a significant portion of the "
+"network\n"
+"(and still that would only be a probabilistic partition, as they wouldn't"
+" know\n"
+"which other tunnels or messages have those delays)."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:518
+#, python-format
+msgid ""
+"Also discussed on the network database "
+"page (bootstrap attack)."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:526
+msgid ""
+"The predecessor attack is passively gathering statistics in an attempt to"
+" see\n"
+"what peers are 'close' to the destination by participating in their "
+"tunnels and\n"
+"keeping track of the previous or next hop (for outbound or inbound "
+"tunnels, \n"
+"respectively). Over time, using a perfectly random sample of peers and "
+"random\n"
+"ordering, an attacker would be able to see which peer shows up as "
+"'closer' \n"
+"statistically more than the rest, and that peer would in turn be where "
+"the\n"
+"target is located."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:536
+#, python-format
+msgid ""
+"I2P avoids this in four ways: first, the peers selected to participate in"
+"\n"
+"tunnels are not randomly sampled throughout the network - they are "
+"derived from\n"
+"the peer selection algorithm which "
+"breaks them\n"
+"into tiers. Second, with strict "
+"ordering of peers\n"
+"in a tunnel, the fact that a peer shows up more frequently does not mean "
+"they're\n"
+"the source. Third, with permuted "
+"tunnel length\n"
+"(not enabled by default)\n"
+"even 0 hop tunnels can provide plausible deniability as the occasional \n"
+"variation of the gateway will look like normal tunnels. Fourth, with \n"
+"restricted routes "
+"(unimplemented), only the peer with\n"
+"a restricted connection to the target will ever contact the target, while"
+" \n"
+"attackers will merely run into that gateway."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:553
+#, python-format
+msgid ""
+"The current tunnel build method\n"
+"was specifically designed to combat the predecessor attack.\n"
+"See also the intersection attack."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:559
+#, python-format
+msgid ""
+"References: %(pdf2008)s\n"
+"which is an update to the 2004 predecessor attack paper\n"
+"%(pdf2004)s."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:571
+msgid ""
+"\"Harvesting\" means compiling a list of users running I2P.\n"
+"It can be used for legal attacks and to help\n"
+"other attacks by simply running a peer, seeing who it connects to, and \n"
+"harvesting whatever references to other peers it can find."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:578
+msgid ""
+"I2P itself is not designed with effective defenses against\n"
+"this attack, since there is the distributed network database \n"
+"containing just this information.\n"
+"The following factors make the attack somewhat harder in practice:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:585
+msgid ""
+"Network growth will make it more difficult to obtain a given proportion "
+"of the network"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:588
+msgid "Floodfill routers implement query limits as DOS protection"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:591
+msgid ""
+"\"Hidden mode\", which prevents a router from publishing its information "
+"to the netDb,\n"
+"(but also prevents it from relaying data) is not widely used now but "
+"could be."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:597
+#, python-format
+msgid ""
+"In future implementations,\n"
+"basic and \n"
+"comprehensive restricted "
+"routes,\n"
+"this attack loses much of its power, as the \"hidden\" peers do not "
+"publish their\n"
+"contact addresses in the network database - only the tunnels through "
+"which \n"
+"they can be reached (as well as their public keys, etc)."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:606
+msgid ""
+"In the future, routers could use GeoIP to identify if they are in a "
+"particular\n"
+"country where identification as an I2P node would be risky.\n"
+"In that case, the router could automatically enable hidden mode, or\n"
+"enact other restricted route methods."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:618
+#, python-format
+msgid ""
+"By inspecting the traffic into and out of a router, a malicious ISP\n"
+"or state-level firewall could identify that a computer is running I2P.\n"
+"As discussed above, I2P is not specifically "
+"designed\n"
+"to hide that a computer is running I2P. However, several design decisions"
+" made\n"
+"in the design of the\n"
+"transport layer and protocols\n"
+"make it somewhat difficult to identify I2P traffic:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:628
+msgid "Random port selection"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:631
+msgid "Point-to-Point Encryption of all traffic"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:634
+msgid ""
+"DH key exchange with no protocol bytes or other unencrypted constant "
+"fields"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:637
+#, python-format
+msgid ""
+"Simultaneous use of both\n"
+"TCP and\n"
+"UDP transports.\n"
+"UDP may be much harder for some Deep Packet Inspection (DPI) equipment to"
+" track."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:645
+msgid ""
+"In the near future, we plan to directly address traffic analysis issues "
+"by further obfuscation of I2P transport protocols, possibly including:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:649
+msgid ""
+"Padding at the transport layer to random lengths, especially during the "
+"connection handshake"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:652
+msgid ""
+"Study of packet size distribution signatures, and additional padding as "
+"necessary"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:655
+msgid ""
+"Development of additional transport methods that mimic SSL or other "
+"common protocols"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:658
+msgid ""
+"Review of padding strategies at higher layers to see how they affect "
+"packet sizes at the transport layer"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:661
+msgid ""
+"Review of methods implemented by various state-level firewalls to block "
+"Tor"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:664
+msgid "Working directly with DPI and obfuscation experts"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:669
+#, python-format
+msgid ""
+"Reference: Breaking and Improving Protocol "
+"Obfuscation"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:678
+msgid ""
+"Sybil describes a category of attacks where the adversary creates "
+"arbitrarily\n"
+"large numbers of colluding nodes and uses the increased numbers to help \n"
+"mounting other attacks. For instance, if an attacker is in a network "
+"where peers\n"
+"are selected randomly and they want an 80% chance to be one of those "
+"peers, they\n"
+"simply create five times the number of nodes that are in the network and "
+"roll \n"
+"the dice. When identity is free, Sybil can be a very potent technique "
+"for a \n"
+"powerful adversary. The primary technique to address this is simply to "
+"make \n"
+"identity 'non free' - Tarzan\n"
+"(among others) uses the fact that IP addresses are limited, while \n"
+"IIP used \n"
+"HashCash to 'charge' for "
+"creating a new\n"
+"identity. We currently have not implemented any particular technique to "
+"address\n"
+"Sybil, but do include placeholder certificates in the router's and \n"
+"destination's data structures which can contain a HashCash certificate of"
+" \n"
+"appropriate value when necessary (or some other certificate proving "
+"scarcity)."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:696
+msgid "Requiring HashCash Certificates in various places has two major problems:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:700
+msgid "Maintaining backward compatibility"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:703
+msgid ""
+"The classic HashCash problem -\n"
+"selecting HashCash values that are meaningful proofs of work on high-end "
+"machines,\n"
+"while still being feasible on low-end machines such as mobile devices."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:710
+msgid ""
+"Various limitations on the number of routers in a given IP range restrict"
+"\n"
+"the vulnerability to attackers that don't have the ability to put "
+"machines\n"
+"in several IP blocks.\n"
+"However, this is not a meaningful defense against a powerful adversary."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:717
+#, python-format
+msgid ""
+"See the network database page\n"
+"for more Sybil discussion."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:727
+#, python-format
+msgid ""
+"(Reference: In Search of an Anonymouns and Secure "
+"Lookup Section 5.2)"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:731
+#, python-format
+msgid ""
+"By refusing to accept or forward tunnel build requests, except to a "
+"colluding peer, a router could ensure\n"
+"that a tunnel is formed wholly from its set of colluding routers.\n"
+"The chances of success are enhanced if there is a large number of "
+"colluding routers,\n"
+"i.e. a Sybil attack.\n"
+"This is somewhat mitigated by our\n"
+"peer profiling methods used to monitor "
+"the performance\n"
+"of peers.\n"
+"However, this is a powerful attack as the number of routers approaches\n"
+"f = 0.2, or 20% malicious nodes, as specifed in the paper.\n"
+"The malicous routers could also maintain connections to the target router"
+" and provide\n"
+"excellent forwarding bandwidth for traffic over those connections, in an "
+"attempt\n"
+"to manipulate the profiles managed by the target and appear attractive.\n"
+"Further research and defenses may be necessary."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:752
+#, python-format
+msgid ""
+"We use strong cryptography with long keys, and\n"
+"we assume the security of the industry-standard cryptographic primitives "
+"used in I2P, as documented\n"
+"on the low-level cryptography page. \n"
+"Security features include the immediate detection of \n"
+"altered messages along the path, the inability to decrypt messages not "
+"addressed to you,\n"
+"and defense against man-in-the-middle attacks.\n"
+"The key sizes chosen in 2003 were quite conservative at the time, and are"
+" still longer than\n"
+"those used in other anonymity "
+"networks.\n"
+"We don't think the current key lengths are our biggest weakness,\n"
+"especially for traditional, non-state-level adversaries;\n"
+"bugs and the small size of the network are much more worrisome.\n"
+"Of course, all cryptographic algorithms eventually become obsolete due to"
+"\n"
+"the advent of faster processors, cryptographic research, and advancements"
+" in\n"
+"methods such as rainbow tables, clusters of video game hardware, etc.\n"
+"Unfortunately, I2P was not designed with easy mechanisms to lengthen keys"
+" or change\n"
+"shared secret values while maintaining backward compatibility."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:771
+#, python-format
+msgid ""
+"Upgrading the various data structures and protocols to support longer "
+"keys\n"
+"will have to be tackled eventually, and this will be a\n"
+"major undertaking, just as it will be "
+"for \n"
+"others.\n"
+"Hopefully, through careful planning, we can minimize the disruption, and\n"
+"implement mechanisms to make it easier for future transitions."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:780
+msgid ""
+"In the future, several I2P protocols and data structures\n"
+"support securely padding messages to arbitrary sizes, so messages could "
+"be made constant\n"
+"size or garlic messages could be modified randomly so that some cloves "
+"appear to contain\n"
+"more subcloves than they actually do. At the moment, however, garlic, "
+"tunnel, and \n"
+"end to end messages include simple random padding."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:790
+msgid "Floodfill Anonymity attacks"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:794
+#, python-format
+msgid ""
+"In addition to the floodfill DOS attacks described\n"
+"above, floodfill routers are uniquely positioned\n"
+"to learn about network participants, due to their role\n"
+"in the netDb, and the high frequency of communication with those "
+"participants.\n"
+"This is somewhat mitigated because floodfill routers only manage a "
+"portion\n"
+"of the total keyspace, and the keyspace rotates daily, as explained \n"
+"on the network database page.\n"
+"The specific mechanisms by which routers communicate with floodfills have"
+" been\n"
+"carefully designed.\n"
+"However, these threats should be studied further.\n"
+"The specific potential threats and corresponding defenses are a topic for"
+" future research."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:810
+#, python-format
+msgid ""
+"A hostile user may attempt to harm the network by\n"
+"creating one or more floodfill routers and crafting them to offer\n"
+"bad, slow, or no responses.\n"
+"Several scenarios are discussed on the\n"
+"network database page."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:820
+msgid "Central Resource Attacks"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:824
+msgid ""
+"There are a few centralized or limited resources (some inside I2P, some "
+"not)\n"
+"that could be attacked or used as a vector for attacks.\n"
+"The absence of jrandom starting November 2007, followed by the loss of "
+"the i2p.net hosting service in January 2008,\n"
+"highlighted numerous centralized resources in the development and "
+"operation of the I2P network,\n"
+"most of which are now distributed.\n"
+"Attacks on externally-reachable resources mainly affect the ability of "
+"new users to find us,\n"
+"not the operation of the network itself."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:834
+#, python-format
+msgid ""
+"The website is mirrored and uses DNS round-robin"
+" for external public access."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:837
+#, python-format
+msgid ""
+"Routers now support multiple external reseed "
+"locations,\n"
+"however more reseed hosts may be needed, and the handling of unreliable "
+"or malicious\n"
+"reseed hosts may need improvement."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:842
+msgid ""
+"Routers now support multiple update file locations.\n"
+"A malicious update host could feed a huge file, need to limit the size."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:846
+msgid "Routers now support multiple default trusted update signers."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:849
+msgid ""
+"Routers now better handle multiple unreliable "
+"floodfill peers.\n"
+"Malicious floodfills needs more study."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:853
+#, python-format
+msgid ""
+"The code is now stored in a distributed source "
+"control system."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:856
+msgid ""
+"Routers rely on a single news host, but there is a hardcoded backup URL "
+"pointing to a different host.\n"
+"A malicious news host could feed a huge file, need to limit the size."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:860
+#, python-format
+msgid ""
+"Naming system services, including addressbook "
+"subscription providers, add-host services,\n"
+"and jump services, could be malicious. Substantial protections for "
+"subscriptions were implemented\n"
+"in release 0.6.1.31, with additional enhancements in subsequent releases."
+"\n"
+"However, all naming services require some measure of trust, see\n"
+"the naming page for details."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:867
+msgid ""
+"We remain reliant on the DNS service for i2p2.de, losing this would cause"
+" substantial\n"
+"disruption in our ability to attract new users,\n"
+"and would shrink the network (in the short-to-medium term), just as the "
+"loss of i2p.net did."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:879
+msgid ""
+"These attacks aren't directly on the network, but instead go after its "
+"development team \n"
+"by either introducing legal hurdles on anyone contributing to the "
+"development\n"
+"of the software, or by using whatever means are available to get the "
+"developers to \n"
+"subvert the software. Traditional technical measures cannot defeat these"
+" attacks, and\n"
+"if someone threatened the life or livelihood of a developer (or even just"
+" issuing a \n"
+"court order along with a gag order, under threat of prison), we would "
+"have a big problem."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:888
+msgid "However, two techniques help defend against these attacks:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:892
+#, python-format
+msgid ""
+"All components of the network must be open source to enable inspection, "
+"verification, \n"
+"modification, and improvement. If a developer is compromised, once it is"
+" noticed \n"
+"the community should demand explanation and cease to accept that "
+"developer's work.\n"
+"All checkins to our distributed source control "
+"system\n"
+"are cryptographically signed, and the release packagers use a trust-list "
+"system\n"
+"to restrict modifications to those previously approved."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:900
+#, python-format
+msgid ""
+"Development over the network itself, allowing developers to stay "
+"anonymous but still \n"
+"secure the development process. All I2P development can occur through "
+"I2P - using\n"
+"a distributed source control system,\n"
+"a distributed source control system, IRC chat,\n"
+"public web servers,\n"
+"discussion forums (forum.i2p), and the software distribution sites,\n"
+"all available within I2P."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:911
+msgid ""
+"We also maintain relationships with various organizations that offer "
+"legal advice,\n"
+"should any defense be necessary."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:916
+msgid "Implementation attacks (bugs)"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:920
+msgid ""
+"Try as we might, most nontrivial applications include errors in the "
+"design or \n"
+"implementation, and I2P is no exception. There may be bugs that could be"
+" exploited to \n"
+"attack the anonymity or security of the communication running over I2P in"
+" unexpected \n"
+"ways. To help withstand attacks against the design or protocols in use, "
+"we publish \n"
+"all designs and documentation and solicit review and criticism with \n"
+"the hope that many eyes will improve the system.\n"
+"We do not believe in\n"
+"security through "
+"obscurity."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:931
+msgid ""
+"In addition, the code is being \n"
+"treated the same way, with little aversion towards reworking or throwing "
+"out \n"
+"something that isn't meeting the needs of the software system (including "
+"ease of \n"
+"modification). Documentation for the design and implementation of the "
+"network and \n"
+"the software components are an essential part of security, as without "
+"them it is \n"
+"unlikely that developers would be willing to spend the time to learn the "
+"software \n"
+"enough to identify shortcomings and bugs."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:941
+msgid ""
+"Our software is likely, in particular, to contain bugs related to denial "
+"of service\n"
+"through out-of-memory errors (OOMs), cross-site-scripting (XSS) issues "
+"in the router console,\n"
+"and other vulnerabilities to non-standard inputs via the various "
+"protocols."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:947
+#, python-format
+msgid ""
+"I2P is still a small network with a small development community and "
+"almost no\n"
+"interest from academic or research groups.\n"
+"Therefore we lack the analysis that\n"
+"other anonymity networks\n"
+"may have received. We continue to recruit people to\n"
+"get involved and help."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:960
+msgid "Blocklists"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:961
+msgid ""
+"To some extent, I2P could be enhanced to avoid peers operating at IP "
+"addresses\n"
+"listed in a blocklist. Several blocklists are commonly available in "
+"standard formats,\n"
+"listing anti-P2P organizations, potential state-level adversaries, and "
+"others."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:967
+msgid ""
+"To the extent that active peers actually do show up in the actual "
+"blocklist,\n"
+"blocking by only a subset of peers would tend to segment the network,\n"
+"exacerbate reachability problems, and decrease overall reliability.\n"
+"Therefore we would want to agree on a particular blocklist and\n"
+"enable it by default."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:975
+msgid ""
+"Blocklists are only a part (perhaps a small part) of an array of defenses"
+"\n"
+"against maliciousness.\n"
+"In large part the profiling system does a good job of measuring\n"
+"router behavior so that we don't need to trust anything in netDb.\n"
+"However there is more that can be done. For each of the areas in the\n"
+"list above there are improvements we can make in detecting badness."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:984
+msgid ""
+"If a blocklist is hosted at a central location with automatic updates\n"
+"the network is vulnerable to a\n"
+"central resource attack.\n"
+"Automatic subscription to a list gives the list provider the power to "
+"shut\n"
+"the i2p network down. Completely."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:992
+msgid ""
+"Currently, a default blocklist is distributed with our software,\n"
+"listing only the IPs of past DOS sources.\n"
+"There is no automatic update mechanism.\n"
+"Should a particular IP range implement serious attacks on the I2P "
+"network,\n"
+"we would have to ask people to update their blocklist manually through\n"
+"out-of-band mechanisms such as forums, blogs, etc."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tunnel-routing.html:2
+#: i2p2www/pages/site/docs/how/tunnel-routing.html:6
+msgid "Tunnel Overview"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tunnel-routing.html:3
+#: i2p2www/pages/site/docs/tunnels/unidirectional.html:3
+msgid "July 2011"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tunnel-routing.html:7
+msgid ""
+"This page contains an overview of I2P tunnel terminology and operation, "
+"with\n"
+"links to more technical pages, details, and specifications."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tunnel-routing.html:12
+#, python-format
+msgid ""
+"As briefly explained in the introduction, I2P "
+"builds virtual \"tunnels\" -\n"
+"temporary and unidirectional paths through a sequence of routers. These"
+" \n"
+"tunnels are classified as either inbound tunnels (where everything \n"
+"given to it goes towards the creator of the tunnel) or outbound tunnels\n"
+"(where the tunnel creator shoves messages away from them). When Alice\n"
+"wants to send a message to Bob, she will (typically) send it out one of\n"
+"her existing outbound tunnels with instructions for that tunnel's "
+"endpoint\n"
+"to forward it to the gateway router for one of Bob's current inbound \n"
+"tunnels, which in turn passes it to Bob."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tunnel-routing.html:25
+msgid "Alice connecting through her outbound tunnel to Bob via his inbound tunnel"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tunnel-routing.html:27
+msgid "Outbound Gateway"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tunnel-routing.html:28
+msgid "Outbound Participant"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tunnel-routing.html:29
+#: i2p2www/pages/site/docs/tunnels/implementation.html:131
+msgid "Outbound Endpoint"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tunnel-routing.html:30
+#: i2p2www/pages/site/docs/tunnels/implementation.html:140
+msgid "Inbound Gateway"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tunnel-routing.html:31
+msgid "Inbound Participant"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tunnel-routing.html:32
+msgid "Inbound Endpoint"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tunnel-routing.html:36
+msgid "Tunnel vocabulary"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tunnel-routing.html:38
+#, python-format
+msgid ""
+"Tunnel gateway - the first router in a tunnel. For inbound "
+"tunnels,\n"
+"this is the one mentioned in the LeaseSet published in the\n"
+"network database. For outbound tunnels, the\n"
+"gateway is the originating router. (e.g. both A and D above)"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tunnel-routing.html:44
+msgid ""
+"Tunnel endpoint - the last router in a tunnel. (e.g. both C and F"
+" above)"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tunnel-routing.html:45
+msgid ""
+"Tunnel participant - all routers in a tunnel except for the "
+"gateway or\n"
+"endpoint (e.g. both B and E above)"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tunnel-routing.html:49
+msgid ""
+"n-Hop tunnel - a tunnel with a specific number of inter-router "
+"jumps, e.g.:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tunnel-routing.html:51
+msgid "0-hop tunnel - a tunnel where the gateway is also the endpoint"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tunnel-routing.html:52
+msgid ""
+"1-hop tunnel - a tunnel where the gateway talks directly to the "
+"endpoint"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tunnel-routing.html:53
+msgid ""
+"2-(or more)-hop tunnel - a tunnel where there is at least one "
+"intermediate\n"
+"tunnel participant. (the above diagram includes two 2-hop tunnels - one\n"
+"outbound from Alice, one inbound to Bob)"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tunnel-routing.html:60
+#, python-format
+msgid ""
+"Tunnel ID - A 4 "
+"byte integer\n"
+"different for each hop in a tunnel, and unique among all tunnels on a "
+"router.\n"
+"Chosen randomly by the tunnel creator."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tunnel-routing.html:67
+msgid "Tunnel Build Information"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tunnel-routing.html:68
+#, python-format
+msgid ""
+"Routers performing the three roles (gateway, participant, endpoint) are "
+"given\n"
+"different pieces of data in the initial\n"
+"Tunnel Build Message\n"
+"to accomplish their tasks:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tunnel-routing.html:75
+msgid "The tunnel gateway gets:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tunnel-routing.html:77
+#: i2p2www/pages/site/docs/how/tunnel-routing.html:97
+#, python-format
+msgid ""
+"tunnel encryption key - an AES private key for "
+"encrypting\n"
+"messages and instructions to the next hop"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tunnel-routing.html:81
+#: i2p2www/pages/site/docs/how/tunnel-routing.html:101
+#, python-format
+msgid ""
+"tunnel IV key - an AES private key for "
+"double-encrypting\n"
+"the IV to the next hop"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tunnel-routing.html:85
+#: i2p2www/pages/site/docs/how/tunnel-routing.html:105
+#, python-format
+msgid ""
+"reply key - an AES public key for "
+"encrypting\n"
+"the reply to the tunnel build request"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tunnel-routing.html:89
+#: i2p2www/pages/site/docs/how/tunnel-routing.html:109
+msgid ""
+"reply IV - the IV for encrypting the reply to the tunnel build "
+"request"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tunnel-routing.html:90
+msgid "tunnel id - 4 byte integer (inbound gateways only)"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tunnel-routing.html:91
+msgid ""
+"next hop - what router is the next one in the path (unless this is"
+" a 0-hop tunnel, and the gateway is also the endpoint)"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tunnel-routing.html:92
+#: i2p2www/pages/site/docs/how/tunnel-routing.html:112
+msgid "next tunnel id - The tunnel ID on the next hop"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tunnel-routing.html:95
+msgid "All intermediate tunnel participants get:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tunnel-routing.html:110
+msgid "tunnel id - 4 byte integer"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tunnel-routing.html:111
+msgid "next hop - what router is the next one in the path"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tunnel-routing.html:115
+msgid "The tunnel endpoint gets:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tunnel-routing.html:117
+#, python-format
+msgid ""
+"tunnel encryption key - an AES private key for "
+"encrypting\n"
+"messages and instructions to the the endpoint (itself)"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tunnel-routing.html:121
+#, python-format
+msgid ""
+"tunnel IV key - an AES private key for "
+"double-encrypting\n"
+"the IV to the endpoint (itself)"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tunnel-routing.html:125
+#, python-format
+msgid ""
+"reply key - an AES public key for "
+"encrypting\n"
+"the reply to the tunnel build request (outbound endpoints only)"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tunnel-routing.html:129
+msgid ""
+"reply IV - the IV for encrypting the reply to the tunnel build "
+"request (outbound endpoints only)"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tunnel-routing.html:130
+msgid "tunnel id - 4 byte integer (outbound endpoints only)"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tunnel-routing.html:131
+msgid ""
+"reply router - the inbound gateway of the tunnel to send the reply"
+" through (outbound endpoints only)"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tunnel-routing.html:132
+msgid ""
+"reply tunnel id - The tunnel ID of the reply router (outbound "
+"endpoints only)"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tunnel-routing.html:137
+#, python-format
+msgid ""
+"Details are in the\n"
+"tunnel creation specification."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tunnel-routing.html:142
+msgid "Tunnel pooling"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tunnel-routing.html:143
+#, python-format
+msgid ""
+"Several tunnels for a particular purpose may be grouped into a \"tunnel "
+"pool\",\n"
+"as described in the\n"
+"tunnel specification.\n"
+"This provides redundancy and additional bandwidth.\n"
+"The pools used by the router itself are called \"exploratory tunnels\".\n"
+"The pools used by applications are called \"client tunnels\"."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tunnel-routing.html:154
+msgid "Tunnel length"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tunnel-routing.html:155
+#, python-format
+msgid ""
+"As mentioned above, each client requests that their router provide "
+"tunnels to\n"
+"include at least a certain number of hops.\n"
+"The decision as to how many routers\n"
+"to have in one's outbound and inbound tunnels has an important effect "
+"upon the\n"
+"latency, throughput, reliability, and anonymity provided by I2P - the "
+"more peers\n"
+"that messages have to go through, the longer it takes to get there and "
+"the more\n"
+"likely that one of those routers will fail prematurely. The less routers"
+" in a\n"
+"tunnel, the easier it is for an adversary to mount traffic analysis "
+"attacks and\n"
+"pierce someone's anonymity.\n"
+"Tunnel lengths are specified by clients via\n"
+"I2CP options.\n"
+"The maximum number of hops in a tunnel is 7."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tunnel-routing.html:171
+msgid "0-hop tunnels"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tunnel-routing.html:172
+msgid ""
+"With no remote routers in a tunnel, the user has very basic plausible\n"
+"deniability (since no one knows for sure that the peer that sent them the"
+"\n"
+"message wasn't simply just forwarding it on as part of the tunnel). "
+"However, it\n"
+"would be fairly easy to mount a statistical analysis attack and notice "
+"that\n"
+"messages targeting a specific destination are always sent through a "
+"single\n"
+"gateway. Statistical analysis against outbound 0-hop tunnels are more "
+"complex,\n"
+"but could show similar information (though would be slightly harder to "
+"mount)."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tunnel-routing.html:182
+msgid "1-hop tunnels"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tunnel-routing.html:183
+#, python-format
+msgid ""
+"With only one remote router in a tunnel, the user has both plausible\n"
+"deniability and basic anonymity, as long as they are not up against an "
+"internal\n"
+"adversary (as described on threat model)."
+" However,\n"
+"if the adversary ran a sufficient number of routers such that the single "
+"remote\n"
+"router in the tunnel is often one of those compromised ones, they would "
+"be able\n"
+"to mount the above statistical traffic analysis attack."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tunnel-routing.html:192
+msgid "2-hop tunnels"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tunnel-routing.html:193
+msgid ""
+"With two or more remote routers in a tunnel, the costs of mounting the "
+"traffic\n"
+"analysis attack increases, since many remote routers would have to be "
+"compromised\n"
+"to mount it."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tunnel-routing.html:199
+msgid "3-hop (or more) tunnels"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tunnel-routing.html:200
+#, python-format
+msgid ""
+"To reduce the susceptibility to some attacks,\n"
+"3 or more hops are recommended for the highest level of protection.\n"
+"Recent studies\n"
+"also conclude that more than 3 hops does not provide additional "
+"protection."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tunnel-routing.html:208
+msgid "Tunnel default lengths"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tunnel-routing.html:209
+#, python-format
+msgid ""
+"The router uses 2-hop tunnels by default for its exploratory tunnels.\n"
+"Client tunnel defaults are set by the application, using\n"
+"I2CP options.\n"
+"Most applications use 2 or 3 hops as their default."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tunnel-routing.html:218
+msgid "Tunnel testing"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tunnel-routing.html:219
+#, python-format
+msgid ""
+"All tunnels are periodically tested by their creator by sending a\n"
+"DeliveryStatusMessage out an outbound tunnel and bound for another "
+"inbound tunnel\n"
+"(testing both tunnels at once). If either fails a number of consecutive "
+"tests, it is marked as no longer\n"
+"functional. If it was used for a client's inbound tunnel, a new leaseSet\n"
+"is created.\n"
+"Tunnel test failures are also reflected in the\n"
+"capacity rating in the peer "
+"profile."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tunnel-routing.html:230
+msgid "Tunnel creation"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tunnel-routing.html:231
+#, python-format
+msgid ""
+"Tunnel creation is handled by garlic "
+"routing\n"
+"a Tunnel Build Message to a router, requesting that they participate in "
+"the\n"
+"tunnel (providing them with all of the appropriate information, as above,"
+" along\n"
+"with a certificate, which right now is a 'null' cert, but will support "
+"hashcash\n"
+"or other non-free certificates when necessary).\n"
+"That router forwards the message to the next hop in the tunnel.\n"
+"Details are in the\n"
+"tunnel creation specification."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tunnel-routing.html:245
+#, python-format
+msgid ""
+"Multi-layer encryption is handled by garlic"
+" encryption\n"
+"of tunnel messages.\n"
+"Details are in the\n"
+"tunnel specification.\n"
+"The IV of each hop is encrypted with a separate key as explained there."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tunnel-routing.html:257
+msgid ""
+"Other tunnel test techniques could be used, such as\n"
+"garlic wrapping a number of tests into cloves, testing individual tunnel\n"
+"participants separately, etc."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tunnel-routing.html:263
+msgid "Move to 3-hop exploratory tunnels defaults."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tunnel-routing.html:267
+msgid ""
+"In a distant future release,\n"
+"options specifying the pooling, mixing, and chaff generation settings may"
+" be implemented."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tunnel-routing.html:272
+msgid ""
+"In a distant future release,\n"
+"limits on the quantity and size of messages allowed during the\n"
+"tunnel's lifetime may be implemented (e.g. no more than 300 messages or\n"
+"1MB per minute)."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tunnel-routing.html:284
+#: i2p2www/pages/site/docs/tunnels/unidirectional.html:15
+msgid "Tunnel specification"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tunnel-routing.html:286
+#: i2p2www/pages/site/docs/tunnels/unidirectional.html:17
+msgid "Tunnel creation specification"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tunnel-routing.html:288
+msgid "Unidirectional tunnels"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tunnel-routing.html:290
+msgid "Tunnel message specification"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tunnel-routing.html:292
+msgid "Garlic routing"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tunnel-routing.html:294
+msgid "ElGamal/AES+SessionTag"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tunnel-routing.html:296
+msgid "I2CP options"
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2cp.html:3
+msgid "November 2012"
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2cp.html:6
+msgid ""
+"The I2P Client Protocol (I2CP) exposes a strong separation of concerns "
+"between\n"
+"the router and any client that wishes to communicate over the network. "
+"It enables\n"
+"secure and asynchronous messaging by sending and receiving messages over "
+"a \n"
+"single TCP socket, yet never exposing any private keys and authenticating"
+" itself\n"
+"to the router only through signatures. With I2CP, a client application "
+"tells the\n"
+"router who they are (their \"destination\"), what anonymity, reliability,"
+" and \n"
+"latency tradeoffs to make, and where to send messages. In turn the "
+"router uses\n"
+"I2CP to tell the client when any messages have arrived, and to request "
+"authorization\n"
+"for some tunnels to be used."
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2cp.html:18
+#, python-format
+msgid ""
+"The protocol itself has only been implemented in Java, to provide the\n"
+"Client SDK.\n"
+"This SDK is exposed in the i2p.jar package, which implements the client-"
+"side of I2CP.\n"
+"Clients should never need to access the router.jar package, which "
+"contains the\n"
+"router itself and the router-side of I2CP."
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2cp.html:26
+#, python-format
+msgid ""
+"While implementing the client side of I2CP in a non-Java language is "
+"certainly feasible,\n"
+"a non-Java client would also have to implement the\n"
+"streaming library for TCP-style "
+"connections.\n"
+"Together, implementing I2CP and the streaming library would be a sizable "
+"task."
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2cp.html:33
+#, python-format
+msgid ""
+"Applications can take advantage of the base I2CP plus the \n"
+"streaming and datagram libraries\n"
+"by using the Simple Anonymous Messaging or BOB protocols,\n"
+"which do not require clients to deal with any sort of cryptography.\n"
+"Also, clients may access the network by one of several proxies -\n"
+"HTTP, CONNECT, and SOCKS 4/4a/5.\n"
+"Alternatively, Java clients may access those libraries in "
+"ministreaming.jar and streaming.jar.\n"
+"So there are several options for both Java and non-Java applications."
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2cp.html:45
+#, python-format
+msgid ""
+"Client-side end-to-end encryption (encrypting the data over the I2CP "
+"connection)\n"
+"was disabled in I2P release 0.6,\n"
+"leaving in place the ElGamal/AES end-to-end "
+"encryption\n"
+"which is implemented in the router.\n"
+"The only cryptography that client libraries must still implement is\n"
+"DSA public/private key signing\n"
+"for LeaseSets and\n"
+"Session Configurations, and"
+" management of those keys."
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2cp.html:58
+msgid ""
+"In a standard I2P installation, port 7654 is used by external java "
+"clients to communicate\n"
+"with the local router via I2CP.\n"
+"By default, the router binds to address 127.0.0.1. To bind to 0.0.0.0, "
+"set the\n"
+"router advanced configuration option "
+"i2cp.tcp.bindAllInterfaces=true and restart.\n"
+"Clients in the same JVM as the router pass messages directly to the "
+"router\n"
+"through an internal JVM interface."
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2cp.html:67
+msgid "I2CP Protocol Specification"
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2cp.html:68
+#, python-format
+msgid "Now on the I2CP Specification page."
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2cp.html:73
+msgid "I2CP Initialization"
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2cp.html:74
+#, python-format
+msgid ""
+"When a client connects to the router, it first sends a single protocol "
+"version byte (0x2A).\n"
+"Then it sends a GetDate Message and "
+"waits for the SetDate Message "
+"response.\n"
+"Next, it sends a CreateSession "
+"Message containing the session configuration.\n"
+"It next awaits a RequestLeaseSet"
+" Message from the router, indicating that inbound tunnels\n"
+"have been built, and responds with a CreateLeaseSetMessage containing the"
+" signed LeaseSet.\n"
+"The client may now initiate or receive connections from other I2P "
+"destinations."
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2cp.html:83
+msgid "I2CP Options"
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2cp.html:84
+#, python-format
+msgid ""
+"The following options are traditionally passed to the router via\n"
+"a SessionConfig contained "
+"in a CreateSession Message or "
+"a ReconfigureSession "
+"Message."
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2cp.html:90
+msgid "Router-side Options"
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2cp.html:95
+#: i2p2www/pages/site/docs/protocol/i2cp.html:438
+msgid "As Of Release"
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2cp.html:96
+#: i2p2www/pages/site/docs/protocol/i2cp.html:439
+msgid "Recommended Arguments"
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2cp.html:97
+#: i2p2www/pages/site/docs/protocol/i2cp.html:440
+msgid "Allowable Range"
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2cp.html:105
+#: i2p2www/pages/site/docs/protocol/i2cp.html:118
+#: i2p2www/pages/site/docs/protocol/i2cp.html:127
+#: i2p2www/pages/site/docs/protocol/i2cp.html:136
+#: i2p2www/pages/site/docs/protocol/i2cp.html:145
+#: i2p2www/pages/site/docs/protocol/i2cp.html:160
+#: i2p2www/pages/site/docs/protocol/i2cp.html:175
+#: i2p2www/pages/site/docs/protocol/i2cp.html:184
+#: i2p2www/pages/site/docs/protocol/i2cp.html:232
+#: i2p2www/pages/site/docs/protocol/i2cp.html:244
+#: i2p2www/pages/site/docs/protocol/i2cp.html:256
+#, python-format
+msgid "number from %(from)s to %(to)s"
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2cp.html:106
+#: i2p2www/pages/site/docs/protocol/i2cp.html:128
+#: i2p2www/pages/site/docs/protocol/i2cp.html:137
+#: i2p2www/pages/site/docs/protocol/i2cp.html:146
+#: i2p2www/pages/site/docs/protocol/i2cp.html:161
+#: i2p2www/pages/site/docs/protocol/i2cp.html:233
+#: i2p2www/pages/site/docs/protocol/i2cp.html:245
+#: i2p2www/pages/site/docs/protocol/i2cp.html:257
+#: i2p2www/pages/site/docs/protocol/i2cp.html:530
+#, python-format
+msgid "%(from)s to %(to)s"
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2cp.html:108
+msgid ""
+"Number of tunnels in.\n"
+"Limit was increased from 6 to 16 in release 0.9; however, numbers higher "
+"than 6 are not\n"
+"currently recommended, as this is untested and is incompatible with older"
+" releases."
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2cp.html:119
+#: i2p2www/pages/site/docs/protocol/i2cp.html:176
+#: i2p2www/pages/site/docs/protocol/i2cp.html:185
+msgid "No limit"
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2cp.html:121
+msgid "Number of tunnels out"
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2cp.html:130
+msgid "Length of tunnels in"
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2cp.html:139
+msgid "Length of tunnels out"
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2cp.html:148
+msgid ""
+"Random amount to add or subtract to the length of tunnels in.\n"
+"A positive number x means add a random amount from 0 to x inclusive.\n"
+"A negative number -x means add a random amount from -x to x inclusive.\n"
+"The router will limit the total length of the tunnel to 0 to 7 inclusive."
+"\n"
+"The default variance was 1 prior to release 0.7.6."
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2cp.html:163
+msgid ""
+"Random amount to add or subtract to the length of tunnels out.\n"
+"A positive number x means add a random amount from 0 to x inclusive.\n"
+"A negative number -x means add a random amount from -x to x inclusive.\n"
+"The router will limit the total length of the tunnel to 0 to 7 inclusive."
+"\n"
+"The default variance was 1 prior to release 0.7.6."
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2cp.html:178
+msgid "Number of redundant fail-over for tunnels in"
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2cp.html:187
+msgid "Number of redundant fail-over for tunnels out"
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2cp.html:196
+msgid ""
+"Name of tunnel - generally used in routerconsole, which will\n"
+"use the first few characters of the Base64 hash of the destination by "
+"default."
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2cp.html:208
+msgid "Name of tunnel - generally ignored unless inbound.nickname is unset."
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2cp.html:217
+msgid "If incoming zero hop tunnel is allowed"
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2cp.html:226
+msgid "If outgoing zero hop tunnel is allowed"
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2cp.html:235
+#: i2p2www/pages/site/docs/protocol/i2cp.html:247
+msgid ""
+"Number of IP bytes to match to determine if\n"
+"two routers should not be in the same tunnel. 0 to disable."
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2cp.html:259
+msgid ""
+"Priority adjustment for outbound messages.\n"
+"Higher is higher priority."
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2cp.html:271
+msgid "Should generally be set to true for clients and false for servers"
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2cp.html:280
+msgid ""
+"Guaranteed is disabled;\n"
+"None implemented in 0.8.1; the streaming lib default is None as of 0.8.1,"
+" the client side default is None as of 0.9.4"
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2cp.html:292
+#: i2p2www/pages/site/docs/protocol/i2cp.html:571
+msgid ""
+"If true, the router just sends the MessagePayload instead\n"
+"of sending a MessageStatus and awaiting a ReceiveMessageBegin."
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2cp.html:304
+msgid ""
+"Comma-separated list of Base 64 Hashes of peers to build tunnels through;"
+" for debugging only"
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2cp.html:313
+#: i2p2www/pages/site/docs/protocol/i2cp.html:325
+msgid ""
+"For authorization, if required by the router.\n"
+"If the client is running in the same JVM as a router, this option is not "
+"required."
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2cp.html:337
+msgid ""
+"Number of ElGamal/AES Session Tags to send at a time.\n"
+"For clients with relatively low bandwidth per-client-pair (IRC, some UDP "
+"apps), this may be set lower."
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2cp.html:349
+msgid ""
+"Minimum number of ElGamal/AES Session Tags before we send more.\n"
+"Recommended: approximately tagsToSend * 2/3"
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2cp.html:361
+msgid ""
+"Set to false to disable ever bundling a reply LeaseSet.\n"
+"For clients that do not publish their LeaseSet, this option must be true\n"
+"for any reply to be possible. \"true\" is also recommended for multihomed"
+" servers\n"
+"with long connection times."
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2cp.html:368
+msgid ""
+"Setting to \"false\" may save significant outbound bandwidth, especially "
+"if\n"
+"the client is configured with a large number of inbound tunnels (Leases)."
+"\n"
+"If replies are still required, this may shift the bandwidth burden to\n"
+"the far-end client and the floodfill.\n"
+"There are several cases where \"false\" may be appropriate:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2cp.html:376
+msgid "Unidirectional communication, no reply required"
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2cp.html:377
+msgid "LeaseSet is published and higher reply latency is acceptable"
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2cp.html:378
+msgid ""
+"LeaseSet is published, client is a \"server\", all connections are "
+"inbound\n"
+"so the connecting far-end destination obviously has the leaseset already."
+"\n"
+"Connections are either short, or it is acceptable for latency on a long-"
+"lived\n"
+"connection to temporarily increase while the other end re-fetches the "
+"LeaseSet\n"
+"after expiration.\n"
+"HTTP servers may fit these requirements."
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2cp.html:396
+msgid ""
+"Any other options prefixed with \"inbound.\" are stored\n"
+"in the \"unknown options\" properties of the inbound tunnel pool's "
+"settings."
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2cp.html:408
+msgid ""
+"Any other options prefixed with \"outbound.\" are stored\n"
+"in the \"unknown options\" properties of the outbound tunnel pool's "
+"settings."
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2cp.html:415
+msgid ""
+"Note: Large quantity, length, or variance settings may cause significant "
+"performance or reliability problems."
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2cp.html:419
+msgid ""
+"Note: As of release 0.7.7, option names and values must use UTF-8 "
+"encoding.\n"
+"This is primarily useful for nicknames.\n"
+"Prior to that release, options with multi-byte characters were corrupted."
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2cp.html:425
+msgid ""
+"The following options are interpreted on the client side,\n"
+"and will be interpreted if passed to the I2PSession via the "
+"I2PClient.createSession() call.\n"
+"The streaming lib should also pass these options through to I2CP.\n"
+"Other implementations may have different defaults."
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2cp.html:433
+msgid "Client-side Options"
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2cp.html:451
+msgid ""
+"Router hostname.\n"
+"If the client is running in the same JVM as a router, this option is "
+"ignored, and the client connects to that router internally."
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2cp.html:463
+msgid ""
+"Router I2CP port.\n"
+"If the client is running in the same JVM as a router, this option is "
+"ignored, and the client connects to that router internally."
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2cp.html:475
+msgid ""
+"Connect to the router using SSL.\n"
+"If the client is running in the same JVM as a router, this option is "
+"ignored, and the client connects to that router internally."
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2cp.html:487
+msgid "Gzip outbound data"
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2cp.html:496
+msgid "Reduce tunnel quantity when idle"
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2cp.html:505
+msgid "Close I2P session when idle"
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2cp.html:512
+#: i2p2www/pages/site/docs/protocol/i2cp.html:521
+#, python-format
+msgid "%(num)s minimum"
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2cp.html:514
+msgid "(ms) Idle time required (default 20 minutes, minimum 5 minutes)"
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2cp.html:523
+msgid "(ms) Idle time required (default 30 minutes)"
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2cp.html:532
+msgid "Tunnel quantity when reduced (applies to both inbound and outbound)"
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2cp.html:541
+msgid "Encrypt the lease"
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2cp.html:550
+msgid "Base64 SessionKey (44 characters)"
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2cp.html:559
+msgid ""
+"Guaranteed is disabled;\n"
+"None implemented in 0.8.1; None is the default as of 0.9.4"
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2cp.html:578
+msgid ""
+"Note: All arguments, including numbers, are strings. True/false values "
+"are case-insensitive strings.\n"
+"Anything other than case-insensitive \"true\" is interpreted as false.\n"
+"All option names are case-sensitive."
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2cp.html:584
+msgid "I2CP Payload Data Format and Multiplexing"
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2cp.html:585
+#, python-format
+msgid ""
+"The end-to-end messages handled by I2CP (i.e. the data sent by the client"
+" in a\n"
+"SendMessageMessage\n"
+"and received by the client in a\n"
+"MessagePayloadMessage)\n"
+"are gzipped with a standard 10-byte gzip\n"
+"header beginning with 0x1F 0x8B 0x08 as\n"
+"specified by RFC "
+"1952.\n"
+"As of release 0.7.1, I2P uses ignored portions of the gzip header to "
+"include\n"
+"protocol, from-port, and to-port information, thus supporting streaming "
+"and\n"
+"datagrams on the same destination, and allowing query/response using "
+"datagrams\n"
+"to work reliably in the presence of multiple channels."
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2cp.html:599
+msgid ""
+"The gzip function cannot be completely turned off, however setting "
+"i2cp.gzip=false\n"
+"turns the gzip effort setting to 0, which may save a little CPU."
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2cp.html:605
+#: i2p2www/pages/site/docs/protocol/i2np.html:33
+msgid "Bytes"
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2cp.html:606
+msgid "Content"
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2cp.html:611
+msgid "Gzip header"
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2cp.html:616
+msgid "Gzip flags"
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2cp.html:621
+msgid "I2P Source port (Gzip mtime)"
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2cp.html:626
+msgid "I2P Destination port (Gzip mtime)"
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2cp.html:631
+msgid "Gzip xflags"
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2cp.html:636
+msgid "I2P Protocol (6 = Streaming, 17 = Datagram, 18 = Raw Datagrams) (Gzip OS)"
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2cp.html:640
+msgid ""
+"Data integrity is verified with the standard gzip CRC-32 as\n"
+"specified by RFC 1952."
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2cp.html:648
+msgid "Implement I2CP and the streaming library in another programming language."
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2cp.html:652
+msgid "Is the initial Get Date / Set Date handshake required?"
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2cp.html:656
+msgid ""
+"The current authorization mechanism could be modified to use hashed "
+"passwords."
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2cp.html:660
+msgid ""
+"Private Keys are included in the Create Lease Set message,\n"
+"are they really required? Revocation is unimplemented."
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2cp.html:665
+#, python-format
+msgid ""
+"Some improvements may be able to use messages previously defined but not "
+"implemented.\n"
+"For reference, here is the\n"
+"I2CP Protocol Specification Version 0.9\n"
+"(PDF) dated August 28, 2003.\n"
+"That document also references the\n"
+"Common Data Structures Specification Version 0.9."
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2np.html:3
+msgid "June 2013"
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2np.html:6
+msgid "I2P Network Protocol"
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2np.html:7
+msgid ""
+"The I2P Network Protocol (I2NP),\n"
+"which is sandwiched between I2CP and the various I2P transport protocols,"
+" manages the\n"
+"routing and mixing of messages between routers, as well as the selection "
+"of what\n"
+"transports to use when communicating with a peer for which there are "
+"multiple\n"
+"common transports supported."
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2np.html:15
+msgid "I2NP Definition"
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2np.html:16
+msgid ""
+"I2NP (I2P Network Protocol) messages can be used for one-hop, router-to-"
+"router, point-to-point messages.\n"
+"By encrypting and wrapping messages in other messages, they can be sent "
+"in a secure way\n"
+"through multiple hops to the ultimate destination.\n"
+"Priority is only used locally at the origin, i.e. when queuing for "
+"outbound delivery."
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2np.html:23
+#, python-format
+msgid ""
+"The priorities listed below may not be current and are subject to change."
+"\n"
+"See the OutNetMessage Javadocs\n"
+"for the current priority settings.\n"
+"Priority queueing implementation may vary."
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2np.html:30
+msgid "Message Format"
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2np.html:33
+#: i2p2www/pages/site/docs/spec/streaming.html:35
+msgid "Field"
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2np.html:34
+msgid "Unique ID"
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2np.html:35
+msgid "Expiration"
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2np.html:36
+#: i2p2www/pages/site/docs/protocol/i2np.html:93
+msgid "Payload Length"
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2np.html:37
+msgid "Checksum"
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2np.html:38
+msgid "Payload"
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2np.html:41
+#, python-format
+msgid ""
+"While the maximum payload size is nominally 64KB, the size is further "
+"constrained by the\n"
+"method of fragmenting I2NP messages into multiple 1KB tunnel messages as "
+"described on\n"
+"the tunnel implementation page.\n"
+"The maximum number of fragments is 64, and the message may not be "
+"perfectly aligned,\n"
+"So the message must nominally fit in 63 fragments."
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2np.html:49
+msgid ""
+"The maximum size of an initial fragment is 956 bytes (assuming TUNNEL "
+"delivery mode);\n"
+"the maximum size of a follow-on fragment is 996 bytes.\n"
+"Therefore the maximum size is approximately 956 + (62 * 996) = 62708 "
+"bytes, or 61.2 KB."
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2np.html:55
+msgid ""
+"In addition, the transports may have additional restrictions.\n"
+"NTCP currently limits to 16KB - 6 = 16378 bytes but this will be "
+"increased in a future release.\n"
+"The SSU limit is approximately 32 KB."
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2np.html:61
+msgid ""
+"Note that these are not the limits for datagrams that the client sees, as"
+" the\n"
+"router may bundle a reply leaseset and/or session tags together with the "
+"client message\n"
+"in a garlic message. The leaseset and tags together may add about 5.5KB.\n"
+"Therefore the current datagram limit is about 10KB. This limit will be\n"
+"increased in a future release."
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2np.html:69
+msgid "Message Types"
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2np.html:70
+msgid ""
+"Higher-numbered priority is higher priority.\n"
+"The majority of traffic is TunnelDataMessages (priority 400),\n"
+"so anything above 400 is essentially high priority, and\n"
+"anything below is low priority.\n"
+"Note also that many of the messages are generally routed\n"
+"through exploratory tunnels, not client tunnels, and\n"
+"therefore may not be in the same queue unless the\n"
+"first hops happen to be on the same peer."
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2np.html:81
+msgid ""
+"Also, not all message types are sent unencrypted.\n"
+"For example, when testing a tunnel, the router wraps a\n"
+"DeliveryStatusMessage, which is wrapped in a GarlicMessage,\n"
+"which is wrapped in a DataMessage."
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2np.html:91
+msgid "Message"
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2np.html:92
+msgid "Type"
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2np.html:95
+msgid "Comments"
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2np.html:103
+msgid "May vary"
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2np.html:109
+msgid ""
+"Size is 65 + 32*(number of hashes) where typically, the hashes for\n"
+"three floodfill routers are returned."
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2np.html:118
+msgid "Varies"
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2np.html:120
+msgid ""
+"Priority may vary.\n"
+"Size is 898 bytes for a typical 2-lease leaseSet.\n"
+"RouterInfo structures are compressed, and size varies; however\n"
+"there is a continuing effort to reduce the amount of data published in a "
+"RouterInfo\n"
+"as we approach release 1.0."
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2np.html:134
+msgid "Priority may vary on a per-destination basis"
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2np.html:144
+msgid ""
+"Used for message replies, and for testing tunnels - generally wrapped in "
+"a GarlicMessage"
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2np.html:152
+msgid ""
+"Generally wrapped in a DataMessage -\n"
+"but when unwrapped, given a priority of 100 by the forwarding router"
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2np.html:179
+msgid ""
+"The most common message. Priority for tunnel participants, outbound "
+"endpoints, and inbound gateways was\n"
+"reduced to 200 as of release 0.6.1.33.\n"
+"Outbound gateway messages (i.e. those originated locally) remains at 400."
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2np.html:199
+msgid "Shorter TunnelBuildMessage as of 0.7.12"
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2np.html:207
+msgid "Shorter TunnelBuildReplyMessage as of 0.7.12"
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2np.html:210
+#, python-format
+msgid "Others listed in 2003 Spec"
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2np.html:216
+msgid "Obsolete, Unused"
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2np.html:220
+msgid "Full Protocol Specification"
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2np.html:221
+#, python-format
+msgid ""
+"On the I2NP Specification page.\n"
+"See also the\n"
+"Common Data Structure Specification "
+"page."
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2np.html:228
+msgid ""
+"It isn't clear whether the current priority scheme is generally "
+"effective,\n"
+"and whether the priorities for various messages should be adjusted "
+"further.\n"
+"This is a topic for further research, analysis and testing."
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/index.html:2
+msgid "Protocol Stack"
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/index.html:7
+#, python-format
+msgid ""
+"Here is the protocol stack for I2P.\n"
+"See also the Index to Technical Documentation."
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/index.html:12
+msgid ""
+"Each of the layers in the stack provides extra capabilities.\n"
+"The capabilities are listed below, starting at the bottom of the protocol"
+" stack."
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/index.html:18
+msgid "Internet Layer:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/index.html:20
+msgid ""
+"IP: Internet Protocol, allow addressing hosts on the regular internet and"
+" routing packets across the internet using best-effort delivery."
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/index.html:23
+msgid "Transport Layer:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/index.html:25
+msgid ""
+"TCP: Transmission Control Protocol, allow reliable, in-order delivery of "
+"packets across the internet."
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/index.html:27
+msgid ""
+"UDP: User Datagram Protocol, allow unreliable, out-of-order delivery of "
+"packets across the internet."
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/index.html:30
+msgid ""
+"I2P Transport Layer: provide encrypted connections between 2 I2P "
+"routers. These are not anonymous yet, this is strictly a hop-to-hop "
+"connection.\n"
+"Two protocols are implemented to provide these capabilities. NTCP builds "
+"on top of TCP, while SSU uses UDP."
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/index.html:35
+msgid "NIO-based TCP"
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/index.html:37
+msgid "Secure Semi-reliable UDP"
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/index.html:40
+msgid "I2P Tunnel Layer: provide full encrypted tunnel connections."
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/index.html:42
+#, python-format
+msgid ""
+"Tunnel messages: tunnel messages are "
+"large messages containing encrypted I2NP (see below) messages and "
+"encrypted instructions for their delivery.\n"
+"The encryption is layered. The first hop will decrypt the tunnel message "
+"and read a part. Another part can still be encrypted (with another key),"
+"\n"
+"so it will be forwarded."
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/index.html:48
+#, python-format
+msgid ""
+"I2NP messages: I2P Network Protocol messages are"
+" used to pass messages through multiple routers. These I2NP messages are "
+"combined in tunnel messages."
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/index.html:53
+msgid ""
+"I2P Garlic Layer: provide encrypted and anonymous end-to-end I2P "
+"message delivery."
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/index.html:55
+#, python-format
+msgid ""
+"I2NP messages: I2P Network Protocol messages are"
+" wrapped in each other and used to ensure encryption between two tunnels "
+"and are passed along from source to destination, keeping both anonymous."
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/index.html:61
+msgid ""
+"The following layers are strictly speaking no longer part of the I2P "
+"Protocol stack, they are not part of the core 'I2P router' functionality."
+"\n"
+"However, each of these layers adds additional functionality, to allow "
+"applications simple and convenient I2P usage."
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/index.html:67
+msgid ""
+"I2P Client Layer: allow any client to use I2P functionality, "
+"without requiring the direct use of the router API."
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/index.html:69
+#, python-format
+msgid ""
+"I2CP: I2P Client Protocol, allows secure and "
+"asynchronous messaging over I2P by communicating messages over the I2CP "
+"TCP socket."
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/index.html:74
+msgid ""
+"I2P End-to-end Transport Layer: allow TCP- or UDP-like "
+"functionality on top of I2P."
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/index.html:76
+#, python-format
+msgid ""
+"Streaming Library: an implementation of "
+"TCP-like streams over I2P. This allows easier porting of existing "
+"applications to I2P."
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/index.html:80
+#, python-format
+msgid ""
+"Datagram Library: an implementation of UDP-"
+"like messages over I2P. This allows easier porting of existing "
+"applications to I2P."
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/index.html:85
+msgid ""
+"I2P Application Interface Layer: additional (optional) libraries "
+"allowing easier implementations on top of I2P."
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/index.html:93
+msgid "I2P Application Proxy Layer: proxy systems."
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/index.html:95
+#, python-format
+msgid "HTTP Client/Server, IRC Client, SOCKS, Streamr"
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/index.html:99
+msgid ""
+"Finally, what could be considered the 'I2P application layer', is "
+"a large number of applications on top of I2P.\n"
+"We can order this based on the I2P stack layer they use."
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/index.html:104
+msgid "Streaming/datagram applications: i2psnark, Syndie, i2phex..."
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/index.html:105
+msgid "SAM/BOB applications: IMule, i2p-bt, i2prufus, Robert..."
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/index.html:106
+#, python-format
+msgid ""
+"Other I2P applications: Syndie, EepGet, plugins..."
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/index.html:107
+msgid ""
+"Regular applications: Jetty, Apache, Monotone, CVS, browsers, "
+"e-mail..."
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/index.html:111
+msgid "I2P Network stack"
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/index.html:113
+msgid "Figure 1: The layers in the I2P Network stack."
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/index.html:118
+msgid "Note: SAM/SAMv2 can use both the streaming lib and datagrams."
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/blockfile.html:2
+msgid "I2P Blockfile Specification"
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/blockfile.html:3
+msgid "January 2012"
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/blockfile.html:6
+msgid "Blockfile and Hosts Database Specification"
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/blockfile.html:8
+#, python-format
+msgid ""
+"This document specifies\n"
+"the I2P blockfile file format\n"
+"and the tables in the hostsdb.blockfile used by the Blockfile Naming Service."
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/blockfile.html:14
+msgid ""
+"The blockfile provides fast Destination lookup in a compact format. While"
+" the blockfile page overhead is substantial,\n"
+"the destinations are stored in binary rather than in Base 64 as in the "
+"hosts.txt format.\n"
+"In addition, the blockfile provides the capability of arbitrary metadata "
+"storage\n"
+"(such as added date, source, and comments) for each entry.\n"
+"The metadata may be used in the future to provide advanced addressbook "
+"features.\n"
+"The blockfile storage requirement is a modest increase over the hosts.txt"
+" format, and the blockfile provides\n"
+"approximately 10x reduction in lookup times."
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/blockfile.html:24
+#, python-format
+msgid ""
+"A blockfile is simply on-disk storage of multiple sorted maps (key-value "
+"pairs),\n"
+"implemented as skiplists.\n"
+"The blockfile format is adopted from the\n"
+"Metanotion Blockfile Database.\n"
+"First we will define the file format, then the use of that format by the "
+"BlockfileNamingService."
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/blockfile.html:32
+msgid "Blockfile Format"
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/blockfile.html:33
+msgid ""
+"The original blockfile spec was modified to add magic numbers to each "
+"page.\n"
+"The file is structured in 1024-byte pages. Pages are numbered starting "
+"from 1.\n"
+"The \"superblock\" is always at page 1, i.e. starting at byte 0 in the "
+"file.\n"
+"The metaindex skiplist is always at page 2, i.e. starting at byte 1024 in"
+" the file."
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/blockfile.html:40
+msgid ""
+"All 2-byte integer values are unsigned.\n"
+"All 4-byte integer values (page numbers) are signed and negative values "
+"are illegal."
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/blockfile.html:45
+msgid ""
+"The database is designed to be opened and accessed by a single thread.\n"
+"The BlockfileNamingService provides synchronization."
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/blockfile.html:50
+msgid "Superblock format:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/blockfile.html:65
+msgid "Skip list block page format:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/blockfile.html:80
+msgid ""
+"Skip level block page format is as follows.\n"
+"All levels have a span. Not all spans have levels."
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/blockfile.html:95
+msgid ""
+"Skip span block page format is as follows.\n"
+"Key/value structures are sorted by key within each span and across all "
+"spans.\n"
+"Key/value structures are sorted by key within each span.\n"
+"Spans other than the first span may not be empty."
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/blockfile.html:112
+msgid "Span Continuation block page format:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/blockfile.html:123
+msgid ""
+"Key/value structure format is as follows.\n"
+"Key and value lengths must not be split across pages, i.e. all 4 bytes "
+"must be on the same page.\n"
+"If there is not enough room the last 1-3 bytes of a page are unused and "
+"the lengths will\n"
+"be at offset 8 in the continuation page.\n"
+"Key and value data may be split across pages.\n"
+"Max key and value lengths are 65535 bytes."
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/blockfile.html:139
+msgid "Free list block page format:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/blockfile.html:151
+msgid "Free page block format:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/blockfile.html:160
+msgid ""
+"The metaindex (located at page 2) is a mapping of US-ASCII strings to "
+"4-byte integers.\n"
+"The key is the name of the skiplist and the value is the page index of "
+"the skiplist."
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/blockfile.html:165
+msgid "Blockfile Naming Service Tables"
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/blockfile.html:166
+msgid ""
+"The tables created and used by the BlockfileNamingService are as follows."
+"\n"
+"The maximum number of entries per span is 16."
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/blockfile.html:171
+msgid "Properties Skiplist"
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/blockfile.html:172
+#, python-format
+msgid ""
+"%(INFO)s is the master database skiplist with String/Properties key/value"
+" entries containing only one entry:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/blockfile.html:184
+msgid "Reverse Lookup Skiplist"
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/blockfile.html:185
+#, python-format
+msgid ""
+"%(REVERSE)s is the reverse lookup skiplist with Integer/Properties "
+"key/value entries\n"
+" (as of database version 2):"
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/blockfile.html:199
+msgid "hosts.txt, userhosts.txt, and privatehosts.txt Skiplists"
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/blockfile.html:200
+msgid ""
+"For each host database, there is a skiplist containing\n"
+"the hosts for that database.\n"
+"The keys/values in these skiplists are as follows:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/blockfile.html:211
+msgid "The DestEntry Properties typically contains:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/blockfile.html:220
+msgid "Hostname keys are stored in lower-case and always end in \".i2p\"."
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/common-structures.html:2
+msgid "Common structure Specification"
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/common-structures.html:6
+msgid "Data types Specification"
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/common-structures.html:7
+#, python-format
+msgid ""
+"This document describes some data types common to all I2P protocols, like"
+"\n"
+"I2NP, I2CP,\n"
+"SSU, etc."
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/common-structures.html:17
+msgid "Represents a non-negative integer.\n"
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/common-structures.html:20
+#: i2p2www/pages/site/docs/spec/common-structures.html:31
+#: i2p2www/pages/site/docs/spec/common-structures.html:41
+#: i2p2www/pages/site/docs/spec/common-structures.html:54
+#: i2p2www/pages/site/docs/spec/common-structures.html:69
+#: i2p2www/pages/site/docs/spec/common-structures.html:82
+#: i2p2www/pages/site/docs/spec/common-structures.html:94
+#: i2p2www/pages/site/docs/spec/common-structures.html:106
+#: i2p2www/pages/site/docs/spec/common-structures.html:118
+#: i2p2www/pages/site/docs/spec/common-structures.html:130
+#: i2p2www/pages/site/docs/spec/common-structures.html:142
+#: i2p2www/pages/site/docs/spec/common-structures.html:154
+#: i2p2www/pages/site/docs/spec/common-structures.html:166
+#: i2p2www/pages/site/docs/spec/common-structures.html:178
+#: i2p2www/pages/site/docs/spec/common-structures.html:231
+#: i2p2www/pages/site/docs/spec/common-structures.html:303
+#: i2p2www/pages/site/docs/spec/common-structures.html:352
+#: i2p2www/pages/site/docs/spec/common-structures.html:404
+#: i2p2www/pages/site/docs/spec/common-structures.html:451
+#: i2p2www/pages/site/docs/spec/common-structures.html:586
+#: i2p2www/pages/site/docs/spec/common-structures.html:643
+#: i2p2www/pages/site/docs/spec/streaming.html:35
+msgid "Contents"
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/common-structures.html:21
+msgid "1 to 8 bytes in network byte order representing an unsigned integer\n"
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/common-structures.html:27
+msgid ""
+"The number of milliseconds since midnight on January 1, 1970 in the GMT "
+"timezone.\n"
+"If the number is 0, the date is undefined or null.\n"
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/common-structures.html:32
+msgid "8 byte Integer\n"
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/common-structures.html:38
+msgid "Represents a UTF-8 encoded string.\n"
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/common-structures.html:42
+msgid ""
+"1 or more bytes where the first byte is the number of bytes (not "
+"characters!)\n"
+"in the string and the remaining 0-255 bytes are the non-null terminated "
+"UTF-8 encoded character array.\n"
+"Length limit is 255 bytes (not characters). Length may be 0.\n"
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/common-structures.html:50
+msgid ""
+"A boolean value, supporting null/unknown representation\n"
+"0=false, 1=true, 2=unknown/null\n"
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/common-structures.html:55
+msgid "1 byte Integer\n"
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/common-structures.html:59
+msgid "Deprecated - unused\n"
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/common-structures.html:65
+#, python-format
+msgid ""
+"This structure is used in ElGamal encryption, representing only the "
+"exponent, not the primes, which are constant and defined in\n"
+"the cryptography specification.\n"
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/common-structures.html:70
+#: i2p2www/pages/site/docs/spec/common-structures.html:83
+msgid "256 bytes\n"
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/common-structures.html:78
+#, python-format
+msgid ""
+"This structure is used in ElGamal decryption, representing only the "
+"exponent, not the primes which are constant and defined in\n"
+"the cryptography specification.\n"
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/common-structures.html:91
+msgid "This structure is used for AES256 encryption and decryption.\n"
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/common-structures.html:95
+#: i2p2www/pages/site/docs/spec/common-structures.html:143
+#: i2p2www/pages/site/docs/spec/common-structures.html:155
+msgid "32 bytes\n"
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/common-structures.html:103
+#, python-format
+msgid ""
+"This structure is used for verifying DSA signatures.\n"
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/common-structures.html:107
+msgid "128 bytes\n"
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/common-structures.html:115
+#, python-format
+msgid ""
+"This structure is used for creating DSA signatures.\n"
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/common-structures.html:119
+msgid "20 bytes\n"
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/common-structures.html:127
+#, python-format
+msgid ""
+"This structure represents the DSA "
+"signature of some data.\n"
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/common-structures.html:131
+msgid "40 bytes\n"
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/common-structures.html:139
+msgid "Represents the SHA256 of some data.\n"
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/common-structures.html:151
+msgid "A random number\n"
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/common-structures.html:163
+msgid "Defines an identifier that is unique to each router in a tunnel.\n"
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/common-structures.html:167
+msgid "4 byte Integer\n"
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/common-structures.html:175
+msgid ""
+"A certificate is a container for various receipts or proof of works used "
+"throughout the I2P network.\n"
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/common-structures.html:179
+msgid ""
+"1 byte Integer specifying certificate type,"
+" followed by a 2 Integer specifying the "
+"size of the certificate payload, then that many bytes.\n"
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/common-structures.html:205
+msgid ""
+"For Router Identities, the "
+"Certificate is always NULL, no others are currently implemented."
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/common-structures.html:209
+#, python-format
+msgid ""
+"For Garlic Cloves, the "
+"Certificate is always NULL, no others are currently implemented."
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/common-structures.html:213
+#, python-format
+msgid ""
+"For Garlic Messages, the Certificate "
+"is always NULL, no others are currently implemented."
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/common-structures.html:217
+msgid ""
+"For Destinations, the Certificate may"
+" be non-NULL,\n"
+"however non-NULL certs are not widely used, and any checking is left to "
+"the application-level."
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/common-structures.html:228
+msgid "A set of key/value mappings or properties\n"
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/common-structures.html:232
+msgid "A 2-byte size Integer followed by a series of String=String; pairs\n"
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/common-structures.html:259
+msgid ""
+"The encoding isn't optimal - we either need the '=' and ';' characters, "
+"or the string lengths, but not both"
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/common-structures.html:263
+msgid ""
+"Some documentation says that the strings may not include '=' or ';' but "
+"this encoding supports them"
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/common-structures.html:267
+msgid ""
+"Strings are defined to be UTF-8 but in the current implementation, I2CP "
+"uses UTF-8 but I2NP does not.\n"
+"For example,\n"
+"UTF-8 strings in a RouterInfo options mapping in a I2NP Database Store "
+"Message will be corrupted."
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/common-structures.html:273
+msgid ""
+"Mappings contained in I2NP messages (i.e. in a RouterAddress or "
+"RouterInfo)\n"
+"must be sorted by key so that the signature will be invariant."
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/common-structures.html:278
+#, python-format
+msgid ""
+"Mappings contained in an I2CP "
+"SessionConfig\n"
+"must be sorted by key so that the signature will be invariant."
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/common-structures.html:283
+msgid ""
+"Key and value string length limits are 255 bytes (not characters) each, "
+"plus the length byte. Length byte may be 0."
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/common-structures.html:287
+msgid ""
+"Total length limit is 65535 bytes, plus the 2 byte size field, or 65537 "
+"total."
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/common-structures.html:296
+msgid "Common structure specification"
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/common-structures.html:300
+msgid "Defines the way to uniquely identify a particular router\n"
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/common-structures.html:304
+msgid ""
+"PublicKey followed by SigningPublicKey and then a Certificate\n"
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/common-structures.html:341
+msgid ""
+"The certificate for a RouterIdentity is currently unused and is always "
+"NULL."
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/common-structures.html:349
+msgid ""
+"A Destination defines a particular endpoint to which messages can be "
+"directed for secure delivery.\n"
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/common-structures.html:353
+msgid ""
+"PublicKey followed by a SigningPublicKey and then a Certificate\n"
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/common-structures.html:401
+msgid ""
+"Defines the authorization for a particular tunnel to receive messages "
+"targeting a Destination.\n"
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/common-structures.html:405
+msgid ""
+"SHA256 Hash of the\n"
+"RouterIdentity of the gateway "
+"router, then the TunnelId, and finally an "
+"end Date\n"
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/common-structures.html:436
+msgid "Total size: 44 bytes"
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/common-structures.html:446
+msgid ""
+"Contains all of the currently authorized Leases for a particular Destination, the PublicKey to which garlic messages can be "
+"encrypted,\n"
+"and then the public key that can "
+"be used to revoke this particular version of the structure. The LeaseSet is one of the two structures "
+"stored in the network database(\n"
+"the other being RouterInfo), and is "
+"keyed under the SHA256 of the contained Destination.\n"
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/common-structures.html:452
+msgid ""
+"Destination, followed by a PublicKey for encryption, then a SigningPublicKey which can be used to"
+" revoke this version of the LeaseSet,\n"
+"then a 1 byte Integer specifying how many "
+"Lease structures are in the set, followed "
+"by the actual Lease structures and finally "
+"a Signature of the previous\n"
+"bytes signed by the Destination's SigningPrivateKey"
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/common-structures.html:544
+msgid ""
+"The public key of the destination was used for the old i2cp-to-i2cp "
+"encryption\n"
+"which was disabled in version 0.6, it is currently unused."
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/common-structures.html:549
+#, python-format
+msgid ""
+"The encryption key is used for end-to-end ElGamal/AES+SessionTag encryption.\n"
+"It is currently generated anew at every router startup, it is not "
+"persistent."
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/common-structures.html:554
+msgid ""
+"The signature may be verified using the signing public key of the "
+"destination."
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/common-structures.html:558
+msgid ""
+"The signing_key is currently unused. It was intended for LeaseSet "
+"revocation, which is unimplemented.\n"
+"It is currently generated anew at every router startup, it is not "
+"persistent."
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/common-structures.html:562
+msgid ""
+"The earliest expiration of all the Leases is treated as the timestamp or "
+"version of the LeaseSet.\n"
+"Routers will generally not accept a store of a LeaseSet unless it is "
+"\"newer\" than the current one.\n"
+"Take care when publishing a new LeaseSet where the oldest Lease is the "
+"same as the oldest Lease\n"
+"in the previous LeaseSet. The publishing router should generally "
+"increment the expiration\n"
+"of the oldest Lease by at least 1 ms in that case."
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/common-structures.html:569
+msgid ""
+"Prior to release 0.9.7, when included in a DatabaseStore Message sent by "
+"the originating router,\n"
+"the router set all the published leases' expirations to the same value, "
+"that of the\n"
+"earliest lease. As of release 0.9.7, the router publishes the actual "
+"lease expiration for each lease.\n"
+"This is an implementation detail and not part of the structures "
+"specification."
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/common-structures.html:583
+msgid ""
+"This structure defines the means to contact a router through a transport "
+"protocol.\n"
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/common-structures.html:587
+msgid ""
+"1 byte Integer defining the relative cost "
+"of using the address, where 0 is free and 255 is expensive, followed by "
+"the expiration Date after which the address "
+"should not be used, or if null, the address never expires.\n"
+"After that comes a String defining the "
+"transport protocol this router address uses. Finally there is a Mapping containing all of the transport "
+"specific options necessary to establish the connection, such as\n"
+"IP address, port number, email address, URL, etc.\n"
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/common-structures.html:622
+msgid "Cost is typically 5 or 6 for SSU, and 10 or 11 for NTCP."
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/common-structures.html:626
+msgid ""
+"Expiration is currently unused, always null (all zeroes)).\n"
+"As of release 0.9.3, the expiration is assumed zero and not stored, so "
+"any non-zero expiration\n"
+"will fail in the RouterInfo signature verification.\n"
+"Implementing expiration (or another use for these bytes) will be a "
+"backwards-incompatible change."
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/common-structures.html:639
+msgid ""
+"Defines all of the data that a router wants to publish for the network to"
+" see. The RouterInfo is one of two "
+"structures stored in the network database(the other being LeaseSet, and is keyed under the SHA256 of"
+"\n"
+"the contained RouterIdentity.\n"
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/common-structures.html:644
+msgid ""
+"RouterIdentity followed by the Date, when the entry was published\n"
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/common-structures.html:723
+msgid ""
+"The peer_size Integer may be followed by a list of that many router "
+"hashes.\n"
+"This is currently unused. It was intended for a form of restricted "
+"routes, which is unimplemented.\n"
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/common-structures.html:728
+msgid ""
+"The signature may be verified using the signing public key of the "
+"router_ident.\n"
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/common-structures.html:736
+#, python-format
+msgid ""
+"Defined in the Tunnel Message "
+"Specification.\n"
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/configuration.html:2
+msgid "Configuration File Specification"
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/configuration.html:7
+msgid ""
+"This page provides a general specification of I2P configuration files,\n"
+"used by the router and various applications.\n"
+"It also gives an overview of the information contained in the various "
+"files,\n"
+"and links to detailed documentation where available."
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/configuration.html:15
+msgid "General Format"
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/configuration.html:16
+#, python-format
+msgid ""
+"An I2P configuration file is formatted as specified in\n"
+"Java Properties\n"
+"with the following exceptions:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/configuration.html:22
+msgid "Encoding must be UTF-8"
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/configuration.html:23
+msgid ""
+"Does not use or recognize any escapes, including '\\', so lines may not "
+"be continued"
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/configuration.html:24
+msgid "'#' or ';' starts a comment, but '!' does not"
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/configuration.html:25
+msgid ""
+"'#' starts a comment in any position but ';' must be in column 1 to start"
+" a comment"
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/configuration.html:26
+msgid "Leading and trailing whitespace is not trimmed on keys"
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/configuration.html:27
+msgid "Leading and trailing whitespace is trimmed on values"
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/configuration.html:28
+msgid "'=' is the only key-termination character (not ':' or whitespace)"
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/configuration.html:29
+msgid ""
+"Lines without '=' are ignored. It does not store the key with a value of "
+"\"\""
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/configuration.html:30
+msgid ""
+"As there are no escapes, keys may not contain '#', '=', or '\n"
+"', or start with ';'"
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/configuration.html:31
+msgid ""
+"As there are no escapes, values may not contain '#' or '\n"
+"', or start or end with '\r"
+"' or whitespace"
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/configuration.html:34
+msgid ""
+"The file need not be sorted, but most applications do sort by key when\n"
+"writing to the file, for ease of reading and manual editing."
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/configuration.html:39
+#, python-format
+msgid ""
+"Reads and writes are implemented in\n"
+"DataHelper loadProps() and storeProps().\n"
+"Note that the file format is significantly different than the\n"
+"serialized format for I2P protocols specified in\n"
+"Mapping."
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/configuration.html:48
+msgid "Core library and router"
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/configuration.html:50
+msgid "Clients"
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/configuration.html:51
+msgid "Configured via /configclients in the router console."
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/configuration.html:55
+msgid "Logger"
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/configuration.html:56
+msgid "Configured via /configlogging in the router console."
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/configuration.html:60
+msgid "Individual Plugin"
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/configuration.html:61
+#, python-format
+msgid "See the plugin specification."
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/configuration.html:66
+msgid "Enable/disable for each installed plugin."
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/configuration.html:70
+msgid "Router"
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/configuration.html:71
+msgid "Configured via /configadvanced in the router console."
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/configuration.html:75
+msgid "Applications"
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/configuration.html:78
+msgid "See documentation in SusiDNS."
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/configuration.html:83
+msgid "Configured via the application gui."
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/configuration.html:88
+msgid "Configured via the /i2ptunnel application in the router console."
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/configuration.html:92
+msgid "Router Console"
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/configuration.html:93
+msgid "The router console uses the router.config file."
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/configuration.html:98
+msgid "See post on zzz.i2p."
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/datagrams.html:2
+msgid "Datagram Specification"
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/datagrams.html:6
+msgid "See the Datagrams page for an overview of the Datagrams API."
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/datagrams.html:12
+msgid "Non-Repliable Datagrams"
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/datagrams.html:13
+msgid ""
+"Non-repliable datagrams have no 'from' address and are not authenticated."
+"\n"
+"They are also called \"raw\" datagrams.\n"
+"Strictly speaking, they are not \"datagrams\" at all, they are just raw "
+"data.\n"
+"They are not handled by the datagram API.\n"
+"However, SAM and the I2PTunnel classes support \"raw datagrams\"."
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/datagrams.html:21
+msgid "Format"
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/datagrams.html:31
+#, python-format
+msgid ""
+"The practical length is limited by lower layers of protocols - the\n"
+"tunnel message spec\n"
+"limits messages to about 61.2 KB and the\n"
+"transports\n"
+"currently limit messages to about 32 KB, although this may be raised in "
+"the future."
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/datagrams.html:40
+msgid "Repliable Datagrams"
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/datagrams.html:41
+msgid ""
+"Repliable datagrams contain a 'from' address and a signature. These add "
+"427 bytes of overhead."
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/datagrams.html:91
+#, python-format
+msgid ""
+"The practical length is limited by lower layers of protocols - the\n"
+"transports\n"
+"currently limit messages to about 32 KB, so the data length here is "
+"limited to about\n"
+"31.5 KB."
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/datagrams.html:97
+msgid "See important notes above about the reliability of large datagrams."
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/geoip.html:2
+msgid "GeoIP File Specification"
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/geoip.html:8
+msgid ""
+"This page specifies the format of the various GeoIP files,\n"
+"used by the router to look up a country for an IP."
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/geoip.html:14
+msgid "Country Name (countries.txt) Format"
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/geoip.html:15
+msgid ""
+"This format is easily generated from data files available from many "
+"public sources.\n"
+"For example:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/geoip.html:33
+msgid "IPv4 (geoip.txt) Format"
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/geoip.html:34
+msgid ""
+"This format is borrowed from Tor and is easily generated from data files "
+"available from many public sources.\n"
+"For example:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/geoip.html:54
+msgid "IPv6 (geoipv6.dat.gz) Format"
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/geoip.html:55
+msgid ""
+"This is a compressed binary format designed for I2P.\n"
+"The file is gzipped. Ungzipped format:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/geoip.html:71
+msgid "NOTES:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/streaming.html:2
+msgid "Streaming Library Specification"
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/streaming.html:6
+msgid "See the Streaming page for an overview of the Streaming Library."
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/streaming.html:11
+msgid "Packet Format"
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/streaming.html:12
+msgid "The format of a single packet in the streaming protocol is:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/streaming.html:35
+msgid "Length"
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/streaming.html:83
+msgid "Flags and Option Data Fields"
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/streaming.html:84
+msgid ""
+"The flags field above specifies some metadata about the packet, and in\n"
+"turn may require certain additional data to be included. The flags are\n"
+"as follows. Any data structures specified must be added to the options "
+"area\n"
+"in the given order."
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/updates.html:2
+msgid "I2P Software Update Specification"
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/updates.html:7
+msgid ""
+"I2P uses a simple, yet secure, system for automated software update.\n"
+"The router console periodically pulls a news file from a configurable I2P"
+" URL.\n"
+"There is a hardcoded backup URL pointing to the project website, in case\n"
+"the default project news host goes down."
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/updates.html:14
+msgid ""
+"The contents of the news file are displayed on the home page of the "
+"router console.\n"
+"In addition, the news file contains the most recent version number of the"
+" software.\n"
+"If the version is higher than the router's version number, it will\n"
+"display an indication to the user that an update is available."
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/updates.html:21
+msgid ""
+"The router may optionally download, or download and install, the new "
+"version\n"
+"if configured to do so."
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/updates.html:26
+msgid "News File Specification"
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/updates.html:27
+msgid "The news.xml file may contain the following elements:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/updates.html:35
+msgid ""
+"Parameters in the i2p.release entry are as follows.\n"
+"All keys are case-insensitive. All values must be enclosed in double "
+"quotes."
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/updates.html:73
+msgid ""
+"The elements may be included inside XML comments to prevent "
+"interpretation by browsers.\n"
+"The i2p.release element and version are required. All others are "
+"optional.\n"
+"NOTE: Due to parser limitations an entire element must be on a single "
+"line."
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/updates.html:80
+msgid "Update File Specification"
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/updates.html:81
+msgid ""
+"As of release 0.9.9, the signed update file, named i2pupdate.su3, will\n"
+"use the \"su3\" file format specified below.\n"
+"Approved release signers will use 4096-bit RSA keys.\n"
+"The X.509 public key certificates for these signers are distributed in "
+"the router installation packages.\n"
+"The updates may contain certificates for new, approved signers, and/or "
+"contain\n"
+"a list of certificates to delete for revocation."
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/updates.html:91
+msgid "Old Update File Specification"
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/updates.html:92
+msgid "This format is obsolte as of release 0.9.9."
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/updates.html:95
+msgid ""
+"The signed update file, traditionally named i2pupdate.sud,\n"
+"is simply a zip file with a prepended 56 byte header.\n"
+"The header contains:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/updates.html:101
+#, python-format
+msgid ""
+"A 40-byte DSA "
+"signature"
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/updates.html:104
+msgid "A 16-byte I2P version in UTF-8, padded with trailing zeroes if necessary"
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/updates.html:109
+#, python-format
+msgid ""
+"The signature covers only the zip archive - not the prepended version.\n"
+"The signature must match one of the DSA public keys "
+"configured into the router,\n"
+"which has a hardcoded default list of keys of the current project release"
+" managers."
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/updates.html:115
+msgid ""
+"For version comparison purposes, version fields contain [0-9]*, field "
+"separators are\n"
+"'-', '_', and '.', and all other characters are ignored."
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/updates.html:120
+msgid ""
+"As of version 0.8.8, the version must also be specified as a zip file "
+"comment in UTF-8,\n"
+"without the trailing zeroes.\n"
+"The updating router verifes that the version in the header (not covered "
+"by the signature)\n"
+"matches the version in the zip file comment, which is covered by the "
+"signature.\n"
+"This prevents spoofing of the version number in the header."
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/updates.html:128
+msgid "Download and Installation"
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/updates.html:129
+msgid ""
+"The router first downloads the header of the update file from one in a "
+"configurable list of I2P URLs,\n"
+"using the built-in HTTP client and proxy,\n"
+"and checks that the version is newer.\n"
+"This prevents the problem of update hosts that do not have the latest "
+"file.\n"
+"The router then downloads the full update file.\n"
+"The router verifies that the update file version is newer before "
+"installation.\n"
+"It also, of course, verifies the signature, and\n"
+"verifes that the zip file comment matches the header version, as "
+"explained above."
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/updates.html:140
+msgid "The zip file is extracted in the base $I2P installation directory."
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/updates.html:144
+msgid ""
+"As of release 0.7.12, the router supports Pack200 decompression.\n"
+"Files inside the zip archive with a .jar.pack or .war.pack suffix\n"
+"are transparently decompressed to a .jar or .war file.\n"
+"Update files containing .pack files are traditionally named with a '.su2'"
+" suffix.\n"
+"Pack200 shrinks the update files by about 60%."
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/updates.html:152
+msgid ""
+"As of release 0.8.7, the router will delete the libjbigi.so and "
+"libjcpuid.so files\n"
+"if the zip archive contains a lib/jbigi.jar file, so that the new files "
+"will\n"
+"be extracted from jbigi.jar."
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/updates.html:158
+msgid ""
+"As of release 0.8.12, if the zip archive contains a file deletelist.txt, "
+"the router will\n"
+"delete the files listed there. The format is:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/updates.html:163
+msgid "One file name per line"
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/updates.html:164
+msgid ""
+"All file names are relative to the installation directory; no absolute "
+"file names allowed, no files starting with \"..\""
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/updates.html:165
+msgid "Comments start with '#'"
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/updates.html:168
+msgid "The router will then delete the deletelist.txt file."
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/updates.html:173
+msgid "New \"su3\" Update File Specification"
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/updates.html:175
+msgid ""
+"This specification is used for router updates and reseed data as of "
+"release 0.9.9."
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/updates.html:179
+msgid "Issues with the previous .sud/.su2 format:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/updates.html:181
+msgid "No magic number or flags"
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/updates.html:184
+msgid "No way to specify compression, pack200 or not, or signing algo"
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/updates.html:187
+msgid ""
+"Version is not covered by signature, so it is enforced by requiring it\n"
+"to be in the zip file comment (for router files) or in the plugin.config\n"
+"file (for plugins)"
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/updates.html:192
+msgid "Signer not specified so verifier must try all known keys"
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/updates.html:195
+msgid "Signature-before-data format requires two passes to generate file"
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/updates.html:201
+msgid "Goals:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/updates.html:204
+msgid "Fix above problems"
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/updates.html:207
+msgid "Migrate to more secure signature algorithm"
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/updates.html:210
+msgid ""
+"Keep version info in same format and offset for compatibility with\n"
+"existing version checkers"
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/updates.html:216
+msgid "Specification:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/updates.html:275
+msgid "All unused fields must be set to 0 for compatibility with future versions."
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/updates.html:282
+msgid ""
+"The network will eventually grow too large for update over HTTP.\n"
+"The built-in BitTorrent client, i2psnark, may be used as a distributed "
+"update method.\n"
+"This development effort is ongoing and should be completed by late 2013."
+msgstr ""
+
+#: i2p2www/pages/site/docs/spec/updates.html:287
+msgid ""
+"The router update mechanism is part of the web router console.\n"
+"There is currently no provision for updates of an embedded router lacking"
+" the router console."
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/index.html:2
+msgid "Transport Overview"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/index.html:3
+msgid "April 2013"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/index.html:6
+msgid "Transports in I2P"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/index.html:8
+msgid ""
+"A \"transport\" in I2P is a method for direct, point-to-point "
+"communication\n"
+"between two routers.\n"
+"Transports must provide confidentiality and integrity \n"
+"against external adversaries while authenticating that the router "
+"contacted \n"
+"is the one who should receive a given message."
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/index.html:16
+msgid ""
+"I2P supports multiple transports simultaneously.\n"
+"There are two transports currently implemented:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/index.html:21
+#, python-format
+msgid "NTCP, a Java New I/O (NIO) TCP transport"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/index.html:22
+#, python-format
+msgid " SSU, or Secure Semireliable UDP"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/index.html:25
+msgid ""
+"Each provides a \"connection\" paradigm, with authentication,\n"
+"flow control, acknowledgments and retransmission."
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/index.html:31
+msgid "Transport Services"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/index.html:33
+msgid "The transport subsystem in I2P provides the following services:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/index.html:37
+msgid ""
+"Maintain a set of router addresses, one or more for each transport,\n"
+"that the router publishes as its global contact information (the "
+"RouterInfo)"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/index.html:41
+msgid "Selection of the best transport for each outgoing message"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/index.html:42
+msgid "Queueing of outbound messages by priority"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/index.html:43
+msgid ""
+"Bandwidth limiting, both outbound and inbound, according to router "
+"configuration"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/index.html:44
+msgid "Setup and teardown of transport connections"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/index.html:45
+msgid "Encryption of point-to-point communications"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/index.html:46
+msgid ""
+"Maintenance of connection limits for each transport, implementation of "
+"various thresholds for these limits,\n"
+"and communication of threshold status to the router so it may make "
+"operational changes based on the status"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/index.html:50
+msgid "Firewall port opening using UPnP (Universal Plug and Play)"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/index.html:51
+msgid "Cooperative NAT/Firewall traversal"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/index.html:52
+msgid ""
+"Local IP detection by various methods, including UPnP, inspection of "
+"incoming connections, and enumeration of network devices"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/index.html:53
+msgid ""
+"Coordination of firewall status and local IP, and changes to either, "
+"among the transports"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/index.html:54
+#: i2p2www/pages/site/docs/transport/ssu.html:32
+msgid ""
+"Communication of firewall status and local IP, and changes to either, to "
+"the router and the user interface"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/index.html:55
+msgid ""
+"Determination of a consensus clock, which is used to periodically update "
+"the router's clock, as a backup for NTP"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/index.html:56
+msgid ""
+"Maintenance of status for each peer, including whether it is connected, "
+"whether it was recently connected,\n"
+"and whether it was reachable in the last attempt"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/index.html:60
+msgid "Qualification of valid IP addresses according to a local rule set"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/index.html:61
+msgid ""
+"Honoring the automated and manual lists of banned peers maintained by the"
+" router,\n"
+"and refusing outbound and inbound connections to those peers"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/index.html:68
+msgid "Transport Addresses"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/index.html:70
+msgid ""
+"The transport subsystem maintains a set of router addresses, each of "
+"which lists a transport method, IP, and port.\n"
+"These addresses constitute the advertised contact points, and are "
+"published by the router to the network database."
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/index.html:75
+msgid "Typical scenarios are:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/index.html:77
+msgid ""
+"A router has no published addresses, so it is considered \"hidden\" and "
+"cannot receive incoming connections"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/index.html:78
+#, python-format
+msgid ""
+"A router is firewalled, and therefore publishes an SSU address which "
+"contains a list of cooperating\n"
+"peers or \"introducers\" who will assist in NAT traversal (see the SSU spec for details)"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/index.html:82
+msgid ""
+"A router is not firewalled or its NAT ports are open; it publishes both "
+"NTCP and SSU addresses containing\n"
+"directly-accessible IP and ports."
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/index.html:88
+msgid "Transport Selection"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/index.html:90
+#, python-format
+msgid ""
+"The transport system delivers I2NP messages. The"
+" transport selected for any message is\n"
+"independent of the upper-layer protocols and contents (router or client "
+"messages, whether an external application was using\n"
+"TCP or UDP to connect to I2P, whether the upper layer was using\n"
+"the streaming library\n"
+"streaming\n"
+"or\n"
+"datagrams,\n"
+"datagrams\n"
+"etc.)."
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/index.html:104
+msgid ""
+"For each outgoing message, the transport system solicits \"bids\" from "
+"each transport.\n"
+"The transport bidding the lowest (best) value wins the bid and receives "
+"the message for delivery.\n"
+"A transport may refuse to bid."
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/index.html:110
+msgid "Whether a transport bids, and with what value, depend on numerous factors:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/index.html:114
+msgid "Configuration of transport preferences"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/index.html:115
+msgid "Whether the transport is already connected to the peer"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/index.html:116
+msgid ""
+"The number of current connections compared to various connection limit "
+"thresholds"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/index.html:117
+msgid "Whether recent connection attempts to the peer have failed"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/index.html:118
+msgid ""
+"The size of the message, as different transports have different size "
+"limits"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/index.html:119
+msgid ""
+"Whether the peer can accept incoming connections for that transport, as "
+"advertised in its RouterInfo"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/index.html:120
+msgid "Whether the connection would be indirect (requiring introducers) or direct"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/index.html:121
+msgid "The peer's transport preference, as advertised in its RouterInfo"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/index.html:124
+msgid ""
+"In general, the bid values are selected so that two routers are only "
+"connected by a single transport\n"
+"at any one time. However, this is not a requirement."
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/index.html:131
+msgid "New Transports and Future Work"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/index.html:133
+msgid "Additional transports may be developed, including:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/index.html:138
+msgid "A TLS/SSH look-alike transport"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/index.html:139
+msgid ""
+"An \"indirect\" transport for routers that are not reachable by all other"
+" routers (one form of \"restricted routes\")"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/index.html:142
+#, python-format
+msgid ""
+"IPv6: The existing transports must be enhanced to support multiple "
+"addresses within a single transport,\n"
+"including IPV6 addresses. Currently, a transport may only advertise a "
+"single IPV4 address.\n"
+"See this thread for discussion."
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/index.html:148
+msgid ""
+"Work continues on adjusting default connection limits for each transport."
+"\n"
+"I2P is designed as a \"mesh network\", where it is assumed that any "
+"router can connect to any other router.\n"
+"This assumption may be broken by routers that have exceeded their "
+"connection limits, and by\n"
+"routers that are behind restrictive state firewalls (restricted routes)."
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/index.html:155
+msgid ""
+"The current connection limits are higher for SSU than for NTCP, based on "
+"the assumption that\n"
+"the memory requirements for an NTCP connection are higher than that for "
+"SSU.\n"
+"However, as NTCP buffers are partially in the kernel and SSU buffers are "
+"on the Java heap,\n"
+"that assumption is difficult to verify."
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/index.html:162
+#, python-format
+msgid ""
+"Analyze Breaking and Improving Protocol "
+"Obfuscation\n"
+"and see how transport-layer padding may improve things."
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:6
+msgid "NTCP (NIO-based TCP)"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:8
+#, python-format
+msgid ""
+"NTCP is one of two transports currently "
+"implemented in I2P.\n"
+"The other is SSU.\n"
+"NTCP is a Java NIO-based transport introduced in I2P release 0.6.1.22.\n"
+"Java NIO (new I/O) does not suffer from the 1 thread per connection "
+"issues of the old TCP transport."
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:15
+msgid ""
+"By default, NTCP uses the IP/Port\n"
+"auto-detected by SSU. When enabled on config.jsp,\n"
+"SSU will notify/restart NTCP when the external address changes\n"
+"or when the firewall status changes.\n"
+"Now you can enable inbound TCP without a static IP or dyndns service."
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:23
+msgid ""
+"The NTCP code within I2P is relatively lightweight (1/4 the size of the "
+"SSU code)\n"
+"because it uses the underlying Java TCP transport for reliable delivery."
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:29
+msgid "NTCP Protocol Specification"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:31
+msgid "Standard Message Format"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:32
+msgid ""
+"After establishment,\n"
+"the NTCP transport sends individual I2NP messages, with a simple "
+"checksum.\n"
+"The unencrypted message is encoded as follows:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:42
+msgid ""
+"The data is then AES/256/CBC encrypted. The session key for the "
+"encryption\n"
+"is negotiated during establishment (using Diffie-Hellman 2048 bit).\n"
+"The establishment between two routers is implemented in the "
+"EstablishState class\n"
+"and detailed below.\n"
+"The IV for AES/256/CBC encryption is the last 16 bytes of the previous "
+"encrypted message."
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:50
+msgid ""
+"0-15 bytes of padding are required to bring the total message length\n"
+"(including the six size and checksum bytes) to a multiple of 16.\n"
+"The maximum message size is currently 16 KB.\n"
+"Therefore the maximum data size is currently 16 KB - 6, or 16378 bytes.\n"
+"The minimum data size is 1."
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:58
+msgid "Time Sync Message Format"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:59
+msgid ""
+"One special case is a metadata message where the sizeof(data) is 0. In\n"
+"that case, the unencrypted message is encoded as:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:70
+msgid ""
+"Total length: 16 bytes. The time sync message is sent at approximately 15"
+" minute intervals.\n"
+"The message is encrypted just as standard messages are."
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:76
+msgid "Checksums"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:77
+#, python-format
+msgid ""
+"The standard and time sync messages use the Adler-32 checksum\n"
+"as defined in the ZLIB Specification."
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:83
+msgid "Establishment Sequence"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:84
+msgid ""
+"In the establish state, there is a 4-phase message sequence to exchange "
+"DH keys and signatures.\n"
+"In the first two messages there is a 2048-bit Diffie Hellman exchange.\n"
+"Then, DSA signatures of the critical data are exchanged to confirm the "
+"connection."
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:98
+msgid "Legend:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:99
+msgid "256 byte DH public keys"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:103
+msgid "timestamps (4 bytes, seconds since epoch)"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:104
+msgid "32 byte Session key"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:105
+msgid "2 byte size of Alice identity to follow"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:108
+msgid "DH Key Exchange"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:109
+#, python-format
+msgid ""
+"The initial 2048-bit DH key exchange\n"
+"uses the same shared prime (p) and generator (g) as that used for I2P's\n"
+"ElGamal encryption."
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:115
+msgid ""
+"The DH key exchange consists of a number of steps, displayed below.\n"
+"The mapping between these steps and the messages sent between I2P "
+"routers,\n"
+"is marked in bold."
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:121
+msgid ""
+"Alice generates a secret 226-bit integer x. She then calculates X ="
+" g^x mod p."
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:122
+msgid "Alice sends X to Bob (Message 1)."
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:123
+msgid ""
+"Bob generates a secret 226-bit integer y. He then calculates Y = "
+"g^y mod p."
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:124
+msgid "Bob sends Y to Alice.(Message 2)"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:125
+msgid "Alice can now compute sessionKey = Y^x mod p."
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:126
+msgid "Bob can now compute sessionKey = X^y mod p."
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:127
+msgid ""
+"Both Alice and Bob now have a shared key sessionKey = g^(x*y) mod "
+"p."
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:129
+msgid ""
+"The sessionKey is then used to exchange identities in Message 3 "
+"and Message 4."
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:133
+msgid "Message 1 (Session Request)"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:134
+#, python-format
+msgid ""
+"This is the DH request. Alice already has Bob's\n"
+"Router "
+"Identity,\n"
+"IP address, and port, as contained in his\n"
+"Router Info,\n"
+"which was published to the\n"
+"network database.\n"
+"Alice sends Bob:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:147
+#: i2p2www/pages/site/docs/transport/ntcp.html:190
+#: i2p2www/pages/site/docs/transport/ntcp.html:270
+#: i2p2www/pages/site/docs/transport/ntcp.html:353
+msgid "Size:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:149
+msgid "Contents:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:167
+msgid "256 byte X from Diffie Hellman"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:169
+#, python-format
+msgid ""
+"SHA256 Hash(X) xored with SHA256 Hash(Bob's Router Identity)"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:176
+#: i2p2www/pages/site/docs/transport/ntcp.html:257
+#: i2p2www/pages/site/docs/transport/ntcp.html:334
+msgid "Notes:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:177
+msgid ""
+"Bob verifies HXxorHI using his own router hash. If it does not verify,\n"
+"Alice has contacted the wrong router, and Bob drops the connection."
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:183
+msgid "Message 2 (Session Created)"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:184
+msgid "This is the DH reply. Bob sends Alice:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:192
+#: i2p2www/pages/site/docs/transport/ntcp.html:272
+#: i2p2www/pages/site/docs/transport/ntcp.html:355
+msgid "Unencrypted Contents:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:214
+#: i2p2www/pages/site/docs/transport/ntcp.html:248
+msgid "256 byte Y from Diffie Hellman"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:216
+msgid "SHA256 Hash(X concatenated with Y)"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:219
+#: i2p2www/pages/site/docs/transport/ntcp.html:304
+msgid "4 byte timestamp (seconds since the epoch)"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:221
+msgid "12 bytes random data"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:226
+#: i2p2www/pages/site/docs/transport/ntcp.html:316
+#: i2p2www/pages/site/docs/transport/ntcp.html:383
+msgid "Encrypted Contents:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:250
+#, python-format
+msgid ""
+"48 bytes AES encrypted using the DH "
+"session key and\n"
+" the last 16 bytes of Y as the IV"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:258
+msgid ""
+"Alice may drop the connection if the clock skew with Bob is too high as "
+"calculated using tsB."
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:263
+msgid "Message 3 (Session Confirm A)"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:264
+msgid ""
+"This contains Alice's router identity, and a DSA signature of the "
+"critical data. Alice sends Bob:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:298
+msgid "2 byte size of Alice's router identity to follow (should always be 387)"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:300
+#, python-format
+msgid ""
+"Alice's 387 byte Router Identity"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:306
+msgid "15 bytes random data"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:308
+#, python-format
+msgid ""
+"the 40 byte DSA "
+"signature of the following concatenated data:\n"
+" X, Y, Bob's Router Identity, "
+"tsA, tsB.\n"
+" Alice signs it with the private signing "
+"key associated with the public signing "
+"key in her Router Identity"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:326
+#, python-format
+msgid ""
+"448 bytes AES encrypted using the DH"
+" session key and\n"
+" the last 16 bytes of HXxorHI (i.e., the last 16 bytes "
+"of message #1) as the IV"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:336
+msgid "Bob verifies the signature, and on failure, drops the connection."
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:339
+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:346
+msgid "Message 4 (Session Confirm B)"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:347
+msgid "This is a DSA signature of the critical data. Bob sends Alice:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:372
+#, python-format
+msgid ""
+"the 40 byte DSA "
+"signature of the following concatenated data:\n"
+" X, Y, Alice's Router Identity, "
+"tsA, tsB.\n"
+" Bob signs it with the private signing "
+"key associated with the public signing "
+"key in his Router Identity"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:378
+msgid "8 bytes random data"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:393
+#, python-format
+msgid ""
+"48 bytes AES encrypted using the DH "
+"session key and\n"
+" the last 16 bytes of the encrypted contents of message "
+"#2 as the IV"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:401
+msgid "Alice verifies the signature, and on failure, drops the connection."
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:408
+msgid "After Establishment"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:409
+msgid ""
+"The connection is established, and standard or time sync messages may be "
+"exchanged.\n"
+"All subsequent messages are AES encrypted using the negotiated DH session"
+" key.\n"
+"Alice will use the last 16 bytes of the encrypted contents of message #3 "
+"as the next IV.\n"
+"Bob will use the last 16 bytes of the encrypted contents of message #4 as"
+" the next IV."
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:418
+msgid "Check Connection Message"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:419
+msgid ""
+"Alternately, when Bob receives a connection, it could be a\n"
+"check connection (perhaps prompted by Bob asking for someone\n"
+"to verify his listener).\n"
+"Check Connection is not currently used.\n"
+"However, for the record, check connections are formatted as follows.\n"
+"A check info connection will receive 256 bytes containing:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:428
+msgid "32 bytes of uninterpreted, ignored data"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:429
+msgid "1 byte size"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:430
+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:431
+msgid "2 byte port number that the local router was reached on"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:432
+msgid ""
+"4 byte i2p network time as known by the remote side (seconds since the "
+"epoch)"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:433
+msgid "uninterpreted padding data, up to byte 223"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:434
+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:438
+msgid "Discussion"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:439
+#, python-format
+msgid "Now on the NTCP Discussion Page."
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:445
+msgid "The maximum message size should be increased to approximately 32 KB."
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:449
+msgid ""
+"A set of fixed packet sizes may be appropriate to further hide the data \n"
+"fragmentation to external adversaries, but the tunnel, garlic, and end to"
+" \n"
+"end padding should be sufficient for most needs until then.\n"
+"However, there is currently no provision for padding beyond the next "
+"16-byte boundary,\n"
+"to create a limited number of message sizes."
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:457
+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:461
+msgid ""
+"Can the establishment messages be randomly padded somehow, to frustrate\n"
+"identification of I2P traffic based on initial packet sizes?"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:466
+msgid "Review and possibly disable 'check connection'"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ssu.html:2
+msgid "SSU Transport"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ssu.html:6
+msgid "Secure Semireliable UDP"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ssu.html:9
+#, python-format
+msgid ""
+"SSU (also called \"UDP\" in much of the I2P documentation and user "
+"interfaces)\n"
+"is one of two transports currently "
+"implemented in I2P.\n"
+"The other is NTCP."
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ssu.html:15
+msgid ""
+"SSU is the newer of the two transports,\n"
+"introduced in I2P release 0.6.\n"
+"In a standard I2P installation, the router uses both NTCP and SSU for "
+"outbound connections."
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ssu.html:21
+msgid "SSU Services"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ssu.html:23
+msgid ""
+"Like the NTCP transport, SSU provides reliable, encrypted, connection-"
+"oriented, point-to-point data transport.\n"
+"Unique to SSU, it also provides IP detection and NAT traversal services, "
+"including:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ssu.html:29
+msgid ""
+"Cooperative NAT/Firewall traversal using introducers"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ssu.html:30
+msgid ""
+"Local IP detection by inspection of incoming packets and peer testing"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ssu.html:31
+msgid ""
+"Communication of firewall status and local IP, and changes to either to "
+"NTCP"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ssu.html:36
+msgid "Protocol Details"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ssu.html:38
+msgid "Congestion control"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ssu.html:40
+msgid ""
+"SSU's need for only semireliable delivery, TCP-friendly operation,\n"
+"and the capacity for high throughput allows a great deal of latitude in\n"
+"congestion control. The congestion control algorithm outlined below is\n"
+"meant to be both efficient in bandwidth as well as simple to implement."
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ssu.html:47
+msgid ""
+"Packets are scheduled according to the router's policy, taking care\n"
+"not to exceed the router's outbound capacity or to exceed the measured \n"
+"capacity of the remote peer. The measured capacity operates along the\n"
+"lines of TCP's slow start and congestion avoidance, with additive "
+"increases\n"
+"to the sending capacity and multiplicative decreases in face of "
+"congestion.\n"
+"Unlike for TCP, routers may give up on some messages after\n"
+"a given period or number of retransmissions while continuing to transmit"
+" \n"
+"other messages."
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ssu.html:58
+msgid ""
+"The congestion detection techniques vary from TCP as well, since each \n"
+"message has its own unique and nonsequential identifier, and each message"
+"\n"
+"has a limited size - at most, 32KB. To efficiently transmit this "
+"feedback\n"
+"to the sender, the receiver periodically includes a list of fully ACKed \n"
+"message identifiers and may also include bitfields for partially received"
+"\n"
+"messages, where each bit represents the reception of a fragment. If \n"
+"duplicate fragments arrive, the message should be ACKed again, or if the\n"
+"message has still not been fully received, the bitfield should be \n"
+"retransmitted with any new updates."
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ssu.html:70
+msgid ""
+"The current implementation does not pad the packets to\n"
+"any particular size, but instead just places a single message fragment "
+"into\n"
+"a packet and sends it off (careful not to exceed the MTU)."
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ssu.html:77
+msgid ""
+"As of router version 0.8.12,\n"
+"two MTU values are used for IPv4: 620 and 1484.\n"
+"The MTU value is adjusted based on the percentage of packets that are "
+"retransmitted."
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ssu.html:83
+msgid ""
+"For both MTU values, it is desirable that (MTU % 16) == 12, so that\n"
+"the payload portion after the 28-byte IP/UDP header is a multiple of\n"
+"16 bytes, for encryption purposes."
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ssu.html:89
+msgid ""
+"For the small MTU value, it is desirable to pack a 2646-byte\n"
+"Variable Tunnel Build Message efficiently into multiple packets;\n"
+"with a 620-byte MTU, it fits into 5 packets with nicely."
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ssu.html:95
+msgid ""
+"Based on measurements, 1492 fits nearly all reasonably small I2NP "
+"messages\n"
+"(larger I2NP messages may be up to 1900 to 4500 bytes, which isn't going "
+"to fit\n"
+"into a live network MTU anyway)."
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ssu.html:101
+msgid ""
+"The MTU values were 608 and 1492 for releases 0.8.9 - 0.8.11.\n"
+"The large MTU was 1350 prior to release 0.8.9."
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ssu.html:106
+msgid ""
+"The maximum receive packet size\n"
+"is 1571 bytes as of release 0.8.12.\n"
+"For releases 0.8.9 - 0.8.11 it was 1535 bytes.\n"
+"Prior to release 0.8.9 it was 2048 bytes."
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ssu.html:113
+msgid ""
+"As of release 0.9.2, if a router's network interface MTU is less than "
+"1484,\n"
+"it will publish that in the network database, and other routers should\n"
+"honor that when a connection is established."
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ssu.html:119
+msgid ""
+"For IPv6, the minimum MTU is 1280. The IPv6 IP/UDP header is 48 bytes,\n"
+"so we use an MTU where (MTN % 16 == 0), which is true for 1280."
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ssu.html:124
+msgid "Message Size Limits"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ssu.html:125
+msgid ""
+"While the maximum message size is nominally 32KB, the practical\n"
+"limit differs. The protocol limits the number of fragments to 7 bits, or "
+"128.\n"
+"The current implementation, however, limits each message to a maximum of "
+"64 fragments,\n"
+"which is sufficient for 64 * 534 = 33.3 KB when using the 608 MTU.\n"
+"Due to overhead for bundled LeaseSets and session keys, the practical "
+"limit\n"
+"at the application level is about 6KB lower, or about 26KB.\n"
+"Further work is necessary to raise the UDP transport limit above 32KB.\n"
+"For connections using the larger MTU, larger messages are possible."
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ssu.html:136
+msgid "Keys"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ssu.html:138
+msgid ""
+"All encryption used is AES256/CBC with 32 byte keys and 16 byte IVs.\n"
+"The MAC and session keys are negotiated as part of the DH exchange, used\n"
+"for the HMAC and encryption, respectively. Prior to the DH exchange, \n"
+"the publicly knowable introKey is used for the MAC and encryption."
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ssu.html:145
+msgid ""
+"When using the introKey, both the initial message and any subsequent\n"
+"reply use the introKey of the responder (Bob) - the responder does \n"
+"not need to know the introKey of the requester (Alice). The DSA \n"
+"signing key used by Bob should already be known to Alice when she \n"
+"contacts him, though Alice's DSA key may not already be known by \n"
+"Bob."
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ssu.html:154
+msgid ""
+"Upon receiving a message, the receiver checks the \"from\" IP address and"
+" port\n"
+"with all established sessions - if there are matches,\n"
+"that session's MAC keys are tested in the HMAC. If none\n"
+"of those verify or if there are no matching IP addresses, the \n"
+"receiver tries their introKey in the MAC. If that does not verify,\n"
+"the packet is dropped. If it does verify, it is interpreted \n"
+"according to the message type, though if the receiver is overloaded,\n"
+"it may be dropped anyway."
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ssu.html:165
+msgid ""
+"If Alice and Bob have an established session, but Alice loses the \n"
+"keys for some reason and she wants to contact Bob, she may at any \n"
+"time simply establish a new session through the SessionRequest and\n"
+"related messages. If Bob has lost the key but Alice does not know\n"
+"that, she will first attempt to prod him to reply, by sending a \n"
+"DataMessage with the wantReply flag set, and if Bob continually \n"
+"fails to reply, she will assume the key is lost and reestablish a \n"
+"new one."
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ssu.html:176
+#, python-format
+msgid ""
+"For the DH key agreement,\n"
+"RFC3526 2048bit\n"
+"MODP group (#14) is used:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ssu.html:186
+#, python-format
+msgid ""
+"These are the same p and g used for I2P's\n"
+"ElGamal encryption."
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ssu.html:191
+msgid "Replay prevention"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ssu.html:193
+msgid ""
+"Replay prevention at the SSU layer occurs by rejecting packets \n"
+"with exceedingly old timestamps or those which reuse an IV. To\n"
+"detect duplicate IVs, a sequence of Bloom filters are employed to\n"
+"\"decay\" periodically so that only recently added IVs are detected."
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ssu.html:200
+msgid ""
+"The messageIds used in DataMessages are defined at layers above\n"
+"the SSU transport and are passed through transparently. These IDs\n"
+"are not in any particular order - in fact, they are likely to be\n"
+"entirely random. The SSU layer makes no attempt at messageId \n"
+"replay prevention - higher layers should take that into account."
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ssu.html:208
+msgid "Addressing"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ssu.html:210
+msgid ""
+"To contact an SSU peer, one of two sets of information is necessary:\n"
+"a direct address, for when the peer is publicly reachable, or an\n"
+"indirect address, for using a third party to introduce the peer.\n"
+"There is no restriction on the number of addresses a peer may have."
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ssu.html:222
+msgid ""
+"Each of the addresses may also expose a series of options - special\n"
+"capabilities of that particular peer. For a list of available\n"
+"capabilities, see below."
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ssu.html:228
+#, python-format
+msgid ""
+"The addresses, options, and capabilities are published in the network database."
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ssu.html:233
+msgid "Direct Session Establishment"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ssu.html:234
+msgid ""
+"Direct session establishment is used when no third party is required for "
+"NAT traversal.\n"
+"The message sequence is as follows:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ssu.html:239
+msgid "Connection establishment (direct)"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ssu.html:240
+msgid "Alice connects directly to Bob."
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ssu.html:254
+#, python-format
+msgid ""
+"After the SessionConfirmed message is received, Bob sends a small\n"
+"DeliveryStatus message\n"
+"as a confirmation.\n"
+"In this message, the 4-byte message ID is set to a random number, and the"
+"\n"
+"8-byte \"arrival time\" is set to the current network-wide ID, which is 2"
+"\n"
+"(i.e. 0x0000000000000002)."
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ssu.html:263
+#, python-format
+msgid ""
+"After the status message is sent, the peers exchange\n"
+"DatabaseStore messages\n"
+"containing their\n"
+"RouterInfos."
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ssu.html:271
+msgid ""
+"It does not appear that the type of the status message or its contents "
+"matters.\n"
+"It was originally added becasue the DatabaseStore message was delayed\n"
+"several seconds; since the store is now sent immediately, perhaps\n"
+"the status message can be eliminated."
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ssu.html:280
+msgid ""
+"Introduction keys are delivered through an external channel \n"
+"(the network database, where they are identical to the router Hash for "
+"now)\n"
+"and must be used when establishing a session key. For the indirect\n"
+"address, the peer must first contact the relayhost and ask them for\n"
+"an introduction to the peer known at that relayhost under the given\n"
+"tag. If possible, the relayhost sends a message to the addressed\n"
+"peer telling them to contact the requesting peer, and also gives \n"
+"the requesting peer the IP and port on which the addressed peer is\n"
+"located. In addition, the peer establishing the connection must \n"
+"already know the public keys of the peer they are connecting to (but\n"
+"not necessary to any intermediary relay peer)."
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ssu.html:294
+msgid ""
+"Indirect session establishment by means of a third party introduction\n"
+"is necessary for efficient NAT traversal. Charlie, a router behind a\n"
+"NAT or firewall which does not allow unsolicited inbound UDP packets,\n"
+"first contacts a few peers, choosing some to serve as introducers. Each\n"
+"of these peers (Bob, Bill, Betty, etc) provide Charlie with an "
+"introduction\n"
+"tag - a 4 byte random number - which he then makes available to the "
+"public\n"
+"as methods of contacting him. Alice, a router who has Charlie's "
+"published\n"
+"contact methods, first sends a RelayRequest packet to one or more of the"
+" \n"
+"introducers, asking each to introduce her to Charlie (offering the \n"
+"introduction tag to identify Charlie). Bob then forwards a RelayIntro\n"
+"packet to Charlie including Alice's public IP and port number, then sends"
+"\n"
+"Alice back a RelayResponse packet containing Charlie's public IP and port"
+"\n"
+"number. When Charlie receives the RelayIntro packet, he sends off a "
+"small\n"
+"random packet to Alice's IP and port (poking a hole in his NAT/firewall),"
+"\n"
+"and when Alice receives Bob's RelayResponse packet, she begins a new \n"
+"full direction session establishment with the specified IP and port."
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ssu.html:321
+msgid "Connection establishment (indirect using an introducer)"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ssu.html:323
+msgid "Alice first connects to introducer Bob, who relays the request to Charlie."
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ssu.html:341
+msgid ""
+"After the hole punch, the session is established between Alice and "
+"Charlie as in a direct establishment."
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ssu.html:352
+msgid "Peer testing"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ssu.html:354
+msgid ""
+"The automation of collaborative reachability testing for peers is\n"
+"enabled by a sequence of PeerTest messages. With its proper \n"
+"execution, a peer will be able to determine their own reachability\n"
+"and may update its behavior accordingly. The testing process is \n"
+"quite simple:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ssu.html:373
+msgid ""
+"Each of the PeerTest messages carry a nonce identifying the\n"
+"test series itself, as initialized by Alice. If Alice doesn't \n"
+"get a particular message that she expects, she will retransmit\n"
+"accordingly, and based upon the data received or the messages\n"
+"missing, she will know her reachability. The various end states\n"
+"that may be reached are as follows:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ssu.html:383
+msgid ""
+"If she doesn't receive a response from Bob, she will retransmit\n"
+"up to a certain number of times, but if no response ever arrives,\n"
+"she will know that her firewall or NAT is somehow misconfigured, \n"
+"rejecting all inbound UDP packets even in direct response to an\n"
+"outbound packet. Alternately, Bob may be down or unable to get \n"
+"Charlie to reply."
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ssu.html:392
+msgid ""
+"If Alice doesn't receive a PeerTest message with the \n"
+"expected nonce from a third party (Charlie), she will retransmit\n"
+"her initial request to Bob up to a certain number of times, even\n"
+"if she has received Bob's reply already. If Charlie's first message \n"
+"still doesn't get through but Bob's does, she knows that she is\n"
+"behind a NAT or firewall that is rejecting unsolicited connection\n"
+"attempts and that port forwarding is not operating properly (the\n"
+"IP and port that Bob offered up should be forwarded)."
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ssu.html:403
+msgid ""
+"If Alice receives Bob's PeerTest message and both of Charlie's\n"
+"PeerTest messages but the enclosed IP and port numbers in Bob's \n"
+"and Charlie's second messages don't match, she knows that she is \n"
+"behind a symmetric NAT, rewriting all of her outbound packets with\n"
+"different 'from' ports for each peer contacted. She will need to\n"
+"explicitly forward a port and always have that port exposed for \n"
+"remote connectivity, ignoring further port discovery."
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ssu.html:413
+msgid ""
+"If Alice receives Charlie's first message but not his second,\n"
+"she will retransmit her PeerTest message to Charlie up to a \n"
+"certain number of times, but if no response is received she knows\n"
+"that Charlie is either confused or no longer online."
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ssu.html:421
+msgid ""
+"Alice should choose Bob arbitrarily from known peers who seem\n"
+"to be capable of participating in peer tests. Bob in turn should\n"
+"choose Charlie arbitrarily from peers that he knows who seem to be\n"
+"capable of participating in peer tests and who are on a different\n"
+"IP from both Bob and Alice. If the first error condition occurs\n"
+"(Alice doesn't get PeerTest messages from Bob), Alice may decide\n"
+"to designate a new peer as Bob and try again with a different nonce."
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ssu.html:431
+msgid ""
+"Alice's introduction key is included in all of the PeerTest \n"
+"messages so that she doesn't need to already have an established\n"
+"session with Bob and so that Charlie can contact her without knowing\n"
+"any additional information. Alice may go on to establish a session\n"
+"with either Bob or Charlie, but it is not required."
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ssu.html:449
+msgid "Transmission window, ACKs and Retransmissions"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ssu.html:450
+#, python-format
+msgid ""
+"The DATA message may contain ACKs of full messages and\n"
+"partial ACKs of individual fragments of a message. See\n"
+"the data message section of\n"
+"the protocol specification page\n"
+"for details."
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ssu.html:458
+#, python-format
+msgid ""
+"The details of windowing, ACK, and retransmission strategies are not "
+"specified\n"
+"here. See the Java code for the current implementation.\n"
+"During the establishment phase, and for peer testing, routers\n"
+"should implement exponential backoff for retransmission.\n"
+"For an established connection, routers should implement\n"
+"an adjustable transmission window, RTT estimate and timeout, similar to "
+"TCP\n"
+"or streaming.\n"
+"See the code for initial, min and max parameters."
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ssu.html:470
+msgid "Security"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ssu.html:471
+msgid ""
+"UDP source addresses may, of course, be spoofed.\n"
+"Additionally, the IPs and ports contained inside specific\n"
+"SSU messages (RelayRequest, RelayResponse, RelayIntro, PeerTest)\n"
+"may not be legitimate.\n"
+"Also, certain actions and responses may need to be rate-limited."
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ssu.html:479
+msgid ""
+"The details of validation are not specified\n"
+"here. Implementers should add defenses where appropriate."
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ssu.html:485
+msgid "Peer capabilities"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ssu.html:489
+msgid ""
+"If the peer address contains the 'B' capability, that means \n"
+"they are willing and able to participate in peer tests as\n"
+"a 'Bob' or 'Charlie'."
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ssu.html:495
+msgid ""
+"If the peer address contains the 'C' capability, that means\n"
+"they are willing and able to serve as an introducer - serving\n"
+"as a Bob for an otherwise unreachable Alice."
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ssu.html:504
+msgid ""
+"Analysis of current SSU performance, including assessment of window size "
+"adjustment\n"
+"and other parameters, and adjustment of the protocol implementation to "
+"improve\n"
+"performance, is a topic for future work."
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ssu.html:510
+msgid ""
+"The current implementation repeatedly sends acknowledgments for the same "
+"packets,\n"
+"which unnecessarily increases overhead."
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ssu.html:515
+msgid ""
+"The default small MTU value of 620 should be analyzed and possibly "
+"increased.\n"
+"The current MTU adjustment strategy should be evaluated.\n"
+"Does a streaming lib 1730-byte packet fit in 3 small SSU packets? "
+"Probably not."
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ssu.html:521
+msgid "The protocol should be extended to exchange MTUs during the setup."
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ssu.html:525
+msgid "Rekeying is currently unimplemented and may never be."
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ssu.html:529
+msgid ""
+"The potential use of the 'challenge' fields in RelayIntro and "
+"RelayResponse,\n"
+"and use of the padding field in SessionRequest and SessionCreated, is "
+"undocumented."
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ssu.html:534
+msgid ""
+"Instead of a single fragment per packet, a more efficient\n"
+"strategy may be to bundle multiple message fragments into the same "
+"packet,\n"
+"so long as it doesn't exceed the MTU."
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ssu.html:540
+msgid ""
+"A set of fixed packet sizes may be appropriate to further hide the data \n"
+"fragmentation to external adversaries, but the tunnel, garlic, and end to"
+" \n"
+"end padding should be sufficient for most needs until then."
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ssu.html:546
+msgid ""
+"Why are introduction keys the same as the router hash, should it be "
+"changed, would there be any benefit?"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ssu.html:550
+msgid "Capacities appear to be unused."
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ssu.html:554
+msgid ""
+"Signed-on times in SessionCreated and SessionConfirmed appear to be "
+"unused or unverified."
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ssu.html:559
+msgid "Implementation Diagram"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ssu.html:560
+msgid ""
+"This diagram\n"
+"should accurately reflect the current implementation, however there may "
+"be small differences."
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ssu.html:568
+msgid "Now on the SSU specification page"
+msgstr ""
+
+#: i2p2www/pages/site/docs/tunnels/implementation.html:2
+msgid "Tunnel Implementation"
+msgstr ""
+
+#: i2p2www/pages/site/docs/tunnels/implementation.html:3
+msgid "October 2010"
+msgstr ""
+
+#: i2p2www/pages/site/docs/tunnels/implementation.html:7
+msgid "This page documents the current tunnel implementation."
+msgstr ""
+
+#: i2p2www/pages/site/docs/tunnels/implementation.html:9
+msgid "Tunnel overview"
+msgstr ""
+
+#: i2p2www/pages/site/docs/tunnels/implementation.html:11
+msgid ""
+"Within I2P, messages are passed in one direction through a virtual\n"
+"tunnel of peers, using whatever means are available to pass the \n"
+"message on to the next hop. Messages arrive at the tunnel's \n"
+"gateway, get bundled up and/or fragmented into fixed-size tunnel "
+"messages, \n"
+"and are forwarded on to the next hop in the tunnel, which processes and "
+"verifies\n"
+"the validity of the message and sends it on to the next hop, and so on, "
+"until\n"
+"it reaches the tunnel endpoint. That endpoint takes the messages\n"
+"bundled up by the gateway and forwards them as instructed - either\n"
+"to another router, to another tunnel on another router, or locally."
+msgstr ""
+
+#: i2p2www/pages/site/docs/tunnels/implementation.html:23
+msgid ""
+"Tunnels all work the same, but can be segmented into two different\n"
+"groups - inbound tunnels and outbound tunnels. The inbound tunnels\n"
+"have an untrusted gateway which passes messages down towards the \n"
+"tunnel creator, which serves as the tunnel endpoint. For outbound \n"
+"tunnels, the tunnel creator serves as the gateway, passing messages\n"
+"out to the remote endpoint."
+msgstr ""
+
+#: i2p2www/pages/site/docs/tunnels/implementation.html:32
+msgid ""
+"The tunnel's creator selects exactly which peers will participate\n"
+"in the tunnel, and provides each with the necessary configuration\n"
+"data. They may have any number of hops.\n"
+"It is the intent to make\n"
+"it hard for either participants or third parties to determine the length "
+"of \n"
+"a tunnel, or even for colluding participants to determine whether they "
+"are a\n"
+"part of the same tunnel at all (barring the situation where colluding "
+"peers are\n"
+"next to each other in the tunnel)."
+msgstr ""
+
+#: i2p2www/pages/site/docs/tunnels/implementation.html:43
+msgid ""
+"In practice, a series of tunnel pools are used for different\n"
+"purposes - each local client destination has its own set of inbound\n"
+"tunnels and outbound tunnels, configured to meet its anonymity and\n"
+"performance needs. In addition, the router itself maintains a series\n"
+"of pools for participating in the network database and for managing\n"
+"the tunnels themselves."
+msgstr ""
+
+#: i2p2www/pages/site/docs/tunnels/implementation.html:52
+msgid ""
+"I2P is an inherently packet switched network, even with these \n"
+"tunnels, allowing it to take advantage of multiple tunnels running \n"
+"in parallel, increasing resilience and balancing load. Outside of\n"
+"the core I2P layer, there is an optional end to end streaming library \n"
+"available for client applications, exposing TCP-esque operation,\n"
+"including message reordering, retransmission, congestion control, etc."
+msgstr ""
+
+#: i2p2www/pages/site/docs/tunnels/implementation.html:61
+#, python-format
+msgid ""
+"An overview of I2P tunnel terminology is\n"
+"on the tunnel overview page."
+msgstr ""
+
+#: i2p2www/pages/site/docs/tunnels/implementation.html:66
+msgid "Tunnel Operation (Message Processing)"
+msgstr ""
+
+#: i2p2www/pages/site/docs/tunnels/implementation.html:69
+#, python-format
+msgid ""
+"After a tunnel is built, I2NP messages are "
+"processed and passed through it.\n"
+"Tunnel operation has four distinct processes, taken on by various \n"
+"peers in the tunnel."
+msgstr ""
+
+#: i2p2www/pages/site/docs/tunnels/implementation.html:75
+msgid ""
+"First, the tunnel gateway accumulates a number\n"
+"of I2NP messages and preprocesses them into tunnel messages for\n"
+"delivery."
+msgstr ""
+
+#: i2p2www/pages/site/docs/tunnels/implementation.html:80
+msgid ""
+"Next, that gateway encrypts that preprocessed data, then\n"
+"forwards it to the first hop."
+msgstr ""
+
+#: i2p2www/pages/site/docs/tunnels/implementation.html:84
+msgid ""
+"That peer, and subsequent tunnel \n"
+"participants, unwrap a layer of the encryption, verifying that it isn't\n"
+"a duplicate, then forward it on to the next peer."
+msgstr ""
+
+#: i2p2www/pages/site/docs/tunnels/implementation.html:89
+msgid ""
+"Eventually, the tunnel messages arrive at the endpoint where the I2NP "
+"messages\n"
+"originally bundled by the gateway are reassembled and forwarded on as \n"
+"requested."
+msgstr ""
+
+#: i2p2www/pages/site/docs/tunnels/implementation.html:96
+msgid ""
+"Intermediate tunnel participants do not know whether they are in an\n"
+"inbound or an outbound tunnel; they always \"encrypt\" for the next hop.\n"
+"Therefore, we take advantage of symmetric AES encryption\n"
+"to \"decrypt\" at the outbound tunnel gateway,\n"
+"so that the plaintext is revealed at the outbound endpoint."
+msgstr ""
+
+#: i2p2www/pages/site/docs/tunnels/implementation.html:110
+msgid "Role"
+msgstr ""
+
+#: i2p2www/pages/site/docs/tunnels/implementation.html:111
+msgid "Preprocessing"
+msgstr ""
+
+#: i2p2www/pages/site/docs/tunnels/implementation.html:112
+msgid "Encryption Operation"
+msgstr ""
+
+#: i2p2www/pages/site/docs/tunnels/implementation.html:113
+msgid "Postprocessing"
+msgstr ""
+
+#: i2p2www/pages/site/docs/tunnels/implementation.html:117
+msgid "Outbound Gateway (Creator)"
+msgstr ""
+
+#: i2p2www/pages/site/docs/tunnels/implementation.html:118
+#: i2p2www/pages/site/docs/tunnels/implementation.html:141
+msgid "Fragment, Batch, and Pad"
+msgstr ""
+
+#: i2p2www/pages/site/docs/tunnels/implementation.html:119
+msgid "Iteratively encrypt (using decryption operations)"
+msgstr ""
+
+#: i2p2www/pages/site/docs/tunnels/implementation.html:120
+#: i2p2www/pages/site/docs/tunnels/implementation.html:127
+#: i2p2www/pages/site/docs/tunnels/implementation.html:143
+#: i2p2www/pages/site/docs/tunnels/implementation.html:150
+msgid "Forward to next hop"
+msgstr ""
+
+#: i2p2www/pages/site/docs/tunnels/implementation.html:124
+#: i2p2www/pages/site/docs/tunnels/implementation.html:147
+msgid "Participant"
+msgstr ""
+
+#: i2p2www/pages/site/docs/tunnels/implementation.html:126
+msgid "Decrypt (using an encryption operation)"
+msgstr ""
+
+#: i2p2www/pages/site/docs/tunnels/implementation.html:133
+msgid "Decrypt (using an encryption operation) to reveal plaintext tunnel message"
+msgstr ""
+
+#: i2p2www/pages/site/docs/tunnels/implementation.html:134
+msgid "Reassemble Fragments, Forward as instructed to Inbound Gateway or Router"
+msgstr ""
+
+#: i2p2www/pages/site/docs/tunnels/implementation.html:142
+#: i2p2www/pages/site/docs/tunnels/implementation.html:149
+msgid "Encrypt"
+msgstr ""
+
+#: i2p2www/pages/site/docs/tunnels/implementation.html:154
+msgid "Inbound Endpoint (Creator)"
+msgstr ""
+
+#: i2p2www/pages/site/docs/tunnels/implementation.html:156
+msgid "Iteratively decrypt to reveal plaintext tunnel message"
+msgstr ""
+
+#: i2p2www/pages/site/docs/tunnels/implementation.html:157
+msgid "Reassemble Fragments, Receive data"
+msgstr ""
+
+#: i2p2www/pages/site/docs/tunnels/implementation.html:163
+msgid "Gateway Processing"
+msgstr ""
+
+#: i2p2www/pages/site/docs/tunnels/implementation.html:164
+msgid "Message Preprocessing"
+msgstr ""
+
+#: i2p2www/pages/site/docs/tunnels/implementation.html:166
+#, python-format
+msgid ""
+"A tunnel gateway's function is to fragment and pack\n"
+"I2NP messages into fixed-size\n"
+"tunnel messages\n"
+"and encrypt the tunnel messages.\n"
+"Tunnel messages contain the following:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/tunnels/implementation.html:174
+msgid "A 4 byte Tunnel ID"
+msgstr ""
+
+#: i2p2www/pages/site/docs/tunnels/implementation.html:175
+msgid "A 16 byte IV (initialization vector)"
+msgstr ""
+
+#: i2p2www/pages/site/docs/tunnels/implementation.html:176
+msgid "A checksum"
+msgstr ""
+
+#: i2p2www/pages/site/docs/tunnels/implementation.html:177
+msgid "Padding, if necessary"
+msgstr ""
+
+#: i2p2www/pages/site/docs/tunnels/implementation.html:178
+msgid "One or more { delivery instruction, I2NP message fragment } pairs"
+msgstr ""
+
+#: i2p2www/pages/site/docs/tunnels/implementation.html:181
+msgid ""
+"Tunnel IDs are 4 byte numbers used at each hop - participants know what\n"
+"tunnel ID to listen for messages with and what tunnel ID they should be "
+"forwarded\n"
+"on as to the next hop, and each hop chooses the tunnel ID which they "
+"receive messages\n"
+"on. Tunnels themselves are short-lived (10 minutes).\n"
+"Even if subsequent tunnels are built using the same sequence of \n"
+"peers, each hop's tunnel ID will change."
+msgstr ""
+
+#: i2p2www/pages/site/docs/tunnels/implementation.html:190
+msgid ""
+"To prevent adversaries from tagging the messages along the path by "
+"adjusting\n"
+"the message size, all tunnel messages are a fixed 1024 bytes in size. To"
+" accommodate \n"
+"larger I2NP messages as well as to support smaller ones more efficiently,"
+" the\n"
+"gateway splits up the larger I2NP messages into fragments contained "
+"within each\n"
+"tunnel message. The endpoint will attempt to rebuild the I2NP message "
+"from the\n"
+"fragments for a short period of time, but will discard them as necessary."
+msgstr ""
+
+#: i2p2www/pages/site/docs/tunnels/implementation.html:199
+#, python-format
+msgid ""
+"Details are in the\n"
+"tunnel message specification."
+msgstr ""
+
+#: i2p2www/pages/site/docs/tunnels/implementation.html:205
+msgid "Gateway Encryption"
+msgstr ""
+
+#: i2p2www/pages/site/docs/tunnels/implementation.html:207
+msgid ""
+"After the preprocessing of messages into a padded payload, the gateway "
+"builds\n"
+"a random 16 byte IV value, iteratively encrypting it and the tunnel "
+"message as\n"
+"necessary, and forwards the tuple {tunnelID, IV, encrypted tunnel "
+"message} to the next hop."
+msgstr ""
+
+#: i2p2www/pages/site/docs/tunnels/implementation.html:213
+msgid ""
+"How encryption at the gateway is done depends on whether the tunnel is an"
+"\n"
+"inbound or an outbound tunnel. For inbound tunnels, they simply select a"
+" random\n"
+"IV, postprocessing and updating it to generate the IV for the gateway and"
+" using \n"
+"that IV along side their own layer key to encrypt the preprocessed data."
+" For outbound \n"
+"tunnels they must iteratively decrypt the (unencrypted) IV and "
+"preprocessed \n"
+"data with the IV and layer keys for all hops in the tunnel. The result "
+"of the outbound\n"
+"tunnel encryption is that when each peer encrypts it, the endpoint will "
+"recover \n"
+"the initial preprocessed data."
+msgstr ""
+
+#: i2p2www/pages/site/docs/tunnels/implementation.html:225
+msgid "Participant Processing"
+msgstr ""
+
+#: i2p2www/pages/site/docs/tunnels/implementation.html:227
+msgid ""
+"When a peer receives a tunnel message, it checks that the message came "
+"from\n"
+"the same previous hop as before (initialized when the first message comes"
+" through\n"
+"the tunnel). If the previous peer is a different router, or if the "
+"message has\n"
+"already been seen, the message is dropped. The participant then encrypts"
+" the \n"
+"received IV with AES256/ECB using their IV key to determine the current "
+"IV, uses \n"
+"that IV with the participant's layer key to encrypt the data, encrypts "
+"the \n"
+"current IV with AES256/ECB using their IV key again, then forwards the "
+"tuple \n"
+"{nextTunnelId, nextIV, encryptedData} to the next hop. This double "
+"encryption\n"
+"of the IV (both before and after use) help address a certain class of\n"
+"confirmation attacks."
+msgstr ""
+
+#: i2p2www/pages/site/docs/tunnels/implementation.html:240
+msgid ""
+"Duplicate message detection is handled by a decaying Bloom filter on "
+"message\n"
+"IVs. Each router maintains a single Bloom filter to contain the XOR of "
+"the IV and\n"
+"the first block of the message received for all of the tunnels it is "
+"participating\n"
+"in, modified to drop seen entries after 10-20 minutes (when the tunnels "
+"will have\n"
+"expired). The size of the bloom filter and the parameters used are "
+"sufficient to\n"
+"more than saturate the router's network connection with a negligible "
+"chance of \n"
+"false positive. The unique value fed into the Bloom filter is the XOR of"
+" the IV \n"
+"and the first block so as to prevent nonsequential colluding peers in the"
+" tunnel \n"
+"from tagging a message by resending it with the IV and first block "
+"switched."
+msgstr ""
+
+#: i2p2www/pages/site/docs/tunnels/implementation.html:253
+msgid "Endpoint Processing"
+msgstr ""
+
+#: i2p2www/pages/site/docs/tunnels/implementation.html:255
+msgid ""
+"After receiving and validating a tunnel message at the last hop in the "
+"tunnel,\n"
+"how the endpoint recovers the data encoded by the gateway depends upon "
+"whether \n"
+"the tunnel is an inbound or an outbound tunnel. For outbound tunnels, "
+"the \n"
+"endpoint encrypts the message with its layer key just like any other "
+"participant, \n"
+"exposing the preprocessed data. For inbound tunnels, the endpoint is "
+"also the \n"
+"tunnel creator so they can merely iteratively decrypt the IV and message,"
+" using the \n"
+"layer and IV keys of each step in reverse order."
+msgstr ""
+
+#: i2p2www/pages/site/docs/tunnels/implementation.html:265
+msgid ""
+"At this point, the tunnel endpoint has the preprocessed data sent by the "
+"gateway,\n"
+"which it may then parse out into the included I2NP messages and forwards "
+"them as\n"
+"requested in their delivery instructions."
+msgstr ""
+
+#: i2p2www/pages/site/docs/tunnels/implementation.html:272
+msgid "Tunnel Building"
+msgstr ""
+
+#: i2p2www/pages/site/docs/tunnels/implementation.html:274
+msgid ""
+"When building a tunnel, the creator must send a request with the "
+"necessary\n"
+"configuration data to each of the hops and wait for all of them to agree "
+"before\n"
+"enabling the tunnel. The requests are encrypted so that only the peers "
+"who need\n"
+"to know a piece of information (such as the tunnel layer or IV key) has "
+"that\n"
+"data. In addition, only the tunnel creator will have access to the "
+"peer's\n"
+"reply. There are three important dimensions to keep in mind when "
+"producing\n"
+"the tunnels: what peers are used (and where), how the requests are sent "
+"(and \n"
+"replies received), and how they are maintained."
+msgstr ""
+
+#: i2p2www/pages/site/docs/tunnels/implementation.html:288
+msgid ""
+"Beyond the two types of tunnels - inbound and outbound - there are two "
+"styles\n"
+"of peer selection used for different tunnels - exploratory and client.\n"
+"Exploratory tunnels are used for both network database maintenance and "
+"tunnel\n"
+"maintenance, while client tunnels are used for end to end client messages."
+msgstr ""
+
+#: i2p2www/pages/site/docs/tunnels/implementation.html:296
+msgid "Exploratory tunnel peer selection"
+msgstr ""
+
+#: i2p2www/pages/site/docs/tunnels/implementation.html:298
+msgid ""
+"Exploratory tunnels are built out of a random selection of peers from a "
+"subset\n"
+"of the network. The particular subset varies on the local router and on "
+"what their\n"
+"tunnel routing needs are. In general, the exploratory tunnels are built "
+"out of\n"
+"randomly selected peers who are in the peer's \"not failing but active\" "
+"profile\n"
+"category. The secondary purpose of the tunnels, beyond merely tunnel "
+"routing,\n"
+"is to find underutilized high capacity peers so that they can be promoted"
+" for\n"
+"use in client tunnels."
+msgstr ""
+
+#: i2p2www/pages/site/docs/tunnels/implementation.html:308
+#, python-format
+msgid ""
+"Exploratory peer selection is discussed further on the\n"
+"Peer Profiling and Selection page."
+msgstr ""
+
+#: i2p2www/pages/site/docs/tunnels/implementation.html:314
+msgid "Client tunnel peer selection"
+msgstr ""
+
+#: i2p2www/pages/site/docs/tunnels/implementation.html:316
+msgid ""
+"Client tunnels are built with a more stringent set of requirements - the "
+"local\n"
+"router will select peers out of its \"fast and high capacity\" profile "
+"category so\n"
+"that performance and reliability will meet the needs of the client "
+"application.\n"
+"However, there are several important details beyond that basic selection "
+"that \n"
+"should be adhered to, depending upon the client's anonymity needs."
+msgstr ""
+
+#: i2p2www/pages/site/docs/tunnels/implementation.html:324
+#, python-format
+msgid ""
+"Client peer selection is discussed further on the\n"
+"Peer Profiling and Selection page."
+msgstr ""
+
+#: i2p2www/pages/site/docs/tunnels/implementation.html:329
+msgid "Peer Ordering within Tunnels"
+msgstr ""
+
+#: i2p2www/pages/site/docs/tunnels/implementation.html:331
+#, python-format
+msgid ""
+"Peers are ordered within tunnels to deal with the\n"
+"predecessor attack\n"
+"(2008 update)."
+msgstr ""
+
+#: i2p2www/pages/site/docs/tunnels/implementation.html:338
+msgid ""
+"To frustrate the predecessor \n"
+"attack, the tunnel selection keeps the peers selected in a strict order -"
+"\n"
+"if A, B, and C are in a tunnel for a particular tunnel pool, the hop "
+"after A is always B, and the hop after\n"
+"B is always C."
+msgstr ""
+
+#: i2p2www/pages/site/docs/tunnels/implementation.html:345
+msgid ""
+"Ordering is implemented by generating a random 32-byte key for each\n"
+"tunnel pool at startup.\n"
+"Peers should not be able to guess the ordering, or an attacker could\n"
+"craft two router hashes far apart to maximize the chance of being at both"
+"\n"
+"ends of a tunnel.\n"
+"Peers are sorted by XOR distance of the\n"
+"SHA256 Hash of (the peer's hash concatenated with the random key) from "
+"the random key"
+msgstr ""
+
+#: i2p2www/pages/site/docs/tunnels/implementation.html:360
+msgid ""
+"Because each tunnel pool uses a different random key, ordering is "
+"consistent\n"
+"within a single pool but not between different pools.\n"
+"New keys are generated at each router restart."
+msgstr ""
+
+#: i2p2www/pages/site/docs/tunnels/implementation.html:367
+msgid "Request delivery"
+msgstr ""
+
+#: i2p2www/pages/site/docs/tunnels/implementation.html:369
+#, python-format
+msgid ""
+"A multi-hop tunnel is built using a single build message which is "
+"repeatedly\n"
+"decrypted and forwarded. In the terminology of\n"
+"Hashing it out in Public,\n"
+"this is \"non-interactive\" telescopic tunnel building."
+msgstr ""
+
+#: i2p2www/pages/site/docs/tunnels/implementation.html:376
+#, python-format
+msgid ""
+"This tunnel request preparation, delivery, and response method is\n"
+"designed to reduce the number of\n"
+"predecessors exposed, cuts the number of messages transmitted, verifies "
+"proper\n"
+"connectivity, and avoids the message counting attack of traditional "
+"telescopic\n"
+"tunnel creation.\n"
+"(This method, which sends messages to extend a tunnel through the "
+"already-established\n"
+"part of the tunnel, is termed \"interactive\" telescopic tunnel building "
+"in\n"
+"the \"Hashing it out\" paper.)"
+msgstr ""
+
+#: i2p2www/pages/site/docs/tunnels/implementation.html:387
+#, python-format
+msgid ""
+"The details of tunnel request and response messages, and their "
+"encryption,\n"
+"are specified here."
+msgstr ""
+
+#: i2p2www/pages/site/docs/tunnels/implementation.html:392
+msgid ""
+"Peers may reject tunnel creation requests for a variety of reasons, "
+"though\n"
+"a series of four increasingly severe rejections are known: probabilistic "
+"rejection\n"
+"(due to approaching the router's capacity, or in response to a flood of "
+"requests), \n"
+"transient overload, bandwidth overload, and critical failure. When "
+"received, \n"
+"those four are interpreted by the tunnel creator to help adjust their "
+"profile of\n"
+"the router in question."
+msgstr ""
+
+#: i2p2www/pages/site/docs/tunnels/implementation.html:401
+#, python-format
+msgid ""
+"For more information on peer profiling, see the\n"
+"Peer Profiling and Selection page."
+msgstr ""
+
+#: i2p2www/pages/site/docs/tunnels/implementation.html:407
+msgid "Tunnel Pools"
+msgstr ""
+
+#: i2p2www/pages/site/docs/tunnels/implementation.html:409
+#, python-format
+msgid ""
+"To allow efficient operation, the router maintains a series of tunnel "
+"pools,\n"
+"each managing a group of tunnels used for a specific purpose with their "
+"own\n"
+"configuration. When a tunnel is needed for that purpose, the router "
+"selects one\n"
+"out of the appropriate pool at random. Overall, there are two "
+"exploratory tunnel\n"
+"pools - one inbound and one outbound - each using the router's default "
+"configuration.\n"
+"In addition, there is a pair of pools for each local destination -\n"
+"one inbound and one outbound tunnel pool. Those pools use the "
+"configuration specified\n"
+"when the local destination connects to the router via I2CP, or the router's defaults if\n"
+"not specified."
+msgstr ""
+
+#: i2p2www/pages/site/docs/tunnels/implementation.html:421
+#, python-format
+msgid ""
+"Each pool has within its configuration a few key settings, defining how "
+"many\n"
+"tunnels to keep active, how many backup tunnels to maintain in case of "
+"failure,\n"
+"how long the tunnels should be, whether those\n"
+"lengths should be randomized, as \n"
+"well as any of the other settings allowed when configuring individual "
+"tunnels.\n"
+"Configuration options are specified on the I2CP "
+"page."
+msgstr ""
+
+#: i2p2www/pages/site/docs/tunnels/implementation.html:431
+msgid "Tunnel Lengths and Defaults"
+msgstr ""
+
+#: i2p2www/pages/site/docs/tunnels/implementation.html:433
+msgid "On the tunnel overview page"
+msgstr ""
+
+#: i2p2www/pages/site/docs/tunnels/implementation.html:435
+msgid "Anticipatory Build Strategy and Priority"
+msgstr ""
+
+#: i2p2www/pages/site/docs/tunnels/implementation.html:437
+msgid ""
+"Tunnel building is expensive, and tunnels expire a fixed time after they "
+"are built.\n"
+"However, when a pool that runs out of tunnels, the Destination is "
+"essentially dead.\n"
+"In addition, tunnel build success rate may vary greatly with both local "
+"and global\n"
+"network conditions.\n"
+"Therefore, it is important to maintain an anticipatory, adaptive build "
+"strategy\n"
+"to ensure that new tunnels are successfully built before they are needed,"
+"\n"
+"without building an excess of tunnels, building them too soon,\n"
+"or consuming too much CPU or bandwidth creating and sending the encrypted"
+" build messages."
+msgstr ""
+
+#: i2p2www/pages/site/docs/tunnels/implementation.html:448
+msgid ""
+"For each tuple {exploratory/client, in/out, length, length variance}\n"
+"the router maintains statistics on the time required for a successful\n"
+"tunnel build.\n"
+"Using these statistics, it calculates how long before a tunnel's "
+"expiration\n"
+"it should start attempting to build a replacement.\n"
+"As the expiration time approaches without a successful replacement,\n"
+"it starts multiple build attempts in parallel, and then\n"
+"will increase the number of parallel attempts if necessary."
+msgstr ""
+
+#: i2p2www/pages/site/docs/tunnels/implementation.html:459
+msgid ""
+"To cap bandwidth and CPU usage,\n"
+"the router also limits the maximum number of build attempts outstanding\n"
+"across all pools.\n"
+"Critical builds (those for exploratory tunnels, and for pools that have\n"
+"run out of tunnels) are prioritized."
+msgstr ""
+
+#: i2p2www/pages/site/docs/tunnels/implementation.html:468
+msgid "Tunnel Message Throttling"
+msgstr ""
+
+#: i2p2www/pages/site/docs/tunnels/implementation.html:470
+msgid ""
+"Even though the tunnels within I2P bear a resemblance to a circuit "
+"switched\n"
+"network, everything within I2P is strictly message based - tunnels are "
+"merely\n"
+"accounting tricks to help organize the delivery of messages. No "
+"assumptions are\n"
+"made regarding reliability or ordering of messages, and retransmissions "
+"are left\n"
+"to higher levels (e.g. I2P's client layer streaming library). This "
+"allows I2P\n"
+"to take advantage of throttling techniques available to both packet "
+"switched and\n"
+"circuit switched networks. For instance, each router may keep track of "
+"the \n"
+"moving average of how much data each tunnel is using, combine that with "
+"all of \n"
+"the averages used by other tunnels the router is participating in, and be"
+" able\n"
+"to accept or reject additional tunnel participation requests based on its"
+" \n"
+"capacity and utilization. On the other hand, each router can simply drop"
+" \n"
+"messages that are beyond its capacity, exploiting the research used on "
+"the \n"
+"normal Internet."
+msgstr ""
+
+#: i2p2www/pages/site/docs/tunnels/implementation.html:486
+msgid ""
+"In the current implementation, routers implement a\n"
+"weighted random early discard (WRED) strategy.\n"
+"For all participating routers (internal participant, inbound gateway, and"
+" outbound endpoint),\n"
+"the router will start randomly dropping a portion of messages as the\n"
+"bandwidth limits are approached.\n"
+"As traffic gets closer to, or exceeds, the limits, more messages are "
+"dropped.\n"
+"For an internal participant, all messages are fragmented and padded and "
+"therefore are the same size.\n"
+"At the inbound gateway and outbound endpoint, however, the dropping "
+"decision is made\n"
+"on the full (coalesced) message, and the message size is taken into "
+"account.\n"
+"Larger messages are more likely to be dropped.\n"
+"Also, messages are more likely to be dropped at the outbound endpoint "
+"than the inbound gateway,\n"
+"as those messages are not as \"far along\" in their journey and thus the "
+"network cost of\n"
+"dropping those messages is lower."
+msgstr ""
+
+#: i2p2www/pages/site/docs/tunnels/implementation.html:504
+msgid "Mixing/batching"
+msgstr ""
+
+#: i2p2www/pages/site/docs/tunnels/implementation.html:506
+msgid ""
+"What strategies could be used at the gateway and at each hop for "
+"delaying,\n"
+"reordering, rerouting, or padding messages? To what extent should this "
+"be done\n"
+"automatically, how much should be configured as a per tunnel or per hop "
+"setting,\n"
+"and how should the tunnel's creator (and in turn, user) control this "
+"operation?\n"
+"All of this is left as unknown, to be worked out for a distant future "
+"release."
+msgstr ""
+
+#: i2p2www/pages/site/docs/tunnels/implementation.html:515
+msgid "Padding"
+msgstr ""
+
+#: i2p2www/pages/site/docs/tunnels/implementation.html:516
+msgid ""
+"The padding strategies can be used on a variety of levels, addressing the"
+"\n"
+"exposure of message size information to different adversaries.\n"
+"The current fixed tunnel message size is 1024 bytes. Within this "
+"however, the fragmented\n"
+"messages themselves are not padded by the tunnel at all, though for end "
+"to end \n"
+"messages, they may be padded as part of the garlic wrapping."
+msgstr ""
+
+#: i2p2www/pages/site/docs/tunnels/implementation.html:526
+msgid ""
+"WRED strategies have a significant impact on end-to-end performance,\n"
+"and prevention of network congestion collapse.\n"
+"The current WRED strategy should be carefully evaluated and improved."
+msgstr ""
+
+#: i2p2www/pages/site/docs/tunnels/old-implementation.html:2
+msgid "Old Tunnel Implementation"
+msgstr ""
+
+#: i2p2www/pages/site/docs/tunnels/old-implementation.html:5
+#, python-format
+msgid ""
+"Note: Obsolete - NOT used! Replaced in 0.6.1.10 - see here for the current implementation"
+msgstr ""
+
+#: i2p2www/pages/site/docs/tunnels/unidirectional.html:7
+msgid ""
+"This page describes the origins and design of I2P's unidirectional "
+"tunnels.\n"
+"For further infomrmation see:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/tunnels/unidirectional.html:13
+msgid "Tunnel overview page"
+msgstr ""
+
+#: i2p2www/pages/site/docs/tunnels/unidirectional.html:19
+msgid "Tunnel design discussion"
+msgstr ""
+
+#: i2p2www/pages/site/docs/tunnels/unidirectional.html:21
+msgid "Peer selection"
+msgstr ""
+
+#: i2p2www/pages/site/docs/tunnels/unidirectional.html:23
+msgid "Meeting 125 (~13:12-13:30)"
+msgstr ""
+
+#: i2p2www/pages/site/docs/tunnels/unidirectional.html:28
+msgid "Review"
+msgstr ""
+
+#: i2p2www/pages/site/docs/tunnels/unidirectional.html:30
+msgid ""
+"While we aren't aware of any published research on the advantages of \n"
+"unidirecdtional tunnels,\n"
+"they appear to make it harder to detect a \n"
+"request/response pattern, which is quite possible to detect over a \n"
+"bidirectional tunnel.\n"
+"Several apps and protocols, notably HTTP,\n"
+"do transfer data in such manner. Having the traffic follow the same \n"
+"route to its destination and back could make it easier for an \n"
+"attacker who has only timing and traffic volume data to infer the path a"
+" \n"
+"tunnel is taking.\n"
+"Having the response come back along a different path arguably \n"
+"makes it harder."
+msgstr ""
+
+#: i2p2www/pages/site/docs/tunnels/unidirectional.html:45
+msgid ""
+"When dealing with \n"
+"an internal adversary or most external adversaries, I2P's undirectional "
+"tunnels\n"
+"expose half as much traffic data than would be exposed with bidirectional"
+" circuits\n"
+"by simply looking at the flows themselves - an HTTP request and response "
+"would \n"
+"follow the same path in Tor, while in I2P the packets making up the "
+"request \n"
+"would go out through one or more outbound tunnels and the packets making "
+"up \n"
+"the response would come back through one or more different inbound "
+"tunnels."
+msgstr ""
+
+#: i2p2www/pages/site/docs/tunnels/unidirectional.html:55
+msgid ""
+"The strategy of using two separate tunnels for inbound and outbound\n"
+"communication is not the only technique available, and it does have "
+"anonymity\n"
+"implications. On the positive side, by using separate tunnels it lessens"
+" the\n"
+"traffic data exposed for analysis to participants in a tunnel - for "
+"instance,\n"
+"peers in an outbound tunnel from a web browser would only see the traffic"
+" of\n"
+"an HTTP GET, while the peers in an inbound tunnel would see the payload \n"
+"delivered along the tunnel. With bidirectional tunnels, all participants"
+" would\n"
+"have access to the fact that e.g. 1KB was sent in one direction, then "
+"100KB\n"
+"in the other. On the negative side, using unidirectional tunnels means "
+"that\n"
+"there are two sets of peers which need to be profiled and accounted for, "
+"and\n"
+"additional care must be taken to address the increased speed of "
+"predecessor\n"
+"attacks. The tunnel pooling and building process\n"
+"(peer selection and ordering strategies)\n"
+"should minimize the worries of the predecessor attack."
+msgstr ""
+
+#: i2p2www/pages/site/docs/tunnels/unidirectional.html:73
+msgid "Anonymity"
+msgstr ""
+
+#: i2p2www/pages/site/docs/tunnels/unidirectional.html:75
+#, python-format
+msgid ""
+"A recent paper by Hermann and Grothoff\n"
+"declared that I2P's unidirectional tunnels \"seems to be a bad design "
+"decision\"."
+msgstr ""
+
+#: i2p2www/pages/site/docs/tunnels/unidirectional.html:80
+msgid ""
+"The paper's main point is that\n"
+"deanonymizations on unidirectional tunnels take a longer time, which is "
+"an \n"
+"advantage, but that an attacker can be more certain in the unidirectional"
+" case. \n"
+"Therefore, the paper claims it isn't an advantage at all, but a "
+"disadvantage, at least\n"
+"with long-living eepsites."
+msgstr ""
+
+#: i2p2www/pages/site/docs/tunnels/unidirectional.html:88
+msgid ""
+"This conclusion is not fully supported by the paper. Unidirectional "
+"tunnels clearly \n"
+"mitigate other attacks and it's not clear how to trade off the risk of "
+"the \n"
+"attack in the paper\n"
+"with attacks on a bidirectional tunnel architecture."
+msgstr ""
+
+#: i2p2www/pages/site/docs/tunnels/unidirectional.html:95
+msgid ""
+"This conclusion is based on an arbitrary certainty vs. time weighting \n"
+"(tradeoff) that may not be applicable in all cases. For \n"
+"example, somebody could make a list of possible IPs then issue subpoenas "
+"to \n"
+"each. Or the attacker could DDoS each in turn and via a simple \n"
+"intersection attack see if the eepsite goes down or is slowed down. So "
+"close \n"
+"may be good enough, or time may be more important."
+msgstr ""
+
+#: i2p2www/pages/site/docs/tunnels/unidirectional.html:104
+msgid ""
+"The conclusion is based on a specific weighting of the importance of "
+"certainty \n"
+"vs. time, and that weighting may be wrong, and it's definitely debatable,"
+" \n"
+"especially in a real world with subpoenas, search warrants, and other "
+"methods \n"
+"available for final confirmation."
+msgstr ""
+
+#: i2p2www/pages/site/docs/tunnels/unidirectional.html:111
+msgid ""
+"A full analysis of the tradeoffs of unidirectional vs. bidirectional \n"
+"tunnels is clearly outside the scope of the paper, and has not been done"
+" \n"
+"elsewhere. For example, how does this attack compare to the numerous "
+"possible \n"
+"timing attacks published about onion-routed networks? Clearly the authors"
+" have not\n"
+"done that analysis, if it's even possible to do it\n"
+"effectively."
+msgstr ""
+
+#: i2p2www/pages/site/docs/tunnels/unidirectional.html:120
+msgid ""
+"Tor uses bidirectional tunnels and has had a lot of academic review. I2P"
+" \n"
+"uses unidirectional tunnels and has had very little review. Does the lack"
+" of a \n"
+"research paper defending unidirectional tunnels mean that it is a poor "
+"design \n"
+"choice, or just that it needs more study? Timing attacks and \n"
+"distributed attacks are difficult to defend against in both I2P and Tor. "
+"The \n"
+"design intent (see references above) was that unidirectional tunnels are "
+"more \n"
+"resistant to timing attacks. However, the paper presents a somewhat "
+"different type of timing \n"
+"attack. Is this attack, innovative as it is, sufficient to label I2P's \n"
+"tunnel architecture (and thus I2P as a whole) a \"bad design\", and by \n"
+"implication clearly inferior to Tor, or is it just a design alternative "
+"that \n"
+"clearly needs further investigation and analysis? There are several other"
+" reasons \n"
+"to consider I2P currently inferior to Tor and other projects (small "
+"network \n"
+"size, lack of funding, lack of review) but is unidirectional tunnels "
+"really a \n"
+"reason?"
+msgstr ""
+
+#: i2p2www/pages/site/docs/tunnels/unidirectional.html:137
+msgid ""
+"In summary, \"bad design decision\" is apparently (since the paper does\n"
+"not label bidirectional tunnels \"bad\") shorthand for \"unidirectional \n"
+"tunnels are unequivocally inferior to bidirectional tunnels\", yet this \n"
+"conclusion is not supported by the paper."
+msgstr ""
+