aboutsummaryrefslogtreecommitdiff
path: root/locale/it/LC_MESSAGES/messages.po
diff options
context:
space:
mode:
Diffstat (limited to 'locale/it/LC_MESSAGES/messages.po')
-rw-r--r--locale/it/LC_MESSAGES/messages.po113
1 files changed, 112 insertions, 1 deletions
diff --git a/locale/it/LC_MESSAGES/messages.po b/locale/it/LC_MESSAGES/messages.po
index 7e9f75a8..901c1f7c 100644
--- a/locale/it/LC_MESSAGES/messages.po
+++ b/locale/it/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: 2022-03-27 11:53+0000\n" 11"PO-Revision-Date: 2022-03-27 11:53+0000\n"
12"Last-Translator: Roberto Pellegrino <speekix@gmail.com>\n" 12"Last-Translator: Roberto Pellegrino <speekix@gmail.com>\n"
13"Language-Team: Italian <http://weblate.taler.net/projects/gnunet/website/it/" 13"Language-Team: Italian <http://weblate.taler.net/projects/gnunet/website/it/"
@@ -3772,6 +3772,117 @@ msgstr ""
3772msgid "Videos related to GNUnet" 3772msgid "Videos related to GNUnet"
3773msgstr "" 3773msgstr ""
3774 3774
3775#: template/dev_pages/t3sserakt.html.j2:8
3776msgid "Developer page: t3sserakt"
3777msgstr ""
3778
3779#: template/dev_pages/t3sserakt.html.j2:23
3780msgid "Current Work"
3781msgstr ""
3782
3783#: template/dev_pages/t3sserakt.html.j2:25
3784msgid ""
3785"At the moment I am working on Transport Next Generation (TNG). The current "
3786"GNUnet TRANSPORT architecture with its pluggable transport mechanism (TCP, "
3787"UDP, HTTP(S) and other protocols) together with the ATS subsystem for "
3788"bandwidth allocation and choosing plugins has several issues with its "
3789"design. With the Layer-2-Overlay project we like to implement the design "
3790"goals of the future GNUnet TRANSPORT Next Generation (TNG) subsystem. For "
3791"details have a look on the <a href=\"https://www.gnunet.org/en/l2o/"
3792"\">project page</a>."
3793msgstr ""
3794
3795#: template/dev_pages/t3sserakt.html.j2:40
3796msgid "Future Work"
3797msgstr ""
3798
3799#: template/dev_pages/t3sserakt.html.j2:42
3800msgid ""
3801"The next project I will work on is named \"Probabilistic NAT Traversal\"."
3802msgstr ""
3803
3804#: template/dev_pages/t3sserakt.html.j2:47
3805msgid ""
3806"Today consumer devices are behind a NAT quite often, restricting internet "
3807"connectivity. There are several methods to reach peers being behind a NAT, "
3808"but there are as many reasons those existing methods might fail. We will "
3809"implement a new way of NAT traversal that we think of being independent from "
3810"the existing network configuration, and does not require a third party which "
3811"is not natted helping two peers to connect to each other. Two peers trying "
3812"to connect to each other will send out a burst of connection attempts to the "
3813"other peer on different ports. The sheer vast amount of connections attempts "
3814"from both side will lead to a high probability that two connection attempts "
3815"from both peers onto the same port will be at the same time leading to a "
3816"successful connection between those peers."
3817msgstr ""
3818
3819#: template/dev_pages/t3sserakt.html.j2:57
3820msgid ""
3821"There are two problems a NAT traversal method has to solve. First there "
3822"needs to be a method to know the global IP address of a peer A another peer "
3823"B wants to connect to. Second – because inbound connections from the outside "
3824"are blocked by the NAT firewall of peer A, peer A needs to be informed of a "
3825"connection attempt by peer B. The most common solution for both problems is "
3826"to have a third party C which is not behind a NAT. This third party C "
3827"obviously knows the global IP address of natted peers, after peer A is "
3828"trying to connect to C. Peer B tells C it likes to connect to peer A, and C "
3829"informs A about it. Using this method for a privacy preserving network like "
3830"GNUnet, this could facilitate eclipse attacks (isolating a peer) which then "
3831"can be used for deanonymization attacks and cencorship. Also any additional "
3832"infrastructure needed to provide some kind of functionality has to be "
3833"maintained by someone, becoming a target and/or point of failure. Therefore "
3834"this method is not suitable. More sophisticated methods like \"Autonomous "
3835"NAT Traversal (pwnat)\" using ICMP fake message, which do not need a third "
3836"party for the initiation of the connection, are not successful in all "
3837"circumstances, because this method depend on the behavior of the NAT "
3838"firewall."
3839msgstr ""
3840
3841#: template/dev_pages/t3sserakt.html.j2:71
3842msgid ""
3843"If two natted peers are using the method to start a burst of connection "
3844"attempts, this method still needs the global IP of the other peer and a "
3845"“start signal” to coordinate. In the NGI Assure project L2O we are "
3846"establishing a backchannel with neighbourhood routing over an ad- hoc "
3847"distance vector protocol to solve the problem of not directly connected "
3848"peers. The peers serving as hops to a distant peer which are a direct "
3849"neighbour of the start or end peer on that path do know the global IP "
3850"address of the start or end peer. If those two peers like to use the burst "
3851"method for hole punching the global IP address is known. Via the distance "
3852"vector protocol we are also able to communicate the \"start signal\". Also "
3853"in the L2O project we introduced a new test framework for GNUnet to test "
3854"network setups with peers having restricted connectivity. This test "
3855"framework will be used to create test setups suitable to test possible NAT "
3856"configurations. A challenge for this NAT traversal method will be how to "
3857"handle the burst in terms of network load, thus we need to experiment with "
3858"different frequencies and the amount of connection attempts."
3859msgstr ""
3860
3861#: template/dev_pages/t3sserakt.html.j2:93
3862msgid "Past Work"
3863msgstr ""
3864
3865#: template/dev_pages/t3sserakt.html.j2:95
3866msgid ""
3867"In the past I have tried to help making the vision of the <a href=\"http://"
3868"secushare.org\">secushare</a> project a reality. To achieve this the GNUnet "
3869"framework was the perfect match for a solution to fullfill the privacy "
3870"preserving part of that vision, and we could concentrate to build a tool for "
3871"social communication that deserves its name. While trying to use GNUnet, we "
3872"found and fixed bugs. For example there was one <a href=\"https://bugs."
3873"gnunet.org/view.php?id=5822\">bug</a> in CADET which prevented the re-"
3874"establishment of a connection after a communication partner suddenly stopped "
3875"communicating. From our perspective there is no alternativ to GNUnet, which "
3876"led us to first bring the parts of GNUnet needed by secushare to a state "
3877"that they can be used prouctively."
3878msgstr ""
3879
3880#: template/dev_pages/t3sserakt.html.j2:110
3881#, fuzzy
3882#| msgid "Contact information"
3883msgid "Contact Information"
3884msgstr "Contatti"
3885
3775#: template/l2o/index.html.j2:6 template/l2o/mile1.html.j2:6 3886#: template/l2o/index.html.j2:6 template/l2o/mile1.html.j2:6
3776#: template/l2o/mile2.html.j2:6 template/l2o/mile3.html.j2:6 3887#: template/l2o/mile2.html.j2:6 template/l2o/mile3.html.j2:6
3777#: template/l2o/mile4.html.j2:6 template/l2o/testng.html.j2:6 3888#: template/l2o/mile4.html.j2:6 template/l2o/testng.html.j2:6