aboutsummaryrefslogtreecommitdiff
path: root/locale/messages.pot
diff options
context:
space:
mode:
Diffstat (limited to 'locale/messages.pot')
-rw-r--r--locale/messages.pot114
1 files changed, 113 insertions, 1 deletions
diff --git a/locale/messages.pot b/locale/messages.pot
index cc5afdcf..4082e644 100644
--- a/locale/messages.pot
+++ b/locale/messages.pot
@@ -8,7 +8,7 @@ msgid ""
8msgstr "" 8msgstr ""
9"Project-Id-Version: PROJECT VERSION\n" 9"Project-Id-Version: PROJECT VERSION\n"
10"Report-Msgid-Bugs-To: EMAIL@ADDRESS\n" 10"Report-Msgid-Bugs-To: EMAIL@ADDRESS\n"
11"POT-Creation-Date: 2022-10-24 23:15+0900\n" 11"POT-Creation-Date: 2022-12-06 23:58+0900\n"
12"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" 12"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
13"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n" 13"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
14"Language-Team: LANGUAGE <LL@li.org>\n" 14"Language-Team: LANGUAGE <LL@li.org>\n"
@@ -2928,6 +2928,118 @@ msgstr ""
2928msgid "Videos related to GNUnet" 2928msgid "Videos related to GNUnet"
2929msgstr "" 2929msgstr ""
2930 2930
2931#: template/dev_pages/t3sserakt.html.j2:8
2932msgid "Developer page: t3sserakt"
2933msgstr ""
2934
2935#: template/dev_pages/t3sserakt.html.j2:23
2936msgid "Current Work"
2937msgstr ""
2938
2939#: template/dev_pages/t3sserakt.html.j2:25
2940msgid ""
2941"At the moment I am working on Transport Next Generation (TNG). The "
2942"current GNUnet TRANSPORT architecture with its pluggable transport "
2943"mechanism (TCP, UDP, HTTP(S) and other protocols) together with the ATS "
2944"subsystem for bandwidth allocation and choosing plugins has several "
2945"issues with its design. With the Layer-2-Overlay project we like to "
2946"implement the design goals of the future GNUnet TRANSPORT Next Generation"
2947" (TNG) subsystem. For details have a look on the <a "
2948"href=\"https://www.gnunet.org/en/l2o/\">project page</a>."
2949msgstr ""
2950
2951#: template/dev_pages/t3sserakt.html.j2:40
2952msgid "Future Work"
2953msgstr ""
2954
2955#: template/dev_pages/t3sserakt.html.j2:42
2956msgid "The next project I will work on is named \"Probabilistic NAT Traversal\"."
2957msgstr ""
2958
2959#: template/dev_pages/t3sserakt.html.j2:47
2960msgid ""
2961"Today consumer devices are behind a NAT quite often, restricting internet"
2962" connectivity. There are several methods to reach peers being behind a "
2963"NAT, but there are as many reasons those existing methods might fail. We "
2964"will implement a new way of NAT traversal that we think of being "
2965"independent from the existing network configuration, and does not require"
2966" a third party which is not natted helping two peers to connect to each "
2967"other. Two peers trying to connect to each other will send out a burst of"
2968" connection attempts to the other peer on different ports. The sheer vast"
2969" amount of connections attempts from both side will lead to a high "
2970"probability that two connection attempts from both peers onto the same "
2971"port will be at the same time leading to a successful connection between "
2972"those peers."
2973msgstr ""
2974
2975#: template/dev_pages/t3sserakt.html.j2:57
2976msgid ""
2977"There are two problems a NAT traversal method has to solve. First there "
2978"needs to be a method to know the global IP address of a peer A another "
2979"peer B wants to connect to. Second – because inbound connections from the"
2980" outside are blocked by the NAT firewall of peer A, peer A needs to be "
2981"informed of a connection attempt by peer B. The most common solution for "
2982"both problems is to have a third party C which is not behind a NAT. This "
2983"third party C obviously knows the global IP address of natted peers, "
2984"after peer A is trying to connect to C. Peer B tells C it likes to "
2985"connect to peer A, and C informs A about it. Using this method for a "
2986"privacy preserving network like GNUnet, this could facilitate eclipse "
2987"attacks (isolating a peer) which then can be used for deanonymization "
2988"attacks and cencorship. Also any additional infrastructure needed to "
2989"provide some kind of functionality has to be maintained by someone, "
2990"becoming a target and/or point of failure. Therefore this method is not "
2991"suitable. More sophisticated methods like \"Autonomous NAT Traversal "
2992"(pwnat)\" using ICMP fake message, which do not need a third party for "
2993"the initiation of the connection, are not successful in all "
2994"circumstances, because this method depend on the behavior of the NAT "
2995"firewall."
2996msgstr ""
2997
2998#: template/dev_pages/t3sserakt.html.j2:71
2999msgid ""
3000"If two natted peers are using the method to start a burst of connection "
3001"attempts, this method still needs the global IP of the other peer and a "
3002"“start signal” to coordinate. In the NGI Assure project L2O we are "
3003"establishing a backchannel with neighbourhood routing over an ad- hoc "
3004"distance vector protocol to solve the problem of not directly connected "
3005"peers. The peers serving as hops to a distant peer which are a direct "
3006"neighbour of the start or end peer on that path do know the global IP "
3007"address of the start or end peer. If those two peers like to use the "
3008"burst method for hole punching the global IP address is known. Via the "
3009"distance vector protocol we are also able to communicate the \"start "
3010"signal\". Also in the L2O project we introduced a new test framework for "
3011"GNUnet to test network setups with peers having restricted connectivity. "
3012"This test framework will be used to create test setups suitable to test "
3013"possible NAT configurations. A challenge for this NAT traversal method "
3014"will be how to handle the burst in terms of network load, thus we need to"
3015" experiment with different frequencies and the amount of connection "
3016"attempts."
3017msgstr ""
3018
3019#: template/dev_pages/t3sserakt.html.j2:93
3020msgid "Past Work"
3021msgstr ""
3022
3023#: template/dev_pages/t3sserakt.html.j2:95
3024msgid ""
3025"In the past I have tried to help making the vision of the <a "
3026"href=\"http://secushare.org\">secushare</a> project a reality. To achieve"
3027" this the GNUnet framework was the perfect match for a solution to "
3028"fullfill the privacy preserving part of that vision, and we could "
3029"concentrate to build a tool for social communication that deserves its "
3030"name. While trying to use GNUnet, we found and fixed bugs. For example "
3031"there was one <a "
3032"href=\"https://bugs.gnunet.org/view.php?id=5822\">bug</a> in CADET which "
3033"prevented the re-establishment of a connection after a communication "
3034"partner suddenly stopped communicating. From our perspective there is no "
3035"alternativ to GNUnet, which led us to first bring the parts of GNUnet "
3036"needed by secushare to a state that they can be used prouctively."
3037msgstr ""
3038
3039#: template/dev_pages/t3sserakt.html.j2:110
3040msgid "Contact Information"
3041msgstr ""
3042
2931#: template/l2o/index.html.j2:6 template/l2o/mile1.html.j2:6 3043#: template/l2o/index.html.j2:6 template/l2o/mile1.html.j2:6
2932#: template/l2o/mile2.html.j2:6 template/l2o/mile3.html.j2:6 3044#: template/l2o/mile2.html.j2:6 template/l2o/mile3.html.j2:6
2933#: template/l2o/mile4.html.j2:6 template/l2o/testng.html.j2:6 3045#: template/l2o/mile4.html.j2:6 template/l2o/testng.html.j2:6