# Translations template for PROJECT. # Copyright (C) 2021 ORGANIZATION # This file is distributed under the same license as the PROJECT project. # FIRST AUTHOR , 2021. # msgid "" msgstr "" "Project-Id-Version: PROJECT VERSION\n" "Report-Msgid-Bugs-To: EMAIL@ADDRESS\n" "POT-Creation-Date: 2021-03-12 15:55+0100\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: Automatically generated\n" "Language-Team: none\n" "Language: ko\n" "MIME-Version: 1.0\n" "Content-Type: text/plain; charset=UTF-8\n" "Content-Transfer-Encoding: 8bit\n" "Generated-By: Babel 2.9.0\n" #: common/base.j2:5 common/news.j2:5 msgid "GNUnet" msgstr "" #: common/base.j2:6 common/news.j2:6 msgid "GNU's framework for secure p2p networking" msgstr "" #: common/footer.j2.inc:7 msgid "Contact" msgstr "" #: common/footer.j2.inc:8 common/navigation.j2.inc:49 msgid "GNUnet e.V." msgstr "" #: common/footer.j2.inc:9 template/about.html.j2:6 msgid "About GNUnet" msgstr "" #: common/footer.j2.inc:14 common/navigation.j2.inc:64 msgid "Bug Tracker" msgstr "" #: common/footer.j2.inc:19 template/copyright.html.j2:6 msgid "Copyright Assignment" msgstr "" #: common/footer.j2.inc:20 common/navigation.j2.inc:90 #: template/developers.html.j2:24 msgid "Bibliography" msgstr "" #: common/footer.j2.inc:31 msgid "Source code of this site." msgstr "" #: common/footer.j2.inc:32 msgid "Report issues with this website." msgstr "" #: common/navigation.j2.inc:38 msgid "About" msgstr "" #: common/navigation.j2.inc:39 news/index.html.j2:8 #: news/oldnews-2011.html.j2:13 news/oldnews-2013.html.j2:13 #: news/oldnews-2018.html.j2:13 news/oldnews-2019.html.j2:13 msgid "News" msgstr "" #: common/navigation.j2.inc:40 template/index.html.j2:289 msgid "Applications" msgstr "" #: common/navigation.j2.inc:44 msgid "Community" msgstr "" #: common/navigation.j2.inc:47 template/index.html.j2:292 msgid "Engage" msgstr "" #: common/navigation.j2.inc:48 msgid "GSoC Projects" msgstr "" #: common/navigation.j2.inc:50 msgid "Copyright for Contributors" msgstr "" #: common/navigation.j2.inc:51 msgid "IRC Archive" msgstr "" #: common/navigation.j2.inc:58 msgid "Development" msgstr "" #: common/navigation.j2.inc:61 msgid "System Architecture" msgstr "" #: common/navigation.j2.inc:63 template/roadmap.html.j2:6 msgid "Roadmap" msgstr "" #: common/navigation.j2.inc:65 template/gnurl.html.j2:186 msgid "Source Code" msgstr "" #: common/navigation.j2.inc:66 msgid "Source Code Documentation" msgstr "" #: common/navigation.j2.inc:67 msgid "Continuous Integration" msgstr "" #: common/navigation.j2.inc:68 msgid "Development Tutorial" msgstr "" #: common/navigation.j2.inc:79 msgid "Documentation" msgstr "" #: common/navigation.j2.inc:82 template/install.html.j2:6 msgid "Install" msgstr "" #: common/navigation.j2.inc:83 template/install-on-openwrt.html.j2:76 msgid "Use" msgstr "" #: common/navigation.j2.inc:84 msgid "Videos" msgstr "" #: common/navigation.j2.inc:85 template/glossary.html.j2:6 msgid "Glossary" msgstr "" #: common/navigation.j2.inc:86 msgid "Handbook" msgstr "" #: common/navigation.j2.inc:87 template/livingstandards.html.j2:8 msgid "Living Standards" msgstr "" #: common/navigation.j2.inc:88 msgid "REST API" msgstr "" #: common/navigation.j2.inc:89 msgid "FAQ" msgstr "" #: news/index.html.j2:11 news/oldnews-2011.html.j2:16 #: news/oldnews-2013.html.j2:16 news/oldnews-2018.html.j2:16 #: news/oldnews-2019.html.j2:16 msgid "News posts about changes related to GNUnet such as releases and events" msgstr "" #: news/index.html.j2:16 news/oldnews-2011.html.j2:21 #: news/oldnews-2013.html.j2:21 news/oldnews-2018.html.j2:21 #: news/oldnews-2019.html.j2:21 msgid "subscribe to our RSS feed" msgstr "" #: news/index.html.j2:36 news/oldnews-2011.html.j2:40 #: news/oldnews-2013.html.j2:40 news/oldnews-2018.html.j2:40 #: news/oldnews-2019.html.j2:40 msgid "read more" msgstr "" #: news/index.html.j2:45 msgid "News archives:" msgstr "" #: template/about.html.j2:11 msgid "What is GNUnet?" msgstr "" #: template/about.html.j2:13 msgid "" "GNUnet is an alternative network stack for building secure, decentralized " "and privacy-preserving distributed applications. Our goal is to replace the " "old insecure Internet protocol stack. Starting from an application for " "secure publication of files, it has grown to include all kinds of basic " "protocol components and applications towards the creation of a GNU internet." msgstr "" #: template/about.html.j2:23 msgid "" "Today, the actual use and thus the social requirements for a global network " "differs widely from those goals of 1970. While the Internet remains suitable " "for military use, where the network equipment is operated by a command " "hierarchy and when necessary isolated from the rest of the world, the " "situation is less tenable for civil society." msgstr "" #: template/about.html.j2:32 msgid "" "Due to fundamental Internet design choices, Internet traffic can be " "misdirected, intercepted, censored and manipulated by hostile routers on the " "network. And indeed, the modern Internet has evolved exactly to the point " "where, as Matthew Green put it, \"the " "network is hostile\"." msgstr "" #: template/about.html.j2:41 msgid "" "We believe liberal societies need a network architecture that uses the anti-" "authoritarian decentralized peer-to-peer paradigm and privacy-preserving " "cryptographic protocols. The goal of the GNUnet project is to provide a Free " "Software realization of this ideal." msgstr "" #: template/about.html.j2:49 msgid "" "Specifically, GNUnet tries to follow the following design principles, in " "order of importance:" msgstr "" #: template/about.html.j2:56 msgid "" "GNUnet must be implemented as Free Software." msgstr "" #: template/about.html.j2:60 msgid "" "GNUnet must minimize the amount of personally identifiable information " "exposed." msgstr "" #: template/about.html.j2:61 msgid "" "GNUnet must be fully distributed and resilient to external attacks and rogue " "participants." msgstr "" #: template/about.html.j2:62 msgid "" "GNUnet must be self-organizing and not depend on administrators or " "centralized infrastructure." msgstr "" #: template/about.html.j2:63 msgid "" "GNUnet must inform the user which other participants have to be trusted when " "establishing private communications." msgstr "" #: template/about.html.j2:64 msgid "GNUnet must be open and permit new peers to join." msgstr "" #: template/about.html.j2:65 msgid "GNUnet must support a diverse range of applications and devices." msgstr "" #: template/about.html.j2:66 msgid "GNUnet must use compartmentalization to protect sensitive information." msgstr "" #: template/about.html.j2:67 msgid "The GNUnet architecture must be resource efficient." msgstr "" #: template/about.html.j2:68 msgid "" "GNUnet must provide incentives for peers to contribute more resources than " "they consume." msgstr "" #: template/about.html.j2:72 msgid "" "To get know and learn more, please check our handbook, especially the chapter on \"Key Concepts" "\", explaining the fundamental concepts of GNUnet: " msgstr "" #: template/about.html.j2:88 msgid "More Resources" msgstr "" #: template/about.html.j2:90 msgid "" "There are many more resources to learn about GNUnet besides the handbook, such as the " "bibliography with papers covering " "the various layers, many videos or a brief glossary." msgstr "" #: template/about.html.j2:95 msgid "" "You are most welcome to get engaged into the " "conversation, install GNUnet, use it and contribute and get engaged " "in various ways." msgstr "" #: template/about.html.j2:100 msgid "" "Please be aware that this project is (despite of it's age) still in an early " "alpha stage when it comes to software – its not an easy task to " "rewrite the whole Internet!" msgstr "" #: template/about.html.j2:105 msgid "Current funding" msgstr "" #: template/about.html.j2:110 msgid "" "We're receiving funding from NLnet's Next Generation Internet funding line " "to document and implement the GNU Name System protocol in a way suitable for " "the IETF standardization process." msgstr "" #: template/about.html.j2:123 msgid "" "This project has received funding from the European Union’s Horizon 2020 " "research and innovation programme under the NGI_TRUST grant agreement no " "825618. The project aims to integrate re:claimID with the GNU Taler payment " "system in a pilot in order to demonstrate the practical feasibility and " "benefits of privacy enhancing technologies for users and commercial service " "providers. The project is called \"Decentralized Identities for Self-" "Sovereign End-users\" (DISSENS)." msgstr "" #: template/about.html.j2:141 msgid "" "We are grateful for free hosting offered by the following organizations:" msgstr "" #: template/about.html.j2:150 msgid "Past funding" msgstr "" #: template/about.html.j2:152 msgid "We are grateful for past funding from the following organizations:" msgstr "" #: template/applications.html.j2:7 msgid "Applications provided by GNUnet" msgstr "" #: template/applications.html.j2:13 template/gns.html.j2:7 msgid "The GNU Name System" msgstr "" #: template/applications.html.j2:15 msgid "" "The GNU Name System (GNS) is a fully decentralized " "replacement for the Domain Name System (DNS). Instead of using a hierarchy, " "GNS uses a directed graph. Naming conventions are similar to DNS, but " "queries and replies are private even with respect to peers providing the " "answers. The integrity of records and privacy of look-ups is " "cryptographically secured. " msgstr "" #: template/applications.html.j2:38 msgid "Self-sovereign, decentralized identity provider" msgstr "" #: template/applications.html.j2:40 msgid "" "re:claimID is a decentralized " "Identity Provider (IdP) service built in top of the GNU Name System. It " "allows users to securely share personal information with websites using " "standardized protocols (OpenID Connect)." msgstr "" #: template/applications.html.j2:57 msgid "Filesharing (Alpha)" msgstr "" #: template/applications.html.j2:59 msgid "" "GNUnet filesharing is an application that aims " "to provide censorship-resistant, anonymous filesharing. The publisher is " "empowered to make a gradual choice between performance and anonymity." msgstr "" #: template/applications.html.j2:73 msgid "Conversation (Pre-Alpha)" msgstr "" #: template/applications.html.j2:75 msgid "" "GNUnet conversation is an application that provides secure voice " "communication in a fully decentralized way by employing GNUnet for routing " "and transport." msgstr "" #: template/applications.html.j2:91 msgid "Applications utilizing GNUnet" msgstr "" #: template/applications.html.j2:97 msgid "GNU Taler (Alpha)" msgstr "" #: template/applications.html.j2:99 msgid "" "GNU Taler is a new privacy-preserving " "electronic payment system. Payments are cryptographically secured and are " "confirmed within milliseconds with extremely low transaction costs." msgstr "" #: template/applications.html.j2:118 msgid "secushare" msgstr "" #: template/applications.html.j2:120 msgid "" "secushare is creating a decentralized " "social networking application on top of GNUnet. Using overlay multicast and " "the extensible PSYC protocol, notifications are distributed end-to-end " "encrypted to authorized recipients only." msgstr "" #: template/applications.html.j2:139 msgid "pretty Easy privacy" msgstr "" #: template/applications.html.j2:141 msgid "" "pretty Easy privacy (p≡p) is " "creating a usable end-to-end encrypted e-mail solution using opportunistic " "key exchange. p≡p will use GNUnet to protect metadata and exploit new " "cryptographic protocols to verify keys." msgstr "" #: template/applications.html.j2:160 msgid "Cadet-GTK" msgstr "" #: template/applications.html.j2:162 msgid "" "Cadet-GTK is a " "convenient but feature-rich graphical application providing messaging using " "especially the CADET subsystem. It is developed using GTK and libhandy for a " "convergent design." msgstr "" #: template/applications.html.j2:180 msgid "groupchat" msgstr "" #: template/applications.html.j2:182 msgid "" "groupchat is a " "terminal user interface providing messaging using especially the CADET " "subsystem. It is developed using nim. Cadet-GTK and groupchat are planned to " "be compatible." msgstr "" #: template/architecture.html.j2:6 msgid "GNUnet System Architecture" msgstr "" #: template/architecture.html.j2:20 msgid "Foundations" msgstr "" #: template/architecture.html.j2:22 msgid "" "The foundations of GNUnet are a distributed hash table (R5N), an SCTP-like " "end-to-end encrypted messaging layer (CADET), a public key infrastructure " "(GNS) and a pluggable transport system (TRANSPORT).
Using public keys " "for addresses and self-organized decentralized routing algorithms, these " "subsystems replace the traditional TCP/IP stack." msgstr "" #: template/architecture.html.j2:35 msgid "Security" msgstr "" #: template/architecture.html.j2:38 msgid "" "GNUnet is implemented using a multi-process architecture. Each subsystem " "runs as a separate process, providing fault-isolation and enabling tight " "permissions to be granted to each subsystem. Naturally, the implementation " "is a GNU package, and will always " "remain free software." msgstr "" #: template/architecture.html.j2:52 msgid "System architecture" msgstr "" #: template/architecture.html.j2:58 msgid "Subsystems" msgstr "" #: template/architecture.html.j2:67 msgid "libgnunetutil" msgstr "" #: template/architecture.html.j2:73 msgid "APIs" msgstr "" #: template/architecture.html.j2:86 msgid "Legend" msgstr "" #: template/contact.html.j2:6 msgid "Contact information" msgstr "" #: template/contact.html.j2:11 msgid "The mailing list" msgstr "" #: template/contact.html.j2:13 msgid "" "An archived, public mailing list for GNUnet is hosted at https://lists.gnu.org/" "mailman/listinfo/gnunet-developers. You can send messages to the list at " "gnunet-developers@gnu.org." msgstr "" #: template/contact.html.j2:23 msgid "The IRC channel" msgstr "" #: template/contact.html.j2:25 msgid "" "#gnunet is reachable via irc." "freenode.net. There is also an archive available." msgstr "" #: template/contact.html.j2:38 msgid "Contacting individuals" msgstr "" #: template/contact.html.j2:40 msgid "" "GNUnet developers are generally reachable at either PSEUDONYM@gnunet." "org or LASTNAME@gnunet.org. Most of us support receiving GnuPG " "encrypted Emails. Urgent and sensitive security issues may be addressed to " "the GNU maintainers schanzen and grothoff." msgstr "" #: template/contact.html.j2:53 msgid "Reporting bugs" msgstr "" #: template/contact.html.j2:55 msgid "" "We track open feature requests and bugs for projects within GNUnet in our Bug tracker. You can also report bugs " "or feature requests to the bug-gnunet mailing list. The mailinglist requires no " "subscription." msgstr "" #: template/copyright.html.j2:11 msgid "" "

Contributors to GNUnet with Git access must sign the copyright assignment to ensure that the GNUnet e.V. --- Taler Systems SA agreement on licensing and collaborative " "development of the GNUnet and GNU Taler projects is satisfied.

" msgstr "" #: template/copyright.html.j2:22 msgid "" "

The agreements ensure that the code will continue to be made available " "under free software licenses, but gives developers the freedom to move code " "between GNUnet and GNU Taler without worrying about licenses and to give the " "company the ability to dual-license (for example, so that we can distribute " "via App-stores that are hostile to free software).

" msgstr "" #: template/copyright.html.j2:30 msgid "" "

Minor contributions (basically, anyone without Git access) do not require " "copyright assignment. Pseudonymous contributions are accepted, in this case " "simply sign the agreement with your pseudonym. Scanned copies are " "sufficient, but snail mail is preferred.

" msgstr "" #: template/developers.html.j2:5 msgid "GNUnet for developers" msgstr "" #: template/developers.html.j2:13 msgid "Repositories" msgstr "" #: template/developers.html.j2:16 msgid "" "A list of our Git repositories can be found on our our Git Server." msgstr "" #: template/developers.html.j2:27 msgid "" "Technical papers can be found in our bibliography." msgstr "" #: template/developers.html.j2:34 msgid "Discussion" msgstr "" #: template/developers.html.j2:37 msgid "" "We have a mailing list for developer discussions. You can subscribe to or " "read the list archive at http://lists.gnu.org/mailman/listinfo/gnunet-developers." msgstr "" #: template/developers.html.j2:47 msgid "Regression Testing" msgstr "" #: template/developers.html.j2:50 msgid "" "We have Buildbot automation tests to " "detect regressions and check for portability at https://old.gnunet.org/buildbot/gnunet/." msgstr "" #: template/developers.html.j2:59 msgid "Code Coverage Analysis" msgstr "" #: template/developers.html.j2:62 msgid "" "We use LCOV to " "analyze the code coverage of our tests, the results are available at https://old.gnunet.org/coverage/." msgstr "" #: template/developers.html.j2:72 msgid "Performance Analysis" msgstr "" #: template/developers.html.j2:75 msgid "" "We use Gauger for performance " "regression analysis of the exchange backend at https://old.gnunet.org/gauger/." msgstr "" #: template/download.html.j2:7 template/gnurl.html.j2:209 msgid "Downloads" msgstr "" #: template/download.html.j2:11 msgid "" "Here you can download releases of our software and find links to the various " "versions." msgstr "" #: template/download.html.j2:17 msgid "0.11.x series" msgstr "" #: template/download.html.j2:18 msgid "tarball" msgstr "" #: template/download.html.j2:20 msgid "" "The tarball of the latest version can be obtained from GNU FTP and its " "mirrors." msgstr "" #: template/download.html.j2:30 msgid "git" msgstr "" #: template/download.html.j2:32 msgid "" "You can fetch the git tag of version 0.11.x from our development server:" msgstr "" #: template/engage.html.j2:6 msgid "Engage!" msgstr "" #: template/ev.html.j2:6 msgid "Verein zur Förderung von GNUnet e.V." msgstr "" #: template/ev.html.j2:11 msgid "About GNUnet e.V." msgstr "" #: template/ev.html.j2:13 msgid "" "On December 27th 2013 a group of GNUnet hackers met at 30c3 to create the " "\"Verein zur Förderung von GNUnet e.V.\", an association under German " "law to support GNUnet development. The Amtsgericht München registered " "the association on the 7th of March under VR 205287." msgstr "" #: template/ev.html.j2:22 msgid "" "The association is officially dedicated to supporting research, development " "and education in the area of secure decentralized networking in general, and " "GNUnet specifically. This is the official website for the association." msgstr "" #: template/ev.html.j2:31 msgid "Becoming a Member of GNUnet e.V." msgstr "" #: template/ev.html.j2:33 msgid "" "GNUnet developers with git (write) access can become members to participate " "in the decision process and formally support GNUnet e.V. For this, all you " "have to do is update the members.txt file in the gnunet-ev repository. There are no " "membership dues; however, members are required to support GNUnet e.V. and in " "particularly contribute to the technical development within their means. For " "further details, we refer to the Satzung (currently only available in German, translations " "welcome)." msgstr "" #: template/ev.html.j2:52 msgid "Governance" msgstr "" #: template/ev.html.j2:54 msgid "" "You can find our \"Satzung\", and the list of members under https://git.gnunet." "org/gnunet-ev.git/tree/satzung.tex. The current board consists of: " "
Vorsitz
Martin " "Schanzenbach
stellvertretender Vorsitz
t3sserakt
" "
Kassenwart
Florian Dold
Beisitzer
Christian Grothoff, ch3
" msgstr "" #: template/ev.html.j2:73 msgid "Official Meeting Notes" msgstr "" #: template/ev.html.j2:86 msgid "Support Us!" msgstr "" #: template/ev.html.j2:88 msgid "" "Everybody is welcome to support us via donations. For financial " "contributions, Europeans are able to donate via SEPA. We hope to setup " "accounts in other major currency areas in the future. You can also donate " "via Bitcoin, routing details are given below. Please note that we are unable " "to provide receipts for your donations. If you are planning to donate a " "significant amount of money, please contact us first as it might be better " "to come to a custom arrangement.
BitCoin
" "
1GNUnetpWeR9Zs3vipdvVywo1GseeksjUh
SEPA/IBAN
" "
DE67830654080004822650 (BIC/SWIFT: GENODEF1SLR)
" msgstr "" #: template/faq.html.j2:12 template/faq.html.j2:23 msgid "General" msgstr "" #: template/faq.html.j2:13 template/faq.html.j2:149 template/gns.html.j2:37 msgid "Features" msgstr "" #: template/faq.html.j2:15 template/faq.html.j2:594 msgid "Error messages" msgstr "" #: template/faq.html.j2:16 template/faq.html.j2:696 msgid "File-sharing" msgstr "" #: template/faq.html.j2:17 template/faq.html.j2:872 msgid "Contributing" msgstr "" #: template/faq.html.j2:26 msgid "What do I do if my question is not answered here?" msgstr "" #: template/faq.html.j2:28 msgid "" "A: There are many other sources of information. You can read additional " "documentation or ask the question on the help-gnunet@gnu.org mailing list or " "the #gnunet IRC on irc.freenode.net." msgstr "" #: template/faq.html.j2:36 msgid "When are you going to release the next version?" msgstr "" #: template/faq.html.j2:38 msgid "" "A: The general answer is, when it is ready. A better answer may be: earlier " "if you contribute (test, debug, code, document). Every release will be " "anounced on the info-gnunet@gnu.org mailing list and on planet GNU. You can subscribe to the mailing list or " "the RSS feed of this site to automatically receive a notification." msgstr "" #: template/faq.html.j2:49 msgid "Is the code free?" msgstr "" #: template/faq.html.j2:51 msgid "" "A: GNUnet is free software, available under the GNU Affero Public License (AGPL)." msgstr "" #: template/faq.html.j2:58 msgid "Are there any known bugs?" msgstr "" #: template/faq.html.j2:60 msgid "" "A: We track the list of currently known bugs in the Mantis system. Some bugs are occasionally reported " "directly to developers or the developer mailing list. This is discouraged " "since developers often do not have the time to feed these bugs back into the " "Mantis database. Please report bugs directly to the bug tracking system. If " "you believe a bug is sensitive, you can set its view status to private (this " "should be the exception)." msgstr "" #: template/faq.html.j2:73 template/faq.html.j2:193 msgid "Is there a graphical user interface?" msgstr "" #: template/faq.html.j2:75 msgid "" "A: gnunet-gtk is a separate download. The package contains various GTK+ " "based graphical interfaces, including a graphical tool for configuration." msgstr "" #: template/faq.html.j2:83 msgid "Why does gnunet-service-nse create a high CPU load?" msgstr "" #: template/faq.html.j2:85 msgid "" "A: The gnunet-service-nse process will initially compute a so-called "" "proof-of-work" which is used to convince the network that your peer is " "real (or, rather, make it expensive for an adversary to mount a Sybil attack " "on the network size estimator). The calculation is expected to take a few " "days, depending on how fast your CPU is. If the CPU load is creating a " "problem for you, you can set the value "WORKDELAY" in the "" "nse" section of your configuration file to a higher value. The default " "is "5 ms"." msgstr "" #: template/faq.html.j2:99 msgid "How does GNUnet compare to Tor?" msgstr "" #: template/faq.html.j2:101 msgid "" "A: Tor focuses on anonymous communication and censorship-resistance for TCP " "connections and, with the Tor Browser Bundle, for the Web in particular. " "GNUnet does not really have one focus; our theme is secure decentralized " "networking, but that is too broad to be called a focus." msgstr "" #: template/faq.html.j2:111 msgid "How does GNUnet compare to I2P?" msgstr "" #: template/faq.html.j2:113 msgid "" "A: Both GNUnet and I2P want to build a better, more secure, more " "decentralized Internet. However, on the technical side, there are almost no " "overlaps.

I2P is written in Java, and has (asymmetric) tunnels " "using onion (or garlic) routing as the basis for various (anonymized) " "applications. I2P is largely used via a Web frontend." msgstr "" #: template/faq.html.j2:124 msgid "Is GNUnet ready for use on production systems?" msgstr "" #: template/faq.html.j2:126 msgid "" "A: GNUnet is still undergoing major development. It is largely not yet ready " "for usage beyond developers. Your mileage will vary depending on the " "functionality you use, but you will always likely run into issues with our " "current low-level transport system. We are currently in the process of " "rewriting it (Project "Transport Next Generation [TNG]")" msgstr "" #: template/faq.html.j2:136 msgid "Is GNUnet build using distributed ledger technologies?" msgstr "" #: template/faq.html.j2:138 msgid "" "A: No. GNUnet is a new network protocol stack for building secure, " "distributed, and privacy-preserving applications. While a ledger could be " "built using GNUnet, we currently have no plans in doing so." msgstr "" #: template/faq.html.j2:151 msgid "What can I do with GNUnet?" msgstr "" #: template/faq.html.j2:153 msgid "" "A: GNUnet is a peer-to-peer framework, by which we mostly mean that it can " "do more than just one thing. Naturally, the implementation and documentation " "of some of the features that exist are more advanced than others." msgstr "" #: template/faq.html.j2:160 msgid "" "For users, GNUnet offers anonymous and non-anonymous file-sharing, a fully " "decentralized and censorship-resistant replacement for DNS and a mechanism " "for IPv4-IPv6 protocol translation and tunneling (NAT-PT with DNS-ALG)." msgstr "" #: template/faq.html.j2:171 msgid "Is it possible to surf the WWW anonymously with GNUnet?" msgstr "" #: template/faq.html.j2:173 msgid "" "A: It is not possible use GNUnet for anonymous browsing at this point. We " "recommend that you use Tor for anonymous surfing." msgstr "" #: template/faq.html.j2:181 msgid "Is it possible to access GNUnet via a browser as an anonymous WWW?" msgstr "" #: template/faq.html.j2:183 msgid "" "A: There is currently no proxy (like fproxy in Freenet) for GNUnet that " "would make it accessible with a browser. It is possible to build such a " "proxy and all one needs to know is the protocol used between browser and " "proxy and a swift look at the GNUnet code for file-sharing." msgstr "" #: template/faq.html.j2:195 msgid "" "A: There are actually a few graphical user interfaces for different " "functions. gnunet-setup is to configure GNUnet, and gnunet-fs-gtk is for " "file-sharing. There are a few other gnunet-XXX-gtk GUIs of lesser " "importance. Note that in order to obtain the GUI, you need to install the " "gnunet-gtk package, which is a separate download. gnunet-gtk is a meta GUI " "that integrates most of the other GUIs in one window. One exception is " "gnunet-setup, which must still be run separately at this time (as setup " "requires the peer to be stopped)." msgstr "" #: template/faq.html.j2:210 msgid "On top of which operating systems does GNUnet run?" msgstr "" #: template/faq.html.j2:212 msgid "" "A: GNUnet is being developed and tested primarily under Debian GNU/Linux. " "Furthermore, we regularly build and test GNUnet on Fedora, Ubuntu, Arch, " "FreeBSD and macOS. We have reports of working versions on many other GNU/" "Linux distributions; in the past we had reports of working versions on " "NetBSD, OpenBSD and Solaris. However, not all of those reports are recent, " "so if you cannot get GNUnet to work on those systems please let us know." msgstr "" #: template/faq.html.j2:228 msgid "Who runs the GNS root zone?" msgstr "" #: template/faq.html.j2:230 msgid "" "A: Short answer: you. The long answer is the GNUnet will ship with a default " "configuration of top-level domains. The governance of this default " "configuration is not yet established. In any case, the user will be able to " "modify this configuration at will. We expect normal users to have no need to " "edit their own GNS zone(s) unless they host services themselves." msgstr "" #: template/faq.html.j2:241 msgid "Where is the per-user GNS database kept?" msgstr "" #: template/faq.html.j2:243 msgid "" "A: The short answer is that the database is kept at the user's GNUnet peer. " "Now, a user may run multiple GNUnet peers, in which case the database could " "be kept at each peer (however, we don't have code for convenient " "replication). Similarly, multiple GNUnet peers can share one instance of the " "database --- the "gnunet-service-namestore" can be accessed from " "remote (via TCP). The actual data can be stored in a Postgres database, for " "which various replication options are again applicable. Ultimately, there " "are many options for how users can store (and secure) their GNS database." msgstr "" #: template/faq.html.j2:258 msgid "What is the expected average size of a GNS namestore database?" msgstr "" #: template/faq.html.j2:260 msgid "" "A: Pretty small. Based on our user study where we looked at browser " "histories and the number of domains visited, we expect that GNS databases " "will only grow to a few tens of thousands of entries, small enough to fit " "even on mobile devices." msgstr "" #: template/faq.html.j2:270 msgid "Is GNS resistant to the attacks on DNS used by the US?" msgstr "" #: template/faq.html.j2:272 msgid "" "A: We believe so, as there is no entity that any government could force to " "change the mapping for a name except for each individual user (and then the " "changes would only apply to the names that this user is the authority for). " "So if everyone used GNS, the only practical attack of a government would be " "to force the operator of a server to change the GNS records for his server " "to point elsewhere. However, if the owner of the private key for a zone is " "unavailable for enforcement, the respective zone cannot be changed and any " "other zone delegating to this zone will achieve proper resolution." msgstr "" #: template/faq.html.j2:286 msgid "What is the difference between GNS and CoDoNS?" msgstr "" #: template/faq.html.j2:288 msgid "" "A: CoDoNS decentralizes the DNS database (using a DHT) but preserves the " "authority structure of DNS. With CoDoNS, IANA/ICANN are still in charge, and " "there are still registrars that determine who owns a name.

With " "GNS, we decentralize the database and also decentralize the responsibility " "for naming: each user runs his own personal root zone and is thus in " "complete control of the names he uses. GNS also has many additional features " "(to keep names short and enable migration) which don't even make sense in " "the context of CoDoNS." msgstr "" #: template/faq.html.j2:304 msgid "What is the difference between GNS and SocialDNS?" msgstr "" #: template/faq.html.j2:306 msgid "" "A: Like GNS, SocialDNS allows each user to create DNS mappings. However, " "with SocialDNS the mappings are shared through the social network and " "subjected to ranking. As the social relationships evolve, names can thus " "change in surprising ways.

With GNS, names are primarily shared via " "delegation, and thus mappings will only change if the user responsible for " "the name (the authority) manually changes the record." msgstr "" #: template/faq.html.j2:320 msgid "What is the difference between GNS and ODDNS?" msgstr "" #: template/faq.html.j2:322 msgid "" "A: ODDNS is primarily designed to bypass the DNS root zone and the TLD " "registries (such as those for \".com\" and \".org\"). Instead of using " "those, each user is expected to maintain a database of (second-level) " "domains (like \"gnu.org\") and the IP addresses of the respective name " "servers. Resolution will fail if the target name servers change IPs." msgstr "" #: template/faq.html.j2:333 msgid "What is the difference between GNS and Namecoin?" msgstr "" #: template/faq.html.j2:340 msgid "What is the difference between GNS and Handshake?" msgstr "" #: template/faq.html.j2:346 msgid "What is the difference between GNS and ENS?" msgstr "" #: template/faq.html.j2:352 msgid "What is the difference between GNS and TrickleDNS?" msgstr "" #: template/faq.html.j2:354 msgid "" "A: TrickleDNS pushes ("critical") DNS records between DNS " "resolvers of participating domains to provide "better availability, " "lower query resolution times, and faster update propagation". Thus " "TrickleDNS is focused on defeating attacks on the availability (and " "performance) of record propagation in DNS, for example via DDoS attacks on " "DNS root servers. TrickleDNS is thus concerned with how to ensure " "distribution of authoritative records, and authority remains derived from " "the DNS hierarchy." msgstr "" #: template/faq.html.j2:367 msgid "" "Does GNS require real-world introduction (secure PKEY exchange) in the style " "of the PGP web of trust?" msgstr "" #: template/faq.html.j2:369 msgid "" "A: For security, it is well known that an initial trust path between the two " "parties must exist. However, for applications where this is not required, " "weaker mechanisms can be used. For example, we have implemented a first-come-" "first-served (FCFS) authority which allows arbitrary users to register " "arbitrary names. The key of this authority is included with every GNUnet " "installation. Thus, any name registered with FCFS is in fact global and " "requires no further introduction. However, the security of these names " "depends entirely on the trustworthiness of the FCFS authority. The authority " "can be queried under the ".pin" TLD." msgstr "" #: template/faq.html.j2:384 msgid "" "How can a legitimate domain owner tell other people to not use his name in " "GNS?" msgstr "" #: template/faq.html.j2:386 msgid "" "A: Names have no owners in GNS, so there cannot be a "legitimate" " "domain owner. Any user can claim any name (as his preferred name or "" "pseudonym") in his NICK record. Similarly, all other users can choose " "to ignore this preference and use a name of their choice (or even assign no " "name) for this user." msgstr "" #: template/faq.html.j2:397 msgid "" "Did you consider the privacy implications of making your personal GNS zone " "visible?" msgstr "" #: template/faq.html.j2:399 msgid "" "A: Each record in GNS has a flag "private". Records are shared " "with other users (via DHT or zone transfers) only if this flag is not set. " "Thus, users have full control over what information about their zones is " "made public." msgstr "" #: template/faq.html.j2:409 msgid "Are \"Legacy Host\" (LEHO) records not going to be obsolete with IPv6?" msgstr "" #: template/faq.html.j2:411 msgid "" "A: The question presumes that (a) virtual hosting is only necessary because " "of IPv4 address scarcity, and (b) that LEHOs are only useful in the context " "of virtual hosting. However, LEHOs are also useful to help with X.509 " "certificate validation (as they specify for which legacy hostname the " "certificate should be valid). Also, even with IPv6 fully deployed and "" "infinite" IP addresses being available, we're not sure that virtual " "hosting would disappear. Finally, we don't want to have to wait for IPv6 to " "become commonplace, GNS should work with today's networks." msgstr "" #: template/faq.html.j2:425 msgid "" "Why does GNS not use a trust metric or consensus to determine globally " "unique names?" msgstr "" #: template/faq.html.j2:427 msgid "" "A: Trust metrics have the fundamental problem that they have thresholds. As " "trust relationships evolve, mappings would change their meaning as they " "cross each others thresholds. We decided that the resulting unpredictability " "of the resolution process was not acceptable. Furthermore, trust and " "consensus might be easy to manipulate by adversaries." msgstr "" #: template/faq.html.j2:438 msgid "How do you handle compromised zone keys in GNS?" msgstr "" #: template/faq.html.j2:440 msgid "" "A: The owner of a private key can create a revocation message. This one can " "then be flooded throughout the overlay network, creating a copy at all " "peers. Before using a public key, peers check if that key has been revoked. " "All names that involve delegation via a revoked zone will then fail to " "resolve. Peers always automatically check for the existence of a revocation " "message when resolving names." msgstr "" #: template/faq.html.j2:452 msgid "Could the signing algorithm of GNS be upgraded in the future?" msgstr "" #: template/faq.html.j2:454 msgid "" "A: Yes. In our efforts to standardize GNS, we have already modified the " "protocol to support alternative delegation records.

Naturally, " "deployed GNS implementations would have to be updated to support the new " "signature scheme. The new scheme can then be run in parallel with the " "existing system by using a new record type to indicate the use of a " "different cipher system." msgstr "" #: template/faq.html.j2:468 msgid "" "How can a GNS zone maintain several name servers, e.g. for load balancing?" msgstr "" #: template/faq.html.j2:470 msgid "" "A: We don't expect this to be necessary, as GNS records are stored (and " "replicated) in the R5N DHT. Thus the authority will typically not be " "contacted whenever clients perform a lookup. Even if the authority goes " "(temporarily) off-line, the DHT will cache the records for some time. " "However, should having multiple servers for a zone be considered truly " "necessary, the owner of the zone can simply run multiple peers (and share " "the zone's key and database among them)." msgstr "" #: template/faq.html.j2:483 msgid "" "Why do you believe it is worth giving up unique names for censorship " "resistance?" msgstr "" #: template/faq.html.j2:485 msgid "" "A: The GNU Name system offers an alternative to DNS that is censorship " "resistant. As with any security mechanism, this comes at a cost (names are " "not globally unique). To draw a parallel, HTTPS connections use more " "bandwidth and have higher latency than HTTP connections. Depending on your " "application, HTTPS may not be worth the cost. However, for users that are " "experiencing censorship (or are concerned about it), giving up globally " "unique names may very well be worth the cost. After all, what is a "" "globally" unique name worth, if it does not resolve?" msgstr "" #: template/faq.html.j2:499 msgid "Why do you say that DNS is 'centralized' and 'distributed'?" msgstr "" #: template/faq.html.j2:501 msgid "" "A: We say that DNS is 'centralized' because it has a central component / " "central point of failure --- the root zone and its management by IANA/ICANN. " "This centralization creates vulnerabilities. For example, the US government " "was able to reassign the management of the country-TLDs of Afganistan and " "Iraq during the wars at the beginning of the 21st century." msgstr "" #: template/faq.html.j2:512 msgid "How does GNS protect against layer-3 censorship?" msgstr "" #: template/faq.html.j2:514 msgid "" "A: GNS does not directly help with layer-3 censorship, but it does help " "indirectly in two ways:
  1. Many websites today use virtual hosting, " "so blocking a particular IP address causes much more collateral damage than " "blocking a DNS name. It thus raises the cost of censorship.
  2. " "Existing layer-3 circumvention solutions (such as Tor) would benefit from a " "censorship resistant naming system. Accessing Tor's ".onion" " "namespace currently requires users to use unmemorable cryptographic " "identifiers. With nicer names, Tor and tor2web-like services would be even " "easier to use.
" msgstr "" #: template/faq.html.j2:533 msgid "Does GNS work with search engines?" msgstr "" #: template/faq.html.j2:535 msgid "" "A: GNS creates no significant problems for search engines, as they can use " "GNS to perform name resolution as well as any normal user. Naturally, while " "we typically expect normal users to install custom software for name " "resolution, this is unlikely to work for search engines today. However, the " "DNS2GNS gateway allows search engines to use DNS to resolve GNS names, so " "they can still index GNS resources. However, as using DNS2GNS gateways " "breaks the cryptographic chain of trust, legacy search engines will " "obviously not obtain censorship-resistant names." msgstr "" #: template/faq.html.j2:549 msgid "How does GNS compare to the Unmanaged Internet Architecture (UIA)?" msgstr "" #: template/faq.html.j2:551 msgid "" "A: UIA and GNS both share the same basic naming model, which actually " "originated with Rivest's SDSI. However, UIA is not concerned about " "integration with legacy applications and instead focuses on universal " "connectivity between a user's many machines. In contrast, GNS was designed " "to interoperate with DNS as much as possible, and to also work as much as " "possible with the existing Web infrastructure. UIA is not at all concerned " "about legacy systems (clean slate)." msgstr "" #: template/faq.html.j2:564 msgid "Doesn't GNS increase the trusted-computing base compared to DNS(SEC)?" msgstr "" #: template/faq.html.j2:566 msgid "" "A: First of all, in GNS you can explicitly see the trust chain, so you know " "if a name you are resolving belongs to a friend, or a friend-of-a-friend, " "and can thus decide how much you trust the result. Naturally, the trusted-" "computing base (TCB) can become arbitrarily large this way --- however, " "given the name length restriction, for an individual name it is always less " "than about 128 entities." msgstr "" #: template/faq.html.j2:578 msgid "" "How does GNS handle SRV/TLSA records where service and protocol are part of " "the domain name?" msgstr "" #: template/faq.html.j2:580 msgid "" "A: When GNS splits a domain name into labels for resolution, it detects the " ""_Service._Proto" syntax, converts "Service" to the " "corresponding port number and "Proto" to the corresponding " "protocol number. The rest of the name is resolved as usual. Then, when the " "result is presented, GNS looks for the GNS-specific "BOX" record " "type. A BOX record is a record that contains another record (such as SRV or " "TLSA records) and adds a service and protocol number (and the original boxed " "record type) to it." msgstr "" #: template/faq.html.j2:596 msgid "" "I receive many "WARNING Calculated flow delay for X at Y for Z". " "Should I worry?" msgstr "" #: template/faq.html.j2:598 msgid "" "A: Right now, this is expected and a known cause for high latency in GNUnet. " "We have started a major rewrite to address this and other problems, but " "until the Transport Next Generation (TNG) is ready, these warnings are " "expected." msgstr "" #: template/faq.html.j2:607 msgid "Error opening `/dev/net/tun': No such file or directory?" msgstr "" #: template/faq.html.j2:609 msgid "" "A: If you get this error message, the solution is simple. Issue the " "following commands (as root) to create the required device file" msgstr "" #: template/faq.html.j2:621 msgid "" "'iptables: No chain/target/match by that name.' (when running gnunet-service-" "dns)?" msgstr "" #: template/faq.html.j2:623 msgid "" "A: For GNUnet DNS, your iptables needs to have "owner" match " "support. This is accomplished by having the correct kernel options. Check if " "your kernel has CONFIG_NETFILTER_XT_MATCH_OWNER set to either 'y' or " "'m' (and the module is loaded)." msgstr "" #: template/faq.html.j2:635 msgid "'Timeout was reached' when running PT on Fedora (and possibly others)?" msgstr "" #: template/faq.html.j2:637 msgid "" "A: If you get an error stating that the VPN timeout was reached, check if " "your firewall is enabled and blocking the connections." msgstr "" #: template/faq.html.j2:645 msgid "" "I'm getting an 'error while loading shared libraries: libgnunetXXX.so.X'" msgstr "" #: template/faq.html.j2:647 msgid "" "A: This error usually occurs when your linker fails to locate one of " "GNUnet's libraries. This can have two causes. First, it is theoretically " "possible that the library is not installed on your system; however, if you " "compiled GNUnet the normal way and/or used a binary package, that is highly " "unlikely. The more common cause is that you installed GNUnet to a directory " "that your linker does not search. There are several ways to fix this that " "are described below. If you are 'root' and you installed to a system folder " "(such as /usr/local), you want to add the libraries to the system-wide " "search path. This is done by adding a line \"/usr/local/lib/\" to /etc/ld.so." "conf and running \"ldconfig\". If you installed GNUnet to /opt or any other " "similar path, you obviously have to change \"/usr/local\" accordingly. If " "you do not have 'root' rights or if you installed GNUnet to say \"/home/" "$USER/\", then you can explicitly tell your linker to search a particular " "directory for libraries using the \"LD_LIBRARY_PATH\" environment variable. " "For example, if you configured GNUnet using a prefix of \"$HOME/gnunet/\" " "you want to run:" msgstr "" #: template/faq.html.j2:673 msgid "" "to ensure GNUnet's binaries and libraries are found. In order to avoid " "having to do so each time, you can add the above lines (without the \"$\") " "to your .bashrc or .profile file. You will have to logout and login again to " "have this new profile be applied to all shells (including your desktop " "environment)." msgstr "" #: template/faq.html.j2:680 msgid "What error messages can be ignored?" msgstr "" #: template/faq.html.j2:682 msgid "" "A: Error messages flagged as \"DEBUG\" should be disabled in binaries built " "for end-users and can always be ignored. Error messages flagged as \"INFO\" " "always refer to harmless events that require no action. For example, GNUnet " "may use an INFO message to indicate that it is currently performing an " "expensive operation that will take some time. GNUnet will also use INFO " "messages to display information about important configuration values." msgstr "" #: template/faq.html.j2:698 msgid "How does GNUnet compare to other file-sharing applications?" msgstr "" #: template/faq.html.j2:700 msgid "" "A: As opposed to Napster, Gnutella, Kazaa, FastTrack, eDonkey and most other " "P2P networks, GNUnet was designed with security in mind as the highest " "priority. We intend on producing a network with comprehensive security " "features. Many other P2P networks are open to a wide variety of attacks, and " "users have little privacy. GNUnet is also Free Software and thus the source " "code is available, so you do not have to worry about being spied upon by the " "software. The following table summarises the main differences between GNUnet " "and other systems. The information is accurate to the best of our knowledge. " "The comparison is difficult since there are sometimes differences between " "various implementations of (almost) the same protocol. In general, we pick a " "free implementation as the reference implementation since it is possible to " "inspect the free code. Also, all of these systems are changing over time and " "thus the data below may not be up-to-date. If you find any flaws, please let " "us know. Finally, the table is not saying terribly much (it is hard to " "compare these systems this briefly), so if you want the real differences, " "read the research papers (and probably the code)." msgstr "" #: template/faq.html.j2:814 msgid "" "Another important point of reference are the various anonymous peer-to-peer " "networks. Here, there are differences in terms of application domain and how " "specifically anonymity is achieved. Anonymous routing is a hard research " "topic, so for a superficial comparisson like this one we focus on the " "latency. Another important factor is the programming language. Type-safe " "languages may offer certain security benefits; however, this may come at the " "cost of significant increases in resource consumption which in turn may " "reduce anonymity." msgstr "" #: template/faq.html.j2:827 msgid "Are there any known attacks (on GNUnet's file-sharing application)?" msgstr "" #: template/faq.html.j2:829 msgid "" "A: Generally, there is the possibility of a known plaintext attack on " "keywords, but since the user has control over the keywords that are " "associated with the content he inserts, the user can take advantage of the " "same techniques used to generate reasonable passwords to defend against such " "an attack. In any event, we are not trying to hide content; thus, unless the " "user is trying to insert information into the network that can only be " "shared with a small group of people, there is no real reason to try to " "obfuscate the content by choosing a difficult keyword anyway." msgstr "" #: template/faq.html.j2:843 msgid "What do you mean by anonymity?" msgstr "" #: template/faq.html.j2:845 msgid "" "A: Anonymity is the lack of distinction of an individual from a (large) " "group. A central goal for anonymous file-sharing in GNUnet is to make all " "users (peers) form a group and to make communications in that group " "anonymous, that is, nobody (but the initiator) should be able to tell which " "of the peers in the group originated the message. In other words, it should " "be difficult to impossible for an adversary to distinguish between the " "originating peer and all other peers." msgstr "" #: template/faq.html.j2:857 msgid "What does my system do when participating in GNUnet file sharing?" msgstr "" #: template/faq.html.j2:859 msgid "" "A: In GNUnet you set up a node (a peer). It is identified by an ID (hash of " "its public key) and has a number of addresses it is reachable by (may have " "no addresses, for instance when it's behind a NAT). You specify bandwidth " "limits (how much traffic GNUnet is allowed to consume) and datastore quote " "(how large your on-disk block storage is) . Your node will then proceed to " "connect to other nodes, becoming part of the network." msgstr "" #: template/faq.html.j2:874 msgid "How can I help translate this webpage into other languages?" msgstr "" #: template/faq.html.j2:876 msgid "" "A: First, you need to register an account with our weblate system. Please " "send an e-mail with the desired target language to translators@gnunet.org or " "ask for help on the #gnunet chat on irc.freenode.net. Typically someone with " "sufficient permissions will then grant you access. Naturally, any abuse will " "result in the loss of permissions." msgstr "" #: template/faq.html.j2:888 msgid "I have some great idea for a new feature, what should I do?" msgstr "" #: template/faq.html.j2:890 msgid "" "A: Sadly, we have many more feature requests than we can possibly implement. " "The best way to actually get a new feature implemented is to do it yourself " "--- and to then send us a patch." msgstr "" #: template/glossary.html.j2:12 msgid "Ego" msgstr "" #: template/glossary.html.j2:14 msgid "" "We use the term \"Ego\" to refer to the fact that users in GNUnet can have " "multiple unlinkable identities, in the sense of alter egos. The ability to " "have more than one identity is crucial, as we may want to keep our egos for " "business separate from those we use for political activities or romance.
" "Egos in GNUnet are technically equivalent to identities (and the code does " "not distinguish between them). We simply sometimes use the term \"ego\" to " "stress that you can have more than one." msgstr "" #: template/glossary.html.j2:27 msgid "Identity" msgstr "" #: template/glossary.html.j2:29 msgid "" "In GNUnet users are identified via a public key, and that public key is then " "often referred to as the \"Identity\" of the user. However, the concept is " "not as draconian as it often is in real life where many are forced to have " "one name, one passport and one unique identification number.
As long as " "identities in GNUnet are simply public keys, users are free to create any " "number of identities, and we call those egos to emphasize the difference. " "Even though users can create such egos freely, it is possible to have an ego " "certified by some certification authority, resulting in something that more " "closely resembles the traditional concept of an identity.
For example, a " "university may certify the identities of its students such that they can " "prove that they are studying. Students may keep their (certified) student " "identity separate from other egos that they use for other activities in life." msgstr "" #: template/glossary.html.j2:50 msgid "Pseudonym" msgstr "" #: template/glossary.html.j2:52 msgid "" "A pseudonym is an ego that is specifically intended to not be linked to " "one's real name. GNUnet users can create many egos, and thus also many " "pseudonyms.
Repeated uses of the same pseudonym are linkable by " "definition, as they involve the same public key. Anonymity requires the use " "of either the special \"anonymous\" pseudonym (for GNUnet, this is the " "neutral element on the elliptic curve) or a throw-away pseudonym that is " "only used once." msgstr "" #: template/glossary.html.j2:71 msgid "Namespaces" msgstr "" #: template/glossary.html.j2:73 msgid "" "The GNU Name System allows every ego (or identity) to securely and privately " "associate any number of label-value pairs with an ego. The values are called " "record sets following the terminology of the Domain Name System (DNS). The " "mapping of labels to record sets for a given ego is called a namespace.
" "If records are made public and thus published, it is possible for other " "users to lookup the record given the ego's public key and the label. Here, " "not only the label can thus act as a passphrase but also the public key -- " "which despite its name may not be public knowledge and is never disclosed by " "the GNS protocol itself." msgstr "" #: template/glossary.html.j2:89 msgid "Peer" msgstr "" #: template/glossary.html.j2:91 msgid "" "A \"peer\" is an instance of GNUnet with its own per-instance public key and " "network addresses. Technically, it is possible to run multiple peers on the " "same host, but this only makes sense for testing.
By design GNUnet " "supports multiple users to share the same peer, just as UNIX is a multi-user " "system. A \"peer\" typically consists of a set of foundational GNUnet " "services running as the \"gnunet\" user and allowing all users in the " "\"gnunet\" group to utilize the API. On multi-user systems, additional " "\"personalized\" services may be required per user.
While peers are " "also identified by public keys, these public keys are completely unrelated " "to egos or identities. Namespaces cannot be associated with a peer, only " "with egos." msgstr "" #: template/gns.html.j2:13 template/gnurl.html.j2:60 msgid "Motivation" msgstr "" #: template/gns.html.j2:15 msgid "" "The Domain Name System today enables traffic amplification attacks, " "censorship (i.e. China), mass surveillance (MORECOWBELL) and offensive cyber " "war (QUANTUMDNS).
Unfortunately, band aid solutions such as DoT, DoH, " "DNSSEC, DPRIVE and the like will not fix this. This is why we built the GNU " "Name System (GNS), a secure, decentralized name system built on top of " "GNUnet." msgstr "" #: template/gns.html.j2:28 msgid "Overview" msgstr "" #: template/gns.html.j2:39 msgid "" "The GNU Name System (GNS) is secure and decentralized naming system. It " "allows its users to register names as top-level domains (TLDs) and resolve " "other namespaces within their TLDs.
GNS is designed to provide: