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