# Translations template for I2P. # Copyright (C) 2018 ORGANIZATION # This file is distributed under the same license as the I2P project. # FIRST AUTHOR , 2018. # #, fuzzy msgid "" msgstr "" "Project-Id-Version: I2P website\n" "Report-Msgid-Bugs-To: http://trac.i2p2.de\n" "POT-Creation-Date: 2018-02-12 00:06+0000\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language-Team: LANGUAGE \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 msgid "February 2016" msgstr "" #: i2p2www/pages/site/research/index.html:5 msgid "" "Academic research and analysis of I2P is an important part of ensuring " "that the software and network performs as expected and is safe for users " "in hostile environments." msgstr "" #: i2p2www/pages/site/research/index.html:9 #, python-format msgid "" "\n" "Recent events have prompted anonymity projects to provide specific " "guidelines\n" "for responsible research.\n" "We endorse the Tor Ethical Research Guidelines " "and incorporate them here.\n" "Please follow the Tor guidelines when researching I2P as well.\n" msgstr "" #: i2p2www/pages/site/research/index.html:16 #, 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" "Free Haven Anonymity Bibliography.\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:26 #, python-format msgid "" "A list of known published papers about I2P is available here." msgstr "" #: i2p2www/pages/site/research/index.html:30 #, python-format msgid "" "\n" "See also the Tor Research Home Page for general " "guidance and links.\n" msgstr "" #: i2p2www/pages/site/research/index.html:34 msgid "Testing Attacks on I2P" msgstr "" #: i2p2www/pages/site/research/index.html:36 msgid "" "I2P can be run as a separate test network by controlling the locations " "that a new router reseeds from so that it only finds other test routers." msgstr "" #: i2p2www/pages/site/research/index.html:40 msgid "" "The standard mode of operation is to have one JVM per router instance; " "hence running multiple copies of I2P on a single machine is inadvisable, " "both due to the potential resource drain and the certain port conflicts. " "To better facilitate setting up small test networks, I2P has a " "multirouter mode which enables multiple distinct routers to be run in the" " same JVM." msgstr "" #: i2p2www/pages/site/research/index.html:44 msgid "" "MultiRouter can be started from the i2p base directory by running the " "below command." msgstr "" #: i2p2www/pages/site/research/index.html:49 msgid "" "Additionally, I2P can be started in a virtual network mode. This mode " "disables all transports, allowing the router to be tested in isolation " "without network traffic. To enable this mode, add " "i2p.vmCommSystem=true to the router.config before starting." msgstr "" #: i2p2www/pages/site/research/index.html:53 msgid "Testing the Live I2P Network" msgstr "" #: i2p2www/pages/site/research/index.html:55 #, python-format msgid "" "If you are planning on conducting research on the live I2P network, " "please contact us before you commence your " "testing. While we do not discourage researchers from responsibly testing " "their ideas on the live network, if an attack becomes apparent and we " "don't have any line of communication then we will end up taking " "countermeasures which could interfere with the test." msgstr "" #: i2p2www/pages/site/research/index.html:60 msgid "Router Family Configuration" msgstr "" #: i2p2www/pages/site/research/index.html:62 msgid "" "As of release 0.9.25, I2P supports a router family configuration.\n" "This provides researchers who run multiple routers with the means to " "publicly identify those routers.\n" "In turn, this helps the I2P project understand that these routers are not" " running an attack on the network.\n" "It also will prevent other routers from including multiple routers of the" " family in a single tunnel,\n" "which could lead to deanonymization.\n" "Routers that appear to be colluding but do not have a declared family may" " be assumed to\n" "be an attack on the network, and may be blocked.\n" "The best way to ensure the success of your research project is to work " "with us." msgstr "" #: i2p2www/pages/site/research/index.html:73 msgid "" "A router family shares a private key so that participation in the family " "cannot be spoofed.\n" "To configure a router family, click on the 'I2P Internals' link in the " "router console,\n" "and then on the 'Family' tab.\n" "Follow the instructions there to generate the private key for the first " "router in the family.\n" "Then, export 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:4 msgid "Network database" msgstr "" #: i2p2www/pages/site/research/questions.html:6 msgid "Transports" msgstr "" #: i2p2www/pages/site/research/questions.html:11 msgid "Tunnels and Destinations" msgstr "" #: i2p2www/pages/site/research/questions.html:13 msgid "Peer selection" msgstr "" #: i2p2www/pages/site/research/questions.html:15 msgid "Unidirectional tunnels" msgstr "" #: i2p2www/pages/site/research/questions.html:21 msgid "Multihoming" msgstr "" #: i2p2www/pages/site/research/questions.html:28 msgid "Message routing" msgstr "" #: i2p2www/pages/site/research/vrp.html:2 msgid "Vulnerability Response Process" msgstr "" #: i2p2www/pages/site/research/vrp.html:3 msgid "January 2017" 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 "Point of Contact for Security Issues" msgstr "" #: i2p2www/pages/site/research/vrp.html:14 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:" msgstr "" #: i2p2www/pages/site/research/vrp.html:25 msgid "Incident Response" msgstr "" #: i2p2www/pages/site/research/vrp.html:28 msgid "Researcher submits report via one or both of two methods:" msgstr "" #: i2p2www/pages/site/research/vrp.html:32 msgid "Email" 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 gratefully\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 "" "If over email, Response Manager opens a HackerOne issue for new " "submission." msgstr "" #: i2p2www/pages/site/research/vrp.html:74 msgid "" "\n" "Establish severity of vulnerability:\n" " " 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." msgstr "" #: i2p2www/pages/site/research/vrp.html:83 msgid "Effects individual routers, or must be carefully exploited." msgstr "" #: i2p2www/pages/site/research/vrp.html:87 msgid "Is not easily exploitable." msgstr "" #: i2p2www/pages/site/research/vrp.html:93 msgid "Respond according to the severity of the vulnerability:" 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" "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." msgstr "" #: i2p2www/pages/site/research/vrp.html:105 msgid "" "The notification must not include any details that could suggest an " "exploitation\n" "path." msgstr "" #: i2p2www/pages/site/research/vrp.html:109 msgid "The latter takes precedence over the former." msgstr "" #: i2p2www/pages/site/research/vrp.html:113 msgid "MEDIUM and HIGH severities will require a Point Release." msgstr "" #: i2p2www/pages/site/research/vrp.html:116 msgid "LOW severities will be addressed in the next Regular Release." msgstr "" #: i2p2www/pages/site/research/vrp.html:122 msgid "Response Team applies appropriate patch(es)." msgstr "" #: i2p2www/pages/site/research/vrp.html:126 msgid "" "Response Manager designates a PRIVATE monotone \"hotfix branch\" to work " "in." msgstr "" #: i2p2www/pages/site/research/vrp.html:129 msgid "Patches are reviewed with the researcher." 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." msgstr "" #: i2p2www/pages/site/research/vrp.html:136 msgid "Vulnerability announcement is drafted." msgstr "" #: i2p2www/pages/site/research/vrp.html:140 msgid "Include severity of vulnerability." msgstr "" #: i2p2www/pages/site/research/vrp.html:143 msgid "Include systems/apps effected." msgstr "" #: i2p2www/pages/site/research/vrp.html:146 msgid "Include solutions (if any) if patch cannot be applied." msgstr "" #: i2p2www/pages/site/research/vrp.html:150 msgid "Release date is discussed." msgstr "" #: i2p2www/pages/site/research/vrp.html:156 msgid "" "At release date, Response Team coordinates with developers to finalize " "update:" msgstr "" #: i2p2www/pages/site/research/vrp.html:160 msgid "Response Manager propagates the \"hotfix branch\" to trunk." msgstr "" #: i2p2www/pages/site/research/vrp.html:163 msgid "" "Response Manager includes vulnerability announcement draft in release " "notes." msgstr "" #: i2p2www/pages/site/research/vrp.html:166 msgid "Proceed with the Point or Regular Release." msgstr "" #: i2p2www/pages/site/research/vrp.html:173 msgid "Post-release Disclosure Process" msgstr "" #: i2p2www/pages/site/research/vrp.html:176 #, python-format 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:" msgstr "" #: i2p2www/pages/site/research/vrp.html:184 msgid "" "Response Manager contacts researcher and asks if researcher wishes for " "credit." msgstr "" #: i2p2www/pages/site/research/vrp.html:187 msgid "Finalize vulnerability announcement draft and include the following:" msgstr "" #: i2p2www/pages/site/research/vrp.html:191 msgid "Project name and URL." msgstr "" #: i2p2www/pages/site/research/vrp.html:194 msgid "Versions known to be affected." msgstr "" #: i2p2www/pages/site/research/vrp.html:197 msgid "" "Versions known to be not affected (for example, the vulnerable code was " "introduced in a recent version, and older versions are therefore " "unaffected)." msgstr "" #: i2p2www/pages/site/research/vrp.html:200 msgid "Versions not checked." msgstr "" #: i2p2www/pages/site/research/vrp.html:203 msgid "Type of vulnerability and its impact." msgstr "" #: i2p2www/pages/site/research/vrp.html:206 msgid "If already obtained or applicable, a CVE-ID." msgstr "" #: i2p2www/pages/site/research/vrp.html:209 msgid "The planned, coordinated release date." msgstr "" #: i2p2www/pages/site/research/vrp.html:212 msgid "" "Mitigating factors (for example, the vulnerability is only exposed in " "uncommon, non-default configurations)." msgstr "" #: i2p2www/pages/site/research/vrp.html:215 msgid "" "Workarounds (configuration changes users can make to reduce their " "exposure to the vulnerability)." msgstr "" #: i2p2www/pages/site/research/vrp.html:218 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." msgstr "" #: i2p2www/pages/site/research/vrp.html:226 msgid "" "For HIGH severities, release finalized vulnerability announcement on " "well-known mailing lists:" msgstr "" #: i2p2www/pages/site/research/vrp.html:234 msgid "If applicable, developers request a CVE-ID." 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." msgstr "" #: i2p2www/pages/site/research/vrp.html:246 msgid "" "If the Incident Response process in section III is *not* successfully " "completed:" 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" "future." msgstr "" #: i2p2www/pages/site/research/vrp.html:255 msgid "" "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" "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" "the researcher (after %(limit)s days) has every right to expose the\n" "vulnerability to the public." msgstr "" #: i2p2www/pages/site/research/vrp.html:273 msgid "Incident Analysis" msgstr "" #: i2p2www/pages/site/research/vrp.html:276 msgid "Isolate codebase" 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:" msgstr "" #: i2p2www/pages/site/research/vrp.html:282 msgid "Problematic implementation of classes/libraries/functions, etc." msgstr "" #: i2p2www/pages/site/research/vrp.html:285 msgid "Focus on apps/distro packaging, etc." msgstr "" #: i2p2www/pages/site/research/vrp.html:288 msgid "Operator/config error, etc." msgstr "" #: i2p2www/pages/site/research/vrp.html:296 msgid "Auditing" msgstr "" #: i2p2www/pages/site/research/vrp.html:302 msgid "Auditing of problem area(s) as discussed in point 1." msgstr "" #: i2p2www/pages/site/research/vrp.html:305 msgid "Generate internal reports and store for future reference." msgstr "" #: i2p2www/pages/site/research/vrp.html:308 msgid "" "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" "completion of section V." msgstr "" #: i2p2www/pages/site/research/vrp.html:322 msgid "Resolutions" 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" "addressed via the following:" msgstr "" #: i2p2www/pages/site/research/vrp.html:338 msgid "Continuous Improvement" msgstr "" #: i2p2www/pages/site/research/vrp.html:341 msgid "" "Response Team and developers should hold annual meetings to review the " "previous\n" "year's incidents." msgstr "" #: i2p2www/pages/site/research/vrp.html:346 msgid "" "Response Team or designated person(s) should give a brief presentation, " "including:" msgstr "" #: i2p2www/pages/site/research/vrp.html:350 msgid "Areas of I2P affected by the incidents." msgstr "" #: i2p2www/pages/site/research/vrp.html:353 msgid "Any network downtime or monetary cost (if any) of the incidents." msgstr "" #: i2p2www/pages/site/research/vrp.html:356 msgid "Ways in which the incidents could have been avoided (if any)." msgstr "" #: i2p2www/pages/site/research/vrp.html:359 msgid "How effective this process was in dealing with the incidents." msgstr "" #: i2p2www/pages/site/research/vrp.html:365 msgid "After the presentation, Response Team and developers should discuss:" msgstr "" #: i2p2www/pages/site/research/vrp.html:369 msgid "Potential changes to development processes to reduce future incidents." msgstr "" #: i2p2www/pages/site/research/vrp.html:372 msgid "Potential changes to this process to improve future responses." msgstr ""