diff options
author | ng0 <ng0@infotropique.org> | 2017-10-17 16:50:33 +0000 |
---|---|---|
committer | ng0 <ng0@infotropique.org> | 2017-10-17 16:50:33 +0000 |
commit | ff4c30d5417e4152db056b00188b63da07f1e4c8 (patch) | |
tree | 2fd33a5d31f8961dd60cf7fcf75bbe782c320169 /doc/chapters | |
parent | b95bd7b268372f5ba7fab90194d1c5b16f481a63 (diff) | |
download | gnunet-ff4c30d5417e4152db056b00188b63da07f1e4c8.tar.gz gnunet-ff4c30d5417e4152db056b00188b63da07f1e4c8.zip |
philosophy: Add footnotes.
Diffstat (limited to 'doc/chapters')
-rw-r--r-- | doc/chapters/philosophy.texi | 30 |
1 files changed, 18 insertions, 12 deletions
diff --git a/doc/chapters/philosophy.texi b/doc/chapters/philosophy.texi index 9f4702b49..cb8787672 100644 --- a/doc/chapters/philosophy.texi +++ b/doc/chapters/philosophy.texi | |||
@@ -158,8 +158,8 @@ active transport services at the same time, and each of these can have a | |||
158 | different addresses. Binding messages expire after at most a week (the | 158 | different addresses. Binding messages expire after at most a week (the |
159 | timeout can be shorter if the user configures the node appropriately). This | 159 | timeout can be shorter if the user configures the node appropriately). This |
160 | expiration ensures that the network will eventually get rid of outdated | 160 | expiration ensures that the network will eventually get rid of outdated |
161 | advertisements.@ | 161 | advertisements. |
162 | More details can be found in the paper @uref{https://gnunet.org/transports, A Transport Layer Abstraction for Peer-to-Peer Networks}. | 162 | @footnote{More details can be found in @uref{https://gnunet.org/transports, A Transport Layer Abstraction for Peer-to-Peer Networks}} |
163 | 163 | ||
164 | @node Accounting to Encourage Resource Sharing | 164 | @node Accounting to Encourage Resource Sharing |
165 | @subsection Accounting to Encourage Resource Sharing | 165 | @subsection Accounting to Encourage Resource Sharing |
@@ -187,7 +187,8 @@ request a (possibly lower) effective priority. Then, they drop the requests | |||
187 | with the lowest effective priority to satisfy their resource constraints. This | 187 | with the lowest effective priority to satisfy their resource constraints. This |
188 | way, GNUnet's economic model ensures that nodes that are not currently | 188 | way, GNUnet's economic model ensures that nodes that are not currently |
189 | considered to have a surplus in contributions will not be served if the | 189 | considered to have a surplus in contributions will not be served if the |
190 | network load is high. More details can be found in @uref{https://gnunet.org/ebe, this paper}. | 190 | network load is high. |
191 | @footnote{More details can be found in @uref{https://gnunet.org/ebe, this paper}} | ||
191 | 192 | ||
192 | @node Confidentiality | 193 | @node Confidentiality |
193 | @subsection Confidentiality | 194 | @subsection Confidentiality |
@@ -215,16 +216,18 @@ anonymous file sharing). | |||
215 | Providing anonymity for users is the central goal for the anonymous | 216 | Providing anonymity for users is the central goal for the anonymous |
216 | file-sharing application. Many other design decisions follow in the footsteps | 217 | file-sharing application. Many other design decisions follow in the footsteps |
217 | of this requirement. Anonymity is never absolute. While there are various | 218 | of this requirement. Anonymity is never absolute. While there are various |
218 | @uref{https://gnunet.org/anonymity_metric, scientific metrics} that can help quantify the level of anonymity that a | 219 | @uref{https://gnunet.org/anonymity_metric, scientific metrics} that can |
219 | given mechanism provides, there is no such thing as complete anonymity. | 220 | help quantify the level of anonymity that a given mechanism provides, |
221 | there is no such thing as complete anonymity. | ||
220 | GNUnet's file-sharing implementation allows users to select for each | 222 | GNUnet's file-sharing implementation allows users to select for each |
221 | operation (publish, search, download) the desired level of anonymity. | 223 | operation (publish, search, download) the desired level of anonymity. |
222 | The metric used is the amount of cover traffic available to hide the request. | 224 | The metric used is the amount of cover traffic available to hide the request. |
223 | While this metric is not as good as, for example, the theoretical metric | 225 | While this metric is not as good as, for example, the theoretical metric |
224 | given in @uref{https://gnunet.org/anonymity_metric, scientific metrics}, it is probably the best metric available to | 226 | given in @uref{https://gnunet.org/anonymity_metric, scientific metrics}, |
225 | a peer with a purely local view of the world that does not rely on unreliable | 227 | it is probably the best metric available to a peer with a purely local |
226 | external information. The default anonymity level is 1, which uses anonymous | 228 | view of the world that does not rely on unreliable external information. |
227 | routing but imposes no minimal requirements on cover traffic. It is possible | 229 | The default anonymity level is 1, which uses anonymous routing but |
230 | imposes no minimal requirements on cover traffic. It is possible | ||
228 | to forego anonymity when this is not required. The anonymity level of 0 | 231 | to forego anonymity when this is not required. The anonymity level of 0 |
229 | allows GNUnet to use more efficient, non-anonymous routing. | 232 | allows GNUnet to use more efficient, non-anonymous routing. |
230 | 233 | ||
@@ -242,7 +245,8 @@ participating nodes in the network and that it can thus see many of the | |||
242 | node-to-node interactions since it controls some of the nodes. | 245 | node-to-node interactions since it controls some of the nodes. |
243 | 246 | ||
244 | The system tries to achieve anonymity based on the idea that users can be | 247 | The system tries to achieve anonymity based on the idea that users can be |
245 | anonymous if they can hide their actions in the traffic created by other users. | 248 | anonymous if they can hide their actions in the traffic created by other |
249 | users. | ||
246 | Hiding actions in the traffic of other users requires participating in the | 250 | Hiding actions in the traffic of other users requires participating in the |
247 | traffic, bringing back the traditional technique of using indirection and | 251 | traffic, bringing back the traditional technique of using indirection and |
248 | source rewriting. Source rewriting is required to gain anonymity since | 252 | source rewriting. Source rewriting is required to gain anonymity since |
@@ -263,7 +267,8 @@ have to indirect the replies if we don't think we need more traffic to hide | |||
263 | our own actions.@ | 267 | our own actions.@ |
264 | 268 | ||
265 | This increases the efficiency of the network as we can indirect less under | 269 | This increases the efficiency of the network as we can indirect less under |
266 | higher load. More details can be found in @uref{https://gnunet.org/gap, this paper}. | 270 | higher load. |
271 | @footnote{More details can be found in @uref{https://gnunet.org/gap, this paper}} | ||
267 | 272 | ||
268 | @node Deniability | 273 | @node Deniability |
269 | @subsection Deniability | 274 | @subsection Deniability |
@@ -282,7 +287,8 @@ encryption as the link-encryption between the nodes. GNUnet has | |||
282 | encryption on the network layer (link encryption, confidentiality, | 287 | encryption on the network layer (link encryption, confidentiality, |
283 | authentication) and again on the application layer (provided | 288 | authentication) and again on the application layer (provided |
284 | by @command{gnunet-publish}, @command{gnunet-download}, @command{gnunet-search} | 289 | by @command{gnunet-publish}, @command{gnunet-download}, @command{gnunet-search} |
285 | and @command{gnunet-gtk}). More details can be found @uref{https://gnunet.org/encoding, here}. | 290 | and @command{gnunet-gtk}). |
291 | @footnote{More details can be found @uref{https://gnunet.org/encoding, here}} | ||
286 | 292 | ||
287 | @node Peer Identities | 293 | @node Peer Identities |
288 | @subsection Peer Identities | 294 | @subsection Peer Identities |