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