Updated translations

This commit is contained in:
str4d
2018-09-12 12:18:57 +00:00
parent 0f0fd000e3
commit 30b922eb9f
161 changed files with 281876 additions and 134680 deletions

File diff suppressed because it is too large Load Diff

File diff suppressed because it is too large Load Diff

View File

@@ -1,7 +1,7 @@
# Translations template for I2P.
# Chinese translations for I2P.
# Copyright (C) 2018 ORGANIZATION
# This file is distributed under the same license as the I2P project.
#
#
# Translators:
# nobody <oiiu19@yahoo.com>, 2015
# nobody <oiiu19@yahoo.com>, 2016
@@ -10,18 +10,18 @@
# yue gao <gaoyue@iie.ac.cn>, 2017
msgid ""
msgstr ""
"Project-Id-Version: I2P\n"
"Project-Id-Version: I2P\n"
"Report-Msgid-Bugs-To: http://trac.i2p2.de\n"
"POT-Creation-Date: 2018-08-24 11:47+0000\n"
"PO-Revision-Date: 2018-08-24 11:51+0000\n"
"Last-Translator: zzzi2p\n"
"Language-Team: Chinese (China) (http://www.transifex.com/otf/I2P/language/zh_CN/)\n"
"Language-Team: Chinese (China) "
"(http://www.transifex.com/otf/I2P/language/zh_CN/)\n"
"Plural-Forms: nplurals=1; plural=0\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Type: text/plain; charset=utf-8\n"
"Content-Transfer-Encoding: 8bit\n"
"Generated-By: Babel 1.3\n"
"Language: zh_CN\n"
"Plural-Forms: nplurals=1; plural=0;\n"
#: i2p2www/pages/site/comparison/freenet.html:2
msgid "I2P Compared to Freenet"
@@ -29,37 +29,57 @@ msgstr "I2P 相比 Freenet"
#: i2p2www/pages/site/comparison/freenet.html:8
msgid ""
"Freenet is a fully distributed, peer to peer anonymous publishing network, offering \n"
"secure ways to store data, as well as some approaches attempting to address the loads\n"
"of a flash flood. While Freenet is designed as a distributed data store, people have\n"
"built applications on top of it to do more generic anonymous communication, such as \n"
"Freenet is a fully distributed, peer to peer anonymous publishing "
"network, offering \n"
"secure ways to store data, as well as some approaches attempting to "
"address the loads\n"
"of a flash flood. While Freenet is designed as a distributed data store,"
" people have\n"
"built applications on top of it to do more generic anonymous "
"communication, such as \n"
"static websites and message boards."
msgstr "Freenet是一个完全分布式的P2P匿名发布网络提供安全的数据存储方式以及一些试图解决洪泛负载的方法。虽然Freenet的设计目的是分布式的数据存储但是人们也在Freenet之上建立了一些应用程序使得更通用的匿名通信成为可能如静态网站和留言板等。"
#: i2p2www/pages/site/comparison/freenet.html:16
#, python-format
msgid ""
"Compared to I2P, Freenet offers some substantial benefits - it is a distributed data\n"
"store, while I2P is not, allowing people to retrieve the content published by others \n"
"even when the publisher is no longer online. In addition, it should be able to \n"
"distribute popular data fairly efficiently. I2P itself does not and will not provide \n"
"this functionality. On the other hand, there is overlap for users who simply want to \n"
"communicate with each other anonymously through websites, message boards, file sharing\n"
"programs, etc. There have also been some attempts to develop a distributed data \n"
"Compared to I2P, Freenet offers some substantial benefits - it is a "
"distributed data\n"
"store, while I2P is not, allowing people to retrieve the content "
"published by others \n"
"even when the publisher is no longer online. In addition, it should be "
"able to \n"
"distribute popular data fairly efficiently. I2P itself does not and will"
" not provide \n"
"this functionality. On the other hand, there is overlap for users who "
"simply want to \n"
"communicate with each other anonymously through websites, message boards,"
" file sharing\n"
"programs, etc. There have also been some attempts to develop a "
"distributed data \n"
"store to run on top of I2P,\n"
"(most recently a port of <a href=\"%(tahoe)s\">Tahoe-LAFS</a>)\n"
"but nothing is yet ready for general use."
msgstr "相比于I2PFreenet提供了一些实质性的好处——它是一个分布式的数据存储网络而I2P并不是Freenet允许用户检索已发布的内容即便内容的发布者已经离线了。此外Freenet应该能够高效地分发流行数据。I2P本身不提供此功能。另一方面对于那些只想通过网站、留言板、文件共享程序等方式匿名交流的用户来说这是有重叠的。I2P也进行了一些尝试以支持分布式数据存储(最近的是<a href=\"%(tahoe)s\">Tahoe-LAFS</a>的移植) 但还没有准备好全面使用。"
msgstr ""
"相比于I2PFreenet提供了一些实质性的好处——它是一个分布式的数据存储网络而I2P并不是Freenet允许用户检索已发布的内容即便内容的发布者已经离线了。此外Freenet应该能够高效地分发流行数据。I2P本身不提供此功能。另一方面对于那些只想通过网站、留言板、文件共享程序等方式匿名交流的用户来说这是有重叠的。I2P也进行了一些尝试以支持分布式数据存储(最近的是<a"
" href=\"%(tahoe)s\">Tahoe-LAFS</a>的移植) 但还没有准备好全面使用。"
#: i2p2www/pages/site/comparison/freenet.html:29
msgid ""
"However, even ignoring any implementations issues, there are some concerns \n"
"about Freenet's algorithms from both a scalability and anonymity perspective, owing \n"
"largely to Freenet's heuristic driven routing. The interactions of various techniques \n"
"certainly may successfully deter various attacks, and perhaps some aspects of the \n"
"routing algorithms will provide the hoped for scalability. Unfortunately, not much\n"
"analysis of the algorithms involved has resulted in positive results, but there is still\n"
"hope. At the very least, Freenet does provide substantial anonymity against an attacker\n"
"However, even ignoring any implementations issues, there are some "
"concerns \n"
"about Freenet's algorithms from both a scalability and anonymity "
"perspective, owing \n"
"largely to Freenet's heuristic driven routing. The interactions of "
"various techniques \n"
"certainly may successfully deter various attacks, and perhaps some "
"aspects of the \n"
"routing algorithms will provide the hoped for scalability. "
"Unfortunately, not much\n"
"analysis of the algorithms involved has resulted in positive results, but"
" there is still\n"
"hope. At the very least, Freenet does provide substantial anonymity "
"against an attacker\n"
"who does not have the resources necessary to analyze it further."
msgstr ""
@@ -69,11 +89,15 @@ msgstr "I2P与其他项目的比较"
#: i2p2www/pages/site/comparison/index.html:4
msgid ""
"There are a great many other applications and projects working on anonymous \n"
"communication and I2P has been inspired by much of their efforts. This is not \n"
"There are a great many other applications and projects working on "
"anonymous \n"
"communication and I2P has been inspired by much of their efforts. This "
"is not \n"
"a comprehensive list of anonymity resources - both freehaven's \n"
"<a href=\"http://freehaven.net/anonbib/topic.html\">Anonymity Bibliography</a>\n"
"and GNUnet's <a href=\"https://www.gnunet.org/links/\">related projects</a>\n"
"<a href=\"http://freehaven.net/anonbib/topic.html\">Anonymity "
"Bibliography</a>\n"
"and GNUnet's <a href=\"https://www.gnunet.org/links/\">related "
"projects</a>\n"
"serve that purpose well. That said, a few systems stand out for further\n"
"comparison. The following have individual comparison pages:"
msgstr ""
@@ -88,8 +112,10 @@ msgstr ""
#: i2p2www/pages/site/comparison/index.html:33
#, python-format
msgid ""
"The content of this page is subject to update, discussion and dispute, and we welcome comments and additions.\n"
"You may contribute an analysis by entering a <a href=\"%(trac)s\">new ticket on Trac</a>."
"The content of this page is subject to update, discussion and dispute, "
"and we welcome comments and additions.\n"
"You may contribute an analysis by entering a <a href=\"%(trac)s\">new "
"ticket on Trac</a>."
msgstr ""
#: i2p2www/pages/site/comparison/other-networks.html:2
@@ -114,31 +140,45 @@ msgstr ""
#, python-format
msgid ""
"RetroShare is a set of peer-to-peer applications running in a\n"
"<a href=\"%(f2fwiki)s\">Friend-to-friend (F2F)</a> network. Each peer of such F2F \n"
"network makes direct IP connections only to authenticated peers (\"friends\") after explicit \n"
"certificates exchange. It can discover unauthenticated peers (e.g. friends of friends), \n"
"but connections to them are relayed over \"friend\" peers for providing privacy and anonymity."
"<a href=\"%(f2fwiki)s\">Friend-to-friend (F2F)</a> network. Each peer of "
"such F2F \n"
"network makes direct IP connections only to authenticated peers "
"(\"friends\") after explicit \n"
"certificates exchange. It can discover unauthenticated peers (e.g. "
"friends of friends), \n"
"but connections to them are relayed over \"friend\" peers for providing "
"privacy and anonymity."
msgstr ""
#: i2p2www/pages/site/comparison/other-networks.html:37
msgid ""
"RetroShare is designed to build a private network of trusted peers, while I2P is designed \n"
"to be a large-scaled public anonymous network. Recent versions of RetroShare have options to run \n"
"as a public \"darknet\" by using I2P or Tor as a transport. That way all connections are \n"
"RetroShare is designed to build a private network of trusted peers, while"
" I2P is designed \n"
"to be a large-scaled public anonymous network. Recent versions of "
"RetroShare have options to run \n"
"as a public \"darknet\" by using I2P or Tor as a transport. That way all "
"connections are \n"
"anonymized and no trust is required for adding new \"friends\"."
msgstr ""
#: i2p2www/pages/site/comparison/other-networks.html:48
#, python-format
msgid ""
"Morphmix and Tarzan are both fully distributed, peer to peer networks of \n"
"anonymizing proxies, allowing people to tunnel out through the low latency \n"
"mix network. Morphmix includes some very interesting collusion detection \n"
"algorithms and Sybil defenses, while Tarzan makes use of the scarcity of IP\n"
"Morphmix and Tarzan are both fully distributed, peer to peer networks of"
" \n"
"anonymizing proxies, allowing people to tunnel out through the low "
"latency \n"
"mix network. Morphmix includes some very interesting collusion detection"
" \n"
"algorithms and Sybil defenses, while Tarzan makes use of the scarcity of "
"IP\n"
"addresses to accomplish the same. The two primary differences between \n"
"these systems and I2P are related to I2P's <a href=\"%(threatmodel)s\">threat model</a> \n"
"and their out-proxy design (as opposed to providing both sender and receiver \n"
"anonymity). There is source code available to both systems, but we are not aware \n"
"these systems and I2P are related to I2P's <a "
"href=\"%(threatmodel)s\">threat model</a> \n"
"and their out-proxy design (as opposed to providing both sender and "
"receiver \n"
"anonymity). There is source code available to both systems, but we are "
"not aware \n"
"of their use outside of academic environments."
msgstr ""
@@ -146,15 +186,19 @@ msgstr ""
#, python-format
msgid ""
"\n"
"Mixminion and Mixmaster are networks to support anonymous email against a very\n"
"Mixminion and Mixmaster are networks to support anonymous email against a"
" very\n"
"powerful adversary.\n"
"High-latency messaging applications running on top of I2P\n"
"(for example <a href=\"%(syndie)s\">Syndie</a> or I2PBote)\n"
"may perhaps prove adequate to meet the threat\n"
"model of those adversaries, while running in parallel along side the needs of low latency users, to provide\n"
"model of those adversaries, while running in parallel along side the "
"needs of low latency users, to provide\n"
"a significantly larger anonymity set.\n"
"High-latency support within the I2P router itself may or may not be added in a distant future release.\n"
"It is too early to say if I2P will meet the needs of users requiring extreme protection for email."
"High-latency support within the I2P router itself may or may not be added"
" in a distant future release.\n"
"It is too early to say if I2P will meet the needs of users requiring "
"extreme protection for email."
msgstr ""
#: i2p2www/pages/site/comparison/other-networks.html:184
@@ -166,20 +210,32 @@ msgstr ""
#: i2p2www/pages/site/comparison/other-networks.html:194
#, python-format
msgid ""
"JAP (Java Anonymous Proxy) is a network of mix cascades for anonymizing web requests,\n"
"and as such it has a few centralized nodes (participants in the cascade) that blend\n"
"and mix requests from clients through the sequence of nodes (the cascade) before \n"
"proxying out onto the web. The scope, threat model, and security is substantially \n"
"different from I2P, but for those who don't require significant anonymity but still\n"
"are not satisfied with an Anonymizer-like service, JAP is worth reviewing. One\n"
"caution to note is that anyone under the jurisdiction of the German courts may want\n"
"to take care, as the German Federal Bureau of Criminal Investigation (FBCI) has \n"
"JAP (Java Anonymous Proxy) is a network of mix cascades for anonymizing "
"web requests,\n"
"and as such it has a few centralized nodes (participants in the cascade) "
"that blend\n"
"and mix requests from clients through the sequence of nodes (the cascade)"
" before \n"
"proxying out onto the web. The scope, threat model, and security is "
"substantially \n"
"different from I2P, but for those who don't require significant anonymity"
" but still\n"
"are not satisfied with an Anonymizer-like service, JAP is worth "
"reviewing. One\n"
"caution to note is that anyone under the jurisdiction of the German "
"courts may want\n"
"to take care, as the German Federal Bureau of Criminal Investigation "
"(FBCI) has \n"
"successfully mounted an \n"
"<a href=\"%(url)s\">attack</a> \n"
"on the network. Even though the method of this attack was later found to be illegal \n"
"in the German courts, the fact that the data was successfully collected is the \n"
"concern. Courts change their minds based upon circumstance, and this is evidence that \n"
"if a government body or intelligence agency wanted to, they could gather the data, even \n"
"on the network. Even though the method of this attack was later found to"
" be illegal \n"
"in the German courts, the fact that the data was successfully collected "
"is the \n"
"concern. Courts change their minds based upon circumstance, and this is "
"evidence that \n"
"if a government body or intelligence agency wanted to, they could gather "
"the data, even \n"
"if it may be found inadmissible in some courts later)"
msgstr ""
@@ -188,23 +244,36 @@ msgstr ""
msgid ""
"Both of these systems work through the same basic \n"
"<a href=\"%(antnet)s\">antnet</a> routing, providing some degree of\n"
"anonymity based on the threat model of providing plausible deniability against a simple \n"
"non-colluding adversary. With the antnet routing, they first either do a random walk or a \n"
"broadcast search to find some peer with the data or identity desired, and then use a feedback\n"
"algorithm to optimize that found path. This works well for applications that merely want to know \n"
"what other people around them have to offer - \"How are y'all doing\" vs. \"Hey Alice, how are you\" - \n"
"you basically get a local cluster of nodes that can share files with and maintain some degree of \n"
"anonymity (though you don't have much control over who is in that group of peers)."
"anonymity based on the threat model of providing plausible deniability "
"against a simple \n"
"non-colluding adversary. With the antnet routing, they first either do a"
" random walk or a \n"
"broadcast search to find some peer with the data or identity desired, and"
" then use a feedback\n"
"algorithm to optimize that found path. This works well for applications "
"that merely want to know \n"
"what other people around them have to offer - \"How are y'all doing\" vs."
" \"Hey Alice, how are you\" - \n"
"you basically get a local cluster of nodes that can share files with and "
"maintain some degree of \n"
"anonymity (though you don't have much control over who is in that group "
"of peers)."
msgstr ""
#: i2p2www/pages/site/comparison/other-networks.html:228
msgid ""
"However, the algorithm does not scale well at all - if the application wants to speak with a \n"
"particular peer it ends up doing a broadcast search or random walk (though if they are lucky enough\n"
"for that to succeed, the antnet routing should optimize that found connection). This means that \n"
"while these networks can work great at small scales, they are not suitable for large networks where\n"
"someone wants to get in touch with another specific peer. That does not mean that there is no \n"
"value in these systems, just that their applicability is limited to situations where their \n"
"However, the algorithm does not scale well at all - if the application "
"wants to speak with a \n"
"particular peer it ends up doing a broadcast search or random walk "
"(though if they are lucky enough\n"
"for that to succeed, the antnet routing should optimize that found "
"connection). This means that \n"
"while these networks can work great at small scales, they are not "
"suitable for large networks where\n"
"someone wants to get in touch with another specific peer. That does not "
"mean that there is no \n"
"value in these systems, just that their applicability is limited to "
"situations where their \n"
"particular issues can be addressed."
msgstr ""
@@ -212,8 +281,10 @@ msgstr ""
#, python-format
msgid ""
"This was a closed-source network targeted at Iranian users.\n"
"Tor did a <a href=\"%(torpost)s\">good writeup on what to look for in a circumvention tool</a>.\n"
"Suffice it to say that being closed source and publicly targeting a specific country are not good ideas.\n"
"Tor did a <a href=\"%(torpost)s\">good writeup on what to look for in a "
"circumvention tool</a>.\n"
"Suffice it to say that being closed source and publicly targeting a "
"specific country are not good ideas.\n"
"I2P is, of course, open source. However, that source, and our\n"
"<a href=\"%(docs)s\">technical documentation</a>, need much more review."
msgstr ""
@@ -433,10 +504,13 @@ msgstr "Tor 相对 I2P 的优势"
#: i2p2www/pages/site/comparison/tor.html:78
msgid ""
"Much bigger user base; much more visibility in the academic and hacker communities; benefits from\n"
"Much bigger user base; much more visibility in the academic and hacker "
"communities; benefits from\n"
"formal studies of anonymity, resistance, and performance;\n"
"has a non-anonymous, visible, university-based leader"
msgstr "大许多的用户群;在学术和黑客群体中得到较多关注;\n基于正式研究的匿名性、抵抗性和性能优势有一个非匿名的来自大学的领导者"
msgstr ""
"大许多的用户群;在学术和黑客群体中得到较多关注;\n"
"基于正式研究的匿名性、抵抗性和性能优势;有一个非匿名的,来自大学的领导者"
#: i2p2www/pages/site/comparison/tor.html:84
msgid "Has already solved some scaling issues I2P has yet to address"
@@ -452,17 +526,20 @@ msgstr "有更多的开发者,其中有些是全职的"
#: i2p2www/pages/site/comparison/tor.html:88
msgid ""
"More resistant to state-level blocking due to TLS transport layer and bridges\n"
"(I2P has proposals for \"full restricted routes\" but these are not yet implemented)"
msgstr "由于具有基于 TLS 的传输和网桥,对国家级封锁有更强的抵抗\nI2P 有“完全限制路由”的提案,但还没有实现)"
"More resistant to state-level blocking due to TLS transport layer and "
"bridges\n"
"(I2P has proposals for \"full restricted routes\" but these are not yet "
"implemented)"
msgstr ""
"由于具有基于 TLS 的传输和网桥,对国家级封锁有更强的抵抗\n"
"I2P 有“完全限制路由”的提案,但还没有实现)"
#: i2p2www/pages/site/comparison/tor.html:93
msgid "Big enough that it has had to adapt to blocking and DOS attempts"
msgstr "足够大所以它已经适应了封锁和拒绝服务攻击"
#: i2p2www/pages/site/comparison/tor.html:94
msgid ""
"Designed and optimized for exit traffic, with a large number of exit nodes"
msgid "Designed and optimized for exit traffic, with a large number of exit nodes"
msgstr ""
#: i2p2www/pages/site/comparison/tor.html:96
@@ -501,8 +578,8 @@ msgstr "I2P 相对 Tor 的优势"
#: i2p2www/pages/site/comparison/tor.html:120
msgid ""
"Designed and optimized for hidden services, which are much faster than in "
"Tor"
"Designed and optimized for hidden services, which are much faster than in"
" Tor"
msgstr "专为隐藏服务设计和优化,在这方面比 Tor 快许多"
#: i2p2www/pages/site/comparison/tor.html:121
@@ -519,7 +596,9 @@ msgstr "通过不断分析和比较性能,而不是根据目录声称的流量
msgid ""
"Floodfill peers (\"directory servers\") are varying and untrusted,\n"
"rather than hardcoded"
msgstr "种子节点(“目录服务器”)是持续变化并且不被信任的,\n而不是硬编码写入"
msgstr ""
"种子节点(“目录服务器”)是持续变化并且不被信任的,\n"
"而不是硬编码写入"
#: i2p2www/pages/site/comparison/tor.html:134
msgid "Small enough that it hasn't been blocked or DOSed much, or at all"
@@ -639,3 +718,4 @@ msgid ""
"where the endpoint will inject dummy messages if there\n"
"are insufficient messages, etc)"
msgstr ""

File diff suppressed because it is too large Load Diff

File diff suppressed because it is too large Load Diff

File diff suppressed because it is too large Load Diff

View File

@@ -1,7 +1,7 @@
# Translations template for I2P.
# Chinese translations for I2P.
# Copyright (C) 2018 ORGANIZATION
# This file is distributed under the same license as the I2P project.
#
#
# Translators:
# xkimo_daeee <michael_ies@yahoo.com>, 2014
# Tommy Lmath <l5h5t7@qq.com>, 2016
@@ -9,18 +9,18 @@
# YF <yfdyh000@gmail.com>, 2014,2016
msgid ""
msgstr ""
"Project-Id-Version: I2P\n"
"Project-Id-Version: I2P\n"
"Report-Msgid-Bugs-To: http://trac.i2p2.de\n"
"POT-Creation-Date: 2018-06-24 13:48+0000\n"
"PO-Revision-Date: 2018-06-24 18:45+0000\n"
"Last-Translator: ducki2p <ducki2p@gmail.com>\n"
"Language-Team: Chinese (China) (http://www.transifex.com/otf/I2P/language/zh_CN/)\n"
"Language-Team: Chinese (China) "
"(http://www.transifex.com/otf/I2P/language/zh_CN/)\n"
"Plural-Forms: nplurals=1; plural=0\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Type: text/plain; charset=utf-8\n"
"Content-Transfer-Encoding: 8bit\n"
"Generated-By: Babel 1.3\n"
"Language: zh_CN\n"
"Plural-Forms: nplurals=1; plural=0;\n"
#: i2p2www/pages/site/research/index.html:2
msgid "Academic Research"
@@ -41,11 +41,16 @@ msgstr ""
#: i2p2www/pages/site/research/index.html:10
msgid ""
"I2P is a very unique project that unfortunately has not received the wider\n"
"academic attention it deserves. To date, most research focus on anonymous and\n"
"onion-routing technology has been around Tor, and while those papers benefit us\n"
"as well, there is a great need for I2P-focused research. This plays a key role\n"
"in both maintaining the security and integrity of the network, as well as\n"
"I2P is a very unique project that unfortunately has not received the "
"wider\n"
"academic attention it deserves. To date, most research focus on anonymous"
" and\n"
"onion-routing technology has been around Tor, and while those papers "
"benefit us\n"
"as well, there is a great need for I2P-focused research. This plays a key"
" role\n"
"in both maintaining the security and integrity of the network, as well as"
"\n"
"opening doors for more impactful future development."
msgstr ""
@@ -53,14 +58,23 @@ msgstr ""
#, python-format
msgid ""
"\n"
"There is a large research community investigating a wide range of aspects of\n"
"anonymity. For a current and comprehensive list of relevant papers, see the\n"
"There is a large research community investigating a wide range of aspects"
" of\n"
"anonymity. For a current and comprehensive list of relevant papers, see "
"the\n"
"<a href=\"%(anonbib)s\">Free Haven Anonymity Bibliography</a>.\n"
"I2P benefits from much of the research into Tor and onion routing, but there is\n"
"little dedicated research interest into the theory behind I2P, and the choices\n"
"and tradeoffs that the network makes. This presents a unique opportunity for\n"
"I2P benefits from much of the research into Tor and onion routing, but "
"there is\n"
"little dedicated research interest into the theory behind I2P, and the "
"choices\n"
"and tradeoffs that the network makes. This presents a unique opportunity "
"for\n"
"original research.\n"
msgstr "\n有一个调查匿名性方面范围广泛的大型研究社区 .当前综合有关论文列表,请参阅<a href=\"%(anonbib)s\">自由避风港匿名参考书目</a>. I2P 得益于对 Tor 和裕 洋葱路由的大量研究. 不过, 对I2P后面的理论以及网络做出的选择和权衡的研究几乎没有. 这为原创研究提供了一个独特的条件.\n"
msgstr ""
"\n"
"有一个调查匿名性方面范围广泛的大型研究社区 .当前综合有关论文列表,请参阅<a "
"href=\"%(anonbib)s\">自由避风港匿名参考书目</a>. I2P 得益于对 Tor 和裕 洋葱路由的大量研究. 不过, "
"对I2P后面的理论以及网络做出的选择和权衡的研究几乎没有. 这为原创研究提供了一个独特的条件.\n"
#: i2p2www/pages/site/research/index.html:29
#, python-format
@@ -73,7 +87,8 @@ msgstr "已知的已发表的有关 I2P 的论文在<a href=\"%(papers)s\">这
msgid ""
"\n"
"This page aims to outline the most needed fields of research, notes to\n"
"potential researchers, our general safety guidelines as well as an expanding\n"
"potential researchers, our general safety guidelines as well as an "
"expanding\n"
"list of open questions that you can begin on at any time.\n"
msgstr ""
@@ -87,12 +102,16 @@ msgstr ""
#: i2p2www/pages/site/research/index.html:44
msgid ""
"While all research on the I2P network is beneficial and appreciated, there are\n"
"While all research on the I2P network is beneficial and appreciated, "
"there are\n"
"certain areas which are more in need than others - most so in defensive\n"
"research. Most people enjoy coming up with fun ways to launch offensives\n"
"against anonymous software, and this is further reinforced by the incentives in\n"
"academic institutions. While we know it is often not the first choice for\n"
"researchers, We would certainly appreciate any and all work towards ways to\n"
"against anonymous software, and this is further reinforced by the "
"incentives in\n"
"academic institutions. While we know it is often not the first choice for"
"\n"
"researchers, We would certainly appreciate any and all work towards ways "
"to\n"
"fortify the network!"
msgstr ""
@@ -103,17 +122,27 @@ msgstr ""
#: i2p2www/pages/site/research/index.html:56
#, python-format
msgid ""
"If you've decided on a research topic that aims to hands-on investigate the I2P\n"
"network or solve a problem of large proportions we ask you to <b>please</b> \n"
"<a href=\"%(contact)s\">communicate your ideas</a> to the development team, the\n"
"sooner the better. I2P is under constant development and a significant amount\n"
"of roadmapping occurs, therefore your problem may have already been identified\n"
"and flagged for update or patch. In the unlikely event you are conducting\n"
"testing that overlaps with / would be of interest to another research project\n"
"already in motion, we are also able to make you aware of this (with their\n"
"permission, of course), and possibly open the door for collaboration. There is\n"
"If you've decided on a research topic that aims to hands-on investigate "
"the I2P\n"
"network or solve a problem of large proportions we ask you to "
"<b>please</b> \n"
"<a href=\"%(contact)s\">communicate your ideas</a> to the development "
"team, the\n"
"sooner the better. I2P is under constant development and a significant "
"amount\n"
"of roadmapping occurs, therefore your problem may have already been "
"identified\n"
"and flagged for update or patch. In the unlikely event you are conducting"
"\n"
"testing that overlaps with / would be of interest to another research "
"project\n"
"already in motion, we are also able to make you aware of this (with their"
"\n"
"permission, of course), and possibly open the door for collaboration. "
"There is\n"
"also a chance that the test itself may significantly harm the network or\n"
"regular users, and the team may have ideas or suggestions to mitigate that risk\n"
"regular users, and the team may have ideas or suggestions to mitigate "
"that risk\n"
"and increase the safety of your testing."
msgstr ""
@@ -129,11 +158,13 @@ msgstr ""
msgid ""
"<ol>\n"
" <li>\n"
" Consider the benefits and risks - is there any doubt that the research\n"
" Consider the benefits and risks - is there any doubt that the "
"research\n"
" provides more value than danger?\n"
" </li>\n"
" <li>\n"
" If the research can be done on a test network then that is the preferred\n"
" If the research can be done on a test network then that is the "
"preferred\n"
" method\n"
" </li>\n"
" <li>\n"
@@ -141,8 +172,10 @@ msgid ""
" collecting data about yourself\n"
" </li>\n"
" <li>\n"
" If you need 'bigger data', It is recommended to first see if you can use\n"
" data sets from previous experiments or other third party resources is\n"
" If you need 'bigger data', It is recommended to first see if you can "
"use\n"
" data sets from previous experiments or other third party resources is"
"\n"
" recommended\n"
" </li>\n"
" <li>\n"
@@ -150,8 +183,10 @@ msgid ""
" publication and collect as little as possible\n"
" </li>\n"
" <li>\n"
" After testing and before publish, review that all data which is to be\n"
" published publicly is <b><i>not</i></b> intended to be private by the\n"
" After testing and before publish, review that all data which is to be"
"\n"
" published publicly is <b><i>not</i></b> intended to be private by the"
"\n"
" originator\n"
" </li>\n"
"</ol>"
@@ -163,24 +198,32 @@ msgstr ""
#: i2p2www/pages/site/research/index.html:108
msgid ""
"I2P can be run as a separate test network by controlling the locations that a\n"
"I2P can be run as a separate test network by controlling the locations "
"that a\n"
"new router reseeds from so that it only finds other test routers.\n"
"\n"
"The standard mode of operation is to have one JVM per router instance; hence\n"
"running multiple copies of I2P on a single machine is inadvisable, both due to\n"
"The standard mode of operation is to have one JVM per router instance; "
"hence\n"
"running multiple copies of I2P on a single machine is inadvisable, both "
"due to\n"
"the potential resource drain and the certain port conflicts. To better\n"
"facilitate setting up small test networks, I2P has a multirouter mode which\n"
"facilitate setting up small test networks, I2P has a multirouter mode "
"which\n"
"enables multiple distinct routers to be run in the same JVM.\n"
"\n"
"MultiRouter can be started from the i2p base directory by running the below\n"
"MultiRouter can be started from the i2p base directory by running the "
"below\n"
"command."
msgstr ""
#: i2p2www/pages/site/research/index.html:124
msgid ""
"Additionally, I2P can be started in a virtual network mode. This mode disables\n"
"all transports, allowing the router to be tested in isolation without network\n"
"traffic. To enable this mode, add <code>i2p.vmCommSystem=true</code> to the\n"
"Additionally, I2P can be started in a virtual network mode. This mode "
"disables\n"
"all transports, allowing the router to be tested in isolation without "
"network\n"
"traffic. To enable this mode, add <code>i2p.vmCommSystem=true</code> to "
"the\n"
"router.config before starting."
msgstr ""
@@ -191,10 +234,13 @@ msgstr ""
#: i2p2www/pages/site/research/index.html:133
#, python-format
msgid ""
"As stated above in the researcher notes, please <a href=\"%(contact)s\">contact\n"
"As stated above in the researcher notes, please <a "
"href=\"%(contact)s\">contact\n"
" us</a> before you commence your testing. While we do not discourage\n"
"researchers from responsibly testing their ideas on the live network, if an\n"
"attack becomes apparent and we don't have any line of communication then we\n"
"researchers from responsibly testing their ideas on the live network, if "
"an\n"
"attack becomes apparent and we don't have any line of communication then "
"we\n"
"will end up taking countermeasures which could interfere with the test."
msgstr ""
@@ -204,23 +250,35 @@ msgstr "路由器系列配置"
#: i2p2www/pages/site/research/index.html:143
msgid ""
"As of release 0.9.25, I2P supports a router family configuration. This provides\n"
"researchers who run multiple routers with the means to publicly identify those\n"
"routers. In turn, this helps the I2P project understand that these routers are\n"
"not running an attack on the network. It also will prevent other routers from\n"
"including multiple routers of the family in a single tunnel, which could lead\n"
"to deanonymization. Routers that appear to be colluding but do not have a\n"
"declared family may be assumed to be an attack on the network, and may be\n"
"blocked. The best way to ensure the success of your research project is to work\n"
"As of release 0.9.25, I2P supports a router family configuration. This "
"provides\n"
"researchers who run multiple routers with the means to publicly identify "
"those\n"
"routers. In turn, this helps the I2P project understand that these "
"routers are\n"
"not running an attack on the network. It also will prevent other routers "
"from\n"
"including multiple routers of the family in a single tunnel, which could "
"lead\n"
"to deanonymization. Routers that appear to be colluding but do not have a"
"\n"
"declared family may be assumed to be an attack on the network, and may be"
"\n"
"blocked. The best way to ensure the success of your research project is "
"to work\n"
"with us directly."
msgstr ""
#: i2p2www/pages/site/research/index.html:155
msgid ""
"A router family shares a private key so that participation in the family cannot\n"
"be spoofed. To configure a router family, click on the 'I2P Internals' link in\n"
"the router console, and then on the 'Family' tab. Follow the instructions there\n"
"to generate the private key for the first router in the family. Then, export\n"
"A router family shares a private key so that participation in the family "
"cannot\n"
"be spoofed. To configure a router family, click on the 'I2P Internals' "
"link in\n"
"the router console, and then on the 'Family' tab. Follow the instructions"
" there\n"
"to generate the private key for the first router in the family. Then, "
"export\n"
"the key from that router, and import it to other members of the family."
msgstr ""
@@ -279,7 +337,8 @@ msgstr ""
#: i2p2www/pages/site/research/vrp.html:6
msgid ""
"\n"
"This process is subject to change. Please refer to this page for the current VRP."
"This process is subject to change. Please refer to this page for the "
"current VRP."
msgstr ""
#: i2p2www/pages/site/research/vrp.html:10
@@ -291,8 +350,7 @@ msgid "Security Response Team"
msgstr ""
#: i2p2www/pages/site/research/vrp.html:16
msgid ""
"Only the following members have access to the security point of contact:"
msgid "Only the following members have access to the security point of contact:"
msgstr ""
#: i2p2www/pages/site/research/vrp.html:25
@@ -309,7 +367,8 @@ msgstr "电子邮件"
#: i2p2www/pages/site/research/vrp.html:37
msgid ""
"Response Team designates a Response Manager who is in charge of the particular\n"
"Response Team designates a Response Manager who is in charge of the "
"particular\n"
"report based on availability and/or knowledge-set."
msgstr ""
@@ -322,7 +381,8 @@ msgstr ""
#: i2p2www/pages/site/research/vrp.html:47
msgid ""
"Response Manager makes inquiries to satisfy any needed information and to\n"
"Response Manager makes inquiries to satisfy any needed information and to"
"\n"
"confirm if submission is indeed a vulnerability."
msgstr ""
@@ -342,13 +402,14 @@ msgstr ""
#: i2p2www/pages/site/research/vrp.html:62
msgid ""
"Response Manager moves discussion to a new or existing ticket on public Trac"
" if necessary."
"Response Manager moves discussion to a new or existing ticket on public "
"Trac if necessary."
msgstr ""
#: i2p2www/pages/site/research/vrp.html:70
msgid ""
"If over email, Response Manager opens a HackerOne issue for new submission."
"If over email, Response Manager opens a HackerOne issue for new "
"submission."
msgstr ""
#: i2p2www/pages/site/research/vrp.html:74
@@ -360,8 +421,8 @@ msgstr ""
#: i2p2www/pages/site/research/vrp.html:79
msgid ""
"Effects network as a whole, has potential to break entire network or is on a"
" scale of great catastrophe."
"Effects network as a whole, has potential to break entire network or is "
"on a scale of great catastrophe."
msgstr ""
#: i2p2www/pages/site/research/vrp.html:83
@@ -379,18 +440,19 @@ msgstr ""
#: i2p2www/pages/site/research/vrp.html:97
#, python-format
msgid ""
"HIGH severities must be notified on website and news feed within %(limit)s\n"
"HIGH severities must be notified on website and news feed within "
"%(limit)s\n"
"working days of classification."
msgstr ""
#: i2p2www/pages/site/research/vrp.html:102
msgid ""
"The notification should list appropriate steps for users to take, if any."
msgid "The notification should list appropriate steps for users to take, if any."
msgstr ""
#: i2p2www/pages/site/research/vrp.html:105
msgid ""
"The notification must not include any details that could suggest an exploitation\n"
"The notification must not include any details that could suggest an "
"exploitation\n"
"path."
msgstr ""
@@ -412,7 +474,8 @@ msgstr ""
#: i2p2www/pages/site/research/vrp.html:126
msgid ""
"Response Manager designates a PRIVATE monotone \"hotfix branch\" to work in."
"Response Manager designates a PRIVATE monotone \"hotfix branch\" to work "
"in."
msgstr ""
#: i2p2www/pages/site/research/vrp.html:129
@@ -421,8 +484,10 @@ msgstr ""
#: i2p2www/pages/site/research/vrp.html:132
msgid ""
"Any messages associated with PUBLIC commits during the time of review should not\n"
"make reference to the security nature of the PRIVATE branch or its commits."
"Any messages associated with PUBLIC commits during the time of review "
"should not\n"
"make reference to the security nature of the PRIVATE branch or its "
"commits."
msgstr ""
#: i2p2www/pages/site/research/vrp.html:136
@@ -457,7 +522,8 @@ msgstr ""
#: i2p2www/pages/site/research/vrp.html:163
msgid ""
"Response Manager includes vulnerability announcement draft in release notes."
"Response Manager includes vulnerability announcement draft in release "
"notes."
msgstr ""
#: i2p2www/pages/site/research/vrp.html:166
@@ -470,13 +536,11 @@ msgstr ""
#: i2p2www/pages/site/research/vrp.html:176
#, python-format
msgid ""
"Response Team has %(limit)s days to fulfill all points within section III."
msgid "Response Team has %(limit)s days to fulfill all points within section III."
msgstr ""
#: i2p2www/pages/site/research/vrp.html:180
msgid ""
"If the Incident Response process in section III is successfully completed:"
msgid "If the Incident Response process in section III is successfully completed:"
msgstr ""
#: i2p2www/pages/site/research/vrp.html:184
@@ -528,8 +592,8 @@ msgstr ""
#: i2p2www/pages/site/research/vrp.html:215
msgid ""
"Workarounds (configuration changes users can make to reduce their exposure "
"to the vulnerability)."
"Workarounds (configuration changes users can make to reduce their "
"exposure to the vulnerability)."
msgstr ""
#: i2p2www/pages/site/research/vrp.html:218
@@ -537,14 +601,13 @@ msgid "If applicable, credits to the original reporter."
msgstr ""
#: i2p2www/pages/site/research/vrp.html:223
msgid ""
"Release finalized vulnerability announcement on website and in news feed."
msgid "Release finalized vulnerability announcement on website and in news feed."
msgstr ""
#: i2p2www/pages/site/research/vrp.html:226
msgid ""
"For HIGH severities, release finalized vulnerability announcement on well-"
"known mailing lists:"
"For HIGH severities, release finalized vulnerability announcement on "
"well-known mailing lists:"
msgstr ""
#: i2p2www/pages/site/research/vrp.html:234
@@ -553,8 +616,8 @@ msgstr ""
#: i2p2www/pages/site/research/vrp.html:238
msgid ""
"The commit that applied the fix is made reference too in a future commit and"
" includes a CVE-ID."
"The commit that applied the fix is made reference too in a future commit "
"and includes a CVE-ID."
msgstr ""
#: i2p2www/pages/site/research/vrp.html:246
@@ -565,28 +628,33 @@ msgstr ""
#: i2p2www/pages/site/research/vrp.html:250
msgid ""
"Response Team and developers organize an IRC meeting to discuss why/what points\n"
"in section III were not resolved and how the team can resolve them in the\n"
"Response Team and developers organize an IRC meeting to discuss why/what "
"points\n"
"in section III were not resolved and how the team can resolve them in the"
"\n"
"future."
msgstr ""
#: i2p2www/pages/site/research/vrp.html:255
msgid ""
"Any developer meetings immediately following the incident should include points\n"
"Any developer meetings immediately following the incident should include "
"points\n"
"made in section V."
msgstr ""
#: i2p2www/pages/site/research/vrp.html:259
msgid ""
"If disputes arise about whether or when to disclose information about a\n"
"vulnerability, the Response Team will publicly discuss the issue via IRC and\n"
"vulnerability, the Response Team will publicly discuss the issue via IRC "
"and\n"
"attempt to reach consensus."
msgstr ""
#: i2p2www/pages/site/research/vrp.html:264
#, python-format
msgid ""
"If consensus on a timely disclosure is not met (no later than %(limit)s days),\n"
"If consensus on a timely disclosure is not met (no later than %(limit)s "
"days),\n"
"the researcher (after %(limit)s days) has every right to expose the\n"
"vulnerability to the public."
msgstr ""
@@ -601,8 +669,7 @@ msgstr ""
#: i2p2www/pages/site/research/vrp.html:278
#: i2p2www/pages/site/research/vrp.html:298
msgid ""
"Response Team and developers should coordinate to work on the following:"
msgid "Response Team and developers should coordinate to work on the following:"
msgstr ""
#: i2p2www/pages/site/research/vrp.html:282
@@ -631,13 +698,15 @@ msgstr ""
#: i2p2www/pages/site/research/vrp.html:308
msgid ""
"If results are not sensitive, share with the public via IRC or public Trac."
"If results are not sensitive, share with the public via IRC or public "
"Trac."
msgstr ""
#: i2p2www/pages/site/research/vrp.html:316
#, python-format
msgid ""
"Response Team has %(limit)s days following completion of section III to ensure\n"
"Response Team has %(limit)s days following completion of section III to "
"ensure\n"
"completion of section V."
msgstr ""
@@ -647,8 +716,10 @@ msgstr ""
#: i2p2www/pages/site/research/vrp.html:324
msgid ""
"Any further questions or resolutions regarding the incident(s) between the\n"
"researcher and response + development team after public disclosure can be\n"
"Any further questions or resolutions regarding the incident(s) between "
"the\n"
"researcher and response + development team after public disclosure can be"
"\n"
"addressed via the following:"
msgstr ""
@@ -658,7 +729,8 @@ msgstr ""
#: i2p2www/pages/site/research/vrp.html:341
msgid ""
"Response Team and developers should hold annual meetings to review the previous\n"
"Response Team and developers should hold annual meetings to review the "
"previous\n"
"year's incidents."
msgstr ""
@@ -695,3 +767,4 @@ msgstr ""
#: i2p2www/pages/site/research/vrp.html:372
msgid "Potential changes to this process to improve future responses."
msgstr ""