diff options
Diffstat (limited to 'locale/messages.pot')
-rw-r--r-- | locale/messages.pot | 563 |
1 files changed, 544 insertions, 19 deletions
diff --git a/locale/messages.pot b/locale/messages.pot index c129e8f2..4b2a70b6 100644 --- a/locale/messages.pot +++ b/locale/messages.pot | |||
@@ -8,7 +8,7 @@ msgid "" | |||
8 | msgstr "" | 8 | msgstr "" |
9 | "Project-Id-Version: PROJECT VERSION\n" | 9 | "Project-Id-Version: PROJECT VERSION\n" |
10 | "Report-Msgid-Bugs-To: EMAIL@ADDRESS\n" | 10 | "Report-Msgid-Bugs-To: EMAIL@ADDRESS\n" |
11 | "POT-Creation-Date: 2021-03-03 21:41+0100\n" | 11 | "POT-Creation-Date: 2021-03-12 12:43+0100\n" |
12 | "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" | 12 | "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" |
13 | "Last-Translator: FULL NAME <EMAIL@ADDRESS>\n" | 13 | "Last-Translator: FULL NAME <EMAIL@ADDRESS>\n" |
14 | "Language-Team: LANGUAGE <LL@li.org>\n" | 14 | "Language-Team: LANGUAGE <LL@li.org>\n" |
@@ -63,6 +63,7 @@ msgid "About" | |||
63 | msgstr "" | 63 | msgstr "" |
64 | 64 | ||
65 | #: common/navigation.j2.inc:39 news/index.html.j2:8 | 65 | #: common/navigation.j2.inc:39 news/index.html.j2:8 |
66 | #: news/oldnews-2011.html.j2:13 news/oldnews-2013.html.j2:13 | ||
66 | #: news/oldnews-2018.html.j2:13 news/oldnews-2019.html.j2:13 | 67 | #: news/oldnews-2018.html.j2:13 news/oldnews-2019.html.j2:13 |
67 | msgid "News" | 68 | msgid "News" |
68 | msgstr "" | 69 | msgstr "" |
@@ -155,17 +156,20 @@ msgstr "" | |||
155 | msgid "FAQ" | 156 | msgid "FAQ" |
156 | msgstr "" | 157 | msgstr "" |
157 | 158 | ||
158 | #: news/index.html.j2:11 news/oldnews-2018.html.j2:16 | 159 | #: news/index.html.j2:11 news/oldnews-2011.html.j2:16 |
160 | #: news/oldnews-2013.html.j2:16 news/oldnews-2018.html.j2:16 | ||
159 | #: news/oldnews-2019.html.j2:16 | 161 | #: news/oldnews-2019.html.j2:16 |
160 | msgid "News posts about changes related to GNUnet such as releases and events" | 162 | msgid "News posts about changes related to GNUnet such as releases and events" |
161 | msgstr "" | 163 | msgstr "" |
162 | 164 | ||
163 | #: news/index.html.j2:16 news/oldnews-2018.html.j2:21 | 165 | #: news/index.html.j2:16 news/oldnews-2011.html.j2:21 |
166 | #: news/oldnews-2013.html.j2:21 news/oldnews-2018.html.j2:21 | ||
164 | #: news/oldnews-2019.html.j2:21 | 167 | #: news/oldnews-2019.html.j2:21 |
165 | msgid "subscribe to our RSS feed" | 168 | msgid "subscribe to our RSS feed" |
166 | msgstr "" | 169 | msgstr "" |
167 | 170 | ||
168 | #: news/index.html.j2:36 news/oldnews-2018.html.j2:40 | 171 | #: news/index.html.j2:36 news/oldnews-2011.html.j2:40 |
172 | #: news/oldnews-2013.html.j2:40 news/oldnews-2018.html.j2:40 | ||
169 | #: news/oldnews-2019.html.j2:40 | 173 | #: news/oldnews-2019.html.j2:40 |
170 | msgid "read more" | 174 | msgid "read more" |
171 | msgstr "" | 175 | msgstr "" |
@@ -792,11 +796,125 @@ msgid "" | |||
792 | "<dd>DE67830654080004822650 (BIC/SWIFT: GENODEF1SLR)</dd> </dl>" | 796 | "<dd>DE67830654080004822650 (BIC/SWIFT: GENODEF1SLR)</dd> </dl>" |
793 | msgstr "" | 797 | msgstr "" |
794 | 798 | ||
795 | #: template/faq.html.j2:12 | 799 | #: template/faq.html.j2:12 template/faq.html.j2:21 |
800 | msgid "General" | ||
801 | msgstr "" | ||
802 | |||
803 | #: template/faq.html.j2:13 template/faq.html.j2:146 template/gns.html.j2:37 | ||
804 | msgid "Features" | ||
805 | msgstr "" | ||
806 | |||
807 | #: template/faq.html.j2:15 template/faq.html.j2:539 | ||
808 | msgid "Error messages" | ||
809 | msgstr "" | ||
810 | |||
811 | #: template/faq.html.j2:24 | ||
812 | msgid "What do I do if my question is not answered here?" | ||
813 | msgstr "" | ||
814 | |||
815 | #: template/faq.html.j2:26 | ||
816 | msgid "" | ||
817 | "A: There are many other sources of information. You can read additional " | ||
818 | "documentation or ask the question on the help-gnunet@gnu.org mailing list" | ||
819 | " or the #gnunet IRC on irc.freenode.net." | ||
820 | msgstr "" | ||
821 | |||
822 | #: template/faq.html.j2:34 | ||
823 | msgid "When are you going to release the next version?" | ||
824 | msgstr "" | ||
825 | |||
826 | #: template/faq.html.j2:36 | ||
827 | msgid "" | ||
828 | "A: The general answer is, when it is ready. A better answer may be: " | ||
829 | "earlier if you contribute (test, debug, code, document). Every release " | ||
830 | "will be anounced on the info-gnunet@gnu.org mailing list and on <a " | ||
831 | "href=\"https://planet.gnu.org\">planet GNU</a>. You can subscribe to the " | ||
832 | "mailing list or the RSS feed of this site to automatically receive a " | ||
833 | "notification." | ||
834 | msgstr "" | ||
835 | |||
836 | #: template/faq.html.j2:47 | ||
837 | msgid "Is the code free?" | ||
838 | msgstr "" | ||
839 | |||
840 | #: template/faq.html.j2:49 | ||
841 | msgid "" | ||
842 | "A: GNUnet is free software, available under the <a " | ||
843 | "href=\"https://www.gnu.org/licenses/agpl-3.0.en.html\">GNU Affero Public " | ||
844 | "License (AGPL)</a>." | ||
845 | msgstr "" | ||
846 | |||
847 | #: template/faq.html.j2:56 | ||
848 | msgid "Are there any known bugs?" | ||
849 | msgstr "" | ||
850 | |||
851 | #: template/faq.html.j2:58 | ||
852 | msgid "" | ||
853 | "A: We track the list of currently known bugs in the <a " | ||
854 | "href=\"https://bugs.gnunet.org/\">Mantis system</a>. Some bugs are " | ||
855 | "occasionally reported directly to developers or the developer mailing " | ||
856 | "list. This is discouraged since developers often do not have the time to " | ||
857 | "feed these bugs back into the Mantis database. Please report bugs " | ||
858 | "directly to the bug tracking system. If you believe a bug is sensitive, " | ||
859 | "you can set its view status to private (this should be the exception)." | ||
860 | msgstr "" | ||
861 | |||
862 | #: template/faq.html.j2:71 | ||
863 | msgid "Is there a graphical user interface?" | ||
864 | msgstr "" | ||
865 | |||
866 | #: template/faq.html.j2:73 | ||
867 | msgid "" | ||
868 | "A: gnunet-gtk is a separate download. The package contains various GTK+ " | ||
869 | "based graphical interfaces, including a graphical tool for configuration." | ||
870 | msgstr "" | ||
871 | |||
872 | #: template/faq.html.j2:81 | ||
873 | msgid "Why does gnunet-service-nse create a high CPU load?" | ||
874 | msgstr "" | ||
875 | |||
876 | #: template/faq.html.j2:83 | ||
877 | msgid "" | ||
878 | "A: The gnunet-service-nse process will initially compute a so-called " | ||
879 | ""proof-of-work" which is used to convince the network that your" | ||
880 | " peer is real (or, rather, make it expensive for an adversary to mount a " | ||
881 | "Sybil attack on the network size estimator). The calculation is expected " | ||
882 | "to take a few days, depending on how fast your CPU is. If the CPU load is" | ||
883 | " creating a problem for you, you can set the value "WORKDELAY" " | ||
884 | "in the "nse" section of your configuration file to a higher " | ||
885 | "value. The default is "5 ms"." | ||
886 | msgstr "" | ||
887 | |||
888 | #: template/faq.html.j2:97 | ||
889 | msgid "How does GNUnet compare to Tor?" | ||
890 | msgstr "" | ||
891 | |||
892 | #: template/faq.html.j2:99 | ||
893 | msgid "" | ||
894 | "A: Tor focuses on anonymous communication and censorship-resistance for " | ||
895 | "TCP connections and, with the Tor Browser Bundle, for the Web in " | ||
896 | "particular. GNUnet does not really have one focus; our theme is secure " | ||
897 | "decentralized networking, but that is too broad to be called a focus." | ||
898 | msgstr "" | ||
899 | |||
900 | #: template/faq.html.j2:109 | ||
901 | msgid "How does GNUnet compare to I2P?" | ||
902 | msgstr "" | ||
903 | |||
904 | #: template/faq.html.j2:111 | ||
905 | msgid "" | ||
906 | "A: Both GNUnet and I2P want to build a better, more secure, more " | ||
907 | "decentralized Internet. However, on the technical side, there are almost " | ||
908 | "no overlaps. <br><br> I2P is written in Java, and has (asymmetric) " | ||
909 | "tunnels using onion (or garlic) routing as the basis for various " | ||
910 | "(anonymized) applications. I2P is largely used via a Web frontend." | ||
911 | msgstr "" | ||
912 | |||
913 | #: template/faq.html.j2:122 | ||
796 | msgid "Is GNUnet ready for use on production systems?" | 914 | msgid "Is GNUnet ready for use on production systems?" |
797 | msgstr "" | 915 | msgstr "" |
798 | 916 | ||
799 | #: template/faq.html.j2:14 | 917 | #: template/faq.html.j2:124 |
800 | msgid "" | 918 | msgid "" |
801 | "A: GNUnet is still undergoing major development. It is largely not yet " | 919 | "A: GNUnet is still undergoing major development. It is largely not yet " |
802 | "ready for usage beyond developers. Your mileage will vary depending on " | 920 | "ready for usage beyond developers. Your mileage will vary depending on " |
@@ -806,24 +924,411 @@ msgid "" | |||
806 | "[TNG]")" | 924 | "[TNG]")" |
807 | msgstr "" | 925 | msgstr "" |
808 | 926 | ||
809 | #: template/faq.html.j2:24 | 927 | #: template/faq.html.j2:134 |
810 | msgid "Is GNUnet build using distributed ledger technologies?" | 928 | msgid "Is GNUnet build using distributed ledger technologies?" |
811 | msgstr "" | 929 | msgstr "" |
812 | 930 | ||
813 | #: template/faq.html.j2:26 | 931 | #: template/faq.html.j2:136 |
814 | msgid "" | 932 | msgid "" |
815 | "A: No. GNUnet is a new network protocol stack for building secure, " | 933 | "A: No. GNUnet is a new network protocol stack for building secure, " |
816 | "distributed, and privacy-preserving applications. While a ledger could be" | 934 | "distributed, and privacy-preserving applications. While a ledger could be" |
817 | " built using GNUnet, we currently have no plans in doing so." | 935 | " built using GNUnet, we currently have no plans in doing so." |
818 | msgstr "" | 936 | msgstr "" |
819 | 937 | ||
820 | #: template/faq.html.j2:35 | 938 | #: template/faq.html.j2:148 |
939 | msgid "What can I do with GNUnet?" | ||
940 | msgstr "" | ||
941 | |||
942 | #: template/faq.html.j2:150 | ||
943 | msgid "" | ||
944 | "A: GNUnet is a peer-to-peer framework, by which we mostly mean that it " | ||
945 | "can do more than just one thing. Naturally, the implementation and " | ||
946 | "documentation of some of the features that exist are more advanced than " | ||
947 | "others." | ||
948 | msgstr "" | ||
949 | |||
950 | #: template/faq.html.j2:157 | ||
951 | msgid "" | ||
952 | "For users, GNUnet offers anonymous and non-anonymous file-sharing, a " | ||
953 | "fully decentralized and censorship-resistant replacement for DNS and a " | ||
954 | "mechanism for IPv4-IPv6 protocol translation and tunneling (NAT-PT with " | ||
955 | "DNS-ALG)." | ||
956 | msgstr "" | ||
957 | |||
958 | #: template/faq.html.j2:171 | ||
959 | msgid "Who runs the GNS root zone?" | ||
960 | msgstr "" | ||
961 | |||
962 | #: template/faq.html.j2:173 | ||
963 | msgid "" | ||
964 | "A: Short answer: you. The long answer is the GNUnet will ship with a " | ||
965 | "default configuration of top-level domains. The governance of this " | ||
966 | "default configuration is not yet established. In any case, the user will " | ||
967 | "be able to modify this configuration at will. We expect normal users to " | ||
968 | "have no need to edit their own GNS zone(s) unless they host services " | ||
969 | "themselves." | ||
970 | msgstr "" | ||
971 | |||
972 | #: template/faq.html.j2:184 | ||
973 | msgid "Where is the per-user GNS database kept?" | ||
974 | msgstr "" | ||
975 | |||
976 | #: template/faq.html.j2:186 | ||
977 | msgid "" | ||
978 | "A: The short answer is that the database is kept at the user's GNUnet " | ||
979 | "peer. Now, a user may run multiple GNUnet peers, in which case the " | ||
980 | "database could be kept at each peer (however, we don't have code for " | ||
981 | "convenient replication). Similarly, multiple GNUnet peers can share one " | ||
982 | "instance of the database --- the "gnunet-service-namestore" can" | ||
983 | " be accessed from remote (via TCP). The actual data can be stored in a " | ||
984 | "Postgres database, for which various replication options are again " | ||
985 | "applicable. Ultimately, there are many options for how users can store " | ||
986 | "(and secure) their GNS database." | ||
987 | msgstr "" | ||
988 | |||
989 | #: template/faq.html.j2:201 | ||
990 | msgid "What is the expected average size of a GNS namestore database?" | ||
991 | msgstr "" | ||
992 | |||
993 | #: template/faq.html.j2:203 | ||
994 | msgid "" | ||
995 | "A: Pretty small. Based on our user study where we looked at browser " | ||
996 | "histories and the number of domains visited, we expect that GNS databases" | ||
997 | " will only grow to a few tens of thousands of entries, small enough to " | ||
998 | "fit even on mobile devices." | ||
999 | msgstr "" | ||
1000 | |||
1001 | #: template/faq.html.j2:213 | ||
1002 | msgid "Is GNS resistant to the attacks on DNS used by the US?" | ||
1003 | msgstr "" | ||
1004 | |||
1005 | #: template/faq.html.j2:215 | ||
1006 | msgid "" | ||
1007 | "A: We believe so, as there is no entity that any government could force " | ||
1008 | "to change the mapping for a name except for each individual user (and " | ||
1009 | "then the changes would only apply to the names that this user is the " | ||
1010 | "authority for). So if everyone used GNS, the only practical attack of a " | ||
1011 | "government would be to force the operator of a server to change the GNS " | ||
1012 | "records for his server to point elsewhere. However, if the owner of the " | ||
1013 | "private key for a zone is unavailable for enforcement, the respective " | ||
1014 | "zone cannot be changed and any other zone delegating to this zone will " | ||
1015 | "achieve proper resolution." | ||
1016 | msgstr "" | ||
1017 | |||
1018 | #: template/faq.html.j2:229 | ||
1019 | msgid "What is the difference between GNS and CoDoNS?" | ||
1020 | msgstr "" | ||
1021 | |||
1022 | #: template/faq.html.j2:231 | ||
1023 | msgid "" | ||
1024 | "A: CoDoNS decentralizes the DNS database (using a DHT) but preserves the " | ||
1025 | "authority structure of DNS. With CoDoNS, IANA/ICANN are still in charge, " | ||
1026 | "and there are still registrars that determine who owns a name. <br><br> " | ||
1027 | "With GNS, we decentralize the database and also decentralize the " | ||
1028 | "responsibility for naming: each user runs his own personal root zone and " | ||
1029 | "is thus in complete control of the names he uses. GNS also has many " | ||
1030 | "additional features (to keep names short and enable migration) which " | ||
1031 | "don't even make sense in the context of CoDoNS." | ||
1032 | msgstr "" | ||
1033 | |||
1034 | #: template/faq.html.j2:247 | ||
1035 | msgid "What is the difference between GNS and SocialDNS?" | ||
1036 | msgstr "" | ||
1037 | |||
1038 | #: template/faq.html.j2:249 | ||
1039 | msgid "" | ||
1040 | "A: Like GNS, SocialDNS allows each user to create DNS mappings. However, " | ||
1041 | "with SocialDNS the mappings are shared through the social network and " | ||
1042 | "subjected to ranking. As the social relationships evolve, names can thus " | ||
1043 | "change in surprising ways. <br><br> With GNS, names are primarily shared " | ||
1044 | "via delegation, and thus mappings will only change if the user " | ||
1045 | "responsible for the name (the authority) manually changes the record." | ||
1046 | msgstr "" | ||
1047 | |||
1048 | #: template/faq.html.j2:263 | ||
1049 | msgid "What is the difference between GNS and ODDNS?" | ||
1050 | msgstr "" | ||
1051 | |||
1052 | #: template/faq.html.j2:265 | ||
1053 | msgid "" | ||
1054 | "A: ODDNS is primarily designed to bypass the DNS root zone and the TLD " | ||
1055 | "registries (such as those for \".com\" and \".org\"). Instead of using " | ||
1056 | "those, each user is expected to maintain a database of (second-level) " | ||
1057 | "domains (like \"gnu.org\") and the IP addresses of the respective name " | ||
1058 | "servers. Resolution will fail if the target name servers change IPs." | ||
1059 | msgstr "" | ||
1060 | |||
1061 | #: template/faq.html.j2:276 | ||
1062 | msgid "What is the difference between GNS and Namecoin?" | ||
1063 | msgstr "" | ||
1064 | |||
1065 | #: template/faq.html.j2:283 | ||
1066 | msgid "What is the difference between GNS and Handshake?" | ||
1067 | msgstr "" | ||
1068 | |||
1069 | #: template/faq.html.j2:289 | ||
1070 | msgid "What is the difference between GNS and ENS?" | ||
1071 | msgstr "" | ||
1072 | |||
1073 | #: template/faq.html.j2:295 | ||
1074 | msgid "What is the difference between GNS and TrickleDNS?" | ||
1075 | msgstr "" | ||
1076 | |||
1077 | #: template/faq.html.j2:297 | ||
1078 | msgid "" | ||
1079 | "A: TrickleDNS pushes ("critical") DNS records between DNS " | ||
1080 | "resolvers of participating domains to provide "better availability, " | ||
1081 | "lower query resolution times, and faster update propagation". Thus " | ||
1082 | "TrickleDNS is focused on defeating attacks on the availability (and " | ||
1083 | "performance) of record propagation in DNS, for example via DDoS attacks " | ||
1084 | "on DNS root servers. TrickleDNS is thus concerned with how to ensure " | ||
1085 | "distribution of authoritative records, and authority remains derived from" | ||
1086 | " the DNS hierarchy." | ||
1087 | msgstr "" | ||
1088 | |||
1089 | #: template/faq.html.j2:310 | ||
1090 | msgid "" | ||
1091 | "Does GNS require real-world introduction (secure PKEY exchange) in the " | ||
1092 | "style of the PGP web of trust?" | ||
1093 | msgstr "" | ||
1094 | |||
1095 | #: template/faq.html.j2:312 | ||
1096 | msgid "" | ||
1097 | "A: For security, it is well known that an initial trust path between the " | ||
1098 | "two parties must exist. However, for applications where this is not " | ||
1099 | "required, weaker mechanisms can be used. For example, we have implemented" | ||
1100 | " a first-come-first-served (FCFS) authority which allows arbitrary users " | ||
1101 | "to register arbitrary names. The key of this authority is included with " | ||
1102 | "every GNUnet installation. Thus, any name registered with FCFS is in fact" | ||
1103 | " global and requires no further introduction. However, the security of " | ||
1104 | "these names depends entirely on the trustworthiness of the FCFS " | ||
1105 | "authority. The authority can be queried under the ".ping" TLD." | ||
1106 | msgstr "" | ||
1107 | |||
1108 | #: template/faq.html.j2:327 | ||
1109 | msgid "" | ||
1110 | "How can a legitimate domain owner tell other people to not use his name " | ||
1111 | "in GNS?" | ||
1112 | msgstr "" | ||
1113 | |||
1114 | #: template/faq.html.j2:329 | ||
1115 | msgid "" | ||
1116 | "A: Names have no owners in GNS, so there cannot be a " | ||
1117 | ""legitimate" domain owner. Any user can claim any name (as his " | ||
1118 | "preferred name or "pseudonym") in his NICK record. Similarly, " | ||
1119 | "all other users can choose to ignore this preference and use a name of " | ||
1120 | "their choice (or even assign no name) for this user." | ||
1121 | msgstr "" | ||
1122 | |||
1123 | #: template/faq.html.j2:340 | ||
1124 | msgid "" | ||
1125 | "Did you consider the privacy implications of making your personal GNS " | ||
1126 | "zone visible?" | ||
1127 | msgstr "" | ||
1128 | |||
1129 | #: template/faq.html.j2:342 | ||
1130 | msgid "" | ||
1131 | "A: Each record in GNS has a flag "private". Records are shared " | ||
1132 | "with other users (via DHT or zone transfers) only if this flag is not " | ||
1133 | "set. Thus, users have full control over what information about their " | ||
1134 | "zones is made public." | ||
1135 | msgstr "" | ||
1136 | |||
1137 | #: template/faq.html.j2:352 | ||
1138 | msgid "Are \"Legacy Host\" (LEHO) records not going to be obsolete with IPv6?" | ||
1139 | msgstr "" | ||
1140 | |||
1141 | #: template/faq.html.j2:354 | ||
1142 | msgid "" | ||
1143 | "A: The question presumes that (a) virtual hosting is only necessary " | ||
1144 | "because of IPv4 address scarcity, and (b) that LEHOs are only useful in " | ||
1145 | "the context of virtual hosting. However, LEHOs are also useful to help " | ||
1146 | "with X.509 certificate validation (as they specify for which legacy " | ||
1147 | "hostname the certificate should be valid). Also, even with IPv6 fully " | ||
1148 | "deployed and "infinite" IP addresses being available, we're not" | ||
1149 | " sure that virtual hosting would disappear. Finally, we don't want to " | ||
1150 | "have to wait for IPv6 to become commonplace, GNS should work with today's" | ||
1151 | " networks." | ||
1152 | msgstr "" | ||
1153 | |||
1154 | #: template/faq.html.j2:368 | ||
1155 | msgid "" | ||
1156 | "Why does GNS not use a trust metric or consensus to determine globally " | ||
1157 | "unique names?" | ||
1158 | msgstr "" | ||
1159 | |||
1160 | #: template/faq.html.j2:370 | ||
1161 | msgid "" | ||
1162 | "A: Trust metrics have the fundamental problem that they have thresholds. " | ||
1163 | "As trust relationships evolve, mappings would change their meaning as " | ||
1164 | "they cross each others thresholds. We decided that the resulting " | ||
1165 | "unpredictability of the resolution process was not acceptable. " | ||
1166 | "Furthermore, trust and consensus might be easy to manipulate by " | ||
1167 | "adversaries." | ||
1168 | msgstr "" | ||
1169 | |||
1170 | #: template/faq.html.j2:381 | ||
1171 | msgid "How do you handle compromised zone keys in GNS?" | ||
1172 | msgstr "" | ||
1173 | |||
1174 | #: template/faq.html.j2:383 | ||
1175 | msgid "" | ||
1176 | "A: The owner of a private key can create a revocation message. This one " | ||
1177 | "can then be flooded throughout the overlay network, creating a copy at " | ||
1178 | "all peers. Before using a public key, peers check if that key has been " | ||
1179 | "revoked. All names that involve delegation via a revoked zone will then " | ||
1180 | "fail to resolve. Peers always automatically check for the existence of a " | ||
1181 | "revocation message when resolving names." | ||
1182 | msgstr "" | ||
1183 | |||
1184 | #: template/faq.html.j2:395 | ||
1185 | msgid "Could the signing algorithm of GNS be upgraded in the future?" | ||
1186 | msgstr "" | ||
1187 | |||
1188 | #: template/faq.html.j2:397 | ||
1189 | msgid "" | ||
1190 | "A: Yes. In our efforts to standardize GNS, we have already modified the " | ||
1191 | "protocol to support alternative delegation records. <br> <br> Naturally, " | ||
1192 | "deployed GNS implementations would have to be updated to support the new " | ||
1193 | "signature scheme. The new scheme can then be run in parallel with the " | ||
1194 | "existing system by using a new record type to indicate the use of a " | ||
1195 | "different cipher system." | ||
1196 | msgstr "" | ||
1197 | |||
1198 | #: template/faq.html.j2:411 | ||
1199 | msgid "How can a GNS zone maintain several name servers, e.g. for load balancing?" | ||
1200 | msgstr "" | ||
1201 | |||
1202 | #: template/faq.html.j2:413 | ||
1203 | msgid "" | ||
1204 | "A: We don't expect this to be necessary, as GNS records are stored (and " | ||
1205 | "replicated) in the R5N DHT. Thus the authority will typically not be " | ||
1206 | "contacted whenever clients perform a lookup. Even if the authority goes " | ||
1207 | "(temporarily) off-line, the DHT will cache the records for some time. " | ||
1208 | "However, should having multiple servers for a zone be considered truly " | ||
1209 | "necessary, the owner of the zone can simply run multiple peers (and share" | ||
1210 | " the zone's key and database among them)." | ||
1211 | msgstr "" | ||
1212 | |||
1213 | #: template/faq.html.j2:426 | ||
1214 | msgid "" | ||
1215 | "Why do you believe it is worth giving up unique names for censorship " | ||
1216 | "resistance?" | ||
1217 | msgstr "" | ||
1218 | |||
1219 | #: template/faq.html.j2:428 | ||
1220 | msgid "" | ||
1221 | "A: The GNU Name system offers an alternative to DNS that is censorship " | ||
1222 | "resistant. As with any security mechanism, this comes at a cost (names " | ||
1223 | "are not globally unique). To draw a parallel, HTTPS connections use more " | ||
1224 | "bandwidth and have higher latency than HTTP connections. Depending on " | ||
1225 | "your application, HTTPS may not be worth the cost. However, for users " | ||
1226 | "that are experiencing censorship (or are concerned about it), giving up " | ||
1227 | "globally unique names may very well be worth the cost. After all, what is" | ||
1228 | " a "globally" unique name worth, if it does not resolve?" | ||
1229 | msgstr "" | ||
1230 | |||
1231 | #: template/faq.html.j2:442 | ||
1232 | msgid "Why do you say that DNS is 'centralized' and 'distributed'?" | ||
1233 | msgstr "" | ||
1234 | |||
1235 | #: template/faq.html.j2:444 | ||
1236 | msgid "" | ||
1237 | "A: We say that DNS is 'centralized' because it has a central component / " | ||
1238 | "central point of failure --- the root zone and its management by " | ||
1239 | "IANA/ICANN. This centralization creates vulnerabilities. For example, the" | ||
1240 | " US government was able to reassign the management of the country-TLDs of" | ||
1241 | " Afganistan and Iraq during the wars at the beginning of the 21st " | ||
1242 | "century." | ||
1243 | msgstr "" | ||
1244 | |||
1245 | #: template/faq.html.j2:455 | ||
1246 | msgid "How does GNS protect against layer-3 censorship?" | ||
1247 | msgstr "" | ||
1248 | |||
1249 | #: template/faq.html.j2:457 | ||
1250 | msgid "" | ||
1251 | "A: GNS does not directly help with layer-3 censorship, but it does help " | ||
1252 | "indirectly in two ways: <ol> <li> Many websites today use virtual " | ||
1253 | "hosting, so blocking a particular IP address causes much more collateral " | ||
1254 | "damage than blocking a DNS name. It thus raises the cost of " | ||
1255 | "censorship.</li> <li> Existing layer-3 circumvention solutions (such as " | ||
1256 | "Tor) would benefit from a censorship resistant naming system. Accessing " | ||
1257 | "Tor's ".onion" namespace currently requires users to use " | ||
1258 | "unmemorable cryptographic identifiers. With nicer names, Tor and tor2web-" | ||
1259 | "like services would be even easier to use. </ol>" | ||
1260 | msgstr "" | ||
1261 | |||
1262 | #: template/faq.html.j2:476 | ||
1263 | msgid "Does GNS work with search engines?" | ||
1264 | msgstr "" | ||
1265 | |||
1266 | #: template/faq.html.j2:478 | ||
1267 | msgid "" | ||
1268 | "A: GNS creates no significant problems for search engines, as they can " | ||
1269 | "use GNS to perform name resolution as well as any normal user. Naturally," | ||
1270 | " while we typically expect normal users to install custom software for " | ||
1271 | "name resolution, this is unlikely to work for search engines today. " | ||
1272 | "However, the DNS2GNS gateway allows search engines to use DNS to resolve " | ||
1273 | "GNS names, so they can still index GNS resources. However, as using " | ||
1274 | "DNS2GNS gateways breaks the cryptographic chain of trust, legacy search " | ||
1275 | "engines will obviously not obtain censorship-resistant names." | ||
1276 | msgstr "" | ||
1277 | |||
1278 | #: template/faq.html.j2:492 | ||
1279 | msgid "How does GNS compare to the Unmanaged Internet Architecture (UIA)?" | ||
1280 | msgstr "" | ||
1281 | |||
1282 | #: template/faq.html.j2:494 | ||
1283 | msgid "" | ||
1284 | "A: UIA and GNS both share the same basic naming model, which actually " | ||
1285 | "originated with Rivest's SDSI. However, UIA is not concerned about " | ||
1286 | "integration with legacy applications and instead focuses on universal " | ||
1287 | "connectivity between a user's many machines. In contrast, GNS was " | ||
1288 | "designed to interoperate with DNS as much as possible, and to also work " | ||
1289 | "as much as possible with the existing Web infrastructure. UIA is not at " | ||
1290 | "all concerned about legacy systems (clean slate)." | ||
1291 | msgstr "" | ||
1292 | |||
1293 | #: template/faq.html.j2:507 | ||
1294 | msgid "Doesn't GNS increase the trusted-computing base compared to DNS(SEC)?" | ||
1295 | msgstr "" | ||
1296 | |||
1297 | #: template/faq.html.j2:509 | ||
1298 | msgid "" | ||
1299 | "A: First of all, in GNS you can explicitly see the trust chain, so you " | ||
1300 | "know if a name you are resolving belongs to a friend, or a friend-" | ||
1301 | "of-a-friend, and can thus decide how much you trust the result. " | ||
1302 | "Naturally, the trusted-computing base (TCB) can become arbitrarily large " | ||
1303 | "this way --- however, given the name length restriction, for an " | ||
1304 | "individual name it is always less than about 128 entities." | ||
1305 | msgstr "" | ||
1306 | |||
1307 | #: template/faq.html.j2:521 | ||
1308 | msgid "" | ||
1309 | "How does GNS handle SRV/TLSA records where service and protocol are part " | ||
1310 | "of the domain name?" | ||
1311 | msgstr "" | ||
1312 | |||
1313 | #: template/faq.html.j2:523 | ||
1314 | msgid "" | ||
1315 | "A: When GNS splits a domain name into labels for resolution, it detects " | ||
1316 | "the "_Service._Proto" syntax, converts "Service" to " | ||
1317 | "the corresponding port number and "Proto" to the corresponding " | ||
1318 | "protocol number. The rest of the name is resolved as usual. Then, when " | ||
1319 | "the result is presented, GNS looks for the GNS-specific "BOX" " | ||
1320 | "record type. A BOX record is a record that contains another record (such " | ||
1321 | "as SRV or TLSA records) and adds a service and protocol number (and the " | ||
1322 | "original boxed record type) to it." | ||
1323 | msgstr "" | ||
1324 | |||
1325 | #: template/faq.html.j2:541 | ||
821 | msgid "" | 1326 | msgid "" |
822 | "I receive many "WARNING Calculated flow delay for X at Y for " | 1327 | "I receive many "WARNING Calculated flow delay for X at Y for " |
823 | "Z". Should I worry?" | 1328 | "Z". Should I worry?" |
824 | msgstr "" | 1329 | msgstr "" |
825 | 1330 | ||
826 | #: template/faq.html.j2:37 | 1331 | #: template/faq.html.j2:543 |
827 | msgid "" | 1332 | msgid "" |
828 | "A: Right now, this is expected and a known cause for high latency in " | 1333 | "A: Right now, this is expected and a known cause for high latency in " |
829 | "GNUnet. We have started a major rewrite to address this and other " | 1334 | "GNUnet. We have started a major rewrite to address this and other " |
@@ -831,14 +1336,38 @@ msgid "" | |||
831 | "warnings are expected." | 1336 | "warnings are expected." |
832 | msgstr "" | 1337 | msgstr "" |
833 | 1338 | ||
834 | #: template/faq.html.j2:46 | 1339 | #: template/faq.html.j2:552 |
835 | msgid "Is there a graphical user interface?" | 1340 | msgid "Error opening `/dev/net/tun': No such file or directory?" |
836 | msgstr "" | 1341 | msgstr "" |
837 | 1342 | ||
838 | #: template/faq.html.j2:48 | 1343 | #: template/faq.html.j2:554 |
839 | msgid "" | 1344 | msgid "" |
840 | "A: gnunet-gtk is a separate download. The package contains various GTK+ " | 1345 | "A: If you get this error message, the solution is simple. Issue the " |
841 | "based graphical interfaces, including a graphical tool for configuration." | 1346 | "following commands (as root) to create the required device file" |
1347 | msgstr "" | ||
1348 | |||
1349 | #: template/faq.html.j2:566 | ||
1350 | msgid "" | ||
1351 | "'iptables: No chain/target/match by that name.' (when running gnunet-" | ||
1352 | "service-dns)?" | ||
1353 | msgstr "" | ||
1354 | |||
1355 | #: template/faq.html.j2:568 | ||
1356 | msgid "" | ||
1357 | "A: For GNUnet DNS, your iptables needs to have "owner" match " | ||
1358 | "support. This is accomplished by having the correct kernel options. Check" | ||
1359 | " if your kernel has CONFIG_NETFILTER_XT_MATCH_OWNER set to either 'y' or " | ||
1360 | "'m' (and the module is loaded)." | ||
1361 | msgstr "" | ||
1362 | |||
1363 | #: template/faq.html.j2:580 | ||
1364 | msgid "'Timeout was reached' when running PT on Fedora (and possibly others)?" | ||
1365 | msgstr "" | ||
1366 | |||
1367 | #: template/faq.html.j2:582 | ||
1368 | msgid "" | ||
1369 | "A: If you get an error stating that the VPN timeout was reached, check if" | ||
1370 | " your firewall is enabled and blocking the connections." | ||
842 | msgstr "" | 1371 | msgstr "" |
843 | 1372 | ||
844 | #: template/glossary.html.j2:12 | 1373 | #: template/glossary.html.j2:12 |
@@ -946,10 +1475,6 @@ msgstr "" | |||
946 | msgid "Overview" | 1475 | msgid "Overview" |
947 | msgstr "" | 1476 | msgstr "" |
948 | 1477 | ||
949 | #: template/gns.html.j2:37 | ||
950 | msgid "Features" | ||
951 | msgstr "" | ||
952 | |||
953 | #: template/gns.html.j2:39 | 1478 | #: template/gns.html.j2:39 |
954 | msgid "" | 1479 | msgid "" |
955 | "The GNU Name System (GNS) is secure and decentralized naming system. It " | 1480 | "The GNU Name System (GNS) is secure and decentralized naming system. It " |