From 841f7c1efbe850d10d4319b72dd8763cb9e57d10 Mon Sep 17 00:00:00 2001 From: anonimal Date: Wed, 19 Oct 2016 06:59:21 +0000 Subject: [PATCH] Moneropedia: resolve various unfinished entries - Resolved TODO's for Base32/64-address, Destination, Transports Referencing: - monero-project/kovri#256 - monero-project/monero-site#155 --- knowledge-base/moneropedia/base32-address.md | 2 -- knowledge-base/moneropedia/base64-address.md | 6 ++---- knowledge-base/moneropedia/destination.md | 12 ++++++------ knowledge-base/moneropedia/transports.md | 9 ++++----- 4 files changed, 12 insertions(+), 17 deletions(-) diff --git a/knowledge-base/moneropedia/base32-address.md b/knowledge-base/moneropedia/base32-address.md index 10284db5..ef38e414 100644 --- a/knowledge-base/moneropedia/base32-address.md +++ b/knowledge-base/moneropedia/base32-address.md @@ -22,8 +22,6 @@ where Ultimately, a Base32 address is a 52 character [Base32 encoded representation](https://en.wikipedia.org/wiki/Base32) of the full SHA-256 hash of an @I2P @base64-address. -TODO(anonimal): finish (256 bits, etc.) - ### Notes **Note: `.b32` is not a sub-domain of `.i2p`** diff --git a/knowledge-base/moneropedia/base64-address.md b/knowledge-base/moneropedia/base64-address.md index 99b85727..a704aaf2 100644 --- a/knowledge-base/moneropedia/base64-address.md +++ b/knowledge-base/moneropedia/base64-address.md @@ -8,15 +8,13 @@ summary: "Base64 encoded I2P destination" ### The Basics -A Base64 address is a 516-character [Base64 encoded](https://en.wikipedia.org/wiki/Base64) @I2P @destination. +A @base64-address is a 516-character [Base64 encoded](https://en.wikipedia.org/wiki/Base64) @I2P @destination. @base64-addresses are primarily used for @address-book, @jump-service, and also internally. Example: {:.cli-code} AQZGLAMpI9Q0l0kmMj1vpJJYK3CjLp~fE3MfvE-e7KMKjI5cPOH6EN8m794uHJ6b09qM8mb9VEv1lVLEov~usVliTSXCSHuRBOCIwIOuDNU0AbVa4BpIx~2sU4TxKhoaA3zQ6VzINoduTdR2IJhPvI5xzezp7dR21CEQGGTbenDslXeQ4iLHFA2~bzp1f7etSl9T2W9RID-KH78sRQmzWnv7dbhNodMbpO6xsf1vENf6bMRzqD5vgHEHZu2aSoNuPyYxDU1eM6--61b2xp9mt1k3ud-5WvPVg89RaU9ugU5cxaHgR927lHMCAEU2Ax~zUb3DbrvgQBOTHnJEx2Fp7pOK~PnP6ylkYKQMfLROosLDXinxOoSKP0UYCh2WgIUPwE7WzJH3PiJVF0~WZ1dZ9mg00c~gzLgmkOxe1NpFRNg6XzoARivNVB5NuWqNxr5WKWMLBGQ9YHvHO1OHhUJTowb9X90BhtHnLK2AHwO6fV-iHWxRJyDabhSMj1kuYpVUBQAEAAcAAA== -TODO(anonimal): finish - ### In-depth Information -TODO(anonimal): finish +See @destination for details behind @base64-address diff --git a/knowledge-base/moneropedia/destination.md b/knowledge-base/moneropedia/destination.md index 91237681..97cfe92b 100644 --- a/knowledge-base/moneropedia/destination.md +++ b/knowledge-base/moneropedia/destination.md @@ -2,18 +2,18 @@ layout: moneropedia entry: "Destination" tags: ["kovri"] -terms: ["Destination"] +terms: ["Destination", "Destinations"] summary: "A in-net address that serves as a final endpoint" --- ### The Basics -A destination is the @I2P @in-net address of the final endpoint you are trying to connect to (example: an @I2P website, service, or simply a peer). - -TODO(anonimal): finish +A @destination is the @I2P @in-net address of the final endpoint you are trying to connect to (example: an @I2P website, service, or Monero node). ### In-depth Information -An @I2P destination can be encoded into a @base32-address or @base64-address. Most users will only care about @base32-address or a `.i2p` hostname while, internally, @Kovri uses @base64-addresses. +An @I2P destination can be encoded into a @base32-address or @base64-address. Most users will only care about @base32-address or a `.i2p` hostname while, internally, @Kovri / @I2P @address-book uses @base64-addresses. Ultimately, all @destinations in @I2P are 516-byte (or longer) keys: -TODO(anonimal): finish +`256-byte public key + 128-byte signing key + a null certificate = 516 bytes in Base64 representation` + +Note: certificates are not used now but, if they were, the keys would be longer. diff --git a/knowledge-base/moneropedia/transports.md b/knowledge-base/moneropedia/transports.md index 4cc6268b..59504f99 100644 --- a/knowledge-base/moneropedia/transports.md +++ b/knowledge-base/moneropedia/transports.md @@ -8,14 +8,13 @@ summary: "The two encrypted transport layers for Kovri" ### The Basics -@Kovri comes with two encrypted [transport layer](https://en.wikipedia.org/wiki/Transport_layer) technologies that allow @Kovri to send @messages across the @I2P network. These *@transports* are @SSU and @NTCP. - -@SSU is encrypted [UDP](https://en.wikipedia.org/wiki/User_Datagram_Protocol) and @NTCP is encrypted [TCP](https://en.wikipedia.org/wiki/Transmission_Control_Protocol). They both allow you to securely use @I2P over [TCP/IP](https://en.wikipedia.org/wiki/Tcp/ip) connections. +@I2P comes with two encrypted transport layer technologies that allow @Kovri to securely use [TCP/IP](https://en.wikipedia.org/wiki/Tcp/ip) connections. These technologies (@SSU and @NTCP) are called *@transports*. ### In-depth information -TODO(anonimal): finish +@SSU is encrypted [UDP](https://en.wikipedia.org/wiki/User_Datagram_Protocol) and @NTCP is encrypted [TCP](https://en.wikipedia.org/wiki/Transmission_Control_Protocol). They provide @encryption at the [transport layer](https://en.wikipedia.org/wiki/Transport_layer) so higher level @messages can be sent through @tunnels across the @I2P network. ### Notes -Read about the transport layer in the [OSI model](https://en.wikipedia.org/wiki/OSI_model) +- Read about @I2P's transports on the [Transport](https://geti2p.net/en/docs/transport) page +- Read about the transports layer within the [OSI model](https://en.wikipedia.org/wiki/OSI_model)