mirror of
https://github.com/go-i2p/www.git
synced 2025-06-24 19:24:49 -04:00
update translations
This commit is contained in:
eyedeekay
File diff suppressed because it is too large
Load Diff
File diff suppressed because it is too large
Load Diff
@ -1,29 +1,30 @@
|
||||
# Chinese translations for I2P.
|
||||
# Copyright (C) 2021 ORGANIZATION
|
||||
# Translations template for I2P.
|
||||
# Copyright (C) 2022 ORGANIZATION
|
||||
# This file is distributed under the same license as the I2P project.
|
||||
#
|
||||
#
|
||||
# Translators:
|
||||
# a7c0396e818c2941c33529bda1f6bf1b_d554568
|
||||
# <93d1ed349b85f9981f2c90624c315cde_129513>, 2015
|
||||
# <93d1ed349b85f9981f2c90624c315cde_129513>, 2016
|
||||
# a7c0396e818c2941c33529bda1f6bf1b_d554568 <93d1ed349b85f9981f2c90624c315cde_129513>, 2015
|
||||
# 591313068a9d8b738947e39c2189fca2_35785ab, 2022
|
||||
# a7c0396e818c2941c33529bda1f6bf1b_d554568 <93d1ed349b85f9981f2c90624c315cde_129513>, 2016
|
||||
# Phonebook3599, 2025
|
||||
# Scott Rhodes <starring169@gmail.com>, 2020
|
||||
# YFdyh000 <yfdyh000@gmail.com>, 2016
|
||||
# YFdyh000 <yfdyh000@gmail.com>, 2015-2016
|
||||
# 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: 2022-08-21 15:32+0000\n"
|
||||
"PO-Revision-Date: 2013-07-15 11:59+0000\n"
|
||||
"Last-Translator: Scott Rhodes <starring169@gmail.com>, 2020\n"
|
||||
"Language-Team: Chinese (China) "
|
||||
"(http://www.transifex.com/otf/I2P/language/zh_CN/)\n"
|
||||
"Plural-Forms: nplurals=1; plural=0\n"
|
||||
"Last-Translator: Phonebook3599, 2025\n"
|
||||
"Language-Team: Chinese (China) (http://app.transifex.com/otf/I2P/language/zh_CN/)\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"
|
||||
@ -31,59 +32,39 @@ 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 ""
|
||||
"相比于I2P，Freenet提供了一些实质性的好处——它是一个分布式的数据存储网络，而I2P并不是，Freenet允许用户检索已发布的内容，即便内容的发布者已经离线了。此外，Freenet应该能够高效地分发流行数据。I2P本身不提供此功能。另一方面，对于那些只想通过网站、留言板、文件共享程序等方式匿名交流的用户来说，这是有重叠的。I2P也进行了一些尝试以支持分布式数据存储，(最近的是<a"
|
||||
" href=\"%(tahoe)s\">Tahoe-LAFS</a>的移植) 但还没有准备好全面使用。"
|
||||
msgstr "相比于I2P，Freenet提供了一些实质性的好处——它是一个分布式的数据存储网络，而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 ""
|
||||
msgstr "然而，即使不考虑任何实施问题，从可扩展性和匿名性的角度来看，\n对Freenet的算法也有一些担忧，这主要是由于Freenet的启发式路由。\n各种技术的相互作用当然可以成功地阻止各种攻击，也许路由算法也将提供希望的可扩展性，\n不幸的是，对所涉及的算法没有太多的分析，但仍有希望已经产生了积极的结果。 \n至少，Freenet确实提供了大量的匿名性，攻击者没有必要的资源来进一步分析它。"
|
||||
|
||||
#: i2p2www/pages/site/comparison/index.html:2
|
||||
msgid "Comparing I2P to other projects"
|
||||
@ -91,34 +72,28 @@ 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 ""
|
||||
msgstr "还有很多其他的应用和项目在进行匿名通信，I2P也受到了他们很多努力的启发。 \n这并不是 一个全面的匿名资源列表 - freehaven的 \n<a href=\"http://freehaven.net/anonbib/topic.html\">Anonymity Bibliography</a>\n和 GNUnet 的<a href=\"https://www.gnunet.org/links/\">相关项目</a>\n都很好地满足了这个目的。 \n有几个网络很突出，可以进一步比较。以下是单独的比较页面："
|
||||
|
||||
#: i2p2www/pages/site/comparison/index.html:20
|
||||
#, python-format
|
||||
msgid ""
|
||||
"The following are discussed on the <a href=\"%(othernetworks)s\">other "
|
||||
"networks page:</a>"
|
||||
msgstr ""
|
||||
msgstr "以下是关于<a href=\"%(othernetworks)s\">其他匿名网络</a>的讨论："
|
||||
|
||||
#: 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 "
|
||||
"issue on Github</a>."
|
||||
msgstr ""
|
||||
"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 issue on Github</a>."
|
||||
msgstr "本页的内容会更新和讨论，我们欢迎评论和补充。\n你可以通过在Github上输入<a href=\"%(trac)s\">新问题</a>来贡献分析。"
|
||||
|
||||
#: i2p2www/pages/site/comparison/other-networks.html:2
|
||||
msgid "I2P Compared to Other Anonymous Networks"
|
||||
@ -126,7 +101,7 @@ msgstr "I2P与其他匿名网络比较"
|
||||
|
||||
#: i2p2www/pages/site/comparison/other-networks.html:5
|
||||
msgid "The following networks are discussed on this page."
|
||||
msgstr ""
|
||||
msgstr "本页面讨论了以下替代网络。"
|
||||
|
||||
#: i2p2www/pages/site/comparison/other-networks.html:17
|
||||
#, python-format
|
||||
@ -136,160 +111,115 @@ msgid ""
|
||||
"<a href=\"%(comparison)s\">main network comparisons page</a>.\n"
|
||||
"You may contribute an analysis by entering a\n"
|
||||
"<a href=\"%(trac)s\">new issue on Github</a>."
|
||||
msgstr ""
|
||||
msgstr "以下大部分章节都是相当旧的，可能并不准确。\n关于可用的对比，见\n<a href=\"%(comparison)s\">网络对比</a>。\n你也可以通过在Github上提交一个\n<a href=\"%(trac)s\">新issue</a>。"
|
||||
|
||||
#: i2p2www/pages/site/comparison/other-networks.html:29
|
||||
#, 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."
|
||||
msgstr ""
|
||||
"<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 "RetroShare是一套运行在<a href=\"%(f2fwiki)s\">朋友对朋友（F2F）</a>网络中的点对点应用程序。\n这种F2F网络的每个节点只与经过认证的节点（\"朋友\"）进行直接的IP连接，并进行证书的交换。\n它可以发现未经认证的对等体（如朋友的朋友），但与他们的连接是通过\"朋友\"转发的，以提供隐私和匿名性。"
|
||||
|
||||
#: 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 ""
|
||||
msgstr "RetroShare旨在建立一个由可信节点组成的私人网络，而I2P则被设计成一个大规模的公共匿名网络。\n最新版本的RetroShare可以选择使用I2P或Tor作为代理 \n这样，所有的连接都是匿名的，添加新的 \"朋友 \"时不需要信任。"
|
||||
|
||||
#: 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 ""
|
||||
msgstr "Morphmix和Tarzan都是完全分布式的、点对点的低延迟mix网络。 \nMorphmix包括一些非常有趣的串通检测算法和Sybil防御，而Tarzan则利用IP地址的稀缺性来实现同样的目的。\n这些系统与I2P的两个主要区别是：I2P的<a href=\"%(threatmodel)s\">威胁模型</a> 和他们的外部代理设计(而不是同时提供发送者和接收者的匿名性）。 \n这两个系统都有源代码，但我们并不清楚它们在学术环境之外的使用情况。"
|
||||
|
||||
#: i2p2www/pages/site/comparison/other-networks.html:172
|
||||
#, 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."
|
||||
msgstr ""
|
||||
"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 "\nMixminion 和 Mixmaster 是支持匿名电子邮件的网络，用于对抗强大的对手。在 I2P 上运行的高延迟消息传递应用程序（例如 <a href=\"%(syndie)s\">Syndie</a> 或 I2PBote）或许足以应对这些对手的威胁模型，同时还能满足低延迟用户的并行运行需求，从而提供更大的匿名集。I2P 路由器本身是否会在未来的某个版本中添加高延迟支持尚不确定。现在判断 I2P 能否满足需要极致电子邮件保护的用户的需求还为时过早。"
|
||||
|
||||
#: i2p2www/pages/site/comparison/other-networks.html:184
|
||||
msgid ""
|
||||
"As with Tor and Onion Routing, \n"
|
||||
"both Mixminion and Mixmaster take the directory based approach as well."
|
||||
msgstr ""
|
||||
msgstr "与 Tor 和洋葱路由一样，Mixminion 和 Mixmaster 也都采取了基于目录的方法。"
|
||||
|
||||
#: 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 ""
|
||||
msgstr "JAP（Java匿名代理）是一个用于匿名上网的混合级联网络。\n因此，它有几个集中的节点（级联的参与者），在级联的节点序列中混合客户端的请求，然后再通过节点序列（级联）代理到网络上。 \n其范围、威胁模型和安全性与I2P有很大不同，但对于那些不需要显著的匿名性，但仍然不满足于类似Anonymizer的服务，JAP是值得一试的。 \n有一点需要注意的是，在德国法院管辖下的任何人可能需要要小心，因为德国联邦刑事调查局（FBCI）已经 \n成功地发动了一次对该网络的<a href=\"%(url)s\">攻击</a>。 \n尽管这次攻击的方法后来在德国法院被认定为非法，但数据被成功收集这一事实已经无法改变。\n法院会根据情况改变他们的想法，这也证明了如果政府机构或情报机构愿意，他们随时可以收集数据，即使后来在某些法庭上可能会被认定为不可接受。"
|
||||
|
||||
#: i2p2www/pages/site/comparison/other-networks.html:216
|
||||
#, python-format
|
||||
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)."
|
||||
msgstr ""
|
||||
"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 "这两个系统都通过相同的基本<a href=\"%(antnet)s\">蚁群网络</a>路由工作，根据针对简单的非共谋攻击者提供合理否认的威胁模型。使用蚁群网络路由时，它们首先进行随机漫步或广播搜索，以找到拥有所需数据或身份的对等节点，然后使用反馈算法优化找到的路径。这对于仅仅想知道周围其他人提供什么信息的应用程序非常有效——例如“你们好吗”与“嗨，爱丽丝，你好吗”——你基本上会得到一个本地节点集群，可以与之共享文件并保持一定程度的匿名性（尽管你无法控制该对等节点组中的成员）。"
|
||||
|
||||
#: 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 ""
|
||||
msgstr "然而，该算法的规模并不大--如果应用程序想与一个特定的节点连接，它只能进行广播搜索或随机行走（尽管如果他们足够幸运地成功的话，蚂蚁网络的路由应该会优化找到的连接）。 \n这意味着这些网络在小范围内可以很好地工作，但它们并不适合大型网络，因为在这些网络中有人可能与任意一个特定的节点取得联系。 \n这并不意味着这些系统没有价值，只是说它们的适用性仅限于可以解决其特定问题的情况。"
|
||||
|
||||
#: i2p2www/pages/site/comparison/other-networks.html:239
|
||||
#, 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 ""
|
||||
msgstr "这是一个针对伊朗用户的闭源网络。\nTor曾写过一篇关于在<a href=\"%(torpost)s\">规避审查工具中应注意什么</a>的好文章，可以说，闭源和公开针对特定国家的做法不是好主意。\n当然，I2P是开放源代码的，然而，我们的源代码和<a href=\"%(docs)s\">技术文档</a>需要更多的研究和审计。"
|
||||
|
||||
#: i2p2www/pages/site/comparison/other-networks.html:248
|
||||
msgid "Paid VPN Services"
|
||||
@ -301,7 +231,7 @@ msgstr "付费VPN服务"
|
||||
msgid ""
|
||||
"You may contribute an analysis by entering a\n"
|
||||
"<a href=\"%(trac)s\">new issue on Github</a>."
|
||||
msgstr ""
|
||||
msgstr "你可以在Github上创建一个\n<a href=\"%(trac)s\">新问题</a>。"
|
||||
|
||||
#: i2p2www/pages/site/comparison/other-networks.html:254
|
||||
msgid "Others"
|
||||
@ -329,7 +259,7 @@ msgid ""
|
||||
"network, as well as gather and report statistics, as \n"
|
||||
"opposed to I2P's distributed <a href=\"%(netdb)s\">network \n"
|
||||
"database</a> and <a href=\"%(peerselection)s\">peer selection</a>."
|
||||
msgstr ""
|
||||
msgstr "Tor 和洋葱路由都是匿名代理网络，允许人们通过其低延迟混合网络进行隧道传输。Tor/洋葱路由与 I2P 之间的两个主要区别同样与威胁模型和外部代理设计有关（尽管 Tor 也支持隐藏服务）。此外，Tor 采用基于目录的方法——提供一个集中式点来管理网络的整体“视图”，并收集和报告统计数据，这与 I2P 的分布式<a href=\"%(netdb)s\">网络数据库</a>和<a href=\"%(peerselection)s\">对等节点选择</a>不同。"
|
||||
|
||||
#: i2p2www/pages/site/comparison/tor.html:23
|
||||
msgid ""
|
||||
@ -342,7 +272,7 @@ msgid ""
|
||||
"outproxies are prone to abuse, along with all of the \n"
|
||||
"other security issues we've come to know and love with \n"
|
||||
"normal Internet traffic."
|
||||
msgstr ""
|
||||
msgstr "I2P/Tor 的出口代理功能对于某些攻击者来说确实存在一些的实质性弱点——一旦通信离开混合网络，全球被动攻击者就能更容易地进行流量分析。此外，出口代理可以访问双向传输数据的明文，出口代理容易被滥用，还有我们熟知并关注的所有其他普通互联网流量的安全问题。"
|
||||
|
||||
#: i2p2www/pages/site/comparison/tor.html:35
|
||||
msgid ""
|
||||
@ -352,21 +282,21 @@ msgid ""
|
||||
"to build outproxy functionality on top of an anonymous\n"
|
||||
"communication layer, they can). In fact, some I2P users\n"
|
||||
"currently take advantage of Tor to outproxy."
|
||||
msgstr ""
|
||||
msgstr "然而，许多人无需担心这些情况，因为它们超出了他们的威胁模型。而且，它们也超出了 I2P 的（正式）功能范围（如果有人想在匿名通信层之上构建出口代理功能，他们可以这样做）。事实上，一些 I2P 用户目前正在利用 Tor 来实现出口代理。"
|
||||
|
||||
#: i2p2www/pages/site/comparison/tor.html:49
|
||||
msgid "Comparison of Tor and I2P Terminology"
|
||||
msgstr ""
|
||||
msgstr "Tor和I2P术语的比较"
|
||||
|
||||
#: i2p2www/pages/site/comparison/tor.html:50
|
||||
msgid ""
|
||||
"While Tor and I2P are similar in many ways, much of the terminology is "
|
||||
"different."
|
||||
msgstr ""
|
||||
msgstr "虽然Tor和I2P在许多方面相似，但许多术语是不同的。"
|
||||
|
||||
#: i2p2www/pages/site/comparison/tor.html:55
|
||||
msgid "Cell"
|
||||
msgstr ""
|
||||
msgstr "Cell（包）"
|
||||
|
||||
#: i2p2www/pages/site/comparison/tor.html:55
|
||||
msgid "Message"
|
||||
@ -394,11 +324,11 @@ msgstr "目录"
|
||||
|
||||
#: i2p2www/pages/site/comparison/tor.html:58
|
||||
msgid "NetDb"
|
||||
msgstr ""
|
||||
msgstr "NetDb（网络数据库）"
|
||||
|
||||
#: i2p2www/pages/site/comparison/tor.html:59
|
||||
msgid "Directory Server"
|
||||
msgstr ""
|
||||
msgstr "目录服务器"
|
||||
|
||||
#: i2p2www/pages/site/comparison/tor.html:59
|
||||
msgid "Floodfill Router"
|
||||
@ -406,11 +336,11 @@ msgstr "种子路由器"
|
||||
|
||||
#: i2p2www/pages/site/comparison/tor.html:60
|
||||
msgid "Entry Guards"
|
||||
msgstr ""
|
||||
msgstr "入口守卫"
|
||||
|
||||
#: i2p2www/pages/site/comparison/tor.html:60
|
||||
msgid "Fast Peers"
|
||||
msgstr ""
|
||||
msgstr "Fast Peers（快速节点）"
|
||||
|
||||
#: i2p2www/pages/site/comparison/tor.html:61
|
||||
msgid "Entry Node"
|
||||
@ -436,7 +366,7 @@ msgstr "隐身服务"
|
||||
#: i2p2www/pages/site/comparison/tor.html:63
|
||||
#: i2p2www/pages/site/comparison/tor.html:68
|
||||
msgid "I2P Site or Destination"
|
||||
msgstr ""
|
||||
msgstr "I2P Site or Destination（I2P网站或目标）"
|
||||
|
||||
#: i2p2www/pages/site/comparison/tor.html:64
|
||||
msgid "Hidden Service Descriptor"
|
||||
@ -448,7 +378,7 @@ msgstr "赁集"
|
||||
|
||||
#: i2p2www/pages/site/comparison/tor.html:65
|
||||
msgid "Introduction point"
|
||||
msgstr ""
|
||||
msgstr "Introduction point（介绍点）"
|
||||
|
||||
#: i2p2www/pages/site/comparison/tor.html:65
|
||||
msgid "Inbound Gateway"
|
||||
@ -470,7 +400,7 @@ msgstr "洋葱代理"
|
||||
|
||||
#: i2p2www/pages/site/comparison/tor.html:67
|
||||
msgid "I2PTunnel Client (more or less)"
|
||||
msgstr ""
|
||||
msgstr "I2PTunnel 客户端（或多或少）"
|
||||
|
||||
#: i2p2www/pages/site/comparison/tor.html:68
|
||||
msgid "Onion Service"
|
||||
@ -482,19 +412,19 @@ msgstr "中继"
|
||||
|
||||
#: i2p2www/pages/site/comparison/tor.html:70
|
||||
msgid "Rendezvous Point"
|
||||
msgstr ""
|
||||
msgstr "Rendezvous Point（会合点）"
|
||||
|
||||
#: i2p2www/pages/site/comparison/tor.html:70
|
||||
msgid "somewhat like Inbound Gateway + Outbound Endpoint"
|
||||
msgstr ""
|
||||
msgstr "有点像入站网关+出站端点"
|
||||
|
||||
#: i2p2www/pages/site/comparison/tor.html:71
|
||||
msgid "Router Descriptor"
|
||||
msgstr ""
|
||||
msgstr "路由身份"
|
||||
|
||||
#: i2p2www/pages/site/comparison/tor.html:71
|
||||
msgid "RouterInfo"
|
||||
msgstr ""
|
||||
msgstr "路由信息"
|
||||
|
||||
#: i2p2www/pages/site/comparison/tor.html:72
|
||||
msgid "Server"
|
||||
@ -506,13 +436,10 @@ 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"
|
||||
@ -528,29 +455,24 @@ 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 的传输和网桥，对国家级封锁有更强的抵抗\n"
|
||||
"（I2P 有“完全限制路由”的提案，但还没有实现）"
|
||||
"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
|
||||
msgid ""
|
||||
"Better documentation, has formal papers and specifications,\n"
|
||||
"better website, many more translations"
|
||||
msgstr ""
|
||||
"更好的文档，拥有正式文件和规范，\n"
|
||||
"更美观的网页，多许多的翻译"
|
||||
msgstr "更好的文档，拥有正式文件和规范，\n更美观的网页，多许多的翻译"
|
||||
|
||||
#: i2p2www/pages/site/comparison/tor.html:101
|
||||
msgid "More efficient with memory usage"
|
||||
@ -558,19 +480,19 @@ msgstr "内存使用更高效"
|
||||
|
||||
#: i2p2www/pages/site/comparison/tor.html:102
|
||||
msgid "Tor client nodes have very low bandwidth overhead"
|
||||
msgstr ""
|
||||
msgstr "Tor客户端节点的带宽开销很小"
|
||||
|
||||
#: i2p2www/pages/site/comparison/tor.html:104
|
||||
msgid ""
|
||||
"Centralized control reduces the complexity at each\n"
|
||||
"node and can efficiently address Sybil attacks"
|
||||
msgstr ""
|
||||
msgstr "集中化控制减少了每个节点的复杂性\n可以有效地解决Sybil攻击。"
|
||||
|
||||
#: i2p2www/pages/site/comparison/tor.html:110
|
||||
msgid ""
|
||||
"A core of high capacity nodes provides higher\n"
|
||||
"throughput and lower latency"
|
||||
msgstr ""
|
||||
msgstr "一个高容量节点能提供更高的\n吞吐量和较低的延时"
|
||||
|
||||
#: i2p2www/pages/site/comparison/tor.html:115
|
||||
msgid "C, not Java (ewww)"
|
||||
@ -582,8 +504,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
|
||||
@ -600,9 +522,7 @@ msgstr "通过不断分析和比较性能，而不是根据目录声称的流量
|
||||
msgid ""
|
||||
"Floodfill peers (\"directory servers\") are varying and untrusted,\n"
|
||||
"rather than hardcoded"
|
||||
msgstr ""
|
||||
"种子节点（“目录服务器”）是持续变化并且不被信任的，\n"
|
||||
"而不是硬编码写入"
|
||||
msgstr "种子对等节点（“目录服务器”）是持续变化并且不被信任的，而不是硬编码的"
|
||||
|
||||
#: i2p2www/pages/site/comparison/tor.html:134
|
||||
msgid "Small enough that it hasn't been blocked or DOSed much, or at all"
|
||||
@ -620,13 +540,13 @@ msgstr "包交换而不是电路交换"
|
||||
msgid ""
|
||||
"implicit transparent load balancing of messages \n"
|
||||
"across multiple peers, rather than a single path"
|
||||
msgstr ""
|
||||
msgstr "在多个对等节点之间实现隐式透明消息负载平衡，而非单一路径 "
|
||||
|
||||
#: i2p2www/pages/site/comparison/tor.html:145
|
||||
msgid ""
|
||||
"resilience vs. failures by running multiple \n"
|
||||
"tunnels in parallel, plus rotating tunnels"
|
||||
msgstr ""
|
||||
msgstr "通过并行运行多个隧道以及轮换隧道来增强对故障的韧性"
|
||||
|
||||
#: i2p2www/pages/site/comparison/tor.html:151
|
||||
msgid ""
|
||||
@ -722,4 +642,3 @@ 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
@ -1,31 +1,31 @@
|
||||
# Chinese translations for I2P.
|
||||
# Translations template for I2P.
|
||||
# Copyright (C) 2022 ORGANIZATION
|
||||
# This file is distributed under the same license as the I2P project.
|
||||
#
|
||||
#
|
||||
# Translators:
|
||||
# bright hong <heathcliff2333@outlook.com>, 2020
|
||||
# ciaran <ciaranchen@qq.com>, 2023
|
||||
# xkimo_daeee <michael_ies@yahoo.com>, 2014
|
||||
# a478a116a491ba89a1cee347ebcf239b_fd74b84, 2022
|
||||
# Narrator Z, 2022
|
||||
# 591313068a9d8b738947e39c2189fca2_35785ab, 2022
|
||||
# Scott Rhodes <starring169@gmail.com>, 2020-2021
|
||||
# Tommy Lmath <l5h5t7@qq.com>, 2016
|
||||
# YFdyh000 <yfdyh000@gmail.com>, 2016
|
||||
# YFdyh000 <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: 2022-08-21 15:33+0000\n"
|
||||
"PO-Revision-Date: 2013-07-15 12:01+0000\n"
|
||||
"Last-Translator: ciaran <ciaranchen@qq.com>, 2023\n"
|
||||
"Language-Team: Chinese (China) "
|
||||
"(http://app.transifex.com/otf/I2P/language/zh_CN/)\n"
|
||||
"Plural-Forms: nplurals=1; plural=0\n"
|
||||
"Language-Team: Chinese (China) (http://app.transifex.com/otf/I2P/language/zh_CN/)\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"
|
||||
@ -46,16 +46,11 @@ msgstr "关于I2P网络的学术研究"
|
||||
|
||||
#: 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 "I2P是一个特别的项目，但它在学术圈没有得到应有的关注。目前，大多数关于匿名和洋葱路由的研究都是围绕Tor进行的，尽管这些文章对我们也有帮助，但我们仍认为需要有围绕I2P的研究。这在保持网络的安全性以及对于启发未来的开发具有重要的影响"
|
||||
|
||||
@ -63,25 +58,14 @@ msgstr "I2P是一个特别的项目，但它在学术圈没有得到应有的关
|
||||
#, 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\">自由避风港匿名参考文献（Free Haven Anonymity Bibliography）</a>。"
|
||||
"\n"
|
||||
"I2P 得益于大量对 Tor 和洋葱路由的研究。但是，对I2P背后的理论以及网络做出的选择和权衡的研究几乎没有。这为原创研究提供了一个独特的机会。"
|
||||
"\n"
|
||||
msgstr "\n有一个大型研究社区研究匿名性的方方面面。想寻找当前全面的论文列表，请参阅<a href=\"%(anonbib)s\">自由避风港匿名参考文献（Free Haven Anonymity Bibliography）</a>。\nI2P 得益于大量对 Tor 和洋葱路由的研究。但是，对I2P背后的理论以及网络做出的选择和权衡的研究几乎没有。这为原创研究提供了一个独特的机会。\n"
|
||||
|
||||
#: i2p2www/pages/site/research/index.html:29
|
||||
#, python-format
|
||||
@ -94,12 +78,9 @@ 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 ""
|
||||
"\n"
|
||||
"本页面希望概括出最急需的研究方面，对潜在研究人员的寄语，我们总的安全指导原则以及一堆你可以着手的开放性问题。\n"
|
||||
msgstr "\n本页面希望概括出最急需的研究方面，对潜在研究人员的寄语，我们总的安全指导原则以及一堆你可以着手的开放性问题。\n"
|
||||
|
||||
#: i2p2www/pages/site/research/index.html:40
|
||||
msgid "Notes to Researchers:"
|
||||
@ -111,16 +92,12 @@ 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 "我们认为所有关于I2P网络的研究都是有用的，且欢迎这样的研究，尽管如此，其中一些领域的研究比起别的更急需--主要在于防御性研究。许多人享受着想出对匿名软件的花式攻击方法，这种状况又被学校的奖励机制助长。尽管我们知道这不是研究人员的第一选择，我们仍期盼任何能够帮助强化网络的工作。"
|
||||
|
||||
@ -131,31 +108,19 @@ 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 ""
|
||||
"如果您决定做一个关于I2P的课题，一步步分析I2P网络，或解决大问题时，我们<b>恳切希望</b>您能尽快与我们的开发团队<a "
|
||||
"href=\"%(contact)s\">交流您的想法</a>。I2P在持续开发中，会有大量开发路线，所以您的问题可能已经被标记准备更新解决。极少数情况下您的测试可能与别的研究组重合，我们也会提前告诉您（当然了，在他们的允许下），或许能促成您与另一团队的合作。也有可能测试本身会严重损害网络或普通用户，开发团队可能会有为您减少测试风险，增加测试安全性的想法或建议。"
|
||||
msgstr "如果您决定做一个关于I2P的课题，一步步分析I2P网络，或解决大问题时，我们<b>恳切希望</b>您能尽快与我们的开发团队<a href=\"%(contact)s\">交流您的想法</a>。I2P在持续开发中，会有大量开发路线，所以您的问题可能已经被标记准备更新解决。极少数情况下您的测试可能与别的研究组重合，我们也会提前告诉您（当然了，在他们的允许下），或许能促成您与另一团队的合作。也有可能测试本身会严重损害网络或普通用户，开发团队可能会有为您减少测试风险，增加测试安全性的想法或建议。"
|
||||
|
||||
#: i2p2www/pages/site/research/index.html:71
|
||||
msgid "Research Ethics & Testing the Network"
|
||||
@ -169,13 +134,11 @@ 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"
|
||||
@ -183,10 +146,8 @@ 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"
|
||||
@ -194,34 +155,12 @@ 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>"
|
||||
msgstr ""
|
||||
"<ol>\n"
|
||||
" <li>\n"
|
||||
" 考虑利益和风险--是否该研究提供的价值毫无疑问大于危险？\n"
|
||||
" </li>\n"
|
||||
" <li>\n"
|
||||
" 如果研究可以在测试网络上进行，那么这就是首选。\n"
|
||||
" </li>\n"
|
||||
" <li>\n"
|
||||
" 如果您必须在实时网络上操作，最安全的途径是只收集关于自己的数据\n"
|
||||
" </li>\n"
|
||||
" <li>\n"
|
||||
" 如果您需要 \"更大的数据\"，建议您首先检查是否可以使用从以前的实验或其他第三方资源的数据集。\n"
|
||||
" </li>\n"
|
||||
" <li>\n"
|
||||
" 如果您必须在实时网络上收集数据，请确保其对于发表和收集都是尽可能安全的。\n"
|
||||
" </li>\n"
|
||||
" <li>\n"
|
||||
" 在测试后和发布前，检查是否所有将要公开发布的数据都是发布人 <b><i>不</i></b> 打算保密的。\n"
|
||||
" </li>\n"
|
||||
"</ol>"
|
||||
msgstr "<ol>\n <li>\n 考虑利益和风险--是否该研究提供的价值毫无疑问大于危险？\n </li>\n <li>\n 如果研究可以在测试网络上进行，那么这就是首选。\n </li>\n <li>\n 如果您必须在实时网络上操作，最安全的途径是只收集关于自己的数据\n </li>\n <li>\n 如果您需要 \"更大的数据\"，建议您首先检查是否可以使用从以前的实验或其他第三方资源的数据集。\n </li>\n <li>\n 如果您必须在实时网络上收集数据，请确保其对于发表和收集都是尽可能安全的。\n </li>\n <li>\n 在测试后和发布前，检查是否所有将要公开发布的数据都是发布人 <b><i>不</i></b> 打算保密的。\n </li>\n</ol>"
|
||||
|
||||
#: i2p2www/pages/site/research/index.html:106
|
||||
msgid "Using a Test Network to Attack I2P"
|
||||
@ -229,47 +168,26 @@ msgstr "使用测试网络攻击 I2P"
|
||||
|
||||
#: 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 ""
|
||||
"I2P可以作为一个单独的测试网络运行，通过控制新路由器的位置\n"
|
||||
"的位置，使其只能找到其他测试路由器。\n"
|
||||
"\n"
|
||||
"标准的操作模式是每个路由器实例有一个JVM；因此\n"
|
||||
"在一台机器上运行多个I2P副本是不可取的，这是因为\n"
|
||||
"潜在的资源消耗和某些端口冲突。为了更好地\n"
|
||||
"为了更好地建立小型测试网络，I2P 有一个多路由器模式，可以让多个不同的路由器运行。\n"
|
||||
"使得多个不同的路由器可以在同一个JVM中运行。\n"
|
||||
"\n"
|
||||
"MultiRouter可以从i2p的基本目录下运行下面的\n"
|
||||
"命令。"
|
||||
msgstr "I2P可以作为一个单独的测试网络运行，通过控制新路由器的位置\n的位置，使其只能找到其他测试路由器。\n\n标准的操作模式是每个路由器实例有一个JVM；因此\n在一台机器上运行多个I2P副本是不可取的，这是因为\n潜在的资源消耗和某些端口冲突。为了更好地\n为了更好地建立小型测试网络，I2P 有一个多路由器模式，可以让多个不同的路由器运行。\n使得多个不同的路由器可以在同一个JVM中运行。\n\nMultiRouter可以从i2p的基本目录下运行下面的\n命令。"
|
||||
|
||||
#: 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 ""
|
||||
"此外，I2P 可以在虚拟网络模式下启动。这种模式下禁用所有传输，允许路由器在没有网络流量下进行隔离测试。要启用此模式，在启动前，向 "
|
||||
"router.config 添加<code>i2p.vmCommSystem=true</code>."
|
||||
msgstr "此外，I2P 可以在虚拟网络模式下启动。这种模式下禁用所有传输，允许路由器在没有网络流量下进行隔离测试。要启用此模式，在启动前，向 router.config 添加<code>i2p.vmCommSystem=true</code>."
|
||||
|
||||
#: i2p2www/pages/site/research/index.html:131
|
||||
msgid "Testing on the Live I2P Network"
|
||||
@ -278,18 +196,12 @@ msgstr "在真实 I2P 网络上测试"
|
||||
#: 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 ""
|
||||
"如果你打算调查研究目前在线的 I2P 网络，请在着手你的测试前<a "
|
||||
"href=\"%(contact)s\">联络我们</a>。虽然我们不阻挠研究员负责任地测试真实的 I2P "
|
||||
"网络，但如果没有收到任何联络通知并且攻击性很明显，我们可能采取相应的对策，可能干扰到“测试”行动。"
|
||||
msgstr "如果你打算调查研究目前在线的 I2P 网络，请在着手你的测试前<a href=\"%(contact)s\">联络我们</a>。虽然我们不阻挠研究员负责任地测试真实的 I2P 网络，但如果没有收到任何联络通知并且攻击性很明显，我们可能采取相应的对策，可能干扰到“测试”行动。"
|
||||
|
||||
#: i2p2www/pages/site/research/index.html:141
|
||||
msgid "Router Family Configuration"
|
||||
@ -297,49 +209,25 @@ 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 ""
|
||||
"从0.9.25版开始，I2P支持路由器家族。这为\n"
|
||||
"研究人员在运行多个路由器时，可以公开识别这些\n"
|
||||
"路由器。反过来，这也有助于 I2P 项目了解这些路由器\n"
|
||||
"没有在网络上运行攻击。它还可以防止其他路由器\n"
|
||||
"将该家族的多个路由器纳入一个隧道，这可能导致\n"
|
||||
"导致非匿名化。那些看起来是串通好的路由器，但却没有一个宣布的家族\n"
|
||||
"的路由器可能会被认为是对网络的攻击，并可能被阻止。\n"
|
||||
"确保你的研究项目成功的最好方法是直接\n"
|
||||
"与我们合作。"
|
||||
msgstr "从0.9.25版开始，I2P支持路由器家族。这为\n研究人员在运行多个路由器时，可以公开识别这些\n路由器。反过来，这也有助于 I2P 项目了解这些路由器\n没有在网络上运行攻击。它还可以防止其他路由器\n将该家族的多个路由器纳入一个隧道，这可能导致\n导致非匿名化。那些看起来是串通好的路由器，但却没有一个宣布的家族\n的路由器可能会被认为是对网络的攻击，并可能被阻止。\n确保你的研究项目成功的最好方法是直接\n与我们合作。"
|
||||
|
||||
#: 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 ""
|
||||
"路由器家族共享一个私钥，以便在参与该家族的路由不能被欺骗。\n"
|
||||
"要配置一个路由器家族，请点击路由器控制台的 \"I2P内部 \"链接，然后点击 \"路由器家族\"标签。\n"
|
||||
"按照这里的指示为路由器家族中的第一个路由器生成私钥。然后，导出密钥，并将其导入到路由器家族的其他成员。"
|
||||
msgstr "路由器家族共享一个私钥，以便在参与该家族的路由不能被欺骗。\n要配置一个路由器家族，请点击路由器控制台的 \"I2P内部 \"链接，然后点击 \"路由器家族\"标签。\n按照这里的指示为路由器家族中的第一个路由器生成私钥。然后，导出密钥，并将其导入到路由器家族的其他成员。"
|
||||
|
||||
#: i2p2www/pages/site/research/questions.html:2
|
||||
msgid "Open research questions"
|
||||
@ -392,11 +280,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."
|
||||
msgstr ""
|
||||
"\n"
|
||||
"这个过程可能会有变化。请参考本页面，了解当前的VRP。"
|
||||
"This process is subject to change. Please refer to this page for the current VRP."
|
||||
msgstr "\n这个过程可能会有变化。请参考本页面，了解当前的VRP。"
|
||||
|
||||
#: i2p2www/pages/site/research/vrp.html:10
|
||||
msgid "This page was last updated in June 2020."
|
||||
@ -404,28 +289,16 @@ msgstr "本页面最后更新于2020年6月"
|
||||
|
||||
#: i2p2www/pages/site/research/vrp.html:12
|
||||
msgid ""
|
||||
"Researchers: while you research/hack, we ask that you refrain from the "
|
||||
"following: - Performing active exploits or Denial of Service attacks on "
|
||||
"the\n"
|
||||
"i2p network - Performing social engineering on i2p development team "
|
||||
"members - Performing any physical or electronic attempts against i2p "
|
||||
"property and/or data\n"
|
||||
"Researchers: while you research/hack, we ask that you refrain from the following: - Performing active exploits or Denial of Service attacks on the\n"
|
||||
"i2p network - Performing social engineering on i2p development team members - Performing any physical or electronic attempts against i2p property and/or data\n"
|
||||
"centers"
|
||||
msgstr ""
|
||||
"致研究人员：当你研究/Hack时，我们希望你不要做以下事情。- 在i2p网络上进行主动开发漏洞或拒绝服务攻击\n"
|
||||
" - 对i2p开发团队成员进行社会工程 - 对i2p财产和/或数据\n"
|
||||
"中心进行任何物理或电子攻击"
|
||||
msgstr "致研究人员：当你研究/Hack时，我们希望你不要做以下事情。- 在i2p网络上进行主动开发漏洞或拒绝服务攻击\n - 对i2p开发团队成员进行社会工程 - 对i2p财产和/或数据\n中心进行任何物理或电子攻击"
|
||||
|
||||
#: i2p2www/pages/site/research/vrp.html:15
|
||||
msgid ""
|
||||
"As i2p is an open-source community, many volunteers and development team "
|
||||
"members run their own I2P Sites as well as public (“non-private "
|
||||
"internet”) domains. These\n"
|
||||
"sites/servers are NOT in the scope of the vulnerability assessment / "
|
||||
"response process, only the underlying code of i2p is."
|
||||
msgstr ""
|
||||
"由于i2p是一个开源社区，许多志愿者和开发团队成员经营着自己的I2P网站以及公共（\"暗网\"）域名。这些\n"
|
||||
"网站/服务器不在漏洞评估/响应过程的范围内，只有i2p的底层代码在。"
|
||||
"As i2p is an open-source community, many volunteers and development team members run their own I2P Sites as well as public (“non-private internet”) domains. These\n"
|
||||
"sites/servers are NOT in the scope of the vulnerability assessment / response process, only the underlying code of i2p is."
|
||||
msgstr "由于i2p是一个开源社区，许多志愿者和开发团队成员经营着自己的I2P网站以及公共（\"暗网\"）域名。这些\n网站/服务器不在漏洞评估/响应过程的范围内，只有i2p的底层代码在。"
|
||||
|
||||
#: i2p2www/pages/site/research/vrp.html:18
|
||||
msgid "Point of Contact for Security Issues"
|
||||
@ -451,8 +324,7 @@ 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 ""
|
||||
|
||||
@ -465,8 +337,7 @@ 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 ""
|
||||
|
||||
@ -486,8 +357,8 @@ 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
|
||||
@ -499,8 +370,8 @@ msgstr ""
|
||||
|
||||
#: i2p2www/pages/site/research/vrp.html:75
|
||||
msgid ""
|
||||
"Affects network as a whole, has potential to break entire network or is "
|
||||
"on a scale of great catastrophe."
|
||||
"Affects 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:79
|
||||
@ -518,19 +389,18 @@ msgstr ""
|
||||
#: i2p2www/pages/site/research/vrp.html:93
|
||||
#, 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:98
|
||||
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:101
|
||||
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 ""
|
||||
|
||||
@ -553,8 +423,8 @@ msgstr ""
|
||||
#: i2p2www/pages/site/research/vrp.html:122
|
||||
msgid ""
|
||||
"Response Manager works on a patch LOCALLY, patches are shared by the "
|
||||
"response team via PGP-encrypted e-mail until such a time as it is safe to"
|
||||
" expose to the public."
|
||||
"response team via PGP-encrypted e-mail until such a time as it is safe to "
|
||||
"expose to the public."
|
||||
msgstr ""
|
||||
|
||||
#: i2p2www/pages/site/research/vrp.html:125
|
||||
@ -563,10 +433,8 @@ msgstr ""
|
||||
|
||||
#: i2p2www/pages/site/research/vrp.html:128
|
||||
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:132
|
||||
@ -601,19 +469,14 @@ msgstr ""
|
||||
|
||||
#: i2p2www/pages/site/research/vrp.html:159
|
||||
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:162
|
||||
msgid ""
|
||||
"Proceed with the Point or Regular Release. At this time, it is not "
|
||||
"possible to release an in-network update for only one operating system or"
|
||||
"\n"
|
||||
"\t\tarchitecture. In order that all affected products can be released as "
|
||||
"quickly as possible, the person responsible\n"
|
||||
"\t\tfor that software should be able to perform necessary release "
|
||||
"processes in a timely manner. Importantly this should include\n"
|
||||
"Proceed with the Point or Regular Release. At this time, it is not possible to release an in-network update for only one operating system or\n"
|
||||
"\t\tarchitecture. In order that all affected products can be released as quickly as possible, the person responsible\n"
|
||||
"\t\tfor that software should be able to perform necessary release processes in a timely manner. Importantly this should include\n"
|
||||
"\t\tconsideration for package maintainers in Debian, Ubuntu and F-Droid."
|
||||
msgstr ""
|
||||
|
||||
@ -623,11 +486,13 @@ msgstr ""
|
||||
|
||||
#: i2p2www/pages/site/research/vrp.html:175
|
||||
#, 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:179
|
||||
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:183
|
||||
@ -679,8 +544,8 @@ msgstr ""
|
||||
|
||||
#: i2p2www/pages/site/research/vrp.html:214
|
||||
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:217
|
||||
@ -688,13 +553,14 @@ msgid "If applicable, credits to the original reporter."
|
||||
msgstr ""
|
||||
|
||||
#: i2p2www/pages/site/research/vrp.html:222
|
||||
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:230
|
||||
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:238
|
||||
@ -703,8 +569,8 @@ msgstr ""
|
||||
|
||||
#: i2p2www/pages/site/research/vrp.html:242
|
||||
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:250
|
||||
@ -715,33 +581,28 @@ msgstr ""
|
||||
|
||||
#: i2p2www/pages/site/research/vrp.html:254
|
||||
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:259
|
||||
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:263
|
||||
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:268
|
||||
#, 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 ""
|
||||
@ -756,7 +617,8 @@ msgstr ""
|
||||
|
||||
#: i2p2www/pages/site/research/vrp.html:282
|
||||
#: i2p2www/pages/site/research/vrp.html:302
|
||||
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:286
|
||||
@ -785,15 +647,13 @@ msgstr ""
|
||||
|
||||
#: i2p2www/pages/site/research/vrp.html:312
|
||||
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:320
|
||||
#, 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 ""
|
||||
|
||||
@ -803,10 +663,8 @@ msgstr ""
|
||||
|
||||
#: i2p2www/pages/site/research/vrp.html:328
|
||||
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 ""
|
||||
|
||||
@ -816,8 +674,7 @@ msgstr ""
|
||||
|
||||
#: i2p2www/pages/site/research/vrp.html:344
|
||||
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 ""
|
||||
|
||||
@ -854,4 +711,3 @@ msgstr ""
|
||||
#: i2p2www/pages/site/research/vrp.html:375
|
||||
msgid "Potential changes to this process to improve future responses."
|
||||
msgstr ""
|
||||
|
||||
|
||||
Reference in New Issue
Block a user