diff --git a/i2p2www/translations/az/LC_MESSAGES/blog.po b/i2p2www/translations/az/LC_MESSAGES/blog.po
new file mode 100644
index 00000000..338c4f06
--- /dev/null
+++ b/i2p2www/translations/az/LC_MESSAGES/blog.po
@@ -0,0 +1,8333 @@
+# Azerbaijani translations for I2P.
+# Copyright (C) 2018 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: 2018-08-24 11:47+0000\n"
+"PO-Revision-Date: 2018-08-24 11:51+0000\n"
+"Last-Translator: zzzi2p\n"
+"Language-Team: Azerbaijani "
+"(http://www.transifex.com/otf/I2P/language/az/)\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 1.3\n"
+
+#: i2p2www/blog/2011/10/11/0.8.9-Release.rst:24
+#: i2p2www/blog/2011/10/20/0.8.10-Release.rst:11
+#: i2p2www/blog/2011/11/08/0.8.11-Release.rst:25
+#: i2p2www/blog/2012/01/06/0.8.12-Release.rst:12
+#: i2p2www/blog/2012/02/27/0.8.13-Release.rst:12
+#: i2p2www/blog/2012/05/02/0.9-Release.rst:17
+#: i2p2www/blog/2012/07/30/0.9.1-Release.rst:12
+#: i2p2www/blog/2012/09/21/0.9.2-Release.rst:16
+#: i2p2www/blog/2012/10/27/0.9.3-Release.rst:16
+#: i2p2www/blog/2012/12/17/0.9.4-Release.rst:26
+#: i2p2www/blog/2013/03/08/0.9.5-Release.rst:19
+#: i2p2www/blog/2013/05/28/0.9.6-Release.rst:19
+msgid "Files are available on the `download page`_."
+msgstr ""
+
+#: i2p2www/blog/2011/10/11/0.8.9-Release.rst:28
+#: i2p2www/blog/2011/10/20/0.8.10-Release.rst:15
+#: i2p2www/blog/2011/11/08/0.8.11-Release.rst:29
+#: i2p2www/blog/2012/01/06/0.8.12-Release.rst:16
+#: i2p2www/blog/2012/02/27/0.8.13-Release.rst:16
+#: i2p2www/blog/2012/05/02/0.9-Release.rst:21
+#: i2p2www/blog/2012/07/30/0.9.1-Release.rst:16
+#: i2p2www/blog/2012/09/21/0.9.2-Release.rst:20
+#: i2p2www/blog/2012/10/27/0.9.3-Release.rst:20
+#: i2p2www/blog/2012/12/17/0.9.4-Release.rst:30
+#: i2p2www/blog/2013/03/08/0.9.5-Release.rst:23
+#: i2p2www/blog/2013/05/28/0.9.6-Release.rst:23
+#: i2p2www/blog/2014/02/16/i2pbrowser-malware.rst:39
+msgid "`download page`"
+msgstr ""
+
+#: i2p2www/blog/2011/10/11/0.8.9-Release.rst:30
+#: i2p2www/blog/2011/10/20/0.8.10-Release.rst:17
+#: i2p2www/blog/2011/11/08/0.8.11-Release.rst:31
+#: i2p2www/blog/2012/01/06/0.8.12-Release.rst:18
+#: i2p2www/blog/2012/02/27/0.8.13-Release.rst:19
+#: i2p2www/blog/2012/07/30/0.9.1-Release.rst:18
+#: i2p2www/blog/2012/09/21/0.9.2-Release.rst:22
+#: i2p2www/blog/2012/10/27/0.9.3-Release.rst:22
+#: i2p2www/blog/2012/12/17/0.9.4-Release.rst:32
+#: i2p2www/blog/2013/03/08/0.9.5-Release.rst:25
+#: i2p2www/blog/2013/05/28/0.9.6-Release.rst:79
+#: i2p2www/blog/2013/07/15/0.9.7-Release.rst:45
+#: i2p2www/blog/2013/08/10/0.9.7.1-Release.rst:13
+#: i2p2www/blog/2013/09/30/0.9.8-Release.rst:101
+#: i2p2www/blog/2013/12/07/0.9.9-Release.rst:26
+#: i2p2www/blog/2014/01/21/Syndie-1.105b-Release.rst:48
+#: i2p2www/blog/2014/01/22/0.9.10-Release.rst:34
+#: i2p2www/blog/2014/02/08/0.9.11-Release.rst:35
+#: i2p2www/blog/2014/03/31/0.9.12-Release.rst:65
+#: i2p2www/blog/2014/05/22/0.9.13-Release.rst:29
+#: i2p2www/blog/2014/07/26/0.9.14-Release.rst:37
+#: i2p2www/blog/2014/08/09/0.9.14.1-Release.rst:32
+#: i2p2www/blog/2014/09/20/0.9.15-Release.rst:38
+#: i2p2www/blog/2014/11/01/0.9.16-Release.rst:36
+#: i2p2www/blog/2014/11/30/0.9.17-Release.rst:43
+#: i2p2www/blog/2015/02/22/0.9.18-Release.rst:27
+#: i2p2www/blog/2015/04/12/0.9.19-Release.rst:30
+#: i2p2www/blog/2015/06/02/0.9.20-Release.rst:44
+#: i2p2www/blog/2015/07/31/0.9.21-Release.rst:36
+#: i2p2www/blog/2015/09/12/0.9.22-Release.rst:34
+#: i2p2www/blog/2015/11/19/0.9.23-Release.rst:73
+#: i2p2www/blog/2016/01/27/0.9.24-Release.rst:53
+#: i2p2www/blog/2016/03/22/0.9.25-Release.rst:35
+#: i2p2www/blog/2016/06/07/0.9.26-Release.rst:54
+#: i2p2www/blog/2016/10/17/0.9.27-Release.rst:33
+#: i2p2www/blog/2016/12/12/0.9.28-Release.rst:35
+#: i2p2www/blog/2017/02/27/0.9.29-Release.rst:32
+#: i2p2www/blog/2017/05/03/0.9.30-Release.rst:56
+#: i2p2www/blog/2017/08/07/0.9.31-Release.rst:32
+#: i2p2www/blog/2017/11/07/0.9.32-Release.rst:29
+#: i2p2www/blog/2018/01/30/0.9.33-Release.rst:30
+#: i2p2www/blog/2018/04/10/0.9.34-Release.rst:30
+#: i2p2www/blog/2018/06/26/0.9.35-Release.rst:36
+#: i2p2www/blog/2018/08/23/0.9.36-Release.rst:33
+msgid "RELEASE DETAILS"
+msgstr ""
+
+#: i2p2www/blog/2011/10/11/0.8.9-Release.rst:32
+#: i2p2www/blog/2011/10/20/0.8.10-Release.rst:19
+#: i2p2www/blog/2011/11/08/0.8.11-Release.rst:33
+#: i2p2www/blog/2012/02/27/0.8.13-Release.rst:40
+#: i2p2www/blog/2012/05/02/0.9-Release.rst:50
+#: i2p2www/blog/2012/09/21/0.9.2-Release.rst:24
+#: i2p2www/blog/2012/10/27/0.9.3-Release.rst:24
+#: i2p2www/blog/2012/12/17/0.9.4-Release.rst:34
+#: i2p2www/blog/2013/09/30/0.9.8-Release.rst:103
+msgid "Major Changes"
+msgstr ""
+
+#: i2p2www/blog/2011/10/11/0.8.9-Release.rst:44
+#: i2p2www/blog/2011/10/20/0.8.10-Release.rst:24
+#: i2p2www/blog/2011/11/08/0.8.11-Release.rst:43
+#: i2p2www/blog/2012/01/06/0.8.12-Release.rst:55
+#: i2p2www/blog/2012/02/27/0.8.13-Release.rst:47
+#: i2p2www/blog/2012/05/02/0.9-Release.rst:58
+#: i2p2www/blog/2012/07/30/0.9.1-Release.rst:43
+#: i2p2www/blog/2012/09/21/0.9.2-Release.rst:32
+#: i2p2www/blog/2012/10/27/0.9.3-Release.rst:30
+#: i2p2www/blog/2012/12/17/0.9.4-Release.rst:39
+#: i2p2www/blog/2013/05/28/0.9.6-Release.rst:81
+#: i2p2www/blog/2013/07/15/0.9.7-Release.rst:54
+#: i2p2www/blog/2013/09/30/0.9.8-Release.rst:112
+#: i2p2www/blog/2013/12/07/0.9.9-Release.rst:34
+#: i2p2www/blog/2014/01/21/Syndie-1.105b-Release.rst:51
+#: i2p2www/blog/2014/01/22/0.9.10-Release.rst:40
+#: i2p2www/blog/2014/02/08/0.9.11-Release.rst:41
+#: i2p2www/blog/2014/03/31/0.9.12-Release.rst:76
+#: i2p2www/blog/2014/05/22/0.9.13-Release.rst:39
+#: i2p2www/blog/2014/07/26/0.9.14-Release.rst:50
+#: i2p2www/blog/2014/08/09/0.9.14.1-Release.rst:35
+#: i2p2www/blog/2014/09/20/0.9.15-Release.rst:51
+#: i2p2www/blog/2014/11/01/0.9.16-Release.rst:55
+#: i2p2www/blog/2014/11/30/0.9.17-Release.rst:53
+#: i2p2www/blog/2015/02/22/0.9.18-Release.rst:30
+#: i2p2www/blog/2015/04/12/0.9.19-Release.rst:40
+#: i2p2www/blog/2015/06/02/0.9.20-Release.rst:57
+#: i2p2www/blog/2015/07/31/0.9.21-Release.rst:52
+#: i2p2www/blog/2015/09/12/0.9.22-Release.rst:42
+#: i2p2www/blog/2015/11/19/0.9.23-Release.rst:80
+#: i2p2www/blog/2016/01/27/0.9.24-Release.rst:63
+#: i2p2www/blog/2016/03/22/0.9.25-Release.rst:47
+#: i2p2www/blog/2016/06/07/0.9.26-Release.rst:71
+#: i2p2www/blog/2016/10/17/0.9.27-Release.rst:43
+#: i2p2www/blog/2016/12/12/0.9.28-Release.rst:47
+#: i2p2www/blog/2017/02/27/0.9.29-Release.rst:48
+#: i2p2www/blog/2017/05/03/0.9.30-Release.rst:68
+#: i2p2www/blog/2017/08/07/0.9.31-Release.rst:41
+#: i2p2www/blog/2017/11/07/0.9.32-Release.rst:37
+#: i2p2www/blog/2018/01/30/0.9.33-Release.rst:43
+#: i2p2www/blog/2018/04/10/0.9.34-Release.rst:38
+#: i2p2www/blog/2018/06/26/0.9.35-Release.rst:45
+#: i2p2www/blog/2018/08/23/0.9.36-Release.rst:43
+msgid "Bug Fixes"
+msgstr ""
+
+#: i2p2www/blog/2011/10/11/0.8.9-Release.rst:54
+#: i2p2www/blog/2011/10/20/0.8.10-Release.rst:30
+#: i2p2www/blog/2011/11/08/0.8.11-Release.rst:47
+#: i2p2www/blog/2012/01/06/0.8.12-Release.rst:69
+#: i2p2www/blog/2012/02/27/0.8.13-Release.rst:63
+#: i2p2www/blog/2012/05/02/0.9-Release.rst:68
+#: i2p2www/blog/2012/07/30/0.9.1-Release.rst:54
+#: i2p2www/blog/2012/09/21/0.9.2-Release.rst:41
+#: i2p2www/blog/2012/10/27/0.9.3-Release.rst:36
+#: i2p2www/blog/2012/12/17/0.9.4-Release.rst:51
+#: i2p2www/blog/2013/03/08/0.9.5-Release.rst:43
+#: i2p2www/blog/2013/05/28/0.9.6-Release.rst:94
+#: i2p2www/blog/2013/07/15/0.9.7-Release.rst:63
+#: i2p2www/blog/2013/08/10/0.9.7.1-Release.rst:19
+#: i2p2www/blog/2013/09/30/0.9.8-Release.rst:118
+#: i2p2www/blog/2013/12/07/0.9.9-Release.rst:52
+#: i2p2www/blog/2014/01/21/Syndie-1.105b-Release.rst:99
+#: i2p2www/blog/2014/01/22/0.9.10-Release.rst:49
+#: i2p2www/blog/2014/02/08/0.9.11-Release.rst:47
+#: i2p2www/blog/2014/03/31/0.9.12-Release.rst:87
+#: i2p2www/blog/2014/05/22/0.9.13-Release.rst:49
+#: i2p2www/blog/2014/07/26/0.9.14-Release.rst:57
+#: i2p2www/blog/2014/08/09/0.9.14.1-Release.rst:42
+#: i2p2www/blog/2014/09/20/0.9.15-Release.rst:60
+#: i2p2www/blog/2014/11/01/0.9.16-Release.rst:68
+#: i2p2www/blog/2014/11/30/0.9.17-Release.rst:65
+#: i2p2www/blog/2015/02/22/0.9.18-Release.rst:38
+#: i2p2www/blog/2015/04/12/0.9.19-Release.rst:49
+#: i2p2www/blog/2015/06/02/0.9.20-Release.rst:75
+#: i2p2www/blog/2015/07/31/0.9.21-Release.rst:65
+#: i2p2www/blog/2015/09/12/0.9.22-Release.rst:50
+#: i2p2www/blog/2015/11/19/0.9.23-Release.rst:89
+#: i2p2www/blog/2016/01/27/0.9.24-Release.rst:76
+#: i2p2www/blog/2016/03/22/0.9.25-Release.rst:53
+#: i2p2www/blog/2016/06/07/0.9.26-Release.rst:83
+#: i2p2www/blog/2016/10/17/0.9.27-Release.rst:58
+#: i2p2www/blog/2016/12/12/0.9.28-Release.rst:57
+#: i2p2www/blog/2017/02/27/0.9.29-Release.rst:62
+#: i2p2www/blog/2017/05/03/0.9.30-Release.rst:82
+#: i2p2www/blog/2017/08/07/0.9.31-Release.rst:54
+#: i2p2www/blog/2017/11/07/0.9.32-Release.rst:44
+#: i2p2www/blog/2018/01/30/0.9.33-Release.rst:74
+#: i2p2www/blog/2018/04/10/0.9.34-Release.rst:47
+#: i2p2www/blog/2018/06/26/0.9.35-Release.rst:57
+#: i2p2www/blog/2018/08/23/0.9.36-Release.rst:53
+msgid "Other"
+msgstr "Digər"
+
+#: i2p2www/blog/2011/10/11/0.8.9-Release.rst:73
+#: i2p2www/blog/2011/10/20/0.8.10-Release.rst:36
+#: i2p2www/blog/2011/11/08/0.8.11-Release.rst:51
+#: i2p2www/blog/2012/01/06/0.8.12-Release.rst:82
+#: i2p2www/blog/2012/02/27/0.8.13-Release.rst:75
+#: i2p2www/blog/2012/05/02/0.9-Release.rst:96
+#: i2p2www/blog/2012/07/30/0.9.1-Release.rst:76
+#: i2p2www/blog/2012/09/21/0.9.2-Release.rst:52
+#: i2p2www/blog/2012/10/27/0.9.3-Release.rst:56
+#: i2p2www/blog/2012/12/17/0.9.4-Release.rst:67
+#: i2p2www/blog/2013/03/08/0.9.5-Release.rst:56
+#: i2p2www/blog/2013/05/28/0.9.6-Release.rst:110
+#: i2p2www/blog/2013/07/15/0.9.7-Release.rst:79
+#: i2p2www/blog/2013/08/10/0.9.7.1-Release.rst:30
+#: i2p2www/blog/2013/09/30/0.9.8-Release.rst:129
+#: i2p2www/blog/2013/10/02/0.9.8.1-Release.rst:27
+#: i2p2www/blog/2013/12/07/0.9.9-Release.rst:76
+#: i2p2www/blog/2014/01/22/0.9.10-Release.rst:64
+#: i2p2www/blog/2014/02/08/0.9.11-Release.rst:59
+#: i2p2www/blog/2014/03/31/0.9.12-Release.rst:104
+#: i2p2www/blog/2014/05/22/0.9.13-Release.rst:62
+#: i2p2www/blog/2014/07/26/0.9.14-Release.rst:73
+#: i2p2www/blog/2014/08/09/0.9.14.1-Release.rst:52
+#: i2p2www/blog/2014/09/20/0.9.15-Release.rst:76
+#: i2p2www/blog/2014/11/01/0.9.16-Release.rst:86
+#: i2p2www/blog/2014/11/30/0.9.17-Release.rst:81
+#: i2p2www/blog/2015/02/22/0.9.18-Release.rst:61
+#: i2p2www/blog/2015/04/12/0.9.19-Release.rst:69
+#: i2p2www/blog/2015/06/02/0.9.20-Release.rst:101
+#: i2p2www/blog/2015/07/31/0.9.21-Release.rst:75
+#: i2p2www/blog/2015/09/12/0.9.22-Release.rst:56
+#: i2p2www/blog/2015/11/19/0.9.23-Release.rst:115
+#: i2p2www/blog/2016/01/27/0.9.24-Release.rst:105
+#: i2p2www/blog/2016/03/22/0.9.25-Release.rst:76
+#: i2p2www/blog/2016/06/07/0.9.26-Release.rst:96
+#: i2p2www/blog/2016/10/17/0.9.27-Release.rst:73
+#: i2p2www/blog/2016/12/12/0.9.28-Release.rst:103
+#: i2p2www/blog/2017/02/27/0.9.29-Release.rst:77
+#: i2p2www/blog/2017/03/04/0.9.29-Windows-Installer-Fix.rst:25
+#: i2p2www/blog/2017/05/03/0.9.30-Release.rst:102
+#: i2p2www/blog/2017/08/07/0.9.31-Release.rst:69
+#: i2p2www/blog/2017/11/07/0.9.32-Release.rst:58
+#: i2p2www/blog/2018/01/30/0.9.33-Release.rst:104
+#: i2p2www/blog/2018/04/10/0.9.34-Release.rst:63
+#: i2p2www/blog/2018/06/26/0.9.35-Release.rst:79
+#: i2p2www/blog/2018/08/23/0.9.36-Release.rst:73
+msgid "SHA256 Checksums:"
+msgstr ""
+
+#: i2p2www/blog/2012/01/06/0.8.12-Release.rst:39
+msgid "Major changes"
+msgstr ""
+
+#: i2p2www/blog/2012/01/06/0.8.12-Release.rst:47
+msgid "Wrapper Update"
+msgstr ""
+
+#: i2p2www/blog/2012/05/02/0.9-Release.rst:23
+msgid "Update Info"
+msgstr ""
+
+#: i2p2www/blog/2012/09/21/0.9.2-Release.rst:2
+msgid "0.9.2 Release"
+msgstr ""
+
+#: i2p2www/blog/2012/09/21/0.9.2-Release.rst:7
+#: i2p2www/blog/2012/09/21/0.9.2-Release.rst:9
+msgid ""
+"0.9.2 includes extensive low-level changes to improve the performance and"
+" efficiency of the router. We have updated our UPnP library, to hopefully"
+" make UPnP work for more people. I2PSnark now has DHT support, but it is "
+"not yet enabled by default, as we plan to do more testing during the "
+"upcoming 0.9.3 development cycle."
+msgstr ""
+
+#: i2p2www/blog/2012/09/21/0.9.2-Release.rst:12
+#: i2p2www/blog/2012/10/27/0.9.3-Release.rst:12
+msgid ""
+"As usual, there's also lots of bug fixes in this release, so updating is "
+"recommended."
+msgstr ""
+
+#: i2p2www/blog/2012/09/21/0.9.2-Release.rst:26
+msgid ""
+"SSU: Fix several problems in our UDP transport, to improve efficiency and"
+" reliability for connection setup. Also improve defenses against various "
+"types of bad input."
+msgstr ""
+
+#: i2p2www/blog/2012/09/21/0.9.2-Release.rst:27
+msgid ""
+"UPnP: Updated our library to fix several issues, should work for more "
+"routers now"
+msgstr ""
+
+#: i2p2www/blog/2012/09/21/0.9.2-Release.rst:28
+msgid ""
+"Transport: Improve performance in both our TCP and UDP transports, to "
+"benefit high-bandwidth routers"
+msgstr ""
+
+#: i2p2www/blog/2012/09/21/0.9.2-Release.rst:29
+msgid ""
+"Crypto: The thresholds and number of ElGamal/AES Session Tags delivered "
+"are now much more flexible, which should lessen protocol overhead and "
+"reduce stalls caused by dropped tags."
+msgstr ""
+
+#: i2p2www/blog/2012/09/21/0.9.2-Release.rst:30
+msgid ""
+"I2PSnark: Add DHT support, not yet enabled by default, will do further "
+"testing and plan to enable by default in 0.9.3."
+msgstr ""
+
+#: i2p2www/blog/2012/09/21/0.9.2-Release.rst:34
+msgid ""
+"Fix various issues affecting memory usage and performance on high-"
+"bandwidth routers"
+msgstr ""
+
+#: i2p2www/blog/2012/09/21/0.9.2-Release.rst:35
+msgid "Fix problems in UDP for routers using a reduced-MTU connection, e.g. a VPN"
+msgstr ""
+
+#: i2p2www/blog/2012/09/21/0.9.2-Release.rst:36
+msgid "Fix i2psnark bug that prevented a completion announcement to the tracker"
+msgstr ""
+
+#: i2p2www/blog/2012/09/21/0.9.2-Release.rst:37
+msgid "Fix a lock contention problem in i2ptunnel"
+msgstr ""
+
+#: i2p2www/blog/2012/09/21/0.9.2-Release.rst:38
+msgid "Fix some OSX installation issues"
+msgstr ""
+
+#: i2p2www/blog/2012/09/21/0.9.2-Release.rst:39
+msgid "Remove uses of direct byte buffers that may have been leaking"
+msgstr ""
+
+#: i2p2www/blog/2012/09/21/0.9.2-Release.rst:43
+msgid "Reduce overhead in network messages"
+msgstr ""
+
+#: i2p2www/blog/2012/09/21/0.9.2-Release.rst:44
+msgid "Add \"universal\" theme support"
+msgstr ""
+
+#: i2p2www/blog/2012/09/21/0.9.2-Release.rst:45
+msgid "Theme updates"
+msgstr ""
+
+#: i2p2www/blog/2012/09/21/0.9.2-Release.rst:46
+msgid "Add a jbigi library for Raspberry Pi"
+msgstr ""
+
+#: i2p2www/blog/2012/09/21/0.9.2-Release.rst:47
+msgid "New Scala unit test framework"
+msgstr ""
+
+#: i2p2www/blog/2012/09/21/0.9.2-Release.rst:48
+msgid "Translation updates for Czech, Dutch, German, and Greek"
+msgstr ""
+
+#: i2p2www/blog/2012/09/21/0.9.2-Release.rst:49
+msgid "Update wrapper to 3.5.15 (new installs and PPA only)"
+msgstr ""
+
+#: i2p2www/blog/2012/09/21/0.9.2-Release.rst:50
+#: i2p2www/blog/2012/10/27/0.9.3-Release.rst:53
+#: i2p2www/blog/2012/12/17/0.9.4-Release.rst:63
+#: i2p2www/blog/2013/03/08/0.9.5-Release.rst:53
+#: i2p2www/blog/2013/05/28/0.9.6-Release.rst:108
+#: i2p2www/blog/2013/07/15/0.9.7-Release.rst:77
+#: i2p2www/blog/2013/09/30/0.9.8-Release.rst:127
+#: i2p2www/blog/2013/12/07/0.9.9-Release.rst:74
+#: i2p2www/blog/2014/01/22/0.9.10-Release.rst:62
+#: i2p2www/blog/2014/02/08/0.9.11-Release.rst:57
+#: i2p2www/blog/2014/03/31/0.9.12-Release.rst:100
+#: i2p2www/blog/2014/05/22/0.9.13-Release.rst:58
+#: i2p2www/blog/2014/07/26/0.9.14-Release.rst:70
+#: i2p2www/blog/2014/08/09/0.9.14.1-Release.rst:49
+#: i2p2www/blog/2014/11/01/0.9.16-Release.rst:83
+#: i2p2www/blog/2014/11/30/0.9.17-Release.rst:78
+#: i2p2www/blog/2015/02/22/0.9.18-Release.rst:58
+#: i2p2www/blog/2015/04/12/0.9.19-Release.rst:66
+#: i2p2www/blog/2015/06/02/0.9.20-Release.rst:96
+#: i2p2www/blog/2015/07/31/0.9.21-Release.rst:72
+#: i2p2www/blog/2015/09/12/0.9.22-Release.rst:53
+#: i2p2www/blog/2015/11/19/0.9.23-Release.rst:112
+#: i2p2www/blog/2016/01/27/0.9.24-Release.rst:97
+#: i2p2www/blog/2016/03/22/0.9.25-Release.rst:68
+#: i2p2www/blog/2016/06/07/0.9.26-Release.rst:88
+#: i2p2www/blog/2016/10/17/0.9.27-Release.rst:65
+#: i2p2www/blog/2016/12/12/0.9.28-Release.rst:95
+#: i2p2www/blog/2017/02/27/0.9.29-Release.rst:69
+#: i2p2www/blog/2017/05/03/0.9.30-Release.rst:94
+#: i2p2www/blog/2017/08/07/0.9.31-Release.rst:60
+#: i2p2www/blog/2017/11/07/0.9.32-Release.rst:49
+#: i2p2www/blog/2018/04/10/0.9.34-Release.rst:55
+#: i2p2www/blog/2018/06/26/0.9.35-Release.rst:71
+msgid "Update GeoIP data (new installs and PPA only)"
+msgstr ""
+
+#: i2p2www/blog/2012/10/27/0.9.3-Release.rst:2
+msgid "0.9.3 Release"
+msgstr ""
+
+#: i2p2www/blog/2012/10/27/0.9.3-Release.rst:7
+#: i2p2www/blog/2012/10/27/0.9.3-Release.rst:9
+msgid ""
+"0.9.3 includes extensive low-level changes to the queueing of messages in"
+" the router.  We implement the CoDel Active Queue Management (AQM) "
+"algorithm.  We also unify the queueing and priority mechanisms in the "
+"transports to aid diagnosis and reduce network latency.  Work continues "
+"on fixing UDP transport bugs and making UDP more resistant to attacks.  "
+"There are more changes to improve the performance of the router and "
+"reduce its memory usage.  Also, we enable i2psnark's DHT support, "
+"introduced last release, by default."
+msgstr ""
+
+#: i2p2www/blog/2012/10/27/0.9.3-Release.rst:26
+msgid "Active Queue Management"
+msgstr ""
+
+#: i2p2www/blog/2012/10/27/0.9.3-Release.rst:27
+msgid "Priority queues"
+msgstr ""
+
+#: i2p2www/blog/2012/10/27/0.9.3-Release.rst:28
+msgid "I2PSnark DHT: Several bug fixes, enable by default."
+msgstr ""
+
+#: i2p2www/blog/2012/10/27/0.9.3-Release.rst:32
+msgid ""
+"Several SSU fixes including memory leak, and better handling of routers "
+"behind firewalls that change UDP ports; additional defenses for malicious"
+" packets."
+msgstr ""
+
+#: i2p2www/blog/2012/10/27/0.9.3-Release.rst:33
+msgid "Fix piece selection (rarest-first) bugs in i2psnark"
+msgstr ""
+
+#: i2p2www/blog/2012/10/27/0.9.3-Release.rst:34
+msgid "Fix bug causing multiple browsers to open at startup"
+msgstr ""
+
+#: i2p2www/blog/2012/10/27/0.9.3-Release.rst:38
+msgid "Improvements in caching"
+msgstr ""
+
+#: i2p2www/blog/2012/10/27/0.9.3-Release.rst:39
+msgid "Several synchronization fixes and lock contention reduction"
+msgstr ""
+
+#: i2p2www/blog/2012/10/27/0.9.3-Release.rst:40
+msgid "Major reduction in SSU buffers memory use"
+msgstr ""
+
+#: i2p2www/blog/2012/10/27/0.9.3-Release.rst:41
+msgid ""
+"Fix streaming connection timeout back to 1 minute, was inadvertently "
+"changed to 5 minutes; set i2ptunnel server read timeout to 5 minutes, was"
+" unlimited"
+msgstr ""
+
+#: i2p2www/blog/2012/10/27/0.9.3-Release.rst:42
+msgid "Improved defenses in i2ptunnel for \"darkloris\""
+msgstr ""
+
+#: i2p2www/blog/2012/10/27/0.9.3-Release.rst:43
+msgid "More validation at torrent creation in i2psnark"
+msgstr ""
+
+#: i2p2www/blog/2012/10/27/0.9.3-Release.rst:44
+msgid "Several parameter changes in SSU to improve throughput"
+msgstr ""
+
+#: i2p2www/blog/2012/10/27/0.9.3-Release.rst:45
+msgid ""
+"New event log for major events including restarts; show multiple restart "
+"lines on graphs"
+msgstr ""
+
+#: i2p2www/blog/2012/10/27/0.9.3-Release.rst:46
+msgid "Remove duplicate messages from logs"
+msgstr ""
+
+#: i2p2www/blog/2012/10/27/0.9.3-Release.rst:47
+msgid "Don't respond to blocked streaming connections with a reset, just drop"
+msgstr ""
+
+#: i2p2www/blog/2012/10/27/0.9.3-Release.rst:48
+msgid "Remove all uses of inefficient SimpleTimer"
+msgstr ""
+
+#: i2p2www/blog/2012/10/27/0.9.3-Release.rst:49
+msgid "More checks for valid IPs and ports entered in console"
+msgstr ""
+
+#: i2p2www/blog/2012/10/27/0.9.3-Release.rst:50
+msgid "Fix bug that wasted a lot of entropy"
+msgstr ""
+
+#: i2p2www/blog/2012/10/27/0.9.3-Release.rst:51
+msgid "Translation updates: Italian, Portuguese, Spanish, Swedish"
+msgstr ""
+
+#: i2p2www/blog/2012/10/27/0.9.3-Release.rst:52
+msgid "Add non-NIO configuration in jetty.xml, recommended for Java 5"
+msgstr ""
+
+#: i2p2www/blog/2012/12/17/0.9.4-Release.rst:2
+msgid "0.9.4 Release"
+msgstr ""
+
+#: i2p2www/blog/2012/12/17/0.9.4-Release.rst:7
+#: i2p2www/blog/2012/12/17/0.9.4-Release.rst:9
+msgid ""
+"0.9.4 includes a fix for a network capacity bug, introduced in 0.9.2, "
+"that was reducing network performance and reliability. It also includes "
+"major changes in the in-network update system, and adds the capability to"
+" update via in-network torrents."
+msgstr ""
+
+#: i2p2www/blog/2012/12/17/0.9.4-Release.rst:13
+msgid ""
+"We fixed several bugs in the i2psnark DHT implementation that was "
+"introduced\n"
+"last release. For those of you using console or http proxy passwords,\n"
+"we converted to the more-secure digest method and improved the security "
+"for console forms."
+msgstr ""
+
+#: i2p2www/blog/2012/12/17/0.9.4-Release.rst:19
+msgid ""
+"For those of you already running development builds, your router should "
+"automatically\n"
+"update to 0.9.4-0 using the new in-network torrent facility.\n"
+"For those running 0.9.3-0, you will update normally using in-network "
+"HTTP, and\n"
+"we will have more information for you when we release 0.9.5."
+msgstr ""
+
+#: i2p2www/blog/2012/12/17/0.9.4-Release.rst:36
+msgid ""
+"Big rework of the update system; Preliminary support for updates via "
+"i2psnark"
+msgstr ""
+
+#: i2p2www/blog/2012/12/17/0.9.4-Release.rst:37
+msgid "Add per-destination outbound priorities"
+msgstr ""
+
+#: i2p2www/blog/2012/12/17/0.9.4-Release.rst:41
+msgid ""
+"Fix major bug that reduced SSU connection limits which reduced tunnel "
+"build success rates"
+msgstr ""
+
+#: i2p2www/blog/2012/12/17/0.9.4-Release.rst:42
+msgid "Fix bug with external I2CP that prevented some external apps from working"
+msgstr ""
+
+#: i2p2www/blog/2012/12/17/0.9.4-Release.rst:43
+msgid "Fixed several bugs in i2psnark DHT"
+msgstr ""
+
+#: i2p2www/blog/2012/12/17/0.9.4-Release.rst:44
+msgid "Fixed bug in i2psnark PEX that inflated peer counts"
+msgstr ""
+
+#: i2p2www/blog/2012/12/17/0.9.4-Release.rst:45
+msgid "Handle dropped I2CP messages better"
+msgstr ""
+
+#: i2p2www/blog/2012/12/17/0.9.4-Release.rst:46
+msgid "Reduce overhead of I2CP messages"
+msgstr ""
+
+#: i2p2www/blog/2012/12/17/0.9.4-Release.rst:47
+msgid "Enforce max size in transport outbound message queues"
+msgstr ""
+
+#: i2p2www/blog/2012/12/17/0.9.4-Release.rst:48
+msgid "Fixes for Windows eepget.bat (new installs and PPA only)"
+msgstr ""
+
+#: i2p2www/blog/2012/12/17/0.9.4-Release.rst:49
+msgid "Fix a bug that would drop messages of exactly 512 bytes in SSU"
+msgstr ""
+
+#: i2p2www/blog/2012/12/17/0.9.4-Release.rst:53
+msgid ""
+"More performance improvements, memory reduction, and object churn "
+"reduction"
+msgstr ""
+
+#: i2p2www/blog/2012/12/17/0.9.4-Release.rst:54
+msgid "Better detection of network disconnections"
+msgstr ""
+
+#: i2p2www/blog/2012/12/17/0.9.4-Release.rst:55
+msgid "Further improvements in the SSU transport"
+msgstr ""
+
+#: i2p2www/blog/2012/12/17/0.9.4-Release.rst:56
+msgid "Add console password form"
+msgstr ""
+
+#: i2p2www/blog/2012/12/17/0.9.4-Release.rst:57
+msgid ""
+"Convert http proxy and console from basic to digest authentication for "
+"added security"
+msgstr ""
+
+#: i2p2www/blog/2012/12/17/0.9.4-Release.rst:58
+msgid ""
+"Improved verification of console form submissions, using jsp sessions. "
+"Cookies may now be required on forms, except when the console password is"
+" enabled"
+msgstr ""
+
+#: i2p2www/blog/2012/12/17/0.9.4-Release.rst:59
+msgid ""
+"Initial work on new interfaces to manage applications started via "
+"clients.config"
+msgstr ""
+
+#: i2p2www/blog/2012/12/17/0.9.4-Release.rst:60
+msgid "Increase minimum peer port to 1024"
+msgstr ""
+
+#: i2p2www/blog/2012/12/17/0.9.4-Release.rst:61
+msgid "Increase granularity of bandwidth limiter for smoother transmissions"
+msgstr ""
+
+#: i2p2www/blog/2012/12/17/0.9.4-Release.rst:62
+msgid ""
+"Translation updates: Chinese, French, German, Italian, Polish, "
+"Portuguese, Swedish, and Ukrainian"
+msgstr ""
+
+#: i2p2www/blog/2012/12/17/0.9.4-Release.rst:64
+msgid "Update wrapper to 3.5.16 (new installs and PPA only)"
+msgstr ""
+
+#: i2p2www/blog/2012/12/17/0.9.4-Release.rst:65
+msgid "New ARMv6 wrapper for Raspberry Pi"
+msgstr ""
+
+#: i2p2www/blog/2013/03/08/0.9.5-Release.rst:2
+msgid "0.9.5 Release"
+msgstr ""
+
+#: i2p2www/blog/2013/03/08/0.9.5-Release.rst:7
+#: i2p2www/blog/2013/03/08/0.9.5-Release.rst:9
+msgid ""
+"0.9.5 includes bug fixes and defenses for some issues and vulnerabilities"
+" that are being investigated by researchers at UCSB. We continue to work "
+"with them on additional improvements. This is a good opportunity to "
+"remind the community that while our network continues to grow rapidly, it"
+" is still relatively small. There may be multiple weaknesses or bugs that"
+" could compromise your anonymity. Help us grow the network by spreading "
+"the word and contributing where you can."
+msgstr ""
+
+#: i2p2www/blog/2013/03/08/0.9.5-Release.rst:13
+#, python-format
+msgid ""
+"In this upgrade cycle, a random 1%(pc)s of routers, (plus all routers "
+"running a\n"
+"development build) will attempt to update via the experimental in-network"
+" bittorrent\n"
+"with i2psnark. If this doesn't work, it should fall back to standard in-"
+"network HTTP update."
+msgstr ""
+
+#: i2p2www/blog/2013/03/08/0.9.5-Release.rst:27
+msgid "Defenses and Bug Fixes"
+msgstr ""
+
+#: i2p2www/blog/2013/03/08/0.9.5-Release.rst:29
+msgid "Fix router bug causing lockup when using iMule"
+msgstr ""
+
+#: i2p2www/blog/2013/03/08/0.9.5-Release.rst:30
+msgid "Recognize, handle, reject duplicate tunnel IDs"
+msgstr ""
+
+#: i2p2www/blog/2013/03/08/0.9.5-Release.rst:31
+msgid "Fix changing of the log file name"
+msgstr ""
+
+#: i2p2www/blog/2013/03/08/0.9.5-Release.rst:32
+msgid "Prevent hashcode attack in session tags"
+msgstr ""
+
+#: i2p2www/blog/2013/03/08/0.9.5-Release.rst:33
+msgid "Add build request throttler based on previous hop"
+msgstr ""
+
+#: i2p2www/blog/2013/03/08/0.9.5-Release.rst:34
+msgid "Limit concurrent next-hop lookups"
+msgstr ""
+
+#: i2p2www/blog/2013/03/08/0.9.5-Release.rst:35
+msgid "Catch exceptions storing nonces in console"
+msgstr ""
+
+#: i2p2www/blog/2013/03/08/0.9.5-Release.rst:36
+msgid "Fix saving graph settings in console"
+msgstr ""
+
+#: i2p2www/blog/2013/03/08/0.9.5-Release.rst:37
+msgid "Fix eepget generation of URLs when not proxied"
+msgstr ""
+
+#: i2p2www/blog/2013/03/08/0.9.5-Release.rst:38
+msgid ""
+"Encrypt database lookup messages end-to-end when sent through exploratory"
+" tunnels"
+msgstr ""
+
+#: i2p2www/blog/2013/03/08/0.9.5-Release.rst:39
+msgid "Don't use multiple floodfills from the same /16 in a query"
+msgstr ""
+
+#: i2p2www/blog/2013/03/08/0.9.5-Release.rst:40
+msgid "Randomize delay before verifying floodfill store"
+msgstr ""
+
+#: i2p2www/blog/2013/03/08/0.9.5-Release.rst:41
+msgid "Increase number of floodfills"
+msgstr ""
+
+#: i2p2www/blog/2013/03/08/0.9.5-Release.rst:45
+msgid "Improve support for mobile browsers"
+msgstr ""
+
+#: i2p2www/blog/2013/03/08/0.9.5-Release.rst:46
+msgid "Partial defenses for UCSB attacks"
+msgstr ""
+
+#: i2p2www/blog/2013/03/08/0.9.5-Release.rst:47
+msgid "Add announce list support to i2psnark"
+msgstr ""
+
+#: i2p2www/blog/2013/03/08/0.9.5-Release.rst:48
+msgid "Jetty: upgrade Apache Tomcat to 6.0.36"
+msgstr ""
+
+#: i2p2www/blog/2013/03/08/0.9.5-Release.rst:49
+msgid "Split router info files into multiple subdirectories"
+msgstr ""
+
+#: i2p2www/blog/2013/03/08/0.9.5-Release.rst:50
+msgid "Add IP to hostname mapping option in SOCKS"
+msgstr ""
+
+#: i2p2www/blog/2013/03/08/0.9.5-Release.rst:51
+msgid "Improve PRNG seeding"
+msgstr ""
+
+#: i2p2www/blog/2013/03/08/0.9.5-Release.rst:52
+msgid ""
+"Translation updates: French, German, Hungarian, Italian, Norwegian, "
+"Polish, Portuguese, Russian, Swedish"
+msgstr ""
+
+#: i2p2www/blog/2013/03/08/0.9.5-Release.rst:54
+msgid "Update wrapper to 3.5.17 (new installs and PPA only)"
+msgstr ""
+
+#: i2p2www/blog/2013/05/28/0.9.6-Release.rst:2
+msgid "0.9.6 Release"
+msgstr ""
+
+#: i2p2www/blog/2013/05/28/0.9.6-Release.rst:7
+#: i2p2www/blog/2013/05/28/0.9.6-Release.rst:9
+msgid ""
+"0.9.6 includes bug fixes and an update from Jetty 6.1.26 (2010-11-10) to "
+"Jetty 7.6.10 (2013-03-12). See below for important information on the "
+"Jetty update. The Jetty 7 series is actively maintained and we plan to "
+"stay current with it in future I2P releases."
+msgstr ""
+
+#: i2p2www/blog/2013/05/28/0.9.6-Release.rst:13
+msgid ""
+"Most users will update via HTTP. Those running development builds will "
+"attempt to update via the\n"
+"experimental in-network bittorrent with i2psnark. We've fixed some bugs "
+"that will enable more users\n"
+"to update via torrent in the 0.9.7 update cycle."
+msgstr ""
+
+#: i2p2www/blog/2013/05/28/0.9.6-Release.rst:25
+msgid "Important fix for Windows Eepsites, first install 0.9.5 only"
+msgstr ""
+
+#: i2p2www/blog/2013/05/28/0.9.6-Release.rst:27
+msgid ""
+"If you first installed I2P with version 0.9.5, on Windows only, we "
+"recommend that you follow the\n"
+"following instructions to fix your eepsite location **before** you update"
+" to 0.9.6.\n"
+"Only original installations of 0.9.5-0 on Windows are affected by this "
+"issue. If your router version\n"
+"is 0.9.5-0-win1, you already have the fix and need not take any action."
+msgstr ""
+
+#: i2p2www/blog/2013/05/28/0.9.6-Release.rst:34
+msgid "See `this page`_ for instructions."
+msgstr ""
+
+#: i2p2www/blog/2013/05/28/0.9.6-Release.rst:38
+msgid "`this page`"
+msgstr ""
+
+#: i2p2www/blog/2013/05/28/0.9.6-Release.rst:40
+msgid "Jetty 7 Migration Details"
+msgstr ""
+
+#: i2p2www/blog/2013/05/28/0.9.6-Release.rst:42
+msgid ""
+"For most people, the update should just work. If you have multiple Jetty "
+"eepsites,\n"
+"OR have made changes to jetty.xml or other Jetty configuration files, "
+"including changing the port\n"
+"from 7658, you MUST take manual action AFTER updating."
+msgstr ""
+
+#: i2p2www/blog/2013/05/28/0.9.6-Release.rst:48
+msgid ""
+"After update, the router will migrate your jetty.xml files to the new "
+"Jetty 7 format."
+msgstr ""
+
+#: i2p2www/blog/2013/05/28/0.9.6-Release.rst:50
+msgid ""
+"The migration resets the port to 7658. If you have more than one Jetty "
+"eepsite, OR your eepsite\n"
+"  is NOT on port 7658, OR you have made other modifications to jetty.xml "
+"(for example changing the\n"
+"  listen address from 127.0.0.1 to 0.0.0.0), you MUST edit the jetty.xml "
+"file for each eepsite to fix them up\n"
+"  after updating, and restart again."
+msgstr ""
+
+#: i2p2www/blog/2013/05/28/0.9.6-Release.rst:55
+msgid ""
+"**The following files will be backed up with a ".jetty6" suffix"
+" and then migrated.**\n"
+"If you have made local changes, you may have to edit them manually and "
+"restart.\n"
+"See http://wiki.eclipse.org/Jetty for assistance in configuring Jetty 7."
+msgstr ""
+
+#: i2p2www/blog/2013/05/28/0.9.6-Release.rst:69
+msgid "Plugins"
+msgstr "Qoşmalar"
+
+#: i2p2www/blog/2013/05/28/0.9.6-Release.rst:71
+msgid "Most plugins should work fine with Jetty 7."
+msgstr ""
+
+#: i2p2www/blog/2013/05/28/0.9.6-Release.rst:75
+msgid ""
+"The I2PControl and zzzot plugins must be updated. Your router should "
+"download and install the new versions shortly after starting 0.9.6."
+msgstr ""
+
+#: i2p2www/blog/2013/05/28/0.9.6-Release.rst:77
+msgid "If a plugin does not work, please contact the maintainer for that plugin."
+msgstr ""
+
+#: i2p2www/blog/2013/05/28/0.9.6-Release.rst:83
+msgid "Several bugs with Windows installation (see above)"
+msgstr ""
+
+#: i2p2www/blog/2013/05/28/0.9.6-Release.rst:84
+msgid "Fix default form action in i2ptunnel"
+msgstr ""
+
+#: i2p2www/blog/2013/05/28/0.9.6-Release.rst:85
+msgid "Fix links on iframed console pages"
+msgstr ""
+
+#: i2p2www/blog/2013/05/28/0.9.6-Release.rst:86
+msgid "Better detection of 64-bit Windows to prevent crashes by systray"
+msgstr ""
+
+#: i2p2www/blog/2013/05/28/0.9.6-Release.rst:87
+msgid "Fix bug preventing router update via torrent"
+msgstr ""
+
+#: i2p2www/blog/2013/05/28/0.9.6-Release.rst:88
+msgid "Several SSU fixes for NATs that change UDP ports"
+msgstr ""
+
+#: i2p2www/blog/2013/05/28/0.9.6-Release.rst:89
+msgid ""
+"Ignore unsupported IPs in RouterInfos when selecting an address (prep for"
+" IPv6)"
+msgstr ""
+
+#: i2p2www/blog/2013/05/28/0.9.6-Release.rst:90
+msgid ""
+"Ignore unused option bits in Database Lookup Message (prep for requesting"
+" encrypted response)"
+msgstr ""
+
+#: i2p2www/blog/2013/05/28/0.9.6-Release.rst:91
+msgid "Fix HTTP proxy error response for malformed URIs"
+msgstr ""
+
+#: i2p2www/blog/2013/05/28/0.9.6-Release.rst:92
+msgid "Recognize UPnP devices without port forwarding capability"
+msgstr ""
+
+#: i2p2www/blog/2013/05/28/0.9.6-Release.rst:96
+msgid "Jetty 7.6.10 (see above for migration information)"
+msgstr ""
+
+#: i2p2www/blog/2013/05/28/0.9.6-Release.rst:97
+msgid "Limit page size in i2psnark"
+msgstr ""
+
+#: i2p2www/blog/2013/05/28/0.9.6-Release.rst:98
+msgid "Add data directory and page size configuration to i2psnark"
+msgstr ""
+
+#: i2p2www/blog/2013/05/28/0.9.6-Release.rst:99
+msgid "Support multiple i2psnark instances"
+msgstr ""
+
+#: i2p2www/blog/2013/05/28/0.9.6-Release.rst:100
+msgid "Piece size adjustments in i2psnark"
+msgstr ""
+
+#: i2p2www/blog/2013/05/28/0.9.6-Release.rst:101
+msgid "Add more graphing support for combined bandwidth graph"
+msgstr ""
+
+#: i2p2www/blog/2013/05/28/0.9.6-Release.rst:102
+msgid "Block b32.i2p supercookies"
+msgstr ""
+
+#: i2p2www/blog/2013/05/28/0.9.6-Release.rst:103
+msgid "Allow stopping clients on /configclients"
+msgstr ""
+
+#: i2p2www/blog/2013/05/28/0.9.6-Release.rst:104
+msgid "Check for nonce count replays in HTTP client"
+msgstr ""
+
+#: i2p2www/blog/2013/05/28/0.9.6-Release.rst:105
+msgid "Support SASL authentication in IRC proxy"
+msgstr ""
+
+#: i2p2www/blog/2013/05/28/0.9.6-Release.rst:106
+msgid "Several cleanups and minor fixes in the update manager"
+msgstr ""
+
+#: i2p2www/blog/2013/05/28/0.9.6-Release.rst:107
+msgid "Translation updates: German, Portuguese, Russian, Spanish, and Swedish"
+msgstr ""
+
+#: i2p2www/blog/2013/07/15/0.9.7-Release.rst:2
+msgid "0.9.7 Release"
+msgstr ""
+
+#: i2p2www/blog/2013/07/15/0.9.7-Release.rst:7
+#: i2p2www/blog/2013/07/15/0.9.7-Release.rst:9
+msgid "0.9.7 includes significant bug fixes and improvements."
+msgstr ""
+
+#: i2p2www/blog/2013/07/15/0.9.7-Release.rst:11
+msgid ""
+"For the first time, class 'N' routers (those with a minimumum of 128 "
+"KBytes/sec of shared bandwidth)\n"
+"will automatically become floodfill (previously it was only 'O' routers "
+"with 256 KBps). This will\n"
+"increase the floodfill population for additional resistance to certain "
+"attacks (see below). Floodfill routers\n"
+"don't consume much additional bandwidth, but they do tend to use "
+"additional memory and concurrent\n"
+"connections. If you do not wish your router to become floodfill, set the "
+"advanced configuration\n"
+"router.floodfillParticipant=false ."
+msgstr ""
+
+#: i2p2www/blog/2013/07/15/0.9.7-Release.rst:20
+#, python-format
+msgid ""
+"As we think the last release fixed the experimental update-via-torrent "
+"bugs, 3%(pc)s of routers should\n"
+"update over in-network bittorrent this cycle."
+msgstr ""
+
+#: i2p2www/blog/2013/07/15/0.9.7-Release.rst:25
+msgid ""
+"Plugin update checks, possibly broken for several releases, are fixed. "
+"Your plugins should once again\n"
+"auto-update after updating the router."
+msgstr ""
+
+#: i2p2www/blog/2013/07/15/0.9.7-Release.rst:30
+msgid ""
+"We fixed a major streaming timer bug that contributed to frequent IRC "
+"disconnects."
+msgstr ""
+
+#: i2p2www/blog/2013/07/15/0.9.7-Release.rst:34
+msgid ""
+"This release contains additional mitigations for the `\"practical "
+"attacks\" paper`_.\n"
+"However, we have a lot more work to do to resist Sybil attacks on the "
+"floodfills, and resist\n"
+"traffic analysis at the gateways and endpoints of exploratory tunnels.\n"
+"It's a good reminder for everybody that our network is still relatively "
+"small and vulnerable.\n"
+"We don't currently recommend any uses that would put anybody in serious "
+"jeopardy.\n"
+"We'll keep working to improve it... please keep working to spread the "
+"word. A bigger network is a better network."
+msgstr ""
+
+#: i2p2www/blog/2013/07/15/0.9.7-Release.rst:43
+msgid "`\"practical attacks\" paper`"
+msgstr ""
+
+#: i2p2www/blog/2013/07/15/0.9.7-Release.rst:47
+#: i2p2www/blog/2013/08/10/0.9.7.1-Release.rst:15
+#: i2p2www/blog/2013/09/30/0.9.8-Release.rst:107
+#: i2p2www/blog/2013/12/07/0.9.9-Release.rst:28
+#: i2p2www/blog/2014/01/22/0.9.10-Release.rst:36
+#: i2p2www/blog/2014/02/08/0.9.11-Release.rst:37
+#: i2p2www/blog/2014/03/31/0.9.12-Release.rst:67
+msgid "Anonymity Improvements"
+msgstr ""
+
+#: i2p2www/blog/2013/07/15/0.9.7-Release.rst:49
+msgid "End-to-end encryption of responses to leaseset lookups"
+msgstr ""
+
+#: i2p2www/blog/2013/07/15/0.9.7-Release.rst:50
+msgid "Expand floodfill pool by enabling class 'N' floodfills"
+msgstr ""
+
+#: i2p2www/blog/2013/07/15/0.9.7-Release.rst:51
+msgid "Randomize padding inside encrypted SSU packets"
+msgstr ""
+
+#: i2p2www/blog/2013/07/15/0.9.7-Release.rst:52
+msgid "Preparation for better SSU protocol obfuscation"
+msgstr ""
+
+#: i2p2www/blog/2013/07/15/0.9.7-Release.rst:56
+msgid "Fix newer lease sets not getting stored or published"
+msgstr ""
+
+#: i2p2www/blog/2013/07/15/0.9.7-Release.rst:57
+msgid ""
+"Fix classpath bug when used with 4-year-old installations, causing the "
+"console not to start"
+msgstr ""
+
+#: i2p2www/blog/2013/07/15/0.9.7-Release.rst:58
+msgid "Fix addressbook database bug preventing update of the reverse index"
+msgstr ""
+
+#: i2p2www/blog/2013/07/15/0.9.7-Release.rst:59
+msgid ""
+"Fix i2psnark bug that changed the infohash of torrents created by Robert "
+"and fetched via magnet link"
+msgstr ""
+
+#: i2p2www/blog/2013/07/15/0.9.7-Release.rst:60
+msgid "Fix version checking for plugins"
+msgstr ""
+
+#: i2p2www/blog/2013/07/15/0.9.7-Release.rst:61
+msgid ""
+"Fix a streaming timer bug causing frequent IRC disconnects (also affects "
+"other close-on-idle tunnels)"
+msgstr ""
+
+#: i2p2www/blog/2013/07/15/0.9.7-Release.rst:65
+msgid "Don't install as a service on Windows by default"
+msgstr ""
+
+#: i2p2www/blog/2013/07/15/0.9.7-Release.rst:66
+msgid "Reduce transport idle timeouts"
+msgstr ""
+
+#: i2p2www/blog/2013/07/15/0.9.7-Release.rst:67
+msgid "Reduce tunnels on idle in i2psnark"
+msgstr ""
+
+#: i2p2www/blog/2013/07/15/0.9.7-Release.rst:68
+msgid "Change default in i2ptunnel GUI to 3 hops"
+msgstr ""
+
+#: i2p2www/blog/2013/07/15/0.9.7-Release.rst:69
+msgid "IE 10 support"
+msgstr ""
+
+#: i2p2www/blog/2013/07/15/0.9.7-Release.rst:70
+msgid ""
+"Individual expiration times in leases, for efficiency on destinations "
+"with a high number of tunnels"
+msgstr ""
+
+#: i2p2www/blog/2013/07/15/0.9.7-Release.rst:71
+msgid "Low-level encryption and XOR speedups"
+msgstr ""
+
+#: i2p2www/blog/2013/07/15/0.9.7-Release.rst:72
+msgid "Jetty 7.6.11"
+msgstr ""
+
+#: i2p2www/blog/2013/07/15/0.9.7-Release.rst:73
+msgid "Tomcat 6.0.37"
+msgstr ""
+
+#: i2p2www/blog/2013/07/15/0.9.7-Release.rst:74
+msgid "Translation updates: Chinese, French, German, Portuguese, Russian, Spanish"
+msgstr ""
+
+#: i2p2www/blog/2013/07/15/0.9.7-Release.rst:75
+msgid "New Turkish translation"
+msgstr ""
+
+#: i2p2www/blog/2013/07/15/0.9.7-Release.rst:76
+msgid "Wrapper 3.5.19 (new installs and PPA only)"
+msgstr ""
+
+#: i2p2www/blog/2013/08/10/0.9.7.1-Release.rst:2
+msgid "0.9.7.1 Release"
+msgstr ""
+
+#: i2p2www/blog/2013/08/10/0.9.7.1-Release.rst:7
+#: i2p2www/blog/2013/08/10/0.9.7.1-Release.rst:9
+msgid ""
+"This unscheduled release disables the RouterInfo verification messages "
+"that were used in the attack published in the UCSB paper, which should "
+"make correlating a LeaseSet and a Router much more difficult. We have "
+"also included a limited number of other fixes listed below. Our 0.9.8 "
+"release, which will include IPv6 support, is still on-schedule for late "
+"September."
+msgstr ""
+
+#: i2p2www/blog/2013/08/10/0.9.7.1-Release.rst:11
+msgid "As usual, we recommend that all users update to this release."
+msgstr ""
+
+#: i2p2www/blog/2013/08/10/0.9.7.1-Release.rst:17
+msgid "Disable RouterInfo verification messages"
+msgstr ""
+
+#: i2p2www/blog/2013/08/10/0.9.7.1-Release.rst:21
+msgid "Extend inbound tunnel expiration"
+msgstr ""
+
+#: i2p2www/blog/2013/08/10/0.9.7.1-Release.rst:22
+msgid "i2prouter: bashism fix"
+msgstr ""
+
+#: i2p2www/blog/2013/08/10/0.9.7.1-Release.rst:23
+msgid "i2psnark: increase max piece size, mime type updates"
+msgstr ""
+
+#: i2p2www/blog/2013/08/10/0.9.7.1-Release.rst:24
+msgid "New reseed host"
+msgstr ""
+
+#: i2p2www/blog/2013/08/10/0.9.7.1-Release.rst:25
+msgid "New update hosts, thanks Meeh and dg"
+msgstr ""
+
+#: i2p2www/blog/2013/08/10/0.9.7.1-Release.rst:26
+msgid "Streaming: RTO changes"
+msgstr ""
+
+#: i2p2www/blog/2013/08/10/0.9.7.1-Release.rst:27
+msgid "Updater: Increase update-via-torrent to 30 percent"
+msgstr ""
+
+#: i2p2www/blog/2013/08/10/0.9.7.1-Release.rst:28
+msgid "UPnP fix for some hardware"
+msgstr ""
+
+#: i2p2www/blog/2013/09/30/0.9.8-Release.rst:2
+msgid "0.9.8 Release"
+msgstr ""
+
+#: i2p2www/blog/2013/09/30/0.9.8-Release.rst:7
+#: i2p2www/blog/2013/09/30/0.9.8-Release.rst:9
+msgid ""
+"0.9.8 includes the long-awaited support for IPv6. It's enabled by "
+"default, but of course you need a public IPv6 address to use it. "
+"Configuration is on the 'network' configuration tab in your console. We "
+"also have anonymity improvements including padding of SSU packets and "
+"longer router private keys."
+msgstr ""
+
+#: i2p2www/blog/2013/09/30/0.9.8-Release.rst:11
+#, python-format
+msgid "30%(pc)s of you will update via in-network torrent in this update cycle."
+msgstr ""
+
+#: i2p2www/blog/2013/09/30/0.9.8-Release.rst:13
+msgid "IPv6 Details"
+msgstr ""
+
+#: i2p2www/blog/2013/09/30/0.9.8-Release.rst:15
+msgid ""
+"IPv6 is enabled and preferred by default. If you have a public IPv6 "
+"address \n"
+"and you are connecting to another router with a published IPv6 address, "
+"it will \n"
+"connect via IPv6. There is a new IPv6 configuration section on /confignet"
+" in \n"
+"the router console. If IPv6 is causing problems you may disable it there."
+msgstr ""
+
+#: i2p2www/blog/2013/09/30/0.9.8-Release.rst:22
+msgid ""
+"As a part of the IPv6 development effort, I2P now supports multiple \n"
+"published IP addresses. If you have multiple public IP addresses (IPv4, "
+"IPv6, \n"
+"or both), you may enable or disable them individually on /confignet. The"
+" \n"
+"default is to use the first IPv4 and IPv6 addresses it discovers. If you "
+"have \n"
+"multiple addresses you should review the configuration on /confignet and "
+"adjust \n"
+"it if necessary.\n"
+"Note that while you may enable multiple IPv4 and IPv6 addresses on "
+"/confignet,\n"
+"we recommend that you use only one IPv4 and one IPv6 address. There are\n"
+"bugs still to be fixed with multiple addresses of each type."
+msgstr ""
+
+#: i2p2www/blog/2013/09/30/0.9.8-Release.rst:34
+msgid ""
+"While IPv6 support was designed and developed over several years, it has"
+" \n"
+"only been tested by a limited number of users and is still beta. If you "
+"do have \n"
+"a public IPv6 address, please monitor your router and the logs for "
+"problems, \n"
+"and disable it necessary. Please report any bugs on \n"
+"http://trac.i2p2.i2p."
+msgstr ""
+
+#: i2p2www/blog/2013/09/30/0.9.8-Release.rst:42
+msgid "Rekeying Details"
+msgstr ""
+
+#: i2p2www/blog/2013/09/30/0.9.8-Release.rst:44
+msgid ""
+"For those of you running I2P on faster hardware (generally, 64-bit x86) "
+"the \n"
+"router will generate a new identity using longer keys. This will "
+"substantially \n"
+"reduce your participating traffic for 48 hours or more, while your router"
+" \n"
+"re-integrates into the network. Due to the new keys, the large number of"
+" \n"
+"torrent updates, and the recent network growth, we expect substantial \n"
+"disruption to the network for a week or more after the update is "
+"released. \n"
+"Please be patient and things should start to improve after a few days."
+msgstr ""
+
+#: i2p2www/blog/2013/09/30/0.9.8-Release.rst:54
+msgid ""
+"These changes may result in higher CPU usage for some of you. We're doing"
+" \n"
+"our best to increase efficiency, but stronger security generally requires"
+" more \n"
+"computation. Performance may also be poor during the first week\n"
+"due to the network churn.\n"
+"We will evaluate the network performace before deciding whether to\n"
+"change the key length on slower hardware in a future release."
+msgstr ""
+
+#: i2p2www/blog/2013/09/30/0.9.8-Release.rst:63
+msgid ""
+"We are experiencing rapid network growth in the last few weeks, which is"
+" \n"
+"causing a bit of a bumpy ride for some, especially on weekends. However, "
+"the \n"
+"network is still performing fairly well, so keep spreading the word."
+msgstr ""
+
+#: i2p2www/blog/2013/09/30/0.9.8-Release.rst:69
+msgid "More Changes Coming"
+msgstr ""
+
+#: i2p2www/blog/2013/09/30/0.9.8-Release.rst:71
+msgid ""
+"We're in the initial stages of desiging major changes to strengthen our \n"
+"crypto. Stronger crypto will use more CPU and it may possibly \n"
+"require a Java 7 JRE at a minimum. We understand your desire to run I2P "
+"on low-power \n"
+"and/or older hardware. We're working hard to minimize the impacts, but "
+"some \n"
+"loss of performance is inevitable. In addition, Java 5 and 6 are no "
+"longer \n"
+"supported by Oracle. Now is a good time to upgrade to Java 7. Any change "
+"in \n"
+"minimum requirements will be announced well in advance."
+msgstr ""
+
+#: i2p2www/blog/2013/09/30/0.9.8-Release.rst:81
+msgid "New Website"
+msgstr ""
+
+#: i2p2www/blog/2013/09/30/0.9.8-Release.rst:83
+msgid ""
+"After a heroic effort by str4d, the new website preview is available at \n"
+"http://i2hq.srv.i2p2.de. We hope to see it go live at \n"
+"https://geti2p.net and http://www.i2p2.i2p soon.  Please \n"
+"contribute to the new website translations on Transifex, especially the \n"
+"website_priority resource."
+msgstr ""
+
+#: i2p2www/blog/2013/09/30/0.9.8-Release.rst:91
+msgid "Community Participation"
+msgstr ""
+
+#: i2p2www/blog/2013/09/30/0.9.8-Release.rst:93
+msgid ""
+"In early August, hottuna and zzz attended DEFCON 21 in Las Vegas.\n"
+"Last weekend, echelon attended the CTS IV conference in Berlin and\n"
+"psi attended the Tahoe-LAFS hackfest at GNU 30 in Cambridge, Mass.\n"
+"Several of us will be at 30C3 in Hamburg late this year.\n"
+"It's great to see people participating at these events and representing "
+"I2P."
+msgstr ""
+
+#: i2p2www/blog/2013/09/30/0.9.8-Release.rst:105
+msgid "IPv6 support for both NTCP and SSU"
+msgstr ""
+
+#: i2p2www/blog/2013/09/30/0.9.8-Release.rst:109
+msgid "SSU protocol obfuscation by adding random padding"
+msgstr ""
+
+#: i2p2www/blog/2013/09/30/0.9.8-Release.rst:110
+msgid "Longer encryption and DH private keys for users on faster platforms"
+msgstr ""
+
+#: i2p2www/blog/2013/09/30/0.9.8-Release.rst:114
+msgid "Fix I2PTunnel / I2CP locking and duplicates (partial)"
+msgstr ""
+
+#: i2p2www/blog/2013/09/30/0.9.8-Release.rst:115
+msgid "Fix translation of HTTP proxy error pages"
+msgstr ""
+
+#: i2p2www/blog/2013/09/30/0.9.8-Release.rst:116
+msgid "Fix occasional runtime exception in NTCP"
+msgstr ""
+
+#: i2p2www/blog/2013/09/30/0.9.8-Release.rst:120
+msgid "Big rework of transport code to accommodate multiple addresses and IPv6"
+msgstr ""
+
+#: i2p2www/blog/2013/09/30/0.9.8-Release.rst:121
+msgid "Streaming: Improved recovery from lost acks, other fixes"
+msgstr ""
+
+#: i2p2www/blog/2013/09/30/0.9.8-Release.rst:122
+msgid "Use Transifex for translation of initial news and HTTP proxy error pages"
+msgstr ""
+
+#: i2p2www/blog/2013/09/30/0.9.8-Release.rst:123
+msgid ""
+"Translation updates: Chinese, French, German, Portuguese, Russian, "
+"Swedish, Turkish"
+msgstr ""
+
+#: i2p2www/blog/2013/09/30/0.9.8-Release.rst:124
+msgid "New Romanian translation"
+msgstr ""
+
+#: i2p2www/blog/2013/09/30/0.9.8-Release.rst:126
+msgid "Wrapper 3.5.20 (new installs and PPA only)"
+msgstr ""
+
+#: i2p2www/blog/2013/10/02/0.9.8.1-Release.rst:2
+msgid "0.9.8.1 Release"
+msgstr ""
+
+#: i2p2www/blog/2013/10/02/0.9.8.1-Release.rst:7
+#: i2p2www/blog/2013/10/02/0.9.8.1-Release.rst:9
+msgid ""
+"0.9.8.1 fixes a problem with updating to 0.9.8 on Windows for some "
+"people. New installs and non-Windows platforms are not affected, however "
+"all platforms will automatically update even if running 0.9.8."
+msgstr ""
+
+#: i2p2www/blog/2013/10/02/0.9.8.1-Release.rst:11
+msgid ""
+"See the `Trac ticket`_ for details and workarounds. See\n"
+"`the 0.9.8 release notes`_ for information on IPv6 and other changes."
+msgstr ""
+
+#: i2p2www/blog/2013/10/02/0.9.8.1-Release.rst:16
+msgid ""
+"Due to recent attacks, logins are disabled on `Trac`_ and new "
+"registrations are\n"
+"disabled on `zzz.i2p`_. Until those services are restored, please report "
+"all\n"
+"bugs on IRC freenode or IRC2P #i2p-dev."
+msgstr ""
+
+#: i2p2www/blog/2013/10/02/0.9.8.1-Release.rst:22
+msgid "`Trac ticket`"
+msgstr ""
+
+#: i2p2www/blog/2013/10/02/0.9.8.1-Release.rst:23
+msgid "`the 0.9.8 release notes`"
+msgstr ""
+
+#: i2p2www/blog/2013/12/07/0.9.9-Release.rst:2
+msgid "0.9.9 Release"
+msgstr ""
+
+#: i2p2www/blog/2013/12/07/0.9.9-Release.rst:7
+#: i2p2www/blog/2013/12/07/0.9.9-Release.rst:9
+msgid ""
+"0.9.9 fixes a number of bugs in the netdb, streaming, and i2ptunnel, and "
+"starts work on a year-long plan to increase the strength of the "
+"cryptographic signing algorithms used in the router, and support multiple"
+" algorithms and key lengths simultaneously. Automatic update files will "
+"now be signed with 4096-bit RSA keys."
+msgstr ""
+
+#: i2p2www/blog/2013/12/07/0.9.9-Release.rst:11
+msgid ""
+"We now support SSL between your router and your servers for security.\n"
+"See `this development thread`_ for more information."
+msgstr ""
+
+#: i2p2www/blog/2013/12/07/0.9.9-Release.rst:16
+msgid "`this development thread`"
+msgstr ""
+
+#: i2p2www/blog/2013/12/07/0.9.9-Release.rst:18
+msgid ""
+"As usual, we recommend that you update to this release.\n"
+"The best way to maintain security and help the network is to run the "
+"latest release.\n"
+"Several members of the I2P team will be at 30C3 in Hamburg this year.\n"
+"Come say hello and ask for an I2P sticker.\n"
+"Thanks to everyone for their support this year."
+msgstr ""
+
+#: i2p2www/blog/2013/12/07/0.9.9-Release.rst:30
+msgid "Don't build client tunnels through zero-hop exploratory tunnels"
+msgstr ""
+
+#: i2p2www/blog/2013/12/07/0.9.9-Release.rst:31
+msgid "New \"su3\" file support using stronger keys"
+msgstr ""
+
+#: i2p2www/blog/2013/12/07/0.9.9-Release.rst:32
+msgid "Use su3 for updates"
+msgstr ""
+
+#: i2p2www/blog/2013/12/07/0.9.9-Release.rst:36
+msgid "Issues with losing data when closing streams"
+msgstr ""
+
+#: i2p2www/blog/2013/12/07/0.9.9-Release.rst:37
+msgid "Fix various streaming connection limit issues"
+msgstr ""
+
+#: i2p2www/blog/2013/12/07/0.9.9-Release.rst:38
+msgid "Issues with resource usage of closed connections"
+msgstr ""
+
+#: i2p2www/blog/2013/12/07/0.9.9-Release.rst:39
+msgid "Clean up timer threads in close-on-idle tunnels"
+msgstr ""
+
+#: i2p2www/blog/2013/12/07/0.9.9-Release.rst:40
+msgid "Several other streaming fixes"
+msgstr ""
+
+#: i2p2www/blog/2013/12/07/0.9.9-Release.rst:41
+msgid "Reject more non-public IPv6 addresses"
+msgstr ""
+
+#: i2p2www/blog/2013/12/07/0.9.9-Release.rst:42
+msgid "Fix IPv6 GeoIP"
+msgstr ""
+
+#: i2p2www/blog/2013/12/07/0.9.9-Release.rst:43
+msgid "Fix peer selection in first minutes after startup"
+msgstr ""
+
+#: i2p2www/blog/2013/12/07/0.9.9-Release.rst:44
+msgid "Several I2PTunnel bug fixes"
+msgstr ""
+
+#: i2p2www/blog/2013/12/07/0.9.9-Release.rst:45
+msgid "Fix major i2psnark DHT bug that prevented magnets from working well"
+msgstr ""
+
+#: i2p2www/blog/2013/12/07/0.9.9-Release.rst:46
+msgid ""
+"Fix client tunnels that fail due to name resolution failure at startup, "
+"particularly with b32 hostnames"
+msgstr ""
+
+#: i2p2www/blog/2013/12/07/0.9.9-Release.rst:47
+msgid "Fix changing client i2ptunnel target list"
+msgstr ""
+
+#: i2p2www/blog/2013/12/07/0.9.9-Release.rst:48
+msgid ""
+"Fix major bugs preventing reception of encrypted responses to leaseset "
+"lookups and verifies"
+msgstr ""
+
+#: i2p2www/blog/2013/12/07/0.9.9-Release.rst:49
+msgid "Fix bad links on some i2psnark buttons in Opera and text-mode browsers"
+msgstr ""
+
+#: i2p2www/blog/2013/12/07/0.9.9-Release.rst:50
+msgid "Fix NPE in Susimail"
+msgstr ""
+
+#: i2p2www/blog/2013/12/07/0.9.9-Release.rst:54
+msgid "Start work on supporting stronger signing keys in the router"
+msgstr ""
+
+#: i2p2www/blog/2013/12/07/0.9.9-Release.rst:55
+msgid "Reduce thread usage for HTTP Server tunnels"
+msgstr ""
+
+#: i2p2www/blog/2013/12/07/0.9.9-Release.rst:56
+msgid "Auto-stop update torrent after some time"
+msgstr ""
+
+#: i2p2www/blog/2013/12/07/0.9.9-Release.rst:57
+msgid "Add ability to stop webapp via console"
+msgstr ""
+
+#: i2p2www/blog/2013/12/07/0.9.9-Release.rst:58
+msgid "New POST throttler in HTTP server tunnel"
+msgstr ""
+
+#: i2p2www/blog/2013/12/07/0.9.9-Release.rst:59
+msgid "Improve connection throttling"
+msgstr ""
+
+#: i2p2www/blog/2013/12/07/0.9.9-Release.rst:60
+msgid "More work to reduce number of connections"
+msgstr ""
+
+#: i2p2www/blog/2013/12/07/0.9.9-Release.rst:61
+msgid "Re-enable router info expiration job"
+msgstr ""
+
+#: i2p2www/blog/2013/12/07/0.9.9-Release.rst:62
+msgid ""
+"Extend router info expiration and other changes to reduce load on "
+"floodfills"
+msgstr ""
+
+#: i2p2www/blog/2013/12/07/0.9.9-Release.rst:63
+msgid "Support multiple servers through a single server tunnel"
+msgstr ""
+
+#: i2p2www/blog/2013/12/07/0.9.9-Release.rst:64
+msgid "Support specification of server port in i2ptunnel clients"
+msgstr ""
+
+#: i2p2www/blog/2013/12/07/0.9.9-Release.rst:65
+msgid "Add support for SSL connections from i2ptunnel to external server"
+msgstr ""
+
+#: i2p2www/blog/2013/12/07/0.9.9-Release.rst:66
+msgid "SSL and crypto code refactoring"
+msgstr ""
+
+#: i2p2www/blog/2013/12/07/0.9.9-Release.rst:67
+msgid "i2psnark storage code refactoring"
+msgstr ""
+
+#: i2p2www/blog/2013/12/07/0.9.9-Release.rst:68
+msgid "New destination cache"
+msgstr ""
+
+#: i2p2www/blog/2013/12/07/0.9.9-Release.rst:69
+msgid "Lots of code cleanup and resolution of findbugs warnings"
+msgstr ""
+
+#: i2p2www/blog/2013/12/07/0.9.9-Release.rst:70
+msgid "New Japanese translation (partial)"
+msgstr ""
+
+#: i2p2www/blog/2013/12/07/0.9.9-Release.rst:71
+msgid ""
+"Translation updates: French, German, Italian, Romanian, Russian, Spanish,"
+" Swedish, and others"
+msgstr ""
+
+#: i2p2www/blog/2013/12/07/0.9.9-Release.rst:73
+msgid "Wrapper 3.5.22 (new installs and PPA only)"
+msgstr ""
+
+#: i2p2www/blog/2014/01/21/Syndie-1.105b-Release.rst:1
+msgid ""
+"=====================\n"
+"Syndie 1.105b Release\n"
+"====================="
+msgstr ""
+
+#: i2p2www/blog/2014/01/21/Syndie-1.105b-Release.rst:9
+msgid "Update to HSQLDB 2.3.1"
+msgstr ""
+
+#: i2p2www/blog/2014/01/21/Syndie-1.105b-Release.rst:11
+msgid ""
+"This is the first stable release since February 2013.\n"
+"It is essentially the same as 1.104b-7-rc, with some translation updates."
+msgstr ""
+
+#: i2p2www/blog/2014/01/21/Syndie-1.105b-Release.rst:16
+msgid ""
+"All binaries and source packages are at `syndie.de`_ and `syndie.i2p`_.\n"
+"Plugins are available at `plugins.i2p`_ and `stats.i2p`_."
+msgstr ""
+
+#: i2p2www/blog/2014/01/21/Syndie-1.105b-Release.rst:21
+msgid ""
+"For those of you upgrading from 1.103b, you will find syndie startup and "
+"shutdown much faster due to the new version of HSQLDB."
+msgstr ""
+
+#: i2p2www/blog/2014/01/21/Syndie-1.105b-Release.rst:25
+msgid ""
+"If you have a large database or an identity you wish to preserve,\n"
+"you may wish to back up your entire ~/.syndie directory before you start."
+"\n"
+"The upgrade process does make its own backup, however you may find it "
+"easier to use your own backup if the upgrade fails."
+msgstr ""
+
+#: i2p2www/blog/2014/01/21/Syndie-1.105b-Release.rst:31
+msgid ""
+"Upgrades from 1.103b may fail for some people due to database corruption "
+"due to bugs in the old HSQLDB.\n"
+"Unfortunately, we don't know how to fix it.\n"
+"Your alternatives are to start over with a clean database, or stay with "
+"1.103b forever.\n"
+"Sorry about that."
+msgstr ""
+
+#: i2p2www/blog/2014/01/21/Syndie-1.105b-Release.rst:43
+#: i2p2www/blog/2014/01/22/0.9.10-Release.rst:29
+msgid ""
+"As usual, we recommend that you update to this release.\n"
+"The best way to maintain security and help the network is to run the "
+"latest release."
+msgstr ""
+
+#: i2p2www/blog/2014/01/21/Syndie-1.105b-Release.rst:56
+msgid "GUI Improvements and Fixes"
+msgstr ""
+
+#: i2p2www/blog/2014/01/21/Syndie-1.105b-Release.rst:72
+msgid "Syndication"
+msgstr ""
+
+#: i2p2www/blog/2014/01/21/Syndie-1.105b-Release.rst:83
+msgid "Database"
+msgstr ""
+
+#: i2p2www/blog/2014/01/21/Syndie-1.105b-Release.rst:104
+msgid "New translations"
+msgstr ""
+
+#: i2p2www/blog/2014/01/21/Syndie-1.105b-Release.rst:105
+#: i2p2www/blog/2014/01/22/0.9.10-Release.rst:60
+#: i2p2www/blog/2014/02/08/0.9.11-Release.rst:56
+#: i2p2www/blog/2014/03/31/0.9.12-Release.rst:99
+#: i2p2www/blog/2014/05/22/0.9.13-Release.rst:57
+#: i2p2www/blog/2014/07/26/0.9.14-Release.rst:69
+#: i2p2www/blog/2014/09/20/0.9.15-Release.rst:72
+#: i2p2www/blog/2014/11/01/0.9.16-Release.rst:82
+#: i2p2www/blog/2014/11/30/0.9.17-Release.rst:77
+#: i2p2www/blog/2015/02/22/0.9.18-Release.rst:57
+#: i2p2www/blog/2015/04/12/0.9.19-Release.rst:65
+#: i2p2www/blog/2015/06/02/0.9.20-Release.rst:95
+#: i2p2www/blog/2015/07/31/0.9.21-Release.rst:71
+#: i2p2www/blog/2015/09/12/0.9.22-Release.rst:52
+#: i2p2www/blog/2015/11/19/0.9.23-Release.rst:111
+#: i2p2www/blog/2016/01/27/0.9.24-Release.rst:96
+#: i2p2www/blog/2016/03/22/0.9.25-Release.rst:67
+#: i2p2www/blog/2016/06/07/0.9.26-Release.rst:87
+#: i2p2www/blog/2016/10/17/0.9.27-Release.rst:64
+#: i2p2www/blog/2016/12/12/0.9.28-Release.rst:94
+#: i2p2www/blog/2017/02/27/0.9.29-Release.rst:68
+#: i2p2www/blog/2017/05/03/0.9.30-Release.rst:93
+#: i2p2www/blog/2017/08/07/0.9.31-Release.rst:59
+#: i2p2www/blog/2017/11/07/0.9.32-Release.rst:48
+#: i2p2www/blog/2018/01/30/0.9.33-Release.rst:94
+#: i2p2www/blog/2018/04/10/0.9.34-Release.rst:54
+#: i2p2www/blog/2018/06/26/0.9.35-Release.rst:70
+#: i2p2www/blog/2018/08/23/0.9.36-Release.rst:63
+msgid "Translation updates"
+msgstr ""
+
+#: i2p2www/blog/2014/01/22/0.9.10-Release.rst:1
+msgid ""
+"==============\n"
+"0.9.10 Release\n"
+"=============="
+msgstr ""
+
+#: i2p2www/blog/2014/01/22/0.9.10-Release.rst:9
+msgid ""
+"0.9.10 changes the mechanism for doing LeaseSet lookups, making it more "
+"difficult for an attacker to correlate a Destination with a Router."
+msgstr ""
+
+#: i2p2www/blog/2014/01/22/0.9.10-Release.rst:11
+msgid ""
+"0.9.10 changes the mechanism for doing LeaseSet lookups, making it more "
+"difficult for an attacker\n"
+"to correlate a Destination with a Router. It also fixes character "
+"encoding bugs in susimail,\n"
+"and includes lots of other bug fixes and translation updates.\n"
+"Most of you will update via torrent, using the new \"su3\" update format "
+"with stronger keys."
+msgstr ""
+
+#: i2p2www/blog/2014/01/22/0.9.10-Release.rst:18
+msgid ""
+"We recently attended `30C3`_ and `Real World Crypto`_, making several new"
+"\n"
+"connections and formulating `big plans`_ for 2014. Thanks to those who\n"
+"supported our attendance with their `donations`_!"
+msgstr ""
+
+#: i2p2www/blog/2014/01/22/0.9.10-Release.rst:26
+msgid "`big plans`"
+msgstr ""
+
+#: i2p2www/blog/2014/01/22/0.9.10-Release.rst:27
+msgid "`donations`"
+msgstr ""
+
+#: i2p2www/blog/2014/01/22/0.9.10-Release.rst:38
+msgid "Use client tunnels for LeaseSet lookups"
+msgstr ""
+
+#: i2p2www/blog/2014/01/22/0.9.10-Release.rst:42
+msgid ""
+"Flood netdb stores to new location before midnight to prevent lookup "
+"fails after midnight"
+msgstr ""
+
+#: i2p2www/blog/2014/01/22/0.9.10-Release.rst:43
+msgid "Fix setting I2CP host/port in BOB"
+msgstr ""
+
+#: i2p2www/blog/2014/01/22/0.9.10-Release.rst:44
+msgid "Fix several character encoding issues in susimail"
+msgstr ""
+
+#: i2p2www/blog/2014/01/22/0.9.10-Release.rst:45
+msgid "Fix StandardServerSocket.close()"
+msgstr ""
+
+#: i2p2www/blog/2014/01/22/0.9.10-Release.rst:46
+msgid "Fix exception in PrivateKeyFile"
+msgstr ""
+
+#: i2p2www/blog/2014/01/22/0.9.10-Release.rst:47
+msgid "Fixes in RouterInfo expiration task"
+msgstr ""
+
+#: i2p2www/blog/2014/01/22/0.9.10-Release.rst:51
+msgid "Tweaks to reduce number of peer connections"
+msgstr ""
+
+#: i2p2www/blog/2014/01/22/0.9.10-Release.rst:52
+msgid "Several threading fixes to reduce blocking in the timer queues"
+msgstr ""
+
+#: i2p2www/blog/2014/01/22/0.9.10-Release.rst:53
+msgid "Disable streaming ping handling for clients"
+msgstr ""
+
+#: i2p2www/blog/2014/01/22/0.9.10-Release.rst:54
+msgid "Use i2psnark's Kademlia library for the router netdb also"
+msgstr ""
+
+#: i2p2www/blog/2014/01/22/0.9.10-Release.rst:55
+msgid ""
+"Increase outbound exploratory default to 2 + 0-1 hops, part of gradual "
+"increase to 3 hops in/out"
+msgstr ""
+
+#: i2p2www/blog/2014/01/22/0.9.10-Release.rst:56
+msgid "More findbugs fixes"
+msgstr ""
+
+#: i2p2www/blog/2014/01/22/0.9.10-Release.rst:57
+msgid "Streaming library refactoring"
+msgstr ""
+
+#: i2p2www/blog/2014/01/22/0.9.10-Release.rst:58
+msgid "Support country-specific translations"
+msgstr ""
+
+#: i2p2www/blog/2014/01/22/0.9.10-Release.rst:59
+msgid "New Brazilian Portuguese translation"
+msgstr ""
+
+#: i2p2www/blog/2014/02/08/0.9.11-Release.rst:1
+msgid ""
+"==============\n"
+"0.9.11 Release\n"
+"=============="
+msgstr ""
+
+#: i2p2www/blog/2014/02/08/0.9.11-Release.rst:9
+msgid ""
+"0.9.11 adds support for outproxy plugins, improves lease set lookup "
+"security, and reduces memory usage."
+msgstr ""
+
+#: i2p2www/blog/2014/02/08/0.9.11-Release.rst:11
+#, python-format
+msgid ""
+"0.9.11 continues improving LeaseSet lookup and storage to prevent an "
+"attacker\n"
+"from correlating a Destination with a Router. It adds support for the\n"
+"%(orchid)s outproxy plugin which is available at %(url)s. There is a\n"
+"reduction in memory usage due to fixes in the transports. We have some "
+"I2CP\n"
+"protocol improvements that will provide better lookup facilities and\n"
+"authorization protection for external clients. Of course, there's also "
+"the\n"
+"usual collection of bug fixes. All users should update."
+msgstr ""
+
+#: i2p2www/blog/2014/02/08/0.9.11-Release.rst:21
+msgid ""
+"This may be the last release that works with Java 5, which is very old "
+"and\n"
+"unsupported. If you are using a Java 5 or 6 runtime, we strongly "
+"recommend that\n"
+"you upgrade to Java 7."
+msgstr ""
+
+#: i2p2www/blog/2014/02/08/0.9.11-Release.rst:30
+#: i2p2www/blog/2014/03/31/0.9.12-Release.rst:30
+#: i2p2www/blog/2014/05/22/0.9.13-Release.rst:17
+#: i2p2www/blog/2014/09/20/0.9.15-Release.rst:32
+#: i2p2www/blog/2014/11/01/0.9.16-Release.rst:30
+#: i2p2www/blog/2014/11/30/0.9.17-Release.rst:37
+#: i2p2www/blog/2015/02/22/0.9.18-Release.rst:21
+#: i2p2www/blog/2015/04/12/0.9.19-Release.rst:24
+#: i2p2www/blog/2015/06/02/0.9.20-Release.rst:29
+#: i2p2www/blog/2015/07/31/0.9.21-Release.rst:25
+#: i2p2www/blog/2015/09/12/0.9.22-Release.rst:24
+#: i2p2www/blog/2015/11/19/0.9.23-Release.rst:67
+#: i2p2www/blog/2016/01/27/0.9.24-Release.rst:47
+#: i2p2www/blog/2016/03/22/0.9.25-Release.rst:29
+#: i2p2www/blog/2016/06/07/0.9.26-Release.rst:48
+#: i2p2www/blog/2016/10/17/0.9.27-Release.rst:27
+#: i2p2www/blog/2016/12/12/0.9.28-Release.rst:29
+#: i2p2www/blog/2017/02/27/0.9.29-Release.rst:26
+#: i2p2www/blog/2017/05/03/0.9.30-Release.rst:50
+#: i2p2www/blog/2017/08/07/0.9.31-Release.rst:26
+#: i2p2www/blog/2017/11/07/0.9.32-Release.rst:23
+#: i2p2www/blog/2018/01/30/0.9.33-Release.rst:24
+#: i2p2www/blog/2018/04/10/0.9.34-Release.rst:24
+#: i2p2www/blog/2018/06/26/0.9.35-Release.rst:30
+#: i2p2www/blog/2018/08/23/0.9.36-Release.rst:27
+msgid ""
+"As usual, we recommend that you update to this release. The best way to\n"
+"maintain security and help the network is to run the latest release."
+msgstr ""
+"Hər zamanki kimi bu versiyanı yeniləməyi məsləhət görürük. Təhlükəsizliyi"
+" qorumaq və şəbəkəyə kömək etmək üçün ən yaxşı yol son buraxılışı "
+"yükləməkdir."
+
+#: i2p2www/blog/2014/02/08/0.9.11-Release.rst:39
+msgid "More leaseset handling improvements"
+msgstr ""
+
+#: i2p2www/blog/2014/02/08/0.9.11-Release.rst:43
+msgid "Fix NPE after client shutdown"
+msgstr ""
+
+#: i2p2www/blog/2014/02/08/0.9.11-Release.rst:44
+msgid "Fix wrapper log encoding on logs page"
+msgstr ""
+
+#: i2p2www/blog/2014/02/08/0.9.11-Release.rst:45
+msgid "Streaming ping and I2Ping fixes"
+msgstr ""
+
+#: i2p2www/blog/2014/02/08/0.9.11-Release.rst:49
+msgid "Add support for Orchid plugin"
+msgstr ""
+
+#: i2p2www/blog/2014/02/08/0.9.11-Release.rst:50
+msgid "Add HTTPS support to HTTP client proxy"
+msgstr ""
+
+#: i2p2www/blog/2014/02/08/0.9.11-Release.rst:51
+msgid "New I2CP support for hostname lookups by external clients"
+msgstr ""
+
+#: i2p2www/blog/2014/02/08/0.9.11-Release.rst:52
+msgid ""
+"Stricter I2CP authorization enforcement of external clients (incompatible"
+" change)"
+msgstr ""
+
+#: i2p2www/blog/2014/02/08/0.9.11-Release.rst:53
+msgid "Increase default inbound exploratory tunnel length variance"
+msgstr ""
+
+#: i2p2www/blog/2014/02/08/0.9.11-Release.rst:54
+msgid "Big reduction in memory usage by transports"
+msgstr ""
+
+#: i2p2www/blog/2014/02/08/0.9.11-Release.rst:55
+msgid "All in-net updates via torrent"
+msgstr ""
+
+#: i2p2www/blog/2014/02/16/i2pbrowser-malware.rst:1
+msgid ""
+"=========================\n"
+"Malware at i2pbrowser.net\n"
+"========================="
+msgstr ""
+
+#: i2p2www/blog/2014/02/16/i2pbrowser-malware.rst:8
+msgid ""
+"The site i2pbrowser.net is a fake I2P website mirror serving up malware "
+"for Windows."
+msgstr ""
+
+#: i2p2www/blog/2014/02/16/i2pbrowser-malware.rst:10
+msgid ""
+"We have recently been made aware of the existence of i2pbrowser.net. This"
+"\n"
+"website copies our homepage and download page, and attempts to trick "
+"users into\n"
+"downloading Windows malware."
+msgstr ""
+
+#: i2p2www/blog/2014/02/16/i2pbrowser-malware.rst:16
+msgid ""
+"There are several indicators that point to i2pbrowser.net being a malware"
+" site:"
+msgstr ""
+
+#: i2p2www/blog/2014/02/16/i2pbrowser-malware.rst:20
+msgid "The domain was registered on February 10th, 2014."
+msgstr ""
+
+#: i2p2www/blog/2014/02/16/i2pbrowser-malware.rst:21
+msgid ""
+"The download URLs for Windows, Mac OSX, Linux, Android etc. all link to "
+"the same .exe file."
+msgstr ""
+
+#: i2p2www/blog/2014/02/16/i2pbrowser-malware.rst:22
+msgid "The .exe is only 741 KB; the official Windows installer for I2P is 13 MB."
+msgstr ""
+
+#: i2p2www/blog/2014/02/16/i2pbrowser-malware.rst:24
+msgid ""
+"We have not examined the malware ourselves, but it does not appear to be "
+"very\n"
+"sophisticated; it is not integrated into or bundled with the I2P "
+"software.\n"
+"Information security expert `Lance James`_ posted `a tweet`_ labelling it"
+" as\n"
+"\"a standard dark comet rat\"."
+msgstr ""
+
+#: i2p2www/blog/2014/02/16/i2pbrowser-malware.rst:31
+msgid ""
+"Spread the word. The only official download locations for I2P are linked "
+"on our\n"
+"`download page`_. All I2P download packages are GPG-signed by the\n"
+"`release signing key`_."
+msgstr ""
+
+#: i2p2www/blog/2014/02/16/i2pbrowser-malware.rst:38
+msgid "`a tweet`"
+msgstr ""
+
+#: i2p2www/blog/2014/02/16/i2pbrowser-malware.rst:40
+msgid "`release signing key`"
+msgstr ""
+
+#: i2p2www/blog/2014/03/12/press-release-ddg-donation.rst:1
+msgid ""
+"================================================================\n"
+"Search Engine DuckDuckGo Awards Invisible Internet Project $5000\n"
+"================================================================"
+msgstr ""
+
+#: i2p2www/blog/2014/03/12/press-release-ddg-donation.rst:10
+msgid ""
+"Search engine `DuckDuckGo`_ `donates`_ $5000 to the `Invisible Internet "
+"Project`_ (I2P) in their open source donation program."
+msgstr ""
+
+#: i2p2www/blog/2014/03/12/press-release-ddg-donation.rst:12
+msgid ""
+"**Somewhere, NH** -- Internet search company `DuckDuckGo`_ `donates`_\n"
+"$5000 to the `Invisible Internet Project`_ (I2P) as part of their yearly "
+"open-source\n"
+"donation program. The award was granted on the basis of `nominations`_ by"
+" members of the public\n"
+"on the DuckDuckGo community portal. With an emphasis on privacy, "
+"DuckDuckGo provides a search\n"
+"engine which does not track its users or store personal data. I2P is an "
+"anonymous network intended to\n"
+"protect individuals from dragnet surveillance regularly performed by ISPs"
+" and governments."
+msgstr ""
+
+#: i2p2www/blog/2014/03/12/press-release-ddg-donation.rst:21
+#: i2p2www/blog/2014/03/31/0.9.12-Release.rst:42
+msgid ""
+"This marks the single largest donation ever received by I2P and reflects "
+"a growing interest in\n"
+"privacy and security by the Internet community. The funding will help I2P"
+" to reach more users, expand\n"
+"development, and audit the code. It will also enable I2P developers to "
+"attend conferences, such\n"
+"as the `Real-World Cryptography`_ conference in New York City, where the "
+"developers met and\n"
+"collaborated with cryptography experts pursuant to I2P's goals of "
+"providing anonymity to the\n"
+"public."
+msgstr ""
+
+#: i2p2www/blog/2014/03/12/press-release-ddg-donation.rst:30
+#: i2p2www/blog/2014/03/31/0.9.12-Release.rst:51
+msgid ""
+"I2P thanks Gabriel Weinberg and DuckDuckGo for the generous donation,\n"
+"and the I2P community for its support in the `nominations`_."
+msgstr ""
+
+#: i2p2www/blog/2014/03/12/press-release-ddg-donation.rst:35
+msgid ""
+"For more information about I2P, visit `our web site`_ or follow us `on "
+"Twitter`_."
+msgstr ""
+
+#: i2p2www/blog/2014/03/12/press-release-ddg-donation.rst:39
+msgid "`donates`"
+msgstr ""
+
+#: i2p2www/blog/2014/03/12/press-release-ddg-donation.rst:42
+msgid "`our web site`"
+msgstr ""
+
+#: i2p2www/blog/2014/03/12/press-release-ddg-donation.rst:43
+#: i2p2www/blog/2014/03/31/0.9.12-Release.rst:59
+msgid "`nominations`"
+msgstr ""
+
+#: i2p2www/blog/2014/03/12/press-release-ddg-donation.rst:45
+msgid "`on Twitter`"
+msgstr ""
+
+#: i2p2www/blog/2014/03/31/0.9.12-Release.rst:1
+msgid ""
+"==============\n"
+"0.9.12 Release\n"
+"=============="
+msgstr ""
+
+#: i2p2www/blog/2014/03/31/0.9.12-Release.rst:10
+msgid "0.9.12 adds support for ECDSA and updates to Jetty 8"
+msgstr ""
+
+#: i2p2www/blog/2014/03/31/0.9.12-Release.rst:12
+msgid ""
+"I2P now requires Java 6 or higher.\n"
+"We strongly recommend that you upgrade to Java 7.\n"
+"If you are still using Java 5, you must upgrade your Java before "
+"installing I2P 0.9.12."
+msgstr ""
+
+#: i2p2www/blog/2014/03/31/0.9.12-Release.rst:18
+msgid ""
+"0.9.12 adds preliminary support for ECDSA-signed Destinations.\n"
+"It contains several fixes for the handling of Delivery Status Messages "
+"(acknowledgements)\n"
+"and those messages are now end-to-end encrypted for increased security."
+msgstr ""
+
+#: i2p2www/blog/2014/03/31/0.9.12-Release.rst:24
+msgid ""
+"We have upgraded to Jetty 8.\n"
+"Jetty 8 is almost identical to Jetty 7, so there are no complex "
+"configuration file conversions as there have been in past Jetty upgrades."
+"\n"
+"No manual changes should be necessary."
+msgstr ""
+
+#: i2p2www/blog/2014/03/31/0.9.12-Release.rst:35
+msgid ""
+"In early March, Internet search company `DuckDuckGo`_ `donated`_\n"
+"$5000 to the `Invisible Internet Project` (I2P) as part of their yearly "
+"open-source\n"
+"donation program. The award was granted on the basis of `nominations`_ by"
+" members of the public\n"
+"on the DuckDuckGo community portal."
+msgstr ""
+
+#: i2p2www/blog/2014/03/31/0.9.12-Release.rst:56
+msgid "`donated`"
+msgstr ""
+
+#: i2p2www/blog/2014/03/31/0.9.12-Release.rst:69
+msgid "Encrypt Delivery Status Messages"
+msgstr ""
+
+#: i2p2www/blog/2014/03/31/0.9.12-Release.rst:70
+msgid "Add preliminary support for ECDSA-signed Destinations"
+msgstr ""
+
+#: i2p2www/blog/2014/03/31/0.9.12-Release.rst:71
+msgid "Add check for replayed NTCP session requests"
+msgstr ""
+
+#: i2p2www/blog/2014/03/31/0.9.12-Release.rst:72
+msgid "Add throttling and blocking checks to streaming ping processing"
+msgstr ""
+
+#: i2p2www/blog/2014/03/31/0.9.12-Release.rst:78
+msgid "Fix RouterInfo exchange in NTCP"
+msgstr ""
+
+#: i2p2www/blog/2014/03/31/0.9.12-Release.rst:79
+msgid "Extend timeout for Delivery Status Messages"
+msgstr ""
+
+#: i2p2www/blog/2014/03/31/0.9.12-Release.rst:80
+msgid "Drop streaming messages from recently closed connections"
+msgstr ""
+
+#: i2p2www/blog/2014/03/31/0.9.12-Release.rst:81
+msgid "Fix restarts on Raspberry Pi"
+msgstr ""
+
+#: i2p2www/blog/2014/03/31/0.9.12-Release.rst:82
+msgid "Restore profileOrganizer.sameCountryBonus advanced config"
+msgstr ""
+
+#: i2p2www/blog/2014/03/31/0.9.12-Release.rst:83
+msgid "Fix for jwebcache and i2phex"
+msgstr ""
+
+#: i2p2www/blog/2014/03/31/0.9.12-Release.rst:89
+msgid "Jetty 8.1.14.v20131031; Java 6 now required"
+msgstr ""
+
+#: i2p2www/blog/2014/03/31/0.9.12-Release.rst:90
+msgid "Reduce target connection count again to reduce tunnel reject rate further"
+msgstr ""
+
+#: i2p2www/blog/2014/03/31/0.9.12-Release.rst:91
+msgid "Add rate limit for outbound connections at tunnel endpoints"
+msgstr ""
+
+#: i2p2www/blog/2014/03/31/0.9.12-Release.rst:92
+msgid "Add optional inproxy blocking in i2ptunnel"
+msgstr ""
+
+#: i2p2www/blog/2014/03/31/0.9.12-Release.rst:93
+msgid "Use SSU session key for relay request/response when available"
+msgstr ""
+
+#: i2p2www/blog/2014/03/31/0.9.12-Release.rst:94
+msgid "Include HTTP POST data in SYN packet"
+msgstr ""
+
+#: i2p2www/blog/2014/03/31/0.9.12-Release.rst:95
+msgid "Add getopt library for better argument processing"
+msgstr ""
+
+#: i2p2www/blog/2014/03/31/0.9.12-Release.rst:96
+msgid "More removal of Jetty dependencies"
+msgstr ""
+
+#: i2p2www/blog/2014/03/31/0.9.12-Release.rst:97
+msgid "Remove MD5 code, use Java libraries instead"
+msgstr ""
+
+#: i2p2www/blog/2014/03/31/0.9.12-Release.rst:98
+msgid "Change the default addressbook subscription URL"
+msgstr ""
+
+#: i2p2www/blog/2014/05/22/0.9.13-Release.rst:1
+msgid ""
+"==============\n"
+"0.9.13 Release\n"
+"=============="
+msgstr ""
+
+#: i2p2www/blog/2014/05/22/0.9.13-Release.rst:10
+msgid "0.9.13 with SusiMail improvements and fixes for firewalled routers"
+msgstr ""
+
+#: i2p2www/blog/2014/05/22/0.9.13-Release.rst:12
+msgid ""
+"0.9.13 includes fixes for firewalled routers, netdb lookup improvements, "
+"and a big SusiMail update.\n"
+"Of course, there's also the usual collection of bug fixes and translation"
+" updates."
+msgstr ""
+
+#: i2p2www/blog/2014/05/22/0.9.13-Release.rst:22
+msgid ""
+"zzz has updated his GPG keys, and the release files are signed with his\n"
+"new keys. His new key fingerprint is:"
+msgstr ""
+
+#: i2p2www/blog/2014/05/22/0.9.13-Release.rst:31
+msgid "SusiMail"
+msgstr "SusiMail"
+
+#: i2p2www/blog/2014/05/22/0.9.13-Release.rst:33
+msgid "Many UI improvements"
+msgstr ""
+
+#: i2p2www/blog/2014/05/22/0.9.13-Release.rst:34
+msgid "Implement local storage of messages"
+msgstr ""
+
+#: i2p2www/blog/2014/05/22/0.9.13-Release.rst:35
+msgid "Add offline mode"
+msgstr ""
+
+#: i2p2www/blog/2014/05/22/0.9.13-Release.rst:36
+msgid "Messages now deleted on server after download"
+msgstr ""
+
+#: i2p2www/blog/2014/05/22/0.9.13-Release.rst:37
+msgid "Several backend POP3 and SMTP speedups and fixes"
+msgstr ""
+
+#: i2p2www/blog/2014/05/22/0.9.13-Release.rst:41
+msgid "NetDB lookup fixes"
+msgstr ""
+
+#: i2p2www/blog/2014/05/22/0.9.13-Release.rst:42
+msgid "Fix transition from not-firewalled to firewalled"
+msgstr ""
+
+#: i2p2www/blog/2014/05/22/0.9.13-Release.rst:43
+msgid "Fix plugin uninstall on Windows"
+msgstr ""
+
+#: i2p2www/blog/2014/05/22/0.9.13-Release.rst:44
+msgid "SSU locking fixes"
+msgstr ""
+
+#: i2p2www/blog/2014/05/22/0.9.13-Release.rst:45
+msgid "Fix rapid republishing of SSU addresses"
+msgstr ""
+
+#: i2p2www/blog/2014/05/22/0.9.13-Release.rst:46
+msgid "IRC client exception fixes"
+msgstr ""
+
+#: i2p2www/blog/2014/05/22/0.9.13-Release.rst:47
+msgid "Fix changing HTTP outproxy configuration without restarting tunnel"
+msgstr ""
+
+#: i2p2www/blog/2014/05/22/0.9.13-Release.rst:51
+msgid "New i2ptunnel server option for unique local address per-client"
+msgstr ""
+
+#: i2p2www/blog/2014/05/22/0.9.13-Release.rst:52
+msgid "Warn in i2ptunnel on duplicate client ports"
+msgstr ""
+
+#: i2p2www/blog/2014/05/22/0.9.13-Release.rst:53
+msgid "Update HTTP User-Agent to match TBB"
+msgstr ""
+
+#: i2p2www/blog/2014/05/22/0.9.13-Release.rst:54
+msgid "Extend SSU establishment retransmission timer"
+msgstr ""
+
+#: i2p2www/blog/2014/05/22/0.9.13-Release.rst:55
+msgid "Use constant-time method for HMAC verification"
+msgstr ""
+
+#: i2p2www/blog/2014/05/22/0.9.13-Release.rst:56
+msgid "New translation: Slovak"
+msgstr ""
+
+#: i2p2www/blog/2014/07/26/0.9.14-Release.rst:1
+msgid ""
+"==============\n"
+"0.9.14 Release\n"
+"=============="
+msgstr ""
+
+#: i2p2www/blog/2014/07/26/0.9.14-Release.rst:10
+msgid "0.9.14 includes critical security fixes"
+msgstr ""
+
+#: i2p2www/blog/2014/07/26/0.9.14-Release.rst:12
+msgid ""
+"0.9.14 includes critical fixes for XSS and remote execution "
+"vulnerabilities reported by Exodus Intelligence.\n"
+"As an added precaution, we have disabled several advanced configuration "
+"features in the router console,\n"
+"including installation of new plugins.\n"
+"We plan to re-enable these in a future release after additional review."
+msgstr ""
+
+#: i2p2www/blog/2014/07/26/0.9.14-Release.rst:19
+msgid ""
+"Due to I2P library changes, I2P-Bote users must upgrade their plugin to "
+"version 0.2.10 to work with I2P 0.9.14.\n"
+"Your router should update the plugin automatically after the router "
+"restarts."
+msgstr ""
+
+#: i2p2www/blog/2014/07/26/0.9.14-Release.rst:24
+msgid ""
+"The release also contains several bug fixes in i2ptunnel, i2psnark, and "
+"other areas,\n"
+"and updates to the latest Jetty, Tomcat, and Wrapper.\n"
+"We've also implemented a faster and more secure method for reseeding.\n"
+"Of course, there's also the usual collection of minor bug fixes and "
+"translation updates."
+msgstr ""
+
+#: i2p2www/blog/2014/07/26/0.9.14-Release.rst:31
+msgid ""
+"You must update to this release immediately. The best way to\n"
+"maintain security and help the network is to run the latest release."
+msgstr ""
+
+#: i2p2www/blog/2014/07/26/0.9.14-Release.rst:39
+msgid "Security Fixes"
+msgstr ""
+
+#: i2p2www/blog/2014/07/26/0.9.14-Release.rst:41
+msgid "Fix several XSS issues"
+msgstr ""
+
+#: i2p2www/blog/2014/07/26/0.9.14-Release.rst:42
+msgid "Disable changing news feed URL from UI"
+msgstr ""
+
+#: i2p2www/blog/2014/07/26/0.9.14-Release.rst:43
+msgid "Disable plugin install"
+msgstr ""
+
+#: i2p2www/blog/2014/07/26/0.9.14-Release.rst:44
+msgid "Disable setting unsigned update URL from UI"
+msgstr ""
+
+#: i2p2www/blog/2014/07/26/0.9.14-Release.rst:45
+msgid "Disable clients.config editing from the UI"
+msgstr ""
+
+#: i2p2www/blog/2014/07/26/0.9.14-Release.rst:46
+msgid "Add Content-Security-Policy and X-XSS-Protection headers"
+msgstr ""
+
+#: i2p2www/blog/2014/07/26/0.9.14-Release.rst:47
+msgid "Disable unused ExecNamingService (thx joernchen of Phenoelit)"
+msgstr ""
+
+#: i2p2www/blog/2014/07/26/0.9.14-Release.rst:52
+msgid "Fix tunnel building so it doesn't get \"stuck\" on a single pool"
+msgstr ""
+
+#: i2p2www/blog/2014/07/26/0.9.14-Release.rst:53
+msgid "Reject participating tunnels when hidden"
+msgstr ""
+
+#: i2p2www/blog/2014/07/26/0.9.14-Release.rst:54
+msgid ""
+"Several i2psnark improvements and fixes (GUI and DHT), including changes "
+"for better compatibility with Vuze"
+msgstr ""
+
+#: i2p2www/blog/2014/07/26/0.9.14-Release.rst:59
+msgid ""
+"Reseeding now fetches a signed zip file containing router infos for "
+"security and speed"
+msgstr ""
+
+#: i2p2www/blog/2014/07/26/0.9.14-Release.rst:60
+msgid "Use JVM's AES implementation if it is faster"
+msgstr ""
+
+#: i2p2www/blog/2014/07/26/0.9.14-Release.rst:61
+msgid "More advanced options shown in the i2ptunnel edit pages"
+msgstr ""
+
+#: i2p2www/blog/2014/07/26/0.9.14-Release.rst:62
+msgid ""
+"Per-message reliabilitiy settings in I2CP and error propagation back from"
+" router to client"
+msgstr ""
+
+#: i2p2www/blog/2014/07/26/0.9.14-Release.rst:63
+msgid "Lots of findbugs fixes and cleanups"
+msgstr ""
+
+#: i2p2www/blog/2014/07/26/0.9.14-Release.rst:64
+msgid "Support signature types in SAM, bump rev to 3.1"
+msgstr ""
+
+#: i2p2www/blog/2014/07/26/0.9.14-Release.rst:65
+msgid "New event log page in console"
+msgstr ""
+
+#: i2p2www/blog/2014/07/26/0.9.14-Release.rst:68
+msgid "Wrapper 3.5.25 (new installs and PPA only)"
+msgstr ""
+
+#: i2p2www/blog/2014/08/09/0.9.14.1-Release.rst:1
+msgid ""
+"================\n"
+"0.9.14.1 Release\n"
+"================"
+msgstr ""
+
+#: i2p2www/blog/2014/08/09/0.9.14.1-Release.rst:10
+msgid "0.9.14.1 includes i2psnark and console fixes"
+msgstr ""
+
+#: i2p2www/blog/2014/08/09/0.9.14.1-Release.rst:12
+msgid ""
+"0.9.14.1 includes fixes for the \"Add Torrent\" form in i2psnark and some"
+" other web forms.\n"
+"We've restored the ability to install plugins via the console, but you "
+"must first edit your router.config file\n"
+"(in ~/.i2p/ or /var/lib/i2p/i2p-config/ or %APPDATA%\\I2P\\) to add the "
+"line routerconsole.enablePluginInstall=true.\n"
+"Other rarely-used advanced features that were removed in 0.9.14 may be "
+"restored by adding the line routerconsole.advanced=true."
+msgstr ""
+
+#: i2p2www/blog/2014/08/09/0.9.14.1-Release.rst:19
+msgid ""
+"As usual, if configured with the default \"Download and Verify\", the "
+"router will automatically download the update and display a button to "
+"restart.\n"
+"However, due to a bug in 0.9.14, if your update is configured for "
+"\"Notify only\", the download button will not be displayed.\n"
+"You must change your configuration to \"Download and Verify\" or "
+"\"Download, Verify, and Restart\" to update."
+msgstr ""
+
+#: i2p2www/blog/2014/08/09/0.9.14.1-Release.rst:25
+msgid ""
+"If you are still running 0.9.13 or older, we recommend that you update to"
+" this release as soon as possible.\n"
+"If you don't often check your router console, please consider changing "
+"your configuration to \"Download, Verify, and Restart\"\n"
+"to ensure you are always running the latest release."
+msgstr ""
+
+#: i2p2www/blog/2014/08/09/0.9.14.1-Release.rst:37
+msgid "Fix i2psnark add torrent form"
+msgstr ""
+
+#: i2p2www/blog/2014/08/09/0.9.14.1-Release.rst:38
+msgid "Fix iptunnel custom options form"
+msgstr ""
+
+#: i2p2www/blog/2014/08/09/0.9.14.1-Release.rst:39
+msgid "Fix update download buttons"
+msgstr ""
+
+#: i2p2www/blog/2014/08/09/0.9.14.1-Release.rst:44
+msgid "Restore all console features if routerconsole.advanced=true"
+msgstr ""
+
+#: i2p2www/blog/2014/08/09/0.9.14.1-Release.rst:45
+msgid "Restore plugin install if routerconsole.enablePluginInstall=true"
+msgstr ""
+
+#: i2p2www/blog/2014/08/09/0.9.14.1-Release.rst:46
+msgid "Restpre client adds/changes if routerconsole.enableClientChange=true"
+msgstr ""
+
+#: i2p2www/blog/2014/08/09/0.9.14.1-Release.rst:47
+msgid ""
+"Plugin signing keys are now whitelisted unless "
+"routerconsole.allowUntrustedPlugins=true"
+msgstr ""
+
+#: i2p2www/blog/2014/08/09/0.9.14.1-Release.rst:48
+#: i2p2www/blog/2014/09/20/0.9.15-Release.rst:71
+msgid "More escaping and cleanups in forms and messages"
+msgstr ""
+
+#: i2p2www/blog/2014/08/15/The-privacy-solutions-project.rst:1
+msgid ""
+"==============================\n"
+"The birth of Privacy Solutions\n"
+"=============================="
+msgstr ""
+
+#: i2p2www/blog/2014/08/15/The-privacy-solutions-project.rst:10
+msgid "Organization launch"
+msgstr ""
+
+#: i2p2www/blog/2014/08/15/The-privacy-solutions-project.rst:14
+msgid ""
+"Hello all!\n"
+"\n"
+"Today we announce the Privacy Solutions project, a new organization that "
+"develops and maintains I2P software. Privacy Solutions includes several "
+"new development efforts designed to enhance the privacy, security, and "
+"anonymity for users, based on I2P protocols and technology.\n"
+"\n"
+"These efforts include\n"
+"\n"
+"1) The Abscond browser bundle.\n"
+"2) The i2pd C++ router project.\n"
+"3) The \"BigBrother\" I2P network monitoring project.\n"
+"4) The Anoncoin crypto-coin project.\n"
+"5) The Monero crypto-coin project.\n"
+"\n"
+"Privacy Solutions' initial funding was provided by the supporters of the "
+"Anoncoin and Monero projects. Privacy Solutions is a Norway-based non-"
+"profit type of organization registered within the Norwegian government "
+"registers. ( Kind of like US 501(c)3. )\n"
+"\n"
+"Privacy Solutions plans to apply for funding from the Norwegian goverment"
+" for network research, because of BigBrother (We'll get back to what that"
+" is) and the coins that are planned to use low-latency networks as "
+"primary transport layer. Our research will support advances in software "
+"technology for anonymity, security, and privacy.\n"
+"\n"
+"\n"
+"First a little bit about the Abscond Browser Bundle. This was first a "
+"one-man project by Meeh, but later on friends started sending patches, "
+"the project is now trying to create the same easy access to I2P as Tor "
+"has with their browser bundle. Our first release isn't far away, it's "
+"just some gitian script tasks left, including setup of the Apple "
+"toolchain. But again we will add monitoring with PROCESS_INFORMATION (A C"
+" struct keeping vital proces information about an process) from the Java "
+"instance to check on I2P before we declare it stable. I2pd will also "
+"switch with the Java version once it's ready, and there is no point in "
+"shipping a JRE in the bundle anymore. You can read more about the Abscond"
+" Browser Bundle at https://hideme.today/dev"
+msgstr ""
+
+#: i2p2www/blog/2014/08/15/The-privacy-solutions-project.rst:36
+msgid ""
+"We would also like to inform of the current status of i2pd. I2pd supports"
+" bi-directional streaming now, that allows to use not only HTTP but long-"
+"lived communication channels. Instant IRC support has been added. I2pd "
+"users are able to use it same way as Java I2P for access to I2P IRC "
+"network. I2PTunnel is one of key features of I2P network, allowing non-"
+"I2P applications communicate transparently. That's why it's vital feature"
+" for i2pd and one of key milestones."
+msgstr ""
+
+#: i2p2www/blog/2014/08/15/The-privacy-solutions-project.rst:40
+msgid ""
+"At last, if you are familiar with I2P you probably know about "
+"Bigbrother.i2p, which is a metrics system Meeh made over a year back. "
+"Recently we noticed that Meeh actually have 100Gb of non-duplicated data "
+"from nodes reporting in since initial launch. This will also be moved to "
+"Privacy Solutions and be rewritten with a NSPOF backend. With this we "
+"will aslo start using the Graphite ( http://graphite.wikidot.com/screen-"
+"shots ). This will give us a great overview over the network without "
+"privacy issues for our end users. The clients filter all data except "
+"country, router hash and success rate on tunnel buildings. The name of "
+"this service is as always a little joke from Meeh."
+msgstr ""
+
+#: i2p2www/blog/2014/08/15/The-privacy-solutions-project.rst:47
+msgid ""
+"We have shorted down a bit of the news here, if you're interested in more"
+" information please visit https://blog.privacysolutions.no/\n"
+"We're still under construction and more content will come!\n"
+"\n"
+"\n"
+"\n"
+"For further information contact: press@privacysolutions.no\n"
+"\n"
+"\n"
+"\n"
+"\n"
+"Best regards,\n"
+"\n"
+"Mikal \"Meeh\" Villa"
+msgstr ""
+
+#: i2p2www/blog/2014/08/23/Android-test-release-on-Google-Play-in-Norway.rst:1
+msgid ""
+"=============================================\n"
+"Android test release on Google Play in Norway\n"
+"============================================="
+msgstr ""
+
+#: i2p2www/blog/2014/08/23/Android-test-release-on-Google-Play-in-Norway.rst:10
+msgid ""
+"I2P Android and Bote have been released on Google Play in Norway, as a "
+"test run for a future worldwide release."
+msgstr ""
+
+#: i2p2www/blog/2014/08/23/Android-test-release-on-Google-Play-in-Norway.rst:12
+msgid ""
+"I2P Android has existed for over three years. In that time, it has "
+"evolved from\n"
+"a simple test project into a usable, useful Android port of the I2P "
+"router. Our\n"
+"eventual goal has been to release I2P Android on Google Play, to make it "
+"easier\n"
+"for users to discover, install and use I2P on their Android devices. "
+"After much\n"
+"work improving the user interface, fixing bugs and testing, we think that"
+" I2P\n"
+"Android is finally ready to go where the users are."
+msgstr ""
+
+#: i2p2www/blog/2014/08/23/Android-test-release-on-Google-Play-in-Norway.rst:21
+msgid ""
+"Initially, we are only releasing to Android users in Norway, as a test "
+"run. I2P\n"
+"Android will have far more exposure on Google Play than it has ever had "
+"before,\n"
+"and there will be bugs and usability issues that we need to fix. It will "
+"be much\n"
+"easier (and less stressful!) to respond to feedback if we only need to "
+"deal with\n"
+"reports from hundreds of users instead of thousands (already orders of "
+"magnitude\n"
+"more feedback than we have ever had)."
+msgstr ""
+
+#: i2p2www/blog/2014/08/23/Android-test-release-on-Google-Play-in-Norway.rst:30
+msgid ""
+"Simultaneously we are making the first public release of Bote, an Android"
+" port\n"
+"of `I2P-Bote`_. Bote is private, distributed, secure email, made easy. It"
+" runs\n"
+"on top of the I2P network, and while it works as a standalone app, it "
+"will use\n"
+"the I2P Android app by default if installed. As with I2P Android, we are\n"
+"initially only releasing Bote to Android users in Norway."
+msgstr ""
+
+#: i2p2www/blog/2014/08/23/Android-test-release-on-Google-Play-in-Norway.rst:38
+msgid ""
+"The apps are being released on Google Play by `The Privacy Solutions "
+"Project`_.\n"
+"See their `blog post`_ for further information, and links to the Google "
+"Play\n"
+"page for Norway users."
+msgstr ""
+
+#: i2p2www/blog/2014/08/23/Android-test-release-on-Google-Play-in-Norway.rst:44
+msgid ""
+"As lead developer for I2P Android and Bote, I look forward to your "
+"comments. You\n"
+"are the people who will be using them, and your perspectives will help me"
+" craft\n"
+"simple, intuitive apps that make privacy accessible to everyone."
+msgstr ""
+
+#: i2p2www/blog/2014/08/23/Android-test-release-on-Google-Play-in-Norway.rst:51
+msgid "`The Privacy Solutions Project`"
+msgstr ""
+
+#: i2p2www/blog/2014/08/23/Android-test-release-on-Google-Play-in-Norway.rst:52
+msgid "`blog post`"
+msgstr ""
+
+#: i2p2www/blog/2014/08/23/Android-test-release-on-Google-Play-in-Norway.rst:54
+msgid "Website release details"
+msgstr ""
+
+#: i2p2www/blog/2014/08/23/Android-test-release-on-Google-Play-in-Norway.rst:56
+msgid ""
+"We have also updated I2P Android on the website to match the release "
+"candidate\n"
+"deployed in Norway. This version will be updated with changes as we "
+"respond to\n"
+"feedback from Norwegian users, heading towards our next stable release."
+msgstr ""
+
+#: i2p2www/blog/2014/08/23/Android-test-release-on-Google-Play-in-Norway.rst:62
+msgid ""
+"Please note that we have upgraded the Android API to 9. This means that "
+"Froyo\n"
+"Android 2.2 will not be supported anymore; the minimum requirement is now"
+"\n"
+"Gingerbread Android 2.3."
+msgstr ""
+
+#: i2p2www/blog/2014/08/23/Android-test-release-on-Google-Play-in-Norway.rst:68
+msgid ""
+"Also note that if you have an earlier version of I2P Android, you will "
+"need to\n"
+"uninstall and reinstall because we have changed the release keys. Further"
+"\n"
+"information about this will be provided in a subsequent blog post."
+msgstr ""
+
+#: i2p2www/blog/2014/09/20/0.9.15-Release.rst:1
+msgid ""
+"==============\n"
+"0.9.15 Release\n"
+"=============="
+msgstr ""
+
+#: i2p2www/blog/2014/09/20/0.9.15-Release.rst:10
+msgid "0.9.15 includes Ed25519 crypto and many fixes"
+msgstr ""
+
+#: i2p2www/blog/2014/09/20/0.9.15-Release.rst:12
+msgid ""
+"0.9.15 adds preliminary support for Ed25519 EdDSA signatures.\n"
+"It includes a new persistent configuration backend for i2psnark and fixes"
+" several issues with i2psnark's handling of file names.\n"
+"There are several improvements to speed up SAM.\n"
+"Plugins now support stronger signatures in the su3 file format.\n"
+"Plugin installation via the console, which was disabled in 0.9.14, is re-"
+"enabled."
+msgstr ""
+
+#: i2p2www/blog/2014/09/20/0.9.15-Release.rst:20
+msgid ""
+"We have supported ECDSA signatures since 0.9.12, and we would like to "
+"start using ECDSA by default.\n"
+"Unfortunately, some of you are still running older I2P versions, and for "
+"others,\n"
+"their distribution or Java runtime does not support ECDSA. Red Hat\n"
+"(RHEL, Fedora) distributions are reported to be missing ECDSA.\n"
+"Some have fixed the Java issues by upgrading from Java 6 to Java 7;\n"
+"others have had success with installing the \"unlimited strength policy "
+"files\".\n"
+"We've added information about missing crypto to the log file and the "
+"/logs page in the console.\n"
+"After you update to 0.9.15, please check if you are missing ECDSA "
+"support, and attempt to fix it if necessary.\n"
+"This is particularly important for those that run popular eepsites and "
+"services."
+msgstr ""
+
+#: i2p2www/blog/2014/09/20/0.9.15-Release.rst:41
+#: i2p2www/blog/2014/11/01/0.9.16-Release.rst:39
+#: i2p2www/blog/2014/11/30/0.9.17-Release.rst:46
+#: i2p2www/blog/2015/04/12/0.9.19-Release.rst:32
+#: i2p2www/blog/2015/06/02/0.9.20-Release.rst:46
+#: i2p2www/blog/2015/07/31/0.9.21-Release.rst:38
+#: i2p2www/blog/2015/09/12/0.9.22-Release.rst:36
+#: i2p2www/blog/2015/11/19/0.9.23-Release.rst:75
+#: i2p2www/blog/2016/01/27/0.9.24-Release.rst:55
+#: i2p2www/blog/2016/03/22/0.9.25-Release.rst:37
+#: i2p2www/blog/2016/06/07/0.9.26-Release.rst:56
+#: i2p2www/blog/2016/10/17/0.9.27-Release.rst:35
+#: i2p2www/blog/2016/12/12/0.9.28-Release.rst:37
+#: i2p2www/blog/2017/02/27/0.9.29-Release.rst:34
+#: i2p2www/blog/2017/05/03/0.9.30-Release.rst:58
+#: i2p2www/blog/2017/08/07/0.9.31-Release.rst:34
+#: i2p2www/blog/2017/11/07/0.9.32-Release.rst:31
+#: i2p2www/blog/2018/01/30/0.9.33-Release.rst:32
+#: i2p2www/blog/2018/04/10/0.9.34-Release.rst:32
+#: i2p2www/blog/2018/06/26/0.9.35-Release.rst:38
+#: i2p2www/blog/2018/08/23/0.9.36-Release.rst:35
+msgid "Changes"
+msgstr ""
+
+#: i2p2www/blog/2014/09/20/0.9.15-Release.rst:43
+msgid "Add support for Ed25519 signatures"
+msgstr ""
+
+#: i2p2www/blog/2014/09/20/0.9.15-Release.rst:44
+msgid ""
+"i2psnark move to separate config file for each torrent to better support "
+"per-torrent settings"
+msgstr ""
+
+#: i2p2www/blog/2014/09/20/0.9.15-Release.rst:45
+msgid "Add i2psnark support for data outside the i2psnark/ directory"
+msgstr ""
+
+#: i2p2www/blog/2014/09/20/0.9.15-Release.rst:46
+msgid "Enable stronger signatures (su3 format) for plugins"
+msgstr ""
+
+#: i2p2www/blog/2014/09/20/0.9.15-Release.rst:47
+msgid "Speed up SSU introductions by responding to hole punch messages"
+msgstr ""
+
+#: i2p2www/blog/2014/09/20/0.9.15-Release.rst:48
+msgid "Several improvements in SAM efficiency"
+msgstr ""
+
+#: i2p2www/blog/2014/09/20/0.9.15-Release.rst:53
+msgid "Form submission fixes in the console and i2psnark"
+msgstr ""
+
+#: i2p2www/blog/2014/09/20/0.9.15-Release.rst:54
+msgid "Streaming fixes for long signatures"
+msgstr ""
+
+#: i2p2www/blog/2014/09/20/0.9.15-Release.rst:55
+msgid "i2psnark fixes for file name character mapping when seeding"
+msgstr ""
+
+#: i2p2www/blog/2014/09/20/0.9.15-Release.rst:56
+msgid "I2PTunnel fixes stopping client tunnels"
+msgstr ""
+
+#: i2p2www/blog/2014/09/20/0.9.15-Release.rst:57
+msgid "I2PTunnel fix updating options on a running delay-open client tunnel"
+msgstr ""
+
+#: i2p2www/blog/2014/09/20/0.9.15-Release.rst:62
+msgid "Re-enable plugin installation via the console, removed in 0.9.14"
+msgstr ""
+
+#: i2p2www/blog/2014/09/20/0.9.15-Release.rst:63
+msgid "i2psnark now remembers uploaded count across restarts"
+msgstr ""
+
+#: i2p2www/blog/2014/09/20/0.9.15-Release.rst:64
+msgid "i2psnark increase max piece size to 8 MB"
+msgstr ""
+
+#: i2p2www/blog/2014/09/20/0.9.15-Release.rst:65
+msgid "i2psnark several UI fixes"
+msgstr ""
+
+#: i2p2www/blog/2014/09/20/0.9.15-Release.rst:66
+msgid "Prohibit SSU peer test requests unless a connection is established"
+msgstr ""
+
+#: i2p2www/blog/2014/09/20/0.9.15-Release.rst:67
+msgid ""
+"i2ptunnel add support for local SSL connections for standard and IRC "
+"client tunnels"
+msgstr ""
+
+#: i2p2www/blog/2014/09/20/0.9.15-Release.rst:68
+msgid "Console and log warnings for unavailable crypto"
+msgstr ""
+
+#: i2p2www/blog/2014/09/20/0.9.15-Release.rst:69
+msgid ""
+"More consistent routing for Delivery Status Messages to reduce network "
+"connections"
+msgstr ""
+
+#: i2p2www/blog/2014/09/20/0.9.15-Release.rst:70
+msgid "Disable external entities in UPnP XML parser"
+msgstr ""
+
+#: i2p2www/blog/2014/09/20/0.9.15-Release.rst:73
+msgid "Update GeoIP data (in both new installs and updates)"
+msgstr ""
+
+#: i2p2www/blog/2014/11/01/0.9.16-Release.rst:1
+msgid ""
+"==============\n"
+"0.9.16 Release\n"
+"=============="
+msgstr ""
+
+#: i2p2www/blog/2014/11/01/0.9.16-Release.rst:10
+msgid "0.9.16 includes crypto migration and many fixes"
+msgstr ""
+
+#: i2p2www/blog/2014/11/01/0.9.16-Release.rst:12
+msgid ""
+"0.9.16 is a significant step forward in our plan to migrate\n"
+"from DSA to ECDSA and then EdDSA cryptographic signatures,\n"
+"and makes several other changes to increase your anonymity and security.\n"
+"Client tunnels for standard, IRC, and SOCKS IRC will use ECDSA signatures"
+" by default.\n"
+"In addition, we've fixed a large number of serious bugs, including "
+"console lockups."
+msgstr ""
+
+#: i2p2www/blog/2014/11/01/0.9.16-Release.rst:20
+msgid ""
+"Changes in router data structures will require i2pcontrol plugin users to"
+" update to version 0.0.9."
+msgstr ""
+
+#: i2p2www/blog/2014/11/01/0.9.16-Release.rst:24
+msgid ""
+"If you run an eepsite or a service and you are not running a recent "
+"release,\n"
+"or your Java or OS does not support ECDSA (as noted in the logs and on "
+"the /logs page in the console),\n"
+"please fix the issue as soon as possible or your users will soon be "
+"unable to connect."
+msgstr ""
+
+#: i2p2www/blog/2014/11/01/0.9.16-Release.rst:41
+msgid "Add support for stronger Router Info signatures"
+msgstr ""
+
+#: i2p2www/blog/2014/11/01/0.9.16-Release.rst:42
+msgid "Encrypt RI lookups and responses on faster boxes"
+msgstr ""
+
+#: i2p2www/blog/2014/11/01/0.9.16-Release.rst:43
+msgid ""
+"Require I2CP authorization for all messages when enabled (requires 0.9.11"
+" or higher client)"
+msgstr ""
+
+#: i2p2www/blog/2014/11/01/0.9.16-Release.rst:44
+msgid "Disable SSLv3 and older ciphers for reseeding and other uses of SSL"
+msgstr ""
+
+#: i2p2www/blog/2014/11/01/0.9.16-Release.rst:45
+msgid ""
+"Use ECDSA by default for i2ptunnel IRC, SOCKS-IRC, and standard client "
+"tunnels"
+msgstr ""
+
+#: i2p2www/blog/2014/11/01/0.9.16-Release.rst:46
+msgid "Don't prefer floodfills in some countries"
+msgstr ""
+
+#: i2p2www/blog/2014/11/01/0.9.16-Release.rst:47
+msgid ""
+"New column sorting, set-all priority buttons, and upload ratio display in"
+" i2psnark"
+msgstr ""
+
+#: i2p2www/blog/2014/11/01/0.9.16-Release.rst:48
+msgid "Increase i2psnark tunnel default to 3 hops"
+msgstr ""
+
+#: i2p2www/blog/2014/11/01/0.9.16-Release.rst:49
+msgid ""
+"Implement bundling of multiple fragments in a single SSU message for "
+"efficiency"
+msgstr ""
+
+#: i2p2www/blog/2014/11/01/0.9.16-Release.rst:50
+msgid "New add-to-addressbook links on netdb leaseset page"
+msgstr ""
+
+#: i2p2www/blog/2014/11/01/0.9.16-Release.rst:51
+msgid ""
+"Implement I2NP DatabaseLookupMessage search type field to improve lookup "
+"efficiency"
+msgstr ""
+
+#: i2p2www/blog/2014/11/01/0.9.16-Release.rst:58
+msgid "CPUID fixes and updates for recent processors"
+msgstr ""
+
+#: i2p2www/blog/2014/11/01/0.9.16-Release.rst:59
+#, python-format
+msgid "i2psnark fix magnet links with %(pc)s-encoding"
+msgstr ""
+
+#: i2p2www/blog/2014/11/01/0.9.16-Release.rst:60
+#, python-format
+msgid ""
+"Improve handling of SSU socket closing out from under us (hopefully fix "
+"100%(pc)s CPU)"
+msgstr ""
+
+#: i2p2www/blog/2014/11/01/0.9.16-Release.rst:61
+msgid "SSU bitfield handling fixes"
+msgstr ""
+
+#: i2p2www/blog/2014/11/01/0.9.16-Release.rst:62
+msgid "Fix HTTP header issues in i2psnark"
+msgstr ""
+
+#: i2p2www/blog/2014/11/01/0.9.16-Release.rst:63
+msgid "Fix rare NPE when building garlic message"
+msgstr ""
+
+#: i2p2www/blog/2014/11/01/0.9.16-Release.rst:64
+msgid "Fix console lockups (hopefully)"
+msgstr ""
+
+#: i2p2www/blog/2014/11/01/0.9.16-Release.rst:65
+msgid "Fix i2ptunnel js confirm-delete"
+msgstr ""
+
+#: i2p2www/blog/2014/11/01/0.9.16-Release.rst:70
+msgid ""
+"Move router data structures from i2p.jar to router.jar (breaks i2pcontrol"
+" plugin)"
+msgstr ""
+
+#: i2p2www/blog/2014/11/01/0.9.16-Release.rst:71
+msgid ""
+"New router keys now stored in router.keys.dat (eepPriv.dat format) "
+"instead of router.keys"
+msgstr ""
+
+#: i2p2www/blog/2014/11/01/0.9.16-Release.rst:72
+msgid "Improve handling of unsupported encryption throughout"
+msgstr ""
+
+#: i2p2www/blog/2014/11/01/0.9.16-Release.rst:73
+msgid "More error checking of client I2CP messages by the router"
+msgstr ""
+
+#: i2p2www/blog/2014/11/01/0.9.16-Release.rst:74
+msgid "Initial work on hooks for pluggable transports"
+msgstr ""
+
+#: i2p2www/blog/2014/11/01/0.9.16-Release.rst:75
+msgid "Enforce request timestamp in tunnel build messages"
+msgstr ""
+
+#: i2p2www/blog/2014/11/01/0.9.16-Release.rst:76
+msgid ""
+"Re-enable message status in streaming, but treat no leaseset as a soft "
+"failure for now"
+msgstr ""
+
+#: i2p2www/blog/2014/11/01/0.9.16-Release.rst:77
+msgid "Return unused DH keypairs to the pool for efficiency"
+msgstr ""
+
+#: i2p2www/blog/2014/11/01/0.9.16-Release.rst:78
+msgid "Raise failsafe tagset limit and improve deletion strategy when hit"
+msgstr ""
+
+#: i2p2www/blog/2014/11/01/0.9.16-Release.rst:79
+msgid ""
+"Change eepsite Jetty threadpool and queue configuration (new installs "
+"only)"
+msgstr ""
+
+#: i2p2www/blog/2014/11/01/0.9.16-Release.rst:80
+msgid "NTCP establishment refactoring in prep for NTCP2 and PT"
+msgstr ""
+
+#: i2p2www/blog/2014/11/30/0.9.17-Release.rst:1
+msgid ""
+"==============\n"
+"0.9.17 Release\n"
+"=============="
+msgstr ""
+
+#: i2p2www/blog/2014/11/30/0.9.17-Release.rst:10
+msgid "0.9.17 with more crypto migration and many fixes"
+msgstr ""
+
+#: i2p2www/blog/2014/11/30/0.9.17-Release.rst:12
+msgid ""
+"0.9.17 is primarily a bugfix release, but it also continues our migration"
+" to stronger cryptographic signatures."
+msgstr ""
+
+#: i2p2www/blog/2014/11/30/0.9.17-Release.rst:16
+msgid ""
+"We have moved the news feed system used for the news on your console and "
+"the latest router version indication\n"
+"to a signed format using RSA 4096-bit keys for enhanced security."
+msgstr ""
+
+#: i2p2www/blog/2014/11/30/0.9.17-Release.rst:21
+msgid ""
+"New eepsites and servers will be ECDSA-signed by default, if ECDSA is "
+"available.\n"
+"There is now a warning in the console sidebar if ECDSA is not available.\n"
+"For RedHat users, we have reports of successful installs of the "
+"BouncyCastle Provider (bcprov) jar to add ECDSA support."
+msgstr ""
+
+#: i2p2www/blog/2014/11/30/0.9.17-Release.rst:27
+msgid ""
+"We've fixed several serious bugs, including an SSU packet corruption "
+"problem,\n"
+"and a SAM bug affecting i2p-messenger and other SAM applications.\n"
+"There are several fixes for the preliminary ECDSA router signatures added"
+" in the last release but not yet enabled."
+msgstr ""
+
+#: i2p2www/blog/2014/11/30/0.9.17-Release.rst:33
+msgid ""
+"Many of us will be attending 31C3 in Hamburg in December. Stop by our "
+"table and say hi!"
+msgstr ""
+
+#: i2p2www/blog/2014/11/30/0.9.17-Release.rst:48
+msgid "Signed news"
+msgstr ""
+
+#: i2p2www/blog/2014/11/30/0.9.17-Release.rst:49
+msgid "ECDSA default for new server tunnels"
+msgstr ""
+
+#: i2p2www/blog/2014/11/30/0.9.17-Release.rst:50
+msgid "Reseeding now SSL-only by default"
+msgstr ""
+
+#: i2p2www/blog/2014/11/30/0.9.17-Release.rst:55
+msgid "Fix SSU sending corrupt ack-only packets with partial bitfields"
+msgstr ""
+
+#: i2p2www/blog/2014/11/30/0.9.17-Release.rst:56
+msgid "Fix SSU inbound connection fail from non-DSA router"
+msgstr ""
+
+#: i2p2www/blog/2014/11/30/0.9.17-Release.rst:57
+msgid "Don't select incompatible peers if we are a non-DSA router"
+msgstr ""
+
+#: i2p2www/blog/2014/11/30/0.9.17-Release.rst:58
+msgid "Fix EdDSA signature verification bug"
+msgstr ""
+
+#: i2p2www/blog/2014/11/30/0.9.17-Release.rst:59
+msgid ""
+"Set I2NP lookup type flags in all cases, not just when a reply tunnel is "
+"used"
+msgstr ""
+
+#: i2p2www/blog/2014/11/30/0.9.17-Release.rst:60
+msgid "Stop i2ptunnel server acceptor thread after close"
+msgstr ""
+
+#: i2p2www/blog/2014/11/30/0.9.17-Release.rst:61
+msgid "Fix bug preventing some plugins from stopping completely"
+msgstr ""
+
+#: i2p2www/blog/2014/11/30/0.9.17-Release.rst:62
+msgid "Fix SAM v3 bug causing failures in incoming connections"
+msgstr ""
+
+#: i2p2www/blog/2014/11/30/0.9.17-Release.rst:67
+msgid "Add a warning in the console sidebar if ECDSA not supported"
+msgstr ""
+
+#: i2p2www/blog/2014/11/30/0.9.17-Release.rst:68
+msgid "Log warnings for Java 6 that we will eventually require Java 7"
+msgstr ""
+
+#: i2p2www/blog/2014/11/30/0.9.17-Release.rst:69
+msgid "Don't let proxied routers auto-floodfill"
+msgstr ""
+
+#: i2p2www/blog/2014/11/30/0.9.17-Release.rst:70
+msgid "Don't resend SSU acks that are too old"
+msgstr ""
+
+#: i2p2www/blog/2014/11/30/0.9.17-Release.rst:71
+msgid "Don't publish direct info in SSU address if introducers are required"
+msgstr ""
+
+#: i2p2www/blog/2014/11/30/0.9.17-Release.rst:72
+msgid "New default opentrackers in i2psnark"
+msgstr ""
+
+#: i2p2www/blog/2014/11/30/0.9.17-Release.rst:73
+msgid "Add support for specifiying data directory per-torrent in i2psnark"
+msgstr ""
+
+#: i2p2www/blog/2014/11/30/0.9.17-Release.rst:74
+msgid "Changes in streaming accept() error behavior"
+msgstr ""
+
+#: i2p2www/blog/2014/11/30/0.9.17-Release.rst:75
+msgid "Minor blockfile format changes"
+msgstr ""
+
+#: i2p2www/blog/2014/11/30/0.9.17-Release.rst:76
+msgid ""
+"New option for persistent random key to preserve peer ordering across "
+"restarts"
+msgstr ""
+
+#: i2p2www/blog/2014/12/01/Android-app-releases.rst:1
+msgid ""
+"====================\n"
+"Android app releases\n"
+"===================="
+msgstr ""
+
+#: i2p2www/blog/2014/12/01/Android-app-releases.rst:10
+msgid ""
+"I2P Android 0.9.17 and Bote 0.3 have been released on the website, Google"
+" Play and F-Droid."
+msgstr ""
+
+#: i2p2www/blog/2014/12/01/Android-app-releases.rst:12
+msgid ""
+"It has been some time since I last posted updates about our Android "
+"development,\n"
+"and several I2P releases have gone by without any matching Android "
+"releases.\n"
+"At last, the wait is over!"
+msgstr ""
+
+#: i2p2www/blog/2014/12/01/Android-app-releases.rst:18
+msgid ""
+"New app versions\n"
+"----------------"
+msgstr ""
+
+#: i2p2www/blog/2014/12/01/Android-app-releases.rst:23
+msgid ""
+"New versions of I2P Android and Bote have been released! They can be "
+"downloaded\n"
+"from these URLs:"
+msgstr ""
+
+#: i2p2www/blog/2014/12/01/Android-app-releases.rst:31
+msgid ""
+"The main change in these releases is the transition to Android's new "
+"Material\n"
+"design system. Material has made it much easier for app developers with, "
+"shall\n"
+"we say, \"minimalist\" design skills (like myself) to create apps that "
+"are nicer\n"
+"to use. I2P Android also updates its underlying I2P router to the just-"
+"released\n"
+"version 0.9.17. Bote brings in several new features along with many "
+"smaller\n"
+"improvements; for example, you can now add new email destinations via QR "
+"codes."
+msgstr ""
+
+#: i2p2www/blog/2014/12/01/Android-app-releases.rst:40
+msgid ""
+"As I mentioned in `my last update`_, the release key that signs the apps "
+"has\n"
+"changed. The reason for this was because we needed to change the package "
+"name\n"
+"of I2P Android. The old package name (``net.i2p.android.router``) had "
+"already\n"
+"been taken on Google Play (we still don't know who was using it), and we "
+"wanted\n"
+"to use the same package name and signing key for all distributions of I2P"
+"\n"
+"Android. Doing so means that a user could initially install the app from "
+"the I2P\n"
+"website, and then later if the website was blocked they could upgrade it "
+"using\n"
+"Google Play. Android OS considers an application to be completely "
+"different when\n"
+"its package name changes, so we took the opportunity to increase the "
+"strength of\n"
+"the signing key."
+msgstr ""
+
+#: i2p2www/blog/2014/12/01/Android-app-releases.rst:53
+msgid "The fingerprint (SHA-256) of the new signing key is:"
+msgstr ""
+
+#: i2p2www/blog/2014/12/01/Android-app-releases.rst:63
+msgid "`my last update`"
+msgstr ""
+
+#: i2p2www/blog/2014/12/01/Android-app-releases.rst:65
+msgid ""
+"Google Play\n"
+"-----------"
+msgstr ""
+
+#: i2p2www/blog/2014/12/01/Android-app-releases.rst:70
+msgid ""
+"A few months ago we `released`_ both I2P Android and Bote on Google Play "
+"in\n"
+"Norway, to test the release process there. We are pleased to announce "
+"that both\n"
+"apps are now being released globally by `Privacy Solutions`_. The apps "
+"can be\n"
+"found at these URLs:"
+msgstr ""
+
+#: i2p2www/blog/2014/12/01/Android-app-releases.rst:80
+msgid ""
+"The global release is being done in several stages, starting with the "
+"countries\n"
+"for which we have translations. The notable exception to this is France; "
+"due to\n"
+"import regulations on cryptographic code, we are unable yet to distribute"
+" these\n"
+"apps on Google Play France. This is the same issue that has affected "
+"other apps\n"
+"like TextSecure and Orbot."
+msgstr ""
+
+#: i2p2www/blog/2014/12/01/Android-app-releases.rst:88
+msgid "`released`"
+msgstr ""
+
+#: i2p2www/blog/2014/12/01/Android-app-releases.rst:90
+msgid "`I2P on Google Play`"
+msgstr ""
+
+#: i2p2www/blog/2014/12/01/Android-app-releases.rst:91
+msgid "`Bote on Google Play`"
+msgstr ""
+
+#: i2p2www/blog/2014/12/01/Android-app-releases.rst:93
+msgid ""
+"F-Droid\n"
+"-------"
+msgstr ""
+
+#: i2p2www/blog/2014/12/01/Android-app-releases.rst:98
+msgid ""
+"Don't think we have forgotten about you, F-Droid users! In addition to "
+"the two\n"
+"locations above, we have set up our own F-Droid repository. If you are "
+"reading\n"
+"this post on your phone, `click here`_ to add it to F-Droid (this only "
+"works in\n"
+"some Android browsers). Or, you can manually add the URL below to your "
+"F-Droid\n"
+"repository list:"
+msgstr ""
+
+#: i2p2www/blog/2014/12/01/Android-app-releases.rst:108
+msgid ""
+"If you would like to manually verify the fingerprint (SHA-256) of the "
+"repository\n"
+"signing key, or type it in when adding the repository, here it is:"
+msgstr ""
+
+#: i2p2www/blog/2014/12/01/Android-app-releases.rst:117
+msgid ""
+"Unfortunately the I2P app in the main F-Droid repository has not been "
+"updated\n"
+"because our F-Droid maintainer has disappeared. We hope that by "
+"maintaining this\n"
+"binary repository, we can better support our F-Droid users and keep them\n"
+"up-to-date. If you have already installed I2P from the main F-Droid "
+"repository,\n"
+"you will need to uninstall it if you want to upgrade, because the signing"
+" key\n"
+"will be different. The apps in our F-Droid repository are the same APKs "
+"that are\n"
+"provided on our website and on Google Play, so in future you will be able"
+" to\n"
+"upgrade using any of these sources."
+msgstr ""
+
+#: i2p2www/blog/2014/12/01/Android-app-releases.rst:128
+msgid "`click here`"
+msgstr ""
+
+#: i2p2www/blog/2015/01/20/31C3-trip-report.rst:1
+msgid ""
+"================\n"
+"31C3 trip report\n"
+"================"
+msgstr ""
+
+#: i2p2www/blog/2015/01/20/31C3-trip-report.rst:9
+msgid ""
+"CCC has always been a productive time for us, and 31C3 was no exception. "
+"Here is a summary of our various meetings and discussions."
+msgstr ""
+
+#: i2p2www/blog/2015/01/20/31C3-trip-report.rst:20
+msgid ""
+"We were, for the second year in a row, at a great location in the "
+"Congress, in\n"
+"`Noisy Square`_, right next to the EFF table. Being part of Noisy Square "
+"has\n"
+"really increased our visibility and helped many people find us. Thanks to"
+" Noisy\n"
+"Square and the 31C3 organizers for a great Congress."
+msgstr ""
+
+#: i2p2www/blog/2015/01/20/31C3-trip-report.rst:29
+msgid ""
+"We also thank Gabriel Weinberg and his fabulous search engine "
+"`DuckDuckGo`_ for\n"
+"their support of open source anonymity tools and their `generous "
+"contribution`_\n"
+"to I2P in 2014. Funding from DuckDuckGo and others helped support our "
+"attendance\n"
+"at CCC. This is the primary annual meetup for I2P developers and it is "
+"critical\n"
+"to our success."
+msgstr ""
+
+#: i2p2www/blog/2015/01/20/31C3-trip-report.rst:38
+msgid "`generous contribution`"
+msgstr ""
+
+#: i2p2www/blog/2015/01/20/31C3-trip-report.rst:40
+msgid ""
+"Discussions with others\n"
+"======================="
+msgstr ""
+
+#: i2p2www/blog/2015/01/20/31C3-trip-report.rst:48
+msgid ""
+"We spoke at length with Christian Grothoff of `GNUnet`_. He has moved "
+"himself\n"
+"and the project from TU Munich to `Inria`_ in France. He has a large "
+"number of\n"
+"`open positions`_. This is a great opportunity to get paid to work on "
+"open\n"
+"source anonymity tools, we encourage everybody to contact him about it."
+msgstr ""
+
+#: i2p2www/blog/2015/01/20/31C3-trip-report.rst:57
+msgid "`open positions`"
+msgstr ""
+
+#: i2p2www/blog/2015/01/20/31C3-trip-report.rst:59
+msgid ""
+"The prospect of an invigorated GNUnet with a large amount of new funding "
+"is\n"
+"quite interesting. We discussed more ways to work together. In early "
+"2014, we\n"
+"worked hard to understand the GnuNet DNS replacement, but we were unable "
+"to\n"
+"figure out a good fit for it in I2P. One of his new ideas is a "
+"distributed,\n"
+"anonymous statistics gathering subsystem, for detecting problems or "
+"attacks on\n"
+"the network. We'd definitely be interested in that."
+msgstr ""
+
+#: i2p2www/blog/2015/01/20/31C3-trip-report.rst:68
+msgid ""
+"We also discussed the `Special-Use Domain Names of Peer-to-Peer Systems "
+"draft`_.\n"
+"A new, greatly simplified version 3 was posted in December. The prospects"
+" for\n"
+"approval remain unclear. The best way to monitor or participate in the\n"
+"discussion is via the `IETF DNSOP WG mailing list`_. We will attempt to "
+"do so\n"
+"on our side, and also give Hellekin a new point-of-contact for this topic."
+msgstr ""
+
+#: i2p2www/blog/2015/01/20/31C3-trip-report.rst:76
+msgid "`Special-Use Domain Names of Peer-to-Peer Systems draft`"
+msgstr ""
+
+#: i2p2www/blog/2015/01/20/31C3-trip-report.rst:77
+msgid "`IETF DNSOP WG mailing list`"
+msgstr ""
+
+#: i2p2www/blog/2015/01/20/31C3-trip-report.rst:79
+msgid ""
+"We apologized to Christian for not being organized enough to have a talk "
+"at his\n"
+"`We Fix The Net assembly`_. One of our biggest failures as a project is "
+"our\n"
+"seeming inability to submit talks at conferences. We'll have to do better"
+" in the\n"
+"new year."
+msgstr ""
+
+#: i2p2www/blog/2015/01/20/31C3-trip-report.rst:86
+msgid "`We Fix The Net assembly`"
+msgstr ""
+
+#: i2p2www/blog/2015/01/20/31C3-trip-report.rst:91
+msgid ""
+"Iain Learmonth, a Debian participant, stopped by. He wants to put I2P in "
+"with\n"
+"other anonymity tools into this new Debian \"superpackage\" of some sort,"
+" and\n"
+"would love to get I2P into Debian in 2015. He claims the process is now "
+"easy,\n"
+"just `follow the instructions`_. We said that's funny, we've been\n"
+"`stuck in the process for over 7 years`_."
+msgstr ""
+
+#: i2p2www/blog/2015/01/20/31C3-trip-report.rst:99
+msgid "`follow the instructions`"
+msgstr ""
+
+#: i2p2www/blog/2015/01/20/31C3-trip-report.rst:100
+msgid "`stuck in the process for over 7 years`"
+msgstr ""
+
+#: i2p2www/blog/2015/01/20/31C3-trip-report.rst:102
+msgid ""
+"He said, well, try the new process, it works great, should be no problem "
+"at all\n"
+"if your package is in good shape. The people in Debian that run this "
+"process are\n"
+"eager volunteers who want nothing more than to get more packages in. We "
+"said our\n"
+"package is indeed in fantastic shape, and we would try out the new "
+"process as\n"
+"soon as possible. If all this is true, we will be in the next Debian "
+"release in\n"
+"late 2015. This would be very very cool."
+msgstr ""
+
+#: i2p2www/blog/2015/01/20/31C3-trip-report.rst:114
+msgid ""
+"We had a nice discussion with BitingBird of Tails. They are very happy "
+"with our\n"
+"rapid response to the `vulnerability disclosure`_ last summer, resulting "
+"in our\n"
+"`0.9.14 release`_. Our vulnerability was initially blamed on Tails, and "
+"they\n"
+"took `great offense`_ to that and the lack of private notification. We "
+"thanked\n"
+"them for taking the heat and fighting back."
+msgstr ""
+
+#: i2p2www/blog/2015/01/20/31C3-trip-report.rst:122
+msgid "`vulnerability disclosure`"
+msgstr ""
+
+#: i2p2www/blog/2015/01/20/31C3-trip-report.rst:123
+msgid "`0.9.14 release`"
+msgstr ""
+
+#: i2p2www/blog/2015/01/20/31C3-trip-report.rst:124
+msgid "`great offense`"
+msgstr ""
+
+#: i2p2www/blog/2015/01/20/31C3-trip-report.rst:126
+msgid ""
+"BitingBird also handles support, and she tells us the number one issue is"
+" how\n"
+"long I2P takes to start up and be useful for browsing I2P sites. Her "
+"standard\n"
+"answer is \"wait ten more minutes\" and that seems to be effective. I2P "
+"is\n"
+"particularly slow to startup on Tails since it does not persist peer data"
+" by\n"
+"default. It would be nice to change that, but there's also things we can "
+"do on\n"
+"the I2P side to make things start faster. Expect some improvement in our "
+"0.9.18\n"
+"release."
+msgstr ""
+
+#: i2p2www/blog/2015/01/20/31C3-trip-report.rst:139
+msgid ""
+"Longtime friend of I2P Bernhard Fischer of `OnionCat`_ stopped by. The "
+"upcoming\n"
+"Tor Hidden Services changes mean that their keys will no longer fit into "
+"a\n"
+"portion of an IPv6 address, and he was working on a solution. We reminded"
+" him\n"
+"that this has always been the case for I2P (with \"GarliCat\"), that it's"
+" not a\n"
+"new problem. He pointed us to `a presentation`_ of his proposal. It "
+"involves\n"
+"storing an extra record in the hidden service directory (equivalent of a\n"
+"leaseset I2P's network database). It wasn't completely clear how this "
+"would\n"
+"work, or if we would consider it abuse of the netDb. We'll follow up with"
+" him\n"
+"as he gets further."
+msgstr ""
+
+#: i2p2www/blog/2015/01/20/31C3-trip-report.rst:152
+msgid "`a presentation`"
+msgstr ""
+
+#: i2p2www/blog/2015/01/20/31C3-trip-report.rst:154
+msgid ""
+"New users\n"
+"---------"
+msgstr ""
+
+#: i2p2www/blog/2015/01/20/31C3-trip-report.rst:159
+msgid ""
+"We spent hours and hours explaining I2P to people stopping by our table. "
+"Some\n"
+"had heard of I2P before, some had not; everybody had heard of Tor and had"
+" at\n"
+"least a vague idea of what hidden services are. As usual, introducing "
+"people to\n"
+"I2P was a struggle. By the end of the Congress, we became convinced that "
+"a part\n"
+"of the problem was a difference in terminology. Back 12 years ago, when "
+"I2P and\n"
+"Tor were both getting started, we each came up with terms for the various"
+" parts\n"
+"of our systems. Today, the Tor terminology such as \"hidden service\" is\n"
+"well-understood and commonplace. The I2P terminology such as \"eepsite\" "
+"is\n"
+"neither. We agreed to review our documentation, router console, and other"
+" places\n"
+"for opportunities to simplify it and use common terms."
+msgstr ""
+
+#: i2p2www/blog/2015/01/20/31C3-trip-report.rst:172
+msgid ""
+"I2P project topics\n"
+"------------------"
+msgstr ""
+
+#: i2p2www/blog/2015/01/20/31C3-trip-report.rst:177
+msgid ""
+"* *Spending money:* We discussed several ways to effectively use our "
+"resources\n"
+"  in 2015, including more hardware for testing and development. Also, we "
+"plan to\n"
+"  increase reimbursement levels for conference attendees."
+msgstr ""
+
+#: i2p2www/blog/2015/01/20/31C3-trip-report.rst:183
+msgid ""
+"* *Toronto meetup:* CCC is such a productive time for us, and it seems "
+"that a\n"
+"  second meetup in the year would be quite helpful. We have proposed it "
+"for\n"
+"  August 2015 in Toronto, Canada, in conjunction with `Toronto Crypto`_. "
+"It\n"
+"  would include developer meetings together with presentations and "
+"tutorials,\n"
+"  all open to the public. We are attempting to gauge interest and "
+"research\n"
+"  possible venues. If you are considering attending, please let us know "
+"by\n"
+"  `tweeting @i2p`_ or posting `on the dev forum thread`_."
+msgstr ""
+
+#: i2p2www/blog/2015/01/20/31C3-trip-report.rst:193
+msgid ""
+"* We discussed Meeh's workload and the state of the various services he "
+"is\n"
+"  running. We made some plans to reduce his load and have some other "
+"people help\n"
+"  out."
+msgstr ""
+
+#: i2p2www/blog/2015/01/20/31C3-trip-report.rst:199
+msgid ""
+"* We reviewed our critieria for placing links to `i2pd`_ on our download "
+"page.\n"
+"  We agreed that the only remaining item is to have a nice page on the\n"
+"  `Privacy Solutions web site`_ or elsewhere with binary packages for "
+"Windows,\n"
+"  Linux, and Mac, and source packages. It's not clear who is responsible "
+"for\n"
+"  building the packages and where the \"official\" version is. Once "
+"there's an\n"
+"  established process for building and signing packages and an official "
+"place to\n"
+"  put them, we're ready to link to it. If it is not feasible to host it "
+"on the\n"
+"  Privacy Solutions website, we will discuss alternatives with orignal,\n"
+"  including possible migration to our download servers."
+msgstr ""
+
+#: i2p2www/blog/2015/01/20/31C3-trip-report.rst:211
+msgid ""
+"* Lots of people coming by the table asked if we had a non-Java version. "
+"It was\n"
+"  great to finally answer \"yes\" and we're eager to get the word out and"
+" get more\n"
+"  users, testers, and developers on it."
+msgstr ""
+
+#: i2p2www/blog/2015/01/20/31C3-trip-report.rst:217
+msgid ""
+"* `Vuze`_ continues to make good progress on their I2P integration. We "
+"look\n"
+"  forward to working with them in the new year on a managed rollout to "
+"more\n"
+"  users."
+msgstr ""
+
+#: i2p2www/blog/2015/01/20/31C3-trip-report.rst:223
+msgid ""
+"* We discussed the state of Meeh's and Sindu's reseed servers. They made "
+"several\n"
+"  improvements while at the congress and are investigating migration to\n"
+"  `Matt Drollette's Go implementation`_. The security and reliability of "
+"our\n"
+"  reseed servers is vital to new users and network operation. `User "
+"'backup'`_\n"
+"  is doing a great job monitoring and managing the pool of reseed servers."
+msgstr ""
+
+#: i2p2www/blog/2015/01/20/31C3-trip-report.rst:231
+msgid ""
+"* We agreed to purchase a second root server for development, testing, "
+"and\n"
+"  services. Echelon will be adminstering it. Contact him if you would "
+"like a VM."
+msgstr ""
+
+#: i2p2www/blog/2015/01/20/31C3-trip-report.rst:236
+msgid ""
+"* We reiterated that we have funds available to purchase test hardware,\n"
+"  especially for Windows and Mac. Talk to echelon for details."
+msgstr ""
+
+#: i2p2www/blog/2015/01/20/31C3-trip-report.rst:241
+msgid ""
+"* We met with Welterde about the state of his services including his\n"
+"  `open tracker`_. These services are not being adequately maintained and"
+" will\n"
+"  soon become inaccessible due to crypto changes if they are not "
+"upgraded. He\n"
+"  committed to upgrading them soon."
+msgstr ""
+
+#: i2p2www/blog/2015/01/20/31C3-trip-report.rst:248
+msgid ""
+"* We met lots of people interested in our `Android app`_. We passed "
+"several\n"
+"  ideas and bug reports back to str4d. We plan to make a big push to give"
+" the\n"
+"  app some development love early in the year."
+msgstr ""
+
+#: i2p2www/blog/2015/01/20/31C3-trip-report.rst:254
+msgid ""
+"* Regrettably, we didn't get to see too many talks at the Congress, as we"
+" were\n"
+"  so busy meeting with people. We plan to catch up and `watch them "
+"online`_. As\n"
+"  usual, Tor's \"State of the Onion\" talk was excellent, and Jacob's "
+"talk was\n"
+"  great. We hear that the cryptography talks were good as well."
+msgstr ""
+
+#: i2p2www/blog/2015/01/20/31C3-trip-report.rst:261
+msgid "`Toronto Crypto`"
+msgstr ""
+
+#: i2p2www/blog/2015/01/20/31C3-trip-report.rst:262
+msgid "`tweeting @i2p`"
+msgstr ""
+
+#: i2p2www/blog/2015/01/20/31C3-trip-report.rst:263
+msgid "`on the dev forum thread`"
+msgstr ""
+
+#: i2p2www/blog/2015/01/20/31C3-trip-report.rst:266
+msgid "`Privacy Solutions web site`"
+msgstr ""
+
+#: i2p2www/blog/2015/01/20/31C3-trip-report.rst:270
+msgid "`Matt Drollette's Go implementation`"
+msgstr ""
+
+#: i2p2www/blog/2015/01/20/31C3-trip-report.rst:271
+msgid "`User 'backup'`"
+msgstr ""
+
+#: i2p2www/blog/2015/01/20/31C3-trip-report.rst:273
+msgid "`open tracker`"
+msgstr ""
+
+#: i2p2www/blog/2015/01/20/31C3-trip-report.rst:275
+msgid "`Android app`"
+msgstr ""
+
+#: i2p2www/blog/2015/01/20/31C3-trip-report.rst:277
+msgid "`watch them online`"
+msgstr ""
+
+#: i2p2www/blog/2015/02/22/0.9.18-Release.rst:1
+msgid ""
+"==============\n"
+"0.9.18 Release\n"
+"=============="
+msgstr ""
+
+#: i2p2www/blog/2015/02/22/0.9.18-Release.rst:10
+msgid "0.9.18 with performance improvements and bug fixes"
+msgstr ""
+
+#: i2p2www/blog/2015/02/22/0.9.18-Release.rst:12
+msgid ""
+"0.9.18 contains several bug fixes and performance improvements.\n"
+"We have shortened the startup time, and reduced latency throughout our "
+"network protocols.\n"
+"We've increased the default connection limits for the fastest routers,\n"
+"and reduced the thread usage in i2ptunnel.\n"
+"UPnP fixes should improve handling of external device changes.\n"
+"CPU usage in high-bandwidth routers may be reduced thanks to some NTCP "
+"fixes."
+msgstr ""
+
+#: i2p2www/blog/2015/02/22/0.9.18-Release.rst:32
+msgid "Fix parsing of ECDSA address helper in HTTP client proxy"
+msgstr ""
+
+#: i2p2www/blog/2015/02/22/0.9.18-Release.rst:33
+msgid "Fix news last-modified processing which prevented notification of update"
+msgstr ""
+
+#: i2p2www/blog/2015/02/22/0.9.18-Release.rst:34
+msgid "Improve handling of UPnP device changes"
+msgstr ""
+
+#: i2p2www/blog/2015/02/22/0.9.18-Release.rst:35
+msgid "Don't hang at startup forever waiting for entropy"
+msgstr ""
+
+#: i2p2www/blog/2015/02/22/0.9.18-Release.rst:36
+msgid "Possible fixes for high CPU usage in NTCP"
+msgstr ""
+
+#: i2p2www/blog/2015/02/22/0.9.18-Release.rst:40
+msgid "Publish router info faster when address costs change"
+msgstr ""
+
+#: i2p2www/blog/2015/02/22/0.9.18-Release.rst:41
+msgid "Start i2ptunnel 90s sooner"
+msgstr ""
+
+#: i2p2www/blog/2015/02/22/0.9.18-Release.rst:42
+msgid "Accept tunnels 10m sooner"
+msgstr ""
+
+#: i2p2www/blog/2015/02/22/0.9.18-Release.rst:43
+msgid "Increase exploratory tunnel quantity during initial exploration"
+msgstr ""
+
+#: i2p2www/blog/2015/02/22/0.9.18-Release.rst:44
+msgid "Latency reductions in several places"
+msgstr ""
+
+#: i2p2www/blog/2015/02/22/0.9.18-Release.rst:45
+msgid ""
+"Add startup browser configuration with advanced config "
+"routerconsole.browser"
+msgstr ""
+
+#: i2p2www/blog/2015/02/22/0.9.18-Release.rst:46
+msgid "Persistent leaseset keys to eliminate correlation with restart"
+msgstr ""
+
+#: i2p2www/blog/2015/02/22/0.9.18-Release.rst:47
+msgid "Faster unchoking of new peers in i2psnark"
+msgstr ""
+
+#: i2p2www/blog/2015/02/22/0.9.18-Release.rst:48
+msgid "More aggressive throttling of lookups at floodfills"
+msgstr ""
+
+#: i2p2www/blog/2015/02/22/0.9.18-Release.rst:49
+msgid "Tunnel build request record refactoring"
+msgstr ""
+
+#: i2p2www/blog/2015/02/22/0.9.18-Release.rst:50
+msgid "Reduce thread usage in i2ptunnel"
+msgstr ""
+
+#: i2p2www/blog/2015/02/22/0.9.18-Release.rst:51
+msgid "Add i2ptunnel server option for multihomed sites"
+msgstr ""
+
+#: i2p2www/blog/2015/02/22/0.9.18-Release.rst:52
+msgid "Disallow some common I2P application ports as router ports"
+msgstr ""
+
+#: i2p2www/blog/2015/02/22/0.9.18-Release.rst:53
+msgid "Increase connection limits for fast routers"
+msgstr ""
+
+#: i2p2www/blog/2015/02/22/0.9.18-Release.rst:54
+msgid "Add Save-As button for SusiMail messages"
+msgstr ""
+
+#: i2p2www/blog/2015/02/22/0.9.18-Release.rst:55
+msgid "Use 'hidden service' terminology in the console"
+msgstr ""
+
+#: i2p2www/blog/2015/02/22/0.9.18-Release.rst:56
+msgid "Encrypted netdb lookups for 32-bit x86"
+msgstr ""
+
+#: i2p2www/blog/2015/04/12/0.9.19-Release.rst:1
+msgid ""
+"==============\n"
+"0.9.19 Release\n"
+"=============="
+msgstr ""
+
+#: i2p2www/blog/2015/04/12/0.9.19-Release.rst:10
+msgid "0.9.19 with performance improvements and bug fixes"
+msgstr ""
+
+#: i2p2www/blog/2015/04/12/0.9.19-Release.rst:12
+msgid ""
+"0.9.19 has several fixes and improvements for floodfill performance.\n"
+"Many of you saw high CPU usage after 0.9.18 was released.\n"
+"This was caused by a combination of increased encryption usage, the big "
+"influx of Vuze users into the network,\n"
+"reduced floodfills due to tighter performance requirements, and some "
+"longstanding bugs.\n"
+"Things should be a lot better after most of the network has updated.\n"
+"As always, the best way to reduce CPU usage is to lower your bandwidth "
+"limits."
+msgstr ""
+
+#: i2p2www/blog/2015/04/12/0.9.19-Release.rst:20
+msgid ""
+"We've also added new ways to reseed manually, and to generate a reseed "
+"file you can easily share with others who need it.\n"
+"See the reseed configuration page in the router console for more "
+"information."
+msgstr ""
+
+#: i2p2www/blog/2015/04/12/0.9.19-Release.rst:34
+#: i2p2www/blog/2015/06/02/0.9.20-Release.rst:48
+msgid "Floodfill performance improvements"
+msgstr ""
+
+#: i2p2www/blog/2015/04/12/0.9.19-Release.rst:35
+msgid "Easier ways to reseed manually from a file or URL"
+msgstr ""
+
+#: i2p2www/blog/2015/04/12/0.9.19-Release.rst:36
+msgid "New way to export reseed data for others"
+msgstr ""
+
+#: i2p2www/blog/2015/04/12/0.9.19-Release.rst:37
+msgid "Support for installing plugin from file"
+msgstr ""
+
+#: i2p2www/blog/2015/04/12/0.9.19-Release.rst:42
+#: i2p2www/blog/2015/06/02/0.9.20-Release.rst:59
+msgid "Fixes for high CPU usage in floodfills"
+msgstr ""
+
+#: i2p2www/blog/2015/04/12/0.9.19-Release.rst:43
+msgid "i2ptunnel locking fixes"
+msgstr ""
+
+#: i2p2www/blog/2015/04/12/0.9.19-Release.rst:44
+msgid "Fixes for read timeout handling in streaming"
+msgstr ""
+
+#: i2p2www/blog/2015/04/12/0.9.19-Release.rst:45
+msgid "Fix changing i2psnark data directory on Windows"
+msgstr ""
+
+#: i2p2www/blog/2015/04/12/0.9.19-Release.rst:46
+msgid "Fix multiple SSL outproxies in HTTP client"
+msgstr ""
+
+#: i2p2www/blog/2015/04/12/0.9.19-Release.rst:51
+msgid "Update to UPnP library version 3.0"
+msgstr ""
+
+#: i2p2www/blog/2015/04/12/0.9.19-Release.rst:52
+msgid "Improve tracking of floodfill lookup success"
+msgstr ""
+
+#: i2p2www/blog/2015/04/12/0.9.19-Release.rst:53
+msgid "Direct router info lookups if connected to floodfill"
+msgstr ""
+
+#: i2p2www/blog/2015/04/12/0.9.19-Release.rst:54
+msgid "Auto-adjustment of i2psnark tunnel quantity"
+msgstr ""
+
+#: i2p2www/blog/2015/04/12/0.9.19-Release.rst:55
+msgid "Increase exploratory tunnel quantity when floodfill"
+msgstr ""
+
+#: i2p2www/blog/2015/04/12/0.9.19-Release.rst:56
+msgid "Increase min and default bandwidth for i2psnark"
+msgstr ""
+
+#: i2p2www/blog/2015/04/12/0.9.19-Release.rst:57
+msgid "Improved strategies for dropping jobs on high job lag to prevent overload"
+msgstr ""
+
+#: i2p2www/blog/2015/04/12/0.9.19-Release.rst:58
+msgid "Drop tunnel build requests on high job lag"
+msgstr ""
+
+#: i2p2www/blog/2015/04/12/0.9.19-Release.rst:59
+msgid "Increase allowed clock skew in I2CP"
+msgstr ""
+
+#: i2p2www/blog/2015/04/12/0.9.19-Release.rst:60
+msgid "New HTTP error page when the server resets the connection"
+msgstr ""
+
+#: i2p2www/blog/2015/04/12/0.9.19-Release.rst:61
+msgid "Require ECDSA support for floodfill"
+msgstr ""
+
+#: i2p2www/blog/2015/04/12/0.9.19-Release.rst:62
+msgid "Republish router info faster when capabilities change"
+msgstr ""
+
+#: i2p2www/blog/2015/04/12/0.9.19-Release.rst:63
+msgid "Better feedback in console for reseed errors"
+msgstr ""
+
+#: i2p2www/blog/2015/06/02/0.9.20-Release.rst:1
+msgid ""
+"==============\n"
+"0.9.20 Release\n"
+"=============="
+msgstr ""
+
+#: i2p2www/blog/2015/06/02/0.9.20-Release.rst:10
+msgid "0.9.20 with performance improvements and bug fixes"
+msgstr ""
+
+#: i2p2www/blog/2015/06/02/0.9.20-Release.rst:12
+msgid ""
+"0.9.20 contains many important bug fixes, and several changes to increase"
+" floodfill capacity in the network."
+msgstr ""
+
+#: i2p2www/blog/2015/06/02/0.9.20-Release.rst:16
+msgid ""
+"Routers configured for 32-64 KB of shared bandwidth may now become "
+"floodfill,\n"
+"and routers configured for 512 KB or more of shared bandwidth will have "
+"higher connection limits.\n"
+"These changes may cause your router to use more resources.\n"
+"If the router becomes too busy, the best way to reduce usage is to lower "
+"the bandwidth settings in your console.\n"
+"If that doesn't help, you may now disable automatic floodfill on the "
+"advanced configuration page in the console."
+msgstr ""
+
+#: i2p2www/blog/2015/06/02/0.9.20-Release.rst:24
+msgid ""
+"We're hopeful that these changes will increase network capacity and "
+"performance,\n"
+"and reduce the congestion that's been affecting the network the last "
+"three months."
+msgstr ""
+
+#: i2p2www/blog/2015/06/02/0.9.20-Release.rst:34
+msgid ""
+"Finally, we're excited to announce our first-ever I2P meetup, in Toronto "
+"August 15-16.\n"
+"There will be lots of presentations and tutorials. All are welcome.\n"
+"For more information, see the `announcement`_."
+msgstr ""
+
+#: i2p2www/blog/2015/06/02/0.9.20-Release.rst:49
+msgid "Add support for address book export"
+msgstr ""
+
+#: i2p2www/blog/2015/06/02/0.9.20-Release.rst:50
+msgid "Add support for SSL in HTTP server tunnel"
+msgstr ""
+
+#: i2p2www/blog/2015/06/02/0.9.20-Release.rst:51
+msgid "Allow class 'M' (64-128 KBps share bandwidth) to become floodfill"
+msgstr ""
+
+#: i2p2www/blog/2015/06/02/0.9.20-Release.rst:52
+msgid ""
+"Raise connection limits for new classes 'P' (512-2000 KBps share "
+"bandwidth) and 'X' (over 2000 KBps)"
+msgstr ""
+
+#: i2p2www/blog/2015/06/02/0.9.20-Release.rst:53
+msgid "Add support for signed development builds"
+msgstr ""
+
+#: i2p2www/blog/2015/06/02/0.9.20-Release.rst:60
+msgid "Clock skew fixes"
+msgstr ""
+
+#: i2p2www/blog/2015/06/02/0.9.20-Release.rst:61
+msgid "Fixes and configuration for when IPv4 is firewalled but IPv6 still works"
+msgstr ""
+
+#: i2p2www/blog/2015/06/02/0.9.20-Release.rst:62
+msgid "Locking fixes for i2ptunnel clients to prevent hangs at startup"
+msgstr ""
+
+#: i2p2www/blog/2015/06/02/0.9.20-Release.rst:63
+msgid "Verify hostnames when reseeding"
+msgstr ""
+
+#: i2p2www/blog/2015/06/02/0.9.20-Release.rst:64
+msgid "Fix deletion of config files for deleted torrents in i2psnark"
+msgstr ""
+
+#: i2p2www/blog/2015/06/02/0.9.20-Release.rst:65
+msgid "Fix hangs fetching proxy.i2p local resources via Privoxy"
+msgstr ""
+
+#: i2p2www/blog/2015/06/02/0.9.20-Release.rst:66
+msgid "Fixes for duplicate shared clients"
+msgstr ""
+
+#: i2p2www/blog/2015/06/02/0.9.20-Release.rst:67
+msgid "Fix for occasional page truncation in HTTP client"
+msgstr ""
+
+#: i2p2www/blog/2015/06/02/0.9.20-Release.rst:68
+msgid "Fixes for handling corrupted SSU packets"
+msgstr ""
+
+#: i2p2www/blog/2015/06/02/0.9.20-Release.rst:69
+msgid "Fix closing of SAM sessions when I2P session closes"
+msgstr ""
+
+#: i2p2www/blog/2015/06/02/0.9.20-Release.rst:70
+msgid "Fix bugs in handling streaming resets"
+msgstr ""
+
+#: i2p2www/blog/2015/06/02/0.9.20-Release.rst:77
+msgid "Reduce NTCP threads"
+msgstr ""
+
+#: i2p2www/blog/2015/06/02/0.9.20-Release.rst:78
+msgid "Eliminate SimpleScheduler threads"
+msgstr ""
+
+#: i2p2www/blog/2015/06/02/0.9.20-Release.rst:79
+msgid "Add continent-based NTP servers as fallbacks for country-based ones"
+msgstr ""
+
+#: i2p2www/blog/2015/06/02/0.9.20-Release.rst:80
+msgid "Remove all default non-SSL reseed hosts"
+msgstr ""
+
+#: i2p2www/blog/2015/06/02/0.9.20-Release.rst:81
+msgid "Disable fallback to non-su3 reseeding"
+msgstr ""
+
+#: i2p2www/blog/2015/06/02/0.9.20-Release.rst:82
+msgid "Several fixes in streaming for better \"loopback\" performance"
+msgstr ""
+
+#: i2p2www/blog/2015/06/02/0.9.20-Release.rst:83
+msgid "Reduce latency in i2ptunnel"
+msgstr ""
+
+#: i2p2www/blog/2015/06/02/0.9.20-Release.rst:84
+msgid "Add a larger Bloom filter for very high bandwidth and memory"
+msgstr ""
+
+#: i2p2www/blog/2015/06/02/0.9.20-Release.rst:85
+msgid ""
+"Add Bloom filter warning when configured for high bandwidth but not "
+"enough memory"
+msgstr ""
+
+#: i2p2www/blog/2015/06/02/0.9.20-Release.rst:86
+msgid "Reduce max netdb search depth to reduce floodfill load"
+msgstr ""
+
+#: i2p2www/blog/2015/06/02/0.9.20-Release.rst:87
+msgid "Improved header processing and error handling in i2ptunnel HTTP server"
+msgstr ""
+
+#: i2p2www/blog/2015/06/02/0.9.20-Release.rst:88
+msgid ""
+"Better error handling and user feedback when HTTP client tunnel is "
+"disabled"
+msgstr ""
+
+#: i2p2www/blog/2015/06/02/0.9.20-Release.rst:89
+msgid "More changes to improve floodfill capacity"
+msgstr ""
+
+#: i2p2www/blog/2015/06/02/0.9.20-Release.rst:90
+msgid "New configuration for forcing IPv4 (only) to firewalled on /confignet"
+msgstr ""
+
+#: i2p2www/blog/2015/06/02/0.9.20-Release.rst:91
+msgid "New configuration for floodfill on /configadvanced"
+msgstr ""
+
+#: i2p2www/blog/2015/06/02/0.9.20-Release.rst:92
+msgid "Show separate IPv4 and IPv6 status in summary bar when appropriate"
+msgstr ""
+
+#: i2p2www/blog/2015/06/02/0.9.20-Release.rst:93
+msgid "Better handling of corrupt SSU packets"
+msgstr ""
+
+#: i2p2www/blog/2015/06/02/Toronto-Meetup.rst:1
+msgid ""
+"==============\n"
+"Toronto Meetup\n"
+"=============="
+msgstr ""
+
+#: i2p2www/blog/2015/06/02/Toronto-Meetup.rst:10
+msgid "I2P Meetup in Toronto on August 15-16."
+msgstr ""
+
+#: i2p2www/blog/2015/06/02/Toronto-Meetup.rst:12
+msgid ""
+"The I2P team is proud to announce that we are going to host a meetup in "
+"Toronto on August 15-16.\n"
+"A number of members of our community will be attending and are going to "
+"host talks, workshops and discussions about and relating to I2P. This "
+"event is not just for I2P people though, it's meant for everyone."
+msgstr ""
+
+#: i2p2www/blog/2015/06/02/Toronto-Meetup.rst:17
+msgid ""
+"If you're curious about I2P, interested in privacy/cryptography/anonymity"
+" or just want to come by and talk to us, please do. This is an event for "
+"everyone. If you're not familiar with any of these topics, come by anyway"
+" and we'll show you how I2P works and what you can do with it.\n"
+"\n"
+"The event is entirely free, you don't need to sign up or register."
+msgstr ""
+
+#: i2p2www/blog/2015/06/02/Toronto-Meetup.rst:23
+msgid ""
+"The meetup couldn't have been arranged without our friends at `Toronto "
+"Crypto <https://torontocrypto.org/>`_ which have been helping us organize"
+" the event, and our friends at `Hacklab <https://hacklab.to/>`_ which are"
+" providing us with a very nice space."
+msgstr ""
+
+#: i2p2www/blog/2015/06/02/Toronto-Meetup.rst:27
+#: i2p2www/blog/2015/07/16/I2PCon.rst:126
+msgid "If you have any questions, feel free to contact us on `@geti2p`_."
+msgstr ""
+
+#: i2p2www/blog/2015/06/02/Toronto-Meetup.rst:34
+#: i2p2www/blog/2015/07/16/I2PCon.rst:38
+msgid ""
+"Details\n"
+"======="
+msgstr ""
+
+#: i2p2www/blog/2015/06/02/Toronto-Meetup.rst:39
+#: i2p2www/blog/2015/07/16/I2PCon.rst:57
+msgid ""
+"Location\n"
+"--------"
+msgstr ""
+
+#: i2p2www/blog/2015/06/02/Toronto-Meetup.rst:44
+msgid "`Hacklab <https://hacklab.to/>`_ at 1266 Queen Street West, Toronto."
+msgstr ""
+
+#: i2p2www/blog/2015/06/02/Toronto-Meetup.rst:48
+msgid ""
+"Day 1, August 15 - 3PM\n"
+"----------------------"
+msgstr ""
+
+#: i2p2www/blog/2015/06/02/Toronto-Meetup.rst:53
+msgid ""
+"The focus will be on an introduction to topics surrounding I2P, privacy "
+"and anonymity online. People of all backgrounds and knowledge levels are "
+"welcome to attend."
+msgstr ""
+
+#: i2p2www/blog/2015/06/02/Toronto-Meetup.rst:57
+msgid "I2P Presentation"
+msgstr ""
+
+#: i2p2www/blog/2015/06/02/Toronto-Meetup.rst:58
+msgid "Crypto party introduction"
+msgstr ""
+
+#: i2p2www/blog/2015/06/02/Toronto-Meetup.rst:59
+msgid "Crypto party"
+msgstr ""
+
+#: i2p2www/blog/2015/06/02/Toronto-Meetup.rst:61
+msgid ""
+"The crypto party will contain a number of stations where "
+"privacy/anonymity software will be demoed. The goal is to provide people "
+"with the tools they need to communicate securely."
+msgstr ""
+
+#: i2p2www/blog/2015/06/02/Toronto-Meetup.rst:65
+msgid "`Vuze/I2P`_ - Downloading torrents anonymously"
+msgstr ""
+
+#: i2p2www/blog/2015/06/02/Toronto-Meetup.rst:66
+msgid "`Veracrypt`_ - Encrypt your data"
+msgstr ""
+
+#: i2p2www/blog/2015/06/02/Toronto-Meetup.rst:67
+msgid "`I2PBote`_ - Anonymous decentralized email"
+msgstr ""
+
+#: i2p2www/blog/2015/06/02/Toronto-Meetup.rst:68
+msgid "Your station idea here"
+msgstr ""
+
+#: i2p2www/blog/2015/06/02/Toronto-Meetup.rst:70
+msgid ""
+"We're currently looking for help staffing the stations. If you want to "
+"help out, you can! Bring a monitor/laptop and run a station. The station "
+"could be any of the ones listed above, or any other privacy/anonymity "
+"related one you would like to run. Please contact us at `@geti2p`_ if "
+"you're interested."
+msgstr ""
+
+#: i2p2www/blog/2015/06/02/Toronto-Meetup.rst:79
+msgid ""
+"Day 2, August 16 - 1PM\n"
+"----------------------"
+msgstr ""
+
+#: i2p2www/blog/2015/06/02/Toronto-Meetup.rst:84
+msgid ""
+"The focus will be on in-depth topics surrounding I2P, the roadmap and "
+"development. Anyone is welcome to attend, but the content will be "
+"somewhat technical."
+msgstr ""
+
+#: i2p2www/blog/2015/06/02/Toronto-Meetup.rst:88
+msgid "I2P Technical presentation"
+msgstr ""
+
+#: i2p2www/blog/2015/06/02/Toronto-Meetup.rst:89
+msgid "Technical discussion"
+msgstr ""
+
+#: i2p2www/blog/2015/06/02/Toronto-Meetup.rst:90
+msgid "I2P App Dev Into"
+msgstr ""
+
+#: i2p2www/blog/2015/06/02/Toronto-Meetup.rst:91
+msgid "I2PD presentation"
+msgstr ""
+
+#: i2p2www/blog/2015/06/02/Toronto-Meetup.rst:92
+msgid "I2P on Android"
+msgstr ""
+
+#: i2p2www/blog/2015/07/16/I2PCon.rst:1
+msgid ""
+"======\n"
+"I2PCon\n"
+"======"
+msgstr ""
+
+#: i2p2www/blog/2015/07/16/I2PCon.rst:10
+msgid "I2PCon will be in Toronto on August 15-16."
+msgstr ""
+
+#: i2p2www/blog/2015/07/16/I2PCon.rst:13
+msgid ""
+"I2PCon is the first event of its kind. It has two short term goals. Where"
+" the\n"
+"first one is to provide the general public with an event where knowledge "
+"about\n"
+"privacy and privacy concerns can be obtained. The second goal is to "
+"further the\n"
+"I2P project and its community. This will take the shape of technical "
+"discussions\n"
+"about cryptography, anonymity and I2P centric topics."
+msgstr ""
+
+#: i2p2www/blog/2015/07/16/I2PCon.rst:21
+msgid ""
+"There is a larger and more long-term goal of this event, and it is to "
+"build a\n"
+"commnutiy of privacy-conscious individuals. By connecting people who "
+"recognize\n"
+"the importance of privacy, we would like to provide a forum where this "
+"community\n"
+"can grow."
+msgstr ""
+
+#: i2p2www/blog/2015/07/16/I2PCon.rst:28
+msgid ""
+"The idea for this event was first spawned by our wonderful friends at\n"
+"`Toronto Crypto`_. The venue and everything relating to it is provided by"
+"\n"
+"`Hacklab`_. Without either of them this event would not have been "
+"possible, so\n"
+"thank you both."
+msgstr ""
+
+#: i2p2www/blog/2015/07/16/I2PCon.rst:43
+msgid ""
+"Cost\n"
+"----"
+msgstr ""
+
+#: i2p2www/blog/2015/07/16/I2PCon.rst:48
+msgid ""
+"I2PCon is entirely free to attend! We ask you to register `here`_, to "
+"give us\n"
+"an estimate of how many people will be attending. No identifying "
+"information has\n"
+"to be given in order to register, but if you have any concerns, please "
+"let us\n"
+"know."
+msgstr ""
+
+#: i2p2www/blog/2015/07/16/I2PCon.rst:55
+#: i2p2www/blog/2016/01/27/0.9.24-Release.rst:45
+msgid "`here`"
+msgstr ""
+
+#: i2p2www/blog/2015/07/16/I2PCon.rst:62
+msgid "`Hacklab`_ at 1266 Queen Street West, Unit #6, Toronto."
+msgstr ""
+
+#: i2p2www/blog/2015/07/16/I2PCon.rst:66
+msgid ""
+"Venue\n"
+"-----"
+msgstr ""
+
+#: i2p2www/blog/2015/07/16/I2PCon.rst:71
+msgid "Power and WiFi access will be provided by `Hacklab`_."
+msgstr ""
+
+#: i2p2www/blog/2015/07/16/I2PCon.rst:76
+msgid ""
+"Schedule\n"
+"========"
+msgstr ""
+
+#: i2p2www/blog/2015/07/16/I2PCon.rst:81
+msgid ""
+"Day 1, August 15\n"
+"----------------"
+msgstr ""
+
+#: i2p2www/blog/2015/07/16/I2PCon.rst:98
+msgid ""
+"Day 2, August 16\n"
+"----------------"
+msgstr ""
+
+#: i2p2www/blog/2015/07/16/I2PCon.rst:121
+msgid ""
+"I'm confused and would like some answers\n"
+"========================================"
+msgstr ""
+
+#: i2p2www/blog/2015/07/31/0.9.21-Release.rst:1
+msgid ""
+"==============\n"
+"0.9.21 Release\n"
+"=============="
+msgstr ""
+
+#: i2p2www/blog/2015/07/31/0.9.21-Release.rst:10
+msgid "0.9.21 with performance improvements and bug fixes"
+msgstr ""
+
+#: i2p2www/blog/2015/07/31/0.9.21-Release.rst:12
+msgid ""
+"0.9.21 contains several changes to add capacity to the network, increase "
+"the efficiency of the floodfills,\n"
+"and use bandwidth more effectively.\n"
+"We have migrated the shared clients tunnels to ECDSA signatures and added"
+" a DSA fallback\n"
+"using the new \"multisession\" capability for those sites that don't "
+"support ECDSA."
+msgstr ""
+"0.9.21 buraxılışı şəbəkə həcmini artıran fərqli dəyişikliklər, \n"
+"floodfill\n"
+"səmərəliliyini artıran və ötürmə qabiliyyətindən daha məhsuldar istifadə "
+"edən xüsusiyyətlər ilə buraxıldı. \n"
+"Paylaşılan müştəri tunellərini ECDSA imzaları ilə birləşdirdik və ECDSA "
+"dəstəkləməyən saytlar üçün yeni \"çoxseanslı\" qabiliyyətini "
+"qiymətləndirən DSA əlavə etdik."
+
+#: i2p2www/blog/2015/07/31/0.9.21-Release.rst:19
+msgid ""
+"The speakers and the schedule of the I2PCon in Toronto 2015 have been "
+"announced.\n"
+"Have a look on the `I2PCon page`_ for details.\n"
+"Reserve your seat on `Eventbrite`_."
+msgstr ""
+
+#: i2p2www/blog/2015/07/31/0.9.21-Release.rst:40
+msgid "Add multisession support for dual-signature crypto on the same tunnels"
+msgstr ""
+
+#: i2p2www/blog/2015/07/31/0.9.21-Release.rst:41
+msgid "Use multisession for shared clients"
+msgstr ""
+
+#: i2p2www/blog/2015/07/31/0.9.21-Release.rst:42
+msgid "Increase default outbound bandwidth limit to 60 KBps"
+msgstr ""
+
+#: i2p2www/blog/2015/07/31/0.9.21-Release.rst:43
+msgid "Increase default maximum participating tunnels"
+msgstr ""
+
+#: i2p2www/blog/2015/07/31/0.9.21-Release.rst:44
+msgid ""
+"Floodfills will send database store acks directly if connected, for "
+"efficiency"
+msgstr ""
+
+#: i2p2www/blog/2015/07/31/0.9.21-Release.rst:45
+msgid "Set TCP keepalive on I2CP and SAM sockets"
+msgstr ""
+
+#: i2p2www/blog/2015/07/31/0.9.21-Release.rst:46
+msgid "More efficient decompression in HTTP proxy, use less threads"
+msgstr ""
+
+#: i2p2www/blog/2015/07/31/0.9.21-Release.rst:47
+msgid "Add support for fast extensions in i2psnark"
+msgstr ""
+
+#: i2p2www/blog/2015/07/31/0.9.21-Release.rst:48
+msgid "i2psnark only autostarts torrents that were running previously"
+msgstr ""
+
+#: i2p2www/blog/2015/07/31/0.9.21-Release.rst:49
+msgid "Add support for translated console news"
+msgstr ""
+
+#: i2p2www/blog/2015/07/31/0.9.21-Release.rst:54
+msgid "SSU fixes to compete better with NTCP for bandwidth when limited"
+msgstr ""
+
+#: i2p2www/blog/2015/07/31/0.9.21-Release.rst:55
+msgid "Fixes to prevent SSU stalls"
+msgstr ""
+
+#: i2p2www/blog/2015/07/31/0.9.21-Release.rst:56
+msgid ""
+"Wait for outbound tunnels before sending first leaseset to client, to "
+"prevent dropping first message"
+msgstr ""
+
+#: i2p2www/blog/2015/07/31/0.9.21-Release.rst:57
+msgid "Clean up resources correctly when SAM stops"
+msgstr ""
+
+#: i2p2www/blog/2015/07/31/0.9.21-Release.rst:58
+msgid "Better error handling and notification when HTTP proxy is not running"
+msgstr ""
+
+#: i2p2www/blog/2015/07/31/0.9.21-Release.rst:59
+msgid "More i2ptunnel fixes at startup and shutdown of tunnels"
+msgstr ""
+
+#: i2p2www/blog/2015/07/31/0.9.21-Release.rst:60
+msgid "Fix total_size in i2psnark metadata message"
+msgstr ""
+
+#: i2p2www/blog/2015/07/31/0.9.21-Release.rst:61
+msgid "Restore dates in console news headers"
+msgstr ""
+
+#: i2p2www/blog/2015/07/31/0.9.21-Release.rst:62
+msgid "Several I2CP fixes"
+msgstr ""
+
+#: i2p2www/blog/2015/07/31/0.9.21-Release.rst:67
+msgid "Use same session for naming lookups in I2PSocketEepGet"
+msgstr ""
+
+#: i2p2www/blog/2015/07/31/0.9.21-Release.rst:68
+msgid "Increase max bandwidth to 16 MBps, add larger Bloom filter"
+msgstr ""
+
+#: i2p2www/blog/2015/07/31/0.9.21-Release.rst:69
+msgid ""
+"New floodfills will send their info to nearby floodfills to speed "
+"integration"
+msgstr ""
+
+#: i2p2www/blog/2015/08/20/I2PCon_Mission_Accomplished.rst:1
+msgid ""
+"============================\n"
+"I2PCon: Mission Accomplished\n"
+"============================"
+msgstr ""
+
+#: i2p2www/blog/2015/08/20/I2PCon_Mission_Accomplished.rst:10
+msgid "I2PCon: Mission Accomplished"
+msgstr ""
+
+#: i2p2www/blog/2015/08/20/I2PCon_Mission_Accomplished.rst:13
+msgid ""
+"I2PCon has been a giant success. For us, the I2P contributors, it "
+"represents a\n"
+"leap forward in terms of what we're capable of pulling off as a "
+"community, how we\n"
+"communicate the usecases of I2P and reach out to privacy conscious "
+"individuals.\n"
+"\n"
+"By arranging this event, we've also grown our community. People who've "
+"previously\n"
+"only lurked on our irc channels, or run our software or possibly hadn't "
+"even heard\n"
+"of I2P are now a part of our comminuty.\n"
+"\n"
+"This event has been our first active step towards building a large and "
+"inclusive\n"
+"community, and as such it's been great success."
+msgstr ""
+
+#: i2p2www/blog/2015/08/20/I2PCon_Mission_Accomplished.rst:27
+msgid ""
+"Minutiae\n"
+"========\n"
+"On day 2 we had two short discussion sessions. A more general discussion "
+"and a roadmapping discussion.\n"
+"\n"
+"The minutiae can be found here: `I2P Roadmap session minutiae`_ and `I2P "
+"Discussion session minutiae`_."
+msgstr ""
+
+#: i2p2www/blog/2015/08/20/I2PCon_Mission_Accomplished.rst:36
+msgid ""
+"Photos\n"
+"======"
+msgstr ""
+
+#: i2p2www/blog/2015/08/20/I2PCon_Mission_Accomplished.rst:44
+msgid "The learn how to setup I2P crypto party station"
+msgstr ""
+
+#: i2p2www/blog/2015/08/20/I2PCon_Mission_Accomplished.rst:49
+msgid "The learn how use I2P and Vuze party station"
+msgstr ""
+
+#: i2p2www/blog/2015/08/20/I2PCon_Mission_Accomplished.rst:54
+msgid "David Dagons wonderful talk"
+msgstr ""
+
+#: i2p2www/blog/2015/08/20/I2PCon_Mission_Accomplished.rst:56
+msgid ""
+"Thanks\n"
+"======"
+msgstr ""
+
+#: i2p2www/blog/2015/08/20/I2PCon_Mission_Accomplished.rst:61
+msgid ""
+"We've had some wonderful speakers, from both inside- and outside of our "
+"community.\n"
+"\n"
+"`David Dagon`_ talked to us about the way forward and how I2P could "
+"handle potential abuse.\n"
+"\n"
+"`Lance James`_ - the creator of our predecessor iip - said Hi and gave us"
+" his thoughts about how far I2P has come.\n"
+"\n"
+"`Nick Johnston`_ gave us a wonderful talk about why privacy matters and "
+"why you should care."
+msgstr ""
+
+#: i2p2www/blog/2015/08/20/I2PCon_Mission_Accomplished.rst:71
+msgid ""
+"I would also like to thank the speakers from our community. `psi`_, "
+"`@str4d`_ and `zzz`_  who all had\n"
+"wonderful talks. Improving our ability to inform people about I2P is "
+"something that\n"
+"is going to be important for us going forward."
+msgstr ""
+
+#: i2p2www/blog/2015/08/20/I2PCon_Mission_Accomplished.rst:77
+msgid ""
+"I would like to thank `Sadie`_ and Siew for helping us out with marketing"
+" and graphics.\n"
+"Without you I2PCon would've been a very different event."
+msgstr ""
+
+#: i2p2www/blog/2015/08/20/I2PCon_Mission_Accomplished.rst:82
+msgid ""
+"I would like to thank `@chlorelium`_ and `Hacklab`_ for being the most "
+"wonderful of hosts."
+msgstr ""
+
+#: i2p2www/blog/2015/08/20/I2PCon_Mission_Accomplished.rst:86
+msgid ""
+"I would like to thank `@darknetj`_, P and `@hizeena`_ of `Toronto "
+"Crypto`_ for their help during the event."
+msgstr ""
+
+#: i2p2www/blog/2015/08/20/I2PCon_Mission_Accomplished.rst:90
+msgid ""
+"I would like to thank `@z3r0fox`_ for doing a wonderful job with the AV "
+"and doing all of the post-production\n"
+"work for the videos of all the talks."
+msgstr ""
+
+#: i2p2www/blog/2015/08/20/I2PCon_Mission_Accomplished.rst:95
+msgid ""
+"I would like to thank `@killyourtv_i2p`_ for hosting a very popular "
+"crypto party station."
+msgstr ""
+
+#: i2p2www/blog/2015/08/20/I2PCon_Mission_Accomplished.rst:99
+msgid ""
+"Thanks to our new favorite journalist `@robinlevinson`_, for showing an "
+"interest in our cause and\n"
+"educating yourself about the technologies involved."
+msgstr ""
+
+#: i2p2www/blog/2015/08/20/I2PCon_Mission_Accomplished.rst:104
+msgid ""
+"Thanks for all the pizza `@Panago_Pizza`_, it keept us going. You very "
+"much made this event better."
+msgstr ""
+
+#: i2p2www/blog/2015/08/20/I2PCon_Mission_Accomplished.rst:108
+msgid ""
+"Finally I would like to thank everyone else who just showed up to the "
+"event and helped out in any way\n"
+"they could.\n"
+"ComradeNosebleed, LazyGravy, `cacapo`_, Xmz, ZeroRax, `echelon`_, it was "
+"most excellent to hang out\n"
+"with you."
+msgstr ""
+
+#: i2p2www/blog/2015/09/12/0.9.22-Release.rst:1
+msgid ""
+"==============\n"
+"0.9.22 Release\n"
+"=============="
+msgstr ""
+
+#: i2p2www/blog/2015/09/12/0.9.22-Release.rst:10
+msgid "0.9.22 with bug fixes and start of Ed25519 migration"
+msgstr ""
+
+#: i2p2www/blog/2015/09/12/0.9.22-Release.rst:12
+msgid ""
+"0.9.22 contains fixes for i2psnark getting stuck before completion, and "
+"begins the migration of router infos to new, stronger Ed25519 signatures."
+"\n"
+"To reduce network churn, your router will have only a small probability "
+"of converting to Ed25519 at each restart.\n"
+"When it does rekey, expect to see lower bandwidth usage for a couple of "
+"days as it reintegrates into the network with its new identity.\n"
+"If all goes well, we will accelerate the rekeying process in the next "
+"release."
+msgstr ""
+"Əvvəlcə 0.9.22 buraxılışında ilişməyə səbəb olan i2psnark problemi həll "
+"olundu və istiqamətləndirici məlumatlarının yeni və daha güclü Ed25519 "
+"imzalarına keçirilməsi təmin olundu.\n"
+"Şəbəkə qarışıqlığı olmasın deyə, istiqmətləndiriciniz hər dəfə yenidən "
+"başlayanda kiçik ehtimalla Ed25519 çevrilməsi edəcək. \n"
+"Əgər bu baş verərsə, yaxın iki gündə yeni ünvan şəbəkəyə uyğunlaşana "
+"qədər trafikin azalması müşahidə olunacaq. \n"
+"Hər şey yolunda getsə, sonrakı buraxılışda yenidən açar yaratmaq "
+"prosesini sürətləndirəcəyik. "
+
+#: i2p2www/blog/2015/09/12/0.9.22-Release.rst:19
+msgid ""
+"I2PCon Toronto was a big success!\n"
+"All the presentations and videos are listed on the `I2PCon page`_."
+msgstr ""
+
+#: i2p2www/blog/2015/09/12/0.9.22-Release.rst:30
+msgid "`I2PCon page`"
+msgstr ""
+
+#: i2p2www/blog/2015/09/12/0.9.22-Release.rst:38
+msgid "Start migration to Ed25519 router info signatures"
+msgstr ""
+
+#: i2p2www/blog/2015/09/12/0.9.22-Release.rst:39
+msgid "Convert i2psnark destinations to Ed25519 signatures"
+msgstr ""
+
+#: i2p2www/blog/2015/09/12/0.9.22-Release.rst:44
+msgid ""
+"Fix i2psnark getting stuck before download complete, and not deleting "
+"temp files"
+msgstr ""
+
+#: i2p2www/blog/2015/09/12/0.9.22-Release.rst:45
+msgid ""
+"Fix starting of torrents added by copying torrent file to i2psnark "
+"directory"
+msgstr ""
+
+#: i2p2www/blog/2015/09/12/0.9.22-Release.rst:46
+msgid "Fix UPnP 'content not allowed in trailing section' error"
+msgstr ""
+
+#: i2p2www/blog/2015/09/12/0.9.22-Release.rst:47
+msgid "Fix excluded SSL ciphers in console"
+msgstr ""
+
+#: i2p2www/blog/2015/11/15/Community-Outreach.rst:1
+msgid ""
+"==================\n"
+"Community Outreach\n"
+"=================="
+msgstr ""
+
+#: i2p2www/blog/2015/11/15/Community-Outreach.rst:10
+msgid "A start to more frequent community status reports."
+msgstr ""
+
+#: i2p2www/blog/2015/11/15/Community-Outreach.rst:12
+msgid "Meta"
+msgstr ""
+
+#: i2p2www/blog/2015/11/15/Community-Outreach.rst:14
+msgid ""
+"Greetings!\n"
+"This is the first in a long series of blogs to help the community see "
+"what is happening in the I2P community.\n"
+"Since many awesome events are happening *inside* the network, we think it"
+" will be worthwhile to talk about some of activities here."
+msgstr ""
+
+#: i2p2www/blog/2015/11/15/Community-Outreach.rst:20
+msgid "A Call for Feedback"
+msgstr ""
+
+#: i2p2www/blog/2015/11/15/Community-Outreach.rst:22
+msgid ""
+"Let's face it -- our console needs improvement.\n"
+"Our site could use an update as well.\n"
+"We are looking for feedback on how to improve the usability of I2P for "
+"new and existing users!"
+msgstr ""
+
+#: i2p2www/blog/2015/11/15/Community-Outreach.rst:28
+msgid ""
+"Any and all feedback is welcome.\n"
+"Please contact `@GetI2P`_, `@str4d`_, or `@YrB1rd`_.\n"
+"If you don't feel comfortable using Twitter, we are always available via "
+"the in-network IRC channel.\n"
+"You don't have to be a long time user.\n"
+"We want to hear from all sorts of people!"
+msgstr ""
+
+#: i2p2www/blog/2015/11/15/Community-Outreach.rst:40
+msgid "Developer Meeting Synopsis"
+msgstr ""
+
+#: i2p2www/blog/2015/11/15/Community-Outreach.rst:42
+msgid ""
+"On 03 November there was an I2P developer meeting (`log`_).\n"
+"This meeting focused on adding new links to the router console, "
+"preparation for CCC, finding a replacement for forum.i2p, and website "
+"improvements."
+msgstr ""
+
+#: i2p2www/blog/2015/11/15/Community-Outreach.rst:49
+msgid ""
+"The consensus was to not add dogecoindark.i2p.\n"
+"There are concerns about usability due to many images being included on "
+"the page.\n"
+"Exchanged.i2p is conditionally added, as long as the maintainer adds a "
+"disclaimer on the site.\n"
+"I2Pwiki.i2p (a backup of ugha.i2p, an older wiki) was accepted, as was "
+"lenta.i2p (a russian news site)."
+msgstr ""
+
+#: i2p2www/blog/2015/11/15/Community-Outreach.rst:56
+msgid ""
+"str4d proposed blocking off the \\*.i2p.i2p namespace so they can be used"
+" for developer's services.\n"
+"He also suggested a more formalized technical proposal system, with more "
+"prominence on the main website."
+msgstr ""
+
+#: i2p2www/blog/2015/11/15/Community-Outreach.rst:61
+msgid ""
+"The I2P Team is going to be in Hamburg, Germany for the 32nd Chaos "
+"Computer Congress.\n"
+"More details are to come on this, but we can promise there will be "
+"stickers."
+msgstr ""
+
+#: i2p2www/blog/2015/11/15/Community-Outreach.rst:66
+msgid "General Announcements"
+msgstr ""
+
+#: i2p2www/blog/2015/11/15/Community-Outreach.rst:68
+msgid "Thank you to `TorontoCrypto`_ for hosting the newest I2P reseed server!"
+msgstr ""
+
+#: i2p2www/blog/2015/11/15/Community-Outreach.rst:74
+msgid ""
+"Translation deadline Thursday, 12 November, translators please update. "
+"All translations are done via `Transifex`_ ."
+msgstr ""
+
+#: i2p2www/blog/2015/11/19/0.9.23-Release.rst:1
+msgid ""
+"==============\n"
+"0.9.23 Release\n"
+"=============="
+msgstr ""
+
+#: i2p2www/blog/2015/11/19/0.9.23-Release.rst:10
+msgid ""
+"0.9.23 contains a variety of bug fixes, and some minor improvements in "
+"I2PSnark"
+msgstr ""
+"0.9.23 buraxılışında çeşidli xəta düzəlişləri və I2PSnark irəliləyişləri "
+"yer alıb"
+
+#: i2p2www/blog/2015/11/19/0.9.23-Release.rst:12
+msgid ""
+"Hello I2P! This is the first release signed by me (str4d), after 49 "
+"releases\n"
+"signed by zzz. This is an important test of our redundancy for all "
+"things,\n"
+"including people."
+msgstr ""
+"Salam I2P! Bu buraxılış zzz tərəfindən imzalanan 49 buraxılışdan sonra "
+"mənim imzaladığım (str4d) ilk buraxılışdır. \n"
+"Layihənin müxtəlif hissələrinin, o cümlədən, iştirakçılarının "
+"dəyişməsinin yoxlanılması."
+
+#: i2p2www/blog/2015/11/19/0.9.23-Release.rst:18
+msgid ""
+"Housekeeping\n"
+"============"
+msgstr ""
+
+#: i2p2www/blog/2015/11/19/0.9.23-Release.rst:23
+msgid ""
+"My signing key has been in router updates for over two years (since "
+"0.9.9), so\n"
+"if you are on a recent version of I2P this update should be just as easy "
+"as\n"
+"every other update. However, if you are running an older version than "
+"0.9.9, you\n"
+"will first need to manually update to a recent version. Update files for "
+"recent\n"
+"versions `can be downloaded here`_, and instructions on how to manually "
+"update\n"
+"`are provided here`_. Once you have manually updated, your router will "
+"then find\n"
+"and download the 0.9.23 update as usual."
+msgstr ""
+
+#: i2p2www/blog/2015/11/19/0.9.23-Release.rst:33
+msgid "`can be downloaded here`"
+msgstr ""
+
+#: i2p2www/blog/2015/11/19/0.9.23-Release.rst:35
+msgid "`are provided here`"
+msgstr ""
+
+#: i2p2www/blog/2015/11/19/0.9.23-Release.rst:37
+msgid ""
+"If you installed I2P via a package manager, you are not affected by the "
+"change,\n"
+"and can update as usual."
+msgstr ""
+"I2P-ni paket idarəçisi tərəfindən quraşdırmısınızsa, dəyişikliklərdən "
+"təsirlənməyəcək və normal şəkildə yeniləyə biləcəksiniz.  "
+
+#: i2p2www/blog/2015/11/19/0.9.23-Release.rst:42
+#: i2p2www/blog/2016/01/27/0.9.24-Release.rst:12
+#: i2p2www/blog/2016/03/22/0.9.25-Release.rst:12
+#: i2p2www/blog/2016/06/07/0.9.26-Release.rst:19
+#: i2p2www/blog/2016/10/17/0.9.27-Release.rst:12
+#: i2p2www/blog/2016/12/12/0.9.28-Release.rst:12
+#: i2p2www/blog/2017/02/27/0.9.29-Release.rst:12
+#: i2p2www/blog/2017/03/04/0.9.29-Windows-Installer-Fix.rst:12
+#: i2p2www/blog/2017/05/03/0.9.30-Release.rst:12
+#: i2p2www/blog/2017/08/07/0.9.31-Release.rst:12
+#: i2p2www/blog/2017/11/07/0.9.32-Release.rst:12
+#: i2p2www/blog/2018/01/30/0.9.33-Release.rst:12
+#: i2p2www/blog/2018/04/10/0.9.34-Release.rst:12
+#: i2p2www/blog/2018/06/26/0.9.35-Release.rst:12
+#: i2p2www/blog/2018/08/23/0.9.36-Release.rst:12
+msgid ""
+"Update details\n"
+"=============="
+msgstr ""
+
+#: i2p2www/blog/2015/11/19/0.9.23-Release.rst:47
+msgid ""
+"The migration of RouterInfos to new, stronger Ed25519 signatures is going"
+" well,\n"
+"with at least half of the network already estimated to have rekeyed. This"
+"\n"
+"release accelerates the rekeying process. To reduce network churn, your "
+"router\n"
+"will have a small probability of converting to Ed25519 at each restart. "
+"When it\n"
+"does rekey, expect to see lower bandwidth usage for a couple of days as "
+"it\n"
+"reintegrates into the network with its new identity."
+msgstr ""
+"Routerinfos üçün yeni və daha güclü Ed25519 imzalarına keçmə işi yaxşı "
+"gedir. \n"
+"Şəbəkənin ən az yarısı yenilənib. Bu buraxılışda açar dəyişdirmə prosesi "
+"sürətləndirildi. Şəbəkədə\n"
+" qarışıqlıq yaratmamaq üçün istiqamətləndiriciniz hər dəfə yenidən "
+"başladıldıqda az miqdarda\n"
+"Ed25519-a dəyişmək ehtimalı var. Əgər bu baş verərsə, yaxın iki gündə "
+"yeni ünvan şəbəkəyə \n"
+"uyğunlaşana qədər trafikin azalması müşahidə olunacaq."
+
+#: i2p2www/blog/2015/11/19/0.9.23-Release.rst:56
+msgid ""
+"Note that this will be the last release to support Java 6. Please update "
+"to\n"
+"Java 7 or 8 as soon as possible. We are already working to make I2P "
+"compatible\n"
+"with the upcoming Java 9, and some of that work is in this release."
+msgstr ""
+"\n"
+"Bu, Java 6-nı dəstəkləyən son buraxılışdır. Java 7 və ya 8 buraxılışına "
+"mümkün qədər tez\n"
+" yeniləməyi unutmayın. I2P buraxılışını tezliklə buraxılacaq Java 9 ilə "
+"uyumlu şəkildə inkişaf \n"
+"etdirməyə başladıq və artıq bəzi dəyişikliklər edilib. "
+
+#: i2p2www/blog/2015/11/19/0.9.23-Release.rst:62
+msgid ""
+"We have also made some minor improvements in I2PSnark, and added a new "
+"page in\n"
+"the routerconsole for viewing older news items."
+msgstr ""
+"I2PSnark-da bəzi kiçik yeniləmələr edərək, routerconsole üçün keçmiş "
+"xəbərlərin görüntülənə biləcəyi yeni səhifə əlavə etdik."
+
+#: i2p2www/blog/2015/11/19/0.9.23-Release.rst:77
+msgid "Accelerate transition to Ed25519"
+msgstr ""
+
+#: i2p2www/blog/2015/11/19/0.9.23-Release.rst:82
+msgid ""
+"Fix some bugs soft restarting after a large clock shift (e.g. resume) "
+"(but more to do)"
+msgstr ""
+
+#: i2p2www/blog/2015/11/19/0.9.23-Release.rst:83
+msgid ""
+"Fix streaming retransmission timers that were dying, and related timer "
+"bugs"
+msgstr ""
+
+#: i2p2www/blog/2015/11/19/0.9.23-Release.rst:84
+msgid "Fix streaming connections rejected while tunnel is opening"
+msgstr ""
+
+#: i2p2www/blog/2015/11/19/0.9.23-Release.rst:85
+msgid "Fix rare i2psnark and UPnP deadlocks"
+msgstr ""
+
+#: i2p2www/blog/2015/11/19/0.9.23-Release.rst:86
+msgid "Fix lifetime participating bandwidth display in console"
+msgstr ""
+
+#: i2p2www/blog/2015/11/19/0.9.23-Release.rst:91
+msgid "Increase default outbound exploratory tunnel length to 3"
+msgstr ""
+
+#: i2p2www/blog/2015/11/19/0.9.23-Release.rst:92
+msgid ""
+"Use max of 2 not-failing peers in exploratory tunnels to improve build "
+"success"
+msgstr ""
+
+#: i2p2www/blog/2015/11/19/0.9.23-Release.rst:93
+msgid "Add support for hostnames prefixed with \"www.\""
+msgstr ""
+
+#: i2p2www/blog/2015/11/19/0.9.23-Release.rst:94
+msgid ""
+"Store news feed items separately on disk, show on new /news page, limit "
+"display on home page to 2"
+msgstr ""
+
+#: i2p2www/blog/2015/11/19/0.9.23-Release.rst:95
+msgid "Increase probability of rekeying to EdDSA"
+msgstr ""
+
+#: i2p2www/blog/2015/11/19/0.9.23-Release.rst:96
+msgid "Detect for broken ECDSA support in Gentoo"
+msgstr ""
+
+#: i2p2www/blog/2015/11/19/0.9.23-Release.rst:97
+msgid "Console: Add a Java 6 warning, this is the last release to support Java 6"
+msgstr ""
+
+#: i2p2www/blog/2015/11/19/0.9.23-Release.rst:98
+msgid "Changes to prepare for Java 9 compatibility"
+msgstr ""
+
+#: i2p2www/blog/2015/11/19/0.9.23-Release.rst:99
+msgid ""
+"Pass Accept-Encoding header through client and server proxies, to allow "
+"end-to-end compression"
+msgstr ""
+
+#: i2p2www/blog/2015/11/19/0.9.23-Release.rst:102
+msgid "Increase piece size, piece count, and file count limits"
+msgstr ""
+
+#: i2p2www/blog/2015/11/19/0.9.23-Release.rst:103
+msgid "Save added and completed times"
+msgstr ""
+
+#: i2p2www/blog/2015/11/19/0.9.23-Release.rst:104
+msgid "Save magnet parameters across restart"
+msgstr ""
+
+#: i2p2www/blog/2015/11/19/0.9.23-Release.rst:105
+msgid "Don't delete .torrent file on errors at startup, rename to .torrent.BAD"
+msgstr ""
+
+#: i2p2www/blog/2015/11/19/0.9.23-Release.rst:106
+msgid "Add recheck, start, stop buttons on details pages"
+msgstr ""
+
+#: i2p2www/blog/2015/11/19/0.9.23-Release.rst:107
+msgid "Add option to disable \"smart sort\""
+msgstr ""
+
+#: i2p2www/blog/2015/11/19/0.9.23-Release.rst:109
+msgid "Speed up IP address validation"
+msgstr ""
+
+#: i2p2www/blog/2015/11/19/0.9.23-Release.rst:110
+msgid "Separate streaming blacklists for ECDSA and EdDSA"
+msgstr ""
+
+#: i2p2www/blog/2016/01/23/32C3.rst:1
+msgid ""
+"=========\n"
+"CCC Recap\n"
+"========="
+msgstr ""
+
+#: i2p2www/blog/2016/01/23/32C3.rst:10
+msgid "CCC!"
+msgstr ""
+
+#: i2p2www/blog/2016/01/23/32C3.rst:12
+msgid ""
+"Attending: Sadie, Colin, lazygravy, zzz, hottuna, kytv, cacapo, and "
+"eche|on."
+msgstr ""
+
+#: i2p2www/blog/2016/01/23/32C3.rst:16
+msgid ""
+"Start\n"
+"=====\n"
+"The project has had another successful year at CCC.\n"
+"We would like to thank the volunteers at `32C3`_ for all of their help in"
+" organizing this event and for being accommodating hosts for us.\n"
+"Many I2P contributors were able to attend this year's Congress due to "
+"many of the generous donations from supporters like you to the project.\n"
+"If you would like to fund I2P, please see `our donation page`_ for more "
+"information."
+msgstr ""
+
+#: i2p2www/blog/2016/01/23/32C3.rst:25
+msgid "`32C3`"
+msgstr ""
+
+#: i2p2www/blog/2016/01/23/32C3.rst:26
+msgid "`our donation page`"
+msgstr ""
+
+#: i2p2www/blog/2016/01/23/32C3.rst:28
+msgid ""
+"Just like previous years we were located in Noisy Square, located near "
+"the EFF's table.\n"
+"This proved to be an ideal spot for us as our table was almost always "
+"busy with current and new users who were interested in I2P, many of whom "
+"we wouldn't have otherwise had the ability to talk to."
+msgstr ""
+
+#: i2p2www/blog/2016/01/23/32C3.rst:62
+msgid ""
+"Reseed Status\n"
+"============="
+msgstr ""
+
+#: i2p2www/blog/2016/01/23/32C3.rst:67
+msgid "Let's get more reseeds!"
+msgstr ""
+
+#: i2p2www/blog/2016/01/23/32C3.rst:71
+msgid ""
+"If you don't know what a reseed server is, it is first the connection new"
+" routers use to find peers.\n"
+"There was a lot of discussion around the current status of the reseed "
+"network right now.\n"
+"As always, more reseed operators are needed!\n"
+"If you would like to strengthen the reseed infrastructure, (or if you're "
+"talented with Go) email `backup -at- i2pmail.org`_."
+msgstr ""
+
+#: i2p2www/blog/2016/01/23/32C3.rst:78
+msgid "`backup -at- i2pmail.org`"
+msgstr ""
+
+#: i2p2www/blog/2016/01/23/32C3.rst:80
+msgid ""
+"Sybil Detection (beta)\n"
+"======================"
+msgstr ""
+
+#: i2p2www/blog/2016/01/23/32C3.rst:85
+msgid ""
+"Due to the decentralized nature of I2P detecting Sybil attacks is not as "
+"straight forward as on other networks (i.e. Tor).\n"
+"To mitigate this zzz has been working on a new router-based Sybil "
+"detection tool.\n"
+"To be brief, the tool runs in the router, and collects information on "
+"floodfills your router is currently aware of.\n"
+"Currently the tool is mainly collecting a baseline and does not act on "
+"any of the information it is collecting.\n"
+"Expect to see a writeup on this more as 0.9.25 or 0.9.26 approaches, as "
+"it is still in active development"
+msgstr ""
+
+#: i2p2www/blog/2016/01/23/32C3.rst:93
+msgid ""
+"Development Meeting\n"
+"==================="
+msgstr ""
+
+#: i2p2www/blog/2016/01/23/32C3.rst:98
+msgid ""
+"On the 30th we held an in person `meeting`_ at our table.\n"
+"The meeting focused on organizationally preparing for more project "
+"management, and public relations (both from Sadie)."
+msgstr ""
+
+#: i2p2www/blog/2016/01/23/32C3.rst:103
+msgid "`meeting`"
+msgstr ""
+
+#: i2p2www/blog/2016/01/23/32C3.rst:105
+msgid ""
+"We discussed how much of the work done on I2P is lost in the commits and "
+"there is not much to see for our users.\n"
+"To remedy this lazygravy plans on preparing a series of posts explaining "
+"some technical topics in I2P.\n"
+"The initial ideas that we discussed writing posts on are what encrypted "
+"lease sets are, why different tunnel types are needed, and some "
+"observations seen in `I2Spy`_.\n"
+"But these are just the start and we would like to hear feedback on topics"
+" we should write about!"
+msgstr ""
+
+#: i2p2www/blog/2016/01/23/32C3.rst:112
+msgid "`i2spy`"
+msgstr ""
+
+#: i2p2www/blog/2016/01/23/32C3.rst:114
+msgid ""
+"Meeting (Future)\n"
+"================"
+msgstr ""
+
+#: i2p2www/blog/2016/01/23/32C3.rst:119
+msgid "There will be a `another meeting`_ on 2 Feburary 2016 to discuss:"
+msgstr ""
+
+#: i2p2www/blog/2016/01/23/32C3.rst:123
+msgid "Review of assigned tasks from 30 December meeting"
+msgstr ""
+
+#: i2p2www/blog/2016/01/23/32C3.rst:124
+msgid "Project meeting plan for 2016"
+msgstr ""
+
+#: i2p2www/blog/2016/01/23/32C3.rst:125
+msgid "GMP 6 readiness"
+msgstr ""
+
+#: i2p2www/blog/2016/01/23/32C3.rst:126
+msgid "A proposal for a code of conduct"
+msgstr ""
+
+#: i2p2www/blog/2016/01/23/32C3.rst:128
+msgid "`another meeting`"
+msgstr ""
+
+#: i2p2www/blog/2016/01/27/0.9.24-Release.rst:1
+msgid ""
+"==============\n"
+"0.9.24 Release\n"
+"=============="
+msgstr ""
+
+#: i2p2www/blog/2016/01/27/0.9.24-Release.rst:10
+msgid "0.9.24 contains a variety of bug fixes and performance enhancements"
+msgstr ""
+
+#: i2p2www/blog/2016/01/27/0.9.24-Release.rst:17
+msgid ""
+"0.9.24 contains a new version of SAM (v3.2) and numerous bug fixes and "
+"efficiency improvements.\n"
+"Note that this release is the first to require Java 7.\n"
+"Please update to Java 7 or 8 as soon as possible.\n"
+"Your router will not automatically update if you are using Java 6."
+msgstr ""
+"0.9.24 yeni SAM (v3.2) buraxılışı və çeşidli xəta və sürətləndirmə "
+"düzəlişlərindən ibarətdir..\n"
+"Bu buraxılışın işləməsi üçün Java 7 tələb olunur. \n"
+"Ən qısa zamanda Java 7 və ya 8-ə yeniləyin.\n"
+"Java 6-dan istifadə etdiyiniz halda istiqamətləndiriciniz avtomatik "
+"olaraq yenilənməyəcək."
+
+#: i2p2www/blog/2016/01/27/0.9.24-Release.rst:24
+msgid ""
+"To prevent the problems caused by the ancient commons-logging library, we"
+" have removed it.\n"
+"This will cause very old I2P-Bote plugins (0.2.10 and below, signed by "
+"HungryHobo) to crash if they have IMAP enabled.\n"
+"The recommended fix is to replace your old I2P-Bote plugin with the "
+"current one signed by str4d.\n"
+"For more details, see `this post`_."
+msgstr ""
+
+#: i2p2www/blog/2016/01/27/0.9.24-Release.rst:31
+msgid "`this post`"
+msgstr ""
+
+#: i2p2www/blog/2016/01/27/0.9.24-Release.rst:33
+msgid ""
+"We had a great `32C3 Congress`_ and are making good progress on our 2016 "
+"project plans.\n"
+"Echelon gave a talk on I2P's history and current status, and his slides "
+"are `available here`_ (pdf).\n"
+"Str4d attended `Real World Crypto`_ and gave a talk on our crypto "
+"migration, his slides are `here`_ (pdf)."
+msgstr ""
+
+#: i2p2www/blog/2016/01/27/0.9.24-Release.rst:39
+msgid "`32C3 Congress`"
+msgstr ""
+
+#: i2p2www/blog/2016/01/27/0.9.24-Release.rst:41
+msgid "`available here`"
+msgstr ""
+
+#: i2p2www/blog/2016/01/27/0.9.24-Release.rst:43
+msgid "`Real World Crypto`"
+msgstr ""
+
+#: i2p2www/blog/2016/01/27/0.9.24-Release.rst:57
+msgid "Java 7 now required"
+msgstr ""
+
+#: i2p2www/blog/2016/01/27/0.9.24-Release.rst:58
+msgid ""
+"SAM 3.2, with several new advanced features, command parser improvements,"
+" and lots of bug fixes"
+msgstr ""
+
+#: i2p2www/blog/2016/01/27/0.9.24-Release.rst:59
+msgid "Router Family"
+msgstr ""
+
+#: i2p2www/blog/2016/01/27/0.9.24-Release.rst:60
+msgid "Commons logging removed"
+msgstr ""
+
+#: i2p2www/blog/2016/01/27/0.9.24-Release.rst:65
+msgid "Fix HTML escaping in the console plugin table"
+msgstr ""
+
+#: i2p2www/blog/2016/01/27/0.9.24-Release.rst:66
+msgid "Fix rare deadlocks in the router"
+msgstr ""
+
+#: i2p2www/blog/2016/01/27/0.9.24-Release.rst:67
+msgid "Fix the tunnel build Bloom filter"
+msgstr ""
+
+#: i2p2www/blog/2016/01/27/0.9.24-Release.rst:68
+msgid ""
+"Don't remove tunnel on next-hop failure indication from transport, it "
+"isn't reliable"
+msgstr ""
+
+#: i2p2www/blog/2016/01/27/0.9.24-Release.rst:69
+msgid "Fix formatting in summary bar to prevent overflow"
+msgstr ""
+
+#: i2p2www/blog/2016/01/27/0.9.24-Release.rst:70
+msgid "Fix console links in i2ptunnel error pages when on nonstandard host/port"
+msgstr ""
+
+#: i2p2www/blog/2016/01/27/0.9.24-Release.rst:71
+msgid ""
+"Don't query floodfills whose version is too old to support encrypted "
+"replies"
+msgstr ""
+
+#: i2p2www/blog/2016/01/27/0.9.24-Release.rst:72
+msgid "Reduce out-of-order delivery in SSU"
+msgstr ""
+
+#: i2p2www/blog/2016/01/27/0.9.24-Release.rst:73
+msgid "Fix a rare NPE in the tunnel build handler"
+msgstr ""
+
+#: i2p2www/blog/2016/01/27/0.9.24-Release.rst:78
+msgid "Listen for Windows Service shutdown events to shutdown cleanly"
+msgstr ""
+
+#: i2p2www/blog/2016/01/27/0.9.24-Release.rst:79
+msgid "Fix some IPv6 issues on Windows"
+msgstr ""
+
+#: i2p2www/blog/2016/01/27/0.9.24-Release.rst:80
+msgid "Change Jetty request logging from b64 to b32"
+msgstr ""
+
+#: i2p2www/blog/2016/01/27/0.9.24-Release.rst:81
+msgid ""
+"New 'family' indication in netdb, don't use two of the same family in a "
+"tunnel"
+msgstr ""
+
+#: i2p2www/blog/2016/01/27/0.9.24-Release.rst:82
+msgid "New overview picture in SusiDNS"
+msgstr ""
+
+#: i2p2www/blog/2016/01/27/0.9.24-Release.rst:83
+msgid "Close connection faster if it's for a rejected tunnel request"
+msgstr ""
+
+#: i2p2www/blog/2016/01/27/0.9.24-Release.rst:84
+msgid "Use SSU extended options field for session request message"
+msgstr ""
+
+#: i2p2www/blog/2016/01/27/0.9.24-Release.rst:85
+msgid "Request introduction in the SSU extended options"
+msgstr ""
+
+#: i2p2www/blog/2016/01/27/0.9.24-Release.rst:86
+msgid ""
+"Don't offer to introduce unless requested, to introduce only those that "
+"need it"
+msgstr ""
+
+#: i2p2www/blog/2016/01/27/0.9.24-Release.rst:87
+msgid "Experimental Sybil analysis tool, requires routerconsole.advanced=true"
+msgstr ""
+
+#: i2p2www/blog/2016/01/27/0.9.24-Release.rst:88
+msgid "Persist some profile netdb stats that weren't being saved"
+msgstr ""
+
+#: i2p2www/blog/2016/01/27/0.9.24-Release.rst:89
+msgid "Memory reduction and other efficiency improvements throughout"
+msgstr ""
+
+#: i2p2www/blog/2016/01/27/0.9.24-Release.rst:90
+msgid "Increase several limits in i2psnark"
+msgstr ""
+
+#: i2p2www/blog/2016/01/27/0.9.24-Release.rst:91
+msgid "New streaming unit tests"
+msgstr ""
+
+#: i2p2www/blog/2016/01/27/0.9.24-Release.rst:92
+msgid "Fix some SSU stats on /peers to be consistent with NTCP"
+msgstr ""
+
+#: i2p2www/blog/2016/01/27/0.9.24-Release.rst:93
+msgid "Change default sig type for new i2ptunnels to Ed25519"
+msgstr ""
+
+#: i2p2www/blog/2016/01/27/0.9.24-Release.rst:94
+msgid "Increase router rekey probability at startup again"
+msgstr ""
+
+#: i2p2www/blog/2016/01/27/0.9.24-Release.rst:95
+msgid "New Chinese (Taiwan) translation"
+msgstr ""
+
+#: i2p2www/blog/2016/01/27/0.9.24-Release.rst:102
+#: i2p2www/blog/2016/03/22/0.9.25-Release.rst:73
+#: i2p2www/blog/2016/06/07/0.9.26-Release.rst:93
+#: i2p2www/blog/2016/10/17/0.9.27-Release.rst:70
+#: i2p2www/blog/2016/12/12/0.9.28-Release.rst:100
+#: i2p2www/blog/2017/02/27/0.9.29-Release.rst:74
+#: i2p2www/blog/2017/05/03/0.9.30-Release.rst:99
+#: i2p2www/blog/2017/08/07/0.9.31-Release.rst:66
+#: i2p2www/blog/2017/11/07/0.9.32-Release.rst:55
+#: i2p2www/blog/2018/01/30/0.9.33-Release.rst:101
+#: i2p2www/blog/2018/04/10/0.9.34-Release.rst:60
+#: i2p2www/blog/2018/06/26/0.9.35-Release.rst:76
+#: i2p2www/blog/2018/08/23/0.9.36-Release.rst:70
+msgid "`Full list of fixed bugs`"
+msgstr ""
+
+#: i2p2www/blog/2016/03/22/0.9.25-Release.rst:1
+msgid ""
+"==============\n"
+"0.9.25 Release\n"
+"=============="
+msgstr ""
+
+#: i2p2www/blog/2016/03/22/0.9.25-Release.rst:10
+msgid "0.9.25 contains SAM 3.3, QR codes, and bug fixes"
+msgstr "0.9.25 buraxılışında SAM 3.3, QR kodları və xəta düzəlişləri yer alıb"
+
+#: i2p2www/blog/2016/03/22/0.9.25-Release.rst:17
+msgid ""
+"0.9.25 contains a major new version of SAM, v3.3, to support "
+"sophisticated multiprotocol applications.\n"
+"It adds QR codes for sharing hidden service addresses with others,\n"
+"and \"identicon\" images for visually distinguishing addresses."
+msgstr ""
+"0.9.25 mürəkkəb çox protokollu tətbiqləri dəstəkləyən yeni SAM, v3.3 "
+"buraxılışından ibarətdir.  \n"
+"Gizli xidmət ünvanlarını paylaşmaq üçün QR kodları və ünvanları gözlə "
+"ayırd edə bilmək üçün \n"
+"\"identicon\" təsvirləri əlavə olundu. "
+
+#: i2p2www/blog/2016/03/22/0.9.25-Release.rst:23
+msgid ""
+"We've added a new \"router family\" configuration page in the console,\n"
+"to make it easier to declare that your group of routers is run by a "
+"single person.\n"
+"There are several changes to increase the capacity of the network and "
+"hopefully improve tunnel build success."
+msgstr ""
+"Təkcə bir adam tərəfindən işlədilən istiqamələndirici qrupunu daha asan "
+"müəyyən etmək üçün \n"
+"konsola yeni \"istiqamətləndirici ailə\" quraşdırma səhifəsi əlavə "
+"olundu. Şəbəkə həcmini və tunel \n"
+"quruluş uğurunu artıran bəzi dəyişikliklər edildi.  "
+
+#: i2p2www/blog/2016/03/22/0.9.25-Release.rst:39
+msgid "Display of identicons and QR codes in address book and i2ptunnel"
+msgstr ""
+
+#: i2p2www/blog/2016/03/22/0.9.25-Release.rst:40
+msgid "SAM v3.3 with advanced features"
+msgstr ""
+
+#: i2p2www/blog/2016/03/22/0.9.25-Release.rst:41
+msgid "Configuration page for router family"
+msgstr ""
+
+#: i2p2www/blog/2016/03/22/0.9.25-Release.rst:42
+msgid "Custom icons for plugins"
+msgstr ""
+
+#: i2p2www/blog/2016/03/22/0.9.25-Release.rst:43
+msgid "Internal implementation of self-signed certificate generation"
+msgstr ""
+
+#: i2p2www/blog/2016/03/22/0.9.25-Release.rst:44
+msgid "Add i2ptunnel http server options to block by referer or user-agent"
+msgstr ""
+
+#: i2p2www/blog/2016/03/22/0.9.25-Release.rst:49
+msgid "IRC server tunnel default fix to help reliability"
+msgstr ""
+
+#: i2p2www/blog/2016/03/22/0.9.25-Release.rst:50
+msgid "Don't wait until a lease expires to switch to a new on"
+msgstr ""
+
+#: i2p2www/blog/2016/03/22/0.9.25-Release.rst:55
+msgid "Preliminary support for certificate revocations"
+msgstr ""
+
+#: i2p2www/blog/2016/03/22/0.9.25-Release.rst:56
+msgid "Preliminary support for storing EdDSA and ElGamal keys in keystores"
+msgstr ""
+
+#: i2p2www/blog/2016/03/22/0.9.25-Release.rst:57
+msgid "More efficient signing and verification with EdDSA"
+msgstr ""
+
+#: i2p2www/blog/2016/03/22/0.9.25-Release.rst:58
+msgid "Increase default connection limits"
+msgstr ""
+
+#: i2p2www/blog/2016/03/22/0.9.25-Release.rst:59
+msgid "Increase default inbound bandwidth"
+msgstr ""
+
+#: i2p2www/blog/2016/03/22/0.9.25-Release.rst:60
+msgid "Increase max files per torrent in i2psnark"
+msgstr ""
+
+#: i2p2www/blog/2016/03/22/0.9.25-Release.rst:61
+msgid "Add more sanity checks to detect bad system clock"
+msgstr ""
+
+#: i2p2www/blog/2016/03/22/0.9.25-Release.rst:62
+msgid "Improve news styling in console"
+msgstr ""
+
+#: i2p2www/blog/2016/03/22/0.9.25-Release.rst:63
+msgid "Improve certificate blacklist implementation"
+msgstr ""
+
+#: i2p2www/blog/2016/03/22/0.9.25-Release.rst:64
+msgid "Faster disconnect after publishing router info to floodfill"
+msgstr ""
+
+#: i2p2www/blog/2016/03/22/0.9.25-Release.rst:65
+msgid "Smooth out the dropping of idle SSU sessions"
+msgstr ""
+
+#: i2p2www/blog/2016/03/22/0.9.25-Release.rst:66
+msgid "Add X-Content-Type-Options headers in console"
+msgstr ""
+
+#: i2p2www/blog/2016/06/01/I2P-Summer-Dev.rst:1
+msgid ""
+"==============\n"
+"I2P Summer Dev\n"
+"=============="
+msgstr ""
+
+#: i2p2www/blog/2016/06/01/I2P-Summer-Dev.rst:10
+msgid ""
+"We are pleased to announce that this summer, I2P will be embarking on a "
+"development program aimed at improving the privacy software ecosystem for"
+" both developers and users."
+msgstr ""
+
+#: i2p2www/blog/2016/06/01/I2P-Summer-Dev.rst:12
+msgid ""
+"Over the last few years, the need for users to be in control of their own"
+" data\n"
+"has become increasingly apparent. Some excellent progress had been made "
+"in this\n"
+"regard with the rise of messaging apps like Signal_, and file storage "
+"systems\n"
+"like Tahoe-LAFS_. The ongoing work of `Let's Encrypt`_ to bring HTTPS to "
+"the\n"
+"whole world is steadily gaining traction."
+msgstr ""
+
+#: i2p2www/blog/2016/06/01/I2P-Summer-Dev.rst:20
+msgid ""
+"But building privacy and anonymity into applications is not trivial. Much"
+" of the\n"
+"software people use every day was not designed to be privacy-preserving, "
+"and the\n"
+"tools developers have available are generally not easy to work with. The\n"
+"recently-published OnionScan_ survey gives some insight into just how "
+"easy it is\n"
+"for even technical users to mis-configure their services, completely "
+"undermining\n"
+"their intentions."
+msgstr ""
+
+#: i2p2www/blog/2016/06/01/I2P-Summer-Dev.rst:35
+msgid ""
+"Helping developers help their users\n"
+"==================================="
+msgstr ""
+
+#: i2p2www/blog/2016/06/01/I2P-Summer-Dev.rst:40
+msgid ""
+"We are pleased to announce that this summer, I2P will be embarking on a\n"
+"development program aimed at improving the privacy software ecosystem. "
+"Our goal\n"
+"is to make life easier both for developers wanting to leverage I2P in "
+"their\n"
+"applications, and for users trying to configure and run their apps "
+"through I2P."
+msgstr ""
+
+#: i2p2www/blog/2016/06/01/I2P-Summer-Dev.rst:47
+msgid "We will be focusing our time this summer into three complementary areas:"
+msgstr ""
+
+#: i2p2www/blog/2016/06/01/I2P-Summer-Dev.rst:51
+msgid ""
+"June: APIs\n"
+"----------"
+msgstr ""
+
+#: i2p2www/blog/2016/06/01/I2P-Summer-Dev.rst:56
+msgid ""
+"In June, we will be updating the various libraries that exist for "
+"interfacing\n"
+"with I2P. We have made significant progress this year on extending our "
+"SAM_ API\n"
+"with additional features, such as support for datagrams and ports. We "
+"plan to\n"
+"make these features easily accessible in our C++ and Python libraries."
+msgstr ""
+
+#: i2p2www/blog/2016/06/01/I2P-Summer-Dev.rst:63
+msgid ""
+"We will also soon be making it much easier for Java and Android "
+"developers to\n"
+"add I2P support to their applications. Stay tuned!"
+msgstr ""
+
+#: i2p2www/blog/2016/06/01/I2P-Summer-Dev.rst:70
+msgid ""
+"July: Apps\n"
+"----------"
+msgstr ""
+
+#: i2p2www/blog/2016/06/01/I2P-Summer-Dev.rst:75
+msgid ""
+"In July we will be working with applications that have expressed interest"
+" in\n"
+"adding support for I2P. There are some really neat ideas being developed "
+"in the\n"
+"privacy space right now, and we want to help their communities leverage "
+"over a\n"
+"decade of research and development on peer-to-peer anonymity. Extending "
+"these\n"
+"applications to work natively over I2P is a good step forward for "
+"usability, and\n"
+"in the process will improve how these applications think about and handle"
+" user\n"
+"information."
+msgstr ""
+
+#: i2p2www/blog/2016/06/01/I2P-Summer-Dev.rst:85
+msgid ""
+"August: Plugins\n"
+"---------------"
+msgstr ""
+
+#: i2p2www/blog/2016/06/01/I2P-Summer-Dev.rst:90
+msgid ""
+"Finally, in August we will turn out attention to the apps we bundle "
+"inside I2P,\n"
+"and the wider array of plugins. Some of these are due for some love, to "
+"make\n"
+"them more user-friendly - as well as fix any outstanding bugs! We hope "
+"that\n"
+"longtime I2P supporters will enjoy the outcome of this work."
+msgstr ""
+
+#: i2p2www/blog/2016/06/01/I2P-Summer-Dev.rst:98
+#: i2p2www/blog/2016/07/02/Summer-Dev-roundup-APIs.rst:124
+#: i2p2www/blog/2017/06/01/Summer-Dev-2017-MOAR-Speed.rst:114
+msgid ""
+"Take part in Summer Dev!\n"
+"========================"
+msgstr ""
+
+#: i2p2www/blog/2016/06/01/I2P-Summer-Dev.rst:103
+#: i2p2www/blog/2016/07/02/Summer-Dev-roundup-APIs.rst:129
+msgid ""
+"We have many more ideas for things we'd like to get done in these areas. "
+"If\n"
+"you're interested in hacking on privacy and anonymity software, designing"
+" usable\n"
+"websites or interfaces, or writing guides for users: come and chat with "
+"us on\n"
+"IRC or Twitter! We are always happy to \"see\" new \"faces\" in our "
+"community, both\n"
+"inside and outside I2P. We'll be sending I2P stickers out to all new\n"
+"contributors taking part (or possibly other pending I2P goodies)!"
+msgstr ""
+
+#: i2p2www/blog/2016/06/01/I2P-Summer-Dev.rst:112
+#: i2p2www/blog/2016/07/02/Summer-Dev-roundup-APIs.rst:138
+msgid ""
+"Likewise, if you are an application developer who wants a hand with "
+"integrating\n"
+"I2P, or even just to chat about the concepts or details: get in touch! If"
+" you\n"
+"want to get involved in our July Apps month, contact `@GetI2P`_, `@i2p`_ "
+"or\n"
+"`@str4d`_ on Twitter. You can also find us in #i2p-dev on OFTC or "
+"FreeNode."
+msgstr ""
+
+#: i2p2www/blog/2016/06/01/I2P-Summer-Dev.rst:119
+#: i2p2www/blog/2016/07/02/Summer-Dev-roundup-APIs.rst:145
+#: i2p2www/blog/2017/06/01/Summer-Dev-2017-MOAR-Speed.rst:130
+msgid ""
+"We'll be posting here as we go, but you can also follow our progress, and"
+" share\n"
+"your own ideas and work, with the hashtag `#I2PSummer`_ on Twitter. Bring"
+" on the\n"
+"summer!"
+msgstr ""
+
+#: i2p2www/blog/2016/06/07/0.9.26-Release.rst:1
+msgid ""
+"==============\n"
+"0.9.26 Release\n"
+"=============="
+msgstr ""
+
+#: i2p2www/blog/2016/06/07/0.9.26-Release.rst:10
+msgid ""
+"0.9.26 contains crypto updates, Debian packaging improvements, and bug "
+"fixes"
+msgstr ""
+"0.9.26 buraxılışında kripto yeniliklər, Debian paketi yaxşılaşmaları və "
+"xəta düzəlişləri var."
+
+#: i2p2www/blog/2016/06/07/0.9.26-Release.rst:12
+msgid ""
+"I2P is now a proposed site on Stack Exchange!\n"
+"Please `commit to using it`_ so the beta phase can begin."
+msgstr ""
+
+#: i2p2www/blog/2016/06/07/0.9.26-Release.rst:17
+msgid "`commit to using it`"
+msgstr ""
+
+#: i2p2www/blog/2016/06/07/0.9.26-Release.rst:24
+msgid ""
+"0.9.26 contains a major upgrade to our native crypto library,\n"
+"a new addressbook subscription protocol with signatures,\n"
+"and major improvements to the Debian/Ubuntu packaging."
+msgstr ""
+"0.9.26 buraxılışında doğma kripto kitabxanaya böyük yeniləmələr,\n"
+"imzalarla birgə yeni ünvan kitabına abunəlik protokolu,\n"
+"Debian/Ubuntu paketləri üçün böyük dəyişikliklər yer alıb."
+
+#: i2p2www/blog/2016/06/07/0.9.26-Release.rst:30
+msgid ""
+"For crypto, we have upgraded to GMP 6.0.0, and added support for newer "
+"processors,\n"
+"which will speed up crypto operations considerably.\n"
+"Also, we are now using constant-time GMP functions to prevent side-"
+"channel attacks.\n"
+"For caution, the GMP changes are enabled for new installs and "
+"Debian/Ubuntu builds only;\n"
+"we will include them for in-net updates in the 0.9.27 release."
+msgstr ""
+"Kriptoqrafiya GMP 6.0.0 buraxılışına yüksəldildi və kriptoqrafiya "
+"sürətini əhəmiyyətli dərəcədə artıracaq daha yeni prosessorlara dəstəyi "
+"əlavə etdik.\n"
+"Bundan əlavə yan kanal hücumlarının qarşısını almaq üçün sabit zamanlı "
+"GMP funksiyalarından istifadə edirik.\n"
+"Diqqətli olun,  GMP dəyişiklikləri yeni quraşdırmalar  və Debian / Ubuntu"
+" quruluşları üçün aktivdir;\n"
+"biz bunları 0.9.27 buraxılışının şəbəkəiçi yeniləmələrinə əlavə edəcəyik."
+
+#: i2p2www/blog/2016/06/07/0.9.26-Release.rst:38
+msgid ""
+"For Debian/Ubuntu builds, we have added dependencies on several packages,"
+"\n"
+"including Jetty 8 and geoip, and removed the equivalent bundled code."
+msgstr ""
+"Debian/Ubuntu qurumları üçün Jetty 8 ve geoip kimi bəzi paket "
+"asılılıqları əlavə olundu və \n"
+"ekvivalent kodlar aradan qaldırıldı. "
+
+#: i2p2www/blog/2016/06/07/0.9.26-Release.rst:43
+msgid ""
+"There's a collection of bug fixes also, including a fix for a timer bug\n"
+"that caused instability and performance degradations over time."
+msgstr ""
+
+#: i2p2www/blog/2016/06/07/0.9.26-Release.rst:58
+msgid ""
+"GMP 6.0.0 and jbigi/jcpuid native libraries, enabling significant "
+"speedups on newer architectures, and constant-time crypto operations  "
+"(new installs and Debian/Ubuntu builds only, will include in the updates "
+"in the next release, 0.9.27)"
+msgstr ""
+
+#: i2p2www/blog/2016/06/07/0.9.26-Release.rst:59
+msgid "Addressbook subscription protocol, enabling signed addressbook updates"
+msgstr ""
+
+#: i2p2www/blog/2016/06/07/0.9.26-Release.rst:60
+msgid "Generate signed authentication strings for subscriptions in i2ptunnel"
+msgstr ""
+
+#: i2p2www/blog/2016/06/07/0.9.26-Release.rst:61
+msgid ""
+"Enhance hosts blockfile format to allow for multiple destinations per "
+"entry"
+msgstr ""
+
+#: i2p2www/blog/2016/06/07/0.9.26-Release.rst:62
+msgid "Use system GeoIP database when available"
+msgstr ""
+
+#: i2p2www/blog/2016/06/07/0.9.26-Release.rst:63
+msgid ""
+"Remove systray4j.jar from non-Windows installers and Debian/Ubuntu "
+"packages"
+msgstr ""
+
+#: i2p2www/blog/2016/06/07/0.9.26-Release.rst:64
+msgid ""
+"Remove multiple external libraries from Debian/Ubuntu builds, and add "
+"dependencies on: geoip-database, gettext-base, libgetopt-java, "
+"libjetty8-java, libservlet3.0-java, glassfish-javaee"
+msgstr ""
+
+#: i2p2www/blog/2016/06/07/0.9.26-Release.rst:65
+msgid ""
+"Store CRLs received in the news feed, to distribute key revocations when "
+"necessary"
+msgstr ""
+
+#: i2p2www/blog/2016/06/07/0.9.26-Release.rst:66
+msgid ""
+"Enhancements to the desktopgui system tray feature, to be enabled by "
+"default in next release"
+msgstr ""
+
+#: i2p2www/blog/2016/06/07/0.9.26-Release.rst:67
+msgid "Wrapper 3.5.29 (new non-Windows installs only)"
+msgstr ""
+
+#: i2p2www/blog/2016/06/07/0.9.26-Release.rst:73
+msgid ""
+"Fix periodic timers not firing after a backwards OS clock shift, which "
+"caused widespread instability and gradual deterioration"
+msgstr ""
+
+#: i2p2www/blog/2016/06/07/0.9.26-Release.rst:74
+msgid ""
+"Fix wrapper on FreeBSD 10 (new installs only, see ticket #1118 for manual"
+" fix)"
+msgstr ""
+
+#: i2p2www/blog/2016/06/07/0.9.26-Release.rst:75
+msgid "Fix NPE on hostname lookup failure in SOCKS 4a"
+msgstr ""
+
+#: i2p2www/blog/2016/06/07/0.9.26-Release.rst:76
+msgid ""
+"Fix setting JAVA_HOME on Mac OS X (new installs only, see ticket #1783 "
+"for manual fix)"
+msgstr ""
+
+#: i2p2www/blog/2016/06/07/0.9.26-Release.rst:77
+msgid "Fix UTF-8 console passwords, and partial fix for usernames"
+msgstr ""
+
+#: i2p2www/blog/2016/06/07/0.9.26-Release.rst:78
+msgid "Fix router family configuration form"
+msgstr ""
+
+#: i2p2www/blog/2016/06/07/0.9.26-Release.rst:79
+msgid "Fix NTP sending random data in some fields that should be zero"
+msgstr ""
+
+#: i2p2www/blog/2016/06/07/0.9.26-Release.rst:85
+msgid "More verification of received NTP packets"
+msgstr ""
+
+#: i2p2www/blog/2016/06/07/0.9.26-Release.rst:86
+msgid ""
+"Rework resource bundle generation for 20x speedup in build time (requires"
+" gettext version 0.19)"
+msgstr ""
+
+#: i2p2www/blog/2016/06/13/I2P-on-Maven-Central.rst:1
+msgid ""
+"====================\n"
+"I2P on Maven Central\n"
+"===================="
+msgstr ""
+
+#: i2p2www/blog/2016/06/13/I2P-on-Maven-Central.rst:10
+msgid "The I2P client libraries are now available on Maven Central!"
+msgstr ""
+
+#: i2p2www/blog/2016/06/13/I2P-on-Maven-Central.rst:12
+msgid ""
+"We're nearly half-way into the APIs month of Summer Dev, and making great"
+"\n"
+"progress on a number of fronts. I'm happy to announce that the first of "
+"these is\n"
+"complete: the I2P client libraries are now available on Maven Central!"
+msgstr ""
+
+#: i2p2www/blog/2016/06/13/I2P-on-Maven-Central.rst:18
+#: i2p2www/blog/2016/07/02/Summer-Dev-roundup-APIs.rst:47
+msgid ""
+"This should make it much simpler for Java developers to use I2P in their\n"
+"applications. Instead of needing to obtain the libraries from a current "
+"install,\n"
+"they can simply add I2P to their dependencies. Upgrading to new versions "
+"will\n"
+"similarly be much easier."
+msgstr ""
+
+#: i2p2www/blog/2016/06/13/I2P-on-Maven-Central.rst:26
+msgid ""
+"How to use them\n"
+"==============="
+msgstr ""
+
+#: i2p2www/blog/2016/06/13/I2P-on-Maven-Central.rst:31
+msgid "There are two libraries that you need to know about:"
+msgstr ""
+
+#: i2p2www/blog/2016/06/13/I2P-on-Maven-Central.rst:35
+msgid "The core I2P APIs; you can use these to send individual datagrams."
+msgstr ""
+
+#: i2p2www/blog/2016/06/13/I2P-on-Maven-Central.rst:36
+msgid "A TCP-like set of sockets for communicating over I2P."
+msgstr ""
+
+#: i2p2www/blog/2016/06/13/I2P-on-Maven-Central.rst:38
+msgid ""
+"Add one or both of these to your project's dependencies, and you're good "
+"to go!"
+msgstr ""
+
+#: i2p2www/blog/2016/06/13/I2P-on-Maven-Central.rst:66
+msgid ""
+"For other build systems, see the Maven Central pages for the `core`_ and\n"
+"`streaming`_ libraries."
+msgstr ""
+
+#: i2p2www/blog/2016/06/13/I2P-on-Maven-Central.rst:71
+msgid ""
+"Android developers should use the `I2P Android client library`_, which "
+"contains\n"
+"the same libraries along with Android-specific helpers. I'll be updating "
+"it soon\n"
+"to depend on the new I2P libraries, so that cross-platform applications "
+"can work\n"
+"natively with either I2P Android or desktop I2P."
+msgstr ""
+
+#: i2p2www/blog/2016/06/13/I2P-on-Maven-Central.rst:80
+#: i2p2www/blog/2016/07/02/Summer-Dev-roundup-APIs.rst:62
+msgid "`I2P Android client library`"
+msgstr ""
+
+#: i2p2www/blog/2016/06/13/I2P-on-Maven-Central.rst:83
+msgid ""
+"Get hacking!\n"
+"============"
+msgstr ""
+
+#: i2p2www/blog/2016/06/13/I2P-on-Maven-Central.rst:88
+msgid ""
+"See our `application development`_ guide for help getting started with "
+"these\n"
+"libraries. You can also chat with us about them in #i2p-dev on IRC. And "
+"if you\n"
+"do start using them, let us know what you're working on with the hashtag\n"
+"`#I2PSummer`_ on Twitter!"
+msgstr ""
+
+#: i2p2www/blog/2016/06/13/I2P-on-Maven-Central.rst:95
+msgid "application development"
+msgstr ""
+
+#: i2p2www/blog/2016/07/02/Summer-Dev-roundup-APIs.rst:1
+msgid ""
+"========================\n"
+"Summer Dev roundup: APIs\n"
+"========================"
+msgstr ""
+
+#: i2p2www/blog/2016/07/02/Summer-Dev-roundup-APIs.rst:10
+msgid ""
+"In the first month of Summer Dev, we have improved the usability of our "
+"APIs for Java, Android, and Python developers."
+msgstr ""
+
+#: i2p2www/blog/2016/07/02/Summer-Dev-roundup-APIs.rst:12
+msgid ""
+"Summer Dev is in full swing: we've been busy greasing wheels, sanding "
+"edges, and\n"
+"tidying the place up. Now it's time for our first roundup, where we bring"
+" you up\n"
+"to speed on the progress we are making!"
+msgstr ""
+
+#: i2p2www/blog/2016/07/02/Summer-Dev-roundup-APIs.rst:18
+msgid ""
+"\n"
+"But first, a big thank you to `Elio Qoshi`_ and `ura`_ for designing us "
+"the\n"
+"fantastic logo you see above. It adds a cheerful personality to our "
+"development\n"
+"program (and is going to look great on t-shirts)."
+msgstr ""
+
+#: i2p2www/blog/2016/07/02/Summer-Dev-roundup-APIs.rst:27
+msgid ""
+"APIs month\n"
+"=========="
+msgstr ""
+
+#: i2p2www/blog/2016/07/02/Summer-Dev-roundup-APIs.rst:32
+msgid ""
+"Our goal for this month was to \"blend in\" - to make our APIs and "
+"libraries work\n"
+"within the existing infrastructure of various communities, so that "
+"application\n"
+"developers can work with I2P more efficiently, and users don't need to "
+"worry\n"
+"about the details."
+msgstr ""
+
+#: i2p2www/blog/2016/07/02/Summer-Dev-roundup-APIs.rst:42
+msgid ""
+"The I2P client libraries are now available on `Maven Central`_! See our\n"
+"`previous blog post`_ for full details.\n"
+msgstr ""
+
+#: i2p2www/blog/2016/07/02/Summer-Dev-roundup-APIs.rst:54
+msgid ""
+"The `I2P Android client library`_ has also been updated to use the new "
+"I2P\n"
+"libraries. This means that cross-platform applications can work natively "
+"with\n"
+"either I2P Android or desktop I2P."
+msgstr ""
+
+#: i2p2www/blog/2016/07/02/Summer-Dev-roundup-APIs.rst:61
+msgid "`previous blog post`"
+msgstr ""
+
+#: i2p2www/blog/2016/07/02/Summer-Dev-roundup-APIs.rst:69
+msgid ""
+"The `Twisted`_ plugin ``txi2p`` now supports in-I2P ports, and will work\n"
+"seamlessly over local, remote, and port-forwarded `SAM APIs`_. See its\n"
+"`documentation`_ for usage instructions, and report any issues on "
+"`GitHub`_."
+msgstr ""
+
+#: i2p2www/blog/2016/07/02/Summer-Dev-roundup-APIs.rst:77
+msgid ""
+"The first (beta) version of ``i2psocket`` has been released! This is a "
+"direct\n"
+"replacement for the standard Python ``socket`` library that extends it "
+"with I2P\n"
+"support over the `SAM API`_. See its `GitHub page`_ for usage "
+"instructions, and\n"
+"to report any issues."
+msgstr ""
+
+#: i2p2www/blog/2016/07/02/Summer-Dev-roundup-APIs.rst:87
+msgid "`documentation`"
+msgstr ""
+
+#: i2p2www/blog/2016/07/02/Summer-Dev-roundup-APIs.rst:89
+msgid "`GitHub page`"
+msgstr ""
+
+#: i2p2www/blog/2016/07/02/Summer-Dev-roundup-APIs.rst:91
+msgid ""
+"Other progress\n"
+"--------------"
+msgstr ""
+
+#: i2p2www/blog/2016/07/02/Summer-Dev-roundup-APIs.rst:96
+msgid ""
+"zzz has been hard at work on Syndie, getting a headstart on Plugins "
+"month. You can follow his progress on `the development forum thread`_."
+msgstr ""
+
+#: i2p2www/blog/2016/07/02/Summer-Dev-roundup-APIs.rst:98
+msgid ""
+"psi has been creating an I2P test network using i2pd, and in the process "
+"has found and fixed several i2pd bugs that will improve its compatibility"
+" with Java I2P."
+msgstr ""
+
+#: i2p2www/blog/2016/07/02/Summer-Dev-roundup-APIs.rst:100
+msgid "`the development forum thread`"
+msgstr ""
+
+#: i2p2www/blog/2016/07/02/Summer-Dev-roundup-APIs.rst:102
+msgid ""
+"Coming up: Apps month!\n"
+"======================"
+msgstr ""
+
+#: i2p2www/blog/2016/07/02/Summer-Dev-roundup-APIs.rst:107
+msgid ""
+"We are excited to be working with `Tahoe-LAFS`_ in July! I2P has for a "
+"long time\n"
+"been home to one of the `largest public grids`_, using a patched version "
+"of\n"
+"Tahoe-LAFS. During Apps month we will be helping them with their ongoing "
+"work to\n"
+"add native support for I2P and Tor, so that I2P users can benefit from "
+"all of\n"
+"the improvements upstream."
+msgstr ""
+
+#: i2p2www/blog/2016/07/02/Summer-Dev-roundup-APIs.rst:115
+msgid ""
+"There are several other projects that we will be talking with about their"
+" plans\n"
+"for I2P integration, and helping with design. Stay tuned!"
+msgstr ""
+
+#: i2p2www/blog/2016/07/02/Summer-Dev-roundup-APIs.rst:121
+msgid "`largest public grids`"
+msgstr ""
+
+#: i2p2www/blog/2016/10/17/0.9.27-Release.rst:1
+msgid ""
+"==============\n"
+"0.9.27 Release\n"
+"=============="
+msgstr ""
+
+#: i2p2www/blog/2016/10/17/0.9.27-Release.rst:10
+msgid "0.9.27 contains bug fixes"
+msgstr "0.9.27 xəta düzəlişləri var"
+
+#: i2p2www/blog/2016/10/17/0.9.27-Release.rst:17
+msgid ""
+"0.9.27 contains a number of bug fixes.\n"
+"The updated GMP library for crypto acceleration, which was bundled in the"
+" 0.9.26 release for new installs and Debian builds only, is now included "
+"in the in-network update for 0.9.27.\n"
+"There are improvements in IPv6 transports, SSU peer testing, and hidden "
+"mode."
+msgstr ""
+"0.9.27 buraxılışında müxtəlif xəta düzəlişləri var. \n"
+"Şifrələməni sürətləndirmək üçün yenilənən və 0.9.26 buraxılışında yalnız "
+"yeni Debian quruluşları üçün əlavə olunan GMP kitapxanası indi şəbəkə "
+"yenilənmələrinə əlavə edildi. \n"
+"IPv6 nəqliyyatı, SSU peer sınağı və gizli rejim məsələlərində yaxşılaşma "
+"var. "
+
+#: i2p2www/blog/2016/10/17/0.9.27-Release.rst:23
+msgid ""
+"We updated a number of plugins during I2P Summer and your router will "
+"automatically update them after restart."
+msgstr ""
+
+#: i2p2www/blog/2016/10/17/0.9.27-Release.rst:37
+msgid "GMP 6 (in-net updates)"
+msgstr ""
+
+#: i2p2www/blog/2016/10/17/0.9.27-Release.rst:38
+msgid "SSU Peer Testing for IPv6"
+msgstr ""
+
+#: i2p2www/blog/2016/10/17/0.9.27-Release.rst:39
+msgid "Add outproxy plugin support for SOCKS"
+msgstr ""
+
+#: i2p2www/blog/2016/10/17/0.9.27-Release.rst:40
+msgid "Enable desktop GUI (tray icon) on Windows"
+msgstr ""
+
+#: i2p2www/blog/2016/10/17/0.9.27-Release.rst:45
+msgid "Fix reported GMP version when jbigi built as a shared library"
+msgstr ""
+
+#: i2p2www/blog/2016/10/17/0.9.27-Release.rst:46
+msgid "Fix SSU peer test happening too frequently"
+msgstr ""
+
+#: i2p2www/blog/2016/10/17/0.9.27-Release.rst:47
+msgid "Fix SSU peer test not terminating properly in some cases"
+msgstr ""
+
+#: i2p2www/blog/2016/10/17/0.9.27-Release.rst:48
+msgid "Fix bote plugin not working in Debian/Ubuntu builds"
+msgstr ""
+
+#: i2p2www/blog/2016/10/17/0.9.27-Release.rst:49
+msgid "Fix rare UPnP NPE when viewing /peers"
+msgstr ""
+
+#: i2p2www/blog/2016/10/17/0.9.27-Release.rst:50
+msgid "Fix standalone i2psnark build and configuration"
+msgstr ""
+
+#: i2p2www/blog/2016/10/17/0.9.27-Release.rst:51
+msgid "Hidden mode improvements: Enable tunnel testing and use fast peers"
+msgstr ""
+
+#: i2p2www/blog/2016/10/17/0.9.27-Release.rst:52
+msgid "Fix possible CSRF in SusiMail"
+msgstr ""
+
+#: i2p2www/blog/2016/10/17/0.9.27-Release.rst:53
+msgid "Fix i2psnark exception on bad configured announce URL"
+msgstr ""
+
+#: i2p2www/blog/2016/10/17/0.9.27-Release.rst:54
+msgid "Fix layout issues on i2ptunnel registration page"
+msgstr ""
+
+#: i2p2www/blog/2016/10/17/0.9.27-Release.rst:55
+msgid "Fix streaming accept() hang when session disconnects"
+msgstr ""
+
+#: i2p2www/blog/2016/10/17/0.9.27-Release.rst:60
+msgid "Split up the large /configclients web page into several"
+msgstr ""
+
+#: i2p2www/blog/2016/10/17/0.9.27-Release.rst:61
+msgid "Add links to view complete router and wrapper log files"
+msgstr ""
+
+#: i2p2www/blog/2016/10/17/0.9.27-Release.rst:62
+msgid "Block 'Proxy' header in i2ptunnel (HTTPoxy)"
+msgstr ""
+
+#: i2p2www/blog/2016/10/17/0.9.27-Release.rst:63
+msgid "Recognize Kaby Lake CPUIDs"
+msgstr ""
+
+#: i2p2www/blog/2016/12/12/0.9.28-Release.rst:1
+msgid ""
+"==============\n"
+"0.9.28 Release\n"
+"=============="
+msgstr ""
+
+#: i2p2www/blog/2016/12/12/0.9.28-Release.rst:10
+msgid "0.9.28 contains bug fixes"
+msgstr "0.9.28 xəta düzəlişləri var"
+
+#: i2p2www/blog/2016/12/12/0.9.28-Release.rst:17
+msgid ""
+"0.9.28 contains fixes for over 25 Trac tickets, and updates for a number "
+"of bundled software packages including Jetty.\n"
+"There are fixes for the IPv6 peer testing feature introduced last "
+"release.\n"
+"We continue improvements to detect and block peers that are potentially "
+"malicious.\n"
+"There are preliminary fixes for Java 9, although we do not yet recommend "
+"Java 9 for general use."
+msgstr ""
+"0.9.28 25-dən artıq Trac biletinə düzəlişlərdən və Jetty də daxil "
+"olmaqla, bir sıra paket proqram üçün yeniliklərdən ibarətdir. \n"
+"Son buraxılışda IPv6 peer testi xüsusiyyətləri üçün düzəlişlər var. \n"
+"Biz potensial zərərli peer-lərin aşkarlanaraq, bloklanması üçün "
+"təkmilləşdirmələrə davam edirik.\n"
+"Java 9 üçün ilkin düzəlişlər var, hərçənd onu hələlik ümumi istifadə üçün"
+" məsləhət görmürük. "
+
+#: i2p2www/blog/2016/12/12/0.9.28-Release.rst:24
+msgid ""
+"I2P will be at 33C3, please stop by our table and give us your ideas on "
+"how to improve the network.\n"
+"We will review our 2017 roadmap and priorities 2017 at the Congress."
+msgstr ""
+"I2P 33C3-də iştirak edəcək, xahiş edirik masamızdan yan keçməyin və "
+"şəbəkənin inkişafı ilə əlaqədar fikirlərinizi bölüşün. \n"
+"Konqresdə 2017-ci ilin yol xəritəsini və prioritetləri nəzərdən "
+"keçirəcəyik."
+
+#: i2p2www/blog/2016/12/12/0.9.28-Release.rst:49
+msgid "Fix version test for SSU IPv6 peer testing"
+msgstr ""
+
+#: i2p2www/blog/2016/12/12/0.9.28-Release.rst:50
+msgid "Fix generation of keys for SSL console"
+msgstr ""
+
+#: i2p2www/blog/2016/12/12/0.9.28-Release.rst:51
+msgid "Fix uploader limit in i2psnark"
+msgstr ""
+
+#: i2p2www/blog/2016/12/12/0.9.28-Release.rst:52
+msgid "Fix susimail nonce error on login after logout"
+msgstr ""
+
+#: i2p2www/blog/2016/12/12/0.9.28-Release.rst:53
+msgid "Fixes for Java 9"
+msgstr ""
+
+#: i2p2www/blog/2016/12/12/0.9.28-Release.rst:59
+msgid "Allow Java 9 in packages"
+msgstr ""
+
+#: i2p2www/blog/2016/12/12/0.9.28-Release.rst:60
+msgid "Add warning for Java 9, not yet recommended"
+msgstr ""
+
+#: i2p2www/blog/2016/12/12/0.9.28-Release.rst:61
+msgid "Preliminary fixes for use with Tomcat 8"
+msgstr ""
+
+#: i2p2www/blog/2016/12/12/0.9.28-Release.rst:62
+msgid "Improved self-signed certificates"
+msgstr ""
+
+#: i2p2www/blog/2016/12/12/0.9.28-Release.rst:63
+msgid "Increase max IPv6 MTU (proposal #127)"
+msgstr ""
+
+#: i2p2www/blog/2016/12/12/0.9.28-Release.rst:64
+msgid "Caching of serialized leasesets"
+msgstr ""
+
+#: i2p2www/blog/2016/12/12/0.9.28-Release.rst:65
+msgid "Peer selection updates"
+msgstr ""
+
+#: i2p2www/blog/2016/12/12/0.9.28-Release.rst:66
+msgid "Restrictions in peer selection for netdb verifies"
+msgstr ""
+
+#: i2p2www/blog/2016/12/12/0.9.28-Release.rst:67
+msgid "New advanced netdb search form"
+msgstr ""
+
+#: i2p2www/blog/2016/12/12/0.9.28-Release.rst:68
+msgid "Sybil tool enhancements"
+msgstr ""
+
+#: i2p2www/blog/2016/12/12/0.9.28-Release.rst:69
+msgid "Blocklist updates in news feed"
+msgstr ""
+
+#: i2p2www/blog/2016/12/12/0.9.28-Release.rst:70
+msgid "Support IPv6 in blocklist"
+msgstr ""
+
+#: i2p2www/blog/2016/12/12/0.9.28-Release.rst:71
+msgid "Add Java version to jar manifests"
+msgstr ""
+
+#: i2p2www/blog/2016/12/12/0.9.28-Release.rst:72
+msgid "Remove dead console home page links"
+msgstr ""
+
+#: i2p2www/blog/2016/12/12/0.9.28-Release.rst:73
+msgid "Add initial news to bottom of full news page"
+msgstr ""
+
+#: i2p2www/blog/2016/12/12/0.9.28-Release.rst:74
+msgid "Fix periodic re-logging of dup log messages"
+msgstr ""
+
+#: i2p2www/blog/2016/12/12/0.9.28-Release.rst:75
+msgid "Periodic saving of profiles and i2psnark DHT nodes"
+msgstr ""
+
+#: i2p2www/blog/2016/12/12/0.9.28-Release.rst:76
+msgid "Catch rare UPnP exceptions"
+msgstr ""
+
+#: i2p2www/blog/2016/12/12/0.9.28-Release.rst:77
+msgid "Add logout button to more susimail pages"
+msgstr ""
+
+#: i2p2www/blog/2016/12/12/0.9.28-Release.rst:78
+msgid "Truncate history.txt in installers"
+msgstr ""
+
+#: i2p2www/blog/2016/12/12/0.9.28-Release.rst:79
+msgid "Use NTCP even before SSU minimums are met or SSU is broken"
+msgstr ""
+
+#: i2p2www/blog/2016/12/12/0.9.28-Release.rst:80
+msgid "Reduce default tunnel build records to 4"
+msgstr ""
+
+#: i2p2www/blog/2016/12/12/0.9.28-Release.rst:81
+msgid "Improved IPv6 address selection"
+msgstr ""
+
+#: i2p2www/blog/2016/12/12/0.9.28-Release.rst:82
+msgid "Add force-firewalled IPv6 setting"
+msgstr ""
+
+#: i2p2www/blog/2016/12/12/0.9.28-Release.rst:83
+msgid "Improved handling of webapps that fail to start"
+msgstr ""
+
+#: i2p2www/blog/2016/12/12/0.9.28-Release.rst:84
+msgid "New configuration for test networks"
+msgstr ""
+
+#: i2p2www/blog/2016/12/12/0.9.28-Release.rst:85
+msgid "Remove deprecated Sha256Standalone, Syndie 1.105 must upgrade"
+msgstr ""
+
+#: i2p2www/blog/2016/12/12/0.9.28-Release.rst:86
+msgid "Actually use a random nonzero byte in ElGamal, as specified"
+msgstr ""
+
+#: i2p2www/blog/2016/12/12/0.9.28-Release.rst:87
+msgid "Disallow RSA for netdb entries"
+msgstr ""
+
+#: i2p2www/blog/2016/12/12/0.9.28-Release.rst:88
+msgid "Add library jars to jar classpath for Debian builds"
+msgstr ""
+
+#: i2p2www/blog/2016/12/12/0.9.28-Release.rst:89
+msgid "Remove old systray code"
+msgstr ""
+
+#: i2p2www/blog/2016/12/12/0.9.28-Release.rst:90
+msgid "Fix low-memory warnings without wrapper"
+msgstr ""
+
+#: i2p2www/blog/2016/12/12/0.9.28-Release.rst:91
+msgid "Various code consolidation and cleanup"
+msgstr ""
+
+#: i2p2www/blog/2016/12/12/0.9.28-Release.rst:92
+msgid "New translations: Galician, Korean"
+msgstr ""
+
+#: i2p2www/blog/2016/12/12/0.9.28-Release.rst:93
+msgid "New translations for some subsytems: Chinese (Taiwan)"
+msgstr ""
+
+#: i2p2www/blog/2017/02/27/0.9.29-Release.rst:1
+msgid ""
+"==============\n"
+"0.9.29 Release\n"
+"=============="
+msgstr ""
+
+#: i2p2www/blog/2017/02/27/0.9.29-Release.rst:10
+msgid "0.9.29 contains bug fixes"
+msgstr "0.9.29 xəta düzəlişləri var"
+
+#: i2p2www/blog/2017/02/27/0.9.29-Release.rst:17
+msgid ""
+"0.9.29 contains fixes for numerous Trac tickets, including workarounds "
+"for corrupt compressed messages.\n"
+"We now support NTP over IPv6.\n"
+"We've added preliminary Docker support.\n"
+"We now have translated man pages.\n"
+"We now pass same-origin Referer headers through the HTTP proxy.\n"
+"There are more fixes for Java 9, although we do not yet recommend Java 9 "
+"for general use."
+msgstr ""
+"0.9.29 çoxsaylı Trac biletlərinə, təhrif olunmuş sıxılmış mesajlar üçün "
+"həllər də daxil olmaqla, düzəlişləri ehtiva edir.\n"
+"Biz artıq IPv6 üzərindən NTP-ni dəstəkləyirik.\n"
+"İlkin Docker dəstəyini əlavə etdik.\n"
+"İndi soraq səhifələrini tərcümə etdik.\n"
+"İndi biz eyni Referer başlıqlarını HTTP proxy vasitəsilə ötürürük.\n"
+"Java 9 üçün daha çox düzəliş var, baxmayaraq ki, biz hələ də ümumi "
+"istifadə üçün Java 9-u məsləhət görmürük.\n"
+
+#: i2p2www/blog/2017/02/27/0.9.29-Release.rst:36
+msgid "BOB database refactor"
+msgstr ""
+
+#: i2p2www/blog/2017/02/27/0.9.29-Release.rst:37
+msgid "Fixes for Java 9, still not recommended for general use"
+msgstr ""
+
+#: i2p2www/blog/2017/02/27/0.9.29-Release.rst:38
+msgid "NTP fixes for security and standards"
+msgstr ""
+
+#: i2p2www/blog/2017/02/27/0.9.29-Release.rst:39
+msgid "NTP IPv6 support"
+msgstr ""
+
+#: i2p2www/blog/2017/02/27/0.9.29-Release.rst:40
+msgid "Don't display very old news in console"
+msgstr ""
+
+#: i2p2www/blog/2017/02/27/0.9.29-Release.rst:41
+msgid "Blocklist checking improvements"
+msgstr ""
+
+#: i2p2www/blog/2017/02/27/0.9.29-Release.rst:42
+msgid "Add preliminary Docker support"
+msgstr ""
+
+#: i2p2www/blog/2017/02/27/0.9.29-Release.rst:43
+msgid "Add Referrer-Policy headers to console"
+msgstr ""
+
+#: i2p2www/blog/2017/02/27/0.9.29-Release.rst:44
+msgid "Pass same-origin Referer headers through proxy"
+msgstr ""
+
+#: i2p2www/blog/2017/02/27/0.9.29-Release.rst:45
+msgid "Translated man pages"
+msgstr ""
+
+#: i2p2www/blog/2017/02/27/0.9.29-Release.rst:50
+msgid "Add support for outproxy plugin to CONNECT proxy"
+msgstr ""
+
+#: i2p2www/blog/2017/02/27/0.9.29-Release.rst:51
+msgid "Replace random tunnel keys when rekeying"
+msgstr ""
+
+#: i2p2www/blog/2017/02/27/0.9.29-Release.rst:52
+msgid "Fix streaming optional delay and choking"
+msgstr ""
+
+#: i2p2www/blog/2017/02/27/0.9.29-Release.rst:53
+msgid "Don't hard fail on message expired error in streaming"
+msgstr ""
+
+#: i2p2www/blog/2017/02/27/0.9.29-Release.rst:54
+msgid "Fix javadoc errors"
+msgstr ""
+
+#: i2p2www/blog/2017/02/27/0.9.29-Release.rst:55
+msgid "Fix broken unit tests"
+msgstr ""
+
+#: i2p2www/blog/2017/02/27/0.9.29-Release.rst:56
+msgid "Ensure i2psnark finishes writing config files at shutdown"
+msgstr ""
+
+#: i2p2www/blog/2017/02/27/0.9.29-Release.rst:57
+msgid "Fix rare NPE in AES via NTCP"
+msgstr ""
+
+#: i2p2www/blog/2017/02/27/0.9.29-Release.rst:58
+msgid "Disable caching of compressors, in an attempt to fix corruption"
+msgstr ""
+
+#: i2p2www/blog/2017/02/27/0.9.29-Release.rst:59
+msgid "Don't close SAM or BOB session on receipt of corrupt compressed data"
+msgstr ""
+
+#: i2p2www/blog/2017/02/27/0.9.29-Release.rst:64
+msgid "Add support for ports to CONNECT proxy"
+msgstr ""
+
+#: i2p2www/blog/2017/02/27/0.9.29-Release.rst:65
+msgid "Consolidate stream copy code"
+msgstr ""
+
+#: i2p2www/blog/2017/02/27/0.9.29-Release.rst:66
+msgid "Consolidate console timer threads"
+msgstr ""
+
+#: i2p2www/blog/2017/02/27/0.9.29-Release.rst:67
+msgid "New streaming test harness"
+msgstr ""
+
+#: i2p2www/blog/2017/03/04/0.9.29-Windows-Installer-Fix.rst:1
+msgid ""
+"============================\n"
+"0.9.29 Windows Installer Fix\n"
+"============================"
+msgstr ""
+
+#: i2p2www/blog/2017/03/04/0.9.29-Windows-Installer-Fix.rst:10
+msgid "0.9.29 Windows installer fix"
+msgstr ""
+
+#: i2p2www/blog/2017/03/04/0.9.29-Windows-Installer-Fix.rst:17
+msgid ""
+"The 0.9.29 Windows installer posted on our website two days ago fails "
+"during install with an Exception.\n"
+"We have fixed the bug and posted the new installer to our website.\n"
+"This does not affect upgrades from previous releases or non-Windows "
+"installers.\n"
+"We apologize for the issue."
+msgstr ""
+
+#: i2p2www/blog/2017/05/03/0.9.30-Release.rst:1
+msgid ""
+"==============\n"
+"0.9.30 Release\n"
+"=============="
+msgstr ""
+
+#: i2p2www/blog/2017/05/03/0.9.30-Release.rst:10
+msgid "0.9.30 with Jetty 9"
+msgstr ""
+
+#: i2p2www/blog/2017/05/03/0.9.30-Release.rst:17
+msgid ""
+"0.9.30 contains an upgrade to Jetty 9 and Tomcat 8.\n"
+"The previous versions are no longer supported, and are not available in "
+"the upcoming Debian Stretch and Ubuntu Zesty releases."
+msgstr ""
+
+#: i2p2www/blog/2017/05/03/0.9.30-Release.rst:22
+msgid ""
+"The router will migrate the jetty.xml configuration file for each Jetty "
+"website to the new Jetty 9 setup.\n"
+"This should work for recent, unmodified configurations but may not work "
+"for modified or very old setups.\n"
+"Verify that your Jetty website works after upgrading, and contact us on "
+"IRC if you need assistance."
+msgstr ""
+
+#: i2p2www/blog/2017/05/03/0.9.30-Release.rst:28
+msgid ""
+"Several plugins are not compatible with Jetty 9 and must be updated.\n"
+"The following plugins have been updated to work with 0.9.30, and your "
+"router should update them after restart:"
+msgstr ""
+
+#: i2p2www/blog/2017/05/03/0.9.30-Release.rst:34
+msgid ""
+"The following plugins (with current versions listed) will not work with "
+"0.9.30.\n"
+"Contact the appropriate plugin developer for the status of new versions:"
+msgstr ""
+
+#: i2p2www/blog/2017/05/03/0.9.30-Release.rst:40
+msgid ""
+"This release also supports migration of old (2014 and earlier) DSA-SHA1 "
+"hidden services to the more-secure EdDSA signature type.\n"
+"See http://zzz.i2p/topics/2271 for further information, including a guide"
+" and FAQ."
+msgstr ""
+
+#: i2p2www/blog/2017/05/03/0.9.30-Release.rst:45
+msgid ""
+"Note: On non-Android ARM platforms such as the Raspberry Pi, the "
+"blockfile database will upgrade on restart, which may take several "
+"minutes.\n"
+"Please be patient."
+msgstr ""
+"Qeyd: Raspberry Pi kimi qeyri-Android ARM platformalarında blok "
+"verilənlər bazası yenidən başladılanda, bu, bir neçə dəqiqə çəkə bilər.\n"
+"Səbrli olun."
+
+#: i2p2www/blog/2017/05/03/0.9.30-Release.rst:60
+msgid "Jetty 9, Tomcat 8"
+msgstr ""
+
+#: i2p2www/blog/2017/05/03/0.9.30-Release.rst:61
+msgid "Stretch / Zesty support"
+msgstr ""
+
+#: i2p2www/blog/2017/05/03/0.9.30-Release.rst:62
+msgid "Migration support for DSA-SHA1 hidden services"
+msgstr ""
+
+#: i2p2www/blog/2017/05/03/0.9.30-Release.rst:63
+msgid "ARM (non-Android) router signature type migration"
+msgstr ""
+
+#: i2p2www/blog/2017/05/03/0.9.30-Release.rst:64
+msgid "ARM (non-Android) blockfile format migration"
+msgstr ""
+
+#: i2p2www/blog/2017/05/03/0.9.30-Release.rst:65
+msgid "Introducer expiration (proposal 133)"
+msgstr ""
+
+#: i2p2www/blog/2017/05/03/0.9.30-Release.rst:70
+msgid "Fix disappearing i2psnark start button"
+msgstr ""
+
+#: i2p2www/blog/2017/05/03/0.9.30-Release.rst:71
+msgid "Fix saving of libjcpuid.jnilib file on Macs"
+msgstr ""
+
+#: i2p2www/blog/2017/05/03/0.9.30-Release.rst:72
+msgid "Fix fallback to 'none' architecture for jbigi"
+msgstr ""
+
+#: i2p2www/blog/2017/05/03/0.9.30-Release.rst:73
+msgid "Fixes for multiple destinations in SusiDNS"
+msgstr ""
+
+#: i2p2www/blog/2017/05/03/0.9.30-Release.rst:74
+msgid "Fix config directory location in Gentoo"
+msgstr ""
+
+#: i2p2www/blog/2017/05/03/0.9.30-Release.rst:75
+msgid "Fix rapid firewalled/not-firewalled transitions"
+msgstr ""
+
+#: i2p2www/blog/2017/05/03/0.9.30-Release.rst:76
+msgid "Fix startup crash on very old Android platforms"
+msgstr ""
+
+#: i2p2www/blog/2017/05/03/0.9.30-Release.rst:77
+msgid "Fixes for advanced authentication strings in i2ptunnel"
+msgstr ""
+
+#: i2p2www/blog/2017/05/03/0.9.30-Release.rst:78
+msgid "Fix exception caused by corrupt stored i2psnark DHT data"
+msgstr ""
+
+#: i2p2www/blog/2017/05/03/0.9.30-Release.rst:79
+msgid "Speed up writes of i2psnark files at shutdown"
+msgstr ""
+
+#: i2p2www/blog/2017/05/03/0.9.30-Release.rst:84
+msgid "Recognize AMD Ryzen processor"
+msgstr ""
+
+#: i2p2www/blog/2017/05/03/0.9.30-Release.rst:85
+msgid "Support for new i2psnark-rpc remote plugin"
+msgstr ""
+
+#: i2p2www/blog/2017/05/03/0.9.30-Release.rst:86
+msgid "Build addressbook as a jar, not a webapp"
+msgstr ""
+
+#: i2p2www/blog/2017/05/03/0.9.30-Release.rst:87
+msgid "Support client registration in app context"
+msgstr ""
+
+#: i2p2www/blog/2017/05/03/0.9.30-Release.rst:88
+msgid "Add support for i2psnark-rpc plugin"
+msgstr ""
+
+#: i2p2www/blog/2017/05/03/0.9.30-Release.rst:89
+msgid "Adjust thresholds for probabalistic throttling on slow platforms"
+msgstr ""
+
+#: i2p2www/blog/2017/05/03/0.9.30-Release.rst:90
+msgid "Add reset() to I2PSocket API"
+msgstr ""
+
+#: i2p2www/blog/2017/05/03/0.9.30-Release.rst:91
+msgid "Add date parameter to subscription authentication strings"
+msgstr ""
+
+#: i2p2www/blog/2017/05/03/0.9.30-Release.rst:92
+msgid "Add bash completion scripts to Debian packages"
+msgstr ""
+
+#: i2p2www/blog/2017/06/01/Summer-Dev-2017-MOAR-Speed.rst:1
+msgid ""
+"================================\n"
+"I2P Summer Dev 2017: MOAR Speed!\n"
+"================================"
+msgstr ""
+
+#: i2p2www/blog/2017/06/01/Summer-Dev-2017-MOAR-Speed.rst:10
+msgid ""
+"This year's Summer Dev will be focused on metrics collection and "
+"performance improvements for the network."
+msgstr ""
+
+#: i2p2www/blog/2017/06/01/Summer-Dev-2017-MOAR-Speed.rst:12
+msgid ""
+"It's that time of year again! We're embarking on our summer development\n"
+"programme, where we focus on a particular aspect of I2P to push it "
+"forward. For\n"
+"the next three months, we'll be encouraging both new contributors and "
+"existing\n"
+"community members to pick a task and have fun with it!"
+msgstr ""
+
+#: i2p2www/blog/2017/06/01/Summer-Dev-2017-MOAR-Speed.rst:19
+msgid ""
+"`Last year`_, we focused on helping users and developers leverage I2P, by"
+"\n"
+"improving API tooling and giving some love to applications that run over "
+"I2P.\n"
+"This year, we want to improve the user experience by working on an aspect"
+" that\n"
+"affects everyone: performance."
+msgstr ""
+
+#: i2p2www/blog/2017/06/01/Summer-Dev-2017-MOAR-Speed.rst:26
+msgid "`Last year`"
+msgstr ""
+
+#: i2p2www/blog/2017/06/01/Summer-Dev-2017-MOAR-Speed.rst:28
+msgid ""
+"Despite onion-routing networks often being called \"low-latency\" "
+"networks, there\n"
+"is significant overhead created by routing traffic through additional "
+"computers.\n"
+"I2P's unidirectional tunnel design means that by default, a round trip "
+"between\n"
+"two Destinations will involve twelve participants! Improving the "
+"performance of\n"
+"these participants will help to both reduce the latency of end-to-end\n"
+"connections [1]_, and increase the quality of tunnels network-wide."
+msgstr ""
+
+#: i2p2www/blog/2017/06/01/Summer-Dev-2017-MOAR-Speed.rst:37
+msgid ""
+"MOAR speed!\n"
+"==========="
+msgstr ""
+
+#: i2p2www/blog/2017/06/01/Summer-Dev-2017-MOAR-Speed.rst:42
+msgid "Our development programme this year will have four components:"
+msgstr ""
+
+#: i2p2www/blog/2017/06/01/Summer-Dev-2017-MOAR-Speed.rst:46
+msgid ""
+"Measure\n"
+"-------"
+msgstr ""
+
+#: i2p2www/blog/2017/06/01/Summer-Dev-2017-MOAR-Speed.rst:51
+msgid ""
+"We can't tell if we improve performance without a baseline! We'll be "
+"creating a\n"
+"metrics system for collecting usage and performance data about I2P in a\n"
+"privacy-preserving way, as well as porting various benchmarking tools to "
+"run\n"
+"over I2P (e.g. iperf3_)."
+msgstr ""
+
+#: i2p2www/blog/2017/06/01/Summer-Dev-2017-MOAR-Speed.rst:60
+msgid ""
+"Optimise\n"
+"--------"
+msgstr ""
+
+#: i2p2www/blog/2017/06/01/Summer-Dev-2017-MOAR-Speed.rst:65
+msgid ""
+"There's a lot of scope for improving the performance of our existing "
+"code, to\n"
+"e.g. reduce the overhead of participating in tunnels. We will be looking "
+"at\n"
+"potential improvements to:"
+msgstr ""
+
+#: i2p2www/blog/2017/06/01/Summer-Dev-2017-MOAR-Speed.rst:71
+msgid "Cryptographic primitives"
+msgstr ""
+
+#: i2p2www/blog/2017/06/01/Summer-Dev-2017-MOAR-Speed.rst:72
+msgid ""
+"Network transports, both at the link-layer (NTCP_, SSU_) and end-to-end "
+"(Streaming_)"
+msgstr ""
+
+#: i2p2www/blog/2017/06/01/Summer-Dev-2017-MOAR-Speed.rst:73
+msgid "Peer profiling"
+msgstr ""
+
+#: i2p2www/blog/2017/06/01/Summer-Dev-2017-MOAR-Speed.rst:74
+msgid "Tunnel path selection"
+msgstr ""
+
+#: i2p2www/blog/2017/06/01/Summer-Dev-2017-MOAR-Speed.rst:80
+msgid ""
+"Advance\n"
+"-------"
+msgstr ""
+
+#: i2p2www/blog/2017/06/01/Summer-Dev-2017-MOAR-Speed.rst:85
+msgid ""
+"We have several open proposals for improving the scalability of the I2P "
+"network\n"
+"(e.g. Prop115_, Prop123_, Prop124_, Prop125_, Prop138_, Prop140_). We "
+"will be\n"
+"working on these proposals, and begin implementing the finalised ones in "
+"the\n"
+"various network routers. The more feedback these proposals receive, the "
+"sooner\n"
+"we can roll them out, and the sooner I2P services can start using them!"
+msgstr ""
+
+#: i2p2www/blog/2017/06/01/Summer-Dev-2017-MOAR-Speed.rst:100
+msgid ""
+"Research\n"
+"--------"
+msgstr ""
+
+#: i2p2www/blog/2017/06/01/Summer-Dev-2017-MOAR-Speed.rst:105
+msgid ""
+"I2P is a packet-switched network, like the internet it runs on top of. "
+"This\n"
+"gives us significant flexibility in how we route packets, both for "
+"performance\n"
+"and privacy. The majority of this flexibility is unexplored! We want to\n"
+"encourage research into how various clearnet techniques for improving "
+"bandwidth\n"
+"can be applied to I2P, and how they might affect the privacy of network\n"
+"participants."
+msgstr ""
+
+#: i2p2www/blog/2017/06/01/Summer-Dev-2017-MOAR-Speed.rst:119
+msgid ""
+"We have many more ideas for things we'd like to get done in these areas. "
+"If\n"
+"you're interested in hacking on privacy and anonymity software, designing"
+"\n"
+"protocols (cryptographic or otherwise), or researching future ideas - "
+"come and\n"
+"chat with us on IRC or Twitter! We are always happy to welcome newcomers "
+"into\n"
+"our community, both inside and outside the I2P network. We'll also be "
+"sending\n"
+"I2P stickers out to all new contributors taking part! If you want to chat"
+" about\n"
+"a specific idea, contact `@GetI2P`_, `@i2p`_ or `@str4d`_ on Twitter. You"
+" can\n"
+"also find us in #i2p-dev on OFTC or Freenode."
+msgstr ""
+
+#: i2p2www/blog/2017/06/01/Summer-Dev-2017-MOAR-Speed.rst:141
+msgid ""
+"Low-latency onion-routing networks are vulnerable to traffic confirmation"
+" attacks, so it would be reasonable to ask whether improved performance "
+"equates to reduced privacy. Some latency can help privacy if applied "
+"correctly via random delays or batching (neither of which are currently "
+"employed by any general-purpose onion-routing network). However, if a "
+"tunnel has uniform overall latency, then traffic confirmation attacks "
+"should be just as viable with or without that latency; thus there should "
+"be little statistical difference when the latency is reduced uniformly."
+msgstr ""
+
+#: i2p2www/blog/2017/08/07/0.9.31-Release.rst:1
+msgid ""
+"==============\n"
+"0.9.31 Release\n"
+"=============="
+msgstr ""
+
+#: i2p2www/blog/2017/08/07/0.9.31-Release.rst:10
+msgid "0.9.31 with Console Updates"
+msgstr ""
+
+#: i2p2www/blog/2017/08/07/0.9.31-Release.rst:17
+msgid ""
+"The changes in this release are much more noticeable than usual!\n"
+"We have refreshed the router console to make it easier to understand,\n"
+"improve accessibility and cross-browser support,\n"
+"and generally tidy things up.\n"
+"This is the first step in a longer-term plan to make the router console "
+"more user-friendly.\n"
+"We have also added torrent ratings and comments support to i2psnark."
+msgstr ""
+
+#: i2p2www/blog/2017/08/07/0.9.31-Release.rst:36
+msgid "Console updates"
+msgstr ""
+
+#: i2p2www/blog/2017/08/07/0.9.31-Release.rst:37
+msgid "i2psnark ratings and comments"
+msgstr ""
+
+#: i2p2www/blog/2017/08/07/0.9.31-Release.rst:43
+msgid "Fix compile error with Jetty 9.2.22"
+msgstr ""
+
+#: i2p2www/blog/2017/08/07/0.9.31-Release.rst:44
+msgid "Preserve CRT parameters for RSA private keys"
+msgstr ""
+
+#: i2p2www/blog/2017/08/07/0.9.31-Release.rst:45
+msgid "Fix AES NPE on 4-core Rasp. Pi"
+msgstr ""
+
+#: i2p2www/blog/2017/08/07/0.9.31-Release.rst:46
+msgid "Fix NPE in GeoIP"
+msgstr ""
+
+#: i2p2www/blog/2017/08/07/0.9.31-Release.rst:47
+msgid "Fix bencoding for scrape response in zzzot plugin"
+msgstr ""
+
+#: i2p2www/blog/2017/08/07/0.9.31-Release.rst:48
+msgid "Fix display of default SusiDNS subscription"
+msgstr ""
+
+#: i2p2www/blog/2017/08/07/0.9.31-Release.rst:49
+msgid "Fix Debian apparmor profile"
+msgstr ""
+
+#: i2p2www/blog/2017/08/07/0.9.31-Release.rst:50
+msgid "Improve handling of read-only i2psnark directory"
+msgstr ""
+
+#: i2p2www/blog/2017/08/07/0.9.31-Release.rst:56
+msgid "Hostname lookup caching improvements"
+msgstr ""
+
+#: i2p2www/blog/2017/08/07/0.9.31-Release.rst:57
+msgid "Move blockfile support from i2p.jar to addressbook.jar"
+msgstr ""
+
+#: i2p2www/blog/2017/08/07/0.9.31-Release.rst:58
+msgid "Locale-independent Jetty directory listing"
+msgstr ""
+
+#: i2p2www/blog/2017/11/07/0.9.32-Release.rst:1
+msgid ""
+"==============\n"
+"0.9.32 Release\n"
+"=============="
+msgstr ""
+
+#: i2p2www/blog/2017/11/07/0.9.32-Release.rst:10
+msgid "0.9.32 with Console Updates"
+msgstr ""
+
+#: i2p2www/blog/2017/11/07/0.9.32-Release.rst:17
+msgid ""
+"0.9.32 contains a number of fixes in the router console and associated "
+"webapps (addressbook, i2psnark, and susimail).\n"
+"We have also changed the way we handle configured hostnames for published"
+" router infos, to eliminate some network enumeration attacks via DNS.\n"
+"We have added some checks in the console to resist rebinding attacks."
+msgstr ""
+"0.9.32 istiqamətləndirici konsolu və onunla əlaqəli webapps- də (ünvan "
+"kitabçası, i2psnark və susimail) bir sıra düzəlişləri ehtiva edir. \n"
+"DNS vasitəsilə bəzi şəbəkə hesablama hücumlarını aradan qaldırmaq üçün "
+"yayımlanan istiqamətləndirici məlumatlar üçün quraşdırılan hostname-lərin"
+" idarəsini dəyişdik.\n"
+"Təkrar hücumların qarşısını almaq üçün konsola bəzi yoxlamalar əlavə "
+"etdik."
+
+#: i2p2www/blog/2017/11/07/0.9.32-Release.rst:33
+msgid "Disallow hostnames in router addresses (proposal 141)"
+msgstr ""
+
+#: i2p2www/blog/2017/11/07/0.9.32-Release.rst:34
+msgid "Validate Host header in console"
+msgstr ""
+
+#: i2p2www/blog/2017/11/07/0.9.32-Release.rst:39
+msgid "Numerous console, i2psnark, susidns, and susimail UI fixes"
+msgstr ""
+
+#: i2p2www/blog/2017/11/07/0.9.32-Release.rst:40
+msgid "Fix i2psnark issues with expanding sections in some browsers"
+msgstr ""
+
+#: i2p2www/blog/2017/11/07/0.9.32-Release.rst:41
+msgid "Debian packaging fixes"
+msgstr ""
+
+#: i2p2www/blog/2017/11/07/0.9.32-Release.rst:46
+msgid "New benchmarking framework"
+msgstr ""
+
+#: i2p2www/blog/2017/11/07/0.9.32-Release.rst:47
+msgid "New Indonesian translation"
+msgstr ""
+
+#: i2p2www/blog/2018/01/30/0.9.33-Release.rst:1
+msgid ""
+"==============\n"
+"0.9.33 Release\n"
+"=============="
+msgstr ""
+
+#: i2p2www/blog/2018/01/30/0.9.33-Release.rst:10
+msgid "0.9.33 with Bug Fixes"
+msgstr ""
+
+#: i2p2www/blog/2018/01/30/0.9.33-Release.rst:17
+msgid ""
+"0.9.33 contains a large number of bug fixes, including i2psnark, "
+"i2ptunnel, streaming, and SusiMail.\n"
+"For those who cannot access the reseed sites directly, we now support "
+"several types of proxies for reseeding.\n"
+"We now set rate limits by default in the hidden services manager.\n"
+"For those that run high-traffic servers, please review and adjust the "
+"limits as necessary."
+msgstr ""
+
+#: i2p2www/blog/2018/01/30/0.9.33-Release.rst:34
+msgid "DesktopGui: Enable on OSX"
+msgstr ""
+
+#: i2p2www/blog/2018/01/30/0.9.33-Release.rst:35
+msgid "i2ptunnel: Set default rate limits"
+msgstr ""
+
+#: i2p2www/blog/2018/01/30/0.9.33-Release.rst:36
+msgid "Reseeding: Add support for proxies"
+msgstr ""
+
+#: i2p2www/blog/2018/01/30/0.9.33-Release.rst:39
+msgid "new installs only"
+msgstr ""
+
+#: i2p2www/blog/2018/01/30/0.9.33-Release.rst:45
+msgid "Client: Remove key when stopping or disabling encrypted lease set"
+msgstr ""
+
+#: i2p2www/blog/2018/01/30/0.9.33-Release.rst:46
+msgid "Console: Several keyring configuration fixes"
+msgstr ""
+
+#: i2p2www/blog/2018/01/30/0.9.33-Release.rst:47
+msgid "EepGet: Detect and reject redirect to https"
+msgstr ""
+
+#: i2p2www/blog/2018/01/30/0.9.33-Release.rst:48
+msgid "HTTP Proxy: Fix up characters in URLs not escaped by browsers "
+msgstr ""
+
+#: i2p2www/blog/2018/01/30/0.9.33-Release.rst:49
+msgid "i2psnark: Fix bad completion status on recheck"
+msgstr ""
+
+#: i2p2www/blog/2018/01/30/0.9.33-Release.rst:50
+msgid "i2psnark: Prohibit comments unless name is set"
+msgstr ""
+
+#: i2p2www/blog/2018/01/30/0.9.33-Release.rst:51
+msgid "i2psnark: Fix crash stopping update torrent"
+msgstr ""
+
+#: i2p2www/blog/2018/01/30/0.9.33-Release.rst:52
+msgid "i2ptunnel: Don't erase messages on refresh in UI"
+msgstr ""
+
+#: i2p2www/blog/2018/01/30/0.9.33-Release.rst:53
+msgid "i2ptunnel: Propagate reset to and from streaming"
+msgstr ""
+
+#: i2p2www/blog/2018/01/30/0.9.33-Release.rst:54
+msgid "i2ptunnel: Add header read timeouts to client proxies"
+msgstr ""
+
+#: i2p2www/blog/2018/01/30/0.9.33-Release.rst:55
+msgid "i2ptunnel: Prevent changing sig type after creating destination"
+msgstr ""
+
+#: i2p2www/blog/2018/01/30/0.9.33-Release.rst:56
+msgid "Jetty: Fix zero length in request log for static content"
+msgstr ""
+
+#: i2p2www/blog/2018/01/30/0.9.33-Release.rst:57
+msgid "Router: Reduce router info lock contention"
+msgstr ""
+
+#: i2p2www/blog/2018/01/30/0.9.33-Release.rst:58
+msgid "Streaming: Fix loopback hangs"
+msgstr ""
+
+#: i2p2www/blog/2018/01/30/0.9.33-Release.rst:59
+msgid "Streaming: Fix bug causing excessive acks"
+msgstr ""
+
+#: i2p2www/blog/2018/01/30/0.9.33-Release.rst:60
+msgid "Streaming: Fix connection close after reset"
+msgstr ""
+
+#: i2p2www/blog/2018/01/30/0.9.33-Release.rst:61
+msgid "SusiMail: Fix several issues when using multiple browser tabs"
+msgstr ""
+
+#: i2p2www/blog/2018/01/30/0.9.33-Release.rst:62
+msgid "SusuMail: Fix bugs corrupting text attachments and large message bodies"
+msgstr ""
+
+#: i2p2www/blog/2018/01/30/0.9.33-Release.rst:63
+msgid "SusiMail: Reject sending messages that exceed server limits"
+msgstr ""
+
+#: i2p2www/blog/2018/01/30/0.9.33-Release.rst:64
+msgid "SusiMail: Reduce chance of crashes sending large attachments"
+msgstr ""
+
+#: i2p2www/blog/2018/01/30/0.9.33-Release.rst:65
+msgid "SusiMail: Subject line encoding fixes"
+msgstr ""
+
+#: i2p2www/blog/2018/01/30/0.9.33-Release.rst:66
+msgid "SusiMail: Fix Cc header"
+msgstr ""
+
+#: i2p2www/blog/2018/01/30/0.9.33-Release.rst:67
+msgid "SusiMail: Fix encoding for attachment file names"
+msgstr ""
+
+#: i2p2www/blog/2018/01/30/0.9.33-Release.rst:68
+msgid "SusiMail: POP3 socket close after failure"
+msgstr ""
+
+#: i2p2www/blog/2018/01/30/0.9.33-Release.rst:69
+#: i2p2www/blog/2018/08/23/0.9.36-Release.rst:64
+msgid "Unit test fixes"
+msgstr ""
+
+#: i2p2www/blog/2018/01/30/0.9.33-Release.rst:70
+msgid "Utils: Use constant-time method to check passwords"
+msgstr ""
+
+#: i2p2www/blog/2018/01/30/0.9.33-Release.rst:76
+msgid "Build: Add partial Gradle support"
+msgstr ""
+
+#: i2p2www/blog/2018/01/30/0.9.33-Release.rst:77
+msgid "Console: Hide or combine aliased tunnels on tunnels pages"
+msgstr ""
+
+#: i2p2www/blog/2018/01/30/0.9.33-Release.rst:78
+msgid "Console: Note encrypted leasesets on netdb page"
+msgstr ""
+
+#: i2p2www/blog/2018/01/30/0.9.33-Release.rst:79
+msgid "Console: Use bandwidth setting for burst bandwidth"
+msgstr ""
+
+#: i2p2www/blog/2018/01/30/0.9.33-Release.rst:80
+msgid "Console: Refactor multipart form handling to use Servlet 3.0 API"
+msgstr ""
+
+#: i2p2www/blog/2018/01/30/0.9.33-Release.rst:81
+msgid "Console: Move most handlers and helpers to the war"
+msgstr ""
+
+#: i2p2www/blog/2018/01/30/0.9.33-Release.rst:82
+msgid "Debian: Xenial build is now separate, Zesty+ matches Buster"
+msgstr ""
+
+#: i2p2www/blog/2018/01/30/0.9.33-Release.rst:83
+msgid ""
+"Debian: Remove ecj dependency; replace glassfish with libtaglibs where "
+"able"
+msgstr ""
+
+#: i2p2www/blog/2018/01/30/0.9.33-Release.rst:84
+msgid "Debian: Fix builds for x32"
+msgstr ""
+
+#: i2p2www/blog/2018/01/30/0.9.33-Release.rst:85
+msgid "i2ptunnel: Refactor edit jsps"
+msgstr ""
+
+#: i2p2www/blog/2018/01/30/0.9.33-Release.rst:86
+msgid "i2ptunnel: Message box improvements"
+msgstr ""
+
+#: i2p2www/blog/2018/01/30/0.9.33-Release.rst:87
+msgid "Session Key Manager: Delete excess tag sets"
+msgstr ""
+
+#: i2p2www/blog/2018/01/30/0.9.33-Release.rst:88
+msgid "SOCKS: Move client code to core"
+msgstr ""
+
+#: i2p2www/blog/2018/01/30/0.9.33-Release.rst:89
+msgid ""
+"Startup: Increase open files ulimit if able, in i2prouter script (new "
+"installs only)"
+msgstr ""
+
+#: i2p2www/blog/2018/01/30/0.9.33-Release.rst:90
+msgid "SusiMail: UI tweaks and minor fixes"
+msgstr ""
+
+#: i2p2www/blog/2018/01/30/0.9.33-Release.rst:91
+msgid "SusiMail: Use internal sockets to connect to servers"
+msgstr ""
+
+#: i2p2www/blog/2018/01/30/0.9.33-Release.rst:92
+msgid "SusiMail: Encoder refactoring"
+msgstr ""
+
+#: i2p2www/blog/2018/01/30/0.9.33-Release.rst:93
+msgid "SusiMail: State tracking refactoring"
+msgstr ""
+
+#: i2p2www/blog/2018/01/30/0.9.33-Release.rst:95
+msgid "Update GeoIP data"
+msgstr ""
+
+#: i2p2www/blog/2018/02/11/high-level-roadmap.rst:1
+msgid ""
+"===========================\n"
+"High-level Roadmap for 2018\n"
+"==========================="
+msgstr ""
+
+#: i2p2www/blog/2018/02/11/high-level-roadmap.rst:10
+msgid ""
+"2018 will be the year of new protocols, new collaborations, and a more "
+"refined focus."
+msgstr ""
+
+#: i2p2www/blog/2018/02/11/high-level-roadmap.rst:12
+msgid ""
+"One of the many things we discussed at 34C3 was what we should focus on "
+"for the\n"
+"coming year. In particular, we wanted a roadmap that was clear about what"
+" we\n"
+"want to ensure we get done, vs what would be really nice to have, and be "
+"able to\n"
+"help onboard newcomers to either category. Here is what we came up with:"
+msgstr ""
+
+#: i2p2www/blog/2018/02/11/high-level-roadmap.rst:19
+msgid ""
+"Priority: New crypto(graphy!)\n"
+"-----------------------------"
+msgstr ""
+
+#: i2p2www/blog/2018/02/11/high-level-roadmap.rst:24
+msgid ""
+"Many of the current primitives and protocols still retain their original "
+"designs\n"
+"from circa 2005, and need improvement. We have had a number of open "
+"proposals\n"
+"for several years with ideas, but forward progress has been slow. We all "
+"agreed\n"
+"that this needs to be our top priority for 2018. The core components are:"
+"\n"
+"\n"
+"- New transport protocols (to replace NTCP and SSU). See Prop111_.\n"
+"- New onion-encryption protocol for building and using tunnels.\n"
+"- New NetDB datatypes to enable enhanced Destinations. See Prop123_.\n"
+"- Upgraded end-to-end protocol (replacing ElGamal)."
+msgstr ""
+
+#: i2p2www/blog/2018/02/11/high-level-roadmap.rst:39
+msgid ""
+"Work on this priority falls into several areas:\n"
+"\n"
+"- Writing proposals.\n"
+"- Writing working implementations of them that we can test.\n"
+"- Reviewing proposals."
+msgstr ""
+
+#: i2p2www/blog/2018/02/11/high-level-roadmap.rst:47
+msgid ""
+"We cannot release new protocol specifications across the entire network "
+"without\n"
+"work on all of these areas."
+msgstr ""
+
+#: i2p2www/blog/2018/02/11/high-level-roadmap.rst:52
+msgid ""
+"Nice-to-have: Code reuse\n"
+"------------------------"
+msgstr ""
+
+#: i2p2www/blog/2018/02/11/high-level-roadmap.rst:57
+msgid ""
+"One of the benefits of starting the above work now, is that over the last"
+" few\n"
+"years there have been independent efforts to create simple protocols and\n"
+"protocol frameworks that achieve many of the aims we have for our own "
+"protocols,\n"
+"and have gained traction with the wider community. By leveraging this "
+"work, we\n"
+"get a \"force multiplier\" effect:\n"
+"\n"
+"- We benefit from protocol designs, security proofs, and code written by "
+"others,\n"
+"  reducing the amount of work we need to do for the same level of\n"
+"  feature-completeness and security assurances.\n"
+"\n"
+"- Work we do can be leveraged by other communities, increasing their "
+"interest in\n"
+"  collaborating with us, and thinking about I2P as a whole."
+msgstr ""
+
+#: i2p2www/blog/2018/02/11/high-level-roadmap.rst:72
+msgid ""
+"My proposals in particular will be leveraging the `Noise Protocol "
+"Framework`_,\n"
+"and the `SPHINX packet format`_. I have collaborations lined up with "
+"several\n"
+"people outside I2P for these!"
+msgstr ""
+
+#: i2p2www/blog/2018/02/11/high-level-roadmap.rst:81
+msgid ""
+"Priority: Clearnet collaboration\n"
+"--------------------------------"
+msgstr ""
+
+#: i2p2www/blog/2018/02/11/high-level-roadmap.rst:86
+msgid ""
+"On that topic, we've been slowly building interest over the last six "
+"months or\n"
+"so. Across PETS2017, 34C3, and RWC2018, I've had some very good "
+"discussions\n"
+"about ways in which we can improve collaboration with the wider "
+"community. This\n"
+"is really important to ensure we can garner as much review as possible "
+"for new\n"
+"protocols. The biggest blocker I've seen is the fact that the majority of"
+" I2P\n"
+"development collaboration currently happens inside I2P itself, which\n"
+"significantly increases the effort required to contribute."
+msgstr ""
+
+#: i2p2www/blog/2018/02/11/high-level-roadmap.rst:96
+msgid ""
+"The two priorities in this area are:\n"
+"\n"
+"- Set up a project-run development forum that is accessible both inside "
+"and\n"
+"  outside I2P.\n"
+"\n"
+"- Set up mailing lists for review and discussion of proposals (possibly\n"
+"  connected to the above forum)."
+msgstr ""
+
+#: i2p2www/blog/2018/02/11/high-level-roadmap.rst:106
+msgid ""
+"Other goals which are classed as nice-to-have:\n"
+"\n"
+"- Set up a usable git-to-mtn pathway, to enable us to effectively solicit"
+"\n"
+"  clearnet contributions on GitHub while keeping the canonical dev "
+"environment\n"
+"  on Monotone.\n"
+"\n"
+"- Write a \"position paper\" that accurately explains I2P to academic "
+"audiences,\n"
+"  and puts it in context with existing literature."
+msgstr ""
+
+#: i2p2www/blog/2018/02/11/high-level-roadmap.rst:117
+msgid ""
+"I expect that collaborations with people outside I2P will be done "
+"entirely on\n"
+"GitHub, for minimal friction."
+msgstr ""
+
+#: i2p2www/blog/2018/02/11/high-level-roadmap.rst:122
+msgid ""
+"Priority: Preparation for long-lived releases\n"
+"---------------------------------------------"
+msgstr ""
+
+#: i2p2www/blog/2018/02/11/high-level-roadmap.rst:127
+msgid ""
+"I2P is now in Debian Sid (their unstable repo) which will stablilise in "
+"around a\n"
+"year and a half, and has also been pulled into the Ubuntu repository for\n"
+"inclusion in the next LTS release in April. We are going to start having "
+"I2P\n"
+"versions that end up hanging around for years, and we need to ensure we "
+"can\n"
+"handle their presence in the network."
+msgstr ""
+
+#: i2p2www/blog/2018/02/11/high-level-roadmap.rst:135
+msgid ""
+"The primary goal here is to roll out as many of the new protocols as we "
+"feasibly\n"
+"can in the next year, to hit the next Debian stable release. For those "
+"that\n"
+"require multi-year rollouts, we should incorporate the forward-"
+"compatability\n"
+"changes as early as we can."
+msgstr ""
+
+#: i2p2www/blog/2018/02/11/high-level-roadmap.rst:142
+msgid ""
+"Priority: Pluginization of current apps\n"
+"---------------------------------------"
+msgstr ""
+
+#: i2p2www/blog/2018/02/11/high-level-roadmap.rst:147
+msgid ""
+"The Debian model encourages having separate packages for separate "
+"components. We\n"
+"agreed that decoupling the currently-bundled Java applications from the "
+"core\n"
+"Java router would be beneficial for several reasons:\n"
+"\n"
+"- It codifies the boundary between the applications and the router.\n"
+"\n"
+"- It should make it easier to get these apps running with non-Java "
+"routers.\n"
+"\n"
+"- It would enable third parties to create \"I2P bundles\" containing just"
+" the\n"
+"  applications they want."
+msgstr ""
+
+#: i2p2www/blog/2018/02/11/high-level-roadmap.rst:160
+msgid ""
+"In combination with the earlier priorities, this moves the main I2P "
+"project more\n"
+"in the direction of e.g. the Linux kernel. We will spend more time "
+"focusing on\n"
+"the network itself, leaving third-party developers to focus on "
+"applications that\n"
+"use the network (something that is significantly easier to do after our "
+"work in\n"
+"the last few years on APIs and libraries)."
+msgstr ""
+
+#: i2p2www/blog/2018/02/11/high-level-roadmap.rst:168
+msgid ""
+"Nice-to-have: App improvements\n"
+"------------------------------"
+msgstr ""
+
+#: i2p2www/blog/2018/02/11/high-level-roadmap.rst:173
+msgid ""
+"There are a bunch of app-level improvements that we want to work on, but "
+"do not\n"
+"currently have the developer time to do so, given our other priorities. "
+"This is\n"
+"an area we would love to see new contributors for! Once the above "
+"decoupling is\n"
+"complete, it will be significantly easier for someone to work on a "
+"specific\n"
+"application independently of the main Java router."
+msgstr ""
+
+#: i2p2www/blog/2018/02/11/high-level-roadmap.rst:181
+msgid ""
+"One such application we would love to have help with is I2P Android. We "
+"will be\n"
+"keeping it up-to-date with the core I2P releases, and fixing bugs as we "
+"can, but\n"
+"there is much that could be done to improve the underlying code as well "
+"as the\n"
+"usability."
+msgstr ""
+
+#: i2p2www/blog/2018/02/11/high-level-roadmap.rst:188
+msgid ""
+"Priority: Susimail and I2P-Bote stabilisation\n"
+"---------------------------------------------"
+msgstr ""
+
+#: i2p2www/blog/2018/02/11/high-level-roadmap.rst:193
+msgid ""
+"Having said that, we do want to work specifically on Susimail and I2P-"
+"Bote fixes\n"
+"in the near term (some of which have landed in 0.9.33). They have had "
+"less work\n"
+"over the last few years than other I2P apps, and so we want to spend some"
+" time\n"
+"bringing their codebases up to par, and making them easier for new "
+"contributors\n"
+"to jump into!"
+msgstr ""
+
+#: i2p2www/blog/2018/02/11/high-level-roadmap.rst:201
+msgid ""
+"Nice-to-have: Ticket triage\n"
+"---------------------------"
+msgstr ""
+
+#: i2p2www/blog/2018/02/11/high-level-roadmap.rst:206
+msgid ""
+"We have a large backlog of tickets in a number of I2P subsystems and "
+"apps. As\n"
+"part of the above stabilisation effort, we would love to clean up some of"
+" our\n"
+"older long-standing issues. More importantly, we want to ensure that our "
+"tickets\n"
+"are correctly organised, so that new contributors can find good tickets "
+"to work\n"
+"on."
+msgstr ""
+
+#: i2p2www/blog/2018/02/11/high-level-roadmap.rst:214
+msgid ""
+"Priority: User support\n"
+"----------------------"
+msgstr ""
+
+#: i2p2www/blog/2018/02/11/high-level-roadmap.rst:219
+msgid ""
+"One aspect of the above we will be focusing on is keeping in touch with "
+"users\n"
+"who take the time to report issues. Thank you! The smaller we can make "
+"the\n"
+"feedback loop, the quicker we can resolve problems that new users face, "
+"and the\n"
+"more likely it is that they keep participating in the community."
+msgstr ""
+
+#: i2p2www/blog/2018/02/11/high-level-roadmap.rst:226
+msgid ""
+"We'd love your help!\n"
+"--------------------"
+msgstr ""
+
+#: i2p2www/blog/2018/02/11/high-level-roadmap.rst:231
+msgid ""
+"That all looks very ambitious, and it is! But many of the items above "
+"overlap,\n"
+"and with careful planning we can make a serious dent in them."
+msgstr ""
+
+#: i2p2www/blog/2018/02/11/high-level-roadmap.rst:236
+msgid ""
+"If you are interested in helping with any of the goals above, come chat "
+"to us!\n"
+"You can find us on OFTC and Freenode (#i2p-dev), and Twitter (@GetI2P)."
+msgstr ""
+
+#: i2p2www/blog/2018/02/12/bsidesnyc.rst:1
+msgid ""
+"================\n"
+"I2P at BSidesNYC\n"
+"================"
+msgstr ""
+
+#: i2p2www/blog/2018/02/12/bsidesnyc.rst:10
+msgid "Trip report about the I2P meetup at BSidesNYC."
+msgstr ""
+
+#: i2p2www/blog/2018/04/10/0.9.34-Release.rst:1
+msgid ""
+"==============\n"
+"0.9.34 Release\n"
+"=============="
+msgstr ""
+
+#: i2p2www/blog/2018/04/10/0.9.34-Release.rst:10
+msgid "0.9.34 with Bug Fixes"
+msgstr ""
+
+#: i2p2www/blog/2018/04/10/0.9.34-Release.rst:17
+msgid ""
+"0.9.34 contains a lot of bug fixes!\n"
+"It also has improvements in SusiMail, IPv6 handling, and tunnel peer "
+"selection.\n"
+"We add support for IGD2 schemas in UPnP.\n"
+"There's also preparation for more improvements you will see in future "
+"releases."
+msgstr ""
+"0.9.34 xeyli xəta düzəlişləri var!\n"
+"SusiMail,  IPv6 ilə işdə və tunel bənzərlərinin seçimində "
+"təkmilləşdirmələr var.\n"
+"Biz UPnP-də IGD2-ə dəstək sxemləri əlavə etdik.\n"
+"Gələcək buraxılışlarda görəcəyiniz əlavə təkmilləşmələrə hazırlıq gedir."
+
+#: i2p2www/blog/2018/04/10/0.9.34-Release.rst:34
+msgid "SusiMail: Improved startup and memory management"
+msgstr ""
+
+#: i2p2www/blog/2018/04/10/0.9.34-Release.rst:35
+msgid "UPnP: Support IGD 2"
+msgstr ""
+
+#: i2p2www/blog/2018/04/10/0.9.34-Release.rst:40
+msgid "Console: Numerous fixes"
+msgstr ""
+
+#: i2p2www/blog/2018/04/10/0.9.34-Release.rst:41
+msgid "i2ptunnel: Fix servers not accepting after router restart"
+msgstr ""
+
+#: i2p2www/blog/2018/04/10/0.9.34-Release.rst:42
+msgid "Router: Improved tunnel peer selection for hidden and IPv6-only modes"
+msgstr ""
+
+#: i2p2www/blog/2018/04/10/0.9.34-Release.rst:43
+msgid "SusiMail: Numerous fixes"
+msgstr ""
+
+#: i2p2www/blog/2018/04/10/0.9.34-Release.rst:44
+msgid "Transport: Better selection of IPv6 addresses"
+msgstr ""
+
+#: i2p2www/blog/2018/04/10/0.9.34-Release.rst:49
+#: i2p2www/blog/2018/06/26/0.9.35-Release.rst:62
+msgid "Prep for HTTPS console and eepsite"
+msgstr ""
+
+#: i2p2www/blog/2018/04/10/0.9.34-Release.rst:50
+#: i2p2www/blog/2018/06/26/0.9.35-Release.rst:63
+msgid "Prep for splitting up Debian package"
+msgstr ""
+
+#: i2p2www/blog/2018/04/10/0.9.34-Release.rst:51
+msgid "Streaming: Return HTTP response when limits exceeded"
+msgstr ""
+
+#: i2p2www/blog/2018/04/10/0.9.34-Release.rst:52
+msgid "Console: Number formatting changes"
+msgstr ""
+
+#: i2p2www/blog/2018/04/10/0.9.34-Release.rst:53
+msgid "EdDSA cleanups"
+msgstr ""
+
+#: i2p2www/blog/2018/06/26/0.9.35-Release.rst:1
+msgid ""
+"==============\n"
+"0.9.35 Release\n"
+"=============="
+msgstr ""
+
+#: i2p2www/blog/2018/06/26/0.9.35-Release.rst:10
+msgid "0.9.35 with SusiMail folders and SSL Wizard"
+msgstr "SusiMail qovluqları və SSL Vizardı ilə 0.9.35"
+
+#: i2p2www/blog/2018/06/26/0.9.35-Release.rst:17
+msgid ""
+"0.9.35 adds support for folders in SusiMail, and a new SSL Wizard for "
+"setting up HTTPS on your Hidden Service website.\n"
+"We also have the usual collection of bug fixes, especially in SusiMail."
+msgstr ""
+"SusiMail-də qovluqlar üçün dəstək və Gizli Xidmət saytında HTTPS-i qurmaq"
+" üçün 0.9.35 yeni SSL Vizardı əlavə edir.\n"
+"Bizim xüsusilə SusiMail-də adi xəta düzəlişləri kolleksiyamız var."
+
+#: i2p2www/blog/2018/06/26/0.9.35-Release.rst:22
+msgid ""
+"We're hard at work on several things for 0.9.36, including a new OSX "
+"installer and a faster, more secure transport protocol called NTCP2."
+msgstr ""
+"Yeni OSX quraşdırıcısı və daha sürətli, daha təhlükəsiz nəqliyyat "
+"protokolu olan NTCP2 də daxil olmaqla, 0.9.36 üçün bir neçə məsələ "
+"üzərində çalışırıq."
+
+#: i2p2www/blog/2018/06/26/0.9.35-Release.rst:26
+msgid "I2P will be at HOPE in New York City, July 20-22. Find us and say hello!"
+msgstr ""
+"I2P 20-22 iyul tarixlərində Nyu-York şəhərində HOPE-da olacaq. Bizi "
+"tapıb, salamlayın!"
+
+#: i2p2www/blog/2018/06/26/0.9.35-Release.rst:40
+msgid "New Hidden Service SSL Wizard"
+msgstr ""
+
+#: i2p2www/blog/2018/06/26/0.9.35-Release.rst:41
+msgid "SusiMail support for Folders, Drafts, background sending"
+msgstr ""
+
+#: i2p2www/blog/2018/06/26/0.9.35-Release.rst:47
+msgid "Console: Fix changes to wrong tunnel on /configtunnels"
+msgstr ""
+
+#: i2p2www/blog/2018/06/26/0.9.35-Release.rst:48
+msgid "CPUID: Fix TBM detection"
+msgstr ""
+
+#: i2p2www/blog/2018/06/26/0.9.35-Release.rst:49
+msgid "i2psnark: Fix torrents ignoring priority settings when autostart enabled"
+msgstr ""
+
+#: i2p2www/blog/2018/06/26/0.9.35-Release.rst:50
+msgid "i2ptunnel: Retry accept after server socket closed"
+msgstr ""
+
+#: i2p2www/blog/2018/06/26/0.9.35-Release.rst:51
+msgid "NTCP: Fix bug causing initial latency for outbound connections"
+msgstr ""
+
+#: i2p2www/blog/2018/06/26/0.9.35-Release.rst:52
+msgid "SusiMail: Include attachments in forwarded mail"
+msgstr ""
+
+#: i2p2www/blog/2018/06/26/0.9.35-Release.rst:53
+msgid "SusiMail: Many other fixes"
+msgstr ""
+
+#: i2p2www/blog/2018/06/26/0.9.35-Release.rst:54
+msgid "Tunnels: Prevent zero-hop even when no active peers"
+msgstr ""
+
+#: i2p2www/blog/2018/06/26/0.9.35-Release.rst:59
+msgid "Add support for notes in Addressbook"
+msgstr ""
+
+#: i2p2www/blog/2018/06/26/0.9.35-Release.rst:60
+msgid "Rewrite and new translations for eepsite help page (new installs only)"
+msgstr ""
+
+#: i2p2www/blog/2018/06/26/0.9.35-Release.rst:61
+msgid "DNSoverHTTPS (disabled by default)"
+msgstr ""
+
+#: i2p2www/blog/2018/06/26/0.9.35-Release.rst:64
+msgid "NTCP refactoring in prep for NTCP2"
+msgstr ""
+
+#: i2p2www/blog/2018/06/26/0.9.35-Release.rst:65
+msgid "Move SusiMail logging to router logs"
+msgstr ""
+
+#: i2p2www/blog/2018/06/26/0.9.35-Release.rst:66
+msgid "SusiMail BCC-to-self feature replaced with Sent folder"
+msgstr ""
+
+#: i2p2www/blog/2018/06/26/0.9.35-Release.rst:67
+msgid "Fix eepget handling of response line with no status text"
+msgstr ""
+
+#: i2p2www/blog/2018/06/26/0.9.35-Release.rst:68
+msgid "i2psnark UI cleanups"
+msgstr ""
+
+#: i2p2www/blog/2018/06/26/0.9.35-Release.rst:69
+msgid "New Azerbaijani translation"
+msgstr ""
+
+#: i2p2www/blog/2018/08/20/NTCP2.rst:1
+msgid ""
+"============================\n"
+"NTCP2 implementation details\n"
+"============================"
+msgstr ""
+
+#: i2p2www/blog/2018/08/20/NTCP2.rst:10
+msgid "I2P's new transport protocol implementation details"
+msgstr ""
+
+#: i2p2www/blog/2018/08/20/NTCP2.rst:12
+msgid "`Source article`_ by orignal at habr.com"
+msgstr ""
+
+#: i2p2www/blog/2018/08/20/NTCP2.rst:18
+msgid ""
+"I2P's transport protocols were originally developed around 15 years ago. "
+"Back \n"
+"then, the main goal was to hide the transferred data, not to hide the "
+"fact that \n"
+"one was using the protocol itself. Nobody thought seriously about "
+"protecting \n"
+"against DPI (deep packets inspection) and protocols censorship. Times "
+"change, \n"
+"and even though original transport protocols are still providing strong "
+"security, \n"
+"there was a demand for a new transport protocol. NTCP2 is designed to "
+"resist \n"
+"current censorship threats. Mainly, DPI analysis of packets length. Plus,"
+" the new \n"
+"protocol uses the most modern cryptography developments. NTCP2 is based "
+"on the \n"
+"`Noise Protocol Framework`_, with SHA256 \n"
+"as a hash function and x25519 as an elliptic curve Diffie-Hellman (DH) "
+"key \n"
+"exchange."
+msgstr ""
+
+#: i2p2www/blog/2018/08/20/NTCP2.rst:35
+msgid "Full specification of NTCP2 protocol can be `found here`_."
+msgstr ""
+
+#: i2p2www/blog/2018/08/20/NTCP2.rst:41
+msgid ""
+"New crypto\n"
+"----------"
+msgstr ""
+
+#: i2p2www/blog/2018/08/20/NTCP2.rst:46
+msgid ""
+"NTCP2 requires adding the next cryptographic algorithms to an I2P "
+"implementation:"
+msgstr ""
+
+#: i2p2www/blog/2018/08/20/NTCP2.rst:57
+msgid ""
+"Compared to our original protocol, NTCP, NTCP2 uses x25519 instead of "
+"ElGamal \n"
+"for DH function, AEAD/Chaha20/Poly1305 instead of AES-256-CBC/Adler32, "
+"and uses \n"
+"SipHash for obfuscating the packet's length information. The key "
+"derivation \n"
+"function used in NTCP2 is more complex, now using many HMAC-SHA256 calls."
+msgstr ""
+
+#: i2p2www/blog/2018/08/20/NTCP2.rst:64
+msgid ""
+"i2pd (C++) implementation note: All of the algorithms mentioned above, "
+"except \n"
+"SipHash, are implemented in OpenSSL 1.1.0. SipHash will be added to the "
+"coming \n"
+"OpenSSL 1.1.1 release. For compatibility with OpenSSL 1.0.2, which is "
+"used in \n"
+"most of the current systems, core i2pd developer \n"
+"`Jeff Becker`_ has contributed standalone \n"
+"implementations of missing cryptographic algorithms."
+msgstr ""
+
+#: i2p2www/blog/2018/08/20/NTCP2.rst:75
+msgid ""
+"RouterInfo changes\n"
+"------------------"
+msgstr ""
+
+#: i2p2www/blog/2018/08/20/NTCP2.rst:80
+msgid ""
+"NTCP2 requires having a third (x25519) key in addition to existing two "
+"(the \n"
+"encryption and signature keys). It is called a static key and it has to "
+"be added \n"
+"to any of RouterInfo addresses as an \"s\" parameter. It is required for "
+"both \n"
+"NTCP2 initiator (Alice) and responder (Bob). If more than one address "
+"supports \n"
+"NTCP2, for example, IPv4 and IPv6, \"s\" is required to be the same for "
+"all of \n"
+"them. Alice's address is allowed to have just the \"s\" parameter without"
+" \"host\" \n"
+"and \"port\" set. Also, a \"v\" parameter is required, that is currently "
+"always set \n"
+"to \"2\"."
+msgstr ""
+
+#: i2p2www/blog/2018/08/20/NTCP2.rst:91
+msgid ""
+"NTCP2 address can be declared as a separate NTCP2 address or as an old-"
+"style \n"
+"NTCP address with additional parameters, in which case it will accept "
+"both \n"
+"NTCP and NTCP2 connections. Java I2P implementation uses the second "
+"approach, \n"
+"i2pd (C++ implementation) uses the first."
+msgstr ""
+
+#: i2p2www/blog/2018/08/20/NTCP2.rst:98
+msgid ""
+"If a node accepts NTCP2 connections, it has to publish its RouterInfo "
+"with the \n"
+"\"i\" parameter, which is used as an initialization vector (IV) for the "
+"public \n"
+"encryption key when that node establishes new connections."
+msgstr ""
+
+#: i2p2www/blog/2018/08/20/NTCP2.rst:104
+msgid ""
+"Establishing a connection\n"
+"-------------------------"
+msgstr ""
+
+#: i2p2www/blog/2018/08/20/NTCP2.rst:109
+msgid ""
+"To establish a connection both sides need to generate pairs of ephemeral "
+"x25519 \n"
+"keys. Based on those keys and \"static\" keys they derive a set of keys "
+"for data \n"
+"transferring. Both parties must verify that the other side actually has a"
+" \n"
+"private key for that static key, and that static key is the same as in "
+"RouterInfo."
+msgstr ""
+
+#: i2p2www/blog/2018/08/20/NTCP2.rst:116
+msgid "Three messages are being sent to establish a connection:"
+msgstr ""
+
+#: i2p2www/blog/2018/08/20/NTCP2.rst:129
+msgid ""
+"A common x25519 key, called «input key material», is computed for each "
+"message, \n"
+"after which message encryption key is generated with a MixKey function. A"
+" value \n"
+"ck (chaining key) is kept while messages are being exchanged. \n"
+"That value is used as a final input when generating keys for data "
+"transferring."
+msgstr ""
+
+#: i2p2www/blog/2018/08/20/NTCP2.rst:136
+msgid ""
+"MixKey function looks something like this in the C++ implementation of "
+"I2P:"
+msgstr ""
+
+#: i2p2www/blog/2018/08/20/NTCP2.rst:157
+msgid ""
+"**SessionRequest** message is made of a public x25519 Alice key (32 "
+"bytes), a \n"
+"block of data encrypted with AEAD/Chacha20/Poly1305 (16 bytes), a hash \n"
+"(16 bytes) and some random data in the end (padding). Padding length is \n"
+"defined in the encrypted block of data. Encrypted block also contains "
+"length of \n"
+"the second part of the **SessionConfirmed** message. A block of data is \n"
+"encrypted and signed with a key derived from Alice's ephemeral key and \n"
+"Bob's static key. Initial ck value for MixKey function is set to SHA256 \n"
+"(Noise_XKaesobfse+hs2+hs3_25519_ChaChaPoly_SHA256)."
+msgstr ""
+
+#: i2p2www/blog/2018/08/20/NTCP2.rst:168
+msgid ""
+"Since 32 bytes of public x25519 key can be detected by DPI, it is "
+"encrypted with \n"
+"AES-256-CBC algorithm using hash of Bob's address as a key and \"i\" "
+"parameter \n"
+"from RouterInfo as an initialization vector (IV)."
+msgstr ""
+
+#: i2p2www/blog/2018/08/20/NTCP2.rst:174
+msgid ""
+"**SessionCreated** message has the same structure as **SessionRequest**, "
+"except \n"
+"the key is computed based on ephemeral keys of both sides. IV generated "
+"after \n"
+"encrypting/decrypting public key from **SessionRequest** message is used "
+"as IV \n"
+"for encrypting/decrypting ephemeral public key."
+msgstr ""
+
+#: i2p2www/blog/2018/08/20/NTCP2.rst:181
+msgid ""
+"**SessionConfirmed** message has 2 parts: public static key and Alice's \n"
+"RouterInfo. The difference from previous messages is that ephemeral "
+"public key \n"
+"is encrypted with AEAD/Chaha20/Poly1305 using the same key as "
+"**SessionCreated**. \n"
+"It leads to increasing first part of the message from 32 to 48 bytes. \n"
+"The second part is also encrypted with AEAD/Chaha20/Poly1305, but using a"
+" new \n"
+"key, computed from Bob's ephemeral key and Alice's static key. RouterInfo"
+" part \n"
+"can also be appended with random data padding, but it is not required, "
+"since \n"
+"RouterInfo usually has various length."
+msgstr ""
+
+#: i2p2www/blog/2018/08/20/NTCP2.rst:192
+msgid ""
+"Generation of data transfer keys\n"
+"--------------------------------"
+msgstr ""
+
+#: i2p2www/blog/2018/08/20/NTCP2.rst:197
+msgid ""
+"If every hash and key verification has succeeded, a common ck value must "
+"be \n"
+"present after the last MixKey operation on both sides. This value is used"
+" to \n"
+"generate two sets of keys <k, sipk, sipiv> for each side of a connection."
+" \"k\" is \n"
+"a AEAD/Chaha20/Poly1305 key, \"sipk\" is a SipHash key, \"sipiv\" is an "
+"initial \n"
+"value for SipHash IV, that is changed after each use."
+msgstr ""
+
+#: i2p2www/blog/2018/08/20/NTCP2.rst:205
+msgid ""
+"Code used to generate keys looks like this in the C++ implementation of "
+"I2P:"
+msgstr ""
+
+#: i2p2www/blog/2018/08/20/NTCP2.rst:244
+msgid ""
+"i2pd (C++) implementation note: First 16 bytes of the \"sipkeys\" array "
+"are a \n"
+"SipHash key, the last 8 bytes are IV. SipHash requires two 8 byte keys, "
+"but i2pd \n"
+"handles them as a single 16 bytes key."
+msgstr ""
+
+#: i2p2www/blog/2018/08/20/NTCP2.rst:250
+msgid ""
+"Data transferring\n"
+"-----------------"
+msgstr ""
+
+#: i2p2www/blog/2018/08/20/NTCP2.rst:255
+msgid "Data is transferred in frames, each frame has 3 parts:"
+msgstr ""
+
+#: i2p2www/blog/2018/08/20/NTCP2.rst:259
+msgid ""
+"- 2 bytes of frame length obfuscated with SipHash\n"
+"- data encrypted with Chacha20\n"
+"- 16 bytes of Poly1305 hash value"
+msgstr ""
+
+#: i2p2www/blog/2018/08/20/NTCP2.rst:265
+msgid "Maximum length of data transferred in one frame is 65519 bytes."
+msgstr ""
+
+#: i2p2www/blog/2018/08/20/NTCP2.rst:269
+msgid ""
+"Message length is obfuscated by applying the XOR function with two first "
+"bytes \n"
+"of the current SipHash IV."
+msgstr ""
+
+#: i2p2www/blog/2018/08/20/NTCP2.rst:274
+msgid ""
+"Encrypted data part contains blocks of data. Each block is prepended with"
+" 3 \n"
+"bytes header, that defines block type and block length. Generally, I2NP "
+"type \n"
+"blocks are transferred, that are I2NP messages with an altered header. "
+"One NTCP2 \n"
+"frame can transfer multiple I2NP blocks."
+msgstr ""
+
+#: i2p2www/blog/2018/08/20/NTCP2.rst:281
+msgid ""
+"The other important data block type is a random data block. It is "
+"recommended to \n"
+"add a random data block to every NTCP2 frame. Only one random data block "
+"can be \n"
+"added ant it must be the last block."
+msgstr ""
+
+#: i2p2www/blog/2018/08/20/NTCP2.rst:287
+msgid "Those are other data blocks used in the current NTCP2 implementation:"
+msgstr ""
+
+#: i2p2www/blog/2018/08/20/NTCP2.rst:291
+msgid ""
+"- RouterInfo  — usually contains Bob's RouterInfo after the connection "
+"has been \n"
+"  established, but it can also contain RouterInfo of a random node for "
+"the purpose \n"
+"  of speeding up floodfills (there is a flags field for that case). \n"
+"- Termination  — is used when a host explicitly terminates a connection "
+"and \n"
+"  specifies a reason for that.\n"
+"- DateTime — a current time in seconds."
+msgstr ""
+
+#: i2p2www/blog/2018/08/20/NTCP2.rst:301
+msgid ""
+"Summary\n"
+"-------"
+msgstr ""
+
+#: i2p2www/blog/2018/08/20/NTCP2.rst:306
+msgid ""
+"The new I2P transport protocol NTCP2 provides effective resistance "
+"against DPI \n"
+"censorship. It also results in reduced CPU load because of the faster, "
+"modern \n"
+"cryptography used. It makes I2P more likely to run on low-end devices, "
+"such as \n"
+"smartphones and home routers. Both major I2P implementations have full "
+"support \n"
+"for NTCP2 and it make NTCP2 available for use starting with version \n"
+"0.9.36 (Java) and 2.20 (i2pd, C++)."
+msgstr ""
+
+#: i2p2www/blog/2018/08/23/0.9.36-Release.rst:1
+msgid ""
+"==============\n"
+"0.9.36 Release\n"
+"=============="
+msgstr ""
+
+#: i2p2www/blog/2018/08/23/0.9.36-Release.rst:10
+msgid "0.9.36 with NTCP2 and bug fixes"
+msgstr ""
+
+#: i2p2www/blog/2018/08/23/0.9.36-Release.rst:17
+msgid ""
+"0.9.36 implements a new, more secure transport protocol called NTCP2.\n"
+"It is disabled by default, but you may enable it for testing.\n"
+"NTCP2 will be enabled in the next release."
+msgstr ""
+
+#: i2p2www/blog/2018/08/23/0.9.36-Release.rst:23
+msgid ""
+"This release also contains a fix for installs on Windows 10, and several "
+"performance improvements."
+msgstr ""
+
+#: i2p2www/blog/2018/08/23/0.9.36-Release.rst:37
+msgid "i2psnark: Add sequential order option"
+msgstr ""
+
+#: i2p2www/blog/2018/08/23/0.9.36-Release.rst:39
+msgid ""
+"NTCP2 (disabled by default, enable with advanced config "
+"i2np.ntcp2.enable=true)"
+msgstr ""
+
+#: i2p2www/blog/2018/08/23/0.9.36-Release.rst:40
+msgid "Transport performance improvements"
+msgstr ""
+
+#: i2p2www/blog/2018/08/23/0.9.36-Release.rst:45
+msgid "Console: Catch rare session exception"
+msgstr ""
+
+#: i2p2www/blog/2018/08/23/0.9.36-Release.rst:46
+msgid "Crypto: EdDSA constant-time fix"
+msgstr ""
+
+#: i2p2www/blog/2018/08/23/0.9.36-Release.rst:47
+msgid "i2psnark: Handle deleted files on recheck/reopen"
+msgstr ""
+
+#: i2p2www/blog/2018/08/23/0.9.36-Release.rst:48
+msgid "i2psnark: Fix error stopping torrent when allocating"
+msgstr ""
+
+#: i2p2www/blog/2018/08/23/0.9.36-Release.rst:49
+msgid "Installer: Fix wrapper selection on Windows 10"
+msgstr ""
+
+#: i2p2www/blog/2018/08/23/0.9.36-Release.rst:50
+msgid "Streaming: Change behavior on read timeout"
+msgstr ""
+
+#: i2p2www/blog/2018/08/23/0.9.36-Release.rst:55
+msgid "Console: Split netdb output into pages"
+msgstr ""
+
+#: i2p2www/blog/2018/08/23/0.9.36-Release.rst:56
+msgid "Debian: Add dependency on famfamfam-flag-png"
+msgstr ""
+
+#: i2p2www/blog/2018/08/23/0.9.36-Release.rst:57
+msgid "Debian: Check for missing libtaglibs at build time"
+msgstr ""
+
+#: i2p2www/blog/2018/08/23/0.9.36-Release.rst:58
+msgid "I2CP: Add option for forcing gzip on/off per-message"
+msgstr ""
+
+#: i2p2www/blog/2018/08/23/0.9.36-Release.rst:59
+msgid "i2psnark: Add icon for comments"
+msgstr ""
+
+#: i2p2www/blog/2018/08/23/0.9.36-Release.rst:60
+msgid "i2ptunnel: Change read timeout defaults to account for streaming changes"
+msgstr ""
+
+#: i2p2www/blog/2018/08/23/0.9.36-Release.rst:61
+msgid "JBigI: Detect processor change at at startup, reselect lib"
+msgstr ""
+
+#: i2p2www/blog/2018/08/23/0.9.36-Release.rst:62
+msgid "Streaming: Performance improvements"
+msgstr ""
+
+#: i2p2www/blog/2018/08/23/0.9.36-Release.rst:65
+msgid "Update GeoIPv6 data (new installs and PPA only)"
+msgstr ""
+
diff --git a/i2p2www/translations/az/LC_MESSAGES/docs.po b/i2p2www/translations/az/LC_MESSAGES/docs.po
new file mode 100644
index 00000000..cf17ba63
--- /dev/null
+++ b/i2p2www/translations/az/LC_MESSAGES/docs.po
@@ -0,0 +1,16130 @@
+# Azerbaijani translations for I2P.
+# Copyright (C) 2018 ORGANIZATION
+# This file is distributed under the same license as the I2P project.
+#
+# Translators:
+# Nikafn <appone6@gmail.com>, 2018
+msgid ""
+msgstr ""
+"Project-Id-Version:  I2P\n"
+"Report-Msgid-Bugs-To: http://trac.i2p2.de\n"
+"POT-Creation-Date: 2018-08-24 11:47+0000\n"
+"PO-Revision-Date: 2018-08-24 11:51+0000\n"
+"Last-Translator: zzzi2p\n"
+"Language-Team: Azerbaijani "
+"(http://www.transifex.com/otf/I2P/language/az/)\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 1.3\n"
+
+#: i2p2www/pages/site/docs/index.html:2 i2p2www/pages/site/docs/index.html:23
+msgid "Index to Technical Documentation"
+msgstr "Texniki sənədlər üçün indeks"
+
+#: i2p2www/pages/site/docs/index.html:3 i2p2www/pages/site/docs/naming.html:3
+#: i2p2www/pages/site/docs/transport/index.html:3
+#: i2p2www/pages/site/docs/transport/ntcp.html:3
+#: i2p2www/pages/site/docs/transport/ssu.html:3
+msgid "June 2018"
+msgstr ""
+
+#: i2p2www/pages/site/docs/index.html:6
+msgid "Following is an index to the technical documentation for I2P."
+msgstr ""
+
+#: i2p2www/pages/site/docs/index.html:10
+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:17
+#, 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"
+"<a href=\"%(trac)s\">enter a ticket identifying the problem</a>."
+msgstr ""
+
+#: i2p2www/pages/site/docs/index.html:25 i2p2www/pages/site/docs/naming.html:6
+#: i2p2www/pages/site/docs/api/bob.html:42
+#: i2p2www/pages/site/docs/api/i2ptunnel.html:7
+#: i2p2www/pages/site/docs/api/streaming.html:6
+#: i2p2www/pages/site/docs/applications/embedding.html:7
+#: i2p2www/pages/site/docs/applications/managed-clients.html:7
+#: 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:9
+#: i2p2www/pages/site/docs/how/tech-intro.html:93
+#: i2p2www/pages/site/docs/how/tunnel-routing.html:6
+#: i2p2www/pages/site/docs/tunnels/implementation.html:67
+#: i2p2www/pages/site/docs/tunnels/unidirectional.html:6
+msgid "Overview"
+msgstr "İcmal"
+
+#: i2p2www/pages/site/docs/index.html:27
+msgid "Technical Introduction"
+msgstr "Texniki giriş"
+
+#: i2p2www/pages/site/docs/index.html:28
+msgid "A Less-Technical Introduction"
+msgstr "Daha az texniki giriş"
+
+#: i2p2www/pages/site/docs/index.html:29
+msgid "Threat model and analysis"
+msgstr "Təhdid modeli və təhlili"
+
+#: i2p2www/pages/site/docs/index.html:30
+msgid "Comparisons to other anonymous networks"
+msgstr "Digər anonim şəbəkələrlə müqayisə"
+
+#: i2p2www/pages/site/docs/index.html:31
+msgid "Specifications"
+msgstr "Xüsusiyyətlər"
+
+#: i2p2www/pages/site/docs/index.html:32
+msgid "Protocol stack chart"
+msgstr "Protokol yığını diaqramı"
+
+#: i2p2www/pages/site/docs/index.html:33
+msgid "Papers on I2P"
+msgstr "I2P haqqında məqalələr"
+
+#: i2p2www/pages/site/docs/index.html:34
+msgid "Presentations, articles, tutorials, videos, and interviews"
+msgstr "Təqdimatlar, məqalələr, dərslər, videolar və müsahibələr"
+
+#: i2p2www/pages/site/docs/index.html:35
+#, python-format
+msgid ""
+"<a href=\"%(pdf)s\">Invisible Internet Project (I2P) Project Overview</a>"
+" August 28, 2003 (pdf)"
+msgstr ""
+"<a href=\"%(pdf)s\"> Invisible Internet Project (I2P) layihəsinin icmalı "
+"</a> 28 Avqust, 2003 (pdf)"
+
+#: i2p2www/pages/site/docs/index.html:38
+msgid "Application-Layer Topics"
+msgstr "Tətbiq Lay mövzuları"
+
+#: i2p2www/pages/site/docs/index.html:41 i2p2www/pages/site/docs/naming.html:2
+msgid "Naming and Addressbook"
+msgstr "Adlandırma və Ünvan kitabçası"
+
+#: i2p2www/pages/site/docs/index.html:42
+msgid "Plugins Overview"
+msgstr "Qoşmaların icmalı"
+
+#: i2p2www/pages/site/docs/index.html:43
+msgid "Plugin Specification"
+msgstr "Qoşma xüsusiyyətləri"
+
+#: i2p2www/pages/site/docs/index.html:44
+#: i2p2www/pages/site/docs/applications/managed-clients.html:2
+#: i2p2www/pages/site/docs/applications/managed-clients.html:20
+msgid "Managed Clients"
+msgstr "İdarə olunan müştərilər"
+
+#: i2p2www/pages/site/docs/index.html:45 i2p2www/pages/site/docs/index.html:231
+msgid "Embedding the router in your application"
+msgstr "Tətbiqinizə istiqamətləndirici daxil edilir"
+
+#: i2p2www/pages/site/docs/index.html:46
+#: i2p2www/pages/site/docs/applications/bittorrent.html:2
+msgid "Bittorrent over I2P"
+msgstr "Bittorrent vasitəsilə I2P"
+
+#: i2p2www/pages/site/docs/index.html:47
+msgid "I2PControl Plugin API"
+msgstr "I2PControl Plugin API"
+
+#: i2p2www/pages/site/docs/index.html:48
+msgid "hostsdb.blockfile Format"
+msgstr "hostsdb.blockfile Format"
+
+#: i2p2www/pages/site/docs/index.html:49 i2p2www/pages/site/docs/index.html:197
+msgid "Configuration File Format"
+msgstr "Quraşdırma fayl formatı"
+
+#: i2p2www/pages/site/docs/index.html:52
+msgid "Application Layer API and Protocols"
+msgstr "APİ Tətbiq layı və  protokollar"
+
+#: i2p2www/pages/site/docs/index.html:53
+msgid ""
+"High-level, easy-to-use APIs for applications written in any language to "
+"send and receive data."
+msgstr ""
+"Data göndərmək və qəbul etmək üçün hər hansı bir dildə yazılmış tətbiqlər"
+" üçün yüksək səviyyəli, asan istifadəli API-lər."
+
+#: i2p2www/pages/site/docs/index.html:55
+msgid "Application Development Overview and Guide"
+msgstr "Tətbiq İnkişafı İcmalı və Bələdçi"
+
+#: i2p2www/pages/site/docs/index.html:59
+#: i2p2www/pages/site/docs/api/i2ptunnel.html:51
+msgid "I2PTunnel Configuration"
+msgstr "I2PTunnel quraşdırması"
+
+#: i2p2www/pages/site/docs/index.html:75
+msgid "SAM Protocol"
+msgstr "SAM Protokol"
+
+#: i2p2www/pages/site/docs/index.html:77
+msgid "SAMv2 Protocol"
+msgstr "SAMv2 Protokol"
+
+#: i2p2www/pages/site/docs/index.html:79
+msgid "SAMv3 Protocol"
+msgstr "SAMv3 Protokol"
+
+#: i2p2www/pages/site/docs/index.html:81
+msgid "BOB Protocol"
+msgstr "BOB Protokol"
+
+#: i2p2www/pages/site/docs/index.html:84
+msgid "End-to-End Transport API and Protocols"
+msgstr "İkitərəfli Nəqliyyat API və protokollar"
+
+#: i2p2www/pages/site/docs/index.html:85
+msgid ""
+"The end-to-end protocols used by clients for reliable and unreliable "
+"communication."
+msgstr ""
+"İkitərəfli protokollar müştərilər tərəfindən etibarlı və etibarsız "
+"əlaqələr üçün istifadə olunur."
+
+#: i2p2www/pages/site/docs/index.html:87
+#: i2p2www/pages/site/docs/api/streaming.html:2
+msgid "Streaming Library"
+msgstr "Axın Kitabxanası"
+
+#: i2p2www/pages/site/docs/index.html:89
+msgid "Streaming Protocol Specification"
+msgstr "Axın protokolunda xüsusiyyət"
+
+#: i2p2www/pages/site/docs/index.html:91
+msgid "Streaming Javadoc"
+msgstr "Javadoc axını"
+
+#: i2p2www/pages/site/docs/index.html:93
+#: i2p2www/pages/site/docs/api/datagrams.html:2
+msgid "Datagrams"
+msgstr "Dataqtamlar"
+
+#: i2p2www/pages/site/docs/index.html:95
+msgid "Datagram Javadoc"
+msgstr "Datagram Javadoc"
+
+#: i2p2www/pages/site/docs/index.html:98
+msgid "Client-to-Router Interface API and Protocol"
+msgstr ""
+
+#: i2p2www/pages/site/docs/index.html:99
+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:104
+msgid "I2CP - I2P Control Protocol / API overview"
+msgstr ""
+
+#: i2p2www/pages/site/docs/index.html:106
+msgid "I2CP Specification"
+msgstr ""
+
+#: i2p2www/pages/site/docs/index.html:108
+msgid "I2CP API Javadoc"
+msgstr ""
+
+#: i2p2www/pages/site/docs/index.html:110
+#: i2p2www/pages/site/docs/index.html:140
+msgid "Common data structures specification"
+msgstr ""
+
+#: i2p2www/pages/site/docs/index.html:112
+#: i2p2www/pages/site/docs/index.html:142
+msgid "Data Structures Javadoc"
+msgstr ""
+
+#: i2p2www/pages/site/docs/index.html:115
+msgid "End-to-End Encryption"
+msgstr ""
+
+#: i2p2www/pages/site/docs/index.html:116
+msgid "How client messages are end-to-end encrypted by the router."
+msgstr ""
+
+#: i2p2www/pages/site/docs/index.html:118
+msgid "ElGamal/AES+SessionTag encryption"
+msgstr ""
+
+#: i2p2www/pages/site/docs/index.html:119
+#: i2p2www/pages/site/docs/index.html:153
+msgid "ElGamal and AES cryptography details"
+msgstr ""
+
+#: i2p2www/pages/site/docs/index.html:122
+#: i2p2www/pages/site/docs/how/tech-intro.html:11
+#: i2p2www/pages/site/docs/how/tech-intro.html:325
+msgid "Network Database"
+msgstr ""
+
+#: i2p2www/pages/site/docs/index.html:123
+msgid ""
+"Distributed storage and retrieval of information about routers and "
+"clients."
+msgstr ""
+
+#: i2p2www/pages/site/docs/index.html:125
+msgid "Network database overview, details, and threat analysis"
+msgstr ""
+
+#: i2p2www/pages/site/docs/index.html:126
+msgid "Cryptographic hashes"
+msgstr ""
+
+#: i2p2www/pages/site/docs/index.html:127
+msgid "Cryptographic signatures"
+msgstr ""
+
+#: i2p2www/pages/site/docs/index.html:128
+#: i2p2www/pages/site/docs/index.html:189
+msgid "Router reseed specification"
+msgstr ""
+
+#: i2p2www/pages/site/docs/index.html:131
+msgid "Router Message Protocol"
+msgstr ""
+
+#: i2p2www/pages/site/docs/index.html:132
+msgid ""
+"I2P is a message-oriented router. The messages sent between routers are "
+"defined by the I2NP protocol."
+msgstr ""
+
+#: i2p2www/pages/site/docs/index.html:134
+msgid "I2NP - I2P Network Protocol Overview"
+msgstr ""
+
+#: i2p2www/pages/site/docs/index.html:136
+msgid "I2NP Specification"
+msgstr ""
+
+#: i2p2www/pages/site/docs/index.html:138
+msgid "I2NP Javadoc"
+msgstr ""
+
+#: i2p2www/pages/site/docs/index.html:145
+#: i2p2www/pages/site/docs/how/tech-intro.html:10
+#: i2p2www/pages/site/docs/how/tech-intro.html:224
+msgid "Tunnels"
+msgstr "Tunellər"
+
+#: i2p2www/pages/site/docs/index.html:146
+msgid ""
+"Selecting peers, requesting tunnels through those peers, and encrypting "
+"and routing messages through these tunnels."
+msgstr ""
+
+#: i2p2www/pages/site/docs/index.html:148
+msgid "Peer profiling and selection"
+msgstr ""
+
+#: i2p2www/pages/site/docs/index.html:149
+msgid "Tunnel routing overview"
+msgstr ""
+
+#: i2p2www/pages/site/docs/index.html:150
+msgid "Garlic routing and \"garlic\" terminology"
+msgstr ""
+
+#: i2p2www/pages/site/docs/index.html:151
+msgid "Tunnel building and encryption"
+msgstr ""
+
+#: i2p2www/pages/site/docs/index.html:152
+msgid "ElGamal/AES"
+msgstr ""
+
+#: i2p2www/pages/site/docs/index.html:152
+msgid "for build request encryption"
+msgstr ""
+
+#: i2p2www/pages/site/docs/index.html:154
+msgid "Tunnel building specification"
+msgstr ""
+
+#: i2p2www/pages/site/docs/index.html:155
+msgid "Low-level tunnel message specification"
+msgstr ""
+
+#: i2p2www/pages/site/docs/index.html:156
+#: i2p2www/pages/site/docs/tunnels/unidirectional.html:2
+msgid "Unidirectional Tunnels"
+msgstr ""
+
+#: i2p2www/pages/site/docs/index.html:157
+#: 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:158
+msgid "2009 paper (pdf), not current but still generally accurate"
+msgstr ""
+
+#: i2p2www/pages/site/docs/index.html:161
+msgid "Transport Layer"
+msgstr ""
+
+#: i2p2www/pages/site/docs/index.html:162
+msgid "The protocols for direct (point-to-point) router to router communication."
+msgstr ""
+
+#: i2p2www/pages/site/docs/index.html:164
+msgid "Transport layer overview"
+msgstr ""
+
+#: i2p2www/pages/site/docs/index.html:166
+msgid "TCP-based transport overview and specification"
+msgstr ""
+
+#: i2p2www/pages/site/docs/index.html:168
+msgid "NTCP2 specification"
+msgstr ""
+
+#: i2p2www/pages/site/docs/index.html:170
+msgid "UDP-based transport overview"
+msgstr ""
+
+#: i2p2www/pages/site/docs/index.html:172
+msgid "SSU specification"
+msgstr ""
+
+#: i2p2www/pages/site/docs/index.html:174
+msgid "NTCP transport encryption"
+msgstr ""
+
+#: i2p2www/pages/site/docs/index.html:176
+msgid "SSU transport encryption"
+msgstr ""
+
+#: i2p2www/pages/site/docs/index.html:178
+msgid "Transport Javadoc"
+msgstr ""
+
+#: i2p2www/pages/site/docs/index.html:180
+msgid "NTCP Javadoc"
+msgstr ""
+
+#: i2p2www/pages/site/docs/index.html:182
+msgid "SSU Javadoc"
+msgstr ""
+
+#: i2p2www/pages/site/docs/index.html:185
+msgid "Other Router Topics"
+msgstr ""
+
+#: i2p2www/pages/site/docs/index.html:187
+msgid "Router software updates"
+msgstr ""
+
+#: i2p2www/pages/site/docs/index.html:191
+msgid "Native BigInteger Library"
+msgstr ""
+
+#: i2p2www/pages/site/docs/index.html:193
+msgid "Time synchronization and NTP"
+msgstr ""
+
+#: i2p2www/pages/site/docs/index.html:195
+msgid "Performance"
+msgstr "Məhsuldarlıq"
+
+#: i2p2www/pages/site/docs/index.html:202
+msgid "Developer's Guides and Resources"
+msgstr ""
+
+#: i2p2www/pages/site/docs/index.html:204
+msgid "New Developer's Guide"
+msgstr ""
+
+#: i2p2www/pages/site/docs/index.html:206
+msgid "New Translator's Guide"
+msgstr ""
+
+#: i2p2www/pages/site/docs/index.html:208
+msgid "Monotone Guide"
+msgstr ""
+
+#: i2p2www/pages/site/docs/index.html:210
+msgid "Developer Guidelines"
+msgstr ""
+
+#: i2p2www/pages/site/docs/index.html:212
+msgid "Javadocs on the standard internet:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/index.html:213
+#: i2p2www/pages/site/docs/index.html:219
+#: i2p2www/pages/site/docs/index.html:221
+#: i2p2www/pages/site/docs/index.html:223
+#, python-format
+msgid "Server %(num)s"
+msgstr ""
+
+#: i2p2www/pages/site/docs/index.html:214
+#: i2p2www/pages/site/docs/index.html:227
+msgid ""
+"Note: always verify that javadocs are current by checking the release "
+"number."
+msgstr ""
+
+#: i2p2www/pages/site/docs/index.html:216
+msgid "Javadocs inside I2P:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/index.html:229
+msgid "Proposals"
+msgstr ""
+
+#: i2p2www/pages/site/docs/index.html:233
+msgid "How to Set up a Reseed Server"
+msgstr ""
+
+#: i2p2www/pages/site/docs/index.html:235
+msgid "Ports used by I2P"
+msgstr ""
+
+#: i2p2www/pages/site/docs/index.html:237
+msgid "Automatic updates to development builds inside I2P"
+msgstr ""
+
+#: i2p2www/pages/site/docs/index.html:239
+msgid "Updating the wrapper manually"
+msgstr ""
+
+#: i2p2www/pages/site/docs/index.html:241
+msgid "User forum"
+msgstr ""
+
+#: i2p2www/pages/site/docs/index.html:243
+msgid "Developer forum inside I2P"
+msgstr ""
+
+#: i2p2www/pages/site/docs/index.html:245
+msgid "Bug tracker"
+msgstr "Xəta indikatoru"
+
+#: i2p2www/pages/site/docs/index.html:248
+msgid "Viewmtn inside I2P"
+msgstr ""
+
+#: i2p2www/pages/site/docs/index.html:251
+msgid "I2P Source exported to GitHub"
+msgstr ""
+
+#: i2p2www/pages/site/docs/index.html:253
+msgid "I2P Source Git Repo inside I2P"
+msgstr ""
+
+#: i2p2www/pages/site/docs/index.html:255
+msgid "Source translation at Transifex"
+msgstr ""
+
+#: i2p2www/pages/site/docs/index.html:257
+msgid "Roadmap"
+msgstr "Yol xəritəsi"
+
+#: i2p2www/pages/site/docs/index.html:259
+msgid "To Do List"
+msgstr ""
+
+#: i2p2www/pages/site/docs/index.html:259
+msgid "not current"
+msgstr ""
+
+#: i2p2www/pages/site/docs/naming.html:8
+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 <a href=\"#addressbook\">addressbook</a>. \n"
+"I2P also supports <a href=\"#base32\">Base32 hostnames</a> similar to "
+"Tor's .onion addresses."
+msgstr ""
+
+#: i2p2www/pages/site/docs/naming.html:15
+msgid ""
+"The addressbook is a web-of-trust\n"
+"driven secure, distributed, and human readable naming system, sacrificing"
+" only\n"
+"the call for all human readable names to be globally unique by mandating "
+"only\n"
+"local uniqueness.  While all messages in I2P are cryptographically "
+"addressed\n"
+"by their destination, different people can have local addressbook entries"
+" for\n"
+"\"Alice\" which refer to different destinations.  People can still "
+"discover new\n"
+"names by importing published addressbooks of peers specified in their web"
+" of trust,\n"
+"by adding in the entries provided through a third party, or (if some "
+"people organize\n"
+"a series of published addressbooks using a first come first serve "
+"registration\n"
+"system) people can choose to treat these addressbooks as name servers, "
+"emulating\n"
+"traditional DNS."
+msgstr ""
+
+#: i2p2www/pages/site/docs/naming.html:29
+#, python-format
+msgid ""
+"NOTE: For the reasoning behind the I2P naming system, common arguments "
+"against it\n"
+"and possible alternatives see the <a href=\"%(namingdiscussion)s\">naming"
+" discussion</a>\n"
+"page."
+msgstr ""
+
+#: i2p2www/pages/site/docs/naming.html:36
+msgid "Naming System Components"
+msgstr ""
+
+#: i2p2www/pages/site/docs/naming.html:38
+msgid ""
+"There is no central naming authority in I2P.\n"
+"All hostnames are local."
+msgstr ""
+
+#: i2p2www/pages/site/docs/naming.html:43
+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:51
+msgid ""
+"The local <a href=\"#lookup\">naming service</a> which does lookups\n"
+"and also handles <a href=\"#base32\">Base32 hostnames</a>."
+msgstr ""
+
+#: i2p2www/pages/site/docs/naming.html:55
+msgid ""
+"The <a href=\"#httpproxy\">HTTP proxy</a> which asks the router for "
+"lookups and points\n"
+"the user to remote jump services to assist with failed lookups."
+msgstr ""
+
+#: i2p2www/pages/site/docs/naming.html:59
+msgid ""
+"HTTP <a href=\"#add-services\">host-add forms</a> which allow users to "
+"add hosts to their local hosts.txt"
+msgstr ""
+
+#: i2p2www/pages/site/docs/naming.html:62
+msgid ""
+"HTTP <a href=\"#jump-services\">jump services</a> which provide their own"
+" lookups and redirection."
+msgstr ""
+
+#: i2p2www/pages/site/docs/naming.html:65
+msgid ""
+"The <a href=\"#addressbook\">addressbook</a> application which merges "
+"external\n"
+"host lists, retrieved via HTTP, with the local list."
+msgstr ""
+
+#: i2p2www/pages/site/docs/naming.html:69
+msgid ""
+"The <a href=\"#susidns\">SusiDNS</a> 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:76
+msgid "Naming Services"
+msgstr ""
+
+#: i2p2www/pages/site/docs/naming.html:78
+#, 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 3-or-more byte certificate, which in Base64 representation is 516 "
+"or more bytes.\n"
+"Non-null <a href=\"%(namingdiscussion)s#certificates\">Certificates</a> "
+"are in use now\n"
+"for signature type indication.\n"
+"Therefore, certificates in recently-generated destinations are more than "
+"3 bytes."
+msgstr ""
+
+#: i2p2www/pages/site/docs/naming.html:87
+msgid ""
+"If an application (i2ptunnel or the HTTP proxy) wishes to access\n"
+"a destination by name, the router does a very simple local lookup\n"
+"to resolve that name."
+msgstr ""
+
+#: i2p2www/pages/site/docs/naming.html:93
+msgid "Hosts.txt Naming Service"
+msgstr ""
+
+#: i2p2www/pages/site/docs/naming.html:95
+msgid ""
+"The hosts.txt Naming Service does a simple linear search through\n"
+"text files. This naming service was the default until\n"
+"release 0.8.8 when it was replaced by the Blockfile Naming Service.\n"
+"The hosts.txt format had become too slow after the file grew to thousands"
+" of entries."
+msgstr ""
+
+#: i2p2www/pages/site/docs/naming.html:102
+#, python-format
+msgid ""
+"It does a linear search through three local files, in order, to\n"
+"look up host names and convert them to a 516-byte destination key.\n"
+"Each file is in a simple <a href=\"%(configuration)s\">configuration file"
+" format</a>, with hostname=base64, one per line.\n"
+"The files are:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/naming.html:114
+msgid "Blockfile Naming Service"
+msgstr ""
+
+#: i2p2www/pages/site/docs/naming.html:116
+msgid ""
+"The Blockfile Naming Service stores multiple \"addressbooks\" in a single"
+"\n"
+"database file named hostsdb.blockfile.\n"
+"This Naming Service is the default since release 0.8.8."
+msgstr ""
+
+#: i2p2www/pages/site/docs/naming.html:122
+#, python-format
+msgid ""
+"A blockfile is simply on-disk storage of multiple sorted maps (key-value "
+"pairs),\n"
+"implemented as skiplists.\n"
+"The blockfile format is specified on the <a "
+"href=\"%(blockfile)s\">Blockfile page</a>.\n"
+"It provides fast Destination lookup in a compact format. While the "
+"blockfile overhead is substantial,\n"
+"the destinations are stored in binary rather than in Base 64 as in the "
+"hosts.txt format.\n"
+"In addition, the blockfile provides the capability of arbitrary metadata "
+"storage\n"
+"(such as added date, source, and comments) for each entry to implement "
+"advanced addressbook features.\n"
+"The blockfile storage requirement is a modest increase over the hosts.txt"
+" format, and the blockfile provides\n"
+"approximately 10x reduction in lookup times."
+msgstr ""
+
+#: i2p2www/pages/site/docs/naming.html:134
+msgid ""
+"On creation, the naming service imports entries from the three files used"
+" by the hosts.txt Naming Service.\n"
+"The blockfile mimics the previous implementation by maintaining three "
+"maps that\n"
+"are searched in-order, named privatehosts.txt, userhosts.txt, and "
+"hosts.txt.\n"
+"It also maintains a reverse-lookup map to implement rapid reverse lookups."
+msgstr ""
+
+#: i2p2www/pages/site/docs/naming.html:141
+msgid "Other Naming Service Facilities"
+msgstr ""
+
+#: i2p2www/pages/site/docs/naming.html:143
+#, python-format
+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.\n"
+"Lookups are cached for a few minutes.\n"
+"Base 32 resolution is <a href=\"#base32\">described below</a>.\n"
+"For a full description of the Naming Service API see the\n"
+"<a href=\"%(nsjavadocs)s\">Naming Service Javadocs</a>.\n"
+"This API was significantly expanded in release 0.8.7 to provide\n"
+"adds and removes, storage of arbitrary properties with the hostname,\n"
+"and other features."
+msgstr ""
+
+#: i2p2www/pages/site/docs/naming.html:156
+msgid "Alternatives and Experimental Naming Services"
+msgstr ""
+
+#: i2p2www/pages/site/docs/naming.html:158
+#, python-format
+msgid ""
+"The naming service is specified with the configuration property "
+"<tt>i2p.naming.impl=class</tt>.\n"
+"Other implementations are possible. For example,\n"
+"there is an experimental facility for real-time lookups (a la DNS) over "
+"the network within the router.\n"
+"For more information see the <a "
+"href=\"%(namingdiscussion)s#alternatives\">alternatives on the discussion"
+" page</a>."
+msgstr ""
+
+#: i2p2www/pages/site/docs/naming.html:165
+msgid ""
+"The HTTP proxy does a lookup via the router for all hostnames ending in "
+"'.i2p'.\n"
+"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:171
+#, python-format
+msgid ""
+"We have <a href=\"%(i2ptld)s\">applied to reserve the .i2p TLD</a>\n"
+"following the procedures specified in <a href=\"%(rfc6761)s\">RFC "
+"6761</a>."
+msgstr ""
+
+#: i2p2www/pages/site/docs/naming.html:177
+msgid ""
+"If the router fails to resolve the hostname, the HTTP proxy returns\n"
+"an error page to the user with links to several \"jump\" services.\n"
+"See below for details."
+msgstr ""
+
+#: i2p2www/pages/site/docs/naming.html:183
+msgid "Addressbook"
+msgstr "Ünvan kitabçası"
+
+#: i2p2www/pages/site/docs/naming.html:184
+msgid "Incoming Subscriptions and Merging"
+msgstr ""
+
+#: i2p2www/pages/site/docs/naming.html:186
+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:194
+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:202
+msgid ""
+"For this reason, the only subscription configured by\n"
+"default is <code>http://i2p-projekt.i2p/hosts.txt "
+"(http://udhdrtrcetjm5sxzskjyr5ztpeszydbh4dpl3pl4utgqqw2v4jna.b32.i2p/hosts.txt)</code>,"
+" \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 <a "
+"href=\"#susidns\">SusiDNS</a>)."
+msgstr ""
+
+#: i2p2www/pages/site/docs/naming.html:211
+msgid "Some other public addressbook subscription links:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/naming.html:218
+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:223
+#: i2p2www/pages/site/docs/naming.html:235
+msgid "Naming Rules"
+msgstr ""
+
+#: i2p2www/pages/site/docs/naming.html:224
+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:239
+msgid "Names are converted to lower case on import."
+msgstr ""
+
+#: i2p2www/pages/site/docs/naming.html:243
+msgid ""
+"Names are checked for conflict with existing names in the existing "
+"userhosts.txt and hosts.txt\n"
+"(but not privatehosts.txt) after conversion to lower case."
+msgstr ""
+
+#: i2p2www/pages/site/docs/naming.html:248
+msgid "Must contain only [a-z] [0-9] '.' and '-' after conversion to lower case."
+msgstr ""
+
+#: i2p2www/pages/site/docs/naming.html:252
+msgid "Must not start with '.' or '-'."
+msgstr ""
+
+#: i2p2www/pages/site/docs/naming.html:256
+msgid "Must end with '.i2p'."
+msgstr ""
+
+#: i2p2www/pages/site/docs/naming.html:260
+msgid "67 characters maximum, including the '.i2p'."
+msgstr ""
+
+#: i2p2www/pages/site/docs/naming.html:264
+msgid "Must not contain '..'."
+msgstr ""
+
+#: i2p2www/pages/site/docs/naming.html:268
+msgid "Must not contain '.-' or '-.' (as of 0.6.1.33)."
+msgstr ""
+
+#: i2p2www/pages/site/docs/naming.html:272
+msgid "Must not contain '--' except in 'xn--' for IDN."
+msgstr ""
+
+#: i2p2www/pages/site/docs/naming.html:276
+msgid ""
+"Base32 hostnames (*.b32.i2p) are reserved for base 32 use and so are not "
+"allowed to be imported."
+msgstr ""
+
+#: i2p2www/pages/site/docs/naming.html:280
+msgid ""
+"Certain hostnames reserved for project use are not allowed\n"
+"(proxy.i2p, router.i2p, console.i2p, *.proxy.i2p, *.router.i2p, "
+"*.console.i2p, and others)"
+msgstr ""
+
+#: i2p2www/pages/site/docs/naming.html:285
+msgid "Keys are checked for base64 validity."
+msgstr ""
+
+#: i2p2www/pages/site/docs/naming.html:289
+msgid ""
+"Keys are checked for conflict with existing keys in hosts.txt (but not "
+"privatehosts.txt)."
+msgstr ""
+
+#: i2p2www/pages/site/docs/naming.html:293
+msgid "Minimum key length 516 bytes."
+msgstr ""
+
+#: i2p2www/pages/site/docs/naming.html:297
+msgid "Maximum key length 616 bytes (to account for certs up to 100 bytes)."
+msgstr ""
+
+#: i2p2www/pages/site/docs/naming.html:302
+msgid ""
+"Any name received via subscription that passes all the checks is added "
+"via the local naming service."
+msgstr ""
+
+#: i2p2www/pages/site/docs/naming.html:306
+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:317
+msgid ""
+"International Domain Names (IDN) also work in i2p (using punycode 'xn--' "
+"form).\n"
+"To see IDN .i2p domain names rendered correctly in Firefox's location "
+"bar,\n"
+"add 'network.IDN.whitelist.i2p (boolean) = true' in about:config."
+msgstr ""
+
+#: i2p2www/pages/site/docs/naming.html:323
+msgid ""
+"As the addressbook application does not use privatehosts.txt at all, in "
+"practice\n"
+"this file is the only place where it is appropriate to place private "
+"aliases or\n"
+"\"pet names\" for sites already in hosts.txt."
+msgstr ""
+
+#: i2p2www/pages/site/docs/naming.html:329
+msgid "Advanced Subscription Feed Format"
+msgstr ""
+
+#: i2p2www/pages/site/docs/naming.html:337
+msgid "Outgoing Subscriptions"
+msgstr ""
+
+#: i2p2www/pages/site/docs/naming.html:338
+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:346
+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:353
+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:358
+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:367
+msgid "Host Add Services"
+msgstr ""
+
+#: i2p2www/pages/site/docs/naming.html:368
+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:375
+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:380
+msgid "A limit on number of 'subdomains'."
+msgstr ""
+
+#: i2p2www/pages/site/docs/naming.html:384
+msgid "Authorization for 'subdomains' through various methods."
+msgstr ""
+
+#: i2p2www/pages/site/docs/naming.html:388
+msgid "Hashcash or signed certificates."
+msgstr ""
+
+#: i2p2www/pages/site/docs/naming.html:392
+msgid "Editorial review of host names and/or content."
+msgstr ""
+
+#: i2p2www/pages/site/docs/naming.html:396
+msgid "Categorization of hosts by content."
+msgstr ""
+
+#: i2p2www/pages/site/docs/naming.html:400
+msgid "Reservation or rejection of certain host names."
+msgstr ""
+
+#: i2p2www/pages/site/docs/naming.html:404
+msgid "Restrictions on the number of names registered in a given time period."
+msgstr ""
+
+#: i2p2www/pages/site/docs/naming.html:408
+msgid "Delays between registration and publication."
+msgstr ""
+
+#: i2p2www/pages/site/docs/naming.html:412
+msgid "Requirement that the host be up for verification."
+msgstr ""
+
+#: i2p2www/pages/site/docs/naming.html:416
+msgid "Expiration and/or revocation."
+msgstr ""
+
+#: i2p2www/pages/site/docs/naming.html:420
+msgid "IDN spoof rejection."
+msgstr ""
+
+#: i2p2www/pages/site/docs/naming.html:425
+msgid "Jump Services"
+msgstr ""
+
+#: i2p2www/pages/site/docs/naming.html:426
+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 "
+"<code>?i2paddresshelper=key</code>\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:436
+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:442
+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:448
+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:454
+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:460
+msgid "Base32 Names"
+msgstr ""
+
+#: i2p2www/pages/site/docs/naming.html:461
+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: "
+"<code>ukeu3k5oycgaauneqgtnvselmt4yemvoilkln7jpvamvfx7dnkdq.b32.i2p</code>"
+msgstr ""
+
+#: i2p2www/pages/site/docs/naming.html:468
+#, python-format
+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"
+"Tor has recently published a\n"
+"<a href=\"https://blog.torproject.org/blog/tor-weekly-news-%E2%80%94"
+"-december-4th-2013\">proposal</a>\n"
+"to convert to an identical format of {52 chars}.onion for their hidden "
+"services.\n"
+"Base32 is implemented in the naming service, which queries the\n"
+"router over I2CP to lookup the LeaseSet to get the full Destination.\n"
+"Base32 lookups will only be successful when the Destination is up and "
+"publishing\n"
+"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:483
+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
+msgid "Plugins"
+msgstr "Qoşmalar"
+
+#: i2p2www/pages/site/docs/plugins.html:3
+msgid "June 2012"
+msgstr ""
+
+#: i2p2www/pages/site/docs/plugins.html:6
+msgid "General Information"
+msgstr ""
+
+#: i2p2www/pages/site/docs/plugins.html:7
+msgid ""
+"I2P includes a plugin architecture\n"
+"to support easy development and installation of additional software."
+msgstr ""
+
+#: i2p2www/pages/site/docs/plugins.html:12
+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:17
+msgid "Benefits to i2p users and app developers:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/plugins.html:22
+msgid "Easy distribution of applications"
+msgstr ""
+
+#: i2p2www/pages/site/docs/plugins.html:26
+msgid ""
+"Allows innovation and use of additional libraries without worrying about\n"
+"increasing the size of <code>i2pupdate.sud</code>"
+msgstr ""
+
+#: i2p2www/pages/site/docs/plugins.html:31
+msgid ""
+"Support large or special-purpose applications that would never be bundled"
+"\n"
+"with the I2P installation"
+msgstr ""
+
+#: i2p2www/pages/site/docs/plugins.html:36
+msgid "Cryptographically signed and verified applications"
+msgstr ""
+
+#: i2p2www/pages/site/docs/plugins.html:40
+msgid "Automatic updates of applications, just like for the router"
+msgstr ""
+
+#: i2p2www/pages/site/docs/plugins.html:44
+msgid ""
+"Separate initial install and update packages, if desired, for smaller "
+"update downloads"
+msgstr ""
+
+#: i2p2www/pages/site/docs/plugins.html:48
+msgid ""
+"One-click installation of applications. No more asking users to modify\n"
+"<code>wrapper.config</code> or <code>clients.config</code>"
+msgstr ""
+
+#: i2p2www/pages/site/docs/plugins.html:53
+msgid "Isolate applications from the base <code>$I2P</code> installation"
+msgstr ""
+
+#: i2p2www/pages/site/docs/plugins.html:57
+msgid ""
+"Automatic compatibility checking for I2P version, Java version, Jetty\n"
+"version, and previous installed application version"
+msgstr ""
+
+#: i2p2www/pages/site/docs/plugins.html:62
+msgid "Automatic link addition in console"
+msgstr ""
+
+#: i2p2www/pages/site/docs/plugins.html:66
+msgid ""
+"Automatic startup of application, including modifying classpath, without "
+"requiring a restart"
+msgstr ""
+
+#: i2p2www/pages/site/docs/plugins.html:70
+msgid "Automatic integration and startup of webapps into console Jetty instance"
+msgstr ""
+
+#: i2p2www/pages/site/docs/plugins.html:74
+#, python-format
+msgid ""
+"Facilitate creation of 'app stores' like the one at\n"
+"<a href=\"http://%(pluginsite)s\">%(pluginsite)s</a>"
+msgstr ""
+
+#: i2p2www/pages/site/docs/plugins.html:79
+msgid "One-click uninstall"
+msgstr ""
+
+#: i2p2www/pages/site/docs/plugins.html:83
+msgid "Language and theme packs for the console"
+msgstr ""
+
+#: i2p2www/pages/site/docs/plugins.html:87
+msgid "Bring detailed application information to the router console"
+msgstr ""
+
+#: i2p2www/pages/site/docs/plugins.html:91
+msgid "Non-java applications also supported"
+msgstr ""
+
+#: i2p2www/pages/site/docs/plugins.html:97
+msgid "Required I2P version"
+msgstr ""
+
+#: i2p2www/pages/site/docs/plugins.html:98
+msgid "0.7.12 or newer."
+msgstr ""
+
+#: i2p2www/pages/site/docs/plugins.html:100
+msgid "Installation"
+msgstr ""
+
+#: i2p2www/pages/site/docs/plugins.html:101
+msgid ""
+"To install and start a plugin, copy the <code>.xpi2p</code> install link "
+"to\n"
+"the form at the bottom of\n"
+"<a "
+"href=\"http://127.0.0.1:7657/configclients.jsp#plugin\">configclients.jsp"
+" in\n"
+"your router console</a> and click the \"install plugin\" button.  After a"
+"\n"
+"plugin is installed and started, a link to the plugin will usually appear"
+" at\n"
+"the top of your summary bar."
+msgstr ""
+
+#: i2p2www/pages/site/docs/plugins.html:110
+msgid ""
+"To update a plugin to the latest version, just click the update button on"
+"\n"
+"<a "
+"href=\"http://127.0.0.1:7657/configclients.jsp#plugin\">configclients.jsp</a>."
+"\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:120
+msgid "Development"
+msgstr ""
+
+#: i2p2www/pages/site/docs/plugins.html:121
+#, python-format
+msgid ""
+"See the latest <a href=\"%(pluginspec)s\">plugin specification</a> and "
+"the\n"
+"<a href=\"http://%(zzz)s/forums/16\">plugin forum</a> on %(zzz)s."
+msgstr ""
+
+#: i2p2www/pages/site/docs/plugins.html:126
+#, python-format
+msgid ""
+"See also the sources for plugins developed by various people.  Some "
+"plugins, such\n"
+"as <a href=\"http://%(pluginsite)s/plugins/snowman\">snowman</a>, were "
+"developed\n"
+"specifically as examples."
+msgstr ""
+
+#: i2p2www/pages/site/docs/plugins.html:132
+msgid ""
+"<b>Developers wanted!</b> Plugins are a great way to learn more about I2P"
+"\n"
+"or easily add some feature."
+msgstr ""
+
+#: i2p2www/pages/site/docs/plugins.html:137
+msgid "Getting Started"
+msgstr ""
+
+#: i2p2www/pages/site/docs/plugins.html:138
+#, python-format
+msgid ""
+"To create a plugin from an existing binary package you will need to get\n"
+"makeplugin.sh from <a href=\"%(url)s\">the i2p.scripts branch in "
+"monotone</a>."
+msgstr ""
+
+#: i2p2www/pages/site/docs/plugins.html:144
+msgid "Known Issues"
+msgstr ""
+
+#: i2p2www/pages/site/docs/plugins.html:145
+msgid ""
+"Note that the router's plugin architecture does <b>NOT</b> currently\n"
+"provide any additional security isolation or sandboxing of plugins."
+msgstr ""
+
+#: i2p2www/pages/site/docs/plugins.html:151
+msgid ""
+"Updates of a plugin with included jars (not wars) won't be recognized if\n"
+"the plugin was already run, as it requires class loader trickery to flush"
+" the\n"
+"class cache; a full router restart is required."
+msgstr ""
+
+#: i2p2www/pages/site/docs/plugins.html:157
+msgid "The stop button may be displayed even if there is nothing to stop."
+msgstr ""
+
+#: i2p2www/pages/site/docs/plugins.html:161
+msgid ""
+"Plugins running in a separate JVM create a <code>logs/</code> directory "
+"in\n"
+"<code>$CWD</code>."
+msgstr ""
+
+#: i2p2www/pages/site/docs/plugins.html:166
+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&mdash;there is no signing key authority."
+msgstr ""
+
+#: i2p2www/pages/site/docs/plugins.html:172
+msgid ""
+"When deleting a plugin, the directory is not always deleted, especially "
+"on\n"
+"Windows."
+msgstr ""
+
+#: i2p2www/pages/site/docs/plugins.html:177
+msgid ""
+"Installing a plugin requiring Java 1.6 on a Java 1.5 machine will result "
+"in a\n"
+"\"plugin is corrupt\" message if pack200 compression of the plugin file "
+"is used."
+msgstr ""
+
+#: i2p2www/pages/site/docs/plugins.html:182
+msgid "Theme and translation plugins are untested."
+msgstr ""
+
+#: i2p2www/pages/site/docs/plugins.html:186
+msgid "Disabling autostart doesn't always work."
+msgstr ""
+
+#: i2p2www/pages/site/docs/ports.html:2
+msgid "Ports Used by I2P"
+msgstr ""
+
+#: i2p2www/pages/site/docs/ports.html:3
+msgid "March 2018"
+msgstr ""
+
+#: 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 <a href=\"%(faq)s#ports\">the FAQ</a>.\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:56
+msgid "recommended spot for new plugins/applications"
+msgstr ""
+
+#: i2p2www/pages/site/docs/reseed.html:2
+msgid "Reseed Hosts"
+msgstr ""
+
+#: i2p2www/pages/site/docs/reseed.html:3
+#: i2p2www/pages/site/docs/how/elgamal-aes.html:3
+msgid "January 2016"
+msgstr "Yanvar 2016"
+
+#: i2p2www/pages/site/docs/reseed.html:8
+msgid "About Reseed hosts"
+msgstr ""
+
+#: i2p2www/pages/site/docs/reseed.html:10
+msgid ""
+"Reseed hosts are needed to for bootstrapping, that is, providing the "
+"initial set of I2P nodes for your I2P node to talk to. Depending on the "
+"status of your node it may need to bootstrap every now and then if many "
+"of the nodes it knows of aren't contactable."
+msgstr ""
+
+#: i2p2www/pages/site/docs/reseed.html:14
+msgid ""
+"Reseeding is done over an encrypted connection and all of the bootstrap "
+"information is signed by the reseed host you connect to, making it "
+"impossible for an unauthenticated source to provide you with false "
+"information."
+msgstr ""
+
+#: i2p2www/pages/site/docs/reseed.html:19
+msgid "Running a Reseed host"
+msgstr ""
+
+#: i2p2www/pages/site/docs/reseed.html:21
+msgid ""
+"The more reseed hosts that are run, the more resilient the I2P network "
+"becomes, and the harder it is to prevent users of I2P from connecting to "
+"the network."
+msgstr ""
+
+#: i2p2www/pages/site/docs/reseed.html:25
+msgid ""
+"There have also been cases where the reseed hosts we had, have been under"
+" heavy load due to botnet activities."
+msgstr ""
+
+#: i2p2www/pages/site/docs/reseed.html:33
+msgid "Thank you"
+msgstr ""
+
+#: i2p2www/pages/site/docs/reseed.html:35
+msgid ""
+"If you are running a reseed server, We would like to thank you for "
+"helping to\n"
+"make the I2P network stronger and more resilient than ever."
+msgstr ""
+
+#: i2p2www/pages/site/docs/reseed.html:41
+msgid "Thank you."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/bob.html:2
+msgid "BOB - Basic Open Bridge"
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/bob.html:3
+msgid "August 2016"
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/bob.html:12
+msgid "Technical differences from SAM (for the better?)"
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/bob.html:14
+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:23
+msgid ""
+"SAM has one connection that does everything, and you need to parse every "
+"packet."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/bob.html:27
+msgid ""
+"BOB does not hold keypair values, nor does the router.\n"
+"Your application holds the keypair values. \n"
+"This is to reduce any extra complexity in the router code, it also adds "
+"to\n"
+"your privacy."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/bob.html:34
+msgid "SAM router stores every keypair you ever make."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/bob.html:38
+msgid "Those are the important differences."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/bob.html:44
+msgid "<code>KEYS</code> = keypair public+private, these are BASE64"
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/bob.html:47
+msgid "<code>KEY</code> = public key, also BASE64"
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/bob.html:50
+msgid ""
+"<code>ERROR</code> as is implied returns the message <code>\"ERROR "
+"\"+DESCRIPTION+\"\\n\"</code>, where the <code>DESCRIPTION</code> is what"
+" went wrong."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/bob.html:53
+msgid ""
+"<code>OK</code> returns <code>\"OK\"</code>, and if data is to be "
+"returned, it is on the same line. <code>OK</code> means the command is "
+"finished."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/bob.html:56
+msgid ""
+"<code>DATA</code> lines contain information that you requested. There may"
+" be multiple <code>DATA</code> lines per request."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/bob.html:60
+msgid ""
+"<b>NOTE:</b> 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:66
+msgid "Connection and Version"
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/bob.html:68
+msgid ""
+"All BOB status output is by lines. Lines may be \\n or \\r\\n terminated,"
+" depending on the system.\n"
+"On connection, BOB outputs two lines:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/bob.html:78
+msgid "The current version is:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/bob.html:82
+msgid ""
+"Note that previous versions used upper-case hex digits and did not "
+"conform to I2P versioning standards.\n"
+"It is recommended that subsequent versions use digits 0-9 only."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/bob.html:87
+msgid "Version history"
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/bob.html:92
+msgid "Version"
+msgstr "Versiya"
+
+#: i2p2www/pages/site/docs/api/bob.html:93
+msgid "I2P Router Version"
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/bob.html:94
+msgid "Changes"
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/bob.html:97
+msgid "current version"
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/bob.html:100
+msgid "development versions"
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/bob.html:104
+msgid "Commands"
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/bob.html:106
+msgid ""
+"<b>PLEASE NOTE:</b>\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:112
+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:117
+msgid "COMMAND"
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/bob.html:117
+msgid "OPERAND"
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/bob.html:117
+msgid "RETURNS"
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/bob.html:145
+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:152
+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:164
+msgid "Examples"
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/bob.html:166
+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:174
+msgid "EXAMPLE SESSION DIALOGUE -- simple telnet 127.0.0.1 2827 works"
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/bob.html:175
+msgid "Application"
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/bob.html:176
+msgid "BOB's Command response."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/bob.html:178
+#: i2p2www/pages/site/docs/api/bob.html:192
+#: i2p2www/pages/site/docs/api/bob.html:212
+#: i2p2www/pages/site/docs/api/bob.html:322
+#: i2p2www/pages/site/docs/api/bob.html:334
+#: i2p2www/pages/site/docs/api/bob.html:349
+msgid "FROM"
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/bob.html:178
+#: i2p2www/pages/site/docs/api/bob.html:192
+#: i2p2www/pages/site/docs/api/bob.html:212
+#: i2p2www/pages/site/docs/api/bob.html:322
+#: i2p2www/pages/site/docs/api/bob.html:334
+#: i2p2www/pages/site/docs/api/bob.html:349
+msgid "TO"
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/bob.html:178
+#: i2p2www/pages/site/docs/api/bob.html:192
+#: i2p2www/pages/site/docs/api/bob.html:212
+#: i2p2www/pages/site/docs/api/bob.html:322
+#: i2p2www/pages/site/docs/api/bob.html:334
+#: i2p2www/pages/site/docs/api/bob.html:349
+msgid "DIALOGUE"
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/bob.html:187
+msgid "MAKE NOTE OF THE ABOVE DESTINATION KEY, YOURS WILL BE DIFFERENT!"
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/bob.html:201
+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 <code>CHARGEN</code> service on <code>19/TCP</code>."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/bob.html:207
+msgid "Now for the other half, so that we can actually contact this destination."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/bob.html:229
+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:236
+msgid ""
+"<b>NOTE:</b> The \"quit\" command in the command channel does NOT "
+"disconnect the tunnels like SAM."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/bob.html:253
+msgid "After a few virtual miles of this spew, press <code>Control-]</code>"
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/bob.html:265
+msgid "Here is what happened..."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/bob.html:273
+msgid "You can connect to EEPSITES too!"
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/bob.html:306
+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:313
+msgid "Let's put down our destinations now that we are all done with them."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/bob.html:317
+msgid "First, lets see what destination nicknames we have."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/bob.html:329
+msgid "Alright, there they are. First, let's remove \"mouth\"."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/bob.html:343
+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:362
+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:368
+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:375
+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:384
+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:3
+#: i2p2www/pages/site/docs/protocol/index.html:3
+msgid "August 2010"
+msgstr ""
+
+#: 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 <a href=\"%(i2cp)s\">I2CP</a> 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 <a href=\"%(streaming)s\">streaming library packets</a>,\n"
+"are an application-level construct.\n"
+"These protocols are independent of the low-level <a "
+"href=\"%(transports)s\">transports</a>;\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 ""
+
+#: i2p2www/pages/site/docs/api/datagrams.html:26
+#, python-format
+msgid ""
+"Applications written in Java may use the \n"
+"<a href=\"%(url)s\">datagram API</a>,\n"
+"while applications in other languages \n"
+"can use <a href=\"%(sam)s\">SAM</a>'s datagram support.\n"
+"There is also limited support in i2ptunnel in the <a "
+"href=\"%(socks)s\">SOCKS proxy</a>,\n"
+"the 'streamr' tunnel types, and udpTunnel classes."
+msgstr ""
+
+#: 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 ""
+
+#: 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"
+"<a href=\"%(elgamalaes)s\">ElGamal/AES</a>, 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 <a href=\"%(i2cp)s#format\">I2CP page</a>."
+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"
+"<a href=\"%(i2psession)s\">I2PSession API</a>\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"
+"<a href=\"%(i2psession)s\">I2PSession API</a>,\n"
+"as implemented in\n"
+"<a href=\"%(i2psessionmuxed)s\">I2PSessionMuxedImpl</a>."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/datagrams.html:93
+#: i2p2www/pages/site/docs/api/streaming.html:418
+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"
+"<a href=\"%(i2cp)s#format\">the I2CP layer</a>.\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:426
+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"
+"<a href=\"%(garlicrouting)s\">Garlic Message</a>).\n"
+"Message encapsulation is implemented in the underlying\n"
+"<a href=\"%(i2cp)s\">I2CP</a>,\n"
+"<a href=\"%(i2np)s\">I2NP</a>, and\n"
+"<a href=\"%(tunnelmessage)s\">tunnel message</a> 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/transport/ssu.html:650
+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:2
+msgid "I2PControl - Remote Control Service"
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:5
+#, python-format
+msgid ""
+"I2P enables a <a href=\"http://en.wikipedia.org/wiki/JSON-"
+"RPC\">JSONRPC2</a> interface via the plugin <a "
+"href=\"%(itoopie)s\">I2PControl</a>.\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 <a href=\"http://software.dzhuvinov.com"
+"/json-rpc-2.0.html\">JSON-RPC 2.0</a>.  \n"
+"A list of implementations of JSON-RPC for various languages can be found "
+"at <a href=\"http://json-rpc.org/wiki/implementations\">the JSON-RPC "
+"wiki</a>."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:12
+msgid "I2PControl is by default listening on https://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:20
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:45
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:58
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:68
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:77
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:87
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:102
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:155
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:176
+msgid "Request:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:33
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:50
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:62
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:72
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:82
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:93
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:119
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:165
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:191
+msgid "Response:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:44
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:46
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:47
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:51
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:52
+#: i2p2www/pages/site/docs/protocol/i2cp.html:108
+#: i2p2www/pages/site/docs/protocol/i2cp.html:483
+msgid "Description"
+msgstr "Açıqlama"
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:48
+msgid ""
+"Token used for authenticating every request (excluding the 'Authenticate'"
+" RPC method)"
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:56
+msgid "Implemented methods"
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:57
+msgid ""
+"Creates and returns an authentication token used for further "
+"communication."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:59
+msgid "The version of the I2PControl API used by the client."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:60
+msgid "The password used for authenticating against the remote server."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:63
+msgid "The primary I2PControl API version implemented by the server."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:64
+msgid "The token used for further communication."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:67
+msgid "Echoes the value of the echo key, used for debugging and testing."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:69
+msgid "Value will be returned in response."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:70
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:80
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:91
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:117
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:163
+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:73
+msgid "Value of the key 'echo' in the request."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:76
+msgid ""
+"Fetches rateStat from router statManager. Creates stat if not already "
+"created."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:78
+#, python-format
+msgid ""
+"Determines which rateStat to fetch, see <a "
+"href=\"%(ratestats)s\">ratestats</a>."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:79
+msgid "Determines which period a stat is fetched for. Measured in ms."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:83
+msgid "Returns the average value for the reuested rateStat and period."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:86
+msgid "Manages I2PControl. Ports, passwords and the like."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:88
+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:89
+msgid ""
+"Sets a new password for I2PControl, all Authentication tokens will be "
+"revoked."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:90
+msgid "Switches which port I2PControl will listen for connections on."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:94
+msgid "Returned if address was changed"
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:95
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:96
+msgid "Returned if setting was changed"
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:97
+msgid "Returns true if any changes were made."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:98
+msgid "Returns true if any changes requiring a restart to take effect were made."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:101
+msgid "Fetches basic information about the I2P router. Uptime, version etc."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:120
+msgid "What the status of the router is."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:121
+msgid "What the uptime of the router is in ms."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:122
+msgid "What version of I2P the router is running."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:123
+msgid "The 1 second average inbound bandwidth in Bps."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:124
+msgid "The 15 second average inbound bandwidth in Bps."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:125
+msgid "The 1 second average outbound bandwidth in Bps."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:126
+msgid "The 15 second average outbound bandwidth in Bps."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:127
+msgid "What the current network status is. According to the below enum:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:146
+msgid "How many tunnels on the I2P net are we participating in."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:147
+msgid "How many peers have we communicated with recently."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:148
+msgid "How many peers are considered 'fast'."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:149
+msgid "How many peers are considered 'high capacity'."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:150
+msgid "Is the router reseeding hosts to its NetDB?"
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:151
+msgid "How many peers are known to us (listed in our NetDB)."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:154
+msgid "Manages I2P router restart/shutdown."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:156
+msgid "<b>Blocking</b>. Initiates a search for signed updates."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:157
+msgid ""
+"Initiates a router reseed, fetching peers into our NetDB from a remote "
+"host."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:158
+msgid "Restarts the router."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:159
+msgid ""
+"Restarts the router gracefully (waits for participating tunnels to "
+"expire)."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:160
+msgid "Shuts down the router."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:161
+msgid ""
+"Shuts down the router gracefully (waits for participating tunnels to "
+"expire)."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:162
+msgid "Initiates a router update from signed sources."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:166
+msgid "<b>Blocking</b>. Returns true iff a signed update has been found."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:167
+msgid "If requested, verifies that a reseed has been initiated."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:168
+msgid "If requested, verifies that a restart has been initiated."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:169
+msgid "If requested, verifies that a graceful restart has been initiated."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:170
+msgid "If requested, verifies that a shutdown has been initiated"
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:171
+msgid "If requested, verifies that a graceful shutdown has been initiated"
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:172
+msgid "<b>Blocking</b>. If requested, returns the status of the the update"
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:175
+msgid "Fetches or sets various network related settings. Ports, addresses etc."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:177
+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:178
+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:179
+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:180
+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:181
+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:182
+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:183
+msgid "What ip has been detected by the UDP transport."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:184
+msgid "Is UPnP enabled. If null is submitted, current setting will be returned."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:185
+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:186
+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:187
+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:188
+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:189
+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:192
+msgid "If requested, returns the port used for the TCP transport."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:193
+msgid "If requested, returns the hostname used for the TCP transport."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:194
+msgid ""
+"If requested, returns the method used for automatically detecting ip for "
+"the TCP transport."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:195
+msgid "If requested, returns the port used for the UDP transport."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:196
+msgid "If requested, returns the hostname used for the UDP transport."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:197
+msgid ""
+"If requested, returns methods used for detecting the ip address of the "
+"UDP transport."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:198
+msgid "If requested, returns what ip has been detected by the UDP transport."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:199
+msgid "If requested, returns the UPNP setting."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:200
+msgid ""
+"If requested, returns how many percent of bandwidth is usable for "
+"participating tunnels."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:201
+msgid "If requested, returns how many KB/s of inbound bandwidth is allowed."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:202
+msgid "If requested, returns how many KB/s of outbound bandwidth is allowed."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:203
+msgid "If requested, returns the laptop mode."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:204
+msgid "Have the provided settings been saved."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:205
+msgid "Is a restart needed for the new settings to be used."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:208
+msgid "Allows for manipulation of advanced i2p settings"
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:209
+msgid "Set:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:209
+msgid "Set the sent key-value pairs"
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:212
+msgid "SetAll:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:212
+msgid "Set the sent key-value pairs, remove everything else"
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:215
+msgid "Get:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:215
+msgid "Get the key-value pairs for the sent keys"
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:218
+msgid "GetAll:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:218
+msgid "Get all the key-value pairs"
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:221
+msgid "denotes an optional value."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:222
+msgid "denotes a possibly occuring return value"
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:224
+msgid "Error codes"
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:225
+msgid "Standard JSON-RPC2 error codes."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:226
+msgid "JSON parse error."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:227
+msgid "Invalid request."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:228
+msgid "Method not found."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:229
+msgid "Invalid parameters."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:230
+msgid "Internal error."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:232
+msgid "I2PControl specific error codes."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:233
+msgid "Invalid password provided."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:234
+msgid "No authentication token presented."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:235
+msgid "Authentication token doesn't exist."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:236
+msgid "The provided authentication token was expired and will be removed."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:237
+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:238
+msgid ""
+"The version of the I2PControl API specified is not supported by "
+"I2PControl."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2ptunnel.html:8
+#, 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 <a "
+"href=\"%(naming)s\">hostname</a>,\n"
+"<a href=\"%(naming)s#base32\">Base32</a>, 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"
+"<a "
+"href=\"http://localhost:7657/i2ptunnel/\">localhost:7657/i2ptunnel/</a>."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2ptunnel.html:20
+msgid "Default Services"
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2ptunnel.html:21
+msgid "Server tunnels"
+msgstr "Server tunelləri"
+
+#: i2p2www/pages/site/docs/api/i2ptunnel.html:23
+msgid ""
+"<b>I2P Webserver</b> - A tunnel pointed to a Jetty webserver run\n"
+"on <a href=\"http://localhost:7658\">localhost:7658</a> for convenient "
+"and quick hosting on I2P.\n"
+"<br>The document root is:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2ptunnel.html:31
+msgid "Client tunnels"
+msgstr "Müştəri tunelləri"
+
+#: i2p2www/pages/site/docs/api/i2ptunnel.html:33
+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:37
+msgid "An IRC tunnel to the default anonymous IRC network, Irc2P."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2ptunnel.html:38
+#, python-format
+msgid ""
+"The anonymous <a href=\"%(monotone)s\">monotone</a>\n"
+"sourcecode repository for I2P"
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2ptunnel.html:42
+#, python-format
+msgid ""
+"A SMTP service provided by postman at <a "
+"href=\"http://%(postman)s/?page_id=16\">%(postman)s</a>"
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2ptunnel.html:45
+#, python-format
+msgid ""
+"The accompanying POP sevice of postman at <a "
+"href=\"http://%(postman)s/?page_id=16\">%(postman)s</a>"
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2ptunnel.html:50
+msgid "Configuration"
+msgstr "Quraşdırma"
+
+#: i2p2www/pages/site/docs/api/i2ptunnel.html:54
+msgid "Client Modes"
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2ptunnel.html:55
+#: i2p2www/pages/site/docs/api/i2ptunnel.html:165
+msgid "Standard"
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2ptunnel.html:56
+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:62
+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:67
+msgid ""
+"<b>Accept, Accept-Charset, Accept-Language\n"
+" and Accept-Ranges</b> as they vary greatly between browsers and can be "
+"used as an identifier."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2ptunnel.html:90
+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:94
+msgid "Outproxy:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2ptunnel.html:95
+msgid "Internal I2P use:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2ptunnel.html:100
+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:105
+msgid "Whitelist:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2ptunnel.html:139
+msgid "Enables using the I2P router as a SOCKS proxy."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2ptunnel.html:144
+msgid ""
+"Enables using the I2P router as a SOCKS proxy with the command whitelist "
+"specified by\n"
+"<a href=\"#client-mode-irc\">IRC</a> client mode."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2ptunnel.html:150
+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:156
+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:164
+msgid "Server Modes"
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2ptunnel.html:166
+msgid "Creates a destination to a local ip:port with an open TCP port."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2ptunnel.html:171
+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:177
+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:184
+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:190
+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\" <a href=\"%(streaming)s\">streaming library</a>.\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 <a href=\"%(api)s\">API documentation</a> 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"
+"<a href=\"%(i2cp)s\">I2CP</a> 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"
+"<a href=\"%(i2ptunnel)s\">I2PTunnel</a> 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 <a href=\"%(minwww)s\">significant</a>.  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 <a href=\"%(api)s\">API</a>\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"
+"<a href=\"%(samv3)s\">SAM</a>'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 <a href=\"%(faq)s#socks\">FAQ</a>:"
+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/network-database.html:183
+#: 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 <a href=\"%(meeting81)s\">Meeting 81</a> and\n"
+"<a href=\"%(meeting82)s\">Meeting 82</a> 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
+msgid "July 2018"
+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"
+"<a href=\"%(datagrams)s\">datagram library</a>."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/streaming.html:18
+#, python-format
+msgid ""
+"The streaming library is a layer on top of the core \n"
+"<a href=\"%(i2cp)s\">I2CP API</a> 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 "APİ"
+
+#: 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 <a href=\"%(i2cp)s\">I2CP</a> API is completely hidden, "
+"except that\n"
+"applications may pass <a href=\"%(i2cp)s#options\">I2CP parameters</a> "
+"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"
+"<a href=\"%(i2psktmf)s\">I2PSocketManagerFactory</a> to create an\n"
+"<a href=\"%(i2psktm)s\">I2PSocketManager</a>. The application then asks "
+"the\n"
+"socket manager for an <a href=\"%(i2psess)s\">I2PSession</a>, which will "
+"cause\n"
+"a connection to the router via <a href=\"%(i2cp)s\">I2CP</a>. The "
+"application\n"
+"can then setup connections with an <a href=\"%(i2pskt)s\">I2PSocket</a> "
+"or\n"
+"receive connections with an <a href=\"%(i2psskt)s\">I2PServerSocket</a>."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/streaming.html:82
+#, python-format
+msgid "Here are the <a href=\"%(url)s\">full streaming library Javadocs</a>."
+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"
+"<a "
+"href=\"%(i2psktmf)s\">I2PSocketManagerFactory</a>.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 <a href=\"%(samv3)s\">SAM</a>,\n"
+"<a href=\"%(bob)s\">BOB</a>, and <a href=\"%(i2ptunnel)s\">I2PTunnel</a>,"
+"\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:103
+#: i2p2www/pages/site/docs/protocol/i2cp.html:478
+msgid "Option"
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/streaming.html:117
+#: i2p2www/pages/site/docs/protocol/i2cp.html:107
+#: i2p2www/pages/site/docs/protocol/i2cp.html:482
+msgid "Default"
+msgstr "Standart"
+
+#: i2p2www/pages/site/docs/api/streaming.html:117
+#: i2p2www/pages/site/docs/how/elgamal-aes.html:264
+#: i2p2www/pages/site/docs/how/peer-selection.html:282
+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:129
+#: i2p2www/pages/site/docs/api/streaming.html:135
+#: i2p2www/pages/site/docs/api/streaming.html:141
+#: i2p2www/pages/site/docs/api/streaming.html:148
+#: i2p2www/pages/site/docs/api/streaming.html:160
+#: i2p2www/pages/site/docs/api/streaming.html:171
+#: i2p2www/pages/site/docs/api/streaming.html:200
+#: i2p2www/pages/site/docs/api/streaming.html:212
+#: i2p2www/pages/site/docs/api/streaming.html:220
+#: i2p2www/pages/site/docs/api/streaming.html:245
+#: i2p2www/pages/site/docs/api/streaming.html:262
+#: i2p2www/pages/site/docs/api/streaming.html:275
+#: i2p2www/pages/site/docs/api/streaming.html:286
+#: i2p2www/pages/site/docs/api/streaming.html:292
+#: i2p2www/pages/site/docs/api/streaming.html:298
+#: i2p2www/pages/site/docs/api/streaming.html:312
+#: i2p2www/pages/site/docs/api/streaming.html:319
+#: i2p2www/pages/site/docs/api/streaming.html:326
+#: i2p2www/pages/site/docs/api/streaming.html:351
+#: i2p2www/pages/site/docs/api/streaming.html:358
+#: i2p2www/pages/site/docs/api/streaming.html:365
+#, python-format
+msgid "As of release %(release)s."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/streaming.html:125
+#: i2p2www/pages/site/docs/api/streaming.html:133
+msgid "Use the access list as a whitelist for incoming connections."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/streaming.html:127
+msgid "The name or number of the signature type for a transient destination."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/streaming.html:139
+msgid "Use the access list as a blacklist for incoming connections."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/streaming.html:153
+msgid "Whether to respond to incoming pings"
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/streaming.html:165
+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:175
+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:179
+msgid ""
+"When we're in congestion avoidance, we grow the window size at the rate\n"
+"of <code>1/(windowSize*factor)</code>.  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:186
+msgid ""
+"How long to wait after instantiating a new con \n"
+"before actually attempting to connect.  If this is\n"
+"&lt;= 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:194
+msgid ""
+"How long to block on connect, in milliseconds. Negative means "
+"indefinitely. Default is 5 minutes."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/streaming.html:198
+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:204
+msgid ""
+"Comma- or space-separated list of Base64 peer Hashes or host names to be\n"
+"contacted using an alternate DSA destination.\n"
+"Only applies if multisession is enabled and the primary session is non-"
+"DSA\n"
+"(generally for shared clients only).\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:216
+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:226
+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:232
+msgid "Idle time before sending a keepalive"
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/streaming.html:235
+msgid "Delay before sending an ack"
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/streaming.html:237
+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:242
+msgid ""
+"Initial timeout\n"
+"(if no <a href=\"#sharing\">sharing data</a> available)."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/streaming.html:249
+msgid ""
+"Initial round trip time estimate\n"
+"(if no <a href=\"#sharing\">sharing data</a> available).\n"
+"Disabled as of release 0.9.8; uses actual RTT."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/streaming.html:255
+msgid "if no <a href=\"#sharing\">sharing data</a> available"
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/streaming.html:255
+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:279
+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:284
+msgid "Incoming connection limit (per peer; 0 means disabled)"
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/streaming.html:290
+#: i2p2www/pages/site/docs/api/streaming.html:296
+msgid "(per peer; 0 means disabled)"
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/streaming.html:302
+msgid "The MTU in bytes."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/streaming.html:306
+msgid "Maximum number of retransmissions before failure."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/streaming.html:310
+msgid "Incoming connection limit (all peers; 0 means disabled)"
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/streaming.html:316
+#: i2p2www/pages/site/docs/api/streaming.html:323
+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:332
+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:337
+msgid "How long to block on read, in milliseconds. Negative means indefinitely."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/streaming.html:341
+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:348
+#: i2p2www/pages/site/docs/api/streaming.html:355
+#: i2p2www/pages/site/docs/api/streaming.html:362
+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:369
+msgid ""
+"How long to block on write/flush, in milliseconds. Negative means "
+"indefinitely."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/streaming.html:377
+msgid "Protocol Specification"
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/streaming.html:379
+msgid "See the Streaming Library Specification page."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/streaming.html:383
+msgid "Implementation Details"
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/streaming.html:385
+msgid "Setup"
+msgstr "Quraşdırma"
+
+#: i2p2www/pages/site/docs/api/streaming.html:386
+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:391
+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:398
+msgid "MTU Selection and Negotiation"
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/streaming.html:399
+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:408
+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:419
+#, python-format
+msgid ""
+"Data integrity is assured by the gzip CRC-32 checksum implemented in\n"
+"<a href=\"%(i2cp)s#format\">the I2CP layer</a>.\n"
+"There is no checksum field in the streaming protocol."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/streaming.html:427
+#, python-format
+msgid ""
+"Each packet is sent through I2P as a single message (or as an individual "
+"clove in a\n"
+"<a href=\"%(garlicrouting)s\">Garlic Message</a>). Message encapsulation "
+"is implemented\n"
+"in the underlying <a href=\"%(i2cp)s\">I2CP</a>, <a "
+"href=\"%(i2np)s\">I2NP</a>, and\n"
+"<a href=\"%(tunnelmessage)s\">tunnel message</a> layers. There is no "
+"packet delimiter\n"
+"mechanism or payload length field in the streaming protocol."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/streaming.html:437
+msgid "Optional Delay"
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/streaming.html:438
+msgid ""
+"Data packets may include an optional delay field specifying the requested"
+" delay,\n"
+"in ms, before the receiver should ack the packet.\n"
+"Valid values are 0 to 60000 inclusive.\n"
+"A value of 0 requests an immediate ack.\n"
+"This is advisory only, and receivers should delay slightly so that\n"
+"additional packets may be acknowledged with a single ack.\n"
+"Some implementations may include an advisory value of (measured RTT / 2) "
+"in this field.\n"
+"For nonzero optional delay values, receivers should limit the maximum "
+"delay\n"
+"before sending an ack to a few seconds at most.\n"
+"Optional delay values greater than 60000 indicate choking, see below."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/streaming.html:452
+msgid "Receive Window and Choking"
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/streaming.html:453
+msgid ""
+"TCP headers include the receive window in bytes.\n"
+"The streaming protocol does not contain a receive window, it uses only a "
+"simple choke/unchoke indication.\n"
+"Each endpoint must maintain its own estimate of the far-end receive "
+"window, in either bytes or packets.\n"
+"The recommended minimum buffer size for receiver implementations is 128 "
+"packets or 217 KB (approximately 128x1730).\n"
+"Because of I2P netowrk latency, packet drops, and the resulting "
+"congestion control,\n"
+"a buffer of this size is rarely filled.\n"
+"Overflow is, however, likely to occur on high-bandwidth \"local "
+"loopback\" (same-router) connections."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/streaming.html:462
+msgid ""
+"To quickly indicate and smoothly recover from overflow conditions,\n"
+"there is a simple mechanism for pushback in the streaming protocol.\n"
+"If a packet is received with an optional delay field of value of 60001 or"
+" higher,\n"
+"that indicates \"choking\" or a receive window of zero.\n"
+"A packet with an optional delay field of value of 60000 or less indicates"
+" \"unchoking\".\n"
+"Packets without an optional delay field do not affect the choke/unchoke "
+"state."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/streaming.html:470
+msgid ""
+"After being choked, no more packets with data should be sent until the "
+"transmitter is unchoked,\n"
+"except for occasional \"probe\" data packets to compensate for possible "
+"lost unchoke packets.\n"
+"The choked endpoint should start a \"persist timer\" to control the "
+"probing, as in TCP.\n"
+"The unchoking endpoint should send several packets with this field set,\n"
+"or continue sending them periodically until data packets are received "
+"again.\n"
+"Maximum time to wait for unchoking is implementation-dependent.\n"
+"Transmitter window size and congestion control strategy after being "
+"unchoked is implementation-dependent."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/streaming.html:481
+msgid "Congestion Control"
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/streaming.html:482
+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:489
+msgid "Close"
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/streaming.html:490
+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:498
+msgid ""
+"There is no ping function at the I2CP layer (equivalent to ICMP echo) or "
+"in datagrams.\n"
+"This function is provided in streaming.\n"
+"Pings and pongs may not be combined with a standard streaming packet;\n"
+"if the ECHO option is set, then\n"
+"most other flags, options, ackThrough, sequenceNum, NACKs, etc. are "
+"ignored."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/streaming.html:506
+msgid ""
+"A ping packet must have the ECHO, SIGNATURE_INCLUDED, and FROM_INCLUDED "
+"flags set.\n"
+"The sendStreamId must be greater than zero, and the receiveStreamId is "
+"ignored.\n"
+"The sendStreamId may or may not correspond to an existing connection."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/streaming.html:512
+msgid ""
+"A pong packet must have the ECHO flag set.\n"
+"The sendStreamId must be zero, and the receiveStreamId is the "
+"sendStreamId from the ping.\n"
+"Prior to release 0.9.18, the pong packet does not include any payload "
+"that was contained in the ping."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/streaming.html:518
+msgid ""
+"As of release 0.9.18, pings and pongs may contain a payload.\n"
+"The payload in the ping, up to a maximum of 32 bytes, is returned in the "
+"pong."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/streaming.html:523
+msgid ""
+"Streaming may be configured to disable sending pongs with the "
+"configuration i2p.streaming.answerPings=false."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/streaming.html:528
+msgid "Control Block Sharing"
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/streaming.html:529
+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"
+"<a href=\"http://www.ietf.org/rfc/rfc2140.txt\">RFC 2140</a>).\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:550
+msgid "Other Parameters"
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/streaming.html:551
+msgid ""
+"The following parameters are hardcoded, but may be of interest for "
+"analysis:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/streaming.html:570
+#: i2p2www/pages/site/docs/how/network-database.html:895
+msgid "History"
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/streaming.html:571
+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:585
+#: i2p2www/pages/site/docs/how/elgamal-aes.html:344
+#: i2p2www/pages/site/docs/how/garlic-routing.html:251
+#: i2p2www/pages/site/docs/how/network-database.html:900
+#: 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:723
+#: i2p2www/pages/site/docs/protocol/i2np.html:226
+#: i2p2www/pages/site/docs/transport/ntcp.html:544
+#: i2p2www/pages/site/docs/transport/ssu.html:585
+#: i2p2www/pages/site/docs/tunnels/implementation.html:506
+msgid "Future Work"
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/streaming.html:586
+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:592
+msgid "Additional tuning of the streaming lib parameters may be necessary."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/streaming.html:595
+#, python-format
+msgid ""
+"Another area for research is the interaction of the streaming lib with "
+"the\n"
+"NTCP and SSU transport layers.\n"
+"See <a href=\"%(ntcpdisc)s\">the NTCP discussion page</a> for details."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/streaming.html:600
+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:610
+msgid "The data in the first SYN packet may exceed the receiver's MTU."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/streaming.html:613
+msgid "The DELAY_REQUESTED field could be used more."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/streaming.html:616
+msgid ""
+"Duplicate initial SYNCHRONIZE packets on short-lived streams may not be "
+"recognized and removed."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/streaming.html:619
+msgid "Don't send the MTU in a retransmission."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/streaming.html:622
+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:627
+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:632
+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
+msgid "January 2017"
+msgstr "Yanvar 2017"
+
+#: 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"
+"<a href=\"%(commonstructures)s#struct_Destination\">Destination</a>,\n"
+"using the I2P Base 64 alphabet [A-Z][a-z][0-9]-~.\n"
+"<a href=\"%(commonstructures)s#struct_Destination\">Destinations</a>\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 ""
+"Current Destinations for clients are 387 or more bytes (516 or more in "
+"Base 64 encoding).\n"
+"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"
+"<a href=\"%(commonstructures)s#struct_Destination\">Destination</a>, 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"
+"<a href=\"%(commonstructures)s#type_Hash\">32-byte SHA-256 Hashes</a>\n"
+"of the binary\n"
+"<a href=\"%(commonstructures)s#struct_Destination\">Destinations</a>\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&#37;."
+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"
+"<a href=\"%(commonstructures)s#struct_Destination\">Destination</a>\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"
+"<a href=\"%(naming)s\">I2P naming standards</a>.\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 <a "
+"href=\"%(commonstructures)s#struct_Destination\">Destinations</a>\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"
+"<a href=\"http://www.bittorrent.org/beps/bep_0010.html\">the extension "
+"handshake</a>.\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"
+"<a href=\"%(commonstructures)s#struct_Destination\">Destinations</a>\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"
+"<a href=\"http://www.bittorrent.org/beps/bep_0005.html\">BEP 5</a>\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"
+"<a href=\"http://www.bittorrent.org/beps/bep_0010.html\">the extension "
+"handshake</a>.\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:286
+msgid "Datagram (UDP) Trackers"
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/bittorrent.html:287
+msgid ""
+"UDP tracker support in clients and trackers is not yet available.\n"
+"Preliminary differences from\n"
+"<a href=\"http://www.bittorrent.org/beps/bep_0015.html\">BEP 15</a>\n"
+"are described below, and are subject to change.\n"
+"Contact the I2P developers if you wish to develop a client or tracker "
+"supporting datagram announces."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/bittorrent.html:295
+msgid ""
+"A UDP tracker listens on two ports.\n"
+"The \"query port\" is the advertised port, and is used to receive "
+"repliable (signed) datagrams, for the connect request only.\n"
+"The \"response port\" is used to receive unsigned (raw) datagrams, and is"
+" the source port for all replies.\n"
+"The response port is arbitrary.\n"
+"A client sends and receives on a single port only.\n"
+"It receives only unsigned (raw) datagrams.\n"
+"Raw datagrams provides increased efficiency for replies since they "
+"contain tokens sent in the query, and need not be signed."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/bittorrent.html:305
+msgid ""
+"In the announce request, the 4-byte IP is replaced by a 32-byte hash, and"
+" the port is still present,\n"
+"although it may be ignored by the tracker.\n"
+"In the announce response, each 4-byte IP and 2-byte port is replaced by a"
+" 32-byte hash (compact peer info), and no port is present.\n"
+"The client sends the announce request and scrape request to the source "
+"port in the announce response packet.\n"
+"The connect request, connect response, scrape request, scrape response, "
+"and error response are the same as in BEP 15."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/bittorrent.html:313
+msgid ""
+"Source addresses in I2P cannot be spoofed, so it is possible to use a "
+"simplified protocol\n"
+"with 2 packets instead of 4, omitting the connect request and response.\n"
+"In this case, the announce request would be a repliable datagram sent to "
+"the tracker's query port,\n"
+"and the tracker would not require a response port.\n"
+"While this is more efficient, it would be more difficult to modify an "
+"existing tracker to support this mode.\n"
+"The URL for the 4-packet-mode tracker would use standard \"udp://\" "
+"prefix. \n"
+"The URL for a modified 2-packet-mode tracker would require a different "
+"prefix if both modes are supported in I2P."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/bittorrent.html:326
+#: i2p2www/pages/site/docs/how/intro.html:184
+msgid "Additional Information"
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/bittorrent.html:328
+#, python-format
+msgid ""
+"I2P bittorrent standards are generally discussed on <a "
+"href=\"http://%(zzz)s/\">%(zzz)s</a>."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/bittorrent.html:331
+#, python-format
+msgid ""
+"A chart of current tracker software capabilities is <a "
+"href=\"http://%(zzz)s/files/trackers.html\">also available there</a>."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/bittorrent.html:334
+#, python-format
+msgid ""
+"The\n"
+"<a href=\"http://%(forum)s/viewtopic.php?t=2068\">I2P bittorrent FAQ</a>"
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/bittorrent.html:338
+#, python-format
+msgid "<a href=\"http://%(zzz)s/topics/812\">DHT on I2P discussion</a>"
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/embedding.html:2
+msgid "Embedding I2P in your Application"
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/embedding.html:3
+msgid "November 2017"
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/embedding.html:8
+msgid ""
+"This page is about bundling the entire I2P router binary with your "
+"application.\n"
+"It is not about writing an application to work with I2P (either bundled "
+"or external)."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/embedding.html:13
+msgid ""
+"Lots of projects are bundling, or talking about bundling, I2P. That's "
+"great if done right.\n"
+"If done wrong, it could cause real harm to our network.\n"
+"The I2P router is complex, and it can be a challenge to hide all the "
+"complexity from your users.\n"
+"This page discusses some general guidelines."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/embedding.html:23
+msgid "Talk to us"
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/embedding.html:24
+msgid ""
+"Start a dialog. We're here to help. Applications that embed I2P are the "
+"most promising - and exciting -\n"
+"opportunities for us to grow the network and improve anonymity for "
+"everyone."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/embedding.html:30
+msgid "Choose your router wisely"
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/embedding.html:31
+msgid ""
+"If your application is in Java or Scala, it's an easy choice - use the "
+"Java router.\n"
+"If in C/C++, we recommend i2pd. The development of i2pcpp has stopped.\n"
+"For apps in other languages, best to use SAM or BOB or SOCKS and bundle "
+"the Java router as a separate process.\n"
+"Some of the following only applies to the Java router."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/embedding.html:39
+msgid "Licensing"
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/embedding.html:40
+msgid "Ensure you meet the license requirements of the software you are bundling."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/embedding.html:45
+msgid "Verify default configuration"
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/embedding.html:46
+msgid ""
+"A correct default configuration is crucial. Most users will not change "
+"the defaults.\n"
+"The defaults for your application may need to be different than the "
+"defaults for the router you are bundling.\n"
+"Override the router defaults if necessary."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/embedding.html:51
+msgid ""
+"Some important defaults to review: Max bandwidth, tunnel quantity and "
+"length, max participating tunnels.\n"
+"A lot of this depends on the expected bandwidth and usage patterns of "
+"your app."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/embedding.html:55
+msgid ""
+"Configure enough bandwidth and tunnels to allow your users to contribute "
+"to the network.\n"
+"Consider disabling external I2CP, as you probably don't need it and it "
+"would conflict with any other running I2P instance.\n"
+"Also look at the configs for disabling killing of the JVM on exit, for "
+"example."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/embedding.html:62
+msgid "Participating Traffic Considerations"
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/embedding.html:63
+msgid ""
+"It may be tempting for you to disable participating traffic.\n"
+"There's several ways to do this (hidden mode, setting max tunnels to 0, "
+"setting shared bandwidth below 12 KBytes/sec).\n"
+"Without participating traffic, you don't have to worry about graceful "
+"shutdown,\n"
+"your users don't see bandwidth usage not generated by them, etc.\n"
+"However, there's lots of reasons why you should allow participating "
+"tunnels."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/embedding.html:70
+msgid ""
+"First of all, the router doesn't work that well if it doesn't have a "
+"chance to \"integrate\" with the network,\n"
+"which is helped tremendously by others building tunnels through you."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/embedding.html:74
+msgid ""
+"Secondly, over 90&#37; of the routers in the current network allow "
+"participating traffic.\n"
+"It's the default in the Java router.\n"
+"If your application doesn't route for others and it gets really popular, "
+"then it's a leech on the network,\n"
+"and it upsets the balance we have now.\n"
+"If it gets really big, then we become Tor, and spend our time begging for"
+" people to enable relaying."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/embedding.html:81
+msgid ""
+"Thirdly, participating traffic is cover traffic that helps your users' "
+"anonymity."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/embedding.html:84
+msgid ""
+"We strongly discourage you from disabling participating traffic by "
+"default.\n"
+"If you do this and your application gets hugely popular, it could break "
+"the network."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/embedding.html:90
+msgid "Persistence"
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/embedding.html:91
+msgid ""
+"You must save the router's data (netdb, configuration, etc.) between runs"
+" of the router.\n"
+"I2P does not work well if you must reseed each startup, and that's a huge"
+" load on our reseed servers, and not very good for anonymity either.\n"
+"Even if you bundle router infos, I2P needs saved profile data for best "
+"performance."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/embedding.html:99
+msgid "Configurability"
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/embedding.html:100
+msgid ""
+"Give your users a way to change the configuration of the important "
+"settings.\n"
+"We understand that you will probably want to hide most of I2P's "
+"complexity, but it's important to show some basic settings.\n"
+"In addition to the defaults above, some network settings such as UPnP, "
+"IP/port may be helpful."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/embedding.html:108
+msgid "Floodfill Considerations"
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/embedding.html:109
+msgid ""
+"Above a certain bandwidth setting, and meeting other health criteria, "
+"your router will become floodfill,\n"
+"which may cause a large increase in connections and memory usage (at "
+"least with the Java router).\n"
+"Think about whether that's OK. You can disable floodfill, but then your "
+"fastest users aren't contributing what they could.\n"
+"It also depends on the typical uptime for your application."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/embedding.html:119
+msgid "Reseeding"
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/embedding.html:120
+msgid ""
+"Decide if you are bundling router infos or using our reseed hosts.\n"
+"The Java reseed host list is in the source code, so if you keep your "
+"source up to date, the host list will be also.\n"
+"Be aware of possible blocking by hostile governments."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/embedding.html:129
+msgid "Reduce Network Resource Usage"
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/embedding.html:130
+msgid ""
+"Consider setting your application tunnels to delay-open, reduce-on-idle "
+"and/or close-on-idle.\n"
+"This is straightforward if using i2ptunnel but you'll have to implement "
+"some of it yourself if using I2CP directly.\n"
+"See i2psnark for code that reduces tunnel count and then closes the "
+"tunnel, even in the presence of some background DHT activity."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/embedding.html:138
+msgid "Updatability"
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/embedding.html:139
+msgid ""
+"Have an auto-update feature if at all possible, or at least auto-"
+"notification of a new version.\n"
+"Our biggest fear is a huge number of routers out there that can't be "
+"updated.\n"
+"We have about 6-8 releases a year of the Java router, and it's critical "
+"to the health of the network that the users keep up.\n"
+"We usually have over 80&#37; of the network on the latest release within "
+"6 weeks after the release, and we'd like to keep it that way.\n"
+"You don't need to worry about disabling the router's built-in auto-update"
+" function, as that code is in the router console,\n"
+"which you presumably are not bundling."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/embedding.html:150
+msgid "Rollout"
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/embedding.html:151
+msgid ""
+"Have a gradual rollout plan. Don't overwhelm the network all at once.\n"
+"We currently have approximately 25K unique users per day and 40K uniques "
+"per month.\n"
+"We are probably able to handle growth of 2-3X per year without too much "
+"issue.\n"
+"If you anticipate a faster rampup than that, OR the bandwidth "
+"distribution (or uptime distribution,\n"
+"or any other significant characteristic) of your userbase is "
+"significantly different from our current userbase,\n"
+"we really need to have a discussion.\n"
+"The bigger your growth plans, the more important everthing else in this "
+"checklist is."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/embedding.html:163
+msgid "Design for and Encourage Long Uptimes"
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/embedding.html:164
+msgid ""
+"Tell your users that I2P works best if it keeps running.\n"
+"It may be several minutes after startup before it works well, and even "
+"more after first install.\n"
+"If your average uptime is less than an hour, I2P is probably the wrong "
+"solution."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/embedding.html:172
+msgid "Show Status"
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/embedding.html:173
+msgid ""
+"Provide some indication to the user that the application tunnels are "
+"ready. Encourage patience."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/embedding.html:178
+msgid "Graceful Shutdown"
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/embedding.html:179
+msgid ""
+"If possible, delay the shutdown until your participating tunnels expire.\n"
+"Don't let your users break tunnels easily, or at least ask them to "
+"confirm."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/embedding.html:185
+msgid "Education and Donation"
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/embedding.html:186
+msgid ""
+"It would be nice if you give your users links to learn more about I2P and"
+" to donate."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/embedding.html:192
+msgid "External Router Option"
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/embedding.html:193
+msgid ""
+"Depending on your user base and application,\n"
+"it may be helpful to provide an option or a separate package to use an "
+"external router."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/embedding.html:200
+msgid "Use of other Common Services"
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/embedding.html:201
+msgid ""
+"If you plan to use or link to other common I2P services (news feeds, "
+"hosts.txt subscriptions, trackers, outproxies, etc.),\n"
+"make sure you aren't overloading them,\n"
+"and talk to the people who are running them to make sure it's ok."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/embedding.html:209
+msgid "Time / NTP Issues"
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/embedding.html:210
+msgid ""
+"I2P includes an SNTP client. I2P requires correct time to operate.\n"
+"It will compensate for a skewed system clock but this may delay startup. "
+"You may disable I2P's SNTP queries,\n"
+"but this isn't advised unless your application makes sure the system "
+"clock is correct."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/embedding.html:218
+msgid "Choose What and How you Bundle"
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/embedding.html:219
+msgid ""
+"At a minimum you will need i2p.jar, router.jar, streaming.jar, and "
+"mstreaming.jar.\n"
+"You may omit the two streaming jars for a datagram-only app.\n"
+"Some apps may need more, e.g. i2ptunnel.jar or addressbook.jar.\n"
+"Don't forget jbigi.jar, or a subset of it for the platforms you support, "
+"to make the crypto much faster.\n"
+"We are currently building them for Java 7, as of 0.9.24. The source is "
+"mostly compatible with Java 6 if you want to do your own compile,\n"
+"but we may start using Java 7 features at any time without notice.\n"
+"If you're building Debian / Ubuntu packages, you should require the I2P "
+"package from our PPA instead of bundling it.\n"
+"You almost certainly do not need susimail, susidns, the router console, "
+"and i2psnark, for example."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/embedding.html:229
+msgid ""
+"The following files should be included in the I2P installation directory,"
+" specified with the \"i2p.dir.base\" property.\n"
+"Don't forget certificates/reseed and certificates/ssl, required for "
+"reseeding, and blocklist.txt for IP validation.\n"
+"The geoip directory is optional, but recommended so the router can make "
+"decisions based on location.\n"
+"The hosts.txt file may be necessary, you may modify it to include any "
+"hosts your application uses.\n"
+"You may add a router.config file to the base directory to override "
+"initial defaults."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/embedding.html:236
+msgid ""
+"License requirements may require you to include the LICENSES.txt file and"
+" the licenses directory."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/embedding.html:242
+msgid "You may also wish to bundle a hosts.txt file."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/embedding.html:245
+msgid "Be sure to specify a Java 7 bootclasspath if compiling with Java 8."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/embedding.html:253
+msgid "Android considerations"
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/embedding.html:254
+msgid ""
+"Our Android router app may be shared by multiple clients.\n"
+"If it is not installed, the user will be prompted when he starts a client"
+" app."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/embedding.html:258
+msgid ""
+"Some developers have expressed concern that this is a poor user "
+"experience,\n"
+"and they wish to embed the router in their app.\n"
+"We do have an Android router service library on our roadmap, which could "
+"make embedding easier.\n"
+"More information needed."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/embedding.html:264
+#: i2p2www/pages/site/docs/applications/embedding.html:275
+msgid "If you require assistance, please contact us."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/embedding.html:270
+msgid "Maven jars"
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/embedding.html:271
+msgid ""
+"We have a limited number of our jars on <a "
+"href=\"http://search.maven.org/#search%7Cga%7C1%7Cg%3A%22net.i2p%22\">Maven"
+" Central</a>.\n"
+"There are numerous trac tickets for us to address that will improve and "
+"expand the released jars on Maven Central."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/embedding.html:281
+msgid "Datagram (DHT) considerations"
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/embedding.html:282
+msgid ""
+"If your application is using I2P datagrams, e.g. for a DHT,\n"
+"there's lots of advanced options available to reduce overhead and "
+"increase reliability.\n"
+"This may take some time and experimentation to get working well.\n"
+"Be aware of size/reliability tradeoffs. Talk to us for help.\n"
+"It is possible - and recommended - to use Datagrams and Streaming on the "
+"same Destination.\n"
+"Don't create separate Destinations for this.\n"
+"Don't try to store your unrelated data in the existing network DHTs "
+"(iMule, bote, bittorrent, and router).\n"
+"Build your own. If you are hardcoding seed nodes, we recommend that you "
+"have several."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/embedding.html:295
+msgid "Comarketing"
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/embedding.html:296
+msgid ""
+"Let's work together. Don't wait until it's done.\n"
+"Give us your Twitter handle and start tweeting about it, we will return "
+"the favor."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/embedding.html:302
+msgid "Malware"
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/embedding.html:303
+msgid ""
+"Please don't use I2P for evil.\n"
+"It could cause great harm both to our network and our reputation."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/embedding.html:309
+msgid "Join Us"
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/embedding.html:310
+msgid ""
+"This may be obvious, but join the community. Run I2P 24/7. Start an "
+"eepsite about your project.\n"
+"Hang out in IRC #i2p-dev. Post on the forums. Spread the word.\n"
+"We can help get you users, testers, translators, or even coders."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/embedding.html:318
+msgid "Application Examples"
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/embedding.html:319
+msgid ""
+"You may wish to install and play with the I2P Android app, and look at "
+"its code, for an example of an application that bundles the router.\n"
+"See what we expose to the user and what we hide.\n"
+"Look at the state machine we use to start and stop the router.\n"
+"Other examples are: Vuze, the Nightweb Android app, iMule, TAILS, iCloak,"
+" and Monero."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/embedding.html:327
+msgid "Code Example"
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/embedding.html:328
+msgid ""
+"None of the above actually tells you how to write your code to\n"
+"bundle the Java router, so following is a brief example."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/embedding.html:358
+msgid ""
+"This code is for the case where your application starts the router, as in"
+" our Android app.\n"
+"You could also have the router start the application via the "
+"clients.config and i2ptunnel.config files,\n"
+"together with Jetty webapps,\n"
+"as is done in our Java packages.\n"
+"As always, state management is the difficult part."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/managed-clients.html:3
+msgid "February 2014"
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/managed-clients.html:8
+#, python-format
+msgid ""
+"Clients may be started directly by the router when they are listed\n"
+"in the <a href=\"%(configspec)s\">clients.config</a> file.\n"
+"These clients may be \"managed\" or \"unmanaged\".\n"
+"This is handled by the ClientAppManager.\n"
+"Additionally, managed or unmanaged clients may register with the\n"
+"ClientAppManager so that other clients may retrieve a reference to them.\n"
+"There is also a simple Port Mapper facility for clients to register an\n"
+"internal port that other clients may look up."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/managed-clients.html:21
+msgid ""
+"As of release 0.9.4, the router supports managed clients.\n"
+"Managed clients are instantiated and started by the ClientAppManager.\n"
+"The ClientAppManager maintains a reference to the client and receives "
+"updates on the client's state.\n"
+"Managed clients are preferred, as it is much easier to implement state "
+"tracking\n"
+"and to start and stop a client. It also is much easier to avoid static "
+"references in the client code\n"
+"which could lead to excessive memory usage after a client is stopped.\n"
+"Managed clients may be started and stopped by the user in the router "
+"console,\n"
+"and are stopped at router shutdown."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/managed-clients.html:31
+msgid ""
+"Managed clients implement either the net.i2p.app.ClientApp or "
+"net.i2p.router.app.RouterApp interface.\n"
+"Clients implementing the ClientApp interface must provide the following "
+"constructor:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/managed-clients.html:38
+msgid ""
+"Clients implementing the RouterApp interface must provide the following "
+"constructor:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/managed-clients.html:44
+msgid "The arguments provided are specified in the clients.config file."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/managed-clients.html:48
+msgid "Unmanaged Clients"
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/managed-clients.html:49
+msgid ""
+"If the main class specified in the clients.config file does not implement"
+" a managed interface,\n"
+"it will be started with main() with the arguments specified,\n"
+"and stopped with main() with the arguments specified.\n"
+"The router does not maintain a reference, since all interactions are via "
+"the static main() method.\n"
+"The console cannot provide accurate state information to the user."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/managed-clients.html:57
+msgid "Registered Clients"
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/managed-clients.html:58
+msgid ""
+"Clients, whether managed or unmanaged, may register with the "
+"ClientAppManager\n"
+"so that other clients may retrieve a reference to them.\n"
+"Registration is by name.\n"
+"Known registered clients are:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/managed-clients.html:68
+msgid "Port Mapper"
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/managed-clients.html:69
+msgid ""
+"The router also provides a simple mechanism for clients to find an "
+"internal socket service,\n"
+"such as the HTTP proxy. This is provided by the Port Mapper.\n"
+"Registration is by name.\n"
+"Clients that register generally provide an internal emulated socket on "
+"that port."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:2
+msgid "Supported Applications"
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:5
+#: i2p2www/pages/site/docs/applications/supported.html:188
+msgid "Blogging, Forums, and Wikis"
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:7
+#: i2p2www/pages/site/docs/applications/supported.html:234
+msgid "Decentralized File Storage"
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:10
+#: i2p2www/pages/site/docs/applications/supported.html:246
+msgid "Development Tools"
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:13
+#: i2p2www/pages/site/docs/applications/supported.html:248
+msgid "Version control"
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:17
+#: i2p2www/pages/site/docs/applications/supported.html:267
+msgid "Domain Naming"
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:19
+#: i2p2www/pages/site/docs/applications/supported.html:285
+msgid "Email"
+msgstr "Email"
+
+#: i2p2www/pages/site/docs/applications/supported.html:22
+#: i2p2www/pages/site/docs/applications/supported.html:330
+msgid "File Sharing"
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:25
+#: i2p2www/pages/site/docs/applications/supported.html:332
+msgid "BitTorrent clients"
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:27
+#: i2p2www/pages/site/docs/applications/supported.html:375
+msgid "BitTorrent trackers and indexers"
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:36
+#: i2p2www/pages/site/docs/applications/supported.html:442
+msgid "Network Administration"
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:39
+#: i2p2www/pages/site/docs/applications/supported.html:444
+msgid "General-purpose socket utilities"
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:46
+#: i2p2www/pages/site/docs/applications/supported.html:485
+msgid "Real-time Chat"
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:49
+#: i2p2www/pages/site/docs/applications/supported.html:487
+msgid "Instant messaging clients"
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:51
+#: i2p2www/pages/site/docs/applications/supported.html:497
+msgid "IRC clients"
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:53
+#: i2p2www/pages/site/docs/applications/supported.html:548
+msgid "IRC servers"
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:58
+#: i2p2www/pages/site/docs/applications/supported.html:564
+msgid "Web Browsing"
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:61
+#: i2p2www/pages/site/docs/applications/supported.html:566
+msgid "Anonymous websites"
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:63
+#: i2p2www/pages/site/docs/applications/supported.html:615
+msgid "Proxy software"
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:65
+#: i2p2www/pages/site/docs/applications/supported.html:640
+msgid "Inproxies"
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:67
+#: i2p2www/pages/site/docs/applications/supported.html:681
+msgid "Outproxies"
+msgstr "Outproxies "
+
+#: i2p2www/pages/site/docs/applications/supported.html:72
+#: i2p2www/pages/site/docs/applications/supported.html:695
+msgid "Website Hosting"
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:75
+#: i2p2www/pages/site/docs/applications/supported.html:710
+msgid "Web servers"
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:82
+#, 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"
+"<a href=\"%(trac)s\">Trac</a>, and be sure to select the\n"
+"“www” component in the submission form."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:89
+msgid ""
+"\n"
+"Supported applications are tagged with one or more of the following:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:94
+#: i2p2www/pages/site/docs/applications/supported.html:281
+#: i2p2www/pages/site/docs/applications/supported.html:313
+#: i2p2www/pages/site/docs/applications/supported.html:338
+#: i2p2www/pages/site/docs/applications/supported.html:707
+msgid "bundled"
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:97
+msgid ""
+"<em>Bundled application</em> — 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:105
+#: i2p2www/pages/site/docs/applications/supported.html:197
+#: i2p2www/pages/site/docs/applications/supported.html:210
+#: i2p2www/pages/site/docs/applications/supported.html:222
+#: i2p2www/pages/site/docs/applications/supported.html:230
+#: i2p2www/pages/site/docs/applications/supported.html:243
+#: i2p2www/pages/site/docs/applications/supported.html:294
+#: i2p2www/pages/site/docs/applications/supported.html:407
+#: i2p2www/pages/site/docs/applications/supported.html:429
+#: i2p2www/pages/site/docs/applications/supported.html:438
+#: i2p2www/pages/site/docs/applications/supported.html:526
+msgid "plugin"
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:108
+#, python-format
+msgid ""
+"<em>Third-party plugin</em> — 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](<a href=\n"
+"\"http://%(plugins)s\">http://%(plugins)s</a>) to identify security and\n"
+"anonymity issues."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:119
+#: i2p2www/pages/site/docs/applications/supported.html:222
+#: i2p2www/pages/site/docs/applications/supported.html:230
+#: i2p2www/pages/site/docs/applications/supported.html:243
+#: i2p2www/pages/site/docs/applications/supported.html:254
+#: i2p2www/pages/site/docs/applications/supported.html:263
+#: i2p2www/pages/site/docs/applications/supported.html:326
+#: i2p2www/pages/site/docs/applications/supported.html:345
+#: i2p2www/pages/site/docs/applications/supported.html:356
+#: i2p2www/pages/site/docs/applications/supported.html:371
+#: i2p2www/pages/site/docs/applications/supported.html:417
+#: i2p2www/pages/site/docs/applications/supported.html:429
+#: i2p2www/pages/site/docs/applications/supported.html:438
+#: i2p2www/pages/site/docs/applications/supported.html:453
+#: i2p2www/pages/site/docs/applications/supported.html:459
+#: i2p2www/pages/site/docs/applications/supported.html:465
+#: i2p2www/pages/site/docs/applications/supported.html:475
+#: i2p2www/pages/site/docs/applications/supported.html:481
+#: i2p2www/pages/site/docs/applications/supported.html:493
+#: i2p2www/pages/site/docs/applications/supported.html:526
+#: i2p2www/pages/site/docs/applications/supported.html:532
+#: i2p2www/pages/site/docs/applications/supported.html:538
+#: i2p2www/pages/site/docs/applications/supported.html:544
+#: i2p2www/pages/site/docs/applications/supported.html:621
+#: i2p2www/pages/site/docs/applications/supported.html:630
+#: i2p2www/pages/site/docs/applications/supported.html:636
+#: i2p2www/pages/site/docs/applications/supported.html:707
+#: i2p2www/pages/site/docs/applications/supported.html:722
+#: i2p2www/pages/site/docs/applications/supported.html:728
+#: i2p2www/pages/site/docs/applications/supported.html:734
+#: i2p2www/pages/site/docs/applications/supported.html:740
+msgid "standalone"
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:119
+#: i2p2www/pages/site/docs/applications/supported.html:197
+#: i2p2www/pages/site/docs/applications/supported.html:204
+#: i2p2www/pages/site/docs/applications/supported.html:210
+#: i2p2www/pages/site/docs/applications/supported.html:216
+#: i2p2www/pages/site/docs/applications/supported.html:365
+#: i2p2www/pages/site/docs/applications/supported.html:389
+#: i2p2www/pages/site/docs/applications/supported.html:398
+#: i2p2www/pages/site/docs/applications/supported.html:554
+#: i2p2www/pages/site/docs/applications/supported.html:560
+msgid "standalone/mod"
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:122
+msgid ""
+"<em>Third-party standalone application</em> — Many standard network\n"
+"applications only require careful setup and configuration to communicate\n"
+"anonymously over I2P. These are tagged with <em>standalone</em>. Some\n"
+"applications, tagged with <em>standalone/mod</em>, 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:304
+#: i2p2www/pages/site/docs/applications/supported.html:574
+#: i2p2www/pages/site/docs/applications/supported.html:584
+#: i2p2www/pages/site/docs/applications/supported.html:593
+#: i2p2www/pages/site/docs/applications/supported.html:599
+#: i2p2www/pages/site/docs/applications/supported.html:605
+#: i2p2www/pages/site/docs/applications/supported.html:611
+#: i2p2www/pages/site/docs/applications/supported.html:653
+#: i2p2www/pages/site/docs/applications/supported.html:661
+#: i2p2www/pages/site/docs/applications/supported.html:670
+#: i2p2www/pages/site/docs/applications/supported.html:677
+#: i2p2www/pages/site/docs/applications/supported.html:691
+msgid "service"
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:138
+msgid ""
+"<em>Third-party essential network service</em> — 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:150
+#: i2p2www/pages/site/docs/applications/supported.html:222
+msgid "unmaintained"
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:153
+msgid ""
+"<em>Unmaintained</em> — 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:161
+#, 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 <a "
+"href=\"%(threatmodel)s\">identified\n"
+"threats to anonymity</a>. 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:173
+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:181
+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:203
+msgid "Lightweight forum software."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:209
+msgid "Another lightweight blogging platform."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:215
+msgid "Most popular open source forum software."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:221
+msgid "Distributed forums software, originally developed by jrandom."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:226
+#, python-format
+msgid ""
+"A Java-based MediaWiki clone. No external database needed.\n"
+"Plugin available <a href=\"http://%(plugins)s/plugins/jamwiki\">here</a>."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:238
+#, python-format
+msgid ""
+"Port of the <a href=\"http://tahoe-lafs.org/\"><strong>Tahoe-"
+"LAFS</strong></a>\n"
+"distributed file system to the I2P network. Controller plugin <a href=\n"
+"\"http://%(stats)s/i2p/plugins/\">here</a>."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:253
+msgid "Most popular distributed version control system."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:259
+#, python-format
+msgid ""
+"Another distributed version control system. Currently\n"
+"<a href=\"%(monotone)s\">used in I2P development</a>."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:271
+#, python-format
+msgid ""
+"Provides management of addressbooks, which are part of a simple,\n"
+"user-controlled <a href=\"%(naming)s\">I2P naming system</a> 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. (<em>Note:</em> 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:290
+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:299
+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:309
+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:318
+#, python-format
+msgid ""
+"Can be configured to use Postman's email service. See\n"
+"<a href=\"%(reviews)s\">this comparison of MUAs</a>,\n"
+"and configuration settings for\n"
+"<a href=\"%(smtp)s\">SMTP</a> and <a href=\"%(pop3)s\">POP3</a>."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:337
+msgid "I2P's integrated BitTorrent client."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:343
+msgid ""
+"Modified version of I2PSnark, no more supported neither\n"
+"    functional."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:350
+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:361
+msgid ""
+"Clean, full-featured cross-platform BitTorrent client with official\n"
+"ports for several GUI toolkits."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:370
+msgid "Has a plugin providing I2P support."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:377
+#, python-format
+msgid ""
+"For a detailed feature comparison of I2P-enabled trackers/indexers, see\n"
+"<a href=\"http://%(zzz)s/files/trackers.html\">here</a>."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:385
+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:394
+#, python-format
+msgid ""
+"Lightweight tracker/indexer. I2P mod available in the i2p.opentracker\n"
+"branch of the <a href=\"%(newdevs)s\">I2P Monotone repository</a>."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:403
+#, python-format
+msgid ""
+"<a href=\"http://%(zzz)s/\">zzz's</a> Java-based open tracker. More info\n"
+"<a href=\"http://%(zzz)s/topics/598?page=1#p2085\">here</a>."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:416
+msgid "I2P port of the aMule ED2K client."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:425
+#, python-format
+msgid ""
+"Port of the <a href=\"http://www.phex.org/mambo/\">Phex</a> Gnutella "
+"client. Website\n"
+"for plugin version <a href=\"http://%(stats)s/i2p/plugins/\">here</a>."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:434
+#, python-format
+msgid ""
+"Cache for Gnutella peers on I2P. Website for plugin version\n"
+"<a href=\"http://%(stats)s/i2p/plugins/\">here</a>."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:449
+msgid ""
+"OpenBSD's rewrite of the Unix standard tool, netcat, for socket relaying."
+"\n"
+"Several clones, ports, and forks have appeared over the years."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:458
+msgid "Like netcat but more powerful."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:464
+msgid ""
+"Proxy providing simple, transparent SOCKS-ification of network "
+"applications."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:474
+msgid ""
+"Most popular implementation of the Secure Shell (SSH) protocol and "
+"related tools."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:480
+msgid "Open source Secure Shell (SSH) client for Windows."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:492
+msgid "IM client with multiple incarnations, unsuported."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:499
+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"
+"<code>/me</code> command) which isn't inherently dangerous."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:510
+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 <a href=\"http://www.wireshark.org/\">Wireshark</a> 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:522
+#, python-format
+msgid ""
+"Small Java-based IRC client. Plugin available <a href=\n"
+"\"http://%(stats)s/i2p/plugins/\">here</a>."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:531
+msgid "Cross-platform graphical IRC client based on XChat."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:537
+msgid "Unixy terminal-based IRC client."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:543
+msgid "Another Unixy terminal-based IRC client."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:553
+msgid "IRC server developed from scratch."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:559
+msgid "Most popular IRC server."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:571
+msgid ""
+"Any website hosted anonymously on I2P, reachable through the I2P router's"
+" HTTP proxy."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:579
+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:589
+#, python-format
+msgid ""
+"Website for <a href=\"http://%(sponge)s/\">sponge's</a> jump service.\n"
+"Source code available."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:598
+msgid "Another jump service."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:604
+msgid "Dynamically updated eepsite index."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:610
+#, python-format
+msgid "Website for <a href=\"http://%(zzz)s/\">zzz's</a> jump service."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:620
+msgid "SOCKS-enabled caching web proxy with basic filtering capabilities."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:626
+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:635
+msgid "Venerable caching web proxy."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:642
+msgid "Gateways allowing users on the public Internet to access eepsites."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:649
+#, python-format
+msgid ""
+"<a href=\"http://%(tino)s/\">tino's</a> inproxy on the public Internet,\n"
+"currently out of service,"
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:658
+#: i2p2www/pages/site/docs/applications/supported.html:667
+#: i2p2www/pages/site/docs/applications/supported.html:674
+msgid "Another inproxy on the public Internet."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:683
+msgid ""
+"Gateways allowing I2P users to access content hosted on the public "
+"Internet."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:690
+msgid "Publicly advertised outproxy running Squid, located in Europe."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:700
+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 <a href=\"http://127.0.0.1:7658/\">user's eepsite</a>. 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:712
+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:721
+msgid "Most popular web server on the public WWW."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:727
+msgid "Web server and Java servlet container. More features than Jetty."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:733
+msgid "Fast lightweight web server."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:739
+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 <a href=\"%(naming)s\">the naming page</a> 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 <a "
+"href=\"#alternatives\">alternate naming systems</a> 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 <a href=\"https://zooko.com/distnames.html\">Names: "
+"Decentralized, Secure, Human-Meaningful: Choose Two</a>."
+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 <b>not globally"
+" \n"
+"unique</b>.  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 <b>locally unique</b>: "
+"they are \n"
+"what <i>you</i> 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 ""
+"<b>Inefficiency:</b>\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 <a href=\"http://%(i2host)s/\">%(i2host)sp</a>),\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"
+"<a href=\"%(url)s\">%(url)s</a>.\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 ""
+"<b>Not Scalable:</b>\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 ""
+"<b>Requires configuration and \"trust\":</b>\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 "<b>It isn't DNS</b>"
+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 ""
+"<b>Not reliable:</b>\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 ""
+"<b>Awkward, not real-time:</b>\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 ""
+"<b>Meta</b> - 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 ""
+"<b>PetName</b> - 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 "<b>HostsTxt</b> - Looks up in the following files, in order:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/discussions/naming.html:234
+msgid ""
+"<b>AddressDB</b> - Each host is listed in a separate file in a addressDb/"
+" directory."
+msgstr ""
+
+#: i2p2www/pages/site/docs/discussions/naming.html:237
+msgid ""
+"<b>Eepget</b> - 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 ""
+"<b>Exec</b> - 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 "<b>Dummy</b> - 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 <a "
+"href=\"%(todo)s#hashcash\">proof of work</a>."
+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/elgamal-aes.html:2
+msgid "ElGamal/AES + SessionTag Encryption"
+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:508
+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:524
+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:</p>"
+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"
+"<a href=\"%(commonstructures)s#type_SessionKey\">Session Key</a>\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"
+"<a href=\"%(cryptography)s#elgamal\">using ElGamal</a>\n"
+"and the encrypted block is 514 bytes long.\n"
+"</p>"
+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:254
+msgid "Minimum length: 48 bytes"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/elgamal-aes.html:257
+#, python-format
+msgid ""
+"The data is then <a href=\"%(cryptography)s\">AES Encrypted</a>,\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"
+"</p>"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/elgamal-aes.html:266
+#, python-format
+msgid ""
+"Actual max payload length, and max block length, is less than 64 KB; see "
+"the <a href=\"%(i2np)s\">I2NP Overview</a>."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/elgamal-aes.html:269
+msgid "New Session Key is currently unused and is never present."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/elgamal-aes.html:274
+msgid "Existing Session Message Specification"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/elgamal-aes.html:275
+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:283
+msgid ""
+"The existing session message is\n"
+"as follows:"
+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 <a "
+"href=\"#new\">New Session Message</a>."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/elgamal-aes.html:331
+msgid "Session Tag Configuration Options"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/elgamal-aes.html:332
+#, python-format
+msgid ""
+"As of release 0.9.2, the client may configure the default number of "
+"Session Tags to send\n"
+"and the low tag threshold for the current session.\n"
+"For brief streaming connections or datagrams, these options may be used "
+"to significantly reduce bandwidth.\n"
+"See the <a href=\"%(i2cp)s#options\">I2CP options specification</a> for "
+"details.\n"
+"The session settings may also be overridden on a per-message basis.\n"
+"See the <a href=\"%(i2cpspec)s#msg_SendMessageExpires\">I2CP Send Message"
+" Expires specification</a> for details."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/elgamal-aes.html:345
+msgid ""
+"There are many possible areas to tune the Session Key Manager's "
+"algorithms;\n"
+"some may interact with the streaming library behavior, or have "
+"significant\n"
+"impact on overall performance."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/elgamal-aes.html:352
+msgid ""
+"The number of tags delivered could depend on message size, keeping in "
+"mind\n"
+"the eventual padding to 1KB at the tunnel message layer."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/elgamal-aes.html:357
+msgid ""
+"Clients could send an estimate of session lifetime to the router, as an "
+"advisory\n"
+"on the number of tags required."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/elgamal-aes.html:362
+msgid ""
+"Delivery of too few tags causes the router to fall back to an expensive "
+"ElGamal encryption."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/elgamal-aes.html:366
+msgid ""
+"The router may assume delivery of Session Tags, or await acknowledgement "
+"before using them;\n"
+"there are tradeoffs for each strategy."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/elgamal-aes.html:371
+msgid ""
+"For very brief messages, almost the full 222 bytes of the pre-IV and "
+"padding fields in the ElGamal block\n"
+"could be used for the entire message, instead of establishing a session."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/elgamal-aes.html:376
+msgid ""
+"Evaluate padding strategy; currently we pad to a minimum of 128 bytes.\n"
+"Would be better to add a few tags to small messages than pad."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/elgamal-aes.html:381
+msgid ""
+"Perhaps things could be more efficient if the Session Tag system was "
+"bidirectional,\n"
+"so tags delivered in the 'forward' path could be used in the 'reverse' "
+"path,\n"
+"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:389
+#, python-format
+msgid ""
+"Change from Session Tags to\n"
+"<a href=\"%(futureperf)s#prng\">a synchronized PRNG</a>."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/elgamal-aes.html:394
+#, python-format
+msgid ""
+"Several of these ideas may require a new I2NP message type, or\n"
+"set a flag in the\n"
+"<a "
+"href=\"%(tunnelmessage)s#struct_TunnelMessageDeliveryInstructions\">Delivery"
+" Instructions</a>,\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:3
+msgid "March 2014"
+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"
+"<a href=\"http://www.cs.princeton.edu/~mfreed/\">Michael J. Freedman</a>\n"
+"in Roger Dingledine's Free Haven \n"
+"<a href=\"http://www.freehaven.net/papers.html\">Master's thesis</a> "
+"Section 8.1.1 (June 2000), as derived from \n"
+"<a href=\"http://www.onion-router.net/\">Onion Routing</a>."
+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 <a href=\"%(comparisons)s\">network comparisons</a>) 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"
+"<a href=\"http://www.onion-router.net/Publications.html\">large amount of"
+" academic research on onion routing</a>,\n"
+"<a href=\"http://freehaven.net/anonbib/topic.html\">Tor, and similar "
+"mixnets</a>."
+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"
+"<a href=\"%(elgamalaes)s\">ElGamal/AES+SessionTag</a> 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"
+"<a href=\"%(tunnelimpl)s\">tunnel implementation page</a>.\n"
+"Tunnel building details are defined on\n"
+"<a href=\"%(tunnelcreation)s\">this page</a>.\n"
+"We use\n"
+"<a href=\"%(elgamalaes)s\">ElGamal/AES+SessionTag</a> 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"
+"<a href=\"%(i2np)s\">I2NP messages</a>, and\n"
+"<a href=\"%(i2npspec)s#msg_Garlic\">Garlic Messages</a> are not used to "
+"build tunnels.\n"
+"We do not bundle multiple\n"
+"<a href=\"%(i2np)s\">I2NP messages</a> into a single\n"
+"<a href=\"%(i2npspec)s#msg_Garlic\">Garlic Message</a> 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"
+"<a href=\"%(commonstructures)s#struct_Destination\">Destinations</a>.\n"
+"Just as within a single tunnel, we use\n"
+"<a href=\"%(elgamalaes)s\">ElGamal/AES+SessionTag</a> for the encryption."
+"\n"
+"Each client message as delivered to the router through the\n"
+"<a href=\"%(i2cp)s\">I2CP interface</a> becomes a single\n"
+"<a href=\"%(i2npspec)s#struct_GarlicClove\">Garlic Clove</a>\n"
+"with its own\n"
+"<a href=\"%(i2npspec)s#struct_GarlicCloveDeliveryInstructions\">Delivery "
+"Instructions</a>,\n"
+"inside a\n"
+"<a href=\"%(i2npspec)s#msg_Garlic\">Garlic Message</a>.\n"
+"Delivery Instructions may specify a Destination, Router, or Tunnel."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/garlic-routing.html:171
+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:176
+msgid "Garlic Message Cloves"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/garlic-routing.html:179
+#, python-format
+msgid ""
+"A\n"
+"<a href=\"%(i2npspec)s#msg_DeliveryStatus\">Delivery Status Message</a>,\n"
+"with\n"
+"<a href=\"%(i2npspec)s#struct_GarlicCloveDeliveryInstructions\">Delivery "
+"Instructions</a>\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:192
+#, python-format
+msgid ""
+"A\n"
+"<a href=\"%(i2npspec)s#msg_DatabaseStore\">Database Store Message</a>,\n"
+"containing a\n"
+"<a href=\"%(commonstructures)s#struct_LeaseSet\">LeaseSet</a>\n"
+"for the originating Destination, with\n"
+"<a href=\"%(i2npspec)s#struct_GarlicCloveDeliveryInstructions\">Delivery "
+"Instructions</a>\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"
+"<a href=\"%(netdb)s\">network database page</a>."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/garlic-routing.html:210
+#, python-format
+msgid ""
+"By default, the Delivery Status and Database Store Messages\n"
+"are bundled when the local LeaseSet changes, when additional\n"
+"<a href=\"%(commonstructures)s#type_SessionTag\">Session Tags</a>\n"
+"are delivered, or if the messages have not been bundled in the previous "
+"minute.\n"
+"As of release 0.9.2, the client may configure the default number of "
+"Session Tags to send\n"
+"and the low tag threshold for the current session.\n"
+"See the <a href=\"%(i2cp)s#options\">I2CP options specification</a> for "
+"details.\n"
+"The session settings may also be overridden on a per-message basis.\n"
+"See the <a href=\"%(i2cpspec)s#msg_SendMessageExpires\">I2CP Send Message"
+" Expires specification</a> for details."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/garlic-routing.html:224
+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:229
+msgid ""
+"As of release 0.9.12, the Delivery Status Message is wrapped in another "
+"Garlic Message\n"
+"by the originator so that the contents are encrypted and not visible to "
+"routers on the return path."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/garlic-routing.html:235
+msgid "Storage to the Floodfill Network Database"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/garlic-routing.html:236
+#, python-format
+msgid ""
+"As explained on the\n"
+"<a href=\"%(netdb)s#delivery\">network database page</a>,\n"
+"local\n"
+"<a href=\"%(commonstructures)s#struct_LeaseSet\">LeaseSets</a>\n"
+"are sent to floodfill routers in a\n"
+"<a href=\"%(i2npspec)s#msg_DatabaseStore\">Database Store Message</a>\n"
+"wrapped in a\n"
+"<a href=\"%(i2npspec)s#msg_Garlic\">Garlic Message</a>\n"
+"so it is not visible to the tunnel's outbound gateway."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/garlic-routing.html:252
+#, 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"
+"<a "
+"href=\"%(tunnelmessage)s#struct_TunnelMessageDeliveryInstructions\">tunnel"
+" message Delivery Instructions</a>,\n"
+"a wide spectrum of batching, delay, mixing, and routing strategies are "
+"possible."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/garlic-routing.html:260
+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:267
+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:273
+#, python-format
+msgid ""
+"As a part of\n"
+"<a href=\"%(elgamalaes)s\">ElGamal/AES encryption</a>,\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:282
+#, python-format
+msgid ""
+"Encryption of additional messages to and from the\n"
+"<a href=\"%(netdb)s#delivery\">floodfill routers</a>."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/garlic-routing.html:290
+#: i2p2www/pages/site/docs/how/peer-selection.html:296
+msgid "References"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/garlic-routing.html:292
+msgid ""
+"The term garlic routing was first coined in Roger Dingledine's Free Haven"
+" \n"
+"<a href=\"http://www.freehaven.net/papers.html\">Master's thesis</a> "
+"(June 2000),\n"
+"see Section 8.1.1 authored by\n"
+"<a href=\"http://www.cs.princeton.edu/~mfreed/\">Michael J. Freedman</a>."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/garlic-routing.html:299
+msgid "Onion router publications"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/garlic-routing.html:301
+msgid "Onion Routing on Wikipedia"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/garlic-routing.html:303
+msgid "Garlic Routing on Wikipedia"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/garlic-routing.html:305
+#, python-format
+msgid ""
+"<a href=\"%(meeting58)s\">I2P Meeting 58</a> (2003) discussing the "
+"implementation of garlic routing"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/garlic-routing.html:311
+msgid "Free Haven publications"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/garlic-routing.html:313
+msgid ""
+"Onion routing was first described in <a href=\"http://www.onion-"
+"router.net/Publications/IH-1996.pdf\">Hiding Routing Information</a>\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 to How I2P Works"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/intro.html:4
+msgid ""
+"I2P is a project to build, deploy, and maintain a network supporting "
+"secure and anonymous\n"
+"communication. People using I2P are in control of the tradeoffs between "
+"anonymity, reliability,\n"
+"bandwidth usage, and latency. There is no central point in the network on"
+" which pressure can be\n"
+"exerted to compromise the integrity, security, or anonymity of the "
+"system. The network supports\n"
+"dynamic reconfiguration in response to various attacks, and has been "
+"designed to make use of\n"
+"additional resources as they become available. Of course, all aspects of "
+"the network are open and\n"
+"freely available."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/intro.html:14
+msgid ""
+"Unlike many other anonymizing networks, I2P doesn't try to provide "
+"anonymity by hiding the\n"
+"originator of some communication and not the recipient, or the other way "
+"around. I2P is designed to\n"
+"allow peers using I2P to communicate with each other anonymously &mdash; "
+"both sender and recipient\n"
+"are unidentifiable to each other as well as to third parties. For "
+"example, today there are both\n"
+"in-I2P web sites (allowing anonymous publishing / hosting) as well as "
+"HTTP proxies to the normal web\n"
+"(allowing anonymous web browsing). Having the ability to run servers "
+"within I2P is essential, as it\n"
+"is quite likely that any outbound proxies to the normal Internet will be "
+"monitored, disabled, or\n"
+"even taken over to attempt more malicious attacks."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/intro.html:25
+#, python-format
+msgid ""
+"The network itself is message oriented - it is essentially a secure and "
+"anonymous IP layer, where\n"
+"messages are addressed to cryptographic keys (Destinations) and can be "
+"significantly larger than IP\n"
+"packets. Some example uses of the network include \"eepsites\" "
+"(webservers hosting normal web\n"
+"applications within I2P), a BitTorrent client (\"I2PSnark\"), or a "
+"distributed data store. With the\n"
+"help of the <a href=\"%(i2ptunnel)s\">I2PTunnel</a> application, we are "
+"able to stream traditional\n"
+"TCP/IP applications over I2P, such as SSH, IRC, a squid proxy, and even "
+"streaming audio. Most people\n"
+"will not use I2P directly, or even need to know they're using it. Instead"
+" their view will be of one\n"
+"of the I2P enabled applications, or perhaps as a little controller app to"
+" turn on and off various\n"
+"proxies to enable the anonymizing functionality."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/intro.html:37
+#, python-format
+msgid ""
+"An essential part of designing, developing, and testing an anonymizing "
+"network is to define the <a\n"
+"href=\"%(threatmodel)s\">threat model</a>, 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, <i>all on the same network</i>, where each one's messages are "
+"essentially indistinguishable\n"
+"from the others."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/intro.html:48
+msgid "Why?"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/intro.html:49
+#, python-format
+msgid ""
+"There are a multitude of reasons why we need a system to support "
+"anonymous communication, and\n"
+"everyone has their own personal rationale. There are many <a "
+"href=\"%(comparisons)s\">other\n"
+"efforts</a> 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:56
+msgid "How?"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/intro.html:58
+#, python-format
+msgid ""
+"The network at a glance is made up of a set of nodes (\"routers\") with a"
+" number of unidirectional\n"
+"inbound and outbound virtual paths (\"tunnels\", as outlined on the <a "
+"href=\"%(tunnelrouting)s\">tunnel routing</a> 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"
+"<a href=\"%(netdb)s\">network database</a> (using a modification of the "
+"Kademlia algorithm) for\n"
+"distributing routing and contact information securely."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/intro.html:71
+msgid "Network topology example"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/intro.html:73
+msgid ""
+"In the above, Alice, Bob, Charlie, and Dave are all running routers with "
+"a single Destination on\n"
+"their local router. They each have a pair of 2-hop inbound tunnels per "
+"destination (labeled 1, 2, 3,\n"
+"4, 5 and 6), and a small subset of each of those router's outbound tunnel"
+" pool is shown with 2-hop\n"
+"outbound tunnels. For simplicity, Charlie's inbound tunnels and Dave's "
+"outbound tunnels are not\n"
+"shown, nor are the rest of each router's outbound tunnel pool (typically "
+"stocked with a few tunnels\n"
+"at a time). When Alice and Bob talk to each other, Alice sends a message "
+"out one of her (pink)\n"
+"outbound tunnels targeting one of Bob's (green) inbound tunnels (tunnel 3"
+" or 4). She knows to send\n"
+"to those tunnels on the correct router by querying the network database, "
+"which is constantly updated\n"
+"as new leases are authorized and old ones expire."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/intro.html:85
+#, python-format
+msgid ""
+"If Bob wants to reply to Alice, he simply goes through the same process -"
+" send a message out one of\n"
+"his outbound tunnels targeting one of Alice's inbound tunnels (tunnel 1 "
+"or 2). To make things\n"
+"easier, most messages sent between Alice and Bob are <a "
+"href=\"%(garlicrouting)s\">garlic</a>\n"
+"wrapped, bundling the sender's own current lease information so that the "
+"recipient can reply\n"
+"immediately without having to look in the network database for the "
+"current data."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/intro.html:93
+#, python-format
+msgid ""
+"To deal with a wide range of attacks, I2P is fully distributed with no "
+"centralized resources - and\n"
+"hence there are no directory servers keeping statistics regarding the "
+"performance and reliability of\n"
+"routers within the network. As such, each router must keep and maintain "
+"profiles of various routers\n"
+"and is responsible for selecting appropriate peers to meet the anonymity,"
+" performance, and\n"
+"reliability needs of the users, as described in the <a "
+"href=\"%(peerselection)s\">peer selection</a>\n"
+"page."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/intro.html:102
+#, python-format
+msgid ""
+"The network itself makes use of a significant number of <a "
+"href=\"%(cryptography)s\">cryptographic\n"
+"techniques and algorithms</a> - 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 <a "
+"href=\"%(elgamalaes)s\">ElGamal / AES+SessionTag</a>."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/intro.html:110
+msgid ""
+"Content sent over I2P is encrypted through three layers garlic encryption"
+" (used to verify the\n"
+"delivery of the message to the recipient), tunnel encryption (all "
+"messages passing through a tunnel\n"
+"is encrypted by the tunnel gateway to the tunnel endpoint), and inter "
+"router transport layer\n"
+"encryption (e.g. the TCP transport uses AES256 with ephemeral keys)."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/intro.html:117
+msgid ""
+"End-to-end (I2CP) encryption (client application to server application) "
+"was disabled in I2P release\n"
+"0.6; end-to-end (garlic) encryption (I2P client router to I2P server "
+"router) from Alice's router \"a\"\n"
+"to Bob's router \"h\" remains. Notice the different use of terms! All "
+"data from a to h is end-to-end\n"
+"encrypted, but the I2CP connection between the I2P router and the "
+"applications is not end-to-end\n"
+"encrypted! A and h are the routers of Alice and Bob, while Alice and Bob "
+"in following chart are the\n"
+"applications running atop of I2P."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/intro.html:126
+msgid "End to end layered encryption"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/intro.html:128
+#, python-format
+msgid ""
+"The specific use of these algorithms are outlined <a "
+"href=\"%(cryptography)s\">elsewhere</a>."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/intro.html:132
+msgid ""
+"The two main mechanisms for allowing people who need strong anonymity to "
+"use the network are\n"
+"explicitly delayed garlic routed messages and more comprehensive tunnels "
+"to include support for\n"
+"pooling and mixing messages. These are currently planned for release 3.0,"
+" but garlic routed messages\n"
+"with no delays and FIFO tunnels are currently in place. Additionally, the"
+" 2.0 release will allow\n"
+"people to set up and operate behind restricted routes (perhaps with "
+"trusted peers), as well as the\n"
+"deployment of more flexible and anonymous transports."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/intro.html:141
+#, python-format
+msgid ""
+"Some questions have been raised with regards to the scalability of I2P, "
+"and reasonably so. There\n"
+"will certainly be more analysis over time, but peer lookup and "
+"integration should be bounded by\n"
+"<code>O(log(N))</code> due to the <a href=\"%(netdb)s\">network "
+"database</a>'s algorithm, while end\n"
+"to end messages should be <code>O(1)</code> (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:150
+msgid "When?"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/intro.html:151
+#, python-format
+msgid ""
+"I2P initially began in Feb 2003 as a proposed modification to <a\n"
+"href=\"http://freenetproject.org\">Freenet</a> to allow it to use "
+"alternate transports, such as <a\n"
+"href=\"%(jms)s\">JMS</a>, 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"
+" <a href=\"%(roadmap)s\">roadmap</a>."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/intro.html:161
+msgid "Who?"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/intro.html:162
+#, python-format
+msgid ""
+"We have a small <a href=\"%(team)s\">team</a> 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 <a href=\"http://java.com/en/\">Sun Java SE</a> and other Java Virtual"
+" Machines."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/intro.html:173
+msgid "Where?"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/intro.html:174
+#, python-format
+msgid ""
+"Anyone interested should join us on the IRC channel #i2p-dev (hosted "
+"concurrently on irc.freenode.net,\n"
+"irc.postman.i2p, irc.echelon.i2p, irc.dg.i2p and irc.oftc.net). There are"
+" currently no\n"
+"scheduled development meetings, however <a href=\"%(meetings)s\">archives"
+" are available</a>."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/intro.html:180
+#, python-format
+msgid "The current source is available in <a href=\"%(monotone)s\">monotone</a>."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/intro.html:185
+#, python-format
+msgid "See <a href=\"%(docs)s\">the Index to Technical Documentation</a>."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:2
+msgid "The Network Database"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:3
+msgid "April 2018"
+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 (<b>RouterInfos</b>) "
+"and destination contact\n"
+"information (<b>LeaseSets</b>). 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 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 signing key"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:39
+msgid "Expected Options"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:41
+msgid ""
+"The following text options, while not strictly required, are expected\n"
+"to be present:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:47
+msgid ""
+"Capabilities flags - used to indicate floodfill participation, "
+"approximate bandwidth, and perceived reachability"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:49
+#: i2p2www/pages/site/docs/how/network-database.html:287
+msgid "Floodfill"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:50
+msgid "Hidden"
+msgstr "Gizli"
+
+#: i2p2www/pages/site/docs/how/network-database.html:51
+#, python-format
+msgid "Under %(amount)s shared bandwidth"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:52
+#: i2p2www/pages/site/docs/how/network-database.html:53
+#: i2p2www/pages/site/docs/how/network-database.html:54
+#: i2p2www/pages/site/docs/how/network-database.html:55
+#: i2p2www/pages/site/docs/how/network-database.html:56
+#, python-format
+msgid "%(amount)s shared bandwidth"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:52
+msgid "default"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:57
+msgid "Reachable"
+msgstr "Əlçatan"
+
+#: i2p2www/pages/site/docs/how/network-database.html:58
+msgid "Unreachable"
+msgstr "Əlçatmaz"
+
+#: i2p2www/pages/site/docs/how/network-database.html:59
+#, python-format
+msgid "Over %(amount)s shared bandwidth"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:66
+msgid "The core library version, always the same as the router version"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:70
+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:73
+msgid "Used to determine compatibility with newer features and messages"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:76
+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 uptime was more than 60m"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:82
+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:91
+msgid "Additional Options"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:93
+#, 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 <a href=\"http://%(stats)s/\">%(stats)s</a>\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:104
+msgid "Exploratory tunnel build success, reject, and timeout rates"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:105
+msgid "1 hour average number of participating tunnels"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:108
+msgid ""
+"Floodfill routers publish additional data on the number of entries in "
+"their network database."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:112
+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:119
+msgid "Family Options"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:121
+msgid ""
+"As of release 0.9.24, routers may declare that they are part of a "
+"\"family\", operated by the same entity.\n"
+"Multiple routers in the same family will not be used in a single tunnel."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:126
+msgid "The family options are:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:132
+msgid "The family name"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:147
+msgid "RouterInfo Expiration"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:148
+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:155
+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:158
+msgid "There is no expiration if there are 25 or less RouterInfos."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:161
+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:166
+#, python-format
+msgid ""
+"RouterInfos containing <a href=\"%(ssu)s\">SSU</a> 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:170
+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:176
+msgid "RouterInfo Persistent Storage"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:178
+msgid ""
+"RouterInfos are periodically written to disk so that they are available "
+"after a restart."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:186
+msgid "RouterInfo specification"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:189
+msgid "RouterInfo Javadoc"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:194
+msgid ""
+"The second piece of data distributed in the netDb is a \"LeaseSet\" - "
+"documenting\n"
+"a group of <b>tunnel entry points (leases)</b> for a particular client "
+"destination.\n"
+"Each of these leases specify the following information:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:200
+msgid "The tunnel gateway router (by specifying its identity)"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:201
+msgid "The tunnel ID on that router to send messages with (a 4 byte number)"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:202
+msgid "When that tunnel will expire."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:204
+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:209
+msgid "In addition to these leases, the LeaseSet includes:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:213
+msgid ""
+"The destination itself (a 2048bit ElGamal encryption key, a signing key "
+"and a certificate)"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:214
+msgid ""
+"Additional encryption public key: used for end-to-end encryption of "
+"garlic messages"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:215
+msgid ""
+"Additional signing public key: intended for LeaseSet revocation, but is "
+"currently unused."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:216
+msgid ""
+"Signature of all the LeaseSet data, to make sure the Destination "
+"published the LeaseSet."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:220
+msgid "Lease specification"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:222
+msgid "LeaseSet specification"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:225
+msgid "Lease Javadoc"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:227
+msgid "LeaseSet Javadoc"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:231
+msgid "Unpublished LeaseSets"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:232
+msgid ""
+"A LeaseSet for a destination used only for outgoing connections is "
+"<i>unpublished</i>.\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 <a href=\"#lsp\">I2NP storage messages</a>."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:242
+msgid "Revoked LeaseSets"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:243
+msgid ""
+"A LeaseSet may be <i>revoked</i> 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:250
+msgid "Encrypted LeaseSets"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:251
+msgid ""
+"In an <i>encrypted</i> LeaseSet, all Leases are encrypted with a separate"
+" 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:260
+msgid "LeaseSet Expiration"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:261
+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:266
+msgid "LeaseSet Persistent Storage"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:267
+msgid ""
+"There is no persistent storage of LeaseSet data since they expire so "
+"quickly."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:272
+msgid "Bootstrapping"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:273
+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 "
+"<code>routerInfo-$hash.dat</code>\n"
+"file and storing it in your <code>netDb/</code> 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:288
+msgid ""
+"The floodfill netDb is a simple distributed storage mechanism.  The "
+"storage\n"
+"algorithm is simple: send the data to the closest peer that has "
+"advertised\n"
+"itself as a floodfill router. When the peer in the floodfill netDb "
+"receives a\n"
+"netDb store from a peer not in the floodfill netDb, they send it to a "
+"subset of\n"
+"the floodfill netDb-peers. The peers selected are the ones closest "
+"(according\n"
+"to the <a href=\"#kad\">XOR-metric</a>) to a specific key."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:297
+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:302
+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:309
+msgid "Floodfill Router Opt-in"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:311
+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:318
+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:328
+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:334
+msgid ""
+"With the current rules for automatic opt-in, approximately 6&#37; of\n"
+"the routers in the network are floodfill routers."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:339
+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:349
+msgid "Floodfill Router Roles"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:350
+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:358
+msgid "Kademlia Closeness Metric"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:359
+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 <a href"
+"=\"#sybil-partial\">Sybil attacks</a>.\n"
+"Instead of the SHA256 hash of the key being looked up of stored, the "
+"SHA256 hash is taken\n"
+"of the 32-byte binary search key appended with the UTC date represented "
+"as an 8-byte ASCII string yyyyMMdd, i.e. SHA256(key + yyyyMMdd).\n"
+"This is called the \"routing key\", and it changes every day at midnight "
+"UTC.\n"
+"Only the search key is modified in this way, not the floodfill router "
+"hashes.\n"
+"The daily transformation of the DHT is sometimes called \"keyspace "
+"rotation\",\n"
+"although it isn't strictly a rotation."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:372
+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:379
+msgid "Storage, Verification, and Lookup Mechanics"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:381
+msgid "RouterInfo Storage to Peers"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:382
+#, python-format
+msgid ""
+"<a href=\"%(i2np)s\">I2NP</a> DatabaseStoreMessages containing the local "
+"RouterInfo are exchanged with peers\n"
+"as a part of the initialization of a <a href=\"%(ntcp)s\">NTCP</a>\n"
+"or <a href=\"%(ssu)s\">SSU</a> transport connection."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:389
+msgid "LeaseSet Storage to Peers"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:390
+#, python-format
+msgid ""
+"<a href=\"%(i2np)s\">I2NP</a> 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:398
+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:407
+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:420
+msgid "RouterInfo Storage to Floodfills"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:421
+#, python-format
+msgid ""
+"A router publishes its own RouterInfo by directly connecting to a "
+"floodfill router\n"
+"and sending it a <a href=\"%(i2np)s\">I2NP</a> 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"
+"<a href=\"%(i2np)s\">I2NP</a> DeliveryStatusMessage,\n"
+"with the Message ID set to the value of the Reply Token."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:435
+msgid "LeaseSet Storage to Floodfills"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:436
+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:441
+#, python-format
+msgid ""
+"A router publishes a local LeaseSet by\n"
+"sending a <a href=\"%(i2np)s\">I2NP</a> 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"
+"<a href=\"%(i2np)s\">I2NP</a> 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:454
+msgid "Flooding"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:455
+#, 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:466
+#, python-format
+msgid ""
+"The floodfill then directly connects to each of those peers\n"
+"and sends it a <a href=\"%(i2np)s\">I2NP</a> 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:476
+msgid "RouterInfo and LeaseSet Lookup"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:477
+#, python-format
+msgid ""
+"The <a href=\"%(i2np)s\">I2NP</a> 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:483
+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:487
+#, python-format
+msgid ""
+"If the key is found locally by the floodfill router, it responds with a\n"
+"<a href=\"%(i2np)s\">I2NP</a> DatabaseStoreMessage.\n"
+"If the key is not found locally by the floodfill router, it responds with"
+" a\n"
+"<a href=\"%(i2np)s\">I2NP</a> DatabaseSearchReplyMessage\n"
+"containing a list of other floodfill routers close to the key."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:495
+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:502
+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:509
+#, python-format
+msgid ""
+"(Reference: <a href=\"%(pdf)s\">Hashing it out in Public</a> Sections "
+"2.2-2.3 for terms below in italics)"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:513
+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 <i>recursive</i> nor <i>iterative</i> routing for lookups was "
+"implemented.\n"
+"Queries were sent through <i>multiple routes simultaneously</i>\n"
+"to <i>reduce the chance of query failure</i>."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:524
+msgid ""
+"As of release 0.8.9, <i>iterative lookups</i> 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:536
+msgid ""
+"<i>Node IDs</i> are <i>verifiable</i> 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"
+"<i>detailed knowledge of the neighborhood of the destination ID space</i>."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:545
+msgid "RouterInfo Storage Verification"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:546
+#, 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"
+"<a href=\"%(egger2013)s\">Practical Attacks Against the I2P Network</a>.\n"
+"It is not clear if verification can be redesigned to be done safely."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:553
+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:561
+msgid "LeaseSet Storage Verification"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:562
+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:572
+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:580
+msgid "Exploration"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:581
+#, python-format
+msgid ""
+"<i>Exploration</i> 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 <a "
+"href=\"%(i2np)s\">I2NP</a> DatabaseLookupMessage, looking for a random "
+"key.\n"
+"As this lookup will fail, the floodfill would normally respond with a\n"
+"<a href=\"%(i2np)s\">I2NP</a> 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:595
+msgid "Notes on Lookup Responses"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:596
+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:606
+msgid "MultiHoming"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:608
+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:618
+msgid "Threat Analysis"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:619
+#, python-format
+msgid ""
+"Also discussed on <a href=\"%(threatmodel)s#floodfill\">the threat model "
+"page</a>."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:623
+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:630
+msgid "General Mitigation Through Growth"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:631
+#, 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:638
+msgid "General Mitigation Through Redundancy"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:639
+#, 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:644
+msgid "Forgeries"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:645
+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:650
+msgid "Slow or Unresponsive"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:651
+#, python-format
+msgid ""
+"Each router maintains an expanded set of statistics in the\n"
+"<a href=\"%(peerselection)s\">peer profile</a> 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:658
+msgid "Average response time"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:659
+msgid "Percentage of queries answered with the data requested"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:660
+msgid "Percentage of stores that were successfully verified"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:661
+msgid "Last successful store"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:662
+msgid "Last successful lookup"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:663
+msgid "Last response"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:666
+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:676
+msgid "Sybil Attack (Full Keyspace)"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:677
+#, python-format
+msgid ""
+"An attacker may mount a <a href=\"%(url)s\">Sybil attack</a>\n"
+"by creating a large number of floodfill routers spread throughout the "
+"keyspace."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:682
+#, python-format
+msgid ""
+"(In a related example, a researcher recently created a\n"
+"<a href=\"%(url)s\">large number of Tor relays</a>.)\n"
+"If successful, this could be an effective DOS attack on the entire "
+"network."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:688
+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:696
+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:701
+msgid ""
+"Ask everyone in the network to enable floodfill manually (fight Sybil "
+"with more Sybil)"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:702
+msgid "Release a new software version that includes the hardcoded \"bad\" list"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:703
+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:707
+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:708
+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:717
+msgid "This attack becomes more difficult as the network size grows."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:723
+msgid "Sybil Attack (Partial Keyspace)"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:724
+#, python-format
+msgid ""
+"An attacker may mount a <a href=\"%(url)s\">Sybil attack</a>\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:733
+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:741
+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:753
+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:761
+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:771
+msgid "Bootstrap Attacks"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:772
+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:779
+msgid "Several defenses are possible, and most of these are planned:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:783
+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:787
+msgid "Bundling reseed data in the installer"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:790
+msgid "Defenses that are implemented:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:794
+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:798
+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:803
+msgid ""
+"As of release 0.9.14, reseed data is bundled into a signed zip file and\n"
+"the signature is verified when downloaded."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:811
+msgid "Query Capture"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:812
+#, python-format
+msgid ""
+"See also <a href=\"#lookup\">lookup</a>\n"
+"(Reference: <a href=\"%(pdf)s\">Hashing it out in Public</a> Sections "
+"2.2-2.3 for terms below in italics)"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:817
+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:822
+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:829
+#, python-format
+msgid ""
+"As of release 0.8.9, <i>iterative lookups</i> are implemented.\n"
+"For floodfill router references returned in a\n"
+"<a href=\"%(i2np)s\">I2NP</a> 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 <i>verifiably correct</i>.\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"
+"<a href=\"%(pdf)s\">Hashing it out in Public</a>\n"
+"is much more difficult."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:848
+msgid "DHT-Based Relay Selection"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:849
+#, python-format
+msgid "(Reference: <a href=\"%(pdf)s\">Hashing it out in Public</a> Section 3)"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:853
+#, python-format
+msgid ""
+"This doesn't have much to do with floodfill, but see\n"
+"the <a href=\"%(peerselection)s\">peer selection page</a>\n"
+"for a discussion of the vulnerabilities of peer selection for tunnels."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:859
+msgid "Information Leaks"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:860
+#, python-format
+msgid ""
+"(Reference: <a href=\"%(pdf)s\">In Search of an Anonymous and Secure "
+"Lookup</a> Section 3)"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:864
+#, 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 <a href=\"%(peerselection)s\">peer "
+"selection</a> and\n"
+"<a href=\"%(tunnelrouting)s\">tunnel building</a> 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:875
+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:883
+#, 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 <i>f</i> = 0.2 (20&#37; malicious nodes, as "
+"specifed in the paper)\n"
+"we expect that many of the Sybil threats we describe\n"
+"(<a href=\"%(threatmodel)s#sybil\">here</a>,\n"
+"<a href=\"#sybil\">here</a> and\n"
+"<a href=\"#sybil-partial\">here</a>)\n"
+"become problematic for several reasons."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:897
+msgid "Moved to the netdb discussion page"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:901
+msgid "End-to-end encryption of additional netDb lookups and responses."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:905
+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 ""
+"<b>Peer profiling</b> is the process of collecting data based on the "
+"<b>observed</b> performance\n"
+"of other routers or peers, and classifying those peers into groups.\n"
+"Profiling does <b>not</b> use any claimed performance data published by "
+"the peer itself\n"
+"in the <a href=\"%(netdb)s\">network database</a>."
+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 <a href=\"%(netdb)s\">network database</a> 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:289
+msgid "Peer Selection"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/peer-selection.html:28
+msgid ""
+"<b>Peer selection</b> 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 <b>only</b> 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"
+"<a href=\"%(threatmodel)s#timing\">timing attacks</a>\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"
+"<a href=\"%(pdf)s\">Peer Profiling and Selection in the I2P Anonymous "
+"Network</a>\n"
+"presented at <a href=\"%(url)s\">PET-CON 2009.1</a>.\n"
+"See <a href=\"#notes\">below</a> 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 <a href=\"%(url)s\">code</a>."
+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"
+"<a href=\"%(url)s\">ProfileOrganizer</a>."
+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 <a href=\"http://blog.torproject.org/blog"
+"/one-cell-enough\">some attacks</a>,\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&#37; 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 <a href=\"%(pdf)s\">predecessor attack</a>\n"
+"<a href=\"%(pdf2008)s\">(2008 update)</a>.\n"
+"More information is on the <a href=\"%(tunnelimpl)s#ordering\">tunnel "
+"page</a>."
+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"
+"<a href=\"%(pdf)s\">Peer Profiling and Selection in the I2P Anonymous "
+"Network</a>,\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 "I2P: A scalable framework for anonymous communication"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:5
+#: i2p2www/pages/site/docs/how/tech-intro.html:20
+#: i2p2www/pages/site/docs/transport/ssu.html:342
+msgid "Introduction"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:7
+msgid "I2P Operation"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:12
+#: i2p2www/pages/site/docs/how/tech-intro.html:397
+msgid "Transport protocols"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:13
+#: i2p2www/pages/site/docs/how/tech-intro.html:454
+msgid "Cryptography"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:21
+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:30
+msgid ""
+"Applications available already provide the full range of typical Internet"
+" activities -\n"
+"<b>anonymous</b> 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:36
+msgid "Web browsing: using any existing browser that supports using a proxy."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:37
+msgid "Chat: IRC, Jabber, <a href=\"#app.i2pmessenger\">I2P-Messenger</a>."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:38
+msgid ""
+"File sharing: <a href=\"#app.i2psnark\">I2PSnark</a>, <a "
+"href=\"#app.robert\">Robert</a>, <a href=\"#app.imule\">iMule</a>, \n"
+"<a href=\"#app.i2phex\">I2Phex</a>, <a href=\"#app.pybit\">PyBit</a>, <a "
+"href=\"#app.i2pbt\">I2P-bt</a>\n"
+"and others."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:43
+msgid ""
+"E-mail: <a href=\"#app.i2pmail\">susimail</a> and <a href=\"#app.i2pbote"
+"\">I2P-Bote</a>."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:44
+msgid ""
+"Blog: using e.g. the pebble plugin or the distributed blogging software "
+"<a href=\"#app.syndie\">Syndie</a>."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:45
+msgid ""
+"Distributed Data Store: Save your data redundantly in the Tahoe-LAFS "
+"cloud over I2P."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:46
+msgid "Newsgroups: using any newsgroup reader that supports using a proxy."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:49
+msgid ""
+"Unlike web sites hosted within content distribution networks like <a "
+"href=\"#similar.freenet\">Freenet</a> \n"
+"or <a href=\"http://www.ovmj.org/GNUnet/\">GNUnet</a>, 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:57
+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 <a href=\"#app.streaming\">streaming</a> 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:74
+#, 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 <a "
+"href=\"%(site)s\">website</a>, \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 (<a "
+"href=\"#app.i2ptunnel\">I2PTunnel</a>, \n"
+"<a href=\"#app.i2pmail\">susimail</a>, <a "
+"href=\"#app.i2psnark\">I2PSnark</a>, <a href=\"#app.i2pbote\">I2P-"
+"Bote</a>, \n"
+"<a href=\"#app.i2phex\">I2Phex</a> and others.).\n"
+"<a href=\"%(halloffame)s\">Funding</a> 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:92
+msgid "Operation"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:94
+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:107
+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:118
+#: i2p2www/pages/site/docs/tunnels/implementation.html:105
+msgid "Inbound and outbound tunnel schematic"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:120
+msgid "Figure 1: Two types of tunnels exist: inbound and outbound."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:123
+msgid ""
+"Two types of tunnels exist:\n"
+"<b>\"outbound\" tunnels</b> send messages away from the tunnel creator,\n"
+"while <b>\"inbound\" tunnels</b> 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:140
+msgid ""
+"A third critical concept to understand is I2P's <b>\"network "
+"database\"</b> (or \"netDb\") \n"
+"- a pair of algorithms used to share network metadata. The two types of "
+"metadata \n"
+"carried are <b>\"routerInfo\"</b> and <b>\"leaseSets\"</b> - 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:151
+msgid "Inbound gateway for a tunnel that allows reaching a specific destination."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:152
+msgid "Time when a tunnel expires."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:153
+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:155
+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:160
+msgid ""
+"We can combine the above concepts to build successful connections in the "
+"network."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:164
+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:171
+msgid "Request information on other routers"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:173
+msgid "Build tunnel using router information"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:175
+msgid "Figure 2: Router information is used to build tunnels."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:178
+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"
+"<a href=\"#app.streaming\">streaming</a> 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:195
+msgid "Connect tunnels using LeaseSets"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:195
+msgid "Connect tunnels using leaseSets"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:197
+msgid "Figure 3: LeaseSets are used to connect outbound and inbound tunnels."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:200
+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 \"<a "
+"href=\"#op.garlic\">garlic \n"
+"encryption</a>\" 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:215
+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 <a href=\"#app.streaming\">streaming</a> library to view I2P as "
+"a streams \n"
+"based network."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:225
+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:240
+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:253
+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:266
+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:284
+msgid ""
+"Using this profile data, the simplest reasonable peer selection strategy "
+"is to\n"
+"pick peers randomly from the top tier (fast and high capacity), and this "
+"is\n"
+"currently deployed for client tunnels. Exploratory tunnels (used for "
+"netDb and\n"
+"tunnel management) pick peers randomly from the \"not failing\" tier "
+"(which\n"
+"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"
+"<a href=\"https://en.wikipedia.org/wiki/Hill_climbing\">hill "
+"climbing</a>. These\n"
+"strategies alone do however leak information regarding the peers in the\n"
+"router's top tier through predecessor and netDb harvesting attacks. In "
+"turn,\n"
+"several alternatives exist which, while not balancing the load as evenly,"
+" will\n"
+"address the attacks mounted by particular classes of adversaries."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:298
+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:318
+#, 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 <a href=\"%(tunnelimpl)s\">tunnel "
+"spec</a>."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:326
+#, python-format
+msgid ""
+"As mentioned earlier, I2P's netDb works to share the network's metadata.\n"
+"This is detailed in <a href=\"%(netdb)s\">the network database</a> page,\n"
+"but a basic explanation is available below."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:332
+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:339
+#, 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 <a href=\"http://en.wikipedia.org/wiki/Kademlia\">Kademlia "
+"algorithm</a>.\n"
+"The 'lookup' queries currently function differently, to avoid an "
+"important\n"
+"<a href=\"%(netdb)s#lookup\">security issue</a>.\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:349
+msgid "Two types of information are stored in the network database."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:353
+msgid ""
+"A <b>RouterInfo</b> stores information on a specific I2P router and how "
+"to contact it"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:354
+msgid ""
+"A <b>LeaseSet</b> stores information on a specific destination (e.g. I2P "
+"website, e-mail server...)"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:356
+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 <a href=\"http://www.pool.ntp.org/\">pool.ntp.org</a> round robin by"
+" default)\n"
+"and detecting skew between routers at the transport layer."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:364
+msgid "Some additional remarks are also important."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:369
+msgid "Unpublished and encrypted leasesets:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:370
+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:377
+msgid "Bootstrapping:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:378
+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:386
+msgid "Lookup scalability:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:387
+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:398
+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:406
+#, 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 <a href=\"%(ssu)s\">UDP-based one</a> - "
+"\"Secure \n"
+"Semireliable UDP\", or \"SSU\"."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:414
+#, python-format
+msgid "As described in the <a href=\"%(ssu)s\">SSU spec</a>:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:418
+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:428
+#, python-format
+msgid ""
+"Following the introduction of SSU, after issues with congestion collapse"
+" \n"
+"appeared, a new NIO-based TCP transport called <a "
+"href=\"%(ntcp)s\">NTCP</a> \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:438
+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:446
+#, 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 <a "
+"href=\"%(ntcp)s\">NTCP \n"
+"page</a>."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:455
+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. <a href=\"#op.tunnels\">Tunnel</a> 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:470
+msgid "Garlic messages"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:471
+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:486
+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 <a "
+"href=\"#future.variablelatency\">nontrivial \n"
+"delays</a> 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:499
+msgid "Session tags"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:500
+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:539
+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:549
+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:562
+msgid "Future"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:563
+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:569
+msgid "Restricted route operation"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:570
+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:582
+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:595
+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:617
+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:629
+msgid "Variable latency"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:630
+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:647
+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:655
+msgid "Open questions"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:657
+msgid "How to get rid of the timing constraint?"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:658
+msgid "Can we deal with the sessionTags more efficiently?"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:659
+msgid ""
+"What, if any, batching/mixing strategies should be made available on the "
+"tunnels?"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:660
+msgid ""
+"What other tunnel peer selection and ordering strategies should be "
+"available?"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:663
+msgid "Similar systems"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:665
+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:675
+#, python-format
+msgid "See also the <a href=\"%(comparisons)s\">Network Comparisons Page</a>."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:680
+#: i2p2www/pages/site/docs/how/tech-intro.html:745
+msgid "website"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:682
+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:703
+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:717
+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:727
+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 <a href=\"#future.restricted\">2.0</a>."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:733
+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:747
+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:766
+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:777
+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:793
+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 <a href=\"#app.streaming\">streaming"
+" library</a> \n"
+"as an implementation of an anonymous and secure TCP layer on top of it. "
+"Beyond \n"
+"that, <a href=\"#app.i2ptunnel\">I2PTunnel</a> 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:804
+msgid "Streaming library"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:805
+msgid ""
+"The I2P streaming library can be viewed as a generic streaming interface "
+"(mirroring TCP sockets),\n"
+"and the implementation supports a <a "
+"href=\"http://en.wikipedia.org/wiki/Sliding_Window_Protocol\">sliding "
+"window protocol</a>\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:815
+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:828
+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:835
+msgid "Naming library and addressbook"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:836
+#, python-format
+msgid ""
+"For more information see the <a href=\"%(naming)s\">Naming and "
+"Addressbook</a> page."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:840
+#: i2p2www/pages/site/docs/how/tech-intro.html:914
+#: i2p2www/pages/site/docs/how/tech-intro.html:961
+#: i2p2www/pages/site/docs/how/tech-intro.html:993
+#: i2p2www/pages/site/docs/how/tech-intro.html:1001
+#: i2p2www/pages/site/docs/how/tech-intro.html:1009
+#: i2p2www/pages/site/docs/how/tech-intro.html:1019
+#: i2p2www/pages/site/docs/how/tech-intro.html:1027
+#: i2p2www/pages/site/docs/how/tech-intro.html:1049
+#, python-format
+msgid "Developed by: %(dev)s"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:842
+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:862
+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:876
+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:886
+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:895
+msgid ""
+"The old Syndie bundled with I2P has been replaced by the new Syndie which"
+"\n"
+"is distributed separately. For more information see the <a "
+"href=\"http://syndie.i2p2.de/\">Syndie</a>\n"
+"pages."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:901
+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:916
+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:930
+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:946
+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 <a "
+"href=\"#app.i2pmail\">I2Pmail's</a> \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:963
+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 <a href=\"#app.streaming\">streaming lib</a> connection to query them "
+"for \n"
+"blocks."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:972
+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:980
+msgid ""
+"I2PSnark developed: jrandom, et al, ported from <a\n"
+"href=\"http://www.klomp.org/mark/\">mjw</a>'s <a\n"
+"href=\"http://www.klomp.org/snark/\">Snark</a> client"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:986
+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:995
+#, python-format
+msgid ""
+"Robert is a Bittorrent client written in Python.\n"
+"It is hosted on <a "
+"href=\"http://%(bob)s/Robert.html\">http://%(bob)s/Robert.html</a> <!-- "
+"TODO: expand -->"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:1003
+#, python-format
+msgid ""
+"PyBit is a Bittorrent client written in Python.\n"
+"It is hosted on <a href=\"%(pybit)s\">%(pybit)s</a> <!-- TODO: expand -->"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:1011
+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:1021
+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:1029
+#, 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"
+"<a href=\"http://%(postman)s/\">%(postman)s</a>."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:1051
+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. <br>\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:1061
+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:93
+msgid "Priority"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:45
+msgid "Index of Attacks"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:47
+#: i2p2www/pages/site/docs/how/threat-model.html:206
+msgid "Brute force attacks"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:48
+#: i2p2www/pages/site/docs/how/threat-model.html:250
+msgid "Timing attacks"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:49
+#: i2p2www/pages/site/docs/how/threat-model.html:287
+msgid "Intersection attacks"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:50
+#: i2p2www/pages/site/docs/how/threat-model.html:367
+msgid "Denial of service attacks"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:51
+#: i2p2www/pages/site/docs/how/threat-model.html:466
+msgid "Tagging attacks"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:52
+#: i2p2www/pages/site/docs/how/threat-model.html:484
+msgid "Partitioning attacks"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:53
+#: i2p2www/pages/site/docs/how/threat-model.html:524
+msgid "Predecessor attacks"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:54
+#: i2p2www/pages/site/docs/how/threat-model.html:569
+msgid "Harvesting attacks"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:55
+#: i2p2www/pages/site/docs/how/threat-model.html:616
+msgid "Identification Through Traffic Analysis"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:56
+#: i2p2www/pages/site/docs/how/threat-model.html:676
+msgid "Sybil attacks"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:57
+#: i2p2www/pages/site/docs/how/threat-model.html:725
+msgid "Buddy Exhaustion attacks"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:58
+#: i2p2www/pages/site/docs/how/threat-model.html:750
+msgid "Cryptographic attacks"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:59
+msgid "Floodfill attacks"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:60
+#: i2p2www/pages/site/docs/how/threat-model.html:811
+msgid "Other Network Database attacks"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:61
+msgid "Attacks on centralized resources"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:62
+#: i2p2www/pages/site/docs/how/threat-model.html:877
+msgid "Development attacks"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:63
+msgid "Implementation attacks"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:64
+#: i2p2www/pages/site/docs/how/threat-model.html:961
+msgid "Other Defenses"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:69
+msgid "What do we mean by \"anonymous\"?"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:71
+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:82
+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:89
+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:95
+msgid "Network Topology Summary"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:96
+#, python-format
+msgid ""
+"I2P builds off the ideas of many <a href=\"%(comparisons)s\">other</a> \n"
+"<a href=\"%(links)s\">systems</a>, but a few key points should be kept in"
+" mind when \n"
+"reviewing related literature:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:102
+msgid ""
+"<b>I2P is a free route mixnet</b> - 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:108
+msgid ""
+"<b>I2P has no official entry and exit points</b> - 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:113
+msgid ""
+"<b>I2P is fully distributed</b> - 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:123
+#, python-format
+msgid ""
+"We have documented plans to implement <a "
+"href=\"%(todo)s#stop\">nontrivial delays</a>\n"
+"and <a href=\"%(todo)s#batching\">batching strategies</a> \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:134
+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:141
+msgid "The Threat Model"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:142
+msgid ""
+"I2P design started in 2003, not long after the advent of\n"
+"<a href=\"http://www.onion-router.net\">[Onion Routing]</a>,\n"
+"<a href=\"http://freenetproject.org/\">[Freenet]</a>, and\n"
+"<a href=\"https://www.torproject.org/\">[Tor]</a>.\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:152
+msgid ""
+"Taking from the attacks and analysis put forth in the \n"
+"<a href=\"http://freehaven.net/anonbib/topic.html\">anonymity "
+"literature</a> (largely \n"
+"<a href=\"http://citeseer.ist.psu.edu/454354.html\">Traffic Analysis: "
+"Protocols, Attacks, Design \n"
+"Issues and Open Problems</a>), 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:161
+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:167
+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:177
+#, python-format
+msgid ""
+"The\n"
+"<a href=\"%(comparisons)s\">network comparisons</a> and\n"
+"<a href=\"%(garlicrouting)s\">\"garlic\" terminology</a> pages may also "
+"be helpful\n"
+"to review."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:210
+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:222
+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"
+"<a "
+"href=\"http://citeseer.ist.psu.edu/freedman02tarzan.html\">Tarzan</a>'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:239
+#, 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"
+"<a href=\"%(peerselection)s\">peer selection page</a>."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:254
+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:264
+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:274
+#, 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 <a href=\"%(todo)s#stop\">nontrivial "
+"delays</a> or \n"
+"<a href=\"%(todo)s#batching\">batching strategies</a>), include protocol "
+"scrubbing, or\n"
+"other advanced tunnel routing <a "
+"href=\"%(todo)s#batching\">techniques</a>,\n"
+"but these are unimplemented in I2P."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:283
+#, python-format
+msgid ""
+"References: <a href=\"%(pdf)s\">Low-Resource Routing Attacks Against "
+"Anonymous Systems</a>"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:291
+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:301
+#, 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 <a href=\"%(url)s\">similar disclaimer</a>."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:309
+msgid "Partial defenses implemented in I2P:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:313
+#, python-format
+msgid "<a href=\"%(tunnelimpl)s#ordering\">strict ordering</a> of peers"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:316
+#, python-format
+msgid ""
+"<a href=\"%(peerselection)s\">peer profiling and selection</a> from a "
+"small group that changes slowly"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:319
+msgid "Limits on the number of tunnels routed through a single peer"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:322
+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:325
+msgid ""
+"For eepsites or other hosted services, we support\n"
+"simultaneous hosting on multiple routers, or\n"
+"<a href=\"#intersection\">multihoming</a>"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:332
+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:337
+msgid "We do not use low-bandwidth \"guard nodes\""
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:340
+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:343
+msgid "Tunnels are not long-lived; new tunnels are built every 10 minutes."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:346
+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:353
+#, python-format
+msgid ""
+"In the future, it could\n"
+"for peers who can afford significant delays (per <a "
+"href=\"%(todo)s#stop\">nontrivial\n"
+"delays</a> and <a href=\"%(todo)s#batching\">batching strategies</a>).  "
+"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.</p>"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:362
+#, python-format
+msgid "Reference: <a href=\"%(oce)s\">One Cell Enough</a>"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:369
+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:375
+msgid ""
+"<b>Greedy user attack:</b> 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:381
+#, 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"
+"<a href=\"%(comparisons)s\">other networks</a>,\n"
+"over 95&#37; of I2P users relay traffic for others."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:387
+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:392
+msgid ""
+"Maintain a strong community with blogs, forums, IRC, and other means of "
+"communication."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:399
+#, python-format
+msgid ""
+"<b>Starvation attack:</b> 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 <a "
+"href=\"%(peerselection)s\">profiles</a> 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:419
+#, python-format
+msgid ""
+"<b>Flooding attack:</b> 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 <a "
+"href=\"%(todo)s#batching\">advanced tunnel\n"
+"operation</a> is implemented)."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:438
+msgid ""
+"<b>CPU load attack:</b> 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:451
+#, python-format
+msgid ""
+"<b>Floodfill DOS attack:</b> 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"
+"<a href=\"%(peerselection)s\">peer profiling</a> are implemented,\n"
+"however there is much more to do.\n"
+"For more information see the\n"
+"<a href=\"%(netdb)s#threat\">network database page</a>."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:470
+#, 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 <a href=\"%(todo)s#tunnelId\">unique hop ids</a> 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:488
+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:504
+#, 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 <a href=\"#harvesting\">harvesting</a>"
+" 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 <a href=\"%(todo)s#stop\">nontrivial "
+"delays</a> and \n"
+"<a href=\"%(todo)s#batching\">batching strategies</a>, 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:520
+#, python-format
+msgid ""
+"Also discussed on the <a href=\"%(netdb)s#threat\">network database "
+"page</a> (bootstrap attack)."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:528
+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:538
+#, 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 <a href=\"%(peerselection)s\">peer selection</a> algorithm which "
+"breaks them\n"
+"into tiers.  Second, with <a href=\"%(tunnelimpl)s#ordering\">strict "
+"ordering</a> 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 <a href=\"%(tunnelimpl)s#length\">permuted "
+"tunnel length</a>\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"
+"<a href=\"%(todo)s#fullRestrictedRoutes\">restricted routes</a> "
+"(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:555
+#, python-format
+msgid ""
+"The current <a href=\"%(tunnelcreation)s\">tunnel build method</a>\n"
+"was specifically designed to combat the predecessor attack.\n"
+"See also <a href=\"#intersection\">the intersection attack</a>."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:561
+#, python-format
+msgid ""
+"References: <a href=\"%(pdf2008)s\">%(pdf2008)s</a>\n"
+"which is an update to the 2004 predecessor attack paper\n"
+"<a href=\"%(pdf2004)s\">%(pdf2004)s</a>."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:573
+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:580
+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:587
+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:590
+msgid "Floodfill routers implement query limits as DOS protection"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:593
+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:599
+#, python-format
+msgid ""
+"In future implementations,\n"
+"<a href=\"%(todo)s#nat\">basic</a> and \n"
+"<a href=\"%(todo)s#fullRestrictedRoutes\">comprehensive</a> 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:608
+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:620
+#, 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 <a href=\"#harvesting\">above</a>, 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"
+"<a href=\"%(transport)s\">transport layer and protocols</a>\n"
+"make it somewhat difficult to identify I2P traffic:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:630
+msgid "Random port selection"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:633
+msgid "Point-to-Point Encryption of all traffic"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:636
+msgid ""
+"DH key exchange with no protocol bytes or other unencrypted constant "
+"fields"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:639
+#, python-format
+msgid ""
+"Simultaneous use of both\n"
+"<a href=\"%(ntcp)s\">TCP</a> and\n"
+"<a href=\"%(ssu)s\">UDP</a> 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:647
+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:651
+msgid ""
+"Padding at the transport layer to random lengths, especially during the "
+"connection handshake"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:654
+msgid ""
+"Study of packet size distribution signatures, and additional padding as "
+"necessary"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:657
+msgid ""
+"Development of additional transport methods that mimic SSL or other "
+"common protocols"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:660
+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:663
+msgid ""
+"Review of methods implemented by various state-level firewalls to block "
+"Tor"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:666
+msgid "Working directly with DPI and obfuscation experts"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:671
+#, python-format
+msgid ""
+"Reference: <a href=\"%(pdf)s\">Breaking and Improving Protocol "
+"Obfuscation</a>"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:680
+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&#37; 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' - <a "
+"href=\"http://www.pdos.lcs.mit.edu/tarzan/\">Tarzan</a>\n"
+"(among others) uses the fact that IP addresses are limited, while \n"
+"IIP used \n"
+"<a href=\"http://www.hashcash.org/\">HashCash</a> 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:698
+msgid "Requiring HashCash Certificates in various places has two major problems:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:702
+msgid "Maintaining backward compatibility"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:705
+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:712
+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:719
+#, python-format
+msgid ""
+"See the <a href=\"%(netdb)s#threat\">network database page</a>\n"
+"for more Sybil discussion."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:729
+#, python-format
+msgid ""
+"(Reference: <a href=\"%(pdf)s\">In Search of an Anonymous and Secure "
+"Lookup</a> Section 5.2)"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:733
+#, 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 <a href=\"#sybil\">Sybil attack</a>.\n"
+"This is somewhat mitigated by our\n"
+"<a href=\"%(peerselection)s\">peer profiling</a> methods used to monitor "
+"the performance\n"
+"of peers.\n"
+"However, this is a powerful attack as the number of routers approaches\n"
+"<i>f</i> = 0.2, or 20&#37; 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:754
+#, 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"
+"<a href=\"%(cryptography)s\">on the low-level cryptography page</a>. \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 <a href=\"https://torproject.org/\">other anonymity "
+"networks</a>.\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:773
+#, 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"
+"<a href=\"%(cryptography)s\">major undertaking</a>, just as it will be "
+"for \n"
+"<a href=\"https://torproject.org/\">others</a>.\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:782
+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:792
+msgid "Floodfill Anonymity attacks"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:796
+#, python-format
+msgid ""
+"In addition to the floodfill DOS attacks described\n"
+"<a href=\"#ffdos\">above</a>, 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 <a href=\"%(netdb)s#threat\">network database page</a>.\n"
+"The specific mechanisms by which routers communicate with floodfills have"
+" been\n"
+"<a href=\"%(netdb)s#delivery\">carefully designed</a>.\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:812
+#, 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"
+"<a href=\"%(netdb)s#threat\">network database page</a>."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:822
+msgid "Central Resource Attacks"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:826
+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:836
+#, python-format
+msgid ""
+"The <a href=\"%(site)s\">website</a> is mirrored and uses DNS round-robin"
+" for external public access."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:839
+#, python-format
+msgid ""
+"Routers now support <a href=\"%(faq)s#reseed\">multiple external reseed "
+"locations</a>,\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:844
+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:848
+msgid "Routers now support multiple default trusted update signers."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:851
+msgid ""
+"Routers now better handle <a href=\"#ffdos\">multiple unreliable "
+"floodfill peers</a>.\n"
+"Malicious floodfills <a href=\"#ffdos\">needs</a> <a "
+"href=\"#floodfill\">more</a> study."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:855
+#, python-format
+msgid ""
+"The code is now stored in a <a href=\"%(monotone)s\">distributed source "
+"control system</a>."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:858
+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:862
+#, python-format
+msgid ""
+"<a href=\"%(naming)s\">Naming system services</a>, 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"
+"<a href=\"%(naming)s\">the naming page</a> for details."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:869
+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:881
+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:890
+msgid "However, two techniques help defend against these attacks:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:894
+#, 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 <a href=\"%(monotone)s\">distributed source control "
+"system</a>\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:902
+#, 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 <a href=\"%(monotone)s\">distributed source control system</a>,\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:913
+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:918
+msgid "Implementation attacks (bugs)"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:922
+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"
+"<a href=\"http://www.haystacknetwork.com/\">security through "
+"obscurity</a>."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:933
+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:943
+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:949
+#, 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"
+"<a href=\"https://torproject.org/\">other anonymity networks</a>\n"
+"may have received. We continue to recruit people to\n"
+"<a href=\"%(volunteer)s\">get involved</a> and help."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:962
+msgid "Blocklists"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:963
+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:969
+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:977
+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:986
+msgid ""
+"If a blocklist is hosted at a central location with automatic updates\n"
+"the network is vulnerable to a\n"
+"<a href=\"#central\">central resource attack</a>.\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:994
+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
+msgid "Tunnel Routing"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tunnel-routing.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 <a href=\"%(intro)s\">introduction</a>, 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 ""
+"<b>Tunnel gateway</b> - the first router in a tunnel.  For inbound "
+"tunnels,\n"
+"this is the one mentioned in the LeaseSet published in the\n"
+"<a href=\"%(netdb)s\">network database</a>.  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 ""
+"<b>Tunnel endpoint</b> - the last router in a tunnel.  (e.g. both C and F"
+" above)"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tunnel-routing.html:45
+msgid ""
+"<b>Tunnel participant</b> - 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 ""
+"<b>n-Hop tunnel</b> - a tunnel with a specific number of inter-router "
+"jumps, e.g.:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tunnel-routing.html:51
+msgid "<b>0-hop tunnel</b> - a tunnel where the gateway is also the endpoint"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tunnel-routing.html:52
+msgid ""
+"<b>1-hop tunnel</b> - a tunnel where the gateway talks directly to the "
+"endpoint"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tunnel-routing.html:53
+msgid ""
+"<b>2-(or more)-hop tunnel</b> - 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 ""
+"<b>Tunnel ID</b> - A <a href=\"%(commonstructures)s#type_TunnelId\">4 "
+"byte integer</a>\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"
+"<a href=\"%(tunnelcreation)s\">Tunnel Build Message</a>\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 ""
+"<b>tunnel encryption key</b> - an <a "
+"href=\"%(commonstructures)s#type_SessionKey\">AES private key</a> 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 ""
+"<b>tunnel IV key</b> - an <a "
+"href=\"%(commonstructures)s#type_SessionKey\">AES private key</a> 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 ""
+"<b>reply key</b> - an <a "
+"href=\"%(commonstructures)s#type_SessionKey\">AES public key</a> 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 ""
+"<b>reply IV</b> - the IV for encrypting the reply to the tunnel build "
+"request"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tunnel-routing.html:90
+msgid "<b>tunnel id</b> - 4 byte integer (inbound gateways only)"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tunnel-routing.html:91
+msgid ""
+"<b>next hop</b> - 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 "<b>next tunnel id</b> - 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 "<b>tunnel id</b> - 4 byte integer"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tunnel-routing.html:111
+msgid "<b>next hop</b> - 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 ""
+"<b>tunnel encryption key</b> - an <a "
+"href=\"%(commonstructures)s#type_SessionKey\">AES private key</a> for "
+"encrypting\n"
+"messages and instructions to the the endpoint (itself)"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tunnel-routing.html:121
+#, python-format
+msgid ""
+"<b>tunnel IV key</b> - an <a "
+"href=\"%(commonstructures)s#type_SessionKey\">AES private key</a> for "
+"double-encrypting\n"
+"the IV to the endpoint (itself)"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tunnel-routing.html:125
+#, python-format
+msgid ""
+"<b>reply key</b> - an <a "
+"href=\"%(commonstructures)s#type_SessionKey\">AES public key</a> for "
+"encrypting\n"
+"the reply to the tunnel build request (outbound endpoints only)"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tunnel-routing.html:129
+msgid ""
+"<b>reply IV</b> - 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 "<b>tunnel id</b> - 4 byte integer (outbound endpoints only)"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tunnel-routing.html:131
+msgid ""
+"<b>reply router</b> - 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 ""
+"<b>reply tunnel id</b> - 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"
+"<a href=\"%(tunnelcreation)s\">tunnel creation specification</a>."
+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"
+"<a href=\"%(tunnelimpl)s#tunnel.pooling\">tunnel specification</a>.\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"
+"<a href=\"%(i2cp)s#options\">I2CP options</a>.\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 <a href=\"%(threatmodel)s\">threat model</a>)."
+" 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 <a href=\"%(url)s\">some attacks</a>,\n"
+"3 or more hops are recommended for the highest level of protection.\n"
+"<a href=\"%(url)s\">Recent studies</a>\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"
+"<a href=\"%(i2cp)s#options\">I2CP options</a>.\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"
+"<a href=\"%(peerselection)s#capacity\">capacity rating in the peer "
+"profile</a>."
+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 <a href=\"%(garlicrouting)s\">garlic "
+"routing</a>\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"
+"<a href=\"%(tunnelcreation)s\">tunnel creation specification</a>."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tunnel-routing.html:245
+#, python-format
+msgid ""
+"Multi-layer encryption is handled by <a href=\"%(garlicrouting)s\">garlic"
+" encryption</a>\n"
+"of tunnel messages.\n"
+"Details are in the\n"
+"<a href=\"%(tunnelimpl)s\">tunnel specification</a>.\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 "Tək istiqamətli tunellər"
+
+#: 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 "February 2016"
+msgstr "Fevral 2016"
+
+#: 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.\n"
+"With I2CP, a client application tells the\n"
+"router who they are (their \"destination\"), what anonymity, reliability,"
+" and \n"
+"latency tradeoffs to make, and where to send messages.  In turn the "
+"router uses\n"
+"I2CP to tell the client when any messages have arrived, and to request "
+"authorization\n"
+"for some tunnels to be used."
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2cp.html:18
+#, python-format
+msgid ""
+"The protocol itself is implemented in Java, to provide the\n"
+"<a href=\"%(url)s\">Client SDK</a>.\n"
+"This SDK is exposed in the i2p.jar package, which implements the client-"
+"side of I2CP.\n"
+"Clients should never need to access the router.jar package, which "
+"contains the\n"
+"router itself and the router-side of I2CP.\n"
+"There is also a <a href=\"%(libi2cp)s\">C library implementation</a>.\n"
+"A non-Java client would also have to implement the\n"
+"<a href=\"%(streaming)s\">streaming library</a> for TCP-style connections."
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2cp.html:31
+#, python-format
+msgid ""
+"Applications can take advantage of the base I2CP plus the \n"
+"<a href=\"%(streaming)s\">streaming</a> and <a "
+"href=\"%(datagrams)s\">datagram</a> libraries\n"
+"by using the <a href=\"%(sam)s\">Simple Anonymous Messaging</a> or <a "
+"href=\"%(bob)s\">BOB</a> 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:43
+#, 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 <a href=\"%(elgamalaes)s\">ElGamal/AES end-to-end "
+"encryption</a>\n"
+"which is implemented in the router.\n"
+"The only cryptography that client libraries must still implement is\n"
+"<a href=\"%(cryptography)s#DSA\">DSA public/private key signing</a>\n"
+"for <a href=\"%(i2cp)s#msg_CreateLeaseSet\">LeaseSets</a> and\n"
+"<a href=\"%(i2cp)s#struct_SessionConfig\">Session Configurations</a>, and"
+" management of those keys."
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2cp.html:56
+msgid ""
+"In a standard I2P installation, port 7654 is used by external java "
+"clients to communicate\n"
+"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 "
+"<tt>i2cp.tcp.bindAllInterfaces=true</tt> 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:65
+#, python-format
+msgid ""
+"The router also supports external connections over SSL.\n"
+"While SSL is not the default, it is strongly recommended for any traffic "
+"that may\n"
+"be exposed to the open Internet. The authorization user/password (if "
+"any), the\n"
+"<a href=\"%(commonstructures)s#type_PrivateKey\">Private Key</a> and\n"
+"<a href=\"%(commonstructures)s#type_SigningPrivateKey\">Signing Private "
+"Key</a> for the\n"
+"<a href=\"%(commonstructures)s#struct_Destination\">Destination</a>\n"
+"are all transmitted in-the-clear unless SSL is enabled."
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2cp.html:75
+msgid "I2CP Protocol Specification"
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2cp.html:76
+#, python-format
+msgid "Now on the <a href=\"%(i2cp)s\">I2CP Specification page</a>."
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2cp.html:81
+msgid "I2CP Initialization"
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2cp.html:82
+#, python-format
+msgid ""
+"When a client connects to the router, it first sends a single protocol "
+"version byte (0x2A).\n"
+"Then it sends a <a href=\"%(i2cp)s#msg_GetDate\">GetDate Message</a> and "
+"waits for the <a href=\"%(i2cp)s#msg_SetDate\">SetDate Message</a> "
+"response.\n"
+"Next, it sends a <a href=\"%(i2cp)s#msg_CreateSession\">CreateSession "
+"Message</a> containing the session configuration.\n"
+"It next awaits a <a href=\"%(i2cp)s#msg_RequestLeaseSet\">RequestLeaseSet"
+" Message</a> from the router, indicating that inbound tunnels\n"
+"have been built, and responds with a CreateLeaseSetMessage containing the"
+" signed LeaseSet.\n"
+"The client may now initiate or receive connections from other I2P "
+"destinations."
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2cp.html:91
+msgid "I2CP Options"
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2cp.html:92
+#: i2p2www/pages/site/docs/protocol/i2cp.html:99
+msgid "Router-side Options"
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2cp.html:93
+#, python-format
+msgid ""
+"The following options are traditionally passed to the router via\n"
+"a <a href=\"%(i2cp)s#struct_SessionConfig\">SessionConfig</a> contained "
+"in a <a href=\"%(i2cp)s#msg_CreateSession\">CreateSession Message</a> or "
+"a <a href=\"%(i2cp)s#msg_ReconfigureSession\">ReconfigureSession "
+"Message</a>."
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2cp.html:104
+#: i2p2www/pages/site/docs/protocol/i2cp.html:479
+msgid "As Of Release"
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2cp.html:105
+#: i2p2www/pages/site/docs/protocol/i2cp.html:480
+msgid "Recommended Arguments"
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2cp.html:106
+#: i2p2www/pages/site/docs/protocol/i2cp.html:481
+msgid "Allowable Range"
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2cp.html:117
+msgid ""
+"The timeout (ms) for all sent messages. Unused.\n"
+"See the protocol specification for per-message settings."
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2cp.html:129
+msgid ""
+"Minimum number of ElGamal/AES Session Tags before we send more.\n"
+"Recommended: approximately tagsToSend * 2/3"
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2cp.html:141
+msgid ""
+"Number of ElGamal/AES Session Tags to send at a time.\n"
+"For clients with relatively low bandwidth per-client-pair (IRC, some UDP "
+"apps), this may be set lower."
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2cp.html:153
+msgid ""
+"Comma-separated list of Base 64 Hashes of peers to build tunnels through;"
+" for debugging only"
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2cp.html:162
+msgid "Should generally be set to true for clients and false for servers"
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2cp.html:171
+#: i2p2www/pages/site/docs/protocol/i2cp.html:519
+msgid ""
+"If true, the router just sends the MessagePayload instead\n"
+"of sending a MessageStatus and awaiting a ReceiveMessageBegin."
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2cp.html:183
+msgid ""
+"Guaranteed is disabled;\n"
+"None implemented in 0.8.1; the streaming lib default is None as of 0.8.1,"
+" the client side default is None as of 0.9.4"
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2cp.html:195
+msgid ""
+"For authorization, if required by the router.\n"
+"If the client is running in the same JVM as a router, this option is not "
+"required.\n"
+"Warning - username and password are sent in the clear to the router, "
+"unless using SSL (i2cp.SSL=true).\n"
+"Authorization is only recommended when using SSL."
+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:232
+#: i2p2www/pages/site/docs/protocol/i2cp.html:241
+#: i2p2www/pages/site/docs/protocol/i2cp.html:250
+#: i2p2www/pages/site/docs/protocol/i2cp.html:262
+#: i2p2www/pages/site/docs/protocol/i2cp.html:274
+#: i2p2www/pages/site/docs/protocol/i2cp.html:283
+#: i2p2www/pages/site/docs/protocol/i2cp.html:292
+#: i2p2www/pages/site/docs/protocol/i2cp.html:307
+#: i2p2www/pages/site/docs/protocol/i2cp.html:343
+#: i2p2www/pages/site/docs/protocol/i2cp.html:355
+#: i2p2www/pages/site/docs/protocol/i2cp.html:368
+#, python-format
+msgid "number from %(from)s to %(to)s"
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2cp.html:233
+#: i2p2www/pages/site/docs/protocol/i2cp.html:242
+#: i2p2www/pages/site/docs/protocol/i2cp.html:369
+msgid "No limit"
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2cp.html:235
+msgid "Number of redundant fail-over for tunnels in"
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2cp.html:244
+msgid "Number of redundant fail-over for tunnels out"
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2cp.html:251
+#: i2p2www/pages/site/docs/protocol/i2cp.html:263
+#: i2p2www/pages/site/docs/protocol/i2cp.html:275
+#: i2p2www/pages/site/docs/protocol/i2cp.html:284
+#: i2p2www/pages/site/docs/protocol/i2cp.html:293
+#: i2p2www/pages/site/docs/protocol/i2cp.html:308
+#: i2p2www/pages/site/docs/protocol/i2cp.html:344
+#: i2p2www/pages/site/docs/protocol/i2cp.html:356
+#: i2p2www/pages/site/docs/protocol/i2cp.html:608
+#, python-format
+msgid "%(from)s to %(to)s"
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2cp.html:253
+#: i2p2www/pages/site/docs/protocol/i2cp.html:265
+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:277
+msgid "Length of tunnels in"
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2cp.html:286
+msgid "Length of tunnels out"
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2cp.html:295
+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:310
+msgid ""
+"Random amount to add or subtract to the length of tunnels out.\n"
+"A positive number x means add a random amount from 0 to x inclusive.\n"
+"A negative number -x means add a random amount from -x to x inclusive.\n"
+"The router will limit the total length of the tunnel to 0 to 7 inclusive."
+"\n"
+"The default variance was 1 prior to release 0.7.6."
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2cp.html:325
+msgid ""
+"Name of tunnel - generally used in routerconsole, which will\n"
+"use the first few characters of the Base64 hash of the destination by "
+"default."
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2cp.html:337
+msgid "Name of tunnel - generally ignored unless inbound.nickname is unset."
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2cp.html:346
+msgid ""
+"Priority adjustment for outbound messages.\n"
+"Higher is higher priority."
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2cp.html:358
+msgid ""
+"Number of tunnels in.\n"
+"Limit was increased from 6 to 16 in release 0.9; however, numbers higher "
+"than 6 are\n"
+"incompatible with older releases."
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2cp.html:371
+msgid "Number of tunnels out"
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2cp.html:380
+msgid "Used for consistent peer ordering across restarts."
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2cp.html:399
+msgid ""
+"Any other options prefixed with \"inbound.\" are stored\n"
+"in the \"unknown options\" properties of the inbound tunnel pool's "
+"settings."
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2cp.html:411
+msgid ""
+"Any other options prefixed with \"outbound.\" are stored\n"
+"in the \"unknown options\" properties of the outbound tunnel pool's "
+"settings."
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2cp.html:423
+msgid ""
+"Set to false to disable ever bundling a reply LeaseSet.\n"
+"For clients that do not publish their LeaseSet, this option must be true\n"
+"for any reply to be possible. \"true\" is also recommended for multihomed"
+" servers\n"
+"with long connection times."
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2cp.html:430
+msgid ""
+"Setting to \"false\" may save significant outbound bandwidth, especially "
+"if\n"
+"the client is configured with a large number of inbound tunnels (Leases)."
+"\n"
+"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:438
+msgid "Unidirectional communication, no reply required"
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2cp.html:439
+msgid "LeaseSet is published and higher reply latency is acceptable"
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2cp.html:440
+msgid ""
+"LeaseSet is published, client is a \"server\", all connections are "
+"inbound\n"
+"so the connecting far-end destination obviously has the leaseset already."
+"\n"
+"Connections are either short, or it is acceptable for latency on a long-"
+"lived\n"
+"connection to temporarily increase while the other end re-fetches the "
+"LeaseSet\n"
+"after expiration.\n"
+"HTTP servers may fit these requirements."
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2cp.html:453
+msgid ""
+"Note: Large quantity, length, or variance settings may cause significant "
+"performance or reliability problems."
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2cp.html:457
+#, python-format
+msgid ""
+"Note: As of release 0.7.7, option names and values must use UTF-8 "
+"encoding.\n"
+"This is primarily useful for nicknames.\n"
+"Prior to that release, options with multi-byte characters were corrupted."
+"\n"
+"Since options are encoded in a <a "
+"href=\"%(commonstructures)s#type_Mapping\">Mapping</a>,\n"
+"all option names and values are limited to 255 bytes (not characters) "
+"maximum."
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2cp.html:465
+#: i2p2www/pages/site/docs/protocol/i2cp.html:474
+msgid "Client-side Options"
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2cp.html:466
+msgid ""
+"The following options are interpreted on the client side,\n"
+"and will be interpreted if passed to the I2PSession via the "
+"I2PClient.createSession() call.\n"
+"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:490
+#: i2p2www/pages/site/docs/protocol/i2cp.html:590
+#, python-format
+msgid "%(num)s minimum"
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2cp.html:492
+msgid "(ms) Idle time required (default 30 minutes)"
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2cp.html:501
+msgid "Close I2P session when idle"
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2cp.html:510
+msgid "Encrypt the lease"
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2cp.html:531
+msgid "Gzip outbound data"
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2cp.html:540
+msgid "For encrypted leasesets. Base 64 SessionKey (44 characters)"
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2cp.html:549
+msgid ""
+"Base 64 private key for encryption.\n"
+"Optionally preceded by the key type and ':'.\n"
+"Only \"ELGAMAL_2048:\" is supported, which is the default.\n"
+"I2CP will generate the public key from the private key.\n"
+"Use for persistent leaseset keys across restarts."
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2cp.html:564
+msgid ""
+"Base 64 private key for signatures.\n"
+"Optionally preceded by the key type and ':'.\n"
+"DSA_SHA1 is the default.\n"
+"Key type must match the signature type in the destination.\n"
+"I2CP will generate the public key from the private key.\n"
+"Use for persistent leaseset keys across restarts."
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2cp.html:580
+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:592
+msgid "(ms) Idle time required (default 20 minutes, minimum 5 minutes)"
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2cp.html:601
+msgid "Reduce tunnel quantity when idle"
+msgstr "Tunellərin miqdarını yubanma zamanı azaltmaq"
+
+#: i2p2www/pages/site/docs/protocol/i2cp.html:610
+msgid "Tunnel quantity when reduced (applies to both inbound and outbound)"
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2cp.html:619
+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:631
+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:643
+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:650
+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:656
+msgid "I2CP Payload Data Format and Multiplexing"
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2cp.html:657
+#, python-format
+msgid ""
+"The end-to-end messages handled by I2CP (i.e. the data sent by the client"
+" in a\n"
+"<a href=\"%(i2cp)s#msg_SendMessage\">SendMessageMessage</a>\n"
+"and received by the client in a\n"
+"<a href=\"%(i2cp)s#msg_MessagePayload\">MessagePayloadMessage</a>)\n"
+"are gzipped with a standard 10-byte gzip\n"
+"header beginning with 0x1F 0x8B 0x08 as\n"
+"specified by <a href=\"http://www.ietf.org/rfc/rfc1952.txt\">RFC "
+"1952</a>.\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:671
+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:677
+#: i2p2www/pages/site/docs/protocol/i2np.html:32
+msgid "Bytes"
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2cp.html:678
+msgid "Content"
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2cp.html:683
+msgid "Gzip header"
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2cp.html:688
+msgid "Gzip flags"
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2cp.html:693
+msgid "I2P Source port (Gzip mtime)"
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2cp.html:698
+msgid "I2P Destination port (Gzip mtime)"
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2cp.html:703
+msgid "Gzip xflags"
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2cp.html:708
+msgid "I2P Protocol (6 = Streaming, 17 = Datagram, 18 = Raw Datagrams) (Gzip OS)"
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2cp.html:717
+msgid ""
+"Data integrity is verified with the standard gzip CRC-32 as\n"
+"specified by <a href=\"http://www.ietf.org/rfc/rfc1952.txt\">RFC 1952</a>."
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2cp.html:725
+msgid ""
+"The current authorization mechanism could be modified to use hashed "
+"passwords."
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2cp.html:729
+msgid ""
+"The Signing Private Keys is included in the Create Lease Set message,\n"
+"it is not required. Revocation is unimplemented.\n"
+"It should be replaced with random data or removed."
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2cp.html:735
+#, python-format
+msgid ""
+"Some improvements may be able to use messages previously defined but not "
+"implemented.\n"
+"For reference, here is the\n"
+"<a href=\"%(pdf1)s\">I2CP Protocol Specification Version 0.9</a>\n"
+"(PDF) dated August 28, 2003.\n"
+"That document also references the\n"
+"<a href=\"%(pdf2)s\">Common Data Structures Specification Version 0.9</a>."
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2np.html:2
+msgid "I2P Network Protocol"
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2np.html:3
+msgid "June 2013"
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2np.html:6
+msgid ""
+"The I2P Network Protocol (I2NP),\n"
+"which is sandwiched between I2CP and the various I2P transport protocols,"
+" manages the\n"
+"routing and mixing of messages between routers, as well as the selection "
+"of what\n"
+"transports to use when communicating with a peer for which there are "
+"multiple\n"
+"common transports supported."
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2np.html:14
+msgid "I2NP Definition"
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2np.html:15
+msgid ""
+"I2NP (I2P Network Protocol) messages can be used for one-hop, router-to-"
+"router, point-to-point messages.\n"
+"By encrypting and wrapping messages in other messages, they can be sent "
+"in a secure way\n"
+"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:22
+#, python-format
+msgid ""
+"The priorities listed below may not be current and are subject to change."
+"\n"
+"See the <a href=\"%(outnetmessage)s\">OutNetMessage Javadocs</a>\n"
+"for the current priority settings.\n"
+"Priority queueing implementation may vary."
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2np.html:29
+msgid "Message Format"
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2np.html:32
+msgid "Field"
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2np.html:33
+msgid "Unique ID"
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2np.html:34
+msgid "Expiration"
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2np.html:35
+#: i2p2www/pages/site/docs/protocol/i2np.html:92
+msgid "Payload Length"
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2np.html:36
+msgid "Checksum"
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2np.html:37
+msgid "Payload"
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2np.html:40
+#, python-format
+msgid ""
+"While the maximum payload size is nominally 64KB, the size is further "
+"constrained by the\n"
+"method of fragmenting I2NP messages into multiple 1KB tunnel messages as "
+"described on\n"
+"<a href=\"%(tunnelimpl)s\">the tunnel implementation page</a>.\n"
+"The maximum number of fragments is 64, and the message may not be "
+"perfectly aligned,\n"
+"So the message must nominally fit in 63 fragments."
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2np.html:48
+msgid ""
+"The maximum size of an initial fragment is 956 bytes (assuming TUNNEL "
+"delivery mode);\n"
+"the maximum size of 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:54
+msgid ""
+"In addition, the transports may have additional restrictions.\n"
+"NTCP currently limits to 16KB - 6 = 16378 bytes but this will be "
+"increased in a future release.\n"
+"The SSU limit is approximately 32 KB."
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2np.html:60
+msgid ""
+"Note that these are not the limits for datagrams that the client sees, as"
+" the\n"
+"router may bundle a reply leaseset and/or session tags together with the "
+"client message\n"
+"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:68
+msgid "Message Types"
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2np.html:69
+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:80
+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:90
+msgid "Message"
+msgstr "İsmarıc"
+
+#: i2p2www/pages/site/docs/protocol/i2np.html:91
+msgid "Type"
+msgstr "Növ"
+
+#: i2p2www/pages/site/docs/protocol/i2np.html:94
+msgid "Comments"
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2np.html:102
+msgid "May vary"
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2np.html:108
+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:117
+msgid "Varies"
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2np.html:119
+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:133
+msgid "Priority may vary on a per-destination basis"
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2np.html:143
+msgid ""
+"Used for message replies, and for testing tunnels - generally wrapped in "
+"a GarlicMessage"
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2np.html:151
+msgid ""
+"Generally wrapped in a DataMessage -\n"
+"but when unwrapped, given a priority of 100 by the forwarding router"
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2np.html:178
+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:198
+msgid "Shorter TunnelBuildMessage as of 0.7.12"
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2np.html:206
+msgid "Shorter TunnelBuildReplyMessage as of 0.7.12"
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2np.html:209
+#, python-format
+msgid "Others listed in <a href=\"%(pdf)s\">2003 Spec</a>"
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2np.html:215
+msgid "Obsolete, Unused"
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2np.html:219
+msgid "Full Protocol Specification"
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2np.html:220
+#, python-format
+msgid ""
+"<a href=\"%(i2npspec)s\">On the I2NP Specification page</a>.\n"
+"See also the\n"
+"<a href=\"%(commonstructures)s\">Common Data Structure Specification "
+"page</a>."
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2np.html:227
+msgid ""
+"It isn't clear whether the current priority scheme is generally "
+"effective,\n"
+"and whether the priorities for various messages should be adjusted "
+"further.\n"
+"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 <a href=\"%(docs)s\">Index to Technical Documentation</a>."
+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 ""
+"<b>I2P Transport Layer:</b> 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 "<b>I2P Tunnel Layer:</b> provide full encrypted tunnel connections."
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/index.html:42
+#, python-format
+msgid ""
+"<a href=\"%(tunnelmessage)s\">Tunnel messages</a>: 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 ""
+"<a href=\"%(i2np)s\">I2NP messages</a>: 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 ""
+"<b>I2P Garlic Layer:</b> provide encrypted and anonymous end-to-end I2P "
+"message delivery."
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/index.html:55
+#, python-format
+msgid ""
+"<a href=\"%(i2np)s\">I2NP messages</a>: 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 ""
+"<b>I2P Client Layer:</b> 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 ""
+"<a href=\"%(i2cp)s\">I2CP</a>: 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 ""
+"<b>I2P End-to-end Transport Layer:</b> allow TCP- or UDP-like "
+"functionality on top of I2P."
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/index.html:76
+#, python-format
+msgid ""
+"<a href=\"%(streaming)s\">Streaming Library</a>: 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 ""
+"<a href=\"%(datagrams)s\">Datagram Library</a>: 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 ""
+"<b>I2P Application Interface Layer:</b> additional (optional) libraries "
+"allowing easier implementations on top of I2P."
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/index.html:93
+msgid "<b>I2P Application Proxy Layer:</b> proxy systems."
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/index.html:95
+#, python-format
+msgid "HTTP Client/Server, IRC Client, <a href=\"%(socks)s\">SOCKS</a>, Streamr"
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/index.html:99
+msgid ""
+"Finally, what could be considered the <b>'I2P application layer'</b>, 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 "<b>Streaming/datagram applications</b>: i2psnark, Syndie, i2phex..."
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/index.html:105
+msgid "<b>SAM/BOB applications</b>: IMule, i2p-bt, i2prufus, Robert..."
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/index.html:106
+#, python-format
+msgid ""
+"<b>Other I2P applications</b>: Syndie, EepGet, <a "
+"href=\"%(plugins)s\">plugins</a>..."
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/index.html:107
+msgid ""
+"<b>Regular applications</b>: 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/transport/index.html:2
+msgid "Transport Overview"
+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 three transports currently implemented:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/index.html:21
+#, python-format
+msgid "<a href=\"%(ntcp)s\">NTCP</a>, a Java New I/O (NIO) TCP transport"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/index.html:22
+#, python-format
+msgid " <a href=\"%(ssu)s\">SSU</a>, or Secure Semireliable UDP"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/index.html:23
+#, python-format
+msgid "<a href=\"%(ntcp2)s\">NTCP2</a>, a new version of NTCP"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/index.html:26
+msgid ""
+"Each provides a \"connection\" paradigm, with authentication,\n"
+"flow control, acknowledgments and retransmission."
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/index.html:32
+msgid "Transport Services"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/index.html:34
+msgid "The transport subsystem in I2P provides the following services:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/index.html:38
+#, python-format
+msgid ""
+"Reliable delivery of <a href=\"%(i2np)s\">I2NP</a> messages.\n"
+"Transports support I2NP message delivery ONLY.\n"
+"They are not general-purpose data pipes."
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/index.html:43
+msgid "In-order delivery of messages is NOT guaranteed by all transports."
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/index.html:44
+msgid ""
+"Maintain a set of router addresses, one or more for each transport,\n"
+"that the router publishes as its global contact information (the "
+"RouterInfo).\n"
+"Each transport may connect using one of these addresses, which may be\n"
+"IPv4 or (as of version 0.9.8) IPv6."
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/index.html:50
+msgid "Selection of the best transport for each outgoing message"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/index.html:51
+msgid "Queueing of outbound messages by priority"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/index.html:52
+msgid ""
+"Bandwidth limiting, both outbound and inbound, according to router "
+"configuration"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/index.html:53
+msgid "Setup and teardown of transport connections"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/index.html:54
+msgid "Encryption of point-to-point communications"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/index.html:55
+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:59
+msgid "Firewall port opening using UPnP (Universal Plug and Play)"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/index.html:60
+msgid "Cooperative NAT/Firewall traversal"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/index.html:61
+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:62
+msgid ""
+"Coordination of firewall status and local IP, and changes to either, "
+"among the transports"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/index.html:63
+#: i2p2www/pages/site/docs/transport/ssu.html:35
+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:64
+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:65
+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:69
+msgid "Qualification of valid IP addresses according to a local rule set"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/index.html:70
+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:77
+msgid "Transport Addresses"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/index.html:79
+msgid ""
+"The transport subsystem maintains a set of router addresses, each of "
+"which lists a transport method, IP, and port.\n"
+"These addresses constitute the advertised contact points, and are "
+"published by the router to the network database.\n"
+"Addresses may also contain an arbitrary set of additional options."
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/index.html:85
+msgid "Each transport method may publish multiple router addresses."
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/index.html:89
+msgid "Typical scenarios are:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/index.html:91
+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:92
+#, 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 <a "
+"href=\"%(ssu)s\">the SSU spec</a> for details)"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/index.html:96
+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:102
+msgid "Transport Selection"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/index.html:104
+#, python-format
+msgid ""
+"The transport system delivers <a href=\"%(i2np)s\">I2NP messages</a> "
+"only. The transport selected for any message is\n"
+"independent of the upper-layer protocols and contents (router or client "
+"messages, whether an external application was using\n"
+"TCP or UDP to connect to I2P, whether the upper layer was using\n"
+"<a href=\"%(streaming)s\">the streaming library</a>\n"
+"streaming\n"
+"or\n"
+"<a href=\"%(datagrams)s\">datagrams</a>,\n"
+"datagrams\n"
+"etc.)."
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/index.html:118
+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:124
+msgid "Whether a transport bids, and with what value, depend on numerous factors:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/index.html:128
+msgid "Configuration of transport preferences"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/index.html:129
+msgid "Whether the transport is already connected to the peer"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/index.html:130
+msgid ""
+"The number of current connections compared to various connection limit "
+"thresholds"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/index.html:131
+msgid "Whether recent connection attempts to the peer have failed"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/index.html:132
+msgid ""
+"The size of the message, as different transports have different size "
+"limits"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/index.html:133
+msgid ""
+"Whether the peer can accept incoming connections for that transport, as "
+"advertised in its RouterInfo"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/index.html:134
+msgid "Whether the connection would be indirect (requiring introducers) or direct"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/index.html:135
+msgid "The peer's transport preference, as advertised in its RouterInfo"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/index.html:138
+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:145
+msgid "New Transports and Future Work"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/index.html:147
+msgid "Additional transports may be developed, including:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/index.html:152
+msgid "A TLS/SSH look-alike transport"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/index.html:153
+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:154
+msgid "Tor-compatible pluggable transports"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/index.html:157
+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:164
+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:171
+#, python-format
+msgid ""
+"Analyze <a href=\"%(pdf)s\">Breaking and Improving Protocol "
+"Obfuscation</a>\n"
+"and see how transport-layer padding may improve things."
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:2
+msgid "NTCP (NIO-based TCP)"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:6
+#, python-format
+msgid ""
+"The others are <a href=\"%(ssu)s\">SSU</a> and <a "
+"href=\"%(ntcp2)s\">NTCP2</a>.\n"
+"NTCP is a Java NIO-based transport introduced in I2P release 0.6.1.22.\n"
+"Java NIO (new I/O) does not suffer from the 1 thread per connection "
+"issues of the old TCP transport.\n"
+"NTCP-over-IPv6 is supported as of version 0.9.8."
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:13
+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:21
+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:27
+#: i2p2www/pages/site/docs/transport/ssu.html:38
+msgid "Router Address Specification"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:29
+#: i2p2www/pages/site/docs/transport/ssu.html:40
+msgid "The following properties are stored in the network database."
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:44
+msgid "NTCP Protocol Specification"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:46
+msgid "Standard Message Format"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:47
+msgid ""
+"After establishment,\n"
+"the NTCP transport sends individual I2NP messages, with a simple "
+"checksum.\n"
+"The unencrypted message is encoded as follows:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:65
+msgid ""
+"The data is then AES/256/CBC encrypted. The session key for the "
+"encryption\n"
+"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:73
+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:81
+msgid "Time Sync Message Format"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:82
+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:93
+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:99
+msgid "Checksums"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:100
+#, python-format
+msgid ""
+"The standard and time sync messages use the Adler-32 checksum\n"
+"as defined in the <a href=\"%(rfc1950)s\">ZLIB Specification</a>."
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:106
+#: i2p2www/pages/site/docs/transport/ssu.html:187
+msgid "Idle Timeout"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:107
+#: i2p2www/pages/site/docs/transport/ssu.html:188
+msgid ""
+"Idle timeout and connection close is at the discretion of each endpoint "
+"and may vary.\n"
+"The current implementation lowers the timeout as the number of "
+"connections approaches the\n"
+"configured maximum, and raises the timeout when the connection count is "
+"low.\n"
+"The recommended minimum timeout is two minutes or more, and the "
+"recommended\n"
+"maximum timeout is ten minutes or more."
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:116
+msgid "RouterInfo Exchange"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:117
+msgid ""
+"After establishment, and every 30-60 minutes thereafter,\n"
+"the two routers should generally exchange RouterInfos using a "
+"DatabaseStoreMessage.\n"
+"However, Alice should check if the first queued message is a "
+"DatabaseStoreMessage\n"
+"so as not to send a duplicate message; this is often the case when "
+"connecting to a floodfill router."
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:125
+msgid "Establishment Sequence"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:126
+msgid ""
+"In the establish state, there is a 4-phase message sequence to exchange "
+"DH keys and signatures.\n"
+"In the first two messages there is a 2048-bit Diffie Hellman exchange.\n"
+"Then, signatures of the critical data are exchanged to confirm the "
+"connection."
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:142
+msgid "Legend:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:143
+msgid "256 byte DH public keys"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:147
+msgid "timestamps (4 bytes, seconds since epoch)"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:148
+msgid "32 byte Session key"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:149
+msgid "2 byte size of Alice identity to follow"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:152
+msgid "DH Key Exchange"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:153
+#, 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"
+"<a href=\"%(cryptography)s#elgamal\">ElGamal encryption</a>."
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:159
+msgid ""
+"The DH key exchange consists of a number of steps, displayed below.\n"
+"The mapping between these steps and the messages sent between I2P "
+"routers,\n"
+"is marked in bold."
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:165
+msgid ""
+"Alice generates a secret integer x. She then calculates <code>X = g^x mod"
+" p</code>."
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:166
+msgid "Alice sends X to Bob <b>(Message 1)</b>."
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:167
+msgid ""
+"Bob generates a secret integer y. He then calculates <code>Y = g^y mod "
+"p</code>."
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:168
+msgid "Bob sends Y to Alice.<b>(Message 2)</b>"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:169
+msgid "Alice can now compute <code>sessionKey = Y^x mod p</code>."
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:170
+msgid "Bob can now compute <code>sessionKey = X^y mod p</code>."
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:171
+msgid ""
+"Both Alice and Bob now have a shared key <code>sessionKey = g^(x*y) mod "
+"p</code>."
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:173
+#, python-format
+msgid ""
+"The sessionKey is then used to exchange identities in <b>Message 3</b> "
+"and <b>Message 4</b>.\n"
+"The exponent (x and y) length for the DH exchange is documented on the\n"
+"<a href=\"%(crypto)s#exponent\">cryptography page</a>."
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:193
+msgid "Message 1 (Session Request)"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:194
+#, python-format
+msgid ""
+"This is the DH request. Alice already has Bob's\n"
+"<a href=\"%(commonstructures)s#struct_RouterIdentity\">Router "
+"Identity</a>,\n"
+"IP address, and port, as contained in his\n"
+"<a href=\"%(commonstructures)s#struct_RouterInfo\">Router Info</a>,\n"
+"which was published to the\n"
+"<a href=\"%(netdb)s\">network database</a>.\n"
+"Alice sends Bob:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:207
+#: i2p2www/pages/site/docs/transport/ntcp.html:250
+#: i2p2www/pages/site/docs/transport/ntcp.html:332
+#: i2p2www/pages/site/docs/transport/ntcp.html:437
+msgid "Size:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:209
+msgid "Contents:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:227
+msgid "256 byte X from Diffie Hellman"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:229
+msgid "SHA256 Hash(X) xored with SHA256 Hash(Bob's `RouterIdentity`)"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:236
+#: i2p2www/pages/site/docs/transport/ntcp.html:319
+#: i2p2www/pages/site/docs/transport/ntcp.html:398
+msgid "Notes:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:237
+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:243
+msgid "Message 2 (Session Created)"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:244
+msgid "This is the DH reply. Bob sends Alice:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:252
+#: i2p2www/pages/site/docs/transport/ntcp.html:334
+#: i2p2www/pages/site/docs/transport/ntcp.html:439
+msgid "Unencrypted Contents:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:274
+#: i2p2www/pages/site/docs/transport/ntcp.html:310
+msgid "256 byte Y from Diffie Hellman"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:276
+msgid "SHA256 Hash(X concatenated with Y)"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:279
+#: i2p2www/pages/site/docs/transport/ntcp.html:364
+msgid "4 byte timestamp (seconds since the epoch)"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:281
+msgid "12 bytes random data"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:285
+#: i2p2www/pages/site/docs/transport/ntcp.html:376
+#: i2p2www/pages/site/docs/transport/ntcp.html:466
+msgid "Encrypted Contents:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:312
+#, python-format
+msgid ""
+"48 bytes <a href=\"%(cryptography)s#AES\">AES encrypted</a> using the DH "
+"session key and\n"
+"                  the last 16 bytes of Y as the IV"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:320
+msgid ""
+"Alice may drop the connection if the clock skew with Bob is too high as "
+"calculated using tsB."
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:325
+msgid "Message 3 (Session Confirm A)"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:326
+msgid ""
+"This contains Alice's router identity, and a signature of the critical "
+"data. Alice sends Bob:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:360
+msgid "2 byte size of Alice's router identity to follow (387+)"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:362
+msgid "Alice's 387+ byte `RouterIdentity`"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:366
+#: i2p2www/pages/site/docs/transport/ntcp.html:461
+msgid "0-15 bytes random data"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:368
+msgid ""
+"the `Signature` of the following concatenated data:\n"
+"             X, Y, Bob's `RouterIdentity`, tsA, tsB.\n"
+"             Alice signs it with the `SigningPrivateKey` associated with "
+"the `SigningPublicKey` in her `RouterIdentity`"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:389
+#, python-format
+msgid ""
+"448 bytes <a href=\"%(cryptography)s#AES\">AES encrypted</a> using the DH"
+" session key and\n"
+"                  the last 16 bytes of HXxorHI (i.e., the last 16 bytes "
+"of message #1) as the IV"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:400
+msgid "Bob verifies the signature, and on failure, drops the connection."
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:403
+msgid ""
+"Bob may drop the connection if the clock skew with Alice is too high as "
+"calculated using tsA."
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:406
+msgid ""
+"Alice will use the last 16 bytes of the encrypted contents of this "
+"message as the IV for the next message."
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:430
+msgid "Message 4 (Session Confirm B)"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:431
+msgid "This is a signature of the critical data. Bob sends Alice:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:455
+msgid ""
+"the `Signature` of the following concatenated data:\n"
+"             X, Y, Alice's `RouterIdentity`, tsA, tsB.\n"
+"             Bob signs it with the `SigningPrivateKey` associated with "
+"the `SigningPublicKey` in his `RouterIdentity`"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:479
+#, python-format
+msgid ""
+"Data <a href=\"%(cryptography)s#AES\">AES encrypted</a> using the DH "
+"session key and\n"
+"                  the last 16 bytes of the encrypted contents of message "
+"#2 as the IV\n"
+"                  48 bytes for a DSA signature, may vary for other "
+"signature types"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:488
+msgid "Alice verifies the signature, and on failure, drops the connection."
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:491
+msgid ""
+"Bob will use the last 16 bytes of the encrypted contents of this message "
+"as the IV for the next message."
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:506
+msgid "After Establishment"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:507
+msgid ""
+"The connection is established, and standard or time sync messages may be "
+"exchanged.\n"
+"All subsequent messages are AES encrypted using the negotiated DH session"
+" key.\n"
+"Alice will use the last 16 bytes of the encrypted contents of message #3 "
+"as the next IV.\n"
+"Bob will use the last 16 bytes of the encrypted contents of message #4 as"
+" the next IV."
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:516
+msgid "Check Connection Message"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:517
+msgid ""
+"Alternately, when Bob receives a connection, it could be a\n"
+"check connection (perhaps prompted by Bob asking for someone\n"
+"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:526
+msgid "32 bytes of uninterpreted, ignored data"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:527
+msgid "1 byte size"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:528
+msgid ""
+"that many bytes making up the local router's IP address (as reached by "
+"the remote side)"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:529
+msgid "2 byte port number that the local router was reached on"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:530
+msgid ""
+"4 byte i2p network time as known by the remote side (seconds since the "
+"epoch)"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:531
+msgid "uninterpreted padding data, up to byte 223"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:532
+msgid ""
+"xor of the local router's identity hash and the SHA256 of bytes 32 "
+"through bytes 223"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:535
+msgid "Check connection is completely disabled as of release 0.9.12."
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:539
+msgid "Discussion"
+msgstr "Müzakirə"
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:540
+#, python-format
+msgid "Now on the <a href=\"%(ntcpdisc)s\">NTCP Discussion Page</a>."
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:546
+msgid "The maximum message size should be increased to approximately 32 KB."
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:550
+msgid ""
+"A set of fixed packet sizes may be appropriate to further hide the data \n"
+"fragmentation to external adversaries, but the tunnel, garlic, and end to"
+" \n"
+"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:558
+msgid ""
+"Memory utilization (including that of the kernel) for NTCP should be "
+"compared to that for SSU."
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:562
+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/ssu.html:2
+msgid "Secure Semireliable UDP"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ssu.html:7
+#, python-format
+msgid ""
+"SSU (also called \"UDP\" in much of the I2P documentation and user "
+"interfaces)\n"
+"is one of three <a href=\"%(transports)s\">transports</a> currently "
+"implemented in I2P.\n"
+"The others are <a href=\"%(ntcp)s\">NTCP</a> and <a "
+"href=\"%(ntcp2)s\">NTCP2</a>."
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ssu.html:13
+msgid ""
+"SSU was introduced in I2P release 0.6.\n"
+"In a standard I2P installation, the router uses both NTCP and SSU for "
+"outbound connections.\n"
+"SSU-over-IPv6 is supported as of version 0.9.8."
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ssu.html:19
+msgid ""
+"SSU is called \"semireliable\" because it will repeatedly retransmit "
+"unacknowledged messages,\n"
+"but only up to a maximum number of times. After that, the message is "
+"dropped."
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ssu.html:24
+msgid "SSU Services"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ssu.html:26
+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:32
+msgid ""
+"Cooperative NAT/Firewall traversal using <a "
+"href=\"#introduction\">introducers</a>"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ssu.html:33
+msgid ""
+"Local IP detection by inspection of incoming packets and <a "
+"href=\"#peerTesting\">peer testing</a>"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ssu.html:34
+msgid ""
+"Communication of firewall status and local IP, and changes to either to "
+"NTCP"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ssu.html:46
+#: i2p2www/pages/site/docs/transport/ssu.html:60
+#: i2p2www/pages/site/docs/transport/ssu.html:61
+#: i2p2www/pages/site/docs/transport/ssu.html:63
+#: i2p2www/pages/site/docs/transport/ssu.html:66
+#: i2p2www/pages/site/docs/transport/ssu.html:70
+#: i2p2www/pages/site/docs/transport/ssu.html:71
+#: i2p2www/pages/site/docs/transport/ssu.html:77
+msgid "See below"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ssu.html:84
+msgid "Protocol Details"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ssu.html:86
+msgid "Congestion control"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ssu.html:88
+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:95
+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:106
+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:118
+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:125
+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:131
+msgid ""
+"For both MTU values, it is desirable that (MTU &#37; 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:137
+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:143
+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:149
+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:154
+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:161
+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:167
+msgid ""
+"For IPv6, the minimum MTU is 1280. The IPv6 IP/UDP header is 48 bytes,\n"
+"so we use an MTU where (MTN &#37; 16 == 0), which is true for 1280.\n"
+"The maximum IPv6 MTU is 1488.\n"
+" (max was 1472 prior to version 0.9.28)."
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ssu.html:174
+msgid "Message Size Limits"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ssu.html:175
+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:197
+msgid "Keys"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ssu.html:199
+msgid ""
+"All encryption used is AES256/CBC with 32 byte keys and 16 byte IVs.\n"
+"When Alice originates a session with Bob,\n"
+"the MAC and session keys are negotiated as part of the DH exchange, and "
+"are then used\n"
+"for the HMAC and encryption, respectively.  During the DH exchange, \n"
+"Bob's publicly knowable introKey is used for the MAC and encryption."
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ssu.html:207
+msgid ""
+"Both the initial message and the 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:216
+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:227
+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:238
+#, python-format
+msgid ""
+"For the DH key agreement,\n"
+"<a href=\"%(rfc3526)s\">RFC3526</a> 2048bit\n"
+"MODP group (#14) is used:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ssu.html:248
+#, python-format
+msgid ""
+"These are the same p and g used for I2P's\n"
+"<a href=\"%(cryptography)s#elgamal\">ElGamal encryption</a>."
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ssu.html:253
+msgid "Replay prevention"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ssu.html:255
+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:262
+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:270
+msgid "Addressing"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ssu.html:272
+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:284
+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 <a href=\"#capabilities\">below</a>."
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ssu.html:290
+#, python-format
+msgid ""
+"The addresses, options, and capabilities are published in the <a "
+"href=\"%(netdb)s\">network database</a>."
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ssu.html:295
+msgid "Direct Session Establishment"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ssu.html:296
+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:301
+msgid "Connection establishment (direct)"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ssu.html:302
+msgid ""
+"Alice connects directly to Bob.\n"
+"IPv6 is supported as of version 0.9.8."
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ssu.html:317
+#, python-format
+msgid ""
+"After the SessionConfirmed message is received, Bob sends a small\n"
+"<a href=\"%(i2npspec)s#msg_DeliveryStatus\">DeliveryStatus message</a>\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:326
+#, python-format
+msgid ""
+"After the status message is sent, the peers usually exchange\n"
+"<a href=\"%(i2npspec)s#msg_DatabaseStore\">DatabaseStore messages</a>\n"
+"containing their\n"
+"<a href=\"%(commonstructures)s#struct_RouterInfo\">RouterInfos</a>,\n"
+"however, this is not required."
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ssu.html:335
+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:344
+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:358
+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:385
+msgid "Connection establishment (indirect using an introducer)"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ssu.html:387
+msgid "Alice first connects to introducer Bob, who relays the request to Charlie."
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ssu.html:405
+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:419
+msgid "Peer testing"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ssu.html:421
+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:440
+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:450
+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:459
+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:470
+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:480
+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:488
+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:498
+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:526
+msgid "Transmission window, ACKs and Retransmissions"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ssu.html:527
+#, 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"
+"<a href=\"%(ssuspec)s\">the protocol specification page</a>\n"
+"for details."
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ssu.html:535
+#, 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 <a href=\"%(streaming)s\">streaming</a>.\n"
+"See the code for initial, min and max parameters."
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ssu.html:547
+msgid "Security"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ssu.html:548
+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:556
+msgid ""
+"The details of validation are not specified\n"
+"here. Implementers should add defenses where appropriate."
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ssu.html:562
+msgid "Peer capabilities"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ssu.html:566
+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:578
+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:587
+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:593
+msgid ""
+"The current implementation repeatedly sends acknowledgments for the same "
+"packets,\n"
+"which unnecessarily increases overhead."
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ssu.html:598
+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:604
+msgid "The protocol should be extended to exchange MTUs during the setup."
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ssu.html:608
+msgid "Rekeying is currently unimplemented and may never be."
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ssu.html:612
+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:617
+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:623
+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:629
+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:633
+msgid "Capacities appear to be unused."
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ssu.html:637
+msgid ""
+"Signed-on times in SessionCreated and SessionConfirmed appear to be "
+"unused or unverified."
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ssu.html:642
+msgid "Implementation Diagram"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ssu.html:643
+msgid ""
+"This diagram\n"
+"should accurately reflect the current implementation, however there may "
+"be small differences."
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ssu.html:651
+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"
+"</i>gateway</i>, 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 <i>endpoint</i> 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"
+"<a href=\"%(tunnelrouting)s\">on the tunnel overview page</a>."
+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, <a href=\"%(i2np)s\">I2NP messages</a> 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"
+"<a href=\"%(i2np)s\">I2NP messages</a> into fixed-size\n"
+"<a href=\"%(tunnelmessage)s\">tunnel messages</a>\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"
+"<a href=\"%(tunnelmessage)s\">tunnel message specification</a>."
+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:243
+msgid ""
+"Duplicate message detection is handled by a decaying Bloom filter on "
+"message\n"
+"IVs.  Each router maintains a single Bloom filter to contain the XOR of "
+"the IV and\n"
+"the first block of the message received for all of the tunnels it is "
+"participating\n"
+"in, modified to drop seen entries after 10-20 minutes (when the tunnels "
+"will have\n"
+"expired).  The size of the bloom filter and the parameters used are "
+"sufficient to\n"
+"more than saturate the router's network connection with a negligible "
+"chance of \n"
+"false positive.  The unique value fed into the Bloom filter is the XOR of"
+" the IV \n"
+"and the first block so as to prevent nonsequential colluding peers in the"
+" tunnel \n"
+"from tagging a message by resending it with the IV and first block "
+"switched."
+msgstr ""
+
+#: i2p2www/pages/site/docs/tunnels/implementation.html:256
+msgid "Endpoint Processing"
+msgstr ""
+
+#: i2p2www/pages/site/docs/tunnels/implementation.html:258
+msgid ""
+"After receiving and validating a tunnel message at the last hop in the "
+"tunnel,\n"
+"how the endpoint recovers the data encoded by the gateway depends upon "
+"whether \n"
+"the tunnel is an inbound or an outbound tunnel.  For outbound tunnels, "
+"the \n"
+"endpoint encrypts the message with its layer key just like any other "
+"participant, \n"
+"exposing the preprocessed data.  For inbound tunnels, the endpoint is "
+"also the \n"
+"tunnel creator so they can merely iteratively decrypt the IV and message,"
+" using the \n"
+"layer and IV keys of each step in reverse order."
+msgstr ""
+
+#: i2p2www/pages/site/docs/tunnels/implementation.html:268
+msgid ""
+"At this point, the tunnel endpoint has the preprocessed data sent by the "
+"gateway,\n"
+"which it may then parse out into the included I2NP messages and forwards "
+"them as\n"
+"requested in their delivery instructions."
+msgstr ""
+
+#: i2p2www/pages/site/docs/tunnels/implementation.html:275
+msgid "Tunnel Building"
+msgstr ""
+
+#: i2p2www/pages/site/docs/tunnels/implementation.html:277
+msgid ""
+"When building a tunnel, the creator must send a request with the "
+"necessary\n"
+"configuration data to each of the hops and wait for all of them to agree "
+"before\n"
+"enabling the tunnel.  The requests are encrypted so that only the peers "
+"who need\n"
+"to know a piece of information (such as the tunnel layer or IV key) has "
+"that\n"
+"data.  In addition, only the tunnel creator will have access to the "
+"peer's\n"
+"reply.  There are three important dimensions to keep in mind when "
+"producing\n"
+"the tunnels: what peers are used (and where), how the requests are sent "
+"(and \n"
+"replies received), and how they are maintained."
+msgstr ""
+
+#: i2p2www/pages/site/docs/tunnels/implementation.html:291
+msgid ""
+"Beyond the two types of tunnels - inbound and outbound - there are two "
+"styles\n"
+"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:299
+msgid "Exploratory tunnel peer selection"
+msgstr ""
+
+#: i2p2www/pages/site/docs/tunnels/implementation.html:301
+msgid ""
+"Exploratory tunnels are built out of a random selection of peers from a "
+"subset\n"
+"of the network.  The particular subset varies on the local router and on "
+"what their\n"
+"tunnel routing needs are.  In general, the exploratory tunnels are built "
+"out of\n"
+"randomly selected peers who are in the peer's \"not failing but active\" "
+"profile\n"
+"category.  The secondary purpose of the tunnels, beyond merely tunnel "
+"routing,\n"
+"is to find underutilized high capacity peers so that they can be promoted"
+" for\n"
+"use in client tunnels."
+msgstr ""
+
+#: i2p2www/pages/site/docs/tunnels/implementation.html:311
+#, python-format
+msgid ""
+"Exploratory peer selection is discussed further on the\n"
+"<a href=\"%(peerselection)s\">Peer Profiling and Selection page</a>."
+msgstr ""
+
+#: i2p2www/pages/site/docs/tunnels/implementation.html:317
+msgid "Client tunnel peer selection"
+msgstr ""
+
+#: i2p2www/pages/site/docs/tunnels/implementation.html:319
+msgid ""
+"Client tunnels are built with a more stringent set of requirements - the "
+"local\n"
+"router will select peers out of its \"fast and high capacity\" profile "
+"category so\n"
+"that performance and reliability will meet the needs of the client "
+"application.\n"
+"However, there are several important details beyond that basic selection "
+"that \n"
+"should be adhered to, depending upon the client's anonymity needs."
+msgstr ""
+
+#: i2p2www/pages/site/docs/tunnels/implementation.html:327
+#, python-format
+msgid ""
+"Client peer selection is discussed further on the\n"
+"<a href=\"%(peerselection)s\">Peer Profiling and Selection page</a>."
+msgstr ""
+
+#: i2p2www/pages/site/docs/tunnels/implementation.html:332
+msgid "Peer Ordering within Tunnels"
+msgstr ""
+
+#: i2p2www/pages/site/docs/tunnels/implementation.html:334
+#, python-format
+msgid ""
+"Peers are ordered within tunnels to deal with the\n"
+"<a href=\"%(pdf)s\">predecessor attack</a>\n"
+"<a href=\"%(pdf2008)s\">(2008 update)</a>."
+msgstr ""
+
+#: i2p2www/pages/site/docs/tunnels/implementation.html:341
+msgid ""
+"To frustrate the predecessor \n"
+"attack, the tunnel selection keeps the peers selected in a strict order -"
+"\n"
+"if A, B, and C are in a tunnel for a particular tunnel pool, the hop "
+"after A is always B, and the hop after\n"
+"B is always C."
+msgstr ""
+
+#: i2p2www/pages/site/docs/tunnels/implementation.html:348
+msgid ""
+"Ordering is implemented by generating a random 32-byte key for each\n"
+"tunnel pool at startup.\n"
+"Peers should not be able to guess the ordering, or an attacker could\n"
+"craft two router hashes far apart to maximize the chance of being at both"
+"\n"
+"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:363
+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:370
+msgid "Request delivery"
+msgstr ""
+
+#: i2p2www/pages/site/docs/tunnels/implementation.html:372
+#, python-format
+msgid ""
+"A multi-hop tunnel is built using a single build message which is "
+"repeatedly\n"
+"decrypted and forwarded. In the terminology of\n"
+"<a href=\"%(pdf)s\">Hashing it out in Public</a>,\n"
+"this is \"non-interactive\" telescopic tunnel building."
+msgstr ""
+
+#: i2p2www/pages/site/docs/tunnels/implementation.html:379
+#, python-format
+msgid ""
+"This tunnel request preparation, delivery, and response method is\n"
+"<a href=\"%(tunnelcreation)s\">designed</a> 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:390
+#, python-format
+msgid ""
+"The details of tunnel request and response messages, and their "
+"encryption,\n"
+"<a href=\"%(tunnelcreation)s\">are specified here</a>."
+msgstr ""
+
+#: i2p2www/pages/site/docs/tunnels/implementation.html:395
+msgid ""
+"Peers may reject tunnel creation requests for a variety of reasons, "
+"though\n"
+"a series of four increasingly severe rejections are known: probabilistic "
+"rejection\n"
+"(due to approaching the router's capacity, or in response to a flood of "
+"requests), \n"
+"transient overload, bandwidth overload, and critical failure.  When "
+"received, \n"
+"those four are interpreted by the tunnel creator to help adjust their "
+"profile of\n"
+"the router in question."
+msgstr ""
+
+#: i2p2www/pages/site/docs/tunnels/implementation.html:404
+#, python-format
+msgid ""
+"For more information on peer profiling, see the\n"
+"<a href=\"%(peerselection)s\">Peer Profiling and Selection page</a>."
+msgstr ""
+
+#: i2p2www/pages/site/docs/tunnels/implementation.html:410
+msgid "Tunnel Pools"
+msgstr ""
+
+#: i2p2www/pages/site/docs/tunnels/implementation.html:412
+#, python-format
+msgid ""
+"To allow efficient operation, the router maintains a series of tunnel "
+"pools,\n"
+"each managing a group of tunnels used for a specific purpose with their "
+"own\n"
+"configuration.  When a tunnel is needed for that purpose, the router "
+"selects one\n"
+"out of the appropriate pool at random.  Overall, there are two "
+"exploratory tunnel\n"
+"pools - one inbound and one outbound - each using the router's default "
+"configuration.\n"
+"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 <a "
+"href=\"%(i2cp)s\">I2CP</a>, or the router's defaults if\n"
+"not specified."
+msgstr ""
+
+#: i2p2www/pages/site/docs/tunnels/implementation.html:424
+#, python-format
+msgid ""
+"Each pool has within its configuration a few key settings, defining how "
+"many\n"
+"tunnels to keep active, how many backup tunnels to maintain in case of "
+"failure,\n"
+"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 <a href=\"%(i2cp)s\">I2CP "
+"page</a>."
+msgstr ""
+
+#: i2p2www/pages/site/docs/tunnels/implementation.html:434
+msgid "Tunnel Lengths and Defaults"
+msgstr ""
+
+#: i2p2www/pages/site/docs/tunnels/implementation.html:436
+msgid "On the tunnel overview page"
+msgstr ""
+
+#: i2p2www/pages/site/docs/tunnels/implementation.html:438
+msgid "Anticipatory Build Strategy and Priority"
+msgstr ""
+
+#: i2p2www/pages/site/docs/tunnels/implementation.html:440
+msgid ""
+"Tunnel building is expensive, and tunnels expire a fixed time after they "
+"are built.\n"
+"However, when a pool that runs out of tunnels, the Destination is "
+"essentially dead.\n"
+"In addition, tunnel build success rate may vary greatly with both local "
+"and global\n"
+"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:451
+msgid ""
+"For each tuple {exploratory/client, in/out, length, length variance}\n"
+"the router maintains statistics on the time required for a successful\n"
+"tunnel build.\n"
+"Using these statistics, it calculates how long before a tunnel's "
+"expiration\n"
+"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:462
+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:471
+msgid "Tunnel Message Throttling"
+msgstr ""
+
+#: i2p2www/pages/site/docs/tunnels/implementation.html:473
+msgid ""
+"Even though the tunnels within I2P bear a resemblance to a circuit "
+"switched\n"
+"network, everything within I2P is strictly message based - tunnels are "
+"merely\n"
+"accounting tricks to help organize the delivery of messages.  No "
+"assumptions are\n"
+"made regarding reliability or ordering of messages, and retransmissions "
+"are left\n"
+"to higher levels (e.g. I2P's client layer streaming library).  This "
+"allows I2P\n"
+"to take advantage of throttling techniques available to both packet "
+"switched and\n"
+"circuit switched networks.  For instance, each router may keep track of "
+"the \n"
+"moving average of how much data each tunnel is using, combine that with "
+"all of \n"
+"the averages used by other tunnels the router is participating in, and be"
+" able\n"
+"to accept or reject additional tunnel participation requests based on its"
+" \n"
+"capacity and utilization.  On the other hand, each router can simply drop"
+" \n"
+"messages that are beyond its capacity, exploiting the research used on "
+"the \n"
+"normal Internet."
+msgstr ""
+
+#: i2p2www/pages/site/docs/tunnels/implementation.html:489
+msgid ""
+"In the current implementation, routers implement a\n"
+"weighted random early discard (WRED) strategy.\n"
+"For all participating routers (internal participant, inbound gateway, and"
+" outbound endpoint),\n"
+"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:507
+msgid "Mixing/batching"
+msgstr ""
+
+#: i2p2www/pages/site/docs/tunnels/implementation.html:509
+msgid ""
+"What strategies could be used at the gateway and at each hop for "
+"delaying,\n"
+"reordering, rerouting, or padding messages?  To what extent should this "
+"be done\n"
+"automatically, how much should be configured as a per tunnel or per hop "
+"setting,\n"
+"and how should the tunnel's creator (and in turn, user) control this "
+"operation?\n"
+"All of this is left as unknown, to be worked out for a distant future "
+"release."
+msgstr ""
+
+#: i2p2www/pages/site/docs/tunnels/implementation.html:518
+msgid "Padding"
+msgstr ""
+
+#: i2p2www/pages/site/docs/tunnels/implementation.html:519
+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:529
+msgid ""
+"WRED strategies have a significant impact on end-to-end performance,\n"
+"and prevention of network congestion collapse.\n"
+"The current WRED strategy should be carefully evaluated and improved."
+msgstr ""
+
+#: 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 <a "
+"href=\"%(tunnelimpl)s\">here</a> for the current implementation"
+msgstr ""
+
+#: i2p2www/pages/site/docs/tunnels/unidirectional.html:3
+msgid "November 2016"
+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 information 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 "Bənzərlərin seçimi"
+
+#: 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 "Baxış-icmal"
+
+#: 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 <a href=\"%(pdf)s\">paper by Hermann and Grothoff</a>\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/az/LC_MESSAGES/get-involved.po b/i2p2www/translations/az/LC_MESSAGES/get-involved.po
new file mode 100644
index 00000000..86c7b1e5
--- /dev/null
+++ b/i2p2www/translations/az/LC_MESSAGES/get-involved.po
@@ -0,0 +1,4123 @@
+# Azerbaijani translations for I2P.
+# Copyright (C) 2018 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: 2018-08-24 11:47+0000\n"
+"PO-Revision-Date: 2018-08-24 11:51+0000\n"
+"Last-Translator: Nikafn <appone6@gmail.com>\n"
+"Language-Team: Azerbaijani "
+"(http://www.transifex.com/otf/I2P/language/az/)\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 1.3\n"
+
+#: i2p2www/pages/site/get-involved/donate.html:2
+#: i2p2www/pages/site/get-involved/index.html:82
+msgid "Donate"
+msgstr ""
+
+#: 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 ""
+
+#: i2p2www/pages/site/get-involved/donate.html:10
+msgid "Tax Status"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/donate.html:11
+msgid ""
+"I2P is not incorporated.\n"
+"Your contributions are probably not tax-deductible.\n"
+"If you would like to discuss a large contribution, please contact eche|on."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/donate.html:17
+msgid "Stickers"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/donate.html:18
+msgid ""
+"While supplies last, we offer I2P stickers to those who donate enough\n"
+"to cover PayPal fees and postage from the U.S.\n"
+"You must include \"stickers please\" and your address in the Paypal "
+"comments.\n"
+"For other payment methods, follow up with an email to eche|on\n"
+"with the subject \"stickers please\", your payment information, and your "
+"address."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/donate.html:25
+msgid "Please allow 30-60 days for delivery."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/donate.html:30
+#, python-format
+msgid ""
+"As of %(date)s, eche|on has been running a\n"
+"<a href=\"%(coinurl)s\">%(cointype)s</a> account for the I2P project.\n"
+"ATTENTION! The address changed on 02-20-2014. ATTENTION!\n"
+"If you'd like to donate using %(cointype)s, just transfer your\n"
+"desired amount of coins to the account <b>%(account)s</b>\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:42
+#: i2p2www/pages/site/get-involved/donate.html:58
+#: i2p2www/pages/site/get-involved/donate.html:74
+msgid "For easy usage, use the QR code below!"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/donate.html:47
+#, python-format
+msgid ""
+"As of %(date)s, Meeh has been running a\n"
+"<a href=\"%(coinurl)s\">%(cointype)s</a> 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 <b>%(account)s</b>\n"
+"and leave Meeh a note if you'd like your donation to be\n"
+"mentioned on the I2P webpage."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/donate.html:63
+#, python-format
+msgid ""
+"As of %(date)s, echelon has been running a\n"
+" <a href=\"%(coinurl)s\">%(cointype)s</a> 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 <b>%(account)s</b>\n"
+" and leave echelon a note if you'd like your donation to be\n"
+" mentioned on the I2P webpage."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/donate.html:80
+#, python-format
+msgid ""
+"We accept most altcoins, just ask Meeh. Other altcoins can be converted "
+"and exchanged for a crypto currency we currently support. Please send a "
+"mail to \"%(account)s\" for a such donation."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/donate.html:87
+#, python-format
+msgid "You can donate direct via PayPal to the account \"%(account)s\"."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/donate.html:93
+msgid "One time donation:"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/donate.html:107
+msgid "Donate 10 &euro;/month for 12 months:"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/donate.html:115
+#: i2p2www/pages/site/get-involved/donate.html:127
+#: i2p2www/pages/site/get-involved/donate.html:139
+#: i2p2www/pages/site/get-involved/donate.html:151
+msgid "I2P donation "
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/donate.html:121
+msgid "Donate 20 &euro;/month for 12 months:"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/donate.html:133
+msgid "Donate 30 &euro;/month for 12 months:"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/donate.html:145
+msgid "Donate 50 &euro;/month for 12 months:"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/donate.html:160
+msgid "Flattr this"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/donate.html:165
+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 ""
+
+#: i2p2www/pages/site/get-involved/donate.html:169
+#, python-format
+msgid ""
+"If you'd like to donate via  snail mail, send an email to <a "
+"href=\"mailto:%(email)s?subject=information about snailmail "
+"donation\">%(email)s</a>\n"
+" and you'll receive an email with instructions detailing how to proceed."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/donate.html:174
+#, 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 <a "
+"href=\"%(halloffame)s\">hall of fame</a>."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/index.html:2
+msgid "Get Involved!"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/index.html:4
+msgid "We need your help!"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/index.html:5
+msgid ""
+"To get involved, please feel free to join us on the #i2p-dev IRC channel "
+"(on\n"
+"irc.freenode.net, irc.oftc.net, or within I2P on irc.echelon.i2p, "
+"irc.dg.i2p or irc.postman.i2p)."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/index.html:9
+#, python-format
+msgid ""
+"If you're interested in joining our <a href=\"%(team)s\">team</a>, 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 get you 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 "Test etmək"
+
+#: i2p2www/pages/site/get-involved/index.html:25
+#, python-format
+msgid ""
+"Run the latest builds from <a href=\"%(monotone)s\">monotone</a>\n"
+"and report results on #i2p or as bugs on <a "
+"href=\"http://%(trac)s/report/1\">Trac</a>."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/index.html:30
+msgid "Documentation"
+msgstr ""
+
+#: 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 ""
+
+#: i2p2www/pages/site/get-involved/index.html:40
+msgid "Make an eepsite! Add some content! Contribute to the community!"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/index.html:43
+msgid "Services"
+msgstr ""
+
+#: 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 ""
+
+#: 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 <a href=\"%(apps)s\">applications page</a>."
+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 <a href=\"http://%(trac)s/report/1\">Trac</a>\n"
+"or the TODO list on <a href=\"http://%(zzz)s\">%(zzz)s</a> for\n"
+"some ideas on where to start.\n"
+"See the <a href=\"%(newdevs)s\">new developer's guide</a> for details."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/index.html:64
+msgid "Translation"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/index.html:65
+#, python-format
+msgid ""
+"Help translate the website and the software into your language.\n"
+"See the <a href=\"%(newtrans)s\">new translator's guide</a> for details."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/index.html:69
+msgid "Analysis"
+msgstr ""
+
+#: 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"
+"<a href=\"%(threatmodel)s\">threat models</a>,\n"
+"and DOS and other weaknesses due to securities holes,\n"
+"need researching."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/index.html:77
+msgid "Reseeding"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/index.html:78
+#, python-format
+msgid ""
+"Set up a reseed server for new routers to bootstrap from.\n"
+"Detailed instructions are on our <a href=\"%(reseed)s\">reseed server "
+"page</a>."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/roadmap-2016.html:2
+#: i2p2www/pages/site/get-involved/roadmap-2017.html:2
+#: i2p2www/pages/site/get-involved/roadmap.html:2
+msgid "Roadmap"
+msgstr "Yol xəritəsi"
+
+#: i2p2www/pages/site/get-involved/roadmap-2016.html:3
+msgid "January 2016"
+msgstr "Yanvar 2016"
+
+#: i2p2www/pages/site/get-involved/roadmap-2016.html:169
+#: i2p2www/pages/site/get-involved/roadmap-2016.html:182
+#: i2p2www/pages/site/get-involved/roadmap-2017.html:295
+#: i2p2www/pages/site/get-involved/roadmap.html:422
+#, python-format
+msgid ""
+"Reachability Mapping / handle peers partially reachable / enhanced <a "
+"href=\"%(todo)s#fullRestrictedRoutes\">restricted routes</a>"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/roadmap-2016.html:172
+#: i2p2www/pages/site/get-involved/roadmap-2016.html:185
+#: i2p2www/pages/site/get-involved/roadmap-2017.html:298
+#: i2p2www/pages/site/get-involved/roadmap.html:425
+msgid "Full restricted routes"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/roadmap-2016.html:173
+#: i2p2www/pages/site/get-involved/roadmap-2016.html:186
+#: i2p2www/pages/site/get-involved/roadmap-2017.html:299
+#: i2p2www/pages/site/get-involved/roadmap.html:426
+msgid "Tunnel mixing and padding"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/roadmap-2016.html:174
+#: i2p2www/pages/site/get-involved/roadmap-2016.html:187
+#: i2p2www/pages/site/get-involved/roadmap-2017.html:300
+#: i2p2www/pages/site/get-involved/roadmap.html:427
+msgid "User defined message delays"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/roadmap-2016.html:190
+#: i2p2www/pages/site/get-involved/roadmap-2017.html:303
+#: i2p2www/pages/site/get-involved/roadmap.html:430
+#, python-format
+msgid ""
+"Please see the <a href=\"%(todo)s\">TODO</a> list for more detailed info "
+"about some of these tasks."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/roadmap-2017.html:3
+#: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:3
+msgid "January 2017"
+msgstr "Yanvar 2017"
+
+#: i2p2www/pages/site/get-involved/roadmap.html:3
+msgid "August 2018"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/todo.html:2
+msgid "I2P Project Targets"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/todo.html:5
+#: i2p2www/pages/site/get-involved/todo.html:47
+msgid "Core functionality"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/todo.html:7
+#: i2p2www/pages/site/get-involved/todo.html:50
+msgid "NetworkDB and profile tuning and ejection policy for large nets"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/todo.html:11
+#: i2p2www/pages/site/get-involved/todo.html:74
+msgid "Security / anonymity"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/todo.html:13
+#: i2p2www/pages/site/get-involved/todo.html:77
+msgid "Full blown n-hop restricted routes with optional trusted links"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/todo.html:16
+#: i2p2www/pages/site/get-involved/todo.html:96
+msgid "Hashcash for routerIdentity, destination, and tunnel request"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/todo.html:19
+#: i2p2www/pages/site/get-involved/todo.html:125
+msgid "Advanced tunnel operation (batching/mixing/throttling/padding)"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/todo.html:22
+#: i2p2www/pages/site/get-involved/todo.html:162
+msgid "Stop &amp; go mix w/ garlics &amp; tunnels"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/todo.html:26
+#: i2p2www/pages/site/get-involved/todo.html:176
+msgid "Performance"
+msgstr "Məhsuldarlıq"
+
+#: i2p2www/pages/site/get-involved/todo.html:31
+#, python-format
+msgid ""
+"Note: This page is not up-to-date.\n"
+"See <a href=\"%(roadmap)s\">the roadmap</a> for current plans."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/todo.html:36
+#, 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 <a href=\"%(roadmap)s\">the roadmap</a>. Want to "
+"help?\n"
+"<a href=\"%(volunteer)s\">Get involved</a>!"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/todo.html:53
+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:68
+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:80
+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:99
+#, 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 <a "
+"href=\"%(link)s\">Sybil</a> \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:107
+msgid ""
+"<a href=\"http://www.hashcash.org/\">Hashcash</a> 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:118
+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:128
+#, 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"
+"<a href=\"%(pdf)s\">research</a> \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:141
+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:154
+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:165
+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:177
+#, python-format
+msgid ""
+"Performance related improvements are listed on the\n"
+"<a href=\"%(futureperf)s\">Performance</a> 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:114
+msgid "Arabic translation"
+msgstr "Ərəbcə tərcümə"
+
+#: 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 &euro; to this bounty.\n"
+"Bounty was almost fullfilled with <a "
+"href=\"http://echelon.i2p/btci2p/\">btci2p</a>, only a small\n"
+"part of creating a plugin is leftover. User giv has been paid for the "
+"work."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/datastore.html:2
+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"
+"<a href=\"http://bugs.debian.org/cgi-"
+"bin/bugreport.cgi?bug=448638\">448638</a> \n"
+"needs to be closed successfully.\n"
+"\n"
+"Done in 2017 by mhatta."
+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 for I2P"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/index.html:5
+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:17
+msgid ""
+"We are also keeping open the ability for people who want to support I2P \n"
+"but don't have strong feelings about the bounties available.  Those "
+"people\n"
+"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:26
+msgid "Current bounties"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/index.html:29
+#: i2p2www/pages/site/get-involved/bounties/index.html:77
+#: i2p2www/pages/site/get-involved/bounties/index.html:97
+msgid "Name"
+msgstr "Ad"
+
+#: i2p2www/pages/site/get-involved/bounties/index.html:29
+#: i2p2www/pages/site/get-involved/bounties/index.html:77
+#: i2p2www/pages/site/get-involved/bounties/index.html:97
+msgid "Status"
+msgstr "Status"
+
+#: i2p2www/pages/site/get-involved/bounties/index.html:29
+#: i2p2www/pages/site/get-involved/bounties/index.html:77
+msgid "Judge"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/index.html:29
+#: i2p2www/pages/site/get-involved/bounties/index.html:77
+msgid "Dev"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/index.html:29
+#: i2p2www/pages/site/get-involved/bounties/index.html:77
+msgid "Bounty"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/index.html:31
+msgid "Frost for I2P datastorage"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/index.html:32
+#: i2p2www/pages/site/get-involved/bounties/index.html:39
+#: i2p2www/pages/site/get-involved/bounties/index.html:46
+#: i2p2www/pages/site/get-involved/bounties/index.html:67
+#: i2p2www/pages/site/get-involved/bounties/index.html:87
+msgid "Proposal in development"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/index.html:34
+#: i2p2www/pages/site/get-involved/bounties/index.html:41
+#: i2p2www/pages/site/get-involved/bounties/index.html:48
+#: i2p2www/pages/site/get-involved/bounties/index.html:69
+#: i2p2www/pages/site/get-involved/bounties/index.html:82
+msgid "vacant"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/index.html:38
+msgid "Eepsites served out of I2P datastorage"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/index.html:45
+msgid "Backporting Phex code onto I2PHex"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/index.html:52
+msgid "Bitcoin client for I2P"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/index.html:53
+msgid "Done, phase of verification"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/index.html:59
+msgid "Unit tests and Multi-router Simulation"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/index.html:60
+msgid "Partly done, partly in work, partly still open"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/index.html:74
+msgid "Hold bounties, set on hold due to jrandom AWOL and missing funding"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/index.html:79
+msgid "Bundling bounties"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/index.html:80
+msgid "Proposed"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/index.html:94
+msgid "Claimed bounties"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/index.html:97
+msgid "Dev team"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/index.html:99
+msgid "I2P package in Debian and Ubuntu mirrors"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/index.html:104
+msgid "Make I2P IPv6 native"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/index.html:109
+msgid "Setting up a SILC server"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/index.html:119
+msgid "Datastore over I2P"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/index.html:124
+#: i2p2www/pages/site/get-involved/bounties/russian-trans.html:3
+msgid "Russian translation"
+msgstr "Rusca tərcümə"
+
+#: i2p2www/pages/site/get-involved/bounties/index.html:129
+msgid "Swarming file transfer"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/index.html:134
+msgid "Streaming library window size"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/index.html:139
+msgid "IRC connect time monitor"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/index.html:144
+msgid "Unit tests (part 1)"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/index.html:156
+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:23
+#: i2p2www/pages/site/get-involved/bounties/vuze-plugin.html:20
+msgid ""
+"For bounties to be declared done and paid, we need the plugin AND the "
+"source.\n"
+"Source and code need to be licensed under a free license (free to change "
+"and \n"
+"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, too."
+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) and has been updated just with\n"
+"small fixes to keep it running. 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 3 Bitcoin."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/bounties/syndie-2012.html:23
+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 &euro;"
+msgstr ""
+
+#: 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.<br>\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 ""
+
+#: 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"
+"<a href=\"%(clover)s\">Clover</a>).  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&#37; 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&#37;\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 ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:7
+#: i2p2www/pages/site/get-involved/develop/applications.html:15
+msgid "Why write I2P-specific code?"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:8
+#: i2p2www/pages/site/get-involved/develop/applications.html:101
+msgid "Important concepts"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:9
+#: i2p2www/pages/site/get-involved/develop/applications.html:189
+msgid "Development options"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:10
+#: i2p2www/pages/site/get-involved/develop/applications.html:302
+msgid "Start developing - a simple guide"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:17
+#, python-format
+msgid ""
+"There are multiple ways to use applications in I2P.\n"
+"Using <a href=\"%(i2ptunnel)s\">I2PTunnel</a>,\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 <a href=\"#tunnel.serverclient\">Figure 1</a>."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:25
+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 <a href=\"#tunnel.peertopeer\">Figure 2</a>.\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:36
+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:42
+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:56
+#: i2p2www/pages/site/get-involved/develop/applications.html:58
+msgid ""
+"Creating a server-client connection using I2PTunnel only requires "
+"creating a single tunnel."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:58
+msgid "Figure 1:"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:63
+#: i2p2www/pages/site/get-involved/develop/applications.html:65
+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:65
+msgid "Figure 2:"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:69
+msgid "In summary, a number of reasons to write I2P-specific code:"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:73
+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:77
+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:82
+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:89
+#, python-format
+msgid ""
+"I2P supports a standard <a href=\"%(plugins)s\">plugins interface</a> for"
+" developers\n"
+"so that applications may be easily integrated and distributed."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:95
+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:103
+msgid "There are a few changes that require adjusting to when using I2P:"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:107
+msgid "Destination ~= host+port"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:109
+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:117
+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:122
+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:129
+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:134
+#, 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"
+"<a href=\"%(naming)s\">Further information on the naming system</a> is "
+"available."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:148
+#, python-format
+msgid ""
+"While most applications do not need to distinguish protocols and ports,\n"
+"I2P <em>does</em> 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 <a href=\"%(datagrams)s\">datagram page</a> 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:157
+msgid "Anonymity and confidentiality"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:159
+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:166
+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:175
+msgid "I2P datagrams can be up to several KB"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:177
+#, 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 <a href=\"%(datagrams)s\">datagram page</a> 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:191
+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:196
+msgid "Streaming Lib"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:197
+#, python-format
+msgid ""
+"The <a href=\"%(streaming)s\">full streaming library</a> is now the "
+"standard\n"
+"interface. It allows programming using TCP-like sockets, as explained in "
+"the <a href=\"#start.streaming\">Streaming development guide</a>."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:203
+#, python-format
+msgid ""
+"BOB is the <a href=\"%(bob)s\">Basic Open Bridge</a>,\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 <a href=\"http://%(boburl)s/\">eepsite</a>."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:216
+msgid "SAM is not recommended. SAM V2 is okay, SAM V3 is recommended."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:217
+#, python-format
+msgid ""
+"SAM is the <a href=\"%(sam)s\">Simple Anonymous Messaging</a> 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:224
+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:227
+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:230
+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:236
+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:243
+#, python-format
+msgid ""
+"<a href=\"%(samv2)s\">SAM V2</a> is a new version used by imule\n"
+"that fixes some of the problems in <a href=\"%(sam)s\">SAM</a>.\n"
+"<br />\n"
+"<a href=\"%(samv3)s\">SAM V3</a> is used by imule since version 1.4.0."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:251
+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:263
+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:270
+msgid "Removed"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:271
+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:276
+msgid "Datagrams"
+msgstr "Dataqtamlar"
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:277
+msgid "Recommended for UDP-like applications"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:278
+#, python-format
+msgid ""
+"The <a href=\"%(datagrams)s\">Datagram library</a> allows sending UDP-"
+"like packets.\n"
+"It's possible to use:"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:283
+msgid "Repliable datagrams"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:284
+msgid "Raw datagrams"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:288
+msgid "Not recommended"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:289
+#, python-format
+msgid ""
+"<a href=\"%(i2cp)s\">I2CP</a> 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:296
+msgid "Web Applications"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:297
+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:303
+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 <a "
+"href=\"#start.streaming\">streaming library</a> or datagram library.\n"
+"Using another programming language, SAM or BOB can be used."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:309
+msgid "Developing with the streaming library"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:311
+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:316
+msgid "This will require the following libraries in your classpath:"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:320
+msgid "The streaming library itself"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:321
+msgid "Factory and interfaces for the streaming library"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:322
+msgid "Standard I2P classes, data structures, API, and utilities"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:325
+msgid ""
+"You can fetch these from an I2P installation, or add the following "
+"dependencies\n"
+"from Maven Central:"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:334
+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:339
+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:370
+msgid "Code example 1: initializing the server application."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:372
+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:456
+msgid "Code example 2: accepting connections from clients and handling messages."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:460
+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:474
+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:478
+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:562
+msgid ""
+"Code example 3: starting the client and connecting it to the server "
+"application."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:564
+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 <a href=\"#start.streaming.destination\">above</a>).\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:570
+msgid "Congratulations, you have successfully communicated over I2P!"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:574
+msgid "Existing Applications"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:575
+msgid "Contact us if you would like to contribute."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:596
+msgid "Application Ideas"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:598
+msgid "NNTP server - there have been some in the past, none at the moment"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:601
+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:604
+msgid "PGP Key server and/or proxy"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:607
+msgid ""
+"Content Distribution / DHT applications - resurrect feedspace,\n"
+"port dijjer, look for alternatives"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:611
+msgid "Help out with <a href=\"http://syndie.i2p2.de/\">Syndie</a> development"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/applications.html:614
+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:619
+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 ""
+"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:8
+msgid ""
+"<a href=\"#commit\">Commit Keys</a> to sign changes checked-in to the "
+"respository; and"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/developers-keys.html:9
+msgid ""
+"<a href=\"#transport\">Transport Keys</a> to push changes to remote "
+"servers."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/developers-keys.html:12
+#, python-format
+msgid ""
+"Everyone that uses Monotone to checkout the I2P codebase will need to\n"
+"<a href=\"%(monotone)s#obtaining-and-deploying-developers-"
+"keys\">import</a> the\n"
+"developer commit keys, but only Monotone <a "
+"href=\"%(monotone)s#operating-a-monotone-server\">\n"
+"server operators</a> will need to import the <a "
+"href=\"#transport\">transport keys</a>."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/developers-keys.html:19
+msgid "Developer Commit keys"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/developers-keys.html:298
+msgid "Developer Transport Keys"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/developers-keys.html:299
+#, python-format
+msgid ""
+"<b>Note:</b> Transport keys are only needed for setting up a\n"
+"<a href=\"%(monotone)s#operating-a-monotone-server\">Monotone server</a>."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/license-agreements.html:2
+msgid "License Agreements"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/license-agreements.html:5
+#, python-format
+msgid "For more information see <a href=\"%(licenses)s\">the licenses page</a>."
+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 ""
+
+#: i2p2www/pages/site/get-involved/develop/licenses.html:2
+msgid "I2P Software Licenses"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/licenses.html:4
+#, python-format
+msgid ""
+"As required by our\n"
+"<a href=\"%(threatmodel)s\">threat model</a> (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:15
+msgid ""
+"While the information below may be more confusing than just simply \n"
+"stating \"I2P is BSD\", \"I2P is GPL\", or \"I2P is public domain\",\n"
+"the short answer to the question \"How is I2P licensed?\" is this:"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/licenses.html:21
+msgid "All software bundled in the I2P distributions will allow:"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/licenses.html:23
+msgid "use without fee"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/licenses.html:24
+msgid ""
+"use with no restrictions on how, when, where, why, or by whom is running "
+"it"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/licenses.html:25
+msgid "access to the source code without fee"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/licenses.html:26
+msgid "modifications to the source"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/licenses.html:29
+msgid ""
+"Most of the software guarantees much more - the ability of <b>anyone</b> "
+"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:42
+msgid "Component licenses"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/licenses.html:43
+msgid ""
+"The I2P distribution contains several resources, reflecting the "
+"partitioning of \n"
+"the source code into components.  Each component has its own license, "
+"which all \n"
+"developers who contribute to it agree to - either by explicitly declaring"
+" the release\n"
+"of code committed under a license compatible with that component, or by "
+"implicitly\n"
+"releasing the code committed under the component's primary license.  Each"
+" of these \n"
+"components has a lead developer who has the final say as to what license "
+"is compatible\n"
+"with the component's primary license, and the I2P project manager has the"
+" final say as\n"
+"to what licenses meet the above four guarantees for inclusion in the I2P "
+"distribution."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/licenses.html:56
+msgid "Component"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/licenses.html:57
+msgid "Source path"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/licenses.html:58
+msgid "Resource"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/licenses.html:59
+msgid "Primary license"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/licenses.html:60
+msgid "Alternate licenses"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/licenses.html:61
+msgid "Lead developer"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/licenses.html:275
+msgid "GPL + java exception"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/licenses.html:276
+#, python-format
+msgid ""
+"While it may be redundant, just for clarity the\n"
+"<a href=\"%(gpl)s\">GPL</a>'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:292
+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:300
+msgid "Website content"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/licenses.html:308
+msgid "Commit privileges"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/licenses.html:309
+#, 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 <a href=\"%(monotone)s\">Monotone Page</a> for details."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/licenses.html:315
+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:322
+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:326
+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:330
+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:336
+#, 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"
+"<a href=\"%(licenseagreements)s\">See developers' license agreements</a>."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/press-key.html:2
+msgid "Press GPG Key"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/press-key.html:4
+msgid "Following is the GPG key for the press _at_ geti2p.net email address:"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/release-signing-key.html:2
+msgid "Release Signing Key"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/release-signing-key.html:4
+msgid "Releases 0.7.6 and later are signed by zzz. His current public key is:"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/release-signing-key.html:190
+msgid "Releases from 0.9.9 could be signed by str4d. His current public key is:"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/release-signing-key.html:563
+msgid "str4d has signed the following releases:"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/release-signing-key.html:571
+msgid "Releases 0.7.6 through 0.9.12 were signed by zzz with the following key:"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/release-signing-key.html:607
+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/security-key.html:2
+msgid "Security GPG Key"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/develop/security-key.html:4
+msgid "Following is the GPG key for the security _at_ geti2p.net email address:"
+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 ""
+
+#: i2p2www/pages/site/get-involved/develop/signed-keys.html:17
+msgid ""
+"<u>Tip:</u> 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 ""
+"<b>Tip:</b> 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 ""
+"<b>Tip:</b> 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 ""
+"<b>Tip:</b> 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 <a "
+"href=\"%(licenseagreements)s\">signed license agreement</a>."
+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:5
+#, python-format
+msgid "Read the <a href=\"%(newdevs)s\">new developers guide</a> first."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:9
+msgid "Basic Guidelines and Coding Style"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:11
+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:19
+msgid "Community"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:21
+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:26
+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 "Release Cycle"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:36
+msgid ""
+"Our normal release cycle is 6-10 weeks.\n"
+"Following are the approximate deadlines within a typical 8-week cycle.\n"
+"Actual deadlines for each release are set by the lead developer."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:43
+msgid "1-2 days after previous release: Checkins to trunk are allowed."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:46
+msgid ""
+"2-3 weeks after previous release: Deadline to propagate major changes "
+"from other branches to trunk."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:49
+msgid "4-5 weeks before release: Deadline to request new home page links."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:52
+msgid "3-4 weeks before release: Feature freeze. Deadline for major new features."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:55
+msgid ""
+"2-3 weeks before release: Hold project meeting to review new home page "
+"link requests, if any."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:58
+msgid ""
+"7-10 days before release: String freeze. No more changes to translated "
+"(\"tagged\") strings.\n"
+"Push strings to Transifex, announce translation deadline on Transifex."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:62
+msgid ""
+"7-10 days before release: Feature deadline. Bug fixes only after this "
+"time. No more features, refactoring or cleanup."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:65
+msgid ""
+"3-4 days before release: Translation deadline. Pull translations from "
+"Transifex and check in."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:68
+msgid ""
+"2-3 days before release: Checkin deadline. No checkins after this time "
+"without the permission of the release builder."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:71
+msgid "Hours before release: Code review deadline."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:80
+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:87
+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:96
+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:101
+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:105
+msgid ""
+"Ensure that you 'mtn pull' and 'mtn update' to the latest revision before"
+" you check in and push.\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:113
+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:120
+msgid "Coding Style"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:122
+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:129
+msgid ""
+"All new public and package-private classes and methods require Javadocs. "
+"Add @since release-number.\n"
+"Javadocs for new private methods are desirable."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:133
+msgid ""
+"For any Javadocs added, there must not be any doclint errors or warnings."
+"\n"
+"Run 'ant javadoc' with Oracle Java 8 or higher to check.\n"
+"All params must have @param lines, all non-void methods must have @return"
+" lines,\n"
+"all exceptions declared thrown must have @throws lines, and no HTML "
+"errors."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:139
+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:147
+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:153
+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:156
+msgid ""
+"Be familiar with common Java pitfalls that are caught by findbugs.\n"
+"Run 'ant findbugs' to learn more."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:160
+msgid ""
+"We require Java 7 to build and run I2P.\n"
+"Do not use Java 8 classes or methods anywhere.\n"
+"Do not use Java 7 or 8 classes or methods in embedded subsystems (core, "
+"router, mstreaming, streaming, i2ptunnel),\n"
+"as Android and embedded applications require only Java 6. All classes "
+"must be available in Android API 9.\n"
+"Java 7 language features are acceptable in these subsystems if supported "
+"by the current version\n"
+"of the Android SDK and they compile to Java 6-compatible code."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:168
+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:172
+msgid "Don't use URL. Use URI."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:175
+msgid ""
+"Don't catch Exception. Catch RuntimeException and checked exceptions "
+"individually."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:178
+msgid ""
+"Don't use String.getBytes() without a UTF-8 charset argument. You may "
+"also use DataHelper.getUTF8() or DataHelper.getASCII()."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:181
+msgid ""
+"Always specify a UTF-8 charset when reading or writing files. The "
+"DataHelper utilities may be helpful."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:184
+msgid ""
+"Always specify a locale (for example Locale.US) when using "
+"String.toLowerCase() or String.toUpperCase().\n"
+"Do not use String.equalsIgnoreCase(), as a locale cannot be specified."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:188
+msgid "Don't use String.split(). Use DataHelper.split()."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:191
+msgid "Ensure that InputStreams and OutputStreams are closed in finally blocks."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:194
+msgid ""
+"Use {} for all for and while blocks, even if only one line.\n"
+"If you use {} for either the if, else, or if-else block, use it for all "
+"blocks.\n"
+"Put \"} else {\" on a single line."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:199
+msgid "Specify fields as final wherever possible."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:202
+msgid ""
+"Don't store I2PAppContext, RouterContext, Log, or any other references to"
+" router or context items in static fields."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:205
+msgid "Don't start threads in constructors. Use I2PAppThread instead of Thread."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:210
+msgid "Licenses"
+msgstr "Lisenziyalar"
+
+#: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:212
+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:219
+msgid ""
+"If you do obtain approval to add external code or jars,\n"
+"and binaries are available in any Debian or Ubuntu package,\n"
+"you must implement build and packaging options to use the external "
+"package instead.\n"
+"Checklist of files to modify:"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:227
+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:234
+msgid "Bugs"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:236
+#, 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:241
+msgid ""
+"New developers should start by fixing a bug.\n"
+"Search for bugs with the 'easy' keyword on trac.\n"
+"When you have a fix, attach your patch to the ticket and add the keyword "
+"'review-needed'.\n"
+"Do not close the ticket until it's been successfully reviewed and you've "
+"checked your changes in.\n"
+"Once you've done this smoothly for a couple of tickets, you may follow "
+"the normal procedure below."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:248
+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 "I2P ilə bir IDE istifadə etmək "
+
+#: i2p2www/pages/site/get-involved/guides/ides.html:4
+msgid ""
+"The main I2P development branch (<code>i2p.i2p</code>) 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 (<code>i2p.i2p</code> and branches from"
+" it) contain build.gradle to enable the branch to be easily set up in "
+"Eclipse."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/ides.html:16
+msgid ""
+"Make sure you have a recent version of Eclipse.  Anything newer than 2017"
+" should do."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/ides.html:20
+msgid ""
+"Check out the I2P branch into some directory (e.g. "
+"<code>$HOME/dev/i2p.i2p</code>)."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/ides.html:24
+msgid ""
+"Select \"File - Import...\" and then under \"Gradle\" select \"Existing "
+"Gradle Project\"."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/ides.html:28
+msgid ""
+"For \"Project root directory:\" choose the directory that the I2P branch "
+"was checked out to."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/ides.html:32
+msgid ""
+"In the \"Import Options\" dialog, select \"Gradle Wrapper\" and press "
+"continue."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/ides.html:36
+msgid ""
+"In the \"Import Preview\" dialog you can review the project structure.  "
+"Multiple projects should appear under \"i2p.i2p\".  Press \"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 (<code>i2p.i2p</code> and branches from"
+" it) contain NetBeans project files."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:2
+msgid "Monotone Guide"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:6
+msgid "Operating a Monotone client"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:8
+#: i2p2www/pages/site/get-involved/guides/monotone.html:61
+msgid "Generating Monotone keys"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:9
+msgid "Trust and initializing your repository"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:10
+#: i2p2www/pages/site/get-involved/guides/monotone.html:194
+msgid "Obtaining and deploying developers' keys"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:11
+#: i2p2www/pages/site/get-involved/guides/monotone.html:225
+msgid "Setting up trust evaluation hooks"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:12
+#: i2p2www/pages/site/get-involved/guides/monotone.html:266
+msgid ""
+"Pulling the <code>i2p.i2p</code>, <code>i2p.www</code> and "
+"<code>i2p.syndie</code> branches"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:13
+#: i2p2www/pages/site/get-involved/guides/monotone.html:312
+msgid "Verifying that trust evaluation works"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:14
+#: i2p2www/pages/site/get-involved/guides/monotone.html:361
+msgid "Checking out a working copy of the latest version"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:15
+#: i2p2www/pages/site/get-involved/guides/monotone.html:388
+msgid "Updating your working copy to the latest version"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:19
+#: i2p2www/pages/site/get-involved/guides/monotone.html:418
+msgid "Operating a Monotone Server"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:21
+msgid "Obtaining and deploying developers’ transport keys"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:22
+#: i2p2www/pages/site/get-involved/guides/monotone.html:428
+msgid "Granting push and pull access"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:23
+#: i2p2www/pages/site/get-involved/guides/monotone.html:473
+msgid "Running Monotone in server mode"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:24
+#: i2p2www/pages/site/get-involved/guides/monotone.html:498
+msgid "Differences under Debian GNU/Linux"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:32
+#, python-format
+msgid ""
+"This is a revised version of <a "
+"href=\"%(transitionguide)s\">Complication's original\n"
+"  guide</a> detailing the use of Monotone in I2P development.\n"
+"  For basic instructions see the <a href=\"%(newdevs)s\">quick-start "
+"guide</a>."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:40
+#, python-format
+msgid ""
+"I2P has a distributed development model. The source code is replicated "
+"across\n"
+"  independently administered <a "
+"href=\"http://www.monotone.ca/\">Monotone</a> (\"MTN\") repositories.\n"
+"  Developers with commit rights are able to push their changes to the "
+"repository\n"
+"  (a <a href=\"%(licenses)s#commit\">license agreement</a> needs to be "
+"signed\n"
+"  before commit rights are granted)."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:50
+msgid ""
+"Some of Monotone's noteworthy qualities are: distributed\n"
+"  version control, cryptographic authentication, access control, its "
+"small size, having few\n"
+"  dependencies, storage of projects in a compressed SQLite database file,"
+" and\n"
+"  having the ability to resume interrupted synchronization attempts."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:59
+msgid "Operating a Monotone Client"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:64
+msgid ""
+"A transport key grants you the ability to push your changes to a Monotone"
+" repository server.\n"
+"  In order to commit code into Monotone (in essence signing your code), a"
+" commit key is also needed.\n"
+"  None of the public Monotone servers on I2P currently require a key in "
+"order to read (or pull) the source code."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:72
+msgid ""
+"Without a transport key, one cannot:\n"
+"  <ul>\n"
+"    <li>pull code from a server which doesn't allow global read "
+"access</li>\n"
+"    <li>push code to any server</li>\n"
+"    <li>run a Monotone server</li>\n"
+"  </ul>"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:83
+msgid ""
+"Without a commit key, one cannot:\n"
+"  <ul>\n"
+"    <li>commit any code</li>\n"
+"  </ul>"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:92
+msgid ""
+"If you only intend to retrieve code from MTN, feel free to skip to the\n"
+"  <a href=\"#trust-and-initializing-your-repository\">next section</a>. "
+"If you want\n"
+"  to generate keys, read the following."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:100
+msgid ""
+"By convention keys are named like an e-mail addresses, but a "
+"corresponding e-mail\n"
+"  address does not need to exist. For example, your keys might be named:"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:111
+msgid ""
+"Monotone stores keys under <code><b>$HOME/.monotone/keys</b></code> in "
+"text files which\n"
+"  are named identically to the keys. For example:"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:121
+msgid ""
+"To generate transport and commit keys, enter the following commands at a "
+"prompt:"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:131
+msgid ""
+"Monotone will prompt you for a password to protect your keys. You are "
+"very strongly encouraged to set a password\n"
+"  for the commit key. Many users will leave an empty password for the "
+"transport key, especially those running a\n"
+"  Monotone server."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:139
+msgid "Trust, and initializing your repository"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:143
+msgid ""
+"Monotone's security model helps to ensure that nobody can easily "
+"impersonate a developer without\n"
+"  it being noticed. Since developers can make mistakes and become "
+"compromised,only manual review can\n"
+"  ensure quality of code. Monotone's trust model will ensure that you "
+"read the right diffs. It does\n"
+"  not replace reading diffs."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:153
+msgid ""
+"A Monotone repository is a single file (a compressed SQLite database) "
+"which contains all of the project's source code and history."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:159
+msgid ""
+"After <a href=\"#obtaining-and-deploying-developers-keys\">importing the "
+"developers' keys into Monotone</a> and\n"
+"  <a href=\"#setting-up-trust-evaluation-hooks\">setting up trust "
+"evaluation hooks</a>,\n"
+"  Monotone will prevent untrusted code from being checked out into your "
+"workspace.\n"
+"  There are commands available to clean untrusted code from your "
+"workspace but in practice they've not been\n"
+"  needed due to the push access policies in place."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:169
+msgid ""
+"A repository can hold many branches. For example, our repository holds "
+"the\n"
+"  following main branches:"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:174
+msgid "The I2P router and associated programs"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:175
+msgid "The I2P project website"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:176
+msgid "Syndie, a distributed forums tool"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:181
+msgid ""
+"By convention, the I2P Monotone repository is named <code>i2p.mtn</code>."
+" 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"
+"  <code>i2p.mtn</code> file and branch directories to be stored and issue"
+" the following\n"
+"  command:"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:197
+msgid ""
+"Keys which developers use to commit code are essential for trust "
+"evaluation in\n"
+"  Monotone. The other developers' transport keys are only required for "
+"Monotone server operators.\n"
+"  "
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:204
+#, python-format
+msgid ""
+"Developers' commit keys are provided GPG-signed <a "
+"href=\"%(signedkeys)s\">on another page</a>."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:210
+#, python-format
+msgid ""
+"To import developers' keys after verifying their authenticity, copy <a "
+"href=\"%(devkeys)s\">all of the keys</a> into a new\n"
+"  file. Create this file (e.g. <code><b>keys.txt</b></code>) in the same "
+"directory where <code>i2p.mtn</code> is located. Import the keys with the"
+" command:"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:220
+msgid ""
+"<b>Note</b>: <i>Never</i> add keys to "
+"<code><b>$HOME/.monotone/keys</b></code> manually."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:228
+msgid ""
+"The default Monotone trust policy is way too lax for our requirements: "
+"every committer is trusted by default.\n"
+"  That is not acceptable for I2P development."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:235
+msgid ""
+"Change into the directory <code><b>$HOME/.monotone</b></code> and open "
+"the file\n"
+"  <code>monotonerc</code> with a text editor. Copy and paste the "
+"following two functions into this file:"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:244
+msgid ""
+"The first function determines an intersection between two sets, in our "
+"case a\n"
+"  revision's signers and trusted signers."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:251
+msgid ""
+"The second function determines trust in a given revision, by calling the "
+"first\n"
+"  function with \"signers\" and \"trusted\" as arguments. If the "
+"intersection is\n"
+"  null, the revision is not trusted. If the intersection is not empty, "
+"the\n"
+"  revision is trusted. Otherwise, the revision is not trusted."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:260
+msgid ""
+"More information about Trust Evaluation Hooks can be found in the <a "
+"href=\"http://www.monotone.ca/docs/Hooks.html\">official Monotone "
+"documentation</a>."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:268
+msgid ""
+"I2P is shipped with a pre-configured tunnel pointing to the project "
+"Monotone server. Ensure that the tunnel has been started\n"
+"  within <a href=\"http://127.0.0.1:7657/i2ptunnel\">I2PTunnel</a> before"
+" attempting to pull the source code from 127.0.0.1:8998."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:275
+msgid ""
+"Enter the directory where you initialized <code>i2p.mtn</code>. Depending"
+" on whether you\n"
+"  want only I2P sources, or also sources for the I2P website and Syndie, "
+"you can\n"
+"  perform the <code>pull</code> operation in different ways."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:283
+msgid "If you only want I2P sources:"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:292
+msgid "If you want all branches:"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:298
+msgid ""
+"If the transfer aborts before completing sucessfully, simply repeating "
+"the pull command will resume the transfer."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:304
+msgid ""
+"Pulling in the above examples is done anonymously by specifying an empty "
+"transport key.\n"
+"  If everyone pulls anonymously it will be harder for an attacker who "
+"gains control of the server\n"
+"  to selectively provide some people with tampered data."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:315
+msgid "To verify that trust evaluation works:"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:319
+msgid "Make a backup of your <code>monotonerc</code> file."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:320
+msgid ""
+"Modify <code><b>monotonerc</b></code> by setting the trusted_signers "
+"variable in the following way:"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:326
+msgid ""
+"With <code><b>monotonerc</b></code> configured as above, Monotone will no"
+" longer trust any committers. Confirm this by changing into the\n"
+"directory where <code>i2p.mtn</code> was created and attempt a checkout "
+"of the I2P branch:"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:336
+msgid ""
+"A directory named <code>i2p.i2p</code> should <b>not</b> appear. You "
+"should encounter many\n"
+"  error messages like:"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:353
+msgid ""
+"If you are satisfied with results, restore the backup of\n"
+"  <code>monotonerc</code> that was created above. If you didn't create a "
+"backup\n"
+"  as advised, re-read <a href=\"#setting-up-trust-evaluation-"
+"hooks\">Setting up trust evaluation hooks</a>."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:364
+msgid ""
+"If you already have a branch checked out, skip to the <a href"
+"=\"#updating-your-working-copy-to-the-latest-version\">next\n"
+"  section</a>."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:371
+msgid ""
+"Change into the directory where <code>i2p.mtn</code> is located. Over "
+"there issue:"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:380
+msgid ""
+"The checkout should complete without error messages and a directory named"
+"\n"
+"  <code>i2p.i2p</code> should appear in the current directory. "
+"Congratulations! You have\n"
+"  successfully checked out the latest I2P sources, ready to be compiled."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:391
+msgid ""
+"If you haven't done this already, pull fresh code from the server to your"
+" local\n"
+"  Monotone repository. To accomplish this, change into the directory "
+"where\n"
+"  <code>i2p.mtn</code> is located and issue:"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:402
+msgid "Now change into your <code>i2p.i2p</code> directory, and over there issue:"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:411
+msgid ""
+"As long as there were no errors&hellip;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:420
+msgid "Obtaining and deploying developers' transport keys"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:423
+msgid ""
+"As a server operator you may want to grant push access to certain "
+"developers."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:431
+msgid "By default the Monotone server denies all access."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:437
+msgid "To grant pull access to all clients, set the following in"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:449
+msgid ""
+"No one will not be able to push code to your server without permission "
+"being explicitly granted. To grant push access:"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:455
+msgid ""
+"Add the name of the user's transport key to\n"
+"<code>$HOME/.monotone/write-permissions</code>, such as\n"
+"<code><pre>\n"
+"    zzz-transport@mail.i2p\n"
+"    complication-transport@mail.i2p\n"
+"</pre></code>\n"
+"with one key per line."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:466
+msgid ""
+"Import the transport key(s) into your database. The procedure for "
+"importing transport keys is the same as for\n"
+"importing commit keys, which is described in the section <a href"
+"=\"#obtaining-and-deploying-developers-keys\">Obtaining and deploying "
+"developers' keys</a>."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:476
+msgid ""
+"A separate database should be used for your Monotone server because "
+"monotone will lock the database while it is served to others.\n"
+"  Make a copy of your development database, then start the server with:"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:483
+msgid ""
+"If your key is protected with a passphrase, Monotone may request the "
+"passphrase\n"
+"  when the first client connects. You can work around this by connecting "
+"making the first client connection to your server\n"
+"  (or by clearing the password for your transport key)."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:491
+msgid ""
+"For your server to be accessible for others over I2P, you will need to "
+"create a\n"
+"  server tunnel for it. Use the \"Standard\" tunnel type and \"Bulk\" "
+"profile."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:501
+msgid ""
+"Debian (amongst other distributions) has integrated Monotone into their\n"
+"  framework of daemons/services. Although Monotone servers can still be "
+"run\n"
+"  \"the ordinary way\" on Debian systems, doing it the \"Debian way\" may"
+" be more straightforward."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/monotone.html:509
+msgid ""
+"Permissions are granted by editing the files\n"
+"  <code>/etc/monotone/read-permissions</code> and\n"
+"  <code>/etc/monotone/write-permissions</code>. You'll also need to edit\n"
+"  <code>/etc/default/monotone</code> 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:3
+msgid "July 2018"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-developers.html:6
+#: i2p2www/pages/site/get-involved/guides/new-developers.html:32
+msgid "Basic study"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-developers.html:7
+#: i2p2www/pages/site/get-involved/guides/new-developers.html:46
+msgid "Getting the I2P code"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-developers.html:9
+#: i2p2www/pages/site/get-involved/guides/new-developers.html:53
+msgid "The easy way: Git"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-developers.html:10
+#: i2p2www/pages/site/get-involved/guides/new-developers.html:73
+msgid "The proper way: Monotone"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-developers.html:12
+#: i2p2www/pages/site/get-involved/guides/new-developers.html:136
+msgid "Building I2P"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-developers.html:13
+#: i2p2www/pages/site/get-involved/guides/new-developers.html:157
+msgid "Development ideas"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-developers.html:14
+#: i2p2www/pages/site/get-involved/guides/new-developers.html:165
+msgid "Making the results available"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-developers.html:15
+#: i2p2www/pages/site/get-involved/guides/new-developers.html:186
+msgid "Get to know us!"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-developers.html:16
+#: i2p2www/pages/site/get-involved/guides/new-developers.html:192
+msgid "Translations"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-developers.html:17
+#: i2p2www/pages/site/get-involved/guides/new-developers.html:198
+msgid "Tools"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-developers.html:22
+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:27
+#, python-format
+msgid ""
+"\n"
+"Not quite ready for coding?\n"
+"Try <a href=\"%(volunteer)s\">getting involved</a> first."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-developers.html:34
+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 <a "
+"href=\"http://www.mindview.net/Books/TIJ/\">Thinking in Java</a>."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-developers.html:38
+#, python-format
+msgid ""
+"Study the <a href=\"%(intro)s\">how intro</a>,\n"
+"the <a href=\"%(docs)s\">other \"how\" documents</a>,\n"
+"the <a href=\"%(techintro)s\">tech intro</a>,\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:48
+msgid ""
+"For development on the I2P router or the embedded applications,\n"
+"there are two ways to get the source code:"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-developers.html:55
+#, python-format
+msgid "Install <a href=\"%(git_url)s\">Git</a>."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-developers.html:58
+#, python-format
+msgid "Get the code from <a href=\"%(i2p_git)s\">the GitHub mirror</a>:"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-developers.html:65
+#: i2p2www/pages/site/get-involved/guides/new-developers.html:120
+msgid "Remarks"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-developers.html:66
+#, python-format
+msgid ""
+"The Git repository is currently a read-only mirror. If you wish to use it"
+" for\n"
+"development, you will need to submit patches to <a href=\"%(trac)s\">our "
+"issue\n"
+"tracker</a>. We can accept GitHub pull requests, but they must be "
+"processed\n"
+"manually by turning them into patches anyway."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-developers.html:75
+msgid ""
+"Install <a href=\"http://www.monotone.ca/\">monotone</a>.\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:80
+msgid ""
+"Skim over the <a "
+"href=\"http://www.monotone.ca/docs/Tutorial.html\">monotone tutorial</a>,"
+" to make sure you understand the concepts."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-developers.html:84
+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:87
+#, python-format
+msgid ""
+"Enable the <a href=\"%(i2ptunnel)s\">i2ptunnel</a> client tunnel on port "
+"8998 pointing to mtn.i2p-projekt.i2p."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-developers.html:91
+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:94
+msgid ""
+"Define the trust list by creating <code>~/.monotone/monotonerc</code> (or"
+" <code>_MTN/monotonerc</code> in the i2p.i2p workspace) with the "
+"following contents:"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-developers.html:99
+#, python-format
+msgid ""
+"Copy and paste the <a href=\"%(devkeys)s\">developer's commit keys</a> "
+"into a new file (e.g. <code>keys.txt</code>) in the same directory\n"
+"  that <code>i2p.mtn</code> is in. Import the keys into your database "
+"with <br><code><pre>      mtn -d i2p.mtn read < keys.txt</pre></code>"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-developers.html:103
+msgid ""
+"Pull the I2P sources to your machine. This may take a long time, "
+"especially if you are doing this over I2P!"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-developers.html:105
+msgid "Anonymously:"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-developers.html:108
+msgid "Non-anonymously:"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-developers.html:114
+msgid ""
+"All the sources are now present on your machine, in the database file. To"
+" make them available in a directory, you need to check them out:"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-developers.html:116
+msgid ""
+"The above command creates a directory i2p.i2p, which contains all of the "
+"I2P sources."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-developers.html:121
+msgid ""
+"\n"
+"To download the website files instead of the I2P source files, use "
+"'i2p.www' instead of 'i2p.i2p'."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-developers.html:124
+msgid ""
+"The initial pull may take several hours using the tunnel.\n"
+"If it fails after a partial pull, simply rerun it, it will start where it"
+" left off.\n"
+"If you are in a hurry, use the non-anonymous access."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-developers.html:129
+#, python-format
+msgid ""
+"A full list of branches, including i2p.i2p and i2p.www can be found on <a"
+" href=\"%(viewmtn)s\">viewmtn</a>."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-developers.html:132
+#, python-format
+msgid ""
+"A long explanation about using monotone is available on the <a "
+"href=\"%(monotone)s\">monotone page</a>."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-developers.html:138
+#, python-format
+msgid ""
+"To compile the code, you need the Sun Java Development Kit 6 or higher, "
+"or equivalent JDK\n"
+"(<a href=\"%(sunjdk6)s\">Sun JDK 6</a> strongly recommended) and\n"
+"<a href=\"http://ant.apache.org/\">Apache ant</a>\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:146
+msgid ""
+"To build or work on console translations, you need\n"
+"the xgettext, msgfmt, and msgmerge tools from the\n"
+"<a href=\"http://www.gnu.org/software/gettext/\">GNU gettext package</a>."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-developers.html:152
+#, python-format
+msgid ""
+"For development on new applications,\n"
+"see the <a href=\"%(apps)s\">application development guide</a>."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-developers.html:158
+#, python-format
+msgid ""
+"See <a href=\"http://%(zzz)s/forums/3\">zzz's TODO lists</a>,\n"
+"<a href=\"%(todo)s\">this website's TODO list</a> or\n"
+"<a href=\"%(trac)s\">Trac</a>\n"
+"for ideas."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-developers.html:167
+#, python-format
+msgid ""
+"See the bottom of <a href=\"%(licenses)s#commit\">the licenses page</a> "
+"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:172
+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:174
+msgid "use an empty passphrase"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-developers.html:175
+msgid "enter a passphrase"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-developers.html:176
+#, python-format
+msgid ""
+"<a href=\"mailto:%(email)s\">send</a> this to a mtn repo operator to get "
+"push privileges"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-developers.html:177
+#, python-format
+msgid ""
+"send this to <a href=\"mailto:%(email)s\">a release manager</a> to get "
+"commit privileges - not required for website"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-developers.html:178
+msgid "check in with this key"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-developers.html:179
+msgid "push with this key"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-developers.html:181
+#, python-format
+msgid "Long version: see the <a href=\"%(monotone)s\">monotone page</a>."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-developers.html:187
+#, 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 <a href=\"%(guidelines)s\">additional guidelines for regular"
+" developers</a>."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-developers.html:193
+#, python-format
+msgid ""
+"Website and router console translators: See the <a "
+"href=\"%(newtrans)s\">New Translator's Guide</a>\n"
+"for next steps."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-developers.html:199
+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:207
+#, 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"
+"<a href=\"%(java)s\">YourKit Java Profiler</a> and\n"
+"<a href=\"%(dotnet)s\">YourKit .NET Profiler</a>."
+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"
+"<a href=\"%(transifex)s\">Transifex</a> 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 <a href=\"%(url)s\">this wiki "
+"page</a>."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-translators.html:25
+#, python-format
+msgid ""
+"Follow the <a href=\"%(newdevs)s\">new developer's guide</a>,\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 ""
+"<b>Create files:</b>\n"
+"If the file for your language does not exist yet:"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-translators.html:38
+msgid ""
+"Run \"<code>./extract-messages.sh</code>\" to generate a "
+"<code>messages.pot</code> in the base directory.\n"
+"Edit the header of this file, then run \"<code>./init-new-po.sh "
+"locale</code>\" to generate the file\n"
+"<code>i2p2www/translations/locale/LC_MESSAGES/messages.po</code>. "
+"\"<code>mtn add</code>\" this file."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-translators.html:43
+msgid ""
+"Edit <code>i2p2www/pages/global/lang.html</code> 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 <code>i2p2www/static/images/flags/</code> for "
+"the menu (copy from the router)."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-translators.html:52
+msgid ""
+"<b>Edit files:</b>\n"
+"Edit <code>i2p2www/translations/locale/LC_MESSAGES/messages.po</code>.\n"
+"To work with .po files efficiently, you may wish to use <a "
+"href=\"http://www.poedit.net/download.php\">POEdit</a>"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-translators.html:58
+#: i2p2www/pages/site/get-involved/guides/new-translators.html:151
+msgid ""
+"<b>Check in:</b>\n"
+"\"<code>mtn pull</code>\", \"<code>mtn update</code>\". Then check in by "
+"\"<code>mtn ci -k yourname@mail.i2p file1 file2 ...</code>\"\n"
+"This collects the diff info of your changed file into your local repo. "
+"Then \"<code>mtn sync mtn.i2p2.de -k yourname-transport@mail.i2p "
+"i2p.i2p</code>\".\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"
+"<a href=\"%(transifex)s\">Transifex</a> 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 <a href=\"%(newdevs)s\">new developer's guide</a>,\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 ""
+"<b>What to translate:</b>\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 ""
+"<b>Create files:</b>\n"
+"If the file for your language does not exist yet, copy another language "
+"file to a new file <code>foo_xx.bar</code> for your language.\n"
+"Then \"<code>mtn add</code>\" the file.\n"
+"After creating a .po file, edit the headers. Then run \"<code>ant "
+"distclean poupdate</code>\"."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-translators.html:144
+msgid ""
+"<b>Start to work:</b>\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 <a "
+"href=\"http://www.poedit.net/download.php\">POEdit</a>"
+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 <code>#i2p-dev</code> on IRC."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/new-translators.html:169
+msgid "FAQ"
+msgstr "FAQ"
+
+#: i2p2www/pages/site/get-involved/guides/new-translators.html:171
+msgid ""
+"Q: Why do I have to install monotone, Java, jsp, learn about .po files "
+"and html, etc.? Why can't I just do a translation and email it to you?"
+msgstr ""
+
+#: 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 <a href=\"%(transifex)s\">here</a>."
+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 <i>before</i> 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 ""
+"<b>In summary:</b>\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 <a "
+"href=\"http://%(zzz)s/forums/14\">translation forum on %(zzz)s</a>."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/reseed.html:2
+msgid "How to Set up a Reseed Server"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/reseed.html:3
+msgid "February 2017"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/reseed.html:6
+msgid "Overview"
+msgstr "İcmal"
+
+#: i2p2www/pages/site/get-involved/guides/reseed.html:8
+msgid ""
+"Thank you for volunteering to run an I2P reseed server.\n"
+"\"Reseeding\" is our term for bootstrapping new routers into the network."
+"\n"
+"New routers fetch a bundle of peer references, or \"router infos\", from "
+"one or more of a hardcoded list of HTTPS URLs."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/reseed.html:14
+msgid "Requirements"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/reseed.html:16
+msgid ""
+"At its simplest, a reseed server consists of a Java I2P router, an HTTPS "
+"web server,\n"
+"and some scripts that periodically gather router infos from the router,\n"
+"bundle and sign them into a custom file format, and deliver these files "
+"over HTTPS.\n"
+"In practice, it's a bit more complex, and a reseed operator must be "
+"fairly competent and attentive.\n"
+"A reseed server is not appropriate for a residential internet connection."
+" The complexities include:"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/reseed.html:25
+msgid ""
+"You must have a secure SSL setup with either a self-signed certificate or"
+" a cert that chains up to a standard CA"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/reseed.html:28
+msgid ""
+"The SSL configuration must conform to current best practices on allowed "
+"ciphers and protocols, and the CN/SAN host name must match the URL"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/reseed.html:31
+msgid ""
+"The scripts are designed to deliver different router info bundles to "
+"different requestors for network diversity"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/reseed.html:34
+msgid ""
+"The scripts are designed to deliver the same bundle to the same repeated "
+"requestor to prevent scraping"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/reseed.html:37
+msgid ""
+"The reseed servers are under periodic attacks and DDoS attempts, and from"
+" other buggy I2P implementations and botnets.\n"
+"This necessitates that you run fail2ban or an equivalent solution."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/reseed.html:43
+msgid "Information Required"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/reseed.html:45
+msgid ""
+"When your setup is complete and ready for testing, we will need the HTTPS"
+" URL,\n"
+"the SSL public key certificate, and the \"su3\" bundle public key.\n"
+"After testing is complete, these will be added to the hardcoded entries "
+"in the Java and C++ routers in the next release,\n"
+"and you will start seeing traffic.\n"
+"We also will need your email address so we may continue to contact you "
+"about reseed administration issues.\n"
+"The email will not be made public but will be known to the other reseed "
+"operators.\n"
+"You should expect that your nick or name and its association with that "
+"URL or IP will become public."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/reseed.html:55
+msgid "Privacy Policy"
+msgstr "Təhlükəsizlik qaydaları"
+
+#: i2p2www/pages/site/get-involved/guides/reseed.html:57
+msgid ""
+"A reseed operator is a trusted role in the network.\n"
+"While we do not yet have a formal privacy policy, you must ensure the "
+"privacy of our users\n"
+"by not publicizing logs or IPs found in those logs, except as necessary "
+"to discuss administration issues with the I2P reseed team."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/reseed.html:63
+msgid "Financial Support"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/reseed.html:65
+msgid ""
+"Modest financial support may be available to those running reseed "
+"servers.\n"
+"This support would be in partial reimbursement for your server costs.\n"
+"Support will not be paid in advance and will probably not cover all your "
+"expenses.\n"
+"Support is only available to those who have been running reseed servers "
+"in good standing for several months, and is based on actual need."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/reseed.html:72
+msgid ""
+"If you would like to discuss support, please contact echelon and CC: "
+"backup."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/reseed.html:77
+msgid "Getting Started"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/reseed.html:79
+msgid ""
+"Our reseed coordinator is \"backup\" and he may be contacted at backup at"
+" mail.i2p or backup at i2pmail.org.\n"
+"Unfortunately, he is not generally on IRC. The reseed setup is somewhat "
+"specialized, and you should direct most questions to him."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/reseed.html:84
+msgid ""
+"For actual implementation, details below. We have one recommended reseed "
+"solution:"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/reseed.html:89
+msgid ""
+"A Go implementation that includes the web server and all the scripts. "
+"This is the recommended solution."
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/reseed.html:95
+msgid ""
+"For further information, read the information at the following links, and"
+" then contact backup.\n"
+"Thank you!"
+msgstr ""
+
+#: i2p2www/pages/site/get-involved/guides/reseed.html:110
+msgid "Detailed Instructions"
+msgstr ""
+
diff --git a/i2p2www/translations/az/LC_MESSAGES/priority.po b/i2p2www/translations/az/LC_MESSAGES/priority.po
new file mode 100644
index 00000000..b0183ba1
--- /dev/null
+++ b/i2p2www/translations/az/LC_MESSAGES/priority.po
@@ -0,0 +1,2765 @@
+# Azerbaijani translations for I2P.
+# Copyright (C) 2018 ORGANIZATION
+# This file is distributed under the same license as the I2P project.
+#
+# Translators:
+# Nikafn <appone6@gmail.com>, 2018
+msgid ""
+msgstr ""
+"Project-Id-Version:  I2P\n"
+"Report-Msgid-Bugs-To: http://trac.i2p2.de\n"
+"POT-Creation-Date: 2018-08-24 11:47+0000\n"
+"PO-Revision-Date: 2018-08-24 11:52+0000\n"
+"Last-Translator: zzzi2p\n"
+"Language-Team: Azerbaijani "
+"(http://www.transifex.com/otf/I2P/language/az/)\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 1.3\n"
+
+#: i2p2www/pages/blog/category.html:2
+msgid "Blog Category"
+msgstr "Bloq kateqoriyası"
+
+#: i2p2www/pages/blog/category.html:4
+#, python-format
+msgid "I2P Blog ATOM Feed for Category: %(category)s"
+msgstr "Kateqoriyanın I2P Blog ATOM Axını: %(category)s"
+
+#: i2p2www/pages/blog/index.html:2 i2p2www/pages/blog/post.html:3
+#: i2p2www/pages/global/nav.html:78
+msgid "Blog"
+msgstr "Bloq"
+
+#: i2p2www/pages/blog/index.html:4 i2p2www/pages/site/index.html:80
+msgid "I2P Blog ATOM Feed"
+msgstr "I2P Blog ATOM Axını"
+
+#: i2p2www/pages/blog/index.html:18
+#, python-format
+msgid "Posted %(date)s by %(author)s"
+msgstr "%(date)s tarixində %(author)s tərəfindən göndərildi"
+
+#: i2p2www/pages/blog/latest.html:5
+msgid "More blog posts&hellip;"
+msgstr "Daha çox bloq yazıları&hellip;"
+
+#: i2p2www/pages/blog/post.html:12
+msgid "Posted:"
+msgstr "Göndərilmə:"
+
+#: i2p2www/pages/blog/post.html:13
+msgid "Author:"
+msgstr "Müəllif:"
+
+#: i2p2www/pages/downloads/debian.html:4
+msgid "Debian I2P Packages"
+msgstr "Debian I2P Paketləri"
+
+#: i2p2www/pages/downloads/debian.html:6
+msgid "Debian Sid, Ubuntu Bionic 18.04"
+msgstr ""
+
+#: i2p2www/pages/downloads/debian.html:7
+msgid ""
+"I2P is available in the official repositories for Ubuntu Bionic 18.04 and"
+" Debian Sid.\n"
+"Install the \"i2p\" package using your package manager, as you would any "
+"other package.  The instructions below are not required."
+msgstr ""
+
+#: i2p2www/pages/downloads/debian.html:12
+msgid "Debian Stretch and older, Ubuntu Artful 17.10 and older"
+msgstr ""
+
+#: i2p2www/pages/downloads/debian.html:13
+msgid ""
+"The Debian packages\n"
+"have been tested and <em>should </em>work on x86/x86_64 platforms running:"
+msgstr ""
+"Debian paketləri\n"
+"sınaqdan keçirildi və <em>bunu işlədən</em> x86/x86_64 platformlarında "
+"çalışmalıdır:"
+
+#: i2p2www/pages/downloads/debian.html:18
+msgid "<a href=\"#ubuntu\">Ubuntu</a> (Precise <em>12.04</em> and newer)"
+msgstr "<a href=\"#ubuntu\">Ubuntu</a> (Dəqiq<em> 12.04 </em>və yeni)"
+
+#: i2p2www/pages/downloads/debian.html:20
+msgid "<a href=\"#debian\">Debian Linux</a> (Wheezy and newer)"
+msgstr "<a href=\"#debian\">Debian Linux</a>(Wheezy və yeni)"
+
+#: i2p2www/pages/downloads/debian.html:24
+#, python-format
+msgid ""
+"The I2P packages <em>may</em> work on systems not listed above. Please "
+"report any issues\n"
+"with these packages on <a href=\"%(trac)s\">Trac</a> at\n"
+"<a href=\"%(trac)s\">https://trac.i2p2.de</a>."
+msgstr ""
+"I2P paketləri yuxarıda göstərilməyən sistemlər üzərində də <em>çalışa "
+"bilər</em>. Lütfən, bu paketlər ilə əlaqədar məsələləri <a "
+"href=\"%(trac)s\">Trac</a> saytına \n"
+"<a href=\"%(trac)s\">https://trac.i2p2.de</a> bildirin."
+
+#: i2p2www/pages/downloads/debian.html:30
+msgid ""
+"Option 1: <a href=\"#ubuntu\">Recent versions</a> of Ubuntu and its "
+"derivatives (<em>Try this if you're not using Debian)</em>"
+msgstr ""
+"1. Seçim: <a href=\"#ubuntu\">Son Ubuntu versiyaları</a> və törəmələri "
+"(<em>Debian-dan istifadə etmirsinzsə, bunu sınayın)</em>"
+
+#: i2p2www/pages/downloads/debian.html:31
+msgid "Option 2: <a href=\"#debian\">Debian</a> (including Debian-derivatives)"
+msgstr "2. Seçim: <a href=\"#debian\">Debian </a>(Debian törəmələri ilə birlikdə)"
+
+#: i2p2www/pages/downloads/debian.html:34
+msgid "Instructions for Ubuntu and derivatives like Linux Mint &amp; Trisquel"
+msgstr ""
+
+#: i2p2www/pages/downloads/debian.html:35
+msgid "Adding the PPA via the command line and installing I2P"
+msgstr "Komanda xəttindən PPA-nı əlavə edin və I2P-ni quraşdırın"
+
+#: i2p2www/pages/downloads/debian.html:38
+msgid "Open a terminal and enter:"
+msgstr "Terminalı açın və daxil edin:"
+
+#: i2p2www/pages/downloads/debian.html:40
+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 ""
+"Bu komanda /etc/apt/sources.list.d-in içinə PPA əlavə edərək, deponun "
+"imzalandığı gpg açarını alır.\n"
+" GPG açarı paketin gəliştirici tərəfindən hazırlandıqdan sonra "
+"dəyişdirilməyəcəyindən əmin \n"
+"olunmasına xidmət edir. "
+
+#: i2p2www/pages/downloads/debian.html:47
+msgid "Notify your package manager of the new PPA by entering:"
+msgstr "Bunu yazaraq paket menecerinizi yeni PPA haqqında məlumatlandırın:"
+
+#: i2p2www/pages/downloads/debian.html:49
+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 ""
+"Bu komanda sisteminiz üçün quraşdırılmış hər bir verilənlər bazasından, "
+"əvvəlki komanda ilə\n"
+" birlikdə əlavə etdiyiniz I2P deposunu da əhatə edən, son versiya "
+"siyahılarını toplayacaq."
+
+#: i2p2www/pages/downloads/debian.html:55
+msgid "You are now ready to install I2P!"
+msgstr "I2P-ni quraşdırmağa hazırsınız!"
+
+#: i2p2www/pages/downloads/debian.html:59
+msgid "Adding the PPA Using Synaptic"
+msgstr "Synaptic-dən istifadə edərək PPA-nın əlavə edilməsi"
+
+#: i2p2www/pages/downloads/debian.html:62
+msgid ""
+"Open Synaptic (System -&gt; Administration -&gt; Synaptic Package "
+"Manager)."
+msgstr ""
+"Synaptic-i açın (Sistem -&gt; Administrasiya -&gt; Synaptic Paket "
+"Meneceri)."
+
+#: i2p2www/pages/downloads/debian.html:67
+msgid ""
+"Once Synaptic opens, select <em>Repositories</em> from the "
+"<em>Settings</em> menu."
+msgstr ""
+"Synaptic açıldığında <em>Tənzimləmələr</em> menyusundan<em> Depoları</em>"
+" seçin."
+
+#: i2p2www/pages/downloads/debian.html:72
+msgid ""
+"Click the <em>Other Sources</em> tab and click <em>Add</em>. Paste "
+"<code>ppa:i2p-maintainers/i2p</code> into the APT-line field and click "
+"<em>Add Source</em>. Click the <em>Close</em> button then "
+"<em>Reload</em>."
+msgstr ""
+"</em>Digər Mənbələr</em> bölümünü seçib, <em>Əlavə Et-i</em> klikləyin. "
+"APT-xətti ərazisinə <code>ppa:i2p-maintainers/i2p</code> kodunu "
+"yapışdırıb, sırayla <em>Mənbə Əlavə</em> et, <em>Bağla</em> və "
+"<em>Yeniden Yüklə-nin</em> üzərinə klikləyin."
+
+#: i2p2www/pages/downloads/debian.html:77
+msgid ""
+"In the Quick Filter box, type in <code>i2p</code> and press enter. When "
+"<code>i2p</code> is returned in the results list, right click "
+"<code>i2p</code> and select <em>Mark for Installation</em>. After doing "
+"so you may see a <em>Mark additional required changes?</em> popup. If so,"
+" click <em>Mark</em> then <em>Apply</em>."
+msgstr ""
+"Sürətli Filtr qutusuna <code>i2p</code> yazıb, Enter düyməsini seçin. "
+"<code>i2p</code> nəticələri görünəndə, <code>i2p</code> üzərinə sağla "
+"klikləyib, <em>Quraşdırmaq üçün işarəsi</em> ilə seçiminizi işarələyin. "
+"Bundan sonra <em>Başqa dəyişiklikləri işarələmək "
+"istəyirsinizmi?</em>yazılan pəncərə görünür. İstəyirsinizsə, "
+"<em>İşarələ</em> və <em>Tətbiq et üzərində klikləyin. "
+
+#: i2p2www/pages/downloads/debian.html:83
+msgid ""
+"After the installation process completes you can move on to the next\n"
+"part of <a href=\"#Post-install_work\">starting I2P</a> and configuring "
+"it for your system."
+msgstr ""
+"Quraşdırma tamamlananda, <a href=\"#Post-install_work\">I2P başlayır</a> "
+"növbəti hissəsinə və sisteminiz üçün \n"
+"quraşdırılmasına keçə bilərsiniz."
+
+#: i2p2www/pages/downloads/debian.html:88
+msgid "Instructions for Debian"
+msgstr "Debian üçün Təlimatlar"
+
+#: i2p2www/pages/downloads/debian.html:90
+msgid ""
+"Currently supported architectures include amd64, i386, armel, armhf (for "
+"Raspbian)."
+msgstr ""
+
+#: i2p2www/pages/downloads/debian.html:92
+msgid ""
+"Note: The steps below should be performed with root access (i.e., "
+"switching\n"
+"user to root with <code>su</code> or by prefixing each command with "
+"<code>sudo</code>)."
+msgstr ""
+
+#: i2p2www/pages/downloads/debian.html:97
+msgid ""
+"Ensure that <code>apt-transport-https</code> and <code>curl</code> are "
+"installed."
+msgstr ""
+
+#: i2p2www/pages/downloads/debian.html:104
+#, python-format
+msgid ""
+"\n"
+"    Check which version of Debian you are using on this page at the <a "
+"href=\"https://wiki.debian.org/LTS/\" target=\"_blank\">Debian wiki</a>"
+" \n"
+"    and verify with <code>%(file2)s</code> on your system.\n"
+"    Then, add lines like the following to <code>%(file)s</code>."
+msgstr ""
+
+#: i2p2www/pages/downloads/debian.html:130
+msgid ""
+"Note: If you are running Debian Sid (testing), then you can install I2P "
+"directly from Debian's main repository"
+msgstr ""
+
+#: i2p2www/pages/downloads/debian.html:137
+#, python-format
+msgid "Download <a href=\"%(repokey)s\">the  key used to sign the repository</a>:"
+msgstr ""
+
+#: i2p2www/pages/downloads/debian.html:148
+msgid "Check the fingerprint and owner of the key without importing anything"
+msgstr ""
+
+#: i2p2www/pages/downloads/debian.html:156
+msgid "Add the key to APT's keyring"
+msgstr ""
+
+#: i2p2www/pages/downloads/debian.html:164
+msgid "Notify your package manager of the new repository by entering"
+msgstr ""
+
+#: i2p2www/pages/downloads/debian.html:169
+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:175
+msgid ""
+"You are now ready to install I2P! Installing the <code>i2p-keyring</code>"
+"\n"
+"package will ensure that you receive updates to the repository's GPG key."
+msgstr ""
+
+#: i2p2www/pages/downloads/debian.html:185
+msgid ""
+"After the installation process completes you can move on to the next part"
+" of <a href=\"#Post-install_work\">starting I2P</a> and configuring it "
+"for your system."
+msgstr ""
+
+#: i2p2www/pages/downloads/debian.html:190
+#: i2p2www/pages/downloads/post-install.html:1
+msgid "Post-install work"
+msgstr ""
+
+#: i2p2www/pages/downloads/debian.html:192
+msgid ""
+"Using these I2P packages the I2P router can be started in the following\n"
+"three ways:"
+msgstr ""
+
+#: i2p2www/pages/downloads/debian.html:198
+msgid ""
+"&quot;on demand&quot; using the i2prouter script. Simply run "
+"&quot;<code>i2prouter\n"
+"start</code>&quot; from a command prompt. (Note: Do "
+"<strong><u>not</u></strong> use\n"
+"sudo or run it as root!)"
+msgstr ""
+
+#: i2p2www/pages/downloads/debian.html:205
+msgid ""
+"&quot;on demand&quot; without the <a "
+"href=\"http://wrapper.tanukisoftware.com/\">java service wrapper</a>\n"
+"(needed on non-Linux/non-x86 systems) by running \"<code>i2prouter-"
+"nowrapper</code>\".\n"
+"(Note: Do <strong><u>not</u></strong>\n"
+"use sudo or run it as root!)"
+msgstr ""
+
+#: i2p2www/pages/downloads/debian.html:213
+msgid ""
+"as a service that automatically runs when your system boots, even\n"
+"before logging in. The service can be enabled with \"<code>dpkg-"
+"reconfigure\n"
+"i2p</code>\" as root or using sudo. This is the recommended means of "
+"operation."
+msgstr ""
+
+#: i2p2www/pages/downloads/debian.html:221
+msgid ""
+"When installing for the first time, please remember to <b>adjust your "
+"NAT/firewall</b>\n"
+"if you can. The ports to forward can be found on the <a "
+"href=\"http://127.0.0.1:7657/confignet\">\n"
+"network configuration page</a> in the router console. If guidance with "
+"respect to forwarding ports is needed,\n"
+"you may find <a href=\"http://portforward.com\">portforward.com</a> to be"
+" helpful."
+msgstr ""
+
+#: i2p2www/pages/downloads/debian.html:228
+msgid ""
+"Please review and <b>adjust the bandwidth settings</b> on the\n"
+"<a href=\"http://127.0.0.1:7657/config.jsp\">configuration page</a>,\n"
+"as the default settings of 96 KB/s down / 40 KB/s up are fairly "
+"conservative."
+msgstr ""
+
+#: i2p2www/pages/downloads/debian.html:234
+#: i2p2www/pages/downloads/post-install.html:34
+#, python-format
+msgid ""
+"If you want to reach eepsites via your browser, have a look on the <a "
+"href=\"%(browserconfig)s\">browser proxy setup</a> page for an easy "
+"howto."
+msgstr ""
+
+#: i2p2www/pages/downloads/list.html:6 i2p2www/pages/downloads/select.html:15
+#: i2p2www/pages/global/nav.html:3
+msgid "Download"
+msgstr "Endir"
+
+#: i2p2www/pages/downloads/list.html:14
+msgid "Source package"
+msgstr ""
+
+#: i2p2www/pages/downloads/list.html:15 i2p2www/pages/downloads/list.html:160
+msgid "Automatic updates"
+msgstr ""
+
+#: i2p2www/pages/downloads/list.html:16
+msgid "Manual updates"
+msgstr ""
+
+#: i2p2www/pages/downloads/list.html:21
+msgid "Dependency"
+msgstr ""
+
+#: i2p2www/pages/downloads/list.html:22
+#, python-format
+msgid ""
+"\n"
+"Java Runtime Version 7 or higher.\n"
+"(<a href=\"%(java)s\">Oracle</a>,\n"
+"<a href=\"%(openjdk)s\">OpenJDK</a>, or\n"
+"<a href=\"%(icedtea)s\">IcedTea</a>\n"
+"Java Version 7 or 8 recommended,\n"
+"except Raspberry Pi: <a href=\"%(arm8)s\">Oracle JDK 8 for ARM</a>,\n"
+"PowerPC: <a href=\"%(ibmsdk7)s\">IBM Java SE 7 or 8</a>)\n"
+"<br />\n"
+"<a href=\"%(detectjre)s\">Determine your installed Java version here</a>\n"
+"or type <tt>java -version</tt> at your command prompt.\n"
+msgstr ""
+
+#: i2p2www/pages/downloads/list.html:39
+msgid ""
+"Java 9 support is in development and it is not recommended for general "
+"use."
+msgstr ""
+
+#: i2p2www/pages/downloads/list.html:46 i2p2www/pages/downloads/list.html:48
+msgid "Release Notes"
+msgstr "Buraxılış qeydləri"
+
+#: i2p2www/pages/downloads/list.html:50
+msgid "Change Log"
+msgstr ""
+
+#: i2p2www/pages/downloads/list.html:52
+msgid "Debian Change Log"
+msgstr ""
+
+#: i2p2www/pages/downloads/list.html:54
+msgid "Android Change Log"
+msgstr ""
+
+#: i2p2www/pages/downloads/list.html:59
+msgid "Clean installs"
+msgstr ""
+
+#: i2p2www/pages/downloads/list.html:63
+msgid "Download that file and run it."
+msgstr ""
+
+#: i2p2www/pages/downloads/list.html:69
+#, python-format
+msgid ""
+"Download that file and double-click it (if that works) or\n"
+"    type <code>java -jar i2pinstall_%(i2pversion)s.jar</code> in a "
+"terminal to run the\n"
+"    installer.\n"
+"    You may be able to right-click and select\n"
+"    &quot;Open with Java&quot;."
+msgstr ""
+
+#: i2p2www/pages/downloads/list.html:77 i2p2www/pages/downloads/list.html:93
+msgid "Command line (headless) install:"
+msgstr ""
+
+#: i2p2www/pages/downloads/list.html:78
+#, python-format
+msgid ""
+"Download the %(i2pversion)s OSX graphical installer file above and\n"
+"    run <code>java -jar i2pinstall_%(i2pversion)s.jar -console</code> "
+"from the command line."
+msgstr ""
+
+#: i2p2www/pages/downloads/list.html:85
+#, python-format
+msgid ""
+"Download that file and double-click it (if that works) or\n"
+"    type <code>java -jar i2pinstall_%(i2pversion)s.jar</code> in a "
+"terminal to run the\n"
+"    installer.\n"
+"    On some platforms you may be able to right-click and select\n"
+"    &quot;Open with Java&quot;."
+msgstr ""
+
+#: i2p2www/pages/downloads/list.html:94
+#, python-format
+msgid ""
+"Download the graphical installer file above and\n"
+"    run <code>java -jar i2pinstall_%(i2pversion)s.jar -console</code> "
+"from the command line."
+msgstr ""
+
+#: i2p2www/pages/downloads/list.html:102
+msgid "Packages for Debian &amp; Ubuntu are available."
+msgstr ""
+
+#: i2p2www/pages/downloads/list.html:108
+msgid ""
+"Requires Android 2.3 (Gingerbread) or higher. If you earlier installed\n"
+"      I2P, you need to reinstall because we have also changed the release"
+" keys."
+msgstr ""
+
+#: i2p2www/pages/downloads/list.html:112
+msgid "512 MB RAM minimum; 1 GB recommended."
+msgstr ""
+
+#: i2p2www/pages/downloads/list.html:115
+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:124
+#, python-format
+msgid ""
+"Alternately, you can fetch the source from <a href=\"%(monotoneurl)s"
+"#getting-the-i2p-code\">monotone</a>\n"
+"    or via Git from <a href=\"%(gitrepo)s\">git.repo.i2p</a> or <a "
+"href=\"%(github)s\">Github</a>.\n"
+"    <br />\n"
+"    Run <code>(tar xjvf i2psource_%(i2pversion)s.tar.bz2 ; cd "
+"i2p-%(i2pversion)s ; ant pkg)</code> then either\n"
+"    run the GUI installer or headless install as above."
+msgstr ""
+
+#: i2p2www/pages/downloads/list.html:134
+#, python-format
+msgid ""
+"Android source is in <a href=\"%(monotoneurl)s#getting-the-i2p-"
+"code\">monotone</a>\n"
+"    and on <a href=\"%(github)s\">Github</a>.\n"
+"    Android builds require the I2P source.\n"
+"    See the documentation in the Android source for additional build "
+"requirements and instructions."
+msgstr ""
+
+#: i2p2www/pages/downloads/list.html:145
+#, python-format
+msgid ""
+"The files are signed by %(signer)s,\n"
+"<a href=\"%(signingkey)s\">whose key is here</a>."
+msgstr ""
+
+#: i2p2www/pages/downloads/list.html:154
+msgid "Updates from earlier releases:"
+msgstr ""
+
+#: i2p2www/pages/downloads/list.html:156
+msgid "Both automatic and manual upgrades are available for the release."
+msgstr ""
+
+#: i2p2www/pages/downloads/list.html:161
+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:167
+msgid ""
+"Since 0.9.23, some releases are signed by str4d, whose signing key has "
+"been in the router\n"
+"since 0.9.9. Routers older than 0.9.9 will fail to verify update files "
+"signed by str4d,\n"
+"and will need to be manually updated using the process below."
+msgstr ""
+
+#: i2p2www/pages/downloads/list.html:178
+msgid ""
+"Download that file to your I2P\n"
+"    installation directory and <b>rename as i2pupdate.zip</b>.\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:187
+msgid "Click <a href=\"http://localhost:7657/configservice.jsp\">\"Restart\"</a>"
+msgstr ""
+
+#: i2p2www/pages/downloads/list.html:192
+msgid "Grab a cup of coffee and come back in 11 minutes"
+msgstr ""
+
+#: i2p2www/pages/downloads/list.html:199
+#, python-format
+msgid ""
+"The file is signed by %(signer)s,\n"
+"<a href=\"%(signingkey)s\">whose key is here</a>."
+msgstr ""
+
+#: i2p2www/pages/downloads/list.html:205
+msgid "Previous Releases"
+msgstr ""
+
+#: i2p2www/pages/downloads/list.html:207
+#, python-format
+msgid ""
+"Previous releases are available on <a "
+"href=\"http://code.google.com/p/i2p/downloads/list?can=1\">Google "
+"Code</a>\n"
+"and <a href=\"https://launchpad.net/i2p/trunk\">Launchpad</a>\n"
+"and within the I2P network on <a "
+"href=\"http://%(echelon)s/\">%(echelon)s</a>."
+msgstr ""
+
+#: i2p2www/pages/downloads/post-install.html:3
+msgid ""
+"After running the installer on windows, simply click on the \"Start I2P\""
+" button\n"
+"which will bring up the <a "
+"href=\"http://localhost:7657/index.jsp\">router console</a>,\n"
+"which has further instructions."
+msgstr ""
+
+#: i2p2www/pages/downloads/post-install.html:9
+msgid ""
+"On Unix-like systems, I2P can be started as a service\n"
+"using the \"i2prouter\" script, located in the directory you selected for"
+" I2P.\n"
+"Changing to that directory in a console and issuing \"sh i2prouter "
+"status\"\n"
+"should tell you the router's status. The arguments \"start\", \"stop\" "
+"and \"restart\"\n"
+"control the service. The <a "
+"href=\"http://localhost:7657/index.jsp\">router console</a>\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/post-install.html:20
+#, python-format
+msgid ""
+"When installing for the first time, please remember to <b>adjust your "
+"NAT/firewall</b>\n"
+"if you can, bearing in mind the Internet-facing ports I2P uses,\n"
+"<a href=\"%(faq)s#ports\">described here</a> among other ports.\n"
+"If you have successfully opened your port to inbound TCP, also enable "
+"inbound TCP on the\n"
+"<a href=\"http://localhost:7657/confignet.jsp\">configuration page</a>."
+msgstr ""
+
+#: i2p2www/pages/downloads/post-install.html:28
+msgid ""
+"Also, please review and <b>adjust the bandwidth settings</b> on the\n"
+"<a href=\"http://localhost:7657/config.jsp\">configuration page</a>,\n"
+"as the default settings of 96 KBps down / 40 KBps up are fairly slow."
+msgstr ""
+
+#: i2p2www/pages/downloads/redirect.html:2
+msgid "Downloading..."
+msgstr ""
+
+#: i2p2www/pages/downloads/redirect.html:8
+#, python-format
+msgid ""
+"Your download will begin shortly. If it doesn't start within 5 seconds, "
+"click <a href=\"%(url)s\">here</a>."
+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? <a href=\"%(donate)s\">Add in your "
+"donation</a>, \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:17 i2p2www/pages/global/nav.html:126
+msgid "Donate"
+msgstr ""
+
+#: i2p2www/pages/global/layout.html:35
+msgid "Skip navigation"
+msgstr ""
+
+#: i2p2www/pages/global/layout.html:38
+msgid "I2P Logo"
+msgstr ""
+
+#: i2p2www/pages/global/layout.html:38 i2p2www/pages/site/index.html:3
+msgid "The Invisible Internet Project"
+msgstr ""
+
+#: i2p2www/pages/global/layout.html:80
+#, 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:84
+#, python-format
+msgid "This page was last updated in %(lastupdated)s."
+msgstr ""
+
+#: i2p2www/pages/global/layout.html:88
+#, python-format
+msgid "This page is accurate for router version %(accuratefor)s."
+msgstr ""
+
+#: i2p2www/pages/global/macros:26
+msgid "Previous"
+msgstr "Əvvəlki"
+
+#: i2p2www/pages/global/macros:41
+msgid "Next"
+msgstr "Növbəti"
+
+#: i2p2www/pages/global/macros:54
+msgid "Posted in"
+msgstr ""
+
+#: i2p2www/pages/global/nav.html:4
+msgid "About"
+msgstr "Haqqında"
+
+#: i2p2www/pages/global/nav.html:6
+msgid "Introduction to I2P"
+msgstr ""
+
+#: 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 "Şəbəkə verilənlər bazası"
+
+#: i2p2www/pages/global/nav.html:26
+msgid "Tunnel routing"
+msgstr ""
+
+#: i2p2www/pages/global/nav.html:27
+msgid "Peer selection"
+msgstr "Bənzərlərin seçimi"
+
+#: i2p2www/pages/global/nav.html:28
+msgid "Cryptography"
+msgstr ""
+
+#: i2p2www/pages/global/nav.html:29
+msgid "ElGamal/AES+SessionTags"
+msgstr ""
+
+#: i2p2www/pages/global/nav.html:32
+msgid "Specifications"
+msgstr "Xüsusiyyətlər"
+
+#: i2p2www/pages/global/nav.html:33
+msgid "Proposals"
+msgstr ""
+
+#: i2p2www/pages/global/nav.html:34
+msgid "API"
+msgstr "APİ"
+
+#: i2p2www/pages/global/nav.html:40
+msgid "Streaming library"
+msgstr ""
+
+#: i2p2www/pages/global/nav.html:41
+msgid "Datagrams"
+msgstr "Dataqtamlar"
+
+#: i2p2www/pages/global/nav.html:45 i2p2www/pages/global/nav.html:109
+msgid "Applications"
+msgstr ""
+
+#: i2p2www/pages/global/nav.html:47
+msgid "Supported applications"
+msgstr ""
+
+#: i2p2www/pages/global/nav.html:48
+msgid "Bittorrent"
+msgstr ""
+
+#: i2p2www/pages/global/nav.html:51
+msgid "Protocols"
+msgstr ""
+
+#: i2p2www/pages/global/nav.html:53
+msgid "Protocol stack"
+msgstr ""
+
+#: i2p2www/pages/global/nav.html:58
+msgid "Transports"
+msgstr "Nəqliyyatlar"
+
+#: i2p2www/pages/global/nav.html:60
+msgid "Transport layer overview"
+msgstr ""
+
+#: i2p2www/pages/global/nav.html:65
+msgid "Tunnels"
+msgstr "Tunellər"
+
+#: i2p2www/pages/global/nav.html:67
+msgid "Tunnel implementation"
+msgstr ""
+
+#: i2p2www/pages/global/nav.html:68
+msgid "Unidirectional tunnels"
+msgstr "Tək istiqamətli tunellər"
+
+#: i2p2www/pages/global/nav.html:69
+msgid "Old implementation"
+msgstr "Köhnə tətbiq"
+
+#: i2p2www/pages/global/nav.html:72
+msgid "Naming and addressbook"
+msgstr "Adlandırma və ünvan kitabçası"
+
+#: i2p2www/pages/global/nav.html:73
+msgid "Plugins"
+msgstr "Qoşmalar"
+
+#: i2p2www/pages/global/nav.html:74
+msgid "Reseed"
+msgstr "Kompleks"
+
+#: i2p2www/pages/global/nav.html:77
+msgid "Team"
+msgstr "Komanda"
+
+#: i2p2www/pages/global/nav.html:79
+msgid "Hall of Fame"
+msgstr "Şöhrət zalı"
+
+#: i2p2www/pages/global/nav.html:80
+msgid "Academic papers and peer review"
+msgstr "Akademik məqalələr və ekspert qiymətləndirməsi "
+
+#: i2p2www/pages/global/nav.html:82
+msgid "Presentations, tutorials and articles"
+msgstr "Təqdimatlar, elmi materiallar və məqalələr"
+
+#: i2p2www/pages/global/nav.html:83
+msgid "Contact us"
+msgstr "Bizimlə əlaqə saxlayın"
+
+#: i2p2www/pages/global/nav.html:84 i2p2www/pages/site/links.html:2
+msgid "Links"
+msgstr "Linklər"
+
+#: i2p2www/pages/global/nav.html:85
+msgid "Impressum"
+msgstr "Minnətdarlıq"
+
+#: i2p2www/pages/global/nav.html:88
+msgid "Help"
+msgstr "Kömək"
+
+#: i2p2www/pages/global/nav.html:90
+msgid "FAQ"
+msgstr "FAQ"
+
+#: i2p2www/pages/global/nav.html:91
+msgid "How to browse I2P"
+msgstr "İ2P-yə necə baxmalı "
+
+#: i2p2www/pages/global/nav.html:92
+msgid "Glossary"
+msgstr "Sözlük"
+
+#: i2p2www/pages/global/nav.html:93
+msgid "Performance"
+msgstr "Məhsuldarlıq"
+
+#: i2p2www/pages/global/nav.html:94 i2p2www/pages/site/contact.html:43
+msgid "Forums"
+msgstr "Forumlar"
+
+#: i2p2www/pages/global/nav.html:95
+msgid "Verify I2P"
+msgstr "I2P-ni yoxlamaq"
+
+#: i2p2www/pages/global/nav.html:97
+msgid "Release signing keys"
+msgstr "Buraxılış üçün imza açarları"
+
+#: i2p2www/pages/global/nav.html:98
+msgid "Signed keys"
+msgstr "İmzalanmış açarlar"
+
+#: i2p2www/pages/global/nav.html:99
+msgid "Developers keys"
+msgstr "Yaradıcıların açarları"
+
+#: i2p2www/pages/global/nav.html:104
+msgid "Volunteer"
+msgstr "Könüllü"
+
+#: i2p2www/pages/global/nav.html:106
+msgid "Get involved!"
+msgstr "Qoşulun!"
+
+#: i2p2www/pages/global/nav.html:107
+msgid "Develop"
+msgstr "İnkişaf"
+
+#: i2p2www/pages/global/nav.html:110
+msgid "Licenses"
+msgstr "Lisenziyalar"
+
+#: i2p2www/pages/global/nav.html:111
+msgid "Bug tracker"
+msgstr "Xəta indikatoru"
+
+#: i2p2www/pages/global/nav.html:114
+msgid "Academic research"
+msgstr "Akademik araşdırma"
+
+#: i2p2www/pages/global/nav.html:115
+msgid "Open research questions"
+msgstr "Tədqiqatın açıq sualları"
+
+#: i2p2www/pages/global/nav.html:116
+msgid "Guides"
+msgstr "Qaydalar"
+
+#: i2p2www/pages/global/nav.html:118
+msgid "New developers"
+msgstr "Yeni yaradıcılar"
+
+#: i2p2www/pages/global/nav.html:119
+msgid "Using an IDE with I2P"
+msgstr "I2P ilə bir IDE istifadə etmək "
+
+#: i2p2www/pages/global/nav.html:120
+msgid "Developer guidelines and coding style"
+msgstr "Yaradıcı qaydaları və kodlaşdırma tərzi "
+
+#: i2p2www/pages/global/nav.html:121
+msgid "Monotone"
+msgstr "Monoton"
+
+#: i2p2www/pages/global/nav.html:122
+msgid "New translators"
+msgstr "Yeni tərcüməçilər"
+
+#: i2p2www/pages/global/nav.html:125
+msgid "Bounties"
+msgstr "Mükafatlar"
+
+#: i2p2www/pages/global/nav.html:127
+msgid "Meetings"
+msgstr "Görüşlər"
+
+#: i2p2www/pages/global/nav.html:128
+msgid "Roadmap"
+msgstr "Yol xəritəsi"
+
+#: i2p2www/pages/global/nav.html:129
+msgid "Task list"
+msgstr "Tapşırıq siyahısı"
+
+#: i2p2www/pages/global/nav.html:132
+msgid "Language"
+msgstr "Dil"
+
+#: i2p2www/pages/meetings/index.html:2
+msgid "Logs of past I2P meetings"
+msgstr "Keçmiş I2P görüşlərinin qeydiyyatı"
+
+#: i2p2www/pages/meetings/index.html:4
+msgid "I2P Meetings ATOM Feed"
+msgstr "I2P Görüşləri ATOM Axını"
+
+#: i2p2www/pages/meetings/index.html:7
+#, python-format
+msgid ""
+"Regularly scheduled project meetings are held on the first Tuesday of "
+"every month at 8 PM UTC.\n"
+"Anyone can schedule and\n"
+"run a meeting, by posting the agenda in\n"
+"<a href=\"%(mtgforum)s\">the meetings forum</a>."
+msgstr ""
+"Layihə görüşləri hər ayın ilk çərşənbə axşamı günü axşam saat 8-də UTC "
+"keçirilir. \n"
+"İstəyən hər bir kəs \n"
+"<a href=\"%(mtgforum)s\">görüşlər forumunda</a> bir görüş planlayaraq, "
+"keçirə bilər. "
+
+#: i2p2www/pages/meetings/index.html:14
+#, python-format
+msgid ""
+"If you have something to discuss, please find the developers on IRC in "
+"#i2p-dev.\n"
+"<a href=\"%(blogindex)s\">Status updates</a> from developers are also "
+"available."
+msgstr ""
+"Müzakirə etmək istədiyiniz mövzular üçün yaradıcıları #i2p-dev. İRC "
+"kanalında tapın. \n"
+"Yaradıcıların <a href=\"%(blogindex)s\">Status yeniləmələri</a>də "
+"mövcuddur."
+
+#: i2p2www/pages/meetings/show.html:2
+#, python-format
+msgid "I2P Development Meeting %(id)s"
+msgstr "İ2P Yaradıcıların Görüşü%(id)s"
+
+#: i2p2www/pages/meetings/show.html:10
+msgid "Full IRC Log"
+msgstr "Tam İRC Qeydiyyatı"
+
+#: i2p2www/pages/papers/list.html:28
+msgid "By topic"
+msgstr "Mövzuya görə"
+
+#: i2p2www/pages/papers/list.html:34
+msgid "By date"
+msgstr "Tarixə görə"
+
+#: i2p2www/pages/papers/list.html:40
+msgid "By author"
+msgstr "Müəllifə görə"
+
+#: i2p2www/pages/papers/list.html:69
+#, python-format
+msgid ""
+"Please send new or corrected entries to\n"
+"<a name=\"contact\"><span class=\"email\">%(email)s</span></a>.<br />\n"
+"If you can, please format them as BibTeX; see our\n"
+"<a href=\"%(bibtex)s\">BibTeX source page</a> for examples.<br />\n"
+"Remember to include URLs if possible:\n"
+"<a href=\"%(citeseer)s\">offline papers are less useful</a>."
+msgstr ""
+
+#: i2p2www/pages/papers/list.html:80
+#, python-format
+msgid ""
+"The source code for this page was adapted from\n"
+"<a href=\"%(anonbib)s\">Free Haven's anonymity bibliography</a>."
+msgstr ""
+
+#: i2p2www/pages/site/contact.html:2
+msgid "Contact"
+msgstr "Əlaqə"
+
+#: i2p2www/pages/site/contact.html:4
+msgid "Email"
+msgstr "Email"
+
+#: i2p2www/pages/site/contact.html:5
+msgid ""
+"Please do not use these email addresses for support requests.\n"
+"These are not public email lists.\n"
+"We do not provide help via email."
+msgstr ""
+
+#: i2p2www/pages/site/contact.html:25
+msgid ""
+"Our primary IRC network is the Irc2P network within I2P; a default tunnel"
+" to this network is set up with new router installs.\n"
+"  We are also present on multiple standard networks like <a "
+"href=\"http://www.oftc.net/oftc/OFTC\">OFTC</a>,\n"
+"  <a href=\"http://www.einirc.de/\">EIN</a> and <a "
+"href=\"http://freenode.net/\">Freenode</a>.\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:33
+msgid "Channel list:"
+msgstr ""
+
+#: i2p2www/pages/site/contact.html:35
+msgid "General i2p discussion and help channel"
+msgstr ""
+
+#: i2p2www/pages/site/contact.html:36
+msgid "Offtopic"
+msgstr ""
+
+#: i2p2www/pages/site/contact.html:37
+msgid "Development talk"
+msgstr "İnkişafetdirici söhbətlər"
+
+#: i2p2www/pages/site/contact.html:38
+msgid "Purple I2P (I2Pd) Development talk"
+msgstr ""
+
+#: i2p2www/pages/site/contact.html:39
+msgid "Abscond browser bundle discussion and development"
+msgstr ""
+
+#: i2p2www/pages/site/contact.html:44
+#, python-format
+msgid ""
+"Most of the discussion about I2P's development happens on the <a "
+"href=\"http://%(zzz)s\">I2P developer forum</a>. This is usually the best"
+" place to start with inquiries, if the dev IRC channel is inactive."
+msgstr ""
+
+#: i2p2www/pages/site/contact.html:48
+msgid "Mailing lists"
+msgstr ""
+
+#: i2p2www/pages/site/contact.html:49
+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:54
+msgid "Subscribing"
+msgstr "Abunə olmaq"
+
+#: i2p2www/pages/site/contact.html:55
+msgid ""
+"To subscribe to a mailing list, go to the list information page (linked "
+"below) and fill out the form. I2P-internal email addresses "
+"(foobar@mail.i2p) can be used."
+msgstr ""
+
+#: i2p2www/pages/site/contact.html:59
+msgid "Unsubscribing"
+msgstr ""
+
+#: i2p2www/pages/site/contact.html:60
+msgid ""
+"To unsubscribe from a mailing list or edit your subscription options, go "
+"to the list information page (linked below) and enter your subscription "
+"email address."
+msgstr ""
+
+#: i2p2www/pages/site/contact.html:64
+msgid "Lists"
+msgstr "Siyahılar"
+
+#: i2p2www/pages/site/contact.html:67 i2p2www/pages/site/contact.html:71
+msgid "Archive"
+msgstr "Arxiv"
+
+#: i2p2www/pages/site/contact.html:68
+msgid "I2P developer discussions - anything related to development of I2P"
+msgstr ""
+
+#: i2p2www/pages/site/contact.html:72
+msgid ""
+"General I2P discussion - anything that doesn't fit in a different list "
+"goes here"
+msgstr ""
+
+#: i2p2www/pages/site/contact.html:78
+msgid ""
+"You don't like mailing lists? Then this is for you. All mailing lists are"
+" available via NNTP as well."
+msgstr ""
+
+#: i2p2www/pages/site/contact.html:83
+msgid "Group-List-mapping:"
+msgstr ""
+
+#: i2p2www/pages/site/contact.html:88
+msgid "Servers:"
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:2
+msgid "Frequently Asked Questions"
+msgstr "Tez-tez verilən suallar"
+
+#: i2p2www/pages/site/faq.html:6
+msgid "General"
+msgstr "Əsas"
+
+#: i2p2www/pages/site/faq.html:8 i2p2www/pages/site/faq.html:50
+msgid "What systems will I2P run on?"
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:9 i2p2www/pages/site/faq.html:75
+msgid "Is installing Java required to use I2P?"
+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:91
+msgid "What do the Active x/y numbers mean in the router console?"
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:12
+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:13 i2p2www/pages/site/faq.html:113
+msgid "I can't access regular Internet sites through I2P."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:14 i2p2www/pages/site/faq.html:124
+msgid "Is using an outproxy safe?"
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:15 i2p2www/pages/site/faq.html:152
+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:17
+msgid "Getting Started"
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:19 i2p2www/pages/site/faq.html:192
+msgid "How do I configure my browser?"
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:20 i2p2www/pages/site/faq.html:200
+msgid "How do I connect to IRC within I2P?"
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:21 i2p2www/pages/site/faq.html:215
+msgid "How do I set up my own eepsite?"
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:22 i2p2www/pages/site/faq.html:222
+msgid "What ports does I2P use?"
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:23 i2p2www/pages/site/faq.html:496
+msgid ""
+"I'm missing lots of hosts in my addressbook. What are some good "
+"subscription links?"
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:24 i2p2www/pages/site/faq.html:521
+msgid ""
+"How can I access the web console from my other machines or password "
+"protect it?"
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:25 i2p2www/pages/site/faq.html:585
+msgid "How can I use applications from my other machines?"
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:26 i2p2www/pages/site/faq.html:593
+msgid "Is it possible to use I2P as a SOCKS proxy?"
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:27 i2p2www/pages/site/faq.html:611
+msgid "How do I reseed manually?"
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:28 i2p2www/pages/site/faq.html:682
+msgid ""
+"How do I access IRC, BitTorrent, or other services on the regular "
+"Internet?"
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:29 i2p2www/pages/site/faq.html:694
+msgid "I can't access https:// or ftp:// sites through I2P."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:31
+msgid "Troubleshooting"
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:33
+msgid "My router is using too much CPU?!?"
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:34 i2p2www/pages/site/faq.html:788
+msgid ""
+"My router has been up for several minutes and has zero or very few "
+"connections"
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:35 i2p2www/pages/site/faq.html:796
+msgid "My router has very few active peers, is this OK?"
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:36 i2p2www/pages/site/faq.html:807
+msgid ""
+"My active peers / known peers / participating tunnels / connections / "
+"bandwidth vary dramatically over time! Is anything wrong?"
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:37 i2p2www/pages/site/faq.html:819
+msgid ""
+"What makes downloads, torrents, web browsing, and everything else slower "
+"on I2P as compared to the regular internet?"
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:38
+msgid ""
+"In <code>wrapper.log</code> I see an error stating <code>Protocol family "
+"unavailable</code> when I2P is loading"
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:39 i2p2www/pages/site/faq.html:920
+msgid "Most of the eepsites within I2P are down?"
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:40
+msgid "Why is I2P listening for connections on port 32000?"
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:41 i2p2www/pages/site/faq.html:942
+msgid "I think I found a bug, where can I report it?"
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:42 i2p2www/pages/site/faq.html:974
+msgid "I have a question!"
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:51
+#, python-format
+msgid ""
+"I2P is written in the <a href=\"%(java)s\">Java programming language</a>."
+" \n"
+"It has been tested on Windows, Linux, FreeBSD and OSX. \n"
+"An <a href=\"%(android)s\">Android port</a> is also available."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:58
+msgid ""
+"In terms of memory usage, I2P is configured to use 128 MB of RAM by "
+"default. \n"
+"This is sufficient for browsing and IRC usage. However, other activities "
+"may require greater memory allocation. \n"
+"For example, if one wishes to run a high-bandwidth router, participate in"
+" I2P torrents or serve high-traffic hidden services, \n"
+"a higher amount of memory is required."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:63
+#, python-format
+msgid ""
+"In terms of CPU usage, I2P has been tested to run on modest systems such "
+"as the <a href=\"%(rpi)s\">Raspberry Pi</a> range of single-board "
+"computers.\n"
+"As I2P makes heavy use of cryptographic techniques, a stronger CPU will "
+"be better suited to handle the workload generated by I2P as well as tasks"
+" \n"
+"related to the rest of the system (i.e. Operating System, GUI, Other "
+"processes e.g. Web Browsing)."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:68
+#, python-format
+msgid ""
+"A comparison of some of the available Java Runtime Environments (JRE) is "
+"available here: \n"
+"<a href=\"%(chart)s\">%(chart)s</a>.\n"
+"\n"
+"Using Sun/Oracle Java or OpenJDK is recommended."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:77
+#, python-format
+msgid ""
+"While the main I2P client implementation requires Java, there are several"
+"\n"
+"<a href=\"%(alt)s\">alternative clients</a> which don't require Java."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:83
+msgid "Whats an \"eepsite\"?"
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:85
+msgid ""
+"An eepsite is a website that is hosted anonymously, a hidden service "
+"which is accessible through your web browser. \n"
+"It can be accessed by setting your web browser's HTTP proxy to use the "
+"I2P web proxy (typically it listens on localhost port 4444), and browsing"
+" to the site."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:93
+msgid ""
+"x is the number of peers you've sent or received a message from "
+"successfully in the last minute, y is the number of peers seen in the "
+"last hour or so. \n"
+"Try hovering your cursor over the other lines of information for a brief "
+"description."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:99
+msgid ""
+"Is my router an \"exit node\" to the regular Internet? I don't want it to"
+" be."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:101
+#, python-format
+msgid ""
+"No. Unlike <a href=\"https://www.torproject.org/\">Tor</a>, \"exit "
+"nodes\" - or \"outproxies\" as they are referred to on the I2P network -"
+" \n"
+"are not an inherent part of the network. \n"
+"Only volunteers who specifically set up and run separate applications "
+"will relay traffic to the regular Internet. \n"
+"There are very, very few of these.\n"
+"\n"
+"By default, I2P's HTTP Proxy (configured to run on port 4444) includes a "
+"single outproxy: false.i2p. This is run on a voluntary basis by Meeh.\n"
+"\n"
+"There is an <a href=\"%(outproxy)s\">outproxy guide</a> available on our "
+"forums, if you would like to learn more about running an outproxy."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:115
+msgid ""
+"I2P is primarily not intended, nor designed, to be used as a proxy to the"
+" regular internet. \n"
+"With that said, there are services which are provided by volunteers that "
+"act as proxies to clearnet based content - these are referred to as "
+"\"outproxies\" on the I2P network. \n"
+"There is an outproxy configured by default in I2P's HTTP client tunnel - "
+"false.i2p. \n"
+"While this service does currently exist, there is no guarantee that it "
+"will always be there as it is not an official service provided by the I2P"
+" project. \n"
+"If your main requirement from an anonymous network is the ability to "
+"access clearnet resources, we would recommend using <a "
+"href=\"https://www.torproject.org/\">Tor</a>."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:126
+msgid ""
+"I2P does not encrypt the Internet, neither does Tor - for example, "
+"through <a "
+"href=\"https://en.wikipedia.org/wiki/Transport_Layer_Security\">Transport"
+" Layer Security (TLS)</a>. \n"
+"I2P and Tor both aim to transport your traffic as-is securely and "
+"anonymously over the corresponding network, to its destination. \n"
+"Any unencrypted traffic generated at your system will arrive at the "
+"outproxy (on I2P) or the exit node (on Tor) as unencrypted traffic. \n"
+"This means that you are vulnerable to snooping by the outproxy operators."
+" \n"
+"One way to protect your outproxy traffic against this is to ensure that "
+"any traffic that will be handled by the outproxy is encrypted with TLS."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:134
+msgid ""
+"For more information, you may read the Tor FAQ's answer to this question:"
+"\n"
+"<a "
+"href=\"https://www.torproject.org/docs/faq#CanExitNodesEavesdrop\">https://www.torproject.org/docs/faq#CanExitNodesEavesdrop</a>"
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:139
+#, 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 <a "
+"href=\"http://%(zzz)s/topics/217\">%(zzz)s</a>.\n"
+"This discussion has been <a href=\"%(i2pforum)s\">mirrored on our "
+"forums</a> as well."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:146
+#, python-format
+msgid ""
+"\n"
+"Ultimately, this is a question that only you can answer because the "
+"correct answer depends on your browsing behaviour, \n"
+"your <a href=\"%(threatmodel)s\">threat model</a>, and how much you "
+"choose to trust the outproxy operator."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:154
+msgid ""
+"I2P is an anonymous network - it is designed to withstand attempts at "
+"blocking or censoring of content, thus providing a means for "
+"communication that anyone can use. \n"
+"I2P traffic that transits through your router is encrypted with several "
+"layers of encryption. \n"
+"Except in the case of a serious security vulnerability (of which none are"
+" currently known), \n"
+"it is not possible to know what the contents of the traffic are and thus "
+"not possible to distinguish between traffic which one is opposed to or "
+"not opposed to.  \n"
+"\n"
+" We consider the 3 parts of the question:"
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:164
+msgid ""
+"<b>Distribution</b><br> \n"
+"All traffic on I2P is encrypted in multiple layers. You don't know a "
+"message's contents, source, or destination.\n"
+"All traffic you route is internal to the I2P network, you are not an <a "
+"href=\"#exit\">exit node</a> (referred to as an outproxy in our "
+"documentation).\n"
+"Your only alternative is to refuse to route <i>any</i> 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&#37; of users route traffic for others."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:174
+msgid ""
+"<b>Storage</b><br> \n"
+"I2P does not do distributed storage of content, this has to be "
+"specifically installed and configured by the user (with Tahoe-LAFS, for "
+"example). \n"
+"That is a feature of a different anonymous network, <a "
+"href=\"http://freenetproject.org/\">Freenet</a>.\n"
+"By running I2P, you are not storing content for anyone."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:182
+msgid ""
+"<b>Access</b><br>\n"
+"If there are hidden services which you dislike, you may refrain from "
+"visiting them.\n"
+"Your router will not request any content without your specific "
+"instruction to do so."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:194
+#, python-format
+msgid ""
+"The proxy config for different browsers is on a <a "
+"href=\"%(browserconfig)s\"> separate page</a> with screenshots. \n"
+"More advanced configs with external tools, such as the browser plug-in "
+"FoxyProxy or the proxy server Privoxy, are possible but could introduce "
+"leaks in your setup."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:202
+msgid ""
+"\n"
+"A tunnel to the main IRC server within I2P, Irc2P, is created when I2P is"
+" installed (see the <a "
+"href=\"http://localhost:7657/i2ptunnel/index.jsp\">I2PTunnel "
+"configuration page</a>), and is automatically started when the I2P router"
+" starts. \n"
+"To connect to it, tell your IRC client to connect to <code>localhost "
+"6668</code>. \n"
+"HexChat-like client users can create a new network with the server "
+"<code>localhost/6668</code> (remember to tick \"Bypass proxy server\" if "
+"you have a proxy server configured).\n"
+"Weechat users can use the following command to add a new network:"
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:217
+msgid ""
+"Click on the <a href=\"http://localhost:7658/\">Website</a> link at the "
+"top of your router console for instructions."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:224
+msgid "The ports that are used by I2P can be divided into 2 sections:"
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:229
+msgid ""
+"Internet-facing ports, which are used for communication with other I2P "
+"routers"
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:230
+msgid "Local ports, for local connections"
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:233
+msgid "These are described in detail below."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:238
+msgid ""
+"Internet-facing ports<br> Note: Since release 0.7.8, new installs do not "
+"use port 8887; \n"
+"    a random port between 9000 and 31000 is selected when the program is "
+"run for the first time. \n"
+"    The selected port is shown on the router <a "
+"href=\"http://127.0.0.1:7657/confignet\">configuration page</a>."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:241
+msgid "OUTBOUND"
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:243
+msgid ""
+"UDP from the random port listed on the <a "
+"href=\"http://127.0.0.1:7657/confignet\">configuration page</a> to "
+"arbitrary remote UDP ports, allowing for replies"
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:244
+msgid "TCP from random high ports to arbitrary remote TCP ports"
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:245
+msgid ""
+"Outbound UDP on port 123, allowing for replies. \n"
+"        This is necessary for I2P's internal time sync (via SNTP - "
+"querying a random SNTP host in pool.ntp.org or another server you "
+"specify)"
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:248
+msgid "INBOUND"
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:250
+msgid ""
+"(Optional, recommended) UDP to the port noted on the <a "
+"href=\"http://127.0.0.1:7657/confignet\">configuration page</a> from "
+"arbitrary locations"
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:251
+msgid ""
+"(Optional, recommended) TCP to the port noted on <a "
+"href=\"http://127.0.0.1:7657/confignet\">configuration page</a> from "
+"arbitrary locations"
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:252
+msgid ""
+"Inbound TCP can be disabled on the <a "
+"href=\"http://127.0.0.1:7657/confignet\">configuration page</a>"
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:255
+msgid ""
+"Local I2P ports, listening only to local connections by default, except "
+"where noted:"
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:259
+msgid "PORT"
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:262
+msgid "PURPOSE"
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:265
+msgid "DESCRIPTION"
+msgstr "AÇIQLAMA:"
+
+#: i2p2www/pages/site/faq.html:276
+msgid ""
+"Cannot be changed. Binds to all interfaces. May be disabled on <a "
+"href=\"http://127.0.0.1:7657/confignet\">confignet</a>."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:287
+msgid ""
+"A higher level socket API for clients. Disabled by default. May be "
+"enabled/disabled on <a "
+"href=\"http://127.0.0.1:7657/configclients\">configclients</a>. \n"
+"          May be changed in the bob.config file."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:299 i2p2www/pages/site/faq.html:310
+#: i2p2www/pages/site/faq.html:321
+msgid ""
+"May be disabled or changed on the i2ptunnel page in the router console. "
+"May also be configured to be bound to a specific interface or all "
+"interfaces."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:332
+msgid ""
+"Binds to the LAN address. \n"
+"          May be changed with advanced config "
+"<code>i2np.upnp.HTTPPort=nnnn</code>. \n"
+"          May be disabled on <a "
+"href=\"http://127.0.0.1:7657/confignet\">confignet</a>."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:345
+msgid ""
+"Binds to the LAN address. \n"
+"          May be changed with advanced config "
+"<code>i2np.upnp.SSDPPort=nnnn</code>. \n"
+"          May be disabled on <a "
+"href=\"http://127.0.0.1:7657/confignet\">confignet</a>."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:358
+msgid ""
+"Used by client apps. \n"
+"          May be changed to a different port on <a "
+"href=\"http://127.0.0.1:7657/configclients\">configclients</a> but this "
+"is not recommended. \n"
+"          May be to bind to a different interface or all interfaces, or "
+"disabled, on <a "
+"href=\"http://127.0.0.1:7657/configclients\">configclients</a>."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:371
+msgid ""
+"A higher level socket API for clients Only opened when a SAM V3 client "
+"requests a UDP session. \n"
+"          May be enabled/disabled on <a "
+"href=\"http://127.0.0.1:7657/configclients\">configclients</a>. \n"
+"          May be changed in the <code>clients.config</code> file with the"
+" SAM command line option <code>sam.udp.port=nnnn</code>."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:384
+msgid ""
+"A higher level socket API for clients Disabled by default for new "
+"installs as of release 0.6.5. \n"
+"          May be enabled/disabled on <a "
+"href=\"http://127.0.0.1:7657/configclients\">configclients</a>. \n"
+"          May be changed in the <code>clients.config</code> file."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:397
+msgid ""
+"May be disabled in the <code>clients.config</code>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:409
+msgid ""
+"May be disabled in the <code>clients.config</code> file. \n"
+"          May also be configured to be bound to a specific interface or "
+"all interfaces in the <code>jetty.xml</code> file."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:421 i2p2www/pages/site/faq.html:433
+#: i2p2www/pages/site/faq.html:445
+msgid ""
+"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:457
+msgid ""
+"Outbound to 32000 only, does not listen on this port. \n"
+"          Starts at 31000 and will increment until 31999 looking for a "
+"free port. \n"
+"          To change, see the <a "
+"href=\"http://wrapper.tanukisoftware.com/doc/english/prop-"
+"port.html\">wrapper documentation</a>. \n"
+"          For more information see <a href=\"#port32000\">below</a>."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:471
+msgid ""
+"To change, see the <a "
+"href=\"http://wrapper.tanukisoftware.com/doc/english/prop-"
+"port.html\">wrapper documentation</a>. \n"
+"          For more information see <a href=\"#port32000\">below</a>."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:479
+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:487
+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 "
+"<a href=\"http://localhost:7657/config\">outbound facing port</a>, 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:497
+msgid "This question can be answered in 3 parts:"
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:502
+msgid ""
+"My router often displays a message saying \"Website Not Found In "
+"Addressbook\", why do I see this message?"
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:503
+msgid ""
+"Human-readable addresses such as <i>http://website.i2p</i> are references"
+" to a long, random string known as a <b>destination</b>. \n"
+"    These references are registered and stored at addressbook services "
+"such as stats.i2p, which is run by zzz. \n"
+"    You will often encounter a \"b32\" address. A \"b32\" is a hash "
+"(specifically, a <a "
+"href=\"https://en.wikipedia.org/wiki/SHA-2\">SHA256</a> hash) of the \n"
+"    destination. This hash is appended with \".b32.i2p\" and serves as a "
+"convenient way to link to your hidden service, without requiring any "
+"registration on an addressbook service."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:507
+msgid ""
+"It is possible to add subscriptions to your router's configuration which "
+"may reduce the frequency of these messages."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:508
+msgid "What is an addressbook subscription?"
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:509
+msgid ""
+"This is a list of files hosted on various I2P websites each of which "
+"contain a list of I2P hosts and their associated destinations."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:510
+msgid ""
+"The addressbook is located at <a "
+"href=\"http://localhost:7657/dns\">http://localhost:7657/dns</a> where "
+"further information can be found."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:511
+msgid "What are some good addressbook subscription links?"
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:512
+msgid "You may try the following:"
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:523
+msgid ""
+"For security purposes, the router's admin console by default only listens"
+" for connections on the local interface.  \n"
+"\n"
+"There are two methods for accessing the console remotely:"
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:529 i2p2www/pages/site/faq.html:535
+msgid "SSH Tunnel"
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:530 i2p2www/pages/site/faq.html:554
+msgid ""
+"Configuring your console to be available on a Public IP address with a "
+"username &amp; password"
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:532
+msgid "These are detailed below:"
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:536
+msgid ""
+"If you are running a Unix-like Operating System, this is the easiest "
+"method for remotely accessing your I2P console. \n"
+"      (Note: SSH server software is available for systems running "
+"Windows, for example <a "
+"href=\"https://github.com/PowerShell/Win32-OpenSSH\">https://github.com/PowerShell/Win32-OpenSSH</a>)"
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:538
+msgid ""
+"Once you have configured SSH access to your system, the '-L' flag is "
+"passed to SSH with appropriate arguments - for example:"
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:556
+msgid "Open <code>~/.i2p/clients.config</code> and replace"
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:570
+msgid ""
+"Go to <a "
+"href=\"http://localhost:7657/configui\">http://localhost:7657/configui</a>"
+" and add a console username and password if desired - \n"
+"        Adding a username &amp; password is highly recommended to secure "
+"your I2P console from tampering, which could lead to de-anonymization."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:572
+msgid ""
+"Go to <a "
+"href=\"http://localhost:7657/index\">http://localhost:7657/index</a> and "
+"hit \"Graceful restart\", \n"
+"        which restarts the JVM and reloads the client applications"
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:575
+msgid ""
+"After that fires up, you should now be able to reach your console "
+"remotely. \n"
+"      Load the router console at <code>http://(System_IP):7657</code> and"
+" you will be prompted for the username and password you specified in step"
+" 2 above if your browser supports the authentication popup."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:578
+msgid ""
+"NOTE: You can specify 0.0.0.0 in the above configuration. \n"
+"      This specifies an interface, not a network or netmask. \n"
+"      0.0.0.0 means \"bind to all interfaces\", so it can be reachable on"
+" 127.0.0.1:7657 as well as any LAN/WAN IP. \n"
+"      Be careful when using this option as the console will be available "
+"on ALL addresses configured on your system."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:587
+msgid ""
+"Please see the previous answer for instructions on using SSH Port "
+"Forwarding, and also see this page in your console: \n"
+"<a "
+"href=\"http://localhost:7657/configi2cp\">http://localhost:7657/configi2cp</a>"
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:595
+msgid ""
+"The SOCKS proxy has been functional since release 0.7.1. SOCKS 4/4a/5 are"
+" supported. \n"
+"I2P does not have a SOCKS outproxy so it is limited to use within I2P "
+"only."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:599
+msgid ""
+"Many applications leak sensitive information that could identify you on "
+"the Internet and this is a risk that one should be aware of when using "
+"the I2P SOCKS proxy. \n"
+"I2P only filters connection data, but if the program you intend to run "
+"sends this information as content, I2P has no way to protect your "
+"anonymity. \n"
+"For example, some mail applications will send the IP address of the "
+"machine they are running on to a mail server. \n"
+"There is no way for I2P to filter this, thus using I2P to 'socksify' "
+"existing applications is possible, but extremely dangerous."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:605
+#, python-format
+msgid ""
+"If you would like more information on the socks proxy application anyway,"
+"\n"
+"there are some helpful hints on the <a href=\"%(socks)s\">socks page</a>."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:613
+msgid ""
+"An I2P router only needs to be seeded once, to join the network for the "
+"first\n"
+"time. Reseeding involves fetching multiple \"RouterInfo\" files (bundled "
+"into a\n"
+"signed zip-file) from at least two predefined server URLs picked from a\n"
+"volunteer-run group of clearnet HTTPS servers."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:620
+msgid ""
+"A typical symptom of a failed reseed is the \"Known\" indicator (on the "
+"left\n"
+"sidebar of the router console) displaying a very small value (often less "
+"than\n"
+"5) which does not increase. This can occur, among other things, if your "
+"local\n"
+"firewall limits outbound traffic or if the reseed request is blocked "
+"entirely."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:627
+msgid ""
+"If you are stuck behind an ISP firewall or filter, you can use the "
+"following\n"
+"manual method (non-automated technical solution) to join the I2P network."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:632
+#, python-format
+msgid ""
+"\n"
+"As of release 0.9.33, you may also configure your router to reseed "
+"through a proxy.\n"
+"Go to <a href=\"%(url)s\">%(url)s</a> and configure the proxy type, "
+"hostname, and port."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:637
+msgid "Joining the I2P Network using a reseed file"
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:638
+msgid ""
+"Please contact a known trustworthy friend who has a running I2P router, "
+"and ask\n"
+"them for help with reseeding your I2P router. Request that they send you "
+"a\n"
+"reseed file exported from their running I2P router. It is vital that the "
+"file is\n"
+"exchanged over a secure channel, e.g. encrypted to avoid external "
+"tampering (PGP\n"
+"Sign, Encrypt and Verified with a trusted public key). The file itself is"
+"\n"
+"unsigned, so please accept files only from known trusted friends. Never "
+"import\n"
+"a reseed file if you can not verify its source."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:648
+#, python-format
+msgid "To import the received %(filename)s file into your local I2P router:"
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:650 i2p2www/pages/site/faq.html:662
+#, python-format
+msgid "Go to <a href=\"%(url)s\">%(url)s</a>"
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:651
+msgid "Under \"Manual Reseed from File\" click \"Browse...\""
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:652
+#, python-format
+msgid "Select the %(filename)s file"
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:653
+msgid "Click \"Reseed from File\""
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:655
+#, python-format
+msgid "Check the <a href=\"%(url)s\">log</a> for the following message:"
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:659
+msgid "Sharing a reseed file"
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:660
+msgid ""
+"For trusted friends you can use your local I2P router to give them a jump"
+" start:"
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:663
+msgid "Under \"Create Reseed File\" click \"Create reseed file\""
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:664
+#, python-format
+msgid "Securely send the %(filename)s file to your friend"
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:666
+msgid ""
+"Do not reveal this file in any case to unknown users, since it contains\n"
+"sensitive private data (100 RouterInfo) from your own I2P router! In "
+"order to\n"
+"protect your anonymity: you may wait a few random hours/days before you "
+"share\n"
+"the file with your trusted friend. It is also advisable to use this "
+"procedure\n"
+"sparingly (< 2 per week)."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:674
+msgid " General guidelines for manual reseeding of I2P "
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:676
+msgid ""
+"Do not publicly publish the reseed file or share these files with a "
+"friend of a friend!"
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:677
+msgid "This file should be used only for a very limited number of friends (< 3)!"
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:678
+msgid "The file is valid only a few days (< 20)!"
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:684
+msgid ""
+"Unless an outproxy has been specifically 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 no SOCKS outproxy. \n"
+"If this type of service is required, we recommend that you use Tor. \n"
+"\n"
+"Please be aware that the Tor project <a "
+"href=\"https://blog.torproject.org/bittorrent-over-tor-isnt-good-"
+"idea\">recommends against using BitTorrent over Tor</a>, \n"
+"as there are serious anonymity-related issues associated with doing so."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:698
+msgid ""
+"Within I2P, there is no requirement to use HTTPS. \n"
+"    All traffic is encrypted end-to-end, any further encryption, e.g. "
+"with the use of HTTPS, doesn't create any further anonymity-related "
+"benefits.\n"
+"\n"
+"    However, if one would like to use HTTPS or has a requirement to do "
+"so, the existing default I2P HTTP Proxy has support for HTTPS traffic."
+"  \n"
+"    Any hidden service operator would have to specifically set up and "
+"enable HTTPS access."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:707
+msgid ""
+"FTP is not supported for technical reasons.\n"
+"\n"
+"    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.\n"
+"\n"
+"    As explained several times above, any existing outproxy isn't a core "
+"part of the network. \n"
+"    They are services run by individuals and they may or may not be "
+"operational at any given time."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:724
+msgid "My router is using a large amount of CPU, what can I do about this?"
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:725
+msgid "There are many possible causes of high CPU usage. Here is a checklist:"
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:730
+msgid "Java Runtime Environment"
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:731
+msgid ""
+"Try to use either OpenJDK or Sun/Oracle Java if it's available for your "
+"system. \n"
+"You can check which version of java you have installed by typing "
+"<code>java -version</code> at a command/shell prompt. \n"
+"Performance tends to suffer with other implementations of java."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:736
+msgid "File sharing applications, e.g. BitTorrent"
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:737
+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:743
+msgid "High bandwidth settings"
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:744
+msgid ""
+"Are your bandwidth limits set too high? It is possible that too much "
+"traffic is going through your I2P router and it is overloaded. \n"
+"Try reducing the setting for <em>share bandwidth percentage</em> on the "
+"<a href=\"http://localhost:7657/config\">configuration</a> page."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:749
+msgid "I2P Version"
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:750
+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:755
+msgid "Memory allocation"
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:756
+msgid ""
+"Has enough memory been set aside for use by I2P? Look at the memory graph"
+" on <a href=\"http://localhost:7657/graphs\">the graphs page</a> \n"
+"to see if the memory usage is \"pegged\"&mdash;the JVM is spending most "
+"of its time in garbage collection. \n"
+"Increase the setting <code>wrapper.java.maxmemory</code> in the file "
+"<code>wrapper.config</code>."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:763
+#, python-format
+msgid "Bursts of high-usage vs. constant 100% usage"
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:764
+msgid ""
+"Is the CPU usage simply higher than you would like, or is it pegged at "
+"100&#37; for a long time?\n"
+"If it is pegged, this could be a bug. Look in the logs for clues."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:770
+msgid "Java-related"
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:771
+#, python-format
+msgid ""
+"You may be using the Java-based BigInteger library instead of the native "
+"version, especially if you are running on a new or unusual OS or hardware"
+" (OpenSolaris, mipsel, etc.).\n"
+"See the <a href=\"%(jbigi)s\">jbigi page</a> for instructions on "
+"diagnosing, building, and testing methods."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:777
+msgid "Participating tunnels"
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:778
+msgid ""
+"If your native jbigi library is working fine, the biggest user of CPU may"
+" be routing traffic for participating tunnels. \n"
+"This uses CPU because at each hop a layer of encryption must be decoded. "
+"You can limit participating traffic in two ways -\n"
+"by reducing the share bandwidth on the <a "
+"href=\"http://localhost:7657/confignet.jsp\">confignet</a> page,\n"
+"or by setting <tt>router.maxParticipatingTunnels=nnn</tt> on the <a "
+"href=\"http://localhost:7657/configadvanced.jsp\">configadvanced</a> "
+"page."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:790
+msgid ""
+"New installations of I2P carry out the reseeding process automatically, "
+"as well as when the number of known peers falls to a drastically low "
+"value. \n"
+"If you need to carry out a reseed of your router, please see the <a "
+"href=\"#manual_reseed\">reseed instructions</a>."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:798
+msgid ""
+"If your router has 10 or more active peers, everything is fine. \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. \n"
+"The amount of bandwidth that is shared by the router can be changed on "
+"the configuration page: \n"
+"  <a "
+"href=\"http://localhost:7657/config\">http://localhost:7657/config</a>"
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:809
+msgid ""
+"No, there isn't anything wrong. \n"
+"This is normal behavior. \n"
+"All routers adjust dynamically to changing network conditions and "
+"demands. \n"
+"Routers come online and go offline depending on whether the system it is "
+"installed on is operational or not, as well as whether there is an "
+"available network connection. \n"
+"Your router is constantly updating its local Network Database. \n"
+"Tunnels which your router is participating in expire every 10 minutes and"
+" may or may not be rebuilt through your router."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:821
+msgid ""
+"The encryption and routing within the I2P network adds a substantial "
+"amount of overhead and limits bandwidth. \n"
+"\n"
+"We can try to clarify this with the aid of a diagram:"
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:829
+msgid ""
+"In this diagram, the path that some I2P traffic takes as it travels "
+"through the network is traced. \n"
+"A user's I2P router is denoted by the box labeled 'A' and an I2P Hidden "
+"Service (for example, the http://stats.i2p website) is labelled as 'B'."
+" \n"
+"Both the client and the server are using 3-hop tunnels, these hops are "
+"represented by the boxes labelled 'P', 'Q', 'R', 'X', 'Y', 'Z', 'P_1', "
+"'Q_1', 'R'_1, 'X_1', 'Y_1' and 'Z_1'."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:835
+msgid ""
+"The boxes labelled 'P', 'Q' and 'R' represent an outbound tunnel for A "
+"while the boxes labelled 'X_1', 'Y_1', 'Z_1' represent an outbound tunnel"
+" for 'B'. \n"
+"Similarly, the boxes labelled 'X', 'Y' and 'Z' represent and inbound "
+"tunnel for 'B' while the boxes labelled 'P_1', 'Q_1' and 'R_1' represent "
+"an inbound tunnel for 'A'. \n"
+"The arrows in between the boxes show the direction of traffic. \n"
+"The text above and below the arrows detail some example bandwidth between"
+" a pair of hops as well as example latencies."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:842
+msgid ""
+"When both client and server are using 3-hop tunnels throughout, a total "
+"of 12 other I2P routers are involved in relaying traffic. \n"
+"6 peers relay traffic from the client to the server which is split into a"
+" 3-hop outbound tunnel from 'A' ('P', 'Q', 'R') and a 3-hop inbound "
+"tunnel to 'B' ('X', 'Y', 'Z').  \n"
+"Similarly, 6 peers relay traffic from the server to back to the client."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:848
+msgid ""
+"First, we can consider latency - the time that it takes for a request "
+"from a client to traverse the I2P network, reach the the server and "
+"traverse back to the client. \n"
+"Adding up all latencies we see that:"
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:862
+msgid ""
+"The total round-trip time in our example adds up to 740 ms - certainly "
+"much higher than what one would normally see while browsing regular "
+"internet websites."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:866
+msgid ""
+"Second, we can consider available bandwidth. \n"
+"This is determined through the slowest link between hops from the client "
+"and server as well as when traffic is being transmitted by the server to "
+"the client. \n"
+"For traffic going from the client to the server, we see that the "
+"available bandwidth in our example between hops 'R' &amp; 'X' as well as "
+"hops 'X' &amp; 'Y' is 32 KB/s. \n"
+"Despite higher available bandwidth between the other hops, these hops "
+"will act as a bottleneck and will limit the maximum available bandwidth "
+"for traffic from 'A' to 'B' at 32 KB/s. \n"
+"Similarly, tracing the path from server to client shows that there is "
+"maximum bandwidth of 64 KB/s - between hops 'Z_1' &amp; 'Y_1, 'Y_1' &amp;"
+" 'X_1' and 'Q_1' &amp; 'P_1'."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:874
+msgid ""
+"We recommend increasing your bandwidth limits. \n"
+"This helps the network by increasing the amount of available bandwidth "
+"which will in turn improve your I2P experience. \n"
+"Bandwidth settings are located on the <a "
+"href=\"http://localhost:7657/config\">http://localhost:7657/config</a> "
+"page. \n"
+"Please be aware of your internet connection's limits as determined by "
+"your ISP, and adjust your settings accordingly."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:881
+msgid ""
+"We also recommend setting a sufficient amount of shared bandwidth - this "
+"allows for participating tunnels to be routed through your I2P router. \n"
+"Allowing participating traffic keeps your router well-integrated in the "
+"network and improves your transfer speeds."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:886
+#, python-format
+msgid ""
+"I2P is a work in progress. Lots of improvements and fixes are being "
+"implemented, and, generally speaking, running the latest release will "
+"help your performance.\n"
+"If you haven't, <a href=\"%(downloadslist)s\">install the latest "
+"release</a>."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:892
+msgid ""
+"In <code>wrapper.log</code> I see an error that states \"<code>Protocol "
+"family unavailable</code>\" when loading the Router Console"
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:894
+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:899
+msgid ""
+"On Linux based systems, you can <code>echo 0 > "
+"/proc/sys/net/ipv6/bindv6only</code>"
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:901
+msgid "Look for the following lines in <code>wrapper.config</code>."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:905
+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:908
+msgid ""
+"Another option would be to remove the <strong>::1</strong> from "
+"<code>~/.i2p/clients.config</code>"
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:912
+msgid ""
+"<strong>WARNING</strong>: For any changes to <code>wrapper.config</code> "
+"to take effect, you must completely\n"
+"stop the router and the wrapper. Clicking <em>Restart</em> on your\n"
+"router console will NOT reread this file! You must\n"
+"click <em>Shutdown</em>, wait 11 minutes, then start I2P."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:922
+#, 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"
+"<a href=\"%(eepstatus)s\">%(eepstatus)s</a> tracks active eepsites."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:930
+msgid "Why is I2P listening on port 32000?"
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:932
+msgid ""
+"The Tanuki java service wrapper that we use opens this port &mdash;bound "
+"to localhost&mdash; in order to communicate with software running inside "
+"the JVM. \n"
+"When the JVM is launched it is given a key so it can connect to the "
+"wrapper. \n"
+"After the JVM establishes its connection to the wrapper, the wrapper "
+"refuses any additional connections."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:937
+msgid ""
+"More information can be found in the <a "
+"href=\"http://wrapper.tanukisoftware.com/doc/english/prop-"
+"port.html\">wrapper documentation</a>."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:944
+msgid ""
+"You may report any bugs/issues that you encounter on our bugtracker, "
+"which is available over both clearnet and I2P. \n"
+"We have a discussion forum, also available on I2P and clearnet. You can "
+"join our IRC channel as well: \n"
+"either through our IRC network, IRC2P, or on Freenode."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:950
+msgid "Our Bugtracker:"
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:952
+msgid "Clearnet:"
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:953
+msgid "On I2P:"
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:955
+msgid "Our forums:"
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:956
+msgid ""
+"You may paste any interesting logs to a paste service such as the "
+"clearnet services listed on the \n"
+"  <a href=\"https://github.com/PrivateBin/PrivateBin/wiki/PrivateBin-"
+"Directory\">PrivateBin Wiki</a>, or an I2P paste service such as this \n"
+"  <a href=\"http://paste.crypthost.i2p\">PrivateBin instance</a> or this"
+" \n"
+"  <a href=\"http://pasta-nojs.i2p\">Javascript-free paste service</a> and"
+" follow up on IRC in #i2p<"
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:960
+msgid "Join #i2p-dev Discuss with the developers on IRC"
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:964
+msgid ""
+"Please include relevant information from the router logs page which is "
+"available at: \n"
+"<a href=\"http://127.0.0.1:7657/logs\">http://127.0.0.1:7657/logs</a>.\n"
+"We request that you share all of the text under the 'I2P Version and "
+"Running Environment' \n"
+"section as well as any errors or warnings displayed in the various logs "
+"displayed on the page."
+msgstr ""
+
+#: i2p2www/pages/site/faq.html:976
+#, python-format
+msgid ""
+"Great! Find us on IRC:\n"
+"<ul>\n"
+"  <li>on <code>irc.freenode.net</code> channel <code>#i2p</code></li>\n"
+"  <li>on <code>IRC2P</code> channel <code>#i2p</code></li>\n"
+"</ul>\n"
+"or post to <a href=\"http://%(forum)s/\">the forum</a> and we'll post it "
+"here (with 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:9
+msgid "What does I2P do for you?"
+msgstr ""
+
+#: i2p2www/pages/site/index.html:10
+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:11
+#, python-format
+msgid "Get I2P %(version)s"
+msgstr ""
+
+#: i2p2www/pages/site/index.html:15
+msgid "What is I2P?"
+msgstr ""
+
+#: i2p2www/pages/site/index.html:17
+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:20
+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:23
+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:26
+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:30
+msgid "Read more&hellip;"
+msgstr ""
+
+#: i2p2www/pages/site/index.html:35
+msgid "What can you do with I2P?"
+msgstr ""
+
+#: i2p2www/pages/site/index.html:38
+#, python-format
+msgid ""
+"<a href=\"%(supported)s#email\">Email:</a> Integrated web mail interface,"
+" plugin for serverless email."
+msgstr ""
+
+#: i2p2www/pages/site/index.html:43
+#, python-format
+msgid ""
+"<a href=\"%(supported)s#web-browsing\">Web browsing:</a> Anonymous "
+"websites, gateways to and from the public Internet."
+msgstr ""
+
+#: i2p2www/pages/site/index.html:48
+#, python-format
+msgid ""
+"<a href=\"%(supported)s#blogging-and-forums\">Blogging and forums:</a> "
+"Blogging and Syndie plugins."
+msgstr ""
+
+#: i2p2www/pages/site/index.html:53
+#, python-format
+msgid ""
+"<a href=\"%(supported)s#website-hosting\">Website hosting:</a> Integrated"
+" anonymous web server."
+msgstr ""
+
+#: i2p2www/pages/site/index.html:58
+#, python-format
+msgid ""
+"<a href=\"%(supported)s#real-time-chat\">Real-time chat:</a> Instant "
+"messaging and IRC clients."
+msgstr ""
+
+#: i2p2www/pages/site/index.html:63
+#, python-format
+msgid ""
+"<a href=\"%(supported)s#file-sharing\">File sharing:</a> ED2K and "
+"Gnutella clients, integrated BitTorrent client."
+msgstr ""
+
+#: i2p2www/pages/site/index.html:68
+#, python-format
+msgid ""
+"<a href=\"%(supported)s#decentralized-file-storage\">Decentralized file "
+"storage:</a> Tahoe-LAFS distributed filesystem plugin."
+msgstr ""
+
+#: i2p2www/pages/site/index.html:73
+#, python-format
+msgid "<a href=\"%(supported)s\"><em>More supported applications&hellip;</em></a>"
+msgstr ""
+
+#: i2p2www/pages/site/index.html:81
+msgid "News &amp; 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"
+"<a href=\"%(media)s\">links to presentations, videos, and tutorials about"
+" I2P</a>."
+msgstr ""
+
+#: i2p2www/pages/site/links.html:12
+msgid "I2P on the web"
+msgstr ""
+
+#: i2p2www/pages/site/links.html:19
+msgid "Friends of I2P"
+msgstr ""
+
+#: i2p2www/pages/site/links.html:33
+msgid "More Projects and Documentation"
+msgstr ""
+
+#: i2p2www/pages/site/links.html:43
+msgid "Press"
+msgstr ""
+
+#: i2p2www/pages/site/links.html:47
+msgid "Boards, newssite, others"
+msgstr ""
+
+#: i2p2www/pages/site/links.html:51
+msgid "Very Old Stuff"
+msgstr ""
+
diff --git a/i2p2www/translations/az/LC_MESSAGES/research.po b/i2p2www/translations/az/LC_MESSAGES/research.po
new file mode 100644
index 00000000..b58bdaf3
--- /dev/null
+++ b/i2p2www/translations/az/LC_MESSAGES/research.po
@@ -0,0 +1,850 @@
+# Azerbaijani translations for I2P.
+# Copyright (C) 2018 ORGANIZATION
+# This file is distributed under the same license as the I2P project.
+#
+# Translators:
+# Nikafn <appone6@gmail.com>, 2018
+msgid ""
+msgstr ""
+"Project-Id-Version:  I2P\n"
+"Report-Msgid-Bugs-To: http://trac.i2p2.de\n"
+"POT-Creation-Date: 2018-06-24 13:48+0000\n"
+"PO-Revision-Date: 2018-06-24 18:44+0000\n"
+"Last-Translator: zzzi2p\n"
+"Language-Team: Azerbaijani "
+"(http://www.transifex.com/otf/I2P/language/az/)\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 1.3\n"
+
+#: i2p2www/pages/site/research/index.html:2
+msgid "Academic Research"
+msgstr "Akademik Araşdırma"
+
+#: i2p2www/pages/site/research/index.html:3
+#: i2p2www/pages/site/research/questions.html:3
+msgid "May 2018"
+msgstr ""
+
+#: i2p2www/pages/site/research/index.html:6
+msgid "Introduction"
+msgstr ""
+
+#: i2p2www/pages/site/research/index.html:8
+msgid "Research on the I2P Network"
+msgstr ""
+
+#: i2p2www/pages/site/research/index.html:10
+msgid ""
+"I2P is a very unique project that unfortunately has not received the "
+"wider\n"
+"academic attention it deserves. To date, most research focus on anonymous"
+" and\n"
+"onion-routing technology has been around Tor, and while those papers "
+"benefit us\n"
+"as well, there is a great need for I2P-focused research. This plays a key"
+" role\n"
+"in both maintaining the security and integrity of the network, as well as"
+"\n"
+"opening doors for more impactful future development."
+msgstr ""
+
+#: i2p2www/pages/site/research/index.html:19
+#, python-format
+msgid ""
+"\n"
+"There is a large research community investigating a wide range of aspects"
+" of\n"
+"anonymity. For a current and comprehensive list of relevant papers, see "
+"the\n"
+"<a href=\"%(anonbib)s\">Free Haven Anonymity Bibliography</a>.\n"
+"I2P benefits from much of the research into Tor and onion routing, but "
+"there is\n"
+"little dedicated research interest into the theory behind I2P, and the "
+"choices\n"
+"and tradeoffs that the network makes. This presents a unique opportunity "
+"for\n"
+"original research.\n"
+msgstr ""
+"\n"
+"Anonimliyin geniş aspektlərini araşdıran böyük araşdırma icması var. "
+"Müvafiq sənədlərin cari və hərtərəfli siyahısı üçün, <a "
+"href=\"%(anonbib)s\">Free Haven Anonymity Bibliography</a>ya baxın.\n"
+"I2P, Tor və \"soğan\" istiqamətləndirici üzərinə araşdırmalardan "
+"yararlanır, ancaq I2P-nin arxasındakı nəzəriyyəni, qərarları və şəbəkənin"
+" səs verməsini araşdırmağa maraq azdır. \n"
+"Bu, orijinal araşdırma üçün unikal imkandır.\n"
+
+#: i2p2www/pages/site/research/index.html:29
+#, python-format
+msgid ""
+"A list of known published papers about I2P is available <a "
+"href=\"%(papers)s\">here</a>."
+msgstr ""
+"Burada I2P haqqında tanınmış məqalələrin siyahısı <a "
+"href=\"%(papers)s\">mövcuddur </a>."
+
+#: i2p2www/pages/site/research/index.html:34
+msgid ""
+"\n"
+"This page aims to outline the most needed fields of research, notes to\n"
+"potential researchers, our general safety guidelines as well as an "
+"expanding\n"
+"list of open questions that you can begin on at any time.\n"
+msgstr ""
+
+#: i2p2www/pages/site/research/index.html:40
+msgid "Notes to Researchers:"
+msgstr ""
+
+#: i2p2www/pages/site/research/index.html:42
+msgid "Defensive Research"
+msgstr ""
+
+#: i2p2www/pages/site/research/index.html:44
+msgid ""
+"While all research on the I2P network is beneficial and appreciated, "
+"there are\n"
+"certain areas which are more in need than others - most so in defensive\n"
+"research. Most people enjoy coming up with fun ways to launch offensives\n"
+"against anonymous software, and this is further reinforced by the "
+"incentives in\n"
+"academic institutions. While we know it is often not the first choice for"
+"\n"
+"researchers, We would certainly appreciate any and all work towards ways "
+"to\n"
+"fortify the network!"
+msgstr ""
+
+#: i2p2www/pages/site/research/index.html:54
+msgid "Offensive and Analytic Tests"
+msgstr ""
+
+#: i2p2www/pages/site/research/index.html:56
+#, python-format
+msgid ""
+"If you've decided on a research topic that aims to hands-on investigate "
+"the I2P\n"
+"network or solve a problem of large proportions we ask you to "
+"<b>please</b> \n"
+"<a href=\"%(contact)s\">communicate your ideas</a> to the development "
+"team, the\n"
+"sooner the better. I2P is under constant development and a significant "
+"amount\n"
+"of roadmapping occurs, therefore your problem may have already been "
+"identified\n"
+"and flagged for update or patch. In the unlikely event you are conducting"
+"\n"
+"testing that overlaps with / would be of interest to another research "
+"project\n"
+"already in motion, we are also able to make you aware of this (with their"
+"\n"
+"permission, of course), and possibly open the door for collaboration. "
+"There is\n"
+"also a chance that the test itself may significantly harm the network or\n"
+"regular users, and the team may have ideas or suggestions to mitigate "
+"that risk\n"
+"and increase the safety of your testing."
+msgstr ""
+
+#: i2p2www/pages/site/research/index.html:71
+msgid "Research Ethics &amp; Testing the Network"
+msgstr ""
+
+#: i2p2www/pages/site/research/index.html:73
+msgid "General Guidelines"
+msgstr ""
+
+#: i2p2www/pages/site/research/index.html:75
+msgid ""
+"<ol>\n"
+"  <li>\n"
+"    Consider the benefits and risks - is there any doubt that the "
+"research\n"
+"    provides more value than danger?\n"
+"  </li>\n"
+"  <li>\n"
+"    If the research can be done on a test network then that is the "
+"preferred\n"
+"    method\n"
+"  </li>\n"
+"  <li>\n"
+"    If you must operate on the live network, the safest route is only\n"
+"    collecting data about yourself\n"
+"  </li>\n"
+"  <li>\n"
+"    If you need 'bigger data', It is recommended to first see if you can "
+"use\n"
+"    data sets from previous experiments or other third party resources is"
+"\n"
+"    recommended\n"
+"  </li>\n"
+"  <li>\n"
+"    If you must collect data on the live network, ensure it is safe for\n"
+"    publication and collect as little as possible\n"
+"  </li>\n"
+"  <li>\n"
+"    After testing and before publish, review that all data which is to be"
+"\n"
+"    published publicly is <b><i>not</i></b> intended to be private by the"
+"\n"
+"    originator\n"
+"  </li>\n"
+"</ol>"
+msgstr ""
+
+#: i2p2www/pages/site/research/index.html:106
+msgid "Using a Test Network to Attack I2P"
+msgstr ""
+
+#: i2p2www/pages/site/research/index.html:108
+msgid ""
+"I2P can be run as a separate test network by controlling the locations "
+"that a\n"
+"new router reseeds from so that it only finds other test routers.\n"
+"\n"
+"The standard mode of operation is to have one JVM per router instance; "
+"hence\n"
+"running multiple copies of I2P on a single machine is inadvisable, both "
+"due to\n"
+"the potential resource drain and the certain port conflicts. To better\n"
+"facilitate setting up small test networks, I2P has a multirouter mode "
+"which\n"
+"enables multiple distinct routers to be run in the same JVM.\n"
+"\n"
+"MultiRouter can be started from the i2p base directory by running the "
+"below\n"
+"command."
+msgstr ""
+
+#: i2p2www/pages/site/research/index.html:124
+msgid ""
+"Additionally, I2P can be started in a virtual network mode. This mode "
+"disables\n"
+"all transports, allowing the router to be tested in isolation without "
+"network\n"
+"traffic. To enable this mode, add <code>i2p.vmCommSystem=true</code> to "
+"the\n"
+"router.config before starting."
+msgstr ""
+
+#: i2p2www/pages/site/research/index.html:131
+msgid "Testing on the Live I2P Network"
+msgstr ""
+
+#: i2p2www/pages/site/research/index.html:133
+#, python-format
+msgid ""
+"As stated above in the researcher notes, please <a "
+"href=\"%(contact)s\">contact\n"
+"  us</a> before you commence your testing. While we do not discourage\n"
+"researchers from responsibly testing their ideas on the live network, if "
+"an\n"
+"attack becomes apparent and we don't have any line of communication then "
+"we\n"
+"will end up taking countermeasures which could interfere with the test."
+msgstr ""
+
+#: i2p2www/pages/site/research/index.html:141
+msgid "Router Family Configuration"
+msgstr "İstiqamətləndiricinin ailə quraşdırması"
+
+#: i2p2www/pages/site/research/index.html:143
+msgid ""
+"As of release 0.9.25, I2P supports a router family configuration. This "
+"provides\n"
+"researchers who run multiple routers with the means to publicly identify "
+"those\n"
+"routers. In turn, this helps the I2P project understand that these "
+"routers are\n"
+"not running an attack on the network. It also will prevent other routers "
+"from\n"
+"including multiple routers of the family in a single tunnel, which could "
+"lead\n"
+"to deanonymization. Routers that appear to be colluding but do not have a"
+"\n"
+"declared family may be assumed to be an attack on the network, and may be"
+"\n"
+"blocked. The best way to ensure the success of your research project is "
+"to work\n"
+"with us directly."
+msgstr ""
+
+#: i2p2www/pages/site/research/index.html:155
+msgid ""
+"A router family shares a private key so that participation in the family "
+"cannot\n"
+"be spoofed. To configure a router family, click on the 'I2P Internals' "
+"link in\n"
+"the router console, and then on the 'Family' tab. Follow the instructions"
+" there\n"
+"to generate the private key for the first router in the family. Then, "
+"export\n"
+"the key from that router, and import it to other members of the family."
+msgstr ""
+
+#: i2p2www/pages/site/research/questions.html:2
+msgid "Open research questions"
+msgstr "Tədqiqatın açıq sualları"
+
+#: i2p2www/pages/site/research/questions.html:5
+msgid "Network database"
+msgstr "Şəbəkə verilənlər bazası"
+
+#: i2p2www/pages/site/research/questions.html:6
+msgid "Floodfills"
+msgstr ""
+
+#: i2p2www/pages/site/research/questions.html:19
+msgid "Transports"
+msgstr "Nəqliyyatlar"
+
+#: i2p2www/pages/site/research/questions.html:31
+msgid "Tunnels and Destinations"
+msgstr "Tunel və istiqamətlər"
+
+#: i2p2www/pages/site/research/questions.html:33
+msgid "Peer selection"
+msgstr "Bənzərlərin seçimi"
+
+#: i2p2www/pages/site/research/questions.html:46
+msgid "Unidirectional tunnels"
+msgstr "Tək istiqamətli tunellər"
+
+#: i2p2www/pages/site/research/questions.html:52
+msgid "Multihoming"
+msgstr "Çoxsaylı ünvan"
+
+#: i2p2www/pages/site/research/questions.html:59
+msgid "Message routing"
+msgstr "İsmarış istiqaməti"
+
+#: i2p2www/pages/site/research/questions.html:66
+msgid "Anonymity"
+msgstr ""
+
+#: i2p2www/pages/site/research/questions.html:75
+msgid "Network Related"
+msgstr ""
+
+#: i2p2www/pages/site/research/vrp.html:2
+msgid "Vulnerability Response Process"
+msgstr "Həssaslığı bildirən proses"
+
+#: i2p2www/pages/site/research/vrp.html:3
+msgid "January 2017"
+msgstr "Yanvar 2017"
+
+#: i2p2www/pages/site/research/vrp.html:6
+msgid ""
+"\n"
+"This process is subject to change. Please refer to this page for the "
+"current VRP."
+msgstr ""
+"\n"
+"Bu proses dəyişdirilə bilər. Mövcud VRP üçün bu səhifəyə baxın."
+
+#: i2p2www/pages/site/research/vrp.html:10
+msgid "Point of Contact for Security Issues"
+msgstr "Təhlükəsizlik məsələləri üzrə təmas nöqtəsi"
+
+#: i2p2www/pages/site/research/vrp.html:14
+msgid "Security Response Team"
+msgstr "Təhlükəsizlik tədbirlər qrupu"
+
+#: i2p2www/pages/site/research/vrp.html:16
+msgid "Only the following members have access to the security point of contact:"
+msgstr ""
+"Yalnız aşağıdakı üzvlər əlaqəli təhlükəsizlik təmas nöqtəsinə daxil ola "
+"bilərlər:"
+
+#: i2p2www/pages/site/research/vrp.html:25
+msgid "Incident Response"
+msgstr "Hadisəyə cavab"
+
+#: i2p2www/pages/site/research/vrp.html:28
+msgid "Researcher submits report via one or both of two methods:"
+msgstr ""
+"Araşdırmaçı hesabatı bir və ya hər iki üsuldan istifadə edərək təqdim "
+"edir:"
+
+#: i2p2www/pages/site/research/vrp.html:32
+msgid "Email"
+msgstr "Email"
+
+#: i2p2www/pages/site/research/vrp.html:37
+msgid ""
+"Response Team designates a Response Manager who is in charge of the "
+"particular\n"
+"report based on availability and/or knowledge-set."
+msgstr ""
+"Cavab qrupu yararlılıq və/ və ya məlumat dəstinə əsaslanan konkret "
+"hesabata cavabdeh müdir təyin edir."
+
+#: i2p2www/pages/site/research/vrp.html:42
+#, python-format
+msgid ""
+"In no more than %(limit)s working days, Response Team should gratefully\n"
+"respond to researcher using only encrypted methods."
+msgstr ""
+"%(limit)siş günündən çox olmamaqla, Response Team \n"
+"yalnız şifrəli üsullardan istifadə edən tədqiqatçıya cavab verir."
+
+#: i2p2www/pages/site/research/vrp.html:47
+msgid ""
+"Response Manager makes inquiries to satisfy any needed information and to"
+"\n"
+"confirm if submission is indeed a vulnerability."
+msgstr ""
+"Cavab meneceri hər hansı zəruri məlumatı təmin etmək üçün sorğu göndərir "
+"və \n"
+"təqdimatın həqiqətən zəiflik olduğunu təsdiqləyir."
+
+#: i2p2www/pages/site/research/vrp.html:52
+msgid "If submission proves to be vulnerable, proceed."
+msgstr "Təqdimatın zəif olduğu təsqilənirsə, davam edin."
+
+#: i2p2www/pages/site/research/vrp.html:55
+msgid "If not vulnerable:"
+msgstr "Zəif deyilsə:"
+
+#: i2p2www/pages/site/research/vrp.html:59
+msgid ""
+"Response Manager responds with reasons why submission is not a "
+"vulnerability."
+msgstr "Cavab meneceri təqdimatın zəif olmadığına dair səbəbləri açıqlayır. "
+
+#: i2p2www/pages/site/research/vrp.html:62
+msgid ""
+"Response Manager moves discussion to a new or existing ticket on public "
+"Trac if necessary."
+msgstr ""
+"Cavab meneceri müzakirəni zəruri hallarda ictimai Trac-da yeni və ya "
+"mövcud biletə keçirir."
+
+#: i2p2www/pages/site/research/vrp.html:70
+msgid ""
+"If over email, Response Manager opens a HackerOne issue for new "
+"submission."
+msgstr ""
+"E-poçt vasitəsilə cavab veribsə, cavab meneceri yeni təqdimat üçün "
+"HackerOne məsələsini açır."
+
+#: i2p2www/pages/site/research/vrp.html:74
+msgid ""
+"\n"
+"Establish severity of vulnerability:\n"
+"  "
+msgstr ""
+"\n"
+"Zəifliyin səviyyəsini müəyyən etmə:"
+
+#: i2p2www/pages/site/research/vrp.html:79
+msgid ""
+"Effects network as a whole, has potential to break entire network or is "
+"on a scale of great catastrophe."
+msgstr ""
+"Effekt şəbəkəsi bütöv bir şəbəkəni pozmaq potensialına malikdir və ya "
+"böyük fəlakət miqyasındadır."
+
+#: i2p2www/pages/site/research/vrp.html:83
+msgid "Effects individual routers, or must be carefully exploited."
+msgstr ""
+"Fərdi istiqamətləndiricilərə təsir edir və ya diqqətlə istismar "
+"edilməlidir."
+
+#: i2p2www/pages/site/research/vrp.html:87
+msgid "Is not easily exploitable."
+msgstr "Asan istifadə edilə bilməz."
+
+#: i2p2www/pages/site/research/vrp.html:93
+msgid "Respond according to the severity of the vulnerability:"
+msgstr "Zəiflik səviyyəsinə uyğun cavab verin:"
+
+#: i2p2www/pages/site/research/vrp.html:97
+#, python-format
+msgid ""
+"HIGH severities must be notified on website and news feed within "
+"%(limit)s\n"
+"working days of classification."
+msgstr ""
+"YÜKSƏK səviyyə veb səhifələrdə və xəbər lentində  %(limit)stəsnifat iş "
+"günləri daxilində bildirilməlidir."
+
+#: i2p2www/pages/site/research/vrp.html:102
+msgid "The notification should list appropriate steps for users to take, if any."
+msgstr "Bildirişdə istifadəçilər üçün müvafiq addımlar göstərilməlidir."
+
+#: i2p2www/pages/site/research/vrp.html:105
+msgid ""
+"The notification must not include any details that could suggest an "
+"exploitation\n"
+"path."
+msgstr ""
+"Bildirişə istismar yolunu təklif edən hər hansı məlumat daxil "
+"edilməməlidir."
+
+#: i2p2www/pages/site/research/vrp.html:109
+msgid "The latter takes precedence over the former."
+msgstr "Sonuncu öncəkindən üstündür."
+
+#: i2p2www/pages/site/research/vrp.html:113
+msgid "MEDIUM and HIGH severities will require a Point Release."
+msgstr "ORTA və YÜKSƏK səviyyə Point Release tələb edəcək."
+
+#: i2p2www/pages/site/research/vrp.html:116
+msgid "LOW severities will be addressed in the next Regular Release."
+msgstr "AŞAĞI səviyyəyə növbəti müntəzəm buraxılışda baxılacaq. "
+
+#: i2p2www/pages/site/research/vrp.html:122
+msgid "Response Team applies appropriate patch(es)."
+msgstr "Cavab qrupu müvafiq yama(lar) tətbiq edir."
+
+#: i2p2www/pages/site/research/vrp.html:126
+msgid ""
+"Response Manager designates a PRIVATE monotone \"hotfix branch\" to work "
+"in."
+msgstr ""
+"Cavab meneceri işləmək üçün ÖZƏL bir monoton \"düzəltmə bölməsi\" təyin "
+"edir."
+
+#: i2p2www/pages/site/research/vrp.html:129
+msgid "Patches are reviewed with the researcher."
+msgstr "Yamalar tədqiqatçı tərəfindən nəzərdən keçirilir."
+
+#: i2p2www/pages/site/research/vrp.html:132
+msgid ""
+"Any messages associated with PUBLIC commits during the time of review "
+"should not\n"
+"make reference to the security nature of the PRIVATE branch or its "
+"commits."
+msgstr ""
+"Baxış zamanı İCTİMAİ ilə əlaqəli hər hansı məlumat ÖZƏL bölmə və ya onun "
+"öhdəlliklərinin \n"
+"təhlükəsizliyinə istinad etməməlidir. "
+
+#: i2p2www/pages/site/research/vrp.html:136
+msgid "Vulnerability announcement is drafted."
+msgstr "Zəiflik elanları hazırlanıb."
+
+#: i2p2www/pages/site/research/vrp.html:140
+msgid "Include severity of vulnerability."
+msgstr "Zəiflik səviyyəsini əlavə edin."
+
+#: i2p2www/pages/site/research/vrp.html:143
+msgid "Include systems/apps effected."
+msgstr "Təsirlənən sistemləri/tətbiqetmələri daxil edin. "
+
+#: i2p2www/pages/site/research/vrp.html:146
+msgid "Include solutions (if any) if patch cannot be applied."
+msgstr "Yamalar tətbiq oluna bilməzsə,(əgər varsa) həll yollarını daxil edin."
+
+#: i2p2www/pages/site/research/vrp.html:150
+msgid "Release date is discussed."
+msgstr "Təqdimat tarixi müzakirə edilir."
+
+#: i2p2www/pages/site/research/vrp.html:156
+msgid ""
+"At release date, Response Team coordinates with developers to finalize "
+"update:"
+msgstr ""
+"Təqdimat tarixində  cavab qrupu yeniləməni yekunlaşdırmaq üçün işi "
+"yaradıcılarla koordinasiya edir."
+
+#: i2p2www/pages/site/research/vrp.html:160
+msgid "Response Manager propagates the \"hotfix branch\" to trunk."
+msgstr "Cavab meneceri \"düzəltmə bölməsi\"ni magistral xəttə yayır. "
+
+#: i2p2www/pages/site/research/vrp.html:163
+msgid ""
+"Response Manager includes vulnerability announcement draft in release "
+"notes."
+msgstr "Cavab meneceri buraxılış qeydlərinə zəiflik elanı layihəsini daxil edir. "
+
+#: i2p2www/pages/site/research/vrp.html:166
+msgid "Proceed with the Point or Regular Release."
+msgstr "Point və ya Regular Release ilə davam edin. "
+
+#: i2p2www/pages/site/research/vrp.html:173
+msgid "Post-release Disclosure Process"
+msgstr "Buraxılışdan sonra açıqlama prosesi"
+
+#: i2p2www/pages/site/research/vrp.html:176
+#, python-format
+msgid "Response Team has %(limit)s days to fulfill all points within section III."
+msgstr ""
+"Cavab qrupunun III hissədəki bütün nöqtələri yerinə yetirmək üçün "
+"%(limit)s günü var."
+
+#: i2p2www/pages/site/research/vrp.html:180
+msgid "If the Incident Response process in section III is successfully completed:"
+msgstr "III bölmədə hadisəyə cavab prosesi uğurla başa çatdıqda:"
+
+#: i2p2www/pages/site/research/vrp.html:184
+msgid ""
+"Response Manager contacts researcher and asks if researcher wishes for "
+"credit."
+msgstr ""
+"Cavab meneceri tədqiqatçı ilə əlaqə qurur və onun kredit istəyib-"
+"istəmədiyini soruşur."
+
+#: i2p2www/pages/site/research/vrp.html:187
+msgid "Finalize vulnerability announcement draft and include the following:"
+msgstr "Zəiflik elanı layihəsini yekunlaşdırın və aşağıdakıları daxil edin:"
+
+#: i2p2www/pages/site/research/vrp.html:191
+msgid "Project name and URL."
+msgstr "Layihənin adı və URL."
+
+#: i2p2www/pages/site/research/vrp.html:194
+msgid "Versions known to be affected."
+msgstr "Təsirə məruz qalan versiyalar."
+
+#: i2p2www/pages/site/research/vrp.html:197
+msgid ""
+"Versions known to be not affected (for example, the vulnerable code was "
+"introduced in a recent version, and older versions are therefore "
+"unaffected)."
+msgstr ""
+"Təsirə məruz qalmayan versiyalar (məsələn, son versiyada zəif kod tətbiq "
+"olundu və bu səbəbdən öncəki versiyalar təsirlənmədi)."
+
+#: i2p2www/pages/site/research/vrp.html:200
+msgid "Versions not checked."
+msgstr "Versiyalar yoxlanmadı."
+
+#: i2p2www/pages/site/research/vrp.html:203
+msgid "Type of vulnerability and its impact."
+msgstr "Zəiflik növü və onun təsiri."
+
+#: i2p2www/pages/site/research/vrp.html:206
+msgid "If already obtained or applicable, a CVE-ID."
+msgstr "Əldə edilmiş və ya tətbiq oluna bilən CVE-ID."
+
+#: i2p2www/pages/site/research/vrp.html:209
+msgid "The planned, coordinated release date."
+msgstr "Planlaşdırılmış, razılaşdırılmış təqdimat tarixi."
+
+#: i2p2www/pages/site/research/vrp.html:212
+msgid ""
+"Mitigating factors (for example, the vulnerability is only exposed in "
+"uncommon, non-default configurations)."
+msgstr ""
+"Azaldıcı amillər (məsələn, zəiflik yalnız qeyri-standart quraşdırmalarda "
+"müşahidə olunur)."
+
+#: i2p2www/pages/site/research/vrp.html:215
+msgid ""
+"Workarounds (configuration changes users can make to reduce their "
+"exposure to the vulnerability)."
+msgstr ""
+"Müvəqqəti həllər (isifadəçilər zəifliyə məruz qalmalarını azaltmaq üçün "
+"quraşdırma dəyişiklikləri edə bilər)."
+
+#: i2p2www/pages/site/research/vrp.html:218
+msgid "If applicable, credits to the original reporter."
+msgstr "Mümkündürsə, əsas müxbirə kredit verin."
+
+#: i2p2www/pages/site/research/vrp.html:223
+msgid "Release finalized vulnerability announcement on website and in news feed."
+msgstr "Vebdə və xəbər lentində yekunlaşdırılmış zəiflik elanının buraxılışı."
+
+#: i2p2www/pages/site/research/vrp.html:226
+msgid ""
+"For HIGH severities, release finalized vulnerability announcement on "
+"well-known mailing lists:"
+msgstr ""
+"YÜKSƏK səviyyə üçün, yekunlaşdırılmış zəiflik elanını tanınan göndəriş "
+"siyahılarına yayın:"
+
+#: i2p2www/pages/site/research/vrp.html:234
+msgid "If applicable, developers request a CVE-ID."
+msgstr "Mümkündürsə, yaradıcılar CVE-ID tələb edir."
+
+#: i2p2www/pages/site/research/vrp.html:238
+msgid ""
+"The commit that applied the fix is made reference too in a future commit "
+"and includes a CVE-ID."
+msgstr ""
+"Düzeltməni tətbiq edən versiya, gələcək fiksasiyada da qeyd olunur və "
+"bura CVE-ID daxildir."
+
+#: i2p2www/pages/site/research/vrp.html:246
+msgid ""
+"If the Incident Response process in section III is *not* successfully "
+"completed:"
+msgstr "III bölmədə hadisəyə cavab prosesi uğurla başa *çatmadıqda*:"
+
+#: i2p2www/pages/site/research/vrp.html:250
+msgid ""
+"Response Team and developers organize an IRC meeting to discuss why/what "
+"points\n"
+"in section III were not resolved and how the team can resolve them in the"
+"\n"
+"future."
+msgstr ""
+"Cavab qrupu və yaradıcılar İİİ bölmədəki niyə/hansı nöqtələrin həll "
+"olunmadığını və gələcəkdə\n"
+" onları necə həll edə biləcəyini müzakirə etmək üçün IRC görüşünü təşkil "
+"edir."
+
+#: i2p2www/pages/site/research/vrp.html:255
+msgid ""
+"Any developer meetings immediately following the incident should include "
+"points\n"
+"made in section V."
+msgstr ""
+"Hadisədən sonra yaradıcıların istənilən görüşü V bölmədəki bəndləri "
+"nəzərə almalıdır."
+
+#: i2p2www/pages/site/research/vrp.html:259
+msgid ""
+"If disputes arise about whether or when to disclose information about a\n"
+"vulnerability, the Response Team will publicly discuss the issue via IRC "
+"and\n"
+"attempt to reach consensus."
+msgstr ""
+"Zəiflik haqqında məlumatın açıqlanması yaxud nə zaman açıqlanması ilə "
+"əlaqədar anlaşılmazlıq \n"
+"yaranarsa, cavab qrupu məsələni İRC vasitəsilə açıq müzakirə edərək, "
+"ortaq məxrəcə gəlməyə\n"
+" çalışacaq."
+
+#: i2p2www/pages/site/research/vrp.html:264
+#, python-format
+msgid ""
+"If consensus on a timely disclosure is not met (no later than %(limit)s "
+"days),\n"
+"the researcher (after %(limit)s days) has every right to expose the\n"
+"vulnerability to the public."
+msgstr ""
+"Əgər vaxtında açıqlama verməyə dair konsensus (%(limit)sgündən gec "
+"olmayaraq) əldə olunmursa, tədqiqatçı (%(limit)sgündən sonra) zəifliyi "
+"ictimaiyyətə açıqlamaq hüququna sahibdir. "
+
+#: i2p2www/pages/site/research/vrp.html:273
+msgid "Incident Analysis"
+msgstr "Hadisənin təhlili"
+
+#: i2p2www/pages/site/research/vrp.html:276
+msgid "Isolate codebase"
+msgstr "Kodbazasını ayırın"
+
+#: i2p2www/pages/site/research/vrp.html:278
+#: i2p2www/pages/site/research/vrp.html:298
+msgid "Response Team and developers should coordinate to work on the following:"
+msgstr ""
+"Cavab qrupu və yaradıcılar işləmək üçün aşağıdakı məsələlərlə bağlı "
+"koordinasiya etməlidirlər:"
+
+#: i2p2www/pages/site/research/vrp.html:282
+msgid "Problematic implementation of classes/libraries/functions, etc."
+msgstr "Siniflərin/ kitabxanaların/funksiyaların və s. problemli tətbiqi "
+
+#: i2p2www/pages/site/research/vrp.html:285
+msgid "Focus on apps/distro packaging, etc."
+msgstr "Tətbiqetmə/distro qablaşdırmaya diqqət edin və s. "
+
+#: i2p2www/pages/site/research/vrp.html:288
+msgid "Operator/config error, etc."
+msgstr "Operator/quraşdırma xətası və s."
+
+#: i2p2www/pages/site/research/vrp.html:296
+msgid "Auditing"
+msgstr "Təftiş"
+
+#: i2p2www/pages/site/research/vrp.html:302
+msgid "Auditing of problem area(s) as discussed in point 1."
+msgstr "1-ci bənddə qeyd edildiyi kimi problemli sahə(lər)in auditi."
+
+#: i2p2www/pages/site/research/vrp.html:305
+msgid "Generate internal reports and store for future reference."
+msgstr "Daxili hesabatlar yaradın və gələcək arayış üçün saxlayın."
+
+#: i2p2www/pages/site/research/vrp.html:308
+msgid ""
+"If results are not sensitive, share with the public via IRC or public "
+"Trac."
+msgstr ""
+"Nəticələr həssas deyilsə, IRC və ya ictimai Trac vasitəsilə ictimaiyyətlə"
+" bölüşün."
+
+#: i2p2www/pages/site/research/vrp.html:316
+#, python-format
+msgid ""
+"Response Team has %(limit)s days following completion of section III to "
+"ensure\n"
+"completion of section V."
+msgstr ""
+"Cavab qrupunun İİİ bölümü bitirdikdən sonra V bölmənin bitməsini təmin "
+"etmək üçün %(limit)s günü var. "
+
+#: i2p2www/pages/site/research/vrp.html:322
+msgid "Resolutions"
+msgstr "Qərarlar"
+
+#: i2p2www/pages/site/research/vrp.html:324
+msgid ""
+"Any further questions or resolutions regarding the incident(s) between "
+"the\n"
+"researcher and response + development team after public disclosure can be"
+"\n"
+"addressed via the following:"
+msgstr ""
+"Tədqiqatçı və cavab + inkişaf qrupu arasında istənilən əlavə suallar və "
+"ya hadisə(lər)lə bağlı qərarlar\n"
+" ictimai açıqlamadan sonra növbəti qaydada həll edilə bilər:"
+
+#: i2p2www/pages/site/research/vrp.html:338
+msgid "Continuous Improvement"
+msgstr "Davamlı inkişaf"
+
+#: i2p2www/pages/site/research/vrp.html:341
+msgid ""
+"Response Team and developers should hold annual meetings to review the "
+"previous\n"
+"year's incidents."
+msgstr ""
+"Cavab qrupu və yaradıcılar əvvəlki illərin hadisələrini nəzərdən keçirmək"
+" üçün illik görüşlər keçirməlidirlər. "
+
+#: i2p2www/pages/site/research/vrp.html:346
+msgid ""
+"Response Team or designated person(s) should give a brief presentation, "
+"including:"
+msgstr ""
+"Cavab qrupu və ya təyin edilmiş şəxs(lər) qısa təqdimat hazırlamalıdır, o"
+" cümlədən: "
+
+#: i2p2www/pages/site/research/vrp.html:350
+msgid "Areas of I2P affected by the incidents."
+msgstr "Hadisələrin təsir etdiyi I2P sahələri."
+
+#: i2p2www/pages/site/research/vrp.html:353
+msgid "Any network downtime or monetary cost (if any) of the incidents."
+msgstr "Hadisələrin istənilən şəbəkə kəsilməsi və ya (varsa) pul xərcləri."
+
+#: i2p2www/pages/site/research/vrp.html:356
+msgid "Ways in which the incidents could have been avoided (if any)."
+msgstr "Hadisələrin qarşısını ala biləcək yollar (əgər varsa)."
+
+#: i2p2www/pages/site/research/vrp.html:359
+msgid "How effective this process was in dealing with the incidents."
+msgstr "Bu proses hadisələrlə mübarizədə nə dərəcədə səmərəli oldu."
+
+#: i2p2www/pages/site/research/vrp.html:365
+msgid "After the presentation, Response Team and developers should discuss:"
+msgstr "Təqdimatdan sonra cavab qrupu və yaradıcılar müzakirə etməlidirlər:"
+
+#: i2p2www/pages/site/research/vrp.html:369
+msgid "Potential changes to development processes to reduce future incidents."
+msgstr ""
+"Gələcək hadisələri azaltmaq üçün inkişaf proseslərinə potensial "
+"dəyişikliklər."
+
+#: i2p2www/pages/site/research/vrp.html:372
+msgid "Potential changes to this process to improve future responses."
+msgstr "Gələcək cavabları yaxşılaşdırmaq üçün bu prosesə potensial dəyişikliklər."
+
diff --git a/i2p2www/translations/et_EE/LC_MESSAGES/docs.po b/i2p2www/translations/et_EE/LC_MESSAGES/docs.po
new file mode 100644
index 00000000..7ae7ef4c
--- /dev/null
+++ b/i2p2www/translations/et_EE/LC_MESSAGES/docs.po
@@ -0,0 +1,16123 @@
+# Estonian (Estonia) translations for I2P.
+# Copyright (C) 2018 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: 2018-08-24 11:47+0000\n"
+"PO-Revision-Date: 2018-08-24 11:51+0000\n"
+"Last-Translator: zzzi2p\n"
+"Language-Team: Estonian (Estonia) "
+"(http://www.transifex.com/otf/I2P/language/et_EE/)\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 1.3\n"
+
+#: i2p2www/pages/site/docs/index.html:2 i2p2www/pages/site/docs/index.html:23
+msgid "Index to Technical Documentation"
+msgstr ""
+
+#: i2p2www/pages/site/docs/index.html:3 i2p2www/pages/site/docs/naming.html:3
+#: i2p2www/pages/site/docs/transport/index.html:3
+#: i2p2www/pages/site/docs/transport/ntcp.html:3
+#: i2p2www/pages/site/docs/transport/ssu.html:3
+msgid "June 2018"
+msgstr ""
+
+#: i2p2www/pages/site/docs/index.html:6
+msgid "Following is an index to the technical documentation for I2P."
+msgstr ""
+
+#: i2p2www/pages/site/docs/index.html:10
+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:17
+#, 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"
+"<a href=\"%(trac)s\">enter a ticket identifying the problem</a>."
+msgstr ""
+
+#: i2p2www/pages/site/docs/index.html:25 i2p2www/pages/site/docs/naming.html:6
+#: i2p2www/pages/site/docs/api/bob.html:42
+#: i2p2www/pages/site/docs/api/i2ptunnel.html:7
+#: i2p2www/pages/site/docs/api/streaming.html:6
+#: i2p2www/pages/site/docs/applications/embedding.html:7
+#: i2p2www/pages/site/docs/applications/managed-clients.html:7
+#: 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:9
+#: i2p2www/pages/site/docs/how/tech-intro.html:93
+#: i2p2www/pages/site/docs/how/tunnel-routing.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:27
+msgid "Technical Introduction"
+msgstr ""
+
+#: i2p2www/pages/site/docs/index.html:28
+msgid "A Less-Technical Introduction"
+msgstr ""
+
+#: i2p2www/pages/site/docs/index.html:29
+msgid "Threat model and analysis"
+msgstr ""
+
+#: i2p2www/pages/site/docs/index.html:30
+msgid "Comparisons to other anonymous networks"
+msgstr ""
+
+#: i2p2www/pages/site/docs/index.html:31
+msgid "Specifications"
+msgstr ""
+
+#: i2p2www/pages/site/docs/index.html:32
+msgid "Protocol stack chart"
+msgstr ""
+
+#: i2p2www/pages/site/docs/index.html:33
+msgid "Papers on I2P"
+msgstr ""
+
+#: i2p2www/pages/site/docs/index.html:34
+msgid "Presentations, articles, tutorials, videos, and interviews"
+msgstr ""
+
+#: i2p2www/pages/site/docs/index.html:35
+#, python-format
+msgid ""
+"<a href=\"%(pdf)s\">Invisible Internet Project (I2P) Project Overview</a>"
+" 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 ""
+
+#: 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
+#: i2p2www/pages/site/docs/applications/managed-clients.html:2
+#: i2p2www/pages/site/docs/applications/managed-clients.html:20
+msgid "Managed Clients"
+msgstr ""
+
+#: i2p2www/pages/site/docs/index.html:45 i2p2www/pages/site/docs/index.html:231
+msgid "Embedding the router in your application"
+msgstr ""
+
+#: i2p2www/pages/site/docs/index.html:46
+#: i2p2www/pages/site/docs/applications/bittorrent.html:2
+msgid "Bittorrent over I2P"
+msgstr ""
+
+#: i2p2www/pages/site/docs/index.html:47
+msgid "I2PControl Plugin API"
+msgstr ""
+
+#: i2p2www/pages/site/docs/index.html:48
+msgid "hostsdb.blockfile Format"
+msgstr ""
+
+#: i2p2www/pages/site/docs/index.html:49 i2p2www/pages/site/docs/index.html:197
+msgid "Configuration File Format"
+msgstr ""
+
+#: i2p2www/pages/site/docs/index.html:52
+msgid "Application Layer API and Protocols"
+msgstr ""
+
+#: i2p2www/pages/site/docs/index.html:53
+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:55
+msgid "Application Development Overview and Guide"
+msgstr ""
+
+#: i2p2www/pages/site/docs/index.html:59
+#: i2p2www/pages/site/docs/api/i2ptunnel.html:51
+msgid "I2PTunnel Configuration"
+msgstr ""
+
+#: i2p2www/pages/site/docs/index.html:75
+msgid "SAM Protocol"
+msgstr ""
+
+#: i2p2www/pages/site/docs/index.html:77
+msgid "SAMv2 Protocol"
+msgstr ""
+
+#: i2p2www/pages/site/docs/index.html:79
+msgid "SAMv3 Protocol"
+msgstr ""
+
+#: i2p2www/pages/site/docs/index.html:81
+msgid "BOB Protocol"
+msgstr ""
+
+#: i2p2www/pages/site/docs/index.html:84
+msgid "End-to-End Transport API and Protocols"
+msgstr ""
+
+#: i2p2www/pages/site/docs/index.html:85
+msgid ""
+"The end-to-end protocols used by clients for reliable and unreliable "
+"communication."
+msgstr ""
+
+#: i2p2www/pages/site/docs/index.html:87
+#: i2p2www/pages/site/docs/api/streaming.html:2
+msgid "Streaming Library"
+msgstr ""
+
+#: i2p2www/pages/site/docs/index.html:89
+msgid "Streaming Protocol Specification"
+msgstr ""
+
+#: i2p2www/pages/site/docs/index.html:91
+msgid "Streaming Javadoc"
+msgstr ""
+
+#: i2p2www/pages/site/docs/index.html:93
+#: i2p2www/pages/site/docs/api/datagrams.html:2
+msgid "Datagrams"
+msgstr ""
+
+#: i2p2www/pages/site/docs/index.html:95
+msgid "Datagram Javadoc"
+msgstr ""
+
+#: i2p2www/pages/site/docs/index.html:98
+msgid "Client-to-Router Interface API and Protocol"
+msgstr ""
+
+#: i2p2www/pages/site/docs/index.html:99
+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:104
+msgid "I2CP - I2P Control Protocol / API overview"
+msgstr ""
+
+#: i2p2www/pages/site/docs/index.html:106
+msgid "I2CP Specification"
+msgstr ""
+
+#: i2p2www/pages/site/docs/index.html:108
+msgid "I2CP API Javadoc"
+msgstr ""
+
+#: i2p2www/pages/site/docs/index.html:110
+#: i2p2www/pages/site/docs/index.html:140
+msgid "Common data structures specification"
+msgstr ""
+
+#: i2p2www/pages/site/docs/index.html:112
+#: i2p2www/pages/site/docs/index.html:142
+msgid "Data Structures Javadoc"
+msgstr ""
+
+#: i2p2www/pages/site/docs/index.html:115
+msgid "End-to-End Encryption"
+msgstr ""
+
+#: i2p2www/pages/site/docs/index.html:116
+msgid "How client messages are end-to-end encrypted by the router."
+msgstr ""
+
+#: i2p2www/pages/site/docs/index.html:118
+msgid "ElGamal/AES+SessionTag encryption"
+msgstr ""
+
+#: i2p2www/pages/site/docs/index.html:119
+#: i2p2www/pages/site/docs/index.html:153
+msgid "ElGamal and AES cryptography details"
+msgstr ""
+
+#: i2p2www/pages/site/docs/index.html:122
+#: i2p2www/pages/site/docs/how/tech-intro.html:11
+#: i2p2www/pages/site/docs/how/tech-intro.html:325
+msgid "Network Database"
+msgstr ""
+
+#: i2p2www/pages/site/docs/index.html:123
+msgid ""
+"Distributed storage and retrieval of information about routers and "
+"clients."
+msgstr ""
+
+#: i2p2www/pages/site/docs/index.html:125
+msgid "Network database overview, details, and threat analysis"
+msgstr ""
+
+#: i2p2www/pages/site/docs/index.html:126
+msgid "Cryptographic hashes"
+msgstr ""
+
+#: i2p2www/pages/site/docs/index.html:127
+msgid "Cryptographic signatures"
+msgstr ""
+
+#: i2p2www/pages/site/docs/index.html:128
+#: i2p2www/pages/site/docs/index.html:189
+msgid "Router reseed specification"
+msgstr ""
+
+#: i2p2www/pages/site/docs/index.html:131
+msgid "Router Message Protocol"
+msgstr ""
+
+#: i2p2www/pages/site/docs/index.html:132
+msgid ""
+"I2P is a message-oriented router. The messages sent between routers are "
+"defined by the I2NP protocol."
+msgstr ""
+
+#: i2p2www/pages/site/docs/index.html:134
+msgid "I2NP - I2P Network Protocol Overview"
+msgstr ""
+
+#: i2p2www/pages/site/docs/index.html:136
+msgid "I2NP Specification"
+msgstr ""
+
+#: i2p2www/pages/site/docs/index.html:138
+msgid "I2NP Javadoc"
+msgstr ""
+
+#: i2p2www/pages/site/docs/index.html:145
+#: i2p2www/pages/site/docs/how/tech-intro.html:10
+#: i2p2www/pages/site/docs/how/tech-intro.html:224
+msgid "Tunnels"
+msgstr "Tunnelid"
+
+#: i2p2www/pages/site/docs/index.html:146
+msgid ""
+"Selecting peers, requesting tunnels through those peers, and encrypting "
+"and routing messages through these tunnels."
+msgstr ""
+
+#: i2p2www/pages/site/docs/index.html:148
+msgid "Peer profiling and selection"
+msgstr ""
+
+#: i2p2www/pages/site/docs/index.html:149
+msgid "Tunnel routing overview"
+msgstr ""
+
+#: i2p2www/pages/site/docs/index.html:150
+msgid "Garlic routing and \"garlic\" terminology"
+msgstr ""
+
+#: i2p2www/pages/site/docs/index.html:151
+msgid "Tunnel building and encryption"
+msgstr ""
+
+#: i2p2www/pages/site/docs/index.html:152
+msgid "ElGamal/AES"
+msgstr ""
+
+#: i2p2www/pages/site/docs/index.html:152
+msgid "for build request encryption"
+msgstr ""
+
+#: i2p2www/pages/site/docs/index.html:154
+msgid "Tunnel building specification"
+msgstr ""
+
+#: i2p2www/pages/site/docs/index.html:155
+msgid "Low-level tunnel message specification"
+msgstr ""
+
+#: i2p2www/pages/site/docs/index.html:156
+#: i2p2www/pages/site/docs/tunnels/unidirectional.html:2
+msgid "Unidirectional Tunnels"
+msgstr ""
+
+#: i2p2www/pages/site/docs/index.html:157
+#: 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:158
+msgid "2009 paper (pdf), not current but still generally accurate"
+msgstr ""
+
+#: i2p2www/pages/site/docs/index.html:161
+msgid "Transport Layer"
+msgstr ""
+
+#: i2p2www/pages/site/docs/index.html:162
+msgid "The protocols for direct (point-to-point) router to router communication."
+msgstr ""
+
+#: i2p2www/pages/site/docs/index.html:164
+msgid "Transport layer overview"
+msgstr ""
+
+#: i2p2www/pages/site/docs/index.html:166
+msgid "TCP-based transport overview and specification"
+msgstr ""
+
+#: i2p2www/pages/site/docs/index.html:168
+msgid "NTCP2 specification"
+msgstr ""
+
+#: i2p2www/pages/site/docs/index.html:170
+msgid "UDP-based transport overview"
+msgstr ""
+
+#: i2p2www/pages/site/docs/index.html:172
+msgid "SSU specification"
+msgstr ""
+
+#: i2p2www/pages/site/docs/index.html:174
+msgid "NTCP transport encryption"
+msgstr ""
+
+#: i2p2www/pages/site/docs/index.html:176
+msgid "SSU transport encryption"
+msgstr ""
+
+#: i2p2www/pages/site/docs/index.html:178
+msgid "Transport Javadoc"
+msgstr ""
+
+#: i2p2www/pages/site/docs/index.html:180
+msgid "NTCP Javadoc"
+msgstr ""
+
+#: i2p2www/pages/site/docs/index.html:182
+msgid "SSU Javadoc"
+msgstr ""
+
+#: i2p2www/pages/site/docs/index.html:185
+msgid "Other Router Topics"
+msgstr ""
+
+#: i2p2www/pages/site/docs/index.html:187
+msgid "Router software updates"
+msgstr ""
+
+#: i2p2www/pages/site/docs/index.html:191
+msgid "Native BigInteger Library"
+msgstr ""
+
+#: i2p2www/pages/site/docs/index.html:193
+msgid "Time synchronization and NTP"
+msgstr ""
+
+#: i2p2www/pages/site/docs/index.html:195
+msgid "Performance"
+msgstr ""
+
+#: i2p2www/pages/site/docs/index.html:202
+msgid "Developer's Guides and Resources"
+msgstr ""
+
+#: i2p2www/pages/site/docs/index.html:204
+msgid "New Developer's Guide"
+msgstr ""
+
+#: i2p2www/pages/site/docs/index.html:206
+msgid "New Translator's Guide"
+msgstr ""
+
+#: i2p2www/pages/site/docs/index.html:208
+msgid "Monotone Guide"
+msgstr ""
+
+#: i2p2www/pages/site/docs/index.html:210
+msgid "Developer Guidelines"
+msgstr ""
+
+#: i2p2www/pages/site/docs/index.html:212
+msgid "Javadocs on the standard internet:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/index.html:213
+#: i2p2www/pages/site/docs/index.html:219
+#: i2p2www/pages/site/docs/index.html:221
+#: i2p2www/pages/site/docs/index.html:223
+#, python-format
+msgid "Server %(num)s"
+msgstr ""
+
+#: i2p2www/pages/site/docs/index.html:214
+#: i2p2www/pages/site/docs/index.html:227
+msgid ""
+"Note: always verify that javadocs are current by checking the release "
+"number."
+msgstr ""
+
+#: i2p2www/pages/site/docs/index.html:216
+msgid "Javadocs inside I2P:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/index.html:229
+msgid "Proposals"
+msgstr ""
+
+#: i2p2www/pages/site/docs/index.html:233
+msgid "How to Set up a Reseed Server"
+msgstr ""
+
+#: i2p2www/pages/site/docs/index.html:235
+msgid "Ports used by I2P"
+msgstr ""
+
+#: i2p2www/pages/site/docs/index.html:237
+msgid "Automatic updates to development builds inside I2P"
+msgstr ""
+
+#: i2p2www/pages/site/docs/index.html:239
+msgid "Updating the wrapper manually"
+msgstr ""
+
+#: i2p2www/pages/site/docs/index.html:241
+msgid "User forum"
+msgstr ""
+
+#: i2p2www/pages/site/docs/index.html:243
+msgid "Developer forum inside I2P"
+msgstr ""
+
+#: i2p2www/pages/site/docs/index.html:245
+msgid "Bug tracker"
+msgstr ""
+
+#: i2p2www/pages/site/docs/index.html:248
+msgid "Viewmtn inside I2P"
+msgstr ""
+
+#: i2p2www/pages/site/docs/index.html:251
+msgid "I2P Source exported to GitHub"
+msgstr ""
+
+#: i2p2www/pages/site/docs/index.html:253
+msgid "I2P Source Git Repo inside I2P"
+msgstr ""
+
+#: i2p2www/pages/site/docs/index.html:255
+msgid "Source translation at Transifex"
+msgstr ""
+
+#: i2p2www/pages/site/docs/index.html:257
+msgid "Roadmap"
+msgstr ""
+
+#: i2p2www/pages/site/docs/index.html:259
+msgid "To Do List"
+msgstr ""
+
+#: i2p2www/pages/site/docs/index.html:259
+msgid "not current"
+msgstr ""
+
+#: i2p2www/pages/site/docs/naming.html:8
+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 <a href=\"#addressbook\">addressbook</a>. \n"
+"I2P also supports <a href=\"#base32\">Base32 hostnames</a> similar to "
+"Tor's .onion addresses."
+msgstr ""
+
+#: i2p2www/pages/site/docs/naming.html:15
+msgid ""
+"The addressbook is a web-of-trust\n"
+"driven secure, distributed, and human readable naming system, sacrificing"
+" only\n"
+"the call for all human readable names to be globally unique by mandating "
+"only\n"
+"local uniqueness.  While all messages in I2P are cryptographically "
+"addressed\n"
+"by their destination, different people can have local addressbook entries"
+" for\n"
+"\"Alice\" which refer to different destinations.  People can still "
+"discover new\n"
+"names by importing published addressbooks of peers specified in their web"
+" of trust,\n"
+"by adding in the entries provided through a third party, or (if some "
+"people organize\n"
+"a series of published addressbooks using a first come first serve "
+"registration\n"
+"system) people can choose to treat these addressbooks as name servers, "
+"emulating\n"
+"traditional DNS."
+msgstr ""
+
+#: i2p2www/pages/site/docs/naming.html:29
+#, python-format
+msgid ""
+"NOTE: For the reasoning behind the I2P naming system, common arguments "
+"against it\n"
+"and possible alternatives see the <a href=\"%(namingdiscussion)s\">naming"
+" discussion</a>\n"
+"page."
+msgstr ""
+
+#: i2p2www/pages/site/docs/naming.html:36
+msgid "Naming System Components"
+msgstr ""
+
+#: i2p2www/pages/site/docs/naming.html:38
+msgid ""
+"There is no central naming authority in I2P.\n"
+"All hostnames are local."
+msgstr ""
+
+#: i2p2www/pages/site/docs/naming.html:43
+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:51
+msgid ""
+"The local <a href=\"#lookup\">naming service</a> which does lookups\n"
+"and also handles <a href=\"#base32\">Base32 hostnames</a>."
+msgstr ""
+
+#: i2p2www/pages/site/docs/naming.html:55
+msgid ""
+"The <a href=\"#httpproxy\">HTTP proxy</a> which asks the router for "
+"lookups and points\n"
+"the user to remote jump services to assist with failed lookups."
+msgstr ""
+
+#: i2p2www/pages/site/docs/naming.html:59
+msgid ""
+"HTTP <a href=\"#add-services\">host-add forms</a> which allow users to "
+"add hosts to their local hosts.txt"
+msgstr ""
+
+#: i2p2www/pages/site/docs/naming.html:62
+msgid ""
+"HTTP <a href=\"#jump-services\">jump services</a> which provide their own"
+" lookups and redirection."
+msgstr ""
+
+#: i2p2www/pages/site/docs/naming.html:65
+msgid ""
+"The <a href=\"#addressbook\">addressbook</a> application which merges "
+"external\n"
+"host lists, retrieved via HTTP, with the local list."
+msgstr ""
+
+#: i2p2www/pages/site/docs/naming.html:69
+msgid ""
+"The <a href=\"#susidns\">SusiDNS</a> 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:76
+msgid "Naming Services"
+msgstr ""
+
+#: i2p2www/pages/site/docs/naming.html:78
+#, 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 3-or-more byte certificate, which in Base64 representation is 516 "
+"or more bytes.\n"
+"Non-null <a href=\"%(namingdiscussion)s#certificates\">Certificates</a> "
+"are in use now\n"
+"for signature type indication.\n"
+"Therefore, certificates in recently-generated destinations are more than "
+"3 bytes."
+msgstr ""
+
+#: i2p2www/pages/site/docs/naming.html:87
+msgid ""
+"If an application (i2ptunnel or the HTTP proxy) wishes to access\n"
+"a destination by name, the router does a very simple local lookup\n"
+"to resolve that name."
+msgstr ""
+
+#: i2p2www/pages/site/docs/naming.html:93
+msgid "Hosts.txt Naming Service"
+msgstr ""
+
+#: i2p2www/pages/site/docs/naming.html:95
+msgid ""
+"The hosts.txt Naming Service does a simple linear search through\n"
+"text files. This naming service was the default until\n"
+"release 0.8.8 when it was replaced by the Blockfile Naming Service.\n"
+"The hosts.txt format had become too slow after the file grew to thousands"
+" of entries."
+msgstr ""
+
+#: i2p2www/pages/site/docs/naming.html:102
+#, python-format
+msgid ""
+"It does a linear search through three local files, in order, to\n"
+"look up host names and convert them to a 516-byte destination key.\n"
+"Each file is in a simple <a href=\"%(configuration)s\">configuration file"
+" format</a>, with hostname=base64, one per line.\n"
+"The files are:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/naming.html:114
+msgid "Blockfile Naming Service"
+msgstr ""
+
+#: i2p2www/pages/site/docs/naming.html:116
+msgid ""
+"The Blockfile Naming Service stores multiple \"addressbooks\" in a single"
+"\n"
+"database file named hostsdb.blockfile.\n"
+"This Naming Service is the default since release 0.8.8."
+msgstr ""
+
+#: i2p2www/pages/site/docs/naming.html:122
+#, python-format
+msgid ""
+"A blockfile is simply on-disk storage of multiple sorted maps (key-value "
+"pairs),\n"
+"implemented as skiplists.\n"
+"The blockfile format is specified on the <a "
+"href=\"%(blockfile)s\">Blockfile page</a>.\n"
+"It provides fast Destination lookup in a compact format. While the "
+"blockfile overhead is substantial,\n"
+"the destinations are stored in binary rather than in Base 64 as in the "
+"hosts.txt format.\n"
+"In addition, the blockfile provides the capability of arbitrary metadata "
+"storage\n"
+"(such as added date, source, and comments) for each entry to implement "
+"advanced addressbook features.\n"
+"The blockfile storage requirement is a modest increase over the hosts.txt"
+" format, and the blockfile provides\n"
+"approximately 10x reduction in lookup times."
+msgstr ""
+
+#: i2p2www/pages/site/docs/naming.html:134
+msgid ""
+"On creation, the naming service imports entries from the three files used"
+" by the hosts.txt Naming Service.\n"
+"The blockfile mimics the previous implementation by maintaining three "
+"maps that\n"
+"are searched in-order, named privatehosts.txt, userhosts.txt, and "
+"hosts.txt.\n"
+"It also maintains a reverse-lookup map to implement rapid reverse lookups."
+msgstr ""
+
+#: i2p2www/pages/site/docs/naming.html:141
+msgid "Other Naming Service Facilities"
+msgstr ""
+
+#: i2p2www/pages/site/docs/naming.html:143
+#, python-format
+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.\n"
+"Lookups are cached for a few minutes.\n"
+"Base 32 resolution is <a href=\"#base32\">described below</a>.\n"
+"For a full description of the Naming Service API see the\n"
+"<a href=\"%(nsjavadocs)s\">Naming Service Javadocs</a>.\n"
+"This API was significantly expanded in release 0.8.7 to provide\n"
+"adds and removes, storage of arbitrary properties with the hostname,\n"
+"and other features."
+msgstr ""
+
+#: i2p2www/pages/site/docs/naming.html:156
+msgid "Alternatives and Experimental Naming Services"
+msgstr ""
+
+#: i2p2www/pages/site/docs/naming.html:158
+#, python-format
+msgid ""
+"The naming service is specified with the configuration property "
+"<tt>i2p.naming.impl=class</tt>.\n"
+"Other implementations are possible. For example,\n"
+"there is an experimental facility for real-time lookups (a la DNS) over "
+"the network within the router.\n"
+"For more information see the <a "
+"href=\"%(namingdiscussion)s#alternatives\">alternatives on the discussion"
+" page</a>."
+msgstr ""
+
+#: i2p2www/pages/site/docs/naming.html:165
+msgid ""
+"The HTTP proxy does a lookup via the router for all hostnames ending in "
+"'.i2p'.\n"
+"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:171
+#, python-format
+msgid ""
+"We have <a href=\"%(i2ptld)s\">applied to reserve the .i2p TLD</a>\n"
+"following the procedures specified in <a href=\"%(rfc6761)s\">RFC "
+"6761</a>."
+msgstr ""
+
+#: i2p2www/pages/site/docs/naming.html:177
+msgid ""
+"If the router fails to resolve the hostname, the HTTP proxy returns\n"
+"an error page to the user with links to several \"jump\" services.\n"
+"See below for details."
+msgstr ""
+
+#: i2p2www/pages/site/docs/naming.html:183
+msgid "Addressbook"
+msgstr "Aadressiraamat"
+
+#: i2p2www/pages/site/docs/naming.html:184
+msgid "Incoming Subscriptions and Merging"
+msgstr ""
+
+#: i2p2www/pages/site/docs/naming.html:186
+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:194
+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:202
+msgid ""
+"For this reason, the only subscription configured by\n"
+"default is <code>http://i2p-projekt.i2p/hosts.txt "
+"(http://udhdrtrcetjm5sxzskjyr5ztpeszydbh4dpl3pl4utgqqw2v4jna.b32.i2p/hosts.txt)</code>,"
+" \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 <a "
+"href=\"#susidns\">SusiDNS</a>)."
+msgstr ""
+
+#: i2p2www/pages/site/docs/naming.html:211
+msgid "Some other public addressbook subscription links:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/naming.html:218
+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:223
+#: i2p2www/pages/site/docs/naming.html:235
+msgid "Naming Rules"
+msgstr ""
+
+#: i2p2www/pages/site/docs/naming.html:224
+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:239
+msgid "Names are converted to lower case on import."
+msgstr ""
+
+#: i2p2www/pages/site/docs/naming.html:243
+msgid ""
+"Names are checked for conflict with existing names in the existing "
+"userhosts.txt and hosts.txt\n"
+"(but not privatehosts.txt) after conversion to lower case."
+msgstr ""
+
+#: i2p2www/pages/site/docs/naming.html:248
+msgid "Must contain only [a-z] [0-9] '.' and '-' after conversion to lower case."
+msgstr ""
+
+#: i2p2www/pages/site/docs/naming.html:252
+msgid "Must not start with '.' or '-'."
+msgstr ""
+
+#: i2p2www/pages/site/docs/naming.html:256
+msgid "Must end with '.i2p'."
+msgstr ""
+
+#: i2p2www/pages/site/docs/naming.html:260
+msgid "67 characters maximum, including the '.i2p'."
+msgstr ""
+
+#: i2p2www/pages/site/docs/naming.html:264
+msgid "Must not contain '..'."
+msgstr ""
+
+#: i2p2www/pages/site/docs/naming.html:268
+msgid "Must not contain '.-' or '-.' (as of 0.6.1.33)."
+msgstr ""
+
+#: i2p2www/pages/site/docs/naming.html:272
+msgid "Must not contain '--' except in 'xn--' for IDN."
+msgstr ""
+
+#: i2p2www/pages/site/docs/naming.html:276
+msgid ""
+"Base32 hostnames (*.b32.i2p) are reserved for base 32 use and so are not "
+"allowed to be imported."
+msgstr ""
+
+#: i2p2www/pages/site/docs/naming.html:280
+msgid ""
+"Certain hostnames reserved for project use are not allowed\n"
+"(proxy.i2p, router.i2p, console.i2p, *.proxy.i2p, *.router.i2p, "
+"*.console.i2p, and others)"
+msgstr ""
+
+#: i2p2www/pages/site/docs/naming.html:285
+msgid "Keys are checked for base64 validity."
+msgstr ""
+
+#: i2p2www/pages/site/docs/naming.html:289
+msgid ""
+"Keys are checked for conflict with existing keys in hosts.txt (but not "
+"privatehosts.txt)."
+msgstr ""
+
+#: i2p2www/pages/site/docs/naming.html:293
+msgid "Minimum key length 516 bytes."
+msgstr ""
+
+#: i2p2www/pages/site/docs/naming.html:297
+msgid "Maximum key length 616 bytes (to account for certs up to 100 bytes)."
+msgstr ""
+
+#: i2p2www/pages/site/docs/naming.html:302
+msgid ""
+"Any name received via subscription that passes all the checks is added "
+"via the local naming service."
+msgstr ""
+
+#: i2p2www/pages/site/docs/naming.html:306
+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:317
+msgid ""
+"International Domain Names (IDN) also work in i2p (using punycode 'xn--' "
+"form).\n"
+"To see IDN .i2p domain names rendered correctly in Firefox's location "
+"bar,\n"
+"add 'network.IDN.whitelist.i2p (boolean) = true' in about:config."
+msgstr ""
+
+#: i2p2www/pages/site/docs/naming.html:323
+msgid ""
+"As the addressbook application does not use privatehosts.txt at all, in "
+"practice\n"
+"this file is the only place where it is appropriate to place private "
+"aliases or\n"
+"\"pet names\" for sites already in hosts.txt."
+msgstr ""
+
+#: i2p2www/pages/site/docs/naming.html:329
+msgid "Advanced Subscription Feed Format"
+msgstr ""
+
+#: i2p2www/pages/site/docs/naming.html:337
+msgid "Outgoing Subscriptions"
+msgstr ""
+
+#: i2p2www/pages/site/docs/naming.html:338
+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:346
+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:353
+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:358
+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:367
+msgid "Host Add Services"
+msgstr ""
+
+#: i2p2www/pages/site/docs/naming.html:368
+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:375
+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:380
+msgid "A limit on number of 'subdomains'."
+msgstr ""
+
+#: i2p2www/pages/site/docs/naming.html:384
+msgid "Authorization for 'subdomains' through various methods."
+msgstr ""
+
+#: i2p2www/pages/site/docs/naming.html:388
+msgid "Hashcash or signed certificates."
+msgstr ""
+
+#: i2p2www/pages/site/docs/naming.html:392
+msgid "Editorial review of host names and/or content."
+msgstr ""
+
+#: i2p2www/pages/site/docs/naming.html:396
+msgid "Categorization of hosts by content."
+msgstr ""
+
+#: i2p2www/pages/site/docs/naming.html:400
+msgid "Reservation or rejection of certain host names."
+msgstr ""
+
+#: i2p2www/pages/site/docs/naming.html:404
+msgid "Restrictions on the number of names registered in a given time period."
+msgstr ""
+
+#: i2p2www/pages/site/docs/naming.html:408
+msgid "Delays between registration and publication."
+msgstr ""
+
+#: i2p2www/pages/site/docs/naming.html:412
+msgid "Requirement that the host be up for verification."
+msgstr ""
+
+#: i2p2www/pages/site/docs/naming.html:416
+msgid "Expiration and/or revocation."
+msgstr ""
+
+#: i2p2www/pages/site/docs/naming.html:420
+msgid "IDN spoof rejection."
+msgstr ""
+
+#: i2p2www/pages/site/docs/naming.html:425
+msgid "Jump Services"
+msgstr ""
+
+#: i2p2www/pages/site/docs/naming.html:426
+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 "
+"<code>?i2paddresshelper=key</code>\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:436
+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:442
+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:448
+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:454
+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:460
+msgid "Base32 Names"
+msgstr ""
+
+#: i2p2www/pages/site/docs/naming.html:461
+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: "
+"<code>ukeu3k5oycgaauneqgtnvselmt4yemvoilkln7jpvamvfx7dnkdq.b32.i2p</code>"
+msgstr ""
+
+#: i2p2www/pages/site/docs/naming.html:468
+#, python-format
+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"
+"Tor has recently published a\n"
+"<a href=\"https://blog.torproject.org/blog/tor-weekly-news-%E2%80%94"
+"-december-4th-2013\">proposal</a>\n"
+"to convert to an identical format of {52 chars}.onion for their hidden "
+"services.\n"
+"Base32 is implemented in the naming service, which queries the\n"
+"router over I2CP to lookup the LeaseSet to get the full Destination.\n"
+"Base32 lookups will only be successful when the Destination is up and "
+"publishing\n"
+"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:483
+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
+msgid "Plugins"
+msgstr ""
+
+#: i2p2www/pages/site/docs/plugins.html:3
+msgid "June 2012"
+msgstr ""
+
+#: i2p2www/pages/site/docs/plugins.html:6
+msgid "General Information"
+msgstr ""
+
+#: i2p2www/pages/site/docs/plugins.html:7
+msgid ""
+"I2P includes a plugin architecture\n"
+"to support easy development and installation of additional software."
+msgstr ""
+
+#: i2p2www/pages/site/docs/plugins.html:12
+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:17
+msgid "Benefits to i2p users and app developers:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/plugins.html:22
+msgid "Easy distribution of applications"
+msgstr ""
+
+#: i2p2www/pages/site/docs/plugins.html:26
+msgid ""
+"Allows innovation and use of additional libraries without worrying about\n"
+"increasing the size of <code>i2pupdate.sud</code>"
+msgstr ""
+
+#: i2p2www/pages/site/docs/plugins.html:31
+msgid ""
+"Support large or special-purpose applications that would never be bundled"
+"\n"
+"with the I2P installation"
+msgstr ""
+
+#: i2p2www/pages/site/docs/plugins.html:36
+msgid "Cryptographically signed and verified applications"
+msgstr ""
+
+#: i2p2www/pages/site/docs/plugins.html:40
+msgid "Automatic updates of applications, just like for the router"
+msgstr ""
+
+#: i2p2www/pages/site/docs/plugins.html:44
+msgid ""
+"Separate initial install and update packages, if desired, for smaller "
+"update downloads"
+msgstr ""
+
+#: i2p2www/pages/site/docs/plugins.html:48
+msgid ""
+"One-click installation of applications. No more asking users to modify\n"
+"<code>wrapper.config</code> or <code>clients.config</code>"
+msgstr ""
+
+#: i2p2www/pages/site/docs/plugins.html:53
+msgid "Isolate applications from the base <code>$I2P</code> installation"
+msgstr ""
+
+#: i2p2www/pages/site/docs/plugins.html:57
+msgid ""
+"Automatic compatibility checking for I2P version, Java version, Jetty\n"
+"version, and previous installed application version"
+msgstr ""
+
+#: i2p2www/pages/site/docs/plugins.html:62
+msgid "Automatic link addition in console"
+msgstr ""
+
+#: i2p2www/pages/site/docs/plugins.html:66
+msgid ""
+"Automatic startup of application, including modifying classpath, without "
+"requiring a restart"
+msgstr ""
+
+#: i2p2www/pages/site/docs/plugins.html:70
+msgid "Automatic integration and startup of webapps into console Jetty instance"
+msgstr ""
+
+#: i2p2www/pages/site/docs/plugins.html:74
+#, python-format
+msgid ""
+"Facilitate creation of 'app stores' like the one at\n"
+"<a href=\"http://%(pluginsite)s\">%(pluginsite)s</a>"
+msgstr ""
+
+#: i2p2www/pages/site/docs/plugins.html:79
+msgid "One-click uninstall"
+msgstr ""
+
+#: i2p2www/pages/site/docs/plugins.html:83
+msgid "Language and theme packs for the console"
+msgstr ""
+
+#: i2p2www/pages/site/docs/plugins.html:87
+msgid "Bring detailed application information to the router console"
+msgstr ""
+
+#: i2p2www/pages/site/docs/plugins.html:91
+msgid "Non-java applications also supported"
+msgstr ""
+
+#: i2p2www/pages/site/docs/plugins.html:97
+msgid "Required I2P version"
+msgstr ""
+
+#: i2p2www/pages/site/docs/plugins.html:98
+msgid "0.7.12 or newer."
+msgstr ""
+
+#: i2p2www/pages/site/docs/plugins.html:100
+msgid "Installation"
+msgstr ""
+
+#: i2p2www/pages/site/docs/plugins.html:101
+msgid ""
+"To install and start a plugin, copy the <code>.xpi2p</code> install link "
+"to\n"
+"the form at the bottom of\n"
+"<a "
+"href=\"http://127.0.0.1:7657/configclients.jsp#plugin\">configclients.jsp"
+" in\n"
+"your router console</a> and click the \"install plugin\" button.  After a"
+"\n"
+"plugin is installed and started, a link to the plugin will usually appear"
+" at\n"
+"the top of your summary bar."
+msgstr ""
+
+#: i2p2www/pages/site/docs/plugins.html:110
+msgid ""
+"To update a plugin to the latest version, just click the update button on"
+"\n"
+"<a "
+"href=\"http://127.0.0.1:7657/configclients.jsp#plugin\">configclients.jsp</a>."
+"\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:120
+msgid "Development"
+msgstr ""
+
+#: i2p2www/pages/site/docs/plugins.html:121
+#, python-format
+msgid ""
+"See the latest <a href=\"%(pluginspec)s\">plugin specification</a> and "
+"the\n"
+"<a href=\"http://%(zzz)s/forums/16\">plugin forum</a> on %(zzz)s."
+msgstr ""
+
+#: i2p2www/pages/site/docs/plugins.html:126
+#, python-format
+msgid ""
+"See also the sources for plugins developed by various people.  Some "
+"plugins, such\n"
+"as <a href=\"http://%(pluginsite)s/plugins/snowman\">snowman</a>, were "
+"developed\n"
+"specifically as examples."
+msgstr ""
+
+#: i2p2www/pages/site/docs/plugins.html:132
+msgid ""
+"<b>Developers wanted!</b> Plugins are a great way to learn more about I2P"
+"\n"
+"or easily add some feature."
+msgstr ""
+
+#: i2p2www/pages/site/docs/plugins.html:137
+msgid "Getting Started"
+msgstr ""
+
+#: i2p2www/pages/site/docs/plugins.html:138
+#, python-format
+msgid ""
+"To create a plugin from an existing binary package you will need to get\n"
+"makeplugin.sh from <a href=\"%(url)s\">the i2p.scripts branch in "
+"monotone</a>."
+msgstr ""
+
+#: i2p2www/pages/site/docs/plugins.html:144
+msgid "Known Issues"
+msgstr ""
+
+#: i2p2www/pages/site/docs/plugins.html:145
+msgid ""
+"Note that the router's plugin architecture does <b>NOT</b> currently\n"
+"provide any additional security isolation or sandboxing of plugins."
+msgstr ""
+
+#: i2p2www/pages/site/docs/plugins.html:151
+msgid ""
+"Updates of a plugin with included jars (not wars) won't be recognized if\n"
+"the plugin was already run, as it requires class loader trickery to flush"
+" the\n"
+"class cache; a full router restart is required."
+msgstr ""
+
+#: i2p2www/pages/site/docs/plugins.html:157
+msgid "The stop button may be displayed even if there is nothing to stop."
+msgstr ""
+
+#: i2p2www/pages/site/docs/plugins.html:161
+msgid ""
+"Plugins running in a separate JVM create a <code>logs/</code> directory "
+"in\n"
+"<code>$CWD</code>."
+msgstr ""
+
+#: i2p2www/pages/site/docs/plugins.html:166
+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&mdash;there is no signing key authority."
+msgstr ""
+
+#: i2p2www/pages/site/docs/plugins.html:172
+msgid ""
+"When deleting a plugin, the directory is not always deleted, especially "
+"on\n"
+"Windows."
+msgstr ""
+
+#: i2p2www/pages/site/docs/plugins.html:177
+msgid ""
+"Installing a plugin requiring Java 1.6 on a Java 1.5 machine will result "
+"in a\n"
+"\"plugin is corrupt\" message if pack200 compression of the plugin file "
+"is used."
+msgstr ""
+
+#: i2p2www/pages/site/docs/plugins.html:182
+msgid "Theme and translation plugins are untested."
+msgstr ""
+
+#: i2p2www/pages/site/docs/plugins.html:186
+msgid "Disabling autostart doesn't always work."
+msgstr ""
+
+#: i2p2www/pages/site/docs/ports.html:2
+msgid "Ports Used by I2P"
+msgstr ""
+
+#: i2p2www/pages/site/docs/ports.html:3
+msgid "March 2018"
+msgstr ""
+
+#: 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 <a href=\"%(faq)s#ports\">the FAQ</a>.\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:56
+msgid "recommended spot for new plugins/applications"
+msgstr ""
+
+#: i2p2www/pages/site/docs/reseed.html:2
+msgid "Reseed Hosts"
+msgstr ""
+
+#: i2p2www/pages/site/docs/reseed.html:3
+#: i2p2www/pages/site/docs/how/elgamal-aes.html:3
+msgid "January 2016"
+msgstr ""
+
+#: i2p2www/pages/site/docs/reseed.html:8
+msgid "About Reseed hosts"
+msgstr ""
+
+#: i2p2www/pages/site/docs/reseed.html:10
+msgid ""
+"Reseed hosts are needed to for bootstrapping, that is, providing the "
+"initial set of I2P nodes for your I2P node to talk to. Depending on the "
+"status of your node it may need to bootstrap every now and then if many "
+"of the nodes it knows of aren't contactable."
+msgstr ""
+
+#: i2p2www/pages/site/docs/reseed.html:14
+msgid ""
+"Reseeding is done over an encrypted connection and all of the bootstrap "
+"information is signed by the reseed host you connect to, making it "
+"impossible for an unauthenticated source to provide you with false "
+"information."
+msgstr ""
+
+#: i2p2www/pages/site/docs/reseed.html:19
+msgid "Running a Reseed host"
+msgstr ""
+
+#: i2p2www/pages/site/docs/reseed.html:21
+msgid ""
+"The more reseed hosts that are run, the more resilient the I2P network "
+"becomes, and the harder it is to prevent users of I2P from connecting to "
+"the network."
+msgstr ""
+
+#: i2p2www/pages/site/docs/reseed.html:25
+msgid ""
+"There have also been cases where the reseed hosts we had, have been under"
+" heavy load due to botnet activities."
+msgstr ""
+
+#: i2p2www/pages/site/docs/reseed.html:33
+msgid "Thank you"
+msgstr ""
+
+#: i2p2www/pages/site/docs/reseed.html:35
+msgid ""
+"If you are running a reseed server, We would like to thank you for "
+"helping to\n"
+"make the I2P network stronger and more resilient than ever."
+msgstr ""
+
+#: i2p2www/pages/site/docs/reseed.html:41
+msgid "Thank you."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/bob.html:2
+msgid "BOB - Basic Open Bridge"
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/bob.html:3
+msgid "August 2016"
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/bob.html:12
+msgid "Technical differences from SAM (for the better?)"
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/bob.html:14
+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:23
+msgid ""
+"SAM has one connection that does everything, and you need to parse every "
+"packet."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/bob.html:27
+msgid ""
+"BOB does not hold keypair values, nor does the router.\n"
+"Your application holds the keypair values. \n"
+"This is to reduce any extra complexity in the router code, it also adds "
+"to\n"
+"your privacy."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/bob.html:34
+msgid "SAM router stores every keypair you ever make."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/bob.html:38
+msgid "Those are the important differences."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/bob.html:44
+msgid "<code>KEYS</code> = keypair public+private, these are BASE64"
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/bob.html:47
+msgid "<code>KEY</code> = public key, also BASE64"
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/bob.html:50
+msgid ""
+"<code>ERROR</code> as is implied returns the message <code>\"ERROR "
+"\"+DESCRIPTION+\"\\n\"</code>, where the <code>DESCRIPTION</code> is what"
+" went wrong."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/bob.html:53
+msgid ""
+"<code>OK</code> returns <code>\"OK\"</code>, and if data is to be "
+"returned, it is on the same line. <code>OK</code> means the command is "
+"finished."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/bob.html:56
+msgid ""
+"<code>DATA</code> lines contain information that you requested. There may"
+" be multiple <code>DATA</code> lines per request."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/bob.html:60
+msgid ""
+"<b>NOTE:</b> 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:66
+msgid "Connection and Version"
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/bob.html:68
+msgid ""
+"All BOB status output is by lines. Lines may be \\n or \\r\\n terminated,"
+" depending on the system.\n"
+"On connection, BOB outputs two lines:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/bob.html:78
+msgid "The current version is:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/bob.html:82
+msgid ""
+"Note that previous versions used upper-case hex digits and did not "
+"conform to I2P versioning standards.\n"
+"It is recommended that subsequent versions use digits 0-9 only."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/bob.html:87
+msgid "Version history"
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/bob.html:92
+msgid "Version"
+msgstr "Versioon"
+
+#: i2p2www/pages/site/docs/api/bob.html:93
+msgid "I2P Router Version"
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/bob.html:94
+msgid "Changes"
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/bob.html:97
+msgid "current version"
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/bob.html:100
+msgid "development versions"
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/bob.html:104
+msgid "Commands"
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/bob.html:106
+msgid ""
+"<b>PLEASE NOTE:</b>\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:112
+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:117
+msgid "COMMAND"
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/bob.html:117
+msgid "OPERAND"
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/bob.html:117
+msgid "RETURNS"
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/bob.html:145
+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:152
+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:164
+msgid "Examples"
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/bob.html:166
+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:174
+msgid "EXAMPLE SESSION DIALOGUE -- simple telnet 127.0.0.1 2827 works"
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/bob.html:175
+msgid "Application"
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/bob.html:176
+msgid "BOB's Command response."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/bob.html:178
+#: i2p2www/pages/site/docs/api/bob.html:192
+#: i2p2www/pages/site/docs/api/bob.html:212
+#: i2p2www/pages/site/docs/api/bob.html:322
+#: i2p2www/pages/site/docs/api/bob.html:334
+#: i2p2www/pages/site/docs/api/bob.html:349
+msgid "FROM"
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/bob.html:178
+#: i2p2www/pages/site/docs/api/bob.html:192
+#: i2p2www/pages/site/docs/api/bob.html:212
+#: i2p2www/pages/site/docs/api/bob.html:322
+#: i2p2www/pages/site/docs/api/bob.html:334
+#: i2p2www/pages/site/docs/api/bob.html:349
+msgid "TO"
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/bob.html:178
+#: i2p2www/pages/site/docs/api/bob.html:192
+#: i2p2www/pages/site/docs/api/bob.html:212
+#: i2p2www/pages/site/docs/api/bob.html:322
+#: i2p2www/pages/site/docs/api/bob.html:334
+#: i2p2www/pages/site/docs/api/bob.html:349
+msgid "DIALOGUE"
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/bob.html:187
+msgid "MAKE NOTE OF THE ABOVE DESTINATION KEY, YOURS WILL BE DIFFERENT!"
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/bob.html:201
+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 <code>CHARGEN</code> service on <code>19/TCP</code>."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/bob.html:207
+msgid "Now for the other half, so that we can actually contact this destination."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/bob.html:229
+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:236
+msgid ""
+"<b>NOTE:</b> The \"quit\" command in the command channel does NOT "
+"disconnect the tunnels like SAM."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/bob.html:253
+msgid "After a few virtual miles of this spew, press <code>Control-]</code>"
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/bob.html:265
+msgid "Here is what happened..."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/bob.html:273
+msgid "You can connect to EEPSITES too!"
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/bob.html:306
+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:313
+msgid "Let's put down our destinations now that we are all done with them."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/bob.html:317
+msgid "First, lets see what destination nicknames we have."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/bob.html:329
+msgid "Alright, there they are. First, let's remove \"mouth\"."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/bob.html:343
+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:362
+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:368
+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:375
+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:384
+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:3
+#: i2p2www/pages/site/docs/protocol/index.html:3
+msgid "August 2010"
+msgstr ""
+
+#: 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 <a href=\"%(i2cp)s\">I2CP</a> 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 <a href=\"%(streaming)s\">streaming library packets</a>,\n"
+"are an application-level construct.\n"
+"These protocols are independent of the low-level <a "
+"href=\"%(transports)s\">transports</a>;\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 ""
+
+#: i2p2www/pages/site/docs/api/datagrams.html:26
+#, python-format
+msgid ""
+"Applications written in Java may use the \n"
+"<a href=\"%(url)s\">datagram API</a>,\n"
+"while applications in other languages \n"
+"can use <a href=\"%(sam)s\">SAM</a>'s datagram support.\n"
+"There is also limited support in i2ptunnel in the <a "
+"href=\"%(socks)s\">SOCKS proxy</a>,\n"
+"the 'streamr' tunnel types, and udpTunnel classes."
+msgstr ""
+
+#: 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 ""
+
+#: 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"
+"<a href=\"%(elgamalaes)s\">ElGamal/AES</a>, 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 <a href=\"%(i2cp)s#format\">I2CP page</a>."
+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"
+"<a href=\"%(i2psession)s\">I2PSession API</a>\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"
+"<a href=\"%(i2psession)s\">I2PSession API</a>,\n"
+"as implemented in\n"
+"<a href=\"%(i2psessionmuxed)s\">I2PSessionMuxedImpl</a>."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/datagrams.html:93
+#: i2p2www/pages/site/docs/api/streaming.html:418
+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"
+"<a href=\"%(i2cp)s#format\">the I2CP layer</a>.\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:426
+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"
+"<a href=\"%(garlicrouting)s\">Garlic Message</a>).\n"
+"Message encapsulation is implemented in the underlying\n"
+"<a href=\"%(i2cp)s\">I2CP</a>,\n"
+"<a href=\"%(i2np)s\">I2NP</a>, and\n"
+"<a href=\"%(tunnelmessage)s\">tunnel message</a> 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/transport/ssu.html:650
+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:2
+msgid "I2PControl - Remote Control Service"
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:5
+#, python-format
+msgid ""
+"I2P enables a <a href=\"http://en.wikipedia.org/wiki/JSON-"
+"RPC\">JSONRPC2</a> interface via the plugin <a "
+"href=\"%(itoopie)s\">I2PControl</a>.\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 <a href=\"http://software.dzhuvinov.com"
+"/json-rpc-2.0.html\">JSON-RPC 2.0</a>.  \n"
+"A list of implementations of JSON-RPC for various languages can be found "
+"at <a href=\"http://json-rpc.org/wiki/implementations\">the JSON-RPC "
+"wiki</a>."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:12
+msgid "I2PControl is by default listening on https://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:20
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:45
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:58
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:68
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:77
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:87
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:102
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:155
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:176
+msgid "Request:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:33
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:50
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:62
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:72
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:82
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:93
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:119
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:165
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:191
+msgid "Response:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:44
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:46
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:47
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:51
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:52
+#: i2p2www/pages/site/docs/protocol/i2cp.html:108
+#: i2p2www/pages/site/docs/protocol/i2cp.html:483
+msgid "Description"
+msgstr "Kirjeldus"
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:48
+msgid ""
+"Token used for authenticating every request (excluding the 'Authenticate'"
+" RPC method)"
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:56
+msgid "Implemented methods"
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:57
+msgid ""
+"Creates and returns an authentication token used for further "
+"communication."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:59
+msgid "The version of the I2PControl API used by the client."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:60
+msgid "The password used for authenticating against the remote server."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:63
+msgid "The primary I2PControl API version implemented by the server."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:64
+msgid "The token used for further communication."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:67
+msgid "Echoes the value of the echo key, used for debugging and testing."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:69
+msgid "Value will be returned in response."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:70
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:80
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:91
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:117
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:163
+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:73
+msgid "Value of the key 'echo' in the request."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:76
+msgid ""
+"Fetches rateStat from router statManager. Creates stat if not already "
+"created."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:78
+#, python-format
+msgid ""
+"Determines which rateStat to fetch, see <a "
+"href=\"%(ratestats)s\">ratestats</a>."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:79
+msgid "Determines which period a stat is fetched for. Measured in ms."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:83
+msgid "Returns the average value for the reuested rateStat and period."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:86
+msgid "Manages I2PControl. Ports, passwords and the like."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:88
+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:89
+msgid ""
+"Sets a new password for I2PControl, all Authentication tokens will be "
+"revoked."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:90
+msgid "Switches which port I2PControl will listen for connections on."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:94
+msgid "Returned if address was changed"
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:95
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:96
+msgid "Returned if setting was changed"
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:97
+msgid "Returns true if any changes were made."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:98
+msgid "Returns true if any changes requiring a restart to take effect were made."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:101
+msgid "Fetches basic information about the I2P router. Uptime, version etc."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:120
+msgid "What the status of the router is."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:121
+msgid "What the uptime of the router is in ms."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:122
+msgid "What version of I2P the router is running."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:123
+msgid "The 1 second average inbound bandwidth in Bps."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:124
+msgid "The 15 second average inbound bandwidth in Bps."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:125
+msgid "The 1 second average outbound bandwidth in Bps."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:126
+msgid "The 15 second average outbound bandwidth in Bps."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:127
+msgid "What the current network status is. According to the below enum:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:146
+msgid "How many tunnels on the I2P net are we participating in."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:147
+msgid "How many peers have we communicated with recently."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:148
+msgid "How many peers are considered 'fast'."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:149
+msgid "How many peers are considered 'high capacity'."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:150
+msgid "Is the router reseeding hosts to its NetDB?"
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:151
+msgid "How many peers are known to us (listed in our NetDB)."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:154
+msgid "Manages I2P router restart/shutdown."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:156
+msgid "<b>Blocking</b>. Initiates a search for signed updates."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:157
+msgid ""
+"Initiates a router reseed, fetching peers into our NetDB from a remote "
+"host."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:158
+msgid "Restarts the router."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:159
+msgid ""
+"Restarts the router gracefully (waits for participating tunnels to "
+"expire)."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:160
+msgid "Shuts down the router."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:161
+msgid ""
+"Shuts down the router gracefully (waits for participating tunnels to "
+"expire)."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:162
+msgid "Initiates a router update from signed sources."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:166
+msgid "<b>Blocking</b>. Returns true iff a signed update has been found."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:167
+msgid "If requested, verifies that a reseed has been initiated."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:168
+msgid "If requested, verifies that a restart has been initiated."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:169
+msgid "If requested, verifies that a graceful restart has been initiated."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:170
+msgid "If requested, verifies that a shutdown has been initiated"
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:171
+msgid "If requested, verifies that a graceful shutdown has been initiated"
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:172
+msgid "<b>Blocking</b>. If requested, returns the status of the the update"
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:175
+msgid "Fetches or sets various network related settings. Ports, addresses etc."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:177
+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:178
+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:179
+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:180
+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:181
+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:182
+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:183
+msgid "What ip has been detected by the UDP transport."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:184
+msgid "Is UPnP enabled. If null is submitted, current setting will be returned."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:185
+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:186
+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:187
+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:188
+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:189
+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:192
+msgid "If requested, returns the port used for the TCP transport."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:193
+msgid "If requested, returns the hostname used for the TCP transport."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:194
+msgid ""
+"If requested, returns the method used for automatically detecting ip for "
+"the TCP transport."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:195
+msgid "If requested, returns the port used for the UDP transport."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:196
+msgid "If requested, returns the hostname used for the UDP transport."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:197
+msgid ""
+"If requested, returns methods used for detecting the ip address of the "
+"UDP transport."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:198
+msgid "If requested, returns what ip has been detected by the UDP transport."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:199
+msgid "If requested, returns the UPNP setting."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:200
+msgid ""
+"If requested, returns how many percent of bandwidth is usable for "
+"participating tunnels."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:201
+msgid "If requested, returns how many KB/s of inbound bandwidth is allowed."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:202
+msgid "If requested, returns how many KB/s of outbound bandwidth is allowed."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:203
+msgid "If requested, returns the laptop mode."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:204
+msgid "Have the provided settings been saved."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:205
+msgid "Is a restart needed for the new settings to be used."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:208
+msgid "Allows for manipulation of advanced i2p settings"
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:209
+msgid "Set:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:209
+msgid "Set the sent key-value pairs"
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:212
+msgid "SetAll:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:212
+msgid "Set the sent key-value pairs, remove everything else"
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:215
+msgid "Get:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:215
+msgid "Get the key-value pairs for the sent keys"
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:218
+msgid "GetAll:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:218
+msgid "Get all the key-value pairs"
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:221
+msgid "denotes an optional value."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:222
+msgid "denotes a possibly occuring return value"
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:224
+msgid "Error codes"
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:225
+msgid "Standard JSON-RPC2 error codes."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:226
+msgid "JSON parse error."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:227
+msgid "Invalid request."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:228
+msgid "Method not found."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:229
+msgid "Invalid parameters."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:230
+msgid "Internal error."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:232
+msgid "I2PControl specific error codes."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:233
+msgid "Invalid password provided."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:234
+msgid "No authentication token presented."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:235
+msgid "Authentication token doesn't exist."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:236
+msgid "The provided authentication token was expired and will be removed."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:237
+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:238
+msgid ""
+"The version of the I2PControl API specified is not supported by "
+"I2PControl."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2ptunnel.html:8
+#, 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 <a "
+"href=\"%(naming)s\">hostname</a>,\n"
+"<a href=\"%(naming)s#base32\">Base32</a>, 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"
+"<a "
+"href=\"http://localhost:7657/i2ptunnel/\">localhost:7657/i2ptunnel/</a>."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2ptunnel.html:20
+msgid "Default Services"
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2ptunnel.html:21
+msgid "Server tunnels"
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2ptunnel.html:23
+msgid ""
+"<b>I2P Webserver</b> - A tunnel pointed to a Jetty webserver run\n"
+"on <a href=\"http://localhost:7658\">localhost:7658</a> for convenient "
+"and quick hosting on I2P.\n"
+"<br>The document root is:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2ptunnel.html:31
+msgid "Client tunnels"
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2ptunnel.html:33
+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:37
+msgid "An IRC tunnel to the default anonymous IRC network, Irc2P."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2ptunnel.html:38
+#, python-format
+msgid ""
+"The anonymous <a href=\"%(monotone)s\">monotone</a>\n"
+"sourcecode repository for I2P"
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2ptunnel.html:42
+#, python-format
+msgid ""
+"A SMTP service provided by postman at <a "
+"href=\"http://%(postman)s/?page_id=16\">%(postman)s</a>"
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2ptunnel.html:45
+#, python-format
+msgid ""
+"The accompanying POP sevice of postman at <a "
+"href=\"http://%(postman)s/?page_id=16\">%(postman)s</a>"
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2ptunnel.html:50
+msgid "Configuration"
+msgstr "Häälestus"
+
+#: i2p2www/pages/site/docs/api/i2ptunnel.html:54
+msgid "Client Modes"
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2ptunnel.html:55
+#: i2p2www/pages/site/docs/api/i2ptunnel.html:165
+msgid "Standard"
+msgstr "Tavalised"
+
+#: i2p2www/pages/site/docs/api/i2ptunnel.html:56
+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:62
+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:67
+msgid ""
+"<b>Accept, Accept-Charset, Accept-Language\n"
+" and Accept-Ranges</b> as they vary greatly between browsers and can be "
+"used as an identifier."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2ptunnel.html:90
+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:94
+msgid "Outproxy:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2ptunnel.html:95
+msgid "Internal I2P use:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2ptunnel.html:100
+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:105
+msgid "Whitelist:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2ptunnel.html:139
+msgid "Enables using the I2P router as a SOCKS proxy."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2ptunnel.html:144
+msgid ""
+"Enables using the I2P router as a SOCKS proxy with the command whitelist "
+"specified by\n"
+"<a href=\"#client-mode-irc\">IRC</a> client mode."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2ptunnel.html:150
+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:156
+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:164
+msgid "Server Modes"
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2ptunnel.html:166
+msgid "Creates a destination to a local ip:port with an open TCP port."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2ptunnel.html:171
+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:177
+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:184
+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:190
+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 "Tähelepanu"
+
+#: i2p2www/pages/site/docs/api/ministreaming.html:7
+#, python-format
+msgid ""
+"The ministreaming library has been enhanced and extended by the\n"
+"\"full\" <a href=\"%(streaming)s\">streaming library</a>.\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 <a href=\"%(api)s\">API documentation</a> 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"
+"<a href=\"%(i2cp)s\">I2CP</a> 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"
+"<a href=\"%(i2ptunnel)s\">I2PTunnel</a> 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 <a href=\"%(minwww)s\">significant</a>.  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 <a href=\"%(api)s\">API</a>\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"
+"<a href=\"%(samv3)s\">SAM</a>'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 <a href=\"%(faq)s#socks\">FAQ</a>:"
+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/network-database.html:183
+#: 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 <a href=\"%(meeting81)s\">Meeting 81</a> and\n"
+"<a href=\"%(meeting82)s\">Meeting 82</a> 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
+msgid "July 2018"
+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"
+"<a href=\"%(datagrams)s\">datagram library</a>."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/streaming.html:18
+#, python-format
+msgid ""
+"The streaming library is a layer on top of the core \n"
+"<a href=\"%(i2cp)s\">I2CP API</a> 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 <a href=\"%(i2cp)s\">I2CP</a> API is completely hidden, "
+"except that\n"
+"applications may pass <a href=\"%(i2cp)s#options\">I2CP parameters</a> "
+"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"
+"<a href=\"%(i2psktmf)s\">I2PSocketManagerFactory</a> to create an\n"
+"<a href=\"%(i2psktm)s\">I2PSocketManager</a>. The application then asks "
+"the\n"
+"socket manager for an <a href=\"%(i2psess)s\">I2PSession</a>, which will "
+"cause\n"
+"a connection to the router via <a href=\"%(i2cp)s\">I2CP</a>. The "
+"application\n"
+"can then setup connections with an <a href=\"%(i2pskt)s\">I2PSocket</a> "
+"or\n"
+"receive connections with an <a href=\"%(i2psskt)s\">I2PServerSocket</a>."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/streaming.html:82
+#, python-format
+msgid "Here are the <a href=\"%(url)s\">full streaming library Javadocs</a>."
+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"
+"<a "
+"href=\"%(i2psktmf)s\">I2PSocketManagerFactory</a>.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 <a href=\"%(samv3)s\">SAM</a>,\n"
+"<a href=\"%(bob)s\">BOB</a>, and <a href=\"%(i2ptunnel)s\">I2PTunnel</a>,"
+"\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:103
+#: i2p2www/pages/site/docs/protocol/i2cp.html:478
+msgid "Option"
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/streaming.html:117
+#: i2p2www/pages/site/docs/protocol/i2cp.html:107
+#: i2p2www/pages/site/docs/protocol/i2cp.html:482
+msgid "Default"
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/streaming.html:117
+#: i2p2www/pages/site/docs/how/elgamal-aes.html:264
+#: i2p2www/pages/site/docs/how/peer-selection.html:282
+msgid "Notes"
+msgstr "Märkused"
+
+#: 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:129
+#: i2p2www/pages/site/docs/api/streaming.html:135
+#: i2p2www/pages/site/docs/api/streaming.html:141
+#: i2p2www/pages/site/docs/api/streaming.html:148
+#: i2p2www/pages/site/docs/api/streaming.html:160
+#: i2p2www/pages/site/docs/api/streaming.html:171
+#: i2p2www/pages/site/docs/api/streaming.html:200
+#: i2p2www/pages/site/docs/api/streaming.html:212
+#: i2p2www/pages/site/docs/api/streaming.html:220
+#: i2p2www/pages/site/docs/api/streaming.html:245
+#: i2p2www/pages/site/docs/api/streaming.html:262
+#: i2p2www/pages/site/docs/api/streaming.html:275
+#: i2p2www/pages/site/docs/api/streaming.html:286
+#: i2p2www/pages/site/docs/api/streaming.html:292
+#: i2p2www/pages/site/docs/api/streaming.html:298
+#: i2p2www/pages/site/docs/api/streaming.html:312
+#: i2p2www/pages/site/docs/api/streaming.html:319
+#: i2p2www/pages/site/docs/api/streaming.html:326
+#: i2p2www/pages/site/docs/api/streaming.html:351
+#: i2p2www/pages/site/docs/api/streaming.html:358
+#: i2p2www/pages/site/docs/api/streaming.html:365
+#, python-format
+msgid "As of release %(release)s."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/streaming.html:125
+#: i2p2www/pages/site/docs/api/streaming.html:133
+msgid "Use the access list as a whitelist for incoming connections."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/streaming.html:127
+msgid "The name or number of the signature type for a transient destination."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/streaming.html:139
+msgid "Use the access list as a blacklist for incoming connections."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/streaming.html:153
+msgid "Whether to respond to incoming pings"
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/streaming.html:165
+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:175
+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:179
+msgid ""
+"When we're in congestion avoidance, we grow the window size at the rate\n"
+"of <code>1/(windowSize*factor)</code>.  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:186
+msgid ""
+"How long to wait after instantiating a new con \n"
+"before actually attempting to connect.  If this is\n"
+"&lt;= 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:194
+msgid ""
+"How long to block on connect, in milliseconds. Negative means "
+"indefinitely. Default is 5 minutes."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/streaming.html:198
+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:204
+msgid ""
+"Comma- or space-separated list of Base64 peer Hashes or host names to be\n"
+"contacted using an alternate DSA destination.\n"
+"Only applies if multisession is enabled and the primary session is non-"
+"DSA\n"
+"(generally for shared clients only).\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:216
+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:226
+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:232
+msgid "Idle time before sending a keepalive"
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/streaming.html:235
+msgid "Delay before sending an ack"
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/streaming.html:237
+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:242
+msgid ""
+"Initial timeout\n"
+"(if no <a href=\"#sharing\">sharing data</a> available)."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/streaming.html:249
+msgid ""
+"Initial round trip time estimate\n"
+"(if no <a href=\"#sharing\">sharing data</a> available).\n"
+"Disabled as of release 0.9.8; uses actual RTT."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/streaming.html:255
+msgid "if no <a href=\"#sharing\">sharing data</a> available"
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/streaming.html:255
+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:279
+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:284
+msgid "Incoming connection limit (per peer; 0 means disabled)"
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/streaming.html:290
+#: i2p2www/pages/site/docs/api/streaming.html:296
+msgid "(per peer; 0 means disabled)"
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/streaming.html:302
+msgid "The MTU in bytes."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/streaming.html:306
+msgid "Maximum number of retransmissions before failure."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/streaming.html:310
+msgid "Incoming connection limit (all peers; 0 means disabled)"
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/streaming.html:316
+#: i2p2www/pages/site/docs/api/streaming.html:323
+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:332
+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:337
+msgid "How long to block on read, in milliseconds. Negative means indefinitely."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/streaming.html:341
+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:348
+#: i2p2www/pages/site/docs/api/streaming.html:355
+#: i2p2www/pages/site/docs/api/streaming.html:362
+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:369
+msgid ""
+"How long to block on write/flush, in milliseconds. Negative means "
+"indefinitely."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/streaming.html:377
+msgid "Protocol Specification"
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/streaming.html:379
+msgid "See the Streaming Library Specification page."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/streaming.html:383
+msgid "Implementation Details"
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/streaming.html:385
+msgid "Setup"
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/streaming.html:386
+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:391
+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:398
+msgid "MTU Selection and Negotiation"
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/streaming.html:399
+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:408
+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:419
+#, python-format
+msgid ""
+"Data integrity is assured by the gzip CRC-32 checksum implemented in\n"
+"<a href=\"%(i2cp)s#format\">the I2CP layer</a>.\n"
+"There is no checksum field in the streaming protocol."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/streaming.html:427
+#, python-format
+msgid ""
+"Each packet is sent through I2P as a single message (or as an individual "
+"clove in a\n"
+"<a href=\"%(garlicrouting)s\">Garlic Message</a>). Message encapsulation "
+"is implemented\n"
+"in the underlying <a href=\"%(i2cp)s\">I2CP</a>, <a "
+"href=\"%(i2np)s\">I2NP</a>, and\n"
+"<a href=\"%(tunnelmessage)s\">tunnel message</a> layers. There is no "
+"packet delimiter\n"
+"mechanism or payload length field in the streaming protocol."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/streaming.html:437
+msgid "Optional Delay"
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/streaming.html:438
+msgid ""
+"Data packets may include an optional delay field specifying the requested"
+" delay,\n"
+"in ms, before the receiver should ack the packet.\n"
+"Valid values are 0 to 60000 inclusive.\n"
+"A value of 0 requests an immediate ack.\n"
+"This is advisory only, and receivers should delay slightly so that\n"
+"additional packets may be acknowledged with a single ack.\n"
+"Some implementations may include an advisory value of (measured RTT / 2) "
+"in this field.\n"
+"For nonzero optional delay values, receivers should limit the maximum "
+"delay\n"
+"before sending an ack to a few seconds at most.\n"
+"Optional delay values greater than 60000 indicate choking, see below."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/streaming.html:452
+msgid "Receive Window and Choking"
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/streaming.html:453
+msgid ""
+"TCP headers include the receive window in bytes.\n"
+"The streaming protocol does not contain a receive window, it uses only a "
+"simple choke/unchoke indication.\n"
+"Each endpoint must maintain its own estimate of the far-end receive "
+"window, in either bytes or packets.\n"
+"The recommended minimum buffer size for receiver implementations is 128 "
+"packets or 217 KB (approximately 128x1730).\n"
+"Because of I2P netowrk latency, packet drops, and the resulting "
+"congestion control,\n"
+"a buffer of this size is rarely filled.\n"
+"Overflow is, however, likely to occur on high-bandwidth \"local "
+"loopback\" (same-router) connections."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/streaming.html:462
+msgid ""
+"To quickly indicate and smoothly recover from overflow conditions,\n"
+"there is a simple mechanism for pushback in the streaming protocol.\n"
+"If a packet is received with an optional delay field of value of 60001 or"
+" higher,\n"
+"that indicates \"choking\" or a receive window of zero.\n"
+"A packet with an optional delay field of value of 60000 or less indicates"
+" \"unchoking\".\n"
+"Packets without an optional delay field do not affect the choke/unchoke "
+"state."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/streaming.html:470
+msgid ""
+"After being choked, no more packets with data should be sent until the "
+"transmitter is unchoked,\n"
+"except for occasional \"probe\" data packets to compensate for possible "
+"lost unchoke packets.\n"
+"The choked endpoint should start a \"persist timer\" to control the "
+"probing, as in TCP.\n"
+"The unchoking endpoint should send several packets with this field set,\n"
+"or continue sending them periodically until data packets are received "
+"again.\n"
+"Maximum time to wait for unchoking is implementation-dependent.\n"
+"Transmitter window size and congestion control strategy after being "
+"unchoked is implementation-dependent."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/streaming.html:481
+msgid "Congestion Control"
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/streaming.html:482
+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:489
+msgid "Close"
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/streaming.html:490
+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:498
+msgid ""
+"There is no ping function at the I2CP layer (equivalent to ICMP echo) or "
+"in datagrams.\n"
+"This function is provided in streaming.\n"
+"Pings and pongs may not be combined with a standard streaming packet;\n"
+"if the ECHO option is set, then\n"
+"most other flags, options, ackThrough, sequenceNum, NACKs, etc. are "
+"ignored."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/streaming.html:506
+msgid ""
+"A ping packet must have the ECHO, SIGNATURE_INCLUDED, and FROM_INCLUDED "
+"flags set.\n"
+"The sendStreamId must be greater than zero, and the receiveStreamId is "
+"ignored.\n"
+"The sendStreamId may or may not correspond to an existing connection."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/streaming.html:512
+msgid ""
+"A pong packet must have the ECHO flag set.\n"
+"The sendStreamId must be zero, and the receiveStreamId is the "
+"sendStreamId from the ping.\n"
+"Prior to release 0.9.18, the pong packet does not include any payload "
+"that was contained in the ping."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/streaming.html:518
+msgid ""
+"As of release 0.9.18, pings and pongs may contain a payload.\n"
+"The payload in the ping, up to a maximum of 32 bytes, is returned in the "
+"pong."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/streaming.html:523
+msgid ""
+"Streaming may be configured to disable sending pongs with the "
+"configuration i2p.streaming.answerPings=false."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/streaming.html:528
+msgid "Control Block Sharing"
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/streaming.html:529
+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"
+"<a href=\"http://www.ietf.org/rfc/rfc2140.txt\">RFC 2140</a>).\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:550
+msgid "Other Parameters"
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/streaming.html:551
+msgid ""
+"The following parameters are hardcoded, but may be of interest for "
+"analysis:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/streaming.html:570
+#: i2p2www/pages/site/docs/how/network-database.html:895
+msgid "History"
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/streaming.html:571
+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:585
+#: i2p2www/pages/site/docs/how/elgamal-aes.html:344
+#: i2p2www/pages/site/docs/how/garlic-routing.html:251
+#: i2p2www/pages/site/docs/how/network-database.html:900
+#: 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:723
+#: i2p2www/pages/site/docs/protocol/i2np.html:226
+#: i2p2www/pages/site/docs/transport/ntcp.html:544
+#: i2p2www/pages/site/docs/transport/ssu.html:585
+#: i2p2www/pages/site/docs/tunnels/implementation.html:506
+msgid "Future Work"
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/streaming.html:586
+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:592
+msgid "Additional tuning of the streaming lib parameters may be necessary."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/streaming.html:595
+#, python-format
+msgid ""
+"Another area for research is the interaction of the streaming lib with "
+"the\n"
+"NTCP and SSU transport layers.\n"
+"See <a href=\"%(ntcpdisc)s\">the NTCP discussion page</a> for details."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/streaming.html:600
+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:610
+msgid "The data in the first SYN packet may exceed the receiver's MTU."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/streaming.html:613
+msgid "The DELAY_REQUESTED field could be used more."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/streaming.html:616
+msgid ""
+"Duplicate initial SYNCHRONIZE packets on short-lived streams may not be "
+"recognized and removed."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/streaming.html:619
+msgid "Don't send the MTU in a retransmission."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/streaming.html:622
+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:627
+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:632
+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
+msgid "January 2017"
+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"
+"<a href=\"%(commonstructures)s#struct_Destination\">Destination</a>,\n"
+"using the I2P Base 64 alphabet [A-Z][a-z][0-9]-~.\n"
+"<a href=\"%(commonstructures)s#struct_Destination\">Destinations</a>\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 ""
+"Current Destinations for clients are 387 or more bytes (516 or more in "
+"Base 64 encoding).\n"
+"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"
+"<a href=\"%(commonstructures)s#struct_Destination\">Destination</a>, 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"
+"<a href=\"%(commonstructures)s#type_Hash\">32-byte SHA-256 Hashes</a>\n"
+"of the binary\n"
+"<a href=\"%(commonstructures)s#struct_Destination\">Destinations</a>\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&#37;."
+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"
+"<a href=\"%(commonstructures)s#struct_Destination\">Destination</a>\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"
+"<a href=\"%(naming)s\">I2P naming standards</a>.\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 <a "
+"href=\"%(commonstructures)s#struct_Destination\">Destinations</a>\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"
+"<a href=\"http://www.bittorrent.org/beps/bep_0010.html\">the extension "
+"handshake</a>.\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"
+"<a href=\"%(commonstructures)s#struct_Destination\">Destinations</a>\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"
+"<a href=\"http://www.bittorrent.org/beps/bep_0005.html\">BEP 5</a>\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"
+"<a href=\"http://www.bittorrent.org/beps/bep_0010.html\">the extension "
+"handshake</a>.\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:286
+msgid "Datagram (UDP) Trackers"
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/bittorrent.html:287
+msgid ""
+"UDP tracker support in clients and trackers is not yet available.\n"
+"Preliminary differences from\n"
+"<a href=\"http://www.bittorrent.org/beps/bep_0015.html\">BEP 15</a>\n"
+"are described below, and are subject to change.\n"
+"Contact the I2P developers if you wish to develop a client or tracker "
+"supporting datagram announces."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/bittorrent.html:295
+msgid ""
+"A UDP tracker listens on two ports.\n"
+"The \"query port\" is the advertised port, and is used to receive "
+"repliable (signed) datagrams, for the connect request only.\n"
+"The \"response port\" is used to receive unsigned (raw) datagrams, and is"
+" the source port for all replies.\n"
+"The response port is arbitrary.\n"
+"A client sends and receives on a single port only.\n"
+"It receives only unsigned (raw) datagrams.\n"
+"Raw datagrams provides increased efficiency for replies since they "
+"contain tokens sent in the query, and need not be signed."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/bittorrent.html:305
+msgid ""
+"In the announce request, the 4-byte IP is replaced by a 32-byte hash, and"
+" the port is still present,\n"
+"although it may be ignored by the tracker.\n"
+"In the announce response, each 4-byte IP and 2-byte port is replaced by a"
+" 32-byte hash (compact peer info), and no port is present.\n"
+"The client sends the announce request and scrape request to the source "
+"port in the announce response packet.\n"
+"The connect request, connect response, scrape request, scrape response, "
+"and error response are the same as in BEP 15."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/bittorrent.html:313
+msgid ""
+"Source addresses in I2P cannot be spoofed, so it is possible to use a "
+"simplified protocol\n"
+"with 2 packets instead of 4, omitting the connect request and response.\n"
+"In this case, the announce request would be a repliable datagram sent to "
+"the tracker's query port,\n"
+"and the tracker would not require a response port.\n"
+"While this is more efficient, it would be more difficult to modify an "
+"existing tracker to support this mode.\n"
+"The URL for the 4-packet-mode tracker would use standard \"udp://\" "
+"prefix. \n"
+"The URL for a modified 2-packet-mode tracker would require a different "
+"prefix if both modes are supported in I2P."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/bittorrent.html:326
+#: i2p2www/pages/site/docs/how/intro.html:184
+msgid "Additional Information"
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/bittorrent.html:328
+#, python-format
+msgid ""
+"I2P bittorrent standards are generally discussed on <a "
+"href=\"http://%(zzz)s/\">%(zzz)s</a>."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/bittorrent.html:331
+#, python-format
+msgid ""
+"A chart of current tracker software capabilities is <a "
+"href=\"http://%(zzz)s/files/trackers.html\">also available there</a>."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/bittorrent.html:334
+#, python-format
+msgid ""
+"The\n"
+"<a href=\"http://%(forum)s/viewtopic.php?t=2068\">I2P bittorrent FAQ</a>"
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/bittorrent.html:338
+#, python-format
+msgid "<a href=\"http://%(zzz)s/topics/812\">DHT on I2P discussion</a>"
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/embedding.html:2
+msgid "Embedding I2P in your Application"
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/embedding.html:3
+msgid "November 2017"
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/embedding.html:8
+msgid ""
+"This page is about bundling the entire I2P router binary with your "
+"application.\n"
+"It is not about writing an application to work with I2P (either bundled "
+"or external)."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/embedding.html:13
+msgid ""
+"Lots of projects are bundling, or talking about bundling, I2P. That's "
+"great if done right.\n"
+"If done wrong, it could cause real harm to our network.\n"
+"The I2P router is complex, and it can be a challenge to hide all the "
+"complexity from your users.\n"
+"This page discusses some general guidelines."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/embedding.html:23
+msgid "Talk to us"
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/embedding.html:24
+msgid ""
+"Start a dialog. We're here to help. Applications that embed I2P are the "
+"most promising - and exciting -\n"
+"opportunities for us to grow the network and improve anonymity for "
+"everyone."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/embedding.html:30
+msgid "Choose your router wisely"
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/embedding.html:31
+msgid ""
+"If your application is in Java or Scala, it's an easy choice - use the "
+"Java router.\n"
+"If in C/C++, we recommend i2pd. The development of i2pcpp has stopped.\n"
+"For apps in other languages, best to use SAM or BOB or SOCKS and bundle "
+"the Java router as a separate process.\n"
+"Some of the following only applies to the Java router."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/embedding.html:39
+msgid "Licensing"
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/embedding.html:40
+msgid "Ensure you meet the license requirements of the software you are bundling."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/embedding.html:45
+msgid "Verify default configuration"
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/embedding.html:46
+msgid ""
+"A correct default configuration is crucial. Most users will not change "
+"the defaults.\n"
+"The defaults for your application may need to be different than the "
+"defaults for the router you are bundling.\n"
+"Override the router defaults if necessary."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/embedding.html:51
+msgid ""
+"Some important defaults to review: Max bandwidth, tunnel quantity and "
+"length, max participating tunnels.\n"
+"A lot of this depends on the expected bandwidth and usage patterns of "
+"your app."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/embedding.html:55
+msgid ""
+"Configure enough bandwidth and tunnels to allow your users to contribute "
+"to the network.\n"
+"Consider disabling external I2CP, as you probably don't need it and it "
+"would conflict with any other running I2P instance.\n"
+"Also look at the configs for disabling killing of the JVM on exit, for "
+"example."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/embedding.html:62
+msgid "Participating Traffic Considerations"
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/embedding.html:63
+msgid ""
+"It may be tempting for you to disable participating traffic.\n"
+"There's several ways to do this (hidden mode, setting max tunnels to 0, "
+"setting shared bandwidth below 12 KBytes/sec).\n"
+"Without participating traffic, you don't have to worry about graceful "
+"shutdown,\n"
+"your users don't see bandwidth usage not generated by them, etc.\n"
+"However, there's lots of reasons why you should allow participating "
+"tunnels."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/embedding.html:70
+msgid ""
+"First of all, the router doesn't work that well if it doesn't have a "
+"chance to \"integrate\" with the network,\n"
+"which is helped tremendously by others building tunnels through you."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/embedding.html:74
+msgid ""
+"Secondly, over 90&#37; of the routers in the current network allow "
+"participating traffic.\n"
+"It's the default in the Java router.\n"
+"If your application doesn't route for others and it gets really popular, "
+"then it's a leech on the network,\n"
+"and it upsets the balance we have now.\n"
+"If it gets really big, then we become Tor, and spend our time begging for"
+" people to enable relaying."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/embedding.html:81
+msgid ""
+"Thirdly, participating traffic is cover traffic that helps your users' "
+"anonymity."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/embedding.html:84
+msgid ""
+"We strongly discourage you from disabling participating traffic by "
+"default.\n"
+"If you do this and your application gets hugely popular, it could break "
+"the network."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/embedding.html:90
+msgid "Persistence"
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/embedding.html:91
+msgid ""
+"You must save the router's data (netdb, configuration, etc.) between runs"
+" of the router.\n"
+"I2P does not work well if you must reseed each startup, and that's a huge"
+" load on our reseed servers, and not very good for anonymity either.\n"
+"Even if you bundle router infos, I2P needs saved profile data for best "
+"performance."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/embedding.html:99
+msgid "Configurability"
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/embedding.html:100
+msgid ""
+"Give your users a way to change the configuration of the important "
+"settings.\n"
+"We understand that you will probably want to hide most of I2P's "
+"complexity, but it's important to show some basic settings.\n"
+"In addition to the defaults above, some network settings such as UPnP, "
+"IP/port may be helpful."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/embedding.html:108
+msgid "Floodfill Considerations"
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/embedding.html:109
+msgid ""
+"Above a certain bandwidth setting, and meeting other health criteria, "
+"your router will become floodfill,\n"
+"which may cause a large increase in connections and memory usage (at "
+"least with the Java router).\n"
+"Think about whether that's OK. You can disable floodfill, but then your "
+"fastest users aren't contributing what they could.\n"
+"It also depends on the typical uptime for your application."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/embedding.html:119
+msgid "Reseeding"
+msgstr "Hangin ruuterite kontakte"
+
+#: i2p2www/pages/site/docs/applications/embedding.html:120
+msgid ""
+"Decide if you are bundling router infos or using our reseed hosts.\n"
+"The Java reseed host list is in the source code, so if you keep your "
+"source up to date, the host list will be also.\n"
+"Be aware of possible blocking by hostile governments."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/embedding.html:129
+msgid "Reduce Network Resource Usage"
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/embedding.html:130
+msgid ""
+"Consider setting your application tunnels to delay-open, reduce-on-idle "
+"and/or close-on-idle.\n"
+"This is straightforward if using i2ptunnel but you'll have to implement "
+"some of it yourself if using I2CP directly.\n"
+"See i2psnark for code that reduces tunnel count and then closes the "
+"tunnel, even in the presence of some background DHT activity."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/embedding.html:138
+msgid "Updatability"
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/embedding.html:139
+msgid ""
+"Have an auto-update feature if at all possible, or at least auto-"
+"notification of a new version.\n"
+"Our biggest fear is a huge number of routers out there that can't be "
+"updated.\n"
+"We have about 6-8 releases a year of the Java router, and it's critical "
+"to the health of the network that the users keep up.\n"
+"We usually have over 80&#37; of the network on the latest release within "
+"6 weeks after the release, and we'd like to keep it that way.\n"
+"You don't need to worry about disabling the router's built-in auto-update"
+" function, as that code is in the router console,\n"
+"which you presumably are not bundling."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/embedding.html:150
+msgid "Rollout"
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/embedding.html:151
+msgid ""
+"Have a gradual rollout plan. Don't overwhelm the network all at once.\n"
+"We currently have approximately 25K unique users per day and 40K uniques "
+"per month.\n"
+"We are probably able to handle growth of 2-3X per year without too much "
+"issue.\n"
+"If you anticipate a faster rampup than that, OR the bandwidth "
+"distribution (or uptime distribution,\n"
+"or any other significant characteristic) of your userbase is "
+"significantly different from our current userbase,\n"
+"we really need to have a discussion.\n"
+"The bigger your growth plans, the more important everthing else in this "
+"checklist is."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/embedding.html:163
+msgid "Design for and Encourage Long Uptimes"
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/embedding.html:164
+msgid ""
+"Tell your users that I2P works best if it keeps running.\n"
+"It may be several minutes after startup before it works well, and even "
+"more after first install.\n"
+"If your average uptime is less than an hour, I2P is probably the wrong "
+"solution."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/embedding.html:172
+msgid "Show Status"
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/embedding.html:173
+msgid ""
+"Provide some indication to the user that the application tunnels are "
+"ready. Encourage patience."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/embedding.html:178
+msgid "Graceful Shutdown"
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/embedding.html:179
+msgid ""
+"If possible, delay the shutdown until your participating tunnels expire.\n"
+"Don't let your users break tunnels easily, or at least ask them to "
+"confirm."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/embedding.html:185
+msgid "Education and Donation"
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/embedding.html:186
+msgid ""
+"It would be nice if you give your users links to learn more about I2P and"
+" to donate."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/embedding.html:192
+msgid "External Router Option"
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/embedding.html:193
+msgid ""
+"Depending on your user base and application,\n"
+"it may be helpful to provide an option or a separate package to use an "
+"external router."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/embedding.html:200
+msgid "Use of other Common Services"
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/embedding.html:201
+msgid ""
+"If you plan to use or link to other common I2P services (news feeds, "
+"hosts.txt subscriptions, trackers, outproxies, etc.),\n"
+"make sure you aren't overloading them,\n"
+"and talk to the people who are running them to make sure it's ok."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/embedding.html:209
+msgid "Time / NTP Issues"
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/embedding.html:210
+msgid ""
+"I2P includes an SNTP client. I2P requires correct time to operate.\n"
+"It will compensate for a skewed system clock but this may delay startup. "
+"You may disable I2P's SNTP queries,\n"
+"but this isn't advised unless your application makes sure the system "
+"clock is correct."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/embedding.html:218
+msgid "Choose What and How you Bundle"
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/embedding.html:219
+msgid ""
+"At a minimum you will need i2p.jar, router.jar, streaming.jar, and "
+"mstreaming.jar.\n"
+"You may omit the two streaming jars for a datagram-only app.\n"
+"Some apps may need more, e.g. i2ptunnel.jar or addressbook.jar.\n"
+"Don't forget jbigi.jar, or a subset of it for the platforms you support, "
+"to make the crypto much faster.\n"
+"We are currently building them for Java 7, as of 0.9.24. The source is "
+"mostly compatible with Java 6 if you want to do your own compile,\n"
+"but we may start using Java 7 features at any time without notice.\n"
+"If you're building Debian / Ubuntu packages, you should require the I2P "
+"package from our PPA instead of bundling it.\n"
+"You almost certainly do not need susimail, susidns, the router console, "
+"and i2psnark, for example."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/embedding.html:229
+msgid ""
+"The following files should be included in the I2P installation directory,"
+" specified with the \"i2p.dir.base\" property.\n"
+"Don't forget certificates/reseed and certificates/ssl, required for "
+"reseeding, and blocklist.txt for IP validation.\n"
+"The geoip directory is optional, but recommended so the router can make "
+"decisions based on location.\n"
+"The hosts.txt file may be necessary, you may modify it to include any "
+"hosts your application uses.\n"
+"You may add a router.config file to the base directory to override "
+"initial defaults."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/embedding.html:236
+msgid ""
+"License requirements may require you to include the LICENSES.txt file and"
+" the licenses directory."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/embedding.html:242
+msgid "You may also wish to bundle a hosts.txt file."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/embedding.html:245
+msgid "Be sure to specify a Java 7 bootclasspath if compiling with Java 8."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/embedding.html:253
+msgid "Android considerations"
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/embedding.html:254
+msgid ""
+"Our Android router app may be shared by multiple clients.\n"
+"If it is not installed, the user will be prompted when he starts a client"
+" app."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/embedding.html:258
+msgid ""
+"Some developers have expressed concern that this is a poor user "
+"experience,\n"
+"and they wish to embed the router in their app.\n"
+"We do have an Android router service library on our roadmap, which could "
+"make embedding easier.\n"
+"More information needed."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/embedding.html:264
+#: i2p2www/pages/site/docs/applications/embedding.html:275
+msgid "If you require assistance, please contact us."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/embedding.html:270
+msgid "Maven jars"
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/embedding.html:271
+msgid ""
+"We have a limited number of our jars on <a "
+"href=\"http://search.maven.org/#search%7Cga%7C1%7Cg%3A%22net.i2p%22\">Maven"
+" Central</a>.\n"
+"There are numerous trac tickets for us to address that will improve and "
+"expand the released jars on Maven Central."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/embedding.html:281
+msgid "Datagram (DHT) considerations"
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/embedding.html:282
+msgid ""
+"If your application is using I2P datagrams, e.g. for a DHT,\n"
+"there's lots of advanced options available to reduce overhead and "
+"increase reliability.\n"
+"This may take some time and experimentation to get working well.\n"
+"Be aware of size/reliability tradeoffs. Talk to us for help.\n"
+"It is possible - and recommended - to use Datagrams and Streaming on the "
+"same Destination.\n"
+"Don't create separate Destinations for this.\n"
+"Don't try to store your unrelated data in the existing network DHTs "
+"(iMule, bote, bittorrent, and router).\n"
+"Build your own. If you are hardcoding seed nodes, we recommend that you "
+"have several."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/embedding.html:295
+msgid "Comarketing"
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/embedding.html:296
+msgid ""
+"Let's work together. Don't wait until it's done.\n"
+"Give us your Twitter handle and start tweeting about it, we will return "
+"the favor."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/embedding.html:302
+msgid "Malware"
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/embedding.html:303
+msgid ""
+"Please don't use I2P for evil.\n"
+"It could cause great harm both to our network and our reputation."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/embedding.html:309
+msgid "Join Us"
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/embedding.html:310
+msgid ""
+"This may be obvious, but join the community. Run I2P 24/7. Start an "
+"eepsite about your project.\n"
+"Hang out in IRC #i2p-dev. Post on the forums. Spread the word.\n"
+"We can help get you users, testers, translators, or even coders."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/embedding.html:318
+msgid "Application Examples"
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/embedding.html:319
+msgid ""
+"You may wish to install and play with the I2P Android app, and look at "
+"its code, for an example of an application that bundles the router.\n"
+"See what we expose to the user and what we hide.\n"
+"Look at the state machine we use to start and stop the router.\n"
+"Other examples are: Vuze, the Nightweb Android app, iMule, TAILS, iCloak,"
+" and Monero."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/embedding.html:327
+msgid "Code Example"
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/embedding.html:328
+msgid ""
+"None of the above actually tells you how to write your code to\n"
+"bundle the Java router, so following is a brief example."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/embedding.html:358
+msgid ""
+"This code is for the case where your application starts the router, as in"
+" our Android app.\n"
+"You could also have the router start the application via the "
+"clients.config and i2ptunnel.config files,\n"
+"together with Jetty webapps,\n"
+"as is done in our Java packages.\n"
+"As always, state management is the difficult part."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/managed-clients.html:3
+msgid "February 2014"
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/managed-clients.html:8
+#, python-format
+msgid ""
+"Clients may be started directly by the router when they are listed\n"
+"in the <a href=\"%(configspec)s\">clients.config</a> file.\n"
+"These clients may be \"managed\" or \"unmanaged\".\n"
+"This is handled by the ClientAppManager.\n"
+"Additionally, managed or unmanaged clients may register with the\n"
+"ClientAppManager so that other clients may retrieve a reference to them.\n"
+"There is also a simple Port Mapper facility for clients to register an\n"
+"internal port that other clients may look up."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/managed-clients.html:21
+msgid ""
+"As of release 0.9.4, the router supports managed clients.\n"
+"Managed clients are instantiated and started by the ClientAppManager.\n"
+"The ClientAppManager maintains a reference to the client and receives "
+"updates on the client's state.\n"
+"Managed clients are preferred, as it is much easier to implement state "
+"tracking\n"
+"and to start and stop a client. It also is much easier to avoid static "
+"references in the client code\n"
+"which could lead to excessive memory usage after a client is stopped.\n"
+"Managed clients may be started and stopped by the user in the router "
+"console,\n"
+"and are stopped at router shutdown."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/managed-clients.html:31
+msgid ""
+"Managed clients implement either the net.i2p.app.ClientApp or "
+"net.i2p.router.app.RouterApp interface.\n"
+"Clients implementing the ClientApp interface must provide the following "
+"constructor:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/managed-clients.html:38
+msgid ""
+"Clients implementing the RouterApp interface must provide the following "
+"constructor:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/managed-clients.html:44
+msgid "The arguments provided are specified in the clients.config file."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/managed-clients.html:48
+msgid "Unmanaged Clients"
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/managed-clients.html:49
+msgid ""
+"If the main class specified in the clients.config file does not implement"
+" a managed interface,\n"
+"it will be started with main() with the arguments specified,\n"
+"and stopped with main() with the arguments specified.\n"
+"The router does not maintain a reference, since all interactions are via "
+"the static main() method.\n"
+"The console cannot provide accurate state information to the user."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/managed-clients.html:57
+msgid "Registered Clients"
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/managed-clients.html:58
+msgid ""
+"Clients, whether managed or unmanaged, may register with the "
+"ClientAppManager\n"
+"so that other clients may retrieve a reference to them.\n"
+"Registration is by name.\n"
+"Known registered clients are:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/managed-clients.html:68
+msgid "Port Mapper"
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/managed-clients.html:69
+msgid ""
+"The router also provides a simple mechanism for clients to find an "
+"internal socket service,\n"
+"such as the HTTP proxy. This is provided by the Port Mapper.\n"
+"Registration is by name.\n"
+"Clients that register generally provide an internal emulated socket on "
+"that port."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:2
+msgid "Supported Applications"
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:5
+#: i2p2www/pages/site/docs/applications/supported.html:188
+msgid "Blogging, Forums, and Wikis"
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:7
+#: i2p2www/pages/site/docs/applications/supported.html:234
+msgid "Decentralized File Storage"
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:10
+#: i2p2www/pages/site/docs/applications/supported.html:246
+msgid "Development Tools"
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:13
+#: i2p2www/pages/site/docs/applications/supported.html:248
+msgid "Version control"
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:17
+#: i2p2www/pages/site/docs/applications/supported.html:267
+msgid "Domain Naming"
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:19
+#: i2p2www/pages/site/docs/applications/supported.html:285
+msgid "Email"
+msgstr "E-post"
+
+#: i2p2www/pages/site/docs/applications/supported.html:22
+#: i2p2www/pages/site/docs/applications/supported.html:330
+msgid "File Sharing"
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:25
+#: i2p2www/pages/site/docs/applications/supported.html:332
+msgid "BitTorrent clients"
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:27
+#: i2p2www/pages/site/docs/applications/supported.html:375
+msgid "BitTorrent trackers and indexers"
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:36
+#: i2p2www/pages/site/docs/applications/supported.html:442
+msgid "Network Administration"
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:39
+#: i2p2www/pages/site/docs/applications/supported.html:444
+msgid "General-purpose socket utilities"
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:46
+#: i2p2www/pages/site/docs/applications/supported.html:485
+msgid "Real-time Chat"
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:49
+#: i2p2www/pages/site/docs/applications/supported.html:487
+msgid "Instant messaging clients"
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:51
+#: i2p2www/pages/site/docs/applications/supported.html:497
+msgid "IRC clients"
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:53
+#: i2p2www/pages/site/docs/applications/supported.html:548
+msgid "IRC servers"
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:58
+#: i2p2www/pages/site/docs/applications/supported.html:564
+msgid "Web Browsing"
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:61
+#: i2p2www/pages/site/docs/applications/supported.html:566
+msgid "Anonymous websites"
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:63
+#: i2p2www/pages/site/docs/applications/supported.html:615
+msgid "Proxy software"
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:65
+#: i2p2www/pages/site/docs/applications/supported.html:640
+msgid "Inproxies"
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:67
+#: i2p2www/pages/site/docs/applications/supported.html:681
+msgid "Outproxies"
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:72
+#: i2p2www/pages/site/docs/applications/supported.html:695
+msgid "Website Hosting"
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:75
+#: i2p2www/pages/site/docs/applications/supported.html:710
+msgid "Web servers"
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:82
+#, 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"
+"<a href=\"%(trac)s\">Trac</a>, and be sure to select the\n"
+"“www” component in the submission form."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:89
+msgid ""
+"\n"
+"Supported applications are tagged with one or more of the following:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:94
+#: i2p2www/pages/site/docs/applications/supported.html:281
+#: i2p2www/pages/site/docs/applications/supported.html:313
+#: i2p2www/pages/site/docs/applications/supported.html:338
+#: i2p2www/pages/site/docs/applications/supported.html:707
+msgid "bundled"
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:97
+msgid ""
+"<em>Bundled application</em> — 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:105
+#: i2p2www/pages/site/docs/applications/supported.html:197
+#: i2p2www/pages/site/docs/applications/supported.html:210
+#: i2p2www/pages/site/docs/applications/supported.html:222
+#: i2p2www/pages/site/docs/applications/supported.html:230
+#: i2p2www/pages/site/docs/applications/supported.html:243
+#: i2p2www/pages/site/docs/applications/supported.html:294
+#: i2p2www/pages/site/docs/applications/supported.html:407
+#: i2p2www/pages/site/docs/applications/supported.html:429
+#: i2p2www/pages/site/docs/applications/supported.html:438
+#: i2p2www/pages/site/docs/applications/supported.html:526
+msgid "plugin"
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:108
+#, python-format
+msgid ""
+"<em>Third-party plugin</em> — 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](<a href=\n"
+"\"http://%(plugins)s\">http://%(plugins)s</a>) to identify security and\n"
+"anonymity issues."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:119
+#: i2p2www/pages/site/docs/applications/supported.html:222
+#: i2p2www/pages/site/docs/applications/supported.html:230
+#: i2p2www/pages/site/docs/applications/supported.html:243
+#: i2p2www/pages/site/docs/applications/supported.html:254
+#: i2p2www/pages/site/docs/applications/supported.html:263
+#: i2p2www/pages/site/docs/applications/supported.html:326
+#: i2p2www/pages/site/docs/applications/supported.html:345
+#: i2p2www/pages/site/docs/applications/supported.html:356
+#: i2p2www/pages/site/docs/applications/supported.html:371
+#: i2p2www/pages/site/docs/applications/supported.html:417
+#: i2p2www/pages/site/docs/applications/supported.html:429
+#: i2p2www/pages/site/docs/applications/supported.html:438
+#: i2p2www/pages/site/docs/applications/supported.html:453
+#: i2p2www/pages/site/docs/applications/supported.html:459
+#: i2p2www/pages/site/docs/applications/supported.html:465
+#: i2p2www/pages/site/docs/applications/supported.html:475
+#: i2p2www/pages/site/docs/applications/supported.html:481
+#: i2p2www/pages/site/docs/applications/supported.html:493
+#: i2p2www/pages/site/docs/applications/supported.html:526
+#: i2p2www/pages/site/docs/applications/supported.html:532
+#: i2p2www/pages/site/docs/applications/supported.html:538
+#: i2p2www/pages/site/docs/applications/supported.html:544
+#: i2p2www/pages/site/docs/applications/supported.html:621
+#: i2p2www/pages/site/docs/applications/supported.html:630
+#: i2p2www/pages/site/docs/applications/supported.html:636
+#: i2p2www/pages/site/docs/applications/supported.html:707
+#: i2p2www/pages/site/docs/applications/supported.html:722
+#: i2p2www/pages/site/docs/applications/supported.html:728
+#: i2p2www/pages/site/docs/applications/supported.html:734
+#: i2p2www/pages/site/docs/applications/supported.html:740
+msgid "standalone"
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:119
+#: i2p2www/pages/site/docs/applications/supported.html:197
+#: i2p2www/pages/site/docs/applications/supported.html:204
+#: i2p2www/pages/site/docs/applications/supported.html:210
+#: i2p2www/pages/site/docs/applications/supported.html:216
+#: i2p2www/pages/site/docs/applications/supported.html:365
+#: i2p2www/pages/site/docs/applications/supported.html:389
+#: i2p2www/pages/site/docs/applications/supported.html:398
+#: i2p2www/pages/site/docs/applications/supported.html:554
+#: i2p2www/pages/site/docs/applications/supported.html:560
+msgid "standalone/mod"
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:122
+msgid ""
+"<em>Third-party standalone application</em> — Many standard network\n"
+"applications only require careful setup and configuration to communicate\n"
+"anonymously over I2P. These are tagged with <em>standalone</em>. Some\n"
+"applications, tagged with <em>standalone/mod</em>, 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:304
+#: i2p2www/pages/site/docs/applications/supported.html:574
+#: i2p2www/pages/site/docs/applications/supported.html:584
+#: i2p2www/pages/site/docs/applications/supported.html:593
+#: i2p2www/pages/site/docs/applications/supported.html:599
+#: i2p2www/pages/site/docs/applications/supported.html:605
+#: i2p2www/pages/site/docs/applications/supported.html:611
+#: i2p2www/pages/site/docs/applications/supported.html:653
+#: i2p2www/pages/site/docs/applications/supported.html:661
+#: i2p2www/pages/site/docs/applications/supported.html:670
+#: i2p2www/pages/site/docs/applications/supported.html:677
+#: i2p2www/pages/site/docs/applications/supported.html:691
+msgid "service"
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:138
+msgid ""
+"<em>Third-party essential network service</em> — 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:150
+#: i2p2www/pages/site/docs/applications/supported.html:222
+msgid "unmaintained"
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:153
+msgid ""
+"<em>Unmaintained</em> — 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:161
+#, 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 <a "
+"href=\"%(threatmodel)s\">identified\n"
+"threats to anonymity</a>. 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:173
+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:181
+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:203
+msgid "Lightweight forum software."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:209
+msgid "Another lightweight blogging platform."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:215
+msgid "Most popular open source forum software."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:221
+msgid "Distributed forums software, originally developed by jrandom."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:226
+#, python-format
+msgid ""
+"A Java-based MediaWiki clone. No external database needed.\n"
+"Plugin available <a href=\"http://%(plugins)s/plugins/jamwiki\">here</a>."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:238
+#, python-format
+msgid ""
+"Port of the <a href=\"http://tahoe-lafs.org/\"><strong>Tahoe-"
+"LAFS</strong></a>\n"
+"distributed file system to the I2P network. Controller plugin <a href=\n"
+"\"http://%(stats)s/i2p/plugins/\">here</a>."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:253
+msgid "Most popular distributed version control system."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:259
+#, python-format
+msgid ""
+"Another distributed version control system. Currently\n"
+"<a href=\"%(monotone)s\">used in I2P development</a>."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:271
+#, python-format
+msgid ""
+"Provides management of addressbooks, which are part of a simple,\n"
+"user-controlled <a href=\"%(naming)s\">I2P naming system</a> 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. (<em>Note:</em> 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:290
+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:299
+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:309
+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:318
+#, python-format
+msgid ""
+"Can be configured to use Postman's email service. See\n"
+"<a href=\"%(reviews)s\">this comparison of MUAs</a>,\n"
+"and configuration settings for\n"
+"<a href=\"%(smtp)s\">SMTP</a> and <a href=\"%(pop3)s\">POP3</a>."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:337
+msgid "I2P's integrated BitTorrent client."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:343
+msgid ""
+"Modified version of I2PSnark, no more supported neither\n"
+"    functional."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:350
+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:361
+msgid ""
+"Clean, full-featured cross-platform BitTorrent client with official\n"
+"ports for several GUI toolkits."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:370
+msgid "Has a plugin providing I2P support."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:377
+#, python-format
+msgid ""
+"For a detailed feature comparison of I2P-enabled trackers/indexers, see\n"
+"<a href=\"http://%(zzz)s/files/trackers.html\">here</a>."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:385
+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:394
+#, python-format
+msgid ""
+"Lightweight tracker/indexer. I2P mod available in the i2p.opentracker\n"
+"branch of the <a href=\"%(newdevs)s\">I2P Monotone repository</a>."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:403
+#, python-format
+msgid ""
+"<a href=\"http://%(zzz)s/\">zzz's</a> Java-based open tracker. More info\n"
+"<a href=\"http://%(zzz)s/topics/598?page=1#p2085\">here</a>."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:416
+msgid "I2P port of the aMule ED2K client."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:425
+#, python-format
+msgid ""
+"Port of the <a href=\"http://www.phex.org/mambo/\">Phex</a> Gnutella "
+"client. Website\n"
+"for plugin version <a href=\"http://%(stats)s/i2p/plugins/\">here</a>."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:434
+#, python-format
+msgid ""
+"Cache for Gnutella peers on I2P. Website for plugin version\n"
+"<a href=\"http://%(stats)s/i2p/plugins/\">here</a>."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:449
+msgid ""
+"OpenBSD's rewrite of the Unix standard tool, netcat, for socket relaying."
+"\n"
+"Several clones, ports, and forks have appeared over the years."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:458
+msgid "Like netcat but more powerful."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:464
+msgid ""
+"Proxy providing simple, transparent SOCKS-ification of network "
+"applications."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:474
+msgid ""
+"Most popular implementation of the Secure Shell (SSH) protocol and "
+"related tools."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:480
+msgid "Open source Secure Shell (SSH) client for Windows."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:492
+msgid "IM client with multiple incarnations, unsuported."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:499
+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"
+"<code>/me</code> command) which isn't inherently dangerous."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:510
+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 <a href=\"http://www.wireshark.org/\">Wireshark</a> 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:522
+#, python-format
+msgid ""
+"Small Java-based IRC client. Plugin available <a href=\n"
+"\"http://%(stats)s/i2p/plugins/\">here</a>."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:531
+msgid "Cross-platform graphical IRC client based on XChat."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:537
+msgid "Unixy terminal-based IRC client."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:543
+msgid "Another Unixy terminal-based IRC client."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:553
+msgid "IRC server developed from scratch."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:559
+msgid "Most popular IRC server."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:571
+msgid ""
+"Any website hosted anonymously on I2P, reachable through the I2P router's"
+" HTTP proxy."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:579
+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:589
+#, python-format
+msgid ""
+"Website for <a href=\"http://%(sponge)s/\">sponge's</a> jump service.\n"
+"Source code available."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:598
+msgid "Another jump service."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:604
+msgid "Dynamically updated eepsite index."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:610
+#, python-format
+msgid "Website for <a href=\"http://%(zzz)s/\">zzz's</a> jump service."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:620
+msgid "SOCKS-enabled caching web proxy with basic filtering capabilities."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:626
+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:635
+msgid "Venerable caching web proxy."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:642
+msgid "Gateways allowing users on the public Internet to access eepsites."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:649
+#, python-format
+msgid ""
+"<a href=\"http://%(tino)s/\">tino's</a> inproxy on the public Internet,\n"
+"currently out of service,"
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:658
+#: i2p2www/pages/site/docs/applications/supported.html:667
+#: i2p2www/pages/site/docs/applications/supported.html:674
+msgid "Another inproxy on the public Internet."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:683
+msgid ""
+"Gateways allowing I2P users to access content hosted on the public "
+"Internet."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:690
+msgid "Publicly advertised outproxy running Squid, located in Europe."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:700
+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 <a href=\"http://127.0.0.1:7658/\">user's eepsite</a>. 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:712
+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:721
+msgid "Most popular web server on the public WWW."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:727
+msgid "Web server and Java servlet container. More features than Jetty."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:733
+msgid "Fast lightweight web server."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:739
+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 <a href=\"%(naming)s\">the naming page</a> 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 <a "
+"href=\"#alternatives\">alternate naming systems</a> 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 <a href=\"https://zooko.com/distnames.html\">Names: "
+"Decentralized, Secure, Human-Meaningful: Choose Two</a>."
+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 <b>not globally"
+" \n"
+"unique</b>.  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 <b>locally unique</b>: "
+"they are \n"
+"what <i>you</i> 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 ""
+"<b>Inefficiency:</b>\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 <a href=\"http://%(i2host)s/\">%(i2host)sp</a>),\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"
+"<a href=\"%(url)s\">%(url)s</a>.\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 ""
+"<b>Not Scalable:</b>\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 ""
+"<b>Requires configuration and \"trust\":</b>\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 "<b>It isn't DNS</b>"
+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 ""
+"<b>Not reliable:</b>\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 ""
+"<b>Awkward, not real-time:</b>\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 ""
+"<b>Meta</b> - 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 ""
+"<b>PetName</b> - 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 "<b>HostsTxt</b> - Looks up in the following files, in order:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/discussions/naming.html:234
+msgid ""
+"<b>AddressDB</b> - Each host is listed in a separate file in a addressDb/"
+" directory."
+msgstr ""
+
+#: i2p2www/pages/site/docs/discussions/naming.html:237
+msgid ""
+"<b>Eepget</b> - 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 ""
+"<b>Exec</b> - 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 "<b>Dummy</b> - 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 <a "
+"href=\"%(todo)s#hashcash\">proof of work</a>."
+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/elgamal-aes.html:2
+msgid "ElGamal/AES + SessionTag Encryption"
+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:508
+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:524
+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:</p>"
+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"
+"<a href=\"%(commonstructures)s#type_SessionKey\">Session Key</a>\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"
+"<a href=\"%(cryptography)s#elgamal\">using ElGamal</a>\n"
+"and the encrypted block is 514 bytes long.\n"
+"</p>"
+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:254
+msgid "Minimum length: 48 bytes"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/elgamal-aes.html:257
+#, python-format
+msgid ""
+"The data is then <a href=\"%(cryptography)s\">AES Encrypted</a>,\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"
+"</p>"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/elgamal-aes.html:266
+#, python-format
+msgid ""
+"Actual max payload length, and max block length, is less than 64 KB; see "
+"the <a href=\"%(i2np)s\">I2NP Overview</a>."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/elgamal-aes.html:269
+msgid "New Session Key is currently unused and is never present."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/elgamal-aes.html:274
+msgid "Existing Session Message Specification"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/elgamal-aes.html:275
+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:283
+msgid ""
+"The existing session message is\n"
+"as follows:"
+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 <a "
+"href=\"#new\">New Session Message</a>."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/elgamal-aes.html:331
+msgid "Session Tag Configuration Options"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/elgamal-aes.html:332
+#, python-format
+msgid ""
+"As of release 0.9.2, the client may configure the default number of "
+"Session Tags to send\n"
+"and the low tag threshold for the current session.\n"
+"For brief streaming connections or datagrams, these options may be used "
+"to significantly reduce bandwidth.\n"
+"See the <a href=\"%(i2cp)s#options\">I2CP options specification</a> for "
+"details.\n"
+"The session settings may also be overridden on a per-message basis.\n"
+"See the <a href=\"%(i2cpspec)s#msg_SendMessageExpires\">I2CP Send Message"
+" Expires specification</a> for details."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/elgamal-aes.html:345
+msgid ""
+"There are many possible areas to tune the Session Key Manager's "
+"algorithms;\n"
+"some may interact with the streaming library behavior, or have "
+"significant\n"
+"impact on overall performance."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/elgamal-aes.html:352
+msgid ""
+"The number of tags delivered could depend on message size, keeping in "
+"mind\n"
+"the eventual padding to 1KB at the tunnel message layer."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/elgamal-aes.html:357
+msgid ""
+"Clients could send an estimate of session lifetime to the router, as an "
+"advisory\n"
+"on the number of tags required."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/elgamal-aes.html:362
+msgid ""
+"Delivery of too few tags causes the router to fall back to an expensive "
+"ElGamal encryption."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/elgamal-aes.html:366
+msgid ""
+"The router may assume delivery of Session Tags, or await acknowledgement "
+"before using them;\n"
+"there are tradeoffs for each strategy."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/elgamal-aes.html:371
+msgid ""
+"For very brief messages, almost the full 222 bytes of the pre-IV and "
+"padding fields in the ElGamal block\n"
+"could be used for the entire message, instead of establishing a session."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/elgamal-aes.html:376
+msgid ""
+"Evaluate padding strategy; currently we pad to a minimum of 128 bytes.\n"
+"Would be better to add a few tags to small messages than pad."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/elgamal-aes.html:381
+msgid ""
+"Perhaps things could be more efficient if the Session Tag system was "
+"bidirectional,\n"
+"so tags delivered in the 'forward' path could be used in the 'reverse' "
+"path,\n"
+"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:389
+#, python-format
+msgid ""
+"Change from Session Tags to\n"
+"<a href=\"%(futureperf)s#prng\">a synchronized PRNG</a>."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/elgamal-aes.html:394
+#, python-format
+msgid ""
+"Several of these ideas may require a new I2NP message type, or\n"
+"set a flag in the\n"
+"<a "
+"href=\"%(tunnelmessage)s#struct_TunnelMessageDeliveryInstructions\">Delivery"
+" Instructions</a>,\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:3
+msgid "March 2014"
+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"
+"<a href=\"http://www.cs.princeton.edu/~mfreed/\">Michael J. Freedman</a>\n"
+"in Roger Dingledine's Free Haven \n"
+"<a href=\"http://www.freehaven.net/papers.html\">Master's thesis</a> "
+"Section 8.1.1 (June 2000), as derived from \n"
+"<a href=\"http://www.onion-router.net/\">Onion Routing</a>."
+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 <a href=\"%(comparisons)s\">network comparisons</a>) 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"
+"<a href=\"http://www.onion-router.net/Publications.html\">large amount of"
+" academic research on onion routing</a>,\n"
+"<a href=\"http://freehaven.net/anonbib/topic.html\">Tor, and similar "
+"mixnets</a>."
+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"
+"<a href=\"%(elgamalaes)s\">ElGamal/AES+SessionTag</a> 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"
+"<a href=\"%(tunnelimpl)s\">tunnel implementation page</a>.\n"
+"Tunnel building details are defined on\n"
+"<a href=\"%(tunnelcreation)s\">this page</a>.\n"
+"We use\n"
+"<a href=\"%(elgamalaes)s\">ElGamal/AES+SessionTag</a> 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"
+"<a href=\"%(i2np)s\">I2NP messages</a>, and\n"
+"<a href=\"%(i2npspec)s#msg_Garlic\">Garlic Messages</a> are not used to "
+"build tunnels.\n"
+"We do not bundle multiple\n"
+"<a href=\"%(i2np)s\">I2NP messages</a> into a single\n"
+"<a href=\"%(i2npspec)s#msg_Garlic\">Garlic Message</a> 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"
+"<a href=\"%(commonstructures)s#struct_Destination\">Destinations</a>.\n"
+"Just as within a single tunnel, we use\n"
+"<a href=\"%(elgamalaes)s\">ElGamal/AES+SessionTag</a> for the encryption."
+"\n"
+"Each client message as delivered to the router through the\n"
+"<a href=\"%(i2cp)s\">I2CP interface</a> becomes a single\n"
+"<a href=\"%(i2npspec)s#struct_GarlicClove\">Garlic Clove</a>\n"
+"with its own\n"
+"<a href=\"%(i2npspec)s#struct_GarlicCloveDeliveryInstructions\">Delivery "
+"Instructions</a>,\n"
+"inside a\n"
+"<a href=\"%(i2npspec)s#msg_Garlic\">Garlic Message</a>.\n"
+"Delivery Instructions may specify a Destination, Router, or Tunnel."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/garlic-routing.html:171
+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:176
+msgid "Garlic Message Cloves"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/garlic-routing.html:179
+#, python-format
+msgid ""
+"A\n"
+"<a href=\"%(i2npspec)s#msg_DeliveryStatus\">Delivery Status Message</a>,\n"
+"with\n"
+"<a href=\"%(i2npspec)s#struct_GarlicCloveDeliveryInstructions\">Delivery "
+"Instructions</a>\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:192
+#, python-format
+msgid ""
+"A\n"
+"<a href=\"%(i2npspec)s#msg_DatabaseStore\">Database Store Message</a>,\n"
+"containing a\n"
+"<a href=\"%(commonstructures)s#struct_LeaseSet\">LeaseSet</a>\n"
+"for the originating Destination, with\n"
+"<a href=\"%(i2npspec)s#struct_GarlicCloveDeliveryInstructions\">Delivery "
+"Instructions</a>\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"
+"<a href=\"%(netdb)s\">network database page</a>."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/garlic-routing.html:210
+#, python-format
+msgid ""
+"By default, the Delivery Status and Database Store Messages\n"
+"are bundled when the local LeaseSet changes, when additional\n"
+"<a href=\"%(commonstructures)s#type_SessionTag\">Session Tags</a>\n"
+"are delivered, or if the messages have not been bundled in the previous "
+"minute.\n"
+"As of release 0.9.2, the client may configure the default number of "
+"Session Tags to send\n"
+"and the low tag threshold for the current session.\n"
+"See the <a href=\"%(i2cp)s#options\">I2CP options specification</a> for "
+"details.\n"
+"The session settings may also be overridden on a per-message basis.\n"
+"See the <a href=\"%(i2cpspec)s#msg_SendMessageExpires\">I2CP Send Message"
+" Expires specification</a> for details."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/garlic-routing.html:224
+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:229
+msgid ""
+"As of release 0.9.12, the Delivery Status Message is wrapped in another "
+"Garlic Message\n"
+"by the originator so that the contents are encrypted and not visible to "
+"routers on the return path."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/garlic-routing.html:235
+msgid "Storage to the Floodfill Network Database"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/garlic-routing.html:236
+#, python-format
+msgid ""
+"As explained on the\n"
+"<a href=\"%(netdb)s#delivery\">network database page</a>,\n"
+"local\n"
+"<a href=\"%(commonstructures)s#struct_LeaseSet\">LeaseSets</a>\n"
+"are sent to floodfill routers in a\n"
+"<a href=\"%(i2npspec)s#msg_DatabaseStore\">Database Store Message</a>\n"
+"wrapped in a\n"
+"<a href=\"%(i2npspec)s#msg_Garlic\">Garlic Message</a>\n"
+"so it is not visible to the tunnel's outbound gateway."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/garlic-routing.html:252
+#, 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"
+"<a "
+"href=\"%(tunnelmessage)s#struct_TunnelMessageDeliveryInstructions\">tunnel"
+" message Delivery Instructions</a>,\n"
+"a wide spectrum of batching, delay, mixing, and routing strategies are "
+"possible."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/garlic-routing.html:260
+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:267
+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:273
+#, python-format
+msgid ""
+"As a part of\n"
+"<a href=\"%(elgamalaes)s\">ElGamal/AES encryption</a>,\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:282
+#, python-format
+msgid ""
+"Encryption of additional messages to and from the\n"
+"<a href=\"%(netdb)s#delivery\">floodfill routers</a>."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/garlic-routing.html:290
+#: i2p2www/pages/site/docs/how/peer-selection.html:296
+msgid "References"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/garlic-routing.html:292
+msgid ""
+"The term garlic routing was first coined in Roger Dingledine's Free Haven"
+" \n"
+"<a href=\"http://www.freehaven.net/papers.html\">Master's thesis</a> "
+"(June 2000),\n"
+"see Section 8.1.1 authored by\n"
+"<a href=\"http://www.cs.princeton.edu/~mfreed/\">Michael J. Freedman</a>."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/garlic-routing.html:299
+msgid "Onion router publications"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/garlic-routing.html:301
+msgid "Onion Routing on Wikipedia"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/garlic-routing.html:303
+msgid "Garlic Routing on Wikipedia"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/garlic-routing.html:305
+#, python-format
+msgid ""
+"<a href=\"%(meeting58)s\">I2P Meeting 58</a> (2003) discussing the "
+"implementation of garlic routing"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/garlic-routing.html:311
+msgid "Free Haven publications"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/garlic-routing.html:313
+msgid ""
+"Onion routing was first described in <a href=\"http://www.onion-"
+"router.net/Publications/IH-1996.pdf\">Hiding Routing Information</a>\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 to How I2P Works"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/intro.html:4
+msgid ""
+"I2P is a project to build, deploy, and maintain a network supporting "
+"secure and anonymous\n"
+"communication. People using I2P are in control of the tradeoffs between "
+"anonymity, reliability,\n"
+"bandwidth usage, and latency. There is no central point in the network on"
+" which pressure can be\n"
+"exerted to compromise the integrity, security, or anonymity of the "
+"system. The network supports\n"
+"dynamic reconfiguration in response to various attacks, and has been "
+"designed to make use of\n"
+"additional resources as they become available. Of course, all aspects of "
+"the network are open and\n"
+"freely available."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/intro.html:14
+msgid ""
+"Unlike many other anonymizing networks, I2P doesn't try to provide "
+"anonymity by hiding the\n"
+"originator of some communication and not the recipient, or the other way "
+"around. I2P is designed to\n"
+"allow peers using I2P to communicate with each other anonymously &mdash; "
+"both sender and recipient\n"
+"are unidentifiable to each other as well as to third parties. For "
+"example, today there are both\n"
+"in-I2P web sites (allowing anonymous publishing / hosting) as well as "
+"HTTP proxies to the normal web\n"
+"(allowing anonymous web browsing). Having the ability to run servers "
+"within I2P is essential, as it\n"
+"is quite likely that any outbound proxies to the normal Internet will be "
+"monitored, disabled, or\n"
+"even taken over to attempt more malicious attacks."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/intro.html:25
+#, python-format
+msgid ""
+"The network itself is message oriented - it is essentially a secure and "
+"anonymous IP layer, where\n"
+"messages are addressed to cryptographic keys (Destinations) and can be "
+"significantly larger than IP\n"
+"packets. Some example uses of the network include \"eepsites\" "
+"(webservers hosting normal web\n"
+"applications within I2P), a BitTorrent client (\"I2PSnark\"), or a "
+"distributed data store. With the\n"
+"help of the <a href=\"%(i2ptunnel)s\">I2PTunnel</a> application, we are "
+"able to stream traditional\n"
+"TCP/IP applications over I2P, such as SSH, IRC, a squid proxy, and even "
+"streaming audio. Most people\n"
+"will not use I2P directly, or even need to know they're using it. Instead"
+" their view will be of one\n"
+"of the I2P enabled applications, or perhaps as a little controller app to"
+" turn on and off various\n"
+"proxies to enable the anonymizing functionality."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/intro.html:37
+#, python-format
+msgid ""
+"An essential part of designing, developing, and testing an anonymizing "
+"network is to define the <a\n"
+"href=\"%(threatmodel)s\">threat model</a>, 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, <i>all on the same network</i>, where each one's messages are "
+"essentially indistinguishable\n"
+"from the others."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/intro.html:48
+msgid "Why?"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/intro.html:49
+#, python-format
+msgid ""
+"There are a multitude of reasons why we need a system to support "
+"anonymous communication, and\n"
+"everyone has their own personal rationale. There are many <a "
+"href=\"%(comparisons)s\">other\n"
+"efforts</a> 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:56
+msgid "How?"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/intro.html:58
+#, python-format
+msgid ""
+"The network at a glance is made up of a set of nodes (\"routers\") with a"
+" number of unidirectional\n"
+"inbound and outbound virtual paths (\"tunnels\", as outlined on the <a "
+"href=\"%(tunnelrouting)s\">tunnel routing</a> 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"
+"<a href=\"%(netdb)s\">network database</a> (using a modification of the "
+"Kademlia algorithm) for\n"
+"distributing routing and contact information securely."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/intro.html:71
+msgid "Network topology example"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/intro.html:73
+msgid ""
+"In the above, Alice, Bob, Charlie, and Dave are all running routers with "
+"a single Destination on\n"
+"their local router. They each have a pair of 2-hop inbound tunnels per "
+"destination (labeled 1, 2, 3,\n"
+"4, 5 and 6), and a small subset of each of those router's outbound tunnel"
+" pool is shown with 2-hop\n"
+"outbound tunnels. For simplicity, Charlie's inbound tunnels and Dave's "
+"outbound tunnels are not\n"
+"shown, nor are the rest of each router's outbound tunnel pool (typically "
+"stocked with a few tunnels\n"
+"at a time). When Alice and Bob talk to each other, Alice sends a message "
+"out one of her (pink)\n"
+"outbound tunnels targeting one of Bob's (green) inbound tunnels (tunnel 3"
+" or 4). She knows to send\n"
+"to those tunnels on the correct router by querying the network database, "
+"which is constantly updated\n"
+"as new leases are authorized and old ones expire."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/intro.html:85
+#, python-format
+msgid ""
+"If Bob wants to reply to Alice, he simply goes through the same process -"
+" send a message out one of\n"
+"his outbound tunnels targeting one of Alice's inbound tunnels (tunnel 1 "
+"or 2). To make things\n"
+"easier, most messages sent between Alice and Bob are <a "
+"href=\"%(garlicrouting)s\">garlic</a>\n"
+"wrapped, bundling the sender's own current lease information so that the "
+"recipient can reply\n"
+"immediately without having to look in the network database for the "
+"current data."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/intro.html:93
+#, python-format
+msgid ""
+"To deal with a wide range of attacks, I2P is fully distributed with no "
+"centralized resources - and\n"
+"hence there are no directory servers keeping statistics regarding the "
+"performance and reliability of\n"
+"routers within the network. As such, each router must keep and maintain "
+"profiles of various routers\n"
+"and is responsible for selecting appropriate peers to meet the anonymity,"
+" performance, and\n"
+"reliability needs of the users, as described in the <a "
+"href=\"%(peerselection)s\">peer selection</a>\n"
+"page."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/intro.html:102
+#, python-format
+msgid ""
+"The network itself makes use of a significant number of <a "
+"href=\"%(cryptography)s\">cryptographic\n"
+"techniques and algorithms</a> - 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 <a "
+"href=\"%(elgamalaes)s\">ElGamal / AES+SessionTag</a>."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/intro.html:110
+msgid ""
+"Content sent over I2P is encrypted through three layers garlic encryption"
+" (used to verify the\n"
+"delivery of the message to the recipient), tunnel encryption (all "
+"messages passing through a tunnel\n"
+"is encrypted by the tunnel gateway to the tunnel endpoint), and inter "
+"router transport layer\n"
+"encryption (e.g. the TCP transport uses AES256 with ephemeral keys)."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/intro.html:117
+msgid ""
+"End-to-end (I2CP) encryption (client application to server application) "
+"was disabled in I2P release\n"
+"0.6; end-to-end (garlic) encryption (I2P client router to I2P server "
+"router) from Alice's router \"a\"\n"
+"to Bob's router \"h\" remains. Notice the different use of terms! All "
+"data from a to h is end-to-end\n"
+"encrypted, but the I2CP connection between the I2P router and the "
+"applications is not end-to-end\n"
+"encrypted! A and h are the routers of Alice and Bob, while Alice and Bob "
+"in following chart are the\n"
+"applications running atop of I2P."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/intro.html:126
+msgid "End to end layered encryption"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/intro.html:128
+#, python-format
+msgid ""
+"The specific use of these algorithms are outlined <a "
+"href=\"%(cryptography)s\">elsewhere</a>."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/intro.html:132
+msgid ""
+"The two main mechanisms for allowing people who need strong anonymity to "
+"use the network are\n"
+"explicitly delayed garlic routed messages and more comprehensive tunnels "
+"to include support for\n"
+"pooling and mixing messages. These are currently planned for release 3.0,"
+" but garlic routed messages\n"
+"with no delays and FIFO tunnels are currently in place. Additionally, the"
+" 2.0 release will allow\n"
+"people to set up and operate behind restricted routes (perhaps with "
+"trusted peers), as well as the\n"
+"deployment of more flexible and anonymous transports."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/intro.html:141
+#, python-format
+msgid ""
+"Some questions have been raised with regards to the scalability of I2P, "
+"and reasonably so. There\n"
+"will certainly be more analysis over time, but peer lookup and "
+"integration should be bounded by\n"
+"<code>O(log(N))</code> due to the <a href=\"%(netdb)s\">network "
+"database</a>'s algorithm, while end\n"
+"to end messages should be <code>O(1)</code> (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:150
+msgid "When?"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/intro.html:151
+#, python-format
+msgid ""
+"I2P initially began in Feb 2003 as a proposed modification to <a\n"
+"href=\"http://freenetproject.org\">Freenet</a> to allow it to use "
+"alternate transports, such as <a\n"
+"href=\"%(jms)s\">JMS</a>, 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"
+" <a href=\"%(roadmap)s\">roadmap</a>."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/intro.html:161
+msgid "Who?"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/intro.html:162
+#, python-format
+msgid ""
+"We have a small <a href=\"%(team)s\">team</a> 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 <a href=\"http://java.com/en/\">Sun Java SE</a> and other Java Virtual"
+" Machines."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/intro.html:173
+msgid "Where?"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/intro.html:174
+#, python-format
+msgid ""
+"Anyone interested should join us on the IRC channel #i2p-dev (hosted "
+"concurrently on irc.freenode.net,\n"
+"irc.postman.i2p, irc.echelon.i2p, irc.dg.i2p and irc.oftc.net). There are"
+" currently no\n"
+"scheduled development meetings, however <a href=\"%(meetings)s\">archives"
+" are available</a>."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/intro.html:180
+#, python-format
+msgid "The current source is available in <a href=\"%(monotone)s\">monotone</a>."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/intro.html:185
+#, python-format
+msgid "See <a href=\"%(docs)s\">the Index to Technical Documentation</a>."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:2
+msgid "The Network Database"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:3
+msgid "April 2018"
+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 (<b>RouterInfos</b>) "
+"and destination contact\n"
+"information (<b>LeaseSets</b>). 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 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 signing key"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:39
+msgid "Expected Options"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:41
+msgid ""
+"The following text options, while not strictly required, are expected\n"
+"to be present:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:47
+msgid ""
+"Capabilities flags - used to indicate floodfill participation, "
+"approximate bandwidth, and perceived reachability"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:49
+#: i2p2www/pages/site/docs/how/network-database.html:287
+msgid "Floodfill"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:50
+msgid "Hidden"
+msgstr "Peidetud"
+
+#: i2p2www/pages/site/docs/how/network-database.html:51
+#, python-format
+msgid "Under %(amount)s shared bandwidth"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:52
+#: i2p2www/pages/site/docs/how/network-database.html:53
+#: i2p2www/pages/site/docs/how/network-database.html:54
+#: i2p2www/pages/site/docs/how/network-database.html:55
+#: i2p2www/pages/site/docs/how/network-database.html:56
+#, python-format
+msgid "%(amount)s shared bandwidth"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:52
+msgid "default"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:57
+msgid "Reachable"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:58
+msgid "Unreachable"
+msgstr "Kättesaadamatud"
+
+#: i2p2www/pages/site/docs/how/network-database.html:59
+#, python-format
+msgid "Over %(amount)s shared bandwidth"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:66
+msgid "The core library version, always the same as the router version"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:70
+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:73
+msgid "Used to determine compatibility with newer features and messages"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:76
+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 uptime was more than 60m"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:82
+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:91
+msgid "Additional Options"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:93
+#, 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 <a href=\"http://%(stats)s/\">%(stats)s</a>\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:104
+msgid "Exploratory tunnel build success, reject, and timeout rates"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:105
+msgid "1 hour average number of participating tunnels"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:108
+msgid ""
+"Floodfill routers publish additional data on the number of entries in "
+"their network database."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:112
+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:119
+msgid "Family Options"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:121
+msgid ""
+"As of release 0.9.24, routers may declare that they are part of a "
+"\"family\", operated by the same entity.\n"
+"Multiple routers in the same family will not be used in a single tunnel."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:126
+msgid "The family options are:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:132
+msgid "The family name"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:147
+msgid "RouterInfo Expiration"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:148
+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:155
+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:158
+msgid "There is no expiration if there are 25 or less RouterInfos."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:161
+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:166
+#, python-format
+msgid ""
+"RouterInfos containing <a href=\"%(ssu)s\">SSU</a> 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:170
+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:176
+msgid "RouterInfo Persistent Storage"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:178
+msgid ""
+"RouterInfos are periodically written to disk so that they are available "
+"after a restart."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:186
+msgid "RouterInfo specification"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:189
+msgid "RouterInfo Javadoc"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:194
+msgid ""
+"The second piece of data distributed in the netDb is a \"LeaseSet\" - "
+"documenting\n"
+"a group of <b>tunnel entry points (leases)</b> for a particular client "
+"destination.\n"
+"Each of these leases specify the following information:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:200
+msgid "The tunnel gateway router (by specifying its identity)"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:201
+msgid "The tunnel ID on that router to send messages with (a 4 byte number)"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:202
+msgid "When that tunnel will expire."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:204
+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:209
+msgid "In addition to these leases, the LeaseSet includes:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:213
+msgid ""
+"The destination itself (a 2048bit ElGamal encryption key, a signing key "
+"and a certificate)"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:214
+msgid ""
+"Additional encryption public key: used for end-to-end encryption of "
+"garlic messages"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:215
+msgid ""
+"Additional signing public key: intended for LeaseSet revocation, but is "
+"currently unused."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:216
+msgid ""
+"Signature of all the LeaseSet data, to make sure the Destination "
+"published the LeaseSet."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:220
+msgid "Lease specification"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:222
+msgid "LeaseSet specification"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:225
+msgid "Lease Javadoc"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:227
+msgid "LeaseSet Javadoc"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:231
+msgid "Unpublished LeaseSets"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:232
+msgid ""
+"A LeaseSet for a destination used only for outgoing connections is "
+"<i>unpublished</i>.\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 <a href=\"#lsp\">I2NP storage messages</a>."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:242
+msgid "Revoked LeaseSets"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:243
+msgid ""
+"A LeaseSet may be <i>revoked</i> 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:250
+msgid "Encrypted LeaseSets"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:251
+msgid ""
+"In an <i>encrypted</i> LeaseSet, all Leases are encrypted with a separate"
+" 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:260
+msgid "LeaseSet Expiration"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:261
+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:266
+msgid "LeaseSet Persistent Storage"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:267
+msgid ""
+"There is no persistent storage of LeaseSet data since they expire so "
+"quickly."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:272
+msgid "Bootstrapping"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:273
+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 "
+"<code>routerInfo-$hash.dat</code>\n"
+"file and storing it in your <code>netDb/</code> 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:288
+msgid ""
+"The floodfill netDb is a simple distributed storage mechanism.  The "
+"storage\n"
+"algorithm is simple: send the data to the closest peer that has "
+"advertised\n"
+"itself as a floodfill router. When the peer in the floodfill netDb "
+"receives a\n"
+"netDb store from a peer not in the floodfill netDb, they send it to a "
+"subset of\n"
+"the floodfill netDb-peers. The peers selected are the ones closest "
+"(according\n"
+"to the <a href=\"#kad\">XOR-metric</a>) to a specific key."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:297
+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:302
+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:309
+msgid "Floodfill Router Opt-in"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:311
+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:318
+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:328
+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:334
+msgid ""
+"With the current rules for automatic opt-in, approximately 6&#37; of\n"
+"the routers in the network are floodfill routers."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:339
+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:349
+msgid "Floodfill Router Roles"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:350
+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:358
+msgid "Kademlia Closeness Metric"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:359
+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 <a href"
+"=\"#sybil-partial\">Sybil attacks</a>.\n"
+"Instead of the SHA256 hash of the key being looked up of stored, the "
+"SHA256 hash is taken\n"
+"of the 32-byte binary search key appended with the UTC date represented "
+"as an 8-byte ASCII string yyyyMMdd, i.e. SHA256(key + yyyyMMdd).\n"
+"This is called the \"routing key\", and it changes every day at midnight "
+"UTC.\n"
+"Only the search key is modified in this way, not the floodfill router "
+"hashes.\n"
+"The daily transformation of the DHT is sometimes called \"keyspace "
+"rotation\",\n"
+"although it isn't strictly a rotation."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:372
+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:379
+msgid "Storage, Verification, and Lookup Mechanics"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:381
+msgid "RouterInfo Storage to Peers"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:382
+#, python-format
+msgid ""
+"<a href=\"%(i2np)s\">I2NP</a> DatabaseStoreMessages containing the local "
+"RouterInfo are exchanged with peers\n"
+"as a part of the initialization of a <a href=\"%(ntcp)s\">NTCP</a>\n"
+"or <a href=\"%(ssu)s\">SSU</a> transport connection."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:389
+msgid "LeaseSet Storage to Peers"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:390
+#, python-format
+msgid ""
+"<a href=\"%(i2np)s\">I2NP</a> 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:398
+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:407
+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:420
+msgid "RouterInfo Storage to Floodfills"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:421
+#, python-format
+msgid ""
+"A router publishes its own RouterInfo by directly connecting to a "
+"floodfill router\n"
+"and sending it a <a href=\"%(i2np)s\">I2NP</a> 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"
+"<a href=\"%(i2np)s\">I2NP</a> DeliveryStatusMessage,\n"
+"with the Message ID set to the value of the Reply Token."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:435
+msgid "LeaseSet Storage to Floodfills"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:436
+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:441
+#, python-format
+msgid ""
+"A router publishes a local LeaseSet by\n"
+"sending a <a href=\"%(i2np)s\">I2NP</a> 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"
+"<a href=\"%(i2np)s\">I2NP</a> 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:454
+msgid "Flooding"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:455
+#, 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:466
+#, python-format
+msgid ""
+"The floodfill then directly connects to each of those peers\n"
+"and sends it a <a href=\"%(i2np)s\">I2NP</a> 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:476
+msgid "RouterInfo and LeaseSet Lookup"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:477
+#, python-format
+msgid ""
+"The <a href=\"%(i2np)s\">I2NP</a> 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:483
+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:487
+#, python-format
+msgid ""
+"If the key is found locally by the floodfill router, it responds with a\n"
+"<a href=\"%(i2np)s\">I2NP</a> DatabaseStoreMessage.\n"
+"If the key is not found locally by the floodfill router, it responds with"
+" a\n"
+"<a href=\"%(i2np)s\">I2NP</a> DatabaseSearchReplyMessage\n"
+"containing a list of other floodfill routers close to the key."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:495
+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:502
+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:509
+#, python-format
+msgid ""
+"(Reference: <a href=\"%(pdf)s\">Hashing it out in Public</a> Sections "
+"2.2-2.3 for terms below in italics)"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:513
+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 <i>recursive</i> nor <i>iterative</i> routing for lookups was "
+"implemented.\n"
+"Queries were sent through <i>multiple routes simultaneously</i>\n"
+"to <i>reduce the chance of query failure</i>."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:524
+msgid ""
+"As of release 0.8.9, <i>iterative lookups</i> 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:536
+msgid ""
+"<i>Node IDs</i> are <i>verifiable</i> 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"
+"<i>detailed knowledge of the neighborhood of the destination ID space</i>."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:545
+msgid "RouterInfo Storage Verification"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:546
+#, 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"
+"<a href=\"%(egger2013)s\">Practical Attacks Against the I2P Network</a>.\n"
+"It is not clear if verification can be redesigned to be done safely."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:553
+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:561
+msgid "LeaseSet Storage Verification"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:562
+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:572
+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:580
+msgid "Exploration"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:581
+#, python-format
+msgid ""
+"<i>Exploration</i> 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 <a "
+"href=\"%(i2np)s\">I2NP</a> DatabaseLookupMessage, looking for a random "
+"key.\n"
+"As this lookup will fail, the floodfill would normally respond with a\n"
+"<a href=\"%(i2np)s\">I2NP</a> 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:595
+msgid "Notes on Lookup Responses"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:596
+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:606
+msgid "MultiHoming"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:608
+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:618
+msgid "Threat Analysis"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:619
+#, python-format
+msgid ""
+"Also discussed on <a href=\"%(threatmodel)s#floodfill\">the threat model "
+"page</a>."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:623
+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:630
+msgid "General Mitigation Through Growth"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:631
+#, 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:638
+msgid "General Mitigation Through Redundancy"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:639
+#, 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:644
+msgid "Forgeries"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:645
+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:650
+msgid "Slow or Unresponsive"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:651
+#, python-format
+msgid ""
+"Each router maintains an expanded set of statistics in the\n"
+"<a href=\"%(peerselection)s\">peer profile</a> 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:658
+msgid "Average response time"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:659
+msgid "Percentage of queries answered with the data requested"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:660
+msgid "Percentage of stores that were successfully verified"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:661
+msgid "Last successful store"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:662
+msgid "Last successful lookup"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:663
+msgid "Last response"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:666
+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:676
+msgid "Sybil Attack (Full Keyspace)"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:677
+#, python-format
+msgid ""
+"An attacker may mount a <a href=\"%(url)s\">Sybil attack</a>\n"
+"by creating a large number of floodfill routers spread throughout the "
+"keyspace."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:682
+#, python-format
+msgid ""
+"(In a related example, a researcher recently created a\n"
+"<a href=\"%(url)s\">large number of Tor relays</a>.)\n"
+"If successful, this could be an effective DOS attack on the entire "
+"network."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:688
+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:696
+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:701
+msgid ""
+"Ask everyone in the network to enable floodfill manually (fight Sybil "
+"with more Sybil)"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:702
+msgid "Release a new software version that includes the hardcoded \"bad\" list"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:703
+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:707
+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:708
+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:717
+msgid "This attack becomes more difficult as the network size grows."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:723
+msgid "Sybil Attack (Partial Keyspace)"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:724
+#, python-format
+msgid ""
+"An attacker may mount a <a href=\"%(url)s\">Sybil attack</a>\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:733
+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:741
+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:753
+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:761
+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:771
+msgid "Bootstrap Attacks"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:772
+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:779
+msgid "Several defenses are possible, and most of these are planned:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:783
+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:787
+msgid "Bundling reseed data in the installer"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:790
+msgid "Defenses that are implemented:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:794
+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:798
+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:803
+msgid ""
+"As of release 0.9.14, reseed data is bundled into a signed zip file and\n"
+"the signature is verified when downloaded."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:811
+msgid "Query Capture"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:812
+#, python-format
+msgid ""
+"See also <a href=\"#lookup\">lookup</a>\n"
+"(Reference: <a href=\"%(pdf)s\">Hashing it out in Public</a> Sections "
+"2.2-2.3 for terms below in italics)"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:817
+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:822
+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:829
+#, python-format
+msgid ""
+"As of release 0.8.9, <i>iterative lookups</i> are implemented.\n"
+"For floodfill router references returned in a\n"
+"<a href=\"%(i2np)s\">I2NP</a> 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 <i>verifiably correct</i>.\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"
+"<a href=\"%(pdf)s\">Hashing it out in Public</a>\n"
+"is much more difficult."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:848
+msgid "DHT-Based Relay Selection"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:849
+#, python-format
+msgid "(Reference: <a href=\"%(pdf)s\">Hashing it out in Public</a> Section 3)"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:853
+#, python-format
+msgid ""
+"This doesn't have much to do with floodfill, but see\n"
+"the <a href=\"%(peerselection)s\">peer selection page</a>\n"
+"for a discussion of the vulnerabilities of peer selection for tunnels."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:859
+msgid "Information Leaks"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:860
+#, python-format
+msgid ""
+"(Reference: <a href=\"%(pdf)s\">In Search of an Anonymous and Secure "
+"Lookup</a> Section 3)"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:864
+#, 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 <a href=\"%(peerselection)s\">peer "
+"selection</a> and\n"
+"<a href=\"%(tunnelrouting)s\">tunnel building</a> 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:875
+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:883
+#, 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 <i>f</i> = 0.2 (20&#37; malicious nodes, as "
+"specifed in the paper)\n"
+"we expect that many of the Sybil threats we describe\n"
+"(<a href=\"%(threatmodel)s#sybil\">here</a>,\n"
+"<a href=\"#sybil\">here</a> and\n"
+"<a href=\"#sybil-partial\">here</a>)\n"
+"become problematic for several reasons."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:897
+msgid "Moved to the netdb discussion page"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:901
+msgid "End-to-end encryption of additional netDb lookups and responses."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:905
+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 ""
+"<b>Peer profiling</b> is the process of collecting data based on the "
+"<b>observed</b> performance\n"
+"of other routers or peers, and classifying those peers into groups.\n"
+"Profiling does <b>not</b> use any claimed performance data published by "
+"the peer itself\n"
+"in the <a href=\"%(netdb)s\">network database</a>."
+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 <a href=\"%(netdb)s\">network database</a> 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:289
+msgid "Peer Selection"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/peer-selection.html:28
+msgid ""
+"<b>Peer selection</b> 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 <b>only</b> 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"
+"<a href=\"%(threatmodel)s#timing\">timing attacks</a>\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"
+"<a href=\"%(pdf)s\">Peer Profiling and Selection in the I2P Anonymous "
+"Network</a>\n"
+"presented at <a href=\"%(url)s\">PET-CON 2009.1</a>.\n"
+"See <a href=\"#notes\">below</a> for notes on minor changes since the "
+"paper was published."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/peer-selection.html:65
+msgid "Profiles"
+msgstr "Profiilid"
+
+#: 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 <a href=\"%(url)s\">code</a>."
+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 "Kiirus"
+
+#: 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 "Maht"
+
+#: 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"
+"<a href=\"%(url)s\">ProfileOrganizer</a>."
+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 <a href=\"http://blog.torproject.org/blog"
+"/one-cell-enough\">some attacks</a>,\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&#37; 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 <a href=\"%(pdf)s\">predecessor attack</a>\n"
+"<a href=\"%(pdf2008)s\">(2008 update)</a>.\n"
+"More information is on the <a href=\"%(tunnelimpl)s#ordering\">tunnel "
+"page</a>."
+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"
+"<a href=\"%(pdf)s\">Peer Profiling and Selection in the I2P Anonymous "
+"Network</a>,\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 "I2P: A scalable framework for anonymous communication"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:5
+#: i2p2www/pages/site/docs/how/tech-intro.html:20
+#: i2p2www/pages/site/docs/transport/ssu.html:342
+msgid "Introduction"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:7
+msgid "I2P Operation"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:12
+#: i2p2www/pages/site/docs/how/tech-intro.html:397
+msgid "Transport protocols"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:13
+#: i2p2www/pages/site/docs/how/tech-intro.html:454
+msgid "Cryptography"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:21
+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:30
+msgid ""
+"Applications available already provide the full range of typical Internet"
+" activities -\n"
+"<b>anonymous</b> 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:36
+msgid "Web browsing: using any existing browser that supports using a proxy."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:37
+msgid "Chat: IRC, Jabber, <a href=\"#app.i2pmessenger\">I2P-Messenger</a>."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:38
+msgid ""
+"File sharing: <a href=\"#app.i2psnark\">I2PSnark</a>, <a "
+"href=\"#app.robert\">Robert</a>, <a href=\"#app.imule\">iMule</a>, \n"
+"<a href=\"#app.i2phex\">I2Phex</a>, <a href=\"#app.pybit\">PyBit</a>, <a "
+"href=\"#app.i2pbt\">I2P-bt</a>\n"
+"and others."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:43
+msgid ""
+"E-mail: <a href=\"#app.i2pmail\">susimail</a> and <a href=\"#app.i2pbote"
+"\">I2P-Bote</a>."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:44
+msgid ""
+"Blog: using e.g. the pebble plugin or the distributed blogging software "
+"<a href=\"#app.syndie\">Syndie</a>."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:45
+msgid ""
+"Distributed Data Store: Save your data redundantly in the Tahoe-LAFS "
+"cloud over I2P."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:46
+msgid "Newsgroups: using any newsgroup reader that supports using a proxy."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:49
+msgid ""
+"Unlike web sites hosted within content distribution networks like <a "
+"href=\"#similar.freenet\">Freenet</a> \n"
+"or <a href=\"http://www.ovmj.org/GNUnet/\">GNUnet</a>, 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:57
+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 <a href=\"#app.streaming\">streaming</a> 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:74
+#, 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 <a "
+"href=\"%(site)s\">website</a>, \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 (<a "
+"href=\"#app.i2ptunnel\">I2PTunnel</a>, \n"
+"<a href=\"#app.i2pmail\">susimail</a>, <a "
+"href=\"#app.i2psnark\">I2PSnark</a>, <a href=\"#app.i2pbote\">I2P-"
+"Bote</a>, \n"
+"<a href=\"#app.i2phex\">I2Phex</a> and others.).\n"
+"<a href=\"%(halloffame)s\">Funding</a> 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:92
+msgid "Operation"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:94
+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:107
+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:118
+#: i2p2www/pages/site/docs/tunnels/implementation.html:105
+msgid "Inbound and outbound tunnel schematic"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:120
+msgid "Figure 1: Two types of tunnels exist: inbound and outbound."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:123
+msgid ""
+"Two types of tunnels exist:\n"
+"<b>\"outbound\" tunnels</b> send messages away from the tunnel creator,\n"
+"while <b>\"inbound\" tunnels</b> 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:140
+msgid ""
+"A third critical concept to understand is I2P's <b>\"network "
+"database\"</b> (or \"netDb\") \n"
+"- a pair of algorithms used to share network metadata. The two types of "
+"metadata \n"
+"carried are <b>\"routerInfo\"</b> and <b>\"leaseSets\"</b> - 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:151
+msgid "Inbound gateway for a tunnel that allows reaching a specific destination."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:152
+msgid "Time when a tunnel expires."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:153
+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:155
+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:160
+msgid ""
+"We can combine the above concepts to build successful connections in the "
+"network."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:164
+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:171
+msgid "Request information on other routers"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:173
+msgid "Build tunnel using router information"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:175
+msgid "Figure 2: Router information is used to build tunnels."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:178
+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"
+"<a href=\"#app.streaming\">streaming</a> 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:195
+msgid "Connect tunnels using LeaseSets"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:195
+msgid "Connect tunnels using leaseSets"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:197
+msgid "Figure 3: LeaseSets are used to connect outbound and inbound tunnels."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:200
+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 \"<a "
+"href=\"#op.garlic\">garlic \n"
+"encryption</a>\" 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:215
+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 <a href=\"#app.streaming\">streaming</a> library to view I2P as "
+"a streams \n"
+"based network."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:225
+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:240
+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:253
+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:266
+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:284
+msgid ""
+"Using this profile data, the simplest reasonable peer selection strategy "
+"is to\n"
+"pick peers randomly from the top tier (fast and high capacity), and this "
+"is\n"
+"currently deployed for client tunnels. Exploratory tunnels (used for "
+"netDb and\n"
+"tunnel management) pick peers randomly from the \"not failing\" tier "
+"(which\n"
+"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"
+"<a href=\"https://en.wikipedia.org/wiki/Hill_climbing\">hill "
+"climbing</a>. These\n"
+"strategies alone do however leak information regarding the peers in the\n"
+"router's top tier through predecessor and netDb harvesting attacks. In "
+"turn,\n"
+"several alternatives exist which, while not balancing the load as evenly,"
+" will\n"
+"address the attacks mounted by particular classes of adversaries."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:298
+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:318
+#, 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 <a href=\"%(tunnelimpl)s\">tunnel "
+"spec</a>."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:326
+#, python-format
+msgid ""
+"As mentioned earlier, I2P's netDb works to share the network's metadata.\n"
+"This is detailed in <a href=\"%(netdb)s\">the network database</a> page,\n"
+"but a basic explanation is available below."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:332
+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:339
+#, 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 <a href=\"http://en.wikipedia.org/wiki/Kademlia\">Kademlia "
+"algorithm</a>.\n"
+"The 'lookup' queries currently function differently, to avoid an "
+"important\n"
+"<a href=\"%(netdb)s#lookup\">security issue</a>.\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:349
+msgid "Two types of information are stored in the network database."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:353
+msgid ""
+"A <b>RouterInfo</b> stores information on a specific I2P router and how "
+"to contact it"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:354
+msgid ""
+"A <b>LeaseSet</b> stores information on a specific destination (e.g. I2P "
+"website, e-mail server...)"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:356
+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 <a href=\"http://www.pool.ntp.org/\">pool.ntp.org</a> round robin by"
+" default)\n"
+"and detecting skew between routers at the transport layer."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:364
+msgid "Some additional remarks are also important."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:369
+msgid "Unpublished and encrypted leasesets:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:370
+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:377
+msgid "Bootstrapping:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:378
+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:386
+msgid "Lookup scalability:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:387
+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:398
+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:406
+#, 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 <a href=\"%(ssu)s\">UDP-based one</a> - "
+"\"Secure \n"
+"Semireliable UDP\", or \"SSU\"."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:414
+#, python-format
+msgid "As described in the <a href=\"%(ssu)s\">SSU spec</a>:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:418
+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:428
+#, python-format
+msgid ""
+"Following the introduction of SSU, after issues with congestion collapse"
+" \n"
+"appeared, a new NIO-based TCP transport called <a "
+"href=\"%(ntcp)s\">NTCP</a> \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:438
+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:446
+#, 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 <a "
+"href=\"%(ntcp)s\">NTCP \n"
+"page</a>."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:455
+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. <a href=\"#op.tunnels\">Tunnel</a> 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:470
+msgid "Garlic messages"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:471
+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:486
+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 <a "
+"href=\"#future.variablelatency\">nontrivial \n"
+"delays</a> 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:499
+msgid "Session tags"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:500
+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:539
+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:549
+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:562
+msgid "Future"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:563
+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:569
+msgid "Restricted route operation"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:570
+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:582
+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:595
+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:617
+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:629
+msgid "Variable latency"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:630
+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:647
+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:655
+msgid "Open questions"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:657
+msgid "How to get rid of the timing constraint?"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:658
+msgid "Can we deal with the sessionTags more efficiently?"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:659
+msgid ""
+"What, if any, batching/mixing strategies should be made available on the "
+"tunnels?"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:660
+msgid ""
+"What other tunnel peer selection and ordering strategies should be "
+"available?"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:663
+msgid "Similar systems"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:665
+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:675
+#, python-format
+msgid "See also the <a href=\"%(comparisons)s\">Network Comparisons Page</a>."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:680
+#: i2p2www/pages/site/docs/how/tech-intro.html:745
+msgid "website"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:682
+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:703
+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:717
+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:727
+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 <a href=\"#future.restricted\">2.0</a>."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:733
+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:747
+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:766
+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:777
+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:793
+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 <a href=\"#app.streaming\">streaming"
+" library</a> \n"
+"as an implementation of an anonymous and secure TCP layer on top of it. "
+"Beyond \n"
+"that, <a href=\"#app.i2ptunnel\">I2PTunnel</a> 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:804
+msgid "Streaming library"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:805
+msgid ""
+"The I2P streaming library can be viewed as a generic streaming interface "
+"(mirroring TCP sockets),\n"
+"and the implementation supports a <a "
+"href=\"http://en.wikipedia.org/wiki/Sliding_Window_Protocol\">sliding "
+"window protocol</a>\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:815
+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:828
+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:835
+msgid "Naming library and addressbook"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:836
+#, python-format
+msgid ""
+"For more information see the <a href=\"%(naming)s\">Naming and "
+"Addressbook</a> page."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:840
+#: i2p2www/pages/site/docs/how/tech-intro.html:914
+#: i2p2www/pages/site/docs/how/tech-intro.html:961
+#: i2p2www/pages/site/docs/how/tech-intro.html:993
+#: i2p2www/pages/site/docs/how/tech-intro.html:1001
+#: i2p2www/pages/site/docs/how/tech-intro.html:1009
+#: i2p2www/pages/site/docs/how/tech-intro.html:1019
+#: i2p2www/pages/site/docs/how/tech-intro.html:1027
+#: i2p2www/pages/site/docs/how/tech-intro.html:1049
+#, python-format
+msgid "Developed by: %(dev)s"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:842
+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:862
+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:876
+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:886
+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:895
+msgid ""
+"The old Syndie bundled with I2P has been replaced by the new Syndie which"
+"\n"
+"is distributed separately. For more information see the <a "
+"href=\"http://syndie.i2p2.de/\">Syndie</a>\n"
+"pages."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:901
+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:916
+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:930
+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:946
+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 <a "
+"href=\"#app.i2pmail\">I2Pmail's</a> \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:963
+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 <a href=\"#app.streaming\">streaming lib</a> connection to query them "
+"for \n"
+"blocks."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:972
+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:980
+msgid ""
+"I2PSnark developed: jrandom, et al, ported from <a\n"
+"href=\"http://www.klomp.org/mark/\">mjw</a>'s <a\n"
+"href=\"http://www.klomp.org/snark/\">Snark</a> client"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:986
+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:995
+#, python-format
+msgid ""
+"Robert is a Bittorrent client written in Python.\n"
+"It is hosted on <a "
+"href=\"http://%(bob)s/Robert.html\">http://%(bob)s/Robert.html</a> <!-- "
+"TODO: expand -->"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:1003
+#, python-format
+msgid ""
+"PyBit is a Bittorrent client written in Python.\n"
+"It is hosted on <a href=\"%(pybit)s\">%(pybit)s</a> <!-- TODO: expand -->"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:1011
+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:1021
+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:1029
+#, 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"
+"<a href=\"http://%(postman)s/\">%(postman)s</a>."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:1051
+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. <br>\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:1061
+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:93
+msgid "Priority"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:45
+msgid "Index of Attacks"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:47
+#: i2p2www/pages/site/docs/how/threat-model.html:206
+msgid "Brute force attacks"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:48
+#: i2p2www/pages/site/docs/how/threat-model.html:250
+msgid "Timing attacks"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:49
+#: i2p2www/pages/site/docs/how/threat-model.html:287
+msgid "Intersection attacks"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:50
+#: i2p2www/pages/site/docs/how/threat-model.html:367
+msgid "Denial of service attacks"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:51
+#: i2p2www/pages/site/docs/how/threat-model.html:466
+msgid "Tagging attacks"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:52
+#: i2p2www/pages/site/docs/how/threat-model.html:484
+msgid "Partitioning attacks"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:53
+#: i2p2www/pages/site/docs/how/threat-model.html:524
+msgid "Predecessor attacks"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:54
+#: i2p2www/pages/site/docs/how/threat-model.html:569
+msgid "Harvesting attacks"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:55
+#: i2p2www/pages/site/docs/how/threat-model.html:616
+msgid "Identification Through Traffic Analysis"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:56
+#: i2p2www/pages/site/docs/how/threat-model.html:676
+msgid "Sybil attacks"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:57
+#: i2p2www/pages/site/docs/how/threat-model.html:725
+msgid "Buddy Exhaustion attacks"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:58
+#: i2p2www/pages/site/docs/how/threat-model.html:750
+msgid "Cryptographic attacks"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:59
+msgid "Floodfill attacks"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:60
+#: i2p2www/pages/site/docs/how/threat-model.html:811
+msgid "Other Network Database attacks"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:61
+msgid "Attacks on centralized resources"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:62
+#: i2p2www/pages/site/docs/how/threat-model.html:877
+msgid "Development attacks"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:63
+msgid "Implementation attacks"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:64
+#: i2p2www/pages/site/docs/how/threat-model.html:961
+msgid "Other Defenses"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:69
+msgid "What do we mean by \"anonymous\"?"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:71
+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:82
+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:89
+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:95
+msgid "Network Topology Summary"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:96
+#, python-format
+msgid ""
+"I2P builds off the ideas of many <a href=\"%(comparisons)s\">other</a> \n"
+"<a href=\"%(links)s\">systems</a>, but a few key points should be kept in"
+" mind when \n"
+"reviewing related literature:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:102
+msgid ""
+"<b>I2P is a free route mixnet</b> - 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:108
+msgid ""
+"<b>I2P has no official entry and exit points</b> - 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:113
+msgid ""
+"<b>I2P is fully distributed</b> - 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:123
+#, python-format
+msgid ""
+"We have documented plans to implement <a "
+"href=\"%(todo)s#stop\">nontrivial delays</a>\n"
+"and <a href=\"%(todo)s#batching\">batching strategies</a> \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:134
+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:141
+msgid "The Threat Model"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:142
+msgid ""
+"I2P design started in 2003, not long after the advent of\n"
+"<a href=\"http://www.onion-router.net\">[Onion Routing]</a>,\n"
+"<a href=\"http://freenetproject.org/\">[Freenet]</a>, and\n"
+"<a href=\"https://www.torproject.org/\">[Tor]</a>.\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:152
+msgid ""
+"Taking from the attacks and analysis put forth in the \n"
+"<a href=\"http://freehaven.net/anonbib/topic.html\">anonymity "
+"literature</a> (largely \n"
+"<a href=\"http://citeseer.ist.psu.edu/454354.html\">Traffic Analysis: "
+"Protocols, Attacks, Design \n"
+"Issues and Open Problems</a>), 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:161
+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:167
+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:177
+#, python-format
+msgid ""
+"The\n"
+"<a href=\"%(comparisons)s\">network comparisons</a> and\n"
+"<a href=\"%(garlicrouting)s\">\"garlic\" terminology</a> pages may also "
+"be helpful\n"
+"to review."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:210
+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:222
+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"
+"<a "
+"href=\"http://citeseer.ist.psu.edu/freedman02tarzan.html\">Tarzan</a>'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:239
+#, 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"
+"<a href=\"%(peerselection)s\">peer selection page</a>."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:254
+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:264
+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:274
+#, 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 <a href=\"%(todo)s#stop\">nontrivial "
+"delays</a> or \n"
+"<a href=\"%(todo)s#batching\">batching strategies</a>), include protocol "
+"scrubbing, or\n"
+"other advanced tunnel routing <a "
+"href=\"%(todo)s#batching\">techniques</a>,\n"
+"but these are unimplemented in I2P."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:283
+#, python-format
+msgid ""
+"References: <a href=\"%(pdf)s\">Low-Resource Routing Attacks Against "
+"Anonymous Systems</a>"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:291
+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:301
+#, 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 <a href=\"%(url)s\">similar disclaimer</a>."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:309
+msgid "Partial defenses implemented in I2P:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:313
+#, python-format
+msgid "<a href=\"%(tunnelimpl)s#ordering\">strict ordering</a> of peers"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:316
+#, python-format
+msgid ""
+"<a href=\"%(peerselection)s\">peer profiling and selection</a> from a "
+"small group that changes slowly"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:319
+msgid "Limits on the number of tunnels routed through a single peer"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:322
+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:325
+msgid ""
+"For eepsites or other hosted services, we support\n"
+"simultaneous hosting on multiple routers, or\n"
+"<a href=\"#intersection\">multihoming</a>"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:332
+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:337
+msgid "We do not use low-bandwidth \"guard nodes\""
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:340
+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:343
+msgid "Tunnels are not long-lived; new tunnels are built every 10 minutes."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:346
+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:353
+#, python-format
+msgid ""
+"In the future, it could\n"
+"for peers who can afford significant delays (per <a "
+"href=\"%(todo)s#stop\">nontrivial\n"
+"delays</a> and <a href=\"%(todo)s#batching\">batching strategies</a>).  "
+"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.</p>"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:362
+#, python-format
+msgid "Reference: <a href=\"%(oce)s\">One Cell Enough</a>"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:369
+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:375
+msgid ""
+"<b>Greedy user attack:</b> 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:381
+#, 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"
+"<a href=\"%(comparisons)s\">other networks</a>,\n"
+"over 95&#37; of I2P users relay traffic for others."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:387
+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:392
+msgid ""
+"Maintain a strong community with blogs, forums, IRC, and other means of "
+"communication."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:399
+#, python-format
+msgid ""
+"<b>Starvation attack:</b> 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 <a "
+"href=\"%(peerselection)s\">profiles</a> 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:419
+#, python-format
+msgid ""
+"<b>Flooding attack:</b> 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 <a "
+"href=\"%(todo)s#batching\">advanced tunnel\n"
+"operation</a> is implemented)."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:438
+msgid ""
+"<b>CPU load attack:</b> 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:451
+#, python-format
+msgid ""
+"<b>Floodfill DOS attack:</b> 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"
+"<a href=\"%(peerselection)s\">peer profiling</a> are implemented,\n"
+"however there is much more to do.\n"
+"For more information see the\n"
+"<a href=\"%(netdb)s#threat\">network database page</a>."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:470
+#, 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 <a href=\"%(todo)s#tunnelId\">unique hop ids</a> 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:488
+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:504
+#, 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 <a href=\"#harvesting\">harvesting</a>"
+" 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 <a href=\"%(todo)s#stop\">nontrivial "
+"delays</a> and \n"
+"<a href=\"%(todo)s#batching\">batching strategies</a>, 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:520
+#, python-format
+msgid ""
+"Also discussed on the <a href=\"%(netdb)s#threat\">network database "
+"page</a> (bootstrap attack)."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:528
+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:538
+#, 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 <a href=\"%(peerselection)s\">peer selection</a> algorithm which "
+"breaks them\n"
+"into tiers.  Second, with <a href=\"%(tunnelimpl)s#ordering\">strict "
+"ordering</a> 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 <a href=\"%(tunnelimpl)s#length\">permuted "
+"tunnel length</a>\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"
+"<a href=\"%(todo)s#fullRestrictedRoutes\">restricted routes</a> "
+"(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:555
+#, python-format
+msgid ""
+"The current <a href=\"%(tunnelcreation)s\">tunnel build method</a>\n"
+"was specifically designed to combat the predecessor attack.\n"
+"See also <a href=\"#intersection\">the intersection attack</a>."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:561
+#, python-format
+msgid ""
+"References: <a href=\"%(pdf2008)s\">%(pdf2008)s</a>\n"
+"which is an update to the 2004 predecessor attack paper\n"
+"<a href=\"%(pdf2004)s\">%(pdf2004)s</a>."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:573
+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:580
+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:587
+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:590
+msgid "Floodfill routers implement query limits as DOS protection"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:593
+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:599
+#, python-format
+msgid ""
+"In future implementations,\n"
+"<a href=\"%(todo)s#nat\">basic</a> and \n"
+"<a href=\"%(todo)s#fullRestrictedRoutes\">comprehensive</a> 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:608
+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:620
+#, 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 <a href=\"#harvesting\">above</a>, 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"
+"<a href=\"%(transport)s\">transport layer and protocols</a>\n"
+"make it somewhat difficult to identify I2P traffic:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:630
+msgid "Random port selection"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:633
+msgid "Point-to-Point Encryption of all traffic"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:636
+msgid ""
+"DH key exchange with no protocol bytes or other unencrypted constant "
+"fields"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:639
+#, python-format
+msgid ""
+"Simultaneous use of both\n"
+"<a href=\"%(ntcp)s\">TCP</a> and\n"
+"<a href=\"%(ssu)s\">UDP</a> 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:647
+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:651
+msgid ""
+"Padding at the transport layer to random lengths, especially during the "
+"connection handshake"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:654
+msgid ""
+"Study of packet size distribution signatures, and additional padding as "
+"necessary"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:657
+msgid ""
+"Development of additional transport methods that mimic SSL or other "
+"common protocols"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:660
+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:663
+msgid ""
+"Review of methods implemented by various state-level firewalls to block "
+"Tor"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:666
+msgid "Working directly with DPI and obfuscation experts"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:671
+#, python-format
+msgid ""
+"Reference: <a href=\"%(pdf)s\">Breaking and Improving Protocol "
+"Obfuscation</a>"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:680
+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&#37; 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' - <a "
+"href=\"http://www.pdos.lcs.mit.edu/tarzan/\">Tarzan</a>\n"
+"(among others) uses the fact that IP addresses are limited, while \n"
+"IIP used \n"
+"<a href=\"http://www.hashcash.org/\">HashCash</a> 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:698
+msgid "Requiring HashCash Certificates in various places has two major problems:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:702
+msgid "Maintaining backward compatibility"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:705
+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:712
+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:719
+#, python-format
+msgid ""
+"See the <a href=\"%(netdb)s#threat\">network database page</a>\n"
+"for more Sybil discussion."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:729
+#, python-format
+msgid ""
+"(Reference: <a href=\"%(pdf)s\">In Search of an Anonymous and Secure "
+"Lookup</a> Section 5.2)"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:733
+#, 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 <a href=\"#sybil\">Sybil attack</a>.\n"
+"This is somewhat mitigated by our\n"
+"<a href=\"%(peerselection)s\">peer profiling</a> methods used to monitor "
+"the performance\n"
+"of peers.\n"
+"However, this is a powerful attack as the number of routers approaches\n"
+"<i>f</i> = 0.2, or 20&#37; 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:754
+#, 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"
+"<a href=\"%(cryptography)s\">on the low-level cryptography page</a>. \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 <a href=\"https://torproject.org/\">other anonymity "
+"networks</a>.\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:773
+#, 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"
+"<a href=\"%(cryptography)s\">major undertaking</a>, just as it will be "
+"for \n"
+"<a href=\"https://torproject.org/\">others</a>.\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:782
+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:792
+msgid "Floodfill Anonymity attacks"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:796
+#, python-format
+msgid ""
+"In addition to the floodfill DOS attacks described\n"
+"<a href=\"#ffdos\">above</a>, 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 <a href=\"%(netdb)s#threat\">network database page</a>.\n"
+"The specific mechanisms by which routers communicate with floodfills have"
+" been\n"
+"<a href=\"%(netdb)s#delivery\">carefully designed</a>.\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:812
+#, 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"
+"<a href=\"%(netdb)s#threat\">network database page</a>."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:822
+msgid "Central Resource Attacks"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:826
+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:836
+#, python-format
+msgid ""
+"The <a href=\"%(site)s\">website</a> is mirrored and uses DNS round-robin"
+" for external public access."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:839
+#, python-format
+msgid ""
+"Routers now support <a href=\"%(faq)s#reseed\">multiple external reseed "
+"locations</a>,\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:844
+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:848
+msgid "Routers now support multiple default trusted update signers."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:851
+msgid ""
+"Routers now better handle <a href=\"#ffdos\">multiple unreliable "
+"floodfill peers</a>.\n"
+"Malicious floodfills <a href=\"#ffdos\">needs</a> <a "
+"href=\"#floodfill\">more</a> study."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:855
+#, python-format
+msgid ""
+"The code is now stored in a <a href=\"%(monotone)s\">distributed source "
+"control system</a>."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:858
+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:862
+#, python-format
+msgid ""
+"<a href=\"%(naming)s\">Naming system services</a>, 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"
+"<a href=\"%(naming)s\">the naming page</a> for details."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:869
+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:881
+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:890
+msgid "However, two techniques help defend against these attacks:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:894
+#, 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 <a href=\"%(monotone)s\">distributed source control "
+"system</a>\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:902
+#, 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 <a href=\"%(monotone)s\">distributed source control system</a>,\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:913
+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:918
+msgid "Implementation attacks (bugs)"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:922
+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"
+"<a href=\"http://www.haystacknetwork.com/\">security through "
+"obscurity</a>."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:933
+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:943
+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:949
+#, 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"
+"<a href=\"https://torproject.org/\">other anonymity networks</a>\n"
+"may have received. We continue to recruit people to\n"
+"<a href=\"%(volunteer)s\">get involved</a> and help."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:962
+msgid "Blocklists"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:963
+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:969
+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:977
+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:986
+msgid ""
+"If a blocklist is hosted at a central location with automatic updates\n"
+"the network is vulnerable to a\n"
+"<a href=\"#central\">central resource attack</a>.\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:994
+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
+msgid "Tunnel Routing"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tunnel-routing.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 <a href=\"%(intro)s\">introduction</a>, 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 "Väljuv otspunkt"
+
+#: i2p2www/pages/site/docs/how/tunnel-routing.html:30
+#: i2p2www/pages/site/docs/tunnels/implementation.html:140
+msgid "Inbound Gateway"
+msgstr "Sisenev lüüs"
+
+#: 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 ""
+"<b>Tunnel gateway</b> - the first router in a tunnel.  For inbound "
+"tunnels,\n"
+"this is the one mentioned in the LeaseSet published in the\n"
+"<a href=\"%(netdb)s\">network database</a>.  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 ""
+"<b>Tunnel endpoint</b> - the last router in a tunnel.  (e.g. both C and F"
+" above)"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tunnel-routing.html:45
+msgid ""
+"<b>Tunnel participant</b> - 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 ""
+"<b>n-Hop tunnel</b> - a tunnel with a specific number of inter-router "
+"jumps, e.g.:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tunnel-routing.html:51
+msgid "<b>0-hop tunnel</b> - a tunnel where the gateway is also the endpoint"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tunnel-routing.html:52
+msgid ""
+"<b>1-hop tunnel</b> - a tunnel where the gateway talks directly to the "
+"endpoint"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tunnel-routing.html:53
+msgid ""
+"<b>2-(or more)-hop tunnel</b> - 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 ""
+"<b>Tunnel ID</b> - A <a href=\"%(commonstructures)s#type_TunnelId\">4 "
+"byte integer</a>\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"
+"<a href=\"%(tunnelcreation)s\">Tunnel Build Message</a>\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 ""
+"<b>tunnel encryption key</b> - an <a "
+"href=\"%(commonstructures)s#type_SessionKey\">AES private key</a> 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 ""
+"<b>tunnel IV key</b> - an <a "
+"href=\"%(commonstructures)s#type_SessionKey\">AES private key</a> 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 ""
+"<b>reply key</b> - an <a "
+"href=\"%(commonstructures)s#type_SessionKey\">AES public key</a> 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 ""
+"<b>reply IV</b> - the IV for encrypting the reply to the tunnel build "
+"request"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tunnel-routing.html:90
+msgid "<b>tunnel id</b> - 4 byte integer (inbound gateways only)"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tunnel-routing.html:91
+msgid ""
+"<b>next hop</b> - 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 "<b>next tunnel id</b> - 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 "<b>tunnel id</b> - 4 byte integer"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tunnel-routing.html:111
+msgid "<b>next hop</b> - 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 ""
+"<b>tunnel encryption key</b> - an <a "
+"href=\"%(commonstructures)s#type_SessionKey\">AES private key</a> for "
+"encrypting\n"
+"messages and instructions to the the endpoint (itself)"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tunnel-routing.html:121
+#, python-format
+msgid ""
+"<b>tunnel IV key</b> - an <a "
+"href=\"%(commonstructures)s#type_SessionKey\">AES private key</a> for "
+"double-encrypting\n"
+"the IV to the endpoint (itself)"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tunnel-routing.html:125
+#, python-format
+msgid ""
+"<b>reply key</b> - an <a "
+"href=\"%(commonstructures)s#type_SessionKey\">AES public key</a> for "
+"encrypting\n"
+"the reply to the tunnel build request (outbound endpoints only)"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tunnel-routing.html:129
+msgid ""
+"<b>reply IV</b> - 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 "<b>tunnel id</b> - 4 byte integer (outbound endpoints only)"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tunnel-routing.html:131
+msgid ""
+"<b>reply router</b> - 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 ""
+"<b>reply tunnel id</b> - 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"
+"<a href=\"%(tunnelcreation)s\">tunnel creation specification</a>."
+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"
+"<a href=\"%(tunnelimpl)s#tunnel.pooling\">tunnel specification</a>.\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"
+"<a href=\"%(i2cp)s#options\">I2CP options</a>.\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 <a href=\"%(threatmodel)s\">threat model</a>)."
+" 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 <a href=\"%(url)s\">some attacks</a>,\n"
+"3 or more hops are recommended for the highest level of protection.\n"
+"<a href=\"%(url)s\">Recent studies</a>\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"
+"<a href=\"%(i2cp)s#options\">I2CP options</a>.\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"
+"<a href=\"%(peerselection)s#capacity\">capacity rating in the peer "
+"profile</a>."
+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 <a href=\"%(garlicrouting)s\">garlic "
+"routing</a>\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"
+"<a href=\"%(tunnelcreation)s\">tunnel creation specification</a>."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tunnel-routing.html:245
+#, python-format
+msgid ""
+"Multi-layer encryption is handled by <a href=\"%(garlicrouting)s\">garlic"
+" encryption</a>\n"
+"of tunnel messages.\n"
+"Details are in the\n"
+"<a href=\"%(tunnelimpl)s\">tunnel specification</a>.\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 "February 2016"
+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.\n"
+"With I2CP, a client application tells the\n"
+"router who they are (their \"destination\"), what anonymity, reliability,"
+" and \n"
+"latency tradeoffs to make, and where to send messages.  In turn the "
+"router uses\n"
+"I2CP to tell the client when any messages have arrived, and to request "
+"authorization\n"
+"for some tunnels to be used."
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2cp.html:18
+#, python-format
+msgid ""
+"The protocol itself is implemented in Java, to provide the\n"
+"<a href=\"%(url)s\">Client SDK</a>.\n"
+"This SDK is exposed in the i2p.jar package, which implements the client-"
+"side of I2CP.\n"
+"Clients should never need to access the router.jar package, which "
+"contains the\n"
+"router itself and the router-side of I2CP.\n"
+"There is also a <a href=\"%(libi2cp)s\">C library implementation</a>.\n"
+"A non-Java client would also have to implement the\n"
+"<a href=\"%(streaming)s\">streaming library</a> for TCP-style connections."
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2cp.html:31
+#, python-format
+msgid ""
+"Applications can take advantage of the base I2CP plus the \n"
+"<a href=\"%(streaming)s\">streaming</a> and <a "
+"href=\"%(datagrams)s\">datagram</a> libraries\n"
+"by using the <a href=\"%(sam)s\">Simple Anonymous Messaging</a> or <a "
+"href=\"%(bob)s\">BOB</a> 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:43
+#, 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 <a href=\"%(elgamalaes)s\">ElGamal/AES end-to-end "
+"encryption</a>\n"
+"which is implemented in the router.\n"
+"The only cryptography that client libraries must still implement is\n"
+"<a href=\"%(cryptography)s#DSA\">DSA public/private key signing</a>\n"
+"for <a href=\"%(i2cp)s#msg_CreateLeaseSet\">LeaseSets</a> and\n"
+"<a href=\"%(i2cp)s#struct_SessionConfig\">Session Configurations</a>, and"
+" management of those keys."
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2cp.html:56
+msgid ""
+"In a standard I2P installation, port 7654 is used by external java "
+"clients to communicate\n"
+"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 "
+"<tt>i2cp.tcp.bindAllInterfaces=true</tt> 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:65
+#, python-format
+msgid ""
+"The router also supports external connections over SSL.\n"
+"While SSL is not the default, it is strongly recommended for any traffic "
+"that may\n"
+"be exposed to the open Internet. The authorization user/password (if "
+"any), the\n"
+"<a href=\"%(commonstructures)s#type_PrivateKey\">Private Key</a> and\n"
+"<a href=\"%(commonstructures)s#type_SigningPrivateKey\">Signing Private "
+"Key</a> for the\n"
+"<a href=\"%(commonstructures)s#struct_Destination\">Destination</a>\n"
+"are all transmitted in-the-clear unless SSL is enabled."
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2cp.html:75
+msgid "I2CP Protocol Specification"
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2cp.html:76
+#, python-format
+msgid "Now on the <a href=\"%(i2cp)s\">I2CP Specification page</a>."
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2cp.html:81
+msgid "I2CP Initialization"
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2cp.html:82
+#, python-format
+msgid ""
+"When a client connects to the router, it first sends a single protocol "
+"version byte (0x2A).\n"
+"Then it sends a <a href=\"%(i2cp)s#msg_GetDate\">GetDate Message</a> and "
+"waits for the <a href=\"%(i2cp)s#msg_SetDate\">SetDate Message</a> "
+"response.\n"
+"Next, it sends a <a href=\"%(i2cp)s#msg_CreateSession\">CreateSession "
+"Message</a> containing the session configuration.\n"
+"It next awaits a <a href=\"%(i2cp)s#msg_RequestLeaseSet\">RequestLeaseSet"
+" Message</a> from the router, indicating that inbound tunnels\n"
+"have been built, and responds with a CreateLeaseSetMessage containing the"
+" signed LeaseSet.\n"
+"The client may now initiate or receive connections from other I2P "
+"destinations."
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2cp.html:91
+msgid "I2CP Options"
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2cp.html:92
+#: i2p2www/pages/site/docs/protocol/i2cp.html:99
+msgid "Router-side Options"
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2cp.html:93
+#, python-format
+msgid ""
+"The following options are traditionally passed to the router via\n"
+"a <a href=\"%(i2cp)s#struct_SessionConfig\">SessionConfig</a> contained "
+"in a <a href=\"%(i2cp)s#msg_CreateSession\">CreateSession Message</a> or "
+"a <a href=\"%(i2cp)s#msg_ReconfigureSession\">ReconfigureSession "
+"Message</a>."
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2cp.html:104
+#: i2p2www/pages/site/docs/protocol/i2cp.html:479
+msgid "As Of Release"
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2cp.html:105
+#: i2p2www/pages/site/docs/protocol/i2cp.html:480
+msgid "Recommended Arguments"
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2cp.html:106
+#: i2p2www/pages/site/docs/protocol/i2cp.html:481
+msgid "Allowable Range"
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2cp.html:117
+msgid ""
+"The timeout (ms) for all sent messages. Unused.\n"
+"See the protocol specification for per-message settings."
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2cp.html:129
+msgid ""
+"Minimum number of ElGamal/AES Session Tags before we send more.\n"
+"Recommended: approximately tagsToSend * 2/3"
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2cp.html:141
+msgid ""
+"Number of ElGamal/AES Session Tags to send at a time.\n"
+"For clients with relatively low bandwidth per-client-pair (IRC, some UDP "
+"apps), this may be set lower."
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2cp.html:153
+msgid ""
+"Comma-separated list of Base 64 Hashes of peers to build tunnels through;"
+" for debugging only"
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2cp.html:162
+msgid "Should generally be set to true for clients and false for servers"
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2cp.html:171
+#: i2p2www/pages/site/docs/protocol/i2cp.html:519
+msgid ""
+"If true, the router just sends the MessagePayload instead\n"
+"of sending a MessageStatus and awaiting a ReceiveMessageBegin."
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2cp.html:183
+msgid ""
+"Guaranteed is disabled;\n"
+"None implemented in 0.8.1; the streaming lib default is None as of 0.8.1,"
+" the client side default is None as of 0.9.4"
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2cp.html:195
+msgid ""
+"For authorization, if required by the router.\n"
+"If the client is running in the same JVM as a router, this option is not "
+"required.\n"
+"Warning - username and password are sent in the clear to the router, "
+"unless using SSL (i2cp.SSL=true).\n"
+"Authorization is only recommended when using SSL."
+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:232
+#: i2p2www/pages/site/docs/protocol/i2cp.html:241
+#: i2p2www/pages/site/docs/protocol/i2cp.html:250
+#: i2p2www/pages/site/docs/protocol/i2cp.html:262
+#: i2p2www/pages/site/docs/protocol/i2cp.html:274
+#: i2p2www/pages/site/docs/protocol/i2cp.html:283
+#: i2p2www/pages/site/docs/protocol/i2cp.html:292
+#: i2p2www/pages/site/docs/protocol/i2cp.html:307
+#: i2p2www/pages/site/docs/protocol/i2cp.html:343
+#: i2p2www/pages/site/docs/protocol/i2cp.html:355
+#: i2p2www/pages/site/docs/protocol/i2cp.html:368
+#, python-format
+msgid "number from %(from)s to %(to)s"
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2cp.html:233
+#: i2p2www/pages/site/docs/protocol/i2cp.html:242
+#: i2p2www/pages/site/docs/protocol/i2cp.html:369
+msgid "No limit"
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2cp.html:235
+msgid "Number of redundant fail-over for tunnels in"
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2cp.html:244
+msgid "Number of redundant fail-over for tunnels out"
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2cp.html:251
+#: i2p2www/pages/site/docs/protocol/i2cp.html:263
+#: i2p2www/pages/site/docs/protocol/i2cp.html:275
+#: i2p2www/pages/site/docs/protocol/i2cp.html:284
+#: i2p2www/pages/site/docs/protocol/i2cp.html:293
+#: i2p2www/pages/site/docs/protocol/i2cp.html:308
+#: i2p2www/pages/site/docs/protocol/i2cp.html:344
+#: i2p2www/pages/site/docs/protocol/i2cp.html:356
+#: i2p2www/pages/site/docs/protocol/i2cp.html:608
+#, python-format
+msgid "%(from)s to %(to)s"
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2cp.html:253
+#: i2p2www/pages/site/docs/protocol/i2cp.html:265
+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:277
+msgid "Length of tunnels in"
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2cp.html:286
+msgid "Length of tunnels out"
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2cp.html:295
+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:310
+msgid ""
+"Random amount to add or subtract to the length of tunnels out.\n"
+"A positive number x means add a random amount from 0 to x inclusive.\n"
+"A negative number -x means add a random amount from -x to x inclusive.\n"
+"The router will limit the total length of the tunnel to 0 to 7 inclusive."
+"\n"
+"The default variance was 1 prior to release 0.7.6."
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2cp.html:325
+msgid ""
+"Name of tunnel - generally used in routerconsole, which will\n"
+"use the first few characters of the Base64 hash of the destination by "
+"default."
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2cp.html:337
+msgid "Name of tunnel - generally ignored unless inbound.nickname is unset."
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2cp.html:346
+msgid ""
+"Priority adjustment for outbound messages.\n"
+"Higher is higher priority."
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2cp.html:358
+msgid ""
+"Number of tunnels in.\n"
+"Limit was increased from 6 to 16 in release 0.9; however, numbers higher "
+"than 6 are\n"
+"incompatible with older releases."
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2cp.html:371
+msgid "Number of tunnels out"
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2cp.html:380
+msgid "Used for consistent peer ordering across restarts."
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2cp.html:399
+msgid ""
+"Any other options prefixed with \"inbound.\" are stored\n"
+"in the \"unknown options\" properties of the inbound tunnel pool's "
+"settings."
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2cp.html:411
+msgid ""
+"Any other options prefixed with \"outbound.\" are stored\n"
+"in the \"unknown options\" properties of the outbound tunnel pool's "
+"settings."
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2cp.html:423
+msgid ""
+"Set to false to disable ever bundling a reply LeaseSet.\n"
+"For clients that do not publish their LeaseSet, this option must be true\n"
+"for any reply to be possible. \"true\" is also recommended for multihomed"
+" servers\n"
+"with long connection times."
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2cp.html:430
+msgid ""
+"Setting to \"false\" may save significant outbound bandwidth, especially "
+"if\n"
+"the client is configured with a large number of inbound tunnels (Leases)."
+"\n"
+"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:438
+msgid "Unidirectional communication, no reply required"
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2cp.html:439
+msgid "LeaseSet is published and higher reply latency is acceptable"
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2cp.html:440
+msgid ""
+"LeaseSet is published, client is a \"server\", all connections are "
+"inbound\n"
+"so the connecting far-end destination obviously has the leaseset already."
+"\n"
+"Connections are either short, or it is acceptable for latency on a long-"
+"lived\n"
+"connection to temporarily increase while the other end re-fetches the "
+"LeaseSet\n"
+"after expiration.\n"
+"HTTP servers may fit these requirements."
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2cp.html:453
+msgid ""
+"Note: Large quantity, length, or variance settings may cause significant "
+"performance or reliability problems."
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2cp.html:457
+#, python-format
+msgid ""
+"Note: As of release 0.7.7, option names and values must use UTF-8 "
+"encoding.\n"
+"This is primarily useful for nicknames.\n"
+"Prior to that release, options with multi-byte characters were corrupted."
+"\n"
+"Since options are encoded in a <a "
+"href=\"%(commonstructures)s#type_Mapping\">Mapping</a>,\n"
+"all option names and values are limited to 255 bytes (not characters) "
+"maximum."
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2cp.html:465
+#: i2p2www/pages/site/docs/protocol/i2cp.html:474
+msgid "Client-side Options"
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2cp.html:466
+msgid ""
+"The following options are interpreted on the client side,\n"
+"and will be interpreted if passed to the I2PSession via the "
+"I2PClient.createSession() call.\n"
+"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:490
+#: i2p2www/pages/site/docs/protocol/i2cp.html:590
+#, python-format
+msgid "%(num)s minimum"
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2cp.html:492
+msgid "(ms) Idle time required (default 30 minutes)"
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2cp.html:501
+msgid "Close I2P session when idle"
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2cp.html:510
+msgid "Encrypt the lease"
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2cp.html:531
+msgid "Gzip outbound data"
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2cp.html:540
+msgid "For encrypted leasesets. Base 64 SessionKey (44 characters)"
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2cp.html:549
+msgid ""
+"Base 64 private key for encryption.\n"
+"Optionally preceded by the key type and ':'.\n"
+"Only \"ELGAMAL_2048:\" is supported, which is the default.\n"
+"I2CP will generate the public key from the private key.\n"
+"Use for persistent leaseset keys across restarts."
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2cp.html:564
+msgid ""
+"Base 64 private key for signatures.\n"
+"Optionally preceded by the key type and ':'.\n"
+"DSA_SHA1 is the default.\n"
+"Key type must match the signature type in the destination.\n"
+"I2CP will generate the public key from the private key.\n"
+"Use for persistent leaseset keys across restarts."
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2cp.html:580
+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:592
+msgid "(ms) Idle time required (default 20 minutes, minimum 5 minutes)"
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2cp.html:601
+msgid "Reduce tunnel quantity when idle"
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2cp.html:610
+msgid "Tunnel quantity when reduced (applies to both inbound and outbound)"
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2cp.html:619
+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:631
+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:643
+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:650
+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:656
+msgid "I2CP Payload Data Format and Multiplexing"
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2cp.html:657
+#, python-format
+msgid ""
+"The end-to-end messages handled by I2CP (i.e. the data sent by the client"
+" in a\n"
+"<a href=\"%(i2cp)s#msg_SendMessage\">SendMessageMessage</a>\n"
+"and received by the client in a\n"
+"<a href=\"%(i2cp)s#msg_MessagePayload\">MessagePayloadMessage</a>)\n"
+"are gzipped with a standard 10-byte gzip\n"
+"header beginning with 0x1F 0x8B 0x08 as\n"
+"specified by <a href=\"http://www.ietf.org/rfc/rfc1952.txt\">RFC "
+"1952</a>.\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:671
+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:677
+#: i2p2www/pages/site/docs/protocol/i2np.html:32
+msgid "Bytes"
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2cp.html:678
+msgid "Content"
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2cp.html:683
+msgid "Gzip header"
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2cp.html:688
+msgid "Gzip flags"
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2cp.html:693
+msgid "I2P Source port (Gzip mtime)"
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2cp.html:698
+msgid "I2P Destination port (Gzip mtime)"
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2cp.html:703
+msgid "Gzip xflags"
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2cp.html:708
+msgid "I2P Protocol (6 = Streaming, 17 = Datagram, 18 = Raw Datagrams) (Gzip OS)"
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2cp.html:717
+msgid ""
+"Data integrity is verified with the standard gzip CRC-32 as\n"
+"specified by <a href=\"http://www.ietf.org/rfc/rfc1952.txt\">RFC 1952</a>."
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2cp.html:725
+msgid ""
+"The current authorization mechanism could be modified to use hashed "
+"passwords."
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2cp.html:729
+msgid ""
+"The Signing Private Keys is included in the Create Lease Set message,\n"
+"it is not required. Revocation is unimplemented.\n"
+"It should be replaced with random data or removed."
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2cp.html:735
+#, python-format
+msgid ""
+"Some improvements may be able to use messages previously defined but not "
+"implemented.\n"
+"For reference, here is the\n"
+"<a href=\"%(pdf1)s\">I2CP Protocol Specification Version 0.9</a>\n"
+"(PDF) dated August 28, 2003.\n"
+"That document also references the\n"
+"<a href=\"%(pdf2)s\">Common Data Structures Specification Version 0.9</a>."
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2np.html:2
+msgid "I2P Network Protocol"
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2np.html:3
+msgid "June 2013"
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2np.html:6
+msgid ""
+"The I2P Network Protocol (I2NP),\n"
+"which is sandwiched between I2CP and the various I2P transport protocols,"
+" manages the\n"
+"routing and mixing of messages between routers, as well as the selection "
+"of what\n"
+"transports to use when communicating with a peer for which there are "
+"multiple\n"
+"common transports supported."
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2np.html:14
+msgid "I2NP Definition"
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2np.html:15
+msgid ""
+"I2NP (I2P Network Protocol) messages can be used for one-hop, router-to-"
+"router, point-to-point messages.\n"
+"By encrypting and wrapping messages in other messages, they can be sent "
+"in a secure way\n"
+"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:22
+#, python-format
+msgid ""
+"The priorities listed below may not be current and are subject to change."
+"\n"
+"See the <a href=\"%(outnetmessage)s\">OutNetMessage Javadocs</a>\n"
+"for the current priority settings.\n"
+"Priority queueing implementation may vary."
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2np.html:29
+msgid "Message Format"
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2np.html:32
+msgid "Field"
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2np.html:33
+msgid "Unique ID"
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2np.html:34
+msgid "Expiration"
+msgstr "Aegumine"
+
+#: i2p2www/pages/site/docs/protocol/i2np.html:35
+#: i2p2www/pages/site/docs/protocol/i2np.html:92
+msgid "Payload Length"
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2np.html:36
+msgid "Checksum"
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2np.html:37
+msgid "Payload"
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2np.html:40
+#, python-format
+msgid ""
+"While the maximum payload size is nominally 64KB, the size is further "
+"constrained by the\n"
+"method of fragmenting I2NP messages into multiple 1KB tunnel messages as "
+"described on\n"
+"<a href=\"%(tunnelimpl)s\">the tunnel implementation page</a>.\n"
+"The maximum number of fragments is 64, and the message may not be "
+"perfectly aligned,\n"
+"So the message must nominally fit in 63 fragments."
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2np.html:48
+msgid ""
+"The maximum size of an initial fragment is 956 bytes (assuming TUNNEL "
+"delivery mode);\n"
+"the maximum size of 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:54
+msgid ""
+"In addition, the transports may have additional restrictions.\n"
+"NTCP currently limits to 16KB - 6 = 16378 bytes but this will be "
+"increased in a future release.\n"
+"The SSU limit is approximately 32 KB."
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2np.html:60
+msgid ""
+"Note that these are not the limits for datagrams that the client sees, as"
+" the\n"
+"router may bundle a reply leaseset and/or session tags together with the "
+"client message\n"
+"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:68
+msgid "Message Types"
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2np.html:69
+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:80
+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:90
+msgid "Message"
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2np.html:91
+msgid "Type"
+msgstr "Tüüp"
+
+#: i2p2www/pages/site/docs/protocol/i2np.html:94
+msgid "Comments"
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2np.html:102
+msgid "May vary"
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2np.html:108
+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:117
+msgid "Varies"
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2np.html:119
+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:133
+msgid "Priority may vary on a per-destination basis"
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2np.html:143
+msgid ""
+"Used for message replies, and for testing tunnels - generally wrapped in "
+"a GarlicMessage"
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2np.html:151
+msgid ""
+"Generally wrapped in a DataMessage -\n"
+"but when unwrapped, given a priority of 100 by the forwarding router"
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2np.html:178
+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:198
+msgid "Shorter TunnelBuildMessage as of 0.7.12"
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2np.html:206
+msgid "Shorter TunnelBuildReplyMessage as of 0.7.12"
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2np.html:209
+#, python-format
+msgid "Others listed in <a href=\"%(pdf)s\">2003 Spec</a>"
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2np.html:215
+msgid "Obsolete, Unused"
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2np.html:219
+msgid "Full Protocol Specification"
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2np.html:220
+#, python-format
+msgid ""
+"<a href=\"%(i2npspec)s\">On the I2NP Specification page</a>.\n"
+"See also the\n"
+"<a href=\"%(commonstructures)s\">Common Data Structure Specification "
+"page</a>."
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2np.html:227
+msgid ""
+"It isn't clear whether the current priority scheme is generally "
+"effective,\n"
+"and whether the priorities for various messages should be adjusted "
+"further.\n"
+"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 <a href=\"%(docs)s\">Index to Technical Documentation</a>."
+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 ""
+"<b>I2P Transport Layer:</b> 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 "<b>I2P Tunnel Layer:</b> provide full encrypted tunnel connections."
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/index.html:42
+#, python-format
+msgid ""
+"<a href=\"%(tunnelmessage)s\">Tunnel messages</a>: 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 ""
+"<a href=\"%(i2np)s\">I2NP messages</a>: 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 ""
+"<b>I2P Garlic Layer:</b> provide encrypted and anonymous end-to-end I2P "
+"message delivery."
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/index.html:55
+#, python-format
+msgid ""
+"<a href=\"%(i2np)s\">I2NP messages</a>: 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 ""
+"<b>I2P Client Layer:</b> 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 ""
+"<a href=\"%(i2cp)s\">I2CP</a>: 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 ""
+"<b>I2P End-to-end Transport Layer:</b> allow TCP- or UDP-like "
+"functionality on top of I2P."
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/index.html:76
+#, python-format
+msgid ""
+"<a href=\"%(streaming)s\">Streaming Library</a>: 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 ""
+"<a href=\"%(datagrams)s\">Datagram Library</a>: 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 ""
+"<b>I2P Application Interface Layer:</b> additional (optional) libraries "
+"allowing easier implementations on top of I2P."
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/index.html:93
+msgid "<b>I2P Application Proxy Layer:</b> proxy systems."
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/index.html:95
+#, python-format
+msgid "HTTP Client/Server, IRC Client, <a href=\"%(socks)s\">SOCKS</a>, Streamr"
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/index.html:99
+msgid ""
+"Finally, what could be considered the <b>'I2P application layer'</b>, 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 "<b>Streaming/datagram applications</b>: i2psnark, Syndie, i2phex..."
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/index.html:105
+msgid "<b>SAM/BOB applications</b>: IMule, i2p-bt, i2prufus, Robert..."
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/index.html:106
+#, python-format
+msgid ""
+"<b>Other I2P applications</b>: Syndie, EepGet, <a "
+"href=\"%(plugins)s\">plugins</a>..."
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/index.html:107
+msgid ""
+"<b>Regular applications</b>: 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/transport/index.html:2
+msgid "Transport Overview"
+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 three transports currently implemented:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/index.html:21
+#, python-format
+msgid "<a href=\"%(ntcp)s\">NTCP</a>, a Java New I/O (NIO) TCP transport"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/index.html:22
+#, python-format
+msgid " <a href=\"%(ssu)s\">SSU</a>, or Secure Semireliable UDP"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/index.html:23
+#, python-format
+msgid "<a href=\"%(ntcp2)s\">NTCP2</a>, a new version of NTCP"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/index.html:26
+msgid ""
+"Each provides a \"connection\" paradigm, with authentication,\n"
+"flow control, acknowledgments and retransmission."
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/index.html:32
+msgid "Transport Services"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/index.html:34
+msgid "The transport subsystem in I2P provides the following services:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/index.html:38
+#, python-format
+msgid ""
+"Reliable delivery of <a href=\"%(i2np)s\">I2NP</a> messages.\n"
+"Transports support I2NP message delivery ONLY.\n"
+"They are not general-purpose data pipes."
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/index.html:43
+msgid "In-order delivery of messages is NOT guaranteed by all transports."
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/index.html:44
+msgid ""
+"Maintain a set of router addresses, one or more for each transport,\n"
+"that the router publishes as its global contact information (the "
+"RouterInfo).\n"
+"Each transport may connect using one of these addresses, which may be\n"
+"IPv4 or (as of version 0.9.8) IPv6."
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/index.html:50
+msgid "Selection of the best transport for each outgoing message"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/index.html:51
+msgid "Queueing of outbound messages by priority"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/index.html:52
+msgid ""
+"Bandwidth limiting, both outbound and inbound, according to router "
+"configuration"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/index.html:53
+msgid "Setup and teardown of transport connections"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/index.html:54
+msgid "Encryption of point-to-point communications"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/index.html:55
+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:59
+msgid "Firewall port opening using UPnP (Universal Plug and Play)"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/index.html:60
+msgid "Cooperative NAT/Firewall traversal"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/index.html:61
+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:62
+msgid ""
+"Coordination of firewall status and local IP, and changes to either, "
+"among the transports"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/index.html:63
+#: i2p2www/pages/site/docs/transport/ssu.html:35
+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:64
+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:65
+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:69
+msgid "Qualification of valid IP addresses according to a local rule set"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/index.html:70
+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:77
+msgid "Transport Addresses"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/index.html:79
+msgid ""
+"The transport subsystem maintains a set of router addresses, each of "
+"which lists a transport method, IP, and port.\n"
+"These addresses constitute the advertised contact points, and are "
+"published by the router to the network database.\n"
+"Addresses may also contain an arbitrary set of additional options."
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/index.html:85
+msgid "Each transport method may publish multiple router addresses."
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/index.html:89
+msgid "Typical scenarios are:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/index.html:91
+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:92
+#, 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 <a "
+"href=\"%(ssu)s\">the SSU spec</a> for details)"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/index.html:96
+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:102
+msgid "Transport Selection"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/index.html:104
+#, python-format
+msgid ""
+"The transport system delivers <a href=\"%(i2np)s\">I2NP messages</a> "
+"only. The transport selected for any message is\n"
+"independent of the upper-layer protocols and contents (router or client "
+"messages, whether an external application was using\n"
+"TCP or UDP to connect to I2P, whether the upper layer was using\n"
+"<a href=\"%(streaming)s\">the streaming library</a>\n"
+"streaming\n"
+"or\n"
+"<a href=\"%(datagrams)s\">datagrams</a>,\n"
+"datagrams\n"
+"etc.)."
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/index.html:118
+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:124
+msgid "Whether a transport bids, and with what value, depend on numerous factors:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/index.html:128
+msgid "Configuration of transport preferences"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/index.html:129
+msgid "Whether the transport is already connected to the peer"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/index.html:130
+msgid ""
+"The number of current connections compared to various connection limit "
+"thresholds"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/index.html:131
+msgid "Whether recent connection attempts to the peer have failed"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/index.html:132
+msgid ""
+"The size of the message, as different transports have different size "
+"limits"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/index.html:133
+msgid ""
+"Whether the peer can accept incoming connections for that transport, as "
+"advertised in its RouterInfo"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/index.html:134
+msgid "Whether the connection would be indirect (requiring introducers) or direct"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/index.html:135
+msgid "The peer's transport preference, as advertised in its RouterInfo"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/index.html:138
+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:145
+msgid "New Transports and Future Work"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/index.html:147
+msgid "Additional transports may be developed, including:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/index.html:152
+msgid "A TLS/SSH look-alike transport"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/index.html:153
+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:154
+msgid "Tor-compatible pluggable transports"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/index.html:157
+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:164
+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:171
+#, python-format
+msgid ""
+"Analyze <a href=\"%(pdf)s\">Breaking and Improving Protocol "
+"Obfuscation</a>\n"
+"and see how transport-layer padding may improve things."
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:2
+msgid "NTCP (NIO-based TCP)"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:6
+#, python-format
+msgid ""
+"The others are <a href=\"%(ssu)s\">SSU</a> and <a "
+"href=\"%(ntcp2)s\">NTCP2</a>.\n"
+"NTCP is a Java NIO-based transport introduced in I2P release 0.6.1.22.\n"
+"Java NIO (new I/O) does not suffer from the 1 thread per connection "
+"issues of the old TCP transport.\n"
+"NTCP-over-IPv6 is supported as of version 0.9.8."
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:13
+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:21
+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:27
+#: i2p2www/pages/site/docs/transport/ssu.html:38
+msgid "Router Address Specification"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:29
+#: i2p2www/pages/site/docs/transport/ssu.html:40
+msgid "The following properties are stored in the network database."
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:44
+msgid "NTCP Protocol Specification"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:46
+msgid "Standard Message Format"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:47
+msgid ""
+"After establishment,\n"
+"the NTCP transport sends individual I2NP messages, with a simple "
+"checksum.\n"
+"The unencrypted message is encoded as follows:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:65
+msgid ""
+"The data is then AES/256/CBC encrypted. The session key for the "
+"encryption\n"
+"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:73
+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:81
+msgid "Time Sync Message Format"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:82
+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:93
+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:99
+msgid "Checksums"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:100
+#, python-format
+msgid ""
+"The standard and time sync messages use the Adler-32 checksum\n"
+"as defined in the <a href=\"%(rfc1950)s\">ZLIB Specification</a>."
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:106
+#: i2p2www/pages/site/docs/transport/ssu.html:187
+msgid "Idle Timeout"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:107
+#: i2p2www/pages/site/docs/transport/ssu.html:188
+msgid ""
+"Idle timeout and connection close is at the discretion of each endpoint "
+"and may vary.\n"
+"The current implementation lowers the timeout as the number of "
+"connections approaches the\n"
+"configured maximum, and raises the timeout when the connection count is "
+"low.\n"
+"The recommended minimum timeout is two minutes or more, and the "
+"recommended\n"
+"maximum timeout is ten minutes or more."
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:116
+msgid "RouterInfo Exchange"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:117
+msgid ""
+"After establishment, and every 30-60 minutes thereafter,\n"
+"the two routers should generally exchange RouterInfos using a "
+"DatabaseStoreMessage.\n"
+"However, Alice should check if the first queued message is a "
+"DatabaseStoreMessage\n"
+"so as not to send a duplicate message; this is often the case when "
+"connecting to a floodfill router."
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:125
+msgid "Establishment Sequence"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:126
+msgid ""
+"In the establish state, there is a 4-phase message sequence to exchange "
+"DH keys and signatures.\n"
+"In the first two messages there is a 2048-bit Diffie Hellman exchange.\n"
+"Then, signatures of the critical data are exchanged to confirm the "
+"connection."
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:142
+msgid "Legend:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:143
+msgid "256 byte DH public keys"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:147
+msgid "timestamps (4 bytes, seconds since epoch)"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:148
+msgid "32 byte Session key"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:149
+msgid "2 byte size of Alice identity to follow"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:152
+msgid "DH Key Exchange"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:153
+#, 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"
+"<a href=\"%(cryptography)s#elgamal\">ElGamal encryption</a>."
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:159
+msgid ""
+"The DH key exchange consists of a number of steps, displayed below.\n"
+"The mapping between these steps and the messages sent between I2P "
+"routers,\n"
+"is marked in bold."
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:165
+msgid ""
+"Alice generates a secret integer x. She then calculates <code>X = g^x mod"
+" p</code>."
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:166
+msgid "Alice sends X to Bob <b>(Message 1)</b>."
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:167
+msgid ""
+"Bob generates a secret integer y. He then calculates <code>Y = g^y mod "
+"p</code>."
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:168
+msgid "Bob sends Y to Alice.<b>(Message 2)</b>"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:169
+msgid "Alice can now compute <code>sessionKey = Y^x mod p</code>."
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:170
+msgid "Bob can now compute <code>sessionKey = X^y mod p</code>."
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:171
+msgid ""
+"Both Alice and Bob now have a shared key <code>sessionKey = g^(x*y) mod "
+"p</code>."
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:173
+#, python-format
+msgid ""
+"The sessionKey is then used to exchange identities in <b>Message 3</b> "
+"and <b>Message 4</b>.\n"
+"The exponent (x and y) length for the DH exchange is documented on the\n"
+"<a href=\"%(crypto)s#exponent\">cryptography page</a>."
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:193
+msgid "Message 1 (Session Request)"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:194
+#, python-format
+msgid ""
+"This is the DH request. Alice already has Bob's\n"
+"<a href=\"%(commonstructures)s#struct_RouterIdentity\">Router "
+"Identity</a>,\n"
+"IP address, and port, as contained in his\n"
+"<a href=\"%(commonstructures)s#struct_RouterInfo\">Router Info</a>,\n"
+"which was published to the\n"
+"<a href=\"%(netdb)s\">network database</a>.\n"
+"Alice sends Bob:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:207
+#: i2p2www/pages/site/docs/transport/ntcp.html:250
+#: i2p2www/pages/site/docs/transport/ntcp.html:332
+#: i2p2www/pages/site/docs/transport/ntcp.html:437
+msgid "Size:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:209
+msgid "Contents:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:227
+msgid "256 byte X from Diffie Hellman"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:229
+msgid "SHA256 Hash(X) xored with SHA256 Hash(Bob's `RouterIdentity`)"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:236
+#: i2p2www/pages/site/docs/transport/ntcp.html:319
+#: i2p2www/pages/site/docs/transport/ntcp.html:398
+msgid "Notes:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:237
+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:243
+msgid "Message 2 (Session Created)"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:244
+msgid "This is the DH reply. Bob sends Alice:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:252
+#: i2p2www/pages/site/docs/transport/ntcp.html:334
+#: i2p2www/pages/site/docs/transport/ntcp.html:439
+msgid "Unencrypted Contents:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:274
+#: i2p2www/pages/site/docs/transport/ntcp.html:310
+msgid "256 byte Y from Diffie Hellman"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:276
+msgid "SHA256 Hash(X concatenated with Y)"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:279
+#: i2p2www/pages/site/docs/transport/ntcp.html:364
+msgid "4 byte timestamp (seconds since the epoch)"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:281
+msgid "12 bytes random data"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:285
+#: i2p2www/pages/site/docs/transport/ntcp.html:376
+#: i2p2www/pages/site/docs/transport/ntcp.html:466
+msgid "Encrypted Contents:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:312
+#, python-format
+msgid ""
+"48 bytes <a href=\"%(cryptography)s#AES\">AES encrypted</a> using the DH "
+"session key and\n"
+"                  the last 16 bytes of Y as the IV"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:320
+msgid ""
+"Alice may drop the connection if the clock skew with Bob is too high as "
+"calculated using tsB."
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:325
+msgid "Message 3 (Session Confirm A)"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:326
+msgid ""
+"This contains Alice's router identity, and a signature of the critical "
+"data. Alice sends Bob:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:360
+msgid "2 byte size of Alice's router identity to follow (387+)"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:362
+msgid "Alice's 387+ byte `RouterIdentity`"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:366
+#: i2p2www/pages/site/docs/transport/ntcp.html:461
+msgid "0-15 bytes random data"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:368
+msgid ""
+"the `Signature` of the following concatenated data:\n"
+"             X, Y, Bob's `RouterIdentity`, tsA, tsB.\n"
+"             Alice signs it with the `SigningPrivateKey` associated with "
+"the `SigningPublicKey` in her `RouterIdentity`"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:389
+#, python-format
+msgid ""
+"448 bytes <a href=\"%(cryptography)s#AES\">AES encrypted</a> using the DH"
+" session key and\n"
+"                  the last 16 bytes of HXxorHI (i.e., the last 16 bytes "
+"of message #1) as the IV"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:400
+msgid "Bob verifies the signature, and on failure, drops the connection."
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:403
+msgid ""
+"Bob may drop the connection if the clock skew with Alice is too high as "
+"calculated using tsA."
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:406
+msgid ""
+"Alice will use the last 16 bytes of the encrypted contents of this "
+"message as the IV for the next message."
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:430
+msgid "Message 4 (Session Confirm B)"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:431
+msgid "This is a signature of the critical data. Bob sends Alice:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:455
+msgid ""
+"the `Signature` of the following concatenated data:\n"
+"             X, Y, Alice's `RouterIdentity`, tsA, tsB.\n"
+"             Bob signs it with the `SigningPrivateKey` associated with "
+"the `SigningPublicKey` in his `RouterIdentity`"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:479
+#, python-format
+msgid ""
+"Data <a href=\"%(cryptography)s#AES\">AES encrypted</a> using the DH "
+"session key and\n"
+"                  the last 16 bytes of the encrypted contents of message "
+"#2 as the IV\n"
+"                  48 bytes for a DSA signature, may vary for other "
+"signature types"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:488
+msgid "Alice verifies the signature, and on failure, drops the connection."
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:491
+msgid ""
+"Bob will use the last 16 bytes of the encrypted contents of this message "
+"as the IV for the next message."
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:506
+msgid "After Establishment"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:507
+msgid ""
+"The connection is established, and standard or time sync messages may be "
+"exchanged.\n"
+"All subsequent messages are AES encrypted using the negotiated DH session"
+" key.\n"
+"Alice will use the last 16 bytes of the encrypted contents of message #3 "
+"as the next IV.\n"
+"Bob will use the last 16 bytes of the encrypted contents of message #4 as"
+" the next IV."
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:516
+msgid "Check Connection Message"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:517
+msgid ""
+"Alternately, when Bob receives a connection, it could be a\n"
+"check connection (perhaps prompted by Bob asking for someone\n"
+"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:526
+msgid "32 bytes of uninterpreted, ignored data"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:527
+msgid "1 byte size"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:528
+msgid ""
+"that many bytes making up the local router's IP address (as reached by "
+"the remote side)"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:529
+msgid "2 byte port number that the local router was reached on"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:530
+msgid ""
+"4 byte i2p network time as known by the remote side (seconds since the "
+"epoch)"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:531
+msgid "uninterpreted padding data, up to byte 223"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:532
+msgid ""
+"xor of the local router's identity hash and the SHA256 of bytes 32 "
+"through bytes 223"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:535
+msgid "Check connection is completely disabled as of release 0.9.12."
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:539
+msgid "Discussion"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:540
+#, python-format
+msgid "Now on the <a href=\"%(ntcpdisc)s\">NTCP Discussion Page</a>."
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:546
+msgid "The maximum message size should be increased to approximately 32 KB."
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:550
+msgid ""
+"A set of fixed packet sizes may be appropriate to further hide the data \n"
+"fragmentation to external adversaries, but the tunnel, garlic, and end to"
+" \n"
+"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:558
+msgid ""
+"Memory utilization (including that of the kernel) for NTCP should be "
+"compared to that for SSU."
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:562
+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/ssu.html:2
+msgid "Secure Semireliable UDP"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ssu.html:7
+#, python-format
+msgid ""
+"SSU (also called \"UDP\" in much of the I2P documentation and user "
+"interfaces)\n"
+"is one of three <a href=\"%(transports)s\">transports</a> currently "
+"implemented in I2P.\n"
+"The others are <a href=\"%(ntcp)s\">NTCP</a> and <a "
+"href=\"%(ntcp2)s\">NTCP2</a>."
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ssu.html:13
+msgid ""
+"SSU was introduced in I2P release 0.6.\n"
+"In a standard I2P installation, the router uses both NTCP and SSU for "
+"outbound connections.\n"
+"SSU-over-IPv6 is supported as of version 0.9.8."
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ssu.html:19
+msgid ""
+"SSU is called \"semireliable\" because it will repeatedly retransmit "
+"unacknowledged messages,\n"
+"but only up to a maximum number of times. After that, the message is "
+"dropped."
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ssu.html:24
+msgid "SSU Services"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ssu.html:26
+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:32
+msgid ""
+"Cooperative NAT/Firewall traversal using <a "
+"href=\"#introduction\">introducers</a>"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ssu.html:33
+msgid ""
+"Local IP detection by inspection of incoming packets and <a "
+"href=\"#peerTesting\">peer testing</a>"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ssu.html:34
+msgid ""
+"Communication of firewall status and local IP, and changes to either to "
+"NTCP"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ssu.html:46
+#: i2p2www/pages/site/docs/transport/ssu.html:60
+#: i2p2www/pages/site/docs/transport/ssu.html:61
+#: i2p2www/pages/site/docs/transport/ssu.html:63
+#: i2p2www/pages/site/docs/transport/ssu.html:66
+#: i2p2www/pages/site/docs/transport/ssu.html:70
+#: i2p2www/pages/site/docs/transport/ssu.html:71
+#: i2p2www/pages/site/docs/transport/ssu.html:77
+msgid "See below"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ssu.html:84
+msgid "Protocol Details"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ssu.html:86
+msgid "Congestion control"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ssu.html:88
+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:95
+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:106
+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:118
+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:125
+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:131
+msgid ""
+"For both MTU values, it is desirable that (MTU &#37; 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:137
+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:143
+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:149
+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:154
+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:161
+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:167
+msgid ""
+"For IPv6, the minimum MTU is 1280. The IPv6 IP/UDP header is 48 bytes,\n"
+"so we use an MTU where (MTN &#37; 16 == 0), which is true for 1280.\n"
+"The maximum IPv6 MTU is 1488.\n"
+" (max was 1472 prior to version 0.9.28)."
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ssu.html:174
+msgid "Message Size Limits"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ssu.html:175
+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:197
+msgid "Keys"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ssu.html:199
+msgid ""
+"All encryption used is AES256/CBC with 32 byte keys and 16 byte IVs.\n"
+"When Alice originates a session with Bob,\n"
+"the MAC and session keys are negotiated as part of the DH exchange, and "
+"are then used\n"
+"for the HMAC and encryption, respectively.  During the DH exchange, \n"
+"Bob's publicly knowable introKey is used for the MAC and encryption."
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ssu.html:207
+msgid ""
+"Both the initial message and the 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:216
+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:227
+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:238
+#, python-format
+msgid ""
+"For the DH key agreement,\n"
+"<a href=\"%(rfc3526)s\">RFC3526</a> 2048bit\n"
+"MODP group (#14) is used:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ssu.html:248
+#, python-format
+msgid ""
+"These are the same p and g used for I2P's\n"
+"<a href=\"%(cryptography)s#elgamal\">ElGamal encryption</a>."
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ssu.html:253
+msgid "Replay prevention"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ssu.html:255
+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:262
+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:270
+msgid "Addressing"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ssu.html:272
+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:284
+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 <a href=\"#capabilities\">below</a>."
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ssu.html:290
+#, python-format
+msgid ""
+"The addresses, options, and capabilities are published in the <a "
+"href=\"%(netdb)s\">network database</a>."
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ssu.html:295
+msgid "Direct Session Establishment"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ssu.html:296
+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:301
+msgid "Connection establishment (direct)"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ssu.html:302
+msgid ""
+"Alice connects directly to Bob.\n"
+"IPv6 is supported as of version 0.9.8."
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ssu.html:317
+#, python-format
+msgid ""
+"After the SessionConfirmed message is received, Bob sends a small\n"
+"<a href=\"%(i2npspec)s#msg_DeliveryStatus\">DeliveryStatus message</a>\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:326
+#, python-format
+msgid ""
+"After the status message is sent, the peers usually exchange\n"
+"<a href=\"%(i2npspec)s#msg_DatabaseStore\">DatabaseStore messages</a>\n"
+"containing their\n"
+"<a href=\"%(commonstructures)s#struct_RouterInfo\">RouterInfos</a>,\n"
+"however, this is not required."
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ssu.html:335
+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:344
+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:358
+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:385
+msgid "Connection establishment (indirect using an introducer)"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ssu.html:387
+msgid "Alice first connects to introducer Bob, who relays the request to Charlie."
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ssu.html:405
+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:419
+msgid "Peer testing"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ssu.html:421
+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:440
+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:450
+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:459
+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:470
+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:480
+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:488
+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:498
+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:526
+msgid "Transmission window, ACKs and Retransmissions"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ssu.html:527
+#, 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"
+"<a href=\"%(ssuspec)s\">the protocol specification page</a>\n"
+"for details."
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ssu.html:535
+#, 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 <a href=\"%(streaming)s\">streaming</a>.\n"
+"See the code for initial, min and max parameters."
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ssu.html:547
+msgid "Security"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ssu.html:548
+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:556
+msgid ""
+"The details of validation are not specified\n"
+"here. Implementers should add defenses where appropriate."
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ssu.html:562
+msgid "Peer capabilities"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ssu.html:566
+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:578
+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:587
+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:593
+msgid ""
+"The current implementation repeatedly sends acknowledgments for the same "
+"packets,\n"
+"which unnecessarily increases overhead."
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ssu.html:598
+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:604
+msgid "The protocol should be extended to exchange MTUs during the setup."
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ssu.html:608
+msgid "Rekeying is currently unimplemented and may never be."
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ssu.html:612
+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:617
+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:623
+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:629
+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:633
+msgid "Capacities appear to be unused."
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ssu.html:637
+msgid ""
+"Signed-on times in SessionCreated and SessionConfirmed appear to be "
+"unused or unverified."
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ssu.html:642
+msgid "Implementation Diagram"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ssu.html:643
+msgid ""
+"This diagram\n"
+"should accurately reflect the current implementation, however there may "
+"be small differences."
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ssu.html:651
+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"
+"</i>gateway</i>, 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 <i>endpoint</i> 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"
+"<a href=\"%(tunnelrouting)s\">on the tunnel overview page</a>."
+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, <a href=\"%(i2np)s\">I2NP messages</a> 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 "Roll"
+
+#: 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 "Osaleja"
+
+#: 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"
+"<a href=\"%(i2np)s\">I2NP messages</a> into fixed-size\n"
+"<a href=\"%(tunnelmessage)s\">tunnel messages</a>\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"
+"<a href=\"%(tunnelmessage)s\">tunnel message specification</a>."
+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:243
+msgid ""
+"Duplicate message detection is handled by a decaying Bloom filter on "
+"message\n"
+"IVs.  Each router maintains a single Bloom filter to contain the XOR of "
+"the IV and\n"
+"the first block of the message received for all of the tunnels it is "
+"participating\n"
+"in, modified to drop seen entries after 10-20 minutes (when the tunnels "
+"will have\n"
+"expired).  The size of the bloom filter and the parameters used are "
+"sufficient to\n"
+"more than saturate the router's network connection with a negligible "
+"chance of \n"
+"false positive.  The unique value fed into the Bloom filter is the XOR of"
+" the IV \n"
+"and the first block so as to prevent nonsequential colluding peers in the"
+" tunnel \n"
+"from tagging a message by resending it with the IV and first block "
+"switched."
+msgstr ""
+
+#: i2p2www/pages/site/docs/tunnels/implementation.html:256
+msgid "Endpoint Processing"
+msgstr ""
+
+#: i2p2www/pages/site/docs/tunnels/implementation.html:258
+msgid ""
+"After receiving and validating a tunnel message at the last hop in the "
+"tunnel,\n"
+"how the endpoint recovers the data encoded by the gateway depends upon "
+"whether \n"
+"the tunnel is an inbound or an outbound tunnel.  For outbound tunnels, "
+"the \n"
+"endpoint encrypts the message with its layer key just like any other "
+"participant, \n"
+"exposing the preprocessed data.  For inbound tunnels, the endpoint is "
+"also the \n"
+"tunnel creator so they can merely iteratively decrypt the IV and message,"
+" using the \n"
+"layer and IV keys of each step in reverse order."
+msgstr ""
+
+#: i2p2www/pages/site/docs/tunnels/implementation.html:268
+msgid ""
+"At this point, the tunnel endpoint has the preprocessed data sent by the "
+"gateway,\n"
+"which it may then parse out into the included I2NP messages and forwards "
+"them as\n"
+"requested in their delivery instructions."
+msgstr ""
+
+#: i2p2www/pages/site/docs/tunnels/implementation.html:275
+msgid "Tunnel Building"
+msgstr ""
+
+#: i2p2www/pages/site/docs/tunnels/implementation.html:277
+msgid ""
+"When building a tunnel, the creator must send a request with the "
+"necessary\n"
+"configuration data to each of the hops and wait for all of them to agree "
+"before\n"
+"enabling the tunnel.  The requests are encrypted so that only the peers "
+"who need\n"
+"to know a piece of information (such as the tunnel layer or IV key) has "
+"that\n"
+"data.  In addition, only the tunnel creator will have access to the "
+"peer's\n"
+"reply.  There are three important dimensions to keep in mind when "
+"producing\n"
+"the tunnels: what peers are used (and where), how the requests are sent "
+"(and \n"
+"replies received), and how they are maintained."
+msgstr ""
+
+#: i2p2www/pages/site/docs/tunnels/implementation.html:291
+msgid ""
+"Beyond the two types of tunnels - inbound and outbound - there are two "
+"styles\n"
+"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:299
+msgid "Exploratory tunnel peer selection"
+msgstr ""
+
+#: i2p2www/pages/site/docs/tunnels/implementation.html:301
+msgid ""
+"Exploratory tunnels are built out of a random selection of peers from a "
+"subset\n"
+"of the network.  The particular subset varies on the local router and on "
+"what their\n"
+"tunnel routing needs are.  In general, the exploratory tunnels are built "
+"out of\n"
+"randomly selected peers who are in the peer's \"not failing but active\" "
+"profile\n"
+"category.  The secondary purpose of the tunnels, beyond merely tunnel "
+"routing,\n"
+"is to find underutilized high capacity peers so that they can be promoted"
+" for\n"
+"use in client tunnels."
+msgstr ""
+
+#: i2p2www/pages/site/docs/tunnels/implementation.html:311
+#, python-format
+msgid ""
+"Exploratory peer selection is discussed further on the\n"
+"<a href=\"%(peerselection)s\">Peer Profiling and Selection page</a>."
+msgstr ""
+
+#: i2p2www/pages/site/docs/tunnels/implementation.html:317
+msgid "Client tunnel peer selection"
+msgstr ""
+
+#: i2p2www/pages/site/docs/tunnels/implementation.html:319
+msgid ""
+"Client tunnels are built with a more stringent set of requirements - the "
+"local\n"
+"router will select peers out of its \"fast and high capacity\" profile "
+"category so\n"
+"that performance and reliability will meet the needs of the client "
+"application.\n"
+"However, there are several important details beyond that basic selection "
+"that \n"
+"should be adhered to, depending upon the client's anonymity needs."
+msgstr ""
+
+#: i2p2www/pages/site/docs/tunnels/implementation.html:327
+#, python-format
+msgid ""
+"Client peer selection is discussed further on the\n"
+"<a href=\"%(peerselection)s\">Peer Profiling and Selection page</a>."
+msgstr ""
+
+#: i2p2www/pages/site/docs/tunnels/implementation.html:332
+msgid "Peer Ordering within Tunnels"
+msgstr ""
+
+#: i2p2www/pages/site/docs/tunnels/implementation.html:334
+#, python-format
+msgid ""
+"Peers are ordered within tunnels to deal with the\n"
+"<a href=\"%(pdf)s\">predecessor attack</a>\n"
+"<a href=\"%(pdf2008)s\">(2008 update)</a>."
+msgstr ""
+
+#: i2p2www/pages/site/docs/tunnels/implementation.html:341
+msgid ""
+"To frustrate the predecessor \n"
+"attack, the tunnel selection keeps the peers selected in a strict order -"
+"\n"
+"if A, B, and C are in a tunnel for a particular tunnel pool, the hop "
+"after A is always B, and the hop after\n"
+"B is always C."
+msgstr ""
+
+#: i2p2www/pages/site/docs/tunnels/implementation.html:348
+msgid ""
+"Ordering is implemented by generating a random 32-byte key for each\n"
+"tunnel pool at startup.\n"
+"Peers should not be able to guess the ordering, or an attacker could\n"
+"craft two router hashes far apart to maximize the chance of being at both"
+"\n"
+"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:363
+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:370
+msgid "Request delivery"
+msgstr ""
+
+#: i2p2www/pages/site/docs/tunnels/implementation.html:372
+#, python-format
+msgid ""
+"A multi-hop tunnel is built using a single build message which is "
+"repeatedly\n"
+"decrypted and forwarded. In the terminology of\n"
+"<a href=\"%(pdf)s\">Hashing it out in Public</a>,\n"
+"this is \"non-interactive\" telescopic tunnel building."
+msgstr ""
+
+#: i2p2www/pages/site/docs/tunnels/implementation.html:379
+#, python-format
+msgid ""
+"This tunnel request preparation, delivery, and response method is\n"
+"<a href=\"%(tunnelcreation)s\">designed</a> 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:390
+#, python-format
+msgid ""
+"The details of tunnel request and response messages, and their "
+"encryption,\n"
+"<a href=\"%(tunnelcreation)s\">are specified here</a>."
+msgstr ""
+
+#: i2p2www/pages/site/docs/tunnels/implementation.html:395
+msgid ""
+"Peers may reject tunnel creation requests for a variety of reasons, "
+"though\n"
+"a series of four increasingly severe rejections are known: probabilistic "
+"rejection\n"
+"(due to approaching the router's capacity, or in response to a flood of "
+"requests), \n"
+"transient overload, bandwidth overload, and critical failure.  When "
+"received, \n"
+"those four are interpreted by the tunnel creator to help adjust their "
+"profile of\n"
+"the router in question."
+msgstr ""
+
+#: i2p2www/pages/site/docs/tunnels/implementation.html:404
+#, python-format
+msgid ""
+"For more information on peer profiling, see the\n"
+"<a href=\"%(peerselection)s\">Peer Profiling and Selection page</a>."
+msgstr ""
+
+#: i2p2www/pages/site/docs/tunnels/implementation.html:410
+msgid "Tunnel Pools"
+msgstr ""
+
+#: i2p2www/pages/site/docs/tunnels/implementation.html:412
+#, python-format
+msgid ""
+"To allow efficient operation, the router maintains a series of tunnel "
+"pools,\n"
+"each managing a group of tunnels used for a specific purpose with their "
+"own\n"
+"configuration.  When a tunnel is needed for that purpose, the router "
+"selects one\n"
+"out of the appropriate pool at random.  Overall, there are two "
+"exploratory tunnel\n"
+"pools - one inbound and one outbound - each using the router's default "
+"configuration.\n"
+"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 <a "
+"href=\"%(i2cp)s\">I2CP</a>, or the router's defaults if\n"
+"not specified."
+msgstr ""
+
+#: i2p2www/pages/site/docs/tunnels/implementation.html:424
+#, python-format
+msgid ""
+"Each pool has within its configuration a few key settings, defining how "
+"many\n"
+"tunnels to keep active, how many backup tunnels to maintain in case of "
+"failure,\n"
+"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 <a href=\"%(i2cp)s\">I2CP "
+"page</a>."
+msgstr ""
+
+#: i2p2www/pages/site/docs/tunnels/implementation.html:434
+msgid "Tunnel Lengths and Defaults"
+msgstr ""
+
+#: i2p2www/pages/site/docs/tunnels/implementation.html:436
+msgid "On the tunnel overview page"
+msgstr ""
+
+#: i2p2www/pages/site/docs/tunnels/implementation.html:438
+msgid "Anticipatory Build Strategy and Priority"
+msgstr ""
+
+#: i2p2www/pages/site/docs/tunnels/implementation.html:440
+msgid ""
+"Tunnel building is expensive, and tunnels expire a fixed time after they "
+"are built.\n"
+"However, when a pool that runs out of tunnels, the Destination is "
+"essentially dead.\n"
+"In addition, tunnel build success rate may vary greatly with both local "
+"and global\n"
+"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:451
+msgid ""
+"For each tuple {exploratory/client, in/out, length, length variance}\n"
+"the router maintains statistics on the time required for a successful\n"
+"tunnel build.\n"
+"Using these statistics, it calculates how long before a tunnel's "
+"expiration\n"
+"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:462
+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:471
+msgid "Tunnel Message Throttling"
+msgstr ""
+
+#: i2p2www/pages/site/docs/tunnels/implementation.html:473
+msgid ""
+"Even though the tunnels within I2P bear a resemblance to a circuit "
+"switched\n"
+"network, everything within I2P is strictly message based - tunnels are "
+"merely\n"
+"accounting tricks to help organize the delivery of messages.  No "
+"assumptions are\n"
+"made regarding reliability or ordering of messages, and retransmissions "
+"are left\n"
+"to higher levels (e.g. I2P's client layer streaming library).  This "
+"allows I2P\n"
+"to take advantage of throttling techniques available to both packet "
+"switched and\n"
+"circuit switched networks.  For instance, each router may keep track of "
+"the \n"
+"moving average of how much data each tunnel is using, combine that with "
+"all of \n"
+"the averages used by other tunnels the router is participating in, and be"
+" able\n"
+"to accept or reject additional tunnel participation requests based on its"
+" \n"
+"capacity and utilization.  On the other hand, each router can simply drop"
+" \n"
+"messages that are beyond its capacity, exploiting the research used on "
+"the \n"
+"normal Internet."
+msgstr ""
+
+#: i2p2www/pages/site/docs/tunnels/implementation.html:489
+msgid ""
+"In the current implementation, routers implement a\n"
+"weighted random early discard (WRED) strategy.\n"
+"For all participating routers (internal participant, inbound gateway, and"
+" outbound endpoint),\n"
+"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:507
+msgid "Mixing/batching"
+msgstr ""
+
+#: i2p2www/pages/site/docs/tunnels/implementation.html:509
+msgid ""
+"What strategies could be used at the gateway and at each hop for "
+"delaying,\n"
+"reordering, rerouting, or padding messages?  To what extent should this "
+"be done\n"
+"automatically, how much should be configured as a per tunnel or per hop "
+"setting,\n"
+"and how should the tunnel's creator (and in turn, user) control this "
+"operation?\n"
+"All of this is left as unknown, to be worked out for a distant future "
+"release."
+msgstr ""
+
+#: i2p2www/pages/site/docs/tunnels/implementation.html:518
+msgid "Padding"
+msgstr ""
+
+#: i2p2www/pages/site/docs/tunnels/implementation.html:519
+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:529
+msgid ""
+"WRED strategies have a significant impact on end-to-end performance,\n"
+"and prevention of network congestion collapse.\n"
+"The current WRED strategy should be carefully evaluated and improved."
+msgstr ""
+
+#: 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 <a "
+"href=\"%(tunnelimpl)s\">here</a> for the current implementation"
+msgstr ""
+
+#: i2p2www/pages/site/docs/tunnels/unidirectional.html:3
+msgid "November 2016"
+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 information 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 <a href=\"%(pdf)s\">paper by Hermann and Grothoff</a>\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/sk/LC_MESSAGES/docs.po b/i2p2www/translations/sk/LC_MESSAGES/docs.po
new file mode 100644
index 00000000..474640f2
--- /dev/null
+++ b/i2p2www/translations/sk/LC_MESSAGES/docs.po
@@ -0,0 +1,16124 @@
+# Slovak translations for I2P.
+# Copyright (C) 2018 ORGANIZATION
+# This file is distributed under the same license as the I2P project.
+#
+# Translators:
+# ondy, 2016
+msgid ""
+msgstr ""
+"Project-Id-Version:  I2P\n"
+"Report-Msgid-Bugs-To: http://trac.i2p2.de\n"
+"POT-Creation-Date: 2018-08-24 11:47+0000\n"
+"PO-Revision-Date: 2018-08-24 11:51+0000\n"
+"Last-Translator: zzzi2p\n"
+"Language-Team: Slovak (http://www.transifex.com/otf/I2P/language/sk/)\n"
+"Plural-Forms: nplurals=4; plural=(n % 1 == 0 && n == 1 ? 0 : n % 1 == 0 "
+"&& n >= 2 && n <= 4 ? 1 : n % 1 != 0 ? 2: 3)\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=utf-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"Generated-By: Babel 1.3\n"
+
+#: i2p2www/pages/site/docs/index.html:2 i2p2www/pages/site/docs/index.html:23
+msgid "Index to Technical Documentation"
+msgstr "Index pre Technickú dokumentáciu"
+
+#: i2p2www/pages/site/docs/index.html:3 i2p2www/pages/site/docs/naming.html:3
+#: i2p2www/pages/site/docs/transport/index.html:3
+#: i2p2www/pages/site/docs/transport/ntcp.html:3
+#: i2p2www/pages/site/docs/transport/ssu.html:3
+msgid "June 2018"
+msgstr ""
+
+#: i2p2www/pages/site/docs/index.html:6
+msgid "Following is an index to the technical documentation for I2P."
+msgstr ""
+
+#: i2p2www/pages/site/docs/index.html:10
+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:17
+#, 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"
+"<a href=\"%(trac)s\">enter a ticket identifying the problem</a>."
+msgstr ""
+
+#: i2p2www/pages/site/docs/index.html:25 i2p2www/pages/site/docs/naming.html:6
+#: i2p2www/pages/site/docs/api/bob.html:42
+#: i2p2www/pages/site/docs/api/i2ptunnel.html:7
+#: i2p2www/pages/site/docs/api/streaming.html:6
+#: i2p2www/pages/site/docs/applications/embedding.html:7
+#: i2p2www/pages/site/docs/applications/managed-clients.html:7
+#: 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:9
+#: i2p2www/pages/site/docs/how/tech-intro.html:93
+#: i2p2www/pages/site/docs/how/tunnel-routing.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:27
+msgid "Technical Introduction"
+msgstr ""
+
+#: i2p2www/pages/site/docs/index.html:28
+msgid "A Less-Technical Introduction"
+msgstr ""
+
+#: i2p2www/pages/site/docs/index.html:29
+msgid "Threat model and analysis"
+msgstr ""
+
+#: i2p2www/pages/site/docs/index.html:30
+msgid "Comparisons to other anonymous networks"
+msgstr ""
+
+#: i2p2www/pages/site/docs/index.html:31
+msgid "Specifications"
+msgstr ""
+
+#: i2p2www/pages/site/docs/index.html:32
+msgid "Protocol stack chart"
+msgstr ""
+
+#: i2p2www/pages/site/docs/index.html:33
+msgid "Papers on I2P"
+msgstr ""
+
+#: i2p2www/pages/site/docs/index.html:34
+msgid "Presentations, articles, tutorials, videos, and interviews"
+msgstr ""
+
+#: i2p2www/pages/site/docs/index.html:35
+#, python-format
+msgid ""
+"<a href=\"%(pdf)s\">Invisible Internet Project (I2P) Project Overview</a>"
+" 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 ""
+
+#: 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
+#: i2p2www/pages/site/docs/applications/managed-clients.html:2
+#: i2p2www/pages/site/docs/applications/managed-clients.html:20
+msgid "Managed Clients"
+msgstr ""
+
+#: i2p2www/pages/site/docs/index.html:45 i2p2www/pages/site/docs/index.html:231
+msgid "Embedding the router in your application"
+msgstr ""
+
+#: i2p2www/pages/site/docs/index.html:46
+#: i2p2www/pages/site/docs/applications/bittorrent.html:2
+msgid "Bittorrent over I2P"
+msgstr ""
+
+#: i2p2www/pages/site/docs/index.html:47
+msgid "I2PControl Plugin API"
+msgstr ""
+
+#: i2p2www/pages/site/docs/index.html:48
+msgid "hostsdb.blockfile Format"
+msgstr ""
+
+#: i2p2www/pages/site/docs/index.html:49 i2p2www/pages/site/docs/index.html:197
+msgid "Configuration File Format"
+msgstr ""
+
+#: i2p2www/pages/site/docs/index.html:52
+msgid "Application Layer API and Protocols"
+msgstr ""
+
+#: i2p2www/pages/site/docs/index.html:53
+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:55
+msgid "Application Development Overview and Guide"
+msgstr ""
+
+#: i2p2www/pages/site/docs/index.html:59
+#: i2p2www/pages/site/docs/api/i2ptunnel.html:51
+msgid "I2PTunnel Configuration"
+msgstr ""
+
+#: i2p2www/pages/site/docs/index.html:75
+msgid "SAM Protocol"
+msgstr ""
+
+#: i2p2www/pages/site/docs/index.html:77
+msgid "SAMv2 Protocol"
+msgstr ""
+
+#: i2p2www/pages/site/docs/index.html:79
+msgid "SAMv3 Protocol"
+msgstr ""
+
+#: i2p2www/pages/site/docs/index.html:81
+msgid "BOB Protocol"
+msgstr ""
+
+#: i2p2www/pages/site/docs/index.html:84
+msgid "End-to-End Transport API and Protocols"
+msgstr ""
+
+#: i2p2www/pages/site/docs/index.html:85
+msgid ""
+"The end-to-end protocols used by clients for reliable and unreliable "
+"communication."
+msgstr ""
+
+#: i2p2www/pages/site/docs/index.html:87
+#: i2p2www/pages/site/docs/api/streaming.html:2
+msgid "Streaming Library"
+msgstr ""
+
+#: i2p2www/pages/site/docs/index.html:89
+msgid "Streaming Protocol Specification"
+msgstr ""
+
+#: i2p2www/pages/site/docs/index.html:91
+msgid "Streaming Javadoc"
+msgstr ""
+
+#: i2p2www/pages/site/docs/index.html:93
+#: i2p2www/pages/site/docs/api/datagrams.html:2
+msgid "Datagrams"
+msgstr ""
+
+#: i2p2www/pages/site/docs/index.html:95
+msgid "Datagram Javadoc"
+msgstr ""
+
+#: i2p2www/pages/site/docs/index.html:98
+msgid "Client-to-Router Interface API and Protocol"
+msgstr ""
+
+#: i2p2www/pages/site/docs/index.html:99
+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:104
+msgid "I2CP - I2P Control Protocol / API overview"
+msgstr ""
+
+#: i2p2www/pages/site/docs/index.html:106
+msgid "I2CP Specification"
+msgstr ""
+
+#: i2p2www/pages/site/docs/index.html:108
+msgid "I2CP API Javadoc"
+msgstr ""
+
+#: i2p2www/pages/site/docs/index.html:110
+#: i2p2www/pages/site/docs/index.html:140
+msgid "Common data structures specification"
+msgstr ""
+
+#: i2p2www/pages/site/docs/index.html:112
+#: i2p2www/pages/site/docs/index.html:142
+msgid "Data Structures Javadoc"
+msgstr ""
+
+#: i2p2www/pages/site/docs/index.html:115
+msgid "End-to-End Encryption"
+msgstr ""
+
+#: i2p2www/pages/site/docs/index.html:116
+msgid "How client messages are end-to-end encrypted by the router."
+msgstr ""
+
+#: i2p2www/pages/site/docs/index.html:118
+msgid "ElGamal/AES+SessionTag encryption"
+msgstr ""
+
+#: i2p2www/pages/site/docs/index.html:119
+#: i2p2www/pages/site/docs/index.html:153
+msgid "ElGamal and AES cryptography details"
+msgstr ""
+
+#: i2p2www/pages/site/docs/index.html:122
+#: i2p2www/pages/site/docs/how/tech-intro.html:11
+#: i2p2www/pages/site/docs/how/tech-intro.html:325
+msgid "Network Database"
+msgstr ""
+
+#: i2p2www/pages/site/docs/index.html:123
+msgid ""
+"Distributed storage and retrieval of information about routers and "
+"clients."
+msgstr ""
+
+#: i2p2www/pages/site/docs/index.html:125
+msgid "Network database overview, details, and threat analysis"
+msgstr ""
+
+#: i2p2www/pages/site/docs/index.html:126
+msgid "Cryptographic hashes"
+msgstr ""
+
+#: i2p2www/pages/site/docs/index.html:127
+msgid "Cryptographic signatures"
+msgstr ""
+
+#: i2p2www/pages/site/docs/index.html:128
+#: i2p2www/pages/site/docs/index.html:189
+msgid "Router reseed specification"
+msgstr ""
+
+#: i2p2www/pages/site/docs/index.html:131
+msgid "Router Message Protocol"
+msgstr ""
+
+#: i2p2www/pages/site/docs/index.html:132
+msgid ""
+"I2P is a message-oriented router. The messages sent between routers are "
+"defined by the I2NP protocol."
+msgstr ""
+
+#: i2p2www/pages/site/docs/index.html:134
+msgid "I2NP - I2P Network Protocol Overview"
+msgstr ""
+
+#: i2p2www/pages/site/docs/index.html:136
+msgid "I2NP Specification"
+msgstr ""
+
+#: i2p2www/pages/site/docs/index.html:138
+msgid "I2NP Javadoc"
+msgstr ""
+
+#: i2p2www/pages/site/docs/index.html:145
+#: i2p2www/pages/site/docs/how/tech-intro.html:10
+#: i2p2www/pages/site/docs/how/tech-intro.html:224
+msgid "Tunnels"
+msgstr "Tunely"
+
+#: i2p2www/pages/site/docs/index.html:146
+msgid ""
+"Selecting peers, requesting tunnels through those peers, and encrypting "
+"and routing messages through these tunnels."
+msgstr ""
+
+#: i2p2www/pages/site/docs/index.html:148
+msgid "Peer profiling and selection"
+msgstr ""
+
+#: i2p2www/pages/site/docs/index.html:149
+msgid "Tunnel routing overview"
+msgstr ""
+
+#: i2p2www/pages/site/docs/index.html:150
+msgid "Garlic routing and \"garlic\" terminology"
+msgstr ""
+
+#: i2p2www/pages/site/docs/index.html:151
+msgid "Tunnel building and encryption"
+msgstr ""
+
+#: i2p2www/pages/site/docs/index.html:152
+msgid "ElGamal/AES"
+msgstr ""
+
+#: i2p2www/pages/site/docs/index.html:152
+msgid "for build request encryption"
+msgstr ""
+
+#: i2p2www/pages/site/docs/index.html:154
+msgid "Tunnel building specification"
+msgstr ""
+
+#: i2p2www/pages/site/docs/index.html:155
+msgid "Low-level tunnel message specification"
+msgstr ""
+
+#: i2p2www/pages/site/docs/index.html:156
+#: i2p2www/pages/site/docs/tunnels/unidirectional.html:2
+msgid "Unidirectional Tunnels"
+msgstr ""
+
+#: i2p2www/pages/site/docs/index.html:157
+#: 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:158
+msgid "2009 paper (pdf), not current but still generally accurate"
+msgstr ""
+
+#: i2p2www/pages/site/docs/index.html:161
+msgid "Transport Layer"
+msgstr ""
+
+#: i2p2www/pages/site/docs/index.html:162
+msgid "The protocols for direct (point-to-point) router to router communication."
+msgstr ""
+
+#: i2p2www/pages/site/docs/index.html:164
+msgid "Transport layer overview"
+msgstr ""
+
+#: i2p2www/pages/site/docs/index.html:166
+msgid "TCP-based transport overview and specification"
+msgstr ""
+
+#: i2p2www/pages/site/docs/index.html:168
+msgid "NTCP2 specification"
+msgstr ""
+
+#: i2p2www/pages/site/docs/index.html:170
+msgid "UDP-based transport overview"
+msgstr ""
+
+#: i2p2www/pages/site/docs/index.html:172
+msgid "SSU specification"
+msgstr ""
+
+#: i2p2www/pages/site/docs/index.html:174
+msgid "NTCP transport encryption"
+msgstr ""
+
+#: i2p2www/pages/site/docs/index.html:176
+msgid "SSU transport encryption"
+msgstr ""
+
+#: i2p2www/pages/site/docs/index.html:178
+msgid "Transport Javadoc"
+msgstr ""
+
+#: i2p2www/pages/site/docs/index.html:180
+msgid "NTCP Javadoc"
+msgstr ""
+
+#: i2p2www/pages/site/docs/index.html:182
+msgid "SSU Javadoc"
+msgstr ""
+
+#: i2p2www/pages/site/docs/index.html:185
+msgid "Other Router Topics"
+msgstr ""
+
+#: i2p2www/pages/site/docs/index.html:187
+msgid "Router software updates"
+msgstr ""
+
+#: i2p2www/pages/site/docs/index.html:191
+msgid "Native BigInteger Library"
+msgstr ""
+
+#: i2p2www/pages/site/docs/index.html:193
+msgid "Time synchronization and NTP"
+msgstr ""
+
+#: i2p2www/pages/site/docs/index.html:195
+msgid "Performance"
+msgstr ""
+
+#: i2p2www/pages/site/docs/index.html:202
+msgid "Developer's Guides and Resources"
+msgstr ""
+
+#: i2p2www/pages/site/docs/index.html:204
+msgid "New Developer's Guide"
+msgstr ""
+
+#: i2p2www/pages/site/docs/index.html:206
+msgid "New Translator's Guide"
+msgstr ""
+
+#: i2p2www/pages/site/docs/index.html:208
+msgid "Monotone Guide"
+msgstr ""
+
+#: i2p2www/pages/site/docs/index.html:210
+msgid "Developer Guidelines"
+msgstr ""
+
+#: i2p2www/pages/site/docs/index.html:212
+msgid "Javadocs on the standard internet:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/index.html:213
+#: i2p2www/pages/site/docs/index.html:219
+#: i2p2www/pages/site/docs/index.html:221
+#: i2p2www/pages/site/docs/index.html:223
+#, python-format
+msgid "Server %(num)s"
+msgstr ""
+
+#: i2p2www/pages/site/docs/index.html:214
+#: i2p2www/pages/site/docs/index.html:227
+msgid ""
+"Note: always verify that javadocs are current by checking the release "
+"number."
+msgstr ""
+
+#: i2p2www/pages/site/docs/index.html:216
+msgid "Javadocs inside I2P:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/index.html:229
+msgid "Proposals"
+msgstr ""
+
+#: i2p2www/pages/site/docs/index.html:233
+msgid "How to Set up a Reseed Server"
+msgstr ""
+
+#: i2p2www/pages/site/docs/index.html:235
+msgid "Ports used by I2P"
+msgstr ""
+
+#: i2p2www/pages/site/docs/index.html:237
+msgid "Automatic updates to development builds inside I2P"
+msgstr ""
+
+#: i2p2www/pages/site/docs/index.html:239
+msgid "Updating the wrapper manually"
+msgstr ""
+
+#: i2p2www/pages/site/docs/index.html:241
+msgid "User forum"
+msgstr ""
+
+#: i2p2www/pages/site/docs/index.html:243
+msgid "Developer forum inside I2P"
+msgstr ""
+
+#: i2p2www/pages/site/docs/index.html:245
+msgid "Bug tracker"
+msgstr ""
+
+#: i2p2www/pages/site/docs/index.html:248
+msgid "Viewmtn inside I2P"
+msgstr ""
+
+#: i2p2www/pages/site/docs/index.html:251
+msgid "I2P Source exported to GitHub"
+msgstr ""
+
+#: i2p2www/pages/site/docs/index.html:253
+msgid "I2P Source Git Repo inside I2P"
+msgstr ""
+
+#: i2p2www/pages/site/docs/index.html:255
+msgid "Source translation at Transifex"
+msgstr ""
+
+#: i2p2www/pages/site/docs/index.html:257
+msgid "Roadmap"
+msgstr ""
+
+#: i2p2www/pages/site/docs/index.html:259
+msgid "To Do List"
+msgstr ""
+
+#: i2p2www/pages/site/docs/index.html:259
+msgid "not current"
+msgstr ""
+
+#: i2p2www/pages/site/docs/naming.html:8
+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 <a href=\"#addressbook\">addressbook</a>. \n"
+"I2P also supports <a href=\"#base32\">Base32 hostnames</a> similar to "
+"Tor's .onion addresses."
+msgstr ""
+
+#: i2p2www/pages/site/docs/naming.html:15
+msgid ""
+"The addressbook is a web-of-trust\n"
+"driven secure, distributed, and human readable naming system, sacrificing"
+" only\n"
+"the call for all human readable names to be globally unique by mandating "
+"only\n"
+"local uniqueness.  While all messages in I2P are cryptographically "
+"addressed\n"
+"by their destination, different people can have local addressbook entries"
+" for\n"
+"\"Alice\" which refer to different destinations.  People can still "
+"discover new\n"
+"names by importing published addressbooks of peers specified in their web"
+" of trust,\n"
+"by adding in the entries provided through a third party, or (if some "
+"people organize\n"
+"a series of published addressbooks using a first come first serve "
+"registration\n"
+"system) people can choose to treat these addressbooks as name servers, "
+"emulating\n"
+"traditional DNS."
+msgstr ""
+
+#: i2p2www/pages/site/docs/naming.html:29
+#, python-format
+msgid ""
+"NOTE: For the reasoning behind the I2P naming system, common arguments "
+"against it\n"
+"and possible alternatives see the <a href=\"%(namingdiscussion)s\">naming"
+" discussion</a>\n"
+"page."
+msgstr ""
+
+#: i2p2www/pages/site/docs/naming.html:36
+msgid "Naming System Components"
+msgstr ""
+
+#: i2p2www/pages/site/docs/naming.html:38
+msgid ""
+"There is no central naming authority in I2P.\n"
+"All hostnames are local."
+msgstr ""
+
+#: i2p2www/pages/site/docs/naming.html:43
+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:51
+msgid ""
+"The local <a href=\"#lookup\">naming service</a> which does lookups\n"
+"and also handles <a href=\"#base32\">Base32 hostnames</a>."
+msgstr ""
+
+#: i2p2www/pages/site/docs/naming.html:55
+msgid ""
+"The <a href=\"#httpproxy\">HTTP proxy</a> which asks the router for "
+"lookups and points\n"
+"the user to remote jump services to assist with failed lookups."
+msgstr ""
+
+#: i2p2www/pages/site/docs/naming.html:59
+msgid ""
+"HTTP <a href=\"#add-services\">host-add forms</a> which allow users to "
+"add hosts to their local hosts.txt"
+msgstr ""
+
+#: i2p2www/pages/site/docs/naming.html:62
+msgid ""
+"HTTP <a href=\"#jump-services\">jump services</a> which provide their own"
+" lookups and redirection."
+msgstr ""
+
+#: i2p2www/pages/site/docs/naming.html:65
+msgid ""
+"The <a href=\"#addressbook\">addressbook</a> application which merges "
+"external\n"
+"host lists, retrieved via HTTP, with the local list."
+msgstr ""
+
+#: i2p2www/pages/site/docs/naming.html:69
+msgid ""
+"The <a href=\"#susidns\">SusiDNS</a> 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:76
+msgid "Naming Services"
+msgstr ""
+
+#: i2p2www/pages/site/docs/naming.html:78
+#, 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 3-or-more byte certificate, which in Base64 representation is 516 "
+"or more bytes.\n"
+"Non-null <a href=\"%(namingdiscussion)s#certificates\">Certificates</a> "
+"are in use now\n"
+"for signature type indication.\n"
+"Therefore, certificates in recently-generated destinations are more than "
+"3 bytes."
+msgstr ""
+
+#: i2p2www/pages/site/docs/naming.html:87
+msgid ""
+"If an application (i2ptunnel or the HTTP proxy) wishes to access\n"
+"a destination by name, the router does a very simple local lookup\n"
+"to resolve that name."
+msgstr ""
+
+#: i2p2www/pages/site/docs/naming.html:93
+msgid "Hosts.txt Naming Service"
+msgstr ""
+
+#: i2p2www/pages/site/docs/naming.html:95
+msgid ""
+"The hosts.txt Naming Service does a simple linear search through\n"
+"text files. This naming service was the default until\n"
+"release 0.8.8 when it was replaced by the Blockfile Naming Service.\n"
+"The hosts.txt format had become too slow after the file grew to thousands"
+" of entries."
+msgstr ""
+
+#: i2p2www/pages/site/docs/naming.html:102
+#, python-format
+msgid ""
+"It does a linear search through three local files, in order, to\n"
+"look up host names and convert them to a 516-byte destination key.\n"
+"Each file is in a simple <a href=\"%(configuration)s\">configuration file"
+" format</a>, with hostname=base64, one per line.\n"
+"The files are:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/naming.html:114
+msgid "Blockfile Naming Service"
+msgstr ""
+
+#: i2p2www/pages/site/docs/naming.html:116
+msgid ""
+"The Blockfile Naming Service stores multiple \"addressbooks\" in a single"
+"\n"
+"database file named hostsdb.blockfile.\n"
+"This Naming Service is the default since release 0.8.8."
+msgstr ""
+
+#: i2p2www/pages/site/docs/naming.html:122
+#, python-format
+msgid ""
+"A blockfile is simply on-disk storage of multiple sorted maps (key-value "
+"pairs),\n"
+"implemented as skiplists.\n"
+"The blockfile format is specified on the <a "
+"href=\"%(blockfile)s\">Blockfile page</a>.\n"
+"It provides fast Destination lookup in a compact format. While the "
+"blockfile overhead is substantial,\n"
+"the destinations are stored in binary rather than in Base 64 as in the "
+"hosts.txt format.\n"
+"In addition, the blockfile provides the capability of arbitrary metadata "
+"storage\n"
+"(such as added date, source, and comments) for each entry to implement "
+"advanced addressbook features.\n"
+"The blockfile storage requirement is a modest increase over the hosts.txt"
+" format, and the blockfile provides\n"
+"approximately 10x reduction in lookup times."
+msgstr ""
+
+#: i2p2www/pages/site/docs/naming.html:134
+msgid ""
+"On creation, the naming service imports entries from the three files used"
+" by the hosts.txt Naming Service.\n"
+"The blockfile mimics the previous implementation by maintaining three "
+"maps that\n"
+"are searched in-order, named privatehosts.txt, userhosts.txt, and "
+"hosts.txt.\n"
+"It also maintains a reverse-lookup map to implement rapid reverse lookups."
+msgstr ""
+
+#: i2p2www/pages/site/docs/naming.html:141
+msgid "Other Naming Service Facilities"
+msgstr ""
+
+#: i2p2www/pages/site/docs/naming.html:143
+#, python-format
+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.\n"
+"Lookups are cached for a few minutes.\n"
+"Base 32 resolution is <a href=\"#base32\">described below</a>.\n"
+"For a full description of the Naming Service API see the\n"
+"<a href=\"%(nsjavadocs)s\">Naming Service Javadocs</a>.\n"
+"This API was significantly expanded in release 0.8.7 to provide\n"
+"adds and removes, storage of arbitrary properties with the hostname,\n"
+"and other features."
+msgstr ""
+
+#: i2p2www/pages/site/docs/naming.html:156
+msgid "Alternatives and Experimental Naming Services"
+msgstr ""
+
+#: i2p2www/pages/site/docs/naming.html:158
+#, python-format
+msgid ""
+"The naming service is specified with the configuration property "
+"<tt>i2p.naming.impl=class</tt>.\n"
+"Other implementations are possible. For example,\n"
+"there is an experimental facility for real-time lookups (a la DNS) over "
+"the network within the router.\n"
+"For more information see the <a "
+"href=\"%(namingdiscussion)s#alternatives\">alternatives on the discussion"
+" page</a>."
+msgstr ""
+
+#: i2p2www/pages/site/docs/naming.html:165
+msgid ""
+"The HTTP proxy does a lookup via the router for all hostnames ending in "
+"'.i2p'.\n"
+"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:171
+#, python-format
+msgid ""
+"We have <a href=\"%(i2ptld)s\">applied to reserve the .i2p TLD</a>\n"
+"following the procedures specified in <a href=\"%(rfc6761)s\">RFC "
+"6761</a>."
+msgstr ""
+
+#: i2p2www/pages/site/docs/naming.html:177
+msgid ""
+"If the router fails to resolve the hostname, the HTTP proxy returns\n"
+"an error page to the user with links to several \"jump\" services.\n"
+"See below for details."
+msgstr ""
+
+#: i2p2www/pages/site/docs/naming.html:183
+msgid "Addressbook"
+msgstr "Adresár"
+
+#: i2p2www/pages/site/docs/naming.html:184
+msgid "Incoming Subscriptions and Merging"
+msgstr ""
+
+#: i2p2www/pages/site/docs/naming.html:186
+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:194
+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:202
+msgid ""
+"For this reason, the only subscription configured by\n"
+"default is <code>http://i2p-projekt.i2p/hosts.txt "
+"(http://udhdrtrcetjm5sxzskjyr5ztpeszydbh4dpl3pl4utgqqw2v4jna.b32.i2p/hosts.txt)</code>,"
+" \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 <a "
+"href=\"#susidns\">SusiDNS</a>)."
+msgstr ""
+
+#: i2p2www/pages/site/docs/naming.html:211
+msgid "Some other public addressbook subscription links:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/naming.html:218
+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:223
+#: i2p2www/pages/site/docs/naming.html:235
+msgid "Naming Rules"
+msgstr ""
+
+#: i2p2www/pages/site/docs/naming.html:224
+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:239
+msgid "Names are converted to lower case on import."
+msgstr ""
+
+#: i2p2www/pages/site/docs/naming.html:243
+msgid ""
+"Names are checked for conflict with existing names in the existing "
+"userhosts.txt and hosts.txt\n"
+"(but not privatehosts.txt) after conversion to lower case."
+msgstr ""
+
+#: i2p2www/pages/site/docs/naming.html:248
+msgid "Must contain only [a-z] [0-9] '.' and '-' after conversion to lower case."
+msgstr ""
+
+#: i2p2www/pages/site/docs/naming.html:252
+msgid "Must not start with '.' or '-'."
+msgstr ""
+
+#: i2p2www/pages/site/docs/naming.html:256
+msgid "Must end with '.i2p'."
+msgstr ""
+
+#: i2p2www/pages/site/docs/naming.html:260
+msgid "67 characters maximum, including the '.i2p'."
+msgstr ""
+
+#: i2p2www/pages/site/docs/naming.html:264
+msgid "Must not contain '..'."
+msgstr ""
+
+#: i2p2www/pages/site/docs/naming.html:268
+msgid "Must not contain '.-' or '-.' (as of 0.6.1.33)."
+msgstr ""
+
+#: i2p2www/pages/site/docs/naming.html:272
+msgid "Must not contain '--' except in 'xn--' for IDN."
+msgstr ""
+
+#: i2p2www/pages/site/docs/naming.html:276
+msgid ""
+"Base32 hostnames (*.b32.i2p) are reserved for base 32 use and so are not "
+"allowed to be imported."
+msgstr ""
+
+#: i2p2www/pages/site/docs/naming.html:280
+msgid ""
+"Certain hostnames reserved for project use are not allowed\n"
+"(proxy.i2p, router.i2p, console.i2p, *.proxy.i2p, *.router.i2p, "
+"*.console.i2p, and others)"
+msgstr ""
+
+#: i2p2www/pages/site/docs/naming.html:285
+msgid "Keys are checked for base64 validity."
+msgstr ""
+
+#: i2p2www/pages/site/docs/naming.html:289
+msgid ""
+"Keys are checked for conflict with existing keys in hosts.txt (but not "
+"privatehosts.txt)."
+msgstr ""
+
+#: i2p2www/pages/site/docs/naming.html:293
+msgid "Minimum key length 516 bytes."
+msgstr ""
+
+#: i2p2www/pages/site/docs/naming.html:297
+msgid "Maximum key length 616 bytes (to account for certs up to 100 bytes)."
+msgstr ""
+
+#: i2p2www/pages/site/docs/naming.html:302
+msgid ""
+"Any name received via subscription that passes all the checks is added "
+"via the local naming service."
+msgstr ""
+
+#: i2p2www/pages/site/docs/naming.html:306
+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:317
+msgid ""
+"International Domain Names (IDN) also work in i2p (using punycode 'xn--' "
+"form).\n"
+"To see IDN .i2p domain names rendered correctly in Firefox's location "
+"bar,\n"
+"add 'network.IDN.whitelist.i2p (boolean) = true' in about:config."
+msgstr ""
+
+#: i2p2www/pages/site/docs/naming.html:323
+msgid ""
+"As the addressbook application does not use privatehosts.txt at all, in "
+"practice\n"
+"this file is the only place where it is appropriate to place private "
+"aliases or\n"
+"\"pet names\" for sites already in hosts.txt."
+msgstr ""
+
+#: i2p2www/pages/site/docs/naming.html:329
+msgid "Advanced Subscription Feed Format"
+msgstr ""
+
+#: i2p2www/pages/site/docs/naming.html:337
+msgid "Outgoing Subscriptions"
+msgstr ""
+
+#: i2p2www/pages/site/docs/naming.html:338
+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:346
+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:353
+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:358
+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:367
+msgid "Host Add Services"
+msgstr ""
+
+#: i2p2www/pages/site/docs/naming.html:368
+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:375
+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:380
+msgid "A limit on number of 'subdomains'."
+msgstr ""
+
+#: i2p2www/pages/site/docs/naming.html:384
+msgid "Authorization for 'subdomains' through various methods."
+msgstr ""
+
+#: i2p2www/pages/site/docs/naming.html:388
+msgid "Hashcash or signed certificates."
+msgstr ""
+
+#: i2p2www/pages/site/docs/naming.html:392
+msgid "Editorial review of host names and/or content."
+msgstr ""
+
+#: i2p2www/pages/site/docs/naming.html:396
+msgid "Categorization of hosts by content."
+msgstr ""
+
+#: i2p2www/pages/site/docs/naming.html:400
+msgid "Reservation or rejection of certain host names."
+msgstr ""
+
+#: i2p2www/pages/site/docs/naming.html:404
+msgid "Restrictions on the number of names registered in a given time period."
+msgstr ""
+
+#: i2p2www/pages/site/docs/naming.html:408
+msgid "Delays between registration and publication."
+msgstr ""
+
+#: i2p2www/pages/site/docs/naming.html:412
+msgid "Requirement that the host be up for verification."
+msgstr ""
+
+#: i2p2www/pages/site/docs/naming.html:416
+msgid "Expiration and/or revocation."
+msgstr ""
+
+#: i2p2www/pages/site/docs/naming.html:420
+msgid "IDN spoof rejection."
+msgstr ""
+
+#: i2p2www/pages/site/docs/naming.html:425
+msgid "Jump Services"
+msgstr ""
+
+#: i2p2www/pages/site/docs/naming.html:426
+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 "
+"<code>?i2paddresshelper=key</code>\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:436
+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:442
+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:448
+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:454
+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:460
+msgid "Base32 Names"
+msgstr ""
+
+#: i2p2www/pages/site/docs/naming.html:461
+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: "
+"<code>ukeu3k5oycgaauneqgtnvselmt4yemvoilkln7jpvamvfx7dnkdq.b32.i2p</code>"
+msgstr ""
+
+#: i2p2www/pages/site/docs/naming.html:468
+#, python-format
+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"
+"Tor has recently published a\n"
+"<a href=\"https://blog.torproject.org/blog/tor-weekly-news-%E2%80%94"
+"-december-4th-2013\">proposal</a>\n"
+"to convert to an identical format of {52 chars}.onion for their hidden "
+"services.\n"
+"Base32 is implemented in the naming service, which queries the\n"
+"router over I2CP to lookup the LeaseSet to get the full Destination.\n"
+"Base32 lookups will only be successful when the Destination is up and "
+"publishing\n"
+"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:483
+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
+msgid "Plugins"
+msgstr ""
+
+#: i2p2www/pages/site/docs/plugins.html:3
+msgid "June 2012"
+msgstr ""
+
+#: i2p2www/pages/site/docs/plugins.html:6
+msgid "General Information"
+msgstr ""
+
+#: i2p2www/pages/site/docs/plugins.html:7
+msgid ""
+"I2P includes a plugin architecture\n"
+"to support easy development and installation of additional software."
+msgstr ""
+
+#: i2p2www/pages/site/docs/plugins.html:12
+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:17
+msgid "Benefits to i2p users and app developers:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/plugins.html:22
+msgid "Easy distribution of applications"
+msgstr ""
+
+#: i2p2www/pages/site/docs/plugins.html:26
+msgid ""
+"Allows innovation and use of additional libraries without worrying about\n"
+"increasing the size of <code>i2pupdate.sud</code>"
+msgstr ""
+
+#: i2p2www/pages/site/docs/plugins.html:31
+msgid ""
+"Support large or special-purpose applications that would never be bundled"
+"\n"
+"with the I2P installation"
+msgstr ""
+
+#: i2p2www/pages/site/docs/plugins.html:36
+msgid "Cryptographically signed and verified applications"
+msgstr ""
+
+#: i2p2www/pages/site/docs/plugins.html:40
+msgid "Automatic updates of applications, just like for the router"
+msgstr ""
+
+#: i2p2www/pages/site/docs/plugins.html:44
+msgid ""
+"Separate initial install and update packages, if desired, for smaller "
+"update downloads"
+msgstr ""
+
+#: i2p2www/pages/site/docs/plugins.html:48
+msgid ""
+"One-click installation of applications. No more asking users to modify\n"
+"<code>wrapper.config</code> or <code>clients.config</code>"
+msgstr ""
+
+#: i2p2www/pages/site/docs/plugins.html:53
+msgid "Isolate applications from the base <code>$I2P</code> installation"
+msgstr ""
+
+#: i2p2www/pages/site/docs/plugins.html:57
+msgid ""
+"Automatic compatibility checking for I2P version, Java version, Jetty\n"
+"version, and previous installed application version"
+msgstr ""
+
+#: i2p2www/pages/site/docs/plugins.html:62
+msgid "Automatic link addition in console"
+msgstr ""
+
+#: i2p2www/pages/site/docs/plugins.html:66
+msgid ""
+"Automatic startup of application, including modifying classpath, without "
+"requiring a restart"
+msgstr ""
+
+#: i2p2www/pages/site/docs/plugins.html:70
+msgid "Automatic integration and startup of webapps into console Jetty instance"
+msgstr ""
+
+#: i2p2www/pages/site/docs/plugins.html:74
+#, python-format
+msgid ""
+"Facilitate creation of 'app stores' like the one at\n"
+"<a href=\"http://%(pluginsite)s\">%(pluginsite)s</a>"
+msgstr ""
+
+#: i2p2www/pages/site/docs/plugins.html:79
+msgid "One-click uninstall"
+msgstr ""
+
+#: i2p2www/pages/site/docs/plugins.html:83
+msgid "Language and theme packs for the console"
+msgstr ""
+
+#: i2p2www/pages/site/docs/plugins.html:87
+msgid "Bring detailed application information to the router console"
+msgstr ""
+
+#: i2p2www/pages/site/docs/plugins.html:91
+msgid "Non-java applications also supported"
+msgstr ""
+
+#: i2p2www/pages/site/docs/plugins.html:97
+msgid "Required I2P version"
+msgstr ""
+
+#: i2p2www/pages/site/docs/plugins.html:98
+msgid "0.7.12 or newer."
+msgstr ""
+
+#: i2p2www/pages/site/docs/plugins.html:100
+msgid "Installation"
+msgstr ""
+
+#: i2p2www/pages/site/docs/plugins.html:101
+msgid ""
+"To install and start a plugin, copy the <code>.xpi2p</code> install link "
+"to\n"
+"the form at the bottom of\n"
+"<a "
+"href=\"http://127.0.0.1:7657/configclients.jsp#plugin\">configclients.jsp"
+" in\n"
+"your router console</a> and click the \"install plugin\" button.  After a"
+"\n"
+"plugin is installed and started, a link to the plugin will usually appear"
+" at\n"
+"the top of your summary bar."
+msgstr ""
+
+#: i2p2www/pages/site/docs/plugins.html:110
+msgid ""
+"To update a plugin to the latest version, just click the update button on"
+"\n"
+"<a "
+"href=\"http://127.0.0.1:7657/configclients.jsp#plugin\">configclients.jsp</a>."
+"\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:120
+msgid "Development"
+msgstr ""
+
+#: i2p2www/pages/site/docs/plugins.html:121
+#, python-format
+msgid ""
+"See the latest <a href=\"%(pluginspec)s\">plugin specification</a> and "
+"the\n"
+"<a href=\"http://%(zzz)s/forums/16\">plugin forum</a> on %(zzz)s."
+msgstr ""
+
+#: i2p2www/pages/site/docs/plugins.html:126
+#, python-format
+msgid ""
+"See also the sources for plugins developed by various people.  Some "
+"plugins, such\n"
+"as <a href=\"http://%(pluginsite)s/plugins/snowman\">snowman</a>, were "
+"developed\n"
+"specifically as examples."
+msgstr ""
+
+#: i2p2www/pages/site/docs/plugins.html:132
+msgid ""
+"<b>Developers wanted!</b> Plugins are a great way to learn more about I2P"
+"\n"
+"or easily add some feature."
+msgstr ""
+
+#: i2p2www/pages/site/docs/plugins.html:137
+msgid "Getting Started"
+msgstr ""
+
+#: i2p2www/pages/site/docs/plugins.html:138
+#, python-format
+msgid ""
+"To create a plugin from an existing binary package you will need to get\n"
+"makeplugin.sh from <a href=\"%(url)s\">the i2p.scripts branch in "
+"monotone</a>."
+msgstr ""
+
+#: i2p2www/pages/site/docs/plugins.html:144
+msgid "Known Issues"
+msgstr ""
+
+#: i2p2www/pages/site/docs/plugins.html:145
+msgid ""
+"Note that the router's plugin architecture does <b>NOT</b> currently\n"
+"provide any additional security isolation or sandboxing of plugins."
+msgstr ""
+
+#: i2p2www/pages/site/docs/plugins.html:151
+msgid ""
+"Updates of a plugin with included jars (not wars) won't be recognized if\n"
+"the plugin was already run, as it requires class loader trickery to flush"
+" the\n"
+"class cache; a full router restart is required."
+msgstr ""
+
+#: i2p2www/pages/site/docs/plugins.html:157
+msgid "The stop button may be displayed even if there is nothing to stop."
+msgstr ""
+
+#: i2p2www/pages/site/docs/plugins.html:161
+msgid ""
+"Plugins running in a separate JVM create a <code>logs/</code> directory "
+"in\n"
+"<code>$CWD</code>."
+msgstr ""
+
+#: i2p2www/pages/site/docs/plugins.html:166
+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&mdash;there is no signing key authority."
+msgstr ""
+
+#: i2p2www/pages/site/docs/plugins.html:172
+msgid ""
+"When deleting a plugin, the directory is not always deleted, especially "
+"on\n"
+"Windows."
+msgstr ""
+
+#: i2p2www/pages/site/docs/plugins.html:177
+msgid ""
+"Installing a plugin requiring Java 1.6 on a Java 1.5 machine will result "
+"in a\n"
+"\"plugin is corrupt\" message if pack200 compression of the plugin file "
+"is used."
+msgstr ""
+
+#: i2p2www/pages/site/docs/plugins.html:182
+msgid "Theme and translation plugins are untested."
+msgstr ""
+
+#: i2p2www/pages/site/docs/plugins.html:186
+msgid "Disabling autostart doesn't always work."
+msgstr ""
+
+#: i2p2www/pages/site/docs/ports.html:2
+msgid "Ports Used by I2P"
+msgstr ""
+
+#: i2p2www/pages/site/docs/ports.html:3
+msgid "March 2018"
+msgstr ""
+
+#: 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 <a href=\"%(faq)s#ports\">the FAQ</a>.\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:56
+msgid "recommended spot for new plugins/applications"
+msgstr ""
+
+#: i2p2www/pages/site/docs/reseed.html:2
+msgid "Reseed Hosts"
+msgstr ""
+
+#: i2p2www/pages/site/docs/reseed.html:3
+#: i2p2www/pages/site/docs/how/elgamal-aes.html:3
+msgid "January 2016"
+msgstr ""
+
+#: i2p2www/pages/site/docs/reseed.html:8
+msgid "About Reseed hosts"
+msgstr ""
+
+#: i2p2www/pages/site/docs/reseed.html:10
+msgid ""
+"Reseed hosts are needed to for bootstrapping, that is, providing the "
+"initial set of I2P nodes for your I2P node to talk to. Depending on the "
+"status of your node it may need to bootstrap every now and then if many "
+"of the nodes it knows of aren't contactable."
+msgstr ""
+
+#: i2p2www/pages/site/docs/reseed.html:14
+msgid ""
+"Reseeding is done over an encrypted connection and all of the bootstrap "
+"information is signed by the reseed host you connect to, making it "
+"impossible for an unauthenticated source to provide you with false "
+"information."
+msgstr ""
+
+#: i2p2www/pages/site/docs/reseed.html:19
+msgid "Running a Reseed host"
+msgstr ""
+
+#: i2p2www/pages/site/docs/reseed.html:21
+msgid ""
+"The more reseed hosts that are run, the more resilient the I2P network "
+"becomes, and the harder it is to prevent users of I2P from connecting to "
+"the network."
+msgstr ""
+
+#: i2p2www/pages/site/docs/reseed.html:25
+msgid ""
+"There have also been cases where the reseed hosts we had, have been under"
+" heavy load due to botnet activities."
+msgstr ""
+
+#: i2p2www/pages/site/docs/reseed.html:33
+msgid "Thank you"
+msgstr ""
+
+#: i2p2www/pages/site/docs/reseed.html:35
+msgid ""
+"If you are running a reseed server, We would like to thank you for "
+"helping to\n"
+"make the I2P network stronger and more resilient than ever."
+msgstr ""
+
+#: i2p2www/pages/site/docs/reseed.html:41
+msgid "Thank you."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/bob.html:2
+msgid "BOB - Basic Open Bridge"
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/bob.html:3
+msgid "August 2016"
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/bob.html:12
+msgid "Technical differences from SAM (for the better?)"
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/bob.html:14
+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:23
+msgid ""
+"SAM has one connection that does everything, and you need to parse every "
+"packet."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/bob.html:27
+msgid ""
+"BOB does not hold keypair values, nor does the router.\n"
+"Your application holds the keypair values. \n"
+"This is to reduce any extra complexity in the router code, it also adds "
+"to\n"
+"your privacy."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/bob.html:34
+msgid "SAM router stores every keypair you ever make."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/bob.html:38
+msgid "Those are the important differences."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/bob.html:44
+msgid "<code>KEYS</code> = keypair public+private, these are BASE64"
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/bob.html:47
+msgid "<code>KEY</code> = public key, also BASE64"
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/bob.html:50
+msgid ""
+"<code>ERROR</code> as is implied returns the message <code>\"ERROR "
+"\"+DESCRIPTION+\"\\n\"</code>, where the <code>DESCRIPTION</code> is what"
+" went wrong."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/bob.html:53
+msgid ""
+"<code>OK</code> returns <code>\"OK\"</code>, and if data is to be "
+"returned, it is on the same line. <code>OK</code> means the command is "
+"finished."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/bob.html:56
+msgid ""
+"<code>DATA</code> lines contain information that you requested. There may"
+" be multiple <code>DATA</code> lines per request."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/bob.html:60
+msgid ""
+"<b>NOTE:</b> 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:66
+msgid "Connection and Version"
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/bob.html:68
+msgid ""
+"All BOB status output is by lines. Lines may be \\n or \\r\\n terminated,"
+" depending on the system.\n"
+"On connection, BOB outputs two lines:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/bob.html:78
+msgid "The current version is:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/bob.html:82
+msgid ""
+"Note that previous versions used upper-case hex digits and did not "
+"conform to I2P versioning standards.\n"
+"It is recommended that subsequent versions use digits 0-9 only."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/bob.html:87
+msgid "Version history"
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/bob.html:92
+msgid "Version"
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/bob.html:93
+msgid "I2P Router Version"
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/bob.html:94
+msgid "Changes"
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/bob.html:97
+msgid "current version"
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/bob.html:100
+msgid "development versions"
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/bob.html:104
+msgid "Commands"
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/bob.html:106
+msgid ""
+"<b>PLEASE NOTE:</b>\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:112
+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:117
+msgid "COMMAND"
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/bob.html:117
+msgid "OPERAND"
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/bob.html:117
+msgid "RETURNS"
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/bob.html:145
+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:152
+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:164
+msgid "Examples"
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/bob.html:166
+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:174
+msgid "EXAMPLE SESSION DIALOGUE -- simple telnet 127.0.0.1 2827 works"
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/bob.html:175
+msgid "Application"
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/bob.html:176
+msgid "BOB's Command response."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/bob.html:178
+#: i2p2www/pages/site/docs/api/bob.html:192
+#: i2p2www/pages/site/docs/api/bob.html:212
+#: i2p2www/pages/site/docs/api/bob.html:322
+#: i2p2www/pages/site/docs/api/bob.html:334
+#: i2p2www/pages/site/docs/api/bob.html:349
+msgid "FROM"
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/bob.html:178
+#: i2p2www/pages/site/docs/api/bob.html:192
+#: i2p2www/pages/site/docs/api/bob.html:212
+#: i2p2www/pages/site/docs/api/bob.html:322
+#: i2p2www/pages/site/docs/api/bob.html:334
+#: i2p2www/pages/site/docs/api/bob.html:349
+msgid "TO"
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/bob.html:178
+#: i2p2www/pages/site/docs/api/bob.html:192
+#: i2p2www/pages/site/docs/api/bob.html:212
+#: i2p2www/pages/site/docs/api/bob.html:322
+#: i2p2www/pages/site/docs/api/bob.html:334
+#: i2p2www/pages/site/docs/api/bob.html:349
+msgid "DIALOGUE"
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/bob.html:187
+msgid "MAKE NOTE OF THE ABOVE DESTINATION KEY, YOURS WILL BE DIFFERENT!"
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/bob.html:201
+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 <code>CHARGEN</code> service on <code>19/TCP</code>."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/bob.html:207
+msgid "Now for the other half, so that we can actually contact this destination."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/bob.html:229
+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:236
+msgid ""
+"<b>NOTE:</b> The \"quit\" command in the command channel does NOT "
+"disconnect the tunnels like SAM."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/bob.html:253
+msgid "After a few virtual miles of this spew, press <code>Control-]</code>"
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/bob.html:265
+msgid "Here is what happened..."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/bob.html:273
+msgid "You can connect to EEPSITES too!"
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/bob.html:306
+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:313
+msgid "Let's put down our destinations now that we are all done with them."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/bob.html:317
+msgid "First, lets see what destination nicknames we have."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/bob.html:329
+msgid "Alright, there they are. First, let's remove \"mouth\"."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/bob.html:343
+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:362
+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:368
+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:375
+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:384
+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:3
+#: i2p2www/pages/site/docs/protocol/index.html:3
+msgid "August 2010"
+msgstr ""
+
+#: 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 <a href=\"%(i2cp)s\">I2CP</a> 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 <a href=\"%(streaming)s\">streaming library packets</a>,\n"
+"are an application-level construct.\n"
+"These protocols are independent of the low-level <a "
+"href=\"%(transports)s\">transports</a>;\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 ""
+
+#: i2p2www/pages/site/docs/api/datagrams.html:26
+#, python-format
+msgid ""
+"Applications written in Java may use the \n"
+"<a href=\"%(url)s\">datagram API</a>,\n"
+"while applications in other languages \n"
+"can use <a href=\"%(sam)s\">SAM</a>'s datagram support.\n"
+"There is also limited support in i2ptunnel in the <a "
+"href=\"%(socks)s\">SOCKS proxy</a>,\n"
+"the 'streamr' tunnel types, and udpTunnel classes."
+msgstr ""
+
+#: 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 ""
+
+#: 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"
+"<a href=\"%(elgamalaes)s\">ElGamal/AES</a>, 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 <a href=\"%(i2cp)s#format\">I2CP page</a>."
+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"
+"<a href=\"%(i2psession)s\">I2PSession API</a>\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"
+"<a href=\"%(i2psession)s\">I2PSession API</a>,\n"
+"as implemented in\n"
+"<a href=\"%(i2psessionmuxed)s\">I2PSessionMuxedImpl</a>."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/datagrams.html:93
+#: i2p2www/pages/site/docs/api/streaming.html:418
+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"
+"<a href=\"%(i2cp)s#format\">the I2CP layer</a>.\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:426
+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"
+"<a href=\"%(garlicrouting)s\">Garlic Message</a>).\n"
+"Message encapsulation is implemented in the underlying\n"
+"<a href=\"%(i2cp)s\">I2CP</a>,\n"
+"<a href=\"%(i2np)s\">I2NP</a>, and\n"
+"<a href=\"%(tunnelmessage)s\">tunnel message</a> 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/transport/ssu.html:650
+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:2
+msgid "I2PControl - Remote Control Service"
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:5
+#, python-format
+msgid ""
+"I2P enables a <a href=\"http://en.wikipedia.org/wiki/JSON-"
+"RPC\">JSONRPC2</a> interface via the plugin <a "
+"href=\"%(itoopie)s\">I2PControl</a>.\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 <a href=\"http://software.dzhuvinov.com"
+"/json-rpc-2.0.html\">JSON-RPC 2.0</a>.  \n"
+"A list of implementations of JSON-RPC for various languages can be found "
+"at <a href=\"http://json-rpc.org/wiki/implementations\">the JSON-RPC "
+"wiki</a>."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:12
+msgid "I2PControl is by default listening on https://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:20
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:45
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:58
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:68
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:77
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:87
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:102
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:155
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:176
+msgid "Request:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:33
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:50
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:62
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:72
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:82
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:93
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:119
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:165
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:191
+msgid "Response:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:44
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:46
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:47
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:51
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:52
+#: i2p2www/pages/site/docs/protocol/i2cp.html:108
+#: i2p2www/pages/site/docs/protocol/i2cp.html:483
+msgid "Description"
+msgstr "Popis"
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:48
+msgid ""
+"Token used for authenticating every request (excluding the 'Authenticate'"
+" RPC method)"
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:56
+msgid "Implemented methods"
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:57
+msgid ""
+"Creates and returns an authentication token used for further "
+"communication."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:59
+msgid "The version of the I2PControl API used by the client."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:60
+msgid "The password used for authenticating against the remote server."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:63
+msgid "The primary I2PControl API version implemented by the server."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:64
+msgid "The token used for further communication."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:67
+msgid "Echoes the value of the echo key, used for debugging and testing."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:69
+msgid "Value will be returned in response."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:70
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:80
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:91
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:117
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:163
+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:73
+msgid "Value of the key 'echo' in the request."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:76
+msgid ""
+"Fetches rateStat from router statManager. Creates stat if not already "
+"created."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:78
+#, python-format
+msgid ""
+"Determines which rateStat to fetch, see <a "
+"href=\"%(ratestats)s\">ratestats</a>."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:79
+msgid "Determines which period a stat is fetched for. Measured in ms."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:83
+msgid "Returns the average value for the reuested rateStat and period."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:86
+msgid "Manages I2PControl. Ports, passwords and the like."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:88
+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:89
+msgid ""
+"Sets a new password for I2PControl, all Authentication tokens will be "
+"revoked."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:90
+msgid "Switches which port I2PControl will listen for connections on."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:94
+msgid "Returned if address was changed"
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:95
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:96
+msgid "Returned if setting was changed"
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:97
+msgid "Returns true if any changes were made."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:98
+msgid "Returns true if any changes requiring a restart to take effect were made."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:101
+msgid "Fetches basic information about the I2P router. Uptime, version etc."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:120
+msgid "What the status of the router is."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:121
+msgid "What the uptime of the router is in ms."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:122
+msgid "What version of I2P the router is running."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:123
+msgid "The 1 second average inbound bandwidth in Bps."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:124
+msgid "The 15 second average inbound bandwidth in Bps."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:125
+msgid "The 1 second average outbound bandwidth in Bps."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:126
+msgid "The 15 second average outbound bandwidth in Bps."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:127
+msgid "What the current network status is. According to the below enum:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:146
+msgid "How many tunnels on the I2P net are we participating in."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:147
+msgid "How many peers have we communicated with recently."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:148
+msgid "How many peers are considered 'fast'."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:149
+msgid "How many peers are considered 'high capacity'."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:150
+msgid "Is the router reseeding hosts to its NetDB?"
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:151
+msgid "How many peers are known to us (listed in our NetDB)."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:154
+msgid "Manages I2P router restart/shutdown."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:156
+msgid "<b>Blocking</b>. Initiates a search for signed updates."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:157
+msgid ""
+"Initiates a router reseed, fetching peers into our NetDB from a remote "
+"host."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:158
+msgid "Restarts the router."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:159
+msgid ""
+"Restarts the router gracefully (waits for participating tunnels to "
+"expire)."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:160
+msgid "Shuts down the router."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:161
+msgid ""
+"Shuts down the router gracefully (waits for participating tunnels to "
+"expire)."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:162
+msgid "Initiates a router update from signed sources."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:166
+msgid "<b>Blocking</b>. Returns true iff a signed update has been found."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:167
+msgid "If requested, verifies that a reseed has been initiated."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:168
+msgid "If requested, verifies that a restart has been initiated."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:169
+msgid "If requested, verifies that a graceful restart has been initiated."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:170
+msgid "If requested, verifies that a shutdown has been initiated"
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:171
+msgid "If requested, verifies that a graceful shutdown has been initiated"
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:172
+msgid "<b>Blocking</b>. If requested, returns the status of the the update"
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:175
+msgid "Fetches or sets various network related settings. Ports, addresses etc."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:177
+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:178
+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:179
+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:180
+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:181
+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:182
+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:183
+msgid "What ip has been detected by the UDP transport."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:184
+msgid "Is UPnP enabled. If null is submitted, current setting will be returned."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:185
+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:186
+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:187
+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:188
+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:189
+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:192
+msgid "If requested, returns the port used for the TCP transport."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:193
+msgid "If requested, returns the hostname used for the TCP transport."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:194
+msgid ""
+"If requested, returns the method used for automatically detecting ip for "
+"the TCP transport."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:195
+msgid "If requested, returns the port used for the UDP transport."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:196
+msgid "If requested, returns the hostname used for the UDP transport."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:197
+msgid ""
+"If requested, returns methods used for detecting the ip address of the "
+"UDP transport."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:198
+msgid "If requested, returns what ip has been detected by the UDP transport."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:199
+msgid "If requested, returns the UPNP setting."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:200
+msgid ""
+"If requested, returns how many percent of bandwidth is usable for "
+"participating tunnels."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:201
+msgid "If requested, returns how many KB/s of inbound bandwidth is allowed."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:202
+msgid "If requested, returns how many KB/s of outbound bandwidth is allowed."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:203
+msgid "If requested, returns the laptop mode."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:204
+msgid "Have the provided settings been saved."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:205
+msgid "Is a restart needed for the new settings to be used."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:208
+msgid "Allows for manipulation of advanced i2p settings"
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:209
+msgid "Set:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:209
+msgid "Set the sent key-value pairs"
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:212
+msgid "SetAll:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:212
+msgid "Set the sent key-value pairs, remove everything else"
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:215
+msgid "Get:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:215
+msgid "Get the key-value pairs for the sent keys"
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:218
+msgid "GetAll:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:218
+msgid "Get all the key-value pairs"
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:221
+msgid "denotes an optional value."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:222
+msgid "denotes a possibly occuring return value"
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:224
+msgid "Error codes"
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:225
+msgid "Standard JSON-RPC2 error codes."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:226
+msgid "JSON parse error."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:227
+msgid "Invalid request."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:228
+msgid "Method not found."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:229
+msgid "Invalid parameters."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:230
+msgid "Internal error."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:232
+msgid "I2PControl specific error codes."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:233
+msgid "Invalid password provided."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:234
+msgid "No authentication token presented."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:235
+msgid "Authentication token doesn't exist."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:236
+msgid "The provided authentication token was expired and will be removed."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2pcontrol.html:237
+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:238
+msgid ""
+"The version of the I2PControl API specified is not supported by "
+"I2PControl."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2ptunnel.html:8
+#, 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 <a "
+"href=\"%(naming)s\">hostname</a>,\n"
+"<a href=\"%(naming)s#base32\">Base32</a>, 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"
+"<a "
+"href=\"http://localhost:7657/i2ptunnel/\">localhost:7657/i2ptunnel/</a>."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2ptunnel.html:20
+msgid "Default Services"
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2ptunnel.html:21
+msgid "Server tunnels"
+msgstr "Serverové tunely"
+
+#: i2p2www/pages/site/docs/api/i2ptunnel.html:23
+msgid ""
+"<b>I2P Webserver</b> - A tunnel pointed to a Jetty webserver run\n"
+"on <a href=\"http://localhost:7658\">localhost:7658</a> for convenient "
+"and quick hosting on I2P.\n"
+"<br>The document root is:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2ptunnel.html:31
+msgid "Client tunnels"
+msgstr "Klientské tunely"
+
+#: i2p2www/pages/site/docs/api/i2ptunnel.html:33
+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:37
+msgid "An IRC tunnel to the default anonymous IRC network, Irc2P."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2ptunnel.html:38
+#, python-format
+msgid ""
+"The anonymous <a href=\"%(monotone)s\">monotone</a>\n"
+"sourcecode repository for I2P"
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2ptunnel.html:42
+#, python-format
+msgid ""
+"A SMTP service provided by postman at <a "
+"href=\"http://%(postman)s/?page_id=16\">%(postman)s</a>"
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2ptunnel.html:45
+#, python-format
+msgid ""
+"The accompanying POP sevice of postman at <a "
+"href=\"http://%(postman)s/?page_id=16\">%(postman)s</a>"
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2ptunnel.html:50
+msgid "Configuration"
+msgstr "Konfigurácia"
+
+#: i2p2www/pages/site/docs/api/i2ptunnel.html:54
+msgid "Client Modes"
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2ptunnel.html:55
+#: i2p2www/pages/site/docs/api/i2ptunnel.html:165
+msgid "Standard"
+msgstr "Štandardné"
+
+#: i2p2www/pages/site/docs/api/i2ptunnel.html:56
+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:62
+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:67
+msgid ""
+"<b>Accept, Accept-Charset, Accept-Language\n"
+" and Accept-Ranges</b> as they vary greatly between browsers and can be "
+"used as an identifier."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2ptunnel.html:90
+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:94
+msgid "Outproxy:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2ptunnel.html:95
+msgid "Internal I2P use:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2ptunnel.html:100
+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:105
+msgid "Whitelist:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2ptunnel.html:139
+msgid "Enables using the I2P router as a SOCKS proxy."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2ptunnel.html:144
+msgid ""
+"Enables using the I2P router as a SOCKS proxy with the command whitelist "
+"specified by\n"
+"<a href=\"#client-mode-irc\">IRC</a> client mode."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2ptunnel.html:150
+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:156
+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:164
+msgid "Server Modes"
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2ptunnel.html:166
+msgid "Creates a destination to a local ip:port with an open TCP port."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/i2ptunnel.html:171
+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:177
+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:184
+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:190
+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\" <a href=\"%(streaming)s\">streaming library</a>.\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 <a href=\"%(api)s\">API documentation</a> 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"
+"<a href=\"%(i2cp)s\">I2CP</a> 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"
+"<a href=\"%(i2ptunnel)s\">I2PTunnel</a> 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 <a href=\"%(minwww)s\">significant</a>.  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 <a href=\"%(api)s\">API</a>\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"
+"<a href=\"%(samv3)s\">SAM</a>'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 <a href=\"%(faq)s#socks\">FAQ</a>:"
+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/network-database.html:183
+#: 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 <a href=\"%(meeting81)s\">Meeting 81</a> and\n"
+"<a href=\"%(meeting82)s\">Meeting 82</a> 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
+msgid "July 2018"
+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"
+"<a href=\"%(datagrams)s\">datagram library</a>."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/streaming.html:18
+#, python-format
+msgid ""
+"The streaming library is a layer on top of the core \n"
+"<a href=\"%(i2cp)s\">I2CP API</a> 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 <a href=\"%(i2cp)s\">I2CP</a> API is completely hidden, "
+"except that\n"
+"applications may pass <a href=\"%(i2cp)s#options\">I2CP parameters</a> "
+"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"
+"<a href=\"%(i2psktmf)s\">I2PSocketManagerFactory</a> to create an\n"
+"<a href=\"%(i2psktm)s\">I2PSocketManager</a>. The application then asks "
+"the\n"
+"socket manager for an <a href=\"%(i2psess)s\">I2PSession</a>, which will "
+"cause\n"
+"a connection to the router via <a href=\"%(i2cp)s\">I2CP</a>. The "
+"application\n"
+"can then setup connections with an <a href=\"%(i2pskt)s\">I2PSocket</a> "
+"or\n"
+"receive connections with an <a href=\"%(i2psskt)s\">I2PServerSocket</a>."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/streaming.html:82
+#, python-format
+msgid "Here are the <a href=\"%(url)s\">full streaming library Javadocs</a>."
+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"
+"<a "
+"href=\"%(i2psktmf)s\">I2PSocketManagerFactory</a>.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 <a href=\"%(samv3)s\">SAM</a>,\n"
+"<a href=\"%(bob)s\">BOB</a>, and <a href=\"%(i2ptunnel)s\">I2PTunnel</a>,"
+"\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:103
+#: i2p2www/pages/site/docs/protocol/i2cp.html:478
+msgid "Option"
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/streaming.html:117
+#: i2p2www/pages/site/docs/protocol/i2cp.html:107
+#: i2p2www/pages/site/docs/protocol/i2cp.html:482
+msgid "Default"
+msgstr "Predvolené"
+
+#: i2p2www/pages/site/docs/api/streaming.html:117
+#: i2p2www/pages/site/docs/how/elgamal-aes.html:264
+#: i2p2www/pages/site/docs/how/peer-selection.html:282
+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:129
+#: i2p2www/pages/site/docs/api/streaming.html:135
+#: i2p2www/pages/site/docs/api/streaming.html:141
+#: i2p2www/pages/site/docs/api/streaming.html:148
+#: i2p2www/pages/site/docs/api/streaming.html:160
+#: i2p2www/pages/site/docs/api/streaming.html:171
+#: i2p2www/pages/site/docs/api/streaming.html:200
+#: i2p2www/pages/site/docs/api/streaming.html:212
+#: i2p2www/pages/site/docs/api/streaming.html:220
+#: i2p2www/pages/site/docs/api/streaming.html:245
+#: i2p2www/pages/site/docs/api/streaming.html:262
+#: i2p2www/pages/site/docs/api/streaming.html:275
+#: i2p2www/pages/site/docs/api/streaming.html:286
+#: i2p2www/pages/site/docs/api/streaming.html:292
+#: i2p2www/pages/site/docs/api/streaming.html:298
+#: i2p2www/pages/site/docs/api/streaming.html:312
+#: i2p2www/pages/site/docs/api/streaming.html:319
+#: i2p2www/pages/site/docs/api/streaming.html:326
+#: i2p2www/pages/site/docs/api/streaming.html:351
+#: i2p2www/pages/site/docs/api/streaming.html:358
+#: i2p2www/pages/site/docs/api/streaming.html:365
+#, python-format
+msgid "As of release %(release)s."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/streaming.html:125
+#: i2p2www/pages/site/docs/api/streaming.html:133
+msgid "Use the access list as a whitelist for incoming connections."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/streaming.html:127
+msgid "The name or number of the signature type for a transient destination."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/streaming.html:139
+msgid "Use the access list as a blacklist for incoming connections."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/streaming.html:153
+msgid "Whether to respond to incoming pings"
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/streaming.html:165
+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:175
+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:179
+msgid ""
+"When we're in congestion avoidance, we grow the window size at the rate\n"
+"of <code>1/(windowSize*factor)</code>.  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:186
+msgid ""
+"How long to wait after instantiating a new con \n"
+"before actually attempting to connect.  If this is\n"
+"&lt;= 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:194
+msgid ""
+"How long to block on connect, in milliseconds. Negative means "
+"indefinitely. Default is 5 minutes."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/streaming.html:198
+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:204
+msgid ""
+"Comma- or space-separated list of Base64 peer Hashes or host names to be\n"
+"contacted using an alternate DSA destination.\n"
+"Only applies if multisession is enabled and the primary session is non-"
+"DSA\n"
+"(generally for shared clients only).\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:216
+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:226
+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:232
+msgid "Idle time before sending a keepalive"
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/streaming.html:235
+msgid "Delay before sending an ack"
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/streaming.html:237
+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:242
+msgid ""
+"Initial timeout\n"
+"(if no <a href=\"#sharing\">sharing data</a> available)."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/streaming.html:249
+msgid ""
+"Initial round trip time estimate\n"
+"(if no <a href=\"#sharing\">sharing data</a> available).\n"
+"Disabled as of release 0.9.8; uses actual RTT."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/streaming.html:255
+msgid "if no <a href=\"#sharing\">sharing data</a> available"
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/streaming.html:255
+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:279
+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:284
+msgid "Incoming connection limit (per peer; 0 means disabled)"
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/streaming.html:290
+#: i2p2www/pages/site/docs/api/streaming.html:296
+msgid "(per peer; 0 means disabled)"
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/streaming.html:302
+msgid "The MTU in bytes."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/streaming.html:306
+msgid "Maximum number of retransmissions before failure."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/streaming.html:310
+msgid "Incoming connection limit (all peers; 0 means disabled)"
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/streaming.html:316
+#: i2p2www/pages/site/docs/api/streaming.html:323
+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:332
+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:337
+msgid "How long to block on read, in milliseconds. Negative means indefinitely."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/streaming.html:341
+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:348
+#: i2p2www/pages/site/docs/api/streaming.html:355
+#: i2p2www/pages/site/docs/api/streaming.html:362
+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:369
+msgid ""
+"How long to block on write/flush, in milliseconds. Negative means "
+"indefinitely."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/streaming.html:377
+msgid "Protocol Specification"
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/streaming.html:379
+msgid "See the Streaming Library Specification page."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/streaming.html:383
+msgid "Implementation Details"
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/streaming.html:385
+msgid "Setup"
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/streaming.html:386
+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:391
+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:398
+msgid "MTU Selection and Negotiation"
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/streaming.html:399
+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:408
+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:419
+#, python-format
+msgid ""
+"Data integrity is assured by the gzip CRC-32 checksum implemented in\n"
+"<a href=\"%(i2cp)s#format\">the I2CP layer</a>.\n"
+"There is no checksum field in the streaming protocol."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/streaming.html:427
+#, python-format
+msgid ""
+"Each packet is sent through I2P as a single message (or as an individual "
+"clove in a\n"
+"<a href=\"%(garlicrouting)s\">Garlic Message</a>). Message encapsulation "
+"is implemented\n"
+"in the underlying <a href=\"%(i2cp)s\">I2CP</a>, <a "
+"href=\"%(i2np)s\">I2NP</a>, and\n"
+"<a href=\"%(tunnelmessage)s\">tunnel message</a> layers. There is no "
+"packet delimiter\n"
+"mechanism or payload length field in the streaming protocol."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/streaming.html:437
+msgid "Optional Delay"
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/streaming.html:438
+msgid ""
+"Data packets may include an optional delay field specifying the requested"
+" delay,\n"
+"in ms, before the receiver should ack the packet.\n"
+"Valid values are 0 to 60000 inclusive.\n"
+"A value of 0 requests an immediate ack.\n"
+"This is advisory only, and receivers should delay slightly so that\n"
+"additional packets may be acknowledged with a single ack.\n"
+"Some implementations may include an advisory value of (measured RTT / 2) "
+"in this field.\n"
+"For nonzero optional delay values, receivers should limit the maximum "
+"delay\n"
+"before sending an ack to a few seconds at most.\n"
+"Optional delay values greater than 60000 indicate choking, see below."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/streaming.html:452
+msgid "Receive Window and Choking"
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/streaming.html:453
+msgid ""
+"TCP headers include the receive window in bytes.\n"
+"The streaming protocol does not contain a receive window, it uses only a "
+"simple choke/unchoke indication.\n"
+"Each endpoint must maintain its own estimate of the far-end receive "
+"window, in either bytes or packets.\n"
+"The recommended minimum buffer size for receiver implementations is 128 "
+"packets or 217 KB (approximately 128x1730).\n"
+"Because of I2P netowrk latency, packet drops, and the resulting "
+"congestion control,\n"
+"a buffer of this size is rarely filled.\n"
+"Overflow is, however, likely to occur on high-bandwidth \"local "
+"loopback\" (same-router) connections."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/streaming.html:462
+msgid ""
+"To quickly indicate and smoothly recover from overflow conditions,\n"
+"there is a simple mechanism for pushback in the streaming protocol.\n"
+"If a packet is received with an optional delay field of value of 60001 or"
+" higher,\n"
+"that indicates \"choking\" or a receive window of zero.\n"
+"A packet with an optional delay field of value of 60000 or less indicates"
+" \"unchoking\".\n"
+"Packets without an optional delay field do not affect the choke/unchoke "
+"state."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/streaming.html:470
+msgid ""
+"After being choked, no more packets with data should be sent until the "
+"transmitter is unchoked,\n"
+"except for occasional \"probe\" data packets to compensate for possible "
+"lost unchoke packets.\n"
+"The choked endpoint should start a \"persist timer\" to control the "
+"probing, as in TCP.\n"
+"The unchoking endpoint should send several packets with this field set,\n"
+"or continue sending them periodically until data packets are received "
+"again.\n"
+"Maximum time to wait for unchoking is implementation-dependent.\n"
+"Transmitter window size and congestion control strategy after being "
+"unchoked is implementation-dependent."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/streaming.html:481
+msgid "Congestion Control"
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/streaming.html:482
+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:489
+msgid "Close"
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/streaming.html:490
+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:498
+msgid ""
+"There is no ping function at the I2CP layer (equivalent to ICMP echo) or "
+"in datagrams.\n"
+"This function is provided in streaming.\n"
+"Pings and pongs may not be combined with a standard streaming packet;\n"
+"if the ECHO option is set, then\n"
+"most other flags, options, ackThrough, sequenceNum, NACKs, etc. are "
+"ignored."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/streaming.html:506
+msgid ""
+"A ping packet must have the ECHO, SIGNATURE_INCLUDED, and FROM_INCLUDED "
+"flags set.\n"
+"The sendStreamId must be greater than zero, and the receiveStreamId is "
+"ignored.\n"
+"The sendStreamId may or may not correspond to an existing connection."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/streaming.html:512
+msgid ""
+"A pong packet must have the ECHO flag set.\n"
+"The sendStreamId must be zero, and the receiveStreamId is the "
+"sendStreamId from the ping.\n"
+"Prior to release 0.9.18, the pong packet does not include any payload "
+"that was contained in the ping."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/streaming.html:518
+msgid ""
+"As of release 0.9.18, pings and pongs may contain a payload.\n"
+"The payload in the ping, up to a maximum of 32 bytes, is returned in the "
+"pong."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/streaming.html:523
+msgid ""
+"Streaming may be configured to disable sending pongs with the "
+"configuration i2p.streaming.answerPings=false."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/streaming.html:528
+msgid "Control Block Sharing"
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/streaming.html:529
+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"
+"<a href=\"http://www.ietf.org/rfc/rfc2140.txt\">RFC 2140</a>).\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:550
+msgid "Other Parameters"
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/streaming.html:551
+msgid ""
+"The following parameters are hardcoded, but may be of interest for "
+"analysis:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/streaming.html:570
+#: i2p2www/pages/site/docs/how/network-database.html:895
+msgid "History"
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/streaming.html:571
+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:585
+#: i2p2www/pages/site/docs/how/elgamal-aes.html:344
+#: i2p2www/pages/site/docs/how/garlic-routing.html:251
+#: i2p2www/pages/site/docs/how/network-database.html:900
+#: 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:723
+#: i2p2www/pages/site/docs/protocol/i2np.html:226
+#: i2p2www/pages/site/docs/transport/ntcp.html:544
+#: i2p2www/pages/site/docs/transport/ssu.html:585
+#: i2p2www/pages/site/docs/tunnels/implementation.html:506
+msgid "Future Work"
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/streaming.html:586
+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:592
+msgid "Additional tuning of the streaming lib parameters may be necessary."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/streaming.html:595
+#, python-format
+msgid ""
+"Another area for research is the interaction of the streaming lib with "
+"the\n"
+"NTCP and SSU transport layers.\n"
+"See <a href=\"%(ntcpdisc)s\">the NTCP discussion page</a> for details."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/streaming.html:600
+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:610
+msgid "The data in the first SYN packet may exceed the receiver's MTU."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/streaming.html:613
+msgid "The DELAY_REQUESTED field could be used more."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/streaming.html:616
+msgid ""
+"Duplicate initial SYNCHRONIZE packets on short-lived streams may not be "
+"recognized and removed."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/streaming.html:619
+msgid "Don't send the MTU in a retransmission."
+msgstr ""
+
+#: i2p2www/pages/site/docs/api/streaming.html:622
+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:627
+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:632
+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
+msgid "January 2017"
+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"
+"<a href=\"%(commonstructures)s#struct_Destination\">Destination</a>,\n"
+"using the I2P Base 64 alphabet [A-Z][a-z][0-9]-~.\n"
+"<a href=\"%(commonstructures)s#struct_Destination\">Destinations</a>\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 ""
+"Current Destinations for clients are 387 or more bytes (516 or more in "
+"Base 64 encoding).\n"
+"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"
+"<a href=\"%(commonstructures)s#struct_Destination\">Destination</a>, 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"
+"<a href=\"%(commonstructures)s#type_Hash\">32-byte SHA-256 Hashes</a>\n"
+"of the binary\n"
+"<a href=\"%(commonstructures)s#struct_Destination\">Destinations</a>\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&#37;."
+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"
+"<a href=\"%(commonstructures)s#struct_Destination\">Destination</a>\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"
+"<a href=\"%(naming)s\">I2P naming standards</a>.\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 <a "
+"href=\"%(commonstructures)s#struct_Destination\">Destinations</a>\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"
+"<a href=\"http://www.bittorrent.org/beps/bep_0010.html\">the extension "
+"handshake</a>.\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"
+"<a href=\"%(commonstructures)s#struct_Destination\">Destinations</a>\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"
+"<a href=\"http://www.bittorrent.org/beps/bep_0005.html\">BEP 5</a>\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"
+"<a href=\"http://www.bittorrent.org/beps/bep_0010.html\">the extension "
+"handshake</a>.\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:286
+msgid "Datagram (UDP) Trackers"
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/bittorrent.html:287
+msgid ""
+"UDP tracker support in clients and trackers is not yet available.\n"
+"Preliminary differences from\n"
+"<a href=\"http://www.bittorrent.org/beps/bep_0015.html\">BEP 15</a>\n"
+"are described below, and are subject to change.\n"
+"Contact the I2P developers if you wish to develop a client or tracker "
+"supporting datagram announces."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/bittorrent.html:295
+msgid ""
+"A UDP tracker listens on two ports.\n"
+"The \"query port\" is the advertised port, and is used to receive "
+"repliable (signed) datagrams, for the connect request only.\n"
+"The \"response port\" is used to receive unsigned (raw) datagrams, and is"
+" the source port for all replies.\n"
+"The response port is arbitrary.\n"
+"A client sends and receives on a single port only.\n"
+"It receives only unsigned (raw) datagrams.\n"
+"Raw datagrams provides increased efficiency for replies since they "
+"contain tokens sent in the query, and need not be signed."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/bittorrent.html:305
+msgid ""
+"In the announce request, the 4-byte IP is replaced by a 32-byte hash, and"
+" the port is still present,\n"
+"although it may be ignored by the tracker.\n"
+"In the announce response, each 4-byte IP and 2-byte port is replaced by a"
+" 32-byte hash (compact peer info), and no port is present.\n"
+"The client sends the announce request and scrape request to the source "
+"port in the announce response packet.\n"
+"The connect request, connect response, scrape request, scrape response, "
+"and error response are the same as in BEP 15."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/bittorrent.html:313
+msgid ""
+"Source addresses in I2P cannot be spoofed, so it is possible to use a "
+"simplified protocol\n"
+"with 2 packets instead of 4, omitting the connect request and response.\n"
+"In this case, the announce request would be a repliable datagram sent to "
+"the tracker's query port,\n"
+"and the tracker would not require a response port.\n"
+"While this is more efficient, it would be more difficult to modify an "
+"existing tracker to support this mode.\n"
+"The URL for the 4-packet-mode tracker would use standard \"udp://\" "
+"prefix. \n"
+"The URL for a modified 2-packet-mode tracker would require a different "
+"prefix if both modes are supported in I2P."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/bittorrent.html:326
+#: i2p2www/pages/site/docs/how/intro.html:184
+msgid "Additional Information"
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/bittorrent.html:328
+#, python-format
+msgid ""
+"I2P bittorrent standards are generally discussed on <a "
+"href=\"http://%(zzz)s/\">%(zzz)s</a>."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/bittorrent.html:331
+#, python-format
+msgid ""
+"A chart of current tracker software capabilities is <a "
+"href=\"http://%(zzz)s/files/trackers.html\">also available there</a>."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/bittorrent.html:334
+#, python-format
+msgid ""
+"The\n"
+"<a href=\"http://%(forum)s/viewtopic.php?t=2068\">I2P bittorrent FAQ</a>"
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/bittorrent.html:338
+#, python-format
+msgid "<a href=\"http://%(zzz)s/topics/812\">DHT on I2P discussion</a>"
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/embedding.html:2
+msgid "Embedding I2P in your Application"
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/embedding.html:3
+msgid "November 2017"
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/embedding.html:8
+msgid ""
+"This page is about bundling the entire I2P router binary with your "
+"application.\n"
+"It is not about writing an application to work with I2P (either bundled "
+"or external)."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/embedding.html:13
+msgid ""
+"Lots of projects are bundling, or talking about bundling, I2P. That's "
+"great if done right.\n"
+"If done wrong, it could cause real harm to our network.\n"
+"The I2P router is complex, and it can be a challenge to hide all the "
+"complexity from your users.\n"
+"This page discusses some general guidelines."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/embedding.html:23
+msgid "Talk to us"
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/embedding.html:24
+msgid ""
+"Start a dialog. We're here to help. Applications that embed I2P are the "
+"most promising - and exciting -\n"
+"opportunities for us to grow the network and improve anonymity for "
+"everyone."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/embedding.html:30
+msgid "Choose your router wisely"
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/embedding.html:31
+msgid ""
+"If your application is in Java or Scala, it's an easy choice - use the "
+"Java router.\n"
+"If in C/C++, we recommend i2pd. The development of i2pcpp has stopped.\n"
+"For apps in other languages, best to use SAM or BOB or SOCKS and bundle "
+"the Java router as a separate process.\n"
+"Some of the following only applies to the Java router."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/embedding.html:39
+msgid "Licensing"
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/embedding.html:40
+msgid "Ensure you meet the license requirements of the software you are bundling."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/embedding.html:45
+msgid "Verify default configuration"
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/embedding.html:46
+msgid ""
+"A correct default configuration is crucial. Most users will not change "
+"the defaults.\n"
+"The defaults for your application may need to be different than the "
+"defaults for the router you are bundling.\n"
+"Override the router defaults if necessary."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/embedding.html:51
+msgid ""
+"Some important defaults to review: Max bandwidth, tunnel quantity and "
+"length, max participating tunnels.\n"
+"A lot of this depends on the expected bandwidth and usage patterns of "
+"your app."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/embedding.html:55
+msgid ""
+"Configure enough bandwidth and tunnels to allow your users to contribute "
+"to the network.\n"
+"Consider disabling external I2CP, as you probably don't need it and it "
+"would conflict with any other running I2P instance.\n"
+"Also look at the configs for disabling killing of the JVM on exit, for "
+"example."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/embedding.html:62
+msgid "Participating Traffic Considerations"
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/embedding.html:63
+msgid ""
+"It may be tempting for you to disable participating traffic.\n"
+"There's several ways to do this (hidden mode, setting max tunnels to 0, "
+"setting shared bandwidth below 12 KBytes/sec).\n"
+"Without participating traffic, you don't have to worry about graceful "
+"shutdown,\n"
+"your users don't see bandwidth usage not generated by them, etc.\n"
+"However, there's lots of reasons why you should allow participating "
+"tunnels."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/embedding.html:70
+msgid ""
+"First of all, the router doesn't work that well if it doesn't have a "
+"chance to \"integrate\" with the network,\n"
+"which is helped tremendously by others building tunnels through you."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/embedding.html:74
+msgid ""
+"Secondly, over 90&#37; of the routers in the current network allow "
+"participating traffic.\n"
+"It's the default in the Java router.\n"
+"If your application doesn't route for others and it gets really popular, "
+"then it's a leech on the network,\n"
+"and it upsets the balance we have now.\n"
+"If it gets really big, then we become Tor, and spend our time begging for"
+" people to enable relaying."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/embedding.html:81
+msgid ""
+"Thirdly, participating traffic is cover traffic that helps your users' "
+"anonymity."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/embedding.html:84
+msgid ""
+"We strongly discourage you from disabling participating traffic by "
+"default.\n"
+"If you do this and your application gets hugely popular, it could break "
+"the network."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/embedding.html:90
+msgid "Persistence"
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/embedding.html:91
+msgid ""
+"You must save the router's data (netdb, configuration, etc.) between runs"
+" of the router.\n"
+"I2P does not work well if you must reseed each startup, and that's a huge"
+" load on our reseed servers, and not very good for anonymity either.\n"
+"Even if you bundle router infos, I2P needs saved profile data for best "
+"performance."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/embedding.html:99
+msgid "Configurability"
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/embedding.html:100
+msgid ""
+"Give your users a way to change the configuration of the important "
+"settings.\n"
+"We understand that you will probably want to hide most of I2P's "
+"complexity, but it's important to show some basic settings.\n"
+"In addition to the defaults above, some network settings such as UPnP, "
+"IP/port may be helpful."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/embedding.html:108
+msgid "Floodfill Considerations"
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/embedding.html:109
+msgid ""
+"Above a certain bandwidth setting, and meeting other health criteria, "
+"your router will become floodfill,\n"
+"which may cause a large increase in connections and memory usage (at "
+"least with the Java router).\n"
+"Think about whether that's OK. You can disable floodfill, but then your "
+"fastest users aren't contributing what they could.\n"
+"It also depends on the typical uptime for your application."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/embedding.html:119
+msgid "Reseeding"
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/embedding.html:120
+msgid ""
+"Decide if you are bundling router infos or using our reseed hosts.\n"
+"The Java reseed host list is in the source code, so if you keep your "
+"source up to date, the host list will be also.\n"
+"Be aware of possible blocking by hostile governments."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/embedding.html:129
+msgid "Reduce Network Resource Usage"
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/embedding.html:130
+msgid ""
+"Consider setting your application tunnels to delay-open, reduce-on-idle "
+"and/or close-on-idle.\n"
+"This is straightforward if using i2ptunnel but you'll have to implement "
+"some of it yourself if using I2CP directly.\n"
+"See i2psnark for code that reduces tunnel count and then closes the "
+"tunnel, even in the presence of some background DHT activity."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/embedding.html:138
+msgid "Updatability"
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/embedding.html:139
+msgid ""
+"Have an auto-update feature if at all possible, or at least auto-"
+"notification of a new version.\n"
+"Our biggest fear is a huge number of routers out there that can't be "
+"updated.\n"
+"We have about 6-8 releases a year of the Java router, and it's critical "
+"to the health of the network that the users keep up.\n"
+"We usually have over 80&#37; of the network on the latest release within "
+"6 weeks after the release, and we'd like to keep it that way.\n"
+"You don't need to worry about disabling the router's built-in auto-update"
+" function, as that code is in the router console,\n"
+"which you presumably are not bundling."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/embedding.html:150
+msgid "Rollout"
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/embedding.html:151
+msgid ""
+"Have a gradual rollout plan. Don't overwhelm the network all at once.\n"
+"We currently have approximately 25K unique users per day and 40K uniques "
+"per month.\n"
+"We are probably able to handle growth of 2-3X per year without too much "
+"issue.\n"
+"If you anticipate a faster rampup than that, OR the bandwidth "
+"distribution (or uptime distribution,\n"
+"or any other significant characteristic) of your userbase is "
+"significantly different from our current userbase,\n"
+"we really need to have a discussion.\n"
+"The bigger your growth plans, the more important everthing else in this "
+"checklist is."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/embedding.html:163
+msgid "Design for and Encourage Long Uptimes"
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/embedding.html:164
+msgid ""
+"Tell your users that I2P works best if it keeps running.\n"
+"It may be several minutes after startup before it works well, and even "
+"more after first install.\n"
+"If your average uptime is less than an hour, I2P is probably the wrong "
+"solution."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/embedding.html:172
+msgid "Show Status"
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/embedding.html:173
+msgid ""
+"Provide some indication to the user that the application tunnels are "
+"ready. Encourage patience."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/embedding.html:178
+msgid "Graceful Shutdown"
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/embedding.html:179
+msgid ""
+"If possible, delay the shutdown until your participating tunnels expire.\n"
+"Don't let your users break tunnels easily, or at least ask them to "
+"confirm."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/embedding.html:185
+msgid "Education and Donation"
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/embedding.html:186
+msgid ""
+"It would be nice if you give your users links to learn more about I2P and"
+" to donate."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/embedding.html:192
+msgid "External Router Option"
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/embedding.html:193
+msgid ""
+"Depending on your user base and application,\n"
+"it may be helpful to provide an option or a separate package to use an "
+"external router."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/embedding.html:200
+msgid "Use of other Common Services"
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/embedding.html:201
+msgid ""
+"If you plan to use or link to other common I2P services (news feeds, "
+"hosts.txt subscriptions, trackers, outproxies, etc.),\n"
+"make sure you aren't overloading them,\n"
+"and talk to the people who are running them to make sure it's ok."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/embedding.html:209
+msgid "Time / NTP Issues"
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/embedding.html:210
+msgid ""
+"I2P includes an SNTP client. I2P requires correct time to operate.\n"
+"It will compensate for a skewed system clock but this may delay startup. "
+"You may disable I2P's SNTP queries,\n"
+"but this isn't advised unless your application makes sure the system "
+"clock is correct."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/embedding.html:218
+msgid "Choose What and How you Bundle"
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/embedding.html:219
+msgid ""
+"At a minimum you will need i2p.jar, router.jar, streaming.jar, and "
+"mstreaming.jar.\n"
+"You may omit the two streaming jars for a datagram-only app.\n"
+"Some apps may need more, e.g. i2ptunnel.jar or addressbook.jar.\n"
+"Don't forget jbigi.jar, or a subset of it for the platforms you support, "
+"to make the crypto much faster.\n"
+"We are currently building them for Java 7, as of 0.9.24. The source is "
+"mostly compatible with Java 6 if you want to do your own compile,\n"
+"but we may start using Java 7 features at any time without notice.\n"
+"If you're building Debian / Ubuntu packages, you should require the I2P "
+"package from our PPA instead of bundling it.\n"
+"You almost certainly do not need susimail, susidns, the router console, "
+"and i2psnark, for example."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/embedding.html:229
+msgid ""
+"The following files should be included in the I2P installation directory,"
+" specified with the \"i2p.dir.base\" property.\n"
+"Don't forget certificates/reseed and certificates/ssl, required for "
+"reseeding, and blocklist.txt for IP validation.\n"
+"The geoip directory is optional, but recommended so the router can make "
+"decisions based on location.\n"
+"The hosts.txt file may be necessary, you may modify it to include any "
+"hosts your application uses.\n"
+"You may add a router.config file to the base directory to override "
+"initial defaults."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/embedding.html:236
+msgid ""
+"License requirements may require you to include the LICENSES.txt file and"
+" the licenses directory."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/embedding.html:242
+msgid "You may also wish to bundle a hosts.txt file."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/embedding.html:245
+msgid "Be sure to specify a Java 7 bootclasspath if compiling with Java 8."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/embedding.html:253
+msgid "Android considerations"
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/embedding.html:254
+msgid ""
+"Our Android router app may be shared by multiple clients.\n"
+"If it is not installed, the user will be prompted when he starts a client"
+" app."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/embedding.html:258
+msgid ""
+"Some developers have expressed concern that this is a poor user "
+"experience,\n"
+"and they wish to embed the router in their app.\n"
+"We do have an Android router service library on our roadmap, which could "
+"make embedding easier.\n"
+"More information needed."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/embedding.html:264
+#: i2p2www/pages/site/docs/applications/embedding.html:275
+msgid "If you require assistance, please contact us."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/embedding.html:270
+msgid "Maven jars"
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/embedding.html:271
+msgid ""
+"We have a limited number of our jars on <a "
+"href=\"http://search.maven.org/#search%7Cga%7C1%7Cg%3A%22net.i2p%22\">Maven"
+" Central</a>.\n"
+"There are numerous trac tickets for us to address that will improve and "
+"expand the released jars on Maven Central."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/embedding.html:281
+msgid "Datagram (DHT) considerations"
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/embedding.html:282
+msgid ""
+"If your application is using I2P datagrams, e.g. for a DHT,\n"
+"there's lots of advanced options available to reduce overhead and "
+"increase reliability.\n"
+"This may take some time and experimentation to get working well.\n"
+"Be aware of size/reliability tradeoffs. Talk to us for help.\n"
+"It is possible - and recommended - to use Datagrams and Streaming on the "
+"same Destination.\n"
+"Don't create separate Destinations for this.\n"
+"Don't try to store your unrelated data in the existing network DHTs "
+"(iMule, bote, bittorrent, and router).\n"
+"Build your own. If you are hardcoding seed nodes, we recommend that you "
+"have several."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/embedding.html:295
+msgid "Comarketing"
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/embedding.html:296
+msgid ""
+"Let's work together. Don't wait until it's done.\n"
+"Give us your Twitter handle and start tweeting about it, we will return "
+"the favor."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/embedding.html:302
+msgid "Malware"
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/embedding.html:303
+msgid ""
+"Please don't use I2P for evil.\n"
+"It could cause great harm both to our network and our reputation."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/embedding.html:309
+msgid "Join Us"
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/embedding.html:310
+msgid ""
+"This may be obvious, but join the community. Run I2P 24/7. Start an "
+"eepsite about your project.\n"
+"Hang out in IRC #i2p-dev. Post on the forums. Spread the word.\n"
+"We can help get you users, testers, translators, or even coders."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/embedding.html:318
+msgid "Application Examples"
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/embedding.html:319
+msgid ""
+"You may wish to install and play with the I2P Android app, and look at "
+"its code, for an example of an application that bundles the router.\n"
+"See what we expose to the user and what we hide.\n"
+"Look at the state machine we use to start and stop the router.\n"
+"Other examples are: Vuze, the Nightweb Android app, iMule, TAILS, iCloak,"
+" and Monero."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/embedding.html:327
+msgid "Code Example"
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/embedding.html:328
+msgid ""
+"None of the above actually tells you how to write your code to\n"
+"bundle the Java router, so following is a brief example."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/embedding.html:358
+msgid ""
+"This code is for the case where your application starts the router, as in"
+" our Android app.\n"
+"You could also have the router start the application via the "
+"clients.config and i2ptunnel.config files,\n"
+"together with Jetty webapps,\n"
+"as is done in our Java packages.\n"
+"As always, state management is the difficult part."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/managed-clients.html:3
+msgid "February 2014"
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/managed-clients.html:8
+#, python-format
+msgid ""
+"Clients may be started directly by the router when they are listed\n"
+"in the <a href=\"%(configspec)s\">clients.config</a> file.\n"
+"These clients may be \"managed\" or \"unmanaged\".\n"
+"This is handled by the ClientAppManager.\n"
+"Additionally, managed or unmanaged clients may register with the\n"
+"ClientAppManager so that other clients may retrieve a reference to them.\n"
+"There is also a simple Port Mapper facility for clients to register an\n"
+"internal port that other clients may look up."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/managed-clients.html:21
+msgid ""
+"As of release 0.9.4, the router supports managed clients.\n"
+"Managed clients are instantiated and started by the ClientAppManager.\n"
+"The ClientAppManager maintains a reference to the client and receives "
+"updates on the client's state.\n"
+"Managed clients are preferred, as it is much easier to implement state "
+"tracking\n"
+"and to start and stop a client. It also is much easier to avoid static "
+"references in the client code\n"
+"which could lead to excessive memory usage after a client is stopped.\n"
+"Managed clients may be started and stopped by the user in the router "
+"console,\n"
+"and are stopped at router shutdown."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/managed-clients.html:31
+msgid ""
+"Managed clients implement either the net.i2p.app.ClientApp or "
+"net.i2p.router.app.RouterApp interface.\n"
+"Clients implementing the ClientApp interface must provide the following "
+"constructor:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/managed-clients.html:38
+msgid ""
+"Clients implementing the RouterApp interface must provide the following "
+"constructor:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/managed-clients.html:44
+msgid "The arguments provided are specified in the clients.config file."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/managed-clients.html:48
+msgid "Unmanaged Clients"
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/managed-clients.html:49
+msgid ""
+"If the main class specified in the clients.config file does not implement"
+" a managed interface,\n"
+"it will be started with main() with the arguments specified,\n"
+"and stopped with main() with the arguments specified.\n"
+"The router does not maintain a reference, since all interactions are via "
+"the static main() method.\n"
+"The console cannot provide accurate state information to the user."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/managed-clients.html:57
+msgid "Registered Clients"
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/managed-clients.html:58
+msgid ""
+"Clients, whether managed or unmanaged, may register with the "
+"ClientAppManager\n"
+"so that other clients may retrieve a reference to them.\n"
+"Registration is by name.\n"
+"Known registered clients are:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/managed-clients.html:68
+msgid "Port Mapper"
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/managed-clients.html:69
+msgid ""
+"The router also provides a simple mechanism for clients to find an "
+"internal socket service,\n"
+"such as the HTTP proxy. This is provided by the Port Mapper.\n"
+"Registration is by name.\n"
+"Clients that register generally provide an internal emulated socket on "
+"that port."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:2
+msgid "Supported Applications"
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:5
+#: i2p2www/pages/site/docs/applications/supported.html:188
+msgid "Blogging, Forums, and Wikis"
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:7
+#: i2p2www/pages/site/docs/applications/supported.html:234
+msgid "Decentralized File Storage"
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:10
+#: i2p2www/pages/site/docs/applications/supported.html:246
+msgid "Development Tools"
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:13
+#: i2p2www/pages/site/docs/applications/supported.html:248
+msgid "Version control"
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:17
+#: i2p2www/pages/site/docs/applications/supported.html:267
+msgid "Domain Naming"
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:19
+#: i2p2www/pages/site/docs/applications/supported.html:285
+msgid "Email"
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:22
+#: i2p2www/pages/site/docs/applications/supported.html:330
+msgid "File Sharing"
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:25
+#: i2p2www/pages/site/docs/applications/supported.html:332
+msgid "BitTorrent clients"
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:27
+#: i2p2www/pages/site/docs/applications/supported.html:375
+msgid "BitTorrent trackers and indexers"
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:36
+#: i2p2www/pages/site/docs/applications/supported.html:442
+msgid "Network Administration"
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:39
+#: i2p2www/pages/site/docs/applications/supported.html:444
+msgid "General-purpose socket utilities"
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:46
+#: i2p2www/pages/site/docs/applications/supported.html:485
+msgid "Real-time Chat"
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:49
+#: i2p2www/pages/site/docs/applications/supported.html:487
+msgid "Instant messaging clients"
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:51
+#: i2p2www/pages/site/docs/applications/supported.html:497
+msgid "IRC clients"
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:53
+#: i2p2www/pages/site/docs/applications/supported.html:548
+msgid "IRC servers"
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:58
+#: i2p2www/pages/site/docs/applications/supported.html:564
+msgid "Web Browsing"
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:61
+#: i2p2www/pages/site/docs/applications/supported.html:566
+msgid "Anonymous websites"
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:63
+#: i2p2www/pages/site/docs/applications/supported.html:615
+msgid "Proxy software"
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:65
+#: i2p2www/pages/site/docs/applications/supported.html:640
+msgid "Inproxies"
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:67
+#: i2p2www/pages/site/docs/applications/supported.html:681
+msgid "Outproxies"
+msgstr "Východzie proxy"
+
+#: i2p2www/pages/site/docs/applications/supported.html:72
+#: i2p2www/pages/site/docs/applications/supported.html:695
+msgid "Website Hosting"
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:75
+#: i2p2www/pages/site/docs/applications/supported.html:710
+msgid "Web servers"
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:82
+#, 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"
+"<a href=\"%(trac)s\">Trac</a>, and be sure to select the\n"
+"“www” component in the submission form."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:89
+msgid ""
+"\n"
+"Supported applications are tagged with one or more of the following:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:94
+#: i2p2www/pages/site/docs/applications/supported.html:281
+#: i2p2www/pages/site/docs/applications/supported.html:313
+#: i2p2www/pages/site/docs/applications/supported.html:338
+#: i2p2www/pages/site/docs/applications/supported.html:707
+msgid "bundled"
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:97
+msgid ""
+"<em>Bundled application</em> — 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:105
+#: i2p2www/pages/site/docs/applications/supported.html:197
+#: i2p2www/pages/site/docs/applications/supported.html:210
+#: i2p2www/pages/site/docs/applications/supported.html:222
+#: i2p2www/pages/site/docs/applications/supported.html:230
+#: i2p2www/pages/site/docs/applications/supported.html:243
+#: i2p2www/pages/site/docs/applications/supported.html:294
+#: i2p2www/pages/site/docs/applications/supported.html:407
+#: i2p2www/pages/site/docs/applications/supported.html:429
+#: i2p2www/pages/site/docs/applications/supported.html:438
+#: i2p2www/pages/site/docs/applications/supported.html:526
+msgid "plugin"
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:108
+#, python-format
+msgid ""
+"<em>Third-party plugin</em> — 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](<a href=\n"
+"\"http://%(plugins)s\">http://%(plugins)s</a>) to identify security and\n"
+"anonymity issues."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:119
+#: i2p2www/pages/site/docs/applications/supported.html:222
+#: i2p2www/pages/site/docs/applications/supported.html:230
+#: i2p2www/pages/site/docs/applications/supported.html:243
+#: i2p2www/pages/site/docs/applications/supported.html:254
+#: i2p2www/pages/site/docs/applications/supported.html:263
+#: i2p2www/pages/site/docs/applications/supported.html:326
+#: i2p2www/pages/site/docs/applications/supported.html:345
+#: i2p2www/pages/site/docs/applications/supported.html:356
+#: i2p2www/pages/site/docs/applications/supported.html:371
+#: i2p2www/pages/site/docs/applications/supported.html:417
+#: i2p2www/pages/site/docs/applications/supported.html:429
+#: i2p2www/pages/site/docs/applications/supported.html:438
+#: i2p2www/pages/site/docs/applications/supported.html:453
+#: i2p2www/pages/site/docs/applications/supported.html:459
+#: i2p2www/pages/site/docs/applications/supported.html:465
+#: i2p2www/pages/site/docs/applications/supported.html:475
+#: i2p2www/pages/site/docs/applications/supported.html:481
+#: i2p2www/pages/site/docs/applications/supported.html:493
+#: i2p2www/pages/site/docs/applications/supported.html:526
+#: i2p2www/pages/site/docs/applications/supported.html:532
+#: i2p2www/pages/site/docs/applications/supported.html:538
+#: i2p2www/pages/site/docs/applications/supported.html:544
+#: i2p2www/pages/site/docs/applications/supported.html:621
+#: i2p2www/pages/site/docs/applications/supported.html:630
+#: i2p2www/pages/site/docs/applications/supported.html:636
+#: i2p2www/pages/site/docs/applications/supported.html:707
+#: i2p2www/pages/site/docs/applications/supported.html:722
+#: i2p2www/pages/site/docs/applications/supported.html:728
+#: i2p2www/pages/site/docs/applications/supported.html:734
+#: i2p2www/pages/site/docs/applications/supported.html:740
+msgid "standalone"
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:119
+#: i2p2www/pages/site/docs/applications/supported.html:197
+#: i2p2www/pages/site/docs/applications/supported.html:204
+#: i2p2www/pages/site/docs/applications/supported.html:210
+#: i2p2www/pages/site/docs/applications/supported.html:216
+#: i2p2www/pages/site/docs/applications/supported.html:365
+#: i2p2www/pages/site/docs/applications/supported.html:389
+#: i2p2www/pages/site/docs/applications/supported.html:398
+#: i2p2www/pages/site/docs/applications/supported.html:554
+#: i2p2www/pages/site/docs/applications/supported.html:560
+msgid "standalone/mod"
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:122
+msgid ""
+"<em>Third-party standalone application</em> — Many standard network\n"
+"applications only require careful setup and configuration to communicate\n"
+"anonymously over I2P. These are tagged with <em>standalone</em>. Some\n"
+"applications, tagged with <em>standalone/mod</em>, 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:304
+#: i2p2www/pages/site/docs/applications/supported.html:574
+#: i2p2www/pages/site/docs/applications/supported.html:584
+#: i2p2www/pages/site/docs/applications/supported.html:593
+#: i2p2www/pages/site/docs/applications/supported.html:599
+#: i2p2www/pages/site/docs/applications/supported.html:605
+#: i2p2www/pages/site/docs/applications/supported.html:611
+#: i2p2www/pages/site/docs/applications/supported.html:653
+#: i2p2www/pages/site/docs/applications/supported.html:661
+#: i2p2www/pages/site/docs/applications/supported.html:670
+#: i2p2www/pages/site/docs/applications/supported.html:677
+#: i2p2www/pages/site/docs/applications/supported.html:691
+msgid "service"
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:138
+msgid ""
+"<em>Third-party essential network service</em> — 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:150
+#: i2p2www/pages/site/docs/applications/supported.html:222
+msgid "unmaintained"
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:153
+msgid ""
+"<em>Unmaintained</em> — 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:161
+#, 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 <a "
+"href=\"%(threatmodel)s\">identified\n"
+"threats to anonymity</a>. 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:173
+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:181
+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:203
+msgid "Lightweight forum software."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:209
+msgid "Another lightweight blogging platform."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:215
+msgid "Most popular open source forum software."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:221
+msgid "Distributed forums software, originally developed by jrandom."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:226
+#, python-format
+msgid ""
+"A Java-based MediaWiki clone. No external database needed.\n"
+"Plugin available <a href=\"http://%(plugins)s/plugins/jamwiki\">here</a>."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:238
+#, python-format
+msgid ""
+"Port of the <a href=\"http://tahoe-lafs.org/\"><strong>Tahoe-"
+"LAFS</strong></a>\n"
+"distributed file system to the I2P network. Controller plugin <a href=\n"
+"\"http://%(stats)s/i2p/plugins/\">here</a>."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:253
+msgid "Most popular distributed version control system."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:259
+#, python-format
+msgid ""
+"Another distributed version control system. Currently\n"
+"<a href=\"%(monotone)s\">used in I2P development</a>."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:271
+#, python-format
+msgid ""
+"Provides management of addressbooks, which are part of a simple,\n"
+"user-controlled <a href=\"%(naming)s\">I2P naming system</a> 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. (<em>Note:</em> 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:290
+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:299
+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:309
+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:318
+#, python-format
+msgid ""
+"Can be configured to use Postman's email service. See\n"
+"<a href=\"%(reviews)s\">this comparison of MUAs</a>,\n"
+"and configuration settings for\n"
+"<a href=\"%(smtp)s\">SMTP</a> and <a href=\"%(pop3)s\">POP3</a>."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:337
+msgid "I2P's integrated BitTorrent client."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:343
+msgid ""
+"Modified version of I2PSnark, no more supported neither\n"
+"    functional."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:350
+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:361
+msgid ""
+"Clean, full-featured cross-platform BitTorrent client with official\n"
+"ports for several GUI toolkits."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:370
+msgid "Has a plugin providing I2P support."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:377
+#, python-format
+msgid ""
+"For a detailed feature comparison of I2P-enabled trackers/indexers, see\n"
+"<a href=\"http://%(zzz)s/files/trackers.html\">here</a>."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:385
+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:394
+#, python-format
+msgid ""
+"Lightweight tracker/indexer. I2P mod available in the i2p.opentracker\n"
+"branch of the <a href=\"%(newdevs)s\">I2P Monotone repository</a>."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:403
+#, python-format
+msgid ""
+"<a href=\"http://%(zzz)s/\">zzz's</a> Java-based open tracker. More info\n"
+"<a href=\"http://%(zzz)s/topics/598?page=1#p2085\">here</a>."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:416
+msgid "I2P port of the aMule ED2K client."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:425
+#, python-format
+msgid ""
+"Port of the <a href=\"http://www.phex.org/mambo/\">Phex</a> Gnutella "
+"client. Website\n"
+"for plugin version <a href=\"http://%(stats)s/i2p/plugins/\">here</a>."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:434
+#, python-format
+msgid ""
+"Cache for Gnutella peers on I2P. Website for plugin version\n"
+"<a href=\"http://%(stats)s/i2p/plugins/\">here</a>."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:449
+msgid ""
+"OpenBSD's rewrite of the Unix standard tool, netcat, for socket relaying."
+"\n"
+"Several clones, ports, and forks have appeared over the years."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:458
+msgid "Like netcat but more powerful."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:464
+msgid ""
+"Proxy providing simple, transparent SOCKS-ification of network "
+"applications."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:474
+msgid ""
+"Most popular implementation of the Secure Shell (SSH) protocol and "
+"related tools."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:480
+msgid "Open source Secure Shell (SSH) client for Windows."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:492
+msgid "IM client with multiple incarnations, unsuported."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:499
+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"
+"<code>/me</code> command) which isn't inherently dangerous."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:510
+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 <a href=\"http://www.wireshark.org/\">Wireshark</a> 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:522
+#, python-format
+msgid ""
+"Small Java-based IRC client. Plugin available <a href=\n"
+"\"http://%(stats)s/i2p/plugins/\">here</a>."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:531
+msgid "Cross-platform graphical IRC client based on XChat."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:537
+msgid "Unixy terminal-based IRC client."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:543
+msgid "Another Unixy terminal-based IRC client."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:553
+msgid "IRC server developed from scratch."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:559
+msgid "Most popular IRC server."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:571
+msgid ""
+"Any website hosted anonymously on I2P, reachable through the I2P router's"
+" HTTP proxy."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:579
+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:589
+#, python-format
+msgid ""
+"Website for <a href=\"http://%(sponge)s/\">sponge's</a> jump service.\n"
+"Source code available."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:598
+msgid "Another jump service."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:604
+msgid "Dynamically updated eepsite index."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:610
+#, python-format
+msgid "Website for <a href=\"http://%(zzz)s/\">zzz's</a> jump service."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:620
+msgid "SOCKS-enabled caching web proxy with basic filtering capabilities."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:626
+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:635
+msgid "Venerable caching web proxy."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:642
+msgid "Gateways allowing users on the public Internet to access eepsites."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:649
+#, python-format
+msgid ""
+"<a href=\"http://%(tino)s/\">tino's</a> inproxy on the public Internet,\n"
+"currently out of service,"
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:658
+#: i2p2www/pages/site/docs/applications/supported.html:667
+#: i2p2www/pages/site/docs/applications/supported.html:674
+msgid "Another inproxy on the public Internet."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:683
+msgid ""
+"Gateways allowing I2P users to access content hosted on the public "
+"Internet."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:690
+msgid "Publicly advertised outproxy running Squid, located in Europe."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:700
+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 <a href=\"http://127.0.0.1:7658/\">user's eepsite</a>. 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:712
+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:721
+msgid "Most popular web server on the public WWW."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:727
+msgid "Web server and Java servlet container. More features than Jetty."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:733
+msgid "Fast lightweight web server."
+msgstr ""
+
+#: i2p2www/pages/site/docs/applications/supported.html:739
+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 <a href=\"%(naming)s\">the naming page</a> 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 <a "
+"href=\"#alternatives\">alternate naming systems</a> 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 <a href=\"https://zooko.com/distnames.html\">Names: "
+"Decentralized, Secure, Human-Meaningful: Choose Two</a>."
+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 <b>not globally"
+" \n"
+"unique</b>.  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 <b>locally unique</b>: "
+"they are \n"
+"what <i>you</i> 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 ""
+"<b>Inefficiency:</b>\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 <a href=\"http://%(i2host)s/\">%(i2host)sp</a>),\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"
+"<a href=\"%(url)s\">%(url)s</a>.\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 ""
+"<b>Not Scalable:</b>\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 ""
+"<b>Requires configuration and \"trust\":</b>\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 "<b>It isn't DNS</b>"
+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 ""
+"<b>Not reliable:</b>\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 ""
+"<b>Awkward, not real-time:</b>\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 ""
+"<b>Meta</b> - 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 ""
+"<b>PetName</b> - 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 "<b>HostsTxt</b> - Looks up in the following files, in order:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/discussions/naming.html:234
+msgid ""
+"<b>AddressDB</b> - Each host is listed in a separate file in a addressDb/"
+" directory."
+msgstr ""
+
+#: i2p2www/pages/site/docs/discussions/naming.html:237
+msgid ""
+"<b>Eepget</b> - 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 ""
+"<b>Exec</b> - 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 "<b>Dummy</b> - 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 <a "
+"href=\"%(todo)s#hashcash\">proof of work</a>."
+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/elgamal-aes.html:2
+msgid "ElGamal/AES + SessionTag Encryption"
+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:508
+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:524
+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:</p>"
+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"
+"<a href=\"%(commonstructures)s#type_SessionKey\">Session Key</a>\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"
+"<a href=\"%(cryptography)s#elgamal\">using ElGamal</a>\n"
+"and the encrypted block is 514 bytes long.\n"
+"</p>"
+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:254
+msgid "Minimum length: 48 bytes"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/elgamal-aes.html:257
+#, python-format
+msgid ""
+"The data is then <a href=\"%(cryptography)s\">AES Encrypted</a>,\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"
+"</p>"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/elgamal-aes.html:266
+#, python-format
+msgid ""
+"Actual max payload length, and max block length, is less than 64 KB; see "
+"the <a href=\"%(i2np)s\">I2NP Overview</a>."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/elgamal-aes.html:269
+msgid "New Session Key is currently unused and is never present."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/elgamal-aes.html:274
+msgid "Existing Session Message Specification"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/elgamal-aes.html:275
+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:283
+msgid ""
+"The existing session message is\n"
+"as follows:"
+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 <a "
+"href=\"#new\">New Session Message</a>."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/elgamal-aes.html:331
+msgid "Session Tag Configuration Options"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/elgamal-aes.html:332
+#, python-format
+msgid ""
+"As of release 0.9.2, the client may configure the default number of "
+"Session Tags to send\n"
+"and the low tag threshold for the current session.\n"
+"For brief streaming connections or datagrams, these options may be used "
+"to significantly reduce bandwidth.\n"
+"See the <a href=\"%(i2cp)s#options\">I2CP options specification</a> for "
+"details.\n"
+"The session settings may also be overridden on a per-message basis.\n"
+"See the <a href=\"%(i2cpspec)s#msg_SendMessageExpires\">I2CP Send Message"
+" Expires specification</a> for details."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/elgamal-aes.html:345
+msgid ""
+"There are many possible areas to tune the Session Key Manager's "
+"algorithms;\n"
+"some may interact with the streaming library behavior, or have "
+"significant\n"
+"impact on overall performance."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/elgamal-aes.html:352
+msgid ""
+"The number of tags delivered could depend on message size, keeping in "
+"mind\n"
+"the eventual padding to 1KB at the tunnel message layer."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/elgamal-aes.html:357
+msgid ""
+"Clients could send an estimate of session lifetime to the router, as an "
+"advisory\n"
+"on the number of tags required."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/elgamal-aes.html:362
+msgid ""
+"Delivery of too few tags causes the router to fall back to an expensive "
+"ElGamal encryption."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/elgamal-aes.html:366
+msgid ""
+"The router may assume delivery of Session Tags, or await acknowledgement "
+"before using them;\n"
+"there are tradeoffs for each strategy."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/elgamal-aes.html:371
+msgid ""
+"For very brief messages, almost the full 222 bytes of the pre-IV and "
+"padding fields in the ElGamal block\n"
+"could be used for the entire message, instead of establishing a session."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/elgamal-aes.html:376
+msgid ""
+"Evaluate padding strategy; currently we pad to a minimum of 128 bytes.\n"
+"Would be better to add a few tags to small messages than pad."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/elgamal-aes.html:381
+msgid ""
+"Perhaps things could be more efficient if the Session Tag system was "
+"bidirectional,\n"
+"so tags delivered in the 'forward' path could be used in the 'reverse' "
+"path,\n"
+"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:389
+#, python-format
+msgid ""
+"Change from Session Tags to\n"
+"<a href=\"%(futureperf)s#prng\">a synchronized PRNG</a>."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/elgamal-aes.html:394
+#, python-format
+msgid ""
+"Several of these ideas may require a new I2NP message type, or\n"
+"set a flag in the\n"
+"<a "
+"href=\"%(tunnelmessage)s#struct_TunnelMessageDeliveryInstructions\">Delivery"
+" Instructions</a>,\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:3
+msgid "March 2014"
+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"
+"<a href=\"http://www.cs.princeton.edu/~mfreed/\">Michael J. Freedman</a>\n"
+"in Roger Dingledine's Free Haven \n"
+"<a href=\"http://www.freehaven.net/papers.html\">Master's thesis</a> "
+"Section 8.1.1 (June 2000), as derived from \n"
+"<a href=\"http://www.onion-router.net/\">Onion Routing</a>."
+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 <a href=\"%(comparisons)s\">network comparisons</a>) 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"
+"<a href=\"http://www.onion-router.net/Publications.html\">large amount of"
+" academic research on onion routing</a>,\n"
+"<a href=\"http://freehaven.net/anonbib/topic.html\">Tor, and similar "
+"mixnets</a>."
+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"
+"<a href=\"%(elgamalaes)s\">ElGamal/AES+SessionTag</a> 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"
+"<a href=\"%(tunnelimpl)s\">tunnel implementation page</a>.\n"
+"Tunnel building details are defined on\n"
+"<a href=\"%(tunnelcreation)s\">this page</a>.\n"
+"We use\n"
+"<a href=\"%(elgamalaes)s\">ElGamal/AES+SessionTag</a> 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"
+"<a href=\"%(i2np)s\">I2NP messages</a>, and\n"
+"<a href=\"%(i2npspec)s#msg_Garlic\">Garlic Messages</a> are not used to "
+"build tunnels.\n"
+"We do not bundle multiple\n"
+"<a href=\"%(i2np)s\">I2NP messages</a> into a single\n"
+"<a href=\"%(i2npspec)s#msg_Garlic\">Garlic Message</a> 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"
+"<a href=\"%(commonstructures)s#struct_Destination\">Destinations</a>.\n"
+"Just as within a single tunnel, we use\n"
+"<a href=\"%(elgamalaes)s\">ElGamal/AES+SessionTag</a> for the encryption."
+"\n"
+"Each client message as delivered to the router through the\n"
+"<a href=\"%(i2cp)s\">I2CP interface</a> becomes a single\n"
+"<a href=\"%(i2npspec)s#struct_GarlicClove\">Garlic Clove</a>\n"
+"with its own\n"
+"<a href=\"%(i2npspec)s#struct_GarlicCloveDeliveryInstructions\">Delivery "
+"Instructions</a>,\n"
+"inside a\n"
+"<a href=\"%(i2npspec)s#msg_Garlic\">Garlic Message</a>.\n"
+"Delivery Instructions may specify a Destination, Router, or Tunnel."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/garlic-routing.html:171
+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:176
+msgid "Garlic Message Cloves"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/garlic-routing.html:179
+#, python-format
+msgid ""
+"A\n"
+"<a href=\"%(i2npspec)s#msg_DeliveryStatus\">Delivery Status Message</a>,\n"
+"with\n"
+"<a href=\"%(i2npspec)s#struct_GarlicCloveDeliveryInstructions\">Delivery "
+"Instructions</a>\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:192
+#, python-format
+msgid ""
+"A\n"
+"<a href=\"%(i2npspec)s#msg_DatabaseStore\">Database Store Message</a>,\n"
+"containing a\n"
+"<a href=\"%(commonstructures)s#struct_LeaseSet\">LeaseSet</a>\n"
+"for the originating Destination, with\n"
+"<a href=\"%(i2npspec)s#struct_GarlicCloveDeliveryInstructions\">Delivery "
+"Instructions</a>\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"
+"<a href=\"%(netdb)s\">network database page</a>."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/garlic-routing.html:210
+#, python-format
+msgid ""
+"By default, the Delivery Status and Database Store Messages\n"
+"are bundled when the local LeaseSet changes, when additional\n"
+"<a href=\"%(commonstructures)s#type_SessionTag\">Session Tags</a>\n"
+"are delivered, or if the messages have not been bundled in the previous "
+"minute.\n"
+"As of release 0.9.2, the client may configure the default number of "
+"Session Tags to send\n"
+"and the low tag threshold for the current session.\n"
+"See the <a href=\"%(i2cp)s#options\">I2CP options specification</a> for "
+"details.\n"
+"The session settings may also be overridden on a per-message basis.\n"
+"See the <a href=\"%(i2cpspec)s#msg_SendMessageExpires\">I2CP Send Message"
+" Expires specification</a> for details."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/garlic-routing.html:224
+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:229
+msgid ""
+"As of release 0.9.12, the Delivery Status Message is wrapped in another "
+"Garlic Message\n"
+"by the originator so that the contents are encrypted and not visible to "
+"routers on the return path."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/garlic-routing.html:235
+msgid "Storage to the Floodfill Network Database"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/garlic-routing.html:236
+#, python-format
+msgid ""
+"As explained on the\n"
+"<a href=\"%(netdb)s#delivery\">network database page</a>,\n"
+"local\n"
+"<a href=\"%(commonstructures)s#struct_LeaseSet\">LeaseSets</a>\n"
+"are sent to floodfill routers in a\n"
+"<a href=\"%(i2npspec)s#msg_DatabaseStore\">Database Store Message</a>\n"
+"wrapped in a\n"
+"<a href=\"%(i2npspec)s#msg_Garlic\">Garlic Message</a>\n"
+"so it is not visible to the tunnel's outbound gateway."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/garlic-routing.html:252
+#, 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"
+"<a "
+"href=\"%(tunnelmessage)s#struct_TunnelMessageDeliveryInstructions\">tunnel"
+" message Delivery Instructions</a>,\n"
+"a wide spectrum of batching, delay, mixing, and routing strategies are "
+"possible."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/garlic-routing.html:260
+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:267
+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:273
+#, python-format
+msgid ""
+"As a part of\n"
+"<a href=\"%(elgamalaes)s\">ElGamal/AES encryption</a>,\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:282
+#, python-format
+msgid ""
+"Encryption of additional messages to and from the\n"
+"<a href=\"%(netdb)s#delivery\">floodfill routers</a>."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/garlic-routing.html:290
+#: i2p2www/pages/site/docs/how/peer-selection.html:296
+msgid "References"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/garlic-routing.html:292
+msgid ""
+"The term garlic routing was first coined in Roger Dingledine's Free Haven"
+" \n"
+"<a href=\"http://www.freehaven.net/papers.html\">Master's thesis</a> "
+"(June 2000),\n"
+"see Section 8.1.1 authored by\n"
+"<a href=\"http://www.cs.princeton.edu/~mfreed/\">Michael J. Freedman</a>."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/garlic-routing.html:299
+msgid "Onion router publications"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/garlic-routing.html:301
+msgid "Onion Routing on Wikipedia"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/garlic-routing.html:303
+msgid "Garlic Routing on Wikipedia"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/garlic-routing.html:305
+#, python-format
+msgid ""
+"<a href=\"%(meeting58)s\">I2P Meeting 58</a> (2003) discussing the "
+"implementation of garlic routing"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/garlic-routing.html:311
+msgid "Free Haven publications"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/garlic-routing.html:313
+msgid ""
+"Onion routing was first described in <a href=\"http://www.onion-"
+"router.net/Publications/IH-1996.pdf\">Hiding Routing Information</a>\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 to How I2P Works"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/intro.html:4
+msgid ""
+"I2P is a project to build, deploy, and maintain a network supporting "
+"secure and anonymous\n"
+"communication. People using I2P are in control of the tradeoffs between "
+"anonymity, reliability,\n"
+"bandwidth usage, and latency. There is no central point in the network on"
+" which pressure can be\n"
+"exerted to compromise the integrity, security, or anonymity of the "
+"system. The network supports\n"
+"dynamic reconfiguration in response to various attacks, and has been "
+"designed to make use of\n"
+"additional resources as they become available. Of course, all aspects of "
+"the network are open and\n"
+"freely available."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/intro.html:14
+msgid ""
+"Unlike many other anonymizing networks, I2P doesn't try to provide "
+"anonymity by hiding the\n"
+"originator of some communication and not the recipient, or the other way "
+"around. I2P is designed to\n"
+"allow peers using I2P to communicate with each other anonymously &mdash; "
+"both sender and recipient\n"
+"are unidentifiable to each other as well as to third parties. For "
+"example, today there are both\n"
+"in-I2P web sites (allowing anonymous publishing / hosting) as well as "
+"HTTP proxies to the normal web\n"
+"(allowing anonymous web browsing). Having the ability to run servers "
+"within I2P is essential, as it\n"
+"is quite likely that any outbound proxies to the normal Internet will be "
+"monitored, disabled, or\n"
+"even taken over to attempt more malicious attacks."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/intro.html:25
+#, python-format
+msgid ""
+"The network itself is message oriented - it is essentially a secure and "
+"anonymous IP layer, where\n"
+"messages are addressed to cryptographic keys (Destinations) and can be "
+"significantly larger than IP\n"
+"packets. Some example uses of the network include \"eepsites\" "
+"(webservers hosting normal web\n"
+"applications within I2P), a BitTorrent client (\"I2PSnark\"), or a "
+"distributed data store. With the\n"
+"help of the <a href=\"%(i2ptunnel)s\">I2PTunnel</a> application, we are "
+"able to stream traditional\n"
+"TCP/IP applications over I2P, such as SSH, IRC, a squid proxy, and even "
+"streaming audio. Most people\n"
+"will not use I2P directly, or even need to know they're using it. Instead"
+" their view will be of one\n"
+"of the I2P enabled applications, or perhaps as a little controller app to"
+" turn on and off various\n"
+"proxies to enable the anonymizing functionality."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/intro.html:37
+#, python-format
+msgid ""
+"An essential part of designing, developing, and testing an anonymizing "
+"network is to define the <a\n"
+"href=\"%(threatmodel)s\">threat model</a>, 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, <i>all on the same network</i>, where each one's messages are "
+"essentially indistinguishable\n"
+"from the others."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/intro.html:48
+msgid "Why?"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/intro.html:49
+#, python-format
+msgid ""
+"There are a multitude of reasons why we need a system to support "
+"anonymous communication, and\n"
+"everyone has their own personal rationale. There are many <a "
+"href=\"%(comparisons)s\">other\n"
+"efforts</a> 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:56
+msgid "How?"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/intro.html:58
+#, python-format
+msgid ""
+"The network at a glance is made up of a set of nodes (\"routers\") with a"
+" number of unidirectional\n"
+"inbound and outbound virtual paths (\"tunnels\", as outlined on the <a "
+"href=\"%(tunnelrouting)s\">tunnel routing</a> 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"
+"<a href=\"%(netdb)s\">network database</a> (using a modification of the "
+"Kademlia algorithm) for\n"
+"distributing routing and contact information securely."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/intro.html:71
+msgid "Network topology example"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/intro.html:73
+msgid ""
+"In the above, Alice, Bob, Charlie, and Dave are all running routers with "
+"a single Destination on\n"
+"their local router. They each have a pair of 2-hop inbound tunnels per "
+"destination (labeled 1, 2, 3,\n"
+"4, 5 and 6), and a small subset of each of those router's outbound tunnel"
+" pool is shown with 2-hop\n"
+"outbound tunnels. For simplicity, Charlie's inbound tunnels and Dave's "
+"outbound tunnels are not\n"
+"shown, nor are the rest of each router's outbound tunnel pool (typically "
+"stocked with a few tunnels\n"
+"at a time). When Alice and Bob talk to each other, Alice sends a message "
+"out one of her (pink)\n"
+"outbound tunnels targeting one of Bob's (green) inbound tunnels (tunnel 3"
+" or 4). She knows to send\n"
+"to those tunnels on the correct router by querying the network database, "
+"which is constantly updated\n"
+"as new leases are authorized and old ones expire."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/intro.html:85
+#, python-format
+msgid ""
+"If Bob wants to reply to Alice, he simply goes through the same process -"
+" send a message out one of\n"
+"his outbound tunnels targeting one of Alice's inbound tunnels (tunnel 1 "
+"or 2). To make things\n"
+"easier, most messages sent between Alice and Bob are <a "
+"href=\"%(garlicrouting)s\">garlic</a>\n"
+"wrapped, bundling the sender's own current lease information so that the "
+"recipient can reply\n"
+"immediately without having to look in the network database for the "
+"current data."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/intro.html:93
+#, python-format
+msgid ""
+"To deal with a wide range of attacks, I2P is fully distributed with no "
+"centralized resources - and\n"
+"hence there are no directory servers keeping statistics regarding the "
+"performance and reliability of\n"
+"routers within the network. As such, each router must keep and maintain "
+"profiles of various routers\n"
+"and is responsible for selecting appropriate peers to meet the anonymity,"
+" performance, and\n"
+"reliability needs of the users, as described in the <a "
+"href=\"%(peerselection)s\">peer selection</a>\n"
+"page."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/intro.html:102
+#, python-format
+msgid ""
+"The network itself makes use of a significant number of <a "
+"href=\"%(cryptography)s\">cryptographic\n"
+"techniques and algorithms</a> - 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 <a "
+"href=\"%(elgamalaes)s\">ElGamal / AES+SessionTag</a>."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/intro.html:110
+msgid ""
+"Content sent over I2P is encrypted through three layers garlic encryption"
+" (used to verify the\n"
+"delivery of the message to the recipient), tunnel encryption (all "
+"messages passing through a tunnel\n"
+"is encrypted by the tunnel gateway to the tunnel endpoint), and inter "
+"router transport layer\n"
+"encryption (e.g. the TCP transport uses AES256 with ephemeral keys)."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/intro.html:117
+msgid ""
+"End-to-end (I2CP) encryption (client application to server application) "
+"was disabled in I2P release\n"
+"0.6; end-to-end (garlic) encryption (I2P client router to I2P server "
+"router) from Alice's router \"a\"\n"
+"to Bob's router \"h\" remains. Notice the different use of terms! All "
+"data from a to h is end-to-end\n"
+"encrypted, but the I2CP connection between the I2P router and the "
+"applications is not end-to-end\n"
+"encrypted! A and h are the routers of Alice and Bob, while Alice and Bob "
+"in following chart are the\n"
+"applications running atop of I2P."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/intro.html:126
+msgid "End to end layered encryption"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/intro.html:128
+#, python-format
+msgid ""
+"The specific use of these algorithms are outlined <a "
+"href=\"%(cryptography)s\">elsewhere</a>."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/intro.html:132
+msgid ""
+"The two main mechanisms for allowing people who need strong anonymity to "
+"use the network are\n"
+"explicitly delayed garlic routed messages and more comprehensive tunnels "
+"to include support for\n"
+"pooling and mixing messages. These are currently planned for release 3.0,"
+" but garlic routed messages\n"
+"with no delays and FIFO tunnels are currently in place. Additionally, the"
+" 2.0 release will allow\n"
+"people to set up and operate behind restricted routes (perhaps with "
+"trusted peers), as well as the\n"
+"deployment of more flexible and anonymous transports."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/intro.html:141
+#, python-format
+msgid ""
+"Some questions have been raised with regards to the scalability of I2P, "
+"and reasonably so. There\n"
+"will certainly be more analysis over time, but peer lookup and "
+"integration should be bounded by\n"
+"<code>O(log(N))</code> due to the <a href=\"%(netdb)s\">network "
+"database</a>'s algorithm, while end\n"
+"to end messages should be <code>O(1)</code> (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:150
+msgid "When?"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/intro.html:151
+#, python-format
+msgid ""
+"I2P initially began in Feb 2003 as a proposed modification to <a\n"
+"href=\"http://freenetproject.org\">Freenet</a> to allow it to use "
+"alternate transports, such as <a\n"
+"href=\"%(jms)s\">JMS</a>, 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"
+" <a href=\"%(roadmap)s\">roadmap</a>."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/intro.html:161
+msgid "Who?"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/intro.html:162
+#, python-format
+msgid ""
+"We have a small <a href=\"%(team)s\">team</a> 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 <a href=\"http://java.com/en/\">Sun Java SE</a> and other Java Virtual"
+" Machines."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/intro.html:173
+msgid "Where?"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/intro.html:174
+#, python-format
+msgid ""
+"Anyone interested should join us on the IRC channel #i2p-dev (hosted "
+"concurrently on irc.freenode.net,\n"
+"irc.postman.i2p, irc.echelon.i2p, irc.dg.i2p and irc.oftc.net). There are"
+" currently no\n"
+"scheduled development meetings, however <a href=\"%(meetings)s\">archives"
+" are available</a>."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/intro.html:180
+#, python-format
+msgid "The current source is available in <a href=\"%(monotone)s\">monotone</a>."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/intro.html:185
+#, python-format
+msgid "See <a href=\"%(docs)s\">the Index to Technical Documentation</a>."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:2
+msgid "The Network Database"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:3
+msgid "April 2018"
+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 (<b>RouterInfos</b>) "
+"and destination contact\n"
+"information (<b>LeaseSets</b>). 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 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 signing key"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:39
+msgid "Expected Options"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:41
+msgid ""
+"The following text options, while not strictly required, are expected\n"
+"to be present:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:47
+msgid ""
+"Capabilities flags - used to indicate floodfill participation, "
+"approximate bandwidth, and perceived reachability"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:49
+#: i2p2www/pages/site/docs/how/network-database.html:287
+msgid "Floodfill"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:50
+msgid "Hidden"
+msgstr "Skrytý"
+
+#: i2p2www/pages/site/docs/how/network-database.html:51
+#, python-format
+msgid "Under %(amount)s shared bandwidth"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:52
+#: i2p2www/pages/site/docs/how/network-database.html:53
+#: i2p2www/pages/site/docs/how/network-database.html:54
+#: i2p2www/pages/site/docs/how/network-database.html:55
+#: i2p2www/pages/site/docs/how/network-database.html:56
+#, python-format
+msgid "%(amount)s shared bandwidth"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:52
+msgid "default"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:57
+msgid "Reachable"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:58
+msgid "Unreachable"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:59
+#, python-format
+msgid "Over %(amount)s shared bandwidth"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:66
+msgid "The core library version, always the same as the router version"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:70
+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:73
+msgid "Used to determine compatibility with newer features and messages"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:76
+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 uptime was more than 60m"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:82
+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:91
+msgid "Additional Options"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:93
+#, 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 <a href=\"http://%(stats)s/\">%(stats)s</a>\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:104
+msgid "Exploratory tunnel build success, reject, and timeout rates"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:105
+msgid "1 hour average number of participating tunnels"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:108
+msgid ""
+"Floodfill routers publish additional data on the number of entries in "
+"their network database."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:112
+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:119
+msgid "Family Options"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:121
+msgid ""
+"As of release 0.9.24, routers may declare that they are part of a "
+"\"family\", operated by the same entity.\n"
+"Multiple routers in the same family will not be used in a single tunnel."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:126
+msgid "The family options are:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:132
+msgid "The family name"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:147
+msgid "RouterInfo Expiration"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:148
+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:155
+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:158
+msgid "There is no expiration if there are 25 or less RouterInfos."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:161
+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:166
+#, python-format
+msgid ""
+"RouterInfos containing <a href=\"%(ssu)s\">SSU</a> 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:170
+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:176
+msgid "RouterInfo Persistent Storage"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:178
+msgid ""
+"RouterInfos are periodically written to disk so that they are available "
+"after a restart."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:186
+msgid "RouterInfo specification"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:189
+msgid "RouterInfo Javadoc"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:194
+msgid ""
+"The second piece of data distributed in the netDb is a \"LeaseSet\" - "
+"documenting\n"
+"a group of <b>tunnel entry points (leases)</b> for a particular client "
+"destination.\n"
+"Each of these leases specify the following information:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:200
+msgid "The tunnel gateway router (by specifying its identity)"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:201
+msgid "The tunnel ID on that router to send messages with (a 4 byte number)"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:202
+msgid "When that tunnel will expire."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:204
+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:209
+msgid "In addition to these leases, the LeaseSet includes:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:213
+msgid ""
+"The destination itself (a 2048bit ElGamal encryption key, a signing key "
+"and a certificate)"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:214
+msgid ""
+"Additional encryption public key: used for end-to-end encryption of "
+"garlic messages"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:215
+msgid ""
+"Additional signing public key: intended for LeaseSet revocation, but is "
+"currently unused."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:216
+msgid ""
+"Signature of all the LeaseSet data, to make sure the Destination "
+"published the LeaseSet."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:220
+msgid "Lease specification"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:222
+msgid "LeaseSet specification"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:225
+msgid "Lease Javadoc"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:227
+msgid "LeaseSet Javadoc"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:231
+msgid "Unpublished LeaseSets"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:232
+msgid ""
+"A LeaseSet for a destination used only for outgoing connections is "
+"<i>unpublished</i>.\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 <a href=\"#lsp\">I2NP storage messages</a>."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:242
+msgid "Revoked LeaseSets"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:243
+msgid ""
+"A LeaseSet may be <i>revoked</i> 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:250
+msgid "Encrypted LeaseSets"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:251
+msgid ""
+"In an <i>encrypted</i> LeaseSet, all Leases are encrypted with a separate"
+" 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:260
+msgid "LeaseSet Expiration"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:261
+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:266
+msgid "LeaseSet Persistent Storage"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:267
+msgid ""
+"There is no persistent storage of LeaseSet data since they expire so "
+"quickly."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:272
+msgid "Bootstrapping"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:273
+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 "
+"<code>routerInfo-$hash.dat</code>\n"
+"file and storing it in your <code>netDb/</code> 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:288
+msgid ""
+"The floodfill netDb is a simple distributed storage mechanism.  The "
+"storage\n"
+"algorithm is simple: send the data to the closest peer that has "
+"advertised\n"
+"itself as a floodfill router. When the peer in the floodfill netDb "
+"receives a\n"
+"netDb store from a peer not in the floodfill netDb, they send it to a "
+"subset of\n"
+"the floodfill netDb-peers. The peers selected are the ones closest "
+"(according\n"
+"to the <a href=\"#kad\">XOR-metric</a>) to a specific key."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:297
+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:302
+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:309
+msgid "Floodfill Router Opt-in"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:311
+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:318
+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:328
+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:334
+msgid ""
+"With the current rules for automatic opt-in, approximately 6&#37; of\n"
+"the routers in the network are floodfill routers."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:339
+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:349
+msgid "Floodfill Router Roles"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:350
+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:358
+msgid "Kademlia Closeness Metric"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:359
+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 <a href"
+"=\"#sybil-partial\">Sybil attacks</a>.\n"
+"Instead of the SHA256 hash of the key being looked up of stored, the "
+"SHA256 hash is taken\n"
+"of the 32-byte binary search key appended with the UTC date represented "
+"as an 8-byte ASCII string yyyyMMdd, i.e. SHA256(key + yyyyMMdd).\n"
+"This is called the \"routing key\", and it changes every day at midnight "
+"UTC.\n"
+"Only the search key is modified in this way, not the floodfill router "
+"hashes.\n"
+"The daily transformation of the DHT is sometimes called \"keyspace "
+"rotation\",\n"
+"although it isn't strictly a rotation."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:372
+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:379
+msgid "Storage, Verification, and Lookup Mechanics"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:381
+msgid "RouterInfo Storage to Peers"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:382
+#, python-format
+msgid ""
+"<a href=\"%(i2np)s\">I2NP</a> DatabaseStoreMessages containing the local "
+"RouterInfo are exchanged with peers\n"
+"as a part of the initialization of a <a href=\"%(ntcp)s\">NTCP</a>\n"
+"or <a href=\"%(ssu)s\">SSU</a> transport connection."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:389
+msgid "LeaseSet Storage to Peers"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:390
+#, python-format
+msgid ""
+"<a href=\"%(i2np)s\">I2NP</a> 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:398
+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:407
+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:420
+msgid "RouterInfo Storage to Floodfills"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:421
+#, python-format
+msgid ""
+"A router publishes its own RouterInfo by directly connecting to a "
+"floodfill router\n"
+"and sending it a <a href=\"%(i2np)s\">I2NP</a> 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"
+"<a href=\"%(i2np)s\">I2NP</a> DeliveryStatusMessage,\n"
+"with the Message ID set to the value of the Reply Token."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:435
+msgid "LeaseSet Storage to Floodfills"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:436
+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:441
+#, python-format
+msgid ""
+"A router publishes a local LeaseSet by\n"
+"sending a <a href=\"%(i2np)s\">I2NP</a> 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"
+"<a href=\"%(i2np)s\">I2NP</a> 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:454
+msgid "Flooding"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:455
+#, 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:466
+#, python-format
+msgid ""
+"The floodfill then directly connects to each of those peers\n"
+"and sends it a <a href=\"%(i2np)s\">I2NP</a> 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:476
+msgid "RouterInfo and LeaseSet Lookup"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:477
+#, python-format
+msgid ""
+"The <a href=\"%(i2np)s\">I2NP</a> 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:483
+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:487
+#, python-format
+msgid ""
+"If the key is found locally by the floodfill router, it responds with a\n"
+"<a href=\"%(i2np)s\">I2NP</a> DatabaseStoreMessage.\n"
+"If the key is not found locally by the floodfill router, it responds with"
+" a\n"
+"<a href=\"%(i2np)s\">I2NP</a> DatabaseSearchReplyMessage\n"
+"containing a list of other floodfill routers close to the key."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:495
+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:502
+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:509
+#, python-format
+msgid ""
+"(Reference: <a href=\"%(pdf)s\">Hashing it out in Public</a> Sections "
+"2.2-2.3 for terms below in italics)"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:513
+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 <i>recursive</i> nor <i>iterative</i> routing for lookups was "
+"implemented.\n"
+"Queries were sent through <i>multiple routes simultaneously</i>\n"
+"to <i>reduce the chance of query failure</i>."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:524
+msgid ""
+"As of release 0.8.9, <i>iterative lookups</i> 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:536
+msgid ""
+"<i>Node IDs</i> are <i>verifiable</i> 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"
+"<i>detailed knowledge of the neighborhood of the destination ID space</i>."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:545
+msgid "RouterInfo Storage Verification"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:546
+#, 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"
+"<a href=\"%(egger2013)s\">Practical Attacks Against the I2P Network</a>.\n"
+"It is not clear if verification can be redesigned to be done safely."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:553
+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:561
+msgid "LeaseSet Storage Verification"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:562
+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:572
+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:580
+msgid "Exploration"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:581
+#, python-format
+msgid ""
+"<i>Exploration</i> 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 <a "
+"href=\"%(i2np)s\">I2NP</a> DatabaseLookupMessage, looking for a random "
+"key.\n"
+"As this lookup will fail, the floodfill would normally respond with a\n"
+"<a href=\"%(i2np)s\">I2NP</a> 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:595
+msgid "Notes on Lookup Responses"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:596
+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:606
+msgid "MultiHoming"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:608
+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:618
+msgid "Threat Analysis"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:619
+#, python-format
+msgid ""
+"Also discussed on <a href=\"%(threatmodel)s#floodfill\">the threat model "
+"page</a>."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:623
+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:630
+msgid "General Mitigation Through Growth"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:631
+#, 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:638
+msgid "General Mitigation Through Redundancy"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:639
+#, 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:644
+msgid "Forgeries"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:645
+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:650
+msgid "Slow or Unresponsive"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:651
+#, python-format
+msgid ""
+"Each router maintains an expanded set of statistics in the\n"
+"<a href=\"%(peerselection)s\">peer profile</a> 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:658
+msgid "Average response time"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:659
+msgid "Percentage of queries answered with the data requested"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:660
+msgid "Percentage of stores that were successfully verified"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:661
+msgid "Last successful store"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:662
+msgid "Last successful lookup"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:663
+msgid "Last response"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:666
+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:676
+msgid "Sybil Attack (Full Keyspace)"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:677
+#, python-format
+msgid ""
+"An attacker may mount a <a href=\"%(url)s\">Sybil attack</a>\n"
+"by creating a large number of floodfill routers spread throughout the "
+"keyspace."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:682
+#, python-format
+msgid ""
+"(In a related example, a researcher recently created a\n"
+"<a href=\"%(url)s\">large number of Tor relays</a>.)\n"
+"If successful, this could be an effective DOS attack on the entire "
+"network."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:688
+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:696
+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:701
+msgid ""
+"Ask everyone in the network to enable floodfill manually (fight Sybil "
+"with more Sybil)"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:702
+msgid "Release a new software version that includes the hardcoded \"bad\" list"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:703
+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:707
+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:708
+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:717
+msgid "This attack becomes more difficult as the network size grows."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:723
+msgid "Sybil Attack (Partial Keyspace)"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:724
+#, python-format
+msgid ""
+"An attacker may mount a <a href=\"%(url)s\">Sybil attack</a>\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:733
+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:741
+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:753
+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:761
+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:771
+msgid "Bootstrap Attacks"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:772
+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:779
+msgid "Several defenses are possible, and most of these are planned:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:783
+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:787
+msgid "Bundling reseed data in the installer"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:790
+msgid "Defenses that are implemented:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:794
+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:798
+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:803
+msgid ""
+"As of release 0.9.14, reseed data is bundled into a signed zip file and\n"
+"the signature is verified when downloaded."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:811
+msgid "Query Capture"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:812
+#, python-format
+msgid ""
+"See also <a href=\"#lookup\">lookup</a>\n"
+"(Reference: <a href=\"%(pdf)s\">Hashing it out in Public</a> Sections "
+"2.2-2.3 for terms below in italics)"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:817
+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:822
+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:829
+#, python-format
+msgid ""
+"As of release 0.8.9, <i>iterative lookups</i> are implemented.\n"
+"For floodfill router references returned in a\n"
+"<a href=\"%(i2np)s\">I2NP</a> 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 <i>verifiably correct</i>.\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"
+"<a href=\"%(pdf)s\">Hashing it out in Public</a>\n"
+"is much more difficult."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:848
+msgid "DHT-Based Relay Selection"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:849
+#, python-format
+msgid "(Reference: <a href=\"%(pdf)s\">Hashing it out in Public</a> Section 3)"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:853
+#, python-format
+msgid ""
+"This doesn't have much to do with floodfill, but see\n"
+"the <a href=\"%(peerselection)s\">peer selection page</a>\n"
+"for a discussion of the vulnerabilities of peer selection for tunnels."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:859
+msgid "Information Leaks"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:860
+#, python-format
+msgid ""
+"(Reference: <a href=\"%(pdf)s\">In Search of an Anonymous and Secure "
+"Lookup</a> Section 3)"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:864
+#, 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 <a href=\"%(peerselection)s\">peer "
+"selection</a> and\n"
+"<a href=\"%(tunnelrouting)s\">tunnel building</a> 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:875
+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:883
+#, 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 <i>f</i> = 0.2 (20&#37; malicious nodes, as "
+"specifed in the paper)\n"
+"we expect that many of the Sybil threats we describe\n"
+"(<a href=\"%(threatmodel)s#sybil\">here</a>,\n"
+"<a href=\"#sybil\">here</a> and\n"
+"<a href=\"#sybil-partial\">here</a>)\n"
+"become problematic for several reasons."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:897
+msgid "Moved to the netdb discussion page"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:901
+msgid "End-to-end encryption of additional netDb lookups and responses."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/network-database.html:905
+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 ""
+"<b>Peer profiling</b> is the process of collecting data based on the "
+"<b>observed</b> performance\n"
+"of other routers or peers, and classifying those peers into groups.\n"
+"Profiling does <b>not</b> use any claimed performance data published by "
+"the peer itself\n"
+"in the <a href=\"%(netdb)s\">network database</a>."
+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 <a href=\"%(netdb)s\">network database</a> 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:289
+msgid "Peer Selection"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/peer-selection.html:28
+msgid ""
+"<b>Peer selection</b> 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 <b>only</b> 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"
+"<a href=\"%(threatmodel)s#timing\">timing attacks</a>\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"
+"<a href=\"%(pdf)s\">Peer Profiling and Selection in the I2P Anonymous "
+"Network</a>\n"
+"presented at <a href=\"%(url)s\">PET-CON 2009.1</a>.\n"
+"See <a href=\"#notes\">below</a> 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 <a href=\"%(url)s\">code</a>."
+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"
+"<a href=\"%(url)s\">ProfileOrganizer</a>."
+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 <a href=\"http://blog.torproject.org/blog"
+"/one-cell-enough\">some attacks</a>,\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&#37; 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 <a href=\"%(pdf)s\">predecessor attack</a>\n"
+"<a href=\"%(pdf2008)s\">(2008 update)</a>.\n"
+"More information is on the <a href=\"%(tunnelimpl)s#ordering\">tunnel "
+"page</a>."
+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"
+"<a href=\"%(pdf)s\">Peer Profiling and Selection in the I2P Anonymous "
+"Network</a>,\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 "I2P: A scalable framework for anonymous communication"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:5
+#: i2p2www/pages/site/docs/how/tech-intro.html:20
+#: i2p2www/pages/site/docs/transport/ssu.html:342
+msgid "Introduction"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:7
+msgid "I2P Operation"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:12
+#: i2p2www/pages/site/docs/how/tech-intro.html:397
+msgid "Transport protocols"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:13
+#: i2p2www/pages/site/docs/how/tech-intro.html:454
+msgid "Cryptography"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:21
+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:30
+msgid ""
+"Applications available already provide the full range of typical Internet"
+" activities -\n"
+"<b>anonymous</b> 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:36
+msgid "Web browsing: using any existing browser that supports using a proxy."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:37
+msgid "Chat: IRC, Jabber, <a href=\"#app.i2pmessenger\">I2P-Messenger</a>."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:38
+msgid ""
+"File sharing: <a href=\"#app.i2psnark\">I2PSnark</a>, <a "
+"href=\"#app.robert\">Robert</a>, <a href=\"#app.imule\">iMule</a>, \n"
+"<a href=\"#app.i2phex\">I2Phex</a>, <a href=\"#app.pybit\">PyBit</a>, <a "
+"href=\"#app.i2pbt\">I2P-bt</a>\n"
+"and others."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:43
+msgid ""
+"E-mail: <a href=\"#app.i2pmail\">susimail</a> and <a href=\"#app.i2pbote"
+"\">I2P-Bote</a>."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:44
+msgid ""
+"Blog: using e.g. the pebble plugin or the distributed blogging software "
+"<a href=\"#app.syndie\">Syndie</a>."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:45
+msgid ""
+"Distributed Data Store: Save your data redundantly in the Tahoe-LAFS "
+"cloud over I2P."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:46
+msgid "Newsgroups: using any newsgroup reader that supports using a proxy."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:49
+msgid ""
+"Unlike web sites hosted within content distribution networks like <a "
+"href=\"#similar.freenet\">Freenet</a> \n"
+"or <a href=\"http://www.ovmj.org/GNUnet/\">GNUnet</a>, 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:57
+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 <a href=\"#app.streaming\">streaming</a> 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:74
+#, 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 <a "
+"href=\"%(site)s\">website</a>, \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 (<a "
+"href=\"#app.i2ptunnel\">I2PTunnel</a>, \n"
+"<a href=\"#app.i2pmail\">susimail</a>, <a "
+"href=\"#app.i2psnark\">I2PSnark</a>, <a href=\"#app.i2pbote\">I2P-"
+"Bote</a>, \n"
+"<a href=\"#app.i2phex\">I2Phex</a> and others.).\n"
+"<a href=\"%(halloffame)s\">Funding</a> 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:92
+msgid "Operation"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:94
+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:107
+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:118
+#: i2p2www/pages/site/docs/tunnels/implementation.html:105
+msgid "Inbound and outbound tunnel schematic"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:120
+msgid "Figure 1: Two types of tunnels exist: inbound and outbound."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:123
+msgid ""
+"Two types of tunnels exist:\n"
+"<b>\"outbound\" tunnels</b> send messages away from the tunnel creator,\n"
+"while <b>\"inbound\" tunnels</b> 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:140
+msgid ""
+"A third critical concept to understand is I2P's <b>\"network "
+"database\"</b> (or \"netDb\") \n"
+"- a pair of algorithms used to share network metadata. The two types of "
+"metadata \n"
+"carried are <b>\"routerInfo\"</b> and <b>\"leaseSets\"</b> - 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:151
+msgid "Inbound gateway for a tunnel that allows reaching a specific destination."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:152
+msgid "Time when a tunnel expires."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:153
+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:155
+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:160
+msgid ""
+"We can combine the above concepts to build successful connections in the "
+"network."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:164
+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:171
+msgid "Request information on other routers"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:173
+msgid "Build tunnel using router information"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:175
+msgid "Figure 2: Router information is used to build tunnels."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:178
+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"
+"<a href=\"#app.streaming\">streaming</a> 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:195
+msgid "Connect tunnels using LeaseSets"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:195
+msgid "Connect tunnels using leaseSets"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:197
+msgid "Figure 3: LeaseSets are used to connect outbound and inbound tunnels."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:200
+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 \"<a "
+"href=\"#op.garlic\">garlic \n"
+"encryption</a>\" 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:215
+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 <a href=\"#app.streaming\">streaming</a> library to view I2P as "
+"a streams \n"
+"based network."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:225
+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:240
+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:253
+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:266
+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:284
+msgid ""
+"Using this profile data, the simplest reasonable peer selection strategy "
+"is to\n"
+"pick peers randomly from the top tier (fast and high capacity), and this "
+"is\n"
+"currently deployed for client tunnels. Exploratory tunnels (used for "
+"netDb and\n"
+"tunnel management) pick peers randomly from the \"not failing\" tier "
+"(which\n"
+"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"
+"<a href=\"https://en.wikipedia.org/wiki/Hill_climbing\">hill "
+"climbing</a>. These\n"
+"strategies alone do however leak information regarding the peers in the\n"
+"router's top tier through predecessor and netDb harvesting attacks. In "
+"turn,\n"
+"several alternatives exist which, while not balancing the load as evenly,"
+" will\n"
+"address the attacks mounted by particular classes of adversaries."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:298
+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:318
+#, 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 <a href=\"%(tunnelimpl)s\">tunnel "
+"spec</a>."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:326
+#, python-format
+msgid ""
+"As mentioned earlier, I2P's netDb works to share the network's metadata.\n"
+"This is detailed in <a href=\"%(netdb)s\">the network database</a> page,\n"
+"but a basic explanation is available below."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:332
+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:339
+#, 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 <a href=\"http://en.wikipedia.org/wiki/Kademlia\">Kademlia "
+"algorithm</a>.\n"
+"The 'lookup' queries currently function differently, to avoid an "
+"important\n"
+"<a href=\"%(netdb)s#lookup\">security issue</a>.\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:349
+msgid "Two types of information are stored in the network database."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:353
+msgid ""
+"A <b>RouterInfo</b> stores information on a specific I2P router and how "
+"to contact it"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:354
+msgid ""
+"A <b>LeaseSet</b> stores information on a specific destination (e.g. I2P "
+"website, e-mail server...)"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:356
+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 <a href=\"http://www.pool.ntp.org/\">pool.ntp.org</a> round robin by"
+" default)\n"
+"and detecting skew between routers at the transport layer."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:364
+msgid "Some additional remarks are also important."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:369
+msgid "Unpublished and encrypted leasesets:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:370
+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:377
+msgid "Bootstrapping:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:378
+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:386
+msgid "Lookup scalability:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:387
+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:398
+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:406
+#, 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 <a href=\"%(ssu)s\">UDP-based one</a> - "
+"\"Secure \n"
+"Semireliable UDP\", or \"SSU\"."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:414
+#, python-format
+msgid "As described in the <a href=\"%(ssu)s\">SSU spec</a>:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:418
+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:428
+#, python-format
+msgid ""
+"Following the introduction of SSU, after issues with congestion collapse"
+" \n"
+"appeared, a new NIO-based TCP transport called <a "
+"href=\"%(ntcp)s\">NTCP</a> \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:438
+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:446
+#, 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 <a "
+"href=\"%(ntcp)s\">NTCP \n"
+"page</a>."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:455
+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. <a href=\"#op.tunnels\">Tunnel</a> 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:470
+msgid "Garlic messages"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:471
+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:486
+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 <a "
+"href=\"#future.variablelatency\">nontrivial \n"
+"delays</a> 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:499
+msgid "Session tags"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:500
+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:539
+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:549
+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:562
+msgid "Future"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:563
+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:569
+msgid "Restricted route operation"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:570
+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:582
+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:595
+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:617
+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:629
+msgid "Variable latency"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:630
+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:647
+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:655
+msgid "Open questions"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:657
+msgid "How to get rid of the timing constraint?"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:658
+msgid "Can we deal with the sessionTags more efficiently?"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:659
+msgid ""
+"What, if any, batching/mixing strategies should be made available on the "
+"tunnels?"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:660
+msgid ""
+"What other tunnel peer selection and ordering strategies should be "
+"available?"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:663
+msgid "Similar systems"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:665
+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:675
+#, python-format
+msgid "See also the <a href=\"%(comparisons)s\">Network Comparisons Page</a>."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:680
+#: i2p2www/pages/site/docs/how/tech-intro.html:745
+msgid "website"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:682
+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:703
+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:717
+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:727
+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 <a href=\"#future.restricted\">2.0</a>."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:733
+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:747
+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:766
+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:777
+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:793
+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 <a href=\"#app.streaming\">streaming"
+" library</a> \n"
+"as an implementation of an anonymous and secure TCP layer on top of it. "
+"Beyond \n"
+"that, <a href=\"#app.i2ptunnel\">I2PTunnel</a> 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:804
+msgid "Streaming library"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:805
+msgid ""
+"The I2P streaming library can be viewed as a generic streaming interface "
+"(mirroring TCP sockets),\n"
+"and the implementation supports a <a "
+"href=\"http://en.wikipedia.org/wiki/Sliding_Window_Protocol\">sliding "
+"window protocol</a>\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:815
+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:828
+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:835
+msgid "Naming library and addressbook"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:836
+#, python-format
+msgid ""
+"For more information see the <a href=\"%(naming)s\">Naming and "
+"Addressbook</a> page."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:840
+#: i2p2www/pages/site/docs/how/tech-intro.html:914
+#: i2p2www/pages/site/docs/how/tech-intro.html:961
+#: i2p2www/pages/site/docs/how/tech-intro.html:993
+#: i2p2www/pages/site/docs/how/tech-intro.html:1001
+#: i2p2www/pages/site/docs/how/tech-intro.html:1009
+#: i2p2www/pages/site/docs/how/tech-intro.html:1019
+#: i2p2www/pages/site/docs/how/tech-intro.html:1027
+#: i2p2www/pages/site/docs/how/tech-intro.html:1049
+#, python-format
+msgid "Developed by: %(dev)s"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:842
+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:862
+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:876
+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:886
+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:895
+msgid ""
+"The old Syndie bundled with I2P has been replaced by the new Syndie which"
+"\n"
+"is distributed separately. For more information see the <a "
+"href=\"http://syndie.i2p2.de/\">Syndie</a>\n"
+"pages."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:901
+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:916
+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:930
+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:946
+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 <a "
+"href=\"#app.i2pmail\">I2Pmail's</a> \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:963
+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 <a href=\"#app.streaming\">streaming lib</a> connection to query them "
+"for \n"
+"blocks."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:972
+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:980
+msgid ""
+"I2PSnark developed: jrandom, et al, ported from <a\n"
+"href=\"http://www.klomp.org/mark/\">mjw</a>'s <a\n"
+"href=\"http://www.klomp.org/snark/\">Snark</a> client"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:986
+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:995
+#, python-format
+msgid ""
+"Robert is a Bittorrent client written in Python.\n"
+"It is hosted on <a "
+"href=\"http://%(bob)s/Robert.html\">http://%(bob)s/Robert.html</a> <!-- "
+"TODO: expand -->"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:1003
+#, python-format
+msgid ""
+"PyBit is a Bittorrent client written in Python.\n"
+"It is hosted on <a href=\"%(pybit)s\">%(pybit)s</a> <!-- TODO: expand -->"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:1011
+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:1021
+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:1029
+#, 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"
+"<a href=\"http://%(postman)s/\">%(postman)s</a>."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tech-intro.html:1051
+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. <br>\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:1061
+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:93
+msgid "Priority"
+msgstr "Priorita"
+
+#: i2p2www/pages/site/docs/how/threat-model.html:45
+msgid "Index of Attacks"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:47
+#: i2p2www/pages/site/docs/how/threat-model.html:206
+msgid "Brute force attacks"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:48
+#: i2p2www/pages/site/docs/how/threat-model.html:250
+msgid "Timing attacks"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:49
+#: i2p2www/pages/site/docs/how/threat-model.html:287
+msgid "Intersection attacks"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:50
+#: i2p2www/pages/site/docs/how/threat-model.html:367
+msgid "Denial of service attacks"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:51
+#: i2p2www/pages/site/docs/how/threat-model.html:466
+msgid "Tagging attacks"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:52
+#: i2p2www/pages/site/docs/how/threat-model.html:484
+msgid "Partitioning attacks"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:53
+#: i2p2www/pages/site/docs/how/threat-model.html:524
+msgid "Predecessor attacks"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:54
+#: i2p2www/pages/site/docs/how/threat-model.html:569
+msgid "Harvesting attacks"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:55
+#: i2p2www/pages/site/docs/how/threat-model.html:616
+msgid "Identification Through Traffic Analysis"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:56
+#: i2p2www/pages/site/docs/how/threat-model.html:676
+msgid "Sybil attacks"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:57
+#: i2p2www/pages/site/docs/how/threat-model.html:725
+msgid "Buddy Exhaustion attacks"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:58
+#: i2p2www/pages/site/docs/how/threat-model.html:750
+msgid "Cryptographic attacks"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:59
+msgid "Floodfill attacks"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:60
+#: i2p2www/pages/site/docs/how/threat-model.html:811
+msgid "Other Network Database attacks"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:61
+msgid "Attacks on centralized resources"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:62
+#: i2p2www/pages/site/docs/how/threat-model.html:877
+msgid "Development attacks"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:63
+msgid "Implementation attacks"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:64
+#: i2p2www/pages/site/docs/how/threat-model.html:961
+msgid "Other Defenses"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:69
+msgid "What do we mean by \"anonymous\"?"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:71
+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:82
+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:89
+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:95
+msgid "Network Topology Summary"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:96
+#, python-format
+msgid ""
+"I2P builds off the ideas of many <a href=\"%(comparisons)s\">other</a> \n"
+"<a href=\"%(links)s\">systems</a>, but a few key points should be kept in"
+" mind when \n"
+"reviewing related literature:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:102
+msgid ""
+"<b>I2P is a free route mixnet</b> - 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:108
+msgid ""
+"<b>I2P has no official entry and exit points</b> - 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:113
+msgid ""
+"<b>I2P is fully distributed</b> - 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:123
+#, python-format
+msgid ""
+"We have documented plans to implement <a "
+"href=\"%(todo)s#stop\">nontrivial delays</a>\n"
+"and <a href=\"%(todo)s#batching\">batching strategies</a> \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:134
+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:141
+msgid "The Threat Model"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:142
+msgid ""
+"I2P design started in 2003, not long after the advent of\n"
+"<a href=\"http://www.onion-router.net\">[Onion Routing]</a>,\n"
+"<a href=\"http://freenetproject.org/\">[Freenet]</a>, and\n"
+"<a href=\"https://www.torproject.org/\">[Tor]</a>.\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:152
+msgid ""
+"Taking from the attacks and analysis put forth in the \n"
+"<a href=\"http://freehaven.net/anonbib/topic.html\">anonymity "
+"literature</a> (largely \n"
+"<a href=\"http://citeseer.ist.psu.edu/454354.html\">Traffic Analysis: "
+"Protocols, Attacks, Design \n"
+"Issues and Open Problems</a>), 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:161
+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:167
+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:177
+#, python-format
+msgid ""
+"The\n"
+"<a href=\"%(comparisons)s\">network comparisons</a> and\n"
+"<a href=\"%(garlicrouting)s\">\"garlic\" terminology</a> pages may also "
+"be helpful\n"
+"to review."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:210
+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:222
+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"
+"<a "
+"href=\"http://citeseer.ist.psu.edu/freedman02tarzan.html\">Tarzan</a>'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:239
+#, 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"
+"<a href=\"%(peerselection)s\">peer selection page</a>."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:254
+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:264
+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:274
+#, 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 <a href=\"%(todo)s#stop\">nontrivial "
+"delays</a> or \n"
+"<a href=\"%(todo)s#batching\">batching strategies</a>), include protocol "
+"scrubbing, or\n"
+"other advanced tunnel routing <a "
+"href=\"%(todo)s#batching\">techniques</a>,\n"
+"but these are unimplemented in I2P."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:283
+#, python-format
+msgid ""
+"References: <a href=\"%(pdf)s\">Low-Resource Routing Attacks Against "
+"Anonymous Systems</a>"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:291
+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:301
+#, 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 <a href=\"%(url)s\">similar disclaimer</a>."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:309
+msgid "Partial defenses implemented in I2P:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:313
+#, python-format
+msgid "<a href=\"%(tunnelimpl)s#ordering\">strict ordering</a> of peers"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:316
+#, python-format
+msgid ""
+"<a href=\"%(peerselection)s\">peer profiling and selection</a> from a "
+"small group that changes slowly"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:319
+msgid "Limits on the number of tunnels routed through a single peer"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:322
+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:325
+msgid ""
+"For eepsites or other hosted services, we support\n"
+"simultaneous hosting on multiple routers, or\n"
+"<a href=\"#intersection\">multihoming</a>"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:332
+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:337
+msgid "We do not use low-bandwidth \"guard nodes\""
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:340
+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:343
+msgid "Tunnels are not long-lived; new tunnels are built every 10 minutes."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:346
+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:353
+#, python-format
+msgid ""
+"In the future, it could\n"
+"for peers who can afford significant delays (per <a "
+"href=\"%(todo)s#stop\">nontrivial\n"
+"delays</a> and <a href=\"%(todo)s#batching\">batching strategies</a>).  "
+"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.</p>"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:362
+#, python-format
+msgid "Reference: <a href=\"%(oce)s\">One Cell Enough</a>"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:369
+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:375
+msgid ""
+"<b>Greedy user attack:</b> 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:381
+#, 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"
+"<a href=\"%(comparisons)s\">other networks</a>,\n"
+"over 95&#37; of I2P users relay traffic for others."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:387
+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:392
+msgid ""
+"Maintain a strong community with blogs, forums, IRC, and other means of "
+"communication."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:399
+#, python-format
+msgid ""
+"<b>Starvation attack:</b> 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 <a "
+"href=\"%(peerselection)s\">profiles</a> 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:419
+#, python-format
+msgid ""
+"<b>Flooding attack:</b> 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 <a "
+"href=\"%(todo)s#batching\">advanced tunnel\n"
+"operation</a> is implemented)."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:438
+msgid ""
+"<b>CPU load attack:</b> 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:451
+#, python-format
+msgid ""
+"<b>Floodfill DOS attack:</b> 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"
+"<a href=\"%(peerselection)s\">peer profiling</a> are implemented,\n"
+"however there is much more to do.\n"
+"For more information see the\n"
+"<a href=\"%(netdb)s#threat\">network database page</a>."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:470
+#, 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 <a href=\"%(todo)s#tunnelId\">unique hop ids</a> 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:488
+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:504
+#, 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 <a href=\"#harvesting\">harvesting</a>"
+" 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 <a href=\"%(todo)s#stop\">nontrivial "
+"delays</a> and \n"
+"<a href=\"%(todo)s#batching\">batching strategies</a>, 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:520
+#, python-format
+msgid ""
+"Also discussed on the <a href=\"%(netdb)s#threat\">network database "
+"page</a> (bootstrap attack)."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:528
+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:538
+#, 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 <a href=\"%(peerselection)s\">peer selection</a> algorithm which "
+"breaks them\n"
+"into tiers.  Second, with <a href=\"%(tunnelimpl)s#ordering\">strict "
+"ordering</a> 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 <a href=\"%(tunnelimpl)s#length\">permuted "
+"tunnel length</a>\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"
+"<a href=\"%(todo)s#fullRestrictedRoutes\">restricted routes</a> "
+"(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:555
+#, python-format
+msgid ""
+"The current <a href=\"%(tunnelcreation)s\">tunnel build method</a>\n"
+"was specifically designed to combat the predecessor attack.\n"
+"See also <a href=\"#intersection\">the intersection attack</a>."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:561
+#, python-format
+msgid ""
+"References: <a href=\"%(pdf2008)s\">%(pdf2008)s</a>\n"
+"which is an update to the 2004 predecessor attack paper\n"
+"<a href=\"%(pdf2004)s\">%(pdf2004)s</a>."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:573
+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:580
+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:587
+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:590
+msgid "Floodfill routers implement query limits as DOS protection"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:593
+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:599
+#, python-format
+msgid ""
+"In future implementations,\n"
+"<a href=\"%(todo)s#nat\">basic</a> and \n"
+"<a href=\"%(todo)s#fullRestrictedRoutes\">comprehensive</a> 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:608
+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:620
+#, 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 <a href=\"#harvesting\">above</a>, 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"
+"<a href=\"%(transport)s\">transport layer and protocols</a>\n"
+"make it somewhat difficult to identify I2P traffic:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:630
+msgid "Random port selection"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:633
+msgid "Point-to-Point Encryption of all traffic"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:636
+msgid ""
+"DH key exchange with no protocol bytes or other unencrypted constant "
+"fields"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:639
+#, python-format
+msgid ""
+"Simultaneous use of both\n"
+"<a href=\"%(ntcp)s\">TCP</a> and\n"
+"<a href=\"%(ssu)s\">UDP</a> 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:647
+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:651
+msgid ""
+"Padding at the transport layer to random lengths, especially during the "
+"connection handshake"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:654
+msgid ""
+"Study of packet size distribution signatures, and additional padding as "
+"necessary"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:657
+msgid ""
+"Development of additional transport methods that mimic SSL or other "
+"common protocols"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:660
+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:663
+msgid ""
+"Review of methods implemented by various state-level firewalls to block "
+"Tor"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:666
+msgid "Working directly with DPI and obfuscation experts"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:671
+#, python-format
+msgid ""
+"Reference: <a href=\"%(pdf)s\">Breaking and Improving Protocol "
+"Obfuscation</a>"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:680
+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&#37; 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' - <a "
+"href=\"http://www.pdos.lcs.mit.edu/tarzan/\">Tarzan</a>\n"
+"(among others) uses the fact that IP addresses are limited, while \n"
+"IIP used \n"
+"<a href=\"http://www.hashcash.org/\">HashCash</a> 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:698
+msgid "Requiring HashCash Certificates in various places has two major problems:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:702
+msgid "Maintaining backward compatibility"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:705
+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:712
+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:719
+#, python-format
+msgid ""
+"See the <a href=\"%(netdb)s#threat\">network database page</a>\n"
+"for more Sybil discussion."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:729
+#, python-format
+msgid ""
+"(Reference: <a href=\"%(pdf)s\">In Search of an Anonymous and Secure "
+"Lookup</a> Section 5.2)"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:733
+#, 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 <a href=\"#sybil\">Sybil attack</a>.\n"
+"This is somewhat mitigated by our\n"
+"<a href=\"%(peerselection)s\">peer profiling</a> methods used to monitor "
+"the performance\n"
+"of peers.\n"
+"However, this is a powerful attack as the number of routers approaches\n"
+"<i>f</i> = 0.2, or 20&#37; 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:754
+#, 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"
+"<a href=\"%(cryptography)s\">on the low-level cryptography page</a>. \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 <a href=\"https://torproject.org/\">other anonymity "
+"networks</a>.\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:773
+#, 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"
+"<a href=\"%(cryptography)s\">major undertaking</a>, just as it will be "
+"for \n"
+"<a href=\"https://torproject.org/\">others</a>.\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:782
+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:792
+msgid "Floodfill Anonymity attacks"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:796
+#, python-format
+msgid ""
+"In addition to the floodfill DOS attacks described\n"
+"<a href=\"#ffdos\">above</a>, 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 <a href=\"%(netdb)s#threat\">network database page</a>.\n"
+"The specific mechanisms by which routers communicate with floodfills have"
+" been\n"
+"<a href=\"%(netdb)s#delivery\">carefully designed</a>.\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:812
+#, 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"
+"<a href=\"%(netdb)s#threat\">network database page</a>."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:822
+msgid "Central Resource Attacks"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:826
+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:836
+#, python-format
+msgid ""
+"The <a href=\"%(site)s\">website</a> is mirrored and uses DNS round-robin"
+" for external public access."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:839
+#, python-format
+msgid ""
+"Routers now support <a href=\"%(faq)s#reseed\">multiple external reseed "
+"locations</a>,\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:844
+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:848
+msgid "Routers now support multiple default trusted update signers."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:851
+msgid ""
+"Routers now better handle <a href=\"#ffdos\">multiple unreliable "
+"floodfill peers</a>.\n"
+"Malicious floodfills <a href=\"#ffdos\">needs</a> <a "
+"href=\"#floodfill\">more</a> study."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:855
+#, python-format
+msgid ""
+"The code is now stored in a <a href=\"%(monotone)s\">distributed source "
+"control system</a>."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:858
+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:862
+#, python-format
+msgid ""
+"<a href=\"%(naming)s\">Naming system services</a>, 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"
+"<a href=\"%(naming)s\">the naming page</a> for details."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:869
+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:881
+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:890
+msgid "However, two techniques help defend against these attacks:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:894
+#, 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 <a href=\"%(monotone)s\">distributed source control "
+"system</a>\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:902
+#, 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 <a href=\"%(monotone)s\">distributed source control system</a>,\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:913
+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:918
+msgid "Implementation attacks (bugs)"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:922
+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"
+"<a href=\"http://www.haystacknetwork.com/\">security through "
+"obscurity</a>."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:933
+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:943
+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:949
+#, 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"
+"<a href=\"https://torproject.org/\">other anonymity networks</a>\n"
+"may have received. We continue to recruit people to\n"
+"<a href=\"%(volunteer)s\">get involved</a> and help."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:962
+msgid "Blocklists"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/threat-model.html:963
+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:969
+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:977
+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:986
+msgid ""
+"If a blocklist is hosted at a central location with automatic updates\n"
+"the network is vulnerable to a\n"
+"<a href=\"#central\">central resource attack</a>.\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:994
+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
+msgid "Tunnel Routing"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tunnel-routing.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 <a href=\"%(intro)s\">introduction</a>, 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 ""
+"<b>Tunnel gateway</b> - the first router in a tunnel.  For inbound "
+"tunnels,\n"
+"this is the one mentioned in the LeaseSet published in the\n"
+"<a href=\"%(netdb)s\">network database</a>.  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 ""
+"<b>Tunnel endpoint</b> - the last router in a tunnel.  (e.g. both C and F"
+" above)"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tunnel-routing.html:45
+msgid ""
+"<b>Tunnel participant</b> - 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 ""
+"<b>n-Hop tunnel</b> - a tunnel with a specific number of inter-router "
+"jumps, e.g.:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tunnel-routing.html:51
+msgid "<b>0-hop tunnel</b> - a tunnel where the gateway is also the endpoint"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tunnel-routing.html:52
+msgid ""
+"<b>1-hop tunnel</b> - a tunnel where the gateway talks directly to the "
+"endpoint"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tunnel-routing.html:53
+msgid ""
+"<b>2-(or more)-hop tunnel</b> - 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 ""
+"<b>Tunnel ID</b> - A <a href=\"%(commonstructures)s#type_TunnelId\">4 "
+"byte integer</a>\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"
+"<a href=\"%(tunnelcreation)s\">Tunnel Build Message</a>\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 ""
+"<b>tunnel encryption key</b> - an <a "
+"href=\"%(commonstructures)s#type_SessionKey\">AES private key</a> 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 ""
+"<b>tunnel IV key</b> - an <a "
+"href=\"%(commonstructures)s#type_SessionKey\">AES private key</a> 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 ""
+"<b>reply key</b> - an <a "
+"href=\"%(commonstructures)s#type_SessionKey\">AES public key</a> 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 ""
+"<b>reply IV</b> - the IV for encrypting the reply to the tunnel build "
+"request"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tunnel-routing.html:90
+msgid "<b>tunnel id</b> - 4 byte integer (inbound gateways only)"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tunnel-routing.html:91
+msgid ""
+"<b>next hop</b> - 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 "<b>next tunnel id</b> - 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 "<b>tunnel id</b> - 4 byte integer"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tunnel-routing.html:111
+msgid "<b>next hop</b> - 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 ""
+"<b>tunnel encryption key</b> - an <a "
+"href=\"%(commonstructures)s#type_SessionKey\">AES private key</a> for "
+"encrypting\n"
+"messages and instructions to the the endpoint (itself)"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tunnel-routing.html:121
+#, python-format
+msgid ""
+"<b>tunnel IV key</b> - an <a "
+"href=\"%(commonstructures)s#type_SessionKey\">AES private key</a> for "
+"double-encrypting\n"
+"the IV to the endpoint (itself)"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tunnel-routing.html:125
+#, python-format
+msgid ""
+"<b>reply key</b> - an <a "
+"href=\"%(commonstructures)s#type_SessionKey\">AES public key</a> for "
+"encrypting\n"
+"the reply to the tunnel build request (outbound endpoints only)"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tunnel-routing.html:129
+msgid ""
+"<b>reply IV</b> - 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 "<b>tunnel id</b> - 4 byte integer (outbound endpoints only)"
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tunnel-routing.html:131
+msgid ""
+"<b>reply router</b> - 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 ""
+"<b>reply tunnel id</b> - 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"
+"<a href=\"%(tunnelcreation)s\">tunnel creation specification</a>."
+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"
+"<a href=\"%(tunnelimpl)s#tunnel.pooling\">tunnel specification</a>.\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"
+"<a href=\"%(i2cp)s#options\">I2CP options</a>.\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 <a href=\"%(threatmodel)s\">threat model</a>)."
+" 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 <a href=\"%(url)s\">some attacks</a>,\n"
+"3 or more hops are recommended for the highest level of protection.\n"
+"<a href=\"%(url)s\">Recent studies</a>\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"
+"<a href=\"%(i2cp)s#options\">I2CP options</a>.\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"
+"<a href=\"%(peerselection)s#capacity\">capacity rating in the peer "
+"profile</a>."
+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 <a href=\"%(garlicrouting)s\">garlic "
+"routing</a>\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"
+"<a href=\"%(tunnelcreation)s\">tunnel creation specification</a>."
+msgstr ""
+
+#: i2p2www/pages/site/docs/how/tunnel-routing.html:245
+#, python-format
+msgid ""
+"Multi-layer encryption is handled by <a href=\"%(garlicrouting)s\">garlic"
+" encryption</a>\n"
+"of tunnel messages.\n"
+"Details are in the\n"
+"<a href=\"%(tunnelimpl)s\">tunnel specification</a>.\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 "I2CP nastavenia"
+
+#: i2p2www/pages/site/docs/protocol/i2cp.html:3
+msgid "February 2016"
+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.\n"
+"With I2CP, a client application tells the\n"
+"router who they are (their \"destination\"), what anonymity, reliability,"
+" and \n"
+"latency tradeoffs to make, and where to send messages.  In turn the "
+"router uses\n"
+"I2CP to tell the client when any messages have arrived, and to request "
+"authorization\n"
+"for some tunnels to be used."
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2cp.html:18
+#, python-format
+msgid ""
+"The protocol itself is implemented in Java, to provide the\n"
+"<a href=\"%(url)s\">Client SDK</a>.\n"
+"This SDK is exposed in the i2p.jar package, which implements the client-"
+"side of I2CP.\n"
+"Clients should never need to access the router.jar package, which "
+"contains the\n"
+"router itself and the router-side of I2CP.\n"
+"There is also a <a href=\"%(libi2cp)s\">C library implementation</a>.\n"
+"A non-Java client would also have to implement the\n"
+"<a href=\"%(streaming)s\">streaming library</a> for TCP-style connections."
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2cp.html:31
+#, python-format
+msgid ""
+"Applications can take advantage of the base I2CP plus the \n"
+"<a href=\"%(streaming)s\">streaming</a> and <a "
+"href=\"%(datagrams)s\">datagram</a> libraries\n"
+"by using the <a href=\"%(sam)s\">Simple Anonymous Messaging</a> or <a "
+"href=\"%(bob)s\">BOB</a> 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:43
+#, 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 <a href=\"%(elgamalaes)s\">ElGamal/AES end-to-end "
+"encryption</a>\n"
+"which is implemented in the router.\n"
+"The only cryptography that client libraries must still implement is\n"
+"<a href=\"%(cryptography)s#DSA\">DSA public/private key signing</a>\n"
+"for <a href=\"%(i2cp)s#msg_CreateLeaseSet\">LeaseSets</a> and\n"
+"<a href=\"%(i2cp)s#struct_SessionConfig\">Session Configurations</a>, and"
+" management of those keys."
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2cp.html:56
+msgid ""
+"In a standard I2P installation, port 7654 is used by external java "
+"clients to communicate\n"
+"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 "
+"<tt>i2cp.tcp.bindAllInterfaces=true</tt> 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:65
+#, python-format
+msgid ""
+"The router also supports external connections over SSL.\n"
+"While SSL is not the default, it is strongly recommended for any traffic "
+"that may\n"
+"be exposed to the open Internet. The authorization user/password (if "
+"any), the\n"
+"<a href=\"%(commonstructures)s#type_PrivateKey\">Private Key</a> and\n"
+"<a href=\"%(commonstructures)s#type_SigningPrivateKey\">Signing Private "
+"Key</a> for the\n"
+"<a href=\"%(commonstructures)s#struct_Destination\">Destination</a>\n"
+"are all transmitted in-the-clear unless SSL is enabled."
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2cp.html:75
+msgid "I2CP Protocol Specification"
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2cp.html:76
+#, python-format
+msgid "Now on the <a href=\"%(i2cp)s\">I2CP Specification page</a>."
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2cp.html:81
+msgid "I2CP Initialization"
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2cp.html:82
+#, python-format
+msgid ""
+"When a client connects to the router, it first sends a single protocol "
+"version byte (0x2A).\n"
+"Then it sends a <a href=\"%(i2cp)s#msg_GetDate\">GetDate Message</a> and "
+"waits for the <a href=\"%(i2cp)s#msg_SetDate\">SetDate Message</a> "
+"response.\n"
+"Next, it sends a <a href=\"%(i2cp)s#msg_CreateSession\">CreateSession "
+"Message</a> containing the session configuration.\n"
+"It next awaits a <a href=\"%(i2cp)s#msg_RequestLeaseSet\">RequestLeaseSet"
+" Message</a> from the router, indicating that inbound tunnels\n"
+"have been built, and responds with a CreateLeaseSetMessage containing the"
+" signed LeaseSet.\n"
+"The client may now initiate or receive connections from other I2P "
+"destinations."
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2cp.html:91
+msgid "I2CP Options"
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2cp.html:92
+#: i2p2www/pages/site/docs/protocol/i2cp.html:99
+msgid "Router-side Options"
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2cp.html:93
+#, python-format
+msgid ""
+"The following options are traditionally passed to the router via\n"
+"a <a href=\"%(i2cp)s#struct_SessionConfig\">SessionConfig</a> contained "
+"in a <a href=\"%(i2cp)s#msg_CreateSession\">CreateSession Message</a> or "
+"a <a href=\"%(i2cp)s#msg_ReconfigureSession\">ReconfigureSession "
+"Message</a>."
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2cp.html:104
+#: i2p2www/pages/site/docs/protocol/i2cp.html:479
+msgid "As Of Release"
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2cp.html:105
+#: i2p2www/pages/site/docs/protocol/i2cp.html:480
+msgid "Recommended Arguments"
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2cp.html:106
+#: i2p2www/pages/site/docs/protocol/i2cp.html:481
+msgid "Allowable Range"
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2cp.html:117
+msgid ""
+"The timeout (ms) for all sent messages. Unused.\n"
+"See the protocol specification for per-message settings."
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2cp.html:129
+msgid ""
+"Minimum number of ElGamal/AES Session Tags before we send more.\n"
+"Recommended: approximately tagsToSend * 2/3"
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2cp.html:141
+msgid ""
+"Number of ElGamal/AES Session Tags to send at a time.\n"
+"For clients with relatively low bandwidth per-client-pair (IRC, some UDP "
+"apps), this may be set lower."
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2cp.html:153
+msgid ""
+"Comma-separated list of Base 64 Hashes of peers to build tunnels through;"
+" for debugging only"
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2cp.html:162
+msgid "Should generally be set to true for clients and false for servers"
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2cp.html:171
+#: i2p2www/pages/site/docs/protocol/i2cp.html:519
+msgid ""
+"If true, the router just sends the MessagePayload instead\n"
+"of sending a MessageStatus and awaiting a ReceiveMessageBegin."
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2cp.html:183
+msgid ""
+"Guaranteed is disabled;\n"
+"None implemented in 0.8.1; the streaming lib default is None as of 0.8.1,"
+" the client side default is None as of 0.9.4"
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2cp.html:195
+msgid ""
+"For authorization, if required by the router.\n"
+"If the client is running in the same JVM as a router, this option is not "
+"required.\n"
+"Warning - username and password are sent in the clear to the router, "
+"unless using SSL (i2cp.SSL=true).\n"
+"Authorization is only recommended when using SSL."
+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:232
+#: i2p2www/pages/site/docs/protocol/i2cp.html:241
+#: i2p2www/pages/site/docs/protocol/i2cp.html:250
+#: i2p2www/pages/site/docs/protocol/i2cp.html:262
+#: i2p2www/pages/site/docs/protocol/i2cp.html:274
+#: i2p2www/pages/site/docs/protocol/i2cp.html:283
+#: i2p2www/pages/site/docs/protocol/i2cp.html:292
+#: i2p2www/pages/site/docs/protocol/i2cp.html:307
+#: i2p2www/pages/site/docs/protocol/i2cp.html:343
+#: i2p2www/pages/site/docs/protocol/i2cp.html:355
+#: i2p2www/pages/site/docs/protocol/i2cp.html:368
+#, python-format
+msgid "number from %(from)s to %(to)s"
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2cp.html:233
+#: i2p2www/pages/site/docs/protocol/i2cp.html:242
+#: i2p2www/pages/site/docs/protocol/i2cp.html:369
+msgid "No limit"
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2cp.html:235
+msgid "Number of redundant fail-over for tunnels in"
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2cp.html:244
+msgid "Number of redundant fail-over for tunnels out"
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2cp.html:251
+#: i2p2www/pages/site/docs/protocol/i2cp.html:263
+#: i2p2www/pages/site/docs/protocol/i2cp.html:275
+#: i2p2www/pages/site/docs/protocol/i2cp.html:284
+#: i2p2www/pages/site/docs/protocol/i2cp.html:293
+#: i2p2www/pages/site/docs/protocol/i2cp.html:308
+#: i2p2www/pages/site/docs/protocol/i2cp.html:344
+#: i2p2www/pages/site/docs/protocol/i2cp.html:356
+#: i2p2www/pages/site/docs/protocol/i2cp.html:608
+#, python-format
+msgid "%(from)s to %(to)s"
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2cp.html:253
+#: i2p2www/pages/site/docs/protocol/i2cp.html:265
+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:277
+msgid "Length of tunnels in"
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2cp.html:286
+msgid "Length of tunnels out"
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2cp.html:295
+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:310
+msgid ""
+"Random amount to add or subtract to the length of tunnels out.\n"
+"A positive number x means add a random amount from 0 to x inclusive.\n"
+"A negative number -x means add a random amount from -x to x inclusive.\n"
+"The router will limit the total length of the tunnel to 0 to 7 inclusive."
+"\n"
+"The default variance was 1 prior to release 0.7.6."
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2cp.html:325
+msgid ""
+"Name of tunnel - generally used in routerconsole, which will\n"
+"use the first few characters of the Base64 hash of the destination by "
+"default."
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2cp.html:337
+msgid "Name of tunnel - generally ignored unless inbound.nickname is unset."
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2cp.html:346
+msgid ""
+"Priority adjustment for outbound messages.\n"
+"Higher is higher priority."
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2cp.html:358
+msgid ""
+"Number of tunnels in.\n"
+"Limit was increased from 6 to 16 in release 0.9; however, numbers higher "
+"than 6 are\n"
+"incompatible with older releases."
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2cp.html:371
+msgid "Number of tunnels out"
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2cp.html:380
+msgid "Used for consistent peer ordering across restarts."
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2cp.html:399
+msgid ""
+"Any other options prefixed with \"inbound.\" are stored\n"
+"in the \"unknown options\" properties of the inbound tunnel pool's "
+"settings."
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2cp.html:411
+msgid ""
+"Any other options prefixed with \"outbound.\" are stored\n"
+"in the \"unknown options\" properties of the outbound tunnel pool's "
+"settings."
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2cp.html:423
+msgid ""
+"Set to false to disable ever bundling a reply LeaseSet.\n"
+"For clients that do not publish their LeaseSet, this option must be true\n"
+"for any reply to be possible. \"true\" is also recommended for multihomed"
+" servers\n"
+"with long connection times."
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2cp.html:430
+msgid ""
+"Setting to \"false\" may save significant outbound bandwidth, especially "
+"if\n"
+"the client is configured with a large number of inbound tunnels (Leases)."
+"\n"
+"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:438
+msgid "Unidirectional communication, no reply required"
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2cp.html:439
+msgid "LeaseSet is published and higher reply latency is acceptable"
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2cp.html:440
+msgid ""
+"LeaseSet is published, client is a \"server\", all connections are "
+"inbound\n"
+"so the connecting far-end destination obviously has the leaseset already."
+"\n"
+"Connections are either short, or it is acceptable for latency on a long-"
+"lived\n"
+"connection to temporarily increase while the other end re-fetches the "
+"LeaseSet\n"
+"after expiration.\n"
+"HTTP servers may fit these requirements."
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2cp.html:453
+msgid ""
+"Note: Large quantity, length, or variance settings may cause significant "
+"performance or reliability problems."
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2cp.html:457
+#, python-format
+msgid ""
+"Note: As of release 0.7.7, option names and values must use UTF-8 "
+"encoding.\n"
+"This is primarily useful for nicknames.\n"
+"Prior to that release, options with multi-byte characters were corrupted."
+"\n"
+"Since options are encoded in a <a "
+"href=\"%(commonstructures)s#type_Mapping\">Mapping</a>,\n"
+"all option names and values are limited to 255 bytes (not characters) "
+"maximum."
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2cp.html:465
+#: i2p2www/pages/site/docs/protocol/i2cp.html:474
+msgid "Client-side Options"
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2cp.html:466
+msgid ""
+"The following options are interpreted on the client side,\n"
+"and will be interpreted if passed to the I2PSession via the "
+"I2PClient.createSession() call.\n"
+"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:490
+#: i2p2www/pages/site/docs/protocol/i2cp.html:590
+#, python-format
+msgid "%(num)s minimum"
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2cp.html:492
+msgid "(ms) Idle time required (default 30 minutes)"
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2cp.html:501
+msgid "Close I2P session when idle"
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2cp.html:510
+msgid "Encrypt the lease"
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2cp.html:531
+msgid "Gzip outbound data"
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2cp.html:540
+msgid "For encrypted leasesets. Base 64 SessionKey (44 characters)"
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2cp.html:549
+msgid ""
+"Base 64 private key for encryption.\n"
+"Optionally preceded by the key type and ':'.\n"
+"Only \"ELGAMAL_2048:\" is supported, which is the default.\n"
+"I2CP will generate the public key from the private key.\n"
+"Use for persistent leaseset keys across restarts."
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2cp.html:564
+msgid ""
+"Base 64 private key for signatures.\n"
+"Optionally preceded by the key type and ':'.\n"
+"DSA_SHA1 is the default.\n"
+"Key type must match the signature type in the destination.\n"
+"I2CP will generate the public key from the private key.\n"
+"Use for persistent leaseset keys across restarts."
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2cp.html:580
+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:592
+msgid "(ms) Idle time required (default 20 minutes, minimum 5 minutes)"
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2cp.html:601
+msgid "Reduce tunnel quantity when idle"
+msgstr "Znížiť množstvo tunelov pri nečinnosti"
+
+#: i2p2www/pages/site/docs/protocol/i2cp.html:610
+msgid "Tunnel quantity when reduced (applies to both inbound and outbound)"
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2cp.html:619
+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:631
+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:643
+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:650
+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:656
+msgid "I2CP Payload Data Format and Multiplexing"
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2cp.html:657
+#, python-format
+msgid ""
+"The end-to-end messages handled by I2CP (i.e. the data sent by the client"
+" in a\n"
+"<a href=\"%(i2cp)s#msg_SendMessage\">SendMessageMessage</a>\n"
+"and received by the client in a\n"
+"<a href=\"%(i2cp)s#msg_MessagePayload\">MessagePayloadMessage</a>)\n"
+"are gzipped with a standard 10-byte gzip\n"
+"header beginning with 0x1F 0x8B 0x08 as\n"
+"specified by <a href=\"http://www.ietf.org/rfc/rfc1952.txt\">RFC "
+"1952</a>.\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:671
+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:677
+#: i2p2www/pages/site/docs/protocol/i2np.html:32
+msgid "Bytes"
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2cp.html:678
+msgid "Content"
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2cp.html:683
+msgid "Gzip header"
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2cp.html:688
+msgid "Gzip flags"
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2cp.html:693
+msgid "I2P Source port (Gzip mtime)"
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2cp.html:698
+msgid "I2P Destination port (Gzip mtime)"
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2cp.html:703
+msgid "Gzip xflags"
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2cp.html:708
+msgid "I2P Protocol (6 = Streaming, 17 = Datagram, 18 = Raw Datagrams) (Gzip OS)"
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2cp.html:717
+msgid ""
+"Data integrity is verified with the standard gzip CRC-32 as\n"
+"specified by <a href=\"http://www.ietf.org/rfc/rfc1952.txt\">RFC 1952</a>."
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2cp.html:725
+msgid ""
+"The current authorization mechanism could be modified to use hashed "
+"passwords."
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2cp.html:729
+msgid ""
+"The Signing Private Keys is included in the Create Lease Set message,\n"
+"it is not required. Revocation is unimplemented.\n"
+"It should be replaced with random data or removed."
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2cp.html:735
+#, python-format
+msgid ""
+"Some improvements may be able to use messages previously defined but not "
+"implemented.\n"
+"For reference, here is the\n"
+"<a href=\"%(pdf1)s\">I2CP Protocol Specification Version 0.9</a>\n"
+"(PDF) dated August 28, 2003.\n"
+"That document also references the\n"
+"<a href=\"%(pdf2)s\">Common Data Structures Specification Version 0.9</a>."
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2np.html:2
+msgid "I2P Network Protocol"
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2np.html:3
+msgid "June 2013"
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2np.html:6
+msgid ""
+"The I2P Network Protocol (I2NP),\n"
+"which is sandwiched between I2CP and the various I2P transport protocols,"
+" manages the\n"
+"routing and mixing of messages between routers, as well as the selection "
+"of what\n"
+"transports to use when communicating with a peer for which there are "
+"multiple\n"
+"common transports supported."
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2np.html:14
+msgid "I2NP Definition"
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2np.html:15
+msgid ""
+"I2NP (I2P Network Protocol) messages can be used for one-hop, router-to-"
+"router, point-to-point messages.\n"
+"By encrypting and wrapping messages in other messages, they can be sent "
+"in a secure way\n"
+"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:22
+#, python-format
+msgid ""
+"The priorities listed below may not be current and are subject to change."
+"\n"
+"See the <a href=\"%(outnetmessage)s\">OutNetMessage Javadocs</a>\n"
+"for the current priority settings.\n"
+"Priority queueing implementation may vary."
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2np.html:29
+msgid "Message Format"
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2np.html:32
+msgid "Field"
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2np.html:33
+msgid "Unique ID"
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2np.html:34
+msgid "Expiration"
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2np.html:35
+#: i2p2www/pages/site/docs/protocol/i2np.html:92
+msgid "Payload Length"
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2np.html:36
+msgid "Checksum"
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2np.html:37
+msgid "Payload"
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2np.html:40
+#, python-format
+msgid ""
+"While the maximum payload size is nominally 64KB, the size is further "
+"constrained by the\n"
+"method of fragmenting I2NP messages into multiple 1KB tunnel messages as "
+"described on\n"
+"<a href=\"%(tunnelimpl)s\">the tunnel implementation page</a>.\n"
+"The maximum number of fragments is 64, and the message may not be "
+"perfectly aligned,\n"
+"So the message must nominally fit in 63 fragments."
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2np.html:48
+msgid ""
+"The maximum size of an initial fragment is 956 bytes (assuming TUNNEL "
+"delivery mode);\n"
+"the maximum size of 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:54
+msgid ""
+"In addition, the transports may have additional restrictions.\n"
+"NTCP currently limits to 16KB - 6 = 16378 bytes but this will be "
+"increased in a future release.\n"
+"The SSU limit is approximately 32 KB."
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2np.html:60
+msgid ""
+"Note that these are not the limits for datagrams that the client sees, as"
+" the\n"
+"router may bundle a reply leaseset and/or session tags together with the "
+"client message\n"
+"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:68
+msgid "Message Types"
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2np.html:69
+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:80
+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:90
+msgid "Message"
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2np.html:91
+msgid "Type"
+msgstr "Typ"
+
+#: i2p2www/pages/site/docs/protocol/i2np.html:94
+msgid "Comments"
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2np.html:102
+msgid "May vary"
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2np.html:108
+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:117
+msgid "Varies"
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2np.html:119
+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:133
+msgid "Priority may vary on a per-destination basis"
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2np.html:143
+msgid ""
+"Used for message replies, and for testing tunnels - generally wrapped in "
+"a GarlicMessage"
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2np.html:151
+msgid ""
+"Generally wrapped in a DataMessage -\n"
+"but when unwrapped, given a priority of 100 by the forwarding router"
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2np.html:178
+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:198
+msgid "Shorter TunnelBuildMessage as of 0.7.12"
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2np.html:206
+msgid "Shorter TunnelBuildReplyMessage as of 0.7.12"
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2np.html:209
+#, python-format
+msgid "Others listed in <a href=\"%(pdf)s\">2003 Spec</a>"
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2np.html:215
+msgid "Obsolete, Unused"
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2np.html:219
+msgid "Full Protocol Specification"
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2np.html:220
+#, python-format
+msgid ""
+"<a href=\"%(i2npspec)s\">On the I2NP Specification page</a>.\n"
+"See also the\n"
+"<a href=\"%(commonstructures)s\">Common Data Structure Specification "
+"page</a>."
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/i2np.html:227
+msgid ""
+"It isn't clear whether the current priority scheme is generally "
+"effective,\n"
+"and whether the priorities for various messages should be adjusted "
+"further.\n"
+"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 <a href=\"%(docs)s\">Index to Technical Documentation</a>."
+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 ""
+"<b>I2P Transport Layer:</b> 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 "<b>I2P Tunnel Layer:</b> provide full encrypted tunnel connections."
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/index.html:42
+#, python-format
+msgid ""
+"<a href=\"%(tunnelmessage)s\">Tunnel messages</a>: 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 ""
+"<a href=\"%(i2np)s\">I2NP messages</a>: 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 ""
+"<b>I2P Garlic Layer:</b> provide encrypted and anonymous end-to-end I2P "
+"message delivery."
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/index.html:55
+#, python-format
+msgid ""
+"<a href=\"%(i2np)s\">I2NP messages</a>: 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 ""
+"<b>I2P Client Layer:</b> 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 ""
+"<a href=\"%(i2cp)s\">I2CP</a>: 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 ""
+"<b>I2P End-to-end Transport Layer:</b> allow TCP- or UDP-like "
+"functionality on top of I2P."
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/index.html:76
+#, python-format
+msgid ""
+"<a href=\"%(streaming)s\">Streaming Library</a>: 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 ""
+"<a href=\"%(datagrams)s\">Datagram Library</a>: 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 ""
+"<b>I2P Application Interface Layer:</b> additional (optional) libraries "
+"allowing easier implementations on top of I2P."
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/index.html:93
+msgid "<b>I2P Application Proxy Layer:</b> proxy systems."
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/index.html:95
+#, python-format
+msgid "HTTP Client/Server, IRC Client, <a href=\"%(socks)s\">SOCKS</a>, Streamr"
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/index.html:99
+msgid ""
+"Finally, what could be considered the <b>'I2P application layer'</b>, 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 "<b>Streaming/datagram applications</b>: i2psnark, Syndie, i2phex..."
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/index.html:105
+msgid "<b>SAM/BOB applications</b>: IMule, i2p-bt, i2prufus, Robert..."
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/index.html:106
+#, python-format
+msgid ""
+"<b>Other I2P applications</b>: Syndie, EepGet, <a "
+"href=\"%(plugins)s\">plugins</a>..."
+msgstr ""
+
+#: i2p2www/pages/site/docs/protocol/index.html:107
+msgid ""
+"<b>Regular applications</b>: 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/transport/index.html:2
+msgid "Transport Overview"
+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 three transports currently implemented:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/index.html:21
+#, python-format
+msgid "<a href=\"%(ntcp)s\">NTCP</a>, a Java New I/O (NIO) TCP transport"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/index.html:22
+#, python-format
+msgid " <a href=\"%(ssu)s\">SSU</a>, or Secure Semireliable UDP"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/index.html:23
+#, python-format
+msgid "<a href=\"%(ntcp2)s\">NTCP2</a>, a new version of NTCP"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/index.html:26
+msgid ""
+"Each provides a \"connection\" paradigm, with authentication,\n"
+"flow control, acknowledgments and retransmission."
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/index.html:32
+msgid "Transport Services"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/index.html:34
+msgid "The transport subsystem in I2P provides the following services:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/index.html:38
+#, python-format
+msgid ""
+"Reliable delivery of <a href=\"%(i2np)s\">I2NP</a> messages.\n"
+"Transports support I2NP message delivery ONLY.\n"
+"They are not general-purpose data pipes."
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/index.html:43
+msgid "In-order delivery of messages is NOT guaranteed by all transports."
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/index.html:44
+msgid ""
+"Maintain a set of router addresses, one or more for each transport,\n"
+"that the router publishes as its global contact information (the "
+"RouterInfo).\n"
+"Each transport may connect using one of these addresses, which may be\n"
+"IPv4 or (as of version 0.9.8) IPv6."
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/index.html:50
+msgid "Selection of the best transport for each outgoing message"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/index.html:51
+msgid "Queueing of outbound messages by priority"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/index.html:52
+msgid ""
+"Bandwidth limiting, both outbound and inbound, according to router "
+"configuration"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/index.html:53
+msgid "Setup and teardown of transport connections"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/index.html:54
+msgid "Encryption of point-to-point communications"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/index.html:55
+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:59
+msgid "Firewall port opening using UPnP (Universal Plug and Play)"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/index.html:60
+msgid "Cooperative NAT/Firewall traversal"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/index.html:61
+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:62
+msgid ""
+"Coordination of firewall status and local IP, and changes to either, "
+"among the transports"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/index.html:63
+#: i2p2www/pages/site/docs/transport/ssu.html:35
+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:64
+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:65
+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:69
+msgid "Qualification of valid IP addresses according to a local rule set"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/index.html:70
+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:77
+msgid "Transport Addresses"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/index.html:79
+msgid ""
+"The transport subsystem maintains a set of router addresses, each of "
+"which lists a transport method, IP, and port.\n"
+"These addresses constitute the advertised contact points, and are "
+"published by the router to the network database.\n"
+"Addresses may also contain an arbitrary set of additional options."
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/index.html:85
+msgid "Each transport method may publish multiple router addresses."
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/index.html:89
+msgid "Typical scenarios are:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/index.html:91
+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:92
+#, 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 <a "
+"href=\"%(ssu)s\">the SSU spec</a> for details)"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/index.html:96
+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:102
+msgid "Transport Selection"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/index.html:104
+#, python-format
+msgid ""
+"The transport system delivers <a href=\"%(i2np)s\">I2NP messages</a> "
+"only. The transport selected for any message is\n"
+"independent of the upper-layer protocols and contents (router or client "
+"messages, whether an external application was using\n"
+"TCP or UDP to connect to I2P, whether the upper layer was using\n"
+"<a href=\"%(streaming)s\">the streaming library</a>\n"
+"streaming\n"
+"or\n"
+"<a href=\"%(datagrams)s\">datagrams</a>,\n"
+"datagrams\n"
+"etc.)."
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/index.html:118
+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:124
+msgid "Whether a transport bids, and with what value, depend on numerous factors:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/index.html:128
+msgid "Configuration of transport preferences"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/index.html:129
+msgid "Whether the transport is already connected to the peer"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/index.html:130
+msgid ""
+"The number of current connections compared to various connection limit "
+"thresholds"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/index.html:131
+msgid "Whether recent connection attempts to the peer have failed"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/index.html:132
+msgid ""
+"The size of the message, as different transports have different size "
+"limits"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/index.html:133
+msgid ""
+"Whether the peer can accept incoming connections for that transport, as "
+"advertised in its RouterInfo"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/index.html:134
+msgid "Whether the connection would be indirect (requiring introducers) or direct"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/index.html:135
+msgid "The peer's transport preference, as advertised in its RouterInfo"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/index.html:138
+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:145
+msgid "New Transports and Future Work"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/index.html:147
+msgid "Additional transports may be developed, including:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/index.html:152
+msgid "A TLS/SSH look-alike transport"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/index.html:153
+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:154
+msgid "Tor-compatible pluggable transports"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/index.html:157
+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:164
+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:171
+#, python-format
+msgid ""
+"Analyze <a href=\"%(pdf)s\">Breaking and Improving Protocol "
+"Obfuscation</a>\n"
+"and see how transport-layer padding may improve things."
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:2
+msgid "NTCP (NIO-based TCP)"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:6
+#, python-format
+msgid ""
+"The others are <a href=\"%(ssu)s\">SSU</a> and <a "
+"href=\"%(ntcp2)s\">NTCP2</a>.\n"
+"NTCP is a Java NIO-based transport introduced in I2P release 0.6.1.22.\n"
+"Java NIO (new I/O) does not suffer from the 1 thread per connection "
+"issues of the old TCP transport.\n"
+"NTCP-over-IPv6 is supported as of version 0.9.8."
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:13
+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:21
+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:27
+#: i2p2www/pages/site/docs/transport/ssu.html:38
+msgid "Router Address Specification"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:29
+#: i2p2www/pages/site/docs/transport/ssu.html:40
+msgid "The following properties are stored in the network database."
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:44
+msgid "NTCP Protocol Specification"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:46
+msgid "Standard Message Format"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:47
+msgid ""
+"After establishment,\n"
+"the NTCP transport sends individual I2NP messages, with a simple "
+"checksum.\n"
+"The unencrypted message is encoded as follows:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:65
+msgid ""
+"The data is then AES/256/CBC encrypted. The session key for the "
+"encryption\n"
+"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:73
+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:81
+msgid "Time Sync Message Format"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:82
+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:93
+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:99
+msgid "Checksums"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:100
+#, python-format
+msgid ""
+"The standard and time sync messages use the Adler-32 checksum\n"
+"as defined in the <a href=\"%(rfc1950)s\">ZLIB Specification</a>."
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:106
+#: i2p2www/pages/site/docs/transport/ssu.html:187
+msgid "Idle Timeout"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:107
+#: i2p2www/pages/site/docs/transport/ssu.html:188
+msgid ""
+"Idle timeout and connection close is at the discretion of each endpoint "
+"and may vary.\n"
+"The current implementation lowers the timeout as the number of "
+"connections approaches the\n"
+"configured maximum, and raises the timeout when the connection count is "
+"low.\n"
+"The recommended minimum timeout is two minutes or more, and the "
+"recommended\n"
+"maximum timeout is ten minutes or more."
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:116
+msgid "RouterInfo Exchange"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:117
+msgid ""
+"After establishment, and every 30-60 minutes thereafter,\n"
+"the two routers should generally exchange RouterInfos using a "
+"DatabaseStoreMessage.\n"
+"However, Alice should check if the first queued message is a "
+"DatabaseStoreMessage\n"
+"so as not to send a duplicate message; this is often the case when "
+"connecting to a floodfill router."
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:125
+msgid "Establishment Sequence"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:126
+msgid ""
+"In the establish state, there is a 4-phase message sequence to exchange "
+"DH keys and signatures.\n"
+"In the first two messages there is a 2048-bit Diffie Hellman exchange.\n"
+"Then, signatures of the critical data are exchanged to confirm the "
+"connection."
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:142
+msgid "Legend:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:143
+msgid "256 byte DH public keys"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:147
+msgid "timestamps (4 bytes, seconds since epoch)"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:148
+msgid "32 byte Session key"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:149
+msgid "2 byte size of Alice identity to follow"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:152
+msgid "DH Key Exchange"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:153
+#, 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"
+"<a href=\"%(cryptography)s#elgamal\">ElGamal encryption</a>."
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:159
+msgid ""
+"The DH key exchange consists of a number of steps, displayed below.\n"
+"The mapping between these steps and the messages sent between I2P "
+"routers,\n"
+"is marked in bold."
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:165
+msgid ""
+"Alice generates a secret integer x. She then calculates <code>X = g^x mod"
+" p</code>."
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:166
+msgid "Alice sends X to Bob <b>(Message 1)</b>."
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:167
+msgid ""
+"Bob generates a secret integer y. He then calculates <code>Y = g^y mod "
+"p</code>."
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:168
+msgid "Bob sends Y to Alice.<b>(Message 2)</b>"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:169
+msgid "Alice can now compute <code>sessionKey = Y^x mod p</code>."
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:170
+msgid "Bob can now compute <code>sessionKey = X^y mod p</code>."
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:171
+msgid ""
+"Both Alice and Bob now have a shared key <code>sessionKey = g^(x*y) mod "
+"p</code>."
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:173
+#, python-format
+msgid ""
+"The sessionKey is then used to exchange identities in <b>Message 3</b> "
+"and <b>Message 4</b>.\n"
+"The exponent (x and y) length for the DH exchange is documented on the\n"
+"<a href=\"%(crypto)s#exponent\">cryptography page</a>."
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:193
+msgid "Message 1 (Session Request)"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:194
+#, python-format
+msgid ""
+"This is the DH request. Alice already has Bob's\n"
+"<a href=\"%(commonstructures)s#struct_RouterIdentity\">Router "
+"Identity</a>,\n"
+"IP address, and port, as contained in his\n"
+"<a href=\"%(commonstructures)s#struct_RouterInfo\">Router Info</a>,\n"
+"which was published to the\n"
+"<a href=\"%(netdb)s\">network database</a>.\n"
+"Alice sends Bob:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:207
+#: i2p2www/pages/site/docs/transport/ntcp.html:250
+#: i2p2www/pages/site/docs/transport/ntcp.html:332
+#: i2p2www/pages/site/docs/transport/ntcp.html:437
+msgid "Size:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:209
+msgid "Contents:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:227
+msgid "256 byte X from Diffie Hellman"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:229
+msgid "SHA256 Hash(X) xored with SHA256 Hash(Bob's `RouterIdentity`)"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:236
+#: i2p2www/pages/site/docs/transport/ntcp.html:319
+#: i2p2www/pages/site/docs/transport/ntcp.html:398
+msgid "Notes:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:237
+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:243
+msgid "Message 2 (Session Created)"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:244
+msgid "This is the DH reply. Bob sends Alice:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:252
+#: i2p2www/pages/site/docs/transport/ntcp.html:334
+#: i2p2www/pages/site/docs/transport/ntcp.html:439
+msgid "Unencrypted Contents:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:274
+#: i2p2www/pages/site/docs/transport/ntcp.html:310
+msgid "256 byte Y from Diffie Hellman"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:276
+msgid "SHA256 Hash(X concatenated with Y)"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:279
+#: i2p2www/pages/site/docs/transport/ntcp.html:364
+msgid "4 byte timestamp (seconds since the epoch)"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:281
+msgid "12 bytes random data"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:285
+#: i2p2www/pages/site/docs/transport/ntcp.html:376
+#: i2p2www/pages/site/docs/transport/ntcp.html:466
+msgid "Encrypted Contents:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:312
+#, python-format
+msgid ""
+"48 bytes <a href=\"%(cryptography)s#AES\">AES encrypted</a> using the DH "
+"session key and\n"
+"                  the last 16 bytes of Y as the IV"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:320
+msgid ""
+"Alice may drop the connection if the clock skew with Bob is too high as "
+"calculated using tsB."
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:325
+msgid "Message 3 (Session Confirm A)"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:326
+msgid ""
+"This contains Alice's router identity, and a signature of the critical "
+"data. Alice sends Bob:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:360
+msgid "2 byte size of Alice's router identity to follow (387+)"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:362
+msgid "Alice's 387+ byte `RouterIdentity`"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:366
+#: i2p2www/pages/site/docs/transport/ntcp.html:461
+msgid "0-15 bytes random data"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:368
+msgid ""
+"the `Signature` of the following concatenated data:\n"
+"             X, Y, Bob's `RouterIdentity`, tsA, tsB.\n"
+"             Alice signs it with the `SigningPrivateKey` associated with "
+"the `SigningPublicKey` in her `RouterIdentity`"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:389
+#, python-format
+msgid ""
+"448 bytes <a href=\"%(cryptography)s#AES\">AES encrypted</a> using the DH"
+" session key and\n"
+"                  the last 16 bytes of HXxorHI (i.e., the last 16 bytes "
+"of message #1) as the IV"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:400
+msgid "Bob verifies the signature, and on failure, drops the connection."
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:403
+msgid ""
+"Bob may drop the connection if the clock skew with Alice is too high as "
+"calculated using tsA."
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:406
+msgid ""
+"Alice will use the last 16 bytes of the encrypted contents of this "
+"message as the IV for the next message."
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:430
+msgid "Message 4 (Session Confirm B)"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:431
+msgid "This is a signature of the critical data. Bob sends Alice:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:455
+msgid ""
+"the `Signature` of the following concatenated data:\n"
+"             X, Y, Alice's `RouterIdentity`, tsA, tsB.\n"
+"             Bob signs it with the `SigningPrivateKey` associated with "
+"the `SigningPublicKey` in his `RouterIdentity`"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:479
+#, python-format
+msgid ""
+"Data <a href=\"%(cryptography)s#AES\">AES encrypted</a> using the DH "
+"session key and\n"
+"                  the last 16 bytes of the encrypted contents of message "
+"#2 as the IV\n"
+"                  48 bytes for a DSA signature, may vary for other "
+"signature types"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:488
+msgid "Alice verifies the signature, and on failure, drops the connection."
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:491
+msgid ""
+"Bob will use the last 16 bytes of the encrypted contents of this message "
+"as the IV for the next message."
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:506
+msgid "After Establishment"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:507
+msgid ""
+"The connection is established, and standard or time sync messages may be "
+"exchanged.\n"
+"All subsequent messages are AES encrypted using the negotiated DH session"
+" key.\n"
+"Alice will use the last 16 bytes of the encrypted contents of message #3 "
+"as the next IV.\n"
+"Bob will use the last 16 bytes of the encrypted contents of message #4 as"
+" the next IV."
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:516
+msgid "Check Connection Message"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:517
+msgid ""
+"Alternately, when Bob receives a connection, it could be a\n"
+"check connection (perhaps prompted by Bob asking for someone\n"
+"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:526
+msgid "32 bytes of uninterpreted, ignored data"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:527
+msgid "1 byte size"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:528
+msgid ""
+"that many bytes making up the local router's IP address (as reached by "
+"the remote side)"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:529
+msgid "2 byte port number that the local router was reached on"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:530
+msgid ""
+"4 byte i2p network time as known by the remote side (seconds since the "
+"epoch)"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:531
+msgid "uninterpreted padding data, up to byte 223"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:532
+msgid ""
+"xor of the local router's identity hash and the SHA256 of bytes 32 "
+"through bytes 223"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:535
+msgid "Check connection is completely disabled as of release 0.9.12."
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:539
+msgid "Discussion"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:540
+#, python-format
+msgid "Now on the <a href=\"%(ntcpdisc)s\">NTCP Discussion Page</a>."
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:546
+msgid "The maximum message size should be increased to approximately 32 KB."
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:550
+msgid ""
+"A set of fixed packet sizes may be appropriate to further hide the data \n"
+"fragmentation to external adversaries, but the tunnel, garlic, and end to"
+" \n"
+"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:558
+msgid ""
+"Memory utilization (including that of the kernel) for NTCP should be "
+"compared to that for SSU."
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ntcp.html:562
+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/ssu.html:2
+msgid "Secure Semireliable UDP"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ssu.html:7
+#, python-format
+msgid ""
+"SSU (also called \"UDP\" in much of the I2P documentation and user "
+"interfaces)\n"
+"is one of three <a href=\"%(transports)s\">transports</a> currently "
+"implemented in I2P.\n"
+"The others are <a href=\"%(ntcp)s\">NTCP</a> and <a "
+"href=\"%(ntcp2)s\">NTCP2</a>."
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ssu.html:13
+msgid ""
+"SSU was introduced in I2P release 0.6.\n"
+"In a standard I2P installation, the router uses both NTCP and SSU for "
+"outbound connections.\n"
+"SSU-over-IPv6 is supported as of version 0.9.8."
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ssu.html:19
+msgid ""
+"SSU is called \"semireliable\" because it will repeatedly retransmit "
+"unacknowledged messages,\n"
+"but only up to a maximum number of times. After that, the message is "
+"dropped."
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ssu.html:24
+msgid "SSU Services"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ssu.html:26
+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:32
+msgid ""
+"Cooperative NAT/Firewall traversal using <a "
+"href=\"#introduction\">introducers</a>"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ssu.html:33
+msgid ""
+"Local IP detection by inspection of incoming packets and <a "
+"href=\"#peerTesting\">peer testing</a>"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ssu.html:34
+msgid ""
+"Communication of firewall status and local IP, and changes to either to "
+"NTCP"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ssu.html:46
+#: i2p2www/pages/site/docs/transport/ssu.html:60
+#: i2p2www/pages/site/docs/transport/ssu.html:61
+#: i2p2www/pages/site/docs/transport/ssu.html:63
+#: i2p2www/pages/site/docs/transport/ssu.html:66
+#: i2p2www/pages/site/docs/transport/ssu.html:70
+#: i2p2www/pages/site/docs/transport/ssu.html:71
+#: i2p2www/pages/site/docs/transport/ssu.html:77
+msgid "See below"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ssu.html:84
+msgid "Protocol Details"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ssu.html:86
+msgid "Congestion control"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ssu.html:88
+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:95
+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:106
+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:118
+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:125
+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:131
+msgid ""
+"For both MTU values, it is desirable that (MTU &#37; 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:137
+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:143
+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:149
+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:154
+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:161
+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:167
+msgid ""
+"For IPv6, the minimum MTU is 1280. The IPv6 IP/UDP header is 48 bytes,\n"
+"so we use an MTU where (MTN &#37; 16 == 0), which is true for 1280.\n"
+"The maximum IPv6 MTU is 1488.\n"
+" (max was 1472 prior to version 0.9.28)."
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ssu.html:174
+msgid "Message Size Limits"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ssu.html:175
+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:197
+msgid "Keys"
+msgstr "Kľúče"
+
+#: i2p2www/pages/site/docs/transport/ssu.html:199
+msgid ""
+"All encryption used is AES256/CBC with 32 byte keys and 16 byte IVs.\n"
+"When Alice originates a session with Bob,\n"
+"the MAC and session keys are negotiated as part of the DH exchange, and "
+"are then used\n"
+"for the HMAC and encryption, respectively.  During the DH exchange, \n"
+"Bob's publicly knowable introKey is used for the MAC and encryption."
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ssu.html:207
+msgid ""
+"Both the initial message and the 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:216
+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:227
+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:238
+#, python-format
+msgid ""
+"For the DH key agreement,\n"
+"<a href=\"%(rfc3526)s\">RFC3526</a> 2048bit\n"
+"MODP group (#14) is used:"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ssu.html:248
+#, python-format
+msgid ""
+"These are the same p and g used for I2P's\n"
+"<a href=\"%(cryptography)s#elgamal\">ElGamal encryption</a>."
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ssu.html:253
+msgid "Replay prevention"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ssu.html:255
+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:262
+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:270
+msgid "Addressing"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ssu.html:272
+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:284
+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 <a href=\"#capabilities\">below</a>."
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ssu.html:290
+#, python-format
+msgid ""
+"The addresses, options, and capabilities are published in the <a "
+"href=\"%(netdb)s\">network database</a>."
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ssu.html:295
+msgid "Direct Session Establishment"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ssu.html:296
+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:301
+msgid "Connection establishment (direct)"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ssu.html:302
+msgid ""
+"Alice connects directly to Bob.\n"
+"IPv6 is supported as of version 0.9.8."
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ssu.html:317
+#, python-format
+msgid ""
+"After the SessionConfirmed message is received, Bob sends a small\n"
+"<a href=\"%(i2npspec)s#msg_DeliveryStatus\">DeliveryStatus message</a>\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:326
+#, python-format
+msgid ""
+"After the status message is sent, the peers usually exchange\n"
+"<a href=\"%(i2npspec)s#msg_DatabaseStore\">DatabaseStore messages</a>\n"
+"containing their\n"
+"<a href=\"%(commonstructures)s#struct_RouterInfo\">RouterInfos</a>,\n"
+"however, this is not required."
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ssu.html:335
+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:344
+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:358
+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:385
+msgid "Connection establishment (indirect using an introducer)"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ssu.html:387
+msgid "Alice first connects to introducer Bob, who relays the request to Charlie."
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ssu.html:405
+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:419
+msgid "Peer testing"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ssu.html:421
+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:440
+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:450
+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:459
+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:470
+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:480
+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:488
+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:498
+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:526
+msgid "Transmission window, ACKs and Retransmissions"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ssu.html:527
+#, 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"
+"<a href=\"%(ssuspec)s\">the protocol specification page</a>\n"
+"for details."
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ssu.html:535
+#, 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 <a href=\"%(streaming)s\">streaming</a>.\n"
+"See the code for initial, min and max parameters."
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ssu.html:547
+msgid "Security"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ssu.html:548
+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:556
+msgid ""
+"The details of validation are not specified\n"
+"here. Implementers should add defenses where appropriate."
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ssu.html:562
+msgid "Peer capabilities"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ssu.html:566
+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:578
+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:587
+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:593
+msgid ""
+"The current implementation repeatedly sends acknowledgments for the same "
+"packets,\n"
+"which unnecessarily increases overhead."
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ssu.html:598
+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:604
+msgid "The protocol should be extended to exchange MTUs during the setup."
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ssu.html:608
+msgid "Rekeying is currently unimplemented and may never be."
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ssu.html:612
+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:617
+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:623
+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:629
+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:633
+msgid "Capacities appear to be unused."
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ssu.html:637
+msgid ""
+"Signed-on times in SessionCreated and SessionConfirmed appear to be "
+"unused or unverified."
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ssu.html:642
+msgid "Implementation Diagram"
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ssu.html:643
+msgid ""
+"This diagram\n"
+"should accurately reflect the current implementation, however there may "
+"be small differences."
+msgstr ""
+
+#: i2p2www/pages/site/docs/transport/ssu.html:651
+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"
+"</i>gateway</i>, 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 <i>endpoint</i> 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"
+"<a href=\"%(tunnelrouting)s\">on the tunnel overview page</a>."
+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, <a href=\"%(i2np)s\">I2NP messages</a> 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"
+"<a href=\"%(i2np)s\">I2NP messages</a> into fixed-size\n"
+"<a href=\"%(tunnelmessage)s\">tunnel messages</a>\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"
+"<a href=\"%(tunnelmessage)s\">tunnel message specification</a>."
+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:243
+msgid ""
+"Duplicate message detection is handled by a decaying Bloom filter on "
+"message\n"
+"IVs.  Each router maintains a single Bloom filter to contain the XOR of "
+"the IV and\n"
+"the first block of the message received for all of the tunnels it is "
+"participating\n"
+"in, modified to drop seen entries after 10-20 minutes (when the tunnels "
+"will have\n"
+"expired).  The size of the bloom filter and the parameters used are "
+"sufficient to\n"
+"more than saturate the router's network connection with a negligible "
+"chance of \n"
+"false positive.  The unique value fed into the Bloom filter is the XOR of"
+" the IV \n"
+"and the first block so as to prevent nonsequential colluding peers in the"
+" tunnel \n"
+"from tagging a message by resending it with the IV and first block "
+"switched."
+msgstr ""
+
+#: i2p2www/pages/site/docs/tunnels/implementation.html:256
+msgid "Endpoint Processing"
+msgstr ""
+
+#: i2p2www/pages/site/docs/tunnels/implementation.html:258
+msgid ""
+"After receiving and validating a tunnel message at the last hop in the "
+"tunnel,\n"
+"how the endpoint recovers the data encoded by the gateway depends upon "
+"whether \n"
+"the tunnel is an inbound or an outbound tunnel.  For outbound tunnels, "
+"the \n"
+"endpoint encrypts the message with its layer key just like any other "
+"participant, \n"
+"exposing the preprocessed data.  For inbound tunnels, the endpoint is "
+"also the \n"
+"tunnel creator so they can merely iteratively decrypt the IV and message,"
+" using the \n"
+"layer and IV keys of each step in reverse order."
+msgstr ""
+
+#: i2p2www/pages/site/docs/tunnels/implementation.html:268
+msgid ""
+"At this point, the tunnel endpoint has the preprocessed data sent by the "
+"gateway,\n"
+"which it may then parse out into the included I2NP messages and forwards "
+"them as\n"
+"requested in their delivery instructions."
+msgstr ""
+
+#: i2p2www/pages/site/docs/tunnels/implementation.html:275
+msgid "Tunnel Building"
+msgstr ""
+
+#: i2p2www/pages/site/docs/tunnels/implementation.html:277
+msgid ""
+"When building a tunnel, the creator must send a request with the "
+"necessary\n"
+"configuration data to each of the hops and wait for all of them to agree "
+"before\n"
+"enabling the tunnel.  The requests are encrypted so that only the peers "
+"who need\n"
+"to know a piece of information (such as the tunnel layer or IV key) has "
+"that\n"
+"data.  In addition, only the tunnel creator will have access to the "
+"peer's\n"
+"reply.  There are three important dimensions to keep in mind when "
+"producing\n"
+"the tunnels: what peers are used (and where), how the requests are sent "
+"(and \n"
+"replies received), and how they are maintained."
+msgstr ""
+
+#: i2p2www/pages/site/docs/tunnels/implementation.html:291
+msgid ""
+"Beyond the two types of tunnels - inbound and outbound - there are two "
+"styles\n"
+"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:299
+msgid "Exploratory tunnel peer selection"
+msgstr ""
+
+#: i2p2www/pages/site/docs/tunnels/implementation.html:301
+msgid ""
+"Exploratory tunnels are built out of a random selection of peers from a "
+"subset\n"
+"of the network.  The particular subset varies on the local router and on "
+"what their\n"
+"tunnel routing needs are.  In general, the exploratory tunnels are built "
+"out of\n"
+"randomly selected peers who are in the peer's \"not failing but active\" "
+"profile\n"
+"category.  The secondary purpose of the tunnels, beyond merely tunnel "
+"routing,\n"
+"is to find underutilized high capacity peers so that they can be promoted"
+" for\n"
+"use in client tunnels."
+msgstr ""
+
+#: i2p2www/pages/site/docs/tunnels/implementation.html:311
+#, python-format
+msgid ""
+"Exploratory peer selection is discussed further on the\n"
+"<a href=\"%(peerselection)s\">Peer Profiling and Selection page</a>."
+msgstr ""
+
+#: i2p2www/pages/site/docs/tunnels/implementation.html:317
+msgid "Client tunnel peer selection"
+msgstr ""
+
+#: i2p2www/pages/site/docs/tunnels/implementation.html:319
+msgid ""
+"Client tunnels are built with a more stringent set of requirements - the "
+"local\n"
+"router will select peers out of its \"fast and high capacity\" profile "
+"category so\n"
+"that performance and reliability will meet the needs of the client "
+"application.\n"
+"However, there are several important details beyond that basic selection "
+"that \n"
+"should be adhered to, depending upon the client's anonymity needs."
+msgstr ""
+
+#: i2p2www/pages/site/docs/tunnels/implementation.html:327
+#, python-format
+msgid ""
+"Client peer selection is discussed further on the\n"
+"<a href=\"%(peerselection)s\">Peer Profiling and Selection page</a>."
+msgstr ""
+
+#: i2p2www/pages/site/docs/tunnels/implementation.html:332
+msgid "Peer Ordering within Tunnels"
+msgstr ""
+
+#: i2p2www/pages/site/docs/tunnels/implementation.html:334
+#, python-format
+msgid ""
+"Peers are ordered within tunnels to deal with the\n"
+"<a href=\"%(pdf)s\">predecessor attack</a>\n"
+"<a href=\"%(pdf2008)s\">(2008 update)</a>."
+msgstr ""
+
+#: i2p2www/pages/site/docs/tunnels/implementation.html:341
+msgid ""
+"To frustrate the predecessor \n"
+"attack, the tunnel selection keeps the peers selected in a strict order -"
+"\n"
+"if A, B, and C are in a tunnel for a particular tunnel pool, the hop "
+"after A is always B, and the hop after\n"
+"B is always C."
+msgstr ""
+
+#: i2p2www/pages/site/docs/tunnels/implementation.html:348
+msgid ""
+"Ordering is implemented by generating a random 32-byte key for each\n"
+"tunnel pool at startup.\n"
+"Peers should not be able to guess the ordering, or an attacker could\n"
+"craft two router hashes far apart to maximize the chance of being at both"
+"\n"
+"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:363
+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:370
+msgid "Request delivery"
+msgstr ""
+
+#: i2p2www/pages/site/docs/tunnels/implementation.html:372
+#, python-format
+msgid ""
+"A multi-hop tunnel is built using a single build message which is "
+"repeatedly\n"
+"decrypted and forwarded. In the terminology of\n"
+"<a href=\"%(pdf)s\">Hashing it out in Public</a>,\n"
+"this is \"non-interactive\" telescopic tunnel building."
+msgstr ""
+
+#: i2p2www/pages/site/docs/tunnels/implementation.html:379
+#, python-format
+msgid ""
+"This tunnel request preparation, delivery, and response method is\n"
+"<a href=\"%(tunnelcreation)s\">designed</a> 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:390
+#, python-format
+msgid ""
+"The details of tunnel request and response messages, and their "
+"encryption,\n"
+"<a href=\"%(tunnelcreation)s\">are specified here</a>."
+msgstr ""
+
+#: i2p2www/pages/site/docs/tunnels/implementation.html:395
+msgid ""
+"Peers may reject tunnel creation requests for a variety of reasons, "
+"though\n"
+"a series of four increasingly severe rejections are known: probabilistic "
+"rejection\n"
+"(due to approaching the router's capacity, or in response to a flood of "
+"requests), \n"
+"transient overload, bandwidth overload, and critical failure.  When "
+"received, \n"
+"those four are interpreted by the tunnel creator to help adjust their "
+"profile of\n"
+"the router in question."
+msgstr ""
+
+#: i2p2www/pages/site/docs/tunnels/implementation.html:404
+#, python-format
+msgid ""
+"For more information on peer profiling, see the\n"
+"<a href=\"%(peerselection)s\">Peer Profiling and Selection page</a>."
+msgstr ""
+
+#: i2p2www/pages/site/docs/tunnels/implementation.html:410
+msgid "Tunnel Pools"
+msgstr ""
+
+#: i2p2www/pages/site/docs/tunnels/implementation.html:412
+#, python-format
+msgid ""
+"To allow efficient operation, the router maintains a series of tunnel "
+"pools,\n"
+"each managing a group of tunnels used for a specific purpose with their "
+"own\n"
+"configuration.  When a tunnel is needed for that purpose, the router "
+"selects one\n"
+"out of the appropriate pool at random.  Overall, there are two "
+"exploratory tunnel\n"
+"pools - one inbound and one outbound - each using the router's default "
+"configuration.\n"
+"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 <a "
+"href=\"%(i2cp)s\">I2CP</a>, or the router's defaults if\n"
+"not specified."
+msgstr ""
+
+#: i2p2www/pages/site/docs/tunnels/implementation.html:424
+#, python-format
+msgid ""
+"Each pool has within its configuration a few key settings, defining how "
+"many\n"
+"tunnels to keep active, how many backup tunnels to maintain in case of "
+"failure,\n"
+"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 <a href=\"%(i2cp)s\">I2CP "
+"page</a>."
+msgstr ""
+
+#: i2p2www/pages/site/docs/tunnels/implementation.html:434
+msgid "Tunnel Lengths and Defaults"
+msgstr ""
+
+#: i2p2www/pages/site/docs/tunnels/implementation.html:436
+msgid "On the tunnel overview page"
+msgstr ""
+
+#: i2p2www/pages/site/docs/tunnels/implementation.html:438
+msgid "Anticipatory Build Strategy and Priority"
+msgstr ""
+
+#: i2p2www/pages/site/docs/tunnels/implementation.html:440
+msgid ""
+"Tunnel building is expensive, and tunnels expire a fixed time after they "
+"are built.\n"
+"However, when a pool that runs out of tunnels, the Destination is "
+"essentially dead.\n"
+"In addition, tunnel build success rate may vary greatly with both local "
+"and global\n"
+"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:451
+msgid ""
+"For each tuple {exploratory/client, in/out, length, length variance}\n"
+"the router maintains statistics on the time required for a successful\n"
+"tunnel build.\n"
+"Using these statistics, it calculates how long before a tunnel's "
+"expiration\n"
+"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:462
+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:471
+msgid "Tunnel Message Throttling"
+msgstr ""
+
+#: i2p2www/pages/site/docs/tunnels/implementation.html:473
+msgid ""
+"Even though the tunnels within I2P bear a resemblance to a circuit "
+"switched\n"
+"network, everything within I2P is strictly message based - tunnels are "
+"merely\n"
+"accounting tricks to help organize the delivery of messages.  No "
+"assumptions are\n"
+"made regarding reliability or ordering of messages, and retransmissions "
+"are left\n"
+"to higher levels (e.g. I2P's client layer streaming library).  This "
+"allows I2P\n"
+"to take advantage of throttling techniques available to both packet "
+"switched and\n"
+"circuit switched networks.  For instance, each router may keep track of "
+"the \n"
+"moving average of how much data each tunnel is using, combine that with "
+"all of \n"
+"the averages used by other tunnels the router is participating in, and be"
+" able\n"
+"to accept or reject additional tunnel participation requests based on its"
+" \n"
+"capacity and utilization.  On the other hand, each router can simply drop"
+" \n"
+"messages that are beyond its capacity, exploiting the research used on "
+"the \n"
+"normal Internet."
+msgstr ""
+
+#: i2p2www/pages/site/docs/tunnels/implementation.html:489
+msgid ""
+"In the current implementation, routers implement a\n"
+"weighted random early discard (WRED) strategy.\n"
+"For all participating routers (internal participant, inbound gateway, and"
+" outbound endpoint),\n"
+"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:507
+msgid "Mixing/batching"
+msgstr ""
+
+#: i2p2www/pages/site/docs/tunnels/implementation.html:509
+msgid ""
+"What strategies could be used at the gateway and at each hop for "
+"delaying,\n"
+"reordering, rerouting, or padding messages?  To what extent should this "
+"be done\n"
+"automatically, how much should be configured as a per tunnel or per hop "
+"setting,\n"
+"and how should the tunnel's creator (and in turn, user) control this "
+"operation?\n"
+"All of this is left as unknown, to be worked out for a distant future "
+"release."
+msgstr ""
+
+#: i2p2www/pages/site/docs/tunnels/implementation.html:518
+msgid "Padding"
+msgstr ""
+
+#: i2p2www/pages/site/docs/tunnels/implementation.html:519
+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:529
+msgid ""
+"WRED strategies have a significant impact on end-to-end performance,\n"
+"and prevention of network congestion collapse.\n"
+"The current WRED strategy should be carefully evaluated and improved."
+msgstr ""
+
+#: 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 <a "
+"href=\"%(tunnelimpl)s\">here</a> for the current implementation"
+msgstr ""
+
+#: i2p2www/pages/site/docs/tunnels/unidirectional.html:3
+msgid "November 2016"
+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 information 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 "Prehľad"
+
+#: 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 <a href=\"%(pdf)s\">paper by Hermann and Grothoff</a>\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 ""
+