monero-project/monero-site
monero-project/monero-site
1
0
Fork 0
mirror of https://github.com/monero-project/monero-site.git synced 2024-11-19 10:31:18 +00:00
Code Issues Projects Releases Packages Wiki Activity Actions
monero-site/knowledge-base/moneropedia/garlic-routing.md
anonimal 000e95cfe4
Moneropedia: add/update/cleanup/fix entries 
Added:
 - In-net
 - Lease
 - Message
 - I2NP (skeleton file)
 - Tunnel (skeleton file)

Updated/cleaned-up/fixed:
 - Router-Info
 - Lease-Set
 - Garlic-Routing
 - Floodfill
 - Destination

Note: term'ed lease-set to LeaseSet because of conflict with Lease

Referencing:
 - monero-project/kovri#256
 - monero-project/monero-site#155
2016-10-15 05:37:07 +00:00

2.1 KiB
Raw Blame History

layout entry tags terms summary
moneropedia Garlic Routing
kovri
garlic-routing
Routing technology as implemented in Kovri/I2P

The Basics

The term Garlic Routing has a diverse history of varying interpretations.

As it currently stands, Monero defines Garlic Routing as the method in which @Kovri and @I2P create a @message-based anonymous overlay network of internet peers.

History

In written form, the term Garlic Routing can be seen as early as June of 2000 in Roger Dingledine's Free Haven Master's thesis (Section 8.1.1) as derived from the term Onion Routing.

As recent as October of 2016, #tor-dev has offered insight into the creation of the term Garlic Routing:

Nick Mathewson:

[I think that there was some attempt to come up with a plant whose structure resembled the 'leaky-pipe' topology of tor, but I don't believe we ever settled on one.]

Roger Dingledine:

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.

Note: permission to use the aforementioned quotes were granted by Nick Mathewson and Roger Dingledine

In-depth Information

In technical terms, for @Kovri and @I2P, Garlic Routing translates to any/all of the following:

  • Layered Encryption (like Onion Routing)
  • Bundling multiple @messages together (garlic cloves)
  • ElGamal/AES Encryption

Note: though Tor uses layered encryption, Tor does not use ElGamal and is not message-based.

Notes

  • In terms of Onion/Garlic Routing, another way to envision layered encryption is by replacing the onion/garlic with a Matryoshka doll
  • For more technical details on Garlic Routing, read the @Java-I2P entry on Garlic Routing