# Translations template for PROJECT.
# Copyright (C) 2021 ORGANIZATION
# This file is distributed under the same license as the PROJECT project.
# FIRST AUTHOR 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. GNUnet の参加者で Git を使われている場合、著作権譲渡書に合意し、GNUnet および GNU Taler プロジェクトの「GNUnet e.V. --- ライセンスと共同開発についての Taler システム SA 合意"
"a>」に順守することが必要となります。 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). 本合意により、今後も自由ソフトウェア ライセンスのもとでコードの公開が可能"
"となり、開発者は GNUnet と GNU Taler の両方の許諾を得なくても双方でプログラム"
"のコードを使うことができます。(例えば、自由ソフトウェアに好意的でないアプリ"
"ストアを通じた配布も可能となります。) 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. Git アクセス権のない方のご協力については、著作権譲渡書は不要です。偽名でご"
"協力いただくことも可能ですが、著作権譲渡書も同じ偽名で署名してください。ス"
"キャンしたコピーも受け付けていますが、郵送を推奨しています。
"
msgstr ""
"詳細はハンドブック"
"a>中の、特に GNUnet の基本概念を説明する「主要概念」の章を参照してください。"
""
#: 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 ""
"GNUnet の詳細については、ハンドブック以外にも多くのリソースがあり、一例としては、多角的な視"
"点での論文を集めた参考文献、各種動画、簡潔な用語集などが挙げられます。"
#: 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 ""
"会話に参加する、GNUnet "
"をインストールする、実際に利用する、貢献して参加するなど、さまざまな方法で活用いただけます。"
#: 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 ""
"NLnet の次世代インターネット資金ラインから支援を受け、IETF 標準化プロセスに適"
"合させる形で GNU ネームシステムプロトコルを文書化し、実装しています。"
#: 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 ""
"このプロジェクトは、欧州連合の「Horizon 2020」研究・イノベーションプログラム"
"から NGI_TRUST 補助金契約 No. 825618 に基づき資金を受け取っています。本プロ"
"ジェクトは、re:claimID および、試験段階にある GNU Taler 支払いシステムを統合"
"することで、ユーザーと商用サービスプロバイダーに向け、実用への可能性とプライ"
"バシー向上技術の利点を証明することを目指しています。プロジェクトは"
"「Decentralized Identities for Self-Sovereign End-uers(DISSENS:自己主権を持"
"つエンドユーザーのための脱中央型 ID)」と呼ばれます。"
#: 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 "GNUnet が提供するアプリケーション"
#: template/applications.html.j2:13 template/gns.html.j2:7
msgid "The GNU Name System"
msgstr "GNU ネームシステム"
#: 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 ""
"GNU ネームシステム(GNS)は、ドメインネームシステム"
"(DNS)が完全に分散されたもので、その代替です。GNU は階層構造に代わり有向グラ"
"フを使用します。命名規則は DNS に類似していますが、クエリと応答は、回答をする"
"ピアに関してもプライベートです。レコードの完全性とルックアップのプライバシー"
"はセキュアに暗号化されます。"
#: template/applications.html.j2:38
msgid "Self-sovereign, decentralized identity provider"
msgstr "自己主権型、脱中央型の IdP"
#: 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 ""
"re:claimID は分散型のアイデンティ"
"ティ プロバイダ(IdP)サービスであり、GNU ネームシステムの上位に組み込まれて"
"います。これによりユーザーは、標準化されたプロトコルを使い、ウェブサイトから"
"個人情報を安全に共有することができます(OpenID Connect)。"
#: 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 ""
"GNUnet のファイル共有は、検閲耐性と匿名性を備えた"
"ファイル共有を目指すアプリケーションです。発行者は、パフォーマンスと匿名性の"
"度合いを自在に選択することができます。"
#: 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 ""
"GNUnet カンバセーションは、ルーティングとトランスポートに GNUnet を採用するこ"
"とにより、完全分散型の安全な音声通話を提供するアプリケーションです。"
#: template/applications.html.j2:91
msgid "Applications utilizing GNUnet"
msgstr "GNUnet を利用するアプリケーション"
#: template/applications.html.j2:97
msgid "GNU Taler (Alpha)"
msgstr "GNU Taler(アルファ)"
#: 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 ""
"GNU Taler は、プライバシーを保護する新しい"
"電子決済システムです。決済はセキュアに暗号化され、数ミリ秒で完了、トランザク"
"ションも大変低コストです。"
#: template/applications.html.j2:118
msgid "secushare"
msgstr "secushare"
#: 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 ""
"secushare は、GNUnet 上に分散型ソー"
"シャルネットワーキング アプリケーションを作成しています。オーバーレイ マルチ"
"キャスト、拡張可能な PSYC プロトコル、通知機能がエンドツーエンドで暗号化さ"
"れ、承認済みの受信者にのみ配信されます。"
#: template/applications.html.j2:139
msgid "pretty Easy privacy"
msgstr "pretty Easy privacy"
#: 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 ""
"pretty Easy privacy(p≡p)は、"
"日和見鍵交換を使用して、実用性のあるエンドツーエンドで暗号化された電子メール"
"ソリューションを作成しています。p≡p は GNUnet によりメタデータを保護"
"し、新たな暗号化プロトコルで鍵を検証します。"
#: template/applications.html.j2:160
msgid "Cadet-GTK"
msgstr "Cadet-GTK"
#: 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 ""
"Cadet-GTK は、"
"高い利便性と豊富な機能を備えたグラフィカル アプリケーションで、特に CADET サ"
"ブシステムを使用してメッセージ機能を提供します。GTK と libhandy を利用して開"
"発されいます。"
#: template/applications.html.j2:180
msgid "groupchat"
msgstr "groupchat"
#: 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 ""
"groupchat は、主に "
"CADET サブシステムを使用してメッセージ機能を提供するターミナル ユーザーイン"
"ターフェースです。開発言語は Nim で、将来的には Cadet-GTK と groupchat と互換"
"性を持つ予定です。"
#: template/architecture.html.j2:6
msgid "GNUnet System Architecture"
msgstr "GNUnet システム アーキテクチャ"
#: 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 ""
"GNUnet の基盤は、分散ハッシュ テーブル(R5N)、SCTP に類似したエンド ツー エ"
"ンドの暗号化メッセージング層(CADET)、公開鍵基盤(GNS)、プラグ可能なトラン"
"スポート システム(TRANSPORT)です。
これらのサブシステムは、アドレスや自"
"己組織する分散型ルーティング アルゴリズムに公開鍵を使用し、従来の TCP/IP ス"
"タックに代替するものです。"
#: 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 ""
"GNUnet はマルチプロセス アーキテクチャを使用して実装されます。各サブシステム"
"は別々のプロセスとして実行され、問題の切り分けや厳格な権限付与がサブシステム"
"毎に可能です。そのため、実装は GNU パッ"
"ケージであり、その後も自由ソフトウェアであり続けます。"
#: 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 "libgnunetutil"
#: template/architecture.html.j2:73
msgid "APIs"
msgstr "API"
#: 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 ""
"GNUnet の公開メーリング リストのアーカイブはhttps://lists.gnu.org/mailman/listinfo/"
"gnunet-developersにホストされています。このリストへのメッセージはgnunet-developers@gnu.orgから送信で"
"きます。"
#: template/contact.html.j2:23
msgid "The IRC channel"
msgstr "IRC チャネル"
#: template/contact.html.j2:25
msgid ""
"#gnunet is reachable via irc."
"freenode.net. There is also an archive available."
msgstr ""
"#gnuneはirc.freenode.netからア"
"クセスできます。また、アーカイブはこちらです。"
#: 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 ""
"GNUnet 開発者へのご連絡は、通常 PSEUDONYM@gnunet.org または "
"LASTNAME@gnunet.org から可能です。ほとんどのメンバーは GnuPG 暗号化"
"メールの受信に対応しています。緊急の場合や機密性の高いセキュリティ関連の問題"
"については、GNU 保守を担当する schanzen および grothoff "
"までご連絡ください。"
#: 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 ""
"GNUnet 内の各種プロジェクトの公開機能リクエストやバグは、バグ トラッカーで管理しています。バグの報告や機能リク"
"エストは、bug-"
"gnunet のメーリングリストからも送信できます。メーリングリストへの登録は必"
"要ありません。"
#: template/copyright.html.j2:11
msgid ""
"
"
msgstr ""
"「Satzung」およびメンバーのリストはhttps://git.gnunet.org/gnunet-ev.git/tree/satzung."
"tex から確認できます。現在の委員会メンバーは次の通りです。 "
"
"
#: 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.
"
msgstr ""
"どなたでも寄付を通じてご支援いただけます。金銭的な貢献に関し、欧州にお住まい"
"の場合 SEPA 経由で寄付いただくことができます。将来的には他の主要通貨でも受け"
"付けられるよう取り組んでいきたいと考えています。また、Bitcoin による寄付も可"
"能で、ルーティング詳細は下に記載しています。ただし、寄付金について領収書は発"
"行することができませんのでご了承ください。大口の寄付につきましては、関税処理"
"が必要な場合があるため、事前にご連絡をいただけますようお願いします。"
"
"
#: 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:695
msgid "Error messages"
msgstr "エラーメッセージ"
#: template/faq.html.j2:16 template/faq.html.j2:797
msgid "File-sharing"
msgstr "ファイル共有"
#: template/faq.html.j2:17 template/faq.html.j2:973
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 ""
"回答:他の方法でも情報を提供しています。例えば、他のドキュメントを参照する、"
"help-gnunet@gnu.org のメーリングリストまたは irc.freenode.net の #gnunet IRC "
"から質問することもできます。"
#: 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 ""
"回答:一般的な回答としては、準備ができ次第です。より理想的な回答としては「テ"
"スト、デバッグ、コード、ドキュメントなどに貢献いただければ早めに」リリースと"
"なるでしょう。全てのリリースは、planet "
"GNU の info-gnunet@gnu.org のメーリングリストで公表しています。こち"
"らのサイトからメーリングリストまたは RSS フィードに登録すると自動で通知が届き"
"ます。"
#: 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 ""
"回答:GNUnet は無料ソフトウェアで、GNU Affero Public License (AGPL) のもとで利用可能で"
"す。"
#: 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 ""
"回答:現時点で既知のバグは Mantis "
"system に記載しています。バグの中には開発者または開発者メーリングリストに"
"直接報告されたものもありますが、Mantis データベースへのバグ登録に時間を取られ"
"るため、この方法は推奨されません。バグは追跡システムに直接報告をお願いしま"
"す。機密扱いが必要と思われるバグに関しては、閲覧ステータスを例外的にプライ"
"ベートに設定することができます。"
#: 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 ""
"回答:gnunet-gtk を別途ダウンロードいただけます。このパッケージには、設定用の"
"グラフィカル ツールなど、各種 GTK+ ベースのグラフィカル インターフェースが含"
"まれます。"
#: template/faq.html.j2:83
msgid "Why does gnunet-service-nse create a high CPU load?"
msgstr "なぜ gnunet-service-nse は CPU 負荷が高いのですか?"
#: 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 ""
"回答:gnunet-service-nse プロセスは最初、ネットワークにピアの正当性を示すため"
"に使用されるいわゆる"プルーフオブワーク"を演算します(または、攻撃"
"者にネットワーク規模評価上、シビル攻撃が高額となるよう仕掛ける方法)。この演"
"算には、CPU 速度にもよりますが、数日を要します。CPU 負荷が問題となる場合は、"
"構成ファイルの" nse" セクションにある "WORKDELAY" 値を高"
"く設定することができます。デフォルトは "5 ミリ秒"です。"
#: template/faq.html.j2:99
msgid "How does GNUnet compare to Tor?"
msgstr "GNUnet と Tor は何が違うのですか?"
#: 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 ""
"回答:Tor は、Tor Browser Bundle により、特にウェブにおける匿名通信と TCP 接続の検閲保護に焦点を当てています。GNUnet "
"は、安全で分散したネットワーク化を趣旨としますが、焦点と呼ぶには大変広義であるため、実質的に一つの焦点はないと言えます。"
#: template/faq.html.j2:111
msgid "How does GNUnet compare to I2P?"
msgstr "GNUnet は I2P とどのように比較されますか?"
#: 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 ""
"回答:GNUnet と I2P "
"はどちらも、安全性と分散化を高め、より優れたインターネットの構築を目指しています。しかし、技術面においてほぼ共通点はありません。
I2P "
"は Java "
"を使用しており、各種(匿名化された)アプリケーションの基盤として、オニオン(またはガーリック)ルーティングを使った(非対称)トンネルを持ちます。I2P "
"はウェブのフロントエンドで広く使われています。"
#: template/faq.html.j2:124
msgid "Is GNUnet ready for use on production systems?"
msgstr "GNUnet は本番システムで利用できますか?"
#: 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 ""
"回答:GNUnet はまだ開発途上であるため、大部分が開発者以外の方による使用には適"
"していません。利用価値は、使いたい機能にもよりますが、現時点では転送システム"
"が洗練されておらず、常に何らかの問題に直面すると考えられます。この部分につい"
"ては現在書き換えを進めています。(プロジェクト"Transport Next "
"Generation [TNG]")"
#: template/faq.html.j2:136
msgid "Is GNUnet build using distributed ledger technologies?"
msgstr "GNUnet は分散型台帳技術を使用して構築されていますか?"
#: 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 ""
"回答:いいえ。GNUnet は、安全で分散型のプライバシー保護を実現したアプリケー"
"ションを構築することができる、新しいネットワーク プロトコル スタックです。"
"GNUnet で台帳を構築することもできますが、現時点でその予定はありません。"
#: template/faq.html.j2:151
msgid "What can I do with GNUnet?"
msgstr "GNUnet では何ができますか?"
#: 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 ""
"回答:GNUnet はピアツーピアのフレームワークであり、つまり、できることは一つに限りません。そのため、既存機能の実装とドキュメンテーションは、他のもの"
"よりも進んでいることがあります。"
#: 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 ""
"ユーザーの観点からは、GNUnet は匿名および非匿名でのファイル共有、完全に分散化され検閲保護された DNS の代替手段、IPv4-IPv6 "
"プロトコル変換およびトンネリングのメカニズム(DNS-ALG を使用した NAT-PT)を提供します。"
#: template/faq.html.j2:171
msgid "Is it possible to surf the WWW anonymously with GNUnet?"
msgstr "GNUnet では匿名の WWW サーフィンは可能ですか?"
#: 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 "回答:現時点で匿名ブラウジングに GNUnet を使用することはできません。匿名サーフィンには Tor をお勧めします。"
#: template/faq.html.j2:181
msgid "Is it possible to access GNUnet via a browser as an anonymous WWW?"
msgstr "匿名の WWW としてブラウザ経由で GNUnet にアクセスすることは可能ですか?"
#: 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 ""
"回答:現在、ブラウザでのアクセスを可能にする GNUnet 用のプロキシ(Freenet の fproxy "
"など)はありません。こうしたプロキシの構築は可能で、必要となるのは、ブラウザとプロキシ間で利用されるプロトコルと、ファイル共通のための GNUnet "
"コード概要のみです。"
#: 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 ""
"回答:実際、異なる機能に向けたグラフィカル ユーザーインターフェースが数種類あります。例えば、gnunet-setup は GNUnet 構成"
"、gnunet-fs-gtk はファイル共有のためのものです。重要性は下がりますが、gnunet-XXX-gtk GUI はその他にもあります。GUI "
"を取得するためには、gnunet-gtk パッケージが必要で、別途ダウンロードを要します。gnunet-gtk はその他ほぼ全ての GUI "
"を一つのウィンドウに統合したメタ GUI です。例外は gnunet-setup "
"で、現時点では単独で実行が必要となります(設定でピアを停止する必要があるため)。"
#: template/faq.html.j2:210
msgid "On top of which operating systems does GNUnet run?"
msgstr "GNUnet はどのオペレーティングシステム上で実行されますか?"
#: 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 ""
"回答:GNUnet の開発とテストは、主に Debian GNU / Linux で実施しています。さらに、Fedora、Ubuntu、 Arch、 "
"FreeBSD、 macOS でも定期的に構築やテストを実施しています。そのほか多くの GNU/Linux でも正常な稼働が認められたという報告があり、"
"これまで NetBSD、OpenBSD、Solaris 上での稼働が報告されています。ただ、こうした報告全てが最近のものとは限らず、これらシステム上で "
"GNUnet を稼働できない場合はお知らせください。"
#: template/faq.html.j2:228
msgid "Who runs the GNS root zone?"
msgstr "GNS ルートゾーンを実行しているのは誰ですか?"
#: 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 ""
"回答:簡潔な回答は「みなさん」です。詳しくいうと、GNUnet は上位ドメインのデフォルト設定でリリースされ、このデフォルト設定のガバナンスはまだ構築され"
"ていません。いずれにしても、ユーザー側でこの設定を好きに変更することができます。一般のユーザーは、サービスを自らホストしない限り、その GNS "
"ゾーンを編集する必要はないとみなしています。"
#: template/faq.html.j2:241
msgid "Where is the per-user GNS database kept?"
msgstr "ユーザーごとの GNS データベースはどこに保管されていますか?"
#: 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 ""
"回答:簡潔には、データベースはユーザーの GNUnet ピアに保管されています。現在、ユーザーが複数の GNUnet "
"ピアを走らせた場合、データベースは各ピアに保管されます(ただし、便宜的なレプリケーションのためのコードはありません)。同様に、複数の GNUnet "
"ピアは、データベースの一つのインスタンスを共有することができ、 "gnunet-service-namestore" は TCP "
"経由で遠隔からアクセスできます。実際のデータは Postgres データベースに保管され、各種レプリケーションのオプションが適用されます。つまり、GNS "
"データベースの保管方法(または安全性の確保)については、ユーザーに多くの選択肢が与えられることになります。"
#: template/faq.html.j2:258
msgid "What is the expected average size of a GNS namestore database?"
msgstr "GNS ネームストア データベースの平均サイズはどれくらいと予測されますか?"
#: 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 ""
"回答:かなり小さいと言えます。実施した調査で、ブラウザ履歴とアクセスしたドメイン数を確認したところ、GNS "
"データベースの規模は数万エントリーに留まり、モバイル端末でも対応できるほど小規模です。"
#: template/faq.html.j2:270
msgid "Is GNS resistant to the attacks on DNS used by the US?"
msgstr "GNS は、米国で使用されている DNS 攻撃に耐性がありますか?"
#: 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 ""
"回答:そのように考えます。理由として、個々のユーザーを除き、いかなる政府も名前のマッピングを変更するよう強制できる組織がないためです(その場合、変更は当該"
"のユーザーが権限を持つ名前にのみ適用されます)。そのため、全員が GNS を利用した場合に唯一考えられる政府による攻撃は、"
"サーバー運用者に対して該当サーバーが他の地点を指すよう GNS レコードの変更を強制することです。しかし、あるゾーンのプライベートキーの所有者が従わないな"
"どの場合、該当するゾーンは変更できず、このゾーンに委任する他のゾーンは全て正常通りに動作します。"
#: template/faq.html.j2:286
msgid "How does GNS compare to other name systems"
msgstr "GNS は他のネームシステムとどのように比較されますか?"
#: template/faq.html.j2:288
msgid ""
"A: A scientific paper on this topic has been published and below is a table from the "
"publication. For detailed descriptions please refer to the paper."
msgstr ""
"回答:このトピックに関する科学論文が公開されており、以下は論文からの表です。詳細については、論文をご覧ください。"
#: template/faq.html.j2:392
msgid "What is the difference between GNS and CoDoNS?"
msgstr "GNS と CoDoNS の違いは何ですか?"
#: template/faq.html.j2:394
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 ""
"回答:CoDoNS は DHT を使用して DNS データベースを分散しますが、DNS の権限構造を保持しています。CoDoNS は IANA/"
"ICANN で管理され、ドメイン名の所有者を決定するレジストラが存在します。
一方で GNS は、データベースを分散化するとともに命名につい"
"ても中央管理はせずに分散化させています。つまり、各ユーザーが自らのルートゾーンを管理するため、使用するドメイン名を完全に制御することになります。GNU "
"には CoDoNS では必要のない追加機能も豊富にあります(名前を短くし移行を実施するため)。"
#: template/faq.html.j2:410
msgid "What is the difference between GNS and SocialDNS?"
msgstr "GNS と SocialDNS の違いは何ですか?"
#: template/faq.html.j2:412
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 ""
"回答:GNS と同様、SocialDNS では各ユーザーが DNS マッピングを作成できます。しかし、SocialDNS "
"ではマッピングがソーシャルネットワークで共有されてランキング対象となるため、関連が複雑化するにつれ、名前が予期せず変更されることがあり得ます。"
"
一方 GNS "
"では、名前の共有は主に移譲によって実施されるため、マッピングは名前の責任者(権限のあるユーザー)が手動で記録を変更した場合にのみ変更されます。"
#: template/faq.html.j2:426
msgid "What is the difference between GNS and ODDNS?"
msgstr "GNS と ODDNS の違いは何ですか?"
#: template/faq.html.j2:428
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 ""
"回答:ODDNS は主に DNS ルート ゾーンと TLD レジストリ(「.com」や「."
"org」など)をバイパスするように設計されています。これらを使わず、各ユーザーは(セカンドレベル)ドメインのデータベース(「gnu.org」など)と、"
"該当するネームサーバーの IP アドレスを保持することが求められます。ターゲットのネームサーバーが IP を変更すると名前解決は失敗します。"
#: template/faq.html.j2:439
msgid "What is the difference between GNS and Handshake?"
msgstr "GNS とハンドシェイクの違いは何ですか??"
#: template/faq.html.j2:441
msgid ""
"A: Handshake is a blockchain-based method for root zone governance. Hence, "
"it does not address the name resolution process itself but delegates "
"resolution into DNS after the initial TLD resolution. Not taking "
"sustainablility considerations into account, handshake could be used as an "
"additional supporting GNS root zone governance model but we currently do not "
"have such plans in mind."
msgstr ""
"回答:ハンドシェイクは、ブロックチェーンベースのルートゾーンガバナンスのための手法です。そのため、名前解決プロセス自体には対処せず、最初の TLD "
"の名前解決後、DNS に名前解決を委任します。ハンドシェイクでは持続性が考慮されていないため、GNS ルートゾーン "
"ガバナンスモデルの追加サポートとして利用できますが、現時点でその予定はありません。"
#: template/faq.html.j2:453
msgid "What is the difference between GNS and TrickleDNS?"
msgstr "GNS と TrickleDNS の違いは何ですか?"
#: template/faq.html.j2:455
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 ""
"回答:TrickleDNS は、参加ドメインの DNS リゾルバー間で("クリティカルな")DNS "
"レコードをプッシュし、"可用性の向上、クエリ解決時間の短縮、更新のプロパゲーション高速化"を実現します。そのため "
"TrickleDNS は、例えば DNS ルートサーバーへの DDoS 攻撃など、DNS "
"におけるレコードプロパゲーションの可用性(およびパフォーマンス)に対する攻撃への対処に主軸をおきます。TrickleDNS "
"は確実に信頼できるレコードを分配する方法を考慮し、権限はこれまで通り DNS 階層に起因しています。"
#: template/faq.html.j2:468
msgid ""
"Does GNS require real-world introduction (secure PKEY exchange) in the style "
"of the PGP web of trust?"
msgstr "GNS は PGP Web の信用モデル(web of trust)による実導入(セキュア PKEY 交換)を必要としますか?"
#: template/faq.html.j2:470
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 ""
"回答:セキュリティの観点から最初の時点で二者間に信頼パスが必要とされていますが、これが必要とされないアプリケーションでは、より脆弱なメカニズムも利用できま"
"す。例えば、私たちは FCFS 権限を実装しており、どのユーザーでも任意の名前を登録できるようになっています。この権限の鍵は全ての GNUnet "
"インストールに含まれるため、FCFS で登録された名前はいずれも事実上グローバルであり、周知のものとなります。ただし、これらの名前のセキュリティは完全に "
"FCFS 権限の信頼性に依ることになります。権限は ".pin" TLD で照会できます。"
#: template/faq.html.j2:485
msgid ""
"How can a legitimate domain owner tell other people to not use his name in "
"GNS?"
msgstr "正当なドメイン所有者が他者に GNS でその名前を使用しないよう伝えるにはどうすればよいですか?"
#: template/faq.html.j2:487
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 ""
"回答:GNS では名前に所有者はいないため、"正当な"ドメイン所有者は存在しません。NICK レコードには、どのユーザーがどの名前(好"
"きな名前または"偽名")を使っても構いません。同様に、他のユーザーもこれを無視し、このユーザーに対し好きな名前を使うことができます(ま"
"たは名前を付けないことも可)。"
#: template/faq.html.j2:498
msgid ""
"Did you consider the privacy implications of making your personal GNS zone "
"visible?"
msgstr "個人の GNS ゾーン表示についてプライバシーへの影響を考慮しましたか?"
#: template/faq.html.j2:500
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 ""
"回答:GNS "
"の各レコードには"プライベート"フラグがあります。レコードは、このフラグが設定されていない場合のみ他のユーザーと共有されます(DHT "
"またはゾーン転送により)。そのため、ゾーンのどの情報を開示するかについては、ユーザーが全て管理することができます。"
#: template/faq.html.j2:510
msgid "Are \"Legacy Host\" (LEHO) records not going to be obsolete with IPv6?"
msgstr "「レガシーホスト」(LEHO)レコードは IPv6 で廃止されるのではありませんか?"
#: template/faq.html.j2:512
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 ""
"回答:この質問は次のことを仮定しています。(a)仮想ホスティングの唯一の必要性は IPv4 アドレスが不足しているため。(b)LEHO "
"は仮想ホスティングの文脈でのみ有用。しかし、LEHO は X.509 "
"証明書の検証にも有用です(証明書が検証されるべきレガシーのホスト名を指定するため)。また、IPv6 が完全に実装され、IP "
"アドレスが"無限に"活用できたとしても、仮想ホスティングが無くなるとは言い切れません。最後に、IPv6 "
"が一般的に利用できるようになるのを待つよりも、GNS は現行のネットワークで運用できるべきです。"
#: template/faq.html.j2:526
msgid ""
"Why does GNS not use a trust metric or consensus to determine globally "
"unique names?"
msgstr "GNS がトラストメトリックまたはコンセンサスを使用してグローバルに一意の名前を決定しないのはなぜですか?"
#: template/faq.html.j2:528
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:539
msgid "How do you handle compromised zone keys in GNS?"
msgstr "GNS では、侵害されたゾーンキーをどのように処理しますか?"
#: template/faq.html.j2:541
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:553
msgid "Could the signing algorithm of GNS be upgraded in the future?"
msgstr "GNS の署名アルゴリズムは将来アップグレードできますか?"
#: template/faq.html.j2:555
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 ""
"回答:はい、できます。GNS を標準化する過程で、代替の委任レコードに対応できるようプロトコルをすでに変更しています。
そのため、"
"デプロイされた GNS 実装は、新しい署名スキームに対応できるよう更新する必要があります。新しいスキームはその後、新しいレコードタイプを使い異なる暗号シス"
"テムの利用を示すことで、既存スキームと並行して実行することができます。"
#: template/faq.html.j2:569
msgid ""
"How can a GNS zone maintain several name servers, e.g. for load balancing?"
msgstr "GNS ゾーンは、例えば負荷分散などで、どのように複数のネーム サーバーを保守していますか?"
#: template/faq.html.j2:571
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 ""
"回答:GNS レコードは R5N DHT に保存(および複製)されるため、そうしたことは必要ないと考えています。そのため、通常クライアントがルックアップを"
"実行するたびに、権威サーバーは連絡を受けません。権威サーバーが(一時的に)オフラインになった場合であっても、DHT はレコードを一定期間キャッシュします。"
"しかし、一つのゾーンに複数のサーバーがどうしても必要な場合、ゾーンの所有者は複数のピアを走らせることができます(ゾーンの鍵とデータベースを共有可能)。"
#: template/faq.html.j2:584
msgid ""
"Why do you believe it is worth giving up unique names for censorship "
"resistance?"
msgstr "検閲への対処のため一意の名前を放棄する価値はありますか?"
#: template/faq.html.j2:586
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 ""
"回答:GNU ネームシステムは、検閲から保護された DNS "
"の代替手段を提供します。どのセキュリティメカニズムにも言えることですが、これには代償もあります(名前がグローバルに一意ではない点)。他の例として、"
"HTTPS 接続は HTTP 接続に比べてより多くの帯域を使用し、レイテンシも大きくなります。使っているアプリケーションによっては、HTTPS のコストは"
"見合わないこともあります。しかし、検閲の対象となっていいる(またはこれを危惧する)ユーザーにとって、グローバルに一意の名前を放棄するという代償は払うに値す"
"るものであると言えます。結局、"グローバルに"一意の名前も、名前解決できなければ意味がありません。"
#: template/faq.html.j2:600
msgid "Why do you say that DNS is 'centralized' and 'distributed'?"
msgstr "DNS が「集中型」および「分散型」であると言うのはどういう意味ですか?"
#: template/faq.html.j2:602
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 ""
"回答:DNS が「集中型」であるのは、中央コンポーネント/中央障害点があり、ルートゾーンを IANA / ICANN "
"が管理しているためです。こうした集中化により、脆弱性が生まれます。例えば米国政府は、21 世紀が明けて戦争を開始した際にアフガニスタンとイラクの国別 "
"TLD の再割り当てを実施しています。"
#: template/faq.html.j2:613
msgid "How does GNS protect against layer-3 censorship?"
msgstr "GNS はレイヤー 3 の検閲にどのように対処しますか?"
#: template/faq.html.j2:615
msgid ""
"A: GNS does not directly help with layer-3 censorship, but it does help "
"indirectly in two ways:
"
msgstr ""
"回答:GNS は、レイヤー 3 の検閲には直接対応しませんが、次の 2 つの方法で間接的に対応します。
"
#: template/faq.html.j2:634
msgid "Does GNS work with search engines?"
msgstr "GNS では検索エンジンを使えますか?"
#: template/faq.html.j2:636
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 ""
"回答:GNS を使用して名前解決やあらゆる標準ユーザーを実行できるため、検索エンジンに大きな問題はありません。通常、標準ユーザーは、カスタムのソフトウェア"
"をインストールして名前解決すると考えられますが、現在この方法は検索エンジンでは使えません。ただし、DNS2GNS ゲートウェイにより検索エンジンが "
"DNS を使用して GNS 名を解決できるため、GNS リソースのインデックスは可能です。しかし、DNS2GNS "
"ゲートウェイの利用は暗号化による信頼の連鎖を崩すため、レガシーの検索エンジンは検閲耐性のある名前を取得できません。"
#: template/faq.html.j2:650
msgid "How does GNS compare to the Unmanaged Internet Architecture (UIA)?"
msgstr "GNS はアンマネージド インターネット アーキテクチャ(UIA)とどのように比較されますか?"
#: template/faq.html.j2:652
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 ""
"回答:UIA と GNS は、どちらも同じ基本命名モデルを共有しており、これは実際 Rivest の SDSI に由来しています。しかし、UIA "
"はレガシー アプリケーションとの統合は考慮せず、ユーザーの複数マシン間における汎用性のあるコネクティビティに注力しています。一方、GNS は DNS "
"との相互運用に加え、既存の Web インフラとの親和性を最大限に考慮して設計されています。UIA "
"はレガシーシステムを全く考慮していません(クリーンスレート)。"
#: template/faq.html.j2:665
msgid "Doesn't GNS increase the trusted-computing base compared to DNS(SEC)?"
msgstr ""
#: template/faq.html.j2:667
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:679
msgid ""
"How does GNS handle SRV/TLSA records where service and protocol are part of "
"the domain name?"
msgstr ""
#: template/faq.html.j2:681
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:697
msgid ""
"I receive many "WARNING Calculated flow delay for X at Y for Z". "
"Should I worry?"
msgstr ""
"「WARNING Calculated flow delay for X at Y for Z」という警告が多くでますが、"
"懸念すべきですか?"
#: template/faq.html.j2:699
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 ""
"回答:現時点でこれは想定内であり、GNUnet での高レイテンシの既知の原因です。こ"
"の件および他の問題に対処するため、主要な書き換えを開始していますが、"
"Transport Next Generation(TNG)が準備できるまでは発生が続くことが見込まれま"
"す。"
#: template/faq.html.j2:708
msgid "Error opening `/dev/net/tun': No such file or directory?"
msgstr ""
#: template/faq.html.j2:710
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:722
msgid ""
"'iptables: No chain/target/match by that name.' (when running gnunet-service-"
"dns)?"
msgstr ""
#: template/faq.html.j2:724
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:736
msgid "'Timeout was reached' when running PT on Fedora (and possibly others)?"
msgstr ""
#: template/faq.html.j2:738
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:746
msgid ""
"I'm getting an 'error while loading shared libraries: libgnunetXXX.so.X'"
msgstr ""
#: template/faq.html.j2:748
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:774
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:781
msgid "What error messages can be ignored?"
msgstr ""
#: template/faq.html.j2:783
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:799
msgid "How does GNUnet compare to other file-sharing applications?"
msgstr ""
#: template/faq.html.j2:801
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:915
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:928
msgid "Are there any known attacks (on GNUnet's file-sharing application)?"
msgstr ""
#: template/faq.html.j2:930
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:944
msgid "What do you mean by anonymity?"
msgstr ""
#: template/faq.html.j2:946
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:958
msgid "What does my system do when participating in GNUnet file sharing?"
msgstr ""
#: template/faq.html.j2:960
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:975
msgid "How can I help translate this webpage into other languages?"
msgstr ""
#: template/faq.html.j2:977
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:989
msgid "I have some great idea for a new feature, what should I do?"
msgstr ""
#: template/faq.html.j2:991
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: "
"
This does not mean there is no confidence in the work done with "
"gnurl, it means that tools which expect curl or libcurl will not make use of "
"a different named binary and library. If you know what you are doing, you "
"should be able to use gnurl as part of your tooling in place of curl. We do "
"not recommend to do so however, as the only usage it is tested for so "
"far is as part of Taler's and GNunet's build-system.
Since "
"no conflicts in filenames occur you are not expected to remove curl to make "
"use of gnurl and viceversa."
msgstr ""
#: template/gnurl.html.j2:188
msgid "You can get the gnurl git repository using:"
msgstr ""
#: template/gnurl.html.j2:201
msgid "The versions are checked in as (signed) git tags."
msgstr ""
#: template/gnurl.html.j2:211
msgid ""
"Releases are published on ftpmirror.gnu.org/gnu/gnunet. gnurl is available from within a "
"variety of distributions and package managers. Some Package Managers which "
"include gnurl are: GNU Guix"
"a> (available as \"gnurl\"), Gentoo "
"through the collaborative ebuild collection youbroketheinternet, Nix, and as www/gnurl in pkgsrc."
msgstr ""
#: template/gnurl.html.j2:228
msgid "Building gnurl"
msgstr ""
#: template/gnurl.html.j2:230
msgid ""
"We suggest to closely follow release announcements, as they might indicate "
"changes in how gnurl is to be build.
If your package manager provides a "
"binary build or build instructions to build gnurl from source automated and "
"integrated with your environment, we strongly suggest to use this binary "
"build.
There are two ways to build gnurl. The first one builds from the "
"most recent git tag, the second one uses the distributed tarball. "
"Distributors generally are supposed to build from the tarball, but we "
"describe both methods here. Both methods are written with a NetBSD 9 "
"userland in mind, substitute tools as necessary.
You should avoid"
"b> building gnurl from the tip of the default git branch, as only tags are "
"considered to be stable and approved builds."
msgstr ""
#: template/gnurl.html.j2:251
msgid "Building from the distributed tarball (prefered method)"
msgstr ""
#: template/gnurl.html.j2:253
msgid ""
"If you want to verify the signature, install an OpenPGP compatible tool such "
"as security/gnupgp2 (and set it up). Assuming you use pkgin:"
msgstr ""
#: template/gnurl.html.j2:267
msgid "Fetch the signature key from"
msgstr ""
#: template/gnurl.html.j2:271
msgid "or via commandline with gnupg2."
msgstr ""
#: template/gnurl.html.j2:276
msgid ""
"Fetch the release, the signature, the checksum file as well as its signature:"
msgstr ""
#: template/gnurl.html.j2:295
msgid ""
"verify the signatures, and verify the checksums against the checksums in "
"the .sum.txt file."
msgstr ""
#: template/gnurl.html.j2:301
msgid "unpack the tarball:"
msgstr ""
#: template/gnurl.html.j2:311
msgid "Change into the directory"
msgstr ""
#: template/gnurl.html.j2:321
msgid "Now you can either run"
msgstr ""
#: template/gnurl.html.j2:331
msgid "directly (and read configure-gnurl before you do so) or invoke"
msgstr ""
#: template/gnurl.html.j2:341
msgid ""
"and pass additional parameters such as a custom PREFIX location. Further "
"reference can be the"
msgstr ""
#: template/gnurl.html.j2:346
msgid "Now run"
msgstr ""
#: template/gnurl.html.j2:356
msgid "(this is optional)"
msgstr ""
#: template/gnurl.html.j2:365
msgid "and you are done."
msgstr ""
#: template/gnurl.html.j2:369
msgid "Building from a tagged git commit"
msgstr ""
#: template/gnurl.html.j2:371
msgid ""
"Follow the steps above, but instead of downloading the tarball, clone the "
"git tag you want to build from."
msgstr ""
#: template/gnurl.html.j2:382
msgid "Reporting Bugs"
msgstr ""
#: template/gnurl.html.j2:384
msgid ""
"You can report bugs on our bug tracker: bugs.gnunet.org. Alternatively you can use our bug mailinglist, but "
"we prefer to track bugs on the bugtracker."
msgstr ""
#: template/gnurl.html.j2:395
msgid "Maintainer and Cryptographic signatures"
msgstr ""
#: template/gnurl.html.j2:397
msgid ""
"gnurl/libgnurl is looking for a new maintainer. Releases after version "
"7.69.1 and up to version 7.72.0 were signed with the OpenPGP Key "
"0xD6B570842F7E7F8D (keys.openpgp.org), with the "
"key fingerprint 6115 012D EA30 26F6 2A98 A556 D6B5 7084 2F7E 7F8D."
msgstr ""
#: template/gsoc-2018-gnunet-webui.html.j2:7
msgid "GSoC 2018: GNUnet WebUI (GNUnet Web-based User Interface)"
msgstr ""
#: template/gsoc-2018-gnunet-webui.html.j2:11
msgid "Tue, 08/14/2018 - 07:55, Phil Buschmann"
msgstr ""
#: template/gsoc-2018-gnunet-webui.html.j2:18
msgid ""
"In the context of Google Summer of Code 2018, my mentor (Martin "
"Schanzenbach) and I have worked on creating and extending the REST API of "
"GNUnet. Currently, we mirrored the functionality of following commands:"
msgstr ""
#: template/gsoc-2018-gnunet-webui.html.j2:32
msgid ""
"Additionally, we developed a website with the Javascript framework Angular 6 "
"and the design framework iotaCSS to use the new REST API. The REST API of "
"GNUnet is now documented with Sphinx."
msgstr ""
#: template/gsoc-2018-gnunet-webui.html.j2:41
msgid ""
"... when you can use the command line tools? We need to keep in mind, that "
"everyone has the right to stay secure and private but not everyone feels "
"comfortable using a terminal. The further developed REST access to GNUnet "
"APIs in addition to the new web application allows new users to interact "
"with GNUnet over a well known tool: their browsers. This addition to the C "
"API and the command line tools may attract new users and developers."
msgstr ""
#: template/gsoc-2018-gnunet-webui.html.j2:54
msgid ""
"
The REST API is already merged "
"into the gnunet.git repository (GNUnet Main Git).
To use the new features, clone the repository "
"and follow the Installation"
"a> on gnunet.org. Then, start the rest service with \"gnunet-arm -i rest\". "
"
The web application is available under "
"the gnunet-webui.git repository (GNUnet WebUI Git).
You need to install the newest "
"version of 'node' and 'yarn'. Dependent on your system, you may need to "
"download newer versions and install them manually and not over your packet "
"manager. After the installation succeeded, you need to clone the repository. "
"Then, you need to run \"yarn install\" and \"yarn start\" for testing "
"purposes. To deploy the website (keep in mind, that this website "
"communicates with another localhost instance) use \"yarn build\" for "
"building the web application and use the output in the 'dist' directory. "
"li>
The documentation is available under the "
"gnunet-rest-api.git repository (GNUnet REST API Docmentation Git).
Clone the repository "
"and \"make html\". Then open the 'index.html' under 'build/html/'.
Additionally, the web application does not prevent wrong inputs but "
"responds with error messages. Adding GNUnet Records is currently only usable "
"for people, who know how a GNS Record looks like. This can be adapted to "
"each record type.
Last but not least, additional features, design "
"changes, etc..."
msgstr ""
#: template/gsoc-2018-gnunet-webui.html.j2:111
msgid "Thanks for reading."
msgstr ""
#: template/gsoc.html.j2:6
msgid "GNUnet's Google Summer of Code projects"
msgstr ""
#: template/gsoc.html.j2:12 template/gsoc.html.j2:29
msgid "Ideas 2021"
msgstr ""
#: template/gsoc.html.j2:13 template/gsoc.html.j2:215
msgid "Past projects"
msgstr ""
#: template/gsoc.html.j2:14 template/gsoc.html.j2:596
msgid "Finished projects"
msgstr ""
#: template/gsoc.html.j2:21
msgid ""
"As a GNU project, GNUnet has participated in the Google Summer of Code "
"(GSoC) for a number of years. This page lists all current, past, and "
"finished projects. If you want to participate and apply for any of the ideas "
"for 2020 below or any past project which is not yet finished (or even your "
"own idea), please contact us either in IRC or mailing list."
msgstr ""
#: template/gsoc.html.j2:34
msgid ""
"The GNUnet team is currently working on a transport layer rewrite in order "
"to fix core issues with connectivity. This new component is currently "
"developed under the name \"TNG\". What is currently known as \"transport "
"plugins\" will in the TNG be represented as \"communicators\". Communicators "
"are processes with a well defined API that allow to connect peers over a "
"specific protocol. The primary protocol which are already implemented are "
"UNIX sockets, UDP sockets, and TCP sockets. For a truly resilient network, "
"other connectivity options such as WiFi mesh, Bluetooth, HTTP(S), QUIC or "
"even more obscure alternatives such as radio are required. In this project, "
"the goal is to select, implement and test new communicators. While TNG is "
"not yet ready, communicators can, by design, be developed and tested against "
"the current API. We expect that this project can be worked on by multiple "
"students as there are a lot of protocols to choose from. The tasks would "
"consist of:
Advantageous "
"skills/languages/frameworks:
Difficulty: Average, "
"but depends on selected protocols.
Mentors: Martin "
"Schanzenbach, t3sserakt"
msgstr ""
#: template/gsoc.html.j2:79
msgid ""
"The REST API currently only supports a single user system. This is an issue "
"as on multi-user systems, access control must be enfoced on a per-user "
"basis. In this project, the REST service must be extended to support user "
"authentication. This includes the correct handling of user context switches. "
"
Advantageous skills/"
"languages/frameworks:
Difficulty: Beginner
Mentors:"
"strong> Martin Schanzenbach"
msgstr ""
#: template/gsoc.html.j2:111
msgid ""
"reclaimID is a decentralized identity system build on top of the GNU Name "
"System. Currently, there is a Webextension which uses the GNUnet REST API. In order to improve adoption and "
"ease of use, this project aims to include a full GNUnet node within the "
"Webextention as a fallback. GNUnet can be compiled to Web Assembly or "
"JavaScript as demonstrated here. The idea "
"is to improve upon this concept and support more of GNUnet's subsystems. The "
"difficulty of this project largely depends on the students proficiency with "
"build tools, emscripten and improvisation skills. There non-exhaustive task "
"list would be:
"
"Advantageous skills/languages/frameworks:
Difficulty: "
"Challenging
Mentors: Martin Schanzenbach"
msgstr ""
#: template/gsoc.html.j2:147
msgid ""
"Currently, the keys in our statistics database are too verbose. For example: "
"
nse # flood messages received: 13
nse # peers connected: 4
nse # nodes in the network (estimate): 203
nse # flood messages "
"started: 5
nse # estimated network diameter: 3
nse # flood "
"messages transmitted: 10
With such verbose keys there's no " "easy way to form compact JSON document or entries for time-series database. " "And you can't query single stats without having to copypaste the line " "exactly and put in quotes. In short, the goals are to...
Please be aware that this project is still in an early alpha stage when " "it comes to running software – its not an easy task to rewrite the " "whole Internet! We are happy to get your helping " "hand anytime! Further information is available in our handbook. If you have any queries " "about the installation or the usage, please get in " "touch!
" msgstr "" #: template/install.html.j2:30 msgid "" "We recommend to use binary packages provided by the package manager " "integrated within your Operating System. GNUnet is reportedly available for " "at least: If GNUnet is " "available for your Operating System and it is missing, send us feedback so " "that we can add it to this list. Furthermore, if you are interested in " "packaging GNUnet for your Operating System, get in touch with us at gnunet-" "developers@gnu.org if you require help with this job. If you were using an " "Operating System with the Alpine package manager, GNUnet could be installed " "as simple as:" msgstr "" #: template/install.html.j2:61 msgid "" "Next we describe a generic way to install from source. If you are using one " "of the following Operating Systems these step-by-step guides might be " "useful: ArchPi, Debian 9, Mac OS, " "NetBSD, Ubuntu 1804. Be aware that not all of them might be " "totally up-to-date! Please ask us if you get " "stuck." msgstr "" #: template/install.html.j2:75 msgid "" "First, install the required dependencies of GNUnet. There are base requirements and " "optional requirements." msgstr "" #: template/install.html.j2:81 msgid "" "Now, you need to decide if you want to install GNUnet from the release " "tarball or from git. If you want to use GNUnet and there is no binary " "package available for your OS, you should stick with the release tarball. If " "you want to develop using the most recent build, you should go with the git repository." msgstr "" #: template/install.html.j2:98 msgid "Alternatively, get the sources from git by entering:" msgstr "" #: template/install.html.j2:106 msgid "" "Before building GNUnet, make sure that you setup the required groups and add " "your user to the groupgnunet
:"
msgstr ""
#: template/install.html.j2:117
msgid "To compile GNUnet, execute:"
msgstr ""
#: template/install.html.j2:128
msgid ""
"You can find more configuration flags in the README.