diff options
author | ng0 <ng0@n0.is> | 2017-12-30 12:21:03 +0000 |
---|---|---|
committer | ng0 <ng0@n0.is> | 2017-12-30 12:21:03 +0000 |
commit | f3752accc1b45b227ad4ccf475b940258e7a849c (patch) | |
tree | 192633c84866bd55764a53c2b07fde27d73f27f3 /doc | |
parent | 67e2e6ad94b470ae591fb37514f0ab4da82a851f (diff) | |
download | gnunet-f3752accc1b45b227ad4ccf475b940258e7a849c.tar.gz gnunet-f3752accc1b45b227ad4ccf475b940258e7a849c.zip |
doc: philosophy
Diffstat (limited to 'doc')
-rw-r--r-- | doc/documentation/chapters/philosophy.texi | 21 |
1 files changed, 11 insertions, 10 deletions
diff --git a/doc/documentation/chapters/philosophy.texi b/doc/documentation/chapters/philosophy.texi index a45ebeb05..6a2eedcd3 100644 --- a/doc/documentation/chapters/philosophy.texi +++ b/doc/documentation/chapters/philosophy.texi | |||
@@ -317,7 +317,7 @@ traffic, bringing back the traditional technique of using indirection and | |||
317 | source rewriting. Source rewriting is required to gain anonymity since | 317 | source rewriting. Source rewriting is required to gain anonymity since |
318 | otherwise an adversary could tell if a message originated from a host by | 318 | otherwise an adversary could tell if a message originated from a host by |
319 | looking at the source address. If all packets look like they originate | 319 | looking at the source address. If all packets look like they originate |
320 | from a node, the adversary can not tell which ones originate from that | 320 | from one node, the adversary can not tell which ones originate from that |
321 | node and which ones were routed. | 321 | node and which ones were routed. |
322 | Note that in this mindset, any node can decide to break the | 322 | Note that in this mindset, any node can decide to break the |
323 | source-rewriting paradigm without violating the protocol, as this | 323 | source-rewriting paradigm without violating the protocol, as this |
@@ -338,7 +338,7 @@ This increases the efficiency of the network as we can indirect less under | |||
338 | higher load.@footnote{Krista Bennett and Christian Grothoff. | 338 | higher load.@footnote{Krista Bennett and Christian Grothoff. |
339 | GAP --- practical anonymous networking. In Proceedings of | 339 | GAP --- practical anonymous networking. In Proceedings of |
340 | Designing Privacy Enhancing Technologies, 2003. | 340 | Designing Privacy Enhancing Technologies, 2003. |
341 | (@uref{https://gnunet.org/git/bibliography.git/plain/docs/aff.pdf, pdf})} | 341 | (@uref{https://gnunet.org/git/bibliography.git/plain/docs/aff.pdf, https://gnunet.org/git/bibliography.git/plain/docs/aff.pdf}}} |
342 | 342 | ||
343 | @cindex Deniability | 343 | @cindex Deniability |
344 | @node Deniability | 344 | @node Deniability |
@@ -394,7 +394,7 @@ GNS@footnote{Matthias Wachs, Martin Schanzenbach, and Christian Grothoff. | |||
394 | A Censorship-Resistant, Privacy-Enhancing and Fully Decentralized Name | 394 | A Censorship-Resistant, Privacy-Enhancing and Fully Decentralized Name |
395 | System. In proceedings of 13th International Conference on Cryptology and | 395 | System. In proceedings of 13th International Conference on Cryptology and |
396 | Network Security (CANS 2014). 2014. | 396 | Network Security (CANS 2014). 2014. |
397 | @uref{https://gnunet.org/git/bibliography.git/plain/docs/gns2014wachs.pdf, pdf}} | 397 | @uref{https://gnunet.org/git/bibliography.git/plain/docs/gns2014wachs.pdf, https://gnunet.org/git/bibliography.git/plain/docs/gns2014wachs.pdf}} |
398 | zones are similar to those of DNS zones, but instead of a hierarchy of | 398 | zones are similar to those of DNS zones, but instead of a hierarchy of |
399 | authorities to governing their use, GNS zones are controlled by a private | 399 | authorities to governing their use, GNS zones are controlled by a private |
400 | key. | 400 | key. |
@@ -405,10 +405,11 @@ Whereas GNS, being decentralised by design, stores that information in | |||
405 | DHT. The validity of the records is assured cryptographically, by | 405 | DHT. The validity of the records is assured cryptographically, by |
406 | signing them with the private key of the respective zone. | 406 | signing them with the private key of the respective zone. |
407 | 407 | ||
408 | Anyone trying to resolve records in a zone your domain can then verify the | 408 | Anyone trying to resolve records in a zone of your domain can then verify |
409 | signature on the records they get from the DHT and be assured that they | 409 | the signature of the records they get from the DHT and be assured that |
410 | are indeed from the respective zone. To make this work, there is a 1:1 | 410 | they are indeed from the respective zone. |
411 | correspondence between zones and their public-private key pairs. | 411 | To make this work, there is a 1:1 correspondence between zones and |
412 | their public-private key pairs. | ||
412 | So when we talk about the owner of a GNS zone, that's really the owner of | 413 | So when we talk about the owner of a GNS zone, that's really the owner of |
413 | the private key. | 414 | the private key. |
414 | And a user accessing a zone needs to somehow specify the corresponding | 415 | And a user accessing a zone needs to somehow specify the corresponding |
@@ -418,8 +419,8 @@ public key first. | |||
418 | @node Egos | 419 | @node Egos |
419 | @subsection Egos | 420 | @subsection Egos |
420 | 421 | ||
421 | Egos are your "identities" in GNUnet. Any user can assume multiple | 422 | Egos are your "identities" in GNUnet. Any user can assume multiple |
422 | identities, for example to separate their activities online. Egos can | 423 | identities, for example to separate their activities online. Egos can |
423 | correspond to pseudonyms or real-world identities. Technically, an | 424 | correspond to pseudonyms or real-world identities. Technically, an |
424 | ego is first of all a public-private key pair. | 425 | ego is first of all a public-private key pair. |
425 | 426 | ||