aboutsummaryrefslogtreecommitdiff
path: root/doc/documentation/chapters/philosophy.texi
diff options
context:
space:
mode:
Diffstat (limited to 'doc/documentation/chapters/philosophy.texi')
-rw-r--r--doc/documentation/chapters/philosophy.texi11
1 files changed, 6 insertions, 5 deletions
diff --git a/doc/documentation/chapters/philosophy.texi b/doc/documentation/chapters/philosophy.texi
index c8e2651c3..681d5acc3 100644
--- a/doc/documentation/chapters/philosophy.texi
+++ b/doc/documentation/chapters/philosophy.texi
@@ -47,7 +47,9 @@ Refer to @uref{https://www.gnu.org/philosophy/free-sw.html, https://www.gnu.org/
47@item GNUnet must only disclose the minimal amount of information 47@item GNUnet must only disclose the minimal amount of information
48necessary. 48necessary.
49@c TODO: Explain 'fully' in the terminology section. 49@c TODO: Explain 'fully' in the terminology section.
50@item GNUnet must be fully distributed and survive Byzantine failures 50@item GNUnet must be fully distributed and survive
51@uref{https://en.wikipedia.org/wiki/Byzantine_fault_tolerance, Byzantine failures}
52@footnote{@uref{https://en.wikipedia.org/wiki/Byzantine_fault_tolerance, https://en.wikipedia.org/wiki/Byzantine_fault_tolerance}}
51at any position in the network. 53at any position in the network.
52@item GNUnet must make it explicit to the user which entities are 54@item GNUnet must make it explicit to the user which entities are
53considered to be trustworthy when establishing secured communications. 55considered to be trustworthy when establishing secured communications.
@@ -163,7 +165,7 @@ DH (Diffie---Hellman) key exchange using ephemeral eliptic curve
163cryptography. The ephemeral ECC (Eliptic Curve Cryptography) keys are 165cryptography. The ephemeral ECC (Eliptic Curve Cryptography) keys are
164signed using ECDSA (@uref{http://en.wikipedia.org/wiki/ECDSA, ECDSA}). 166signed using ECDSA (@uref{http://en.wikipedia.org/wiki/ECDSA, ECDSA}).
165The shared secret from ECDHE is used to create a pair of session keys 167The shared secret from ECDHE is used to create a pair of session keys
166@c FIXME: LOng word for HKDF 168@c FIXME: LOng word for HKDF. More FIXMEs: Explain MITM etc.
167(using HKDF) which are then used to encrypt the communication between the 169(using HKDF) which are then used to encrypt the communication between the
168two peers using both 256-bit AES (Advanced Encryption Standard) 170two peers using both 256-bit AES (Advanced Encryption Standard)
169and 256-bit Twofish (with independently derived secret keys). 171and 256-bit Twofish (with independently derived secret keys).
@@ -173,8 +175,6 @@ without requiring signatures each time. GNUnet uses SHA-512
173(Secure Hash Algorithm) hash codes to verify the integrity of messages. 175(Secure Hash Algorithm) hash codes to verify the integrity of messages.
174 176
175In GNUnet, the identity of a host is its public key. For that reason, 177In GNUnet, the identity of a host is its public key. For that reason,
176@c FIXME: is it clear to the average reader what a man-in-the-middle
177@c attack is?
178man-in-the-middle attacks will not break the authentication or accounting 178man-in-the-middle attacks will not break the authentication or accounting
179goals. Essentially, for GNUnet, the IP of the host has nothing to do with 179goals. Essentially, for GNUnet, the IP of the host has nothing to do with
180the identity of the host. As the public key is the only thing that truly 180the identity of the host. As the public key is the only thing that truly
@@ -420,8 +420,9 @@ public key first.
420@node Egos 420@node Egos
421@subsection Egos 421@subsection Egos
422 422
423@c what is the difference between peer identity and egos? It seems
424@c like both are linked to public-private key pair.
423Egos are your "identities" in GNUnet. Any user can assume multiple 425Egos are your "identities" in GNUnet. Any user can assume multiple
424identities, for example to separate their activities online. Egos can 426identities, for example to separate their activities online. Egos can
425correspond to pseudonyms or real-world identities. Technically, an 427correspond to pseudonyms or real-world identities. Technically, an
426ego is first of all a public-private key pair. 428ego is first of all a public-private key pair.
427