aboutsummaryrefslogtreecommitdiff
path: root/locale/zh_Hant/LC_MESSAGES/messages.po
diff options
context:
space:
mode:
Diffstat (limited to 'locale/zh_Hant/LC_MESSAGES/messages.po')
-rw-r--r--locale/zh_Hant/LC_MESSAGES/messages.po113
1 files changed, 112 insertions, 1 deletions
diff --git a/locale/zh_Hant/LC_MESSAGES/messages.po b/locale/zh_Hant/LC_MESSAGES/messages.po
index e47db942..a81b68f4 100644
--- a/locale/zh_Hant/LC_MESSAGES/messages.po
+++ b/locale/zh_Hant/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-08-24 08:59+0000\n" 11"PO-Revision-Date: 2021-08-24 08:59+0000\n"
12"Last-Translator: Ting-Yi Fu <futingyi0215@gmail.com>\n" 12"Last-Translator: Ting-Yi Fu <futingyi0215@gmail.com>\n"
13"Language-Team: Chinese (Traditional) <http://weblate.taler.net/projects/" 13"Language-Team: Chinese (Traditional) <http://weblate.taler.net/projects/"
@@ -3621,6 +3621,117 @@ msgstr "天哪,你們打破了我的網際網路"
3621msgid "Videos related to GNUnet" 3621msgid "Videos related to GNUnet"
3622msgstr "與 GNUnet 相關的影片" 3622msgstr "與 GNUnet 相關的影片"
3623 3623
3624#: template/dev_pages/t3sserakt.html.j2:8
3625msgid "Developer page: t3sserakt"
3626msgstr ""
3627
3628#: template/dev_pages/t3sserakt.html.j2:23
3629msgid "Current Work"
3630msgstr ""
3631
3632#: template/dev_pages/t3sserakt.html.j2:25
3633msgid ""
3634"At the moment I am working on Transport Next Generation (TNG). The current "
3635"GNUnet TRANSPORT architecture with its pluggable transport mechanism (TCP, "
3636"UDP, HTTP(S) and other protocols) together with the ATS subsystem for "
3637"bandwidth allocation and choosing plugins has several issues with its "
3638"design. With the Layer-2-Overlay project we like to implement the design "
3639"goals of the future GNUnet TRANSPORT Next Generation (TNG) subsystem. For "
3640"details have a look on the <a href=\"https://www.gnunet.org/en/l2o/"
3641"\">project page</a>."
3642msgstr ""
3643
3644#: template/dev_pages/t3sserakt.html.j2:40
3645msgid "Future Work"
3646msgstr ""
3647
3648#: template/dev_pages/t3sserakt.html.j2:42
3649msgid ""
3650"The next project I will work on is named \"Probabilistic NAT Traversal\"."
3651msgstr ""
3652
3653#: template/dev_pages/t3sserakt.html.j2:47
3654msgid ""
3655"Today consumer devices are behind a NAT quite often, restricting internet "
3656"connectivity. There are several methods to reach peers being behind a NAT, "
3657"but there are as many reasons those existing methods might fail. We will "
3658"implement a new way of NAT traversal that we think of being independent from "
3659"the existing network configuration, and does not require a third party which "
3660"is not natted helping two peers to connect to each other. Two peers trying "
3661"to connect to each other will send out a burst of connection attempts to the "
3662"other peer on different ports. The sheer vast amount of connections attempts "
3663"from both side will lead to a high probability that two connection attempts "
3664"from both peers onto the same port will be at the same time leading to a "
3665"successful connection between those peers."
3666msgstr ""
3667
3668#: template/dev_pages/t3sserakt.html.j2:57
3669msgid ""
3670"There are two problems a NAT traversal method has to solve. First there "
3671"needs to be a method to know the global IP address of a peer A another peer "
3672"B wants to connect to. Second – because inbound connections from the outside "
3673"are blocked by the NAT firewall of peer A, peer A needs to be informed of a "
3674"connection attempt by peer B. The most common solution for both problems is "
3675"to have a third party C which is not behind a NAT. This third party C "
3676"obviously knows the global IP address of natted peers, after peer A is "
3677"trying to connect to C. Peer B tells C it likes to connect to peer A, and C "
3678"informs A about it. Using this method for a privacy preserving network like "
3679"GNUnet, this could facilitate eclipse attacks (isolating a peer) which then "
3680"can be used for deanonymization attacks and cencorship. Also any additional "
3681"infrastructure needed to provide some kind of functionality has to be "
3682"maintained by someone, becoming a target and/or point of failure. Therefore "
3683"this method is not suitable. More sophisticated methods like \"Autonomous "
3684"NAT Traversal (pwnat)\" using ICMP fake message, which do not need a third "
3685"party for the initiation of the connection, are not successful in all "
3686"circumstances, because this method depend on the behavior of the NAT "
3687"firewall."
3688msgstr ""
3689
3690#: template/dev_pages/t3sserakt.html.j2:71
3691msgid ""
3692"If two natted peers are using the method to start a burst of connection "
3693"attempts, this method still needs the global IP of the other peer and a "
3694"“start signal” to coordinate. In the NGI Assure project L2O we are "
3695"establishing a backchannel with neighbourhood routing over an ad- hoc "
3696"distance vector protocol to solve the problem of not directly connected "
3697"peers. The peers serving as hops to a distant peer which are a direct "
3698"neighbour of the start or end peer on that path do know the global IP "
3699"address of the start or end peer. If those two peers like to use the burst "
3700"method for hole punching the global IP address is known. Via the distance "
3701"vector protocol we are also able to communicate the \"start signal\". Also "
3702"in the L2O project we introduced a new test framework for GNUnet to test "
3703"network setups with peers having restricted connectivity. This test "
3704"framework will be used to create test setups suitable to test possible NAT "
3705"configurations. A challenge for this NAT traversal method will be how to "
3706"handle the burst in terms of network load, thus we need to experiment with "
3707"different frequencies and the amount of connection attempts."
3708msgstr ""
3709
3710#: template/dev_pages/t3sserakt.html.j2:93
3711msgid "Past Work"
3712msgstr ""
3713
3714#: template/dev_pages/t3sserakt.html.j2:95
3715msgid ""
3716"In the past I have tried to help making the vision of the <a href=\"http://"
3717"secushare.org\">secushare</a> project a reality. To achieve this the GNUnet "
3718"framework was the perfect match for a solution to fullfill the privacy "
3719"preserving part of that vision, and we could concentrate to build a tool for "
3720"social communication that deserves its name. While trying to use GNUnet, we "
3721"found and fixed bugs. For example there was one <a href=\"https://bugs."
3722"gnunet.org/view.php?id=5822\">bug</a> in CADET which prevented the re-"
3723"establishment of a connection after a communication partner suddenly stopped "
3724"communicating. From our perspective there is no alternativ to GNUnet, which "
3725"led us to first bring the parts of GNUnet needed by secushare to a state "
3726"that they can be used prouctively."
3727msgstr ""
3728
3729#: template/dev_pages/t3sserakt.html.j2:110
3730#, fuzzy
3731#| msgid "Contact information"
3732msgid "Contact Information"
3733msgstr "聯絡資訊"
3734
3624#: template/l2o/index.html.j2:6 template/l2o/mile1.html.j2:6 3735#: template/l2o/index.html.j2:6 template/l2o/mile1.html.j2:6
3625#: template/l2o/mile2.html.j2:6 template/l2o/mile3.html.j2:6 3736#: template/l2o/mile2.html.j2:6 template/l2o/mile3.html.j2:6
3626#: template/l2o/mile4.html.j2:6 template/l2o/testng.html.j2:6 3737#: template/l2o/mile4.html.j2:6 template/l2o/testng.html.j2:6