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