aboutsummaryrefslogtreecommitdiff
path: root/locale/messages.pot
diff options
context:
space:
mode:
Diffstat (limited to 'locale/messages.pot')
-rw-r--r--locale/messages.pot2941
1 files changed, 2941 insertions, 0 deletions
diff --git a/locale/messages.pot b/locale/messages.pot
index e69de29b..381e6906 100644
--- a/locale/messages.pot
+++ b/locale/messages.pot
@@ -0,0 +1,2941 @@
1# Translations template for PROJECT.
2# Copyright (C) 2021 ORGANIZATION
3# This file is distributed under the same license as the PROJECT project.
4# FIRST AUTHOR <EMAIL@ADDRESS>, 2021.
5#
6#, fuzzy
7msgid ""
8msgstr ""
9"Project-Id-Version: PROJECT VERSION\n"
10"Report-Msgid-Bugs-To: EMAIL@ADDRESS\n"
11"POT-Creation-Date: 2021-05-07 18:09+0200\n"
12"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
13"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
14"Language-Team: LANGUAGE <LL@li.org>\n"
15"MIME-Version: 1.0\n"
16"Content-Type: text/plain; charset=utf-8\n"
17"Content-Transfer-Encoding: 8bit\n"
18"Generated-By: Babel 2.9.0\n"
19
20#: common/base.j2:5 common/news.j2:5
21msgid "GNUnet"
22msgstr ""
23
24#: common/base.j2:6 common/news.j2:6
25msgid "GNU's framework for secure p2p networking"
26msgstr ""
27
28#: common/footer.j2.inc:7
29msgid "Contact"
30msgstr ""
31
32#: common/footer.j2.inc:8
33msgid "GNUnet e.V."
34msgstr ""
35
36#: common/footer.j2.inc:9 template/about.html.j2:6
37msgid "About GNUnet"
38msgstr ""
39
40#: common/footer.j2.inc:14 common/navigation.j2.inc:64
41msgid "Bug Tracker"
42msgstr ""
43
44#: common/footer.j2.inc:19 template/copyright.html.j2:6
45msgid "Copyright Assignment"
46msgstr ""
47
48#: common/footer.j2.inc:20 common/navigation.j2.inc:90
49#: template/developers.html.j2:24
50msgid "Bibliography"
51msgstr ""
52
53#: common/footer.j2.inc:31
54msgid "Source code of this site."
55msgstr ""
56
57#: common/footer.j2.inc:32
58msgid "Report issues with this website."
59msgstr ""
60
61#: common/navigation.j2.inc:38
62msgid "About"
63msgstr ""
64
65#: common/navigation.j2.inc:39 common/old-news.j2.inc:7
66#: template/news/index.html.j2:8
67msgid "News"
68msgstr ""
69
70#: common/navigation.j2.inc:40 template/index.html.j2:289
71msgid "Applications"
72msgstr ""
73
74#: common/navigation.j2.inc:44
75msgid "Community"
76msgstr ""
77
78#: common/navigation.j2.inc:47 template/index.html.j2:292
79msgid "Engage"
80msgstr ""
81
82#: common/navigation.j2.inc:48
83msgid "GSoC Projects"
84msgstr ""
85
86#: common/navigation.j2.inc:50
87msgid "Copyright for Contributors"
88msgstr ""
89
90#: common/navigation.j2.inc:51
91msgid "IRC Archive"
92msgstr ""
93
94#: common/navigation.j2.inc:58
95msgid "Development"
96msgstr ""
97
98#: common/navigation.j2.inc:61
99msgid "System Architecture"
100msgstr ""
101
102#: common/navigation.j2.inc:63 template/roadmap.html.j2:6
103msgid "Roadmap"
104msgstr ""
105
106#: common/navigation.j2.inc:65 template/gnurl.html.j2:186
107msgid "Source Code"
108msgstr ""
109
110#: common/navigation.j2.inc:66
111msgid "Source Code Documentation"
112msgstr ""
113
114#: common/navigation.j2.inc:67
115msgid "Continuous Integration"
116msgstr ""
117
118#: common/navigation.j2.inc:68
119msgid "Development Tutorial"
120msgstr ""
121
122#: common/navigation.j2.inc:79
123msgid "Documentation"
124msgstr ""
125
126#: common/navigation.j2.inc:82 template/install.html.j2:6
127msgid "Install"
128msgstr ""
129
130#: common/navigation.j2.inc:83 template/install-on-openwrt.html.j2:76
131msgid "Use"
132msgstr ""
133
134#: common/navigation.j2.inc:84
135msgid "Videos"
136msgstr ""
137
138#: common/navigation.j2.inc:85 template/glossary.html.j2:6
139msgid "Glossary"
140msgstr ""
141
142#: common/navigation.j2.inc:86
143msgid "Handbook"
144msgstr ""
145
146#: common/navigation.j2.inc:88
147msgid "REST API"
148msgstr ""
149
150#: common/navigation.j2.inc:89
151msgid "FAQ"
152msgstr ""
153
154#: common/old-news.j2.inc:10 template/news/index.html.j2:11
155msgid "News posts about changes related to GNUnet such as releases and events"
156msgstr ""
157
158#: common/old-news.j2.inc:15 template/news/index.html.j2:16
159msgid "subscribe to our RSS feed"
160msgstr ""
161
162#: common/old-news.j2.inc:34 template/news/index.html.j2:36
163msgid "read more"
164msgstr ""
165
166#: template/about.html.j2:11
167msgid "What is GNUnet?"
168msgstr ""
169
170#: template/about.html.j2:13
171msgid ""
172"GNUnet is an alternative network stack for building secure, decentralized"
173" and privacy-preserving distributed applications. Our goal is to replace "
174"the old insecure Internet protocol stack. Starting from an application "
175"for secure publication of files, it has grown to include all kinds of "
176"basic protocol components and applications towards the creation of a GNU "
177"internet."
178msgstr ""
179
180#: template/about.html.j2:23
181msgid ""
182"Today, the actual use and thus the social requirements for a global "
183"network differs widely from those goals of 1970. While the Internet "
184"remains suitable for military use, where the network equipment is "
185"operated by a command hierarchy and when necessary isolated from the rest"
186" of the world, the situation is less tenable for civil society."
187msgstr ""
188
189#: template/about.html.j2:32
190msgid ""
191"Due to fundamental Internet design choices, Internet traffic can be "
192"misdirected, intercepted, censored and manipulated by hostile routers on "
193"the network. And indeed, the modern Internet has evolved exactly to the "
194"point where, as Matthew Green put it, <a "
195"href=\"https://blog.cryptographyengineering.com/2015/08/16/the-network-"
196"is-hostile/\">\"the network is hostile\"</a>."
197msgstr ""
198
199#: template/about.html.j2:41
200msgid ""
201"We believe liberal societies need a network architecture that uses the "
202"anti-authoritarian decentralized peer-to-peer paradigm and privacy-"
203"preserving cryptographic protocols. The goal of the GNUnet project is to "
204"provide a Free Software realization of this ideal."
205msgstr ""
206
207#: template/about.html.j2:49
208msgid ""
209"Specifically, GNUnet tries to follow the following design principles, in "
210"order of importance:"
211msgstr ""
212
213#: template/about.html.j2:56
214msgid ""
215"GNUnet must be implemented as <a href=\"https://www.gnu.org/philosophy"
216"/free-sw.html\">Free Software</a>."
217msgstr ""
218
219#: template/about.html.j2:60
220msgid ""
221"GNUnet must minimize the amount of personally identifiable information "
222"exposed."
223msgstr ""
224
225#: template/about.html.j2:61
226msgid ""
227"GNUnet must be fully distributed and resilient to external attacks and "
228"rogue participants."
229msgstr ""
230
231#: template/about.html.j2:62
232msgid ""
233"GNUnet must be self-organizing and not depend on administrators or "
234"centralized infrastructure."
235msgstr ""
236
237#: template/about.html.j2:63
238msgid ""
239"GNUnet must inform the user which other participants have to be trusted "
240"when establishing private communications."
241msgstr ""
242
243#: template/about.html.j2:64
244msgid "GNUnet must be open and permit new peers to join."
245msgstr ""
246
247#: template/about.html.j2:65
248msgid "GNUnet must support a diverse range of applications and devices."
249msgstr ""
250
251#: template/about.html.j2:66
252msgid "GNUnet must use compartmentalization to protect sensitive information."
253msgstr ""
254
255#: template/about.html.j2:67
256msgid "The GNUnet architecture must be resource efficient."
257msgstr ""
258
259#: template/about.html.j2:68
260msgid ""
261"GNUnet must provide incentives for peers to contribute more resources "
262"than they consume."
263msgstr ""
264
265#: template/about.html.j2:72
266msgid ""
267"To get know and learn more, please check our <a "
268"href=\"https://docs.gnunet.org/handbook/gnunet.html\">handbook</a>, "
269"especially the <a href=\"https://docs.gnunet.org/handbook/gnunet.html"
270"#Key-Concepts\">chapter on \"Key Concepts\"</a>, explaining the "
271"fundamental concepts of GNUnet: <ul> <li><a "
272"href=\"https://docs.gnunet.org/handbook/gnunet.html#Authentication\">Authentication</a></li>"
273" <li><a href=\"https://docs.gnunet.org/handbook/gnunet.html#Accounting-"
274"to-Encourage-Resource-Sharing\">Accounting to Encourage Resource "
275"Sharing</a></li> <li><a "
276"href=\"https://docs.gnunet.org/handbook/gnunet.html#Confidentiality\">Confidentiality</a></li>"
277" <li><a "
278"href=\"https://docs.gnunet.org/handbook/gnunet.html#Anonymity\">Anonymity</a></li>"
279" <li><a "
280"href=\"https://docs.gnunet.org/handbook/gnunet.html#Deniability\">Deniability</a></li>"
281" <li><a href=\"https://docs.gnunet.org/handbook/gnunet.html#Peer-"
282"Identities\">Peer Identities</a></li> <li><a "
283"href=\"https://docs.gnunet.org/handbook/gnunet.html#Zones-in-the-GNU-"
284"Name-System-_0028GNS-Zones_0029\">Zones in the GNU Name System (GNS "
285"Zones)</a></li> <li><a "
286"href=\"https://docs.gnunet.org/handbook/gnunet.html#Egos\">Egos</a></li> "
287"</ul>"
288msgstr ""
289
290#: template/about.html.j2:88
291msgid "More Resources"
292msgstr ""
293
294#: template/about.html.j2:90
295msgid ""
296"There are many more resources to learn about GNUnet besides the <a "
297"href=\"https://docs.gnunet.org/handbook/gnunet.html\">handbook</a>, such "
298"as the <a href=\"https://bib.gnunet.org/\">bibliography</a> with papers "
299"covering the various layers, many <a "
300"href=\"https://gnunet.org/en/video.html\">videos</a> or a brief <a "
301"href=\"https://gnunet.org/en/glossary.html\">glossary</a>."
302msgstr ""
303
304#: template/about.html.j2:95
305msgid ""
306"You are most welcome to <a href=\"engage.html\">get engaged into the "
307"conversation</a>, <a href=\"install.html\">install GNUnet</a>, <a "
308"href=\"use.html\">use it</a> and <a href=\"engage.html\">contribute and "
309"get engaged</a> in various ways."
310msgstr ""
311
312#: template/about.html.j2:100
313msgid ""
314"Please be aware that this project is (despite of it's age) still in an "
315"early alpha stage when it comes to software &#8211; its not an easy task "
316"to rewrite the whole Internet!"
317msgstr ""
318
319#: template/about.html.j2:105
320msgid "Current funding"
321msgstr ""
322
323#: template/about.html.j2:110
324msgid ""
325"We're receiving funding from NLnet's Next Generation Internet funding "
326"line to document and implement the GNU Name System protocol in a way "
327"suitable for the IETF standardization process."
328msgstr ""
329
330#: template/about.html.j2:123
331msgid ""
332"This project has received funding from the European Union’s Horizon 2020 "
333"research and innovation programme under the NGI_TRUST grant agreement no "
334"825618. The project aims to integrate re:claimID with the GNU Taler "
335"payment system in a pilot in order to demonstrate the practical "
336"feasibility and benefits of privacy enhancing technologies for users and "
337"commercial service providers. The project is called \"Decentralized "
338"Identities for Self-Sovereign End-users\" (DISSENS)."
339msgstr ""
340
341#: template/about.html.j2:141
342msgid "We are grateful for free hosting offered by the following organizations:"
343msgstr ""
344
345#: template/about.html.j2:150
346msgid "Past funding"
347msgstr ""
348
349#: template/about.html.j2:152
350msgid "We are grateful for past funding from the following organizations:"
351msgstr ""
352
353#: template/applications.html.j2:7
354msgid "Applications provided by GNUnet"
355msgstr ""
356
357#: template/applications.html.j2:13 template/gns.html.j2:7
358msgid "The GNU Name System"
359msgstr ""
360
361#: template/applications.html.j2:15
362msgid ""
363"The <a href=\"gns.html\">GNU Name System (GNS)</a> is a fully "
364"decentralized replacement for the Domain Name System (DNS). Instead of "
365"using a hierarchy, GNS uses a directed graph. Naming conventions are "
366"similar to DNS, but queries and replies are private even with respect to "
367"peers providing the answers. The integrity of records and privacy of "
368"look-ups are cryptographically secured. <!-- Too technical: GNS "
369"integrates a robust, efficient and instant key revocation mechanism. -->"
370msgstr ""
371
372#: template/applications.html.j2:38
373msgid "Self-sovereign, decentralized identity provider"
374msgstr ""
375
376#: template/applications.html.j2:40
377msgid ""
378"<a href=\"https://reclaim.gnunet.org/\">re:claimID</a> is a decentralized"
379" Identity Provider (IdP) service built in top of the GNU Name System. It "
380"allows users to securely share personal information with websites using "
381"standardized protocols (OpenID Connect)."
382msgstr ""
383
384#: template/applications.html.j2:57
385msgid "Filesharing (Alpha)"
386msgstr ""
387
388#: template/applications.html.j2:59
389msgid ""
390"GNUnet <a href=\"use.html#fs\">filesharing</a> is an application that "
391"aims to provide censorship-resistant, anonymous filesharing. The "
392"publisher is empowered to make a gradual choice between performance and "
393"anonymity."
394msgstr ""
395
396#: template/applications.html.j2:73
397msgid "Conversation (Pre-Alpha)"
398msgstr ""
399
400#: template/applications.html.j2:75
401msgid ""
402"GNUnet conversation is an application that provides secure voice "
403"communication in a fully decentralized way by employing GNUnet for "
404"routing and transport."
405msgstr ""
406
407#: template/applications.html.j2:91
408msgid "Applications utilizing GNUnet"
409msgstr ""
410
411#: template/applications.html.j2:97
412msgid "GNU Taler (Alpha)"
413msgstr ""
414
415#: template/applications.html.j2:99
416msgid ""
417"<a href=\"https://taler.net/\">GNU Taler</a> is a new privacy-preserving "
418"electronic payment system. Payments are cryptographically secured and are"
419" confirmed within milliseconds with extremely low transaction costs."
420msgstr ""
421
422#: template/applications.html.j2:118
423msgid "secushare"
424msgstr ""
425
426#: template/applications.html.j2:120
427msgid ""
428"<a href=\"https://secushare.org/\">secushare</a> is creating a "
429"decentralized social networking application on top of GNUnet. Using "
430"overlay multicast and the extensible PSYC protocol, notifications are "
431"distributed end-to-end encrypted to authorized recipients only."
432msgstr ""
433
434#: template/applications.html.j2:139
435msgid "pretty Easy privacy"
436msgstr ""
437
438#: template/applications.html.j2:141
439msgid ""
440"<a href=\"https://pep.foundation/\">pretty Easy privacy</a> (p&#8801;p) "
441"is creating a usable end-to-end encrypted e-mail solution using "
442"opportunistic key exchange. p&#8801;p will use GNUnet to protect metadata"
443" and exploit new cryptographic protocols to verify keys."
444msgstr ""
445
446#: template/applications.html.j2:160
447msgid "Cadet-GTK"
448msgstr ""
449
450#: template/applications.html.j2:162
451msgid ""
452"<a href=\"https://gitlab.com/gnunet-messenger/cadet-gtk\">Cadet-GTK</a> "
453"is a convenient but feature-rich graphical application providing "
454"messaging using the CADET subsystem. It is developed using GTK and "
455"libhandy for a convergent design."
456msgstr ""
457
458#: template/applications.html.j2:180
459msgid "groupchat"
460msgstr ""
461
462#: template/applications.html.j2:182
463msgid ""
464"<a href=\"https://git.gnunet.org/groupchat.git/\">groupchat</a> is a "
465"terminal user interface providing messaging using the CADET subsystem. It"
466" is developed using nim. Cadet-GTK and groupchat are planned to be "
467"compatible."
468msgstr ""
469
470#: template/architecture.html.j2:6
471msgid "GNUnet System Architecture"
472msgstr ""
473
474#: template/architecture.html.j2:20
475msgid "Foundations"
476msgstr ""
477
478#: template/architecture.html.j2:22
479msgid ""
480"The foundations of GNUnet are a distributed hash table (R5N), an SCTP-"
481"like end-to-end encrypted messaging layer (CADET), a public key "
482"infrastructure (GNS) and a pluggable transport system (TRANSPORT).<br> "
483"Using public keys for addresses and self-organizing decentralized routing"
484" algorithms, these subsystems replace the traditional TCP/IP stack."
485msgstr ""
486
487#: template/architecture.html.j2:35
488msgid "Security"
489msgstr ""
490
491#: template/architecture.html.j2:38
492msgid ""
493"GNUnet is implemented using a multi-process architecture. Each subsystem "
494"runs as a separate process, providing fault isolation and enabling tight "
495"permissions to be granted to each subsystem. Naturally, the "
496"implementation is a <a href=\"https://www.gnu.org/\">GNU</a> package, and"
497" will always remain free software."
498msgstr ""
499
500#: template/architecture.html.j2:52
501msgid "System architecture"
502msgstr ""
503
504#: template/architecture.html.j2:58
505msgid "Subsystems"
506msgstr ""
507
508#: template/architecture.html.j2:67
509msgid "libgnunetutil"
510msgstr ""
511
512#: template/architecture.html.j2:73
513msgid "APIs"
514msgstr ""
515
516#: template/architecture.html.j2:86
517msgid "Legend"
518msgstr ""
519
520#: template/contact.html.j2:6
521msgid "Contact information"
522msgstr ""
523
524#: template/contact.html.j2:11
525msgid "The mailing list"
526msgstr ""
527
528#: template/contact.html.j2:13
529msgid ""
530"An archived, public mailing list for GNUnet is hosted at <a "
531"href=\"https://lists.gnu.org/mailman/listinfo/gnunet-"
532"developers\">https://lists.gnu.org/mailman/listinfo/gnunet-"
533"developers</a>. You can send messages to the list at <a href=\"mailto"
534":gnunet-developers@gnu.org\">gnunet-developers@gnu.org</a>."
535msgstr ""
536
537#: template/contact.html.j2:23
538msgid "The IRC channel"
539msgstr ""
540
541#: template/contact.html.j2:25
542msgid ""
543"<tt>#gnunet</tt> is reachable via <a "
544"href=\"https://freenode.net\">irc.freenode.net</a>. There is also an <a "
545"href=\"https://view.matrix.org/room/!IjaAfLiruzjxFFzKAV:matrix.org/\">archive</a>"
546" available."
547msgstr ""
548
549#: template/contact.html.j2:38
550msgid "Contacting individuals"
551msgstr ""
552
553#: template/contact.html.j2:40
554msgid ""
555"GNUnet developers are generally reachable at either "
556"<tt>PSEUDONYM@gnunet.org</tt> or <tt>LASTNAME@gnunet.org</tt>. Most of us"
557" support receiving GnuPG encrypted Emails. Urgent and sensitive security "
558"issues may be addressed to the GNU maintainers <tt>schanzen</tt> and "
559"<tt>grothoff</tt>."
560msgstr ""
561
562#: template/contact.html.j2:53
563msgid "Reporting bugs"
564msgstr ""
565
566#: template/contact.html.j2:55
567msgid ""
568"We track open feature requests and bugs for projects within GNUnet in our"
569" <a href=\"https://bugs.gnunet.org/\">Bug tracker</a>. You can also "
570"report bugs or feature requests to the <a "
571"href=\"https://lists.gnu.org/mailman/listinfo/bug-gnunet\">bug-gnunet</a>"
572" mailing list. The mailinglist requires no subscription."
573msgstr ""
574
575#: template/copyright.html.j2:11
576msgid ""
577"<p> Contributors to GNUnet with Git access must sign the <a "
578"href=\"/static/pdf/copyright.pdf\">copyright assignment</a> to ensure "
579"that the <a href=\"https://git.gnunet.org/gnunet-"
580"ev.git/tree/gnunet_taler_agreement.tex\">GNUnet e.V. --- Taler Systems SA"
581" agreement on licensing and collaborative development</a> of the GNUnet "
582"and GNU Taler projects is satisfied. </p>"
583msgstr ""
584
585#: template/copyright.html.j2:22
586msgid ""
587"<p>The agreements ensure that the code will continue to be made available"
588" under free software licenses, but gives developers the freedom to move "
589"code between GNUnet and GNU Taler without worrying about licenses and to "
590"give the company the ability to dual-license (for example, so that we can"
591" distribute via App-stores that are hostile to free software).</p>"
592msgstr ""
593
594#: template/copyright.html.j2:30
595msgid ""
596"<p>Minor contributions (basically, anyone without Git access) do not "
597"require copyright assignment. Pseudonymous contributions are accepted, in"
598" this case simply sign the agreement with your pseudonym. Scanned copies "
599"are sufficient, but snail mail is preferred.</p>"
600msgstr ""
601
602#: template/developers.html.j2:5
603msgid "GNUnet for developers"
604msgstr ""
605
606#: template/developers.html.j2:13
607msgid "Repositories"
608msgstr ""
609
610#: template/developers.html.j2:16
611msgid ""
612"A list of our Git repositories can be found on our our <a "
613"href=\"https://git.gnunet.org/\">Git Server</a>."
614msgstr ""
615
616#: template/developers.html.j2:27
617msgid ""
618"Technical papers can be found in our <a "
619"href=\"https://old.gnunet.org/bibliography\">bibliography</a>."
620msgstr ""
621
622#: template/developers.html.j2:34
623msgid "Discussion"
624msgstr ""
625
626#: template/developers.html.j2:37
627msgid ""
628"We have a mailing list for developer discussions. You can subscribe to or"
629" read the list archive at <a href=\"http://lists.gnu.org/mailman/listinfo"
630"/gnunet-developers\">http://lists.gnu.org/mailman/listinfo/gnunet-"
631"developers</a>."
632msgstr ""
633
634#: template/developers.html.j2:47
635msgid "Regression Testing"
636msgstr ""
637
638#: template/developers.html.j2:50
639msgid ""
640"We have <a href=\"https://buildbot.net/\">Buildbot</a> automation tests "
641"to detect regressions and check for portability at <a "
642"href=\"https://old.gnunet.org/buildbot/gnunet/\">https://old.gnunet.org/buildbot/gnunet/</a>."
643msgstr ""
644
645#: template/developers.html.j2:59
646msgid "Code Coverage Analysis"
647msgstr ""
648
649#: template/developers.html.j2:62
650msgid ""
651"We use <a href=\"http://ltp.sourceforge.net/coverage/lcov.php\">LCOV</a> "
652"to analyze the code coverage of our tests, the results are available at "
653"<a "
654"href=\"https://old.gnunet.org/coverage/\">https://old.gnunet.org/coverage/</a>."
655msgstr ""
656
657#: template/developers.html.j2:72
658msgid "Performance Analysis"
659msgstr ""
660
661#: template/developers.html.j2:75
662msgid ""
663"We use <a href=\"https://old.gnunet.org/gauger\">Gauger</a> for "
664"performance regression analysis of the exchange backend at <a "
665"href=\"https://old.gnunet.org/gauger/\">https://old.gnunet.org/gauger/</a>."
666msgstr ""
667
668#: template/download.html.j2:7 template/gnurl.html.j2:209
669msgid "Downloads"
670msgstr ""
671
672#: template/download.html.j2:11
673msgid ""
674"Here you can download releases of our software and find links to the "
675"various versions."
676msgstr ""
677
678#: template/download.html.j2:17
679msgid "0.11.x series"
680msgstr ""
681
682#: template/download.html.j2:18
683msgid "tarball"
684msgstr ""
685
686#: template/download.html.j2:20
687msgid ""
688"The tarball of the latest version can be obtained from GNU FTP and its "
689"mirrors."
690msgstr ""
691
692#: template/download.html.j2:30
693msgid "git"
694msgstr ""
695
696#: template/download.html.j2:32
697msgid "You can fetch the git tag of version 0.11.x from our development server:"
698msgstr ""
699
700#: template/engage.html.j2:6
701msgid "Engage!"
702msgstr ""
703
704#: template/ev.html.j2:6
705msgid "Verein zur F&ouml;rderung von GNUnet e.V."
706msgstr ""
707
708#: template/ev.html.j2:11
709msgid "About GNUnet e.V."
710msgstr ""
711
712#: template/ev.html.j2:13
713msgid ""
714"On December 27th 2013 a group of GNUnet hackers met at 30c3 to create the"
715" \"Verein zur F&ouml;rderung von GNUnet e.V.\", an association under "
716"German law to support GNUnet development. The Amtsgericht M&uuml;nchen "
717"registered the association on the 7th of March under VR 205287."
718msgstr ""
719
720#: template/ev.html.j2:22
721msgid ""
722"The association is officially dedicated to supporting research, "
723"development and education in the area of secure decentralized networking "
724"in general, and GNUnet specifically. This is the official website for the"
725" association."
726msgstr ""
727
728#: template/ev.html.j2:31
729msgid "Becoming a Member of GNUnet e.V."
730msgstr ""
731
732#: template/ev.html.j2:33
733msgid ""
734"GNUnet developers with git (write) access can become members to "
735"participate in the decision process and formally support GNUnet e.V. For "
736"this, all you have to do is update the <tt>members.txt</tt> file in the "
737"<a href=\"https://git.gnunet.org/gnunet-ev.git/\">gnunet-ev</a> "
738"repository. There are no membership dues; however, members are required "
739"to support GNUnet e.V. and in particularly contribute to the technical "
740"development within their means. For further details, we refer to the <a "
741"href=\"https://git.gnunet.org/gnunet-ev.git/\">Satzung (Charter)</a> "
742"(currently only available in German, translations welcome)."
743msgstr ""
744
745#: template/ev.html.j2:52
746msgid "Governance"
747msgstr ""
748
749#: template/ev.html.j2:54
750msgid ""
751"You can find our charter, and the list of members under <a "
752"href=\"https://git.gnunet.org/gnunet-"
753"ev.git/tree/satzung.tex\">https://git.gnunet.org/gnunet-"
754"ev.git/tree/satzung.tex</a>. The current board consists of: "
755"<dl><dt>Vorsitz</dt> <dd><a href=\"https://schanzen.eu\">Martin "
756"Schanzenbach</a></dd> <dt>stellvertretender Vorsitz</dt> "
757"<dd>t3sserakt</dd> <dt>Kassenwart</dt> <dd>Florian Dold</dd> "
758"<dt>Beisitzer</dt> <dd> <a "
759"href=\"https://grothoff.org/christian/\">Christian Grothoff</a>, ch3 "
760"</dd> </dl>"
761msgstr ""
762
763#: template/ev.html.j2:73
764msgid "Official Meeting Notes"
765msgstr ""
766
767#: template/ev.html.j2:86
768msgid "Support Us!"
769msgstr ""
770
771#: template/ev.html.j2:88
772msgid ""
773"Everybody is welcome to support us via donations. For financial "
774"contributions, Europeans are able to donate via SEPA. We hope to setup "
775"accounts in other major currency areas in the future. You can also donate"
776" via Bitcoin, routing details are given below. Please note that we are "
777"unable to provide receipts for your donations. If you are planning to "
778"donate a significant amount of money, please contact us first as it might"
779" be better to come to a custom arrangement. <dl><dt>BitCoin</dt> "
780"<dd>1GNUnetpWeR9Zs3vipdvVywo1GseeksjUh</dd> <dt>SEPA/IBAN</dt> "
781"<dd>DE67830654080004822650 (BIC/SWIFT: GENODEF1SLR)</dd> </dl>"
782msgstr ""
783
784#: template/faq.html.j2:12 template/faq.html.j2:23
785msgid "General"
786msgstr ""
787
788#: template/faq.html.j2:13 template/faq.html.j2:149 template/gns.html.j2:37
789msgid "Features"
790msgstr ""
791
792#: template/faq.html.j2:15 template/faq.html.j2:695
793msgid "Error messages"
794msgstr ""
795
796#: template/faq.html.j2:16 template/faq.html.j2:797
797msgid "File-sharing"
798msgstr ""
799
800#: template/faq.html.j2:17 template/faq.html.j2:973
801msgid "Contributing"
802msgstr ""
803
804#: template/faq.html.j2:26
805msgid "What do I do if my question is not answered here?"
806msgstr ""
807
808#: template/faq.html.j2:28
809msgid ""
810"A: There are many other sources of information. You can read additional "
811"documentation or ask the question on the help-gnunet@gnu.org mailing list"
812" or the #gnunet IRC on irc.freenode.net."
813msgstr ""
814
815#: template/faq.html.j2:36
816msgid "When are you going to release the next version?"
817msgstr ""
818
819#: template/faq.html.j2:38
820msgid ""
821"A: The general answer is, when it is ready. A better answer may be: "
822"earlier if you contribute (test, debug, code, document). Every release "
823"will be anounced on the info-gnunet@gnu.org mailing list and on <a "
824"href=\"https://planet.gnu.org\">planet GNU</a>. You can subscribe to the "
825"mailing list or the RSS feed of this site to automatically receive a "
826"notification."
827msgstr ""
828
829#: template/faq.html.j2:49
830msgid "Is the code free?"
831msgstr ""
832
833#: template/faq.html.j2:51
834msgid ""
835"A: GNUnet is free software, available under the <a "
836"href=\"https://www.gnu.org/licenses/agpl-3.0.en.html\">GNU Affero Public "
837"License (AGPL)</a>."
838msgstr ""
839
840#: template/faq.html.j2:58
841msgid "Are there any known bugs?"
842msgstr ""
843
844#: template/faq.html.j2:60
845msgid ""
846"A: We track the list of currently known bugs in the <a "
847"href=\"https://bugs.gnunet.org/\">Mantis system</a>. Some bugs are "
848"occasionally reported directly to developers or the developer mailing "
849"list. This is discouraged since developers often do not have the time to "
850"feed these bugs back into the Mantis database. Please report bugs "
851"directly to the bug tracking system. If you believe a bug is sensitive, "
852"you can set its view status to private (this should be the exception)."
853msgstr ""
854
855#: template/faq.html.j2:73 template/faq.html.j2:193
856msgid "Is there a graphical user interface?"
857msgstr ""
858
859#: template/faq.html.j2:75
860msgid ""
861"A: gnunet-gtk is a separate download. The package contains various GTK+ "
862"based graphical interfaces, including a graphical tool for configuration."
863msgstr ""
864
865#: template/faq.html.j2:83
866msgid "Why does gnunet-service-nse create a high CPU load?"
867msgstr ""
868
869#: template/faq.html.j2:85
870msgid ""
871"A: The gnunet-service-nse process will initially compute a so-called "
872"&quot;proof-of-work&quot; which is used to convince the network that your"
873" peer is real (or, rather, make it expensive for an adversary to mount a "
874"Sybil attack on the network size estimator). The calculation is expected "
875"to take a few days, depending on how fast your CPU is. If the CPU load is"
876" creating a problem for you, you can set the value &quot;WORKDELAY&quot; "
877"in the &quot;nse&quot; section of your configuration file to a higher "
878"value. The default is &quot;5 ms&quot;."
879msgstr ""
880
881#: template/faq.html.j2:99
882msgid "How does GNUnet compare to Tor?"
883msgstr ""
884
885#: template/faq.html.j2:101
886msgid ""
887"A: Tor focuses on anonymous communication and censorship-resistance for "
888"TCP connections and, with the Tor Browser Bundle, for the Web in "
889"particular. GNUnet does not really have one focus; our theme is secure "
890"decentralized networking, but that is too broad to be called a focus."
891msgstr ""
892
893#: template/faq.html.j2:111
894msgid "How does GNUnet compare to I2P?"
895msgstr ""
896
897#: template/faq.html.j2:113
898msgid ""
899"A: Both GNUnet and I2P want to build a better, more secure, more "
900"decentralized Internet. However, on the technical side, there are almost "
901"no overlaps. <br><br> I2P is written in Java, and has (asymmetric) "
902"tunnels using onion (or garlic) routing as the basis for various "
903"(anonymized) applications. I2P is largely used via a Web frontend."
904msgstr ""
905
906#: template/faq.html.j2:124
907msgid "Is GNUnet ready for use on production systems?"
908msgstr ""
909
910#: template/faq.html.j2:126
911msgid ""
912"A: GNUnet is still undergoing major development. It is largely not yet "
913"ready for usage beyond developers. Your mileage will vary depending on "
914"the functionality you use, but you will always likely run into issues "
915"with our current low-level transport system. We are currently in the "
916"process of rewriting it (Project &quot;Transport Next Generation "
917"[TNG]&quot;)"
918msgstr ""
919
920#: template/faq.html.j2:136
921msgid "Is GNUnet build using distributed ledger technologies?"
922msgstr ""
923
924#: template/faq.html.j2:138
925msgid ""
926"A: No. GNUnet is a new network protocol stack for building secure, "
927"distributed, and privacy-preserving applications. While a ledger could be"
928" built using GNUnet, we currently have no plans in doing so."
929msgstr ""
930
931#: template/faq.html.j2:151
932msgid "What can I do with GNUnet?"
933msgstr ""
934
935#: template/faq.html.j2:153
936msgid ""
937"A: GNUnet is a peer-to-peer framework, by which we mostly mean that it "
938"can do more than just one thing. Naturally, the implementation and "
939"documentation of some of the features that exist are more advanced than "
940"others."
941msgstr ""
942
943#: template/faq.html.j2:160
944msgid ""
945"For users, GNUnet offers anonymous and non-anonymous file-sharing, a "
946"fully decentralized and censorship-resistant replacement for DNS and a "
947"mechanism for IPv4-IPv6 protocol translation and tunneling (NAT-PT with "
948"DNS-ALG)."
949msgstr ""
950
951#: template/faq.html.j2:171
952msgid "Is it possible to surf the WWW anonymously with GNUnet?"
953msgstr ""
954
955#: template/faq.html.j2:173
956msgid ""
957"A: It is not possible use GNUnet for anonymous browsing at this point. We"
958" recommend that you use Tor for anonymous surfing."
959msgstr ""
960
961#: template/faq.html.j2:181
962msgid "Is it possible to access GNUnet via a browser as an anonymous WWW?"
963msgstr ""
964
965#: template/faq.html.j2:183
966msgid ""
967"A: There is currently no proxy (like fproxy in Freenet) for GNUnet that "
968"would make it accessible via a browser. It is possible to build such a "
969"proxy and all one needs to know is the protocol used between the browser "
970"and the proxy and the GNUnet code for file-sharing."
971msgstr ""
972
973#: template/faq.html.j2:195
974msgid ""
975"A: There are actually a few graphical user interfaces for different "
976"functions. gnunet-setup is to configure GNUnet, and gnunet-fs-gtk is for "
977"file-sharing. There are a few other gnunet-XXX-gtk GUIs of lesser "
978"importance. Note that in order to obtain the GUI, you need to install the"
979" gnunet-gtk package, which is a separate download. gnunet-gtk is a meta "
980"GUI that integrates most of the other GUIs in one window. One exception "
981"is gnunet-setup, which must still be run separately at this time (as "
982"setup requires the peer to be stopped)."
983msgstr ""
984
985#: template/faq.html.j2:210
986msgid "Which operating systems does GNUnet run on?"
987msgstr ""
988
989#: template/faq.html.j2:212
990msgid ""
991"A: GNUnet is being developed and tested primarily under Debian GNU/Linux."
992" Furthermore, we regularly build and test GNUnet on Fedora, Ubuntu, Arch,"
993" FreeBSD and macOS. We have reports of working versions on many other "
994"GNU/Linux distributions; in the past we had reports of working versions "
995"on NetBSD, OpenBSD and Solaris. However, not all of those reports are "
996"recent, so if you cannot get GNUnet to work on those systems please let "
997"us know."
998msgstr ""
999
1000#: template/faq.html.j2:228
1001msgid "Who runs the GNS root zone?"
1002msgstr ""
1003
1004#: template/faq.html.j2:230
1005msgid ""
1006"A: Short answer: you. The long answer is the GNUnet will ship with a "
1007"default configuration of top-level domains. The governance of this "
1008"default configuration is not yet established. In any case, the user will "
1009"be able to modify this configuration at will. We expect normal users to "
1010"have no need to edit their own GNS zone(s) unless they host services "
1011"themselves."
1012msgstr ""
1013
1014#: template/faq.html.j2:241
1015msgid "Where is the per-user GNS database kept?"
1016msgstr ""
1017
1018#: template/faq.html.j2:243
1019msgid ""
1020"A: The short answer is that the database is kept at the user's GNUnet "
1021"peer. Now, a user may run multiple GNUnet peers, in which case the "
1022"database could be kept at each peer (however, we don't have code for "
1023"convenient replication). Similarly, multiple GNUnet peers can share one "
1024"instance of the database --- the &quot;gnunet-service-namestore&quot; can"
1025" be accessed from remote (via TCP). The actual data can be stored in a "
1026"Postgres database, for which various replication options are again "
1027"applicable. Ultimately, there are many options for how users can store "
1028"(and secure) their GNS database."
1029msgstr ""
1030
1031#: template/faq.html.j2:258
1032msgid "What is the expected average size of a GNS namestore database?"
1033msgstr ""
1034
1035#: template/faq.html.j2:260
1036msgid ""
1037"A: Pretty small. Based on our user study where we looked at browser "
1038"histories and the number of domains visited, we expect that GNS databases"
1039" will only grow to a few tens of thousands of entries, small enough to "
1040"fit even on mobile devices."
1041msgstr ""
1042
1043#: template/faq.html.j2:270
1044msgid "Is GNS resistant to the attacks on DNS used by the US?"
1045msgstr ""
1046
1047#: template/faq.html.j2:272
1048msgid ""
1049"A: We believe so, as there is no entity that any government could force "
1050"to change the mapping for a name except for each individual user (and "
1051"then the changes would only apply to the names that this user is the "
1052"authority for). So if everyone used GNS, the only practical attack of a "
1053"government would be to force the operator of a server to change the GNS "
1054"records for his server to point elsewhere. However, if the owner of the "
1055"private key for a zone is unavailable for enforcement, the respective "
1056"zone cannot be changed and any other zone delegating to this zone will "
1057"achieve proper resolution."
1058msgstr ""
1059
1060#: template/faq.html.j2:286
1061msgid "How does GNS compare to other name systems?"
1062msgstr ""
1063
1064#: template/faq.html.j2:288
1065msgid ""
1066"A: A scientific paper on this topic <a "
1067"href=\"https://grothoff.org/christian/ns2018.pdf\">has been published "
1068"</a> and below is a table from the publication. For detailed descriptions"
1069" please refer to the paper."
1070msgstr ""
1071
1072#: template/faq.html.j2:392
1073msgid "What is the difference between GNS and CoDoNS?"
1074msgstr ""
1075
1076#: template/faq.html.j2:394
1077msgid ""
1078"A: CoDoNS decentralizes the DNS database (using a DHT) but preserves the "
1079"authority structure of DNS. With CoDoNS, IANA/ICANN are still in charge, "
1080"and there are still registrars that determine who owns a name. <br><br> "
1081"With GNS, we decentralize the database and also decentralize the "
1082"responsibility for naming: each user runs their own personal root zone "
1083"and is thus in complete control of the names they use. GNS also has many "
1084"additional features (to keep names short and enable migration) which "
1085"don't even make sense in the context of CoDoNS."
1086msgstr ""
1087
1088#: template/faq.html.j2:410
1089msgid "What is the difference between GNS and SocialDNS?"
1090msgstr ""
1091
1092#: template/faq.html.j2:412
1093msgid ""
1094"A: Like GNS, SocialDNS allows each user to create DNS mappings. However, "
1095"with SocialDNS the mappings are shared through the social network and "
1096"subjected to ranking. As the social relationships evolve, names can thus "
1097"change in surprising ways. <br><br> With GNS, names are primarily shared "
1098"via delegation, and thus mappings will only change if the user "
1099"responsible for the name (the authority) manually changes the record."
1100msgstr ""
1101
1102#: template/faq.html.j2:426
1103msgid "What is the difference between GNS and ODDNS?"
1104msgstr ""
1105
1106#: template/faq.html.j2:428
1107msgid ""
1108"A: ODDNS is primarily designed to bypass the DNS root zone and the TLD "
1109"registries (such as those for \".com\" and \".org\"). Instead of using "
1110"those, each user is expected to maintain a database of (second-level) "
1111"domains (like \"gnu.org\") and the IP addresses of the respective name "
1112"servers. Resolution will fail if the target name servers change IPs."
1113msgstr ""
1114
1115#: template/faq.html.j2:439
1116msgid "What is the difference between GNS and Handshake?"
1117msgstr ""
1118
1119#: template/faq.html.j2:441
1120msgid ""
1121"A: Handshake is a blockchain-based method for root zone governance. "
1122"Hence, it does not address the name resolution process itself but "
1123"delegates resolution into DNS after the initial TLD resolution. Not "
1124"taking sustainablility considerations into account, Handshake could be "
1125"used as an additional supporting GNS root zone governance model, but we "
1126"currently do not have such plans in mind."
1127msgstr ""
1128
1129#: template/faq.html.j2:453
1130msgid "What is the difference between GNS and TrickleDNS?"
1131msgstr ""
1132
1133#: template/faq.html.j2:455
1134msgid ""
1135"A: TrickleDNS pushes (&quot;critical&quot;) DNS records between DNS "
1136"resolvers of participating domains to provide &quot;better availability, "
1137"lower query resolution times, and faster update propagation&quot;. Thus "
1138"TrickleDNS is focused on defeating attacks on the availability (and "
1139"performance) of record propagation in DNS, for example via DDoS attacks "
1140"on DNS root servers. TrickleDNS is thus concerned with how to ensure "
1141"distribution of authoritative records, and authority remains derived from"
1142" the DNS hierarchy."
1143msgstr ""
1144
1145#: template/faq.html.j2:468
1146msgid ""
1147"Does GNS require real-world introduction (secure PKEY exchange) in the "
1148"style of the PGP web of trust?"
1149msgstr ""
1150
1151#: template/faq.html.j2:470
1152msgid ""
1153"A: For security, it is well known that an initial trust path between the "
1154"two parties must exist. However, for applications where this is not "
1155"required, weaker mechanisms can be used. For example, we have implemented"
1156" a first-come-first-served (FCFS) authority which allows arbitrary users "
1157"to register arbitrary names. The key of this authority is included with "
1158"every GNUnet installation. Thus, any name registered with FCFS is in fact"
1159" global and requires no further introduction. However, the security of "
1160"these names depends entirely on the trustworthiness of the FCFS "
1161"authority. The authority can be queried under the &quot;.pin&quot; TLD."
1162msgstr ""
1163
1164#: template/faq.html.j2:485
1165msgid ""
1166"How can a legitimate domain owner tell other people to not use his name "
1167"in GNS?"
1168msgstr ""
1169
1170#: template/faq.html.j2:487
1171msgid ""
1172"A: Names have no owners in GNS, so there cannot be a "
1173"&quot;legitimate&quot; domain owner. Any user can claim any name (as his "
1174"preferred name or &quot;pseudonym&quot;) in his NICK record. Similarly, "
1175"all other users can choose to ignore this preference and use a name of "
1176"their choice (or even assign no name) for this user."
1177msgstr ""
1178
1179#: template/faq.html.j2:498
1180msgid ""
1181"Did you consider the privacy implications of making your personal GNS "
1182"zone visible?"
1183msgstr ""
1184
1185#: template/faq.html.j2:500
1186msgid ""
1187"A: Each record in GNS has a flag &quot;private&quot;. Records are shared "
1188"with other users (via DHT or zone transfers) only if this flag is not "
1189"set. Thus, users have full control over what information about their "
1190"zones is made public."
1191msgstr ""
1192
1193#: template/faq.html.j2:510
1194msgid "Are \"Legacy Host\" (LEHO) records not going to be obsolete with IPv6?"
1195msgstr ""
1196
1197#: template/faq.html.j2:512
1198msgid ""
1199"A: The question presumes that (a) virtual hosting is only necessary "
1200"because of IPv4 address scarcity, and (b) that LEHOs are only useful in "
1201"the context of virtual hosting. However, LEHOs are also useful to help "
1202"with X.509 certificate validation (as they specify for which legacy "
1203"hostname the certificate should be valid). Also, even with IPv6 fully "
1204"deployed and &quot;infinite&quot; IP addresses being available, we're not"
1205" sure that virtual hosting would disappear. Finally, we don't want to "
1206"have to wait for IPv6 to become commonplace, GNS should work with today's"
1207" networks."
1208msgstr ""
1209
1210#: template/faq.html.j2:526
1211msgid ""
1212"Why does GNS not use a trust metric or consensus to determine globally "
1213"unique names?"
1214msgstr ""
1215
1216#: template/faq.html.j2:528
1217msgid ""
1218"A: Trust metrics have the fundamental problem that they have thresholds. "
1219"As trust relationships evolve, mappings would change their meaning as "
1220"they cross each others thresholds. We decided that the resulting "
1221"unpredictability of the resolution process was not acceptable. "
1222"Furthermore, trust and consensus might be easy to manipulate by "
1223"adversaries."
1224msgstr ""
1225
1226#: template/faq.html.j2:539
1227msgid "How do you handle compromised zone keys in GNS?"
1228msgstr ""
1229
1230#: template/faq.html.j2:541
1231msgid ""
1232"A: The owner of a private key can create a revocation message. This one "
1233"can then be flooded throughout the overlay network, creating a copy at "
1234"all peers. Before using a public key, peers check if that key has been "
1235"revoked. All names that involve delegation via a revoked zone will then "
1236"fail to resolve. Peers always automatically check for the existence of a "
1237"revocation message when resolving names."
1238msgstr ""
1239
1240#: template/faq.html.j2:553
1241msgid "Could the signing algorithm of GNS be upgraded in the future?"
1242msgstr ""
1243
1244#: template/faq.html.j2:555
1245msgid ""
1246"A: Yes. In our efforts to standardize GNS, we have already modified the "
1247"protocol to support alternative delegation records. <br> <br> Naturally, "
1248"deployed GNS implementations would have to be updated to support the new "
1249"signature scheme. The new scheme can then be run in parallel with the "
1250"existing system by using a new record type to indicate the use of a "
1251"different cipher system."
1252msgstr ""
1253
1254#: template/faq.html.j2:569
1255msgid "How can a GNS zone maintain several name servers, e.g. for load balancing?"
1256msgstr ""
1257
1258#: template/faq.html.j2:571
1259msgid ""
1260"A: We don't expect this to be necessary, as GNS records are stored (and "
1261"replicated) in the R5N DHT. Thus the authority will typically not be "
1262"contacted whenever clients perform a lookup. Even if the authority goes "
1263"(temporarily) off-line, the DHT will cache the records for some time. "
1264"However, should having multiple servers for a zone be considered truly "
1265"necessary, the owner of the zone can simply run multiple peers (and share"
1266" the zone's key and database among them)."
1267msgstr ""
1268
1269#: template/faq.html.j2:584
1270msgid ""
1271"Why do you believe it is worth giving up unique names for censorship "
1272"resistance?"
1273msgstr ""
1274
1275#: template/faq.html.j2:586
1276msgid ""
1277"A: The GNU Name system offers an alternative to DNS that is censorship "
1278"resistant. As with any security mechanism, this comes at a cost (names "
1279"are not globally unique). To draw a parallel, HTTPS connections use more "
1280"bandwidth and have higher latency than HTTP connections. Depending on "
1281"your application, HTTPS may not be worth the cost. However, for users "
1282"that are experiencing censorship (or are concerned about it), giving up "
1283"globally unique names may very well be worth the cost. After all, what is"
1284" a &quot;globally&quot; unique name worth, if it does not resolve?"
1285msgstr ""
1286
1287#: template/faq.html.j2:600
1288msgid "Why do you say that DNS is 'centralized' and 'distributed'?"
1289msgstr ""
1290
1291#: template/faq.html.j2:602
1292msgid ""
1293"A: We say that DNS is 'centralized' because it has a central component / "
1294"central point of failure --- the root zone and its management by "
1295"IANA/ICANN. This centralization creates vulnerabilities. For example, the"
1296" US government was able to reassign the management of the country-TLDs of"
1297" Afganistan and Iraq during the wars at the beginning of the 21st "
1298"century."
1299msgstr ""
1300
1301#: template/faq.html.j2:613
1302msgid "How does GNS protect against layer-3 censorship?"
1303msgstr ""
1304
1305#: template/faq.html.j2:615
1306msgid ""
1307"A: GNS does not directly help with layer-3 censorship, but it does help "
1308"indirectly in two ways: <ol> <li> Many websites today use virtual "
1309"hosting, so blocking a particular IP address causes much more collateral "
1310"damage than blocking a DNS name. It thus raises the cost of "
1311"censorship.</li> <li> Existing layer-3 circumvention solutions (such as "
1312"Tor) would benefit from a censorship resistant naming system. Accessing "
1313"Tor's &quot;.onion&quot; namespace currently requires users to use "
1314"unmemorable cryptographic identifiers. With nicer names, Tor and tor2web-"
1315"like services would be even easier to use. </ol>"
1316msgstr ""
1317
1318#: template/faq.html.j2:634
1319msgid "Does GNS work with search engines?"
1320msgstr ""
1321
1322#: template/faq.html.j2:636
1323msgid ""
1324"A: GNS creates no significant problems for search engines, as they can "
1325"use GNS to perform name resolution as well as any normal user. Naturally,"
1326" while we typically expect normal users to install custom software for "
1327"name resolution, this is unlikely to work for search engines today. "
1328"However, the DNS2GNS gateway allows search engines to use DNS to resolve "
1329"GNS names, so they can still index GNS resources. However, as using "
1330"DNS2GNS gateways breaks the cryptographic chain of trust, legacy search "
1331"engines will obviously not obtain censorship-resistant names."
1332msgstr ""
1333
1334#: template/faq.html.j2:650
1335msgid "How does GNS compare to the Unmanaged Internet Architecture (UIA)?"
1336msgstr ""
1337
1338#: template/faq.html.j2:652
1339msgid ""
1340"A: UIA and GNS both share the same basic naming model, which actually "
1341"originated with Rivest's SDSI. However, UIA is not concerned about "
1342"integration with legacy applications and instead focuses on universal "
1343"connectivity between a user's many machines. In contrast, GNS was "
1344"designed to interoperate with DNS as much as possible, and to also work "
1345"as much as possible with the existing Web infrastructure. UIA is not at "
1346"all concerned about legacy systems (clean slate)."
1347msgstr ""
1348
1349#: template/faq.html.j2:665
1350msgid "Doesn't GNS increase the trusted-computing base compared to DNS(SEC)?"
1351msgstr ""
1352
1353#: template/faq.html.j2:667
1354msgid ""
1355"A: First of all, in GNS you can explicitly see the trust chain, so you "
1356"know if a name you are resolving belongs to a friend, or a friend-"
1357"of-a-friend, and can thus decide how much you trust the result. "
1358"Naturally, the trusted-computing base (TCB) can become arbitrarily large "
1359"this way --- however, given the name length restriction, for an "
1360"individual name it is always less than about 128 entities."
1361msgstr ""
1362
1363#: template/faq.html.j2:679
1364msgid ""
1365"How does GNS handle SRV/TLSA records where service and protocol are part "
1366"of the domain name?"
1367msgstr ""
1368
1369#: template/faq.html.j2:681
1370msgid ""
1371"A: When GNS splits a domain name into labels for resolution, it detects "
1372"the &quot;_Service._Proto&quot; syntax, converts &quot;Service&quot; to "
1373"the corresponding port number and &quot;Proto&quot; to the corresponding "
1374"protocol number. The rest of the name is resolved as usual. Then, when "
1375"the result is presented, GNS looks for the GNS-specific &quot;BOX&quot; "
1376"record type. A BOX record is a record that contains another record (such "
1377"as SRV or TLSA records) and adds a service and protocol number (and the "
1378"original boxed record type) to it."
1379msgstr ""
1380
1381#: template/faq.html.j2:697
1382msgid ""
1383"I receive many &quot;WARNING Calculated flow delay for X at Y for "
1384"Z&quot;. Should I worry?"
1385msgstr ""
1386
1387#: template/faq.html.j2:699
1388msgid ""
1389"A: Right now, this is expected and a known cause for high latency in "
1390"GNUnet. We have started a major rewrite to address this and other "
1391"problems, but until the Transport Next Generation (TNG) is ready, these "
1392"warnings are expected."
1393msgstr ""
1394
1395#: template/faq.html.j2:708
1396msgid "Error opening `/dev/net/tun': No such file or directory?"
1397msgstr ""
1398
1399#: template/faq.html.j2:710
1400msgid ""
1401"A: If you get this error message, the solution is simple. Issue the "
1402"following commands (as root) to create the required device file"
1403msgstr ""
1404
1405#: template/faq.html.j2:722
1406msgid ""
1407"'iptables: No chain/target/match by that name.' (when running gnunet-"
1408"service-dns)?"
1409msgstr ""
1410
1411#: template/faq.html.j2:724
1412msgid ""
1413"A: For GNUnet DNS, your iptables needs to have &quot;owner&quot; match "
1414"support. This is accomplished by having the correct kernel options. Check"
1415" if your kernel has CONFIG_NETFILTER_XT_MATCH_OWNER set to either 'y' or "
1416"'m' (and the module is loaded)."
1417msgstr ""
1418
1419#: template/faq.html.j2:736
1420msgid "'Timeout was reached' when running PT on Fedora (and possibly others)?"
1421msgstr ""
1422
1423#: template/faq.html.j2:738
1424msgid ""
1425"A: If you get an error stating that the VPN timeout was reached, check if"
1426" your firewall is enabled and blocking the connections."
1427msgstr ""
1428
1429#: template/faq.html.j2:746
1430msgid "I'm getting an 'error while loading shared libraries: libgnunetXXX.so.X'"
1431msgstr ""
1432
1433#: template/faq.html.j2:748
1434msgid ""
1435"A: This error usually occurs when your linker fails to locate one of "
1436"GNUnet's libraries. This can have two causes. First, it is theoretically "
1437"possible that the library is not installed on your system; however, if "
1438"you compiled GNUnet the normal way and/or used a binary package, that is "
1439"highly unlikely. The more common cause is that you installed GNUnet to a "
1440"directory that your linker does not search. There are several ways to fix"
1441" this that are described below. If you are 'root' and you installed to a "
1442"system folder (such as /usr/local), you want to add the libraries to the "
1443"system-wide search path. This is done by adding a line "
1444"\"/usr/local/lib/\" to /etc/ld.so.conf and running \"ldconfig\". If you "
1445"installed GNUnet to /opt or any other similar path, you obviously have to"
1446" change \"/usr/local\" accordingly. If you do not have 'root' rights or "
1447"if you installed GNUnet to say \"/home/$USER/\", then you can explicitly "
1448"tell your linker to search a particular directory for libraries using the"
1449" \"LD_LIBRARY_PATH\" environment variable. For example, if you configured"
1450" GNUnet using a prefix of \"$HOME/gnunet/\" you want to run:"
1451msgstr ""
1452
1453#: template/faq.html.j2:774
1454msgid ""
1455"to ensure GNUnet's binaries and libraries are found. In order to avoid "
1456"having to do so each time, you can add the above lines (without the "
1457"\"$\") to your .bashrc or .profile file. You will have to logout and "
1458"login again to have this new profile be applied to all shells (including "
1459"your desktop environment)."
1460msgstr ""
1461
1462#: template/faq.html.j2:781
1463msgid "What error messages can be ignored?"
1464msgstr ""
1465
1466#: template/faq.html.j2:783
1467msgid ""
1468"A: Error messages flagged as \"DEBUG\" should be disabled in binaries "
1469"built for end-users and can always be ignored. Error messages flagged as "
1470"\"INFO\" always refer to harmless events that require no action. For "
1471"example, GNUnet may use an INFO message to indicate that it is currently "
1472"performing an expensive operation that will take some time. GNUnet will "
1473"also use INFO messages to display information about important "
1474"configuration values."
1475msgstr ""
1476
1477#: template/faq.html.j2:799
1478msgid "How does GNUnet compare to other file-sharing applications?"
1479msgstr ""
1480
1481#: template/faq.html.j2:801
1482msgid ""
1483"A: As opposed to Napster, Gnutella, Kazaa, FastTrack, eDonkey and most "
1484"other P2P networks, GNUnet was designed with security in mind as the "
1485"highest priority. We intend on producing a network with comprehensive "
1486"security features. Many other P2P networks are open to a wide variety of "
1487"attacks, and users have little privacy. GNUnet is also Free Software and "
1488"thus the source code is available, so you do not have to worry about "
1489"being spied upon by the software. The following table summarises the main"
1490" differences between GNUnet and other systems. The information is "
1491"accurate to the best of our knowledge. The comparison is difficult since "
1492"there are sometimes differences between various implementations of "
1493"(almost) the same protocol. In general, we pick a free implementation as "
1494"the reference implementation since it is possible to inspect the free "
1495"code. Also, all of these systems are changing over time and thus the data"
1496" below may not be up-to-date. If you find any flaws, please let us know. "
1497"Finally, the table is not saying terribly much (it is hard to compare "
1498"these systems this briefly), so if you want the real differences, read "
1499"the research papers (and probably the code)."
1500msgstr ""
1501
1502#: template/faq.html.j2:915
1503msgid ""
1504"Another important point of reference are the various anonymous peer-to-"
1505"peer networks. Here, there are differences in terms of application domain"
1506" and how specifically anonymity is achieved. Anonymous routing is a hard "
1507"research topic, so for a superficial comparison like this one we focus on"
1508" the latency. Another important factor is the programming language. Type-"
1509"safe languages may offer certain security benefits; however, this may "
1510"come at the cost of significant increases in resource consumption which "
1511"in turn may reduce anonymity."
1512msgstr ""
1513
1514#: template/faq.html.j2:928
1515msgid "Are there any known attacks (on GNUnet's file-sharing application)?"
1516msgstr ""
1517
1518#: template/faq.html.j2:930
1519msgid ""
1520"A: Generally, there is the possibility of a known plaintext attack on "
1521"keywords, but since the user has control over the keywords that are "
1522"associated with the content he inserts, the user can take advantage of "
1523"the same techniques used to generate reasonable passwords to defend "
1524"against such an attack. In any event, we are not trying to hide content; "
1525"thus, unless the user is trying to insert information into the network "
1526"that can only be shared with a small group of people, there is no real "
1527"reason to try to obfuscate the content by choosing a difficult keyword "
1528"anyway."
1529msgstr ""
1530
1531#: template/faq.html.j2:944
1532msgid "What do you mean by anonymity?"
1533msgstr ""
1534
1535#: template/faq.html.j2:946
1536msgid ""
1537"A: Anonymity is the lack of distinction of an individual from a (large) "
1538"group. A central goal for anonymous file-sharing in GNUnet is to make all"
1539" users (peers) form a group and to make communications in that group "
1540"anonymous, that is, nobody (but the initiator) should be able to tell "
1541"which of the peers in the group originated the message. In other words, "
1542"it should be difficult to impossible for an adversary to distinguish "
1543"between the originating peer and all other peers."
1544msgstr ""
1545
1546#: template/faq.html.j2:958
1547msgid "What does my system do when participating in GNUnet file sharing?"
1548msgstr ""
1549
1550#: template/faq.html.j2:960
1551msgid ""
1552"A: In GNUnet you set up a node (a peer). It is identified by an ID (hash "
1553"of its public key) and has a number of addresses it is reachable by (may "
1554"have no addresses, for instance when it's behind a NAT). You specify "
1555"bandwidth limits (how much traffic GNUnet is allowed to consume) and "
1556"datastore quote (how large your on-disk block storage is) . Your node "
1557"will then proceed to connect to other nodes, becoming part of the "
1558"network."
1559msgstr ""
1560
1561#: template/faq.html.j2:975
1562msgid "How can I help translate this webpage into other languages?"
1563msgstr ""
1564
1565#: template/faq.html.j2:977
1566msgid ""
1567"A: First, you need to register an account with our weblate system. Please"
1568" send an e-mail with the desired target language to "
1569"translators@gnunet.org or ask for help on the #gnunet chat on "
1570"irc.freenode.net. Typically someone with sufficient permissions will then"
1571" grant you access. Naturally, any abuse will result in the loss of "
1572"permissions."
1573msgstr ""
1574
1575#: template/faq.html.j2:989
1576msgid "I have some great idea for a new feature, what should I do?"
1577msgstr ""
1578
1579#: template/faq.html.j2:991
1580msgid ""
1581"A: Sadly, we have many more feature requests than we can possibly "
1582"implement. The best way to actually get a new feature implemented is to "
1583"do it yourself --- and to then send us a patch."
1584msgstr ""
1585
1586#: template/glossary.html.j2:12
1587msgid "Ego"
1588msgstr ""
1589
1590#: template/glossary.html.j2:14
1591msgid ""
1592"We use the term \"Ego\" to refer to the fact that users in GNUnet can "
1593"have multiple unlinkable identities, in the sense of alter egos. The "
1594"ability to have more than one identity is crucial, as we may want to keep"
1595" our egos for business separate from those we use for political "
1596"activities or romance.<br> Egos in GNUnet are technically equivalent to "
1597"identities (and the code does not distinguish between them). We simply "
1598"sometimes use the term \"ego\" to stress that you can have more than one."
1599msgstr ""
1600
1601#: template/glossary.html.j2:27
1602msgid "Identity"
1603msgstr ""
1604
1605#: template/glossary.html.j2:29
1606msgid ""
1607"In GNUnet users are identified via a public key, and that public key is "
1608"then often referred to as the \"Identity\" of the user. However, the "
1609"concept is not as draconian as it often is in real life where many are "
1610"forced to have one name, one passport and one unique identification "
1611"number. <br> As long as identities in GNUnet are simply public keys, "
1612"users are free to create any number of identities, and we call those egos"
1613" to emphasize the difference. Even though users can create such egos "
1614"freely, it is possible to have an ego certified by some certification "
1615"authority, resulting in something that more closely resembles the "
1616"traditional concept of an identity.<br> For example, a university may "
1617"certify the identities of its students such that they can prove that they"
1618" are studying. Students may keep their (certified) student identity "
1619"separate from other egos that they use for other activities in life."
1620msgstr ""
1621
1622#: template/glossary.html.j2:50
1623msgid "Pseudonym"
1624msgstr ""
1625
1626#: template/glossary.html.j2:52
1627msgid ""
1628"A pseudonym is an ego that is specifically intended to not be linked to "
1629"one's real name. GNUnet users can create many egos, and thus also many "
1630"pseudonyms. <br> Repeated uses of the same pseudonym are linkable by "
1631"definition, as they involve the same public key. Anonymity requires the "
1632"use of either the special \"anonymous\" pseudonym (for GNUnet, this is "
1633"the neutral element on the elliptic curve) or a throw-away pseudonym that"
1634" is only used once."
1635msgstr ""
1636
1637#: template/glossary.html.j2:71
1638msgid "Namespaces"
1639msgstr ""
1640
1641#: template/glossary.html.j2:73
1642msgid ""
1643"The GNU Name System allows every ego (or identity) to securely and "
1644"privately associate any number of label-value pairs with an ego. The "
1645"values are called record sets following the terminology of the Domain "
1646"Name System (DNS). The mapping of labels to record sets for a given ego "
1647"is called a namespace. <br> If records are made public and thus "
1648"published, it is possible for other users to lookup the record given the "
1649"ego's public key and the label. Here, not only the label can thus act as "
1650"a passphrase but also the public key -- which despite its name may not be"
1651" public knowledge and is never disclosed by the GNS protocol itself."
1652msgstr ""
1653
1654#: template/glossary.html.j2:89
1655msgid "Peer"
1656msgstr ""
1657
1658#: template/glossary.html.j2:91
1659msgid ""
1660"A \"peer\" is an instance of GNUnet with its own per-instance public key "
1661"and network addresses. Technically, it is possible to run multiple peers "
1662"on the same host, but this only makes sense for testing. <br> By design "
1663"GNUnet supports multiple users to share the same peer, just as UNIX is a "
1664"multi-user system. A \"peer\" typically consists of a set of foundational"
1665" GNUnet services running as the \"gnunet\" user and allowing all users in"
1666" the \"gnunet\" group to utilize the API. On multi-user systems, "
1667"additional \"personalized\" services may be required per user. <br> While"
1668" peers are also identified by public keys, these public keys are "
1669"completely unrelated to egos or identities. Namespaces cannot be "
1670"associated with a peer, only with egos."
1671msgstr ""
1672
1673#: template/gns.html.j2:13 template/gnurl.html.j2:60
1674msgid "Motivation"
1675msgstr ""
1676
1677#: template/gns.html.j2:15
1678msgid ""
1679"The Domain Name System today enables traffic amplification attacks, "
1680"censorship (i.e. China), mass surveillance (MORECOWBELL) and offensive "
1681"cyber war (QUANTUMDNS).<br/> Unfortunately, band aid solutions such as "
1682"DoT, DoH, DNSSEC, DPRIVE and the like will not fix this. This is why we "
1683"built the GNU Name System (GNS), a secure, decentralized name system "
1684"built on top of GNUnet."
1685msgstr ""
1686
1687#: template/gns.html.j2:28
1688msgid "Overview"
1689msgstr ""
1690
1691#: template/gns.html.j2:39
1692msgid ""
1693"The GNU Name System (GNS) is secure and decentralized naming system. It "
1694"allows its users to register names as top-level domains (TLDs) and "
1695"resolve other namespaces within their TLDs. <br/> GNS is designed to "
1696"provide: <ul> <li>Censorship resistance</li> <li>Query privacy</li> "
1697"<li>Secure name resolution</li> <li>Compatibility with DNS</li>"
1698msgstr ""
1699
1700#: template/gns.html.j2:52
1701msgid "Resources"
1702msgstr ""
1703
1704#: template/gnurl.html.j2:21
1705msgid ""
1706"libgnurl is a micro fork of libcurl. The goal of libgnurl is to support "
1707"only HTTP and HTTPS (and only HTTP 1.x) with a single crypto backend "
1708"(GnuTLS) to ensure a small footprint and uniform experience for "
1709"developers regardless of how libcurl was compiled."
1710msgstr ""
1711
1712#: template/gnurl.html.j2:30
1713msgid ""
1714"Our main usecase is for GNUnet and Taler, but it might be usable for "
1715"others, hence we&#39;re releasing the code to the general public."
1716msgstr ""
1717
1718#: template/gnurl.html.j2:37
1719msgid ""
1720"libgnurl is released under the same license as libcurl. Please read the "
1721"README for instructions, as you must supply the correct options to "
1722"configure to get a proper build of libgnurl."
1723msgstr ""
1724
1725#: template/gnurl.html.j2:48
1726msgid "About gnurl"
1727msgstr ""
1728
1729#: template/gnurl.html.j2:50
1730msgid ""
1731"Large parts of the following 6 paragraphs are old and need to be "
1732"rewritten."
1733msgstr ""
1734
1735#: template/gnurl.html.j2:62
1736msgid ""
1737"cURL supports many crypto backends. GNUnet requires the use of GnuTLS, "
1738"but other variants are used by some distributions. Supporting other "
1739"crypto backends would again expose us to a wider array of security "
1740"issues, may create licensing issues and most importantly introduce new "
1741"bugs as some crypto backends are known to introduce subtle runtime "
1742"issues. While it is possible to have two versions of libcurl installed on"
1743" the same system, this is error-prone, especially as if we are linked "
1744"against the wrong version, the bugs that arise might be rather subtle."
1745msgstr ""
1746
1747#: template/gnurl.html.j2:75
1748msgid ""
1749"For GNUnet, we also need a particularly modern version of GnuTLS. Thus, "
1750"it would anyway be necessary to recompile cURL for GNUnet. But what "
1751"happens if one links cURL against this version of GnuTLS? Well, first one"
1752" would install GnuTLS by hand in the system. Then, we build cURL. cURL "
1753"will build against it just fine, but the linker will eventually complain "
1754"bitterly. The reason is that cURL also links against a bunch of other "
1755"system libraries (gssapi, ldap, ssh2, rtmp, krb5, sasl2, see discussion "
1756"on obscure protocols above), which --- as they are part of the "
1757"distribution --- were linked against an older version of GnuTLS. As a "
1758"result, the same binary would be linked against two different versions of"
1759" GnuTLS. That is typically a recipe for disaster. Thus, in order to avoid"
1760" updating a dozen system libraries (and having two versions of those "
1761"installed), it is necessary to disable all of those cURL features that "
1762"GNUnet does not use, and there are many of those. For GNUnet, the more "
1763"obscure protocols supported by cURL are close to dead code --- mostly "
1764"harmless, but not useful. However, as some application may use one of "
1765"those features, distributions are typically forced to enable all of those"
1766" features, and thus including security issues that might arise from that "
1767"code."
1768msgstr ""
1769
1770#: template/gnurl.html.j2:99
1771msgid ""
1772"So to use a modern version of GnuTLS, a sane approach is to disable all "
1773"of the \"optional\" features of cURL that drag in system libraries that "
1774"link against the older GnuTLS. That works, except that one should then "
1775"NEVER install that version of libcurl in say /usr or /usr/local, as that "
1776"may break other parts of the system that might depend on these features "
1777"that we just disabled. Libtool versioning doesn't help here, as it is not"
1778" intended to deal with libraries that have optional features. Naturally, "
1779"installing cURL somewhere else is also problematic, as we now need to be "
1780"really careful that the linker will link GNUnet against the right "
1781"version. Note that none of this can really be trivially fixed by the cURL"
1782" developers."
1783msgstr ""
1784
1785#: template/gnurl.html.j2:118
1786msgid "Rename to fix"
1787msgstr ""
1788
1789#: template/gnurl.html.j2:120
1790#, python-format
1791msgid ""
1792"How does forking fix it? Easy. First, we can get rid of all of the "
1793"compatibility issues --- if you use libgnurl, you state that you "
1794"don&#39;t need anything but HTTP/HTTPS. Those applications that need "
1795"more, should stick with the original cURL. Those that do not, can choose "
1796"to move to something simpler. As the library gets a new name, we do not "
1797"have to worry about tons of packages breaking as soon as one rebuilds it."
1798" So renaming itself and saying that \"libgnurl = libcurl with only "
1799"HTTP/HTTPS support and GnuTLS\" fixes 99%% of the problems that darkened "
1800"my mood. Note that this pretty much CANNOT be done without a fork, as "
1801"renaming is an essential part of the fix. Now, there might be creative "
1802"solutions to achieve the same thing within the standard cURL build "
1803"system, but this was deemed to be too much work when gnurl was originally"
1804" started. The changes libgnurl makes to curl are miniscule and can easily"
1805" be applied again and again whenever libcurl makes a new release."
1806msgstr ""
1807
1808#: template/gnurl.html.j2:142
1809msgid "Using libgnurl"
1810msgstr ""
1811
1812#: template/gnurl.html.j2:144
1813msgid ""
1814"Projects that use cURL only for HTTP/HTTPS and that would work with "
1815"GnuTLS should be able to switch to libgnurl by changing \"-lcurl\" to "
1816"\"-lgnurl\". That&#39;s it. No changes to the source code should be "
1817"required, as libgnurl strives for bug-for-bug compatibility with the "
1818"HTTP/HTTPS/GnuTLS subset of cURL. We might add new features relating to "
1819"this core subset if they are proposed, but so far we have kept our "
1820"changes minimal and no additions to the original curl source have been "
1821"written."
1822msgstr ""
1823
1824#: template/gnurl.html.j2:161
1825msgid "Gotchas"
1826msgstr ""
1827
1828#: template/gnurl.html.j2:163
1829msgid ""
1830"libgnurl and gnurl are not intended to be used as a replacement for curl "
1831"for users: <br> This does not mean there is no confidence in the work "
1832"done with gnurl, it means that tools which expect curl or libcurl will "
1833"not make use of a different named binary and library. If you know what "
1834"you are doing, you should be able to use gnurl as part of your tooling in"
1835" place of curl. We do not recommend to do so however, as the only usage "
1836"it is tested for <em>so far</em> is as part of Taler&#39;s and "
1837"GNunet&#39;s build-system. <br> Since no conflicts in filenames occur you"
1838" are not expected to remove curl to make use of gnurl and viceversa."
1839msgstr ""
1840
1841#: template/gnurl.html.j2:188
1842msgid "You can get the gnurl git repository using:"
1843msgstr ""
1844
1845#: template/gnurl.html.j2:201
1846msgid "The versions are checked in as (signed) git tags."
1847msgstr ""
1848
1849#: template/gnurl.html.j2:211
1850msgid ""
1851"Releases are published on <a "
1852"href=\"https://ftpmirror.gnu.org/gnu/gnunet/\">ftpmirror.gnu.org/gnu/gnunet</a>."
1853" gnurl is available from within a variety of distributions and package "
1854"managers. Some Package Managers which include gnurl are: <a "
1855"href=\"https://www.gnu.org/software/guix/\">GNU Guix</a> (available as "
1856"\"gnurl\"), <a href=\"https://gentoo.org\">Gentoo</a> through the "
1857"collaborative ebuild collection <a href=\"https://git.gnunet.org"
1858"/youbroketheinternet-overlay.git/\">youbroketheinternet</a>, <a "
1859"href=\"https://nixos.org/nix/\">Nix</a>, and as www/gnurl in <a "
1860"href=\"https://pkgsrc.org\">pkgsrc</a>."
1861msgstr ""
1862
1863#: template/gnurl.html.j2:228
1864msgid "Building gnurl"
1865msgstr ""
1866
1867#: template/gnurl.html.j2:230
1868msgid ""
1869"We suggest to closely follow release announcements, as they might "
1870"indicate changes in how gnurl is to be build. <br> If your package "
1871"manager provides a binary build or build instructions to build gnurl from"
1872" source automated and integrated with your environment, we strongly "
1873"suggest to use this binary build. <br> There are two ways to build gnurl."
1874" The first one builds from the most recent git tag, the second one uses "
1875"the distributed tarball. Distributors generally are supposed to build "
1876"from the tarball, but we describe both methods here. Both methods are "
1877"written with a NetBSD 9 userland in mind, substitute tools as necessary. "
1878"<br> You should <b>avoid</b> building gnurl from the tip of the default "
1879"git branch, as only tags are considered to be stable and approved builds."
1880msgstr ""
1881
1882#: template/gnurl.html.j2:251
1883msgid "Building from the distributed tarball (prefered method)"
1884msgstr ""
1885
1886#: template/gnurl.html.j2:253
1887msgid ""
1888"If you want to verify the signature, install an OpenPGP compatible tool "
1889"such as security/gnupgp2 (and set it up). Assuming you use pkgin:"
1890msgstr ""
1891
1892#: template/gnurl.html.j2:267
1893msgid "Fetch the signature key from"
1894msgstr ""
1895
1896#: template/gnurl.html.j2:271
1897msgid "or via commandline with gnupg2."
1898msgstr ""
1899
1900#: template/gnurl.html.j2:276
1901msgid ""
1902"Fetch the release, the signature, the checksum file as well as its "
1903"signature:"
1904msgstr ""
1905
1906#: template/gnurl.html.j2:295
1907msgid ""
1908"verify the signatures, and verify the checksums against the checksums in "
1909"the .sum.txt file."
1910msgstr ""
1911
1912#: template/gnurl.html.j2:301
1913msgid "unpack the tarball:"
1914msgstr ""
1915
1916#: template/gnurl.html.j2:311
1917msgid "Change into the directory"
1918msgstr ""
1919
1920#: template/gnurl.html.j2:321
1921msgid "Now you can either run"
1922msgstr ""
1923
1924#: template/gnurl.html.j2:331
1925msgid "directly (and read configure-gnurl before you do so) or invoke"
1926msgstr ""
1927
1928#: template/gnurl.html.j2:341
1929msgid ""
1930"and pass additional parameters such as a custom PREFIX location. Further "
1931"reference can be the"
1932msgstr ""
1933
1934#: template/gnurl.html.j2:346
1935msgid "Now run"
1936msgstr ""
1937
1938#: template/gnurl.html.j2:356
1939msgid "(this is optional)"
1940msgstr ""
1941
1942#: template/gnurl.html.j2:365
1943msgid "and you are done."
1944msgstr ""
1945
1946#: template/gnurl.html.j2:369
1947msgid "Building from a tagged git commit"
1948msgstr ""
1949
1950#: template/gnurl.html.j2:371
1951msgid ""
1952"Follow the steps above, but instead of downloading the tarball, clone the"
1953" git tag you want to build from."
1954msgstr ""
1955
1956#: template/gnurl.html.j2:382
1957msgid "Reporting Bugs"
1958msgstr ""
1959
1960#: template/gnurl.html.j2:384
1961msgid ""
1962"You can report bugs on our bug tracker: <a "
1963"href=\"https://bugs.gnunet.org/\">bugs.gnunet.org</a>. Alternatively you "
1964"can use our bug mailinglist, but we prefer to track bugs on the "
1965"bugtracker."
1966msgstr ""
1967
1968#: template/gnurl.html.j2:395
1969msgid "Maintainer and Cryptographic signatures"
1970msgstr ""
1971
1972#: template/gnurl.html.j2:397
1973msgid ""
1974"gnurl/libgnurl is looking for a new maintainer. Releases after version "
1975"7.69.1 and up to version 7.72.0 were signed with the OpenPGP Key "
1976"<b>0xD6B570842F7E7F8D</b> (<a "
1977"href=\"https://keys.openpgp.org/search?q=6115012DEA3026F62A98A556D6B570842F7E7F8D\">keys.openpgp.org</a>),"
1978" with the key fingerprint <b>6115 012D EA30 26F6 2A98 A556 D6B5 7084 2F7E"
1979" 7F8D</b>."
1980msgstr ""
1981
1982#: template/gsoc-2018-gnunet-webui.html.j2:7
1983msgid "GSoC 2018: GNUnet WebUI (GNUnet Web-based User Interface)"
1984msgstr ""
1985
1986#: template/gsoc-2018-gnunet-webui.html.j2:11
1987msgid "Tue, 08/14/2018 - 07:55, Phil Buschmann"
1988msgstr ""
1989
1990#: template/gsoc-2018-gnunet-webui.html.j2:18
1991msgid ""
1992"In the context of Google Summer of Code 2018, my mentor (Martin "
1993"Schanzenbach) and I have worked on creating and extending the REST API of"
1994" GNUnet. Currently, we mirrored the functionality of following commands:"
1995msgstr ""
1996
1997#: template/gsoc-2018-gnunet-webui.html.j2:32
1998msgid ""
1999"Additionally, we developed a website with the Javascript framework "
2000"Angular 6 and the design framework iotaCSS to use the new REST API. The "
2001"REST API of GNUnet is now documented with Sphinx."
2002msgstr ""
2003
2004#: template/gsoc-2018-gnunet-webui.html.j2:41
2005msgid ""
2006"... when you can use the command line tools? We need to keep in mind, "
2007"that everyone has the right to stay secure and private but not everyone "
2008"feels comfortable using a terminal. The further developed REST access to "
2009"GNUnet APIs in addition to the new web application allows new users to "
2010"interact with GNUnet over a well known tool: their browsers. This "
2011"addition to the C API and the command line tools may attract new users "
2012"and developers."
2013msgstr ""
2014
2015#: template/gsoc-2018-gnunet-webui.html.j2:54
2016msgid ""
2017"<li> The REST API developed in GNUnet<br> The REST API is already merged "
2018"into the gnunet.git repository (<a "
2019"href=\"https://gnunet.org/git/gnunet.git/\">GNUnet Main Git</a>).<br /> "
2020"To use the new features, clone the repository and follow the <a "
2021"href=\"https://gnunet.org/en/install.html\">Installation</a> on "
2022"gnunet.org. Then, start the rest service with \"gnunet-arm -i rest\". "
2023"</li> <li> The Web Application<br> The web application is available under"
2024" the gnunet-webui.git repository (<a href=\"https://gnunet.org/git"
2025"/gnunet-webui.git/\">GNUnet WebUI Git</a>).<br /> You need to install the"
2026" newest version of 'node' and 'yarn'. Dependent on your system, you may "
2027"need to download newer versions and install them manually and not over "
2028"your packet manager. After the installation succeeded, you need to clone "
2029"the repository. Then, you need to run \"yarn install\" and \"yarn start\""
2030" for testing purposes. To deploy the website (keep in mind, that this "
2031"website communicates with another localhost instance) use \"yarn build\" "
2032"for building the web application and use the output in the 'dist' "
2033"directory. </li> <li> The Documentation<br /> The documentation is "
2034"available under the gnunet-rest-api.git repository (<a "
2035"href=\"https://gnunet.org/git/gnunet-rest-api.git/\">GNUnet REST API "
2036"Docmentation Git</a>).<br /> Clone the repository and \"make html\". Then"
2037" open the 'index.html' under 'build/html/'. </li>"
2038msgstr ""
2039
2040#: template/gsoc-2018-gnunet-webui.html.j2:91
2041msgid ""
2042"Please, give it a try and contact me, if you find any bugs or "
2043"unintentional features. ;)"
2044msgstr ""
2045
2046#: template/gsoc-2018-gnunet-webui.html.j2:98
2047msgid ""
2048"Right now, the build process of the web application may be a little too "
2049"complex for a casual user. We may be able to solve this by using "
2050"docker.<br /> Additionally, the web application does not prevent wrong "
2051"inputs but responds with error messages. Adding GNUnet Records is "
2052"currently only usable for people, who know how a GNS Record looks like. "
2053"This can be adapted to each record type.<br /> Last but not least, "
2054"additional features, design changes, etc..."
2055msgstr ""
2056
2057#: template/gsoc-2018-gnunet-webui.html.j2:111
2058msgid "Thanks for reading."
2059msgstr ""
2060
2061#: template/gsoc.html.j2:6
2062msgid "GNUnet's Google Summer of Code projects"
2063msgstr ""
2064
2065#: template/gsoc.html.j2:12 template/gsoc.html.j2:29
2066msgid "Ideas 2021"
2067msgstr ""
2068
2069#: template/gsoc.html.j2:13 template/gsoc.html.j2:215
2070msgid "Past projects"
2071msgstr ""
2072
2073#: template/gsoc.html.j2:14 template/gsoc.html.j2:596
2074msgid "Finished projects"
2075msgstr ""
2076
2077#: template/gsoc.html.j2:21
2078msgid ""
2079"As a GNU project, GNUnet has participated in the Google Summer of Code "
2080"(GSoC) for a number of years. This page lists all current, past, and "
2081"finished projects. If you want to participate and apply for any of the "
2082"ideas for 2020 below or any past project which is not yet finished (or "
2083"even your own idea), please contact us either in IRC or mailing list."
2084msgstr ""
2085
2086#: template/gsoc.html.j2:34
2087msgid ""
2088"The GNUnet team is currently working on a transport layer rewrite in "
2089"order to fix core issues with connectivity. This new component is "
2090"currently developed under the name \"TNG\". What is currently known as "
2091"\"transport plugins\" will in the TNG be represented as "
2092"\"communicators\". Communicators are processes with a well defined API "
2093"that allow to connect peers over a specific protocol. The primary "
2094"protocol which are already implemented are UNIX sockets, UDP sockets, and"
2095" TCP sockets. For a truly resilient network, other connectivity options "
2096"such as WiFi mesh, Bluetooth, HTTP(S), QUIC or even more obscure "
2097"alternatives such as radio are required. In this project, the goal is to "
2098"select, implement and test new communicators. While TNG is not yet ready,"
2099" communicators can, by design, be developed and tested against the "
2100"current API. We expect that this project can be worked on by multiple "
2101"students as there are a lot of protocols to choose from. The tasks would "
2102"consist of: <ol> <li>Deciding which communicators to implement.</li> "
2103"<li>Test the communicators.</li> <li>Documentation.</li> </ol> "
2104"Advantageous skills/languages/frameworks: <ol> <li>C</li> <li>Knowledge "
2105"of HTTPS, QUIC, Bluetooth or WiFi.</li> </ol> <br/> "
2106"<strong>Difficulty:</strong> Average, but depends on selected protocols. "
2107"<br/> <strong>Mentors:</strong> Martin Schanzenbach, t3sserakt"
2108msgstr ""
2109
2110#: template/gsoc.html.j2:79
2111msgid ""
2112"The REST API currently only supports a single user system. This is an "
2113"issue as on multi-user systems, access control must be enfoced on a per-"
2114"user basis. In this project, the REST service must be extended to support"
2115" user authentication. This includes the correct handling of user context "
2116"switches. <ol> <li>Implement user authentication.</li> <li>Test the "
2117"access control.</li> <li>Document the changes to the REST API.</li> </ol>"
2118" Advantageous skills/languages/frameworks: <ol> <li>C</li> <li>Knowledge "
2119"of user authentication subsystems on Linux/Unix.</li> <li>REST/HTTP "
2120"Authentication methods</li> </ol> <br/> <strong>Difficulty:</strong> "
2121"Beginner <br/> <strong>Mentors:</strong> Martin Schanzenbach"
2122msgstr ""
2123
2124#: template/gsoc.html.j2:111
2125msgid ""
2126"reclaimID is a decentralized identity system build on top of the GNU Name"
2127" System. Currently, there is a Webextension which uses the GNUnet <a "
2128"href=\"https://rest.gnunet.org\">REST API</a>. In order to improve "
2129"adoption and ease of use, this project aims to include a full GNUnet node"
2130" within the Webextention as a fallback. GNUnet can be compiled to Web "
2131"Assembly or JavaScript as demonstrated <a "
2132"href=\"https://gnunet.io\">here</a>. The idea is to improve upon this "
2133"concept and support more of GNUnet's subsystems. The difficulty of this "
2134"project largely depends on the students proficiency with build tools, "
2135"emscripten and improvisation skills. There non-exhaustive task list would"
2136" be: <ol> <li>Improve existing GNUnet emscripten build to include more "
2137"subsystems.</li> <li>Integrate the result into a Webextention.</li> "
2138"<li>Integrate the result into the re:claimID Webextension</li> </ol> "
2139"Advantageous skills/languages/frameworks: <ol> <li>C</li> "
2140"<li>emscripten</li> <li>Webextensions</li> </ol> <br/> "
2141"<strong>Difficulty:</strong> Challenging <br/> <strong>Mentors:</strong> "
2142"Martin Schanzenbach"
2143msgstr ""
2144
2145#: template/gsoc.html.j2:147
2146msgid ""
2147"Currently, the keys in our statistics database are too verbose. For "
2148"example: </p> <p> nse # flood messages received: 13<br/> nse # peers "
2149"connected: 4<br/> nse # nodes in the network (estimate): 203<br/> nse # "
2150"flood messages started: 5<br/> nse # estimated network diameter: 3<br/> "
2151"nse # flood messages transmitted: 10<br/> </p> <p> With such verbose keys"
2152" there's no easy way to form compact JSON document or entries for time-"
2153"series database. And you can't query single stats without having to "
2154"copypaste the line exactly and put in quotes. In short, the goals are "
2155"to... <ol> <li>Think of a way how statistics entries can be made "
2156"canonical.</li> <li>Implement the change and migrate existing uses.</li> "
2157"<li>Document the format(s) and define an appropriate registration "
2158"mechanism for identifiers</li> </ol> Relevant bugs: <a "
2159"href=\"https://bugs.gnunet.org/view.php?id=5650\">#5650</a><br/> "
2160"Advantageous skills/languages/frameworks: <ol> <li>C</li> <li>HTML</li> "
2161"</ol> <br/> <strong>Difficulty:</strong> Beginner <br/> "
2162"<strong>Mentors:</strong> Martin Schanzenbach"
2163msgstr ""
2164
2165#: template/gsoc.html.j2:187
2166msgid ""
2167"The goal is to either build upon the (outdated) <a "
2168"href=\"https://github.com/canndrew/gnunet-rs\">GNUnet Rust bindings</a> "
2169"or to follow the path of <a href=\"GNUnet Go\">https://github.com/bfix"
2170"/gnunet-go</a> which tries to reimplement most of the GNUnet stack. The "
2171"end result should be an extension template for GNUnet in the form of the "
2172"existing <a href=\"https://git.gnunet.org/gnunet-ext.git/\">C "
2173"template</a> which allows to quickly start implementing services and "
2174"libraries for GNUnet."
2175msgstr ""
2176
2177#: template/gsoc.html.j2:198 template/gsoc.html.j2:652
2178msgid "<strong>Mentors:</strong> Martin Schanzenbach"
2179msgstr ""
2180
2181#: template/gsoc.html.j2:203
2182msgid "Required Skills: Solid knowledge of Rust and ideally asynchronuous IO."
2183msgstr ""
2184
2185#: template/gsoc.html.j2:208 template/gsoc.html.j2:321
2186#: template/gsoc.html.j2:531 template/gsoc.html.j2:662
2187msgid "Difficulty level: medium"
2188msgstr ""
2189
2190#: template/gsoc.html.j2:222
2191msgid ""
2192"It is time for GNUnet to run properly on Android. Note that GNUnet is "
2193"written in C, and this is not about rewriting GNUnet in Java, but about "
2194"getting the C code to run on Android."
2195msgstr ""
2196
2197#: template/gsoc.html.j2:229
2198msgid ""
2199"Includes: Implementation of rudimentary Android compatibility for GNUnet,"
2200" in part by porting the GNUnet utils scheduler to act as a thin wrapper "
2201"over libuv."
2202msgstr ""
2203
2204#: template/gsoc.html.j2:236
2205msgid ""
2206"<strong>Mentors:</strong> <a href=\"https://www.goebel-"
2207"consult.de/\">Hartmut Goebel</a>, Jeff Burdges, Christian Grothoff"
2208msgstr ""
2209
2210#: template/gsoc.html.j2:245
2211msgid ""
2212"There is a push for migrating our CI to Gitlab. The CI should eventually "
2213"not just run \"make check\" on various platforms, but also perform tests "
2214"with multiple peers running in different VMs with specific network "
2215"topologies (i.e. NAT) between them being simulated. The CI should also be"
2216" integrated with Gauger for performance regression analysis. Running jobs"
2217" only when dependencies have changed and scripting more granular triggers"
2218" or ideally automatic dependency discovery (as done by the autotools) is "
2219"also important."
2220msgstr ""
2221
2222#: template/gsoc.html.j2:257
2223msgid "<strong>Mentors:</strong> TBD"
2224msgstr ""
2225
2226#: template/gsoc.html.j2:267
2227msgid ""
2228"One great problem of the current Internet is the lack of "
2229"disintermediation. When people want to talk they need a chat service. "
2230"When they want to share files they need a file transfer service. Although"
2231" GNUnet already possesses quite advanced integration into Linux "
2232"networking, a little extra work is needed for existing applications like "
2233"irc, www, ftp, rsh, nntpd to run over it in a peer-to-peer way, simply by"
2234" using a GNS hostname like friend.gnu. Once people have added a person to"
2235" their GNS they can immediately message, exchange files and suchlike "
2236"directly, with nothing but the GNUnet in the middle, using applications "
2237"that have been distributed with unix systems ever since the 1980's. We "
2238"can produce an OS distribution where these things work out of the box "
2239"with the nicknames of people instead of cloud services. For more "
2240"information and context, read"
2241msgstr ""
2242
2243#: template/gsoc.html.j2:288
2244msgid "<strong>Mentors:</strong> lynX &amp; dvn"
2245msgstr ""
2246
2247#: template/gsoc.html.j2:296
2248msgid ""
2249"Implement the AnycastExit spec to enable GNUnet clients to connect over "
2250"Tor."
2251msgstr ""
2252
2253#: template/gsoc.html.j2:302 template/gsoc.html.j2:337
2254#: template/gsoc.html.j2:352
2255msgid "<strong>Mentors:</strong> Jeff Burdges"
2256msgstr ""
2257
2258#: template/gsoc.html.j2:307
2259msgid ""
2260"Note: There was a Special TLDs spec to allow Tor to resolve domain names "
2261"using GNS over Tor too, but currently that's on hold until folks think "
2262"more about how names should be moved around the local system. We're "
2263"calling this more collaborative approach NSS2 for now."
2264msgstr ""
2265
2266#: template/gsoc.html.j2:316 template/gsoc.html.j2:456
2267#: template/gsoc.html.j2:496 template/gsoc.html.j2:526
2268msgid "Required Skills: C"
2269msgstr ""
2270
2271#: template/gsoc.html.j2:329
2272msgid ""
2273"Improve the Rust implementation of GNUnet utils, possibly including "
2274"adding support for asynchronous IO using mio, or perhaps a higher level "
2275"asynchronous IO library built upon it, such as rotor, mioco, eventual_io,"
2276" or gj."
2277msgstr ""
2278
2279#: template/gsoc.html.j2:345
2280msgid ""
2281"Implementation of a replacement for PANDA (see Pond) with better "
2282"security, and maybe integration with the GNU Name System for key "
2283"exchange."
2284msgstr ""
2285
2286#: template/gsoc.html.j2:357
2287msgid "Required Skills: Rust or C, crypto"
2288msgstr ""
2289
2290#: template/gsoc.html.j2:362 template/gsoc.html.j2:419
2291#: template/gsoc.html.j2:461 template/gsoc.html.j2:501
2292msgid "Difficulty level: high"
2293msgstr ""
2294
2295#: template/gsoc.html.j2:370
2296msgid ""
2297"Implement different place types and file sharing by creating a new place "
2298"for the shared content."
2299msgstr ""
2300
2301#: template/gsoc.html.j2:376
2302msgid "Place types to be implemented:"
2303msgstr ""
2304
2305#: template/gsoc.html.j2:380
2306msgid ""
2307"<ul> <li>File: generic file with comments</li> <li>Image: display an "
2308"image with comments referencing a region of the image</li> <li>Sound: "
2309"play a sound file with comments referencing a timestamp</li> "
2310"<li>Directory/Album: pointers to File / Image / Sound places</li> "
2311"<li>Event: with RSVP</li> <li>Survey: ask your social neighborhood "
2312"questions in a structured form</li> </ul>"
2313msgstr ""
2314
2315#: template/gsoc.html.j2:391
2316msgid "Also provide the following UI functionality:"
2317msgstr ""
2318
2319#: template/gsoc.html.j2:395
2320msgid ""
2321"<ul> <li>Fork existing channels, reorganize people into new chatrooms or "
2322"channels.</li> <li>Share a post (edit and repost something elsewhere, on "
2323"a fan page for example).</li> <li>Edit a previously published post + "
2324"offer edit history to readers.</li> <li>Control expiry of channel "
2325"history.</li> </ul>"
2326msgstr ""
2327
2328#: template/gsoc.html.j2:404
2329msgid ""
2330"See also <a "
2331"href=\"http://secushare.org/features\">http://secushare.org/features</a>"
2332msgstr ""
2333
2334#: template/gsoc.html.j2:409
2335msgid "<strong>Mentors:</strong> lynX"
2336msgstr ""
2337
2338#: template/gsoc.html.j2:414
2339msgid "Required Skills: C/C++"
2340msgstr ""
2341
2342#: template/gsoc.html.j2:427
2343msgid ""
2344"Implement aggregation of distributed state from various channels in order"
2345" to provide for a powerful social graph API capable of producing social "
2346"network profiles, dashboards, a calendar out of upcoming event "
2347"invitations (if available), social search functionality and most of all "
2348"to make it easy for users to adopt cryptographic identities of their "
2349"contacts/friends simply by finding them in the social graph of their "
2350"existing contacts (\"This is Linda. You have 11 contacts in common with "
2351"her. [ADD]\")."
2352msgstr ""
2353
2354#: template/gsoc.html.j2:445
2355msgid ""
2356"Related to <a "
2357"href=\"http://secushare.org/rendezvous\">secushare.org/rendezvous</a>"
2358msgstr ""
2359
2360#: template/gsoc.html.j2:451 template/gsoc.html.j2:491
2361msgid "<strong>Mentors:</strong> t3sserakt, lynX"
2362msgstr ""
2363
2364#: template/gsoc.html.j2:468
2365msgid ""
2366"<ul> <li> Emulate IMAP/SMTP protocols as necessary to transform "
2367"traditional mail clients into secushare user interfaces. </li> <li> Think"
2368" of ways to map e-mail addresses to secushare identities. </li> <li> "
2369"Encode or translate various e-mail features into secushare equivalents. "
2370"</li> <li> Parts of secushare are currently written in Rust, therefore "
2371"Rust is preferred for this task but it is not an requirement. </li> </ul>"
2372msgstr ""
2373
2374#: template/gsoc.html.j2:509
2375msgid ""
2376"Implementation of the GNUnet auction system described in Chapter 3 of <a "
2377"href=\"https://grothoff.org/christian/teich2017ms.pdf\">this thesis</a>. "
2378"Specific tasks are adding smart contract creation and round time "
2379"enforcement to libbrandt as well as creating the GNUnet auction service, "
2380"library and the three user interface programs create, info and join."
2381msgstr ""
2382
2383#: template/gsoc.html.j2:521
2384msgid "<strong>Mentors:</strong> mate, cg"
2385msgstr ""
2386
2387#: template/gsoc.html.j2:539
2388msgid ""
2389"Implementation of additional transports to make GNUnet communication more"
2390" robust in the presence of problematic networks: GNUnet-over-SMTP, "
2391"GNUnet-over-DNS"
2392msgstr ""
2393
2394#: template/gsoc.html.j2:546 template/gsoc.html.j2:560
2395msgid "<strong>Mentors:</strong> Matthias Wachs"
2396msgstr ""
2397
2398#: template/gsoc.html.j2:554
2399msgid ""
2400"Implementation of ALG-based NAT traversal methods (FTP/SIP-based hole "
2401"punching, better STUN support)"
2402msgstr ""
2403
2404#: template/gsoc.html.j2:568
2405msgid "<strong>Mentors:</strong> Matthias Wachs, Christian Grothoff, Jeff Burdges"
2406msgstr ""
2407
2408#: template/gsoc.html.j2:576
2409msgid ""
2410"Improving libaboss to make computation on shared secrets (including "
2411"repeated multiplication) based on <a "
2412"href=\"https://dl.acm.org/citation.cfm?doid=62212.62213\">Ben-Or et "
2413"al.</a> if possible. This in particular means moving libaboss to bignums "
2414"(gcry_mpi)."
2415msgstr ""
2416
2417#: template/gsoc.html.j2:589
2418msgid ""
2419"Please refer to the description for this project listed under GNU Guix "
2420"project ideas."
2421msgstr ""
2422
2423#: template/gsoc.html.j2:602
2424msgid ""
2425"Python 2.7 is reaching its end-of-life, and we want to get rid of the "
2426"dependency on Python. The existing gnunet-qr tool is a rather simple "
2427"wrapper around python-zbar, which itself wraps libzbar. The goal of this "
2428"project is to directly use libzbar to scan QR codes for GNUnet / the GNU "
2429"Name System (see also <a "
2430"href=\"https://bugs.gnunet.org/view.php?id=5562\">#5562</a>)."
2431msgstr ""
2432
2433#: template/gsoc.html.j2:612
2434msgid "<strong>Mentors:</strong> Christian Grothoff"
2435msgstr ""
2436
2437#: template/gsoc.html.j2:617
2438msgid "Required Skills:"
2439msgstr ""
2440
2441#: template/gsoc.html.j2:622
2442msgid "Difficulty level:"
2443msgstr ""
2444
2445#: template/gsoc.html.j2:627
2446msgid "Report:"
2447msgstr ""
2448
2449#: template/gsoc.html.j2:632
2450msgid "Unfinished/Abandoned as gnunet-qr was moved to C outside of GSoC."
2451msgstr ""
2452
2453#: template/gsoc.html.j2:642
2454msgid ""
2455"Implementation of a Web-based UI for GNUnet similar to GNUnet-Gtk with a "
2456"yet to be determined framework such as Angular2. This includes the design"
2457" and implementation of not yet existing <a "
2458"href=\"http://jsonapi.org/\">REST APIs</a> that expose the <a "
2459"href=\"https://docs.gnunet.org/doxygen/modules.html\">GNUnet API</a>."
2460msgstr ""
2461
2462#: template/gsoc.html.j2:657
2463msgid "Required Skills: C, JavaScript, CSS"
2464msgstr ""
2465
2466#: template/gsoc.html.j2:667
2467msgid ""
2468"Report: <a href=\"gsoc-2018-gnunet-webui.html\">GSoC 2018: GNUnet "
2469"WebUI</a>"
2470msgstr ""
2471
2472#: template/index.html.j2:8
2473msgid "The Internet of tomorrow needs GNUnet today"
2474msgstr ""
2475
2476#: template/index.html.j2:26
2477msgid "Latest news"
2478msgstr ""
2479
2480#: template/index.html.j2:32
2481msgid "Older news entries"
2482msgstr ""
2483
2484#: template/index.html.j2:47
2485msgid "The Internet is broken"
2486msgstr ""
2487
2488#: template/index.html.j2:49
2489msgid ""
2490"The conventional Internet is currently like a system of roads with deep "
2491"potholes and highwaymen all over the place. Even if you still can use the"
2492" roads (e.g. send emails, or browse websites) your vehicle might get "
2493"hijacked, damaged, or long arms might reach into its back and steal your "
2494"items (data) to use it against you and sell it to others - while you "
2495"can&#39;t even notice the thievery nor accuse and hold the scroungers "
2496"accountable. <!-- Proposal from Fabian Gerlach: The conventional Internet"
2497" is currently like a system of roads with deep potholes and surveillance "
2498"cameras all over the place. Even if you still can use the roads (e.g. "
2499"send emails, or browse websites) your vehicle might gets damaged. And the"
2500" surveillance cameras will create a movement profile about your life: "
2501"They recognize your car license plate, track you everywhere you drive, "
2502"and save this information in a central data base. --> The Internet was "
2503"not designed with security in mind: protecting against address forgery, "
2504"routers learning metadata, or choosing trustworthy third parties is "
2505"nontrivial and sometimes impossible. <!-- Proposal from Fabian Gerlach: "
2506"The Internet is not designed with security in mind: The network generally"
2507" learns too much about users; it has insecure defaults and high "
2508"complexity; and it is centralized. That makes it very vulnerable for "
2509"multiple attacks massively threatening our freedom. -->"
2510msgstr ""
2511
2512#: template/index.html.j2:94
2513msgid "GNUnet helps building a new Internet"
2514msgstr ""
2515
2516#: template/index.html.j2:96
2517msgid ""
2518"GNUnet is a network protocol stack for building secure, distributed, and "
2519"privacy-preserving applications.<br/> With strong roots in <a "
2520"class=\"link\" href=\"https://bib.gnunet.org\">academic research</a>, our"
2521" goal is to replace the <a class=\"link\" href=\"https://secushare.org"
2522"/broken-internet\">old insecure Internet</a> protocol stack."
2523msgstr ""
2524
2525#: template/index.html.j2:119
2526msgid "Metadata is exposed"
2527msgstr ""
2528
2529#: template/index.html.j2:121
2530msgid ""
2531"Your metadata is just as revealing as the actual content; and it gets "
2532"exposed on the Internet.<br> Even though transport encryption is "
2533"increasingly being deployed on the Internet, it still reveals data that "
2534"can threaten democracy: the identities of senders and receivers, the "
2535"times, frequency and the volume of communication are all still "
2536"revealed.<br>"
2537msgstr ""
2538
2539#: template/index.html.j2:150
2540msgid "GNUnet provides privacy-by design"
2541msgstr ""
2542
2543#: template/index.html.j2:152
2544msgid ""
2545"It provides <a class=\"link\" "
2546"href=\"https://www.w3.org/2014/strint/papers/65.pdf\"> improving "
2547"addressing, routing, naming and content distribution</a> in a technically"
2548" robust manner - as opposed to ad-hoc designs in place today. <!-- "
2549"Proposal from fabian gerlach: GNUnet is built <a "
2550"href=\"https://www.w3.org/2014/strint/papers/65.pdf\">\"privacy by "
2551"design\"</a> and \"distributed by design\". This improves addressing, "
2552"routing, naming and content distribution in a technically robust manner. "
2553"-->"
2554msgstr ""
2555
2556#: template/index.html.j2:177
2557msgid "Freedoms are not respected"
2558msgstr ""
2559
2560#: template/index.html.j2:179
2561msgid ""
2562"Today, monitoring increasingly centralized infrastructure, proprietary "
2563"implementations, traffic shapers and firewalls restrict all of the <a "
2564"class=\"link\" href=\"https://www.gnu.org/philosophy/free-"
2565"sw.html\">essential freedoms</a> to various degrees."
2566msgstr ""
2567
2568#: template/index.html.j2:203
2569msgid "GNUnet supports a free and open society"
2570msgstr ""
2571
2572#: template/index.html.j2:205
2573msgid ""
2574"GNUnet is a self-organizing network and it is <a class=\"link\" "
2575"href=\"https://www.gnu.org/philosophy/free-sw.html\">free software</a> as"
2576" in freedom. GNUnet puts you in control of your data. You determine which"
2577" data to share with whom, and you&#39;re not pressured to accept "
2578"compromises. It gives users freedoms to securely access information "
2579"(\"run\" the network), to study all aspects of the network&#39;s "
2580"operation (\"access the code\"), to distribute information (\"copy\"), as"
2581" well as the freedom to deploy new applications (\"modify\")."
2582msgstr ""
2583
2584#: template/index.html.j2:229
2585msgid "Decentralization is the key, but hard"
2586msgstr ""
2587
2588#: template/index.html.j2:232
2589msgid ""
2590"<!-- replaced with Proposal from Fabian Gerlach: It seems as if every "
2591"other distributed or P2P project develops its own library stack, covering"
2592" transports, stream muxing, discovery and others. This divides effort and"
2593" multiplies bug count. --> Instead of sharing common components and tools"
2594" for building P2P systems, every P2P project seems to re-invent the "
2595"wheel. <!-- TODO: rework this sentence. --> This heightens the effort and"
2596" increases the potential number of vulnerabilities."
2597msgstr ""
2598
2599#: template/index.html.j2:264
2600msgid "GNUnet is a framework"
2601msgstr ""
2602
2603#: template/index.html.j2:266
2604msgid ""
2605"It offers a metadata-preserving foundation for your application. It "
2606"offers components for addressing, reliable encrypted channels with "
2607"advanced routing and resource discovery and naming. Our work is based on "
2608"continuous research spanning almost two decades."
2609msgstr ""
2610
2611#: template/index.html.j2:286
2612msgid "Learn more"
2613msgstr ""
2614
2615#: template/index.html.j2:295
2616msgid "Get started"
2617msgstr ""
2618
2619#: template/install-on-archpi.html.j2:6
2620msgid "Tutorial: GNUnet on Arch Linux/Pi"
2621msgstr ""
2622
2623#: template/install-on-archpi.html.j2:16
2624msgid "Requirements for Raspberry Pi 3"
2625msgstr ""
2626
2627#: template/install-on-archpi.html.j2:40
2628msgid "Get the Source Code"
2629msgstr ""
2630
2631#: template/install-on-archpi.html.j2:62
2632#: template/install-on-debian9.html.j2:131
2633msgid "In Addition: gnunet-gtk"
2634msgstr ""
2635
2636#: template/install-on-archpi.html.j2:81
2637msgid "Run"
2638msgstr ""
2639
2640#: template/install-on-archpi.html.j2:133
2641#: template/install-on-openwrt.html.j2:111
2642msgid "Make sure, it works!"
2643msgstr ""
2644
2645#: template/install-on-debian9.html.j2:6
2646msgid "Tutorial: GNUnet on Debian 9"
2647msgstr ""
2648
2649#: template/install-on-debian9.html.j2:9
2650#: template/install-on-ubuntu1804.html.j2:9
2651msgid "Introduction"
2652msgstr ""
2653
2654#: template/install-on-debian9.html.j2:29 template/install-on-macos.html.j2:17
2655#: template/install-on-netbsd.html.j2:19
2656#: template/install-on-ubuntu1804.html.j2:26
2657msgid "Requirements"
2658msgstr ""
2659
2660#: template/install-on-debian9.html.j2:46
2661#: template/install-on-ubuntu1804.html.j2:41
2662msgid "Make an installation directory"
2663msgstr ""
2664
2665#: template/install-on-debian9.html.j2:60 template/install-on-macos.html.j2:134
2666#: template/install-on-netbsd.html.j2:237
2667#: template/install-on-ubuntu1804.html.j2:53
2668msgid "Get the source code"
2669msgstr ""
2670
2671#: template/install-on-debian9.html.j2:79 template/install-on-macos.html.j2:142
2672#: template/install-on-netbsd.html.j2:245
2673#: template/install-on-ubuntu1804.html.j2:61
2674msgid "Compile and Install"
2675msgstr ""
2676
2677#: template/install-on-debian9.html.j2:104
2678#: template/install-on-ubuntu1804.html.j2:70
2679msgid "Option 1: GNUnet for testing / usage"
2680msgstr ""
2681
2682#: template/install-on-debian9.html.j2:117
2683#: template/install-on-ubuntu1804.html.j2:82
2684msgid "Option 2: GNUnet for development"
2685msgstr ""
2686
2687#: template/install-on-debian9.html.j2:154
2688#: template/install-on-ubuntu1804.html.j2:97
2689msgid "Install GNUnet plugin for name resolution"
2690msgstr ""
2691
2692#: template/install-on-debian9.html.j2:208
2693#: template/install-on-ubuntu1804.html.j2:134
2694msgid "Create configuration file"
2695msgstr ""
2696
2697#: template/install-on-debian9.html.j2:228
2698#: template/install-on-ubuntu1804.html.j2:156
2699msgid "Use GNUnet!"
2700msgstr ""
2701
2702#: template/install-on-debian9.html.j2:233
2703#: template/install-on-ubuntu1804.html.j2:162
2704msgid "Uninstall GNUnet and its dependencies"
2705msgstr ""
2706
2707#: template/install-on-macos.html.j2:6
2708msgid "Tutorial: GNUnet on macOS 10.14 (Mojave)"
2709msgstr ""
2710
2711#: template/install-on-macos.html.j2:24 template/install-on-netbsd.html.j2:36
2712#: template/install-on-openwrt.html.j2:15
2713msgid "Installation"
2714msgstr ""
2715
2716#: template/install-on-macos.html.j2:42 template/install-on-netbsd.html.j2:115
2717msgid "First steps"
2718msgstr ""
2719
2720#: template/install-on-macos.html.j2:109 template/install-on-netbsd.html.j2:195
2721msgid "Alternative: Installation from source"
2722msgstr ""
2723
2724#: template/install-on-macos.html.j2:154 template/install-on-netbsd.html.j2:265
2725msgid "Option 1: GNUnet for production / usage"
2726msgstr ""
2727
2728#: template/install-on-macos.html.j2:187 template/install-on-netbsd.html.j2:293
2729msgid "Option 2: GNUnet experimental"
2730msgstr ""
2731
2732#: template/install-on-netbsd.html.j2:6
2733msgid "Tutorial: GNUnet on NetBSD 8.0 CURRENT"
2734msgstr ""
2735
2736#: template/install-on-openwrt.html.j2:6
2737msgid "Tutorial: GNUnet on OpenWrt"
2738msgstr ""
2739
2740#: template/install-on-openwrt.html.j2:47
2741msgid "Configuration"
2742msgstr ""
2743
2744#: template/install-on-ubuntu1804.html.j2:6
2745msgid "Tutorial: GNUnet on Ubuntu 18.04"
2746msgstr ""
2747
2748#: template/install.html.j2:12
2749msgid ""
2750"Notice: GNUnet is still undergoing major development. It is largely "
2751"<i>not yet ready</i> for usage beyond developers."
2752msgstr ""
2753
2754#: template/install.html.j2:18
2755msgid ""
2756"<p>Please be aware that this project is still in an early alpha stage "
2757"when it comes to running software &#8211; its not an easy task to rewrite"
2758" the whole Internet! We are happy to get your <a "
2759"href=\"engage.html\">helping hand</a> anytime! Further information is "
2760"available in our <a href=\"https://docs.gnunet.org/#toc-Using-"
2761"GNUnet-1\">handbook</a>. If you have any queries about the installation "
2762"or the usage, please <a href=\"engage.html\">get in touch!</a></p>"
2763msgstr ""
2764
2765#: template/install.html.j2:30
2766msgid ""
2767"We recommend to use binary packages provided by the package manager "
2768"integrated within your Operating System. GNUnet is reportedly available "
2769"for at least: <ul> <li><a "
2770"href=\"https://pkgs.alpinelinux.org/package/edge/testing/x86_64/gnunet\">Alpine</a></li>"
2771" <li><a "
2772"href=\"https://www.archlinux.org/packages/community/x86_64/gnunet/\">Arch</a></li>"
2773" <li><a "
2774"href=\"https://packages.debian.org/search?keywords=gnunet\">Debian</a></li>"
2775" <li><a "
2776"href=\"https://copr.fedorainfracloud.org/coprs/yosl/gnunet/\">Fedora "
2777"(Copr)</a></li> <li><a "
2778"href=\"https://guix.gnu.org/en/packages/G/\">Guix</a></li> <li><a "
2779"href=\"https://github.com/Homebrew/homebrew-"
2780"core/blob/master/Formula/gnunet.rb\">Homebrew</a></li> <li><a "
2781"href=\"https://nixos.org/nixos/packages.html?attr=gnunet&channel=nixpkgs-"
2782"unstable&query=gnunet\">NixOS</a></li> <li><a href=\"install-on-"
2783"openwrt.html\">OpenWrt</a></li> </ul> If GNUnet is available for your "
2784"Operating System and it is missing, send us feedback so that we can add "
2785"it to this list. Furthermore, if you are interested in packaging GNUnet "
2786"for your Operating System, get in touch with us at gnunet-"
2787"developers@gnu.org if you require help with this job. If you were using "
2788"an Operating System with the APT package manager, GNUnet could be "
2789"installed as simple as:"
2790msgstr ""
2791
2792#: template/install.html.j2:61
2793msgid ""
2794"Next we describe a generic way to install from source. If you are using "
2795"one of the following Operating Systems these step-by-step guides might be"
2796" useful: <a href=\"install-on-archpi.html\">ArchPi</a>, <a href"
2797"=\"install-on-debian9.html\">Debian 9</a>, <a href=\"install-on-"
2798"macos.html\">Mac OS</a>, <a href=\"install-on-netbsd.html\">NetBSD</a>, "
2799"<a href=\"install-on-ubuntu1804.html\">Ubuntu 1804</a>. Be aware that not"
2800" all of them might be totally up-to-date! Please <a "
2801"href=\"engage.html\">ask us</a> if you get stuck."
2802msgstr ""
2803
2804#: template/install.html.j2:75
2805msgid ""
2806"First, install the <a "
2807"href=\"https://git.gnunet.org/gnunet.git/tree/README\">required "
2808"dependencies</a> of GNUnet. There are base requirements and optional "
2809"requirements."
2810msgstr ""
2811
2812#: template/install.html.j2:81
2813msgid ""
2814"Now, you need to decide if you want to install GNUnet from the release "
2815"tarball or from git. If you want to use GNUnet and there is no binary "
2816"package available for your OS, you should stick with the release tarball."
2817" If you want to develop using the most recent build, you should go with "
2818"the <a href=\"https://git.gnunet.org/\">git repository</a>."
2819msgstr ""
2820
2821#: template/install.html.j2:98
2822msgid "To compile gnunet from the git source you can do so by entering:"
2823msgstr ""
2824
2825#: template/install.html.j2:106
2826msgid ""
2827"Before building GNUnet, make sure that you setup the required groups and "
2828"add your user to the group <code>gnunet</code>:"
2829msgstr ""
2830
2831#: template/install.html.j2:117
2832msgid "To compile GNUnet, execute:"
2833msgstr ""
2834
2835#: template/install.html.j2:128
2836msgid ""
2837"You can find more configuration flags in the <a "
2838"href=\"https://git.gnunet.org/gnunet.git/tree/README\">README</a>.<br> "
2839"Install GNUnet with:"
2840msgstr ""
2841
2842#: template/install.html.j2:138
2843msgid "You can now start GNUnet by running:"
2844msgstr ""
2845
2846#: template/install.html.j2:146
2847msgid ""
2848"Check the <a href=\"https://docs.gnunet.org/handbook/gnunet.html#Minimal-"
2849"configuration\">handbook</a> for detailed documentation. For a more "
2850"hands-on experience, <a href=\"https://gnunet.org/en/use.html\">continue "
2851"here</a>."
2852msgstr ""
2853
2854#: template/livingstandards.html.j2:11
2855msgid "On this page you can find links to our technical specifications."
2856msgstr ""
2857
2858#: template/use.html.j2:6
2859msgid "How to use GNUnet - in a nutshell"
2860msgstr ""
2861
2862#: template/use.html.j2:12 template/use.html.j2:125
2863msgid "Filesharing"
2864msgstr ""
2865
2866#: template/use.html.j2:13
2867msgid "CADET"
2868msgstr ""
2869
2870#: template/use.html.j2:14
2871msgid "Minimal Groupchat"
2872msgstr ""
2873
2874#: template/use.html.j2:15
2875msgid "GNS with CLI"
2876msgstr ""
2877
2878#: template/use.html.j2:16
2879msgid "GNS with Browser"
2880msgstr ""
2881
2882#: template/use.html.j2:17 template/use.html.j2:448
2883msgid "VPN"
2884msgstr ""
2885
2886#: template/use.html.j2:18 template/use.html.j2:508
2887msgid "Conversation"
2888msgstr ""
2889
2890#: template/use.html.j2:19 template/use.html.j2:519
2891msgid "Trouble Shooting"
2892msgstr ""
2893
2894#: template/use.html.j2:34
2895msgid "Accessing GNUnet"
2896msgstr ""
2897
2898#: template/use.html.j2:78
2899msgid "Leaving GNUnet"
2900msgstr ""
2901
2902#: template/use.html.j2:88
2903msgid "Make sure your GNUnet installation works..."
2904msgstr ""
2905
2906#: template/use.html.j2:107
2907msgid "... and play around with it."
2908msgstr ""
2909
2910#: template/use.html.j2:179
2911msgid "CADET (and Chat)"
2912msgstr ""
2913
2914#: template/use.html.j2:219
2915msgid "Chatting with a (simple) client"
2916msgstr ""
2917
2918#: template/use.html.j2:283
2919msgid "Name resolution using GNS on the command line"
2920msgstr ""
2921
2922#: template/use.html.j2:360
2923msgid "Name resolution using GNS with a browser"
2924msgstr ""
2925
2926#: template/use.html.j2:521
2927msgid "You can't reach other people's nodes"
2928msgstr ""
2929
2930#: template/use.html.j2:557
2931msgid "OMG you guys broke my internet"
2932msgstr ""
2933
2934#: template/video.html.j2:12
2935msgid "Videos related to GNUnet"
2936msgstr ""
2937
2938#: template/news/index.html.j2:45
2939msgid "News archives:"
2940msgstr ""
2941