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