aboutsummaryrefslogtreecommitdiff
path: root/doc
diff options
context:
space:
mode:
Diffstat (limited to 'doc')
-rw-r--r--doc/documentation/chapters/philosophy.texi10
-rw-r--r--doc/documentation/chapters/user.texi6
2 files changed, 8 insertions, 8 deletions
diff --git a/doc/documentation/chapters/philosophy.texi b/doc/documentation/chapters/philosophy.texi
index 148f0cd91..72c3476a3 100644
--- a/doc/documentation/chapters/philosophy.texi
+++ b/doc/documentation/chapters/philosophy.texi
@@ -161,11 +161,11 @@ The second part describes concepts specific to anonymous file-sharing.
161 161
162Almost all peer-to-peer communications in GNUnet are between mutually 162Almost all peer-to-peer communications in GNUnet are between mutually
163authenticated peers. The authentication works by using ECDHE, that is a 163authenticated peers. The authentication works by using ECDHE, that is a
164DH (Diffie---Hellman) key exchange using ephemeral eliptic curve 164DH (Diffie---Hellman) key exchange using ephemeral elliptic curve
165cryptography. The ephemeral ECC (Eliptic Curve Cryptography) keys are 165cryptography. The ephemeral ECC (Elliptic Curve Cryptography) keys are
166signed using ECDSA (@uref{http://en.wikipedia.org/wiki/ECDSA, ECDSA}). 166signed using ECDSA (@uref{http://en.wikipedia.org/wiki/ECDSA, ECDSA}).
167The 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
168@c FIXME: LOng word for HKDF. More FIXMEs: Explain MITM etc. 168@c FIXME: Long word for HKDF. More FIXMEs: Explain MITM etc.
169(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
170two peers using both 256-bit AES (Advanced Encryption Standard) 170two peers using both 256-bit AES (Advanced Encryption Standard)
171and 256-bit Twofish (with independently derived secret keys). 171and 256-bit Twofish (with independently derived secret keys).
@@ -174,12 +174,12 @@ authenticates each packet
174without requiring signatures each time. GNUnet uses SHA-512 174without requiring signatures each time. GNUnet uses SHA-512
175(Secure Hash Algorithm) hash codes to verify the integrity of messages. 175(Secure Hash Algorithm) hash codes to verify the integrity of messages.
176 176
177@c Fixme: A while back I got the feedback that I should try and integrate 177@c FIXME: A while back I got the feedback that I should try and integrate
178@c explanation boxes in the long-run. So we could explain 178@c explanation boxes in the long-run. So we could explain
179@c "man-in-the-middle" and "man-in-the-middle attacks" and other words 179@c "man-in-the-middle" and "man-in-the-middle attacks" and other words
180@c which are not common knowledge. MITM is not common knowledge. To be 180@c which are not common knowledge. MITM is not common knowledge. To be
181@c selfcontained, we should be able to explain words and concepts used in 181@c selfcontained, we should be able to explain words and concepts used in
182@c a chapter or paragraph without hinting at wikipedia and other online 182@c a chapter or paragraph without hinting at Wikipedia and other online
183@c sources which might not be available or accessible to everyone. 183@c sources which might not be available or accessible to everyone.
184@c On the other hand we could write an introductionary chapter or book 184@c On the other hand we could write an introductionary chapter or book
185@c that we could then reference in each chapter, which sound like it 185@c that we could then reference in each chapter, which sound like it
diff --git a/doc/documentation/chapters/user.texi b/doc/documentation/chapters/user.texi
index f2dc5b35d..4a82295c4 100644
--- a/doc/documentation/chapters/user.texi
+++ b/doc/documentation/chapters/user.texi
@@ -92,7 +92,7 @@ start of @command{gnunet-gtk}).
92You can click on "Traffic" to see information about the amount of 92You can click on "Traffic" to see information about the amount of
93bandwidth your peer has consumed, and on "Storage" to check the amount 93bandwidth your peer has consumed, and on "Storage" to check the amount
94of storage available and used by your peer. Note that "Traffic" is 94of storage available and used by your peer. Note that "Traffic" is
95plotted cummulatively, so you should see a strict upwards trend in the 95plotted cumulatively, so you should see a strict upwards trend in the
96traffic. 96traffic.
97 97
98@node Peer Information 98@node Peer Information
@@ -227,7 +227,7 @@ a little area for downloading appears.
227In the downloading area, you can select the target directory (default is 227In the downloading area, you can select the target directory (default is
228"Downloads") and specify the desired filename (by default the filename it 228"Downloads") and specify the desired filename (by default the filename it
229taken from the meta data of the published file). Additionally, you can 229taken from the meta data of the published file). Additionally, you can
230specify if the download should be anonynmous and (for directories) if 230specify if the download should be anonymous and (for directories) if
231the download should be recursive. In most cases, you can simply start 231the download should be recursive. In most cases, you can simply start
232the download with the "Download!" button. 232the download with the "Download!" button.
233 233
@@ -309,7 +309,7 @@ rules - GO0T87F9BPMF8NKD5A54L2AH1T0GRML539TPFSRMCEA98182QD30
309@subsection The GNS Tab 309@subsection The GNS Tab
310@c %**end of header 310@c %**end of header
311 311
312Maintaing your zones is through the NAMESTORE service and is discussed 312Maintaining your zones is through the NAMESTORE service and is discussed
313here. You can manage your zone using @command{gnunet-identity} and 313here. You can manage your zone using @command{gnunet-identity} and
314@command{gnunet-namestore}, or most conveniently using 314@command{gnunet-namestore}, or most conveniently using
315@command{gnunet-namestore-gtk}. 315@command{gnunet-namestore-gtk}.