# Translations template for I2P. # Copyright (C) 2021 ORGANIZATION # This file is distributed under the same license as the I2P project. # # Translators: # Scott Rhodes , 2020 # YFdyh000 , 2015-2016 msgid "" msgstr "" "Project-Id-Version: I2P\n" "Report-Msgid-Bugs-To: http://trac.i2p2.de\n" "POT-Creation-Date: 2021-10-11 16:26+0000\n" "PO-Revision-Date: 2013-07-15 11:59+0000\n" "Last-Translator: Scott Rhodes , 2020\n" "Language-Team: Chinese (China) (http://www.transifex.com/otf/I2P/language/zh_CN/)\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" "Language: zh_CN\n" "Plural-Forms: nplurals=1; plural=0;\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/09/21/0.9.2-Release.rst:17 #: i2p2www/blog/2012/10/27/0.9.3-Release.rst:17 #: i2p2www/blog/2012/12/17/0.9.4-Release.rst:27 #: i2p2www/blog/2013/03/08/0.9.5-Release.rst:20 #: i2p2www/blog/2013/05/28/0.9.6-Release.rst:20 msgid "Files are available on the `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:23 #: i2p2www/blog/2012/10/27/0.9.3-Release.rst:23 #: i2p2www/blog/2012/12/17/0.9.4-Release.rst:33 #: i2p2www/blog/2013/03/08/0.9.5-Release.rst:26 #: i2p2www/blog/2013/05/28/0.9.6-Release.rst:80 #: i2p2www/blog/2013/07/15/0.9.7-Release.rst:46 #: i2p2www/blog/2013/08/10/0.9.7.1-Release.rst:14 #: i2p2www/blog/2013/09/30/0.9.8-Release.rst:102 #: i2p2www/blog/2013/12/07/0.9.9-Release.rst:26 #: i2p2www/blog/2014/01/21/Syndie-1.105b-Release.rst:49 #: i2p2www/blog/2014/01/22/0.9.10-Release.rst:35 #: i2p2www/blog/2014/02/08/0.9.11-Release.rst:36 #: i2p2www/blog/2014/03/31/0.9.12-Release.rst:63 #: i2p2www/blog/2014/05/22/0.9.13-Release.rst:30 #: i2p2www/blog/2014/07/26/0.9.14-Release.rst:38 #: i2p2www/blog/2014/08/09/0.9.14.1-Release.rst:33 #: i2p2www/blog/2014/09/20/0.9.15-Release.rst:39 #: i2p2www/blog/2014/11/01/0.9.16-Release.rst:37 #: i2p2www/blog/2014/11/30/0.9.17-Release.rst:44 #: i2p2www/blog/2015/02/22/0.9.18-Release.rst:28 #: i2p2www/blog/2015/04/12/0.9.19-Release.rst:31 #: i2p2www/blog/2015/06/02/0.9.20-Release.rst:45 #: i2p2www/blog/2015/07/31/0.9.21-Release.rst:37 #: i2p2www/blog/2015/09/12/0.9.22-Release.rst:36 #: i2p2www/blog/2015/11/19/0.9.23-Release.rst:74 #: i2p2www/blog/2016/01/27/0.9.24-Release.rst:54 #: i2p2www/blog/2016/03/22/0.9.25-Release.rst:36 #: i2p2www/blog/2016/06/07/0.9.26-Release.rst:55 #: i2p2www/blog/2016/10/17/0.9.27-Release.rst:34 #: i2p2www/blog/2016/12/12/0.9.28-Release.rst:36 #: i2p2www/blog/2017/02/27/0.9.29-Release.rst:33 #: i2p2www/blog/2017/05/03/0.9.30-Release.rst:57 #: i2p2www/blog/2017/08/07/0.9.31-Release.rst:33 #: i2p2www/blog/2017/11/07/0.9.32-Release.rst:30 #: 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:35 #: i2p2www/blog/2018/08/23/0.9.36-Release.rst:33 #: i2p2www/blog/2018/10/04/0.9.37-Release.rst:26 #: i2p2www/blog/2019/01/22/0.9.38-Release.rst:33 #: i2p2www/blog/2019/03/21/0.9.39-Release.rst:34 #: i2p2www/blog/2019/05/07/0.9.40-Release.rst:34 #: i2p2www/blog/2019/07/02/0.9.41-Release.rst:34 #: i2p2www/blog/2019/08/27/0.9.42-Release.rst:30 #: i2p2www/blog/2019/10/22/0.9.43-Release.rst:29 #: i2p2www/blog/2019/12/01/0.9.44-Release.rst:35 #: i2p2www/blog/2020/02/25/0.9.45-Release.rst:28 #: i2p2www/blog/2020/05/25/0.9.46-Release.rst:40 #: i2p2www/blog/2020/08/24/0.9.47-Release.rst:33 #: i2p2www/blog/2020/11/30/0.9.48-Release.rst:33 #: i2p2www/blog/2021/02/17/0.9.49-Release.rst:45 #: i2p2www/blog/2021/05/17/0.9.50-Release.rst:35 #: i2p2www/blog/2021/08/23/1.5.0-Release.rst:34 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:25 #: i2p2www/blog/2012/10/27/0.9.3-Release.rst:25 #: i2p2www/blog/2012/12/17/0.9.4-Release.rst:35 #: i2p2www/blog/2013/09/30/0.9.8-Release.rst:104 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:33 #: i2p2www/blog/2012/10/27/0.9.3-Release.rst:31 #: i2p2www/blog/2012/12/17/0.9.4-Release.rst:40 #: i2p2www/blog/2013/05/28/0.9.6-Release.rst:82 #: i2p2www/blog/2013/07/15/0.9.7-Release.rst:55 #: i2p2www/blog/2013/09/30/0.9.8-Release.rst:113 #: i2p2www/blog/2013/12/07/0.9.9-Release.rst:34 #: i2p2www/blog/2014/01/21/Syndie-1.105b-Release.rst:52 #: i2p2www/blog/2014/01/22/0.9.10-Release.rst:41 #: i2p2www/blog/2014/02/08/0.9.11-Release.rst:42 #: i2p2www/blog/2014/03/31/0.9.12-Release.rst:74 #: i2p2www/blog/2014/05/22/0.9.13-Release.rst:40 #: i2p2www/blog/2014/07/26/0.9.14-Release.rst:51 #: i2p2www/blog/2014/08/09/0.9.14.1-Release.rst:36 #: i2p2www/blog/2014/09/20/0.9.15-Release.rst:52 #: i2p2www/blog/2014/11/01/0.9.16-Release.rst:56 #: i2p2www/blog/2014/11/30/0.9.17-Release.rst:54 #: i2p2www/blog/2015/02/22/0.9.18-Release.rst:31 #: i2p2www/blog/2015/04/12/0.9.19-Release.rst:41 #: i2p2www/blog/2015/06/02/0.9.20-Release.rst:58 #: i2p2www/blog/2015/07/31/0.9.21-Release.rst:53 #: i2p2www/blog/2015/09/12/0.9.22-Release.rst:44 #: i2p2www/blog/2015/11/19/0.9.23-Release.rst:81 #: i2p2www/blog/2016/01/27/0.9.24-Release.rst:64 #: i2p2www/blog/2016/03/22/0.9.25-Release.rst:48 #: i2p2www/blog/2016/06/07/0.9.26-Release.rst:72 #: i2p2www/blog/2016/10/17/0.9.27-Release.rst:44 #: i2p2www/blog/2016/12/12/0.9.28-Release.rst:48 #: i2p2www/blog/2017/02/27/0.9.29-Release.rst:49 #: i2p2www/blog/2017/05/03/0.9.30-Release.rst:69 #: i2p2www/blog/2017/08/07/0.9.31-Release.rst:42 #: i2p2www/blog/2017/11/07/0.9.32-Release.rst:38 #: 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:44 #: i2p2www/blog/2018/08/23/0.9.36-Release.rst:43 #: i2p2www/blog/2018/10/04/0.9.37-Release.rst:35 #: i2p2www/blog/2019/01/22/0.9.38-Release.rst:46 #: i2p2www/blog/2019/03/21/0.9.39-Release.rst:44 #: i2p2www/blog/2019/05/07/0.9.40-Release.rst:51 #: i2p2www/blog/2019/07/02/0.9.41-Release.rst:45 #: i2p2www/blog/2019/08/27/0.9.42-Release.rst:46 #: i2p2www/blog/2019/10/22/0.9.43-Release.rst:39 #: i2p2www/blog/2019/12/01/0.9.44-Release.rst:48 #: i2p2www/blog/2020/02/25/0.9.45-Release.rst:41 #: i2p2www/blog/2020/05/25/0.9.46-Release.rst:52 #: i2p2www/blog/2020/08/24/0.9.47-Release.rst:49 #: i2p2www/blog/2020/11/30/0.9.48-Release.rst:51 #: i2p2www/blog/2021/02/17/0.9.49-Release.rst:64 #: i2p2www/blog/2021/05/17/0.9.50-Release.rst:51 #: i2p2www/blog/2021/08/23/1.5.0-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:42 #: i2p2www/blog/2012/10/27/0.9.3-Release.rst:37 #: i2p2www/blog/2012/12/17/0.9.4-Release.rst:52 #: i2p2www/blog/2013/03/08/0.9.5-Release.rst:44 #: i2p2www/blog/2013/05/28/0.9.6-Release.rst:95 #: i2p2www/blog/2013/07/15/0.9.7-Release.rst:64 #: i2p2www/blog/2013/08/10/0.9.7.1-Release.rst:20 #: i2p2www/blog/2013/09/30/0.9.8-Release.rst:119 #: i2p2www/blog/2013/12/07/0.9.9-Release.rst:52 #: i2p2www/blog/2014/01/21/Syndie-1.105b-Release.rst:100 #: i2p2www/blog/2014/01/22/0.9.10-Release.rst:50 #: i2p2www/blog/2014/02/08/0.9.11-Release.rst:48 #: i2p2www/blog/2014/03/31/0.9.12-Release.rst:85 #: i2p2www/blog/2014/05/22/0.9.13-Release.rst:50 #: i2p2www/blog/2014/07/26/0.9.14-Release.rst:58 #: i2p2www/blog/2014/08/09/0.9.14.1-Release.rst:43 #: i2p2www/blog/2014/09/20/0.9.15-Release.rst:61 #: i2p2www/blog/2014/11/01/0.9.16-Release.rst:69 #: i2p2www/blog/2014/11/30/0.9.17-Release.rst:66 #: i2p2www/blog/2015/02/22/0.9.18-Release.rst:39 #: i2p2www/blog/2015/04/12/0.9.19-Release.rst:50 #: i2p2www/blog/2015/06/02/0.9.20-Release.rst:76 #: i2p2www/blog/2015/07/31/0.9.21-Release.rst:66 #: i2p2www/blog/2015/09/12/0.9.22-Release.rst:52 #: i2p2www/blog/2015/11/19/0.9.23-Release.rst:90 #: i2p2www/blog/2016/01/27/0.9.24-Release.rst:77 #: i2p2www/blog/2016/03/22/0.9.25-Release.rst:54 #: i2p2www/blog/2016/06/07/0.9.26-Release.rst:84 #: i2p2www/blog/2016/10/17/0.9.27-Release.rst:59 #: i2p2www/blog/2016/12/12/0.9.28-Release.rst:58 #: i2p2www/blog/2017/02/27/0.9.29-Release.rst:63 #: i2p2www/blog/2017/05/03/0.9.30-Release.rst:83 #: i2p2www/blog/2017/08/07/0.9.31-Release.rst:55 #: i2p2www/blog/2017/11/07/0.9.32-Release.rst:45 #: 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:56 #: i2p2www/blog/2018/08/23/0.9.36-Release.rst:53 #: i2p2www/blog/2018/10/04/0.9.37-Release.rst:42 #: i2p2www/blog/2019/01/22/0.9.38-Release.rst:56 #: i2p2www/blog/2019/03/21/0.9.39-Release.rst:55 #: i2p2www/blog/2019/05/07/0.9.40-Release.rst:60 #: i2p2www/blog/2019/07/02/0.9.41-Release.rst:56 #: i2p2www/blog/2019/08/27/0.9.42-Release.rst:55 #: i2p2www/blog/2019/10/22/0.9.43-Release.rst:48 #: i2p2www/blog/2019/12/01/0.9.44-Release.rst:61 #: i2p2www/blog/2020/02/25/0.9.45-Release.rst:48 #: i2p2www/blog/2020/05/25/0.9.46-Release.rst:61 #: i2p2www/blog/2020/08/24/0.9.47-Release.rst:62 #: i2p2www/blog/2020/11/30/0.9.48-Release.rst:65 #: i2p2www/blog/2021/02/17/0.9.49-Release.rst:76 #: i2p2www/blog/2021/05/17/0.9.50-Release.rst:74 #: i2p2www/blog/2021/08/23/1.5.0-Release.rst:52 msgid "Other" msgstr "其他" #: 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:53 #: i2p2www/blog/2012/10/27/0.9.3-Release.rst:57 #: i2p2www/blog/2012/12/17/0.9.4-Release.rst:68 #: i2p2www/blog/2013/03/08/0.9.5-Release.rst:57 #: i2p2www/blog/2013/05/28/0.9.6-Release.rst:111 #: i2p2www/blog/2013/07/15/0.9.7-Release.rst:80 #: i2p2www/blog/2013/08/10/0.9.7.1-Release.rst:31 #: i2p2www/blog/2013/09/30/0.9.8-Release.rst:130 #: i2p2www/blog/2013/10/02/0.9.8.1-Release.rst:29 #: i2p2www/blog/2013/12/07/0.9.9-Release.rst:76 #: i2p2www/blog/2014/01/22/0.9.10-Release.rst:65 #: i2p2www/blog/2014/02/08/0.9.11-Release.rst:60 #: i2p2www/blog/2014/03/31/0.9.12-Release.rst:102 #: i2p2www/blog/2014/05/22/0.9.13-Release.rst:63 #: i2p2www/blog/2014/07/26/0.9.14-Release.rst:74 #: i2p2www/blog/2014/08/09/0.9.14.1-Release.rst:53 #: i2p2www/blog/2014/09/20/0.9.15-Release.rst:77 #: i2p2www/blog/2014/11/01/0.9.16-Release.rst:87 #: i2p2www/blog/2014/11/30/0.9.17-Release.rst:82 #: i2p2www/blog/2015/02/22/0.9.18-Release.rst:62 #: i2p2www/blog/2015/04/12/0.9.19-Release.rst:70 #: i2p2www/blog/2015/06/02/0.9.20-Release.rst:102 #: i2p2www/blog/2015/07/31/0.9.21-Release.rst:76 #: i2p2www/blog/2015/09/12/0.9.22-Release.rst:58 #: i2p2www/blog/2015/11/19/0.9.23-Release.rst:116 #: i2p2www/blog/2016/01/27/0.9.24-Release.rst:106 #: i2p2www/blog/2016/03/22/0.9.25-Release.rst:77 #: i2p2www/blog/2016/06/07/0.9.26-Release.rst:97 #: i2p2www/blog/2016/10/17/0.9.27-Release.rst:74 #: i2p2www/blog/2016/12/12/0.9.28-Release.rst:104 #: i2p2www/blog/2017/02/27/0.9.29-Release.rst:78 #: i2p2www/blog/2017/03/04/0.9.29-Windows-Installer-Fix.rst:26 #: i2p2www/blog/2017/05/03/0.9.30-Release.rst:103 #: i2p2www/blog/2017/08/07/0.9.31-Release.rst:70 #: i2p2www/blog/2017/11/07/0.9.32-Release.rst:59 #: 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:78 #: i2p2www/blog/2018/08/23/0.9.36-Release.rst:73 #: i2p2www/blog/2018/10/04/0.9.37-Release.rst:55 #: i2p2www/blog/2019/01/22/0.9.38-Release.rst:72 #: i2p2www/blog/2019/03/21/0.9.39-Release.rst:72 #: i2p2www/blog/2019/05/07/0.9.40-Release.rst:75 #: i2p2www/blog/2019/07/02/0.9.41-Release.rst:75 #: i2p2www/blog/2019/08/27/0.9.42-Release.rst:69 #: i2p2www/blog/2019/10/22/0.9.43-Release.rst:66 #: i2p2www/blog/2019/12/01/0.9.44-Release.rst:75 #: i2p2www/blog/2020/02/25/0.9.45-Release.rst:65 #: i2p2www/blog/2020/05/25/0.9.46-Release.rst:87 #: i2p2www/blog/2020/08/24/0.9.47-Release.rst:76 #: i2p2www/blog/2020/11/30/0.9.48-Release.rst:93 #: i2p2www/blog/2021/02/17/0.9.49-Release.rst:97 #: i2p2www/blog/2021/05/17/0.9.50-Release.rst:94 #: i2p2www/blog/2021/08/23/1.5.0-Release.rst:66 msgid "SHA256 Checksums:" msgstr "SHA256 校验：" #: 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 "Wrapper 更新" #: i2p2www/blog/2012/05/02/0.9-Release.rst:23 msgid "Update Info" msgstr "更新信息" #: i2p2www/blog/2012/07/30/0.9.1-Release.rst:12 msgid "Files are available on the `download page`_." msgstr "文件在`下载页面`_可用。" #: i2p2www/blog/2012/07/30/0.9.1-Release.rst:16 msgid "`download page`" msgstr "`下载页面`" #: i2p2www/blog/2012/09/21/0.9.2-Release.rst:2 msgid "0.9.2 Release" msgstr "0.9.2发布" #: i2p2www/blog/2012/09/21/0.9.2-Release.rst:8 #: i2p2www/blog/2012/09/21/0.9.2-Release.rst:10 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:13 #: i2p2www/blog/2012/10/27/0.9.3-Release.rst:13 msgid "" "As usual, there's also lots of bug fixes in this release, so updating is " "recommended." msgstr "如往常一样，此发布中也修复了很多bug，所以推荐更新。" #: i2p2www/blog/2012/09/21/0.9.2-Release.rst:27 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:28 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:29 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:30 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:31 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:35 msgid "" "Fix various issues affecting memory usage and performance on high-bandwidth " "routers" msgstr "" #: i2p2www/blog/2012/09/21/0.9.2-Release.rst:36 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:37 msgid "" "Fix i2psnark bug that prevented a completion announcement to the tracker" msgstr "" #: i2p2www/blog/2012/09/21/0.9.2-Release.rst:38 msgid "Fix a lock contention problem in i2ptunnel" msgstr "修复一个 i2ptunnel 中锁定争用问题" #: i2p2www/blog/2012/09/21/0.9.2-Release.rst:39 msgid "Fix some OSX installation issues" msgstr "修复一些 OSX 安装问题" #: i2p2www/blog/2012/09/21/0.9.2-Release.rst:40 msgid "Remove uses of direct byte buffers that may have been leaking" msgstr "" #: i2p2www/blog/2012/09/21/0.9.2-Release.rst:44 msgid "Reduce overhead in network messages" msgstr "减少网络消息开销" #: i2p2www/blog/2012/09/21/0.9.2-Release.rst:45 msgid "Add \"universal\" theme support" msgstr "添加“通用”主题支持" #: i2p2www/blog/2012/09/21/0.9.2-Release.rst:46 msgid "Theme updates" msgstr "主题更新" #: i2p2www/blog/2012/09/21/0.9.2-Release.rst:47 msgid "Add a jbigi library for Raspberry Pi" msgstr "为Raspberry Pi（树莓派）添加一个jbigi库" #: i2p2www/blog/2012/09/21/0.9.2-Release.rst:48 msgid "New Scala unit test framework" msgstr "新的Scala单元测试框架" #: i2p2www/blog/2012/09/21/0.9.2-Release.rst:49 msgid "Translation updates for Czech, Dutch, German, and Greek" msgstr "捷克语、荷兰语、德语和希腊语翻译更新" #: i2p2www/blog/2012/09/21/0.9.2-Release.rst:50 msgid "Update wrapper to 3.5.15 (new installs and PPA only)" msgstr "更新wrapper到3.5.15（仅新安装和PPA）" #: i2p2www/blog/2012/09/21/0.9.2-Release.rst:51 #: i2p2www/blog/2012/10/27/0.9.3-Release.rst:54 #: i2p2www/blog/2012/12/17/0.9.4-Release.rst:64 #: i2p2www/blog/2013/03/08/0.9.5-Release.rst:54 #: i2p2www/blog/2013/05/28/0.9.6-Release.rst:109 #: i2p2www/blog/2013/07/15/0.9.7-Release.rst:78 #: i2p2www/blog/2013/09/30/0.9.8-Release.rst:128 #: i2p2www/blog/2013/12/07/0.9.9-Release.rst:74 #: i2p2www/blog/2014/01/22/0.9.10-Release.rst:63 #: i2p2www/blog/2014/02/08/0.9.11-Release.rst:58 #: i2p2www/blog/2014/03/31/0.9.12-Release.rst:98 #: i2p2www/blog/2014/05/22/0.9.13-Release.rst:59 #: i2p2www/blog/2014/07/26/0.9.14-Release.rst:71 #: i2p2www/blog/2014/08/09/0.9.14.1-Release.rst:50 #: i2p2www/blog/2014/11/01/0.9.16-Release.rst:84 #: i2p2www/blog/2014/11/30/0.9.17-Release.rst:79 #: i2p2www/blog/2015/02/22/0.9.18-Release.rst:59 #: i2p2www/blog/2015/04/12/0.9.19-Release.rst:67 #: i2p2www/blog/2015/06/02/0.9.20-Release.rst:97 #: i2p2www/blog/2015/07/31/0.9.21-Release.rst:73 #: i2p2www/blog/2015/09/12/0.9.22-Release.rst:55 #: i2p2www/blog/2015/11/19/0.9.23-Release.rst:113 #: i2p2www/blog/2016/01/27/0.9.24-Release.rst:98 #: i2p2www/blog/2016/03/22/0.9.25-Release.rst:69 #: i2p2www/blog/2016/06/07/0.9.26-Release.rst:89 #: i2p2www/blog/2016/10/17/0.9.27-Release.rst:66 #: i2p2www/blog/2016/12/12/0.9.28-Release.rst:96 #: i2p2www/blog/2017/02/27/0.9.29-Release.rst:70 #: i2p2www/blog/2017/05/03/0.9.30-Release.rst:95 #: i2p2www/blog/2017/08/07/0.9.31-Release.rst:61 #: i2p2www/blog/2017/11/07/0.9.32-Release.rst:50 #: i2p2www/blog/2018/04/10/0.9.34-Release.rst:55 #: i2p2www/blog/2018/06/26/0.9.35-Release.rst:70 #: i2p2www/blog/2019/01/22/0.9.38-Release.rst:64 msgid "Update GeoIP data (new installs and PPA only)" msgstr "更新GeoIP数据（仅新安装和PPA）" #: 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:8 #: i2p2www/blog/2012/10/27/0.9.3-Release.rst:10 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:27 msgid "Active Queue Management" msgstr "主动队列管理" #: i2p2www/blog/2012/10/27/0.9.3-Release.rst:28 msgid "Priority queues" msgstr "优先级队列" #: i2p2www/blog/2012/10/27/0.9.3-Release.rst:29 msgid "I2PSnark DHT: Several bug fixes, enable by default." msgstr "" #: i2p2www/blog/2012/10/27/0.9.3-Release.rst:33 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:34 msgid "Fix piece selection (rarest-first) bugs in i2psnark" msgstr "" #: i2p2www/blog/2012/10/27/0.9.3-Release.rst:35 msgid "Fix bug causing multiple browsers to open at startup" msgstr "" #: i2p2www/blog/2012/10/27/0.9.3-Release.rst:39 msgid "Improvements in caching" msgstr "改善缓存" #: i2p2www/blog/2012/10/27/0.9.3-Release.rst:40 msgid "Several synchronization fixes and lock contention reduction" msgstr "几点同步修复和锁争用减少" #: i2p2www/blog/2012/10/27/0.9.3-Release.rst:41 msgid "Major reduction in SSU buffers memory use" msgstr "显著减少SSU缓冲区内存使用量" #: i2p2www/blog/2012/10/27/0.9.3-Release.rst:42 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:43 msgid "Improved defenses in i2ptunnel for \"darkloris\"" msgstr "i2ptunnel 中对 \"darkloris\" 改进的防护加固" #: i2p2www/blog/2012/10/27/0.9.3-Release.rst:44 msgid "More validation at torrent creation in i2psnark" msgstr "" #: i2p2www/blog/2012/10/27/0.9.3-Release.rst:45 msgid "Several parameter changes in SSU to improve throughput" msgstr "" #: i2p2www/blog/2012/10/27/0.9.3-Release.rst:46 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:47 msgid "Remove duplicate messages from logs" msgstr "" #: i2p2www/blog/2012/10/27/0.9.3-Release.rst:48 msgid "Don't respond to blocked streaming connections with a reset, just drop" msgstr "" #: i2p2www/blog/2012/10/27/0.9.3-Release.rst:49 msgid "Remove all uses of inefficient SimpleTimer" msgstr "" #: i2p2www/blog/2012/10/27/0.9.3-Release.rst:50 msgid "More checks for valid IPs and ports entered in console" msgstr "" #: i2p2www/blog/2012/10/27/0.9.3-Release.rst:51 msgid "Fix bug that wasted a lot of entropy" msgstr "" #: i2p2www/blog/2012/10/27/0.9.3-Release.rst:52 msgid "Translation updates: Italian, Portuguese, Spanish, Swedish" msgstr "" #: i2p2www/blog/2012/10/27/0.9.3-Release.rst:53 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:8 #: i2p2www/blog/2012/12/17/0.9.4-Release.rst:10 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:14 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:20 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:37 msgid "" "Big rework of the update system; Preliminary support for updates via " "i2psnark" msgstr "" #: i2p2www/blog/2012/12/17/0.9.4-Release.rst:38 msgid "Add per-destination outbound priorities" msgstr "" #: i2p2www/blog/2012/12/17/0.9.4-Release.rst:42 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:43 msgid "" "Fix bug with external I2CP that prevented some external apps from working" msgstr "" #: i2p2www/blog/2012/12/17/0.9.4-Release.rst:44 msgid "Fixed several bugs in i2psnark DHT" msgstr "" #: i2p2www/blog/2012/12/17/0.9.4-Release.rst:45 msgid "Fixed bug in i2psnark PEX that inflated peer counts" msgstr "" #: i2p2www/blog/2012/12/17/0.9.4-Release.rst:46 msgid "Handle dropped I2CP messages better" msgstr "" #: i2p2www/blog/2012/12/17/0.9.4-Release.rst:47 msgid "Reduce overhead of I2CP messages" msgstr "" #: i2p2www/blog/2012/12/17/0.9.4-Release.rst:48 msgid "Enforce max size in transport outbound message queues" msgstr "" #: i2p2www/blog/2012/12/17/0.9.4-Release.rst:49 msgid "Fixes for Windows eepget.bat (new installs and PPA only)" msgstr "" #: i2p2www/blog/2012/12/17/0.9.4-Release.rst:50 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:54 msgid "" "More performance improvements, memory reduction, and object churn reduction" msgstr "" #: i2p2www/blog/2012/12/17/0.9.4-Release.rst:55 msgid "Better detection of network disconnections" msgstr "" #: i2p2www/blog/2012/12/17/0.9.4-Release.rst:56 msgid "Further improvements in the SSU transport" msgstr "" #: i2p2www/blog/2012/12/17/0.9.4-Release.rst:57 msgid "Add console password form" msgstr "" #: i2p2www/blog/2012/12/17/0.9.4-Release.rst:58 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:59 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:60 msgid "" "Initial work on new interfaces to manage applications started via " "clients.config" msgstr "" #: i2p2www/blog/2012/12/17/0.9.4-Release.rst:61 msgid "Increase minimum peer port to 1024" msgstr "" #: i2p2www/blog/2012/12/17/0.9.4-Release.rst:62 msgid "Increase granularity of bandwidth limiter for smoother transmissions" msgstr "" #: i2p2www/blog/2012/12/17/0.9.4-Release.rst:63 msgid "" "Translation updates: Chinese, French, German, Italian, Polish, Portuguese, " "Swedish, and Ukrainian" msgstr "" #: i2p2www/blog/2012/12/17/0.9.4-Release.rst:65 msgid "Update wrapper to 3.5.16 (new installs and PPA only)" msgstr "" #: i2p2www/blog/2012/12/17/0.9.4-Release.rst:66 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:8 #: i2p2www/blog/2013/03/08/0.9.5-Release.rst:10 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:14 #, 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:28 msgid "Defenses and Bug Fixes" msgstr "防护加固和问题修复" #: i2p2www/blog/2013/03/08/0.9.5-Release.rst:30 msgid "Fix router bug causing lockup when using iMule" msgstr "修复路由器问题导致使用 iMule 时的网络查询" #: i2p2www/blog/2013/03/08/0.9.5-Release.rst:31 msgid "Recognize, handle, reject duplicate tunnel IDs" msgstr "识别、处理和拒绝重复的隧道ID" #: i2p2www/blog/2013/03/08/0.9.5-Release.rst:32 msgid "Fix changing of the log file name" msgstr "修复日志文件名的更改" #: i2p2www/blog/2013/03/08/0.9.5-Release.rst:33 msgid "Prevent hashcode attack in session tags" msgstr "避免会话标签中的哈希码攻击" #: i2p2www/blog/2013/03/08/0.9.5-Release.rst:34 msgid "Add build request throttler based on previous hop" msgstr "" #: i2p2www/blog/2013/03/08/0.9.5-Release.rst:35 msgid "Limit concurrent next-hop lookups" msgstr "" #: i2p2www/blog/2013/03/08/0.9.5-Release.rst:36 msgid "Catch exceptions storing nonces in console" msgstr "" #: i2p2www/blog/2013/03/08/0.9.5-Release.rst:37 msgid "Fix saving graph settings in console" msgstr "" #: i2p2www/blog/2013/03/08/0.9.5-Release.rst:38 msgid "Fix eepget generation of URLs when not proxied" msgstr "" #: i2p2www/blog/2013/03/08/0.9.5-Release.rst:39 msgid "" "Encrypt database lookup messages end-to-end when sent through exploratory " "tunnels" msgstr "" #: i2p2www/blog/2013/03/08/0.9.5-Release.rst:40 msgid "Don't use multiple floodfills from the same /16 in a query" msgstr "" #: i2p2www/blog/2013/03/08/0.9.5-Release.rst:41 msgid "Randomize delay before verifying floodfill store" msgstr "验证种子存储前随机化延迟" #: i2p2www/blog/2013/03/08/0.9.5-Release.rst:42 msgid "Increase number of floodfills" msgstr "增加种子的数量" #: i2p2www/blog/2013/03/08/0.9.5-Release.rst:46 msgid "Improve support for mobile browsers" msgstr "" #: i2p2www/blog/2013/03/08/0.9.5-Release.rst:47 msgid "Partial defenses for UCSB attacks" msgstr "对 UCSB 攻击的部分防护" #: i2p2www/blog/2013/03/08/0.9.5-Release.rst:48 msgid "Add announce list support to i2psnark" msgstr "" #: i2p2www/blog/2013/03/08/0.9.5-Release.rst:49 msgid "Jetty: upgrade Apache Tomcat to 6.0.36" msgstr "" #: i2p2www/blog/2013/03/08/0.9.5-Release.rst:50 msgid "Split router info files into multiple subdirectories" msgstr "" #: i2p2www/blog/2013/03/08/0.9.5-Release.rst:51 msgid "Add IP to hostname mapping option in SOCKS" msgstr "" #: i2p2www/blog/2013/03/08/0.9.5-Release.rst:52 msgid "Improve PRNG seeding" msgstr "" #: i2p2www/blog/2013/03/08/0.9.5-Release.rst:53 msgid "" "Translation updates: French, German, Hungarian, Italian, Norwegian, Polish, " "Portuguese, Russian, Swedish" msgstr "" #: i2p2www/blog/2013/03/08/0.9.5-Release.rst:55 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:8 #: i2p2www/blog/2013/05/28/0.9.6-Release.rst:10 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:14 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:26 msgid "Important fix for Windows Eepsites, first install 0.9.5 only" msgstr "" #: i2p2www/blog/2013/05/28/0.9.6-Release.rst:28 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:35 msgid "See `this page`__ for instructions." msgstr "" #: i2p2www/blog/2013/05/28/0.9.6-Release.rst:41 msgid "Jetty 7 Migration Details" msgstr "" #: i2p2www/blog/2013/05/28/0.9.6-Release.rst:43 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:49 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:51 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:56 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:70 msgid "Plugins" msgstr "插件" #: i2p2www/blog/2013/05/28/0.9.6-Release.rst:72 msgid "Most plugins should work fine with Jetty 7." msgstr "" #: i2p2www/blog/2013/05/28/0.9.6-Release.rst:76 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:78 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:84 msgid "Several bugs with Windows installation (see above)" msgstr "几个 Windows 安装包的问题（见上）" #: i2p2www/blog/2013/05/28/0.9.6-Release.rst:85 msgid "Fix default form action in i2ptunnel" msgstr "修复 i2ptunnel 中的默认操作" #: i2p2www/blog/2013/05/28/0.9.6-Release.rst:86 msgid "Fix links on iframed console pages" msgstr "" #: i2p2www/blog/2013/05/28/0.9.6-Release.rst:87 msgid "Better detection of 64-bit Windows to prevent crashes by systray" msgstr "更好的检测 64-bit Windows 以避免系统托盘崩溃" #: i2p2www/blog/2013/05/28/0.9.6-Release.rst:88 msgid "Fix bug preventing router update via torrent" msgstr "修复问题，防止阻止通过BT种子进行路由器更新" #: i2p2www/blog/2013/05/28/0.9.6-Release.rst:89 msgid "Several SSU fixes for NATs that change UDP ports" msgstr "" #: i2p2www/blog/2013/05/28/0.9.6-Release.rst:90 msgid "" "Ignore unsupported IPs in RouterInfos when selecting an address (prep for " "IPv6)" msgstr "" #: i2p2www/blog/2013/05/28/0.9.6-Release.rst:91 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:92 msgid "Fix HTTP proxy error response for malformed URIs" msgstr "" #: i2p2www/blog/2013/05/28/0.9.6-Release.rst:93 msgid "Recognize UPnP devices without port forwarding capability" msgstr "" #: i2p2www/blog/2013/05/28/0.9.6-Release.rst:97 msgid "Jetty 7.6.10 (see above for migration information)" msgstr "" #: i2p2www/blog/2013/05/28/0.9.6-Release.rst:98 msgid "Limit page size in i2psnark" msgstr "" #: i2p2www/blog/2013/05/28/0.9.6-Release.rst:99 msgid "Add data directory and page size configuration to i2psnark" msgstr "" #: i2p2www/blog/2013/05/28/0.9.6-Release.rst:100 msgid "Support multiple i2psnark instances" msgstr "" #: i2p2www/blog/2013/05/28/0.9.6-Release.rst:101 msgid "Piece size adjustments in i2psnark" msgstr "" #: i2p2www/blog/2013/05/28/0.9.6-Release.rst:102 msgid "Add more graphing support for combined bandwidth graph" msgstr "" #: i2p2www/blog/2013/05/28/0.9.6-Release.rst:103 msgid "Block b32.i2p supercookies" msgstr "" #: i2p2www/blog/2013/05/28/0.9.6-Release.rst:104 msgid "Allow stopping clients on /configclients" msgstr "" #: i2p2www/blog/2013/05/28/0.9.6-Release.rst:105 msgid "Check for nonce count replays in HTTP client" msgstr "" #: i2p2www/blog/2013/05/28/0.9.6-Release.rst:106 msgid "Support SASL authentication in IRC proxy" msgstr "" #: i2p2www/blog/2013/05/28/0.9.6-Release.rst:107 msgid "Several cleanups and minor fixes in the update manager" msgstr "" #: i2p2www/blog/2013/05/28/0.9.6-Release.rst:108 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:8 #: i2p2www/blog/2013/07/15/0.9.7-Release.rst:10 msgid "0.9.7 includes significant bug fixes and improvements." msgstr "" #: i2p2www/blog/2013/07/15/0.9.7-Release.rst:12 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:21 #, 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:26 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:31 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:35 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:48 #: i2p2www/blog/2013/08/10/0.9.7.1-Release.rst:16 #: i2p2www/blog/2013/09/30/0.9.8-Release.rst:108 #: i2p2www/blog/2013/12/07/0.9.9-Release.rst:28 #: i2p2www/blog/2014/01/22/0.9.10-Release.rst:37 #: i2p2www/blog/2014/02/08/0.9.11-Release.rst:38 #: i2p2www/blog/2014/03/31/0.9.12-Release.rst:65 msgid "Anonymity Improvements" msgstr "" #: i2p2www/blog/2013/07/15/0.9.7-Release.rst:50 msgid "End-to-end encryption of responses to leaseset lookups" msgstr "" #: i2p2www/blog/2013/07/15/0.9.7-Release.rst:51 msgid "Expand floodfill pool by enabling class 'N' floodfills" msgstr "" #: i2p2www/blog/2013/07/15/0.9.7-Release.rst:52 msgid "Randomize padding inside encrypted SSU packets" msgstr "" #: i2p2www/blog/2013/07/15/0.9.7-Release.rst:53 msgid "Preparation for better SSU protocol obfuscation" msgstr "" #: i2p2www/blog/2013/07/15/0.9.7-Release.rst:57 msgid "Fix newer lease sets not getting stored or published" msgstr "" #: i2p2www/blog/2013/07/15/0.9.7-Release.rst:58 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:59 msgid "Fix addressbook database bug preventing update of the reverse index" msgstr "" #: i2p2www/blog/2013/07/15/0.9.7-Release.rst:60 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:61 msgid "Fix version checking for plugins" msgstr "" #: i2p2www/blog/2013/07/15/0.9.7-Release.rst:62 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:66 msgid "Don't install as a service on Windows by default" msgstr "" #: i2p2www/blog/2013/07/15/0.9.7-Release.rst:67 msgid "Reduce transport idle timeouts" msgstr "" #: i2p2www/blog/2013/07/15/0.9.7-Release.rst:68 msgid "Reduce tunnels on idle in i2psnark" msgstr "" #: i2p2www/blog/2013/07/15/0.9.7-Release.rst:69 msgid "Change default in i2ptunnel GUI to 3 hops" msgstr "" #: i2p2www/blog/2013/07/15/0.9.7-Release.rst:70 msgid "IE 10 support" msgstr "" #: i2p2www/blog/2013/07/15/0.9.7-Release.rst:71 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:72 msgid "Low-level encryption and XOR speedups" msgstr "" #: i2p2www/blog/2013/07/15/0.9.7-Release.rst:73 msgid "Jetty 7.6.11" msgstr "" #: i2p2www/blog/2013/07/15/0.9.7-Release.rst:74 msgid "Tomcat 6.0.37" msgstr "" #: i2p2www/blog/2013/07/15/0.9.7-Release.rst:75 msgid "" "Translation updates: Chinese, French, German, Portuguese, Russian, Spanish" msgstr "" #: i2p2www/blog/2013/07/15/0.9.7-Release.rst:76 msgid "New Turkish translation" msgstr "" #: i2p2www/blog/2013/07/15/0.9.7-Release.rst:77 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:8 #: i2p2www/blog/2013/08/10/0.9.7.1-Release.rst:10 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:12 msgid "As usual, we recommend that all users update to this release." msgstr "" #: i2p2www/blog/2013/08/10/0.9.7.1-Release.rst:18 msgid "Disable RouterInfo verification messages" msgstr "" #: i2p2www/blog/2013/08/10/0.9.7.1-Release.rst:22 msgid "Extend inbound tunnel expiration" msgstr "" #: i2p2www/blog/2013/08/10/0.9.7.1-Release.rst:23 msgid "i2prouter: bashism fix" msgstr "" #: i2p2www/blog/2013/08/10/0.9.7.1-Release.rst:24 msgid "i2psnark: increase max piece size, mime type updates" msgstr "" #: i2p2www/blog/2013/08/10/0.9.7.1-Release.rst:25 msgid "New reseed host" msgstr "" #: i2p2www/blog/2013/08/10/0.9.7.1-Release.rst:26 msgid "New update hosts, thanks Meeh and dg" msgstr "" #: i2p2www/blog/2013/08/10/0.9.7.1-Release.rst:27 msgid "Streaming: RTO changes" msgstr "" #: i2p2www/blog/2013/08/10/0.9.7.1-Release.rst:28 msgid "Updater: Increase update-via-torrent to 30 percent" msgstr "" #: i2p2www/blog/2013/08/10/0.9.7.1-Release.rst:29 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:8 #: i2p2www/blog/2013/09/30/0.9.8-Release.rst:10 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:12 #, 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:14 msgid "IPv6 Details" msgstr "" #: i2p2www/blog/2013/09/30/0.9.8-Release.rst:16 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:23 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:35 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:43 msgid "Rekeying Details" msgstr "" #: i2p2www/blog/2013/09/30/0.9.8-Release.rst:45 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:55 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:64 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:70 msgid "More Changes Coming" msgstr "" #: i2p2www/blog/2013/09/30/0.9.8-Release.rst:72 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:82 msgid "New Website" msgstr "" #: i2p2www/blog/2013/09/30/0.9.8-Release.rst:84 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:92 msgid "Community Participation" msgstr "" #: i2p2www/blog/2013/09/30/0.9.8-Release.rst:94 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:106 msgid "IPv6 support for both NTCP and SSU" msgstr "" #: i2p2www/blog/2013/09/30/0.9.8-Release.rst:110 msgid "SSU protocol obfuscation by adding random padding" msgstr "" #: i2p2www/blog/2013/09/30/0.9.8-Release.rst:111 msgid "Longer encryption and DH private keys for users on faster platforms" msgstr "" #: i2p2www/blog/2013/09/30/0.9.8-Release.rst:115 msgid "Fix I2PTunnel / I2CP locking and duplicates (partial)" msgstr "" #: i2p2www/blog/2013/09/30/0.9.8-Release.rst:116 msgid "Fix translation of HTTP proxy error pages" msgstr "" #: i2p2www/blog/2013/09/30/0.9.8-Release.rst:117 msgid "Fix occasional runtime exception in NTCP" msgstr "" #: i2p2www/blog/2013/09/30/0.9.8-Release.rst:121 msgid "" "Big rework of transport code to accommodate multiple addresses and IPv6" msgstr "" #: i2p2www/blog/2013/09/30/0.9.8-Release.rst:122 msgid "Streaming: Improved recovery from lost acks, other fixes" msgstr "" #: i2p2www/blog/2013/09/30/0.9.8-Release.rst:123 msgid "" "Use Transifex for translation of initial news and HTTP proxy error pages" msgstr "" #: i2p2www/blog/2013/09/30/0.9.8-Release.rst:124 msgid "" "Translation updates: Chinese, French, German, Portuguese, Russian, Swedish, " "Turkish" msgstr "" #: i2p2www/blog/2013/09/30/0.9.8-Release.rst:125 msgid "New Romanian translation" msgstr "" #: i2p2www/blog/2013/09/30/0.9.8-Release.rst:127 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:20 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/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: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 "新的 HTTP 服务器隧道中的 POST 节流器" #: 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 "支持 i2ptunnel 客户端中服务器端口的规范" #: i2p2www/blog/2013/12/07/0.9.9-Release.rst:65 msgid "Add support for SSL connections from i2ptunnel to external server" msgstr "添加从 i2ptunnel 至外部服务器的 SSL 连接的支持" #: 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:10 msgid "Update to HSQLDB 2.3.1" msgstr "" #: i2p2www/blog/2014/01/21/Syndie-1.105b-Release.rst:12 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:17 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:22 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:26 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:32 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:44 #: i2p2www/blog/2014/01/22/0.9.10-Release.rst:30 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:57 msgid "GUI Improvements and Fixes" msgstr "" #: i2p2www/blog/2014/01/21/Syndie-1.105b-Release.rst:73 msgid "Syndication" msgstr "" #: i2p2www/blog/2014/01/21/Syndie-1.105b-Release.rst:84 msgid "Database" msgstr "" #: i2p2www/blog/2014/01/21/Syndie-1.105b-Release.rst:105 msgid "New translations" msgstr "" #: i2p2www/blog/2014/01/21/Syndie-1.105b-Release.rst:106 #: i2p2www/blog/2014/01/22/0.9.10-Release.rst:61 #: i2p2www/blog/2014/02/08/0.9.11-Release.rst:57 #: i2p2www/blog/2014/03/31/0.9.12-Release.rst:97 #: 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/09/20/0.9.15-Release.rst:73 #: 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:54 #: 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/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:69 #: i2p2www/blog/2018/08/23/0.9.36-Release.rst:63 #: i2p2www/blog/2018/10/04/0.9.37-Release.rst:46 #: i2p2www/blog/2019/01/22/0.9.38-Release.rst:63 #: i2p2www/blog/2019/03/21/0.9.39-Release.rst:63 #: i2p2www/blog/2019/05/07/0.9.40-Release.rst:66 #: i2p2www/blog/2019/07/02/0.9.41-Release.rst:66 #: i2p2www/blog/2019/08/27/0.9.42-Release.rst:60 #: i2p2www/blog/2019/10/22/0.9.43-Release.rst:57 #: i2p2www/blog/2019/12/01/0.9.44-Release.rst:66 #: i2p2www/blog/2020/02/25/0.9.45-Release.rst:55 #: i2p2www/blog/2020/05/25/0.9.46-Release.rst:78 #: i2p2www/blog/2020/08/24/0.9.47-Release.rst:67 #: i2p2www/blog/2020/11/30/0.9.48-Release.rst:83 #: i2p2www/blog/2021/02/17/0.9.49-Release.rst:87 #: i2p2www/blog/2021/05/17/0.9.50-Release.rst:84 #: i2p2www/blog/2021/08/23/1.5.0-Release.rst:58 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:10 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:12 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:19 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:39 msgid "Use client tunnels for LeaseSet lookups" msgstr "" #: i2p2www/blog/2014/01/22/0.9.10-Release.rst:43 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:44 msgid "Fix setting I2CP host/port in BOB" msgstr "" #: i2p2www/blog/2014/01/22/0.9.10-Release.rst:45 msgid "Fix several character encoding issues in susimail" msgstr "" #: i2p2www/blog/2014/01/22/0.9.10-Release.rst:46 msgid "Fix StandardServerSocket.close()" msgstr "" #: i2p2www/blog/2014/01/22/0.9.10-Release.rst:47 msgid "Fix exception in PrivateKeyFile" msgstr "" #: i2p2www/blog/2014/01/22/0.9.10-Release.rst:48 msgid "Fixes in RouterInfo expiration task" msgstr "" #: i2p2www/blog/2014/01/22/0.9.10-Release.rst:52 msgid "Tweaks to reduce number of peer connections" msgstr "" #: i2p2www/blog/2014/01/22/0.9.10-Release.rst:53 msgid "Several threading fixes to reduce blocking in the timer queues" msgstr "" #: i2p2www/blog/2014/01/22/0.9.10-Release.rst:54 msgid "Disable streaming ping handling for clients" msgstr "" #: i2p2www/blog/2014/01/22/0.9.10-Release.rst:55 msgid "Use i2psnark's Kademlia library for the router netdb also" msgstr "" #: i2p2www/blog/2014/01/22/0.9.10-Release.rst:56 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:57 msgid "More findbugs fixes" msgstr "" #: i2p2www/blog/2014/01/22/0.9.10-Release.rst:58 msgid "Streaming library refactoring" msgstr "" #: i2p2www/blog/2014/01/22/0.9.10-Release.rst:59 msgid "Support country-specific translations" msgstr "" #: i2p2www/blog/2014/01/22/0.9.10-Release.rst:60 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:10 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:12 #, 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:22 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:31 #: i2p2www/blog/2014/03/31/0.9.12-Release.rst:30 #: i2p2www/blog/2014/05/22/0.9.13-Release.rst:18 #: i2p2www/blog/2014/09/20/0.9.15-Release.rst:33 #: i2p2www/blog/2014/11/01/0.9.16-Release.rst:31 #: i2p2www/blog/2014/11/30/0.9.17-Release.rst:38 #: i2p2www/blog/2015/02/22/0.9.18-Release.rst:22 #: i2p2www/blog/2015/04/12/0.9.19-Release.rst:25 #: i2p2www/blog/2015/06/02/0.9.20-Release.rst:30 #: i2p2www/blog/2015/07/31/0.9.21-Release.rst:26 #: i2p2www/blog/2015/09/12/0.9.22-Release.rst:27 #: i2p2www/blog/2015/11/19/0.9.23-Release.rst:68 #: i2p2www/blog/2016/01/27/0.9.24-Release.rst:48 #: i2p2www/blog/2016/03/22/0.9.25-Release.rst:30 #: i2p2www/blog/2016/06/07/0.9.26-Release.rst:49 #: i2p2www/blog/2016/10/17/0.9.27-Release.rst:28 #: i2p2www/blog/2016/12/12/0.9.28-Release.rst:30 #: i2p2www/blog/2017/02/27/0.9.29-Release.rst:27 #: i2p2www/blog/2017/05/03/0.9.30-Release.rst:51 #: i2p2www/blog/2017/08/07/0.9.31-Release.rst:27 #: i2p2www/blog/2017/11/07/0.9.32-Release.rst:24 #: 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:29 #: i2p2www/blog/2018/08/23/0.9.36-Release.rst:27 #: i2p2www/blog/2018/10/04/0.9.37-Release.rst:20 #: i2p2www/blog/2019/01/22/0.9.38-Release.rst:27 #: i2p2www/blog/2019/03/21/0.9.39-Release.rst:28 #: i2p2www/blog/2019/05/07/0.9.40-Release.rst:28 #: i2p2www/blog/2019/07/02/0.9.41-Release.rst:28 #: i2p2www/blog/2019/08/27/0.9.42-Release.rst:24 #: i2p2www/blog/2019/10/22/0.9.43-Release.rst:23 #: i2p2www/blog/2019/12/01/0.9.44-Release.rst:29 #: i2p2www/blog/2020/02/25/0.9.45-Release.rst:22 #: i2p2www/blog/2020/05/25/0.9.46-Release.rst:34 #: i2p2www/blog/2020/08/24/0.9.47-Release.rst:27 #: i2p2www/blog/2020/11/30/0.9.48-Release.rst:27 #: i2p2www/blog/2021/02/17/0.9.49-Release.rst:39 #: i2p2www/blog/2021/05/17/0.9.50-Release.rst:29 #: i2p2www/blog/2021/08/23/1.5.0-Release.rst:28 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 "0.9.22 带有bug修复并且开始 Ed25519 迁移" #: i2p2www/blog/2014/02/08/0.9.11-Release.rst:40 msgid "More leaseset handling improvements" msgstr "" #: i2p2www/blog/2014/02/08/0.9.11-Release.rst:44 msgid "Fix NPE after client shutdown" msgstr "" #: i2p2www/blog/2014/02/08/0.9.11-Release.rst:45 msgid "Fix wrapper log encoding on logs page" msgstr "" #: i2p2www/blog/2014/02/08/0.9.11-Release.rst:46 msgid "Streaming ping and I2Ping fixes" msgstr "" #: i2p2www/blog/2014/02/08/0.9.11-Release.rst:50 msgid "Add support for Orchid plugin" msgstr "" #: i2p2www/blog/2014/02/08/0.9.11-Release.rst:51 msgid "Add HTTPS support to HTTP client proxy" msgstr "" #: i2p2www/blog/2014/02/08/0.9.11-Release.rst:52 msgid "New I2CP support for hostname lookups by external clients" msgstr "" #: i2p2www/blog/2014/02/08/0.9.11-Release.rst:53 msgid "" "Stricter I2CP authorization enforcement of external clients (incompatible " "change)" msgstr "" #: i2p2www/blog/2014/02/08/0.9.11-Release.rst:54 msgid "Increase default inbound exploratory tunnel length variance" msgstr "" #: i2p2www/blog/2014/02/08/0.9.11-Release.rst:55 msgid "Big reduction in memory usage by transports" msgstr "" #: i2p2www/blog/2014/02/08/0.9.11-Release.rst:56 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:9 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:11 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:17 msgid "" "There are several indicators that point to i2pbrowser.net being a malware " "site:" msgstr "" #: i2p2www/blog/2014/02/16/i2pbrowser-malware.rst:21 msgid "The domain was registered on February 10th, 2014." msgstr "" #: i2p2www/blog/2014/02/16/i2pbrowser-malware.rst:22 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:23 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:25 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:35 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/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:26 #: i2p2www/blog/2014/03/31/0.9.12-Release.rst:46 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:37 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:44 msgid "" "For more information about I2P, visit `our web site`__ or follow us `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:11 msgid "0.9.12 adds support for ECDSA and updates to Jetty 8" msgstr "0.9.12 添加 ECDSA 的支持并更新 Jetty 8" #: i2p2www/blog/2014/03/31/0.9.12-Release.rst:13 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:19 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:57 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/31/0.9.12-Release.rst:67 msgid "Encrypt Delivery Status Messages" msgstr "" #: i2p2www/blog/2014/03/31/0.9.12-Release.rst:68 msgid "Add preliminary support for ECDSA-signed Destinations" msgstr "初步添加 ECDSA 签名对目标的支持" #: i2p2www/blog/2014/03/31/0.9.12-Release.rst:69 msgid "Add check for replayed NTCP session requests" msgstr "" #: i2p2www/blog/2014/03/31/0.9.12-Release.rst:70 msgid "Add throttling and blocking checks to streaming ping processing" msgstr "" #: i2p2www/blog/2014/03/31/0.9.12-Release.rst:76 msgid "Fix RouterInfo exchange in NTCP" msgstr "" #: i2p2www/blog/2014/03/31/0.9.12-Release.rst:77 msgid "Extend timeout for Delivery Status Messages" msgstr "" #: i2p2www/blog/2014/03/31/0.9.12-Release.rst:78 msgid "Drop streaming messages from recently closed connections" msgstr "" #: i2p2www/blog/2014/03/31/0.9.12-Release.rst:79 msgid "Fix restarts on Raspberry Pi" msgstr "" #: i2p2www/blog/2014/03/31/0.9.12-Release.rst:80 msgid "Restore profileOrganizer.sameCountryBonus advanced config" msgstr "" #: i2p2www/blog/2014/03/31/0.9.12-Release.rst:81 msgid "Fix for jwebcache and i2phex" msgstr "" #: i2p2www/blog/2014/03/31/0.9.12-Release.rst:87 msgid "Jetty 8.1.14.v20131031; Java 6 now required" msgstr "" #: i2p2www/blog/2014/03/31/0.9.12-Release.rst:88 msgid "" "Reduce target connection count again to reduce tunnel reject rate further" msgstr "" #: i2p2www/blog/2014/03/31/0.9.12-Release.rst:89 msgid "Add rate limit for outbound connections at tunnel endpoints" msgstr "" #: i2p2www/blog/2014/03/31/0.9.12-Release.rst:90 msgid "Add optional inproxy blocking in i2ptunnel" msgstr "" #: i2p2www/blog/2014/03/31/0.9.12-Release.rst:91 msgid "Use SSU session key for relay request/response when available" msgstr "" #: i2p2www/blog/2014/03/31/0.9.12-Release.rst:92 msgid "Include HTTP POST data in SYN packet" msgstr "" #: i2p2www/blog/2014/03/31/0.9.12-Release.rst:93 msgid "Add getopt library for better argument processing" msgstr "" #: i2p2www/blog/2014/03/31/0.9.12-Release.rst:94 msgid "More removal of Jetty dependencies" msgstr "" #: i2p2www/blog/2014/03/31/0.9.12-Release.rst:95 msgid "Remove MD5 code, use Java libraries instead" msgstr "" #: i2p2www/blog/2014/03/31/0.9.12-Release.rst:96 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:11 msgid "0.9.13 with SusiMail improvements and fixes for firewalled routers" msgstr "" #: i2p2www/blog/2014/05/22/0.9.13-Release.rst:13 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:23 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:32 msgid "SusiMail" msgstr "SusiMail" #: i2p2www/blog/2014/05/22/0.9.13-Release.rst:34 msgid "Many UI improvements" msgstr "" #: i2p2www/blog/2014/05/22/0.9.13-Release.rst:35 msgid "Implement local storage of messages" msgstr "" #: i2p2www/blog/2014/05/22/0.9.13-Release.rst:36 msgid "Add offline mode" msgstr "" #: i2p2www/blog/2014/05/22/0.9.13-Release.rst:37 msgid "Messages now deleted on server after download" msgstr "" #: i2p2www/blog/2014/05/22/0.9.13-Release.rst:38 msgid "Several backend POP3 and SMTP speedups and fixes" msgstr "" #: i2p2www/blog/2014/05/22/0.9.13-Release.rst:42 msgid "NetDB lookup fixes" msgstr "" #: i2p2www/blog/2014/05/22/0.9.13-Release.rst:43 msgid "Fix transition from not-firewalled to firewalled" msgstr "" #: i2p2www/blog/2014/05/22/0.9.13-Release.rst:44 msgid "Fix plugin uninstall on Windows" msgstr "" #: i2p2www/blog/2014/05/22/0.9.13-Release.rst:45 msgid "SSU locking fixes" msgstr "" #: i2p2www/blog/2014/05/22/0.9.13-Release.rst:46 msgid "Fix rapid republishing of SSU addresses" msgstr "" #: i2p2www/blog/2014/05/22/0.9.13-Release.rst:47 msgid "IRC client exception fixes" msgstr "" #: i2p2www/blog/2014/05/22/0.9.13-Release.rst:48 msgid "Fix changing HTTP outproxy configuration without restarting tunnel" msgstr "" #: i2p2www/blog/2014/05/22/0.9.13-Release.rst:52 msgid "New i2ptunnel server option for unique local address per-client" msgstr "" #: i2p2www/blog/2014/05/22/0.9.13-Release.rst:53 msgid "Warn in i2ptunnel on duplicate client ports" msgstr "" #: i2p2www/blog/2014/05/22/0.9.13-Release.rst:54 msgid "Update HTTP User-Agent to match TBB" msgstr "" #: i2p2www/blog/2014/05/22/0.9.13-Release.rst:55 msgid "Extend SSU establishment retransmission timer" msgstr "" #: i2p2www/blog/2014/05/22/0.9.13-Release.rst:56 msgid "Use constant-time method for HMAC verification" msgstr "" #: i2p2www/blog/2014/05/22/0.9.13-Release.rst:57 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:11 msgid "0.9.14 includes critical security fixes" msgstr "" #: i2p2www/blog/2014/07/26/0.9.14-Release.rst:13 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:20 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:25 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:32 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:40 msgid "Security Fixes" msgstr "" #: i2p2www/blog/2014/07/26/0.9.14-Release.rst:42 msgid "Fix several XSS issues" msgstr "" #: i2p2www/blog/2014/07/26/0.9.14-Release.rst:43 msgid "Disable changing news feed URL from UI" msgstr "" #: i2p2www/blog/2014/07/26/0.9.14-Release.rst:44 msgid "Disable plugin install" msgstr "" #: i2p2www/blog/2014/07/26/0.9.14-Release.rst:45 msgid "Disable setting unsigned update URL from UI" msgstr "" #: i2p2www/blog/2014/07/26/0.9.14-Release.rst:46 msgid "Disable clients.config editing from the UI" msgstr "" #: i2p2www/blog/2014/07/26/0.9.14-Release.rst:47 msgid "Add Content-Security-Policy and X-XSS-Protection headers" msgstr "" #: i2p2www/blog/2014/07/26/0.9.14-Release.rst:48 msgid "Disable unused ExecNamingService (thx joernchen of Phenoelit)" msgstr "" #: i2p2www/blog/2014/07/26/0.9.14-Release.rst:53 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:54 msgid "Reject participating tunnels when hidden" msgstr "" #: i2p2www/blog/2014/07/26/0.9.14-Release.rst:55 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:60 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:61 msgid "Use JVM's AES implementation if it is faster" msgstr "" #: i2p2www/blog/2014/07/26/0.9.14-Release.rst:62 msgid "More advanced options shown in the i2ptunnel edit pages" msgstr "" #: i2p2www/blog/2014/07/26/0.9.14-Release.rst:63 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:64 msgid "Lots of findbugs fixes and cleanups" msgstr "" #: i2p2www/blog/2014/07/26/0.9.14-Release.rst:65 msgid "Support signature types in SAM, bump rev to 3.1" msgstr "" #: i2p2www/blog/2014/07/26/0.9.14-Release.rst:66 msgid "New event log page in console" msgstr "" #: i2p2www/blog/2014/07/26/0.9.14-Release.rst:69 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:11 msgid "0.9.14.1 includes i2psnark and console fixes" msgstr "" #: i2p2www/blog/2014/08/09/0.9.14.1-Release.rst:13 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:20 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:26 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:38 msgid "Fix i2psnark add torrent form" msgstr "" #: i2p2www/blog/2014/08/09/0.9.14.1-Release.rst:39 msgid "Fix iptunnel custom options form" msgstr "" #: i2p2www/blog/2014/08/09/0.9.14.1-Release.rst:40 msgid "Fix update download buttons" msgstr "" #: i2p2www/blog/2014/08/09/0.9.14.1-Release.rst:45 msgid "Restore all console features if routerconsole.advanced=true" msgstr "" #: i2p2www/blog/2014/08/09/0.9.14.1-Release.rst:46 msgid "Restore plugin install if routerconsole.enablePluginInstall=true" msgstr "" #: i2p2www/blog/2014/08/09/0.9.14.1-Release.rst:47 msgid "Restpre client adds/changes if routerconsole.enableClientChange=true" msgstr "" #: i2p2www/blog/2014/08/09/0.9.14.1-Release.rst:48 msgid "" "Plugin signing keys are now whitelisted unless " "routerconsole.allowUntrustedPlugins=true" msgstr "" #: i2p2www/blog/2014/08/09/0.9.14.1-Release.rst:49 #: i2p2www/blog/2014/09/20/0.9.15-Release.rst:72 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:11 msgid "Organization launch" msgstr "" #: i2p2www/blog/2014/08/15/The-privacy-solutions-project.rst:13 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:35 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:39 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:46 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:11 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:13 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:22 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:31 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:41 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:50 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:57 msgid "Website release details" msgstr "" #: i2p2www/blog/2014/08/23/Android-test-release-on-Google-Play-in-Norway.rst:59 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:65 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:71 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:11 msgid "0.9.15 includes Ed25519 crypto and many fixes" msgstr "" #: i2p2www/blog/2014/09/20/0.9.15-Release.rst:13 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:21 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:42 #: i2p2www/blog/2014/11/01/0.9.16-Release.rst:40 #: i2p2www/blog/2014/11/30/0.9.17-Release.rst:47 #: i2p2www/blog/2015/04/12/0.9.19-Release.rst:33 #: i2p2www/blog/2015/06/02/0.9.20-Release.rst:47 #: i2p2www/blog/2015/07/31/0.9.21-Release.rst:39 #: i2p2www/blog/2015/09/12/0.9.22-Release.rst:38 #: i2p2www/blog/2015/11/19/0.9.23-Release.rst:76 #: i2p2www/blog/2016/01/27/0.9.24-Release.rst:56 #: i2p2www/blog/2016/03/22/0.9.25-Release.rst:38 #: i2p2www/blog/2016/06/07/0.9.26-Release.rst:57 #: i2p2www/blog/2016/10/17/0.9.27-Release.rst:36 #: i2p2www/blog/2016/12/12/0.9.28-Release.rst:38 #: i2p2www/blog/2017/02/27/0.9.29-Release.rst:35 #: i2p2www/blog/2017/05/03/0.9.30-Release.rst:59 #: i2p2www/blog/2017/08/07/0.9.31-Release.rst:35 #: i2p2www/blog/2017/11/07/0.9.32-Release.rst:32 #: 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:37 #: i2p2www/blog/2018/08/23/0.9.36-Release.rst:35 #: i2p2www/blog/2018/10/04/0.9.37-Release.rst:28 #: i2p2www/blog/2019/01/22/0.9.38-Release.rst:35 #: i2p2www/blog/2019/03/21/0.9.39-Release.rst:36 #: i2p2www/blog/2019/05/07/0.9.40-Release.rst:36 #: i2p2www/blog/2019/07/02/0.9.41-Release.rst:36 #: i2p2www/blog/2019/08/27/0.9.42-Release.rst:32 #: i2p2www/blog/2019/10/22/0.9.43-Release.rst:31 #: i2p2www/blog/2019/12/01/0.9.44-Release.rst:37 #: i2p2www/blog/2020/02/25/0.9.45-Release.rst:30 #: i2p2www/blog/2020/05/25/0.9.46-Release.rst:42 #: i2p2www/blog/2020/08/24/0.9.47-Release.rst:35 #: i2p2www/blog/2020/11/30/0.9.48-Release.rst:35 #: i2p2www/blog/2021/02/17/0.9.49-Release.rst:47 #: i2p2www/blog/2021/05/17/0.9.50-Release.rst:37 #: i2p2www/blog/2021/08/23/1.5.0-Release.rst:36 msgid "Changes" msgstr "" #: i2p2www/blog/2014/09/20/0.9.15-Release.rst:44 msgid "Add support for Ed25519 signatures" msgstr "" #: i2p2www/blog/2014/09/20/0.9.15-Release.rst:45 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:46 msgid "Add i2psnark support for data outside the i2psnark/ directory" msgstr "" #: i2p2www/blog/2014/09/20/0.9.15-Release.rst:47 msgid "Enable stronger signatures (su3 format) for plugins" msgstr "" #: i2p2www/blog/2014/09/20/0.9.15-Release.rst:48 msgid "Speed up SSU introductions by responding to hole punch messages" msgstr "" #: i2p2www/blog/2014/09/20/0.9.15-Release.rst:49 msgid "Several improvements in SAM efficiency" msgstr "" #: i2p2www/blog/2014/09/20/0.9.15-Release.rst:54 msgid "Form submission fixes in the console and i2psnark" msgstr "" #: i2p2www/blog/2014/09/20/0.9.15-Release.rst:55 msgid "Streaming fixes for long signatures" msgstr "" #: i2p2www/blog/2014/09/20/0.9.15-Release.rst:56 msgid "i2psnark fixes for file name character mapping when seeding" msgstr "" #: i2p2www/blog/2014/09/20/0.9.15-Release.rst:57 msgid "I2PTunnel fixes stopping client tunnels" msgstr "" #: i2p2www/blog/2014/09/20/0.9.15-Release.rst:58 msgid "I2PTunnel fix updating options on a running delay-open client tunnel" msgstr "" #: i2p2www/blog/2014/09/20/0.9.15-Release.rst:63 msgid "Re-enable plugin installation via the console, removed in 0.9.14" msgstr "" #: i2p2www/blog/2014/09/20/0.9.15-Release.rst:64 msgid "i2psnark now remembers uploaded count across restarts" msgstr "" #: i2p2www/blog/2014/09/20/0.9.15-Release.rst:65 msgid "i2psnark increase max piece size to 8 MB" msgstr "" #: i2p2www/blog/2014/09/20/0.9.15-Release.rst:66 msgid "i2psnark several UI fixes" msgstr "" #: i2p2www/blog/2014/09/20/0.9.15-Release.rst:67 msgid "Prohibit SSU peer test requests unless a connection is established" msgstr "" #: i2p2www/blog/2014/09/20/0.9.15-Release.rst:68 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:69 msgid "Console and log warnings for unavailable crypto" msgstr "" #: i2p2www/blog/2014/09/20/0.9.15-Release.rst:70 msgid "" "More consistent routing for Delivery Status Messages to reduce network " "connections" msgstr "" #: i2p2www/blog/2014/09/20/0.9.15-Release.rst:71 msgid "Disable external entities in UPnP XML parser" msgstr "" #: i2p2www/blog/2014/09/20/0.9.15-Release.rst:74 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:11 msgid "0.9.16 includes crypto migration and many fixes" msgstr "" #: i2p2www/blog/2014/11/01/0.9.16-Release.rst:13 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:21 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:25 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:42 msgid "Add support for stronger Router Info signatures" msgstr "" #: i2p2www/blog/2014/11/01/0.9.16-Release.rst:43 msgid "Encrypt RI lookups and responses on faster boxes" msgstr "" #: i2p2www/blog/2014/11/01/0.9.16-Release.rst:44 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:45 msgid "Disable SSLv3 and older ciphers for reseeding and other uses of SSL" msgstr "" #: i2p2www/blog/2014/11/01/0.9.16-Release.rst:46 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:47 msgid "Don't prefer floodfills in some countries" msgstr "默认不在一些国家播种" #: i2p2www/blog/2014/11/01/0.9.16-Release.rst:48 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:49 msgid "Increase i2psnark tunnel default to 3 hops" msgstr "" #: i2p2www/blog/2014/11/01/0.9.16-Release.rst:50 msgid "" "Implement bundling of multiple fragments in a single SSU message for " "efficiency" msgstr "" #: i2p2www/blog/2014/11/01/0.9.16-Release.rst:51 msgid "New add-to-addressbook links on netdb leaseset page" msgstr "" #: i2p2www/blog/2014/11/01/0.9.16-Release.rst:52 msgid "" "Implement I2NP DatabaseLookupMessage search type field to improve lookup " "efficiency" msgstr "" #: i2p2www/blog/2014/11/01/0.9.16-Release.rst:59 msgid "CPUID fixes and updates for recent processors" msgstr "" #: i2p2www/blog/2014/11/01/0.9.16-Release.rst:60 #, python-format msgid "i2psnark fix magnet links with %(pc)s-encoding" msgstr "" #: i2p2www/blog/2014/11/01/0.9.16-Release.rst:61 #, 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:62 msgid "SSU bitfield handling fixes" msgstr "" #: i2p2www/blog/2014/11/01/0.9.16-Release.rst:63 msgid "Fix HTTP header issues in i2psnark" msgstr "" #: i2p2www/blog/2014/11/01/0.9.16-Release.rst:64 msgid "Fix rare NPE when building garlic message" msgstr "" #: i2p2www/blog/2014/11/01/0.9.16-Release.rst:65 msgid "Fix console lockups (hopefully)" msgstr "" #: i2p2www/blog/2014/11/01/0.9.16-Release.rst:66 msgid "Fix i2ptunnel js confirm-delete" msgstr "" #: i2p2www/blog/2014/11/01/0.9.16-Release.rst:71 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:72 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:73 msgid "Improve handling of unsupported encryption throughout" msgstr "" #: i2p2www/blog/2014/11/01/0.9.16-Release.rst:74 msgid "More error checking of client I2CP messages by the router" msgstr "" #: i2p2www/blog/2014/11/01/0.9.16-Release.rst:75 msgid "Initial work on hooks for pluggable transports" msgstr "" #: i2p2www/blog/2014/11/01/0.9.16-Release.rst:76 msgid "Enforce request timestamp in tunnel build messages" msgstr "" #: i2p2www/blog/2014/11/01/0.9.16-Release.rst:77 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:78 msgid "Return unused DH keypairs to the pool for efficiency" msgstr "" #: i2p2www/blog/2014/11/01/0.9.16-Release.rst:79 msgid "Raise failsafe tagset limit and improve deletion strategy when hit" msgstr "" #: i2p2www/blog/2014/11/01/0.9.16-Release.rst:80 msgid "" "Change eepsite Jetty threadpool and queue configuration (new installs only)" msgstr "" #: i2p2www/blog/2014/11/01/0.9.16-Release.rst:81 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:11 msgid "0.9.17 with more crypto migration and many fixes" msgstr "" #: i2p2www/blog/2014/11/30/0.9.17-Release.rst:13 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:17 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:22 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:28 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:34 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:49 msgid "Signed news" msgstr "" #: i2p2www/blog/2014/11/30/0.9.17-Release.rst:50 msgid "ECDSA default for new server tunnels" msgstr "" #: i2p2www/blog/2014/11/30/0.9.17-Release.rst:51 msgid "Reseeding now SSL-only by default" msgstr "" #: i2p2www/blog/2014/11/30/0.9.17-Release.rst:56 msgid "Fix SSU sending corrupt ack-only packets with partial bitfields" msgstr "" #: i2p2www/blog/2014/11/30/0.9.17-Release.rst:57 msgid "Fix SSU inbound connection fail from non-DSA router" msgstr "" #: i2p2www/blog/2014/11/30/0.9.17-Release.rst:58 msgid "Don't select incompatible peers if we are a non-DSA router" msgstr "" #: i2p2www/blog/2014/11/30/0.9.17-Release.rst:59 msgid "Fix EdDSA signature verification bug" msgstr "" #: i2p2www/blog/2014/11/30/0.9.17-Release.rst:60 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:61 msgid "Stop i2ptunnel server acceptor thread after close" msgstr "" #: i2p2www/blog/2014/11/30/0.9.17-Release.rst:62 msgid "Fix bug preventing some plugins from stopping completely" msgstr "" #: i2p2www/blog/2014/11/30/0.9.17-Release.rst:63 msgid "Fix SAM v3 bug causing failures in incoming connections" msgstr "" #: i2p2www/blog/2014/11/30/0.9.17-Release.rst:68 msgid "Add a warning in the console sidebar if ECDSA not supported" msgstr "" #: i2p2www/blog/2014/11/30/0.9.17-Release.rst:69 msgid "Log warnings for Java 6 that we will eventually require Java 7" msgstr "" #: i2p2www/blog/2014/11/30/0.9.17-Release.rst:70 msgid "Don't let proxied routers auto-floodfill" msgstr "不要让经过代理的路由器自动播种" #: i2p2www/blog/2014/11/30/0.9.17-Release.rst:71 msgid "Don't resend SSU acks that are too old" msgstr "" #: i2p2www/blog/2014/11/30/0.9.17-Release.rst:72 msgid "Don't publish direct info in SSU address if introducers are required" msgstr "" #: i2p2www/blog/2014/11/30/0.9.17-Release.rst:73 msgid "New default opentrackers in i2psnark" msgstr "" #: i2p2www/blog/2014/11/30/0.9.17-Release.rst:74 msgid "Add support for specifiying data directory per-torrent in i2psnark" msgstr "" #: i2p2www/blog/2014/11/30/0.9.17-Release.rst:75 msgid "Changes in streaming accept() error behavior" msgstr "" #: i2p2www/blog/2014/11/30/0.9.17-Release.rst:76 msgid "Minor blockfile format changes" msgstr "" #: i2p2www/blog/2014/11/30/0.9.17-Release.rst:77 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:11 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:13 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:19 msgid "" "New app versions\n" "----------------" msgstr "" #: i2p2www/blog/2014/12/01/Android-app-releases.rst:24 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:35 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:44 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:59 msgid "The fingerprint (SHA-256) of the new signing key is:" msgstr "" #: i2p2www/blog/2014/12/01/Android-app-releases.rst:68 msgid "" "Google Play\n" "-----------" msgstr "" #: i2p2www/blog/2014/12/01/Android-app-releases.rst:73 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:89 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:98 msgid "" "F-Droid\n" "-------" msgstr "" #: i2p2www/blog/2014/12/01/Android-app-releases.rst:103 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:115 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:124 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/2015/01/20/31C3-trip-report.rst:1 msgid "" "================\n" "31C3 trip report\n" "================" msgstr "" #: i2p2www/blog/2015/01/20/31C3-trip-report.rst:10 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:21 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:30 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:41 msgid "" "Discussions with others\n" "=======================" msgstr "" #: i2p2www/blog/2015/01/20/31C3-trip-report.rst:49 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:60 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:69 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:80 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:92 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:103 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:115 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:127 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:140 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:155 msgid "" "New users\n" "---------" msgstr "" #: i2p2www/blog/2015/01/20/31C3-trip-report.rst:160 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:173 msgid "" "I2P project topics\n" "------------------" msgstr "" #: i2p2www/blog/2015/01/20/31C3-trip-report.rst:178 msgid "" "* *Spending money:* We discussed several ways to effectively use our " "resources in 2015, including more hardware for testing and development. " "Also, we plan to increase reimbursement levels for conference attendees." msgstr "" #: i2p2www/blog/2015/01/20/31C3-trip-report.rst:182 msgid "" "* *Toronto meetup:* CCC is such a productive time for us, and it seems that " "a second meetup in the year would be quite helpful. We have proposed it for " "August 2015 in Toronto, Canada, in conjunction with `Toronto Crypto`__. It " "would include developer meetings together with presentations and tutorials, " "all open to the public. We are attempting to gauge interest and research " "possible venues. If you are considering attending, please let us know by " "`tweeting @i2p`__ or posting `on the dev forum thread`__." msgstr "" #: i2p2www/blog/2015/01/20/31C3-trip-report.rst:190 msgid "" "* We discussed Meeh's workload and the state of the various services he is " "running. We made some plans to reduce his load and have some other people " "help out." msgstr "" #: i2p2www/blog/2015/01/20/31C3-trip-report.rst:194 msgid "" "* We reviewed our critieria for placing links to `i2pd`__ on our download " "page. We agreed that the only remaining item is to have a nice page on the " "`Privacy Solutions web site`__ or elsewhere with binary packages for " "Windows, Linux, and Mac, and source packages. It's not clear who is " "responsible for building the packages and where the \"official\" version is." " Once there's an established process for building and signing packages and " "an official place to put them, we're ready to link to it. If it is not " "feasible to host it on the Privacy Solutions website, we will discuss " "alternatives with orignal, including possible migration to our download " "servers." msgstr "" #: i2p2www/blog/2015/01/20/31C3-trip-report.rst:201 msgid "" "* Lots of people coming by the table asked if we had a non-Java version. It " "was great to finally answer \"yes\" and we're eager to get the word out and " "get more users, testers, and developers on it." msgstr "" #: i2p2www/blog/2015/01/20/31C3-trip-report.rst:205 msgid "" "* `Vuze`__ continues to make good progress on their I2P integration. We look" " forward to working with them in the new year on a managed rollout to more " "users." msgstr "" #: i2p2www/blog/2015/01/20/31C3-trip-report.rst:211 msgid "" "* We discussed the state of Meeh's and Sindu's reseed servers. They made " "several improvements while at the congress and are investigating migration " "to `Matt Drollette's Go implementation`__. The security and reliability of " "our reseed servers is vital to new users and network operation. `User " "'backup'`__ is doing a great job monitoring and managing the pool of reseed " "servers." msgstr "" #: i2p2www/blog/2015/01/20/31C3-trip-report.rst:218 msgid "" "* We agreed to purchase a second root server for development, testing, and " "services. Echelon will be adminstering it. Contact him if you would like a " "VM." msgstr "" #: i2p2www/blog/2015/01/20/31C3-trip-report.rst:222 msgid "" "* We reiterated that we have funds available to purchase test hardware, " "especially for Windows and Mac. Talk to echelon for details." msgstr "" #: i2p2www/blog/2015/01/20/31C3-trip-report.rst:226 msgid "" "* We met with Welterde about the state of his services including his `open " "tracker`__. These services are not being adequately maintained and will soon" " become inaccessible due to crypto changes if they are not upgraded. He " "committed to upgrading them soon." msgstr "" #: i2p2www/blog/2015/01/20/31C3-trip-report.rst:232 msgid "" "* We met lots of people interested in our `Android app`__. We passed several" " ideas and bug reports back to str4d. We plan to make a big push to give the" " app some development love early in the year." msgstr "" #: i2p2www/blog/2015/01/20/31C3-trip-report.rst:238 msgid "" "* Regrettably, we didn't get to see too many talks at the Congress, as we " "were so busy meeting with people. We plan to catch up and `watch them " "online`__. As usual, Tor's \"State of the Onion\" talk was excellent, and " "Jacob's talk was great. We hear that the cryptography talks were good as " "well." 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:11 msgid "0.9.18 with performance improvements and bug fixes" msgstr "" #: i2p2www/blog/2015/02/22/0.9.18-Release.rst:13 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:33 msgid "Fix parsing of ECDSA address helper in HTTP client proxy" msgstr "" #: i2p2www/blog/2015/02/22/0.9.18-Release.rst:34 msgid "" "Fix news last-modified processing which prevented notification of update" msgstr "" #: i2p2www/blog/2015/02/22/0.9.18-Release.rst:35 msgid "Improve handling of UPnP device changes" msgstr "" #: i2p2www/blog/2015/02/22/0.9.18-Release.rst:36 msgid "Don't hang at startup forever waiting for entropy" msgstr "" #: i2p2www/blog/2015/02/22/0.9.18-Release.rst:37 msgid "Possible fixes for high CPU usage in NTCP" msgstr "" #: i2p2www/blog/2015/02/22/0.9.18-Release.rst:41 msgid "Publish router info faster when address costs change" msgstr "" #: i2p2www/blog/2015/02/22/0.9.18-Release.rst:42 msgid "Start i2ptunnel 90s sooner" msgstr "" #: i2p2www/blog/2015/02/22/0.9.18-Release.rst:43 msgid "Accept tunnels 10m sooner" msgstr "" #: i2p2www/blog/2015/02/22/0.9.18-Release.rst:44 msgid "Increase exploratory tunnel quantity during initial exploration" msgstr "" #: i2p2www/blog/2015/02/22/0.9.18-Release.rst:45 msgid "Latency reductions in several places" msgstr "" #: i2p2www/blog/2015/02/22/0.9.18-Release.rst:46 msgid "" "Add startup browser configuration with advanced config routerconsole.browser" msgstr "" #: i2p2www/blog/2015/02/22/0.9.18-Release.rst:47 msgid "Persistent leaseset keys to eliminate correlation with restart" msgstr "" #: i2p2www/blog/2015/02/22/0.9.18-Release.rst:48 msgid "Faster unchoking of new peers in i2psnark" msgstr "" #: i2p2www/blog/2015/02/22/0.9.18-Release.rst:49 msgid "More aggressive throttling of lookups at floodfills" msgstr "更具侵略性的种子查询节流阀" #: i2p2www/blog/2015/02/22/0.9.18-Release.rst:50 msgid "Tunnel build request record refactoring" msgstr "" #: i2p2www/blog/2015/02/22/0.9.18-Release.rst:51 msgid "Reduce thread usage in i2ptunnel" msgstr "" #: i2p2www/blog/2015/02/22/0.9.18-Release.rst:52 msgid "Add i2ptunnel server option for multihomed sites" msgstr "" #: i2p2www/blog/2015/02/22/0.9.18-Release.rst:53 msgid "Disallow some common I2P application ports as router ports" msgstr "" #: i2p2www/blog/2015/02/22/0.9.18-Release.rst:54 msgid "Increase connection limits for fast routers" msgstr "" #: i2p2www/blog/2015/02/22/0.9.18-Release.rst:55 msgid "Add Save-As button for SusiMail messages" msgstr "" #: i2p2www/blog/2015/02/22/0.9.18-Release.rst:56 msgid "Use 'hidden service' terminology in the console" msgstr "" #: i2p2www/blog/2015/02/22/0.9.18-Release.rst:57 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:11 msgid "0.9.19 with performance improvements and bug fixes" msgstr "" #: i2p2www/blog/2015/04/12/0.9.19-Release.rst:13 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:21 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:35 #: i2p2www/blog/2015/06/02/0.9.20-Release.rst:49 msgid "Floodfill performance improvements" msgstr "" #: i2p2www/blog/2015/04/12/0.9.19-Release.rst:36 msgid "Easier ways to reseed manually from a file or URL" msgstr "" #: i2p2www/blog/2015/04/12/0.9.19-Release.rst:37 msgid "New way to export reseed data for others" msgstr "" #: i2p2www/blog/2015/04/12/0.9.19-Release.rst:38 msgid "Support for installing plugin from file" msgstr "" #: i2p2www/blog/2015/04/12/0.9.19-Release.rst:43 #: i2p2www/blog/2015/06/02/0.9.20-Release.rst:60 msgid "Fixes for high CPU usage in floodfills" msgstr "" #: i2p2www/blog/2015/04/12/0.9.19-Release.rst:44 msgid "i2ptunnel locking fixes" msgstr "" #: i2p2www/blog/2015/04/12/0.9.19-Release.rst:45 msgid "Fixes for read timeout handling in streaming" msgstr "" #: i2p2www/blog/2015/04/12/0.9.19-Release.rst:46 msgid "Fix changing i2psnark data directory on Windows" msgstr "" #: i2p2www/blog/2015/04/12/0.9.19-Release.rst:47 msgid "Fix multiple SSL outproxies in HTTP client" msgstr "" #: i2p2www/blog/2015/04/12/0.9.19-Release.rst:52 msgid "Update to UPnP library version 3.0" msgstr "" #: i2p2www/blog/2015/04/12/0.9.19-Release.rst:53 msgid "Improve tracking of floodfill lookup success" msgstr "" #: i2p2www/blog/2015/04/12/0.9.19-Release.rst:54 msgid "Direct router info lookups if connected to floodfill" msgstr "" #: i2p2www/blog/2015/04/12/0.9.19-Release.rst:55 msgid "Auto-adjustment of i2psnark tunnel quantity" msgstr "" #: i2p2www/blog/2015/04/12/0.9.19-Release.rst:56 msgid "Increase exploratory tunnel quantity when floodfill" msgstr "" #: i2p2www/blog/2015/04/12/0.9.19-Release.rst:57 msgid "Increase min and default bandwidth for i2psnark" msgstr "" #: i2p2www/blog/2015/04/12/0.9.19-Release.rst:58 msgid "" "Improved strategies for dropping jobs on high job lag to prevent overload" msgstr "" #: i2p2www/blog/2015/04/12/0.9.19-Release.rst:59 msgid "Drop tunnel build requests on high job lag" msgstr "" #: i2p2www/blog/2015/04/12/0.9.19-Release.rst:60 msgid "Increase allowed clock skew in I2CP" msgstr "" #: i2p2www/blog/2015/04/12/0.9.19-Release.rst:61 msgid "New HTTP error page when the server resets the connection" msgstr "" #: i2p2www/blog/2015/04/12/0.9.19-Release.rst:62 msgid "Require ECDSA support for floodfill" msgstr "" #: i2p2www/blog/2015/04/12/0.9.19-Release.rst:63 msgid "Republish router info faster when capabilities change" msgstr "" #: i2p2www/blog/2015/04/12/0.9.19-Release.rst:64 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:11 msgid "0.9.20 with performance improvements and bug fixes" msgstr "" #: i2p2www/blog/2015/06/02/0.9.20-Release.rst:13 msgid "" "0.9.20 contains many important bug fixes, and several changes to increase " "floodfill capacity in the network." msgstr "0.9.20 包含很多重要的缺陷修复，并且增加了网络中的播种（floodfill）容量。" #: i2p2www/blog/2015/06/02/0.9.20-Release.rst:17 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:25 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:35 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:50 msgid "Add support for address book export" msgstr "" #: i2p2www/blog/2015/06/02/0.9.20-Release.rst:51 msgid "Add support for SSL in HTTP server tunnel" msgstr "" #: i2p2www/blog/2015/06/02/0.9.20-Release.rst:52 msgid "Allow class 'M' (64-128 KBps share bandwidth) to become floodfill" msgstr "" #: i2p2www/blog/2015/06/02/0.9.20-Release.rst:53 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:54 msgid "Add support for signed development builds" msgstr "" #: i2p2www/blog/2015/06/02/0.9.20-Release.rst:61 msgid "Clock skew fixes" msgstr "" #: i2p2www/blog/2015/06/02/0.9.20-Release.rst:62 msgid "" "Fixes and configuration for when IPv4 is firewalled but IPv6 still works" msgstr "" #: i2p2www/blog/2015/06/02/0.9.20-Release.rst:63 msgid "Locking fixes for i2ptunnel clients to prevent hangs at startup" msgstr "" #: i2p2www/blog/2015/06/02/0.9.20-Release.rst:64 msgid "Verify hostnames when reseeding" msgstr "" #: i2p2www/blog/2015/06/02/0.9.20-Release.rst:65 msgid "Fix deletion of config files for deleted torrents in i2psnark" msgstr "" #: i2p2www/blog/2015/06/02/0.9.20-Release.rst:66 msgid "Fix hangs fetching proxy.i2p local resources via Privoxy" msgstr "" #: i2p2www/blog/2015/06/02/0.9.20-Release.rst:67 msgid "Fixes for duplicate shared clients" msgstr "" #: i2p2www/blog/2015/06/02/0.9.20-Release.rst:68 msgid "Fix for occasional page truncation in HTTP client" msgstr "" #: i2p2www/blog/2015/06/02/0.9.20-Release.rst:69 msgid "Fixes for handling corrupted SSU packets" msgstr "" #: i2p2www/blog/2015/06/02/0.9.20-Release.rst:70 msgid "Fix closing of SAM sessions when I2P session closes" msgstr "" #: i2p2www/blog/2015/06/02/0.9.20-Release.rst:71 msgid "Fix bugs in handling streaming resets" msgstr "" #: i2p2www/blog/2015/06/02/0.9.20-Release.rst:78 msgid "Reduce NTCP threads" msgstr "" #: i2p2www/blog/2015/06/02/0.9.20-Release.rst:79 msgid "Eliminate SimpleScheduler threads" msgstr "" #: i2p2www/blog/2015/06/02/0.9.20-Release.rst:80 msgid "Add continent-based NTP servers as fallbacks for country-based ones" msgstr "" #: i2p2www/blog/2015/06/02/0.9.20-Release.rst:81 msgid "Remove all default non-SSL reseed hosts" msgstr "" #: i2p2www/blog/2015/06/02/0.9.20-Release.rst:82 msgid "Disable fallback to non-su3 reseeding" msgstr "" #: i2p2www/blog/2015/06/02/0.9.20-Release.rst:83 msgid "Several fixes in streaming for better \"loopback\" performance" msgstr "" #: i2p2www/blog/2015/06/02/0.9.20-Release.rst:84 msgid "Reduce latency in i2ptunnel" msgstr "" #: i2p2www/blog/2015/06/02/0.9.20-Release.rst:85 msgid "Add a larger Bloom filter for very high bandwidth and memory" msgstr "" #: i2p2www/blog/2015/06/02/0.9.20-Release.rst:86 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:87 msgid "Reduce max netdb search depth to reduce floodfill load" msgstr "" #: i2p2www/blog/2015/06/02/0.9.20-Release.rst:88 msgid "Improved header processing and error handling in i2ptunnel HTTP server" msgstr "" #: i2p2www/blog/2015/06/02/0.9.20-Release.rst:89 msgid "" "Better error handling and user feedback when HTTP client tunnel is disabled" msgstr "" #: i2p2www/blog/2015/06/02/0.9.20-Release.rst:90 msgid "More changes to improve floodfill capacity" msgstr "" #: i2p2www/blog/2015/06/02/0.9.20-Release.rst:91 msgid "New configuration for forcing IPv4 (only) to firewalled on /confignet" msgstr "" #: i2p2www/blog/2015/06/02/0.9.20-Release.rst:92 msgid "New configuration for floodfill on /configadvanced" msgstr "" #: i2p2www/blog/2015/06/02/0.9.20-Release.rst:93 msgid "Show separate IPv4 and IPv6 status in summary bar when appropriate" msgstr "" #: i2p2www/blog/2015/06/02/0.9.20-Release.rst:94 msgid "Better handling of corrupt SSU packets" msgstr "" #: i2p2www/blog/2015/06/02/Toronto-Meetup.rst:2 msgid "Toronto Meetup" msgstr "" #: i2p2www/blog/2015/06/02/Toronto-Meetup.rst:11 msgid "I2P Meetup in Toronto on August 15-16" msgstr "" #: i2p2www/blog/2015/06/02/Toronto-Meetup.rst:13 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:18 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:24 msgid "" "The meetup couldn't have been arranged without our friends at `Toronto " "Crypto `_ which have been helping us organize " "the event, and our friends at `Hacklab `_ which are " "providing us with a very nice space." msgstr "" #: i2p2www/blog/2015/06/02/Toronto-Meetup.rst:28 #: i2p2www/blog/2015/07/16/I2PCon.rst:127 msgid "If you have any questions, feel free to contact us on `@geti2p`_." msgstr "" #: i2p2www/blog/2015/06/02/Toronto-Meetup.rst:35 #: i2p2www/blog/2015/07/16/I2PCon.rst:39 msgid "Details" msgstr "详细信息" #: i2p2www/blog/2015/06/02/Toronto-Meetup.rst:41 #: i2p2www/blog/2015/07/16/I2PCon.rst:58 msgid "Location" msgstr "位置" #: i2p2www/blog/2015/06/02/Toronto-Meetup.rst:46 msgid "`Hacklab `_ at 1266 Queen Street West, Toronto." msgstr "" #: i2p2www/blog/2015/06/02/Toronto-Meetup.rst:50 msgid "Day 1, August 15 - 3PM" msgstr "" #: i2p2www/blog/2015/06/02/Toronto-Meetup.rst:55 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:59 msgid "I2P Presentation" msgstr "" #: i2p2www/blog/2015/06/02/Toronto-Meetup.rst:60 msgid "Crypto party introduction" msgstr "" #: i2p2www/blog/2015/06/02/Toronto-Meetup.rst:61 msgid "Crypto party" msgstr "" #: i2p2www/blog/2015/06/02/Toronto-Meetup.rst:63 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:67 msgid "`Vuze/I2P`_ - Downloading torrents anonymously" msgstr "" #: i2p2www/blog/2015/06/02/Toronto-Meetup.rst:68 msgid "`Veracrypt`_ - Encrypt your data" msgstr "" #: i2p2www/blog/2015/06/02/Toronto-Meetup.rst:69 msgid "`I2PBote`_ - Anonymous decentralized email" msgstr "" #: i2p2www/blog/2015/06/02/Toronto-Meetup.rst:70 msgid "Your station idea here" msgstr "" #: i2p2www/blog/2015/06/02/Toronto-Meetup.rst:72 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:81 msgid "Day 2, August 16 - 1PM" msgstr "" #: i2p2www/blog/2015/06/02/Toronto-Meetup.rst:86 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:90 msgid "I2P Technical presentation" msgstr "" #: i2p2www/blog/2015/06/02/Toronto-Meetup.rst:91 msgid "Technical discussion" msgstr "" #: i2p2www/blog/2015/06/02/Toronto-Meetup.rst:92 msgid "I2P App Dev Into" msgstr "" #: i2p2www/blog/2015/06/02/Toronto-Meetup.rst:93 msgid "I2PD presentation" msgstr "" #: i2p2www/blog/2015/06/02/Toronto-Meetup.rst:94 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:11 msgid "I2PCon will be in Toronto on August 15-16." msgstr "" #: i2p2www/blog/2015/07/16/I2PCon.rst:14 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:22 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:29 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:44 msgid "Cost" msgstr "免费" #: i2p2www/blog/2015/07/16/I2PCon.rst:49 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:63 msgid "`Hacklab`_ at 1266 Queen Street West, Unit #6, Toronto." msgstr "" #: i2p2www/blog/2015/07/16/I2PCon.rst:67 msgid "Venue" msgstr "" #: i2p2www/blog/2015/07/16/I2PCon.rst:72 msgid "Power and WiFi access will be provided by `Hacklab`_." msgstr "" #: i2p2www/blog/2015/07/16/I2PCon.rst:77 msgid "Schedule" msgstr "排程" #: i2p2www/blog/2015/07/16/I2PCon.rst:82 msgid "Day 1, August 15" msgstr "" #: i2p2www/blog/2015/07/16/I2PCon.rst:99 msgid "Day 2, August 16" msgstr "" #: i2p2www/blog/2015/07/16/I2PCon.rst:122 msgid "I'm confused and would like some answers" 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:11 msgid "0.9.21 with performance improvements and bug fixes" msgstr "" #: i2p2www/blog/2015/07/31/0.9.21-Release.rst:13 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 包含几个更改，以增加网络容量、提高播种效率，并更有效率的使用带宽。我们已经迁移共享客户端隧道到 ECDSA 签名，并使用新的 \"multisession\" 功能为那些不支持 ECDSA 的站点添加一个 DSA 后备。" #: i2p2www/blog/2015/07/31/0.9.21-Release.rst:20 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:41 msgid "Add multisession support for dual-signature crypto on the same tunnels" msgstr "" #: i2p2www/blog/2015/07/31/0.9.21-Release.rst:42 msgid "Use multisession for shared clients" msgstr "" #: i2p2www/blog/2015/07/31/0.9.21-Release.rst:43 msgid "Increase default outbound bandwidth limit to 60 KBps" msgstr "" #: i2p2www/blog/2015/07/31/0.9.21-Release.rst:44 msgid "Increase default maximum participating tunnels" msgstr "" #: i2p2www/blog/2015/07/31/0.9.21-Release.rst:45 msgid "" "Floodfills will send database store acks directly if connected, for " "efficiency" msgstr "" #: i2p2www/blog/2015/07/31/0.9.21-Release.rst:46 msgid "Set TCP keepalive on I2CP and SAM sockets" msgstr "" #: i2p2www/blog/2015/07/31/0.9.21-Release.rst:47 msgid "More efficient decompression in HTTP proxy, use less threads" msgstr "" #: i2p2www/blog/2015/07/31/0.9.21-Release.rst:48 msgid "Add support for fast extensions in i2psnark" msgstr "" #: i2p2www/blog/2015/07/31/0.9.21-Release.rst:49 msgid "i2psnark only autostarts torrents that were running previously" msgstr "" #: i2p2www/blog/2015/07/31/0.9.21-Release.rst:50 msgid "Add support for translated console news" msgstr "" #: i2p2www/blog/2015/07/31/0.9.21-Release.rst:55 msgid "SSU fixes to compete better with NTCP for bandwidth when limited" msgstr "" #: i2p2www/blog/2015/07/31/0.9.21-Release.rst:56 msgid "Fixes to prevent SSU stalls" msgstr "" #: i2p2www/blog/2015/07/31/0.9.21-Release.rst:57 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:58 msgid "Clean up resources correctly when SAM stops" msgstr "" #: i2p2www/blog/2015/07/31/0.9.21-Release.rst:59 msgid "Better error handling and notification when HTTP proxy is not running" msgstr "" #: i2p2www/blog/2015/07/31/0.9.21-Release.rst:60 msgid "More i2ptunnel fixes at startup and shutdown of tunnels" msgstr "" #: i2p2www/blog/2015/07/31/0.9.21-Release.rst:61 msgid "Fix total_size in i2psnark metadata message" msgstr "" #: i2p2www/blog/2015/07/31/0.9.21-Release.rst:62 msgid "Restore dates in console news headers" msgstr "" #: i2p2www/blog/2015/07/31/0.9.21-Release.rst:63 msgid "Several I2CP fixes" msgstr "" #: i2p2www/blog/2015/07/31/0.9.21-Release.rst:68 msgid "Use same session for naming lookups in I2PSocketEepGet" msgstr "" #: i2p2www/blog/2015/07/31/0.9.21-Release.rst:69 msgid "Increase max bandwidth to 16 MBps, add larger Bloom filter" msgstr "" #: i2p2www/blog/2015/07/31/0.9.21-Release.rst:70 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:11 msgid "I2PCon: Mission Accomplished" msgstr "" #: i2p2www/blog/2015/08/20/I2PCon_Mission_Accomplished.rst:14 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:28 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:37 msgid "" "Photos\n" "======" msgstr "" #: i2p2www/blog/2015/08/20/I2PCon_Mission_Accomplished.rst:45 msgid "The learn how to setup I2P crypto party station" msgstr "" #: i2p2www/blog/2015/08/20/I2PCon_Mission_Accomplished.rst:50 msgid "The learn how use I2P and Vuze party station" msgstr "" #: i2p2www/blog/2015/08/20/I2PCon_Mission_Accomplished.rst:55 msgid "David Dagons wonderful talk" msgstr "" #: i2p2www/blog/2015/08/20/I2PCon_Mission_Accomplished.rst:57 msgid "" "Thanks\n" "======" msgstr "" #: i2p2www/blog/2015/08/20/I2PCon_Mission_Accomplished.rst:62 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:72 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:78 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:83 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:87 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:91 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:96 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:100 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:105 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:109 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:11 msgid "0.9.22 with bug fixes and start of Ed25519 migration" msgstr "" #: i2p2www/blog/2015/09/12/0.9.22-Release.rst:13 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 "0.9.21 版本带有性能改进和缺陷修复。<br>" #: i2p2www/blog/2015/09/12/0.9.22-Release.rst:20 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:40 msgid "Start migration to Ed25519 router info signatures" msgstr "" #: i2p2www/blog/2015/09/12/0.9.22-Release.rst:41 msgid "Convert i2psnark destinations to Ed25519 signatures" msgstr "" #: i2p2www/blog/2015/09/12/0.9.22-Release.rst:46 msgid "" "Fix i2psnark getting stuck before download complete, and not deleting temp " "files" msgstr "" #: i2p2www/blog/2015/09/12/0.9.22-Release.rst:47 msgid "" "Fix starting of torrents added by copying torrent file to i2psnark directory" msgstr "" #: i2p2www/blog/2015/09/12/0.9.22-Release.rst:48 msgid "Fix UPnP 'content not allowed in trailing section' error" msgstr "" #: i2p2www/blog/2015/09/12/0.9.22-Release.rst:49 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:11 msgid "A start to more frequent community status reports." msgstr "" #: i2p2www/blog/2015/11/15/Community-Outreach.rst:13 msgid "Meta" msgstr "" #: i2p2www/blog/2015/11/15/Community-Outreach.rst:15 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:21 msgid "A Call for Feedback" msgstr "" #: i2p2www/blog/2015/11/15/Community-Outreach.rst:23 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:29 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:41 msgid "Developer Meeting Synopsis" msgstr "" #: i2p2www/blog/2015/11/15/Community-Outreach.rst:43 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:50 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:57 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:62 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:67 msgid "General Announcements" msgstr "" #: i2p2www/blog/2015/11/15/Community-Outreach.rst:69 msgid "" "Thank you to `TorontoCrypto`_ for hosting the newest I2P reseed server!" msgstr "" #: i2p2www/blog/2015/11/15/Community-Outreach.rst:75 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:11 msgid "" "0.9.23 contains a variety of bug fixes, and some minor improvements in " "I2PSnark" msgstr "0.9.23 包含多个错误修复，以及一些对 I2PSnark 的小幅改善" #: i2p2www/blog/2015/11/19/0.9.23-Release.rst:13 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 "欢迎使用 I2P！这是我 (str4d) 签发的第一个版本，在 zzz 签发 49 个版本之后。这是我们对所有事物过多冗余的一次重要测试，包括人员。" #: i2p2www/blog/2015/11/19/0.9.23-Release.rst:19 msgid "Housekeeping" msgstr "管家" #: i2p2www/blog/2015/11/19/0.9.23-Release.rst:24 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:38 msgid "" "If you installed I2P via a package manager, you are not affected by the change,\n" "and can update as usual." msgstr "如果您已通过一个软件包管理器来安装 I2P，您不会受到此更改的影响，并且可以照常更新。" #: i2p2www/blog/2015/11/19/0.9.23-Release.rst:43 msgid "" "Update details\n" "==============" msgstr "" #: i2p2www/blog/2015/11/19/0.9.23-Release.rst:48 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 到新的、更强的 Ed25519 签名很顺利，预计已有至少一半的网络转换密钥。此次发布加速了密钥更新的过程。为了减少网络客户端的流失，您的路由器将在每次重启时有较小的概率转换到 Ed25519。在它转换密钥后，可预期的两天内将有更低的带宽，因为它需要将新的身份重新集成到网络。" #: i2p2www/blog/2015/11/19/0.9.23-Release.rst:57 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 "请注意，这是最后一个支持 Java 6 的发布版本。请尽快更新到 Java 7 或者 8。我们已经努力使 I2P 兼容即将到来的 Java 9，并且一些成果已经放在此次发布中。" #: i2p2www/blog/2015/11/19/0.9.23-Release.rst:63 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 做了一些细微的改进，并且在路由器控制台中加入了一个新的页面用以查看较旧的新闻。" #: i2p2www/blog/2015/11/19/0.9.23-Release.rst:78 msgid "Accelerate transition to Ed25519" msgstr "" #: i2p2www/blog/2015/11/19/0.9.23-Release.rst:83 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:84 msgid "" "Fix streaming retransmission timers that were dying, and related timer bugs" msgstr "" #: i2p2www/blog/2015/11/19/0.9.23-Release.rst:85 msgid "Fix streaming connections rejected while tunnel is opening" msgstr "" #: i2p2www/blog/2015/11/19/0.9.23-Release.rst:86 msgid "Fix rare i2psnark and UPnP deadlocks" msgstr "" #: i2p2www/blog/2015/11/19/0.9.23-Release.rst:87 msgid "Fix lifetime participating bandwidth display in console" msgstr "" #: i2p2www/blog/2015/11/19/0.9.23-Release.rst:92 msgid "Increase default outbound exploratory tunnel length to 3" msgstr "" #: i2p2www/blog/2015/11/19/0.9.23-Release.rst:93 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:94 msgid "Add support for hostnames prefixed with \"www.\"" msgstr "" #: i2p2www/blog/2015/11/19/0.9.23-Release.rst:95 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:96 msgid "Increase probability of rekeying to EdDSA" msgstr "" #: i2p2www/blog/2015/11/19/0.9.23-Release.rst:97 msgid "Detect for broken ECDSA support in Gentoo" msgstr "" #: i2p2www/blog/2015/11/19/0.9.23-Release.rst:98 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:99 msgid "Changes to prepare for Java 9 compatibility" msgstr "" #: i2p2www/blog/2015/11/19/0.9.23-Release.rst:100 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:103 msgid "Increase piece size, piece count, and file count limits" msgstr "" #: i2p2www/blog/2015/11/19/0.9.23-Release.rst:104 msgid "Save added and completed times" msgstr "" #: i2p2www/blog/2015/11/19/0.9.23-Release.rst:105 msgid "Save magnet parameters across restart" msgstr "" #: i2p2www/blog/2015/11/19/0.9.23-Release.rst:106 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:107 msgid "Add recheck, start, stop buttons on details pages" msgstr "" #: i2p2www/blog/2015/11/19/0.9.23-Release.rst:108 msgid "Add option to disable \"smart sort\"" msgstr "" #: i2p2www/blog/2015/11/19/0.9.23-Release.rst:110 msgid "Speed up IP address validation" msgstr "" #: i2p2www/blog/2015/11/19/0.9.23-Release.rst:111 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:11 msgid "CCC!" msgstr "" #: i2p2www/blog/2016/01/23/32C3.rst:13 msgid "" "Attending: Sadie, Colin, lazygravy, zzz, hottuna, kytv, cacapo, and eche|on." msgstr "" #: i2p2www/blog/2016/01/23/32C3.rst:17 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:29 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:63 msgid "" "Reseed Status\n" "=============" msgstr "" #: i2p2www/blog/2016/01/23/32C3.rst:68 msgid "Let's get more reseeds!" msgstr "" #: i2p2www/blog/2016/01/23/32C3.rst:72 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:81 msgid "" "Sybil Detection (beta)\n" "======================" msgstr "" #: i2p2www/blog/2016/01/23/32C3.rst:86 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:94 msgid "" "Development Meeting\n" "===================" msgstr "" #: i2p2www/blog/2016/01/23/32C3.rst:99 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:106 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:115 msgid "" "Meeting (Future)\n" "================" msgstr "" #: i2p2www/blog/2016/01/23/32C3.rst:120 msgid "There will be a `another meeting`__ on 2 Feburary 2016 to discuss:" msgstr "" #: i2p2www/blog/2016/01/23/32C3.rst:124 msgid "Review of assigned tasks from 30 December meeting" msgstr "" #: i2p2www/blog/2016/01/23/32C3.rst:125 msgid "Project meeting plan for 2016" msgstr "" #: i2p2www/blog/2016/01/23/32C3.rst:126 msgid "GMP 6 readiness" msgstr "" #: i2p2www/blog/2016/01/23/32C3.rst:127 msgid "A proposal for a code of conduct" 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:11 msgid "0.9.24 contains a variety of bug fixes and performance enhancements" msgstr "" #: i2p2www/blog/2016/01/27/0.9.24-Release.rst:13 #: i2p2www/blog/2016/03/22/0.9.25-Release.rst:13 #: i2p2www/blog/2016/06/07/0.9.26-Release.rst:20 #: i2p2www/blog/2016/10/17/0.9.27-Release.rst:13 #: i2p2www/blog/2016/12/12/0.9.28-Release.rst:13 #: i2p2www/blog/2017/02/27/0.9.29-Release.rst:13 #: i2p2www/blog/2017/03/04/0.9.29-Windows-Installer-Fix.rst:13 #: i2p2www/blog/2017/05/03/0.9.30-Release.rst:13 #: i2p2www/blog/2017/08/07/0.9.31-Release.rst:13 #: i2p2www/blog/2017/11/07/0.9.32-Release.rst:13 #: 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:11 #: i2p2www/blog/2018/08/23/0.9.36-Release.rst:12 #: i2p2www/blog/2018/10/04/0.9.37-Release.rst:11 #: i2p2www/blog/2019/01/22/0.9.38-Release.rst:11 #: i2p2www/blog/2019/03/21/0.9.39-Release.rst:11 #: i2p2www/blog/2019/05/07/0.9.40-Release.rst:11 #: i2p2www/blog/2019/07/02/0.9.41-Release.rst:11 #: i2p2www/blog/2019/08/27/0.9.42-Release.rst:11 #: i2p2www/blog/2019/10/22/0.9.43-Release.rst:11 #: i2p2www/blog/2019/12/01/0.9.44-Release.rst:11 #: i2p2www/blog/2020/02/25/0.9.45-Release.rst:11 #: i2p2www/blog/2020/05/25/0.9.46-Release.rst:11 #: i2p2www/blog/2020/08/24/0.9.47-Release.rst:11 #: i2p2www/blog/2020/11/30/0.9.48-Release.rst:11 #: i2p2www/blog/2021/02/17/0.9.49-Release.rst:11 #: i2p2www/blog/2021/05/17/0.9.50-Release.rst:11 #: i2p2www/blog/2021/08/23/1.5.0-Release.rst:11 msgid "Update details" msgstr "更新细节" #: i2p2www/blog/2016/01/27/0.9.24-Release.rst:18 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 包含新版本的 SAM (v3.2) 和众多问题修复和效率改进。\n注意，这是首个必需使用 Java 7 的发布版本。\n请尽快升级到 Java 7 或 8。\n如果您在使用 Java 6，您的路由将不会自动更新。" #: i2p2www/blog/2016/01/27/0.9.24-Release.rst:25 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:34 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:58 msgid "Java 7 now required" msgstr "" #: i2p2www/blog/2016/01/27/0.9.24-Release.rst:59 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:60 msgid "Router Family" msgstr "路由器家族" #: i2p2www/blog/2016/01/27/0.9.24-Release.rst:61 msgid "Commons logging removed" msgstr "" #: i2p2www/blog/2016/01/27/0.9.24-Release.rst:66 msgid "Fix HTML escaping in the console plugin table" msgstr "" #: i2p2www/blog/2016/01/27/0.9.24-Release.rst:67 msgid "Fix rare deadlocks in the router" msgstr "" #: i2p2www/blog/2016/01/27/0.9.24-Release.rst:68 msgid "Fix the tunnel build Bloom filter" msgstr "" #: i2p2www/blog/2016/01/27/0.9.24-Release.rst:69 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:70 msgid "Fix formatting in summary bar to prevent overflow" msgstr "" #: i2p2www/blog/2016/01/27/0.9.24-Release.rst:71 msgid "" "Fix console links in i2ptunnel error pages when on nonstandard host/port" msgstr "" #: i2p2www/blog/2016/01/27/0.9.24-Release.rst:72 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:73 msgid "Reduce out-of-order delivery in SSU" msgstr "" #: i2p2www/blog/2016/01/27/0.9.24-Release.rst:74 msgid "Fix a rare NPE in the tunnel build handler" msgstr "" #: i2p2www/blog/2016/01/27/0.9.24-Release.rst:79 msgid "Listen for Windows Service shutdown events to shutdown cleanly" msgstr "" #: i2p2www/blog/2016/01/27/0.9.24-Release.rst:80 msgid "Fix some IPv6 issues on Windows" msgstr "" #: i2p2www/blog/2016/01/27/0.9.24-Release.rst:81 msgid "Change Jetty request logging from b64 to b32" msgstr "" #: i2p2www/blog/2016/01/27/0.9.24-Release.rst:82 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:83 msgid "New overview picture in SusiDNS" msgstr "" #: i2p2www/blog/2016/01/27/0.9.24-Release.rst:84 msgid "Close connection faster if it's for a rejected tunnel request" msgstr "" #: i2p2www/blog/2016/01/27/0.9.24-Release.rst:85 msgid "Use SSU extended options field for session request message" msgstr "" #: i2p2www/blog/2016/01/27/0.9.24-Release.rst:86 msgid "Request introduction in the SSU extended options" msgstr "" #: i2p2www/blog/2016/01/27/0.9.24-Release.rst:87 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:88 msgid "Experimental Sybil analysis tool, requires routerconsole.advanced=true" msgstr "" #: i2p2www/blog/2016/01/27/0.9.24-Release.rst:89 msgid "Persist some profile netdb stats that weren't being saved" msgstr "" #: i2p2www/blog/2016/01/27/0.9.24-Release.rst:90 msgid "Memory reduction and other efficiency improvements throughout" msgstr "" #: i2p2www/blog/2016/01/27/0.9.24-Release.rst:91 msgid "Increase several limits in i2psnark" msgstr "" #: i2p2www/blog/2016/01/27/0.9.24-Release.rst:92 msgid "New streaming unit tests" msgstr "" #: i2p2www/blog/2016/01/27/0.9.24-Release.rst:93 msgid "Fix some SSU stats on /peers to be consistent with NTCP" msgstr "" #: i2p2www/blog/2016/01/27/0.9.24-Release.rst:94 msgid "Change default sig type for new i2ptunnels to Ed25519" msgstr "" #: i2p2www/blog/2016/01/27/0.9.24-Release.rst:95 msgid "Increase router rekey probability at startup again" msgstr "" #: i2p2www/blog/2016/01/27/0.9.24-Release.rst:96 msgid "New Chinese (Taiwan) translation" msgstr "" #: i2p2www/blog/2016/01/27/0.9.24-Release.rst:101 #: i2p2www/blog/2016/03/22/0.9.25-Release.rst:72 #: i2p2www/blog/2016/06/07/0.9.26-Release.rst:92 #: i2p2www/blog/2016/10/17/0.9.27-Release.rst:69 #: i2p2www/blog/2016/12/12/0.9.28-Release.rst:99 #: i2p2www/blog/2017/02/27/0.9.29-Release.rst:73 #: i2p2www/blog/2017/05/03/0.9.30-Release.rst:98 #: i2p2www/blog/2017/08/07/0.9.31-Release.rst:65 #: i2p2www/blog/2017/11/07/0.9.32-Release.rst:54 #: i2p2www/blog/2018/01/30/0.9.33-Release.rst:99 #: i2p2www/blog/2018/04/10/0.9.34-Release.rst:58 #: i2p2www/blog/2018/06/26/0.9.35-Release.rst:73 #: i2p2www/blog/2018/08/23/0.9.36-Release.rst:68 #: i2p2www/blog/2018/10/04/0.9.37-Release.rst:50 #: i2p2www/blog/2019/01/22/0.9.38-Release.rst:67 #: i2p2www/blog/2019/03/21/0.9.39-Release.rst:67 #: i2p2www/blog/2019/05/07/0.9.40-Release.rst:70 #: i2p2www/blog/2019/07/02/0.9.41-Release.rst:70 #: i2p2www/blog/2019/08/27/0.9.42-Release.rst:64 #: i2p2www/blog/2019/10/22/0.9.43-Release.rst:61 #: i2p2www/blog/2019/12/01/0.9.44-Release.rst:70 #: i2p2www/blog/2020/02/25/0.9.45-Release.rst:60 #: i2p2www/blog/2020/05/25/0.9.46-Release.rst:82 #: i2p2www/blog/2020/08/24/0.9.47-Release.rst:71 #: i2p2www/blog/2020/11/30/0.9.48-Release.rst:88 #: i2p2www/blog/2021/02/17/0.9.49-Release.rst:92 #: i2p2www/blog/2021/05/17/0.9.50-Release.rst:89 #: i2p2www/blog/2021/08/23/1.5.0-Release.rst:61 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:11 msgid "0.9.25 contains SAM 3.3, QR codes, and bug fixes" msgstr "0.9.25 包含 SAM 3.3、QR 码及缺陷修复" #: i2p2www/blog/2016/03/22/0.9.25-Release.rst:18 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 包含 SAM 的一个主要新版本 v3.3，以支持复杂的多协议应用程序。\n增加了 QR 码用于与其他人分享隐身服务。\n增加了“身份”图像用于视觉上区分地址。" #: i2p2www/blog/2016/03/22/0.9.25-Release.rst:24 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 "我们在控制台中添加了新的“路由器家族”配置页面，\n这可以让您更容易的声明您的一组路由器是由一个人运行。\n有一些变更以增加网络容量，并希望能够提升隧道构建成功率。" #: i2p2www/blog/2016/03/22/0.9.25-Release.rst:40 msgid "Display of identicons and QR codes in address book and i2ptunnel" msgstr "" #: i2p2www/blog/2016/03/22/0.9.25-Release.rst:41 msgid "SAM v3.3 with advanced features" msgstr "" #: i2p2www/blog/2016/03/22/0.9.25-Release.rst:42 msgid "Configuration page for router family" msgstr "" #: i2p2www/blog/2016/03/22/0.9.25-Release.rst:43 msgid "Custom icons for plugins" msgstr "" #: i2p2www/blog/2016/03/22/0.9.25-Release.rst:44 msgid "Internal implementation of self-signed certificate generation" msgstr "" #: i2p2www/blog/2016/03/22/0.9.25-Release.rst:45 msgid "Add i2ptunnel http server options to block by referer or user-agent" msgstr "" #: i2p2www/blog/2016/03/22/0.9.25-Release.rst:50 msgid "IRC server tunnel default fix to help reliability" msgstr "" #: i2p2www/blog/2016/03/22/0.9.25-Release.rst:51 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:56 msgid "Preliminary support for certificate revocations" msgstr "" #: i2p2www/blog/2016/03/22/0.9.25-Release.rst:57 msgid "Preliminary support for storing EdDSA and ElGamal keys in keystores" msgstr "" #: i2p2www/blog/2016/03/22/0.9.25-Release.rst:58 msgid "More efficient signing and verification with EdDSA" msgstr "" #: i2p2www/blog/2016/03/22/0.9.25-Release.rst:59 msgid "Increase default connection limits" msgstr "" #: i2p2www/blog/2016/03/22/0.9.25-Release.rst:60 msgid "Increase default inbound bandwidth" msgstr "" #: i2p2www/blog/2016/03/22/0.9.25-Release.rst:61 msgid "Increase max files per torrent in i2psnark" msgstr "" #: i2p2www/blog/2016/03/22/0.9.25-Release.rst:62 msgid "Add more sanity checks to detect bad system clock" msgstr "" #: i2p2www/blog/2016/03/22/0.9.25-Release.rst:63 msgid "Improve news styling in console" msgstr "" #: i2p2www/blog/2016/03/22/0.9.25-Release.rst:64 msgid "Improve certificate blacklist implementation" msgstr "" #: i2p2www/blog/2016/03/22/0.9.25-Release.rst:65 msgid "Faster disconnect after publishing router info to floodfill" msgstr "" #: i2p2www/blog/2016/03/22/0.9.25-Release.rst:66 msgid "Smooth out the dropping of idle SSU sessions" msgstr "" #: i2p2www/blog/2016/03/22/0.9.25-Release.rst:67 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:11 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:13 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:21 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:36 msgid "" "Helping developers help their users\n" "===================================" msgstr "" #: i2p2www/blog/2016/06/01/I2P-Summer-Dev.rst:41 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:48 msgid "" "We will be focusing our time this summer into three complementary areas:" msgstr "" #: i2p2www/blog/2016/06/01/I2P-Summer-Dev.rst:52 msgid "" "June: APIs\n" "----------" msgstr "" #: i2p2www/blog/2016/06/01/I2P-Summer-Dev.rst:57 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:64 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:71 msgid "" "July: Apps\n" "----------" msgstr "" #: i2p2www/blog/2016/06/01/I2P-Summer-Dev.rst:76 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:86 msgid "" "August: Plugins\n" "---------------" msgstr "" #: i2p2www/blog/2016/06/01/I2P-Summer-Dev.rst:91 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:99 #: i2p2www/blog/2016/07/02/Summer-Dev-roundup-APIs.rst:126 #: i2p2www/blog/2017/06/01/Summer-Dev-2017-MOAR-Speed.rst:115 msgid "" "Take part in Summer Dev!\n" "========================" msgstr "" #: i2p2www/blog/2016/06/01/I2P-Summer-Dev.rst:104 #: i2p2www/blog/2016/07/02/Summer-Dev-roundup-APIs.rst:131 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:113 #: i2p2www/blog/2016/07/02/Summer-Dev-roundup-APIs.rst:140 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:120 #: i2p2www/blog/2016/07/02/Summer-Dev-roundup-APIs.rst:147 #: i2p2www/blog/2017/06/01/Summer-Dev-2017-MOAR-Speed.rst:131 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:11 msgid "" "0.9.26 contains crypto updates, Debian packaging improvements, and bug fixes" msgstr "0.9.26 包含加密学更新，Debian 包改进，以及缺陷修复。" #: i2p2www/blog/2016/06/07/0.9.26-Release.rst:13 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:25 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 对我们的加密程序库进行了一次重要升级，有新的地址簿订阅协议和签名，以及 Debian/Ubuntu 包的重要改进。" #: i2p2www/blog/2016/06/07/0.9.26-Release.rst:31 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 "加密学方面，我们升级到 GMP 6.0.0，并添加较新处理器的支持，这可以大幅加速密码运算。\n另外，我们现在使用常数时间的 GMP 函数以防止侧信道攻击。\n出于谨慎，GMP 更改只对新的安装和 Debian/Ubuntu 构建启用；我们会在 0.9.27 发布时更新它们。" #: i2p2www/blog/2016/06/07/0.9.26-Release.rst:39 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 构建，我们添加了几个包的依赖，包括 Jetty 8 和 geoip，并移除封装的等效代码。" #: i2p2www/blog/2016/06/07/0.9.26-Release.rst:44 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:59 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:60 msgid "Addressbook subscription protocol, enabling signed addressbook updates" msgstr "" #: i2p2www/blog/2016/06/07/0.9.26-Release.rst:61 msgid "Generate signed authentication strings for subscriptions in i2ptunnel" msgstr "" #: i2p2www/blog/2016/06/07/0.9.26-Release.rst:62 msgid "" "Enhance hosts blockfile format to allow for multiple destinations per entry" msgstr "" #: i2p2www/blog/2016/06/07/0.9.26-Release.rst:63 msgid "Use system GeoIP database when available" msgstr "" #: i2p2www/blog/2016/06/07/0.9.26-Release.rst:64 msgid "" "Remove systray4j.jar from non-Windows installers and Debian/Ubuntu packages" msgstr "" #: i2p2www/blog/2016/06/07/0.9.26-Release.rst:65 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:66 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:67 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:68 msgid "Wrapper 3.5.29 (new non-Windows installs only)" msgstr "" #: i2p2www/blog/2016/06/07/0.9.26-Release.rst:74 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:75 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:76 msgid "Fix NPE on hostname lookup failure in SOCKS 4a" msgstr "" #: i2p2www/blog/2016/06/07/0.9.26-Release.rst:77 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:78 msgid "Fix UTF-8 console passwords, and partial fix for usernames" msgstr "" #: i2p2www/blog/2016/06/07/0.9.26-Release.rst:79 msgid "Fix router family configuration form" msgstr "" #: i2p2www/blog/2016/06/07/0.9.26-Release.rst:80 msgid "Fix NTP sending random data in some fields that should be zero" msgstr "" #: i2p2www/blog/2016/06/07/0.9.26-Release.rst:86 msgid "More verification of received NTP packets" msgstr "" #: i2p2www/blog/2016/06/07/0.9.26-Release.rst:87 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:11 msgid "The I2P client libraries are now available on Maven Central!" msgstr "" #: i2p2www/blog/2016/06/13/I2P-on-Maven-Central.rst:13 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:19 #: i2p2www/blog/2016/07/02/Summer-Dev-roundup-APIs.rst:51 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:27 msgid "" "How to use them\n" "===============" msgstr "" #: i2p2www/blog/2016/06/13/I2P-on-Maven-Central.rst:32 msgid "There are two libraries that you need to know about:" msgstr "" #: i2p2www/blog/2016/06/13/I2P-on-Maven-Central.rst:36 msgid "The core I2P APIs; you can use these to send individual datagrams." msgstr "" #: i2p2www/blog/2016/06/13/I2P-on-Maven-Central.rst:37 msgid "A TCP-like set of sockets for communicating over I2P." msgstr "" #: i2p2www/blog/2016/06/13/I2P-on-Maven-Central.rst:39 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:67 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:72 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:84 msgid "" "Get hacking!\n" "============" msgstr "" #: i2p2www/blog/2016/06/13/I2P-on-Maven-Central.rst:89 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/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:11 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:13 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:19 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:28 msgid "" "APIs month\n" "==========" msgstr "" #: i2p2www/blog/2016/07/02/Summer-Dev-roundup-APIs.rst:33 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:43 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:58 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:71 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:84 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:93 msgid "" "Other progress\n" "--------------" msgstr "" #: i2p2www/blog/2016/07/02/Summer-Dev-roundup-APIs.rst:98 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:100 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:104 msgid "" "Coming up: Apps month!\n" "======================" msgstr "" #: i2p2www/blog/2016/07/02/Summer-Dev-roundup-APIs.rst:109 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:117 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/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:11 msgid "0.9.27 contains bug fixes" msgstr "0.9.27 包含缺陷修复" #: i2p2www/blog/2016/10/17/0.9.27-Release.rst:18 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 包含一些缺陷修复。\n更新的 GMP 程序库为加密提速了，这在新安装的 0.9.26 版本及 Debian 版本中启用，网络更新用户将在 0.9.27 时享用到它。\nIPv6 传输、SSU 对等端测试、隐身模式等也有改进。" #: i2p2www/blog/2016/10/17/0.9.27-Release.rst:24 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:38 msgid "GMP 6 (in-net updates)" msgstr "" #: i2p2www/blog/2016/10/17/0.9.27-Release.rst:39 msgid "SSU Peer Testing for IPv6" msgstr "" #: i2p2www/blog/2016/10/17/0.9.27-Release.rst:40 msgid "Add outproxy plugin support for SOCKS" msgstr "" #: i2p2www/blog/2016/10/17/0.9.27-Release.rst:41 msgid "Enable desktop GUI (tray icon) on Windows" msgstr "" #: i2p2www/blog/2016/10/17/0.9.27-Release.rst:46 msgid "Fix reported GMP version when jbigi built as a shared library" msgstr "" #: i2p2www/blog/2016/10/17/0.9.27-Release.rst:47 msgid "Fix SSU peer test happening too frequently" msgstr "" #: i2p2www/blog/2016/10/17/0.9.27-Release.rst:48 msgid "Fix SSU peer test not terminating properly in some cases" msgstr "" #: i2p2www/blog/2016/10/17/0.9.27-Release.rst:49 msgid "Fix bote plugin not working in Debian/Ubuntu builds" msgstr "" #: i2p2www/blog/2016/10/17/0.9.27-Release.rst:50 msgid "Fix rare UPnP NPE when viewing /peers" msgstr "" #: i2p2www/blog/2016/10/17/0.9.27-Release.rst:51 msgid "Fix standalone i2psnark build and configuration" msgstr "" #: i2p2www/blog/2016/10/17/0.9.27-Release.rst:52 msgid "Hidden mode improvements: Enable tunnel testing and use fast peers" msgstr "" #: i2p2www/blog/2016/10/17/0.9.27-Release.rst:53 msgid "Fix possible CSRF in SusiMail" msgstr "" #: i2p2www/blog/2016/10/17/0.9.27-Release.rst:54 msgid "Fix i2psnark exception on bad configured announce URL" msgstr "" #: i2p2www/blog/2016/10/17/0.9.27-Release.rst:55 msgid "Fix layout issues on i2ptunnel registration page" msgstr "" #: i2p2www/blog/2016/10/17/0.9.27-Release.rst:56 msgid "Fix streaming accept() hang when session disconnects" msgstr "" #: i2p2www/blog/2016/10/17/0.9.27-Release.rst:61 msgid "Split up the large /configclients web page into several" msgstr "" #: i2p2www/blog/2016/10/17/0.9.27-Release.rst:62 msgid "Add links to view complete router and wrapper log files" msgstr "" #: i2p2www/blog/2016/10/17/0.9.27-Release.rst:63 msgid "Block 'Proxy' header in i2ptunnel (HTTPoxy)" msgstr "" #: i2p2www/blog/2016/10/17/0.9.27-Release.rst:64 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:11 msgid "0.9.28 contains bug fixes" msgstr "0.9.28 包含缺陷修复" #: i2p2www/blog/2016/12/12/0.9.28-Release.rst:18 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 个 Trac 工单的修复，并更新了捆绑的一些软件包，包括 Jetty。\n它修复了上一版本引入的 IPv6 对等端测试功能。\n我们继续改进以检测和阻止潜在的恶意对等端。\n虽然我们尚不推荐将 Java 9 用作一般用途，但也为 Java 9 做了初步修复。" #: i2p2www/blog/2016/12/12/0.9.28-Release.rst:25 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，请来我们的桌边逛逛，并告诉我们您改进这个网络的想法。\n我们会在大会上回顾我们2017年的蓝图以及优先事项。" #: i2p2www/blog/2016/12/12/0.9.28-Release.rst:50 msgid "Fix version test for SSU IPv6 peer testing" msgstr "" #: i2p2www/blog/2016/12/12/0.9.28-Release.rst:51 msgid "Fix generation of keys for SSL console" msgstr "" #: i2p2www/blog/2016/12/12/0.9.28-Release.rst:52 msgid "Fix uploader limit in i2psnark" msgstr "" #: i2p2www/blog/2016/12/12/0.9.28-Release.rst:53 msgid "Fix susimail nonce error on login after logout" msgstr "" #: i2p2www/blog/2016/12/12/0.9.28-Release.rst:54 msgid "Fixes for Java 9" msgstr "" #: i2p2www/blog/2016/12/12/0.9.28-Release.rst:60 msgid "Allow Java 9 in packages" msgstr "" #: i2p2www/blog/2016/12/12/0.9.28-Release.rst:61 msgid "Add warning for Java 9, not yet recommended" msgstr "" #: i2p2www/blog/2016/12/12/0.9.28-Release.rst:62 msgid "Preliminary fixes for use with Tomcat 8" msgstr "" #: i2p2www/blog/2016/12/12/0.9.28-Release.rst:63 msgid "Improved self-signed certificates" msgstr "" #: i2p2www/blog/2016/12/12/0.9.28-Release.rst:64 msgid "Increase max IPv6 MTU (proposal #127)" msgstr "" #: i2p2www/blog/2016/12/12/0.9.28-Release.rst:65 msgid "Caching of serialized leasesets" msgstr "" #: i2p2www/blog/2016/12/12/0.9.28-Release.rst:66 msgid "Peer selection updates" msgstr "" #: i2p2www/blog/2016/12/12/0.9.28-Release.rst:67 msgid "Restrictions in peer selection for netdb verifies" msgstr "" #: i2p2www/blog/2016/12/12/0.9.28-Release.rst:68 msgid "New advanced netdb search form" msgstr "" #: i2p2www/blog/2016/12/12/0.9.28-Release.rst:69 msgid "Sybil tool enhancements" msgstr "" #: i2p2www/blog/2016/12/12/0.9.28-Release.rst:70 msgid "Blocklist updates in news feed" msgstr "" #: i2p2www/blog/2016/12/12/0.9.28-Release.rst:71 msgid "Support IPv6 in blocklist" msgstr "" #: i2p2www/blog/2016/12/12/0.9.28-Release.rst:72 msgid "Add Java version to jar manifests" msgstr "" #: i2p2www/blog/2016/12/12/0.9.28-Release.rst:73 msgid "Remove dead console home page links" msgstr "" #: i2p2www/blog/2016/12/12/0.9.28-Release.rst:74 msgid "Add initial news to bottom of full news page" msgstr "" #: i2p2www/blog/2016/12/12/0.9.28-Release.rst:75 msgid "Fix periodic re-logging of dup log messages" msgstr "" #: i2p2www/blog/2016/12/12/0.9.28-Release.rst:76 msgid "Periodic saving of profiles and i2psnark DHT nodes" msgstr "" #: i2p2www/blog/2016/12/12/0.9.28-Release.rst:77 msgid "Catch rare UPnP exceptions" msgstr "" #: i2p2www/blog/2016/12/12/0.9.28-Release.rst:78 msgid "Add logout button to more susimail pages" msgstr "" #: i2p2www/blog/2016/12/12/0.9.28-Release.rst:79 msgid "Truncate history.txt in installers" msgstr "" #: i2p2www/blog/2016/12/12/0.9.28-Release.rst:80 msgid "Use NTCP even before SSU minimums are met or SSU is broken" msgstr "" #: i2p2www/blog/2016/12/12/0.9.28-Release.rst:81 msgid "Reduce default tunnel build records to 4" msgstr "" #: i2p2www/blog/2016/12/12/0.9.28-Release.rst:82 msgid "Improved IPv6 address selection" msgstr "" #: i2p2www/blog/2016/12/12/0.9.28-Release.rst:83 msgid "Add force-firewalled IPv6 setting" msgstr "" #: i2p2www/blog/2016/12/12/0.9.28-Release.rst:84 msgid "Improved handling of webapps that fail to start" msgstr "" #: i2p2www/blog/2016/12/12/0.9.28-Release.rst:85 msgid "New configuration for test networks" msgstr "" #: i2p2www/blog/2016/12/12/0.9.28-Release.rst:86 msgid "Remove deprecated Sha256Standalone, Syndie 1.105 must upgrade" msgstr "" #: i2p2www/blog/2016/12/12/0.9.28-Release.rst:87 msgid "Actually use a random nonzero byte in ElGamal, as specified" msgstr "" #: i2p2www/blog/2016/12/12/0.9.28-Release.rst:88 msgid "Disallow RSA for netdb entries" msgstr "" #: i2p2www/blog/2016/12/12/0.9.28-Release.rst:89 msgid "Add library jars to jar classpath for Debian builds" msgstr "" #: i2p2www/blog/2016/12/12/0.9.28-Release.rst:90 msgid "Remove old systray code" msgstr "" #: i2p2www/blog/2016/12/12/0.9.28-Release.rst:91 msgid "Fix low-memory warnings without wrapper" msgstr "" #: i2p2www/blog/2016/12/12/0.9.28-Release.rst:92 msgid "Various code consolidation and cleanup" msgstr "" #: i2p2www/blog/2016/12/12/0.9.28-Release.rst:93 msgid "New translations: Galician, Korean" msgstr "" #: i2p2www/blog/2016/12/12/0.9.28-Release.rst:94 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:11 msgid "0.9.29 contains bug fixes" msgstr "0.9.29包含缺陷修复" #: i2p2www/blog/2017/02/27/0.9.29-Release.rst:18 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版本包含大量Trac工单的修复，包括针对错误压缩的消息的变通方案。\n我们现在在IPv6上提供对NTP的支持。\n我们对Docker加入了初步的支持。\n我们翻译了手册页。\n我们现在通过HTTP代理传输same-origin Referer标头。\n我们为Java 9进行了更多的修复，然而我们尚不推荐将Java 9用作一般用途。" #: i2p2www/blog/2017/02/27/0.9.29-Release.rst:37 msgid "BOB database refactor" msgstr "" #: i2p2www/blog/2017/02/27/0.9.29-Release.rst:38 msgid "Fixes for Java 9, still not recommended for general use" msgstr "" #: i2p2www/blog/2017/02/27/0.9.29-Release.rst:39 msgid "NTP fixes for security and standards" msgstr "" #: i2p2www/blog/2017/02/27/0.9.29-Release.rst:40 msgid "NTP IPv6 support" msgstr "" #: i2p2www/blog/2017/02/27/0.9.29-Release.rst:41 msgid "Don't display very old news in console" msgstr "" #: i2p2www/blog/2017/02/27/0.9.29-Release.rst:42 msgid "Blocklist checking improvements" msgstr "" #: i2p2www/blog/2017/02/27/0.9.29-Release.rst:43 msgid "Add preliminary Docker support" msgstr "" #: i2p2www/blog/2017/02/27/0.9.29-Release.rst:44 msgid "Add Referrer-Policy headers to console" msgstr "" #: i2p2www/blog/2017/02/27/0.9.29-Release.rst:45 msgid "Pass same-origin Referer headers through proxy" msgstr "" #: i2p2www/blog/2017/02/27/0.9.29-Release.rst:46 msgid "Translated man pages" msgstr "" #: i2p2www/blog/2017/02/27/0.9.29-Release.rst:51 msgid "Add support for outproxy plugin to CONNECT proxy" msgstr "" #: i2p2www/blog/2017/02/27/0.9.29-Release.rst:52 msgid "Replace random tunnel keys when rekeying" msgstr "" #: i2p2www/blog/2017/02/27/0.9.29-Release.rst:53 msgid "Fix streaming optional delay and choking" msgstr "" #: i2p2www/blog/2017/02/27/0.9.29-Release.rst:54 msgid "Don't hard fail on message expired error in streaming" msgstr "" #: i2p2www/blog/2017/02/27/0.9.29-Release.rst:55 msgid "Fix javadoc errors" msgstr "" #: i2p2www/blog/2017/02/27/0.9.29-Release.rst:56 msgid "Fix broken unit tests" msgstr "" #: i2p2www/blog/2017/02/27/0.9.29-Release.rst:57 msgid "Ensure i2psnark finishes writing config files at shutdown" msgstr "" #: i2p2www/blog/2017/02/27/0.9.29-Release.rst:58 msgid "Fix rare NPE in AES via NTCP" msgstr "" #: i2p2www/blog/2017/02/27/0.9.29-Release.rst:59 msgid "Disable caching of compressors, in an attempt to fix corruption" msgstr "" #: i2p2www/blog/2017/02/27/0.9.29-Release.rst:60 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:65 msgid "Add support for ports to CONNECT proxy" msgstr "" #: i2p2www/blog/2017/02/27/0.9.29-Release.rst:66 msgid "Consolidate stream copy code" msgstr "" #: i2p2www/blog/2017/02/27/0.9.29-Release.rst:67 msgid "Consolidate console timer threads" msgstr "" #: i2p2www/blog/2017/02/27/0.9.29-Release.rst:68 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:11 msgid "0.9.29 Windows installer fix" msgstr "" #: i2p2www/blog/2017/03/04/0.9.29-Windows-Installer-Fix.rst:18 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:11 msgid "0.9.30 with Jetty 9" msgstr "" #: i2p2www/blog/2017/05/03/0.9.30-Release.rst:18 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:23 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:29 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:35 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:41 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:46 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 "注意：在非Android的ARM平台，例如树莓派，文件块数据库将在重启时升级，这也许会花上数分钟。\n请保持耐心。" #: i2p2www/blog/2017/05/03/0.9.30-Release.rst:61 msgid "Jetty 9, Tomcat 8" msgstr "" #: i2p2www/blog/2017/05/03/0.9.30-Release.rst:62 msgid "Stretch / Zesty support" msgstr "" #: i2p2www/blog/2017/05/03/0.9.30-Release.rst:63 msgid "Migration support for DSA-SHA1 hidden services" msgstr "" #: i2p2www/blog/2017/05/03/0.9.30-Release.rst:64 msgid "ARM (non-Android) router signature type migration" msgstr "" #: i2p2www/blog/2017/05/03/0.9.30-Release.rst:65 msgid "ARM (non-Android) blockfile format migration" msgstr "" #: i2p2www/blog/2017/05/03/0.9.30-Release.rst:66 msgid "Introducer expiration (proposal 133)" msgstr "" #: i2p2www/blog/2017/05/03/0.9.30-Release.rst:71 msgid "Fix disappearing i2psnark start button" msgstr "" #: i2p2www/blog/2017/05/03/0.9.30-Release.rst:72 msgid "Fix saving of libjcpuid.jnilib file on Macs" msgstr "" #: i2p2www/blog/2017/05/03/0.9.30-Release.rst:73 msgid "Fix fallback to 'none' architecture for jbigi" msgstr "" #: i2p2www/blog/2017/05/03/0.9.30-Release.rst:74 msgid "Fixes for multiple destinations in SusiDNS" msgstr "" #: i2p2www/blog/2017/05/03/0.9.30-Release.rst:75 msgid "Fix config directory location in Gentoo" msgstr "" #: i2p2www/blog/2017/05/03/0.9.30-Release.rst:76 msgid "Fix rapid firewalled/not-firewalled transitions" msgstr "" #: i2p2www/blog/2017/05/03/0.9.30-Release.rst:77 msgid "Fix startup crash on very old Android platforms" msgstr "" #: i2p2www/blog/2017/05/03/0.9.30-Release.rst:78 msgid "Fixes for advanced authentication strings in i2ptunnel" msgstr "" #: i2p2www/blog/2017/05/03/0.9.30-Release.rst:79 msgid "Fix exception caused by corrupt stored i2psnark DHT data" msgstr "" #: i2p2www/blog/2017/05/03/0.9.30-Release.rst:80 msgid "Speed up writes of i2psnark files at shutdown" msgstr "" #: i2p2www/blog/2017/05/03/0.9.30-Release.rst:85 msgid "Recognize AMD Ryzen processor" msgstr "" #: i2p2www/blog/2017/05/03/0.9.30-Release.rst:86 msgid "Support for new i2psnark-rpc remote plugin" msgstr "" #: i2p2www/blog/2017/05/03/0.9.30-Release.rst:87 msgid "Build addressbook as a jar, not a webapp" msgstr "" #: i2p2www/blog/2017/05/03/0.9.30-Release.rst:88 msgid "Support client registration in app context" msgstr "" #: i2p2www/blog/2017/05/03/0.9.30-Release.rst:89 msgid "Add support for i2psnark-rpc plugin" msgstr "" #: i2p2www/blog/2017/05/03/0.9.30-Release.rst:90 msgid "Adjust thresholds for probabalistic throttling on slow platforms" msgstr "" #: i2p2www/blog/2017/05/03/0.9.30-Release.rst:91 msgid "Add reset() to I2PSocket API" msgstr "" #: i2p2www/blog/2017/05/03/0.9.30-Release.rst:92 msgid "Add date parameter to subscription authentication strings" msgstr "" #: i2p2www/blog/2017/05/03/0.9.30-Release.rst:93 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:11 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:13 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:20 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:29 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:38 msgid "" "MOAR speed!\n" "===========" msgstr "" #: i2p2www/blog/2017/06/01/Summer-Dev-2017-MOAR-Speed.rst:43 msgid "Our development programme this year will have four components:" msgstr "" #: i2p2www/blog/2017/06/01/Summer-Dev-2017-MOAR-Speed.rst:47 msgid "" "Measure\n" "-------" msgstr "" #: i2p2www/blog/2017/06/01/Summer-Dev-2017-MOAR-Speed.rst:52 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:61 msgid "" "Optimise\n" "--------" msgstr "" #: i2p2www/blog/2017/06/01/Summer-Dev-2017-MOAR-Speed.rst:66 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:72 msgid "Cryptographic primitives" msgstr "" #: i2p2www/blog/2017/06/01/Summer-Dev-2017-MOAR-Speed.rst:73 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:74 msgid "Peer profiling" msgstr "" #: i2p2www/blog/2017/06/01/Summer-Dev-2017-MOAR-Speed.rst:75 msgid "Tunnel path selection" msgstr "" #: i2p2www/blog/2017/06/01/Summer-Dev-2017-MOAR-Speed.rst:81 msgid "" "Advance\n" "-------" msgstr "" #: i2p2www/blog/2017/06/01/Summer-Dev-2017-MOAR-Speed.rst:86 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:101 msgid "" "Research\n" "--------" msgstr "" #: i2p2www/blog/2017/06/01/Summer-Dev-2017-MOAR-Speed.rst:106 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:120 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:142 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:11 msgid "0.9.31 with Console Updates" msgstr "" #: i2p2www/blog/2017/08/07/0.9.31-Release.rst:18 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:37 msgid "Console updates" msgstr "" #: i2p2www/blog/2017/08/07/0.9.31-Release.rst:38 msgid "i2psnark ratings and comments" msgstr "" #: i2p2www/blog/2017/08/07/0.9.31-Release.rst:44 msgid "Fix compile error with Jetty 9.2.22" msgstr "" #: i2p2www/blog/2017/08/07/0.9.31-Release.rst:45 msgid "Preserve CRT parameters for RSA private keys" msgstr "" #: i2p2www/blog/2017/08/07/0.9.31-Release.rst:46 msgid "Fix AES NPE on 4-core Rasp. Pi" msgstr "" #: i2p2www/blog/2017/08/07/0.9.31-Release.rst:47 #: i2p2www/blog/2019/01/22/0.9.38-Release.rst:48 msgid "Fix NPE in GeoIP" msgstr "" #: i2p2www/blog/2017/08/07/0.9.31-Release.rst:48 msgid "Fix bencoding for scrape response in zzzot plugin" msgstr "" #: i2p2www/blog/2017/08/07/0.9.31-Release.rst:49 msgid "Fix display of default SusiDNS subscription" msgstr "" #: i2p2www/blog/2017/08/07/0.9.31-Release.rst:50 msgid "Fix Debian apparmor profile" msgstr "" #: i2p2www/blog/2017/08/07/0.9.31-Release.rst:51 msgid "Improve handling of read-only i2psnark directory" msgstr "" #: i2p2www/blog/2017/08/07/0.9.31-Release.rst:57 msgid "Hostname lookup caching improvements" msgstr "" #: i2p2www/blog/2017/08/07/0.9.31-Release.rst:58 msgid "Move blockfile support from i2p.jar to addressbook.jar" msgstr "" #: i2p2www/blog/2017/08/07/0.9.31-Release.rst:59 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:11 msgid "0.9.32 with Console Updates" msgstr "" #: i2p2www/blog/2017/11/07/0.9.32-Release.rst:18 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包含若干路由控制台和有关web应用（地址簿，i2psnark和Susimail）的修复。\n我们亦同时修改了处理用于发布路由信息的配置主机名的方式，以消除一些通过DNS的网络穷举攻击。\n我们已经在控制台中加入了一些检查以抵御重绑定攻击。" #: i2p2www/blog/2017/11/07/0.9.32-Release.rst:34 msgid "Disallow hostnames in router addresses (proposal 141)" msgstr "" #: i2p2www/blog/2017/11/07/0.9.32-Release.rst:35 msgid "Validate Host header in console" msgstr "" #: i2p2www/blog/2017/11/07/0.9.32-Release.rst:40 msgid "Numerous console, i2psnark, susidns, and susimail UI fixes" msgstr "" #: i2p2www/blog/2017/11/07/0.9.32-Release.rst:41 msgid "Fix i2psnark issues with expanding sections in some browsers" msgstr "" #: i2p2www/blog/2017/11/07/0.9.32-Release.rst:42 msgid "Debian packaging fixes" msgstr "" #: i2p2www/blog/2017/11/07/0.9.32-Release.rst:47 msgid "New benchmarking framework" msgstr "" #: i2p2www/blog/2017/11/07/0.9.32-Release.rst:48 msgid "New Indonesian translation" msgstr "" #: i2p2www/blog/2018/01/30/0.9.33-Release.rst:2 msgid "0.9.33 Release" 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 "0.9.33包含大量的错误修复，包括i2psnark，i2p隧道，streaming和SusiMail。\n对于那些不能直接访问补种页面的用户，我们现在提供几种形式的代理用于补种。\n我们现在在隐藏服务管理器中默认设置了比率限制。\n对于高流量服务器，如有必要请浏览并调整限制。" #: 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 #: i2p2www/blog/2019/08/27/0.9.42-Release.rst:59 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 #: i2p2www/blog/2019/03/21/0.9.39-Release.rst:64 #: i2p2www/blog/2019/05/07/0.9.40-Release.rst:67 #: i2p2www/blog/2019/07/02/0.9.41-Release.rst:67 #: i2p2www/blog/2019/08/27/0.9.42-Release.rst:61 #: i2p2www/blog/2019/10/22/0.9.43-Release.rst:58 #: i2p2www/blog/2019/12/01/0.9.44-Release.rst:67 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:11 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:13 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:20 msgid "" "Priority: New crypto(graphy!)\n" "-----------------------------" msgstr "" #: i2p2www/blog/2018/02/11/high-level-roadmap.rst:25 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:41 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:50 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:55 msgid "" "Nice-to-have: Code reuse\n" "------------------------" msgstr "" #: i2p2www/blog/2018/02/11/high-level-roadmap.rst:60 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:76 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:85 msgid "" "Priority: Clearnet collaboration\n" "--------------------------------" msgstr "" #: i2p2www/blog/2018/02/11/high-level-roadmap.rst:90 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:100 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:111 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:123 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:128 msgid "" "Priority: Preparation for long-lived releases\n" "---------------------------------------------" msgstr "" #: i2p2www/blog/2018/02/11/high-level-roadmap.rst:133 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:141 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:148 msgid "" "Priority: Pluginization of current apps\n" "---------------------------------------" msgstr "" #: i2p2www/blog/2018/02/11/high-level-roadmap.rst:153 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:167 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:175 msgid "" "Nice-to-have: App improvements\n" "------------------------------" msgstr "" #: i2p2www/blog/2018/02/11/high-level-roadmap.rst:180 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:188 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:195 msgid "" "Priority: Susimail and I2P-Bote stabilisation\n" "---------------------------------------------" msgstr "" #: i2p2www/blog/2018/02/11/high-level-roadmap.rst:200 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:208 msgid "" "Nice-to-have: Ticket triage\n" "---------------------------" msgstr "" #: i2p2www/blog/2018/02/11/high-level-roadmap.rst:213 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:221 msgid "" "Priority: User support\n" "----------------------" msgstr "" #: i2p2www/blog/2018/02/11/high-level-roadmap.rst:226 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:233 msgid "" "We'd love your help!\n" "--------------------" msgstr "" #: i2p2www/blog/2018/02/11/high-level-roadmap.rst:238 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:243 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:11 msgid "Trip report about the I2P meetup at BSidesNYC." msgstr "" #: i2p2www/blog/2018/04/10/0.9.34-Release.rst:2 msgid "0.9.34 Release" 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包含大量漏洞修复！" #: 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:61 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:62 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:2 msgid "0.9.35 Release" msgstr "" #: i2p2www/blog/2018/06/26/0.9.35-Release.rst:9 msgid "0.9.35 with SusiMail folders and SSL Wizard" msgstr "0.9.35，SusiMail 文件夹及 SSL 向导" #: i2p2www/blog/2018/06/26/0.9.35-Release.rst:16 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 "0.9.35 在Susimail中加入了文件夹的支持，以及在您的隐藏服务页面用于建立HTTPS的新SSL向导。\n我们如同往常一样收集错误修复，尤其是在Susimail中。" #: i2p2www/blog/2018/06/26/0.9.35-Release.rst:21 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 "我们正在为0.9.36努力，包括新的OSX安装包以及更快、更安全的被称为NTCP2传输协议。" #: i2p2www/blog/2018/06/26/0.9.35-Release.rst:25 msgid "" "I2P will be at HOPE in New York City, July 20-22. Find us and say hello!" msgstr "7月20到22号 I2P 将在纽约市HOPE。欢迎拜访并打招呼！" #: i2p2www/blog/2018/06/26/0.9.35-Release.rst:39 msgid "New Hidden Service SSL Wizard" msgstr "" #: i2p2www/blog/2018/06/26/0.9.35-Release.rst:40 msgid "SusiMail support for Folders, Drafts, background sending" msgstr "" #: i2p2www/blog/2018/06/26/0.9.35-Release.rst:46 msgid "Console: Fix changes to wrong tunnel on /configtunnels" msgstr "" #: i2p2www/blog/2018/06/26/0.9.35-Release.rst:47 msgid "CPUID: Fix TBM detection" msgstr "" #: i2p2www/blog/2018/06/26/0.9.35-Release.rst:48 msgid "" "i2psnark: Fix torrents ignoring priority settings when autostart enabled" msgstr "" #: i2p2www/blog/2018/06/26/0.9.35-Release.rst:49 msgid "i2ptunnel: Retry accept after server socket closed" msgstr "" #: i2p2www/blog/2018/06/26/0.9.35-Release.rst:50 msgid "NTCP: Fix bug causing initial latency for outbound connections" msgstr "" #: i2p2www/blog/2018/06/26/0.9.35-Release.rst:51 msgid "SusiMail: Include attachments in forwarded mail" msgstr "" #: i2p2www/blog/2018/06/26/0.9.35-Release.rst:52 msgid "SusiMail: Many other fixes" msgstr "" #: i2p2www/blog/2018/06/26/0.9.35-Release.rst:53 msgid "Tunnels: Prevent zero-hop even when no active peers" msgstr "" #: i2p2www/blog/2018/06/26/0.9.35-Release.rst:58 msgid "Add support for notes in Addressbook" msgstr "" #: i2p2www/blog/2018/06/26/0.9.35-Release.rst:59 msgid "Rewrite and new translations for eepsite help page (new installs only)" msgstr "" #: i2p2www/blog/2018/06/26/0.9.35-Release.rst:60 msgid "DNSoverHTTPS (disabled by default)" msgstr "" #: i2p2www/blog/2018/06/26/0.9.35-Release.rst:63 msgid "NTCP refactoring in prep for NTCP2" msgstr "" #: i2p2www/blog/2018/06/26/0.9.35-Release.rst:64 msgid "Move SusiMail logging to router logs" msgstr "" #: i2p2www/blog/2018/06/26/0.9.35-Release.rst:65 msgid "SusiMail BCC-to-self feature replaced with Sent folder" msgstr "" #: i2p2www/blog/2018/06/26/0.9.35-Release.rst:66 msgid "Fix eepget handling of response line with no status text" msgstr "" #: i2p2www/blog/2018/06/26/0.9.35-Release.rst:67 msgid "i2psnark UI cleanups" msgstr "" #: i2p2www/blog/2018/06/26/0.9.35-Release.rst:68 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:11 msgid "I2P's new transport protocol implementation details" msgstr "" #: i2p2www/blog/2018/08/20/NTCP2.rst:13 msgid "`Source article`_ by orignal at habr.com" msgstr "" #: i2p2www/blog/2018/08/20/NTCP2.rst:20 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:37 msgid "Full specification of NTCP2 protocol can be `found here`_." msgstr "" #: i2p2www/blog/2018/08/20/NTCP2.rst:43 msgid "" "New crypto\n" "----------" msgstr "" #: i2p2www/blog/2018/08/20/NTCP2.rst:48 msgid "" "NTCP2 requires adding the next cryptographic algorithms to an I2P " "implementation:" msgstr "" #: i2p2www/blog/2018/08/20/NTCP2.rst:59 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:66 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:77 msgid "" "RouterInfo changes\n" "------------------" msgstr "" #: i2p2www/blog/2018/08/20/NTCP2.rst:82 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:93 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:100 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:106 msgid "" "Establishing a connection\n" "-------------------------" msgstr "" #: i2p2www/blog/2018/08/20/NTCP2.rst:111 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:118 msgid "Three messages are being sent to establish a connection:" msgstr "" #: i2p2www/blog/2018/08/20/NTCP2.rst:131 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:138 msgid "" "MixKey function looks something like this in the C++ implementation of I2P:" msgstr "" #: i2p2www/blog/2018/08/20/NTCP2.rst:159 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:170 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:176 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:183 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:194 msgid "" "Generation of data transfer keys\n" "--------------------------------" msgstr "" #: i2p2www/blog/2018/08/20/NTCP2.rst:199 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 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:207 msgid "" "Code used to generate keys looks like this in the C++ implementation of I2P:" msgstr "" #: i2p2www/blog/2018/08/20/NTCP2.rst:246 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:252 msgid "" "Data transferring\n" "-----------------" msgstr "" #: i2p2www/blog/2018/08/20/NTCP2.rst:257 msgid "Data is transferred in frames, each frame has 3 parts:" msgstr "" #: i2p2www/blog/2018/08/20/NTCP2.rst:261 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:267 msgid "Maximum length of data transferred in one frame is 65519 bytes." msgstr "" #: i2p2www/blog/2018/08/20/NTCP2.rst:271 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:276 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:283 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 and it must be the last block." msgstr "" #: i2p2www/blog/2018/08/20/NTCP2.rst:289 msgid "Those are other data blocks used in the current NTCP2 implementation:" msgstr "" #: i2p2www/blog/2018/08/20/NTCP2.rst:293 msgid "" "- RouterInfo — usually contains Bob's RouterInfo after the connection has been established, but it can also contain RouterInfo of a random node for the purpose of speeding up floodfills (there is a flags field for that case). \n" "- Termination — is used when a host explicitly terminates a connection and specifies a reason for that.\n" "- DateTime — a current time in seconds." msgstr "" #: i2p2www/blog/2018/08/20/NTCP2.rst:300 msgid "" "Summary\n" "-------" msgstr "" #: i2p2www/blog/2018/08/20/NTCP2.rst:305 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:2 msgid "0.9.36 Release" msgstr "" #: i2p2www/blog/2018/08/23/0.9.36-Release.rst:10 msgid "0.9.36 with NTCP2 and bug fixes" msgstr "0.9.36，NTCP2 及缺陷修复" #: 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 #: i2p2www/blog/2019/03/21/0.9.39-Release.rst:60 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 #: i2p2www/blog/2018/10/04/0.9.37-Release.rst:47 msgid "Update GeoIPv6 data (new installs and PPA only)" msgstr "" #: i2p2www/blog/2018/10/04/0.9.37-Release.rst:2 msgid "0.9.37 Release" msgstr "" #: i2p2www/blog/2018/10/04/0.9.37-Release.rst:9 msgid "0.9.37 with NTCP2 enabled" msgstr "0.9.37，NTCP2 已启用" #: i2p2www/blog/2018/10/04/0.9.37-Release.rst:16 msgid "" "0.9.37 enables the faster, more secure transport protocol called NTCP2." msgstr "" #: i2p2www/blog/2018/10/04/0.9.37-Release.rst:30 msgid "Enable NTCP2 by default" msgstr "" #: i2p2www/blog/2018/10/04/0.9.37-Release.rst:37 msgid "NTCP2 fixes" msgstr "" #: i2p2www/blog/2018/10/04/0.9.37-Release.rst:38 msgid "Workaround for build hang with Tomcat 8.5.33/34" msgstr "" #: i2p2www/blog/2018/10/04/0.9.37-Release.rst:44 msgid "Progress on reproducible builds" msgstr "" #: i2p2www/blog/2018/10/04/0.9.37-Release.rst:45 msgid "Additional Arabic translations" msgstr "" #: i2p2www/blog/2018/10/23/application-development-basics.rst:1 msgid "" "=========================================================\n" "Developing privacy-aware applications with Python and I2P\n" "=========================================================" msgstr "" #: i2p2www/blog/2018/10/23/application-development-basics.rst:11 msgid "Basic concepts of I2P application development with Python" msgstr "" #: i2p2www/blog/2018/10/23/application-development-basics.rst:16 msgid "i2plib" msgstr "" #: i2p2www/blog/2018/10/23/application-development-basics.rst:18 msgid "" "`Invisible Internet Project`_ (I2P) provides a framework for\n" "developing privacy-aware applications. It is a virtual network working on top of\n" "the regular Internet, in which hosts can exchange data without disclosing their\n" "\"real\" IP addresses. Connections inside I2P network are established between \n" "virtual addresses called *I2P destinations*. It's possible to have as many\n" "of destinations as one needs, even use a new destination for each connection,\n" "they don't disclose any information about the real IP address to the other\n" "side." msgstr "" #: i2p2www/blog/2018/10/23/application-development-basics.rst:31 msgid "" "This article describes basic concepts one needs to know when developing I2P\n" "applications. Code samples are written in Python with the use of built-in\n" "asynchronous framework asyncio." msgstr "" #: i2p2www/blog/2018/10/23/application-development-basics.rst:37 msgid "" "Enabling SAM API and i2plib installation\n" "========================================" msgstr "" #: i2p2www/blog/2018/10/23/application-development-basics.rst:42 msgid "" "I2P provides many different APIs to the client applications. Regular\n" "client-server apps can use I2PTunnel, HTTP and Socks proxies, Java applications \n" "usually use I2CP. For developing with other languages, like Python, the best \n" "option is `SAM`_. SAM is disabled by \n" "default in the original Java client implementation, so we need to enable it. \n" "Go to Router Console, page \"I2P internals\" -> \"Clients\". Check \"Run at Startup\" \n" "and press \"Start\", then \"Save Client Configuration\"." msgstr "" #: i2p2www/blog/2018/10/23/application-development-basics.rst:57 msgid "Enable SAM API" msgstr "" #: i2p2www/blog/2018/10/23/application-development-basics.rst:59 msgid "`C++ implementation i2pd`_ has SAM enabled by default." msgstr "" #: i2p2www/blog/2018/10/23/application-development-basics.rst:65 msgid "" "I've developed a handy Python library for SAM API called\n" "`i2plib`_. You can install it with pip or\n" "manually download the source code from GitHub." msgstr "" #: i2p2www/blog/2018/10/23/application-development-basics.rst:79 msgid "" "This library works with the Python's built-in `asynchronous framework asyncio`_,\n" "so please note that code samples are taken from async functions (coroutines)\n" "which are running inside the event loop. Additional examples of i2plib usage can\n" "be found in the `source code repository`_." msgstr "" #: i2p2www/blog/2018/10/23/application-development-basics.rst:89 msgid "" "I2P Destination and session creation\n" "====================================" msgstr "" #: i2p2www/blog/2018/10/23/application-development-basics.rst:94 msgid "" "I2P destination is literally a set of encryption and cryptographic signature\n" "keys. Public keys from this set are published to the I2P network and are used to\n" "make connections instead of IP addresses." msgstr "" #: i2p2www/blog/2018/10/23/application-development-basics.rst:100 msgid "This is how you create `i2plib.Destination`_:" msgstr "" #: i2p2www/blog/2018/10/23/application-development-basics.rst:112 msgid "" "base32 address is a hash which is used by other peers to discover your full\n" "Destination in the network. If you plan to use this destination as a permanent\n" "address in your program, save the binary data from *dest.private\\_key.data* \n" "to a local file." msgstr "" #: i2p2www/blog/2018/10/23/application-development-basics.rst:119 msgid "" "Now you can create a SAM session, which literally means to make the Destination\n" "online in I2P:" msgstr "" #: i2p2www/blog/2018/10/23/application-development-basics.rst:130 msgid "" "Important note here: Destination will remain online while *session\\_writer* socket\n" "is kept open. If you wish to switch it off, you can call *session\\_writer.close()*." msgstr "" #: i2p2www/blog/2018/10/23/application-development-basics.rst:135 msgid "" "Making outgoing connections\n" "===========================" msgstr "" #: i2p2www/blog/2018/10/23/application-development-basics.rst:140 msgid "" "Now when the Destination is online, you can use it to connect to other peers.\n" "For example, this is how you connect to\n" "\"udhdrtrcetjm5sxzskjyr5ztpeszydbh4dpl3pl4utgqqw2v4jna.b32.i2p\", send HTTP GET\n" "request and read the response (it is \"i2p-projekt.i2p\" web server):" msgstr "" #: i2p2www/blog/2018/10/23/application-development-basics.rst:166 msgid "" "Accepting incoming connections\n" "==============================" msgstr "" #: i2p2www/blog/2018/10/23/application-development-basics.rst:171 msgid "" "While making outgoing connections is trivial, when you accept connections there\n" "is one important detail. After a new client is connected, SAM API sends an ASCII\n" "string with base64-encoded client's Destination to the socket. Since Destination \n" "and data can come in one chunk, you should be aware of it." msgstr "" #: i2p2www/blog/2018/10/23/application-development-basics.rst:178 msgid "" "This is how a simple PING-PONG server looks like. It accepts incoming\n" "connection, saves client's Destination to a *remote\\_destination* variable and\n" "sends back \"PONG\" string:" msgstr "" #: i2p2www/blog/2018/10/23/application-development-basics.rst:203 msgid "" "More info\n" "=========" msgstr "" #: i2p2www/blog/2018/10/23/application-development-basics.rst:208 msgid "" "This article describes the usage of a TCP-like Streaming protocol. SAM API also\n" "provides a UDP-like protocol to send and receive datagrams. This feature will\n" "be added to i2plib later." msgstr "" #: i2p2www/blog/2018/10/23/application-development-basics.rst:214 msgid "" "This is just a basic information, but it's enough to start your own project with\n" "the use of I2P. Invisible Internet is a great tool to develop all kinds of\n" "privacy-aware applications. There are no design constraints by the network,\n" "those applications can be client-server as well as P2P." msgstr "" #: i2p2www/blog/2019/01/22/0.9.38-Release.rst:2 msgid "0.9.38 Release" msgstr "" #: i2p2www/blog/2019/01/22/0.9.38-Release.rst:9 msgid "0.9.38 with new setup wizard" msgstr "0.9.38 含有全新安装向导" #: i2p2www/blog/2019/01/22/0.9.38-Release.rst:16 msgid "" "0.9.38 includes a new first-install wizard with a bandwidth tester.\n" "We've added support for the latest GeoIP database format.\n" "There's a new Firefox profile installer and a new, native Mac OSX installer on our website.\n" "Work continues on supporting the new \"LS2\" netdb format." msgstr "0.9.38 含有一个若为首次安装则会启动的向导，还有一个带宽测试器。我们已经支持最新的GeoIP数据库格式。我们的网站上有一个新的配置Firefox的安装包和一个新的本地Mac OSX安装包。我们继续努力支持新的“LS2”网络数据库格式。" #: i2p2www/blog/2019/01/22/0.9.38-Release.rst:23 msgid "" "This release also contains plenty of bug fixes, including several issues " "with susimail attachments, and a fix for IPv6-only routers." msgstr "这次发布还有大量的bug修复，包括修复了susimail附件的一些问题，还含有针对纯IPv6路由器的一个修复。" #: i2p2www/blog/2019/01/22/0.9.38-Release.rst:37 msgid "New setup wizard with bandwidth testing" msgstr "" #: i2p2www/blog/2019/01/22/0.9.38-Release.rst:38 msgid "New beta OSX installer" msgstr "" #: i2p2www/blog/2019/01/22/0.9.38-Release.rst:39 msgid "New Firefox profile installer" msgstr "" #: i2p2www/blog/2019/01/22/0.9.38-Release.rst:40 msgid "Preliminary floodfill support for LS2" msgstr "" #: i2p2www/blog/2019/01/22/0.9.38-Release.rst:41 msgid "Sybil tool background analysis" msgstr "" #: i2p2www/blog/2019/01/22/0.9.38-Release.rst:42 msgid "Add support for Maxmind GeoLite2 GeoIP format" msgstr "" #: i2p2www/blog/2019/01/22/0.9.38-Release.rst:43 msgid "Switch JSON lib to json-simple, add Debian dependency" msgstr "" #: i2p2www/blog/2019/01/22/0.9.38-Release.rst:49 msgid "Fix RouterInfo publishing for IPv6-only routers" msgstr "" #: i2p2www/blog/2019/01/22/0.9.38-Release.rst:50 msgid "I2CP error propagation fixes" msgstr "" #: i2p2www/blog/2019/01/22/0.9.38-Release.rst:51 msgid "Fix rare NetDb deadlock" msgstr "" #: i2p2www/blog/2019/01/22/0.9.38-Release.rst:52 msgid "Fix several bugs with susimail attachments" msgstr "" #: i2p2www/blog/2019/01/22/0.9.38-Release.rst:53 msgid "AppArmor fixes" msgstr "" #: i2p2www/blog/2019/01/22/0.9.38-Release.rst:58 msgid "Refactoring to support LS2" msgstr "" #: i2p2www/blog/2019/01/22/0.9.38-Release.rst:59 msgid "Preliminary LS2 support in I2CP" msgstr "" #: i2p2www/blog/2019/01/22/0.9.38-Release.rst:60 msgid "ShellCommand and UrlLauncher refactoring for security" msgstr "" #: i2p2www/blog/2019/01/22/0.9.38-Release.rst:61 msgid "Split /peers page into tabs" msgstr "" #: i2p2www/blog/2019/01/22/0.9.38-Release.rst:62 msgid "New background for light theme" msgstr "" #: i2p2www/blog/2019/02/14/i2p-lab.rst:2 msgid "I2P Laboratory" msgstr "I2P 实验室" #: i2p2www/blog/2019/02/14/i2p-lab.rst:9 msgid "I2P Laboratory - Home For Experimental Projects" msgstr "" #: i2p2www/blog/2019/02/14/i2p-lab.rst:12 msgid "Hello everyone," msgstr "" #: i2p2www/blog/2019/02/14/i2p-lab.rst:16 msgid "" "There are many projects in the I2P world that we are excited about, but not " "all of them are ready for prime-time. We decided to create a place where we" " can make those available for anyone interested in trying them out, that " "will serve as proving grounds for projects that may one day become official " "I2P products. This place is the `I2P Laboratory`_." msgstr "" #: i2p2www/blog/2019/02/14/i2p-lab.rst:22 msgid "" "In the lab we will be offering downoads ready for you to try. Keep in mind " "that they are not going to be \"release\" quality, and some may not even be " "\"beta\" quality. We do not offer official support for them. Any of the " "lab projects may get discontinued at any time." msgstr "" #: i2p2www/blog/2019/02/14/i2p-lab.rst:26 msgid "" "If you are feeling adventurous we invite you to try our ideas. We welcome " "your feedback at the `I2P Lab Forum`_." msgstr "" #: i2p2www/blog/2019/03/21/0.9.39-Release.rst:2 msgid "0.9.39 Release" msgstr "" #: i2p2www/blog/2019/03/21/0.9.39-Release.rst:9 msgid "0.9.39 with performance improvements" msgstr "0.9.39 带有性能提升" #: i2p2www/blog/2019/03/21/0.9.39-Release.rst:16 msgid "" "0.9.39 includes extensive changes for the new network database types (proposal 123).\n" "We've bundled the i2pcontrol plugin as a webapp to support development of RPC applications.\n" "There are numerous performance improvements and bug fixes." msgstr "0.9.39 包含了针对新网络库格式的大量更新(proposal 123).\n我们将 i2pcontrol 插件作为一个 webapp 打包进来从而支持 RPC 应用的开发.\n另外还有众多的性能提升和bug修复." #: i2p2www/blog/2019/03/21/0.9.39-Release.rst:22 msgid "" "We've removed the midnight and classic themes to reduce the maintenance burden;\n" "previous users of those themes will now see the dark or light theme.\n" "There's also new home page icons, a first step in updating the console." msgstr "我们移除了午夜和经典主题从而减轻维护压力.\n之前使用这些主题的用户现在将会看到暗或者亮色调主题.\n以及主页有了新的的图标, 控制台更新的第一步." #: i2p2www/blog/2019/03/21/0.9.39-Release.rst:38 msgid "I2PControl RPC plugin bundled as a webapp" msgstr "" #: i2p2www/blog/2019/03/21/0.9.39-Release.rst:39 msgid "Encrypted LS2 support in floodfills (proposal 123)" msgstr "" #: i2p2www/blog/2019/03/21/0.9.39-Release.rst:40 msgid "New option to disable NTCP1" msgstr "" #: i2p2www/blog/2019/03/21/0.9.39-Release.rst:41 msgid "Add offline key support in streaming" msgstr "" #: i2p2www/blog/2019/03/21/0.9.39-Release.rst:46 msgid "Numerous LS2 fixes (proposal 123)" msgstr "" #: i2p2www/blog/2019/03/21/0.9.39-Release.rst:47 msgid "Fixes for NTCP only (SSU disabled)" msgstr "" #: i2p2www/blog/2019/03/21/0.9.39-Release.rst:48 msgid "Proxy fixes for websockets" msgstr "" #: i2p2www/blog/2019/03/21/0.9.39-Release.rst:49 msgid "Streaming fix for sending expired messages" msgstr "" #: i2p2www/blog/2019/03/21/0.9.39-Release.rst:50 msgid "SSU RTO/RTT calculation fixes" msgstr "" #: i2p2www/blog/2019/03/21/0.9.39-Release.rst:51 msgid "UPnP startup fixes" msgstr "" #: i2p2www/blog/2019/03/21/0.9.39-Release.rst:52 msgid "Fix connectivity test at startup" msgstr "" #: i2p2www/blog/2019/03/21/0.9.39-Release.rst:57 msgid "Remove classic and midnight themes" msgstr "" #: i2p2www/blog/2019/03/21/0.9.39-Release.rst:58 msgid "New console home page icons" msgstr "" #: i2p2www/blog/2019/03/21/0.9.39-Release.rst:59 msgid "Caching of outproxy selection" msgstr "" #: i2p2www/blog/2019/03/21/0.9.39-Release.rst:61 msgid "Faster startup for i2ptunnel" msgstr "" #: i2p2www/blog/2019/05/07/0.9.40-Release.rst:2 msgid "0.9.40 Release" msgstr "" #: i2p2www/blog/2019/05/07/0.9.40-Release.rst:9 msgid "0.9.40 with new icons" msgstr "0.9.40 有新的图标" #: i2p2www/blog/2019/05/07/0.9.40-Release.rst:16 msgid "" "0.9.40 includes support for the new encrypted leaseset format.\n" "We disabled the old NTCP 1 transport protocol.\n" "There's a new SusiDNS import feature, and a new scripted filtering mechanism for incoming connections." msgstr "0.9.40 支持新的租契集格式。\n我们已禁用旧的 NTCP 1 传输协议。\n有一个新的 SusiDNS 导入功能，以及一个用于传入连接的新的脚本化过滤机制。" #: i2p2www/blog/2019/05/07/0.9.40-Release.rst:22 msgid "" "We've made a lot of improvements to the OSX native installer, and we've updated the IzPack installer as well.\n" "The work continues on refreshing the console with new icons.\n" "As usual, we've fixed lots of bugs as well!" msgstr "" #: i2p2www/blog/2019/05/07/0.9.40-Release.rst:38 msgid "Change installer to IzPack 5.1.3" msgstr "" #: i2p2www/blog/2019/05/07/0.9.40-Release.rst:39 msgid "Change Windows installer from launch4j to izpack2exe" msgstr "" #: i2p2www/blog/2019/05/07/0.9.40-Release.rst:40 msgid "Sign Windows installer" msgstr "" #: i2p2www/blog/2019/05/07/0.9.40-Release.rst:41 msgid "Console, SusiDNS: New icons" msgstr "" #: i2p2www/blog/2019/05/07/0.9.40-Release.rst:42 msgid "Disable NTCP 1" msgstr "" #: i2p2www/blog/2019/05/07/0.9.40-Release.rst:43 msgid "New SusiDNS import feature" msgstr "" #: i2p2www/blog/2019/05/07/0.9.40-Release.rst:44 msgid "Add UI and router support for Encrypted LS2 (proposal 123)" msgstr "" #: i2p2www/blog/2019/05/07/0.9.40-Release.rst:45 msgid "Add support for new base 32 format for Encrypted LS2" msgstr "" #: i2p2www/blog/2019/05/07/0.9.40-Release.rst:46 msgid "New incoming connection filter for i2ptunnel" msgstr "" #: i2p2www/blog/2019/05/07/0.9.40-Release.rst:47 msgid "Add Red25519 signature type option for server tunnels" msgstr "" #: i2p2www/blog/2019/05/07/0.9.40-Release.rst:48 msgid "OSX: Theme selection, auto updater, upgrade to newer swift version" msgstr "" #: i2p2www/blog/2019/05/07/0.9.40-Release.rst:53 msgid "Several fixes for Android" msgstr "" #: i2p2www/blog/2019/05/07/0.9.40-Release.rst:54 msgid "Fixes for SSU disabled (NTCP only)" msgstr "" #: i2p2www/blog/2019/05/07/0.9.40-Release.rst:55 msgid "Fixes for encrypted LS2 (proposal 123)" msgstr "" #: i2p2www/blog/2019/05/07/0.9.40-Release.rst:56 msgid "Fix for rare 100% CPU in NTCP" msgstr "" #: i2p2www/blog/2019/05/07/0.9.40-Release.rst:57 msgid "Fixes for NTCP 1 disabled" msgstr "" #: i2p2www/blog/2019/05/07/0.9.40-Release.rst:62 msgid "New supported Docker image" msgstr "" #: i2p2www/blog/2019/05/07/0.9.40-Release.rst:63 msgid "Support for SAM 3.2 features in SAM libraries" msgstr "" #: i2p2www/blog/2019/05/07/0.9.40-Release.rst:64 msgid "Remove connect delay, profile, and I2CP options in i2ptunnel UI" msgstr "" #: i2p2www/blog/2019/05/25/help-bootstrap-bote.rst:2 msgid "How to volunteer by helping I2P-Bote bootstrap" msgstr "" #: i2p2www/blog/2019/05/25/help-bootstrap-bote.rst:8 msgid "Help Bootstrap I2P-Bote!" msgstr "" #: i2p2www/blog/2019/05/25/help-bootstrap-bote.rst:10 msgid "" "An easy way to help people message eachother privately is to run an\n" "I2P-Bote peer which can be used by new bote users to bootstrap their own\n" "I2P-Bote peers. Unfortunately, until now, the process of setting up an\n" "I2P-Bote bootstrap peer has been much more obscure than it should be.\n" "It's actually extremely simple!" msgstr "" #: i2p2www/blog/2019/05/25/help-bootstrap-bote.rst:18 msgid "" "::\n" "\n" " What is I2P-bote?\n" " I2P-bote is a private messaging system built on i2p, which has additional\n" " features to make it even more difficult to discern information about the\n" " messages that are transmitted. Because of this, it can be used to transmit\n" " private messages securely while tolerating high latency and not relying on\n" " a centralized relay to send messages when the sender goes offline. This is\n" " in contrast to almost every other popular private messaging system, which\n" " either require both parties to be online or rely on a semi-trusted service\n" " which transmits messages on behalf of senders who go offline.\n" "\n" " or, ELI5: It's used similarly to e-mail, but it suffers from none of e-mail's\n" " privacy defects." msgstr "" #: i2p2www/blog/2019/05/25/help-bootstrap-bote.rst:36 msgid "Step One: Install I2P-Bote" msgstr "" #: i2p2www/blog/2019/05/25/help-bootstrap-bote.rst:38 msgid "" "\n" "\n" "I2P-Bote is an i2p plugin, and installing it is very easy. The original\n" "instructions are available at the `bote eepSite,\n" "bote.i2p `__, but if you want to read them on\n" "the clearnet, these instructions come courtesy of bote.i2p:" msgstr "" #: i2p2www/blog/2019/05/25/help-bootstrap-bote.rst:47 msgid "" "\n" "\n" "1. Go to the plugin install form in your routerconsole:\n" " http://127.0.0.1:7657/configclients#plugin\n" "2. Paste in the URL http://bote.i2p/i2pbote.su3\n" "3. Click Install Plugin.\n" "4. Once installed, click SecureMail in the routerconsole sidebar or\n" " homepage, or go to http://127.0.0.1:7657/i2pbote/" msgstr "" #: i2p2www/blog/2019/05/25/help-bootstrap-bote.rst:58 msgid "Step Two: Get your I2P-Bote node's base64 address" msgstr "" #: i2p2www/blog/2019/05/25/help-bootstrap-bote.rst:60 msgid "" "\n" "\n" "This is the part where a person might get stuck, but fear not. While a\n" "little hard to find instructions, this is actually easy and there are\n" "several tools and options available to you, depending on what your\n" "circumstances are. For people who want to help run bootstrap nodes as\n" "volunteers, the best way is to retrieve the required information from\n" "the private key file used by the bote tunnel." msgstr "" #: i2p2www/blog/2019/05/25/help-bootstrap-bote.rst:71 msgid "Where are the keys?" msgstr "" #: i2p2www/blog/2019/05/25/help-bootstrap-bote.rst:73 msgid "" "\n" "\n" "I2P-Bote stores it's destination keys in a text file which, on Debian,\n" "is located at */var/lib/i2p/i2p-config/i2pbote/local_dest.key*. In\n" "non-Debian systems where i2p is installed by the user, the key will be\n" "in *$HOME/.i2p/i2pbote/local_dest.key*, and on Windows, the file will be\n" "in *C:\\\\ProgramData\\\\i2p\\\\i2pbote\\\\local_dest.key*." msgstr "" #: i2p2www/blog/2019/05/25/help-bootstrap-bote.rst:83 msgid "Method A: Convert the plain-text key to the base64 destination" msgstr "" #: i2p2www/blog/2019/05/25/help-bootstrap-bote.rst:85 msgid "" "\n" "\n" "In order to convert a plain-text key into a base64 destination, one\n" "needs to take the key and separate only the destination part from it. In\n" "order to do this properly, one must take the following steps:" msgstr "" #: i2p2www/blog/2019/05/25/help-bootstrap-bote.rst:93 msgid "" "\n" "\n" "1. First, take the full destination and decode it from i2p's base64\n" " character set into binary.\n" "2. Second, take bytes 386 and 387 and convert them to a single\n" " Big-Endian integer.\n" "3. Add the number you computed from the two bytes in step two to 387. This is\n" " the length of the base64 destination.\n" "4. Take that nummber of bytes from the front of the full destination to get\n" " the destination as a range of bytes.\n" "5. Convert back to a base64 representation using i2p's base64 character\n" " set." msgstr "" #: i2p2www/blog/2019/05/25/help-bootstrap-bote.rst:108 msgid "" "\n" "\n" "A number of applications and scripts exist to perform these steps for\n" "you. Here are some of them, but this is far from exhaustive:" msgstr "" #: i2p2www/blog/2019/05/25/help-bootstrap-bote.rst:115 msgid "" "\n" "\n" "- `the i2p.scripts collection of scripts(Mostly java and\n" " bash) `__\n" "- `my application for converting\n" " keys(Go) `__" msgstr "" #: i2p2www/blog/2019/05/25/help-bootstrap-bote.rst:124 msgid "" "\n" "\n" "These capabilities are also available in a number of I2P application\n" "development libraries." msgstr "" #: i2p2www/blog/2019/05/25/help-bootstrap-bote.rst:131 msgid "Shortcut:" msgstr "" #: i2p2www/blog/2019/05/25/help-bootstrap-bote.rst:133 msgid "" "\n" "\n" "Since the local destination of your bote node is a DSA destination, then\n" "it's quicker to just truncate the local_dest.key file to the first 516\n" "bytes. To do that easily, run this command when running I2P-Bote with\n" "I2P on Debian:" msgstr "" #: i2p2www/blog/2019/05/25/help-bootstrap-bote.rst:142 msgid "" "\n" "::\n" "\n" " sudo -u i2psvc head -c 516 /var/lib/i2p/i2p-config/i2pbote/local_dest.key" msgstr "" #: i2p2www/blog/2019/05/25/help-bootstrap-bote.rst:149 msgid "" "\n" "\n" "Or, if I2P is installed as your user:" msgstr "" #: i2p2www/blog/2019/05/25/help-bootstrap-bote.rst:155 msgid "" "\n" "::\n" "\n" " head -c 516 ~/.i2p/i2pbote/local_dest.key" msgstr "" #: i2p2www/blog/2019/05/25/help-bootstrap-bote.rst:162 msgid "Methon B: Do a lookup" msgstr "" #: i2p2www/blog/2019/05/25/help-bootstrap-bote.rst:164 msgid "" "\n" "\n" "If that seems like a bit too much work, it's possible for you to look up\n" "the base64 destination of your Bote connection by querying it's base32\n" "address using any of the available means for looking up a base32\n" "address. The base32 address of your Bote node is available on the\n" "\"Connection\" page under the bote plugin application, at\n" "`127.0.0.1:7657/i2pbote/network `__" msgstr "" #: i2p2www/blog/2019/05/25/help-bootstrap-bote.rst:175 msgid "Step Three: Contact Us!" msgstr "" #: i2p2www/blog/2019/05/25/help-bootstrap-bote.rst:177 msgid "" "\n" "\n" ".. _update-the-built-in-peerstxt-file-with-your-new-node:" msgstr "" #: i2p2www/blog/2019/05/25/help-bootstrap-bote.rst:183 msgid "Update the built-in-peers.txt file with your new node" msgstr "" #: i2p2www/blog/2019/05/25/help-bootstrap-bote.rst:185 msgid "" "\n" "\n" "Now that you've got the correct destination for your I2P-Bote node, the\n" "final step is to add yourself to the default peers list for `I2P-Bote\n" "here `__\n" "here. You can do this by forking the repository, adding yourself to the\n" "list with your name commented out, and your 516-char destination\n" "directly below it, like this:" msgstr "" #: i2p2www/blog/2019/05/25/help-bootstrap-bote.rst:196 msgid "" "\n" "\n" "::\n" "\n" " # idk\n" " QuabT3H5ljZyd-PXCQjvDzdfCec-2yv8E9i6N71I5WHAtSEZgazQMReYNhPWakqOEj8BbpRvnarpHqbQjoT6yJ5UObKv2hA2M4XrroJmydPV9CLJUCqgCqFfpG-bkSo0gEhB-GRCUaugcAgHxddmxmAsJVRj3UeABLPHLYiakVz3CG2iBMHLJpnC6H3g8TJivtqabPYOxmZGCI-P~R-s4vwN2st1lJyKDl~u7OG6M6Y~gNbIzIYeQyNggvnANL3t6cUqS4v0Vb~t~CCtXgfhuK5SK65Rtkt2Aid3s7mrR2hDxK3SIxmAsHpnQ6MA~z0Nus-VVcNYcbHUBNpOcTeKlncXsuFj8vZL3ssnepmr2DCB25091t9B6r5~681xGEeqeIwuMHDeyoXIP0mhEcy3aEB1jcchLBRLMs6NtFKPlioxz0~Vs13VaNNP~78bTjFje5ya20ahWlO0Md~x5P5lWLIKDgaqwNdIrijtZAcILn1h18tmABYauYZQtYGyLTOXAAAA" msgstr "" #: i2p2www/blog/2019/05/25/help-bootstrap-bote.rst:205 msgid "" "\n" "\n" "and submitting a pull request. That's all there is to it so help keep\n" "i2p alive, decentralized, and reliable." msgstr "" #: i2p2www/blog/2019/06/02/basic-tunnel-tutorial.rst:4 msgid "Basic i2ptunnel Setup" msgstr "" #: i2p2www/blog/2019/06/02/basic-tunnel-tutorial.rst:7 msgid "Basic I2P Tunnels Tutorial with Pictures" msgstr "" #: i2p2www/blog/2019/06/02/basic-tunnel-tutorial.rst:10 msgid "" "Although the Java I2P router comes pre-configured with a static web server,\n" "jetty, to provide the user's first eepSite, many require more sophisticated\n" "functionality from their web server and would rather create an eepSite with a\n" "different server. This is of course possible, and actually is really easy once\n" "you've done it one time." msgstr "" #: i2p2www/blog/2019/06/02/basic-tunnel-tutorial.rst:18 msgid "" "Although it is easy to do, there are a few things you should consider before\n" "doing it. You will want to remove identifying characteristics from your web\n" "server, like potentially identifying headers and default error pages that\n" "report the server/distro type. More information about threats to anonymity\n" "posed by improperly configured applications see:\n" "`Riseup here: `__,\n" "`Whonix Here: `__,\n" "`This blog article for some opsec fails: `__,\n" "`and the I2P applications page here `__.\n" "Although much of this information is expressed for Tor Onion Services, the same\n" "procedures and principles apply to hosting applications over I2P." msgstr "" #: i2p2www/blog/2019/06/02/basic-tunnel-tutorial.rst:32 msgid "Step One: Open the Tunnel Wizard" msgstr "" #: i2p2www/blog/2019/06/02/basic-tunnel-tutorial.rst:35 msgid "" "Go to the I2P web interface at 127.0.0.1:7657 and open the\n" "`Hidden Services Manager `__\\ (links to\n" "localhost). Click the button that says \"Tunnel Wizard\" to begin." msgstr "" #: i2p2www/blog/2019/06/02/basic-tunnel-tutorial.rst:45 msgid "Step Two: Select a Server Tunnel" msgstr "" #: i2p2www/blog/2019/06/02/basic-tunnel-tutorial.rst:48 msgid "" "The tunnel wizard is very simple. Since we're setting up an http *server*, all\n" "we need to do is select a *server* tunnel." msgstr "" #: i2p2www/blog/2019/06/02/basic-tunnel-tutorial.rst:57 msgid "Step Three: Select an HTTP Tunnel" msgstr "" #: i2p2www/blog/2019/06/02/basic-tunnel-tutorial.rst:60 msgid "" "An HTTP tunnel is the tunnel type that is optimized for hosting HTTP services.\n" "It has filtering and rate-limiting features enabled that are tailored\n" "specifically to that purpose. A standard tunnel may work as well, but if you\n" "select a atandard tunnel you'll need to take care of those security features\n" "yourself. A more in-depth dive into the HTTP Tunnel configuration is available\n" "in the next tutorial." msgstr "" #: i2p2www/blog/2019/06/02/basic-tunnel-tutorial.rst:73 msgid "Step Four: Give it a name and a description" msgstr "" #: i2p2www/blog/2019/06/02/basic-tunnel-tutorial.rst:76 msgid "" "For your own benefit and ability to remeber and distinguish the what you are\n" "using the tunnel for, give it a good nickname and description. If you need to\n" "come back and do more management later, then this is how you will identify the\n" "tunnel in the hidden services manager." msgstr "" #: i2p2www/blog/2019/06/02/basic-tunnel-tutorial.rst:87 msgid "Step Five: Configure the Host and Port" msgstr "" #: i2p2www/blog/2019/06/02/basic-tunnel-tutorial.rst:90 msgid "" "In this step, you point the web server at the TCP port where your web server is\n" "listening. Since most web servers listen on port 80 or port 8080, the example\n" "shows that. If you use alternate ports or virtual machines or containers to\n" "isolate your web services, you may need to adjust the host, port, or both." msgstr "" #: i2p2www/blog/2019/06/02/basic-tunnel-tutorial.rst:101 msgid "Step Six: Decide whether to start it automatically" msgstr "" #: i2p2www/blog/2019/06/02/basic-tunnel-tutorial.rst:104 msgid "I cannot think of a way to elaborate on this step." msgstr "" #: i2p2www/blog/2019/06/02/basic-tunnel-tutorial.rst:112 msgid "Step Seven: Review your settings" msgstr "" #: i2p2www/blog/2019/06/02/basic-tunnel-tutorial.rst:115 msgid "" "Finally, take a look at the settings you have selected. If you approve, save\n" "them. If you did not choose to start the tunnel automatically, go to the hidden\n" "services manager and start it manually when you wish to make your service\n" "available." msgstr "" #: i2p2www/blog/2019/06/02/basic-tunnel-tutorial.rst:126 msgid "Appendix: HTTP Server Customization Options" msgstr "" #: i2p2www/blog/2019/06/02/basic-tunnel-tutorial.rst:129 msgid "" "I2P provides a detailed panel for configuring the http server tunnel in custom\n" "ways. I'll finish this tutorial by walking through all of them. Eventually." msgstr "" #: i2p2www/blog/2019/06/02/mirroring-guide.rst:4 msgid "Offering an I2P Mirror" msgstr "" #: i2p2www/blog/2019/06/02/mirroring-guide.rst:7 msgid "How to offer your existing Web Site as an I2P eepSite" msgstr "" #: i2p2www/blog/2019/06/02/mirroring-guide.rst:10 msgid "" "This blog post is intended as a general guide to running a mirror of a clear-net\n" "service as an eepSite. It elaborates on the previous blog post about basic\n" "I2PTunnel tunnels." msgstr "" #: i2p2www/blog/2019/06/02/mirroring-guide.rst:16 msgid "" "Unfortunately, it's probably impossible to *completely* cover all possible cases\n" "of making an existing web site available as an eepSite, there's simply too\n" "diverse an array of server-side software, not to mention the in-practice\n" "peculiarities of any particular deployment of software. Instead, I'm going to\n" "try and convey, as specifically as possible, the general process preparing a\n" "service for deployment to the eepWeb or other hidden services." msgstr "" #: i2p2www/blog/2019/06/02/mirroring-guide.rst:25 msgid "" "Much of this guide will be treating the reader as a conversational participant,\n" "in particular If I really mean it I will address the reader directly(i.e. using\n" "\"you\" instead of \"one\") and I'll frequently head sections with questions I think\n" "the reader might be asking. This is, after all, a \"process\" that an\n" "administrator must consider themselves \"involved\" in just like hosting any other\n" "service." msgstr "" #: i2p2www/blog/2019/06/02/mirroring-guide.rst:34 msgid "DISCLAIMERS:" msgstr "" #: i2p2www/blog/2019/06/02/mirroring-guide.rst:37 msgid "" "While it would be wonderful, it's probably impossible for me to put specific\n" "instructions for every single kind of software that one might use to host web\n" "sites. As such, this tutorial requires some assumptions on the part of the\n" "writer and some critical thinking and common sense on the part of the reader.\n" "To be clear, **I have assumed that the person following this tutorial is**\n" "**already operating a clear-web service linkable to a real identity or**\n" "**organization** and thus is simply offering anonymous access and not\n" "anonymizing themselves." msgstr "" #: i2p2www/blog/2019/06/02/mirroring-guide.rst:48 msgid "" "Thus, **it makes no attempt whatsoever to anonymize** a connection from one\n" "server to another. If you want to run a new, un-linkable hidden service that\n" "makes server-to-server connections, additional steps will be required and will\n" "be covered in another tutorial." msgstr "" #: i2p2www/blog/2019/06/02/mirroring-guide.rst:55 msgid "" "That said: If you can be sure that a *brand new service* which is *not*\n" "*available to the clear-web* will never make a server-to-server connection and\n" "will not leak server metadata in responses to clients, then services configured\n" "in this way will be anonymous." msgstr "" #: i2p2www/blog/2019/06/02/mirroring-guide.rst:62 msgid "Process One: Prepare your Server" msgstr "" #: i2p2www/blog/2019/06/02/mirroring-guide.rst:65 msgid "Step one: Determine what software you are running" msgstr "" #: i2p2www/blog/2019/06/02/mirroring-guide.rst:68 msgid "" "In practice, your web service probably uses a number of things to enhance it's\n" "reliability and security. These things could be proxies, reverse proxies,\n" "containers, tunnels, Intrusion Detection Systems, rate-limiters, load balancers,\n" "among many other things. When you get started, you should go through your\n" "deployment and determine which software you are using, and what you are using it\n" "for." msgstr "" #: i2p2www/blog/2019/06/02/mirroring-guide.rst:77 msgid "As you examine your software, ask yourself these questions" msgstr "" #: i2p2www/blog/2019/06/02/mirroring-guide.rst:80 msgid "" "These questions should help you evaluate what parts of your software stack are\n" "relevant to your I2P eepSite." msgstr "" #: i2p2www/blog/2019/06/02/mirroring-guide.rst:85 msgid "Does this software work based on IP addresses?" msgstr "" #: i2p2www/blog/2019/06/02/mirroring-guide.rst:88 msgid "" "If you are using software which alters the behavior of traffic based on the IP\n" "address of the sender, these things will probably not work with I2P, or may work\n" "in complicated or unexpected ways. This is because the address will usually be\n" "the localhost, or at least the host where your I2P router is running. Software\n" "which sometimes does things based on IP addresses could be Fail2Ban, iptables,\n" "and similar applications." msgstr "" #: i2p2www/blog/2019/06/02/mirroring-guide.rst:97 msgid "Does this software work by \"Tagging\" traffic with additional metadata?" msgstr "" #: i2p2www/blog/2019/06/02/mirroring-guide.rst:100 msgid "" "Some software may be configured to add information to the traffic it handles.\n" "Obviously, if this information is identifying it should not be part of the chain\n" "of services that is exposed to the I2P network." msgstr "" #: i2p2www/blog/2019/06/02/mirroring-guide.rst:106 msgid "" "Does this software work by communicating with a remote resource? What " "triggers this behavior?" msgstr "" #: i2p2www/blog/2019/06/02/mirroring-guide.rst:109 msgid "" "Some software may also draw from remote resources, to find up-to-date rules and\n" "block lists which can be used to prevent attacks. Some of these might be useful\n" "as part of the service that is exposed to I2P, but you should make sure that the\n" "rules are applicable and that a rules update cannot be triggered as a result of\n" "a normal client request. This would create a server-to-server communication\n" "which could reveal the timing of an I2P communication to a third party." msgstr "" #: i2p2www/blog/2019/06/02/mirroring-guide.rst:118 msgid "" "Step two: Determine which port to Forward to I2P and Optionally locate your " "TLS certificate" msgstr "" #: i2p2www/blog/2019/06/02/mirroring-guide.rst:121 msgid "" "Now you've gathered all the information that you will require to forward your\n" "service to I2P. Once you've selected the point at which you would like to make\n" "your site available to I2P, you will need to note the port you wish to foward.\n" "In simple scenarios, this will probably just be port 80 or port 8080. In more\n" "sophisticated scenarios, this might be a reverse proxy or something like that.\n" "Make a note of the port." msgstr "" #: i2p2www/blog/2019/06/02/mirroring-guide.rst:130 msgid "Establishing a Common Identity for both the Clearnet and your eepSite" msgstr "" #: i2p2www/blog/2019/06/02/mirroring-guide.rst:133 msgid "" "Should you be a non-anonymous organization that wishes to provide enhanced\n" "privacy to your users by providing a hidden service, you may wish to establish\n" "a common identity between versions of your site. However, since we can't add\n" "`.i2p domains to clearnet TLS certificates `__, we have to do\n" "this in another way. To do this, **even if you are forwarding the HTTP port**\n" "**and not HTTPS**, make a note of the location of your TLS certificate for use\n" "in the final step." msgstr "" #: i2p2www/blog/2019/06/02/mirroring-guide.rst:143 msgid "Process Two: Forward your service to an eepSite" msgstr "" #: i2p2www/blog/2019/06/02/mirroring-guide.rst:146 msgid "" "Congratulations! You've completed the most difficult part. From here on, the\n" "decisions you must make, and the consequences that they will have, are much\n" "more straightforward and easy to enumerate. Such is the beauty of a\n" "cryptographically secure network layer like I2P!" msgstr "" #: i2p2www/blog/2019/06/02/mirroring-guide.rst:155 msgid "Step three: Generate your .i2p Tunnels and Addresses" msgstr "" #: i2p2www/blog/2019/06/02/mirroring-guide.rst:158 msgid "" "For eepSites, you will need to create an HTTP Server Tunnel. This is\n" "an I2P destination with a few special features for hosting HTTP services to\n" "enable things like rate-limiting, filtering, and the inclusion of headers to\n" "identify the destination of the client to the server. These enable flexibility\n" "in how you handle connections in terms of load-balancing and rate-limiting on\n" "a case-by-case basis, among other things. Explore these options and how they\n" "relate to the applications which you considered in step one, even though a very\n" "simple setup is easy, larger sites may benefit from taking advantage of these\n" "features." msgstr "" #: i2p2www/blog/2019/06/02/mirroring-guide.rst:170 msgid "Create an HTTP Tunnel for your application" msgstr "" #: i2p2www/blog/2019/06/02/mirroring-guide.rst:173 msgid "" "If you've configured a reverse proxy or an SSH tunnel before, then the general\n" "idea here should be very familiar to you. I2PTunnel, in essence, is just\n" "forwarding ports from the host to the I2P Network. To set this up using the web\n" "interface, go to the I2PTunnel configuration page." msgstr "" #: i2p2www/blog/2019/06/02/mirroring-guide.rst:180 msgid "" "At the bottom of the \"I2P Hidden Services\" section of the page, select an HTTP\n" "Service from the drop-down and click \"Create.\"" msgstr "" #: i2p2www/blog/2019/06/02/mirroring-guide.rst:189 msgid "" "It will immediately drop you into the granular tunnel configuration page, which\n" "we're about to explore from top-to-bottom. The first, most essential settings\n" "are the tunnel name and the target host:port. **The target host:port is**\n" "**the place where you input the address of the service you are forwarding to**\n" "**I2P**. Once you've configured that, your web site will become available over\n" "i2p. However, there are probably a few things that we can improve." msgstr "" #: i2p2www/blog/2019/06/02/mirroring-guide.rst:202 msgid "" "Next, you may want to pick a hostname to use for your eepSite. This hostname\n" "doesn't need to be universally unique, for now, it will only be used locally.\n" "We'll publish it to an address helper later. **If** the *Local Destination*\n" "field isn't populated with your Base64 Destination yet, you should scroll down\n" "to the bottom, save the tunnel configuration, and return to the tunnel\n" "configuration." msgstr "" #: i2p2www/blog/2019/06/02/mirroring-guide.rst:215 msgid "" "A little further down the configuration page, the tunnel options are available.\n" "Since you've got a site which is not intended to be anonymous, but rather to\n" "provide anonymous access to others by an alternate gateway, it may be good to\n" "reduce the number of hops the tunnel takes on the I2P network." msgstr "" #: i2p2www/blog/2019/06/02/mirroring-guide.rst:226 msgid "" "Next are the encrypted leaseset options. You can probably leave these as the\n" "defaults, since your site isn't anonymous it probably doesn't need features like\n" "blinding or encrypted leasesets. If you were to choose encrypted leasesets, you\n" "would not be accessible to anyone unless you shared a key with them in advance." msgstr "" #: i2p2www/blog/2019/06/02/mirroring-guide.rst:237 msgid "" "The next few parts may be especially useful to you if you run a high-traffic\n" "site or find yourself subject to DDOS attacks. Here you can configure various\n" "kinds of connection limits." msgstr "" #: i2p2www/blog/2019/06/02/mirroring-guide.rst:247 msgid "" "After that, there are a few other ways of filtering connections by client\n" "characteristics. First, you can block access via inproxies like I2P.to and\n" "similar. Since you have a clearnet presence already, changing this may be better\n" "if you want to encourage I2P users to only use your eepSite. You can also block\n" "accesses via specific user-agents, for instance blocking wget may be helpful if\n" "you want to prevent spidering. Finally, and of particular interest to Fail2Ban\n" "users, the \"Unique local address per client\" will give each client it's own\n" "local IP address instead of them all appearing to the server to be from\n" "127.0.0.1." msgstr "" #: i2p2www/blog/2019/06/02/mirroring-guide.rst:263 msgid "You can probably leave these next few options to the defaults." msgstr "" #: i2p2www/blog/2019/06/02/mirroring-guide.rst:271 msgid "" "Lastly, you can set up an advanced filter definition. Writing filters is beyond\n" "what I'm prepared to do in this document, for more information see the format\n" "specification for now." msgstr "" #: i2p2www/blog/2019/06/02/mirroring-guide.rst:281 msgid "Multi-Home an Application" msgstr "" #: i2p2www/blog/2019/06/02/mirroring-guide.rst:284 msgid "" "One interesting thing that I2P can do is host the same site on multiple servers\n" "at the same time transparently, which is referred to as \"Multihoming.\" In order\n" "to multihome your application, you will need to return to the tunnel menu and\n" "change the location of your private key file to it's own, non-shared location." msgstr "" #: i2p2www/blog/2019/06/02/mirroring-guide.rst:295 msgid "" "When you're done, copy the new key file for your new multihomed service to a\n" "storage device. Now, you can re-produce your service/tunnel configuration with\n" "those same keys on any I2P router and increase your service's redundancy." msgstr "" #: i2p2www/blog/2019/06/02/mirroring-guide.rst:301 msgid "Step four: Publicize and Authenticate your eepSite" msgstr "" #: i2p2www/blog/2019/06/02/mirroring-guide.rst:304 msgid "" "Since you're running an anonymously accessible instance of an existing clear-net\n" "service, you'll probably want to leverage some existing form of trust to\n" "distribute your eepSite URL, like a TLS Certificate signed by a recognized and\n" "reputable authority. What can I say we live in an imperfect world." msgstr "" #: i2p2www/blog/2019/06/02/mirroring-guide.rst:313 msgid "Place your .b32.i2p link on your clearnet page" msgstr "" #: i2p2www/blog/2019/06/02/mirroring-guide.rst:316 msgid "" "The simplest way to provide a link to your eepSite using an existing site to\n" "distribute the link is to distribute a so-called \"Base32\" address. The Base32\n" "address is the hash of the public key of your I2P destination, so it cannot be\n" "forged if it is provided by a reliable source. In the case of a clear-net site\n" "with a hidden service presence, one of those places is likely to be that\n" "clear-net site." msgstr "" #: i2p2www/blog/2019/06/02/mirroring-guide.rst:325 msgid "" "Your base32 address is visible on the main i2ptunnel configuration page and it\n" "looks like this:" msgstr "" #: i2p2www/blog/2019/06/02/mirroring-guide.rst:334 msgid "" "Your users can copy-and-paste this link directly into their I2P browsers and\n" "it will just work, no additional configuration required." msgstr "" #: i2p2www/blog/2019/06/02/mirroring-guide.rst:339 msgid "Distributing an \"Addresshelper\" link from your clearnet page" msgstr "" #: i2p2www/blog/2019/06/02/mirroring-guide.rst:342 msgid "" "You can also distribute a human-readable link to suggest to your potential users\n" "by taking advantage of I2P's \"Address Book\" feature, which allows the users to\n" "decide to assign a human-readable domain name to your cryptographically\n" "assured identity. You can do this by distributing a specially crafted link\n" "containing the domain name that you want to suggest, followed by a slash,\n" "followed by ?i2paddresshelper=, followed by the Local Destination of the tunnel\n" "you just created, which you can see here:" msgstr "" #: i2p2www/blog/2019/06/02/mirroring-guide.rst:356 msgid "So, for the example site, such a link would point to this address" msgstr "" #: i2p2www/blog/2019/06/02/mirroring-guide.rst:364 msgid "" "I keep saying suggest because when the such a link is visited, I2P asks for the\n" "user's consent to add this human-readable name to the user's local address book.\n" "That means there is no expectation that this domain be universally agreed upon\n" "by all visitors on the I2P network, whereas in the case of base32 addresses,\n" "the opposite is true." msgstr "" #: i2p2www/blog/2019/06/02/mirroring-guide.rst:372 msgid "Registering with an Addresshelper service" msgstr "" #: i2p2www/blog/2019/06/02/mirroring-guide.rst:375 msgid "" "Nonetheless, there do exist publicly available address subscription feeds, and\n" "special services for discovering new human-readable addresses, such as no.i2p,\n" "inr.i2p, and stats.i2p. These are sometimes known as Address helpers or Jump\n" "Services, and can also be subscribed to automatically. This may be espescially\n" "helpful to users of your service who wish to acquire the address without leaving\n" "I2P or visiting your clearnet service." msgstr "" #: i2p2www/blog/2019/06/02/mirroring-guide.rst:384 msgid "Register a name with stats.i2p" msgstr "" #: i2p2www/blog/2019/06/02/mirroring-guide.rst:385 msgid "Register a new name with inr.i2p" msgstr "" #: i2p2www/blog/2019/06/02/mirroring-guide.rst:402 msgid "See Also:" msgstr "" #: i2p2www/blog/2019/06/02/mirroring-guide.rst:405 msgid "" "Most of the security issues of hosting Tor hidden services also apply to I2P. It\n" "would be advisable to take advantage of their resources as well as this one:" msgstr "" #: i2p2www/blog/2019/06/02/mirroring-guide.rst:410 msgid "Misc Links" msgstr "" #: i2p2www/blog/2019/06/02/mirroring-guide.rst:413 msgid "Official Guide" msgstr "" #: i2p2www/blog/2019/06/02/mirroring-guide.rst:414 msgid "Riseup best Practices" msgstr "" #: i2p2www/blog/2019/06/02/mirroring-guide.rst:415 msgid "Blog about config fails" msgstr "" #: i2p2www/blog/2019/06/02/mirroring-guide.rst:416 msgid "Whonix Docs Onion Service" msgstr "" #: i2p2www/blog/2019/06/02/mirroring-guide.rst:417 msgid "Reddit thread" msgstr "" #: i2p2www/blog/2019/06/02/mirroring-guide.rst:422 msgid "Hosting clearnet site as onion service" msgstr "" #: i2p2www/blog/2019/06/02/mirroring-guide.rst:423 msgid "Securing a Tor Hidden Service" msgstr "" #: i2p2www/blog/2019/06/02/mirroring-guide.rst:424 msgid "Effects of hosting hidden and non-hidden services" msgstr "" #: i2p2www/blog/2019/06/02/mirroring-guide.rst:429 msgid "Propublica" msgstr "" #: i2p2www/blog/2019/06/02/mirroring-guide.rst:430 msgid "Wikipedia Proposal" msgstr "" #: i2p2www/blog/2019/06/15/i2p-i2pd-ssh-config.rst:7 msgid "How to set up an ssh server behind I2P for personal access" msgstr "" #: i2p2www/blog/2019/06/15/i2p-i2pd-ssh-config.rst:10 msgid "" "This is a tutorial on how to set up and tweak an I2P tunnel in order to use it\n" "to access an SSH server remotely, using either I2P or i2pd. For now, it assumes\n" "you will install your SSH server from a package manager and that it's running\n" "as a service." msgstr "" #: i2p2www/blog/2019/06/15/i2p-i2pd-ssh-config.rst:17 msgid "" "Considerations: In this guide, I'm assuming a few things. They will need to be\n" "adjusted depending on the complications that arise in your particular setup,\n" "especially if you use VM's or containers for isolation. This assumes that the\n" "I2P router and the ssh server are running on the same localhost. You should be\n" "using newly-generated SSH host keys, either by using a freshly installed sshd,\n" "or by deleting old keys and forcing their re-generation. For example:" msgstr "" #: i2p2www/blog/2019/06/15/i2p-i2pd-ssh-config.rst:35 msgid "Step One: Set up I2P tunnel for SSH Server" msgstr "" #: i2p2www/blog/2019/06/15/i2p-i2pd-ssh-config.rst:38 #: i2p2www/blog/2019/06/15/i2p-i2pd-ssh-config.rst:189 msgid "Using Java I2P" msgstr "" #: i2p2www/blog/2019/06/15/i2p-i2pd-ssh-config.rst:41 msgid "" "Using java I2P's web interface, navigate to the (Links to your Router Console)\\ `Hidden Services Manager `__\n" "and start the tunnel wizard." msgstr "" #: i2p2www/blog/2019/06/15/i2p-i2pd-ssh-config.rst:46 #: i2p2www/blog/2019/06/15/i2p-i2pd-ssh-config.rst:194 msgid "Tunnel Wizard" msgstr "隧道向导" #: i2p2www/blog/2019/06/15/i2p-i2pd-ssh-config.rst:49 msgid "" "Since you are setting up this tunnel for the SSH server, you need to select the\n" "\"Server\" tunnel type." msgstr "" #: i2p2www/blog/2019/06/15/i2p-i2pd-ssh-config.rst:58 msgid "" "You should fine-tune it later, but the Standard tunnel type is easiest to start\n" "with." msgstr "" #: i2p2www/blog/2019/06/15/i2p-i2pd-ssh-config.rst:67 msgid "Give it a good description:" msgstr "" #: i2p2www/blog/2019/06/15/i2p-i2pd-ssh-config.rst:75 msgid "And tell it where the SSH server will be available." msgstr "" #: i2p2www/blog/2019/06/15/i2p-i2pd-ssh-config.rst:81 msgid "Look over the results, and save your settings." msgstr "" #: i2p2www/blog/2019/06/15/i2p-i2pd-ssh-config.rst:89 #: i2p2www/blog/2019/06/15/i2p-i2pd-ssh-config.rst:263 msgid "Advanced Settings" msgstr "高级设置" #: i2p2www/blog/2019/06/15/i2p-i2pd-ssh-config.rst:92 msgid "" "Now head back over the the Hidden Services Manager, and look over the available\n" "advanced settings. One thing you'll definitely want to change is to set it up\n" "for interactive connections intstead of bulk connections." msgstr "" #: i2p2www/blog/2019/06/15/i2p-i2pd-ssh-config.rst:102 msgid "" "Besides that, these other options can affect performance when accessing your SSH\n" "server. If you aren't that concerned about your anonymity, then you could reduce\n" "the number of hops you take. If you have trouble with speed, a higher tunnel\n" "count might help. A few backup tunnels are probably a good idea. You might have\n" "to dial-it-in a bit." msgstr "" #: i2p2www/blog/2019/06/15/i2p-i2pd-ssh-config.rst:114 msgid "Finally, restart the tunnel so that all of your settings take effect." msgstr "" #: i2p2www/blog/2019/06/15/i2p-i2pd-ssh-config.rst:118 msgid "" "Another interesting setting, especially if you choose to run a high number of\n" "tunnels is \"Reduce on Idle\" which will reduce the number of tunnels that run\n" "when the serve has experienced extended inactivity." msgstr "" #: i2p2www/blog/2019/06/15/i2p-i2pd-ssh-config.rst:128 #: i2p2www/blog/2019/06/15/i2p-i2pd-ssh-config.rst:279 msgid "Using i2pd" msgstr "" #: i2p2www/blog/2019/06/15/i2p-i2pd-ssh-config.rst:131 msgid "" "With i2pd, all configuration is done with files instead of via a web interface.\n" "In order to configure an SSH Service tunnel for i2pd, tweak the following\n" "example settings to your anonymity and performance needs and copy them into\n" "tunnels.conf" msgstr "" #: i2p2www/blog/2019/06/15/i2p-i2pd-ssh-config.rst:152 msgid "Restart your I2P router" msgstr "" #: i2p2www/blog/2019/06/15/i2p-i2pd-ssh-config.rst:155 msgid "Step Two: Set up SSH server" msgstr "" #: i2p2www/blog/2019/06/15/i2p-i2pd-ssh-config.rst:158 msgid "" "Depending on how you want to access your SSH Server, you may want to make a few\n" "changes to the settings. Besides the obvious SSH hardening stuff you should do\n" "on all SSH servers(Public-Key Authentication, no login as root, etc), if you\n" "don't want your SSH server to listen on any addresses except your server tunnel,\n" "you should change AddressFamily to inet and ListenAddress to 127.0.0.1." msgstr "" #: i2p2www/blog/2019/06/15/i2p-i2pd-ssh-config.rst:171 msgid "" "If you choose to use a port other than 22 for your SSH server, you will need to\n" "change the port in your I2P tunnel configuration." msgstr "" #: i2p2www/blog/2019/06/15/i2p-i2pd-ssh-config.rst:176 msgid "Step Three: Set up I2P tunnel for SSH Client" msgstr "" #: i2p2www/blog/2019/06/15/i2p-i2pd-ssh-config.rst:179 msgid "" "You will need to be able to see the I2P router console of the SSH server in\n" "order to configure your client connection. One neat thing about this setup is\n" "that the initial connection to the I2P tunnel is authenticated, somewhat\n" "reducing the risk of your initial connection to the SSH server being MITM'ed,\n" "as is a risk in Trust-On-First-Use scenarios." msgstr "" #: i2p2www/blog/2019/06/15/i2p-i2pd-ssh-config.rst:197 msgid "" "First, start the tunnel configuration wizard from the hidden services manager\n" "and select a client tunnel." msgstr "" #: i2p2www/blog/2019/06/15/i2p-i2pd-ssh-config.rst:206 msgid "" "Next, select the standard tunnel type. You will fine-tune this configuration\n" "later." msgstr "" #: i2p2www/blog/2019/06/15/i2p-i2pd-ssh-config.rst:215 msgid "Give it a good description." msgstr "" #: i2p2www/blog/2019/06/15/i2p-i2pd-ssh-config.rst:223 msgid "" "This is the only slightly tricky part. Go to the hidden services manager of the\n" "I2P router console and find the base64 \"local destination\" of the SSH server\n" "tunnel. You'll need to find a way to copy this information into the next step.\n" "I generally `Tox `__ it to myself, any off-the-record\n" "should be sufficient for most people." msgstr "" #: i2p2www/blog/2019/06/15/i2p-i2pd-ssh-config.rst:235 msgid "" "Once you've found the base64 destination you want to connect to transmitted to\n" "your client device, then paste it into the client destination field." msgstr "" #: i2p2www/blog/2019/06/15/i2p-i2pd-ssh-config.rst:244 msgid "" "Lastly, set a local port to connect your ssh client to. This will local port\n" "will be connected to the base64 destination and thus the SSH server." msgstr "" #: i2p2www/blog/2019/06/15/i2p-i2pd-ssh-config.rst:253 msgid "Decide whether you want it to start automatically." msgstr "" #: i2p2www/blog/2019/06/15/i2p-i2pd-ssh-config.rst:266 msgid "" "Like before, you'll want to change the settings to be optimized for interactive\n" "connections. Additionally, if you want to set up client whiteliting on the\n" "server, you should check the \"Generate key to enable persistent client tunnel\n" "identity\" radial button." msgstr "" #: i2p2www/blog/2019/06/15/i2p-i2pd-ssh-config.rst:282 msgid "" "You can set this up by adding the following lines to your tunnels.conf and\n" "adjust it for your performance/anonymity needs." msgstr "" #: i2p2www/blog/2019/06/15/i2p-i2pd-ssh-config.rst:303 msgid "Restart the I2P router on the client" msgstr "" #: i2p2www/blog/2019/06/15/i2p-i2pd-ssh-config.rst:306 msgid "Step Four: Set up SSH client" msgstr "" #: i2p2www/blog/2019/06/15/i2p-i2pd-ssh-config.rst:309 msgid "" "There are lots of ways to set up an SSH client to connect to your server on I2P,\n" "but there are a few things you should do to secure your SSH client for anonymous\n" "use. First, you should configure it to only identify itself to SSH server with\n" "a single, specific key so that you don't risk contaminating your anonymous and\n" "non-anonymous SSH connections." msgstr "" #: i2p2www/blog/2019/06/15/i2p-i2pd-ssh-config.rst:317 msgid "Make sure your $HOME/.ssh/config contains the following lines:" msgstr "" #: i2p2www/blog/2019/06/15/i2p-i2pd-ssh-config.rst:328 msgid "" "Alternatively, you could make a .bash_alias entry to enforce your options and\n" "automatically connect to I2P. You get the idea, you need to enforce\n" "IdentitiesOnly and provide an identity file." msgstr "" #: i2p2www/blog/2019/06/15/i2p-i2pd-ssh-config.rst:340 msgid "Step Five: Whitelist only the client tunnel" msgstr "" #: i2p2www/blog/2019/06/15/i2p-i2pd-ssh-config.rst:343 msgid "" "This is more-or-less optional, but it's pretty cool and will prevent anyone who\n" "happens to come across your destination from being able to tell you are hosting\n" "an SSH service." msgstr "" #: i2p2www/blog/2019/06/15/i2p-i2pd-ssh-config.rst:349 msgid "" "First, retrieve the persistent client tunnel destination and transmit it to the\n" "server." msgstr "" #: i2p2www/blog/2019/06/15/i2p-i2pd-ssh-config.rst:358 msgid "" "Add the client's base64 destination to the server's destination whitelist. Now\n" "you'll only be able to connect to the server tunnel from that specific client\n" "tunnel and no one else will be able to connect to that destination." msgstr "" #: i2p2www/blog/2019/06/15/i2p-i2pd-ssh-config.rst:368 msgid "Mutual authentication FTW." msgstr "" #: i2p2www/blog/2019/06/23/sam-library-basics.rst:2 msgid "So You Want To Write A SAM Library" msgstr "" #: i2p2www/blog/2019/06/23/sam-library-basics.rst:8 msgid "Beginners guide to writing a SAM library!" msgstr "" #: i2p2www/blog/2019/06/23/sam-library-basics.rst:12 msgid "" "One of the best features of I2P, in my opinion, is it's SAM API, which can be\n" "used to build a bridge between I2P and your application or language of choice.\n" "Currently, dozens of SAM libraries exist for a variety of languages, including:" msgstr "" #: i2p2www/blog/2019/06/23/sam-library-basics.rst:32 msgid "" "If you're using any of these languages, you may be able to port your application\n" "to I2P already, using an existing library. That's not what this tutorial is\n" "about, though. This tutorial is about what to do if you want to create a SAM\n" "library in a new language. In this tutorial, I will implement a new SAM library\n" "in Java. I chose Java because there isn't a Java library that connects you to\n" "SAM yet, because of Java's use in Android, and because it's a language almost\n" "everybody has at least a *little* experience with, so hopefully you can\n" "translate it into a language of your choice." msgstr "" #: i2p2www/blog/2019/06/23/sam-library-basics.rst:43 msgid "Creating your library" msgstr "" #: i2p2www/blog/2019/06/23/sam-library-basics.rst:46 msgid "" "How you set up your own library will vary depending on the language you wish\n" "to use. For this example library, we'll be using java so we can create a library\n" "like this:" msgstr "" #: i2p2www/blog/2019/06/23/sam-library-basics.rst:58 msgid "Or, if you are using gradle 5 or greater:" msgstr "" #: i2p2www/blog/2019/06/23/sam-library-basics.rst:66 msgid "Setting up the Library" msgstr "" #: i2p2www/blog/2019/06/23/sam-library-basics.rst:69 msgid "" "There are a few pieces of data that almost any SAM library should probably\n" "manage. It will at least need to store the address of the SAM Bridge you intend\n" "to use and the signature type you wish to use." msgstr "" #: i2p2www/blog/2019/06/23/sam-library-basics.rst:75 msgid "Storing the SAM address" msgstr "" #: i2p2www/blog/2019/06/23/sam-library-basics.rst:78 msgid "" "I prefer to store the SAM address as a String and an Integer, and re-combine\n" "them in a function at runtime." msgstr "" #: i2p2www/blog/2019/06/23/sam-library-basics.rst:91 msgid "Storing the Signature Type" msgstr "" #: i2p2www/blog/2019/06/23/sam-library-basics.rst:94 msgid "" "The valid signature types for an I2P Tunnel are DSA_SHA1, ECDSA_SHA256_P256,\n" "ECDSA_SHA384_P384, ECDSA_SHA512_P521, EdDSA_SHA512_Ed25519, but it is\n" "strongly recommended that you use EdDSA_SHA512_Ed25519 as a default if you\n" "implement at least SAM 3.1. In java, the 'enum' datastructure lends itself to\n" "this task, as it is intended to contain a group of constants. Add the enum, and\n" "an instance of the enum, to your java class definition." msgstr "" #: i2p2www/blog/2019/06/23/sam-library-basics.rst:114 msgid "Retrieving the signature type:" msgstr "" #: i2p2www/blog/2019/06/23/sam-library-basics.rst:117 msgid "" "That takes care of reliably storing the signature type in use by the SAM\n" "connection, but you've still got to retrieve it as a string to communicate it\n" "to the bridge." msgstr "" #: i2p2www/blog/2019/06/23/sam-library-basics.rst:141 msgid "It's important to test things, so let's write some tests:" msgstr "" #: i2p2www/blog/2019/06/23/sam-library-basics.rst:156 msgid "" "Once that's done, begin creating your constructor. Note that we've given our\n" "library defaults which will be useful in default situations on all existing I2P\n" "routers so far." msgstr "" #: i2p2www/blog/2019/06/23/sam-library-basics.rst:170 msgid "Establishing a SAM Connection" msgstr "" #: i2p2www/blog/2019/06/23/sam-library-basics.rst:173 msgid "" "Finally, the good part. Interaction with the SAM bridge is done by sending a\n" "\"command\" to the address of the SAM bridge, and you can parse the result of the\n" "command as a set of string-based key-value pairs. So bearing that in mind, let's\n" "estabish a read-write connection to the SAM Address we defined before, then\n" "write a \"CommandSAM\" Function and a reply parser." msgstr "" #: i2p2www/blog/2019/06/23/sam-library-basics.rst:181 msgid "Connecting to the SAM Port" msgstr "" #: i2p2www/blog/2019/06/23/sam-library-basics.rst:184 msgid "" "We're communicating with SAM via a Socket, so in order to connect to, read from,\n" "and write to the socket, you'll need to create the following private variables\n" "in the Jsam class:" msgstr "" #: i2p2www/blog/2019/06/23/sam-library-basics.rst:196 msgid "" "You will also want to instantiate those variables in your Constructors by\n" "creating a function to do so." msgstr "" #: i2p2www/blog/2019/06/23/sam-library-basics.rst:219 msgid "Sending a Command to SAM" msgstr "" #: i2p2www/blog/2019/06/23/sam-library-basics.rst:222 msgid "" "Now you're all set up to finally start talking to SAM. In order to keep things\n" "nicely organized, let's create a function which sends a single command to SAM,\n" "terminated by a newline, and which returns a Reply object, which we will create\n" "in the next step:" msgstr "" #: i2p2www/blog/2019/06/23/sam-library-basics.rst:241 msgid "" "Note that we are using the writer and reader we created from the socket in the\n" "previous step as our inputs and outputs to the socket. When we get a reply from\n" "the reader, we pass the string to the Reply constructor, which parses it and\n" "returns the Reply object." msgstr "" #: i2p2www/blog/2019/06/23/sam-library-basics.rst:250 msgid "Parsing a reply and creating a Reply object." msgstr "" #: i2p2www/blog/2019/06/23/sam-library-basics.rst:253 msgid "" "In order to more easily handle replies, we'll use a Reply object to\n" "automatically parse the results we get from the SAM bridge. A reply has at least\n" "a topic, a type, and a result, as well as an arbitrary number of key-value\n" "pairs." msgstr "" #: i2p2www/blog/2019/06/23/sam-library-basics.rst:268 msgid "" "As you can see, we will be storing the \"result\" as an enum, REPLY_TYPES. This\n" "enum contains all the possible reply results which the SAM bridge might respond\n" "with." msgstr "" #: i2p2www/blog/2019/06/23/sam-library-basics.rst:335 msgid "" "Now let's create our constructor, which takes the reply string recieved from the\n" "socket as a parameter, parses it, and uses the information to set up the reply\n" "object. The reply is space-delimited, with key-value pairs joined by an equal\n" "sign and terminated by a newline." msgstr "" #: i2p2www/blog/2019/06/23/sam-library-basics.rst:364 msgid "" "Lastly, for the sake of convenience, let's give the reply object a toString()\n" "function which returns a string representation of the Reply object." msgstr "" #: i2p2www/blog/2019/06/23/sam-library-basics.rst:376 msgid "Saying \"HELLO\" to SAM" msgstr "" #: i2p2www/blog/2019/06/23/sam-library-basics.rst:379 msgid "" "Now we're ready to establish communication with SAM by sending a \"Hello\"\n" "message. If you're writing a new SAM library, you should probably target at\n" "least SAM 3.1, since it's available in both I2P and i2pd and introduces support\n" "for the SIGNATURE_TYPE parameter." msgstr "" #: i2p2www/blog/2019/06/23/sam-library-basics.rst:397 msgid "" "As you can see, we use the CommandSAM function we created before to send the\n" "newline-terminated command ``HELLO VERSION MIN=3.0 MAX=3.1 \\n``. This tells\n" "SAM that you want to start communicating with the API, and that you know how\n" "to speak SAM version 3.0 and 3.1. The router, in turn, will respond with\n" "like ``HELLO REPLY RESULT=OK VERSION=3.1`` which is a string you can pass to\n" "the Reply constructor to get a valid Reply object. From now on, we can use our\n" "CommandSAM function and Reply object to deal with all our communication across\n" "the SAM bridge." msgstr "" #: i2p2www/blog/2019/06/23/sam-library-basics.rst:408 msgid "Finally, let's add a test for our \"HelloSAM\" function." msgstr "" #: i2p2www/blog/2019/06/23/sam-library-basics.rst:423 msgid "" "Now that you've negotiated your connection to SAM and agreed on a SAM version\n" "you both speak, you can set up peer-to-peer connections for your application\n" "to connect to other i2p applications. You do this by sending a \"SESSION CREATE\"\n" "command to the SAM Bridge. To do that, we'll use a CreateSession function that\n" "accepts a session ID and a destination type parameter." msgstr "" #: i2p2www/blog/2019/06/23/sam-library-basics.rst:444 msgid "" "That was easy, right? All we had to do was adapt the pattern we used in our\n" "HelloSAM function to the ``SESSION CREATE`` command. A good reply from the\n" "bridge will still return OK, and in that case we return the ID of the newly\n" "created SAM connection. Otherwise, we return an empty string because that's an\n" "invalid ID anyway and it failed, so it's easy to check. Let's see if this\n" "function works by writing a test for it:" msgstr "" #: i2p2www/blog/2019/06/23/sam-library-basics.rst:461 msgid "" "Note that in this test, we *must* call HelloSAM first to establish communication\n" "with SAM before starting our session. If not, the bridge will reply with an\n" "error and the test will fail." msgstr "" #: i2p2www/blog/2019/06/23/sam-library-basics.rst:472 msgid "" "Now you have your session established and your local destination, and need to\n" "decide what you want to do with them. Your session can now be commanded to\n" "connect to a remote service over I2P, or to wait for incoming connections to\n" "respond to. However, before you can connect to a remote destination, you may\n" "need to obtain the base64 of the destination, which is what the API expects. In\n" "order to do this, we'll create a LookupName function, which will return the\n" "base64 in a usable form." msgstr "" #: i2p2www/blog/2019/06/23/sam-library-basics.rst:494 msgid "" "Again, this is almost the same as our HelloSAM and CreateSession functions,\n" "with one difference. Since we're looking for the VALUE specifically and the NAME\n" "field will be the same as the ``name`` argument, it simply returns the base64\n" "string of the destination requested." msgstr "" #: i2p2www/blog/2019/06/23/sam-library-basics.rst:501 msgid "Now that we have our LookupName function, let's test it:" msgstr "" #: i2p2www/blog/2019/06/23/sam-library-basics.rst:516 msgid "" "At last, we are going to establish a connection to another service with our new\n" "library. This part confused me a bit at first, but the most astute Java\n" "developers were probably wondering why we didn't extend the socket class\n" "instead of creating a Socket variable inside of the Jsam class. That's because\n" "until now, we've been communicating with the \"Control Socket\" and we need to\n" "create a new socket to do the actual communication. So we've waited to extend\n" "the the Socket class with the Jsam class until now:" msgstr "" #: i2p2www/blog/2019/06/23/sam-library-basics.rst:530 msgid "" "Also, let's alter our startConnection function so that we can use it to switch\n" "over from the control socket to the socket we'll be using in our application. It\n" "will now take a Socket argument." msgstr "" #: i2p2www/blog/2019/06/23/sam-library-basics.rst:556 msgid "" "This allows us to quickly and easily open a new socket to communicate over,\n" "perform the \"Hello SAM\" handshake over again, and connect the stream." msgstr "" #: i2p2www/blog/2019/06/23/sam-library-basics.rst:579 msgid "" "And now you have a new Socket for communicating over SAM! Let's do the same\n" "thing for Accepting remote connections:" msgstr "" #: i2p2www/blog/2019/06/23/sam-library-basics.rst:599 msgid "" "There you have it. That's how you build a SAM library, step-by-step. In the\n" "future, I will cross-reference this with the working version of the library,\n" "Jsam, and the SAM v3 specification but for now I've got to get some other stuff\n" "done." msgstr "" #: i2p2www/blog/2019/07/02/0.9.41-Release.rst:2 msgid "0.9.41 Release" msgstr "" #: i2p2www/blog/2019/07/02/0.9.41-Release.rst:9 msgid "0.9.41 with bug fixes" msgstr "0.9.41 包含了错误修复" #: i2p2www/blog/2019/07/02/0.9.41-Release.rst:16 msgid "" "0.9.41 continues the work to implement new features for proposal 123,\n" "including per-client authentication for encrypted leasesets.\n" "The console has an updated I2P logo and several new icons.\n" "We've updated the Linux installer." msgstr "0.9.41 继续着手落实提案 123 引入的新功能，\n包括对加密的租契集做客户端级别的身份验证。\n控制台的 I2P 标志及若干图标已更新。\n更新了 Linux 安装程序。" #: i2p2www/blog/2019/07/02/0.9.41-Release.rst:23 msgid "" "Startup should be faster on platforms such as Raspberry Pi.\n" "We've fixed several bugs, including some serious ones affecting low-level network messages." msgstr "启动速度在树莓派（Raspberry Pi）等平台上更快了。\n已修正若干缺陷，包括部分严重影响底层网络消息的问题。" #: i2p2www/blog/2019/07/02/0.9.41-Release.rst:38 msgid "" "Add configuration UI for encrypted leasesets, including per-client " "authentication (proposal 123)" msgstr "" #: i2p2www/blog/2019/07/02/0.9.41-Release.rst:39 msgid "Switch to IzPack 5 for non-Windows installer" msgstr "" #: i2p2www/blog/2019/07/02/0.9.41-Release.rst:40 msgid "Implementation for sending Meta LS2 to floodfills (proposal 123)" msgstr "" #: i2p2www/blog/2019/07/02/0.9.41-Release.rst:41 msgid "Wrapper 3.5.39 (new installs only)" msgstr "" #: i2p2www/blog/2019/07/02/0.9.41-Release.rst:42 msgid "Add wrapper for arm7 and aarch64 (new installs only)" msgstr "" #: i2p2www/blog/2019/07/02/0.9.41-Release.rst:47 msgid "Fixes for transitioning out of hidden mode" msgstr "" #: i2p2www/blog/2019/07/02/0.9.41-Release.rst:48 msgid "Fix i2psnark writing config files at shutdown" msgstr "" #: i2p2www/blog/2019/07/02/0.9.41-Release.rst:49 msgid "Fix netdb ready after initial reseed" msgstr "" #: i2p2www/blog/2019/07/02/0.9.41-Release.rst:50 msgid "Fix delivery of acks for a database store message" msgstr "" #: i2p2www/blog/2019/07/02/0.9.41-Release.rst:51 msgid "Fix delivery of large messages in SSU" msgstr "" #: i2p2www/blog/2019/07/02/0.9.41-Release.rst:52 msgid "Fix console install for IzPack 5" msgstr "" #: i2p2www/blog/2019/07/02/0.9.41-Release.rst:53 msgid "Fixes for webapps in Jetty eepsite" msgstr "" #: i2p2www/blog/2019/07/02/0.9.41-Release.rst:58 msgid "New console logos and icons" msgstr "" #: i2p2www/blog/2019/07/02/0.9.41-Release.rst:59 msgid "Update hidden mode country list" msgstr "" #: i2p2www/blog/2019/07/02/0.9.41-Release.rst:60 msgid "Limit UPnP lease duration" msgstr "" #: i2p2www/blog/2019/07/02/0.9.41-Release.rst:61 msgid "Faster netdb startup" msgstr "" #: i2p2www/blog/2019/07/02/0.9.41-Release.rst:62 msgid "Startup improvements for Android" msgstr "" #: i2p2www/blog/2019/07/02/0.9.41-Release.rst:63 msgid "" "New X25519 code for LS2 per-client authentication (proposal 123) and " "upcoming new encryption (proposal 144)" msgstr "" #: i2p2www/blog/2019/07/02/0.9.41-Release.rst:64 msgid "Sybil tool enhancements and bug fixes" msgstr "" #: i2p2www/blog/2019/07/02/0.9.41-Release.rst:65 msgid "Start first geoIP lookup sooner" msgstr "" #: i2p2www/blog/2019/07/27/mhatta-post-one.rst:5 #: i2p2www/blog/2019/07/27/mhatta-post-one.rst:8 msgid "Speeding up your I2P network" msgstr "" #: i2p2www/blog/2019/07/27/mhatta-post-one.rst:11 msgid "" "*This post is adapted directly from material originally created for mhatta's*\n" "`medium blog `__\\ *.*\n" "*He deserves the credit for the OP. It has been updated in certain places where*\n" "*it refers to old versions of I2P as current and has undergone some light*\n" "*editing. -idk*" msgstr "" #: i2p2www/blog/2019/07/27/mhatta-post-one.rst:17 msgid "" "Right after it starts up, I2P is often seen as a little bit slow. It's true, and\n" "we all know why, by nature, `garlic routing `__\n" "adds overhead to the familiar experience of using the internet so that you can\n" "have privacy, but this means that for many or most I2P services, your data will\n" "need to go through 12 hops by default." msgstr "" #: i2p2www/blog/2019/07/27/mhatta-post-one.rst:28 msgid "" "Also, unlike Tor, I2P was primarily designed as a closed network. You can\n" "easily access `eepsites `__ or other resources inside I2P, but you are not supposed\n" "to access `clearnet `__\n" "websites through I2P. There exist a few I2P “outproxies” similar to\n" "`Tor `__\\ ’s exit nodes to\n" "access clearnet, but most of them are very slow to use as going to the clearnet\n" "is effectively *another* hop in the already 6 hops in, six hops out connection." msgstr "" #: i2p2www/blog/2019/07/27/mhatta-post-one.rst:36 msgid "" "Until a few versions ago, this problem was even harder to deal with because many\n" "I2P router users were having difficulties configuring the bandwidth settings for\n" "their routers. If everyone who can takes the time to adjust their bandwidth\n" "settings properly, they will improve not only your connection but also the I2P\n" "network as a whole." msgstr "" #: i2p2www/blog/2019/07/27/mhatta-post-one.rst:42 msgid "Adjusting bandwidth limits" msgstr "" #: i2p2www/blog/2019/07/27/mhatta-post-one.rst:45 msgid "" "Since I2P is a peer-to-peer network, you have to share some of your network\n" "bandwidth with other peers. You see choose how much in “I2P Bandwidth\n" "Configuration” (“Configure Bandwidth” button in the “Applications and\n" "Configuration” section of I2P Router Console, or\n" "http://localhost:7657/config)." msgstr "" #: i2p2www/blog/2019/07/27/mhatta-post-one.rst:55 msgid "" "If you see a shared bandwidth limit of 48 KBps, which is very low, then you\n" "may not have adjusted your shared bandwidth from the default. As the original\n" "author of the material this blog post is adapted from noted, I2P has a default\n" "shared bandwidth limit that is very low until the user adjusts it to avoid\n" "causing issues with the user's connection." msgstr "" #: i2p2www/blog/2019/07/27/mhatta-post-one.rst:61 msgid "" "However, since many users may not know exactly which bandwidth settings to\n" "adjust, the `I2P 0.9.38 release `__ introduced a\n" "New Install Wizard. It contains a Bandwidth Test, which automatically detects\n" "(thanks to M-Lab’s `NDT `__) and adjusts\n" "I2P’s bandwidth settings accordingly." msgstr "" #: i2p2www/blog/2019/07/27/mhatta-post-one.rst:67 msgid "" "If you want to re-run the wizard, for instance following a change in your\n" "service provider or bcause you installed I2P before version 0.9.38, you can\n" "re-launch it from the 'Setup' link on the 'Help & FAQ' page, or simply access\n" "the wizard directly at http://localhost:7657/welcome" msgstr "" #: i2p2www/blog/2019/07/27/mhatta-post-one.rst:76 msgid "" "Using the Wizard is straightforward, simply keep clicking “Next”. Sometimes\n" "M-Lab’s chosen measurement servers are down and the test fails. In such case,\n" "click “Previous” (do not use your web browser’s “back” button), then\n" "try it again." msgstr "" #: i2p2www/blog/2019/07/27/mhatta-post-one.rst:85 msgid "Running I2P continuously" msgstr "" #: i2p2www/blog/2019/07/27/mhatta-post-one.rst:88 msgid "" "Even after adjusted the bandwidth, your connection might still be slow As I\n" "said, I2P is a P2P network. It will take some time for your I2P router to be\n" "discovered by other peers and integrated into the I2P network. If your router\n" "not up long enough to become well integrated, or if you shut down un-gracefully\n" "too often, the network will remain fairly slow. On the other hand, the longer\n" "you run your I2P router continuously, the faster and more stable your connection\n" "becomes, and more of your bandwidth share will be used in the network." msgstr "" #: i2p2www/blog/2019/07/27/mhatta-post-one.rst:96 msgid "" "However, many people might not be able to stay your I2P router up. In such\n" "case, you can still run the I2P router on a remote server such as VPS, then use\n" "SSH port forwarding." msgstr "" #: i2p2www/blog/2019/08/27/0.9.42-Release.rst:2 msgid "0.9.42 Release" msgstr "" #: i2p2www/blog/2019/08/27/0.9.42-Release.rst:9 msgid "0.9.42 with bug fixes" msgstr "0.9.42 包含了bug修复" #: i2p2www/blog/2019/08/27/0.9.42-Release.rst:16 msgid "" "0.9.42 continues the work to make I2P faster and more reliable.\n" "It includes several changes to speed up our UDP transport.\n" "We have split up the configuration files to enable future work for more modular packaging.\n" "We continue work to implement new proposals for faster and more secure encryption.\n" "There are, of course, a lot of bug fixes also." msgstr "0.9.42 继续使I2P更快更稳定.\n此版本包含了几处改动以提高UDP传输速度。\n我们拆分了设置文件，以便将来进一步模块化。\n我们将继续努力，将关于更快、更安全的加密的建议付诸实践。\n理所当然地， 还有许多bug修复。" #: i2p2www/blog/2019/08/27/0.9.42-Release.rst:34 msgid "Console: Split up help page, tag text for translation" msgstr "" #: i2p2www/blog/2019/08/27/0.9.42-Release.rst:35 msgid "Console: Hide NetDB RI and LS tabs" msgstr "" #: i2p2www/blog/2019/08/27/0.9.42-Release.rst:36 msgid "Debian: Update files for Buster" msgstr "" #: i2p2www/blog/2019/08/27/0.9.42-Release.rst:37 msgid "i2psnark: Add last-activity to details page" msgstr "" #: i2p2www/blog/2019/08/27/0.9.42-Release.rst:38 msgid "i2ptunnel: Split i2ptunnel.config into individual files per-tunnel" msgstr "" #: i2p2www/blog/2019/08/27/0.9.42-Release.rst:39 msgid "JBigI: GMP 6.1.2 (Linux 64-bit only)" msgstr "" #: i2p2www/blog/2019/08/27/0.9.42-Release.rst:40 msgid "" "NetDB: Choose alternate gateway for store replies to reduce connections" msgstr "" #: i2p2www/blog/2019/08/27/0.9.42-Release.rst:41 msgid "Router: Split clients.config into individual files per-client" msgstr "" #: i2p2www/blog/2019/08/27/0.9.42-Release.rst:42 msgid "SSU: performance improvements" msgstr "" #: i2p2www/blog/2019/08/27/0.9.42-Release.rst:43 msgid "Transports: Cross-network prevention (proposal 147)" msgstr "" #: i2p2www/blog/2019/08/27/0.9.42-Release.rst:48 msgid "i2psnark: Autostart fixes" msgstr "" #: i2p2www/blog/2019/08/27/0.9.42-Release.rst:49 msgid "i2psnark: Dup. data checks" msgstr "" #: i2p2www/blog/2019/08/27/0.9.42-Release.rst:50 msgid "i2ptunnel: Failsafe timeouts" msgstr "" #: i2p2www/blog/2019/08/27/0.9.42-Release.rst:51 msgid "NetDB: Fix NPE on store of encrypted LS2" msgstr "" #: i2p2www/blog/2019/08/27/0.9.42-Release.rst:52 msgid "Router: Fix Bloom filter false positives" msgstr "" #: i2p2www/blog/2019/08/27/0.9.42-Release.rst:57 msgid "Initial support for encryption types" msgstr "" #: i2p2www/blog/2019/08/27/0.9.42-Release.rst:58 msgid "Support for new LS2 bit for blinding (proposal 123)" msgstr "" #: i2p2www/blog/2019/08/30/defcon.rst:2 i2p2www/blog/2019/08/30/defcon.rst:9 msgid "Def Con Trip Report- zzz" msgstr "" #: i2p2www/blog/2019/08/30/defcon.rst:11 #: i2p2www/blog/2019/08/30/defcon2.rst:11 msgid "Def Con Trip Report" msgstr "" #: i2p2www/blog/2019/08/30/defcon.rst:14 msgid "" "idk and I attended DEFCON 27 and presented two workshops on I2P for application\n" "developers, with support from mhatta and Alex. I gave the workshop at Monero\n" "Village and idk gave the one at Crypto/Privacy Village. Here, I will summarize\n" "the Monero Village workshop, and a Tor talk by Roger Dingledine. idk will post a\n" "trip report covering his workshop." msgstr "" #: i2p2www/blog/2019/08/30/defcon.rst:22 msgid "" "We had about 8 attendees for the Monero Village workshop, entitled \"I2P for\n" "Cryptocurrency Developers\". We planned to discuss the particular networking\n" "needs for each application and work through the various i2ptunnel and SAM\n" "options available. However, all attendees were relatively unfamiliar with I2P,\n" "so we pivoted and gave an overview of I2P. As none of the attendees had a laptop\n" "with them, we helped several of them install I2P on their Android phone and\n" "walked through some of the features of the app. For all users, the app appeared\n" "to reseed and build tunnels fairly quickly." msgstr "" #: i2p2www/blog/2019/08/30/defcon.rst:33 msgid "" "One common question after installing the app was \"what do I do now?\". The app\n" "doesn't have a 'hidden services of interest' section or first-run wizard like\n" "our desktop application does, and most of the default addressbook entries are\n" "long-dead. There's improvements we could make to the first-run experience.\n" "Also, some of the more interesting parts of the app are hidden behind an\n" "advanced setting; we should review those items and consider un-hiding some of\n" "them." msgstr "" #: i2p2www/blog/2019/08/30/defcon.rst:43 msgid "" "It's always useful to go to Tor talks, not so much to find out what they're\n" "doing, but to hear how they explain things to people, and what terminology they\n" "are using. Roger's talk \"The Tor Censorship Arms Race\" was in a large room\n" "attended by about two thousand people. He gave a very brief overview of Tor\n" "with only three or four slides. He says they now have \"two to eight million\n" "users a day\". Most of the talk was a review of national blocking attempts over\n" "the years, starting with Thailand and Iran in '06-'07 through Tunisia, china,\n" "and Ethiopia in 2011. He called Tor bridges a \"crappy arms race\". He showed a\n" "new form to be showed to new users, with a checkbox \"Tor is censored in my\n" "country\"." msgstr "" #: i2p2www/blog/2019/08/30/defcon.rst:56 msgid "" "Their new pluggable transport \"snowflake\" uses a combination of domain\n" "fronting, webrtc, javascript, brokers and proxies to reach a Tor bridge. Roger\n" "only had one slide on it, and I wasn't familiar with it, so we should do more\n" "research on what it's all about. He briefly mentioned some things they may be\n" "working on next, including \"salmon\" distribution of bridges, FTE/Marionette,\n" "decoy routing, and \"cupcake\" which is an extension of snowflake. While I don't\n" "have any further information about them, they may be good buzzwords to keep an\n" "eye out for on their mailing lists." msgstr "" #: i2p2www/blog/2019/08/30/defcon.rst:67 msgid "" "Much of Tor's censorship woes is due to Tor's popularity, but their TLS\n" "handshake is a particular issue and it's been the focus of much of the \"arms\n" "race\" over the years. In some ways we're in better shape, as we've taken\n" "several features of their current-best obfs4 pluggable transport and build them\n" "into NTCP2. However, we do have issues with our website and reseeds being\n" "blocked, as Sadie and Phong will be presenting at USENIX FOCI this week." msgstr "" #: i2p2www/blog/2019/08/30/defcon.rst:76 msgid "" "Notes for next time: I do recommend DEFCON, as long as we find a village to\n" "call our home. It's an enormous conference and the limited general hangout\n" "spaces are massively overcrowded. Both Monero Village and Crypto/Privacy\n" "Village were fantastic hosts and we had several hours at each spot to meet with\n" "people. We should find more opportunities to work with both organizations.\n" "There were also ZCash people at the Monero Village and we should work with them\n" "also. Any future workshop should be targeted at a more general audience. We do\n" "need a standard \"Intro to I2P\" slide deck; it would have been helpful at the\n" "workshops. Don't expect attendees to have laptops with them, focus on Android\n" "for any hands-on exercises. There's several improvements to be made in our\n" "Android app. Drink lots of water in Vegas... and stay away from the slot\n" "machines." msgstr "" #: i2p2www/blog/2019/08/30/defcon2.rst:2 i2p2www/blog/2019/08/30/defcon2.rst:9 msgid "Def Con Trip Report- idk" msgstr "" #: i2p2www/blog/2019/08/30/defcon2.rst:14 msgid "" "I went to Def Con 27 last weekend to give a workshop on I2P application\n" "development, and to meet zzz, mhatta, and Alex in person." msgstr "" #: i2p2www/blog/2019/08/30/defcon2.rst:19 msgid "" "My workshop went well, we even had a few application developers attend! In\n" "particular I had a pretty lengthy conversation with a person named Mary about\n" "how I2P could be used to eliminate centralization and enhance privacy in\n" "a \"Magic Wormhole\" type of application. While I wasn't totally familiar with\n" "Magic Wormhole at the time, I think most of my advice was usable. I think Mary\n" "had some very interesting and workable ideas about sharing information in more\n" "human-centric ways that could be interesting in I2P applications, and am looking\n" "forward to experimenting with some of those." msgstr "" #: i2p2www/blog/2019/08/30/defcon2.rst:30 msgid "" "The materials I made for the application development workshop are available on\n" "Github! https://github.com/eyedeekay/defcon Please consider it a living document,\n" "your input is desired! As it is licensed permissively, you are free to fork it\n" "and make it your own as well. Share your examples, your hacks, or correct my\n" "comma use, complain about my document preparation style, or just print off your\n" "own copy in booklet form!" msgstr "" #: i2p2www/blog/2019/08/30/defcon2.rst:39 msgid "" "I also talked to a guy who gives advice to the government about the differences\n" "between I2P and Tor, why I2P is more P2P-friendly, and some scenarios in which\n" "peers in a P2P application might want to have enhanced privacy from each-other,\n" "and why I2P is perhaps uniquely suited to accomplish that." msgstr "" #: i2p2www/blog/2019/08/30/defcon2.rst:46 msgid "" "In general, both the application development workshops went well, even though\n" "they didn't go entirely according to plan in that only a small proportion of the\n" "audience were application developers. The impression I got was that many people\n" "are very interested in I2P, but also many people are confused by how interacting\n" "with I2P works. By re-focusing on their questions and by teaming off with zzz,\n" "mhatta, and Alex we were fairly successful at dealing with our audience, which\n" "was more varied in terms of occupation, interest, and I2P knowledge than\n" "expected." msgstr "" #: i2p2www/blog/2019/08/30/defcon2.rst:57 msgid "" "Besides that, I also talked to Alex about my experimental contextual-identity\n" "driven I2P proxy plugin for Firefox and eventually, Brave Browser. Got to talk\n" "a little about bundling, but not too much, as it was a very busy convention. I'm\n" "looking forward to following up with him on that soon." msgstr "" #: i2p2www/blog/2019/08/30/defcon2.rst:64 msgid "" "mhatta and I almost won a lobster from a claw machine, but it was a real\n" "fighter and got away at the last second. Really thought I had it for a moment\n" "though. :)" msgstr "" #: i2p2www/blog/2019/08/30/defcon2.rst:70 msgid "" "To add to zzz's notes for next time, aside from being more general I believe our\n" "workshops would not have been as able to adapt to the needs of the audience\n" "without the support of mhatta and Alex. Having people who can help particpants\n" "individually or in small groups was immensely helpful, many, many thanks to both\n" "of them for helping us out." msgstr "" #: i2p2www/blog/2019/08/30/foci.rst:2 i2p2www/blog/2019/08/30/foci.rst:9 #: i2p2www/blog/2019/08/30/foci.rst:11 msgid "USENIX FOCI Trip Report" msgstr "" #: i2p2www/blog/2019/08/30/foci.rst:14 msgid "" "Over the past year I have had the good fortune to participate in the research\n" "Nguyen Phong Hoang from Stony Brook University has been doing regarding I2P\n" "censorship. The infrastructure used for this research provided numerous and\n" "geographically diverse vantage points, and also the ability to conduct in-depth\n" "measurements across all levels of the network stack. I2P services which were\n" "measured for availability included official homepage, mirror site, reseed\n" "servers and active relays." msgstr "" #: i2p2www/blog/2019/08/30/foci.rst:24 msgid "" "The presentation on Tuesday went very well, and Phong was very busy afterwards\n" "answering questions about his work. I was busy too answering questions about\n" "I2P and what it does. The new stickers featuring the updated logo by Ura Design\n" "got rave reviews! It was a very positive experience and I will be looking\n" "forward to continuing to work with Phong and monitoring I2P censorship. I would\n" "encourage anyone who has encountered blocking, or has had success using I2P to\n" "communicate in restricted environments to reach out if you can. I2P is\n" "currently working on new solutions to circumvent internet blocking. Having met\n" "people this year who have given me first hand accounts of the effects of\n" "censorship and the need to stay connected, makes the need for I2P to be more\n" "resilient where it needs to be and for the team to be creating guides for using\n" "I2P in these situations." msgstr "" #: i2p2www/blog/2019/08/30/foci.rst:39 msgid "" "I will be putting together better resources for researchers interested in I2P,\n" "as well." msgstr "" #: i2p2www/blog/2019/08/30/foci.rst:44 msgid "" "I also had the good fortune to spend time with Mhatta, who is an I2P\n" "contributor, and to make connections for future funding. A huge thank you to\n" "the community builders I met in Tunis who I met again and who are offering so\n" "much support to the project. This has been an exciting year so far, and I2P has\n" "so much work to do. Please consider donating your time or funding the project\n" "as it needs to scale quickly to new challenges." msgstr "" #: i2p2www/blog/2019/08/30/foci.rst:53 msgid "" "If you have an opportunity to, you can read the full report Measuring I2P\n" "Censorship at a Global Scale here\n" "https://www.usenix.org/conference/foci19/presentation/hoang" msgstr "" #: i2p2www/blog/2019/08/30/foci.rst:59 msgid "" "Another great workshop in the measurements workshop was On the Importance of\n" "Encrypted-SNI (ESNI) to Censorship Circumvention\n" "https://www.usenix.org/conference/foci19/presentation/chai" msgstr "" #: i2p2www/blog/2019/08/30/foci.rst:65 msgid "" "There are so many great workshops that I attended - anyone who would like too\n" "can access the program and related materials here:\n" "https://www.usenix.org/conference/foci19/workshop-program" msgstr "" #: i2p2www/blog/2019/08/30/foci.rst:71 msgid "" "I will be attending Our Networks in Toronto next month https://ournetworks.ca/\n" "- and so should you! The program can be viewed here\n" "https://ournetworks.ca/program/" msgstr "" #: i2p2www/blog/2019/08/30/freedom.rst:2 i2p2www/blog/2019/08/30/freedom.rst:9 #: i2p2www/blog/2019/08/30/freedom.rst:11 msgid "Internet Freedom Festival Trip Report" msgstr "" #: i2p2www/blog/2019/08/30/freedom.rst:14 msgid "" "This was my first time attending IFF, and what a great experience for I2P this\n" "was! I met with human rights defenders, people who work on censorship metrics,\n" "and of course UX and security professionals." msgstr "" #: i2p2www/blog/2019/08/30/freedom.rst:20 msgid "" "My goal was to connect with people to further support I2P’s UX overhaul,\n" "keeping in mind security and UX considerations for frontline workers. As it was\n" "pointed out to me, people see I2P as a very important and powerful resource to\n" "circumvent censorship and support safe communication, however the interface\n" "suffers from some usability concerns. People were happy with our initial steps\n" "to make first time users have a better experience, such as our set up wizard\n" "and bandwidth detection tool. I also received positive reviews on our changes\n" "to the website and /home icons. It was very encouraging to hear directly from\n" "the community that small changes we have made are in the right direction." msgstr "" #: i2p2www/blog/2019/08/30/freedom.rst:32 msgid "" "Things like having configuration happen out of the box and not having to put\n" "people in the position where they need to rely on reading so much documentation\n" "or chasing documentation were discussed. Also, improved documentation for\n" "setting up outproxies and and site mirroring were requested and suggested.\n" "Please see Mikal’s very good instructions on setting up an I2P outproxy that\n" "came out of the suggestions this week —\n" "https://0xcc.re/howto-setup-an-i2p-outproxy/. Another suggestion was to make\n" "bug reporting easier." msgstr "" #: i2p2www/blog/2019/08/30/freedom.rst:43 msgid "" "To this point, I truly hope that the project will secure resources to continue\n" "the improvements to its usability that it requires to meet the growing demand\n" "for I2P services. It is humbling to to be working with such talented people and\n" "to be able to work together with our community during a time when people all\n" "over the globe need all of the privacy protecting resources we as people who\n" "develop, design and educate can offer." msgstr "" #: i2p2www/blog/2019/08/30/rights.rst:2 i2p2www/blog/2019/08/30/rights.rst:9 #: i2p2www/blog/2019/08/30/rights.rst:11 msgid "RightsCon Trip Report" msgstr "" #: i2p2www/blog/2019/08/30/rights.rst:14 msgid "" "The messages from activists in Syria during the Access No\\_! session on the\n" "first day were deeply moving and really drove home why I work in digital\n" "rights. We listened to the experiences of activists who are unable to travel\n" "due to lack of status, documentation and active conflict. For these people\n" "“the internet is the only passport (they) carry.” Human rights defenders\n" "spoke of the importance of digital training to keep people protected when they\n" "are communicating with family inside of the country, as well as with family and\n" "friends who have left. They had created digital clinics to show people how to\n" "use services securely, for instance, how to use features like Signal’s\n" "disappearing messages so that those messages could not be used against them\n" "when devices are searched at security check points. Continuing to pursue\n" "education was also very important, the internet being relied on to access\n" "resources." msgstr "" #: i2p2www/blog/2019/08/30/rights.rst:30 msgid "" "The following days we met with people who had both questions about I2P and\n" "suggestions for potential use cases. We also discussed overhauling the project\n" "documentation for threat models, improving guides for users with little\n" "technical background, and ensuring that these guides are easily translatable. I\n" "made a note that I should go through the proposals and connect then to human\n" "use cases and solutions. This will be part of the projects’ continued effort\n" "to improve its user guides and onboarding." msgstr "" #: i2p2www/blog/2019/08/30/rights.rst:40 msgid "" "The opportunity to meet face to face with people who are using I2P and have\n" "successfully used it to circumvent internet blockages was inspiring. As the\n" "project has began working on its own browser and is examining outproxy\n" "packaging, it needs as much feedback and testing as possible to create secure\n" "and frictionless experiences for people. Also, the I2P network needs more\n" "hosted content and mirrored sites in order to expand resources for its users." msgstr "" #: i2p2www/blog/2019/10/05/ournetworks-idk.rst:2 #: i2p2www/blog/2019/10/05/ournetworks-idk.rst:9 msgid "Our Networks Trip Report- idk" msgstr "" #: i2p2www/blog/2019/10/05/ournetworks-idk.rst:11 msgid "Our Networks Trip Report" msgstr "" #: i2p2www/blog/2019/10/05/ournetworks-idk.rst:14 msgid "" "The weekend of September 20th I traveled to Toronto to meet with Sadie to take\n" "part in the Our Networks conference. The Our Networks conference encompasses a\n" "wide variety of topic including many peer-to-peer technologies with an eye\n" "toward their potential to make the world a better place." msgstr "" #: i2p2www/blog/2019/10/05/ournetworks-idk.rst:21 msgid "" "The conference was fascinating, full of very smart people working on everything\n" "from physical mesh networks to the distributed web to, of course, anonymity. We\n" "got to talk to some great people from Tor, Protocol Labs, Parity Labs, the Dat\n" "Project, as well as a variety of artists and social scientists. Lots of fun too,\n" "and a great environment. Dat in particular presents some pretty cool\n" "opportunities for future co-operation I think." msgstr "" #: i2p2www/blog/2019/10/05/ournetworks-idk.rst:30 msgid "" "I hadn't planned on giving a talk, but we were having so much fun that when\n" "we were asked, Sadie and I put something together and I gave a quick lightning\n" "talk about I2P and how it's design choices are relevant to Peer-to-Peer\n" "application development. The talk was recorded and when the video becomes\n" "available, I'll make sure to add it to this blog. Next year, I'll have some\n" "submissions for their Zine Library about I2P." msgstr "" #: i2p2www/blog/2019/10/05/ournetworks-idk.rst:39 msgid "" "Besides that, I really enjoyed my time visiting Toronto, it was a great place\n" "to visit." msgstr "" #: i2p2www/blog/2019/10/22/0.9.43-Release.rst:2 msgid "0.9.43 Release" msgstr "" #: i2p2www/blog/2019/10/22/0.9.43-Release.rst:9 msgid "0.9.43 with bug fixes" msgstr "0.9.43 包含了错误修复" #: i2p2www/blog/2019/10/22/0.9.43-Release.rst:16 msgid "" "In the 0.9.43 release, we continue work on stronger security and privacy features and performance improvements.\n" "Our implementation of the new leaseset specification (LS2) is now complete.\n" "We are beginning our implementation of stronger and faster end-to-end encryption (proposal 144) for a future release.\n" "Several IPv6 address detection issues have been fixed, and there of course are several other bug fixes." msgstr "在 0.9.43 发布版本中，我们继续致力于更强的安全性，隐私功能和性能提升。我们的新的租契集规范 (LS2) 实现现在已完成。我们正在开始用于未来发布版本的更强大快速的端到端加密（提案 144）实现。一些 IPv6 探测问题已修复，当然还有一些其他错误修复。" #: i2p2www/blog/2019/10/22/0.9.43-Release.rst:33 msgid "Console setup wizard improvements" msgstr "" #: i2p2www/blog/2019/10/22/0.9.43-Release.rst:34 msgid "Tunnel wizard simplification" msgstr "" #: i2p2www/blog/2019/10/22/0.9.43-Release.rst:35 msgid "New I2CP BlindingInfo message for LS2" msgstr "" #: i2p2www/blog/2019/10/22/0.9.43-Release.rst:36 msgid "New proxy page to enter encrypted leaseset credentials" msgstr "" #: i2p2www/blog/2019/10/22/0.9.43-Release.rst:41 msgid "Fix tunnel SSL wizard" msgstr "" #: i2p2www/blog/2019/10/22/0.9.43-Release.rst:42 msgid "Fixes for SusiMail sent and drafts folder page" msgstr "" #: i2p2www/blog/2019/10/22/0.9.43-Release.rst:43 msgid "Detect IPv6 address changes" msgstr "" #: i2p2www/blog/2019/10/22/0.9.43-Release.rst:44 msgid "Fix detection and handling of IPv6 firewalled" msgstr "" #: i2p2www/blog/2019/10/22/0.9.43-Release.rst:45 msgid "Fix manual reseed from URL" msgstr "" #: i2p2www/blog/2019/10/22/0.9.43-Release.rst:50 msgid "i2ptunnel support for quoted custom options" msgstr "" #: i2p2www/blog/2019/10/22/0.9.43-Release.rst:51 msgid "" "i2psnark now starts with reduced tunnel count then increases as necessary" msgstr "" #: i2p2www/blog/2019/10/22/0.9.43-Release.rst:52 msgid "NTCP performance improvement" msgstr "" #: i2p2www/blog/2019/10/22/0.9.43-Release.rst:53 msgid "Refactor and speed up tunnel AES processing" msgstr "" #: i2p2www/blog/2019/10/22/0.9.43-Release.rst:54 msgid "Preliminary support for Servlet 3.0 webapps" msgstr "" #: i2p2www/blog/2019/10/22/0.9.43-Release.rst:55 msgid "Standardize date/time formatting in console" msgstr "" #: i2p2www/blog/2019/10/25/research-highlights.rst:2 msgid "Highlighting Research" msgstr "" #: i2p2www/blog/2019/10/25/research-highlights.rst:9 msgid "" "An Empirical Study of the I2P Anonymity Network and its Censorship " "Resistance" msgstr "" #: i2p2www/blog/2019/10/25/research-highlights.rst:11 msgid "" "Highlighting Research - An Empirical Study of the I2P Anonymity Network and " "its Censorship Resistance" msgstr "" #: i2p2www/blog/2019/10/25/research-highlights.rst:16 msgid "" "The following blog post is authored by Information Controls Fellow Hoàng Nguyên\n" "Phong. As an ICFP fellow, Phong's research focused on analyzing different\n" "aspects of the I2P network, a privacy-enhancing Internet tool that can be used\n" "to access online content over an anonymity-enhancing network helpful in\n" "circumventing state-imposed censorship. Working with his host organization, the\n" "University of Massachusetts Amherst, Phong studied the I2P network's censorship\n" "resilience, including identifying what blocking methods a state censor might use\n" "to inhibit access to I2P and investigating potential solutions to make I2P more\n" "resistant to such blockage." msgstr "" #: i2p2www/blog/2019/10/25/research-highlights.rst:28 msgid "" "Phong found blocking attempts on the I2P network (specifically via DNS\n" "poisoning, SNI-based blocking, TCP packet injection, and page-specific blocks)\n" "emanating from five countries: China, Oman, Qatar, Iran, and Kuwait. Phong\n" "posits that because the blocks are usually imposed on the I2P download page and\n" "reseed servers, such blocking could be mitigated by hosting download links to\n" "this content on large cloud service providers - raising the collateral cost of\n" "blocking. Phong also built a metrics portal for the platform so that researchers\n" "and others can better understand who is using I2P, finding that there are about\n" "20,000 relays in the network on a daily basis." msgstr "" #: i2p2www/blog/2019/10/25/research-highlights.rst:40 msgid "(Excerpt taken from OTF blog post)" msgstr "" #: i2p2www/blog/2019/10/25/research-highlights.rst:48 msgid "The research paper is also available here:" msgstr "" #: i2p2www/blog/2019/10/25/research-highlights.rst:55 msgid "" "We thank Phong and his collaborators for their excellent study as we move to\n" "address the issues that were identified. It's exciting to see more academic\n" "study of I2P and are excited to keep working with him." msgstr "" #: i2p2www/blog/2019/12/01/0.9.44-Release.rst:2 msgid "0.9.44 Release" msgstr "" #: i2p2www/blog/2019/12/01/0.9.44-Release.rst:9 msgid "0.9.44 with bug fixes" msgstr "0.9.44 包含了错误修复" #: i2p2www/blog/2019/12/01/0.9.44-Release.rst:16 msgid "" "0.9.44 contains an important fix for a denial of service issue in hidden services handling of new encryption types.\n" "All users should update as soon as possible." msgstr "0.9.44 包含一个隐藏服务处理新加密类型中拒绝服务问题的重要修复。所有用户都应尽快更新。" #: i2p2www/blog/2019/12/01/0.9.44-Release.rst:21 msgid "" "The release includes initial support for new end-to-end encryption (proposal 144).\n" "Work continues on this project, and it is not yet ready for use.\n" "There are changes to the console home page, and new embedded HTML5 media players in i2psnark.\n" "Additional fixes for firewalled IPv6 networks are included.\n" "Tunnel build fixes should result in faster startup for some users." msgstr "发布版本包含新端到端加密的初始支持（提案 144）。此项目上的工作仍在继续，尚未准备好使用。有一些控制台主页的更改，及 i2psnark 中新的嵌入式 HTML5 媒体播放器。包含对受到防火墙限制的 IPv6 网络的额外修复。隧道建立的修复应当使得一些用户更快的启动。" #: i2p2www/blog/2019/12/01/0.9.44-Release.rst:39 msgid "Console home page changes" msgstr "" #: i2p2www/blog/2019/12/01/0.9.44-Release.rst:40 msgid "Initial code for new encryption (proposal 144)" msgstr "" #: i2p2www/blog/2019/12/01/0.9.44-Release.rst:41 msgid "Router changes to support multiple encryption types" msgstr "" #: i2p2www/blog/2019/12/01/0.9.44-Release.rst:42 msgid "HTML5 players in i2psnark" msgstr "" #: i2p2www/blog/2019/12/01/0.9.44-Release.rst:43 msgid "Audio playlist in i2psnark" msgstr "" #: i2p2www/blog/2019/12/01/0.9.44-Release.rst:44 msgid "Change Windows data location to %LOCALAPPDIR% (new installs only)" msgstr "" #: i2p2www/blog/2019/12/01/0.9.44-Release.rst:50 msgid "Fix AppArmor config for Java 11" msgstr "" #: i2p2www/blog/2019/12/01/0.9.44-Release.rst:51 msgid "Fix handling of unsupported encryption types" msgstr "" #: i2p2www/blog/2019/12/01/0.9.44-Release.rst:52 msgid "IPv6 firewalled fixes" msgstr "" #: i2p2www/blog/2019/12/01/0.9.44-Release.rst:53 msgid "Fix long stop delay for some plugins" msgstr "" #: i2p2www/blog/2019/12/01/0.9.44-Release.rst:54 msgid "Fix custom icons for some plugins" msgstr "" #: i2p2www/blog/2019/12/01/0.9.44-Release.rst:55 msgid "Fix exploratory tunnel build issues causing long startup times" msgstr "" #: i2p2www/blog/2019/12/01/0.9.44-Release.rst:56 msgid "Prevent multiple zero-hop tunnels in a pool" msgstr "" #: i2p2www/blog/2019/12/01/0.9.44-Release.rst:57 msgid "Recognize gettext 0.20 in build scripts" msgstr "" #: i2p2www/blog/2019/12/01/0.9.44-Release.rst:63 msgid "Don't check clove ID in Bloom filter" msgstr "" #: i2p2www/blog/2019/12/01/0.9.44-Release.rst:64 msgid "Reduce SessionTag memory usage" msgstr "" #: i2p2www/blog/2019/12/01/0.9.44-Release.rst:65 msgid "Change default sig type to EdDSA for Android" msgstr "" #: i2p2www/blog/2020/02/25/0.9.45-Release.rst:2 msgid "0.9.45 Release" msgstr "" #: i2p2www/blog/2020/02/25/0.9.45-Release.rst:9 msgid "0.9.45 with bug fixes" msgstr "0.9.45 包含了错误修复" #: i2p2www/blog/2020/02/25/0.9.45-Release.rst:16 msgid "" "0.9.45 contains important fixes for hidden mode and the bandwidth tester.\n" "There's an update to the console dark theme.\n" "We continue work on improving performance and the development of new end-to-end encryption (proposal 144)." msgstr "0.9.45包含了隐身模式和带宽测试的重要修复。\n这是一个对于控制台暗色主题的更新。\n我们继续努力提高性能并开发新的端到端加密(提案 144)。" #: i2p2www/blog/2020/02/25/0.9.45-Release.rst:32 msgid "Dark theme improvements" msgstr "" #: i2p2www/blog/2020/02/25/0.9.45-Release.rst:33 msgid "Console icon changes" msgstr "" #: i2p2www/blog/2020/02/25/0.9.45-Release.rst:34 msgid "" "Move some translations from console to router and core for embedded uses" msgstr "" #: i2p2www/blog/2020/02/25/0.9.45-Release.rst:37 msgid "i2psnark HTML5 preview player for partial files" msgstr "" #: i2p2www/blog/2020/02/25/0.9.45-Release.rst:43 msgid "Numerous bandwidth test fixes" msgstr "" #: i2p2www/blog/2020/02/25/0.9.45-Release.rst:44 msgid "Hidden mode fixes to prevent losing peers" msgstr "" #: i2p2www/blog/2020/02/25/0.9.45-Release.rst:45 msgid "Hebrew translation fixes" msgstr "" #: i2p2www/blog/2020/02/25/0.9.45-Release.rst:50 msgid "Content Security Policy improvements" msgstr "" #: i2p2www/blog/2020/02/25/0.9.45-Release.rst:51 msgid "SSU extend timeout for large messages" msgstr "" #: i2p2www/blog/2020/02/25/0.9.45-Release.rst:52 msgid "ECIES-X25519 continued development and fixes" msgstr "" #: i2p2www/blog/2020/02/25/0.9.45-Release.rst:53 msgid "Cancel timeout jobs on message reply" msgstr "" #: i2p2www/blog/2020/02/25/0.9.45-Release.rst:54 msgid "Add SSL and SSL redirect support to EepGet" msgstr "" #: i2p2www/blog/2020/02/25/0.9.45-Release.rst:56 msgid "Update JBigI library" msgstr "" #: i2p2www/blog/2020/03/06/git-over-i2p.rst:2 msgid "Git over I2P for Users" msgstr "" #: i2p2www/blog/2020/03/06/git-over-i2p.rst:8 msgid "Git over I2P" msgstr "" #: i2p2www/blog/2020/03/06/git-over-i2p.rst:10 msgid "" "Tutorial for setting up git access through an I2P Tunnel. This tunnel\n" "will act as your access point to a single git service on I2P. It is part of the\n" "overall effort to transition I2P from monotone to Git." msgstr "" #: i2p2www/blog/2020/03/06/git-over-i2p.rst:16 msgid "" "Before anything else: Know the capabilities the service offers to the public" msgstr "" #: i2p2www/blog/2020/03/06/git-over-i2p.rst:19 msgid "" "Depending on how the git service is configured, it may or may not offer\n" "all services on the same address. In the case of git.idk.i2p, there is a\n" "public HTTP URL, and an SSH URL(g6u4vqiuy6bdc3dbu6a7gmi3ip45sqwgtbgrr6uupqaaqfyztrka.b32.i2p) to configure for your Git SSH client. Either\n" "can be used to push or pull, but SSH is recommended." msgstr "" #: i2p2www/blog/2020/03/06/git-over-i2p.rst:26 msgid "First: Set up an account at a Git service" msgstr "" #: i2p2www/blog/2020/03/06/git-over-i2p.rst:29 msgid "" "To create your repositories on a remote git service, sign up for a user\n" "account at that service. Of course it’s also possible to create\n" "repositories locally and push them to a remote git service, but most\n" "will require an account and for you to create a space for the repository\n" "on the server. Gitlab has a very simple sign-up form:" msgstr "" #: i2p2www/blog/2020/03/06/git-over-i2p.rst:43 msgid "Second: Create a project to test with" msgstr "" #: i2p2www/blog/2020/03/06/git-over-i2p.rst:46 msgid "" "To make sure the setup process works, it helps to make a repository to\n" "test with from the server, and for the sake of this tutorial, we’re\n" "going to use a fork of the I2P router. First, browse to the\n" "i2p-hackers/i2p.i2p repository:" msgstr "" #: i2p2www/blog/2020/03/06/git-over-i2p.rst:61 msgid "Then, fork it to your account." msgstr "" #: i2p2www/blog/2020/03/06/git-over-i2p.rst:73 msgid "Third: Set up your git client tunnel" msgstr "" #: i2p2www/blog/2020/03/06/git-over-i2p.rst:76 msgid "" "To have read-write access to my server, you’ll need to set up a tunnel\n" "for your SSH client. As an example, we’re going to use the HTTP tunnel\n" "instead, but if all you need is read-only, HTTP/S cloning, then you can\n" "skip all this and just use the http_proxy environment variable to\n" "configure git to use the pre-configured I2P HTTP Proxy. For example:" msgstr "" #: i2p2www/blog/2020/03/06/git-over-i2p.rst:97 msgid "" "Then, add the address you will be pushing and pulling from. Note that\n" "this example address is for Read-Only HTTP-over-I2P clones, if your\n" "admin does not allow the git HTTP(Smart HTTP) protocol, then you will\n" "need to get the SSH clone base32 from them. Use this Base32 to connect the\n" "client tunnel to the Git SSH service: **g6u4vqiuy6bdc3dbu6a7gmi3ip45sqwgtbgrr6uupqaaqfyztrka.b32.i2p**" msgstr "" #: i2p2www/blog/2020/03/06/git-over-i2p.rst:109 msgid "Pick a port to forward the I2P service to locally." msgstr "" #: i2p2www/blog/2020/03/06/git-over-i2p.rst:117 msgid "" "I use it alot, so I start my client tunnel automatically, but it’s up to\n" "you." msgstr "" #: i2p2www/blog/2020/03/06/git-over-i2p.rst:126 msgid "When you’re all done, it should look alot like this." msgstr "" #: i2p2www/blog/2020/03/06/git-over-i2p.rst:134 msgid "Fourth: Attempt a clone" msgstr "" #: i2p2www/blog/2020/03/06/git-over-i2p.rst:137 msgid "Now your tunnel is all set up, you can attempt a clone over SSH." msgstr "" #: i2p2www/blog/2020/03/06/git-over-i2p.rst:146 msgid "" "You might get an error where the remote end hangs up unexpectedly.\n" "Unfortunately git still doesn’t support resumable cloning. Until it\n" "does, there are a couple fairly easy ways to handle this. The first and\n" "easiest is to try and clone to a shallow depth:" msgstr "" #: i2p2www/blog/2020/03/06/git-over-i2p.rst:158 msgid "" "Once you’ve performed a shallow clone, you can fetch the rest resumably\n" "by changing to the repo directory and running:" msgstr "" #: i2p2www/blog/2020/03/06/git-over-i2p.rst:167 msgid "" "At this point, you still don’t have all your branches yet. You can get\n" "them by running the following commands:" msgstr "" #: i2p2www/blog/2020/03/06/git-over-i2p.rst:177 msgid "" "Which tells git to alter the repository configuration so that fetching\n" "from origin fetches all branches." msgstr "" #: i2p2www/blog/2020/03/06/git-over-i2p.rst:182 msgid "" "If that doesn’t work, you can try opening the tunnel configuration menu\n" "and adding some backup tunnels." msgstr "" #: i2p2www/blog/2020/03/06/git-over-i2p.rst:193 msgid "" "If that doesn’t work, then the next easy thing to try is to decrease the\n" "tunnel length. Don’t do this if you believe you are at risk of your\n" "code-contribution activity being de-anonymized by a well-resourced\n" "attacker seeking to run many malicious nodes and control your whole\n" "path. If that sounds unlikely to you then you can probably do it safely." msgstr "" #: i2p2www/blog/2020/03/06/git-over-i2p.rst:207 msgid "Suggested Workflow for Developers!" msgstr "" #: i2p2www/blog/2020/03/06/git-over-i2p.rst:210 msgid "" "Revision control can make your life easier, but it works best if you use\n" "it well! In light of this, we strongly suggest a fork-first,\n" "feature-branch workflow as many are familiar with from Github. In such a\n" "workflow, the master branch is used as a sort of “Trunk” for updates and\n" "is never touched by the programmmer, instead, all changes to the master\n" "are merged from branches. In order to do set up your workspace for this,\n" "take the following steps:" msgstr "" #: i2p2www/blog/2020/03/06/git-over-i2p.rst:220 msgid "" "**Never make changes to the Master Branch**. You will be using the\n" " master branch to periodially obtain updates to the official source\n" " code. All changes should be made in feature branches." msgstr "" #: i2p2www/blog/2020/03/06/git-over-i2p.rst:224 msgid "" "Set up a second remote in your local repository using the upstream\n" " source code." msgstr "" #: i2p2www/blog/2020/03/06/git-over-i2p.rst:231 msgid "Pull in any upstream changes on your current master:" msgstr "" #: i2p2www/blog/2020/03/06/git-over-i2p.rst:237 msgid "" "Before making any changes to the source code, check out a new feature\n" " branch to develop on:" msgstr "" #: i2p2www/blog/2020/03/06/git-over-i2p.rst:244 msgid "" "When you’re done with your changes, commit them and push them to your\n" " branch" msgstr "" #: i2p2www/blog/2020/03/06/git-over-i2p.rst:252 msgid "" "Submit a merge request. When the merge request is approved and\n" " brought into the upstream master, check out the master locally and\n" " pull in the changes:" msgstr "" #: i2p2www/blog/2020/03/06/git-over-i2p.rst:261 msgid "" "Whenever a change to the upstream master(i2p-hackers/i2p.i2p) is\n" " made, you can update your master code using this procedure as well." msgstr "" #: i2p2www/blog/2020/03/16/gitlab-over-i2p.rst:1 msgid "Gitlab over I2P Setup" msgstr "" #: i2p2www/blog/2020/03/16/gitlab-over-i2p.rst:7 msgid "" "Mirror I2P Git repositories and Bridge Clearnet repositories for others." msgstr "" #: i2p2www/blog/2020/03/16/gitlab-over-i2p.rst:9 msgid "" "This is the setup process I use for configuring Gitlab and I2P, with\n" "Docker in place to manage the service itself. Gitlab is very easy to\n" "host on I2P in this fashion, it can be administered by one person\n" "without much difficulty. In my configuration, I use a Debian VM to host\n" "docker containers and an I2P router, on a Debian Host system, however,\n" "this may be more than necessary for some people. These instructions\n" "should work on any Debian-based system, regardless of whether it is in a\n" "VM or not, and should easily translate to any system where Docker and an\n" "I2P router are available. This guide starts at Docker and does not\n" "assume any VM underneath." msgstr "" #: i2p2www/blog/2020/03/16/gitlab-over-i2p.rst:22 msgid "Dependencies and Docker" msgstr "" #: i2p2www/blog/2020/03/16/gitlab-over-i2p.rst:25 msgid "" "Because Gitlab runs in a container, we only need to install the\n" "dependencies required for the container on our main system.\n" "Conveniently, you can install everything you need with:" msgstr "" #: i2p2www/blog/2020/03/16/gitlab-over-i2p.rst:35 msgid "" "on an otherwise unmodified Debian system, or if you have added Docker’s\n" "own “Community” Debian repository, you may use:" msgstr "" #: i2p2www/blog/2020/03/16/gitlab-over-i2p.rst:44 msgid "instead." msgstr "" #: i2p2www/blog/2020/03/16/gitlab-over-i2p.rst:49 msgid "Fetch the Docker Containers" msgstr "" #: i2p2www/blog/2020/03/16/gitlab-over-i2p.rst:52 msgid "" "Once you have docker installed, you can fetch the docker containers\n" "required for gitlab. *Don’t run them yet.*" msgstr "" #: i2p2www/blog/2020/03/16/gitlab-over-i2p.rst:61 msgid "" "For those who are concerned, the gitlab-ce Docker image is built using\n" "only Ubuntu Docker images as a parent, which are built from scratch\n" "images. Since there are no third-party images involved here, updates\n" "should come as soon as they are available in the host images. To review\n" "the Dockerfile for yourself, visit the `Gitlab source\n" "code `__." msgstr "" #: i2p2www/blog/2020/03/16/gitlab-over-i2p.rst:70 msgid "" "Set up an I2P HTTP Proxy for Gitlab to use(Important information, optional " "steps)" msgstr "" #: i2p2www/blog/2020/03/16/gitlab-over-i2p.rst:73 msgid "" "Gitlab servers inside of I2P can be run with or without the ability to\n" "interact with servers on the internet outside of I2P. In the case where\n" "the Gitlab server is *not allowed* to interact with servers outside of\n" "I2P, they cannot be de-anonymized by cloning a git repository from a git\n" "server on the internet outside of I2P. They can, however, export and\n" "mirror repositories from other git services inside of I2P." msgstr "" #: i2p2www/blog/2020/03/16/gitlab-over-i2p.rst:82 msgid "" "In the case where the Gitlab server is *allowed* to interact with\n" "servers outside of I2P, it can act as a “Bridge” for the users, who can\n" "use it to mirror content outside I2P to an I2P-accessible source,\n" "however it *is not anonymous* in this case. Git services on the\n" "non-anonymous internet will be connected to directly." msgstr "" #: i2p2www/blog/2020/03/16/gitlab-over-i2p.rst:90 msgid "" "**If you want to have a bridged, non-anonymous Gitlab instance with\n" "access to** **web repositories,** no further modification is necessary." msgstr "" #: i2p2www/blog/2020/03/16/gitlab-over-i2p.rst:95 msgid "" "**If you want to have an I2P-Only Gitlab instance with no access to\n" "Web-Only** **Repositories**, you will need to configure Gitlab to use an\n" "I2P HTTP Proxy. Since the default I2P HTTP proxy only listens on\n" "``127.0.0.1``, you will need to set up a new one for Docker that listens\n" "on the Host/Gateway address of the Docker network, which is usually\n" "``172.17.0.1``. I configure mine on port ``4446``." msgstr "" #: i2p2www/blog/2020/03/16/gitlab-over-i2p.rst:104 msgid "Start the Container Locally" msgstr "" #: i2p2www/blog/2020/03/16/gitlab-over-i2p.rst:107 msgid "" "Once you have that set up, you can start the container and publish your\n" "Gitlab instance locally." msgstr "" #: i2p2www/blog/2020/03/16/gitlab-over-i2p.rst:124 msgid "" "Visit your Local Gitlab instance and set up your admin account. Choose a\n" "strong password, and configure user account limits to match your\n" "resources." msgstr "" #: i2p2www/blog/2020/03/16/gitlab-over-i2p.rst:130 msgid "" "Modify gitlab.rb(Optional, but a good idea for “Bridged non-anonymous” " "hosts)" msgstr "" #: i2p2www/blog/2020/03/16/gitlab-over-i2p.rst:133 msgid "" "It’s also possible to apply your HTTP Proxy settings in a more granular\n" "way, so that you can only allow users to mirror repositories from the\n" "domains that you choose. Since the domain is presumably operated by an\n" "organization, you can use this to ensure that repositories that are\n" "mirrorable follow a reasonable set of policies. After all, there is far\n" "more abusive content on the non-anonymous internet than there is on I2P,\n" "we wouldn’t want to make it too easy to introduce abusive content from\n" "such a nefarious place." msgstr "" #: i2p2www/blog/2020/03/16/gitlab-over-i2p.rst:144 msgid "" "Add the following lines to your gitlab.rb file inside the\n" "/src/gitlab/config container. These settings will take effect when you\n" "restart in a moment." msgstr "" #: i2p2www/blog/2020/03/16/gitlab-over-i2p.rst:169 msgid "Set up your Service tunnels and sign up for a Hostname" msgstr "" #: i2p2www/blog/2020/03/16/gitlab-over-i2p.rst:172 msgid "" "Once you have Gitlab set up locally, go to the I2P Router console. You\n" "will need to set up two server tunnels, one leading to the Gitlab\n" "web(HTTP) interface on TCP port 8080, and one to the Gitlab SSH\n" "interface on TCP Port 8022." msgstr "" #: i2p2www/blog/2020/03/16/gitlab-over-i2p.rst:179 msgid "Gitlab Web(HTTP) Interface" msgstr "" #: i2p2www/blog/2020/03/16/gitlab-over-i2p.rst:182 msgid "" "For the Web interface, use an “HTTP” server tunnel. From\n" "http://127.0.0.1:7657/i2ptunnelmgr launch the “New Tunnel Wizard” and\n" "enter the following values at each step:" msgstr "" #: i2p2www/blog/2020/03/16/gitlab-over-i2p.rst:188 #: i2p2www/blog/2020/03/16/gitlab-over-i2p.rst:221 msgid "Select “Server Tunnel”" msgstr "" #: i2p2www/blog/2020/03/16/gitlab-over-i2p.rst:189 msgid "Select “HTTP Server”" msgstr "" #: i2p2www/blog/2020/03/16/gitlab-over-i2p.rst:190 msgid "Fill in “Gitlab Web Service” or otherwise describe the tunnel" msgstr "" #: i2p2www/blog/2020/03/16/gitlab-over-i2p.rst:191 msgid "Fill in ``127.0.0.1`` for the host and ``8080`` for the port." msgstr "" #: i2p2www/blog/2020/03/16/gitlab-over-i2p.rst:192 #: i2p2www/blog/2020/03/16/gitlab-over-i2p.rst:225 msgid "Select “Automatically start tunnel when Router Starts”" msgstr "" #: i2p2www/blog/2020/03/16/gitlab-over-i2p.rst:193 #: i2p2www/blog/2020/03/16/gitlab-over-i2p.rst:226 msgid "Confirm your selections." msgstr "" #: i2p2www/blog/2020/03/16/gitlab-over-i2p.rst:195 msgid "Register a Hostname(Optional)" msgstr "" #: i2p2www/blog/2020/03/16/gitlab-over-i2p.rst:198 msgid "" "Web services on I2P can register hostnames for themselves by providing\n" "an authentication string to a jump service provider like\n" "`stats.i2p `__. To do this, open the\n" "http://127.0.0.1:7657/i2ptunnelmgr again and click on the “Gitlab Web\n" "Service” item you just set up. Scroll to the bottom of the “Edit Server\n" "Settings” section and click Registration Authentication. Copy the field\n" "that says “Authentication for adding Hostname” and visit\n" "`stats.i2p `__ to add your hostname.\n" "Note that if you want to use a subdomain(Like git.idk.i2p) then you will\n" "have to use the correct authentication string for your subdomain, which\n" "is a little bit more complicated and merits it’s own instructions." msgstr "" #: i2p2www/blog/2020/03/16/gitlab-over-i2p.rst:212 msgid "Gitlab SSH Interface" msgstr "" #: i2p2www/blog/2020/03/16/gitlab-over-i2p.rst:215 msgid "" "For the SSH interface, use a “Standard” server tunnel. From\n" "http://127.0.0.1:7657/i2ptunnelmgr launch the “New Tunnel Wizard” and\n" "enter the following values at each step:" msgstr "" #: i2p2www/blog/2020/03/16/gitlab-over-i2p.rst:222 msgid "Select “Standard Server”" msgstr "" #: i2p2www/blog/2020/03/16/gitlab-over-i2p.rst:223 msgid "Fill in “Gitlab SSH Service” or otherwise describe the tunnel" msgstr "" #: i2p2www/blog/2020/03/16/gitlab-over-i2p.rst:224 msgid "Fill in ``127.0.0.1`` for the host and ``8022`` for the port." msgstr "" #: i2p2www/blog/2020/03/16/gitlab-over-i2p.rst:228 msgid "Re-start the Gitlab Service with the new Hostname" msgstr "" #: i2p2www/blog/2020/03/16/gitlab-over-i2p.rst:231 msgid "" "Finally, if you either modified ``gitlab.rb`` or you registered a\n" "hostname, you will need to re-start the gitlab service for the settings\n" "to take effect." msgstr "" #: i2p2www/blog/2020/03/18/bundle-over-torrent.rst:1 msgid "Using a git bundle to fetch the I2P source code" msgstr "" #: i2p2www/blog/2020/03/18/bundle-over-torrent.rst:7 msgid "Download the I2P Source code via Bittorrent." msgstr "" #: i2p2www/blog/2020/03/18/bundle-over-torrent.rst:9 msgid "" "Cloning large software repositories over I2P can be difficult, and using\n" "git can sometimes make this harder. Fortunately, it can also sometimes\n" "make it easier. Git has a ``git bundle`` command which can be used to\n" "turn a git repository into a file which git can then clone, fetch, or\n" "import from a location on your local disk. By combining this capability\n" "with bittorrent downloads, we can solve our remaining problems with\n" "``git clone``." msgstr "" #: i2p2www/blog/2020/03/18/bundle-over-torrent.rst:17 msgid "Before you Start" msgstr "" #: i2p2www/blog/2020/03/18/bundle-over-torrent.rst:20 msgid "" "If you intend to generate a git bundle, you **must** already possess a\n" "full copy of the **git** repository, not the mtn repository. You can get\n" "it from github or from git.idk.i2p, but a shallow clone(a clone done to\n" "–depth=1) *will not* *work*. It will fail silently, creating what looks\n" "like a bundle, but when you try to clone it it will fail. If you are\n" "just retrieving a pre-generated git bundle, then this section does not\n" "apply to you." msgstr "" #: i2p2www/blog/2020/03/18/bundle-over-torrent.rst:28 msgid "Fetching I2P Source via Bittorrent" msgstr "" #: i2p2www/blog/2020/03/18/bundle-over-torrent.rst:31 #, python-format msgid "" "Someone will need to supply you with a torrent file or a magnet link\n" "corresponding to an existing ``git bundle`` that they have already\n" "generated for you. A recent, correctly-generated bundle of the mainline\n" "i2p.i2p source code as-of Wednesday, March 18, 2020, can be found inside\n" "of I2P at my pastebin\n" "`paste.idk.i2p/f/4hq37i `__. You can also use a\n" "`magnet link `__,\n" "and if you're a BiglyBT user who wants to bridge the torrent, use \n" "`this magnet link instead `__\n" "to announce to clearnet trackers as well." msgstr "" #: i2p2www/blog/2020/03/18/bundle-over-torrent.rst:43 msgid "" "Once you have a bundle, you will need to use git to create a working\n" "repository from it. If you’re using GNU/Linux and i2psnark, the git\n" "bundle should be located in $HOME/.i2p/i2psnark or, as a service on\n" "Debian, /var/lib/i2p/i2p-config/i2psnark. If you are using BiglyBT on\n" "GNU/Linux, it is probably at “$HOME/BiglyBT Downloads/” instead. The\n" "examples here assume I2PSnark on GNU/Linux, if you use something else,\n" "replace the path to the bundle with the download directory preferred by\n" "your client and platform." msgstr "" #: i2p2www/blog/2020/03/18/bundle-over-torrent.rst:52 msgid "Using ``git clone``" msgstr "" #: i2p2www/blog/2020/03/18/bundle-over-torrent.rst:55 msgid "Cloning from a git bundle is easy, just:" msgstr "" #: i2p2www/blog/2020/03/18/bundle-over-torrent.rst:61 msgid "" "If you get the following error, try using git init and git fetch\n" "manually instead." msgstr "" #: i2p2www/blog/2020/03/18/bundle-over-torrent.rst:68 msgid "Using ``git init`` and ``git fetch``" msgstr "" #: i2p2www/blog/2020/03/18/bundle-over-torrent.rst:71 msgid "First, create an i2p.i2p directory to turn into a git repository." msgstr "" #: i2p2www/blog/2020/03/18/bundle-over-torrent.rst:77 msgid "Next, initialize an empty git repository to fetch changes back into." msgstr "" #: i2p2www/blog/2020/03/18/bundle-over-torrent.rst:84 msgid "Finally, fetch the repository from the bundle." msgstr "" #: i2p2www/blog/2020/03/18/bundle-over-torrent.rst:91 msgid "Replace the bundle remote with the upstream remote" msgstr "" #: i2p2www/blog/2020/03/18/bundle-over-torrent.rst:94 msgid "" "Now that you have a bundle, you can keep up with changes by setting the\n" "remote to the upstream repository source." msgstr "" #: i2p2www/blog/2020/03/18/bundle-over-torrent.rst:101 msgid "Generating a Bundle" msgstr "" #: i2p2www/blog/2020/03/18/bundle-over-torrent.rst:104 msgid "" "First, follow the `Git guide for Users `__ until you have a\n" "successfully ``--unshallow``\\ ed clone of clone of the i2p.i2p\n" "repository. If you already have a clone, make sure you run\n" "``git fetch --unshallow`` before you generate a torrent bundle." msgstr "" #: i2p2www/blog/2020/03/18/bundle-over-torrent.rst:109 msgid "Once you have that, simply run the corresponding ant target:" msgstr "" #: i2p2www/blog/2020/03/18/bundle-over-torrent.rst:115 msgid "" "and copy the resulting bundle into your I2PSnark downloads directory.\n" "For instance:" msgstr "" #: i2p2www/blog/2020/03/18/bundle-over-torrent.rst:122 msgid "" "In a minute or two, I2PSnark will pick up on the torrent. Click on the\n" "“Start” button to begin seeding the torrent." msgstr "" #: i2p2www/blog/2020/05/25/0.9.46-Release.rst:2 msgid "0.9.46 Release" msgstr "" #: i2p2www/blog/2020/05/25/0.9.46-Release.rst:9 msgid "0.9.46 with new ECIES Encryption" msgstr "" #: i2p2www/blog/2020/05/25/0.9.46-Release.rst:16 msgid "" "0.9.46 contains significant performance improvements in the streaming library.\n" "We have completed development of ECIES encryption (proposal 144) and there is now an option to enable it for testing." msgstr "0.9.46 包含 streaming 库显著的性能提升。\n我们已经完成了 ECIES 加密（提案144）的开发，现在可以选择启用它以进行测试。" #: i2p2www/blog/2020/05/25/0.9.46-Release.rst:21 msgid "" "Windows users only:\n" "This release fixes a local privilege escalation vulnerability\n" "which could be exploited by a local user that has the ability to run programs.\n" "Please apply the update as soon as possible.\n" "Thanks to Blaze Infosec for their responsible disclosure of the issue." msgstr "" #: i2p2www/blog/2020/05/25/0.9.46-Release.rst:29 msgid "" "This is the last release to support Java 7, Debian packages Wheezy and Stretch, and Ubuntu packages Precise and Trusty.\n" "Users on those platforms must upgrade to receive future I2P updates." msgstr "这是最后一个支持 Java 7、Debian 软件包 Wheezy 和 Stretch 以及 Ubuntu 软件包 Precise 和 Trusty 的发布。\n使用上述平台的用户务必升级以获得未来的 I2P 更新。" #: i2p2www/blog/2020/05/25/0.9.46-Release.rst:44 msgid "" "ECIES-X25519-AEAD-Ratchet encryption complete, ready for testing (proposal " "144)" msgstr "" #: i2p2www/blog/2020/05/25/0.9.46-Release.rst:45 msgid "Hidden Services Manager: Redesign edit pages" msgstr "" #: i2p2www/blog/2020/05/25/0.9.46-Release.rst:46 msgid "i2psnark: Fix marking torrents as BAD at startup" msgstr "" #: i2p2www/blog/2020/05/25/0.9.46-Release.rst:47 msgid "NetDB: Support ECIES replies to lookups (proposal 154)" msgstr "" #: i2p2www/blog/2020/05/25/0.9.46-Release.rst:48 msgid "RRD4J 3.5 replaces jrobin" msgstr "" #: i2p2www/blog/2020/05/25/0.9.46-Release.rst:49 msgid "Streaming performance improvments using Westwood+ congestion control" msgstr "" #: i2p2www/blog/2020/05/25/0.9.46-Release.rst:54 msgid "" "Hidden Services Manager: Fixes for changing shared client options, prevent " "changing certain options while tunnel is running" msgstr "" #: i2p2www/blog/2020/05/25/0.9.46-Release.rst:55 msgid "Reproducible build fix" msgstr "" #: i2p2www/blog/2020/05/25/0.9.46-Release.rst:56 msgid "Streaming: Multiple fixes" msgstr "" #: i2p2www/blog/2020/05/25/0.9.46-Release.rst:57 msgid "UPnP: Several fixes for changing interfaces and devices" msgstr "" #: i2p2www/blog/2020/05/25/0.9.46-Release.rst:58 msgid "Windows: Fix permissions on install directory" msgstr "" #: i2p2www/blog/2020/05/25/0.9.46-Release.rst:63 msgid "Build process changes to support git" msgstr "" #: i2p2www/blog/2020/05/25/0.9.46-Release.rst:64 msgid "Console: Don't show IPv6 temporary addresses as bind options" msgstr "" #: i2p2www/blog/2020/05/25/0.9.46-Release.rst:65 msgid "Console: Fix up javascript, stricter Content Security Policy" msgstr "" #: i2p2www/blog/2020/05/25/0.9.46-Release.rst:66 msgid "Crypto: Disable speculative tagset usage" msgstr "" #: i2p2www/blog/2020/05/25/0.9.46-Release.rst:67 msgid "Eepsites: Add Jetty GzipHandler for Jetty 9.3+" msgstr "" #: i2p2www/blog/2020/05/25/0.9.46-Release.rst:68 msgid "I2CP: Disable gzip for HTTP server tunnels and i2psnark" msgstr "" #: i2p2www/blog/2020/05/25/0.9.46-Release.rst:69 msgid "i2psnark: Connect out to other seeds to fetch new comments" msgstr "" #: i2p2www/blog/2020/05/25/0.9.46-Release.rst:70 msgid "i2psnark: Support file paths in add form" msgstr "" #: i2p2www/blog/2020/05/25/0.9.46-Release.rst:71 msgid "NetDB: Don't send \"fake hash\" to indicate exploration" msgstr "" #: i2p2www/blog/2020/05/25/0.9.46-Release.rst:72 msgid "Profiles: Change decay algorithm" msgstr "" #: i2p2www/blog/2020/05/25/0.9.46-Release.rst:73 msgid "Profiles: Limit average speed calculation to high capacity peers" msgstr "" #: i2p2www/blog/2020/05/25/0.9.46-Release.rst:74 msgid "Router: Auto-floodfill now class N minimum" msgstr "" #: i2p2www/blog/2020/05/25/0.9.46-Release.rst:75 msgid "Router: Checks for key certificates in destinations (proposal 145)" msgstr "" #: i2p2www/blog/2020/05/25/0.9.46-Release.rst:76 msgid "Router: Enforce minimum version for tunnel peers" msgstr "" #: i2p2www/blog/2020/05/25/0.9.46-Release.rst:77 msgid "SusiDNS: Support adding Base 32 addresses" msgstr "" #: i2p2www/blog/2020/06/07/file-based-reseed.rst:2 msgid "Help your Friends Join I2P by Sharing Reseed Bundles" msgstr "" #: i2p2www/blog/2020/06/07/file-based-reseed.rst:9 msgid "Create, exchange, and use reseed bundles" msgstr "" #: i2p2www/blog/2020/06/07/file-based-reseed.rst:11 msgid "" "Most new I2P routers join the network by bootstrapping with the help of\n" "a reseed service. However, reseed services are centralized and\n" "comparatively easy to block, considering the emphasis on de-centralized\n" "and un-blockable connections in the rest of the I2P network. If a new\n" "I2P router finds itself unable to bootstrap, it may be a possible to use\n" "an existing I2P router to generate a working “Reseed bundle” and\n" "bootstrap without the need of a reseed service." msgstr "" #: i2p2www/blog/2020/06/07/file-based-reseed.rst:21 msgid "" "It is possible for a user with a working I2P connection to help a\n" "blocked router join the network by generating a reseed file and passing\n" "it to them via a secret or non-blocked channel. In fact, in many\n" "circumstances, an I2P router that is already connected will not be\n" "affected by reseed blocking at all, so **having working I2P routers\n" "around means that existing I2P routers can help new I2P routers by\n" "providing them with a hidden way of bootstrapping**." msgstr "" #: i2p2www/blog/2020/06/07/file-based-reseed.rst:31 msgid "Generating a Reseed Bundle" msgstr "" #: i2p2www/blog/2020/06/07/file-based-reseed.rst:34 msgid "" "To create a reseed bundle for others to use, go to the `Reseed\n" " configuration page `__. You will\n" " see a section that looks like this. Click the button indicated by the\n" " red circle. |Create a Reseed Zip|" msgstr "" #: i2p2www/blog/2020/06/07/file-based-reseed.rst:38 msgid "" "Now that you’ve clicked the button, a zip will be generated\n" " containing enough information to bootstrap a new I2P router. Download\n" " it and transfer it to the computer with the new, un-bootstrapped I2P\n" " router. |Downloads a Reseed Zip|" msgstr "" #: i2p2www/blog/2020/06/07/file-based-reseed.rst:43 msgid "Performing a Reseed from File" msgstr "" #: i2p2www/blog/2020/06/07/file-based-reseed.rst:46 msgid "" "Obtain an i2preseed.zip file from a friend with an I2P router that is\n" " already running, or from a trusted source somewhere on the internet,\n" " and visit the `Reseed Configuration\n" " page `__. Click the button that\n" " says “Select zip or su3 file” and navigate to that file. |Select a\n" " Reseed Zip|" msgstr "" #: i2p2www/blog/2020/06/07/file-based-reseed.rst:52 msgid "" "When you’ve selected your reseed file, click the “Reseed from File”\n" " button. |Reseed from a Zip File|. You’re done! Your router will now\n" " bootstrap using the zip file, and you will be ready to join the I2P\n" " network." msgstr "" #: i2p2www/blog/2020/08/24/0.9.47-Release.rst:2 msgid "0.9.47 Release" msgstr "" #: i2p2www/blog/2020/08/24/0.9.47-Release.rst:9 msgid "0.9.47 enables new ECIES Encryption" msgstr "" #: i2p2www/blog/2020/08/24/0.9.47-Release.rst:16 msgid "" "0.9.47 enables our new end-to-end encryption protocol (proposal 144) by default for some services.\n" "The Sybil analysis and blocking tool is now enabled by default." msgstr "0.9.47 在一些服务中默认启用了我们的新端到端加密协议（提案 144）。\nSybil 分析和屏蔽工具现在已默认启用。" #: i2p2www/blog/2020/08/24/0.9.47-Release.rst:21 msgid "" "Java 8 or higher is now required.\n" "Debian packages for Wheezy and Stretch, and for Ubuntu Trusty and Precise, are no longer supported.\n" "Users on those platforms should upgrade so you may continue to receive I2P updates." msgstr "现在需要 Java 8 或更高版本。\nDebian 软件包 Wheezy 和 Stretch，以及 Ubuntu 软件包 Trusty 和 Precise 现已不再支持。\n使用上述平台的用户需要升级以继续获得 I2P 更新。" #: i2p2www/blog/2020/08/24/0.9.47-Release.rst:37 msgid "Java 8 now required" msgstr "" #: i2p2www/blog/2020/08/24/0.9.47-Release.rst:42 msgid "" "ECIES-X25519-AEAD-Ratchet encryption enabled for i2psnark, shared clients, " "HTTP proxy, and new tunnels" msgstr "" #: i2p2www/blog/2020/08/24/0.9.47-Release.rst:43 msgid "Increase streaming MTU for ECIES connections" msgstr "" #: i2p2www/blog/2020/08/24/0.9.47-Release.rst:44 msgid "Enable Sybil analysis and blocking tool by default" msgstr "" #: i2p2www/blog/2020/08/24/0.9.47-Release.rst:51 msgid "" "Hidden Services Manager: Fix missing server tunnel length configuration" msgstr "" #: i2p2www/blog/2020/08/24/0.9.47-Release.rst:52 msgid "Hidden Services Manager: Fix missing server throttle configuration" msgstr "" #: i2p2www/blog/2020/08/24/0.9.47-Release.rst:53 msgid "i2psnark: Fix javascript confirmation for delete buttons" msgstr "" #: i2p2www/blog/2020/08/24/0.9.47-Release.rst:54 msgid "UPnP: More fixes for changing interfaces and devices" msgstr "" #: i2p2www/blog/2020/08/24/0.9.47-Release.rst:55 msgid "Fix DoH handling of Cloudflare responses" msgstr "" #: i2p2www/blog/2020/08/24/0.9.47-Release.rst:56 msgid "Fix blinded/encrypted leaseset creation" msgstr "" #: i2p2www/blog/2020/08/24/0.9.47-Release.rst:57 msgid "Fix persistent leaseset keys" msgstr "" #: i2p2www/blog/2020/08/24/0.9.47-Release.rst:64 msgid "Sign Windows dlls" msgstr "" #: i2p2www/blog/2020/08/24/0.9.47-Release.rst:65 msgid "Faster gzip uncompression for level 0" msgstr "" #: i2p2www/blog/2020/08/24/0.9.47-Release.rst:66 msgid "i2psnark: Increase max pipeline" msgstr "" #: i2p2www/blog/2020/11/30/0.9.48-Release.rst:2 msgid "0.9.48 Release" msgstr "" #: i2p2www/blog/2020/11/30/0.9.48-Release.rst:9 msgid "0.9.48 with performance enhancements" msgstr "0.9.48 包含性能提升" #: i2p2www/blog/2020/11/30/0.9.48-Release.rst:16 msgid "" "0.9.48 enables our new end-to-end encryption protocol (proposal 144) for most services.\n" "We have added preliminary support for new tunnel build message encryption (proposal 152).\n" "There are significant performance improvements throughout the router." msgstr "0.9.48 在大多数服务上启用了我们的新端到端加密协议（提案144）。\n我们已经添加对新隧道建立的信息加密（提案152）的初步支持。\n整个路由的性能都有显著提高。" #: i2p2www/blog/2020/11/30/0.9.48-Release.rst:22 msgid "" "Packages for Ubuntu Xenial (16.04 LTS) are no longer supported.\n" "Users on that platform should upgrade so you may continue to receive I2P updates." msgstr "Ubuntu Xenial (16.04 长期支持版) 的软件包已不再支持。\n使用该平台的用户应当升级以继续获得 I2P 更新。" #: i2p2www/blog/2020/11/30/0.9.48-Release.rst:37 msgid "Avoid old DSA-SHA1 routers for lookups, stores, and tunnel peers" msgstr "" #: i2p2www/blog/2020/11/30/0.9.48-Release.rst:38 msgid "Block same-country connections when in hidden mode" msgstr "" #: i2p2www/blog/2020/11/30/0.9.48-Release.rst:39 msgid "BOB: Add deprecation warning" msgstr "" #: i2p2www/blog/2020/11/30/0.9.48-Release.rst:40 msgid "Build: Drop support for Xenial; ant 1.9.8 or higher required to build" msgstr "" #: i2p2www/blog/2020/11/30/0.9.48-Release.rst:41 msgid "i2ptunnel: Enable dual-key encryption for most tunnel types" msgstr "" #: i2p2www/blog/2020/11/30/0.9.48-Release.rst:42 msgid "JBigI: Add library for Linux aarch64, zen, and zen2" msgstr "" #: i2p2www/blog/2020/11/30/0.9.48-Release.rst:43 msgid "Preliminary support for ECIES-X25519 routers (proposals 152 and 156)" msgstr "" #: i2p2www/blog/2020/11/30/0.9.48-Release.rst:44 msgid "Ratchet: Efficiency improvements and memory reduction" msgstr "" #: i2p2www/blog/2020/11/30/0.9.48-Release.rst:45 msgid "SSU: Randomize intro key" msgstr "" #: i2p2www/blog/2020/11/30/0.9.48-Release.rst:46 msgid "SSU performance improvements" msgstr "" #: i2p2www/blog/2020/11/30/0.9.48-Release.rst:47 msgid "System tray: Enable by default for Linux KDE and LXDE" msgstr "" #: i2p2www/blog/2020/11/30/0.9.48-Release.rst:53 msgid "Build: Set release property for better runtime compatibility" msgstr "" #: i2p2www/blog/2020/11/30/0.9.48-Release.rst:54 msgid "Console: Fix Jetty not starting on Java 11.0.9.1" msgstr "" #: i2p2www/blog/2020/11/30/0.9.48-Release.rst:55 msgid "i2psnark: Limit size of embedded video" msgstr "" #: i2p2www/blog/2020/11/30/0.9.48-Release.rst:56 msgid "Improved IPv6 address validation" msgstr "" #: i2p2www/blog/2020/11/30/0.9.48-Release.rst:57 msgid "Installer: Disable pack200 to support Java 14+" msgstr "" #: i2p2www/blog/2020/11/30/0.9.48-Release.rst:58 msgid "Installer: Add missing linux armv7 and aarch64 wrapper binaries" msgstr "" #: i2p2www/blog/2020/11/30/0.9.48-Release.rst:59 msgid "i2ptunnel: Filter server response headers when not compressing" msgstr "" #: i2p2www/blog/2020/11/30/0.9.48-Release.rst:60 msgid "NTCP2: Fix sending termination message on idle timeout" msgstr "" #: i2p2www/blog/2020/11/30/0.9.48-Release.rst:61 msgid "Streaming: Fix handling of tag options" msgstr "" #: i2p2www/blog/2020/11/30/0.9.48-Release.rst:67 msgid "Build: Reproducible build fix" msgstr "" #: i2p2www/blog/2020/11/30/0.9.48-Release.rst:68 msgid "Core: Refactoring of data structures to reduce memory usage" msgstr "" #: i2p2www/blog/2020/11/30/0.9.48-Release.rst:69 msgid "Crypto: Cache HMAC256 instances" msgstr "" #: i2p2www/blog/2020/11/30/0.9.48-Release.rst:70 msgid "i2psnark: Hide BEP 48 padding directory in UI" msgstr "" #: i2p2www/blog/2020/11/30/0.9.48-Release.rst:71 msgid "i2psnark: Checks for unsupported v2 torrents" msgstr "" #: i2p2www/blog/2020/11/30/0.9.48-Release.rst:72 msgid "i2psnark: Remove old opentrackers" msgstr "" #: i2p2www/blog/2020/11/30/0.9.48-Release.rst:73 msgid "i2ptunnel: Improved support for offline keys" msgstr "" #: i2p2www/blog/2020/11/30/0.9.48-Release.rst:75 msgid "NetDB: Increase minimum floodfill version for leaseset lookups" msgstr "" #: i2p2www/blog/2020/11/30/0.9.48-Release.rst:76 msgid "NTCP: Set nodelay on sockets" msgstr "" #: i2p2www/blog/2020/11/30/0.9.48-Release.rst:77 msgid "Proxy: Remove old jump servers" msgstr "" #: i2p2www/blog/2020/11/30/0.9.48-Release.rst:78 msgid "Ratchet: Rotate keys faster" msgstr "" #: i2p2www/blog/2020/11/30/0.9.48-Release.rst:80 msgid "Wrapper 3.5.44 (new installs only)" msgstr "" #: i2p2www/blog/2020/11/30/0.9.48-Release.rst:82 msgid "New partial translations for Kurdish, Turkmen, Argentinian Spanish" msgstr "" #: i2p2www/blog/2020/12/10/Hello-git-goodbye-mtn.rst:2 #: i2p2www/blog/2020/12/10/Hello-git-goodbye-mtn.rst:11 msgid "Hello Git, Goodbye Monotone" msgstr "" #: i2p2www/blog/2020/12/10/Hello-git-goodbye-mtn.rst:9 msgid "Hello git, goodbye mtn" msgstr "" #: i2p2www/blog/2020/12/10/Hello-git-goodbye-mtn.rst:16 msgid "The I2P Git Migration is nearly concluded" msgstr "" #: i2p2www/blog/2020/12/10/Hello-git-goodbye-mtn.rst:21 msgid "" "For over a decade, I2P has relied on the venerable Monotone service to support\n" "its version control needs, but during the past few years, most of the world has\n" "moved on to the now-universal Git version control system. In that same\n" "time, the I2P Network has become faster and more reliable, and accessible\n" "workarounds to Git's non-resumability have been developed." msgstr "" #: i2p2www/blog/2020/12/10/Hello-git-goodbye-mtn.rst:29 msgid "" "Today marks a significant occasion for I2P, as we switched off the old mtn\n" "i2p.i2p branch, and moved the development of the core Java I2P libraries from\n" "Monotone to Git officially." msgstr "" #: i2p2www/blog/2020/12/10/Hello-git-goodbye-mtn.rst:35 msgid "" "While our use of mtn has been questioned in the past, and it's not always been a\n" "popular choice, I'd like to take this moment, as perhaps the very last project to use\n" "Monotone to thank the Monotone developers, current and former, wherever they are,\n" "for the software they created." msgstr "" #: i2p2www/blog/2020/12/10/Hello-git-goodbye-mtn.rst:44 msgid "GPG Signing" msgstr "" #: i2p2www/blog/2020/12/10/Hello-git-goodbye-mtn.rst:49 msgid "" "Checkins to the I2P Project repositories require you to configure GPG signing for\n" "your git commits, including Merge Requests and Pull Requests. Please configure\n" "your git client for GPG signing before you fork i2p.i2p and check anything in." msgstr "" #: i2p2www/blog/2020/12/10/Hello-git-goodbye-mtn.rst:55 msgid "Official Repositories and Gitlab/Github Syncing" msgstr "" #: i2p2www/blog/2020/12/10/Hello-git-goodbye-mtn.rst:60 msgid "" "The official repository is the one hosted at https://i2pgit.org/i2p-hackers/i2p.i2p\n" "and at https://git.idk.i2p/i2p-hackers/i2p.i2p, but there is a \"Mirror\" available\n" "at Github at https://github.com/i2p/i2p.i2p." msgstr "" #: i2p2www/blog/2020/12/10/Hello-git-goodbye-mtn.rst:66 msgid "" "Now that we're on git, we can synchronize repositories from our own self-hosted Gitlab\n" "instance, to Github, and back again. This means that it is possible to create and submit\n" "a merge request on Gitlab and when it is merged, the result will be synced with Github,\n" "and a Pull Request on Github, when merged, will appear on Gitlab." msgstr "" #: i2p2www/blog/2020/12/10/Hello-git-goodbye-mtn.rst:73 msgid "" "This means that it's possible to submit code to us through our Gitlab instance or through\n" "Github depending on what you prefer, however, more of the I2P developers are regularly\n" "monitoring Gitlab than Github. MR's to Gitlab are more likely to be merged sooner\n" "than PR's to Github." msgstr "" #: i2p2www/blog/2020/12/10/Hello-git-goodbye-mtn.rst:80 msgid "Thanks" msgstr "感谢" #: i2p2www/blog/2020/12/10/Hello-git-goodbye-mtn.rst:85 msgid "" "Congratulations and thanks to everyone who helped in the git migration, especially\n" "zzz, eche|on, nextloop, and our site mirror operators! While some of us will miss\n" "Monotone, it has become a barrier for new and existing participants in I2P development\n" "and we're excited to join the world of developers using Git to manage their distributed\n" "projects." msgstr "" #: i2p2www/blog/2021/02/17/0.9.49-Release.rst:2 msgid "0.9.49 Release" msgstr "" #: i2p2www/blog/2021/02/17/0.9.49-Release.rst:9 msgid "0.9.49 with SSU fixes and faster crypto" msgstr "0.9.49 包含SSU修复及更快速的加密" #: i2p2www/blog/2021/02/17/0.9.49-Release.rst:16 msgid "" "0.9.49 continues the work to make I2P faster and more secure.\n" "We have several improvements and fixes for the SSU (UDP) transport that should result in faster speeds.\n" "This release also starts the migration to new, faster ECIES-X25519 encryption for routers.\n" "(Destinations have been using this encryption for a few releases now)\n" "We've been working on the specifications and protocols for new encryption for several years,\n" "and we are getting close to the end of it! The migration will take several releases to complete." msgstr "0.9.49 继续使 I2P 更快更安全。\n我们对 SSU (UDP) 传输做了若干改进和修复，速度应有所提高。\n同时此发布开始为路由迁移至新的，更快的 ECIES-X25519 加密。\n（至今目标地址采用此加密已有数个发布）\n这几年，我们一直致力于新加密的规范和协议，\n现已经接近尾声了！迁移会在数个发布中完成。" #: i2p2www/blog/2021/02/17/0.9.49-Release.rst:25 msgid "" "For this release, to minimize disruption, only new installs and a very small percentage of existing installs\n" "(randomly selected at restart) will be using the new encryption.\n" "If your router does \"rekey\" to use the new encryption, it may have lower traffic or less reliability than usual for several days after you restart.\n" "This is normal, because your router has generated a new identity.\n" "Your performance should recover after a while." msgstr "对于此发布，为尽量减少中断，只有新安装的以及极小比例的现有安装\n（重启时随机选择）会采用新加密。\n如果你的路由确实“重新键入”以使用新加密，在你重启后的几天内，它可能会比平时流量更少或可靠性更低。\n这是正常现象，因为你的路由生成了一个新的身份。\n你的路由性能随后会恢复正常。" #: i2p2www/blog/2021/02/17/0.9.49-Release.rst:33 msgid "" "We have \"rekeyed\" the network twice before, when changing the default signature type,\n" "but this is the first time we've changed the default encryption type.\n" "Hopefully it will all go smoothly, but we're starting slowly to be sure." msgstr "以往我们在改变默认签名类型时已两次“重新键入”网络，\n但这是首次更改默认加密方式。\n希望一切都能顺利进行，我们正逐步确定。" #: i2p2www/blog/2021/02/17/0.9.49-Release.rst:49 msgid "Build: Git migration" msgstr "" #: i2p2www/blog/2021/02/17/0.9.49-Release.rst:50 msgid "Build: Move web resources to wars" msgstr "" #: i2p2www/blog/2021/02/17/0.9.49-Release.rst:51 msgid "i2psnark WebSeed support" msgstr "" #: i2p2www/blog/2021/02/17/0.9.49-Release.rst:52 msgid "i2psnark padding file support" msgstr "" #: i2p2www/blog/2021/02/17/0.9.49-Release.rst:53 msgid "i2ptunnel: Move proxy resources to jar" msgstr "" #: i2p2www/blog/2021/02/17/0.9.49-Release.rst:54 msgid "Router: Redesign ECIES encryption for floodfills (proposal 156)" msgstr "" #: i2p2www/blog/2021/02/17/0.9.49-Release.rst:55 msgid "Router: Verify RI stores after startup" msgstr "" #: i2p2www/blog/2021/02/17/0.9.49-Release.rst:56 msgid "Router: Reduce Sybil threshold" msgstr "" #: i2p2www/blog/2021/02/17/0.9.49-Release.rst:57 msgid "Router: ECIES for new routers" msgstr "" #: i2p2www/blog/2021/02/17/0.9.49-Release.rst:58 msgid "Router: Start of ECIES migration" msgstr "" #: i2p2www/blog/2021/02/17/0.9.49-Release.rst:59 msgid "SSU: Send individual fragments of messages" msgstr "" #: i2p2www/blog/2021/02/17/0.9.49-Release.rst:60 msgid "SSU: Westwood+ congestion control" msgstr "" #: i2p2www/blog/2021/02/17/0.9.49-Release.rst:61 msgid "SSU: Fast retransmit" msgstr "" #: i2p2www/blog/2021/02/17/0.9.49-Release.rst:66 msgid "Build: Fix Gradle build" msgstr "" #: i2p2www/blog/2021/02/17/0.9.49-Release.rst:67 msgid "Crypto: Increase ratchet tag window to prevent message loss" msgstr "" #: i2p2www/blog/2021/02/17/0.9.49-Release.rst:68 msgid "" "I2CP: Fix encrypted leaseset combined with ECIES crypto or offline keys" msgstr "" #: i2p2www/blog/2021/02/17/0.9.49-Release.rst:69 msgid "i2ptunnel: Fix config file saving issues" msgstr "" #: i2p2www/blog/2021/02/17/0.9.49-Release.rst:70 msgid "Router: Fix leaseset request fails causing watchdog to bark" msgstr "" #: i2p2www/blog/2021/02/17/0.9.49-Release.rst:71 msgid "Router: Hidden mode fixes" msgstr "" #: i2p2www/blog/2021/02/17/0.9.49-Release.rst:72 msgid "SSU: Fix partial acks not being sent" msgstr "" #: i2p2www/blog/2021/02/17/0.9.49-Release.rst:73 msgid "SSU: Fix occasional high CPU usage" msgstr "" #: i2p2www/blog/2021/02/17/0.9.49-Release.rst:78 msgid "Crypto: AES performance improvements" msgstr "" #: i2p2www/blog/2021/02/17/0.9.49-Release.rst:79 msgid "DoH: Change to RFC 8484 style" msgstr "" #: i2p2www/blog/2021/02/17/0.9.49-Release.rst:80 msgid "i2ptunnel: Remove DSA shared clients" msgstr "" #: i2p2www/blog/2021/02/17/0.9.49-Release.rst:81 msgid "Proxy: Add jump servers" msgstr "" #: i2p2www/blog/2021/02/17/0.9.49-Release.rst:82 msgid "Router: Add more countries for hidden mode" msgstr "" #: i2p2www/blog/2021/02/17/0.9.49-Release.rst:83 msgid "Router: Tunnel peer selection changes" msgstr "" #: i2p2www/blog/2021/02/17/0.9.49-Release.rst:84 msgid "Router: Move Sybil subsystem from console to router for embedded use" msgstr "" #: i2p2www/blog/2021/02/17/0.9.49-Release.rst:85 msgid "Router: Verify RI stores for a while after startup" msgstr "" #: i2p2www/blog/2021/02/17/0.9.49-Release.rst:86 msgid "Util: New unit tests" msgstr "" #: i2p2www/blog/2021/05/17/0.9.50-Release.rst:2 msgid "0.9.50 Release" msgstr "" #: i2p2www/blog/2021/05/17/0.9.50-Release.rst:9 msgid "0.9.50 with IPv6 fixes" msgstr "0.9.50 包含 IPv6 修复" #: i2p2www/blog/2021/05/17/0.9.50-Release.rst:16 msgid "" "0.9.50 continues the transition to ECIES-X25519 for router encryption keys.\n" "We have enabled DNS over HTTPS for reseeding to protect users from passive DNS snooping.\n" "There are numerous fixes and improvements for IPv6 addresses, including new UPnP support." msgstr "0.9.50 继续为路由加密密钥迁移至 ECIES-X25519。\n我们已为补种启用 DNS over HTTPS 以保护用户免受被动 DNS 窥探。\n还有若干对 IPv6 地址的修复和提升，包括新的 UPnP 支持。" #: i2p2www/blog/2021/05/17/0.9.50-Release.rst:22 msgid "" "We have finally fixed some longstanding SusiMail corruption bugs.\n" "Changes to the bandwidth limiter should improve network tunnel performance.\n" "There are several improvements in our Docker containers.\n" "We have improved our defenses for possible malicious and buggy routers in the network." msgstr "我们终于修复了一些 SusiMail 长期存在的错误。\n对带宽限制器的修改应该能改善网络隧道表现。\n在我们的 Docker 容器有几处改善。\n我们已经提升了对网络中可能的恶意和异常路由的防御。" #: i2p2www/blog/2021/05/17/0.9.50-Release.rst:39 msgid "Docker improvements" msgstr "" #: i2p2www/blog/2021/05/17/0.9.50-Release.rst:40 msgid "NTCP: Remove support for version 1" msgstr "" #: i2p2www/blog/2021/05/17/0.9.50-Release.rst:41 msgid "Reseed: Use DNSOverHTTPS" msgstr "" #: i2p2www/blog/2021/05/17/0.9.50-Release.rst:42 msgid "Router: Increase ECIES rekey probability" msgstr "" #: i2p2www/blog/2021/05/17/0.9.50-Release.rst:43 msgid "Router: Persist Sybil blocklist" msgstr "" #: i2p2www/blog/2021/05/17/0.9.50-Release.rst:44 msgid "SSU: Enable introducers and introductions via IPv6 (proposal 158)" msgstr "" #: i2p2www/blog/2021/05/17/0.9.50-Release.rst:46 msgid "Transports: Publish support for outbound IPv4/v6 (proposal 158)" msgstr "" #: i2p2www/blog/2021/05/17/0.9.50-Release.rst:47 msgid "UPnP: Add support for IPv6" msgstr "" #: i2p2www/blog/2021/05/17/0.9.50-Release.rst:53 msgid "Debian: Fix link to compiler jar" msgstr "" #: i2p2www/blog/2021/05/17/0.9.50-Release.rst:54 msgid "i2psnark: Fix theme selection" msgstr "" #: i2p2www/blog/2021/05/17/0.9.50-Release.rst:55 msgid "Jetty: Fix detection of SSL connector" msgstr "" #: i2p2www/blog/2021/05/17/0.9.50-Release.rst:56 msgid "NetDB: Fix NPE when validating expired blinded leaseset" msgstr "" #: i2p2www/blog/2021/05/17/0.9.50-Release.rst:57 msgid "NTP: Year 2036 fixes" msgstr "" #: i2p2www/blog/2021/05/17/0.9.50-Release.rst:58 msgid "Router: Fix rekeying every restart on ARM" msgstr "" #: i2p2www/blog/2021/05/17/0.9.50-Release.rst:59 msgid "Router: Fix decryption of encrypted leasesets" msgstr "" #: i2p2www/blog/2021/05/17/0.9.50-Release.rst:60 msgid "SAM: Fix removal of subsessions" msgstr "" #: i2p2www/blog/2021/05/17/0.9.50-Release.rst:61 msgid "SSU: Fix excessive dropping by the bandwidth limiter" msgstr "" #: i2p2www/blog/2021/05/17/0.9.50-Release.rst:62 msgid "SSU: Fix publishing 'C' capability when not an introducer" msgstr "" #: i2p2www/blog/2021/05/17/0.9.50-Release.rst:63 msgid "SSU: Fixes for firewalled/not firewalled state transitions" msgstr "" #: i2p2www/blog/2021/05/17/0.9.50-Release.rst:64 msgid "SSU: IPv6 fixes" msgstr "" #: i2p2www/blog/2021/05/17/0.9.50-Release.rst:65 msgid "SSU: Peer test fixes" msgstr "" #: i2p2www/blog/2021/05/17/0.9.50-Release.rst:66 msgid "SusiMail: Fix theme selection" msgstr "" #: i2p2www/blog/2021/05/17/0.9.50-Release.rst:67 msgid "SusiMail: Fix stream closed errors" msgstr "" #: i2p2www/blog/2021/05/17/0.9.50-Release.rst:68 msgid "SusiMail: Fix corruption in display of large, new messages" msgstr "" #: i2p2www/blog/2021/05/17/0.9.50-Release.rst:69 msgid "Tunnels: Several fixes in the participating tunnel bandwidth limiter" msgstr "" #: i2p2www/blog/2021/05/17/0.9.50-Release.rst:70 msgid "UPnP: Fix leases not being renewed before expiration" msgstr "" #: i2p2www/blog/2021/05/17/0.9.50-Release.rst:76 msgid "Build: Remove empty jars and wars from installers" msgstr "" #: i2p2www/blog/2021/05/17/0.9.50-Release.rst:77 msgid "Build: Prep for different release and API versions" msgstr "" #: i2p2www/blog/2021/05/17/0.9.50-Release.rst:78 msgid "Build: Remove launcher code" msgstr "" #: i2p2www/blog/2021/05/17/0.9.50-Release.rst:79 msgid "Gradle build fixes" msgstr "" #: i2p2www/blog/2021/05/17/0.9.50-Release.rst:80 msgid "Profiles: Disable tunnel peer test" msgstr "" #: i2p2www/blog/2021/05/17/0.9.50-Release.rst:81 msgid "Profiles: Remove unused tunnel test response time stat" msgstr "" #: i2p2www/blog/2021/05/17/0.9.50-Release.rst:82 msgid "SSU: Avoid outbound connections to buggy routers" msgstr "" #: i2p2www/blog/2021/05/17/0.9.50-Release.rst:83 msgid "Transports: Increase connection limits for some platforms" msgstr "" #: i2p2www/blog/2021/08/23/1.5.0-Release.rst:2 msgid "1.5.0 Release" msgstr "" #: i2p2www/blog/2021/08/23/1.5.0-Release.rst:9 msgid "1.5.0 with new tunnel build messages" msgstr "1.5.0 包含新的隧道搭建信息" #: i2p2www/blog/2021/08/23/1.5.0-Release.rst:16 msgid "" "Yes, that's right, after 9 years of 0.9.x releases, we are going straight from 0.9.50 to 1.5.0.\n" "This does not signify a major API change, or a claim that development is now complete.\n" "It is simply a recognition of almost 20 years of work to provide anonymity and security for our users." msgstr "是的没错，在 0.9.x 发布9年后，我们直接从 0.9.50 跳到 1.5.0。\n这并不意味着有重大的API更改，也不意味着开发已经完成。\n这仅仅是对近20年来为我们的用户提供匿名和安全的工作的认可。" #: i2p2www/blog/2021/08/23/1.5.0-Release.rst:22 msgid "" "This release finishes implementation of smaller tunnel build messages to reduce bandwidth.\n" "We continue the transition of the network's routers to X25519 encryption.\n" "Of course there are also numerous bug fixes and performance improvements." msgstr "此发布完成了更小的隧道构建消息的实现从而减少带宽使用。\n我们继续迁移网络的路由至 X25519 加密。\n当然也有许多错误修复和性能提升。" #: i2p2www/blog/2021/08/23/1.5.0-Release.rst:39 msgid "Tunnels: Finish support for new build messages (proposal 157)" msgstr "" #: i2p2www/blog/2021/08/23/1.5.0-Release.rst:40 msgid "Updates: Support for .dmg and .exe updates" msgstr "" #: i2p2www/blog/2021/08/23/1.5.0-Release.rst:45 msgid "Console: Fix generation of SSL keys on Java 17" msgstr "" #: i2p2www/blog/2021/08/23/1.5.0-Release.rst:46 msgid "i2psnark: Fix autostart for magnets" msgstr "" #: i2p2www/blog/2021/08/23/1.5.0-Release.rst:47 msgid "Router: Fix rare deadlock in publishing our RI" msgstr "" #: i2p2www/blog/2021/08/23/1.5.0-Release.rst:48 msgid "SSU: Fix handling of bad peer test responses" msgstr "" #: i2p2www/blog/2021/08/23/1.5.0-Release.rst:49 msgid "UPnP: IPv6 fixes" msgstr "" #: i2p2www/blog/2021/08/23/1.5.0-Release.rst:54 msgid "Jetty: Improve sort in directory listings" msgstr "" #: i2p2www/blog/2021/08/23/1.5.0-Release.rst:55 msgid "Jetty: Add X-I2P-Location header" msgstr "" #: i2p2www/blog/2021/08/23/1.5.0-Release.rst:56 msgid "Router: Increase probability to rekey to ECIES" msgstr "" #: i2p2www/blog/2021/08/23/1.5.0-Release.rst:57 msgid "Streaming: Performance improvements for low-latency connections" msgstr "" #: i2p2www/blog/2021/08/26/20-Years-of-I2P.rst:2 msgid "I2P Celebrates its 20th Year" msgstr "" #: i2p2www/blog/2021/08/26/20-Years-of-I2P.rst:9 msgid "I2P has been around for 20 years, let's take a look back" msgstr "" #: i2p2www/blog/2021/08/26/20-Years-of-I2P.rst:11 msgid "20 Years of I2P" msgstr "" #: i2p2www/blog/2021/08/26/20-Years-of-I2P.rst:16 msgid "" "It's hard to believe, but I2P has been around for nearly 20 years! From its\n" "beginning as a C project which provided anonymous access to IRC, we've had\n" "hundreds of contributors, accepted checkins from dozens of coders, used 2\n" "main languages, 3 version control systems, experienced a migration of its\n" "crypography, and multiple soft-forks. There have been around 500 registered\n" "sites on the Invisible Web, and countless unregistered I2P sites that were only\n" "accessible via their cryptographic hostnames." msgstr "" #: i2p2www/blog/2021/08/26/20-Years-of-I2P.rst:26 msgid "" "Thanks to the participation of users like you, the network has grown from a tiny\n" "group of power users to over 75,000 nodes operated from all over the world,\n" "made of I2P routers bundled in perhaps dozens of applications. Today I2P is\n" "available in on Windows, Mac OSX, Linux, and has ports for FreeBSD, OpenBSD, and\n" "many other systems. I2P can run on phones and even in SOHO routers (thanks to the\n" "independent C++ implementation of the protocol, i2pd)." msgstr "" #: i2p2www/blog/2021/08/26/20-Years-of-I2P.rst:35 msgid "A Routing Protocol with Flagship Applications" msgstr "" #: i2p2www/blog/2021/08/26/20-Years-of-I2P.rst:40 msgid "" "Even before other anonymity projects were providing their own application\n" "bundles, I2P was a tool for building applications that were configured for\n" "anonymity. Over the years, we've leaned on this strength, by expanding our\n" "APIs to support more and more versatile applications. Today, we're still\n" "developing new ways of building I2P into applications." msgstr "" #: i2p2www/blog/2021/08/26/20-Years-of-I2P.rst:48 msgid "" "Using the power of the Hidden Services Manager or the SAM API, developers of all\n" "kinds of applications can empower their users with anonymity using I2P. Exciting\n" "downstream projects like Monero's I2P-Zero have made it very easy for developers\n" "to help their users get connected to I2P. Today, I2P helps provide anonymity to\n" "dozens of applications including Bitcoin, IRC, email and multiple file-sharing\n" "protocols." msgstr "" #: i2p2www/blog/2021/08/26/20-Years-of-I2P.rst:57 msgid "An Anonymous Network By Everyone, For Everyone" msgstr "" #: i2p2www/blog/2021/08/26/20-Years-of-I2P.rst:62 msgid "" "I2P has always been a decentralized network, because its obvious that providing\n" "an anonymity network is an intrinsically collaborative process. To illustrate\n" "with the most extreme example, a single computer cannot provide itself\n" "with anonymity, nor can it be a useful network, by definiton. However, building\n" "I2P in this fully-decentralized manner hasn't always been easy." msgstr "" #: i2p2www/blog/2021/08/26/20-Years-of-I2P.rst:70 msgid "" "From the beginning, I2P would need to be scalable, and be able to balance itself\n" "so that high-bandwidth nodes wouldn't be able to easily take over the network.\n" "Sybil attacks would leave the realm of academia and we would need to develop\n" "new defenses against them." msgstr "" #: i2p2www/blog/2021/08/26/20-Years-of-I2P.rst:77 msgid "" "We've worked very hard to never compromise on this stance, and today every I2P\n" "router helps participate in providing the network with bandwidth resources and\n" "providing the users with anonymity. In doing so, we've learned incredible things\n" "and produced a network which at times has seemed inconceivable." msgstr "" #: i2p2www/blog/2021/08/26/20-Years-of-I2P.rst:84 msgid "Celebrating I2P" msgstr "" #: i2p2www/blog/2021/08/26/20-Years-of-I2P.rst:89 msgid "" "Over the next 2 weeks, we've planned some blog posts where we'll explore the past,\n" "present, and future of I2P, highlight applications and tools that build on\n" "and enhance I2P, and showcase the best of our community. Check back here for\n" "more in the coming days!" msgstr "" #: i2p2www/blog/2021/08/26/20-Years-of-I2P.rst:96 msgid "" "`The History of I2P\n" " `_" msgstr "" #: i2p2www/blog/2021/08/26/20-Years-of-I2P.rst:98 msgid "" "`Dependency-Free I2P of the Future - Jpackage Bundles and I2P-Zero (from Monero)\n" " `_" msgstr "" #: i2p2www/blog/2021/08/26/20-Years-of-I2P.rst:100 msgid "" "`Level-Up your I2P use with Encrypted LeaseSets\n" " `_" msgstr "" #: i2p2www/blog/2021/08/26/20-Years-of-I2P.rst:102 msgid "" "Dividing the Triangle: How I2P Eases Naming and Increases Flexibility for " "End-Users" msgstr "" #: i2p2www/blog/2021/08/26/20-Years-of-I2P.rst:103 msgid "I2P's Usability Journey" msgstr "" #: i2p2www/blog/2021/08/26/20-Years-of-I2P.rst:104 msgid "Building Bridges - Making Connections with Other Privacy Projects" msgstr "" #: i2p2www/blog/2021/08/28/History-of-I2P.rst:2 msgid "20 Years of Privacy: A brief History of I2P" msgstr "" #: i2p2www/blog/2021/08/28/History-of-I2P.rst:9 msgid "A history of I2P As We Know It" msgstr "" #: i2p2www/blog/2021/08/28/History-of-I2P.rst:11 msgid "" "Invisibility is the best defense: building an internet within an internet" msgstr "" #: i2p2www/blog/2021/08/28/History-of-I2P.rst:16 msgid "" "I believe most people want this technology so they can express\n" " themselves freely. It’s a comfortable feeling when you know you can\n" " do that. At the same time we can conquer some of the problems seen\n" " within the Internet by changing the way security and privacy is\n" " viewed, as well as the extent to what it is valued." msgstr "" #: i2p2www/blog/2021/08/28/History-of-I2P.rst:23 msgid "" "In October 2001, 0x90 ( Lance James) had a dream. It started as a\n" "“desire for instant communication with other Freenet users to talk about\n" "Freenet issues, and exchange Freenet keys while still maintaining\n" "anonymity, privacy and security.” It was called IIP — the Invisible IRC\n" "Project." msgstr "" #: i2p2www/blog/2021/08/28/History-of-I2P.rst:35 msgid "" "The Invisible IRC Project was based on an ideal and framework behind The\n" "InvisibleNet:" msgstr "" #: i2p2www/blog/2021/08/28/History-of-I2P.rst:38 msgid "In an interview from 2002, 0x90 described the project:" msgstr "" #: i2p2www/blog/2021/08/28/History-of-I2P.rst:40 msgid "" "“InvisibleNet is a research & development driven organization whose main\n" " focus is the innovation of intelligent network technology. Our goal is\n" " to provide the highest standards in security and privacy on the widely\n" " used, yet notoriously insecure Internet.\"" msgstr "" #: i2p2www/blog/2021/08/28/History-of-I2P.rst:45 msgid "" "\"The InvisibleNet team is comprised of a talented group of developers and\n" " architects entirely dedicated to providing its users with both\n" " convenience and the very best in secure communication.\"" msgstr "" #: i2p2www/blog/2021/08/28/History-of-I2P.rst:49 msgid "" "\"Our technological ideals are reflected in the implementation of a\n" " framework that is solid in design, and transparent in its application.\"" msgstr "" #: i2p2www/blog/2021/08/28/History-of-I2P.rst:52 msgid "" "\"Here at InvisibleNet we strive towards the greatest level of quality\n" " possible by keeping all areas of our research & development open and\n" " available to the public for peer review, feedback, suggestions and new\n" " ideas.”" msgstr "" #: i2p2www/blog/2021/08/28/History-of-I2P.rst:57 msgid "" "\"The Invisible Internet Project: Defined as the “New Internet”.\n" " Peer 2 Peer Internet. Using your peers to protect you. It is a\n" " similar concept to the Invisible IRC Project, with its design as our\n" " test model. We plan to re-design the Internet by taking it a step\n" " further and having security and privacy be first priority.\"" msgstr "" #: i2p2www/blog/2021/08/28/History-of-I2P.rst:63 msgid "" "\"The Invisible Internet Project or Protocol will be utilizing the\n" " tests and research/development concepts of the Invisible IRC Project\n" " to give us the scalability that we need and leverage this to take it\n" " to the next level.\"" msgstr "" #: i2p2www/blog/2021/08/28/History-of-I2P.rst:68 msgid "" "\"This, in essence will be an impenetrable neural-network, that is\n" " self-driven, self-defensed, and completely seamless to already\n" " applied protocols, specifically client to server (or agents as I call\n" " them). It will be THE next transport layer, a layer on top of the\n" " notoriously insecure Internet, to deliver full anonymity, privacy,\n" " and security at the highest level possible. Decentralized and peer to\n" " peer Internet, by the way, means no more worrying about your ISP\n" " controlling your traffic. This will allow you to do seamless\n" " activities and change the way we look at security and even the\n" " Internet, utilizing public key cryptography, IP steganography, and\n" " message authentication. The Internet that should have been, will be\n" " soon.\"" msgstr "" #: i2p2www/blog/2021/08/28/History-of-I2P.rst:85 msgid "All citations and quotes are from the interviews found here:" msgstr "" #: i2p2www/blog/2021/08/28/History-of-I2P.rst:90 msgid "" "By 2003, several other similar projects had started, the largest being\n" "Freenet, GNUNet, and Tor. All of these projects had broad goals to\n" "encrypt and anonymize a variety of traffic. For IIP, it became clear\n" "that IRC alone was not a big-enough target. What was needed was an\n" "anonymizing layer for all protocols. IIP by now was also being called\n" "“InvisibleNet”." msgstr "" #: i2p2www/blog/2021/08/28/History-of-I2P.rst:97 msgid "" "In early 2003, a new anonymous developer, “jrandom” joined the project.\n" "His explicit goal was to broaden the charter of IIP." msgstr "" #: i2p2www/blog/2021/08/28/History-of-I2P.rst:100 msgid "" "jrandom wished to rewrite the IIP code base in Java, a language he was\n" "familiar with, and the same language Freenet was using. He also wished\n" "to redesign the IIP protocols based on recent papers and the early\n" "design decisions that Tor and Freenet were making. Some of these\n" "concepts and naming conventions, such as “onion routing”, were modified\n" "to become “garlic routing”. For several of the design decisions, jrandom\n" "made different choices than Tor did, including selecting different\n" "cryptographic primitives in a number of places. Many (but not all) of\n" "these choices turned out quite well. For some others, such as using\n" "unidirectional tunnels rather than Tor’s bidirectional tunnels, the\n" "benefits and trade-offs are still not well-studied." msgstr "" #: i2p2www/blog/2021/08/28/History-of-I2P.rst:112 msgid "" "jrandom also set out a clear vision for the architecture of the code. It\n" "would be a client/server model, with the server (i.e. the router)\n" "isolated from any “client” protocols. Clients such as web browsers, web\n" "servers, IRC clients and servers, and others, would communicate through\n" "the router using I2CP, the I2P Client Protocol." msgstr "" #: i2p2www/blog/2021/08/28/History-of-I2P.rst:118 msgid "" "jrandom also had strong opinions on the direction of the project and its\n" "philosophy. He was strongly committed to open source and free software.\n" "He explicitly set a goal of protection from organizations with\n" "“unlimited financial and political resources.”" msgstr "" #: i2p2www/blog/2021/08/28/History-of-I2P.rst:123 msgid "" "By late summer 2003, jrandom had taken control of the project, and\n" "renamed it the Invisible Internet Project or “I2P”. He published a\n" "document outlining the philosophy of the project, and placed its\n" "technical goals and design in the context of mixnets and anonymizing\n" "layers. He also published the specification of two protocols (I2CP and\n" "I2NP) and their underlying data structures, that formed the basis of the\n" "network I2P uses today. Lance (“nop”) was last seen in a project meeting\n" "on November 11, 2003." msgstr "" #: i2p2www/blog/2021/08/28/History-of-I2P.rst:138 msgid "" "By fall 2003, I2P, Freenet, and Tor were rapidly developing. Business\n" "Week published an article on “The Underground Internet” which referenced\n" "InvisibleNet and discussed “darknets” extensively. jrandom released I2P\n" "version 0.2 on November 1, 2003, and continued rapid releases for the\n" "next 3 years. He maintained regular weekly meetings and status notes\n" "during this time. Several popular services and “respites” emerged during\n" "this time. Auto updates via clearnet HTTP became available in 2004." msgstr "" #: i2p2www/blog/2021/08/28/History-of-I2P.rst:146 msgid "" "Through 2004 and 2005, router development continued, and several\n" "“clients” or applications were added to the I2P package. “Mihi” wrote\n" "the first streaming protocol implementation and the i2ptunnel interface\n" "for configuring and starting client tunnels. “Susi” wrote the web mail\n" "and address book applications SusiMail and SusiDNS. Many people worked\n" "on the router console web interface. A bridge to make it easier for\n" "non-I2P clients to communicate over I2P, called “SAM” (Simple Anonymous\n" "Messaging) was added." msgstr "" #: i2p2www/blog/2021/08/28/History-of-I2P.rst:155 msgid "In February 2005, zzz installed I2P for the first time." msgstr "" #: i2p2www/blog/2021/08/28/History-of-I2P.rst:156 msgid "" "Anonymity projects were in the news. After surveying the field, he\n" " installed Freenet, and found it ambiguous, and difficult to explore.\n" " Not only that, it was very resource heavy and it was difficult to get\n" " anything to load. Tor and I2P were the other options, and he tried\n" " I2P." msgstr "" #: i2p2www/blog/2021/08/28/History-of-I2P.rst:162 msgid "" "zzz had no preconceived plans to contribute to the project, and had\n" "never written a line of Java. He had maybe used IRC once. At this time,\n" "I2P was at version 0.5, with maybe a thousand users and three hard-coded\n" "floodfills. Forum.i2p and postman’s tracker were up and running at the\n" "time, and weekly meetings and status notes, and releases every couple of\n" "week were happening." msgstr "" #: i2p2www/blog/2021/08/28/History-of-I2P.rst:169 msgid "" "By summer 2005, zzz had set up two websites. The first was zzz.i2p,\n" "which over the years became a central resource for I2P development, and\n" "still is. The second was stats.i2p, the first site to gather statistics\n" "on I2P network performance and present graphs on both the network and\n" "individual routers. While the individual router statistics eventually\n" "had to be shut down due to the tremendous growth of the network, the\n" "overall performance graphs remain. We are not sure that he ever planned\n" "to become the release manger for almost 2 decades, but we are happy he\n" "did. The project has not only stayed active, it has thrived and scaled\n" "to the demands of its growth." msgstr "" #: i2p2www/blog/2021/08/28/History-of-I2P.rst:184 msgid "" "On July 27, 2005, jrandom released I2P version 0.6, including an\n" "innovative new UDP transport protocol he designed called “SSU”, for\n" "Secure Semi-reliable UDP. It contained features for IP discovery and\n" "firewall traversal." msgstr "" #: i2p2www/blog/2021/08/28/History-of-I2P.rst:189 msgid "" "In September 2005, jrandom bundled “Syndie”, his new high-latency\n" "anonymous messaging system. In October 2005, jrandom ported Snark, a\n" "Java BitTorrent client, to become an I2P application and bundled it with\n" "the I2P package. This completed the collection of client applications\n" "that are still bundled with I2P today." msgstr "" #: i2p2www/blog/2021/08/28/History-of-I2P.rst:195 msgid "" "In late 2005 and early 2006, jrandom redesigned the way that I2P built\n" "tunnels. This was a major effort that was done to increase the security\n" "of the tunnel building, which is crucial to maintain anonymity and\n" "resist attacks. He worked closely with the Freenet developers, including\n" "“Toad”, on this design. The new build protocol required new I2NP\n" "messages and a hard cut-over or “flag day”. These changes were released\n" "in version 0.6.1.10 on February 16, 2006. This is significant as it is\n" "the last flag day I2P has had. While, in practice, an 0.6.1.10 router\n" "would not work well, if at all, in today’s network, we are, technically\n" "speaking, backwards-compatible with this ten-year-old version today." msgstr "" #: i2p2www/blog/2021/08/28/History-of-I2P.rst:206 msgid "" "By early 2006, the I2P software was at least feature-complete, but it\n" "was still not widely-known. jrandom’s view was that it shouldn’t be\n" "marketed publicly until it was near-perfect, and labeled as version 1.0.\n" "The network had perhaps a thousand users at the time. Project members\n" "were discouraged from talking about it online, and the website\n" "(`i2p.net `__) was unpolished and incomplete." msgstr "" #: i2p2www/blog/2021/08/28/History-of-I2P.rst:213 msgid "" "On July 27, 2006, jrandom released I2P version 0.6.1.23, including an\n" "innovative new TCP transport protocol he designed called “NTCP”, for\n" "new-IO-based TCP. It used Java’s new IO library for efficient handling\n" "of large numbers of TCP connections." msgstr "" #: i2p2www/blog/2021/08/28/History-of-I2P.rst:218 msgid "" "In late 2006, jrandom turned his focus to Syndie. He came to see it as\n" "his top priority, and the “killer application” for I2P. Highly secure\n" "and almost unusable, it delayed messages for up to two days before\n" "delivery to resist traffic analysis. Later in 2006, he stopped work on\n" "the bundled Syndie application and started a new, incompatible,\n" "standalone messaging application. This application was, confusingly,\n" "also called “Syndie”. The new Syndie was a large and complex\n" "development, and it was essentially a one-man project." msgstr "" #: i2p2www/blog/2021/08/28/History-of-I2P.rst:227 msgid "" "From late 2006 into 2007, core I2P development and releases slowed\n" "dramatically. From almost 30 releases in 2005 and 13 in the first half\n" "of 2006, there were only 5 in the second half of 2006 and only 4 in all\n" "of 2007. During this time, zzz and a developer named Complication had\n" "source code commit privileges and were making changes, but their\n" "understanding of the code base was limited. zzz worked, for example, on\n" "improving i2psnark, fixing bugs, and redesigning the strategy for\n" "anticipatory tunnel building. But there was a lot more that needed to be\n" "done. Complication and zzz did what they could, and they wrote the code\n" "for almost all the changes in the four 2007 releases\n" "(0.6.1.27–0.6.1.30). By this time, jrandom was providing very little\n" "guidance, code review, or direction for the project." msgstr "" #: i2p2www/blog/2021/08/28/History-of-I2P.rst:240 msgid "It wasn’t apparent at the time, but the project was in trouble." msgstr "" #: i2p2www/blog/2021/08/28/History-of-I2P.rst:242 msgid "" "jrandom had almost stopped working on the core I2P router and\n" "applications. Even the new Syndie, which he had declared as far more\n" "important than I2P itself, languished. After regular releases through\n" "March 2007, his next Syndie release, 1.100a, was August 25, 2007. All\n" "I2P releases were required to be signed by jrandom’s key, and he built\n" "and signed his last release, 0.6.1.30, on October 7, 2007." msgstr "" #: i2p2www/blog/2021/08/28/History-of-I2P.rst:249 msgid "" "In November 2007, disaster struck. Complication and zzz received a\n" "cryptic message from jrandom, that he would have to take time off from\n" "both Syndie and I2P development for a year or more. He expected that he\n" "would still be available to sign releases, but was willing to pass the\n" "release signing key to somebody else. Complication and zzz immediately\n" "replied with a request for the release key and other credentials, such\n" "as access to the website, mailing list, CVS administration, and others.\n" "Unfortunately, they never heard from jrandom again." msgstr "" #: i2p2www/blog/2021/08/28/History-of-I2P.rst:258 msgid "" "Late 2007 and early 2008, they awaited jrandom’s response, and wondered\n" "what to do next. However, all of the project infrastructure remained\n" "active, so it didn’t seem to be an immediate crisis. They knew, however,\n" "that without the release key or website access, they would have to sign\n" "with new keys, host the files on a new website, and require everybody to\n" "manually update since their keys wouldn’t be recognized." msgstr "" #: i2p2www/blog/2021/08/28/History-of-I2P.rst:265 msgid "" "The second stage of the disaster happened on January 13, 2008. The\n" "hosting company for almost all `i2p.net `__ servers\n" "suffered a power outage, and they did not fully return to service. Only\n" "jrandom had the credentials required to restore service. In addition,\n" "the centralized CVS source control appeared to be down, so five years of\n" "source control history appeared to be lost. Luckily, the CVS server was\n" "up, only the name server for it was down. The full contents of the CVS\n" "archive was quickly downloaded." msgstr "" #: i2p2www/blog/2021/08/28/History-of-I2P.rst:274 msgid "" "Complication, welterde, and zzz quickly made a number of decisions to\n" " get the project back up and running. Welterde started a new website at\n" " `i2p2.de `__. I2P needed to move to a decentralized\n" " source code control system. They tested bazaar and that did not work\n" " well over I2P. Git was just getting started. jrandom had used monotone\n" " for Syndie and liked its security properties, and it worked well over\n" " I2P, so it was selected." msgstr "" #: i2p2www/blog/2021/08/28/History-of-I2P.rst:281 msgid "" "Several people set up new services. The next release, 0.6.1.31, was\n" " signed by Complication and required a manual upgrade. It was released\n" " on February 10, 2008." msgstr "" #: i2p2www/blog/2021/08/28/History-of-I2P.rst:285 msgid "" "The project realized that even though it claimed to be totally\n" "decentralized, it actually depended on a number of centralized\n" "resources, above all, on jrandom. Work was done throughout 2008 to\n" "decentralize the project, and distribute roles to a number of people.\n" "Additionally, it was realized that development had essentially stalled\n" "in 2007, because jrandom had stopped working on it, but had not\n" "delegated to other developers. Nobody had an overall understanding of\n" "the code base." msgstr "" #: i2p2www/blog/2021/08/28/History-of-I2P.rst:294 msgid "" "Complication continued to sign the releases through mid-2009, but his\n" "contributions declined as he focused on activism and other projects.\n" "Starting with release 0.7.6 on July 31, 2009, zzz would sign the next 49\n" "releases." msgstr "" #: i2p2www/blog/2021/08/28/History-of-I2P.rst:299 msgid "" "In December 2008, zzz attended his first CCC, 25C3 in Berlin, and met\n" "other I2P project team members for the first time, including hottuna and\n" "welterde. The experience was overwhelming, and also humbling, as he\n" "struggled to explain I2P to others or answer even basic questions about\n" "its design and use of cryptography." msgstr "" #: i2p2www/blog/2021/08/28/History-of-I2P.rst:305 msgid "" "By mid-2009, zzz had come to understand the code base much better. Far\n" "from being complete or perfect, it was filled with problems and\n" "scalability issues. In 2009 the project experienced more network growth\n" "due to its anonymizing properties as well as its circumvention\n" "abilities. Participants appeared who were beginning to adopt the network\n" "for reasons like censorship and clearnet issues like blocking of popular\n" "services. For development gains, in-net auto updates became available\n" "for the software." msgstr "" #: i2p2www/blog/2021/08/28/History-of-I2P.rst:316 msgid "" "July 2010 zzz briefly presented I2P at the end of Adrian Hong’s\n" "presentation at HOPE XXXX. Adrian talked about how tech has helped\n" "expose human rights violations, and the need for defensive tools for\n" "activists. He urged that we all be ambassadors for all tech, stay on top\n" "of new tech, and keep the barrier low and educate people about how to\n" "use the tool we create." msgstr "" #: i2p2www/blog/2021/08/28/History-of-I2P.rst:323 msgid "" "He also talked about how we need many options for people to use, and\n" "asked how do we make it easier to support human rights, freedom of\n" "expression?" msgstr "" #: i2p2www/blog/2021/08/28/History-of-I2P.rst:327 msgid "" "At the end of the talk, zzz was invited on stage to introduce I2P and\n" "give an overview of what the project was about. The same weekend, it was\n" "pointed out that the I2P documentation was not in great shape." msgstr "" #: i2p2www/blog/2021/08/28/History-of-I2P.rst:331 msgid "" "In Fall 2010, zzz declared a moratorium on I2P development until the\n" "website documentation was complete and accurate. It took 3 months to get\n" "it done." msgstr "" #: i2p2www/blog/2021/08/28/History-of-I2P.rst:335 msgid "" "Beginning in 2010, until COVID restrictions were put in place, zzz, ech,\n" "hottuna, and other I2P contributors have attended CCC ( Chaos\n" "Communications Congress) every year. Over the years, meeh, Zab, Sadie,\n" "LazyGravy, KYTV, IDK and others have made the trip to Germany to share\n" "tables with other projects and celebrate the end of a year of releases.\n" "The project looks forward to one day being able to meet up again and\n" "have an in-person yearly roadmap meeting." msgstr "" #: i2p2www/blog/2021/08/28/History-of-I2P.rst:343 msgid "" "Anoncoin, a digital cryptocurrency that focuses on privacy and anonymity\n" "for its users was created in 2013. It was the first coin that provided\n" "built-in support for I2P, as well as Tor that makes it impossible to\n" "determine the IP address of the user. The developers, including meeh,\n" "also ran organizations like Privacy Solutions, and provided infrastructure\n" "support to the I2P network by running services like outproxies and\n" "reseed servers." msgstr "" #: i2p2www/blog/2021/08/28/History-of-I2P.rst:351 msgid "" "I2PBote development started to take off again in 2014 when str4d began\n" "contributing to the project. Bote is a server-less email client — it\n" "stores email in a `distributed hash\n" "table `__. Email is\n" "“automatically encrypted and digitally signed, which ensures no one but\n" "the intended recipient can read the email, and third parties cannot\n" "forge them.” ( https://i2pbote.xyz/). The project has existed since\n" "2009." msgstr "" #: i2p2www/blog/2021/08/28/History-of-I2P.rst:366 msgid "" "At Real World Crypto that year, zzz, psi and str4d began to talk about\n" "and review the plan to update I2P’s cryptography. The same year, the\n" "project was awarded a $5k donation from Duck Duck Go. Lavabit,\n" "SecureDrop, RiseUp and Mailpile also received donations for supporting\n" "better trust and privacy online." msgstr "" #: i2p2www/blog/2021/08/28/History-of-I2P.rst:372 msgid "" "By late 2014 most new signing crypto was complete, including ECDSA and\n" "EdDSA. New destination crypto was available; but new router info crypto\n" "needed to wait a year for the network to upgrade sufficiently." msgstr "" #: i2p2www/blog/2021/08/28/History-of-I2P.rst:376 msgid "" "During the early part of 2015, zzz posted to Twitter that it would be\n" "great to have a mini conference for I2P. In Spring, it was decided that\n" "I2PCon would take place that August over the course of a weekend." msgstr "" #: i2p2www/blog/2021/08/28/History-of-I2P.rst:380 msgid "" "Hottuna and Sadie organized most of the details, getting graphic assets\n" "created, posters printed and a banner made for the podium. Nick at\n" "Hacklab, where the event would take place, helped with making sure the\n" "space was ready for the event. Sadie reached out to the local infosec\n" "community and helped secure guest speakers as well. The event happened\n" "on one of the hottest weekends of the Summer, with attendees arriving\n" "from America and Europe. The I2P community did an amazing job of\n" "supporting the event by postering, giving talks, and spreading the word\n" "in forums and on social media. The talks can be viewed on KYTV’s YouTube\n" "Channel https://www.youtube.com/channel/UCZfD2Dk6POE-VU8DOqW7VVw" msgstr "" #: i2p2www/blog/2021/08/28/History-of-I2P.rst:395 msgid "" "In January 2016 at Real World Crypto Stanford — str4d gave a talk on the\n" "crypto migration progress and future plans for the project. zzz and\n" "others would continue weekly meetings to plan the migration over the\n" "next few years." msgstr "" #: i2p2www/blog/2021/08/28/History-of-I2P.rst:400 msgid "" "NTCP2 was implemented in 2018, in release 0.9.36. It was disabled by\n" "default so that it could be tested. It was enabled in 0.9.37. NTCP1 was\n" "disabled in 0.9.40." msgstr "" #: i2p2www/blog/2021/08/28/History-of-I2P.rst:404 msgid "" "The new I2P transport protocol provides effective resistance against\n" " DPI censorship. It also results in reduced CPU load because of the\n" " faster, modern cryptography used. It makes I2P more likely to run on\n" " low-end devices, such as smartphones and home routers. Both major I2P\n" " implementations have full support for NTCP2 and it make NTCP2\n" " available for use starting with version 0.9.36 (Java) and 2.20 (i2pd,\n" " C++)." msgstr "" #: i2p2www/blog/2021/08/28/History-of-I2P.rst:412 msgid "" "The complete implementation details can be read here\n" "https://geti2p.net/en/blog/post/2018/08/20/NTCP2" msgstr "" #: i2p2www/blog/2021/08/28/History-of-I2P.rst:415 msgid "" "0.9.39 included extensive changes for new network database types\n" "(proposal 123). The i2pcontrol plugin was bundled as a web-app to support\n" "development of RPC applications." msgstr "" #: i2p2www/blog/2021/08/28/History-of-I2P.rst:419 msgid "" "In 2019, the team decided to attend more conferences. That year IDK and\n" "zzz attended DefCon, and IDK gave a workshop on I2P application\n" "development. At Monero Village, zzz gave a talk called I2P for\n" "Cryptocurrency Developers." msgstr "" #: i2p2www/blog/2021/08/28/History-of-I2P.rst:424 msgid "" "Late that year, Sadie and IDK attended Our Networks in Toronto, where\n" "IDK gave a lightning talk about I2P." msgstr "" #: i2p2www/blog/2021/08/28/History-of-I2P.rst:427 msgid "" "Sadie attended RightsCon in Tunis and the Internet Freedom Festival in\n" "Valencia to meet with NGO’s and Human Right Defenders. Thanks to the the\n" "connections we made, the project received grants for usability and\n" "accessibility support from Open Tech Fund, and most recently Internews.\n" "This will ensure more user friendly onboarding, UX, and information\n" "architecture improvements to support the growing interest in the\n" "network. It will also support specific tooling to help in-need users\n" "with specific risk surfaces through user research." msgstr "" #: i2p2www/blog/2021/08/28/History-of-I2P.rst:438 msgid "" "That Summer, Hoàng Nguyên Phong had his research into I2P censorship\n" "accepted too FOCI at USENIX in Santa Clara. Sadie had supported the\n" "research and they attended together. I2P Metrics was created during this\n" "time https://i2p-metrics.np-tokumei.net/, and well as research into more\n" "resistant reseed servers for the I2P network\n" "https://homepage.np-tokumei.net/post/notes-i2p-reseed-over-cloudflare/.\n" "You can read the research report here\n" "https://homepage.np-tokumei.net/post/notes-otf-wrapup-blogpost/." msgstr "" #: i2p2www/blog/2021/08/28/History-of-I2P.rst:447 msgid "" "At CCC that year, the decision was made to migrate from Monotone too\n" "GitLab. The project was one of the last to use Monotone, and it was time\n" "to prepare to move on. IDK would spend 2020 ensuring the process was as\n" "smooth as it could be. The pandemic would result in the team not being\n" "able to see each other that year to celebrate the ( mostly) smooth move\n" "to Gitlab. On December 10. 2020, the project switched off the old mtn\n" "i2p.i2p branch, and moved the development of the core Java I2P libraries\n" "from Monotone to Git officially." msgstr "" #: i2p2www/blog/2021/08/28/History-of-I2P.rst:456 msgid "" "Congratulations and thanks to everyone who helped in the git\n" " migration, especially zzz, eche|on, nextloop, and our site mirror\n" " operators! While some of us will miss Monotone, it has become a\n" " barrier for new and existing participants in I2P development and\n" " we’re excited to join the world of developers using Git to manage\n" " their distributed projects." msgstr "" #: i2p2www/blog/2021/08/28/History-of-I2P.rst:465 msgid "" "0.9.47 enabled the new end-to-end encryption protocol (proposal 144) by\n" "default for some services. A Sybil analysis and blocking tool was also\n" "now enabled by default. 0.9.48 enabled the new end-to-end encryption\n" "protocol (proposal 144) for most services. Preliminary support was added\n" "for new tunnel build message encryption (proposal 152). There were\n" "significant performance improvements throughout the router." msgstr "" #: i2p2www/blog/2021/08/28/History-of-I2P.rst:472 msgid "" "0.9.49 was the release that brought faster crypto. The I2P network\n" "became faster and more secure. Improvements and fixes for the SSU (UDP)\n" "transport resulted in faster speeds. The release also started the\n" "migration to new, faster ECIES-X25519 encryption for routers. The\n" "project had been working on the specifications and protocols for new\n" "encryption for several years, and was getting close to the end of it.\n" "The migration would take several releases to complete." msgstr "" #: i2p2www/blog/2021/08/28/History-of-I2P.rst:480 msgid "" "To minimize disruption, only new installs and a very small percentage of\n" "existing installs (randomly selected at restart) would be using the new\n" "encryption." msgstr "" #: i2p2www/blog/2021/08/28/History-of-I2P.rst:484 msgid "" "The project had “rekeyed” the network twice before, when changing the\n" "default signature type, but this was the first time it had changed the\n" "default encryption type. 0.9.50 enabled DNS over HTTPS for reseeding to\n" "protect users from passive DNS snooping. There were numerous fixes and\n" "improvements for IPv6 addresses, including new UPnP support." msgstr "" #: i2p2www/blog/2021/08/28/History-of-I2P.rst:492 msgid "1.5.0 — The early anniversary release because it is so good!" msgstr "" #: i2p2www/blog/2021/08/28/History-of-I2P.rst:495 msgid "" "Yes, that’s right, after 9 years of 0.9.x releases, we are going\n" " straight from 0.9.50 to 1.5.0. This does not signify a major API\n" " change, or a claim that development is now complete. It is simply a\n" " recognition of almost 20 years of work to provide anonymity and\n" " security for our users." msgstr "" #: i2p2www/blog/2021/08/28/History-of-I2P.rst:501 msgid "" "This release finishes implementation of smaller tunnel build messages\n" " to reduce bandwidth. We continue the transition of the network’s\n" " routers to X25519 encryption. Of course there are also numerous bug\n" " fixes and performance improvements." msgstr "" #: i2p2www/blog/2021/08/28/History-of-I2P.rst:506 msgid "" "As usual, we recommend that you update to this release. The best way\n" " to maintain security and help the network is to run the latest\n" " release." msgstr "" #: i2p2www/blog/2021/08/28/History-of-I2P.rst:510 msgid "Congratulations team. Let’s do another 20." msgstr "" #: i2p2www/blog/2021/09/07/Level-Up-Encrypted-Leasesets.rst:2 #: i2p2www/blog/2021/09/07/Level-Up-Encrypted-Leasesets.rst:11 msgid "Level up your I2P Skills with Encrypted LeaseSets" msgstr "" #: i2p2www/blog/2021/09/07/Level-Up-Encrypted-Leasesets.rst:9 msgid "" "It has been said that I2P emphasizes Hidden Services, we examine one " "interpretation of this" msgstr "" #: i2p2www/blog/2021/09/07/Level-Up-Encrypted-Leasesets.rst:16 msgid "" "It has been said in the past that I2P emphasizes support for Hidden Services,\n" "which is true in many ways. However, what this means to users, developers, and\n" "hidden service administrators isn't always the same. Encrypted LeaseSets and\n" "their use-cases provide a unique, practical window into how I2P makes hidden\n" "services more versatile, easier to administer, and how I2P extends on the\n" "Hidden Service concept to provide security benefits for potentially interesting\n" "use-cases." msgstr "" #: i2p2www/blog/2021/09/07/Level-Up-Encrypted-Leasesets.rst:26 msgid "" "What is a LeaseSet?\n" "-------------------" msgstr "" #: i2p2www/blog/2021/09/07/Level-Up-Encrypted-Leasesets.rst:31 msgid "" "When you create a hidden service, you publish something called a \"LeaseSet\" to\n" "the I2P NetDB. The \"LeaseSet\" is, in the simplest terms, what other I2P users\n" "need to discover \"where\" your hidden service is on the I2P Network. It contains\n" "\"Leases\" which identify tunnels that can be used to reach your hidden service,\n" "and the public key of your destination, which clients will encrypt messages to.\n" "This type of hidden service is reachable by anyone who has the address, which\n" "is probably the most common use case for now." msgstr "" #: i2p2www/blog/2021/09/07/Level-Up-Encrypted-Leasesets.rst:41 msgid "" "Sometimes, you might not want to allow your hidden services to be accessible by\n" "anyone, though. Some people use hidden services as a way of accessing an SSH\n" "server on a home PC, or to stitch together a network of IOT Devices. In these\n" "cases it's not necessary, and may be counter-productive, to make your hidden\n" "service accessible to everyone one the I2P Network. This is where \"Encrypted\n" "LeaseSets\" come into play." msgstr "" #: i2p2www/blog/2021/09/07/Level-Up-Encrypted-Leasesets.rst:50 msgid "" "Encrypted LeaseSets: VERY Hidden Services\n" "------------------------------------------" msgstr "" #: i2p2www/blog/2021/09/07/Level-Up-Encrypted-Leasesets.rst:55 msgid "" "Encrypted LeaseSets are LeaseSets which are published to the NetDB in an\n" "encrypted form, where none of the Leases or public keys are visible unless\n" "the client has the keys required to decrypt the LeaseSet inside of it. Only\n" "clients you share keys with(For PSK Encrypted LeaseSets), or who share their\n" "keys with you(For DH Encrypted LeaseSets), will be able to see the destination\n" "and no one else." msgstr "" #: i2p2www/blog/2021/09/07/Level-Up-Encrypted-Leasesets.rst:64 msgid "" "I2P Supports several strategies for Encrypted LeaseSets. The key characteristics\n" "of each strategy are important to understand when deciding which one to use. If\n" "an Encrypted LeaseSet uses a \"Pre-Shared Key(PSK)\" strategy, then the server\n" "will generate a key(or keys) which the server operator then shares with each\n" "client. Of course, this exchange must happen out-of-band, possibly via an\n" "exchange on IRC for example. This version of Encrypted LeaseSets is sort of\n" "like logging into Wi-Fi with a password. Except, what you're logging into is\n" "a Hidden Service." msgstr "" #: i2p2www/blog/2021/09/07/Level-Up-Encrypted-Leasesets.rst:75 msgid "" "If an Encrypted LeaseSet uses a \"Diffie-Hellman(DH)\n" "strategy, then they keys are generated on the client instead. When a\n" "Diffie-Hellman client connects to a destination with an Encrypted LeaseSet, they\n" "must first share their keys with the server operator. The server operator then\n" "decides whether to authorize the DH client. This version of Encrypted LeaseSets\n" "is sort of like SSH with an `authorized_keys` file. Except, what you're logging\n" "into is a Hidden Service." msgstr "" #: i2p2www/blog/2021/09/07/Level-Up-Encrypted-Leasesets.rst:85 msgid "" "By Encrypting your LeaseSet, you not only make it impossible for unauthorized\n" "users to connect to your destination, you make it impossible for unauthorized\n" "visitors to even discover the real destination of the I2P Hidden Service. Some\n" "readers have probably already considered a use-case for their own Encrypted\n" "LeaseSet." msgstr "" #: i2p2www/blog/2021/09/07/Level-Up-Encrypted-Leasesets.rst:93 msgid "" "Using Encrypted LeaseSets to Safely Access a Router Console\n" "-----------------------------------------------------------" msgstr "" #: i2p2www/blog/2021/09/07/Level-Up-Encrypted-Leasesets.rst:98 msgid "" "As a general rule, the more complex information a service has access to about\n" "your device, the more dangerous it is to expose that service to the Internet or\n" "indeed, to a Hidden Service network like I2P. If you want to expose such a\n" "service, you need to protect it with something like a password, or, in the case\n" "of I2P, a much more thorough and secure option could be an Encrypted LeaseSet." msgstr "" #: i2p2www/blog/2021/09/07/Level-Up-Encrypted-Leasesets.rst:106 msgid "" "**Before continuing, please read and understand that if you do the following**\n" "**procedure without an Encrypted LeaseSet, you will be defeating the security of**\n" "**your I2P router. Do not configure access to your router console over I2P without**\n" "**an Encrypted LeaseSet. Additionally, do not share your Encrypted LeaseSet PSK's**\n" "**with any devices you do not control.**" msgstr "" #: i2p2www/blog/2021/09/07/Level-Up-Encrypted-Leasesets.rst:114 msgid "" "One such service which is useful to share over I2P, but ONLY with an Encrypted\n" "LeaseSet, is the I2P router console itself. Exposing the I2P router console on\n" "one machine to I2P with an Encrypted LeaseSet allows another machine with a\n" "browser to administer the remote I2P instance. I find this useful for remotely\n" "monitoring my regular I2P Services. It could also be used to monitor a server\n" "which is used to seed a torrent long-term as a way to access I2PSnark." msgstr "" #: i2p2www/blog/2021/09/07/Level-Up-Encrypted-Leasesets.rst:123 msgid "" "For as long as it takes to explain them, setting up an Encrypted LeaseSet is\n" "straightforward to configure via the Hidden Services Manager UI." msgstr "" #: i2p2www/blog/2021/09/07/Level-Up-Encrypted-Leasesets.rst:128 msgid "" "On the \"Server\"\n" "---------------" msgstr "" #: i2p2www/blog/2021/09/07/Level-Up-Encrypted-Leasesets.rst:137 msgid "" "Start by opening the Hidden Services Manager at http://127.0.0.1:7657/i2ptunnelmgr\n" "and scroll to the bottom of the section that says \"I2P Hidden Services.\" Create\n" "a new hidden service with the host \"127.0.0.1\" and the port \"7657\" with these\n" "\"Tunnel Cryptography Options\" and save the hidden service." msgstr "" #: i2p2www/blog/2021/09/07/Level-Up-Encrypted-Leasesets.rst:148 msgid "" "Then, select your new tunnel from the Hidden Services Manager main page. The\n" "Tunnel Cryptography Options should now include your first Pre-Shared Key. Copy\n" "this down for the next step, along with the Encrypted Base32 Address of your\n" "tunnel." msgstr "" #: i2p2www/blog/2021/09/07/Level-Up-Encrypted-Leasesets.rst:159 msgid "" "On the \"Client\"\n" "---------------" msgstr "" #: i2p2www/blog/2021/09/07/Level-Up-Encrypted-Leasesets.rst:164 msgid "" "Now switch computers to the client which will connect to the hidden service,\n" "and visit the Keyring Configuration at http://127.0.0.1:7657/configkeyring to\n" "add the keys from earlier. Start by pasting the Base32 from the Server into\n" "the field labeled: \"Full destination, name, Base32, or hash.\" Next, paste the\n" "Pre-Shared Key from the server into the \"Encryption Key\" field. Click save,\n" "and you're ready to securely visit the Hidden Service using an Encrypted\n" "LeaseSet." msgstr "" #: i2p2www/blog/2021/09/07/Level-Up-Encrypted-Leasesets.rst:178 msgid "" "Now You're Ready to Remotely Administer I2P\n" "-------------------------------------------" msgstr "" #: i2p2www/blog/2021/09/07/Level-Up-Encrypted-Leasesets.rst:183 msgid "" "As you can see, I2P offers unique capabilities to Hidden Service Administrators\n" "which empower them to securely manage their I2P connections from anywhere in the\n" "world. Other Encrypted LeaseSets I keep on the same device for the same reason\n" "point to the SSH server, the Portainer instance I user to manage my service\n" "containers, and my personal NextCloud instance. With I2P, truly private, always\n" "reachable Self-Hosting is an achievable goal, in fact I think it's one of the\n" "things we're uniquely suited to, because of Encrypted LeaseSets. With them, I2P\n" "could become the key to securing self-hosted home automation or simply become\n" "the backbone of a new more private peer-to-peer web." msgstr "" #: i2p2www/blog/2021/09/15/i2p-jpackages.rst:2 msgid "Improving I2P Adoption and Onboarding using Jpackage, I2P-Zero" msgstr "" #: i2p2www/blog/2021/09/15/i2p-jpackages.rst:9 msgid "" "Versatile and emerging ways of installing and embedding I2P in your " "application" msgstr "" #: i2p2www/blog/2021/09/15/i2p-jpackages.rst:11 msgid "" "For the majority of I2P's existence, it's been an application that runs with the\n" "help of a Java Virtual Machine that is already installed on the platform. This\n" "has always been the normal way to distribute Java applications, but it leads to\n" "a complicated installation procedure for many people. To make things even more\n" "complicated, the \"right answer\" to making I2P easy to install on any given\n" "platform might not be the same as any other platform. For example, I2P is quite\n" "simple to install with standard tools on Debian and Ubuntu based operating\n" "systems, because we can simply list the required Java components as \"Required\"\n" "by our package, however on Windows or OSX, there is no such system allowing us to make\n" "sure that a compatible Java is installed." msgstr "" #: i2p2www/blog/2021/09/15/i2p-jpackages.rst:24 msgid "" "The obvious solution would be to manage the Java installation ourselves, but\n" "this used to a problem in-and-of-itself, outside of the scope of I2P. However,\n" "in recent Java versions, a new set of options has emerged which has the\n" "potential to solve this problem for many Java software. This exciting tool is\n" "called **\"Jpackage.\"**" msgstr "" #: i2p2www/blog/2021/09/15/i2p-jpackages.rst:32 msgid "I2P-Zero and Dependency-Free I2P Installation" msgstr "" #: i2p2www/blog/2021/09/15/i2p-jpackages.rst:37 msgid "" "The first very successful effort at building a dependency-free I2P Package was\n" "I2P-Zero, which was created by the Monero project originally for use with the\n" "Monero cryptocurrency. This project got us very excited because of it's success\n" "in creating a general-purpose I2P router which could easily packaged with an\n" "I2P application. Especially on Reddit, many people express their preference for\n" "the simplicity of setting up an I2P-Zero router." msgstr "" #: i2p2www/blog/2021/09/15/i2p-jpackages.rst:46 msgid "" "This really proved to us that a dependency-free I2P Package which was easy to\n" "install was possible using modern Java tools, but I2P-Zero's use case was a\n" "little bit different than ours. It is best for embedded apps that need an I2P\n" "router that they can easily control using it's convenient control port on port\n" "\"8051\". Our next step would be to adapt the technology to the general-purpose\n" "I2P Application." msgstr "" #: i2p2www/blog/2021/09/15/i2p-jpackages.rst:55 msgid "OSX Application Security Changes affect I2P IzPack Installer" msgstr "" #: i2p2www/blog/2021/09/15/i2p-jpackages.rst:60 msgid "" "The issue became more pressing in recent versions of Mac OSX, where it is no\n" "longer straightforward to use the \"Classic\" installer which comes in the .jar\n" "format. This is because the application is not \"Notarized\" by Apple authorities\n" "and it is deemed a security risk. **However**, Jpackage can produce a .dmg file,\n" "which can be notarized by Apple authorities, conveniently solving our problem." msgstr "" #: i2p2www/blog/2021/09/15/i2p-jpackages.rst:68 msgid "" "The new I2P .dmg installer, created by Zlatinb, makes I2P easier to install on\n" "OSX than ever, no longer requiring users to install Java themselves and using\n" "standard OSX installation tools in their prescribed ways. The new .dmg installer\n" "makes setting up I2P on Mac OSX easier than it's ever been." msgstr "" #: i2p2www/blog/2021/09/15/i2p-jpackages.rst:79 msgid "The I2P of the future is Easy to Install" msgstr "" #: i2p2www/blog/2021/09/15/i2p-jpackages.rst:84 msgid "" "One of the things I hear from users the most is that if I2P wants adoption, it\n" "needs to be easy to use for people. Many of them want a \"Tor Browser Like\" user\n" "experience, to quote or paraphrase many familiar Redditors. Installation should\n" "not require complicated and error-prone \"post-installation\" steps. Many new\n" "users are not prepared to deal with their browser configuration in a thorough\n" "and complete way. To address this problem, we created the I2P Profile Bundle\n" "which configured Firefox so that it would automatically \"Just Work\" for I2P.\n" "As it's developed, it's added security features and improved integration with\n" "I2P itself. In it's latest version, it **also** bundles a complete, Jpackage\n" "powered I2P Router. The I2P Firefox Profile is now a fully-fledged distribution\n" "of I2P for Windows, with the only remaining dependency being Firefox itself.\n" "This should provide an unprecedented level of convenience for I2P users on\n" "Windows." msgstr "" #: i2p2www/blog/2021/09/18/i2p-bitcoin.draft.rst:2 msgid "Bitcoin Core adds support for I2P!" msgstr "" #: i2p2www/blog/2021/09/18/i2p-bitcoin.draft.rst:9 msgid "A new use case and a signal of growing acceptance" msgstr "" #: i2p2www/blog/2021/09/18/i2p-bitcoin.draft.rst:11 msgid "" "An event months in the making, Bitcoin Core has added official support for I2P!\n" "Bitcoin-over-I2P nodes can interact fully with the rest of the Bitcoin nodes,\n" "using the help of nodes that operate within both I2P and the clearnet, making\n" "them first-class participants in the Bitcoin network. It's exciting to see\n" "large communities like Bitcoin taking notice of the advantages I2P can bring\n" "to them providing privacy and reachability to people all over the world." msgstr "" #: i2p2www/blog/2021/09/18/i2p-bitcoin.draft.rst:20 msgid "How it Works" msgstr "" #: i2p2www/blog/2021/09/18/i2p-bitcoin.draft.rst:25 msgid "" "I2P support is automatic, via the SAM API. This is also exciting news, because\n" "it highlights some of the things I2P is singularly good at, like empowering \n" "application developers to build I2P connections programmatically and\n" "conveniently. Bitcoin-over-I2P users can use I2P with no manual configuration by\n" "enabling the SAM API and running Bitcoin with I2P enabled." msgstr "" #: i2p2www/blog/2021/09/18/i2p-bitcoin.draft.rst:33 msgid "Configuring your I2P Router" msgstr "" #: i2p2www/blog/2021/09/18/i2p-bitcoin.draft.rst:38 msgid "" "In order to set up an I2P Router to provide anonymous connectivity to bitcoin,\n" "the SAM API needs to be enabled. In Java I2P, you should go to `http://127.0.0.1:7657/configclients\n" "`_. and start the SAM Application Bridge\n" "with the \"Start\" button. You may also want to enable the SAM Application Bridge\n" "by default by checking the \"Run at Startup\" box and clicking \"Save Client\n" "Configuration.\"" msgstr "" #: i2p2www/blog/2021/09/18/i2p-bitcoin.draft.rst:47 msgid "" "On i2pd, the SAM API is normally enabled by default, but if it isn't, you should\n" "set::\n" "\n" " sam.enabled=true\n" "\n" "in your i2pd.conf file." msgstr "" #: i2p2www/blog/2021/09/18/i2p-bitcoin.draft.rst:56 msgid "Configuring your Bitcoin Node for Anonymity and Connectivity" msgstr "" #: i2p2www/blog/2021/09/18/i2p-bitcoin.draft.rst:61 msgid "" "Getting Bitcoin itself launched in an anonymous mode still requires editing some\n" "configuration files in the Bitcoin Data Directory, which is %APPDATA%\\Bitcoin on\n" "Windows, ~/.bitcoin on Linux, and ~/Library/Application Support/Bitcoin/ on Mac\n" "OSX. It also requires at least version 22.0.0 for I2P support to be present." msgstr "" #: i2p2www/blog/2021/09/18/i2p-bitcoin.draft.rst:68 msgid "" "After following these instructions, you should have a private Bitcoin\n" "node which uses I2P for I2P connections, and Tor for .onion and clearnet\n" "connections, so that all your connections are anonymous. For convenience,\n" "Windows users should open their Bitcoin Data Directory by opening the start menu\n" "and searching for \"Run.\" Inside the run prompt, type \"%APPDATA%\\Bitcoin\" and\n" "press enter." msgstr "" #: i2p2www/blog/2021/09/18/i2p-bitcoin.draft.rst:77 msgid "" "In that directory create a file called \"i2p.conf.\" On Windows, you should make\n" "sure that you've add quotes around the file when you save it, in order to\n" "prevent Windows from adding a default file extension to the file. The file\n" "should contain the following I2P-Related Bitcoin configuration options::\n" "\n" " i2psam=127.0.0.1:7656\n" " i2pacceptincoming=true\n" " onlynet=i2p\n" "\n" "Next, you should create another file called \"tor.conf.\" The file should contain\n" "the following Tor related configuration options::\n" "\n" " proxy=127.0.0.1:9050\n" " onion=127.0.0.1:9050\n" " onlynet=tor\n" "\n" "Finally, you'll need to \"include\" these configuration options in your Bitcoin\n" "configuration file, called \"bitcoin.conf\" in the Data Directory. Add these two\n" "lines to your bitcoin.conf file::\n" "\n" " includeconf=i2p.conf\n" " includeconf=tor.conf\n" "\n" "Now your Bitcoin node is configured to only use anonymous connections. In order\n" "to enable direct connections to remote nodes, remove the lines beginning in::\n" "\n" " onlynet=\n" "\n" "You can do this if you do not require your Bitcoin node to be anonymous, and\n" "it helps anonymous users connect to the rest of the Bitcoin network." msgstr ""