i2p.www/pots/research.pot

# Translations template for I2P.
# Copyright (C) 2022 ORGANIZATION
# This file is distributed under the same license as the I2P project.
# FIRST AUTHOR <EMAIL@ADDRESS>, 2022.
#
#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: I2P website\n"
"Report-Msgid-Bugs-To: http://trac.i2p2.de\n"
"POT-Creation-Date: 2022-08-21 15:33+0000\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
"Language-Team: LANGUAGE <LL@li.org>\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=utf-8\n"
"Content-Transfer-Encoding: 8bit\n"
"Generated-By: Babel 1.3\n"

#: i2p2www/pages/site/research/index.html:2
msgid "Academic Research"
msgstr ""

#: i2p2www/pages/site/research/index.html:3
#: i2p2www/pages/site/research/questions.html:3
msgid "May 2018"
msgstr ""

#: i2p2www/pages/site/research/index.html:6
msgid "Introduction"
msgstr ""

#: i2p2www/pages/site/research/index.html:8
msgid "Research on the I2P Network"
msgstr ""

#: i2p2www/pages/site/research/index.html:10
msgid ""
"I2P is a very unique project that unfortunately has not received the "
"wider\n"
"academic attention it deserves. To date, most research focus on anonymous"
" and\n"
"onion-routing technology has been around Tor, and while those papers "
"benefit us\n"
"as well, there is a great need for I2P-focused research. This plays a key"
" role\n"
"in both maintaining the security and integrity of the network, as well as"
"\n"
"opening doors for more impactful future development."
msgstr ""

#: i2p2www/pages/site/research/index.html:19
#, python-format
msgid ""
"\n"
"There is a large research community investigating a wide range of aspects"
" of\n"
"anonymity. For a current and comprehensive list of relevant papers, see "
"the\n"
"<a href=\"%(anonbib)s\">Free Haven Anonymity Bibliography</a>.\n"
"I2P benefits from much of the research into Tor and onion routing, but "
"there is\n"
"little dedicated research interest into the theory behind I2P, and the "
"choices\n"
"and tradeoffs that the network makes. This presents a unique opportunity "
"for\n"
"original research.\n"
msgstr ""

#: i2p2www/pages/site/research/index.html:29
#, python-format
msgid ""
"A list of known published papers about I2P is available <a "
"href=\"%(papers)s\">here</a>."
msgstr ""

#: i2p2www/pages/site/research/index.html:34
msgid ""
"\n"
"This page aims to outline the most needed fields of research, notes to\n"
"potential researchers, our general safety guidelines as well as an "
"expanding\n"
"list of open questions that you can begin on at any time.\n"
msgstr ""

#: i2p2www/pages/site/research/index.html:40
msgid "Notes to Researchers:"
msgstr ""

#: i2p2www/pages/site/research/index.html:42
msgid "Defensive Research"
msgstr ""

#: i2p2www/pages/site/research/index.html:44
msgid ""
"While all research on the I2P network is beneficial and appreciated, "
"there are\n"
"certain areas which are more in need than others - most so in defensive\n"
"research. Most people enjoy coming up with fun ways to launch offensives\n"
"against anonymous software, and this is further reinforced by the "
"incentives in\n"
"academic institutions. While we know it is often not the first choice for"
"\n"
"researchers, We would certainly appreciate any and all work towards ways "
"to\n"
"fortify the network!"
msgstr ""

#: i2p2www/pages/site/research/index.html:54
msgid "Offensive and Analytic Tests"
msgstr ""

#: i2p2www/pages/site/research/index.html:56
#, python-format
msgid ""
"If you've decided on a research topic that aims to hands-on investigate "
"the I2P\n"
"network or solve a problem of large proportions we ask you to "
"<b>please</b> \n"
"<a href=\"%(contact)s\">communicate your ideas</a> to the development "
"team, the\n"
"sooner the better. I2P is under constant development and a significant "
"amount\n"
"of roadmapping occurs, therefore your problem may have already been "
"identified\n"
"and flagged for update or patch. In the unlikely event you are conducting"
"\n"
"testing that overlaps with / would be of interest to another research "
"project\n"
"already in motion, we are also able to make you aware of this (with their"
"\n"
"permission, of course), and possibly open the door for collaboration. "
"There is\n"
"also a chance that the test itself may significantly harm the network or\n"
"regular users, and the team may have ideas or suggestions to mitigate "
"that risk\n"
"and increase the safety of your testing."
msgstr ""

#: i2p2www/pages/site/research/index.html:71
msgid "Research Ethics &amp; Testing the Network"
msgstr ""

#: i2p2www/pages/site/research/index.html:73
msgid "General Guidelines"
msgstr ""

#: i2p2www/pages/site/research/index.html:75
msgid ""
"<ol>\n"
"  <li>\n"
"    Consider the benefits and risks - is there any doubt that the "
"research\n"
"    provides more value than danger?\n"
"  </li>\n"
"  <li>\n"
"    If the research can be done on a test network then that is the "
"preferred\n"
"    method\n"
"  </li>\n"
"  <li>\n"
"    If you must operate on the live network, the safest route is only\n"
"    collecting data about yourself\n"
"  </li>\n"
"  <li>\n"
"    If you need 'bigger data', It is recommended to first see if you can "
"use\n"
"    data sets from previous experiments or other third party resources is"
"\n"
"    recommended\n"
"  </li>\n"
"  <li>\n"
"    If you must collect data on the live network, ensure it is safe for\n"
"    publication and collect as little as possible\n"
"  </li>\n"
"  <li>\n"
"    After testing and before publish, review that all data which is to be"
"\n"
"    published publicly is <b><i>not</i></b> intended to be private by the"
"\n"
"    originator\n"
"  </li>\n"
"</ol>"
msgstr ""

#: i2p2www/pages/site/research/index.html:106
msgid "Using a Test Network to Attack I2P"
msgstr ""

#: i2p2www/pages/site/research/index.html:108
msgid ""
"I2P can be run as a separate test network by controlling the locations "
"that a\n"
"new router reseeds from so that it only finds other test routers.\n"
"\n"
"The standard mode of operation is to have one JVM per router instance; "
"hence\n"
"running multiple copies of I2P on a single machine is inadvisable, both "
"due to\n"
"the potential resource drain and the certain port conflicts. To better\n"
"facilitate setting up small test networks, I2P has a multirouter mode "
"which\n"
"enables multiple distinct routers to be run in the same JVM.\n"
"\n"
"MultiRouter can be started from the i2p base directory by running the "
"below\n"
"command."
msgstr ""

#: i2p2www/pages/site/research/index.html:124
msgid ""
"Additionally, I2P can be started in a virtual network mode. This mode "
"disables\n"
"all transports, allowing the router to be tested in isolation without "
"network\n"
"traffic. To enable this mode, add <code>i2p.vmCommSystem=true</code> to "
"the\n"
"router.config before starting."
msgstr ""

#: i2p2www/pages/site/research/index.html:131
msgid "Testing on the Live I2P Network"
msgstr ""

#: i2p2www/pages/site/research/index.html:133
#, python-format
msgid ""
"As stated above in the researcher notes, please <a "
"href=\"%(contact)s\">contact\n"
"  us</a> before you commence your testing. While we do not discourage\n"
"researchers from responsibly testing their ideas on the live network, if "
"an\n"
"attack becomes apparent and we don't have any line of communication then "
"we\n"
"will end up taking countermeasures which could interfere with the test."
msgstr ""

#: i2p2www/pages/site/research/index.html:141
msgid "Router Family Configuration"
msgstr ""

#: i2p2www/pages/site/research/index.html:143
msgid ""
"As of release 0.9.25, I2P supports a router family configuration. This "
"provides\n"
"researchers who run multiple routers with the means to publicly identify "
"those\n"
"routers. In turn, this helps the I2P project understand that these "
"routers are\n"
"not running an attack on the network. It also will prevent other routers "
"from\n"
"including multiple routers of the family in a single tunnel, which could "
"lead\n"
"to deanonymization. Routers that appear to be colluding but do not have a"
"\n"
"declared family may be assumed to be an attack on the network, and may be"
"\n"
"blocked. The best way to ensure the success of your research project is "
"to work\n"
"with us directly."
msgstr ""

#: i2p2www/pages/site/research/index.html:155
msgid ""
"A router family shares a private key so that participation in the family "
"cannot\n"
"be spoofed. To configure a router family, click on the 'I2P Internals' "
"link in\n"
"the router console, and then on the 'Family' tab. Follow the instructions"
" there\n"
"to generate the private key for the first router in the family. Then, "
"export\n"
"the key from that router, and import it to other members of the family."
msgstr ""

#: i2p2www/pages/site/research/questions.html:2
msgid "Open research questions"
msgstr ""

#: i2p2www/pages/site/research/questions.html:5
msgid "Network database"
msgstr ""

#: i2p2www/pages/site/research/questions.html:6
msgid "Floodfills"
msgstr ""

#: i2p2www/pages/site/research/questions.html:19
msgid "Transports"
msgstr ""

#: i2p2www/pages/site/research/questions.html:31
msgid "Tunnels and Destinations"
msgstr ""

#: i2p2www/pages/site/research/questions.html:33
msgid "Peer selection"
msgstr ""

#: i2p2www/pages/site/research/questions.html:46
msgid "Unidirectional tunnels"
msgstr ""

#: i2p2www/pages/site/research/questions.html:52
msgid "Multihoming"
msgstr ""

#: i2p2www/pages/site/research/questions.html:59
msgid "Message routing"
msgstr ""

#: i2p2www/pages/site/research/questions.html:66
msgid "Anonymity"
msgstr ""

#: i2p2www/pages/site/research/questions.html:75
msgid "Network Related"
msgstr ""

#: i2p2www/pages/site/research/vrp.html:2
msgid "Vulnerability Response Process"
msgstr ""

#: 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 ""

#: i2p2www/pages/site/research/vrp.html:10
msgid "This page was last updated in June 2020."
msgstr ""

#: 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"
"centers"
msgstr ""

#: 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 ""

#: i2p2www/pages/site/research/vrp.html:18
msgid "Point of Contact for Security Issues"
msgstr ""

#: i2p2www/pages/site/research/vrp.html:22
msgid "Security Response Team"
msgstr ""

#: i2p2www/pages/site/research/vrp.html:24
msgid ""
"Echelon is the trusted security point-of-contact. He forwards e-mails to "
"team members as appropriate."
msgstr ""

#: i2p2www/pages/site/research/vrp.html:28
msgid "Incident Response"
msgstr ""

#: i2p2www/pages/site/research/vrp.html:31
msgid "Researcher submits report via:"
msgstr ""

#: i2p2www/pages/site/research/vrp.html:37
msgid ""
"Response Team designates a Response Manager who is in charge of the "
"particular\n"
"report based on availability and/or knowledge-set."
msgstr ""

#: i2p2www/pages/site/research/vrp.html:42
#, python-format
msgid ""
"In no more than %(limit)s working days, Response Team should\n"
"respond to researcher using only encrypted methods."
msgstr ""

#: i2p2www/pages/site/research/vrp.html:47
msgid ""
"Response Manager makes inquiries to satisfy any needed information and to"
"\n"
"confirm if submission is indeed a vulnerability."
msgstr ""

#: i2p2www/pages/site/research/vrp.html:52
msgid "If submission proves to be vulnerable, proceed."
msgstr ""

#: i2p2www/pages/site/research/vrp.html:55
msgid "If not vulnerable:"
msgstr ""

#: i2p2www/pages/site/research/vrp.html:59
msgid ""
"Response Manager responds with reasons why submission is not a "
"vulnerability."
msgstr ""

#: i2p2www/pages/site/research/vrp.html:62
msgid ""
"Response Manager moves discussion to a new or existing ticket on public "
"Trac if necessary."
msgstr ""

#: i2p2www/pages/site/research/vrp.html:70
msgid ""
"\n"
"Establish severity of vulnerability:\n"
"  "
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."
msgstr ""

#: i2p2www/pages/site/research/vrp.html:79
msgid "Affects individual routers, or must be carefully exploited."
msgstr ""

#: i2p2www/pages/site/research/vrp.html:83
msgid "Is not easily exploitable."
msgstr ""

#: i2p2www/pages/site/research/vrp.html:89
msgid "Respond according to the severity of the vulnerability:"
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"
"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."
msgstr ""

#: i2p2www/pages/site/research/vrp.html:101
msgid ""
"The notification must not include any details that could suggest an "
"exploitation\n"
"path."
msgstr ""

#: i2p2www/pages/site/research/vrp.html:105
msgid "The latter takes precedence over the former."
msgstr ""

#: i2p2www/pages/site/research/vrp.html:109
msgid "MEDIUM and HIGH severities will require a Point Release."
msgstr ""

#: i2p2www/pages/site/research/vrp.html:112
msgid "LOW severities will be addressed in the next Regular Release."
msgstr ""

#: i2p2www/pages/site/research/vrp.html:118
msgid "Response Team applies appropriate patch(es)."
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."
msgstr ""

#: i2p2www/pages/site/research/vrp.html:125
msgid "Patches are reviewed with the researcher."
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."
msgstr ""

#: i2p2www/pages/site/research/vrp.html:132
msgid "Vulnerability announcement is drafted."
msgstr ""

#: i2p2www/pages/site/research/vrp.html:136
msgid "Include severity of vulnerability."
msgstr ""

#: i2p2www/pages/site/research/vrp.html:139
msgid "Include systems/apps effected."
msgstr ""

#: i2p2www/pages/site/research/vrp.html:142
msgid "Include solutions (if any) if patch cannot be applied."
msgstr ""

#: i2p2www/pages/site/research/vrp.html:146
msgid "Release date is discussed."
msgstr ""

#: i2p2www/pages/site/research/vrp.html:152
msgid ""
"At release date, Response Team coordinates with developers to finalize "
"update:"
msgstr ""

#: i2p2www/pages/site/research/vrp.html:156
msgid "Response Manager propagates the \"hotfix branch\" to trunk."
msgstr ""

#: i2p2www/pages/site/research/vrp.html:159
msgid ""
"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"
"\t\tconsideration for package maintainers in Debian, Ubuntu and F-Droid."
msgstr ""

#: i2p2www/pages/site/research/vrp.html:172
msgid "Post-release Disclosure Process"
msgstr ""

#: i2p2www/pages/site/research/vrp.html:175
#, python-format
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:"
msgstr ""

#: i2p2www/pages/site/research/vrp.html:183
msgid ""
"Response Manager contacts researcher and asks if researcher wishes for "
"credit."
msgstr ""

#: i2p2www/pages/site/research/vrp.html:186
msgid "Finalize vulnerability announcement draft and include the following:"
msgstr ""

#: i2p2www/pages/site/research/vrp.html:190
msgid "Project name and URL."
msgstr ""

#: i2p2www/pages/site/research/vrp.html:193
msgid "Versions known to be affected."
msgstr ""

#: i2p2www/pages/site/research/vrp.html:196
msgid ""
"Versions known to be not affected (for example, the vulnerable code was "
"introduced in a recent version, and older versions are therefore "
"unaffected)."
msgstr ""

#: i2p2www/pages/site/research/vrp.html:199
msgid "Versions not checked."
msgstr ""

#: i2p2www/pages/site/research/vrp.html:202
msgid "Type of vulnerability and its impact."
msgstr ""

#: i2p2www/pages/site/research/vrp.html:205
msgid "If already obtained or applicable, a CVE-ID."
msgstr ""

#: i2p2www/pages/site/research/vrp.html:208
msgid "The planned, coordinated release date."
msgstr ""

#: i2p2www/pages/site/research/vrp.html:211
msgid ""
"Mitigating factors (for example, the vulnerability is only exposed in "
"uncommon, non-default configurations)."
msgstr ""

#: i2p2www/pages/site/research/vrp.html:214
msgid ""
"Workarounds (configuration changes users can make to reduce their "
"exposure to the vulnerability)."
msgstr ""

#: i2p2www/pages/site/research/vrp.html:217
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."
msgstr ""

#: i2p2www/pages/site/research/vrp.html:230
msgid ""
"For HIGH severities, release finalized vulnerability announcement on "
"well-known mailing lists:"
msgstr ""

#: i2p2www/pages/site/research/vrp.html:238
msgid "If applicable, developers request a CVE-ID."
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."
msgstr ""

#: i2p2www/pages/site/research/vrp.html:250
msgid ""
"If the Incident Response process in section III is *not* successfully "
"completed:"
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"
"future."
msgstr ""

#: i2p2www/pages/site/research/vrp.html:259
msgid ""
"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"
"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"
"the researcher (after %(limit)s days) has every right to expose the\n"
"vulnerability to the public."
msgstr ""

#: i2p2www/pages/site/research/vrp.html:277
msgid "Incident Analysis"
msgstr ""

#: i2p2www/pages/site/research/vrp.html:280
msgid "Isolate codebase"
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:"
msgstr ""

#: i2p2www/pages/site/research/vrp.html:286
msgid "Problematic implementation of classes/libraries/functions, etc."
msgstr ""

#: i2p2www/pages/site/research/vrp.html:289
msgid "Focus on apps/distro packaging, etc."
msgstr ""

#: i2p2www/pages/site/research/vrp.html:292
msgid "Operator/config error, etc."
msgstr ""

#: i2p2www/pages/site/research/vrp.html:300
msgid "Auditing"
msgstr ""

#: i2p2www/pages/site/research/vrp.html:306
msgid "Auditing of problem area(s) as discussed in point 1."
msgstr ""

#: i2p2www/pages/site/research/vrp.html:309
msgid "Generate internal reports and store for future reference."
msgstr ""

#: i2p2www/pages/site/research/vrp.html:312
msgid ""
"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"
"completion of section V."
msgstr ""

#: i2p2www/pages/site/research/vrp.html:326
msgid "Resolutions"
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"
"addressed via the following:"
msgstr ""

#: i2p2www/pages/site/research/vrp.html:341
msgid "Continuous Improvement"
msgstr ""

#: i2p2www/pages/site/research/vrp.html:344
msgid ""
"Response Team and developers should hold annual meetings to review the "
"previous\n"
"year's incidents."
msgstr ""

#: i2p2www/pages/site/research/vrp.html:349
msgid ""
"Response Team or designated person(s) should give a brief presentation, "
"including:"
msgstr ""

#: i2p2www/pages/site/research/vrp.html:353
msgid "Areas of I2P affected by the incidents."
msgstr ""

#: i2p2www/pages/site/research/vrp.html:356
msgid "Any network downtime or monetary cost (if any) of the incidents."
msgstr ""

#: i2p2www/pages/site/research/vrp.html:359
msgid "Ways in which the incidents could have been avoided (if any)."
msgstr ""

#: i2p2www/pages/site/research/vrp.html:362
msgid "How effective this process was in dealing with the incidents."
msgstr ""

#: i2p2www/pages/site/research/vrp.html:368
msgid "After the presentation, Response Team and developers should discuss:"
msgstr ""

#: i2p2www/pages/site/research/vrp.html:372
msgid "Potential changes to development processes to reduce future incidents."
msgstr ""

#: i2p2www/pages/site/research/vrp.html:375
msgid "Potential changes to this process to improve future responses."
msgstr ""