diff options
authorNils Gillmann <>2018-10-10 07:33:24 +0000
committerNils Gillmann <>2018-10-10 07:33:24 +0000
commite8606de55e081fa55dc718e6db4b397968a7c594 (patch)
parentd55141a33196e43139fde20d5fbb5707ecb6b29c (diff)
developer: likewise.
Signed-off-by: Nils Gillmann <>
1 files changed, 32 insertions, 26 deletions
diff --git a/doc/documentation/chapters/developer.texi b/doc/documentation/chapters/developer.texi
index e82e32b59..4038190a1 100644
--- a/doc/documentation/chapters/developer.texi
+++ b/doc/documentation/chapters/developer.texi
@@ -11,7 +11,8 @@ For developers, GNUnet is:
@itemize @bullet
@item developed by a community that believes in the GNU philosophy
@item Free Software (Free as in Freedom), licensed under the
-GNU Affero General Public License@footnote{@uref{,}}
+GNU Affero General Public License
@item A set of standards, including coding conventions and
architectural rules
@item A set of layered protocols, both specifying the communication
@@ -136,7 +137,7 @@ It can be accessed at
Anyone can report bugs.
@item Our site installation of the
-CI@footnote{Continuous Integration} system @code{Buildbot} is used
+Continuous Integration (CI) system @code{Buildbot} is used
to check GNUnet builds automatically on a range of platforms.
The web interface of this CI is exposed at
@@ -1230,7 +1231,11 @@ right set of features. We called this specialized set of libcurl
by GNUnet and some of its dependencies.
We download libgnurl and its digital signature from the GNU fileserver,
-assuming @env{TMPDIR} exists@footnote{It might be @file{/tmp}, @env{TMPDIR}, @env{TMP} or any other location. For consistency we assume @env{TMPDIR} points to @file{/tmp} for the remainder of this section.}
+assuming @env{TMPDIR} exists.
+Note: TMPDIR might be @file{/tmp}, @env{TMPDIR}, @env{TMP} or any other
+location. For consistency we assume @env{TMPDIR} points to @file{/tmp}
+for the remainder of this section.
@@ -1898,9 +1903,9 @@ random links are to be given
@item @code{GNUNET_TESTBED_TOPOLOGY_SCALE_FREE}: Connects peers in a
topology where peer connectivity follows power law - new peers are
connected with high probability to well connected peers.
-@footnote{See Emergence of Scaling in Random Networks. Science 286,
+(See Emergence of Scaling in Random Networks. Science 286,
509-512, 1999
-(@uref{, pdf})}
+(@uref{, pdf}))
@item @code{GNUNET_TESTBED_TOPOLOGY_FROM_FILE}: The topology information
is loaded from a file. The path to the file has to be given.
@@ -2294,7 +2299,8 @@ subsystem.
@node CORE must be started
@subsubsection CORE must be started
-A uncomplicated issue is bug #3993@footnote{@uref{,}}:
+A uncomplicated issue is bug #3993
Your configuration MUST somehow ensure that for each peer the
@code{CORE} service is started when the peer is setup, otherwise
@code{TESTBED} may fail to connect peers when the topology is initialized,
@@ -3941,11 +3947,8 @@ considers Bob's address to be valid, the connection itself is not
considered 'established'. In particular, Alice may have many addresses
for Bob that Alice considers valid.
-@c TODO: reference Footnotes so that I don't have to duplicate the
-@c footnotes or add them to an index at the end. Is this possible at
-@c all in Texinfo?
The @code{PONG} message is protected with a nonce/challenge against replay
-attacks@footnote{@uref{, replay}}
+attacks (@uref{, replay})
and uses an expiration time for the signature (but those are almost
implementation details).
@@ -4773,23 +4776,24 @@ then adds fundamental security to the connections:
@itemize @bullet
@item confidentiality with so-called perfect forward secrecy; we use
-ECDHE@footnote{@uref{, Elliptic-curve Diffie---Hellman}}
+(@uref{, Elliptic-curve Diffie---Hellman})
powered by Curve25519
-@footnote{@uref{, Curve25519}} for the key
+(@uref{, Curve25519}) for the key
exchange and then use symmetric encryption, encrypting with both AES-256
-@footnote{@uref{, AES-256}} and
-Twofish @footnote{@uref{, Twofish}}
+(@uref{, AES-256}) and
+Twofish (@uref{, Twofish})
@item @uref{, authentication}
is achieved by signing the ephemeral keys using Ed25519
-@footnote{@uref{, Ed25519}}, a deterministic
+(@uref{, Ed25519}), a deterministic
variant of ECDSA
-@footnote{@uref{, ECDSA}}
+(@uref{, ECDSA})
@item integrity protection (using SHA-512
-@footnote{@uref{, SHA-512}} to do
+(@uref{, SHA-512}) to do
-@footnote{@uref{, encrypt-then-MAC}})
+(@uref{, encrypt-then-MAC}))
@item Replay
-@footnote{@uref{, replay}}
+(@uref{, replay})
protection (using nonces, timestamps, challenge-response,
message counters and ephemeral keys)
@item liveness (keep-alive messages, timeout)
@@ -5037,7 +5041,8 @@ public-private key pair and signs the corresponding
@code{EphemeralKeyMessage} with its long-term key (which we usually call
the peer's identity; the hash of the public long term key is what results
in a @code{struct GNUNET_PeerIdentity} in all GNUnet APIs. The ephemeral
-key is ONLY used for an ECDHE@footnote{@uref{, Elliptic-curve Diffie---Hellman}}
+key is ONLY used for an ECDHE
+(@uref{, Elliptic-curve Diffie---Hellman})
exchange by the CORE service to establish symmetric session keys. A peer
will use the same @code{EphemeralKeyMessage} for all peers for
@code{REKEY_FREQUENCY}, which is usually 12 hours. After that time, it
@@ -5094,10 +5099,11 @@ All functions related to the key exchange and encryption/decryption of
messages can be found in @file{gnunet-service-core_kx.c} (except for the
cryptographic primitives, which are in @file{util/crypto*.c}).
Given the key material from ECDHE, a Key derivation function
-@footnote{@uref{, Key derivation function}}
+(@uref{, Key derivation function})
is used to derive two pairs of encryption and decryption keys for AES-256
and TwoFish, as well as initialization vectors and authentication keys
-(for HMAC@footnote{@uref{, HMAC}}).
+(for HMAC
+(@uref{, HMAC})).
The HMAC is computed over the encrypted payload.
Encrypted messages include an iv_seed and the HMAC in the header.
@@ -5523,15 +5529,15 @@ Let's close with a couple examples.
@table @asis
@item Average: 10, std dev: 1 Here the estimate would be
-2^10 = 1024 peers. @footnote{The range in which we can be 95% sure is:
+2^10 = 1024 peers. (The range in which we can be 95% sure is:
[2^8, 2^12] = [256, 4096]. We can be very (>99.7%) sure that the network
is not a hundred peers and absolutely sure that it is not a million peers,
-but somewhere around a thousand.}
+but somewhere around a thousand.)
@item Average 22, std dev: 0.2 Here the estimate would be
-2^22 = 4 Million peers. @footnote{The range in which we can be 99.7% sure
+2^22 = 4 Million peers. (The range in which we can be 99.7% sure
is: [2^21.4, 2^22.6] = [2.8M, 6.3M]. We can be sure that the network size
-is around four million, with absolutely way of it being 1 million.}
+is around four million, with absolutely way of it being 1 million.)
@end table