diff options
Diffstat (limited to 'doc')
-rw-r--r-- | doc/documentation/chapters/philosophy.texi | 18 |
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 | ||
134 | In this section, the fundamental concepts of GNUnet are explained. | 134 | In 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. |
137 | Most of them are also described in our research papers. | 137 | Most of them are also described in our research papers. |
138 | First, some of the concepts used in the GNUnet framework are detailed. | 138 | First, 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 | ||
156 | Almost all peer-to-peer communications in GNUnet are between mutually | 156 | Almost all peer-to-peer communications in GNUnet are between mutually |
157 | authenticated peers. The authentication works by using ECDHE, that is a | 157 | authenticated peers. The authentication works by using ECDHE, that is a |
158 | DH key exchange using ephemeral eliptic curve cryptography. The ephemeral | 158 | DH (Diffie---Hellman) key exchange using ephemeral eliptic curve |
159 | ECC (Eliptic Curve Cryptography) keys are signed using ECDSA. | 159 | cryptography. The ephemeral ECC (Eliptic Curve Cryptography) keys are |
160 | @c FIXME: Long word for ECDSA | 160 | signed using ECDSA (@uref{http://en.wikipedia.org/wiki/ECDSA, ECDSA}). |
161 | The shared secret from ECDHE is used to create a pair of session keys | 161 | The 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 | |||
230 | recipient will increase its trust in the responder: | 230 | recipient will increase its trust in the responder: |
231 | the responder contributed resources. | 231 | the responder contributed resources. |
232 | If a peer is too busy to answer all requests, it needs to prioritize. | 232 | If 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 | ||
233 | For that, peers to not take the priorities of the requests received at | 234 | For that, peers to not take the priorities of the requests received at |
234 | face value. | 235 | face value. |
235 | First, they check how much they trust the sender, and depending on that | 236 | First, 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 | ||
391 | GNS 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. | ||
394 | GNS@footnote{Matthias Wachs, Martin Schanzenbach, and Christian Grothoff. | ||
395 | A Censorship-Resistant, Privacy-Enhancing and Fully Decentralized Name | ||
396 | System. In proceedings of 13th International Conference on Cryptology and | ||
397 | Network Security (CANS 2014). 2014. | ||
398 | @uref{https://gnunet.org/git/bibliography.git/plain/docs/gns2014wachs.pdf, pdf}} | ||
399 | zones are similar to those of DNS zones, but instead of a hierarchy of | ||
392 | authorities to governing their use, GNS zones are controlled by a private | 400 | authorities to governing their use, GNS zones are controlled by a private |
393 | key. | 401 | key. |
394 | When you create a record in a DNS zone, that information stored in your | 402 | When you create a record in a DNS zone, that information stored in your |