aboutsummaryrefslogtreecommitdiff
path: root/doc/documentation
diff options
context:
space:
mode:
authorng0 <ng0@n0.is>2017-11-22 20:20:48 +0000
committerng0 <ng0@n0.is>2017-11-22 20:20:48 +0000
commitab80115e823a056f760b0bbd916be56e2711aa8d (patch)
tree638947226aa9bcc52805a26e22685ed079c58322 /doc/documentation
parent9812ab6abacc1e86a92dd8d110ada991ff85dab7 (diff)
downloadgnunet-ab80115e823a056f760b0bbd916be56e2711aa8d.tar.gz
gnunet-ab80115e823a056f760b0bbd916be56e2711aa8d.zip
+ philo
Diffstat (limited to 'doc/documentation')
-rw-r--r--doc/documentation/chapters/philosophy.texi18
1 files changed, 13 insertions, 5 deletions
diff --git a/doc/documentation/chapters/philosophy.texi b/doc/documentation/chapters/philosophy.texi
index af273fec6..e5c63339e 100644
--- a/doc/documentation/chapters/philosophy.texi
+++ b/doc/documentation/chapters/philosophy.texi
@@ -132,7 +132,7 @@ with the goals of the group is always preferable.
132@section Key Concepts 132@section Key Concepts
133 133
134In this section, the fundamental concepts of GNUnet are explained. 134In this section, the fundamental concepts of GNUnet are explained.
135@c FIXME: Use @uref{https://docs.gnunet.org/whatever/, research papers} 135@c FIXME: Use @uref{https://docs.gnunet.org/bib/, research papers}
136@c once we have the new bibliography + subdomain setup. 136@c once we have the new bibliography + subdomain setup.
137Most of them are also described in our research papers. 137Most of them are also described in our research papers.
138First, some of the concepts used in the GNUnet framework are detailed. 138First, some of the concepts used in the GNUnet framework are detailed.
@@ -155,9 +155,9 @@ The second part describes concepts specific to anonymous file-sharing.
155 155
156Almost all peer-to-peer communications in GNUnet are between mutually 156Almost all peer-to-peer communications in GNUnet are between mutually
157authenticated peers. The authentication works by using ECDHE, that is a 157authenticated peers. The authentication works by using ECDHE, that is a
158DH key exchange using ephemeral eliptic curve cryptography. The ephemeral 158DH (Diffie---Hellman) key exchange using ephemeral eliptic curve
159ECC (Eliptic Curve Cryptography) keys are signed using ECDSA. 159cryptography. The ephemeral ECC (Eliptic Curve Cryptography) keys are
160@c FIXME: Long word for ECDSA 160signed using ECDSA (@uref{http://en.wikipedia.org/wiki/ECDSA, ECDSA}).
161The shared secret from ECDHE is used to create a pair of session keys 161The shared secret from ECDHE is used to create a pair of session keys
162@c FIXME: LOng word for HKDF 162@c FIXME: LOng word for HKDF
163(using HKDF) which are then used to encrypt the communication between the 163(using HKDF) which are then used to encrypt the communication between the
@@ -230,6 +230,7 @@ this request is. If a peer responds to an important request, the
230recipient will increase its trust in the responder: 230recipient will increase its trust in the responder:
231the responder contributed resources. 231the responder contributed resources.
232If a peer is too busy to answer all requests, it needs to prioritize. 232If a peer is too busy to answer all requests, it needs to prioritize.
233@c FIXME: 'peers to not take' -> 'peers do not take' would make more sense
233For that, peers to not take the priorities of the requests received at 234For that, peers to not take the priorities of the requests received at
234face value. 235face value.
235First, they check how much they trust the sender, and depending on that 236First, they check how much they trust the sender, and depending on that
@@ -388,7 +389,14 @@ You can find your peer identity by running @command{gnunet-peerinfo -s}.
388@node Zones in the GNU Name System (GNS Zones) 389@node Zones in the GNU Name System (GNS Zones)
389@subsection Zones in the GNU Name System (GNS Zones) 390@subsection Zones in the GNU Name System (GNS Zones)
390 391
391GNS zones are similar to those of DNS zones, but instead of a hierarchy of 392@c FIXME: Explain or link to an explanation of the concept of public keys
393@c and private keys.
394GNS@footnote{Matthias Wachs, Martin Schanzenbach, and Christian Grothoff.
395A Censorship-Resistant, Privacy-Enhancing and Fully Decentralized Name
396System. In proceedings of 13th International Conference on Cryptology and
397Network Security (CANS 2014). 2014.
398@uref{https://gnunet.org/git/bibliography.git/plain/docs/gns2014wachs.pdf, pdf}}
399zones are similar to those of DNS zones, but instead of a hierarchy of
392authorities to governing their use, GNS zones are controlled by a private 400authorities to governing their use, GNS zones are controlled by a private
393key. 401key.
394When you create a record in a DNS zone, that information stored in your 402When you create a record in a DNS zone, that information stored in your