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.po577
1 files changed, 548 insertions, 29 deletions
diff --git a/locale/it/LC_MESSAGES/messages.po b/locale/it/LC_MESSAGES/messages.po
index dc4f31e9..c22c09b4 100644
--- a/locale/it/LC_MESSAGES/messages.po
+++ b/locale/it/LC_MESSAGES/messages.po
@@ -7,11 +7,11 @@ 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: 2021-03-03 21:41+0100\n" 10"POT-Creation-Date: 2021-03-12 12:43+0100\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: Sabino Miani <sbn.miani@gmail.com>\n" 12"Last-Translator: Sabino Miani <sbn.miani@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/"
14"\n" 14">\n"
15"Language: it\n" 15"Language: it\n"
16"MIME-Version: 1.0\n" 16"MIME-Version: 1.0\n"
17"Content-Type: text/plain; charset=UTF-8\n" 17"Content-Type: text/plain; charset=UTF-8\n"
@@ -66,6 +66,7 @@ msgid "About"
66msgstr "Per quanto riguarda" 66msgstr "Per quanto riguarda"
67 67
68#: common/navigation.j2.inc:39 news/index.html.j2:8 68#: common/navigation.j2.inc:39 news/index.html.j2:8
69#: news/oldnews-2011.html.j2:13 news/oldnews-2013.html.j2:13
69#: news/oldnews-2018.html.j2:13 news/oldnews-2019.html.j2:13 70#: news/oldnews-2018.html.j2:13 news/oldnews-2019.html.j2:13
70msgid "News" 71msgid "News"
71msgstr "Notizia" 72msgstr "Notizia"
@@ -158,19 +159,22 @@ msgstr "REST API"
158msgid "FAQ" 159msgid "FAQ"
159msgstr "Domande Frequenti" 160msgstr "Domande Frequenti"
160 161
161#: news/index.html.j2:11 news/oldnews-2018.html.j2:16 162#: news/index.html.j2:11 news/oldnews-2011.html.j2:16
163#: news/oldnews-2013.html.j2:16 news/oldnews-2018.html.j2:16
162#: news/oldnews-2019.html.j2:16 164#: news/oldnews-2019.html.j2:16
163msgid "News posts about changes related to GNUnet such as releases and events" 165msgid "News posts about changes related to GNUnet such as releases and events"
164msgstr "" 166msgstr ""
165"Annunci di notizie legate ai cambiamenti di GNUnet come comunicati stampa ed " 167"Annunci di notizie legate ai cambiamenti di GNUnet come comunicati stampa ed "
166"eventi" 168"eventi"
167 169
168#: news/index.html.j2:16 news/oldnews-2018.html.j2:21 170#: news/index.html.j2:16 news/oldnews-2011.html.j2:21
171#: news/oldnews-2013.html.j2:21 news/oldnews-2018.html.j2:21
169#: news/oldnews-2019.html.j2:21 172#: news/oldnews-2019.html.j2:21
170msgid "subscribe to our RSS feed" 173msgid "subscribe to our RSS feed"
171msgstr "Fai la sottoscrizione alla nostra bacheca RSS" 174msgstr "Fai la sottoscrizione alla nostra bacheca RSS"
172 175
173#: news/index.html.j2:36 news/oldnews-2018.html.j2:40 176#: news/index.html.j2:36 news/oldnews-2011.html.j2:40
177#: news/oldnews-2013.html.j2:40 news/oldnews-2018.html.j2:40
174#: news/oldnews-2019.html.j2:40 178#: news/oldnews-2019.html.j2:40
175msgid "read more" 179msgid "read more"
176msgstr "Per saperne di più" 180msgstr "Per saperne di più"
@@ -227,8 +231,8 @@ msgstr ""
227"ostili presenti nella rete. \n" 231"ostili presenti nella rete. \n"
228"Inoltre, l'internet dei giorni nostri si è evoluto al punto che, come " 232"Inoltre, l'internet dei giorni nostri si è evoluto al punto che, come "
229"sottolineato da Matthew Green, \n" 233"sottolineato da Matthew Green, \n"
230"<a href=\"https://blog.cryptographyengineering.com/2015/08/16/" 234"<a href=\"https://blog.cryptographyengineering.com/2015/08/16/the-network-is-"
231"the-network-is-hostile/\">\"la rete è ostile\"</a>." 235"hostile/\">\"la rete è ostile\"</a>."
232 236
233#: template/about.html.j2:41 237#: template/about.html.j2:41
234msgid "" 238msgid ""
@@ -294,7 +298,8 @@ msgstr ""
294 298
295#: template/about.html.j2:64 299#: template/about.html.j2:64
296msgid "GNUnet must be open and permit new peers to join." 300msgid "GNUnet must be open and permit new peers to join."
297msgstr "GNUnet deve essere aperto e lasciare che nuovi colleghi possano unirsi." 301msgstr ""
302"GNUnet deve essere aperto e lasciare che nuovi colleghi possano unirsi."
298 303
299#: template/about.html.j2:65 304#: template/about.html.j2:65
300msgid "GNUnet must support a diverse range of applications and devices." 305msgid "GNUnet must support a diverse range of applications and devices."
@@ -366,9 +371,9 @@ msgstr ""
366"Esistono molte più risorse che permettono di conoscere GNUnet oltre che il " 371"Esistono molte più risorse che permettono di conoscere GNUnet oltre che il "
367"<a href=\"https://docs.gnunet.org/handbook/gnunet.html\">manuale</a>, " 372"<a href=\"https://docs.gnunet.org/handbook/gnunet.html\">manuale</a>, "
368"abbiamo la<a href=\"https://bib.gnunet.org/\">bibliografia</a> con fogli che " 373"abbiamo la<a href=\"https://bib.gnunet.org/\">bibliografia</a> con fogli che "
369"coprono i vari strati, molti<a href=\"https://gnunet.org/en/video.html\"" 374"coprono i vari strati, molti<a href=\"https://gnunet.org/en/video.html"
370">video</a>o un breve <a href=\"https://gnunet.org/en/glossary.html\"" 375"\">video</a>o un breve <a href=\"https://gnunet.org/en/glossary.html"
371">glossario</a>." 376"\">glossario</a>."
372 377
373#: template/about.html.j2:95 378#: template/about.html.j2:95
374msgid "" 379msgid ""
@@ -379,8 +384,8 @@ msgid ""
379msgstr "" 384msgstr ""
380"Sei sempre il benvenuto <a href=\"engage.html\">quando si tratta di " 385"Sei sempre il benvenuto <a href=\"engage.html\">quando si tratta di "
381"affrontare conversazioni</a>, <a href=\"install.html\">installare GNUnet</" 386"affrontare conversazioni</a>, <a href=\"install.html\">installare GNUnet</"
382"a>, <a href=\"use.html\">utilizzarlo</a> e <a href=\"engage.html\"" 387"a>, <a href=\"use.html\">utilizzarlo</a> e <a href=\"engage.html"
383">contribuire ed impegnarsi</a> in svariati modi." 388"\">contribuire ed impegnarsi</a> in svariati modi."
384 389
385#: template/about.html.j2:100 390#: template/about.html.j2:100
386msgid "" 391msgid ""
@@ -905,11 +910,123 @@ msgid ""
905"<dd>DE67830654080004822650 (BIC/SWIFT: GENODEF1SLR)</dd> </dl>" 910"<dd>DE67830654080004822650 (BIC/SWIFT: GENODEF1SLR)</dd> </dl>"
906msgstr "" 911msgstr ""
907 912
908#: template/faq.html.j2:12 913#: template/faq.html.j2:12 template/faq.html.j2:21
914msgid "General"
915msgstr ""
916
917#: template/faq.html.j2:13 template/faq.html.j2:146 template/gns.html.j2:37
918msgid "Features"
919msgstr ""
920
921#: template/faq.html.j2:15 template/faq.html.j2:539
922msgid "Error messages"
923msgstr ""
924
925#: template/faq.html.j2:24
926msgid "What do I do if my question is not answered here?"
927msgstr ""
928
929#: template/faq.html.j2:26
930msgid ""
931"A: There are many other sources of information. You can read additional "
932"documentation or ask the question on the help-gnunet@gnu.org mailing list or "
933"the #gnunet IRC on irc.freenode.net."
934msgstr ""
935
936#: template/faq.html.j2:34
937msgid "When are you going to release the next version?"
938msgstr ""
939
940#: template/faq.html.j2:36
941msgid ""
942"A: The general answer is, when it is ready. A better answer may be: earlier "
943"if you contribute (test, debug, code, document). Every release will be "
944"anounced on the info-gnunet@gnu.org mailing list and on <a href=\"https://"
945"planet.gnu.org\">planet GNU</a>. You can subscribe to the mailing list or "
946"the RSS feed of this site to automatically receive a notification."
947msgstr ""
948
949#: template/faq.html.j2:47
950msgid "Is the code free?"
951msgstr ""
952
953#: template/faq.html.j2:49
954msgid ""
955"A: GNUnet is free software, available under the <a href=\"https://www.gnu."
956"org/licenses/agpl-3.0.en.html\">GNU Affero Public License (AGPL)</a>."
957msgstr ""
958
959#: template/faq.html.j2:56
960msgid "Are there any known bugs?"
961msgstr ""
962
963#: template/faq.html.j2:58
964msgid ""
965"A: We track the list of currently known bugs in the <a href=\"https://bugs."
966"gnunet.org/\">Mantis system</a>. Some bugs are occasionally reported "
967"directly to developers or the developer mailing list. This is discouraged "
968"since developers often do not have the time to feed these bugs back into the "
969"Mantis database. Please report bugs directly to the bug tracking system. If "
970"you believe a bug is sensitive, you can set its view status to private (this "
971"should be the exception)."
972msgstr ""
973
974#: template/faq.html.j2:71
975msgid "Is there a graphical user interface?"
976msgstr ""
977
978#: template/faq.html.j2:73
979msgid ""
980"A: gnunet-gtk is a separate download. The package contains various GTK+ "
981"based graphical interfaces, including a graphical tool for configuration."
982msgstr ""
983
984#: template/faq.html.j2:81
985msgid "Why does gnunet-service-nse create a high CPU load?"
986msgstr ""
987
988#: template/faq.html.j2:83
989msgid ""
990"A: The gnunet-service-nse process will initially compute a so-called &quot;"
991"proof-of-work&quot; which is used to convince the network that your peer is "
992"real (or, rather, make it expensive for an adversary to mount a Sybil attack "
993"on the network size estimator). The calculation is expected to take a few "
994"days, depending on how fast your CPU is. If the CPU load is creating a "
995"problem for you, you can set the value &quot;WORKDELAY&quot; in the &quot;"
996"nse&quot; section of your configuration file to a higher value. The default "
997"is &quot;5 ms&quot;."
998msgstr ""
999
1000#: template/faq.html.j2:97
1001msgid "How does GNUnet compare to Tor?"
1002msgstr ""
1003
1004#: template/faq.html.j2:99
1005msgid ""
1006"A: Tor focuses on anonymous communication and censorship-resistance for TCP "
1007"connections and, with the Tor Browser Bundle, for the Web in particular. "
1008"GNUnet does not really have one focus; our theme is secure decentralized "
1009"networking, but that is too broad to be called a focus."
1010msgstr ""
1011
1012#: template/faq.html.j2:109
1013msgid "How does GNUnet compare to I2P?"
1014msgstr ""
1015
1016#: template/faq.html.j2:111
1017msgid ""
1018"A: Both GNUnet and I2P want to build a better, more secure, more "
1019"decentralized Internet. However, on the technical side, there are almost no "
1020"overlaps. <br><br> I2P is written in Java, and has (asymmetric) tunnels "
1021"using onion (or garlic) routing as the basis for various (anonymized) "
1022"applications. I2P is largely used via a Web frontend."
1023msgstr ""
1024
1025#: template/faq.html.j2:122
909msgid "Is GNUnet ready for use on production systems?" 1026msgid "Is GNUnet ready for use on production systems?"
910msgstr "" 1027msgstr ""
911 1028
912#: template/faq.html.j2:14 1029#: template/faq.html.j2:124
913msgid "" 1030msgid ""
914"A: GNUnet is still undergoing major development. It is largely not yet ready " 1031"A: GNUnet is still undergoing major development. It is largely not yet ready "
915"for usage beyond developers. Your mileage will vary depending on the " 1032"for usage beyond developers. Your mileage will vary depending on the "
@@ -918,24 +1035,406 @@ msgid ""
918"rewriting it (Project &quot;Transport Next Generation [TNG]&quot;)" 1035"rewriting it (Project &quot;Transport Next Generation [TNG]&quot;)"
919msgstr "" 1036msgstr ""
920 1037
921#: template/faq.html.j2:24 1038#: template/faq.html.j2:134
922msgid "Is GNUnet build using distributed ledger technologies?" 1039msgid "Is GNUnet build using distributed ledger technologies?"
923msgstr "" 1040msgstr ""
924 1041
925#: template/faq.html.j2:26 1042#: template/faq.html.j2:136
926msgid "" 1043msgid ""
927"A: No. GNUnet is a new network protocol stack for building secure, " 1044"A: No. GNUnet is a new network protocol stack for building secure, "
928"distributed, and privacy-preserving applications. While a ledger could be " 1045"distributed, and privacy-preserving applications. While a ledger could be "
929"built using GNUnet, we currently have no plans in doing so." 1046"built using GNUnet, we currently have no plans in doing so."
930msgstr "" 1047msgstr ""
931 1048
932#: template/faq.html.j2:35 1049#: template/faq.html.j2:148
1050#, fuzzy
1051#| msgid "What is GNUnet?"
1052msgid "What can I do with GNUnet?"
1053msgstr "Cos'è GNUnet?"
1054
1055#: template/faq.html.j2:150
1056msgid ""
1057"A: GNUnet is a peer-to-peer framework, by which we mostly mean that it can "
1058"do more than just one thing. Naturally, the implementation and documentation "
1059"of some of the features that exist are more advanced than others."
1060msgstr ""
1061
1062#: template/faq.html.j2:157
1063msgid ""
1064"For users, GNUnet offers anonymous and non-anonymous file-sharing, a fully "
1065"decentralized and censorship-resistant replacement for DNS and a mechanism "
1066"for IPv4-IPv6 protocol translation and tunneling (NAT-PT with DNS-ALG)."
1067msgstr ""
1068
1069#: template/faq.html.j2:171
1070msgid "Who runs the GNS root zone?"
1071msgstr ""
1072
1073#: template/faq.html.j2:173
1074msgid ""
1075"A: Short answer: you. The long answer is the GNUnet will ship with a default "
1076"configuration of top-level domains. The governance of this default "
1077"configuration is not yet established. In any case, the user will be able to "
1078"modify this configuration at will. We expect normal users to have no need to "
1079"edit their own GNS zone(s) unless they host services themselves."
1080msgstr ""
1081
1082#: template/faq.html.j2:184
1083msgid "Where is the per-user GNS database kept?"
1084msgstr ""
1085
1086#: template/faq.html.j2:186
1087msgid ""
1088"A: The short answer is that the database is kept at the user's GNUnet peer. "
1089"Now, a user may run multiple GNUnet peers, in which case the database could "
1090"be kept at each peer (however, we don't have code for convenient "
1091"replication). Similarly, multiple GNUnet peers can share one instance of the "
1092"database --- the &quot;gnunet-service-namestore&quot; can be accessed from "
1093"remote (via TCP). The actual data can be stored in a Postgres database, for "
1094"which various replication options are again applicable. Ultimately, there "
1095"are many options for how users can store (and secure) their GNS database."
1096msgstr ""
1097
1098#: template/faq.html.j2:201
1099msgid "What is the expected average size of a GNS namestore database?"
1100msgstr ""
1101
1102#: template/faq.html.j2:203
1103msgid ""
1104"A: Pretty small. Based on our user study where we looked at browser "
1105"histories and the number of domains visited, we expect that GNS databases "
1106"will only grow to a few tens of thousands of entries, small enough to fit "
1107"even on mobile devices."
1108msgstr ""
1109
1110#: template/faq.html.j2:213
1111msgid "Is GNS resistant to the attacks on DNS used by the US?"
1112msgstr ""
1113
1114#: template/faq.html.j2:215
1115msgid ""
1116"A: We believe so, as there is no entity that any government could force to "
1117"change the mapping for a name except for each individual user (and then the "
1118"changes would only apply to the names that this user is the authority for). "
1119"So if everyone used GNS, the only practical attack of a government would be "
1120"to force the operator of a server to change the GNS records for his server "
1121"to point elsewhere. However, if the owner of the private key for a zone is "
1122"unavailable for enforcement, the respective zone cannot be changed and any "
1123"other zone delegating to this zone will achieve proper resolution."
1124msgstr ""
1125
1126#: template/faq.html.j2:229
1127msgid "What is the difference between GNS and CoDoNS?"
1128msgstr ""
1129
1130#: template/faq.html.j2:231
1131msgid ""
1132"A: CoDoNS decentralizes the DNS database (using a DHT) but preserves the "
1133"authority structure of DNS. With CoDoNS, IANA/ICANN are still in charge, and "
1134"there are still registrars that determine who owns a name. <br><br> With "
1135"GNS, we decentralize the database and also decentralize the responsibility "
1136"for naming: each user runs his own personal root zone and is thus in "
1137"complete control of the names he uses. GNS also has many additional features "
1138"(to keep names short and enable migration) which don't even make sense in "
1139"the context of CoDoNS."
1140msgstr ""
1141
1142#: template/faq.html.j2:247
1143msgid "What is the difference between GNS and SocialDNS?"
1144msgstr ""
1145
1146#: template/faq.html.j2:249
1147msgid ""
1148"A: Like GNS, SocialDNS allows each user to create DNS mappings. However, "
1149"with SocialDNS the mappings are shared through the social network and "
1150"subjected to ranking. As the social relationships evolve, names can thus "
1151"change in surprising ways. <br><br> With GNS, names are primarily shared via "
1152"delegation, and thus mappings will only change if the user responsible for "
1153"the name (the authority) manually changes the record."
1154msgstr ""
1155
1156#: template/faq.html.j2:263
1157msgid "What is the difference between GNS and ODDNS?"
1158msgstr ""
1159
1160#: template/faq.html.j2:265
1161msgid ""
1162"A: ODDNS is primarily designed to bypass the DNS root zone and the TLD "
1163"registries (such as those for \".com\" and \".org\"). Instead of using "
1164"those, each user is expected to maintain a database of (second-level) "
1165"domains (like \"gnu.org\") and the IP addresses of the respective name "
1166"servers. Resolution will fail if the target name servers change IPs."
1167msgstr ""
1168
1169#: template/faq.html.j2:276
1170msgid "What is the difference between GNS and Namecoin?"
1171msgstr ""
1172
1173#: template/faq.html.j2:283
1174msgid "What is the difference between GNS and Handshake?"
1175msgstr ""
1176
1177#: template/faq.html.j2:289
1178msgid "What is the difference between GNS and ENS?"
1179msgstr ""
1180
1181#: template/faq.html.j2:295
1182msgid "What is the difference between GNS and TrickleDNS?"
1183msgstr ""
1184
1185#: template/faq.html.j2:297
1186msgid ""
1187"A: TrickleDNS pushes (&quot;critical&quot;) DNS records between DNS "
1188"resolvers of participating domains to provide &quot;better availability, "
1189"lower query resolution times, and faster update propagation&quot;. Thus "
1190"TrickleDNS is focused on defeating attacks on the availability (and "
1191"performance) of record propagation in DNS, for example via DDoS attacks on "
1192"DNS root servers. TrickleDNS is thus concerned with how to ensure "
1193"distribution of authoritative records, and authority remains derived from "
1194"the DNS hierarchy."
1195msgstr ""
1196
1197#: template/faq.html.j2:310
1198msgid ""
1199"Does GNS require real-world introduction (secure PKEY exchange) in the style "
1200"of the PGP web of trust?"
1201msgstr ""
1202
1203#: template/faq.html.j2:312
1204msgid ""
1205"A: For security, it is well known that an initial trust path between the two "
1206"parties must exist. However, for applications where this is not required, "
1207"weaker mechanisms can be used. For example, we have implemented a first-come-"
1208"first-served (FCFS) authority which allows arbitrary users to register "
1209"arbitrary names. The key of this authority is included with every GNUnet "
1210"installation. Thus, any name registered with FCFS is in fact global and "
1211"requires no further introduction. However, the security of these names "
1212"depends entirely on the trustworthiness of the FCFS authority. The authority "
1213"can be queried under the &quot;.ping&quot; TLD."
1214msgstr ""
1215
1216#: template/faq.html.j2:327
1217msgid ""
1218"How can a legitimate domain owner tell other people to not use his name in "
1219"GNS?"
1220msgstr ""
1221
1222#: template/faq.html.j2:329
1223msgid ""
1224"A: Names have no owners in GNS, so there cannot be a &quot;legitimate&quot; "
1225"domain owner. Any user can claim any name (as his preferred name or &quot;"
1226"pseudonym&quot;) in his NICK record. Similarly, all other users can choose "
1227"to ignore this preference and use a name of their choice (or even assign no "
1228"name) for this user."
1229msgstr ""
1230
1231#: template/faq.html.j2:340
1232msgid ""
1233"Did you consider the privacy implications of making your personal GNS zone "
1234"visible?"
1235msgstr ""
1236
1237#: template/faq.html.j2:342
1238msgid ""
1239"A: Each record in GNS has a flag &quot;private&quot;. Records are shared "
1240"with other users (via DHT or zone transfers) only if this flag is not set. "
1241"Thus, users have full control over what information about their zones is "
1242"made public."
1243msgstr ""
1244
1245#: template/faq.html.j2:352
1246msgid "Are \"Legacy Host\" (LEHO) records not going to be obsolete with IPv6?"
1247msgstr ""
1248
1249#: template/faq.html.j2:354
1250msgid ""
1251"A: The question presumes that (a) virtual hosting is only necessary because "
1252"of IPv4 address scarcity, and (b) that LEHOs are only useful in the context "
1253"of virtual hosting. However, LEHOs are also useful to help with X.509 "
1254"certificate validation (as they specify for which legacy hostname the "
1255"certificate should be valid). Also, even with IPv6 fully deployed and &quot;"
1256"infinite&quot; IP addresses being available, we're not sure that virtual "
1257"hosting would disappear. Finally, we don't want to have to wait for IPv6 to "
1258"become commonplace, GNS should work with today's networks."
1259msgstr ""
1260
1261#: template/faq.html.j2:368
1262msgid ""
1263"Why does GNS not use a trust metric or consensus to determine globally "
1264"unique names?"
1265msgstr ""
1266
1267#: template/faq.html.j2:370
1268msgid ""
1269"A: Trust metrics have the fundamental problem that they have thresholds. As "
1270"trust relationships evolve, mappings would change their meaning as they "
1271"cross each others thresholds. We decided that the resulting unpredictability "
1272"of the resolution process was not acceptable. Furthermore, trust and "
1273"consensus might be easy to manipulate by adversaries."
1274msgstr ""
1275
1276#: template/faq.html.j2:381
1277msgid "How do you handle compromised zone keys in GNS?"
1278msgstr ""
1279
1280#: template/faq.html.j2:383
1281msgid ""
1282"A: The owner of a private key can create a revocation message. This one can "
1283"then be flooded throughout the overlay network, creating a copy at all "
1284"peers. Before using a public key, peers check if that key has been revoked. "
1285"All names that involve delegation via a revoked zone will then fail to "
1286"resolve. Peers always automatically check for the existence of a revocation "
1287"message when resolving names."
1288msgstr ""
1289
1290#: template/faq.html.j2:395
1291msgid "Could the signing algorithm of GNS be upgraded in the future?"
1292msgstr ""
1293
1294#: template/faq.html.j2:397
1295msgid ""
1296"A: Yes. In our efforts to standardize GNS, we have already modified the "
1297"protocol to support alternative delegation records. <br> <br> Naturally, "
1298"deployed GNS implementations would have to be updated to support the new "
1299"signature scheme. The new scheme can then be run in parallel with the "
1300"existing system by using a new record type to indicate the use of a "
1301"different cipher system."
1302msgstr ""
1303
1304#: template/faq.html.j2:411
1305msgid ""
1306"How can a GNS zone maintain several name servers, e.g. for load balancing?"
1307msgstr ""
1308
1309#: template/faq.html.j2:413
1310msgid ""
1311"A: We don't expect this to be necessary, as GNS records are stored (and "
1312"replicated) in the R5N DHT. Thus the authority will typically not be "
1313"contacted whenever clients perform a lookup. Even if the authority goes "
1314"(temporarily) off-line, the DHT will cache the records for some time. "
1315"However, should having multiple servers for a zone be considered truly "
1316"necessary, the owner of the zone can simply run multiple peers (and share "
1317"the zone's key and database among them)."
1318msgstr ""
1319
1320#: template/faq.html.j2:426
1321msgid ""
1322"Why do you believe it is worth giving up unique names for censorship "
1323"resistance?"
1324msgstr ""
1325
1326#: template/faq.html.j2:428
1327msgid ""
1328"A: The GNU Name system offers an alternative to DNS that is censorship "
1329"resistant. As with any security mechanism, this comes at a cost (names are "
1330"not globally unique). To draw a parallel, HTTPS connections use more "
1331"bandwidth and have higher latency than HTTP connections. Depending on your "
1332"application, HTTPS may not be worth the cost. However, for users that are "
1333"experiencing censorship (or are concerned about it), giving up globally "
1334"unique names may very well be worth the cost. After all, what is a &quot;"
1335"globally&quot; unique name worth, if it does not resolve?"
1336msgstr ""
1337
1338#: template/faq.html.j2:442
1339msgid "Why do you say that DNS is 'centralized' and 'distributed'?"
1340msgstr ""
1341
1342#: template/faq.html.j2:444
1343msgid ""
1344"A: We say that DNS is 'centralized' because it has a central component / "
1345"central point of failure --- the root zone and its management by IANA/ICANN. "
1346"This centralization creates vulnerabilities. For example, the US government "
1347"was able to reassign the management of the country-TLDs of Afganistan and "
1348"Iraq during the wars at the beginning of the 21st century."
1349msgstr ""
1350
1351#: template/faq.html.j2:455
1352msgid "How does GNS protect against layer-3 censorship?"
1353msgstr ""
1354
1355#: template/faq.html.j2:457
1356msgid ""
1357"A: GNS does not directly help with layer-3 censorship, but it does help "
1358"indirectly in two ways: <ol> <li> Many websites today use virtual hosting, "
1359"so blocking a particular IP address causes much more collateral damage than "
1360"blocking a DNS name. It thus raises the cost of censorship.</li> <li> "
1361"Existing layer-3 circumvention solutions (such as Tor) would benefit from a "
1362"censorship resistant naming system. Accessing Tor's &quot;.onion&quot; "
1363"namespace currently requires users to use unmemorable cryptographic "
1364"identifiers. With nicer names, Tor and tor2web-like services would be even "
1365"easier to use. </ol>"
1366msgstr ""
1367
1368#: template/faq.html.j2:476
1369msgid "Does GNS work with search engines?"
1370msgstr ""
1371
1372#: template/faq.html.j2:478
1373msgid ""
1374"A: GNS creates no significant problems for search engines, as they can use "
1375"GNS to perform name resolution as well as any normal user. Naturally, while "
1376"we typically expect normal users to install custom software for name "
1377"resolution, this is unlikely to work for search engines today. However, the "
1378"DNS2GNS gateway allows search engines to use DNS to resolve GNS names, so "
1379"they can still index GNS resources. However, as using DNS2GNS gateways "
1380"breaks the cryptographic chain of trust, legacy search engines will "
1381"obviously not obtain censorship-resistant names."
1382msgstr ""
1383
1384#: template/faq.html.j2:492
1385msgid "How does GNS compare to the Unmanaged Internet Architecture (UIA)?"
1386msgstr ""
1387
1388#: template/faq.html.j2:494
1389msgid ""
1390"A: UIA and GNS both share the same basic naming model, which actually "
1391"originated with Rivest's SDSI. However, UIA is not concerned about "
1392"integration with legacy applications and instead focuses on universal "
1393"connectivity between a user's many machines. In contrast, GNS was designed "
1394"to interoperate with DNS as much as possible, and to also work as much as "
1395"possible with the existing Web infrastructure. UIA is not at all concerned "
1396"about legacy systems (clean slate)."
1397msgstr ""
1398
1399#: template/faq.html.j2:507
1400msgid "Doesn't GNS increase the trusted-computing base compared to DNS(SEC)?"
1401msgstr ""
1402
1403#: template/faq.html.j2:509
1404msgid ""
1405"A: First of all, in GNS you can explicitly see the trust chain, so you know "
1406"if a name you are resolving belongs to a friend, or a friend-of-a-friend, "
1407"and can thus decide how much you trust the result. Naturally, the trusted-"
1408"computing base (TCB) can become arbitrarily large this way --- however, "
1409"given the name length restriction, for an individual name it is always less "
1410"than about 128 entities."
1411msgstr ""
1412
1413#: template/faq.html.j2:521
1414msgid ""
1415"How does GNS handle SRV/TLSA records where service and protocol are part of "
1416"the domain name?"
1417msgstr ""
1418
1419#: template/faq.html.j2:523
1420msgid ""
1421"A: When GNS splits a domain name into labels for resolution, it detects the "
1422"&quot;_Service._Proto&quot; syntax, converts &quot;Service&quot; to the "
1423"corresponding port number and &quot;Proto&quot; to the corresponding "
1424"protocol number. The rest of the name is resolved as usual. Then, when the "
1425"result is presented, GNS looks for the GNS-specific &quot;BOX&quot; record "
1426"type. A BOX record is a record that contains another record (such as SRV or "
1427"TLSA records) and adds a service and protocol number (and the original boxed "
1428"record type) to it."
1429msgstr ""
1430
1431#: template/faq.html.j2:541
933msgid "" 1432msgid ""
934"I receive many &quot;WARNING Calculated flow delay for X at Y for Z&quot;. " 1433"I receive many &quot;WARNING Calculated flow delay for X at Y for Z&quot;. "
935"Should I worry?" 1434"Should I worry?"
936msgstr "" 1435msgstr ""
937 1436
938#: template/faq.html.j2:37 1437#: template/faq.html.j2:543
939msgid "" 1438msgid ""
940"A: Right now, this is expected and a known cause for high latency in GNUnet. " 1439"A: Right now, this is expected and a known cause for high latency in GNUnet. "
941"We have started a major rewrite to address this and other problems, but " 1440"We have started a major rewrite to address this and other problems, but "
@@ -943,14 +1442,38 @@ msgid ""
943"expected." 1442"expected."
944msgstr "" 1443msgstr ""
945 1444
946#: template/faq.html.j2:46 1445#: template/faq.html.j2:552
947msgid "Is there a graphical user interface?" 1446msgid "Error opening `/dev/net/tun': No such file or directory?"
948msgstr "" 1447msgstr ""
949 1448
950#: template/faq.html.j2:48 1449#: template/faq.html.j2:554
951msgid "" 1450msgid ""
952"A: gnunet-gtk is a separate download. The package contains various GTK+ " 1451"A: If you get this error message, the solution is simple. Issue the "
953"based graphical interfaces, including a graphical tool for configuration." 1452"following commands (as root) to create the required device file"
1453msgstr ""
1454
1455#: template/faq.html.j2:566
1456msgid ""
1457"'iptables: No chain/target/match by that name.' (when running gnunet-service-"
1458"dns)?"
1459msgstr ""
1460
1461#: template/faq.html.j2:568
1462msgid ""
1463"A: For GNUnet DNS, your iptables needs to have &quot;owner&quot; match "
1464"support. This is accomplished by having the correct kernel options. Check if "
1465"your kernel has CONFIG_NETFILTER_XT_MATCH_OWNER set to either 'y' or "
1466"'m' (and the module is loaded)."
1467msgstr ""
1468
1469#: template/faq.html.j2:580
1470msgid "'Timeout was reached' when running PT on Fedora (and possibly others)?"
1471msgstr ""
1472
1473#: template/faq.html.j2:582
1474msgid ""
1475"A: If you get an error stating that the VPN timeout was reached, check if "
1476"your firewall is enabled and blocking the connections."
954msgstr "" 1477msgstr ""
955 1478
956#: template/glossary.html.j2:12 1479#: template/glossary.html.j2:12
@@ -1057,10 +1580,6 @@ msgstr ""
1057msgid "Overview" 1580msgid "Overview"
1058msgstr "" 1581msgstr ""
1059 1582
1060#: template/gns.html.j2:37
1061msgid "Features"
1062msgstr ""
1063
1064#: template/gns.html.j2:39 1583#: template/gns.html.j2:39
1065msgid "" 1584msgid ""
1066"The GNU Name System (GNS) is secure and decentralized naming system. It " 1585"The GNU Name System (GNS) is secure and decentralized naming system. It "