po

1 files changed, 112 insertions, 1 deletions

diff --git a/locale/ar/LC_MESSAGES/messages.po b/locale/ar/LC_MESSAGES/messages.po
index a0dca494..d3b59f90 100644
--- a/locale/ar/LC_MESSAGES/messages.po
+++ b/locale/ar/LC_MESSAGES/messages.po
@@ -7,7 +7,7 @@ msgid ""
 msgstr ""
 "Project-Id-Version: PROJECT VERSION\n"
 "Report-Msgid-Bugs-To: EMAIL@ADDRESS\n"
-"POT-Creation-Date: 2022-10-24 23:15+0900\n"
+"POT-Creation-Date: 2022-12-06 23:58+0900\n"
 "PO-Revision-Date: 2021-05-21 14:59+0000\n"
 "Last-Translator: Shorouk Hassouna <shoroukhassuna@gmail.com>\n"
 "Language-Team: Arabic <http://weblate.taler.net/projects/gnunet/website/ar/"
@@ -2909,6 +2909,117 @@ msgstr ""
 msgid "Videos related to GNUnet"
 msgstr ""
 
+#: template/dev_pages/t3sserakt.html.j2:8
+msgid "Developer page: t3sserakt"
+msgstr ""
+
+#: template/dev_pages/t3sserakt.html.j2:23
+msgid "Current Work"
+msgstr ""
+
+#: template/dev_pages/t3sserakt.html.j2:25
+msgid ""
+"At the moment I am working on Transport Next Generation (TNG). The current "
+"GNUnet TRANSPORT architecture with its pluggable transport mechanism (TCP, "
+"UDP, HTTP(S) and other protocols) together with the ATS subsystem for "
+"bandwidth allocation and choosing plugins has several issues with its "
+"design. With the Layer-2-Overlay project we like to implement the design "
+"goals of the future GNUnet TRANSPORT Next Generation (TNG) subsystem. For "
+"details have a look on the <a href=\"https://www.gnunet.org/en/l2o/"
+"\">project page</a>."
+msgstr ""
+
+#: template/dev_pages/t3sserakt.html.j2:40
+msgid "Future Work"
+msgstr ""
+
+#: template/dev_pages/t3sserakt.html.j2:42
+msgid ""
+"The next project I will work on is named \"Probabilistic NAT Traversal\"."
+msgstr ""
+
+#: template/dev_pages/t3sserakt.html.j2:47
+msgid ""
+"Today consumer devices are behind a NAT quite often, restricting internet "
+"connectivity. There are several methods to reach peers being behind a NAT, "
+"but there are as many reasons those existing methods might fail. We will "
+"implement a new way of NAT traversal that we think of being independent from "
+"the existing network configuration, and does not require a third party which "
+"is not natted helping two peers to connect to each other. Two peers trying "
+"to connect to each other will send out a burst of connection attempts to the "
+"other peer on different ports. The sheer vast amount of connections attempts "
+"from both side will lead to a high probability that two connection attempts "
+"from both peers onto the same port will be at the same time leading to a "
+"successful connection between those peers."
+msgstr ""
+
+#: template/dev_pages/t3sserakt.html.j2:57
+msgid ""
+"There are two problems a NAT traversal method has to solve. First there "
+"needs to be a method to know the global IP address of a peer A another peer "
+"B wants to connect to. Second – because inbound connections from the outside "
+"are blocked by the NAT firewall of peer A, peer A needs to be informed of a "
+"connection attempt by peer B. The most common solution for both problems is "
+"to have a third party C which is not behind a NAT. This third party C "
+"obviously knows the global IP address of natted peers, after peer A is "
+"trying to connect to C. Peer B tells C it likes to connect to peer A, and C "
+"informs A about it. Using this method for a privacy preserving network like "
+"GNUnet, this could facilitate eclipse attacks (isolating a peer) which then "
+"can be used for deanonymization attacks and cencorship. Also any additional "
+"infrastructure needed to provide some kind of functionality has to be "
+"maintained by someone, becoming a target and/or point of failure. Therefore "
+"this method is not suitable. More sophisticated methods like \"Autonomous "
+"NAT Traversal (pwnat)\" using ICMP fake message, which do not need a third "
+"party for the initiation of the connection, are not successful in all "
+"circumstances, because this method depend on the behavior of the NAT "
+"firewall."
+msgstr ""
+
+#: template/dev_pages/t3sserakt.html.j2:71
+msgid ""
+"If two natted peers are using the method to start a burst of connection "
+"attempts, this method still needs the global IP of the other peer and a "
+"“start signal” to coordinate. In the NGI Assure project L2O we are "
+"establishing a backchannel with neighbourhood routing over an ad- hoc "
+"distance vector protocol to solve the problem of not directly connected "
+"peers. The peers serving as hops to a distant peer which are a direct "
+"neighbour of the start or end peer on that path do know the global IP "
+"address of the start or end peer. If those two peers like to use the burst "
+"method for hole punching the global IP address is known. Via the distance "
+"vector protocol we are also able to communicate the \"start signal\". Also "
+"in the L2O project we introduced a new test framework for GNUnet to test "
+"network setups with peers having restricted connectivity. This test "
+"framework will be used to create test setups suitable to test possible NAT "
+"configurations. A challenge for this NAT traversal method will be how to "
+"handle the burst in terms of network load, thus we need to experiment with "
+"different frequencies and the amount of connection attempts."
+msgstr ""
+
+#: template/dev_pages/t3sserakt.html.j2:93
+msgid "Past Work"
+msgstr ""
+
+#: template/dev_pages/t3sserakt.html.j2:95
+msgid ""
+"In the past I have tried to help making the vision of the <a href=\"http://"
+"secushare.org\">secushare</a> project a reality. To achieve this the GNUnet "
+"framework was the perfect match for a solution to fullfill the privacy "
+"preserving part of that vision, and we could concentrate to build a tool for "
+"social communication that deserves its name. While trying to use GNUnet, we "
+"found and fixed bugs. For example there was one <a href=\"https://bugs."
+"gnunet.org/view.php?id=5822\">bug</a> in CADET which prevented the re-"
+"establishment of a connection after a communication partner suddenly stopped "
+"communicating. From our perspective there is no alternativ to GNUnet, which "
+"led us to first bring the parts of GNUnet needed by secushare to a state "
+"that they can be used prouctively."
+msgstr ""
+
+#: template/dev_pages/t3sserakt.html.j2:110
+#, fuzzy
+#| msgid "Continuous Integration"
+msgid "Contact Information"
+msgstr "الدمج المستمر"
+
 #: template/l2o/index.html.j2:6 template/l2o/mile1.html.j2:6
 #: template/l2o/mile2.html.j2:6 template/l2o/mile3.html.j2:6
 #: template/l2o/mile4.html.j2:6 template/l2o/testng.html.j2:6