aboutsummaryrefslogtreecommitdiff
path: root/locale/pt/LC_MESSAGES/messages.po
diff options
context:
space:
mode:
Diffstat (limited to 'locale/pt/LC_MESSAGES/messages.po')
-rw-r--r--locale/pt/LC_MESSAGES/messages.po111
1 files changed, 110 insertions, 1 deletions
diff --git a/locale/pt/LC_MESSAGES/messages.po b/locale/pt/LC_MESSAGES/messages.po
index edd2fb02..d30eebce 100644
--- a/locale/pt/LC_MESSAGES/messages.po
+++ b/locale/pt/LC_MESSAGES/messages.po
@@ -7,7 +7,7 @@ msgid ""
7msgstr "" 7msgstr ""
8"Project-Id-Version: PROJECT VERSION\n" 8"Project-Id-Version: PROJECT VERSION\n"
9"Report-Msgid-Bugs-To: EMAIL@ADDRESS\n" 9"Report-Msgid-Bugs-To: EMAIL@ADDRESS\n"
10"POT-Creation-Date: 2022-10-24 23:15+0900\n" 10"POT-Creation-Date: 2022-12-06 23:58+0900\n"
11"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" 11"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
12"Last-Translator: Automatically generated\n" 12"Last-Translator: Automatically generated\n"
13"Language-Team: none\n" 13"Language-Team: none\n"
@@ -2870,6 +2870,115 @@ msgstr ""
2870msgid "Videos related to GNUnet" 2870msgid "Videos related to GNUnet"
2871msgstr "" 2871msgstr ""
2872 2872
2873#: template/dev_pages/t3sserakt.html.j2:8
2874msgid "Developer page: t3sserakt"
2875msgstr ""
2876
2877#: template/dev_pages/t3sserakt.html.j2:23
2878msgid "Current Work"
2879msgstr ""
2880
2881#: template/dev_pages/t3sserakt.html.j2:25
2882msgid ""
2883"At the moment I am working on Transport Next Generation (TNG). The current "
2884"GNUnet TRANSPORT architecture with its pluggable transport mechanism (TCP, "
2885"UDP, HTTP(S) and other protocols) together with the ATS subsystem for "
2886"bandwidth allocation and choosing plugins has several issues with its "
2887"design. With the Layer-2-Overlay project we like to implement the design "
2888"goals of the future GNUnet TRANSPORT Next Generation (TNG) subsystem. For "
2889"details have a look on the <a href=\"https://www.gnunet.org/en/l2o/"
2890"\">project page</a>."
2891msgstr ""
2892
2893#: template/dev_pages/t3sserakt.html.j2:40
2894msgid "Future Work"
2895msgstr ""
2896
2897#: template/dev_pages/t3sserakt.html.j2:42
2898msgid ""
2899"The next project I will work on is named \"Probabilistic NAT Traversal\"."
2900msgstr ""
2901
2902#: template/dev_pages/t3sserakt.html.j2:47
2903msgid ""
2904"Today consumer devices are behind a NAT quite often, restricting internet "
2905"connectivity. There are several methods to reach peers being behind a NAT, "
2906"but there are as many reasons those existing methods might fail. We will "
2907"implement a new way of NAT traversal that we think of being independent from "
2908"the existing network configuration, and does not require a third party which "
2909"is not natted helping two peers to connect to each other. Two peers trying "
2910"to connect to each other will send out a burst of connection attempts to the "
2911"other peer on different ports. The sheer vast amount of connections attempts "
2912"from both side will lead to a high probability that two connection attempts "
2913"from both peers onto the same port will be at the same time leading to a "
2914"successful connection between those peers."
2915msgstr ""
2916
2917#: template/dev_pages/t3sserakt.html.j2:57
2918msgid ""
2919"There are two problems a NAT traversal method has to solve. First there "
2920"needs to be a method to know the global IP address of a peer A another peer "
2921"B wants to connect to. Second – because inbound connections from the outside "
2922"are blocked by the NAT firewall of peer A, peer A needs to be informed of a "
2923"connection attempt by peer B. The most common solution for both problems is "
2924"to have a third party C which is not behind a NAT. This third party C "
2925"obviously knows the global IP address of natted peers, after peer A is "
2926"trying to connect to C. Peer B tells C it likes to connect to peer A, and C "
2927"informs A about it. Using this method for a privacy preserving network like "
2928"GNUnet, this could facilitate eclipse attacks (isolating a peer) which then "
2929"can be used for deanonymization attacks and cencorship. Also any additional "
2930"infrastructure needed to provide some kind of functionality has to be "
2931"maintained by someone, becoming a target and/or point of failure. Therefore "
2932"this method is not suitable. More sophisticated methods like \"Autonomous "
2933"NAT Traversal (pwnat)\" using ICMP fake message, which do not need a third "
2934"party for the initiation of the connection, are not successful in all "
2935"circumstances, because this method depend on the behavior of the NAT "
2936"firewall."
2937msgstr ""
2938
2939#: template/dev_pages/t3sserakt.html.j2:71
2940msgid ""
2941"If two natted peers are using the method to start a burst of connection "
2942"attempts, this method still needs the global IP of the other peer and a "
2943"“start signal” to coordinate. In the NGI Assure project L2O we are "
2944"establishing a backchannel with neighbourhood routing over an ad- hoc "
2945"distance vector protocol to solve the problem of not directly connected "
2946"peers. The peers serving as hops to a distant peer which are a direct "
2947"neighbour of the start or end peer on that path do know the global IP "
2948"address of the start or end peer. If those two peers like to use the burst "
2949"method for hole punching the global IP address is known. Via the distance "
2950"vector protocol we are also able to communicate the \"start signal\". Also "
2951"in the L2O project we introduced a new test framework for GNUnet to test "
2952"network setups with peers having restricted connectivity. This test "
2953"framework will be used to create test setups suitable to test possible NAT "
2954"configurations. A challenge for this NAT traversal method will be how to "
2955"handle the burst in terms of network load, thus we need to experiment with "
2956"different frequencies and the amount of connection attempts."
2957msgstr ""
2958
2959#: template/dev_pages/t3sserakt.html.j2:93
2960msgid "Past Work"
2961msgstr ""
2962
2963#: template/dev_pages/t3sserakt.html.j2:95
2964msgid ""
2965"In the past I have tried to help making the vision of the <a href=\"http://"
2966"secushare.org\">secushare</a> project a reality. To achieve this the GNUnet "
2967"framework was the perfect match for a solution to fullfill the privacy "
2968"preserving part of that vision, and we could concentrate to build a tool for "
2969"social communication that deserves its name. While trying to use GNUnet, we "
2970"found and fixed bugs. For example there was one <a href=\"https://bugs."
2971"gnunet.org/view.php?id=5822\">bug</a> in CADET which prevented the re-"
2972"establishment of a connection after a communication partner suddenly stopped "
2973"communicating. From our perspective there is no alternativ to GNUnet, which "
2974"led us to first bring the parts of GNUnet needed by secushare to a state "
2975"that they can be used prouctively."
2976msgstr ""
2977
2978#: template/dev_pages/t3sserakt.html.j2:110
2979msgid "Contact Information"
2980msgstr ""
2981
2873#: template/l2o/index.html.j2:6 template/l2o/mile1.html.j2:6 2982#: template/l2o/index.html.j2:6 template/l2o/mile1.html.j2:6
2874#: template/l2o/mile2.html.j2:6 template/l2o/mile3.html.j2:6 2983#: template/l2o/mile2.html.j2:6 template/l2o/mile3.html.j2:6
2875#: template/l2o/mile4.html.j2:6 template/l2o/testng.html.j2:6 2984#: template/l2o/mile4.html.j2:6 template/l2o/testng.html.j2:6