aboutsummaryrefslogtreecommitdiff
path: root/locale/hi
diff options
context:
space:
mode:
authorMartin Schanzenbach <schanzen@gnunet.org>2022-12-07 00:19:40 +0900
committerMartin Schanzenbach <schanzen@gnunet.org>2022-12-07 00:19:40 +0900
commitcf944d8c5fc1239f27136605c87ef895f6dcedb7 (patch)
tree9fb5d62a7129e816236e038f469ef5fd2d7a87f7 /locale/hi
parent930acde63fef036e1a83f3acc50cad0ea40f1a0f (diff)
downloadwww-cf944d8c5fc1239f27136605c87ef895f6dcedb7.tar.gz
www-cf944d8c5fc1239f27136605c87ef895f6dcedb7.zip
po
Diffstat (limited to 'locale/hi')
-rw-r--r--locale/hi/LC_MESSAGES/messages.po113
1 files changed, 112 insertions, 1 deletions
diff --git a/locale/hi/LC_MESSAGES/messages.po b/locale/hi/LC_MESSAGES/messages.po
index a3cc1484..8e74c8a5 100644
--- a/locale/hi/LC_MESSAGES/messages.po
+++ b/locale/hi/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: 2021-03-09 18:35+0000\n" 11"PO-Revision-Date: 2021-03-09 18:35+0000\n"
12"Last-Translator: Jigisha Sharma <jigishas38@gmail.com>\n" 12"Last-Translator: Jigisha Sharma <jigishas38@gmail.com>\n"
13"Language-Team: Hindi <http://weblate.taler.net/projects/gnunet/website/hi/>\n" 13"Language-Team: Hindi <http://weblate.taler.net/projects/gnunet/website/hi/>\n"
@@ -2906,6 +2906,117 @@ msgstr ""
2906msgid "Videos related to GNUnet" 2906msgid "Videos related to GNUnet"
2907msgstr "" 2907msgstr ""
2908 2908
2909#: template/dev_pages/t3sserakt.html.j2:8
2910msgid "Developer page: t3sserakt"
2911msgstr ""
2912
2913#: template/dev_pages/t3sserakt.html.j2:23
2914msgid "Current Work"
2915msgstr ""
2916
2917#: template/dev_pages/t3sserakt.html.j2:25
2918msgid ""
2919"At the moment I am working on Transport Next Generation (TNG). The current "
2920"GNUnet TRANSPORT architecture with its pluggable transport mechanism (TCP, "
2921"UDP, HTTP(S) and other protocols) together with the ATS subsystem for "
2922"bandwidth allocation and choosing plugins has several issues with its "
2923"design. With the Layer-2-Overlay project we like to implement the design "
2924"goals of the future GNUnet TRANSPORT Next Generation (TNG) subsystem. For "
2925"details have a look on the <a href=\"https://www.gnunet.org/en/l2o/"
2926"\">project page</a>."
2927msgstr ""
2928
2929#: template/dev_pages/t3sserakt.html.j2:40
2930msgid "Future Work"
2931msgstr ""
2932
2933#: template/dev_pages/t3sserakt.html.j2:42
2934msgid ""
2935"The next project I will work on is named \"Probabilistic NAT Traversal\"."
2936msgstr ""
2937
2938#: template/dev_pages/t3sserakt.html.j2:47
2939msgid ""
2940"Today consumer devices are behind a NAT quite often, restricting internet "
2941"connectivity. There are several methods to reach peers being behind a NAT, "
2942"but there are as many reasons those existing methods might fail. We will "
2943"implement a new way of NAT traversal that we think of being independent from "
2944"the existing network configuration, and does not require a third party which "
2945"is not natted helping two peers to connect to each other. Two peers trying "
2946"to connect to each other will send out a burst of connection attempts to the "
2947"other peer on different ports. The sheer vast amount of connections attempts "
2948"from both side will lead to a high probability that two connection attempts "
2949"from both peers onto the same port will be at the same time leading to a "
2950"successful connection between those peers."
2951msgstr ""
2952
2953#: template/dev_pages/t3sserakt.html.j2:57
2954msgid ""
2955"There are two problems a NAT traversal method has to solve. First there "
2956"needs to be a method to know the global IP address of a peer A another peer "
2957"B wants to connect to. Second – because inbound connections from the outside "
2958"are blocked by the NAT firewall of peer A, peer A needs to be informed of a "
2959"connection attempt by peer B. The most common solution for both problems is "
2960"to have a third party C which is not behind a NAT. This third party C "
2961"obviously knows the global IP address of natted peers, after peer A is "
2962"trying to connect to C. Peer B tells C it likes to connect to peer A, and C "
2963"informs A about it. Using this method for a privacy preserving network like "
2964"GNUnet, this could facilitate eclipse attacks (isolating a peer) which then "
2965"can be used for deanonymization attacks and cencorship. Also any additional "
2966"infrastructure needed to provide some kind of functionality has to be "
2967"maintained by someone, becoming a target and/or point of failure. Therefore "
2968"this method is not suitable. More sophisticated methods like \"Autonomous "
2969"NAT Traversal (pwnat)\" using ICMP fake message, which do not need a third "
2970"party for the initiation of the connection, are not successful in all "
2971"circumstances, because this method depend on the behavior of the NAT "
2972"firewall."
2973msgstr ""
2974
2975#: template/dev_pages/t3sserakt.html.j2:71
2976msgid ""
2977"If two natted peers are using the method to start a burst of connection "
2978"attempts, this method still needs the global IP of the other peer and a "
2979"“start signal” to coordinate. In the NGI Assure project L2O we are "
2980"establishing a backchannel with neighbourhood routing over an ad- hoc "
2981"distance vector protocol to solve the problem of not directly connected "
2982"peers. The peers serving as hops to a distant peer which are a direct "
2983"neighbour of the start or end peer on that path do know the global IP "
2984"address of the start or end peer. If those two peers like to use the burst "
2985"method for hole punching the global IP address is known. Via the distance "
2986"vector protocol we are also able to communicate the \"start signal\". Also "
2987"in the L2O project we introduced a new test framework for GNUnet to test "
2988"network setups with peers having restricted connectivity. This test "
2989"framework will be used to create test setups suitable to test possible NAT "
2990"configurations. A challenge for this NAT traversal method will be how to "
2991"handle the burst in terms of network load, thus we need to experiment with "
2992"different frequencies and the amount of connection attempts."
2993msgstr ""
2994
2995#: template/dev_pages/t3sserakt.html.j2:93
2996msgid "Past Work"
2997msgstr ""
2998
2999#: template/dev_pages/t3sserakt.html.j2:95
3000msgid ""
3001"In the past I have tried to help making the vision of the <a href=\"http://"
3002"secushare.org\">secushare</a> project a reality. To achieve this the GNUnet "
3003"framework was the perfect match for a solution to fullfill the privacy "
3004"preserving part of that vision, and we could concentrate to build a tool for "
3005"social communication that deserves its name. While trying to use GNUnet, we "
3006"found and fixed bugs. For example there was one <a href=\"https://bugs."
3007"gnunet.org/view.php?id=5822\">bug</a> in CADET which prevented the re-"
3008"establishment of a connection after a communication partner suddenly stopped "
3009"communicating. From our perspective there is no alternativ to GNUnet, which "
3010"led us to first bring the parts of GNUnet needed by secushare to a state "
3011"that they can be used prouctively."
3012msgstr ""
3013
3014#: template/dev_pages/t3sserakt.html.j2:110
3015#, fuzzy
3016#| msgid "Continuous Integration"
3017msgid "Contact Information"
3018msgstr "लगातार एकीकरण"
3019
2909#: template/l2o/index.html.j2:6 template/l2o/mile1.html.j2:6 3020#: template/l2o/index.html.j2:6 template/l2o/mile1.html.j2:6
2910#: template/l2o/mile2.html.j2:6 template/l2o/mile3.html.j2:6 3021#: template/l2o/mile2.html.j2:6 template/l2o/mile3.html.j2:6
2911#: template/l2o/mile4.html.j2:6 template/l2o/testng.html.j2:6 3022#: template/l2o/mile4.html.j2:6 template/l2o/testng.html.j2:6