Moneropedia: finish Garlic-Encryption

- Resolves remaining TODO's
- Also, minor adjustments in Encryption/Garlic-Routing

Referencing:
 - monero-project/kovri#256
 - monero-project/monero-site#155
This commit is contained in:
anonimal 2016-10-20 10:09:47 +00:00
parent 27214fd58b
commit 613995da5b
No known key found for this signature in database
GPG key ID: 66A76ECF914409F1
3 changed files with 18 additions and 6 deletions

View file

@ -2,7 +2,7 @@
layout: moneropedia layout: moneropedia
entry: "Encryption" entry: "Encryption"
tags: ["kovri"] tags: ["kovri"]
terms: ["encryption", "encrypted", "encrypting"] terms: ["encryption", "encrypted", "encrypting", "decryption", "decrypted", "decrypting"]
summary: "The process of encoding messages or information in a way that only authorized parties can decode and read" summary: "The process of encoding messages or information in a way that only authorized parties can decode and read"
--- ---

View file

@ -3,13 +3,23 @@ layout: moneropedia
entry: "Garlic-Encryption" entry: "Garlic-Encryption"
tags: ["kovri"] tags: ["kovri"]
terms: ["Garlic-Encryption", "Layered-Encryption"] terms: ["Garlic-Encryption", "Layered-Encryption"]
summary: "TODO(anonimal): finish" summary: "Layered encryption as implemented in Kovri / I2P"
--- ---
### The Basics ### The Basics
TODO(anonimal): finish @garlic-encryption is @I2P's implementation of @message based @layered-encryption (similar to flow-based [Onion-Routing](https://en.wikipedia.org/wiki/Onion_routing)).
By @encrypting @messages in layers, this allows a @message to be routed through a sequence of proxies without allowing the proxies (or any intermediaries) to read the contents of the @message. @Layered-Encryption is a fundamental feature in @Kovri, @I2P, and [Tor](https://torproject.org) and is the cornerstone for securing anonymity within these overlay-networks.
### In-depth information ### In-depth information
TODO(anonimal): finish For @garlic-encryption, the primary difference between @Kovri/@I2P and Tor is:
- @Kovri/@I2P bundles multiple @messages together to form garlic "cloves"
- any number of messages can be contained in a "clove" instead of *only* a single message
- @Kovri/@I2P uses [ElGamal](https://en.wikipedia.org/wiki/ElGamal)/[AES](https://en.wikipedia.org/wiki/Advanced_Encryption_Standard) @encryption for @messages and @transports
### Notes
For details, see @garlic-routing.

View file

@ -25,7 +25,7 @@ As recent as October of 2016, [#tor-dev](https://oftc.net/WebChat/) has offered
>during the free haven brainstorming, there was a moment where we described a routing mechanism, and somebody said "garlic routing!", and everybody laughed. >during the free haven brainstorming, there was a moment where we described a routing mechanism, and somebody said "garlic routing!", and everybody laughed.
so we for sure thought we had invented the name, at the time. so we for sure thought we had invented the name, at the time.
Note: permission to use the aforementioned quotes were granted by Nick Mathewson and Roger Dingledine *Note: permission to use the aforementioned quotes were granted by Nick Mathewson and Roger Dingledine*
### In-depth Information ### In-depth Information
@ -35,7 +35,9 @@ In technical terms, for @Kovri and @I2P, *@garlic-routing* translates to any/all
- Bundling multiple @messages together (garlic cloves) - Bundling multiple @messages together (garlic cloves)
- ElGamal/AES @encryption - ElGamal/AES @encryption
Note: though [Tor](https://torproject.org/) uses @layered-encryption, Tor does not use ElGamal and is not message-based. *Note: though [Tor](https://torproject.org/) uses @layered-encryption, Tor does not use ElGamal and is not message-based.*
**Read more in @garlic-encryption.**
### Notes ### Notes