diff --git a/_i18n/ar/resources/moneropedia/base32-address.md b/_i18n/ar/resources/moneropedia/base32-address.md deleted file mode 100644 index 0e3a88e2..00000000 --- a/_i18n/ar/resources/moneropedia/base32-address.md +++ /dev/null @@ -1,26 +0,0 @@ ---- -tags: ["kovri"] -terms: ["Base32-address", "Base32-addresses"] -summary: "Base32 encoded hash of a Base64 address" ---- - -{% include untranslated.html %} -### The Basics - -A Base32 address is a shortened, encoded version of an @I2P address. The Base32 address is the first part in a `.b32.i2p` hostname. - -Example: - -`i35yftyyb22xhcvghmev46t5knefur5v66qzekkajatwfwhyklvq.b32.i2p` - -where - -`i35yftyyb22xhcvghmev46t5knefur5v66qzekkajatwfwhyklvq` is the Base32 address. - -### In-depth Information - -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. - -### Notes - -**Note: `.b32` is not a sub-domain of `.i2p`** diff --git a/_i18n/ar/resources/moneropedia/base64-address.md b/_i18n/ar/resources/moneropedia/base64-address.md deleted file mode 100644 index b9985658..00000000 --- a/_i18n/ar/resources/moneropedia/base64-address.md +++ /dev/null @@ -1,21 +0,0 @@ ---- -tags: ["kovri"] -terms: ["Base64-address", "Base64-addresses"] -summary: "Base64 encoded I2P destination" ---- - -{% include untranslated.html %} -### The Basics - -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: - -``` -AQZGLAMpI9Q0l0kmMj1vpJJYK3CjLp~fE3MfvE-e7KMKjI5cPOH6EN8m794uHJ6b09qM8mb9VEv1lVLEov~usVliTSXCSHuRBOCIwIOuDNU0AbVa4BpIx~2sU4TxKhoaA3zQ6VzINoduTdR2IJhPvI5xzezp7dR21CEQGGTbenDslXeQ4iLHFA2~bzp1f7etSl9T2W9RID-KH78sRQmzWnv7dbhNodMbpO6xsf1vENf6bMRzqD5vgHEHZu2aSoNuPyYxDU1eM6--61b2xp9mt1k3ud-5WvPVg89RaU9ugU5cxaHgR927lHMCAEU2Ax~zUb3DbrvgQBOTHnJEx2Fp7pOK~PnP6ylkYKQMfLROosLDXinxOoSKP0UYCh2WgIUPwE7WzJH3PiJVF0~WZ1dZ9mg00c~gzLgmkOxe1NpFRNg6XzoARivNVB5NuWqNxr5WKWMLBGQ9YHvHO1OHhUJTowb9X90BhtHnLK2AHwO6fV-iHWxRJyDabhSMj1kuYpVUBQAEAAcAAA== -``` - - -### In-depth Information - -See @destination for details behind @base64-address diff --git a/_i18n/ar/resources/moneropedia/data-directory.md b/_i18n/ar/resources/moneropedia/data-directory.md deleted file mode 100644 index 761cfd46..00000000 --- a/_i18n/ar/resources/moneropedia/data-directory.md +++ /dev/null @@ -1,21 +0,0 @@ ---- -tags: ["kovri"] -terms: ["Data-Directory"] -summary: "Where essential kovri data for runtime is stored" ---- - -{% include untranslated.html %} -### The Basics - -Depending on your OS, @Kovri currently stores all run-time data in the following directory: - -- Linux/FreeBSD: - - `$HOME/.kovri` - -- OSX: - - `$HOME/Library/Application\ Support/Kovri` - -- Windows: - - `"$APPDATA"\\Kovri` - -This includes all configuration files, @address-book, certificates, and resources. diff --git a/_i18n/ar/resources/moneropedia/eepsite.md b/_i18n/ar/resources/moneropedia/eepsite.md deleted file mode 100644 index cd450d97..00000000 --- a/_i18n/ar/resources/moneropedia/eepsite.md +++ /dev/null @@ -1,29 +0,0 @@ ---- -tags: ["kovri"] -terms: ["Eepsite", "Hidden-Service", "Garlic-Site", "Garlic-Service"] -summary: "A website or service hosted within the I2P network" ---- - -{% include untranslated.html %} -### The Basics - -Is it [**EEP!** *(in response to the site's content)*](https://en.wikipedia.org/wiki/Onomatopoeia), or **end-to-end protocol**, or something else entirely different? - -While the original definition of eepsite has been lost with time, its use-case remains: an eepsite is a website or service that is hosted within (and only accessible by) the @I2P network. - -### In-depth Information - -Alternate names include: - -1. *Hidden Service* - - because the site/service is *hidden* within the @I2P network and can only be visited within the network -2. *Garlic Site* - - because the website utilizes @I2P's @garlic-routing technology as a means of communicating with a client - - because the service is hosted as a website and not any other type of service -3. *Garlic Service* - - because the service utilizes @I2P's @garlic-routing technology as a means of communicating with a client - - because the service is specific to services like IRC, email, or a Monero peer (but may also include websites) - -### Notes - -To learn how to setup an Eepsite (Hidden Service, Garlic Site, Garlic Service) visit the @Kovri [user-guide](https://gitlab.com/kovri-project/kovri-docs/blob/master/i18n/en/user_guide.md). diff --git a/_i18n/ar/resources/moneropedia/floodfill.md b/_i18n/ar/resources/moneropedia/floodfill.md deleted file mode 100644 index cccd9011..00000000 --- a/_i18n/ar/resources/moneropedia/floodfill.md +++ /dev/null @@ -1,14 +0,0 @@ ---- -tags: ["kovri"] -terms: ["Floodfill"] -summary: "An I2P router which maintains a distributed network-database" ---- - -{% include untranslated.html %} -### The Basics - -By actively managing a distributed network-database, a router with *floodfill* capability has the ability to help maintain network stability and resiliancy while also being decentralized and trust-less. - -### In-depth information - -Though floodfill itself is a simple storage system, the technical underpinnings of floodfill as it relates to @network-database and other protocols within @I2P are much more complex. Visit the [Network Database](https://geti2p.net/en/docs/how/network-database) page for details. diff --git a/_i18n/ar/resources/moneropedia/garlic-encryption.md b/_i18n/ar/resources/moneropedia/garlic-encryption.md deleted file mode 100644 index a0548b3c..00000000 --- a/_i18n/ar/resources/moneropedia/garlic-encryption.md +++ /dev/null @@ -1,24 +0,0 @@ ---- -tags: ["kovri"] -terms: ["Garlic-Encryption", "Layered-Encryption"] -summary: "Layered encryption as implemented in Kovri / I2P" ---- - -{% include untranslated.html %} -### The Basics - -@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 - -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. diff --git a/_i18n/ar/resources/moneropedia/garlic-routing.md b/_i18n/ar/resources/moneropedia/garlic-routing.md deleted file mode 100644 index 4a1d26b9..00000000 --- a/_i18n/ar/resources/moneropedia/garlic-routing.md +++ /dev/null @@ -1,44 +0,0 @@ ---- -tags: ["kovri"] -terms: ["Garlic-Routing"] -summary: "Routing technology as implemented in Kovri" ---- - -{% include untranslated.html %} -### 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. - -The @Garlic-Encryption of @Garlic-Routing is similar to the @Layered-Encryption of [Onion Routing](https://en.wikipedia.org/wiki/Onion_routing) and effectively conceals the IP address of the sender and secures information sent from the sender to its @destination (and vice-versa). - -### 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](http://www.freehaven.net/papers.html) (Section 8.1.1) as derived from the term Onion Routing. - -As recent as October of 2016, [#tor-dev](https://oftc.net/WebChat/) has offered insight into the creation of the term *@garlic-routing*: - -[Nick Mathewson](https://en.wikipedia.org/wiki/The_Tor_Project,_Inc): ->[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](https://en.wikipedia.org/wiki/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 was 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 (similar to the @layered-encryption in Onion Routing) -- Bundling multiple @messages together (garlic cloves) -- ElGamal/AES @encryption - -*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 - -- In terms of Onion/Garlic Routing, another way to envision layered @encryption is by replacing the onion/garlic with a [Matryoshka doll](https://en.wikipedia.org/wiki/Matryoshka_doll) - with each outer/inner doll having a lock and public key to the next/previous doll -- For more technical details on Garlic Routing, read the @Java-I2P entry on [Garlic Routing](https://geti2p.net/en/docs/how/garlic-routing) diff --git a/_i18n/ar/resources/moneropedia/i2np.md b/_i18n/ar/resources/moneropedia/i2np.md deleted file mode 100644 index 1e7841ae..00000000 --- a/_i18n/ar/resources/moneropedia/i2np.md +++ /dev/null @@ -1,27 +0,0 @@ ---- -tags: ["kovri"] -terms: ["I2NP"] -summary: "The I2P Network Protocol: the mechanism in which I2NP messages are sent over the I2P network" ---- - -{% include untranslated.html %} -### The Basics - -From @Java-I2P: - -> -@I2NP manages the routing and mixing of messages between routers, as well as the selection of what transports to use when communicating with a peer for which there are multiple common transports supported - -### In-depth information - -From @Java-I2P: - -> -@I2NP (@I2P Network Protocol) @messages can be used for one-hop, router-to-router, point-to-point @messages. By @encrypting and wrapping @messages in other @messages, they can be sent in a secure way through multiple hops to the ultimate @destination. @I2NP does not specify nor require any particular @transport layer but does require at least one @transport in use. - -> -Whenever a @destination wants to send a message to to another @destination, it provides its local router with both the @destination structure and the raw bytes of the message to be sent. The router then determines where to send it, delivers it through outbound @tunnels, instructing the end point to pass it along to the appropriate inbound @tunnel, where it is passed along again to that @tunnel's end point and made available to the target for reception. - -### Notes - -Read more about the @I2NP [protocol](https://geti2p.net/en/docs/protocol/i2np) and [specification](https://geti2p.net/spec/i2np). diff --git a/_i18n/ar/resources/moneropedia/i2p.md b/_i18n/ar/resources/moneropedia/i2p.md deleted file mode 100644 index 7a6980c3..00000000 --- a/_i18n/ar/resources/moneropedia/i2p.md +++ /dev/null @@ -1,30 +0,0 @@ ---- -tags: ["kovri"] -terms: ["I2P"] -summary: "The Invisible Internet Project: an anonymizing overlay network" ---- - -{% include untranslated.html %} -### Monero - -For Monero's implementation of @I2P, see @Kovri. For a comparison of @I2P to [Tor](https://torproject.org/), read the [Comparison](https://geti2p.net/en/comparison/tor) page. - -### The Basics - -From @Java-I2P: - ->The I2P network provides strong privacy protections for communication over the Internet. Many activities that would risk your privacy on the public Internet can be conducted anonymously inside I2P. - -### In-depth information - -From @Java-I2P: - ->I2P is an anonymous overlay network - a network within a network. It is intended to protect communication from dragnet surveillance and monitoring by third parties such as ISPs. - ->I2P is used by many people who care about their privacy: activists, oppressed people, journalists and whistleblowers, as well as the average person. - ->No network can be "perfectly anonymous". The continued goal of I2P is to make attacks more and more difficult to mount. Its anonymity will get stronger as the size of the network increases and with ongoing academic review. - -### Notes - -@I2P documentation and specifications are available [here](https://geti2p.net/docs/). diff --git a/_i18n/ar/resources/moneropedia/i2pcontrol.md b/_i18n/ar/resources/moneropedia/i2pcontrol.md deleted file mode 100644 index b419423c..00000000 --- a/_i18n/ar/resources/moneropedia/i2pcontrol.md +++ /dev/null @@ -1,16 +0,0 @@ ---- -tags: ["kovri"] -terms: ["I2PControl"] -summary: "An API inteface for Kovri and Java-I2P that allows simple remote control" ---- - -{% include untranslated.html %} -### The Basics - -@I2Pcontrol is a [JSONRPC2](https://en.wikipedia.org/wiki/JSON-RPC) [API](https://en.wikipedia.org/wiki/Application_programming_interface) for @Kovri and @Java-I2P which allows an @I2PControl client to remote control/monitor a running instance. - -Two available @I2PControl clients are: [qtoopie](https://github.com/EinMByte/qtoopie) (C++ client) and [itoopie](https://github.com/i2p/i2p.itoopie) (Java client). Read `kovri.conf` to configure @I2PControl for @Kovri. - -### In-depth information - -Details and specification available on the [I2PControl](https://geti2p.net/en/docs/api/i2pcontrol) page. diff --git a/_i18n/ar/resources/moneropedia/in-net.md b/_i18n/ar/resources/moneropedia/in-net.md deleted file mode 100644 index ec3c5c8a..00000000 --- a/_i18n/ar/resources/moneropedia/in-net.md +++ /dev/null @@ -1,14 +0,0 @@ ---- -tags: ["kovri"] -terms: ["In-net"] -summary: "Within the I2P network" ---- - -{% include untranslated.html %} -### The Basics - -**In-net** is a [colloquial](https://en.wikipedia.org/wiki/Colloquial) term of which describes activities, protocols, or functionality that exist *only* within the @I2P network. - -### In-depth information - -Example: *in-net download* would be defined as downloading *only* within @I2P. diff --git a/_i18n/ar/resources/moneropedia/java-i2p.md b/_i18n/ar/resources/moneropedia/java-i2p.md deleted file mode 100644 index 8a21da5d..00000000 --- a/_i18n/ar/resources/moneropedia/java-i2p.md +++ /dev/null @@ -1,14 +0,0 @@ ---- -tags: ["kovri"] -terms: ["Java-I2P"] -summary: "The original implementation of I2P - written in Java" ---- - -{% include untranslated.html %} -### The Basics - -The term "Java I2P" is often used to describe the original @I2P implementation currently most known and used today. There are various other @I2P implementations, including @Kovri; all of which look up to the original Java implementation. - -### Notes - -To download/learn more about the Java implementation, visit their [website](https://geti2p.net/). diff --git a/_i18n/ar/resources/moneropedia/jump-service.md b/_i18n/ar/resources/moneropedia/jump-service.md deleted file mode 100644 index a62c5276..00000000 --- a/_i18n/ar/resources/moneropedia/jump-service.md +++ /dev/null @@ -1,33 +0,0 @@ ---- -tags: ["kovri"] -terms: ["Jump-Service"] -summary: "An I2P website service that adds addresses to your address book" ---- - -{% include untranslated.html %} -### The Basics - -In your @I2P configured web browser, you can use a Jump Service to *jump* to an @I2P address that you don't have in your @address-book. Once you've *jumped* to the address, the address will be saved into your @address-book. - -### In-depth Information - -In an @I2P configured browser, visit: http://stats.i2p/i2p/lookup.html (courtesy of @Java-I2P's lead developer *zzz*) - -Then, you'll have two options: - -1. *Hostname lookup* the address you wish to visit and then manually copy/paste the result -2. *Jump* to the @I2P website by entering the @I2P hostname (**recommended**) - -### Using hostname lookup - -For example, entering `pinkpaste.i2p` into the *Hostname lookup* box (and then submitting) will return: - -``` -pinkpaste.i2p=m-HrPrIAsdxts0WM~P4mE8mt9P7g-QTaBvu7Gc6Nl0UX7Vwck-i~RvOPfK6W~kfdRvwhNTqevkBL2UF5l36We02Aiywu7kB2xOHRkze68h-Tg2ewvRVwokohguCD2G3wwAEz~7FVda2avYDCb9-N6TfuzxKLnmhPMvbNSjGL7ZsD2p-h207R3-2kvuMV9bfu-K~w9NI9XJhIyufvUnFYc2jnTVg8PbaR4UP57cNaOO2YIMPkbr6~yTcIu9B1sUfHK6-N~6virQDOxW4M-62rjnZkLpaCtkOsXslmCwZI--TkZ6hKi1kXZvNmJRE1rYfffYRFn38zhaqszeETX8HiIvahZhXF5fNumBziYdmLdw8hkuN1A~emU6Xz9g~a1Ixfsq1Qr~guYoOtaw-0rOFxNRS9yMehE-2LCb8c-cAg6z5OdlN4qJDl~ZHgru4d~EHp~BpAK3v7u2Gi-8l1ygVW-1CHVna~fwnbOPN3ANPwh6~~yUit0Cx1f54XiNRn6-nPBQAEAAcAAA== -``` - -Copy/paste this host=@base64-address pairing into your **private** @subscription. - -### Directly jumping - -For example, entering `pinkpaste.i2p` into the *Jump* box (and then submitting) will automatically redirect you to the website **and** insert the @locally-unique-host into @address-book. diff --git a/_i18n/ar/resources/moneropedia/lease-set.md b/_i18n/ar/resources/moneropedia/lease-set.md deleted file mode 100644 index 412f2005..00000000 --- a/_i18n/ar/resources/moneropedia/lease-set.md +++ /dev/null @@ -1,24 +0,0 @@ ---- -tags: ["kovri"] -terms: ["LeaseSet", "LeaseSets"] -summary: "Contains all currently authorized Leases for a particular I2P Destination" ---- - -{% include untranslated.html %} -### The Basics - -A Lease-Set contains a set of authorized @leases (and other related information) for a particular @destination. - -### In-depth information - -A Lease-Set contains: - -- all of the currently authorized @leases for a particular @destination -- the public key to which garlic messages can be encrypted (see @garlic-routing) -- the signing public key that can be used to revoke this particular version of the structure - -The Lease-Set is one of the two structures stored in the @network-database (the other being @router-info), and is keyed under the SHA256 of the contained @destination. - -### Notes - -For further details, read @Java-I2P's [LeaseSet](https://geti2p.net/en/docs/how/network-database#leaseSet) diff --git a/_i18n/ar/resources/moneropedia/lease.md b/_i18n/ar/resources/moneropedia/lease.md deleted file mode 100644 index cfb13659..00000000 --- a/_i18n/ar/resources/moneropedia/lease.md +++ /dev/null @@ -1,14 +0,0 @@ ---- -tags: ["kovri"] -terms: ["Lease", "Leases"] -summary: "Authorizes an I2P tunnel to receive messages targeting a destination" ---- - -{% include untranslated.html %} -### The Basics - -A lease defines the authorization for a particular @I2P @tunnel to receive a @messages targeting a @destination. - -### In-depth information - -For further details, read @Java-I2P's [Lease](https://geti2p.net/spec/common-structures#lease) diff --git a/_i18n/ar/resources/moneropedia/message.md b/_i18n/ar/resources/moneropedia/message.md deleted file mode 100644 index 975277a3..00000000 --- a/_i18n/ar/resources/moneropedia/message.md +++ /dev/null @@ -1,32 +0,0 @@ ---- -tags: ["kovri"] -terms: ["Message", "Messages"] -summary: "The mechanisms in which information travels within I2P" ---- - -{% include untranslated.html %} -### The Basics - -*Messages* (which exist on top of the @transports layer), contain varying types of information that are needed for the network but, most importantly, everything you see, do, send, or receive, will come and go in the form of *messages*. - -There are 2 essential types of *messages* in @I2P: - -- @Tunnel messages -- @I2NP messages - -Essentially: *@tunnel messages* **contain** @I2NP **message fragments** which are then [reassembled](https://geti2p.net/en/docs/tunnels/implementation) at certain points within a @tunnel's path. - -### In-depth information - -@I2NP messages have a close relationship with @tunnel @messages so it is easy to get the term *messages* confused when reading @Java-I2P specifications: - -> -1. First, the tunnel gateway accumulates a number of I2NP messages and preprocesses them into tunnel messages for delivery. -2. Next, that gateway encrypts that preprocessed data, then forwards it to the first hop. -3. That peer, and subsequent tunnel participants, unwrap a layer of the encryption, verifying that it isn't a duplicate, then forward it on to the next peer. -4. Eventually, the tunnel messages arrive at the endpoint where the I2NP messages originally bundled by the gateway are reassembled and forwarded on as requested. - -### Notes - -- @I2NP @messages need to be fragmented because they are variable in size (from 0 to almost 64 KB) and @tunnel @messages are fixed-size (approximately 1 KB). -- For details and specifications, visit the [I2NP spec](https://geti2p.net/spec/i2np) and [Tunnel Message spec](https://geti2p.net/spec/tunnel-message) diff --git a/_i18n/ar/resources/moneropedia/network-database.md b/_i18n/ar/resources/moneropedia/network-database.md deleted file mode 100644 index ac94231a..00000000 --- a/_i18n/ar/resources/moneropedia/network-database.md +++ /dev/null @@ -1,24 +0,0 @@ ---- -tags: ["kovri"] -terms: ["Network-Database"] -summary: "A distributed database which contains needed router information so the network can stay intact" ---- - -{% include untranslated.html %} -### The Basics - -@network-database is a [distributed database](https://en.wikipedia.org/wiki/Distributed_database) which contains router information that peers must use so the network can stay intact. - -### In-depth information - -From @Java-I2P: - -> -@I2P's @network-database is a specialized distributed database, containing just two types of data - router contact information (@Router-Infos) and @destination contact information (@LeaseSets). Each piece of data is signed by the appropriate party and verified by anyone who uses or stores it. In addition, the data has liveliness information within it, allowing irrelevant entries to be dropped, newer entries to replace older ones, and protection against certain classes of attack. - -> -The @network-database is distributed with a simple technique called "@floodfill", where a subset of all routers, called "@floodfill routers", maintains the distributed database. - -### Notes - -Read [Network-Database](https://geti2p.net/en/docs/how/network-database) for details. diff --git a/_i18n/ar/resources/moneropedia/ntcp.md b/_i18n/ar/resources/moneropedia/ntcp.md deleted file mode 100644 index 4c3f68b2..00000000 --- a/_i18n/ar/resources/moneropedia/ntcp.md +++ /dev/null @@ -1,33 +0,0 @@ ---- -tags: ["kovri"] -terms: ["NTCP"] -summary: "NIO-Based TCP (Non-blocking I/O based TCP): one of two Kovri transports" ---- - -{% include untranslated.html %} -### The Basics - -*NIO-Based TCP (Non-blocking I/O based TCP)* is one of two encrypted @transports for @Kovri. - -Similar to @SSU, @NTCP's *primary* purpose is to securely transmit @in-net @I2NP messages through @tunnels but, unlike @SSU, @NTCP functions solely over encrypted [TCP](https://en.wikipedia.org/wiki/Transmission_Control_Protocol). - -### In-depth information - - - Passes along individual @I2NP messages (both Standard and Time Sync) after: - - TCP has been established - - Establishment Sequence has been completed - - Uses the following @encryption: - - 2048-bit [Diffie-Hellman](https://en.wikipedia.org/wiki/Diffie-hellman) - - [AES-256](https://en.wikipedia.org/wiki/Advanced_Encryption_Standard)/[CBC](https://en.wikipedia.org/wiki/Block_cipher_modes_of_operation) - - Establishment Sequence has the following *states*: - - Pre-establishment - - Establishment - - Post-establishment or "Established" - - Uses the following from the @network-database: - - Transport name: NTCP - - Host: IP (IPv4 or IPv6) or host name (shortened IPv6 address (with "::") is allowed) - - Port: 1024 - 65535 - -### Notes - -For further details, read @Java-I2P's [NTCP](https://geti2p.net/en/docs/transport/ntcp) diff --git a/_i18n/ar/resources/moneropedia/reseed.md b/_i18n/ar/resources/moneropedia/reseed.md deleted file mode 100644 index 179f34c5..00000000 --- a/_i18n/ar/resources/moneropedia/reseed.md +++ /dev/null @@ -1,16 +0,0 @@ ---- -tags: ["kovri"] -terms: ["Reseed"] -summary: "The method of which Kovri uses to bootstrap into the I2P network" ---- - -{% include untranslated.html %} -### The Basics - -When you start @Kovri for the first time (or if it's been offline for a long time), @Kovri will need a list of peers to connect to so it can [bootstrap](https://en.wikipedia.org/wiki/Bootstrap) into the @I2P network. @Kovri gets these peers from a special file stored on a reseed server. On this file are all the various pieces of information @Kovri needs in order to connect with @I2P peers. - -### In-depth information - -@Kovri has a list of [hard-coded](https://en.wikipedia.org/wiki/Hard-coded) reseed servers available to fetch from. These servers securely serve an [SU3](https://geti2p.net/spec/updates#su3) file (signed with a cryptographic @signature) over @clearnet with [HTTPS](https://en.wikipedia.org/wiki/HTTPS). This SU3 file contains information that's used to verify both the integrity of the file and its content. - -Aside from the technical elements needed to verify and process the file, the file's main contents consist of a series of @router-info files which @Kovri and @I2P routers use to locate and communicate with other @I2P peers. These peers are then stored into a @network-database. diff --git a/_i18n/ar/resources/moneropedia/router-info.md b/_i18n/ar/resources/moneropedia/router-info.md deleted file mode 100644 index cb190f9d..00000000 --- a/_i18n/ar/resources/moneropedia/router-info.md +++ /dev/null @@ -1,67 +0,0 @@ ---- -tags: ["kovri"] -terms: ["Router-Info", "Router-infos"] -summary: "A data structure or file which contains an I2P peer's needed network information" ---- - -{% include untranslated.html %} -### The Basics - -@Router-Info is a data structure (periodically written to a [binary file](https://en.wikipedia.org/wiki/Binary_file)) which contains all needed information to locate, identify, and communicate with an @I2P peer. @Router-Info includes IP address, router identity, other misc. technical details; is needed for @network-database and is published to @floodfill routers. - -### In-depth information - -In human-readable form, Router-Info may look like this: - -``` -Identity: [RouterIdentity: -Hash: nYZ5Qe7gQ-~QgfgJVRUG4c0JnVeVqzM~duUX1EGT1ek= -Certificate: [Certificate: type: Key certificate -Crypto type: 0 -Sig type: 7 (EdDSA_SHA512_Ed25519)] -PublicKey: [PublicKey: size: 256] -SigningPublicKey: [SigningPublicKey EdDSA_SHA512_Ed25519: size: 32] -Padding: 96 bytes] -Signature: [Signature EdDSA_SHA512_Ed25519: size: 64] -Published: Sun Oct 09 01:34:59 UTC 2016 -Options (5): - [caps] = [LfR] - [netId] = [2] - [netdb.knownLeaseSets] = [37] - [netdb.knownRouters] = [2435] - [router.version] = [0.9.26] -Addresses (4): -[RouterAddress: -Type: SSU -Cost: 4 -Options (5): - [caps] = [BC] - [host] = [2a01:e35:8b5c:b240:71a2:6750:8d4:47fa] - [key] = [nYZ5Qe7gQ-~QgfgJVRUG4c0JnVeVqzM~duUX1EGT1ek=] - [mtu] = [1472] - [port] = [22244]] -[RouterAddress: -Type: NTCP -Cost: 9 -Options (2): - [host] = [2a01:e35:8b5c:b240:71a2:6750:8d4:47fa] - [port] = [22244]] -[RouterAddress: -Type: SSU -Cost: 6 -Options (4): - [caps] = [BC] - [host] = [88.181.203.36] - [key] = [nYZ5Qe7gQ-~QgfgJVRUG4c0JnVeVqzM~duUX1EGT1ek=] - [port] = [22244]] -[RouterAddress: -Type: NTCP -Cost: 11 -Options (2): - [host] = [88.181.203.36] - [port] = [22244]]] -``` - -### Notes - -For details and specification, visit @Java-I2P [Network Database](https://geti2p.net/en/docs/how/network-database) page. diff --git a/_i18n/ar/resources/moneropedia/ssu.md b/_i18n/ar/resources/moneropedia/ssu.md deleted file mode 100644 index cbdadfdc..00000000 --- a/_i18n/ar/resources/moneropedia/ssu.md +++ /dev/null @@ -1,25 +0,0 @@ ---- -tags: ["kovri"] -terms: ["SSU"] -summary: "Secure Semi-reliable UDP: one of two Kovri transports" ---- - -{% include untranslated.html %} -### The Basics - -*Secure Semi-reliable UDP* is one of two encrypted @transports for @Kovri. - -Similar to @NTCP, @SSU's *primary* purpose is to securely transmit @in-net @I2NP messages through @tunnels but, unlike @NTCP, @SSU functions solely over encrypted [UDP](https://en.wikipedia.org/wiki/User_Datagram_Protocol). - -### In-depth information - -- Like @NTCP, @SSU is a connection-oriented, point-to-point data transport -- Termed *semi-reliable* because @SSU will repeatedly retransmit *unacknowledged* messages (up to maximum number then dropped) -- @SSU also provides several unique services (in addition to its function as a @transport layer): - - IP detection (local inspection or with [peer testing](https://geti2p.net/en/docs/transport/ssu#peerTesting)) - - [NAT](https://en.wikipedia.org/wiki/Network_address_translation) traversal (using [introducers](https://geti2p.net/en/docs/transport/ssu#introduction)) - - [Firewall](https://en.wikipedia.org/wiki/Firewall_%28computing%29) status and, if implemented, @SSU can notify @NTCP if the external address or firewall status changes - -### Notes - -For further details, read @Java-I2P's [SSU](https://geti2p.net/en/docs/transport/ssu) diff --git a/_i18n/ar/resources/moneropedia/subscription.md b/_i18n/ar/resources/moneropedia/subscription.md deleted file mode 100644 index 9396fba4..00000000 --- a/_i18n/ar/resources/moneropedia/subscription.md +++ /dev/null @@ -1,46 +0,0 @@ ---- -tags: ["kovri"] -terms: ["Subscription"] -summary: "A file used by address book which contains I2P hosts paired with I2P destinations" ---- - -{% include untranslated.html %} -### The Basics - -A subscription is a file which contains a list of `.i2p` hosts paired with their respective @destination. Subscriptions are used by the @address-book. - -### In-depth information - -Similar to how a [hosts file](https://en.wikipedia.org/wiki/Hosts_(file)) can map an Internet hostname to a specified address, a subscription matches a `.i2p` address to @base64-address by using the following format (no spaces allowed): `host=address` - -More specifically, a subscription pairs a @locally-unique-host to @base64-address. - -Example: - -``` -anonimal.i2p=AQZGLAMpI9Q0l0kmMj1vpJJYK3CjLp~fE3MfvE-e7KMKjI5cPOH6EN8m794uHJ6b09qM8mb9VEv1lVLEov~usVliTSXCSHuRBOCIwIOuDNU0AbVa4BpIx~2sU4TxKhoaA3zQ6VzINoduTdR2IJhPvI5xzezp7dR21CEQGGTbenDslXeQ4iLHFA2~bzp1f7etSl9T2W9RID-KH78sRQmzWnv7dbhNodMbpO6xsf1vENf6bMRzqD5vgHEHZu2aSoNuPyYxDU1eM6--61b2xp9mt1k3ud-5WvPVg89RaU9ugU5cxaHgR927lHMCAEU2Ax~zUb3DbrvgQBOTHnJEx2Fp7pOK~PnP6ylkYKQMfLROosLDXinxOoSKP0UYCh2WgIUPwE7WzJH3PiJVF0~WZ1dZ9mg00c~gzLgmkOxe1NpFRNg6XzoARivNVB5NuWqNxr5WKWMLBGQ9YHvHO1OHhUJTowb9X90BhtHnLK2AHwO6fV-iHWxRJyDabhSMj1kuYpVUBQAEAAcAAA== -``` - -1. `anonimal.i2p` is the @locally-unique-host -2. `=` is the separator -3. Everything that remains is the @base64-address - -### Subscription types - -For @Kovri, there are two types of subscription files: *public* and *private*. - -A *public* subscription: -- is used when bootstrapping to use essential services (IRC, email, Monero, etc.) -- is static and is refreshed every 12 hours from Monero's @address-book server -- allows you to safely share the subscription with everyone as it is publically available (anyone who shares the same public subscription will also be able to resolve the same hostname to the same destination as you) - -A *private* subscription: -- is used exclusively by you and is not shared with others unless you explicitly choose to share the file -- default file is `private_hosts.txt` in your @data-directory - -### Updating a private subscription - -You can use a @jump-service to manually update your private subscription. The updated subscription will then be fed into the @address-book for you to use. - -### Notes -To learn how to subscribe to multiple subscriptions, see the [user-guide](https://gitlab.com/kovri-project/kovri-docs/blob/master/i18n/en/user_guide.md). diff --git a/_i18n/ar/resources/moneropedia/transports.md b/_i18n/ar/resources/moneropedia/transports.md deleted file mode 100644 index b1471cd6..00000000 --- a/_i18n/ar/resources/moneropedia/transports.md +++ /dev/null @@ -1,19 +0,0 @@ ---- -tags: ["kovri"] -terms: ["Transports", "Transport"] -summary: "The two encrypted transport layers for Kovri" ---- - -{% include untranslated.html %} -### The Basics - -@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 - -@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 @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) diff --git a/_i18n/ar/resources/moneropedia/tunnel.md b/_i18n/ar/resources/moneropedia/tunnel.md deleted file mode 100644 index a9ebfaaa..00000000 --- a/_i18n/ar/resources/moneropedia/tunnel.md +++ /dev/null @@ -1,36 +0,0 @@ ---- -tags: ["kovri"] -terms: ["Tunnel", "Tunnels"] -summary: "Uni-directional virtual paths that pass messages through a defined sequence of I2P routers" ---- - -{% include untranslated.html %} -### The Basics - -When you communicate over @I2P (visit an @eepsite / use a @garlic-service), you'll first need to connect to a peer by using @transports and then build virtual *tunnels*. These virtual tunnels are temporary, uni-directional paths that pass information through a defined sequence of @I2P routers to your @destination. Tunnels are built, and then used, with layered @garlic-encryption and are a general-purpose mechanism to transport all @I2NP @messages. - -Each peer builds, at a minimum, *two* uni-directional tunnels: one for **outbound traffic**, and one for **inbound traffic**. These tunnels are classified as either **inbound tunnels** (where @messages come toward the creator of the tunnel) or **outbound tunnels** (where the tunnel creator sends @messages away from the creator of the tunnel). Thus, *four* tunnels are required for a single round-trip @message and reply to your @destination (two for your, two for your destination). - -### In-depth information - -From @Java-I2P: - -> -Within I2P, @messages are passed in one direction through a virtual tunnel of peers, using whatever means are available to pass the @message on to the next hop. Messages arrive at the tunnel's gateway, get bundled up and/or fragmented into fixed-size @tunnel @messages, and are forwarded on to the next hop in the tunnel, which processes and verifies the validity of the @message and sends it on to the next hop, and so on, until it reaches the @tunnel endpoint. That endpoint takes the messages bundled up by the gateway and forwards them as instructed - either to another router, to another tunnel on another router, or locally. - -> -Tunnels all work the same, but can be segmented into two different groups - inbound tunnels and outbound tunnels. The inbound tunnels have an untrusted gateway which passes messages down towards the tunnel creator, which serves as the tunnel endpoint. For outbound tunnels, the tunnel creator serves as the gateway, passing messages out to the remote endpoint. - -> -The tunnel's creator selects exactly which peers will participate in the tunnel, and provides each with the necessary configuration data. They may have any number of hops. It is the intent to make it hard for either participants or third parties to determine the length of a tunnel, or even for colluding participants to determine whether they are a part of the same tunnel at all (barring the situation where colluding peers are next to each other in the tunnel). - -### Notes - -From @Java-I2P: - -> -@I2P is an inherently packet switched network, even with these tunnels, allowing it to take advantage of multiple tunnels running in parallel, increasing resilience and balancing load. Even though the tunnels within I2P bear a resemblance to a circuit switched network, everything within I2P is strictly message based - tunnels are merely accounting tricks to help organize the delivery of messages. No assumptions are made regarding reliability or ordering of messages, and retransmissions are left to higher levels (e.g. I2P's client layer streaming library). - -### Documentation - -For specification and detailed documentation, visit the [Tunnel-Routing](https://geti2p.net/en/docs/how/tunnel-routing) and [Tunnel-Implementation](https://geti2p.net/en/docs/tunnels/implementation) page. diff --git a/_i18n/de/resources/moneropedia/base32-address.md b/_i18n/de/resources/moneropedia/base32-address.md deleted file mode 100644 index 0e3a88e2..00000000 --- a/_i18n/de/resources/moneropedia/base32-address.md +++ /dev/null @@ -1,26 +0,0 @@ ---- -tags: ["kovri"] -terms: ["Base32-address", "Base32-addresses"] -summary: "Base32 encoded hash of a Base64 address" ---- - -{% include untranslated.html %} -### The Basics - -A Base32 address is a shortened, encoded version of an @I2P address. The Base32 address is the first part in a `.b32.i2p` hostname. - -Example: - -`i35yftyyb22xhcvghmev46t5knefur5v66qzekkajatwfwhyklvq.b32.i2p` - -where - -`i35yftyyb22xhcvghmev46t5knefur5v66qzekkajatwfwhyklvq` is the Base32 address. - -### In-depth Information - -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. - -### Notes - -**Note: `.b32` is not a sub-domain of `.i2p`** diff --git a/_i18n/de/resources/moneropedia/base64-address.md b/_i18n/de/resources/moneropedia/base64-address.md deleted file mode 100644 index b9985658..00000000 --- a/_i18n/de/resources/moneropedia/base64-address.md +++ /dev/null @@ -1,21 +0,0 @@ ---- -tags: ["kovri"] -terms: ["Base64-address", "Base64-addresses"] -summary: "Base64 encoded I2P destination" ---- - -{% include untranslated.html %} -### The Basics - -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: - -``` -AQZGLAMpI9Q0l0kmMj1vpJJYK3CjLp~fE3MfvE-e7KMKjI5cPOH6EN8m794uHJ6b09qM8mb9VEv1lVLEov~usVliTSXCSHuRBOCIwIOuDNU0AbVa4BpIx~2sU4TxKhoaA3zQ6VzINoduTdR2IJhPvI5xzezp7dR21CEQGGTbenDslXeQ4iLHFA2~bzp1f7etSl9T2W9RID-KH78sRQmzWnv7dbhNodMbpO6xsf1vENf6bMRzqD5vgHEHZu2aSoNuPyYxDU1eM6--61b2xp9mt1k3ud-5WvPVg89RaU9ugU5cxaHgR927lHMCAEU2Ax~zUb3DbrvgQBOTHnJEx2Fp7pOK~PnP6ylkYKQMfLROosLDXinxOoSKP0UYCh2WgIUPwE7WzJH3PiJVF0~WZ1dZ9mg00c~gzLgmkOxe1NpFRNg6XzoARivNVB5NuWqNxr5WKWMLBGQ9YHvHO1OHhUJTowb9X90BhtHnLK2AHwO6fV-iHWxRJyDabhSMj1kuYpVUBQAEAAcAAA== -``` - - -### In-depth Information - -See @destination for details behind @base64-address diff --git a/_i18n/de/resources/moneropedia/data-directory.md b/_i18n/de/resources/moneropedia/data-directory.md deleted file mode 100644 index 761cfd46..00000000 --- a/_i18n/de/resources/moneropedia/data-directory.md +++ /dev/null @@ -1,21 +0,0 @@ ---- -tags: ["kovri"] -terms: ["Data-Directory"] -summary: "Where essential kovri data for runtime is stored" ---- - -{% include untranslated.html %} -### The Basics - -Depending on your OS, @Kovri currently stores all run-time data in the following directory: - -- Linux/FreeBSD: - - `$HOME/.kovri` - -- OSX: - - `$HOME/Library/Application\ Support/Kovri` - -- Windows: - - `"$APPDATA"\\Kovri` - -This includes all configuration files, @address-book, certificates, and resources. diff --git a/_i18n/de/resources/moneropedia/eepsite.md b/_i18n/de/resources/moneropedia/eepsite.md deleted file mode 100644 index cd450d97..00000000 --- a/_i18n/de/resources/moneropedia/eepsite.md +++ /dev/null @@ -1,29 +0,0 @@ ---- -tags: ["kovri"] -terms: ["Eepsite", "Hidden-Service", "Garlic-Site", "Garlic-Service"] -summary: "A website or service hosted within the I2P network" ---- - -{% include untranslated.html %} -### The Basics - -Is it [**EEP!** *(in response to the site's content)*](https://en.wikipedia.org/wiki/Onomatopoeia), or **end-to-end protocol**, or something else entirely different? - -While the original definition of eepsite has been lost with time, its use-case remains: an eepsite is a website or service that is hosted within (and only accessible by) the @I2P network. - -### In-depth Information - -Alternate names include: - -1. *Hidden Service* - - because the site/service is *hidden* within the @I2P network and can only be visited within the network -2. *Garlic Site* - - because the website utilizes @I2P's @garlic-routing technology as a means of communicating with a client - - because the service is hosted as a website and not any other type of service -3. *Garlic Service* - - because the service utilizes @I2P's @garlic-routing technology as a means of communicating with a client - - because the service is specific to services like IRC, email, or a Monero peer (but may also include websites) - -### Notes - -To learn how to setup an Eepsite (Hidden Service, Garlic Site, Garlic Service) visit the @Kovri [user-guide](https://gitlab.com/kovri-project/kovri-docs/blob/master/i18n/en/user_guide.md). diff --git a/_i18n/de/resources/moneropedia/floodfill.md b/_i18n/de/resources/moneropedia/floodfill.md deleted file mode 100644 index cccd9011..00000000 --- a/_i18n/de/resources/moneropedia/floodfill.md +++ /dev/null @@ -1,14 +0,0 @@ ---- -tags: ["kovri"] -terms: ["Floodfill"] -summary: "An I2P router which maintains a distributed network-database" ---- - -{% include untranslated.html %} -### The Basics - -By actively managing a distributed network-database, a router with *floodfill* capability has the ability to help maintain network stability and resiliancy while also being decentralized and trust-less. - -### In-depth information - -Though floodfill itself is a simple storage system, the technical underpinnings of floodfill as it relates to @network-database and other protocols within @I2P are much more complex. Visit the [Network Database](https://geti2p.net/en/docs/how/network-database) page for details. diff --git a/_i18n/de/resources/moneropedia/garlic-encryption.md b/_i18n/de/resources/moneropedia/garlic-encryption.md deleted file mode 100644 index a0548b3c..00000000 --- a/_i18n/de/resources/moneropedia/garlic-encryption.md +++ /dev/null @@ -1,24 +0,0 @@ ---- -tags: ["kovri"] -terms: ["Garlic-Encryption", "Layered-Encryption"] -summary: "Layered encryption as implemented in Kovri / I2P" ---- - -{% include untranslated.html %} -### The Basics - -@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 - -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. diff --git a/_i18n/de/resources/moneropedia/garlic-routing.md b/_i18n/de/resources/moneropedia/garlic-routing.md deleted file mode 100644 index 4a1d26b9..00000000 --- a/_i18n/de/resources/moneropedia/garlic-routing.md +++ /dev/null @@ -1,44 +0,0 @@ ---- -tags: ["kovri"] -terms: ["Garlic-Routing"] -summary: "Routing technology as implemented in Kovri" ---- - -{% include untranslated.html %} -### 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. - -The @Garlic-Encryption of @Garlic-Routing is similar to the @Layered-Encryption of [Onion Routing](https://en.wikipedia.org/wiki/Onion_routing) and effectively conceals the IP address of the sender and secures information sent from the sender to its @destination (and vice-versa). - -### 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](http://www.freehaven.net/papers.html) (Section 8.1.1) as derived from the term Onion Routing. - -As recent as October of 2016, [#tor-dev](https://oftc.net/WebChat/) has offered insight into the creation of the term *@garlic-routing*: - -[Nick Mathewson](https://en.wikipedia.org/wiki/The_Tor_Project,_Inc): ->[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](https://en.wikipedia.org/wiki/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 was 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 (similar to the @layered-encryption in Onion Routing) -- Bundling multiple @messages together (garlic cloves) -- ElGamal/AES @encryption - -*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 - -- In terms of Onion/Garlic Routing, another way to envision layered @encryption is by replacing the onion/garlic with a [Matryoshka doll](https://en.wikipedia.org/wiki/Matryoshka_doll) - with each outer/inner doll having a lock and public key to the next/previous doll -- For more technical details on Garlic Routing, read the @Java-I2P entry on [Garlic Routing](https://geti2p.net/en/docs/how/garlic-routing) diff --git a/_i18n/de/resources/moneropedia/i2np.md b/_i18n/de/resources/moneropedia/i2np.md deleted file mode 100644 index 1e7841ae..00000000 --- a/_i18n/de/resources/moneropedia/i2np.md +++ /dev/null @@ -1,27 +0,0 @@ ---- -tags: ["kovri"] -terms: ["I2NP"] -summary: "The I2P Network Protocol: the mechanism in which I2NP messages are sent over the I2P network" ---- - -{% include untranslated.html %} -### The Basics - -From @Java-I2P: - -> -@I2NP manages the routing and mixing of messages between routers, as well as the selection of what transports to use when communicating with a peer for which there are multiple common transports supported - -### In-depth information - -From @Java-I2P: - -> -@I2NP (@I2P Network Protocol) @messages can be used for one-hop, router-to-router, point-to-point @messages. By @encrypting and wrapping @messages in other @messages, they can be sent in a secure way through multiple hops to the ultimate @destination. @I2NP does not specify nor require any particular @transport layer but does require at least one @transport in use. - -> -Whenever a @destination wants to send a message to to another @destination, it provides its local router with both the @destination structure and the raw bytes of the message to be sent. The router then determines where to send it, delivers it through outbound @tunnels, instructing the end point to pass it along to the appropriate inbound @tunnel, where it is passed along again to that @tunnel's end point and made available to the target for reception. - -### Notes - -Read more about the @I2NP [protocol](https://geti2p.net/en/docs/protocol/i2np) and [specification](https://geti2p.net/spec/i2np). diff --git a/_i18n/de/resources/moneropedia/i2p.md b/_i18n/de/resources/moneropedia/i2p.md deleted file mode 100644 index 7a6980c3..00000000 --- a/_i18n/de/resources/moneropedia/i2p.md +++ /dev/null @@ -1,30 +0,0 @@ ---- -tags: ["kovri"] -terms: ["I2P"] -summary: "The Invisible Internet Project: an anonymizing overlay network" ---- - -{% include untranslated.html %} -### Monero - -For Monero's implementation of @I2P, see @Kovri. For a comparison of @I2P to [Tor](https://torproject.org/), read the [Comparison](https://geti2p.net/en/comparison/tor) page. - -### The Basics - -From @Java-I2P: - ->The I2P network provides strong privacy protections for communication over the Internet. Many activities that would risk your privacy on the public Internet can be conducted anonymously inside I2P. - -### In-depth information - -From @Java-I2P: - ->I2P is an anonymous overlay network - a network within a network. It is intended to protect communication from dragnet surveillance and monitoring by third parties such as ISPs. - ->I2P is used by many people who care about their privacy: activists, oppressed people, journalists and whistleblowers, as well as the average person. - ->No network can be "perfectly anonymous". The continued goal of I2P is to make attacks more and more difficult to mount. Its anonymity will get stronger as the size of the network increases and with ongoing academic review. - -### Notes - -@I2P documentation and specifications are available [here](https://geti2p.net/docs/). diff --git a/_i18n/de/resources/moneropedia/i2pcontrol.md b/_i18n/de/resources/moneropedia/i2pcontrol.md deleted file mode 100644 index b419423c..00000000 --- a/_i18n/de/resources/moneropedia/i2pcontrol.md +++ /dev/null @@ -1,16 +0,0 @@ ---- -tags: ["kovri"] -terms: ["I2PControl"] -summary: "An API inteface for Kovri and Java-I2P that allows simple remote control" ---- - -{% include untranslated.html %} -### The Basics - -@I2Pcontrol is a [JSONRPC2](https://en.wikipedia.org/wiki/JSON-RPC) [API](https://en.wikipedia.org/wiki/Application_programming_interface) for @Kovri and @Java-I2P which allows an @I2PControl client to remote control/monitor a running instance. - -Two available @I2PControl clients are: [qtoopie](https://github.com/EinMByte/qtoopie) (C++ client) and [itoopie](https://github.com/i2p/i2p.itoopie) (Java client). Read `kovri.conf` to configure @I2PControl for @Kovri. - -### In-depth information - -Details and specification available on the [I2PControl](https://geti2p.net/en/docs/api/i2pcontrol) page. diff --git a/_i18n/de/resources/moneropedia/in-net.md b/_i18n/de/resources/moneropedia/in-net.md deleted file mode 100644 index ec3c5c8a..00000000 --- a/_i18n/de/resources/moneropedia/in-net.md +++ /dev/null @@ -1,14 +0,0 @@ ---- -tags: ["kovri"] -terms: ["In-net"] -summary: "Within the I2P network" ---- - -{% include untranslated.html %} -### The Basics - -**In-net** is a [colloquial](https://en.wikipedia.org/wiki/Colloquial) term of which describes activities, protocols, or functionality that exist *only* within the @I2P network. - -### In-depth information - -Example: *in-net download* would be defined as downloading *only* within @I2P. diff --git a/_i18n/de/resources/moneropedia/java-i2p.md b/_i18n/de/resources/moneropedia/java-i2p.md deleted file mode 100644 index 8a21da5d..00000000 --- a/_i18n/de/resources/moneropedia/java-i2p.md +++ /dev/null @@ -1,14 +0,0 @@ ---- -tags: ["kovri"] -terms: ["Java-I2P"] -summary: "The original implementation of I2P - written in Java" ---- - -{% include untranslated.html %} -### The Basics - -The term "Java I2P" is often used to describe the original @I2P implementation currently most known and used today. There are various other @I2P implementations, including @Kovri; all of which look up to the original Java implementation. - -### Notes - -To download/learn more about the Java implementation, visit their [website](https://geti2p.net/). diff --git a/_i18n/de/resources/moneropedia/jump-service.md b/_i18n/de/resources/moneropedia/jump-service.md deleted file mode 100644 index a62c5276..00000000 --- a/_i18n/de/resources/moneropedia/jump-service.md +++ /dev/null @@ -1,33 +0,0 @@ ---- -tags: ["kovri"] -terms: ["Jump-Service"] -summary: "An I2P website service that adds addresses to your address book" ---- - -{% include untranslated.html %} -### The Basics - -In your @I2P configured web browser, you can use a Jump Service to *jump* to an @I2P address that you don't have in your @address-book. Once you've *jumped* to the address, the address will be saved into your @address-book. - -### In-depth Information - -In an @I2P configured browser, visit: http://stats.i2p/i2p/lookup.html (courtesy of @Java-I2P's lead developer *zzz*) - -Then, you'll have two options: - -1. *Hostname lookup* the address you wish to visit and then manually copy/paste the result -2. *Jump* to the @I2P website by entering the @I2P hostname (**recommended**) - -### Using hostname lookup - -For example, entering `pinkpaste.i2p` into the *Hostname lookup* box (and then submitting) will return: - -``` -pinkpaste.i2p=m-HrPrIAsdxts0WM~P4mE8mt9P7g-QTaBvu7Gc6Nl0UX7Vwck-i~RvOPfK6W~kfdRvwhNTqevkBL2UF5l36We02Aiywu7kB2xOHRkze68h-Tg2ewvRVwokohguCD2G3wwAEz~7FVda2avYDCb9-N6TfuzxKLnmhPMvbNSjGL7ZsD2p-h207R3-2kvuMV9bfu-K~w9NI9XJhIyufvUnFYc2jnTVg8PbaR4UP57cNaOO2YIMPkbr6~yTcIu9B1sUfHK6-N~6virQDOxW4M-62rjnZkLpaCtkOsXslmCwZI--TkZ6hKi1kXZvNmJRE1rYfffYRFn38zhaqszeETX8HiIvahZhXF5fNumBziYdmLdw8hkuN1A~emU6Xz9g~a1Ixfsq1Qr~guYoOtaw-0rOFxNRS9yMehE-2LCb8c-cAg6z5OdlN4qJDl~ZHgru4d~EHp~BpAK3v7u2Gi-8l1ygVW-1CHVna~fwnbOPN3ANPwh6~~yUit0Cx1f54XiNRn6-nPBQAEAAcAAA== -``` - -Copy/paste this host=@base64-address pairing into your **private** @subscription. - -### Directly jumping - -For example, entering `pinkpaste.i2p` into the *Jump* box (and then submitting) will automatically redirect you to the website **and** insert the @locally-unique-host into @address-book. diff --git a/_i18n/de/resources/moneropedia/lease-set.md b/_i18n/de/resources/moneropedia/lease-set.md deleted file mode 100644 index 412f2005..00000000 --- a/_i18n/de/resources/moneropedia/lease-set.md +++ /dev/null @@ -1,24 +0,0 @@ ---- -tags: ["kovri"] -terms: ["LeaseSet", "LeaseSets"] -summary: "Contains all currently authorized Leases for a particular I2P Destination" ---- - -{% include untranslated.html %} -### The Basics - -A Lease-Set contains a set of authorized @leases (and other related information) for a particular @destination. - -### In-depth information - -A Lease-Set contains: - -- all of the currently authorized @leases for a particular @destination -- the public key to which garlic messages can be encrypted (see @garlic-routing) -- the signing public key that can be used to revoke this particular version of the structure - -The Lease-Set is one of the two structures stored in the @network-database (the other being @router-info), and is keyed under the SHA256 of the contained @destination. - -### Notes - -For further details, read @Java-I2P's [LeaseSet](https://geti2p.net/en/docs/how/network-database#leaseSet) diff --git a/_i18n/de/resources/moneropedia/lease.md b/_i18n/de/resources/moneropedia/lease.md deleted file mode 100644 index cfb13659..00000000 --- a/_i18n/de/resources/moneropedia/lease.md +++ /dev/null @@ -1,14 +0,0 @@ ---- -tags: ["kovri"] -terms: ["Lease", "Leases"] -summary: "Authorizes an I2P tunnel to receive messages targeting a destination" ---- - -{% include untranslated.html %} -### The Basics - -A lease defines the authorization for a particular @I2P @tunnel to receive a @messages targeting a @destination. - -### In-depth information - -For further details, read @Java-I2P's [Lease](https://geti2p.net/spec/common-structures#lease) diff --git a/_i18n/de/resources/moneropedia/message.md b/_i18n/de/resources/moneropedia/message.md deleted file mode 100644 index 975277a3..00000000 --- a/_i18n/de/resources/moneropedia/message.md +++ /dev/null @@ -1,32 +0,0 @@ ---- -tags: ["kovri"] -terms: ["Message", "Messages"] -summary: "The mechanisms in which information travels within I2P" ---- - -{% include untranslated.html %} -### The Basics - -*Messages* (which exist on top of the @transports layer), contain varying types of information that are needed for the network but, most importantly, everything you see, do, send, or receive, will come and go in the form of *messages*. - -There are 2 essential types of *messages* in @I2P: - -- @Tunnel messages -- @I2NP messages - -Essentially: *@tunnel messages* **contain** @I2NP **message fragments** which are then [reassembled](https://geti2p.net/en/docs/tunnels/implementation) at certain points within a @tunnel's path. - -### In-depth information - -@I2NP messages have a close relationship with @tunnel @messages so it is easy to get the term *messages* confused when reading @Java-I2P specifications: - -> -1. First, the tunnel gateway accumulates a number of I2NP messages and preprocesses them into tunnel messages for delivery. -2. Next, that gateway encrypts that preprocessed data, then forwards it to the first hop. -3. That peer, and subsequent tunnel participants, unwrap a layer of the encryption, verifying that it isn't a duplicate, then forward it on to the next peer. -4. Eventually, the tunnel messages arrive at the endpoint where the I2NP messages originally bundled by the gateway are reassembled and forwarded on as requested. - -### Notes - -- @I2NP @messages need to be fragmented because they are variable in size (from 0 to almost 64 KB) and @tunnel @messages are fixed-size (approximately 1 KB). -- For details and specifications, visit the [I2NP spec](https://geti2p.net/spec/i2np) and [Tunnel Message spec](https://geti2p.net/spec/tunnel-message) diff --git a/_i18n/de/resources/moneropedia/network-database.md b/_i18n/de/resources/moneropedia/network-database.md deleted file mode 100644 index ac94231a..00000000 --- a/_i18n/de/resources/moneropedia/network-database.md +++ /dev/null @@ -1,24 +0,0 @@ ---- -tags: ["kovri"] -terms: ["Network-Database"] -summary: "A distributed database which contains needed router information so the network can stay intact" ---- - -{% include untranslated.html %} -### The Basics - -@network-database is a [distributed database](https://en.wikipedia.org/wiki/Distributed_database) which contains router information that peers must use so the network can stay intact. - -### In-depth information - -From @Java-I2P: - -> -@I2P's @network-database is a specialized distributed database, containing just two types of data - router contact information (@Router-Infos) and @destination contact information (@LeaseSets). Each piece of data is signed by the appropriate party and verified by anyone who uses or stores it. In addition, the data has liveliness information within it, allowing irrelevant entries to be dropped, newer entries to replace older ones, and protection against certain classes of attack. - -> -The @network-database is distributed with a simple technique called "@floodfill", where a subset of all routers, called "@floodfill routers", maintains the distributed database. - -### Notes - -Read [Network-Database](https://geti2p.net/en/docs/how/network-database) for details. diff --git a/_i18n/de/resources/moneropedia/ntcp.md b/_i18n/de/resources/moneropedia/ntcp.md deleted file mode 100644 index 4c3f68b2..00000000 --- a/_i18n/de/resources/moneropedia/ntcp.md +++ /dev/null @@ -1,33 +0,0 @@ ---- -tags: ["kovri"] -terms: ["NTCP"] -summary: "NIO-Based TCP (Non-blocking I/O based TCP): one of two Kovri transports" ---- - -{% include untranslated.html %} -### The Basics - -*NIO-Based TCP (Non-blocking I/O based TCP)* is one of two encrypted @transports for @Kovri. - -Similar to @SSU, @NTCP's *primary* purpose is to securely transmit @in-net @I2NP messages through @tunnels but, unlike @SSU, @NTCP functions solely over encrypted [TCP](https://en.wikipedia.org/wiki/Transmission_Control_Protocol). - -### In-depth information - - - Passes along individual @I2NP messages (both Standard and Time Sync) after: - - TCP has been established - - Establishment Sequence has been completed - - Uses the following @encryption: - - 2048-bit [Diffie-Hellman](https://en.wikipedia.org/wiki/Diffie-hellman) - - [AES-256](https://en.wikipedia.org/wiki/Advanced_Encryption_Standard)/[CBC](https://en.wikipedia.org/wiki/Block_cipher_modes_of_operation) - - Establishment Sequence has the following *states*: - - Pre-establishment - - Establishment - - Post-establishment or "Established" - - Uses the following from the @network-database: - - Transport name: NTCP - - Host: IP (IPv4 or IPv6) or host name (shortened IPv6 address (with "::") is allowed) - - Port: 1024 - 65535 - -### Notes - -For further details, read @Java-I2P's [NTCP](https://geti2p.net/en/docs/transport/ntcp) diff --git a/_i18n/de/resources/moneropedia/reseed.md b/_i18n/de/resources/moneropedia/reseed.md deleted file mode 100644 index 179f34c5..00000000 --- a/_i18n/de/resources/moneropedia/reseed.md +++ /dev/null @@ -1,16 +0,0 @@ ---- -tags: ["kovri"] -terms: ["Reseed"] -summary: "The method of which Kovri uses to bootstrap into the I2P network" ---- - -{% include untranslated.html %} -### The Basics - -When you start @Kovri for the first time (or if it's been offline for a long time), @Kovri will need a list of peers to connect to so it can [bootstrap](https://en.wikipedia.org/wiki/Bootstrap) into the @I2P network. @Kovri gets these peers from a special file stored on a reseed server. On this file are all the various pieces of information @Kovri needs in order to connect with @I2P peers. - -### In-depth information - -@Kovri has a list of [hard-coded](https://en.wikipedia.org/wiki/Hard-coded) reseed servers available to fetch from. These servers securely serve an [SU3](https://geti2p.net/spec/updates#su3) file (signed with a cryptographic @signature) over @clearnet with [HTTPS](https://en.wikipedia.org/wiki/HTTPS). This SU3 file contains information that's used to verify both the integrity of the file and its content. - -Aside from the technical elements needed to verify and process the file, the file's main contents consist of a series of @router-info files which @Kovri and @I2P routers use to locate and communicate with other @I2P peers. These peers are then stored into a @network-database. diff --git a/_i18n/de/resources/moneropedia/router-info.md b/_i18n/de/resources/moneropedia/router-info.md deleted file mode 100644 index cb190f9d..00000000 --- a/_i18n/de/resources/moneropedia/router-info.md +++ /dev/null @@ -1,67 +0,0 @@ ---- -tags: ["kovri"] -terms: ["Router-Info", "Router-infos"] -summary: "A data structure or file which contains an I2P peer's needed network information" ---- - -{% include untranslated.html %} -### The Basics - -@Router-Info is a data structure (periodically written to a [binary file](https://en.wikipedia.org/wiki/Binary_file)) which contains all needed information to locate, identify, and communicate with an @I2P peer. @Router-Info includes IP address, router identity, other misc. technical details; is needed for @network-database and is published to @floodfill routers. - -### In-depth information - -In human-readable form, Router-Info may look like this: - -``` -Identity: [RouterIdentity: -Hash: nYZ5Qe7gQ-~QgfgJVRUG4c0JnVeVqzM~duUX1EGT1ek= -Certificate: [Certificate: type: Key certificate -Crypto type: 0 -Sig type: 7 (EdDSA_SHA512_Ed25519)] -PublicKey: [PublicKey: size: 256] -SigningPublicKey: [SigningPublicKey EdDSA_SHA512_Ed25519: size: 32] -Padding: 96 bytes] -Signature: [Signature EdDSA_SHA512_Ed25519: size: 64] -Published: Sun Oct 09 01:34:59 UTC 2016 -Options (5): - [caps] = [LfR] - [netId] = [2] - [netdb.knownLeaseSets] = [37] - [netdb.knownRouters] = [2435] - [router.version] = [0.9.26] -Addresses (4): -[RouterAddress: -Type: SSU -Cost: 4 -Options (5): - [caps] = [BC] - [host] = [2a01:e35:8b5c:b240:71a2:6750:8d4:47fa] - [key] = [nYZ5Qe7gQ-~QgfgJVRUG4c0JnVeVqzM~duUX1EGT1ek=] - [mtu] = [1472] - [port] = [22244]] -[RouterAddress: -Type: NTCP -Cost: 9 -Options (2): - [host] = [2a01:e35:8b5c:b240:71a2:6750:8d4:47fa] - [port] = [22244]] -[RouterAddress: -Type: SSU -Cost: 6 -Options (4): - [caps] = [BC] - [host] = [88.181.203.36] - [key] = [nYZ5Qe7gQ-~QgfgJVRUG4c0JnVeVqzM~duUX1EGT1ek=] - [port] = [22244]] -[RouterAddress: -Type: NTCP -Cost: 11 -Options (2): - [host] = [88.181.203.36] - [port] = [22244]]] -``` - -### Notes - -For details and specification, visit @Java-I2P [Network Database](https://geti2p.net/en/docs/how/network-database) page. diff --git a/_i18n/de/resources/moneropedia/ssu.md b/_i18n/de/resources/moneropedia/ssu.md deleted file mode 100644 index cbdadfdc..00000000 --- a/_i18n/de/resources/moneropedia/ssu.md +++ /dev/null @@ -1,25 +0,0 @@ ---- -tags: ["kovri"] -terms: ["SSU"] -summary: "Secure Semi-reliable UDP: one of two Kovri transports" ---- - -{% include untranslated.html %} -### The Basics - -*Secure Semi-reliable UDP* is one of two encrypted @transports for @Kovri. - -Similar to @NTCP, @SSU's *primary* purpose is to securely transmit @in-net @I2NP messages through @tunnels but, unlike @NTCP, @SSU functions solely over encrypted [UDP](https://en.wikipedia.org/wiki/User_Datagram_Protocol). - -### In-depth information - -- Like @NTCP, @SSU is a connection-oriented, point-to-point data transport -- Termed *semi-reliable* because @SSU will repeatedly retransmit *unacknowledged* messages (up to maximum number then dropped) -- @SSU also provides several unique services (in addition to its function as a @transport layer): - - IP detection (local inspection or with [peer testing](https://geti2p.net/en/docs/transport/ssu#peerTesting)) - - [NAT](https://en.wikipedia.org/wiki/Network_address_translation) traversal (using [introducers](https://geti2p.net/en/docs/transport/ssu#introduction)) - - [Firewall](https://en.wikipedia.org/wiki/Firewall_%28computing%29) status and, if implemented, @SSU can notify @NTCP if the external address or firewall status changes - -### Notes - -For further details, read @Java-I2P's [SSU](https://geti2p.net/en/docs/transport/ssu) diff --git a/_i18n/de/resources/moneropedia/subscription.md b/_i18n/de/resources/moneropedia/subscription.md deleted file mode 100644 index 9396fba4..00000000 --- a/_i18n/de/resources/moneropedia/subscription.md +++ /dev/null @@ -1,46 +0,0 @@ ---- -tags: ["kovri"] -terms: ["Subscription"] -summary: "A file used by address book which contains I2P hosts paired with I2P destinations" ---- - -{% include untranslated.html %} -### The Basics - -A subscription is a file which contains a list of `.i2p` hosts paired with their respective @destination. Subscriptions are used by the @address-book. - -### In-depth information - -Similar to how a [hosts file](https://en.wikipedia.org/wiki/Hosts_(file)) can map an Internet hostname to a specified address, a subscription matches a `.i2p` address to @base64-address by using the following format (no spaces allowed): `host=address` - -More specifically, a subscription pairs a @locally-unique-host to @base64-address. - -Example: - -``` -anonimal.i2p=AQZGLAMpI9Q0l0kmMj1vpJJYK3CjLp~fE3MfvE-e7KMKjI5cPOH6EN8m794uHJ6b09qM8mb9VEv1lVLEov~usVliTSXCSHuRBOCIwIOuDNU0AbVa4BpIx~2sU4TxKhoaA3zQ6VzINoduTdR2IJhPvI5xzezp7dR21CEQGGTbenDslXeQ4iLHFA2~bzp1f7etSl9T2W9RID-KH78sRQmzWnv7dbhNodMbpO6xsf1vENf6bMRzqD5vgHEHZu2aSoNuPyYxDU1eM6--61b2xp9mt1k3ud-5WvPVg89RaU9ugU5cxaHgR927lHMCAEU2Ax~zUb3DbrvgQBOTHnJEx2Fp7pOK~PnP6ylkYKQMfLROosLDXinxOoSKP0UYCh2WgIUPwE7WzJH3PiJVF0~WZ1dZ9mg00c~gzLgmkOxe1NpFRNg6XzoARivNVB5NuWqNxr5WKWMLBGQ9YHvHO1OHhUJTowb9X90BhtHnLK2AHwO6fV-iHWxRJyDabhSMj1kuYpVUBQAEAAcAAA== -``` - -1. `anonimal.i2p` is the @locally-unique-host -2. `=` is the separator -3. Everything that remains is the @base64-address - -### Subscription types - -For @Kovri, there are two types of subscription files: *public* and *private*. - -A *public* subscription: -- is used when bootstrapping to use essential services (IRC, email, Monero, etc.) -- is static and is refreshed every 12 hours from Monero's @address-book server -- allows you to safely share the subscription with everyone as it is publically available (anyone who shares the same public subscription will also be able to resolve the same hostname to the same destination as you) - -A *private* subscription: -- is used exclusively by you and is not shared with others unless you explicitly choose to share the file -- default file is `private_hosts.txt` in your @data-directory - -### Updating a private subscription - -You can use a @jump-service to manually update your private subscription. The updated subscription will then be fed into the @address-book for you to use. - -### Notes -To learn how to subscribe to multiple subscriptions, see the [user-guide](https://gitlab.com/kovri-project/kovri-docs/blob/master/i18n/en/user_guide.md). diff --git a/_i18n/de/resources/moneropedia/transports.md b/_i18n/de/resources/moneropedia/transports.md deleted file mode 100644 index b1471cd6..00000000 --- a/_i18n/de/resources/moneropedia/transports.md +++ /dev/null @@ -1,19 +0,0 @@ ---- -tags: ["kovri"] -terms: ["Transports", "Transport"] -summary: "The two encrypted transport layers for Kovri" ---- - -{% include untranslated.html %} -### The Basics - -@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 - -@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 @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) diff --git a/_i18n/de/resources/moneropedia/tunnel.md b/_i18n/de/resources/moneropedia/tunnel.md deleted file mode 100644 index a9ebfaaa..00000000 --- a/_i18n/de/resources/moneropedia/tunnel.md +++ /dev/null @@ -1,36 +0,0 @@ ---- -tags: ["kovri"] -terms: ["Tunnel", "Tunnels"] -summary: "Uni-directional virtual paths that pass messages through a defined sequence of I2P routers" ---- - -{% include untranslated.html %} -### The Basics - -When you communicate over @I2P (visit an @eepsite / use a @garlic-service), you'll first need to connect to a peer by using @transports and then build virtual *tunnels*. These virtual tunnels are temporary, uni-directional paths that pass information through a defined sequence of @I2P routers to your @destination. Tunnels are built, and then used, with layered @garlic-encryption and are a general-purpose mechanism to transport all @I2NP @messages. - -Each peer builds, at a minimum, *two* uni-directional tunnels: one for **outbound traffic**, and one for **inbound traffic**. These tunnels are classified as either **inbound tunnels** (where @messages come toward the creator of the tunnel) or **outbound tunnels** (where the tunnel creator sends @messages away from the creator of the tunnel). Thus, *four* tunnels are required for a single round-trip @message and reply to your @destination (two for your, two for your destination). - -### In-depth information - -From @Java-I2P: - -> -Within I2P, @messages are passed in one direction through a virtual tunnel of peers, using whatever means are available to pass the @message on to the next hop. Messages arrive at the tunnel's gateway, get bundled up and/or fragmented into fixed-size @tunnel @messages, and are forwarded on to the next hop in the tunnel, which processes and verifies the validity of the @message and sends it on to the next hop, and so on, until it reaches the @tunnel endpoint. That endpoint takes the messages bundled up by the gateway and forwards them as instructed - either to another router, to another tunnel on another router, or locally. - -> -Tunnels all work the same, but can be segmented into two different groups - inbound tunnels and outbound tunnels. The inbound tunnels have an untrusted gateway which passes messages down towards the tunnel creator, which serves as the tunnel endpoint. For outbound tunnels, the tunnel creator serves as the gateway, passing messages out to the remote endpoint. - -> -The tunnel's creator selects exactly which peers will participate in the tunnel, and provides each with the necessary configuration data. They may have any number of hops. It is the intent to make it hard for either participants or third parties to determine the length of a tunnel, or even for colluding participants to determine whether they are a part of the same tunnel at all (barring the situation where colluding peers are next to each other in the tunnel). - -### Notes - -From @Java-I2P: - -> -@I2P is an inherently packet switched network, even with these tunnels, allowing it to take advantage of multiple tunnels running in parallel, increasing resilience and balancing load. Even though the tunnels within I2P bear a resemblance to a circuit switched network, everything within I2P is strictly message based - tunnels are merely accounting tricks to help organize the delivery of messages. No assumptions are made regarding reliability or ordering of messages, and retransmissions are left to higher levels (e.g. I2P's client layer streaming library). - -### Documentation - -For specification and detailed documentation, visit the [Tunnel-Routing](https://geti2p.net/en/docs/how/tunnel-routing) and [Tunnel-Implementation](https://geti2p.net/en/docs/tunnels/implementation) page. diff --git a/_i18n/en.yml b/_i18n/en.yml index 4419a2b8..290e2c40 100644 --- a/_i18n/en.yml +++ b/_i18n/en.yml @@ -619,8 +619,6 @@ moneropedia: address: Address airgap: Airgap atomic-units: Atomic Units - base32-address: Base32 address - base64-address: Base64 address blockchain: Blockchain block: Block bootstrap-node: Bootstrap-node @@ -631,32 +629,16 @@ moneropedia: coinbase: Coinbase Transaction consensus: Consensus cryptocurrency: Cryptocurrency - data-directory: Data Directory denominations: Denominations destination: Destination - eepsite: Eepsite encryption: Encryption - floodfill: Floodfill fluffyblocks: Fluffy Blocks fungibility: Fungibility - garlic-encryption: Garlic-Encryption - garlic-routing: Garlic Routing - i2np: I2NP - i2pcontrol: I2PControl - i2p: I2P - in-net: In-net - java-i2p: Java I2P - jump-service: Jump Service kovri: Kovri - lease: Lease - lease-set: Lease-Set locally-unique-host: Locally-unique host - message: Message mining: Mining mnemonicseed: Mnemonic Seed - network-database: Network Database node: Node - ntcp: NTCP openalias: OpenAlias paperwallet: Paper Wallet paymentid: Payment ID @@ -664,22 +646,16 @@ moneropedia: pruning: Pruning randomx: RandomX remote-node: Remote Node - reseed: Reseed ringCT: Ring CT ringsignatures: Ring Signature ring-size: Ring Size - router-info: Router-Info scalability: Scalability signature: Cryptographic Signature smartmining: Smart Mining spendkey: Spend Key - ssu: SSU stealthaddress: Stealth Address - subscription: Subscription tail-emission: Tail Emission transaction: Transactions - transports: Transports - tunnel: Tunnel unlocktime: Transaction Unlock Time viewkey: View Key wallet: Wallet diff --git a/_i18n/en/resources/moneropedia/base32-address.md b/_i18n/en/resources/moneropedia/base32-address.md deleted file mode 100644 index 9737f7c0..00000000 --- a/_i18n/en/resources/moneropedia/base32-address.md +++ /dev/null @@ -1,25 +0,0 @@ ---- -tags: ["kovri"] -terms: ["Base32-address", "Base32-addresses"] -summary: "Base32 encoded hash of a Base64 address" ---- - -### The Basics - -A Base32 address is a shortened, encoded version of an @I2P address. The Base32 address is the first part in a `.b32.i2p` hostname. - -Example: - -`i35yftyyb22xhcvghmev46t5knefur5v66qzekkajatwfwhyklvq.b32.i2p` - -where - -`i35yftyyb22xhcvghmev46t5knefur5v66qzekkajatwfwhyklvq` is the Base32 address. - -### In-depth Information - -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. - -### Notes - -**Note: `.b32` is not a sub-domain of `.i2p`** diff --git a/_i18n/en/resources/moneropedia/base64-address.md b/_i18n/en/resources/moneropedia/base64-address.md deleted file mode 100644 index 56a0589a..00000000 --- a/_i18n/en/resources/moneropedia/base64-address.md +++ /dev/null @@ -1,20 +0,0 @@ ---- -tags: ["kovri"] -terms: ["Base64-address", "Base64-addresses"] -summary: "Base64 encoded I2P destination" ---- - -### The Basics - -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: - -``` -AQZGLAMpI9Q0l0kmMj1vpJJYK3CjLp~fE3MfvE-e7KMKjI5cPOH6EN8m794uHJ6b09qM8mb9VEv1lVLEov~usVliTSXCSHuRBOCIwIOuDNU0AbVa4BpIx~2sU4TxKhoaA3zQ6VzINoduTdR2IJhPvI5xzezp7dR21CEQGGTbenDslXeQ4iLHFA2~bzp1f7etSl9T2W9RID-KH78sRQmzWnv7dbhNodMbpO6xsf1vENf6bMRzqD5vgHEHZu2aSoNuPyYxDU1eM6--61b2xp9mt1k3ud-5WvPVg89RaU9ugU5cxaHgR927lHMCAEU2Ax~zUb3DbrvgQBOTHnJEx2Fp7pOK~PnP6ylkYKQMfLROosLDXinxOoSKP0UYCh2WgIUPwE7WzJH3PiJVF0~WZ1dZ9mg00c~gzLgmkOxe1NpFRNg6XzoARivNVB5NuWqNxr5WKWMLBGQ9YHvHO1OHhUJTowb9X90BhtHnLK2AHwO6fV-iHWxRJyDabhSMj1kuYpVUBQAEAAcAAA== -``` - - -### In-depth Information - -See @destination for details behind @base64-address diff --git a/_i18n/en/resources/moneropedia/data-directory.md b/_i18n/en/resources/moneropedia/data-directory.md deleted file mode 100644 index abe307f2..00000000 --- a/_i18n/en/resources/moneropedia/data-directory.md +++ /dev/null @@ -1,20 +0,0 @@ ---- -tags: ["kovri"] -terms: ["Data-Directory"] -summary: "Where essential kovri data for runtime is stored" ---- - -### The Basics - -Depending on your OS, @Kovri currently stores all run-time data in the following directory: - -- Linux/FreeBSD: - - `$HOME/.kovri` - -- OSX: - - `$HOME/Library/Application\ Support/Kovri` - -- Windows: - - `"$APPDATA"\\Kovri` - -This includes all configuration files, @address-book, certificates, and resources. diff --git a/_i18n/en/resources/moneropedia/eepsite.md b/_i18n/en/resources/moneropedia/eepsite.md deleted file mode 100644 index efb16e1a..00000000 --- a/_i18n/en/resources/moneropedia/eepsite.md +++ /dev/null @@ -1,28 +0,0 @@ ---- -tags: ["kovri"] -terms: ["Eepsite", "Hidden-Service", "Garlic-Site", "Garlic-Service"] -summary: "A website or service hosted within the I2P network" ---- - -### The Basics - -Is it [**EEP!** *(in response to the site's content)*](https://en.wikipedia.org/wiki/Onomatopoeia), or **end-to-end protocol**, or something else entirely different? - -While the original definition of eepsite has been lost with time, its use-case remains: an eepsite is a website or service that is hosted within (and only accessible by) the @I2P network. - -### In-depth Information - -Alternate names include: - -1. *Hidden Service* - - because the site/service is *hidden* within the @I2P network and can only be visited within the network -2. *Garlic Site* - - because the website utilizes @I2P's @garlic-routing technology as a means of communicating with a client - - because the service is hosted as a website and not any other type of service -3. *Garlic Service* - - because the service utilizes @I2P's @garlic-routing technology as a means of communicating with a client - - because the service is specific to services like IRC, email, or a Monero peer (but may also include websites) - -### Notes - -To learn how to setup an Eepsite (Hidden Service, Garlic Site, Garlic Service) visit the @Kovri [user-guide](https://gitlab.com/kovri-project/kovri-docs/blob/master/i18n/en/user_guide.md). diff --git a/_i18n/en/resources/moneropedia/floodfill.md b/_i18n/en/resources/moneropedia/floodfill.md deleted file mode 100644 index f2cb5f04..00000000 --- a/_i18n/en/resources/moneropedia/floodfill.md +++ /dev/null @@ -1,13 +0,0 @@ ---- -tags: ["kovri"] -terms: ["Floodfill"] -summary: "An I2P router which maintains a distributed network-database" ---- - -### The Basics - -By actively managing a distributed network-database, a router with *floodfill* capability has the ability to help maintain network stability and resiliancy while also being decentralized and trust-less. - -### In-depth information - -Though floodfill itself is a simple storage system, the technical underpinnings of floodfill as it relates to @network-database and other protocols within @I2P are much more complex. Visit the [Network Database](https://geti2p.net/en/docs/how/network-database) page for details. diff --git a/_i18n/en/resources/moneropedia/garlic-encryption.md b/_i18n/en/resources/moneropedia/garlic-encryption.md deleted file mode 100644 index 271d7f0c..00000000 --- a/_i18n/en/resources/moneropedia/garlic-encryption.md +++ /dev/null @@ -1,23 +0,0 @@ ---- -tags: ["kovri"] -terms: ["Garlic-Encryption", "Layered-Encryption"] -summary: "Layered encryption as implemented in Kovri / I2P" ---- - -### The Basics - -@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 - -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. diff --git a/_i18n/en/resources/moneropedia/garlic-routing.md b/_i18n/en/resources/moneropedia/garlic-routing.md deleted file mode 100644 index 6e4865e3..00000000 --- a/_i18n/en/resources/moneropedia/garlic-routing.md +++ /dev/null @@ -1,43 +0,0 @@ ---- -tags: ["kovri"] -terms: ["Garlic-Routing"] -summary: "Routing technology as implemented in Kovri" ---- - -### 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. - -The @Garlic-Encryption of @Garlic-Routing is similar to the @Layered-Encryption of [Onion Routing](https://en.wikipedia.org/wiki/Onion_routing) and effectively conceals the IP address of the sender and secures information sent from the sender to its @destination (and vice-versa). - -### 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](http://www.freehaven.net/papers.html) (Section 8.1.1) as derived from the term Onion Routing. - -As recent as October of 2016, [#tor-dev](https://oftc.net/WebChat/) has offered insight into the creation of the term *@garlic-routing*: - -[Nick Mathewson](https://en.wikipedia.org/wiki/The_Tor_Project,_Inc): ->[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](https://en.wikipedia.org/wiki/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 was 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 (similar to the @layered-encryption in Onion Routing) -- Bundling multiple @messages together (garlic cloves) -- ElGamal/AES @encryption - -*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 - -- In terms of Onion/Garlic Routing, another way to envision layered @encryption is by replacing the onion/garlic with a [Matryoshka doll](https://en.wikipedia.org/wiki/Matryoshka_doll) - with each outer/inner doll having a lock and public key to the next/previous doll -- For more technical details on Garlic Routing, read the @Java-I2P entry on [Garlic Routing](https://geti2p.net/en/docs/how/garlic-routing) diff --git a/_i18n/en/resources/moneropedia/i2np.md b/_i18n/en/resources/moneropedia/i2np.md deleted file mode 100644 index 556f59ee..00000000 --- a/_i18n/en/resources/moneropedia/i2np.md +++ /dev/null @@ -1,26 +0,0 @@ ---- -tags: ["kovri"] -terms: ["I2NP"] -summary: "The I2P Network Protocol: the mechanism in which I2NP messages are sent over the I2P network" ---- - -### The Basics - -From @Java-I2P: - -> -@I2NP manages the routing and mixing of messages between routers, as well as the selection of what transports to use when communicating with a peer for which there are multiple common transports supported - -### In-depth information - -From @Java-I2P: - -> -@I2NP (@I2P Network Protocol) @messages can be used for one-hop, router-to-router, point-to-point @messages. By @encrypting and wrapping @messages in other @messages, they can be sent in a secure way through multiple hops to the ultimate @destination. @I2NP does not specify nor require any particular @transport layer but does require at least one @transport in use. - -> -Whenever a @destination wants to send a message to to another @destination, it provides its local router with both the @destination structure and the raw bytes of the message to be sent. The router then determines where to send it, delivers it through outbound @tunnels, instructing the end point to pass it along to the appropriate inbound @tunnel, where it is passed along again to that @tunnel's end point and made available to the target for reception. - -### Notes - -Read more about the @I2NP [protocol](https://geti2p.net/en/docs/protocol/i2np) and [specification](https://geti2p.net/spec/i2np). diff --git a/_i18n/en/resources/moneropedia/i2p.md b/_i18n/en/resources/moneropedia/i2p.md deleted file mode 100644 index 26ef9c46..00000000 --- a/_i18n/en/resources/moneropedia/i2p.md +++ /dev/null @@ -1,29 +0,0 @@ ---- -tags: ["kovri"] -terms: ["I2P"] -summary: "The Invisible Internet Project: an anonymizing overlay network" ---- - -### Monero - -For Monero's implementation of @I2P, see @Kovri. For a comparison of @I2P to [Tor](https://torproject.org/), read the [Comparison](https://geti2p.net/en/comparison/tor) page. - -### The Basics - -From @Java-I2P: - ->The I2P network provides strong privacy protections for communication over the Internet. Many activities that would risk your privacy on the public Internet can be conducted anonymously inside I2P. - -### In-depth information - -From @Java-I2P: - ->I2P is an anonymous overlay network - a network within a network. It is intended to protect communication from dragnet surveillance and monitoring by third parties such as ISPs. - ->I2P is used by many people who care about their privacy: activists, oppressed people, journalists and whistleblowers, as well as the average person. - ->No network can be "perfectly anonymous". The continued goal of I2P is to make attacks more and more difficult to mount. Its anonymity will get stronger as the size of the network increases and with ongoing academic review. - -### Notes - -@I2P documentation and specifications are available [here](https://geti2p.net/docs/). diff --git a/_i18n/en/resources/moneropedia/i2pcontrol.md b/_i18n/en/resources/moneropedia/i2pcontrol.md deleted file mode 100644 index 5491fc4e..00000000 --- a/_i18n/en/resources/moneropedia/i2pcontrol.md +++ /dev/null @@ -1,15 +0,0 @@ ---- -tags: ["kovri"] -terms: ["I2PControl"] -summary: "An API inteface for Kovri and Java-I2P that allows simple remote control" ---- - -### The Basics - -@I2Pcontrol is a [JSONRPC2](https://en.wikipedia.org/wiki/JSON-RPC) [API](https://en.wikipedia.org/wiki/Application_programming_interface) for @Kovri and @Java-I2P which allows an @I2PControl client to remote control/monitor a running instance. - -Two available @I2PControl clients are: [qtoopie](https://github.com/EinMByte/qtoopie) (C++ client) and [itoopie](https://github.com/i2p/i2p.itoopie) (Java client). Read `kovri.conf` to configure @I2PControl for @Kovri. - -### In-depth information - -Details and specification available on the [I2PControl](https://geti2p.net/en/docs/api/i2pcontrol) page. diff --git a/_i18n/en/resources/moneropedia/in-net.md b/_i18n/en/resources/moneropedia/in-net.md deleted file mode 100644 index 884d40f0..00000000 --- a/_i18n/en/resources/moneropedia/in-net.md +++ /dev/null @@ -1,13 +0,0 @@ ---- -tags: ["kovri"] -terms: ["In-net"] -summary: "Within the I2P network" ---- - -### The Basics - -**In-net** is a [colloquial](https://en.wikipedia.org/wiki/Colloquial) term of which describes activities, protocols, or functionality that exist *only* within the @I2P network. - -### In-depth information - -Example: *in-net download* would be defined as downloading *only* within @I2P. diff --git a/_i18n/en/resources/moneropedia/java-i2p.md b/_i18n/en/resources/moneropedia/java-i2p.md deleted file mode 100644 index ede62818..00000000 --- a/_i18n/en/resources/moneropedia/java-i2p.md +++ /dev/null @@ -1,13 +0,0 @@ ---- -tags: ["kovri"] -terms: ["Java-I2P"] -summary: "The original implementation of I2P - written in Java" ---- - -### The Basics - -The term "Java I2P" is often used to describe the original @I2P implementation currently most known and used today. There are various other @I2P implementations, including @Kovri; all of which look up to the original Java implementation. - -### Notes - -To download/learn more about the Java implementation, visit their [website](https://geti2p.net/). diff --git a/_i18n/en/resources/moneropedia/jump-service.md b/_i18n/en/resources/moneropedia/jump-service.md deleted file mode 100644 index 60619ede..00000000 --- a/_i18n/en/resources/moneropedia/jump-service.md +++ /dev/null @@ -1,32 +0,0 @@ ---- -tags: ["kovri"] -terms: ["Jump-Service"] -summary: "An I2P website service that adds addresses to your address book" ---- - -### The Basics - -In your @I2P configured web browser, you can use a Jump Service to *jump* to an @I2P address that you don't have in your @address-book. Once you've *jumped* to the address, the address will be saved into your @address-book. - -### In-depth Information - -In an @I2P configured browser, visit: http://stats.i2p/i2p/lookup.html (courtesy of @Java-I2P's lead developer *zzz*) - -Then, you'll have two options: - -1. *Hostname lookup* the address you wish to visit and then manually copy/paste the result -2. *Jump* to the @I2P website by entering the @I2P hostname (**recommended**) - -### Using hostname lookup - -For example, entering `pinkpaste.i2p` into the *Hostname lookup* box (and then submitting) will return: - -``` -pinkpaste.i2p=m-HrPrIAsdxts0WM~P4mE8mt9P7g-QTaBvu7Gc6Nl0UX7Vwck-i~RvOPfK6W~kfdRvwhNTqevkBL2UF5l36We02Aiywu7kB2xOHRkze68h-Tg2ewvRVwokohguCD2G3wwAEz~7FVda2avYDCb9-N6TfuzxKLnmhPMvbNSjGL7ZsD2p-h207R3-2kvuMV9bfu-K~w9NI9XJhIyufvUnFYc2jnTVg8PbaR4UP57cNaOO2YIMPkbr6~yTcIu9B1sUfHK6-N~6virQDOxW4M-62rjnZkLpaCtkOsXslmCwZI--TkZ6hKi1kXZvNmJRE1rYfffYRFn38zhaqszeETX8HiIvahZhXF5fNumBziYdmLdw8hkuN1A~emU6Xz9g~a1Ixfsq1Qr~guYoOtaw-0rOFxNRS9yMehE-2LCb8c-cAg6z5OdlN4qJDl~ZHgru4d~EHp~BpAK3v7u2Gi-8l1ygVW-1CHVna~fwnbOPN3ANPwh6~~yUit0Cx1f54XiNRn6-nPBQAEAAcAAA== -``` - -Copy/paste this host=@base64-address pairing into your **private** @subscription. - -### Directly jumping - -For example, entering `pinkpaste.i2p` into the *Jump* box (and then submitting) will automatically redirect you to the website **and** insert the @locally-unique-host into @address-book. diff --git a/_i18n/en/resources/moneropedia/lease-set.md b/_i18n/en/resources/moneropedia/lease-set.md deleted file mode 100644 index dc1c4a24..00000000 --- a/_i18n/en/resources/moneropedia/lease-set.md +++ /dev/null @@ -1,23 +0,0 @@ ---- -tags: ["kovri"] -terms: ["LeaseSet", "LeaseSets"] -summary: "Contains all currently authorized Leases for a particular I2P Destination" ---- - -### The Basics - -A Lease-Set contains a set of authorized @leases (and other related information) for a particular @destination. - -### In-depth information - -A Lease-Set contains: - -- all of the currently authorized @leases for a particular @destination -- the public key to which garlic messages can be encrypted (see @garlic-routing) -- the signing public key that can be used to revoke this particular version of the structure - -The Lease-Set is one of the two structures stored in the @network-database (the other being @router-info), and is keyed under the SHA256 of the contained @destination. - -### Notes - -For further details, read @Java-I2P's [LeaseSet](https://geti2p.net/en/docs/how/network-database#leaseSet) diff --git a/_i18n/en/resources/moneropedia/lease.md b/_i18n/en/resources/moneropedia/lease.md deleted file mode 100644 index c5a78058..00000000 --- a/_i18n/en/resources/moneropedia/lease.md +++ /dev/null @@ -1,13 +0,0 @@ ---- -tags: ["kovri"] -terms: ["Lease", "Leases"] -summary: "Authorizes an I2P tunnel to receive messages targeting a destination" ---- - -### The Basics - -A lease defines the authorization for a particular @I2P @tunnel to receive a @messages targeting a @destination. - -### In-depth information - -For further details, read @Java-I2P's [Lease](https://geti2p.net/spec/common-structures#lease) diff --git a/_i18n/en/resources/moneropedia/message.md b/_i18n/en/resources/moneropedia/message.md deleted file mode 100644 index 5cce553b..00000000 --- a/_i18n/en/resources/moneropedia/message.md +++ /dev/null @@ -1,31 +0,0 @@ ---- -tags: ["kovri"] -terms: ["Message", "Messages"] -summary: "The mechanisms in which information travels within I2P" ---- - -### The Basics - -*Messages* (which exist on top of the @transports layer), contain varying types of information that are needed for the network but, most importantly, everything you see, do, send, or receive, will come and go in the form of *messages*. - -There are 2 essential types of *messages* in @I2P: - -- @Tunnel messages -- @I2NP messages - -Essentially: *@tunnel messages* **contain** @I2NP **message fragments** which are then [reassembled](https://geti2p.net/en/docs/tunnels/implementation) at certain points within a @tunnel's path. - -### In-depth information - -@I2NP messages have a close relationship with @tunnel @messages so it is easy to get the term *messages* confused when reading @Java-I2P specifications: - -> -1. First, the tunnel gateway accumulates a number of I2NP messages and preprocesses them into tunnel messages for delivery. -2. Next, that gateway encrypts that preprocessed data, then forwards it to the first hop. -3. That peer, and subsequent tunnel participants, unwrap a layer of the encryption, verifying that it isn't a duplicate, then forward it on to the next peer. -4. Eventually, the tunnel messages arrive at the endpoint where the I2NP messages originally bundled by the gateway are reassembled and forwarded on as requested. - -### Notes - -- @I2NP @messages need to be fragmented because they are variable in size (from 0 to almost 64 KB) and @tunnel @messages are fixed-size (approximately 1 KB). -- For details and specifications, visit the [I2NP spec](https://geti2p.net/spec/i2np) and [Tunnel Message spec](https://geti2p.net/spec/tunnel-message) diff --git a/_i18n/en/resources/moneropedia/network-database.md b/_i18n/en/resources/moneropedia/network-database.md deleted file mode 100644 index eb3925cd..00000000 --- a/_i18n/en/resources/moneropedia/network-database.md +++ /dev/null @@ -1,23 +0,0 @@ ---- -tags: ["kovri"] -terms: ["Network-Database"] -summary: "A distributed database which contains needed router information so the network can stay intact" ---- - -### The Basics - -@network-database is a [distributed database](https://en.wikipedia.org/wiki/Distributed_database) which contains router information that peers must use so the network can stay intact. - -### In-depth information - -From @Java-I2P: - -> -@I2P's @network-database is a specialized distributed database, containing just two types of data - router contact information (@Router-Infos) and @destination contact information (@LeaseSets). Each piece of data is signed by the appropriate party and verified by anyone who uses or stores it. In addition, the data has liveliness information within it, allowing irrelevant entries to be dropped, newer entries to replace older ones, and protection against certain classes of attack. - -> -The @network-database is distributed with a simple technique called "@floodfill", where a subset of all routers, called "@floodfill routers", maintains the distributed database. - -### Notes - -Read [Network-Database](https://geti2p.net/en/docs/how/network-database) for details. diff --git a/_i18n/en/resources/moneropedia/ntcp.md b/_i18n/en/resources/moneropedia/ntcp.md deleted file mode 100644 index 69d10a3f..00000000 --- a/_i18n/en/resources/moneropedia/ntcp.md +++ /dev/null @@ -1,32 +0,0 @@ ---- -tags: ["kovri"] -terms: ["NTCP"] -summary: "NIO-Based TCP (Non-blocking I/O based TCP): one of two Kovri transports" ---- - -### The Basics - -*NIO-Based TCP (Non-blocking I/O based TCP)* is one of two encrypted @transports for @Kovri. - -Similar to @SSU, @NTCP's *primary* purpose is to securely transmit @in-net @I2NP messages through @tunnels but, unlike @SSU, @NTCP functions solely over encrypted [TCP](https://en.wikipedia.org/wiki/Transmission_Control_Protocol). - -### In-depth information - - - Passes along individual @I2NP messages (both Standard and Time Sync) after: - - TCP has been established - - Establishment Sequence has been completed - - Uses the following @encryption: - - 2048-bit [Diffie-Hellman](https://en.wikipedia.org/wiki/Diffie-hellman) - - [AES-256](https://en.wikipedia.org/wiki/Advanced_Encryption_Standard)/[CBC](https://en.wikipedia.org/wiki/Block_cipher_modes_of_operation) - - Establishment Sequence has the following *states*: - - Pre-establishment - - Establishment - - Post-establishment or "Established" - - Uses the following from the @network-database: - - Transport name: NTCP - - Host: IP (IPv4 or IPv6) or host name (shortened IPv6 address (with "::") is allowed) - - Port: 1024 - 65535 - -### Notes - -For further details, read @Java-I2P's [NTCP](https://geti2p.net/en/docs/transport/ntcp) diff --git a/_i18n/en/resources/moneropedia/reseed.md b/_i18n/en/resources/moneropedia/reseed.md deleted file mode 100644 index 59727311..00000000 --- a/_i18n/en/resources/moneropedia/reseed.md +++ /dev/null @@ -1,15 +0,0 @@ ---- -tags: ["kovri"] -terms: ["Reseed"] -summary: "The method of which Kovri uses to bootstrap into the I2P network" ---- - -### The Basics - -When you start @Kovri for the first time (or if it's been offline for a long time), @Kovri will need a list of peers to connect to so it can [bootstrap](https://en.wikipedia.org/wiki/Bootstrap) into the @I2P network. @Kovri gets these peers from a special file stored on a reseed server. On this file are all the various pieces of information @Kovri needs in order to connect with @I2P peers. - -### In-depth information - -@Kovri has a list of [hard-coded](https://en.wikipedia.org/wiki/Hard-coded) reseed servers available to fetch from. These servers securely serve an [SU3](https://geti2p.net/spec/updates#su3) file (signed with a cryptographic @signature) over @clearnet with [HTTPS](https://en.wikipedia.org/wiki/HTTPS). This SU3 file contains information that's used to verify both the integrity of the file and its content. - -Aside from the technical elements needed to verify and process the file, the file's main contents consist of a series of @router-info files which @Kovri and @I2P routers use to locate and communicate with other @I2P peers. These peers are then stored into a @network-database. diff --git a/_i18n/en/resources/moneropedia/router-info.md b/_i18n/en/resources/moneropedia/router-info.md deleted file mode 100644 index ad50c13f..00000000 --- a/_i18n/en/resources/moneropedia/router-info.md +++ /dev/null @@ -1,66 +0,0 @@ ---- -tags: ["kovri"] -terms: ["Router-Info", "Router-infos"] -summary: "A data structure or file which contains an I2P peer's needed network information" ---- - -### The Basics - -@Router-Info is a data structure (periodically written to a [binary file](https://en.wikipedia.org/wiki/Binary_file)) which contains all needed information to locate, identify, and communicate with an @I2P peer. @Router-Info includes IP address, router identity, other misc. technical details; is needed for @network-database and is published to @floodfill routers. - -### In-depth information - -In human-readable form, Router-Info may look like this: - -``` -Identity: [RouterIdentity: -Hash: nYZ5Qe7gQ-~QgfgJVRUG4c0JnVeVqzM~duUX1EGT1ek= -Certificate: [Certificate: type: Key certificate -Crypto type: 0 -Sig type: 7 (EdDSA_SHA512_Ed25519)] -PublicKey: [PublicKey: size: 256] -SigningPublicKey: [SigningPublicKey EdDSA_SHA512_Ed25519: size: 32] -Padding: 96 bytes] -Signature: [Signature EdDSA_SHA512_Ed25519: size: 64] -Published: Sun Oct 09 01:34:59 UTC 2016 -Options (5): - [caps] = [LfR] - [netId] = [2] - [netdb.knownLeaseSets] = [37] - [netdb.knownRouters] = [2435] - [router.version] = [0.9.26] -Addresses (4): -[RouterAddress: -Type: SSU -Cost: 4 -Options (5): - [caps] = [BC] - [host] = [2a01:e35:8b5c:b240:71a2:6750:8d4:47fa] - [key] = [nYZ5Qe7gQ-~QgfgJVRUG4c0JnVeVqzM~duUX1EGT1ek=] - [mtu] = [1472] - [port] = [22244]] -[RouterAddress: -Type: NTCP -Cost: 9 -Options (2): - [host] = [2a01:e35:8b5c:b240:71a2:6750:8d4:47fa] - [port] = [22244]] -[RouterAddress: -Type: SSU -Cost: 6 -Options (4): - [caps] = [BC] - [host] = [88.181.203.36] - [key] = [nYZ5Qe7gQ-~QgfgJVRUG4c0JnVeVqzM~duUX1EGT1ek=] - [port] = [22244]] -[RouterAddress: -Type: NTCP -Cost: 11 -Options (2): - [host] = [88.181.203.36] - [port] = [22244]]] -``` - -### Notes - -For details and specification, visit @Java-I2P [Network Database](https://geti2p.net/en/docs/how/network-database) page. diff --git a/_i18n/en/resources/moneropedia/ssu.md b/_i18n/en/resources/moneropedia/ssu.md deleted file mode 100644 index a7b2eb5b..00000000 --- a/_i18n/en/resources/moneropedia/ssu.md +++ /dev/null @@ -1,24 +0,0 @@ ---- -tags: ["kovri"] -terms: ["SSU"] -summary: "Secure Semi-reliable UDP: one of two Kovri transports" ---- - -### The Basics - -*Secure Semi-reliable UDP* is one of two encrypted @transports for @Kovri. - -Similar to @NTCP, @SSU's *primary* purpose is to securely transmit @in-net @I2NP messages through @tunnels but, unlike @NTCP, @SSU functions solely over encrypted [UDP](https://en.wikipedia.org/wiki/User_Datagram_Protocol). - -### In-depth information - -- Like @NTCP, @SSU is a connection-oriented, point-to-point data transport -- Termed *semi-reliable* because @SSU will repeatedly retransmit *unacknowledged* messages (up to maximum number then dropped) -- @SSU also provides several unique services (in addition to its function as a @transport layer): - - IP detection (local inspection or with [peer testing](https://geti2p.net/en/docs/transport/ssu#peerTesting)) - - [NAT](https://en.wikipedia.org/wiki/Network_address_translation) traversal (using [introducers](https://geti2p.net/en/docs/transport/ssu#introduction)) - - [Firewall](https://en.wikipedia.org/wiki/Firewall_%28computing%29) status and, if implemented, @SSU can notify @NTCP if the external address or firewall status changes - -### Notes - -For further details, read @Java-I2P's [SSU](https://geti2p.net/en/docs/transport/ssu) diff --git a/_i18n/en/resources/moneropedia/subscription.md b/_i18n/en/resources/moneropedia/subscription.md deleted file mode 100644 index 78ef1bf4..00000000 --- a/_i18n/en/resources/moneropedia/subscription.md +++ /dev/null @@ -1,45 +0,0 @@ ---- -tags: ["kovri"] -terms: ["Subscription"] -summary: "A file used by address book which contains I2P hosts paired with I2P destinations" ---- - -### The Basics - -A subscription is a file which contains a list of `.i2p` hosts paired with their respective @destination. Subscriptions are used by the @address-book. - -### In-depth information - -Similar to how a [hosts file](https://en.wikipedia.org/wiki/Hosts_(file)) can map an internet hostname to a specified address, a subscription matches a `.i2p` address to @base64-address by using the following format (no spaces allowed): `host=address` - -More specifically, a subscription pairs a @locally-unique-host to @base64-address. - -Example: - -``` -anonimal.i2p=AQZGLAMpI9Q0l0kmMj1vpJJYK3CjLp~fE3MfvE-e7KMKjI5cPOH6EN8m794uHJ6b09qM8mb9VEv1lVLEov~usVliTSXCSHuRBOCIwIOuDNU0AbVa4BpIx~2sU4TxKhoaA3zQ6VzINoduTdR2IJhPvI5xzezp7dR21CEQGGTbenDslXeQ4iLHFA2~bzp1f7etSl9T2W9RID-KH78sRQmzWnv7dbhNodMbpO6xsf1vENf6bMRzqD5vgHEHZu2aSoNuPyYxDU1eM6--61b2xp9mt1k3ud-5WvPVg89RaU9ugU5cxaHgR927lHMCAEU2Ax~zUb3DbrvgQBOTHnJEx2Fp7pOK~PnP6ylkYKQMfLROosLDXinxOoSKP0UYCh2WgIUPwE7WzJH3PiJVF0~WZ1dZ9mg00c~gzLgmkOxe1NpFRNg6XzoARivNVB5NuWqNxr5WKWMLBGQ9YHvHO1OHhUJTowb9X90BhtHnLK2AHwO6fV-iHWxRJyDabhSMj1kuYpVUBQAEAAcAAA== -``` - -1. `anonimal.i2p` is the @locally-unique-host -2. `=` is the separator -3. Everything that remains is the @base64-address - -### Subscription types - -For @Kovri, there are two types of subscription files: *public* and *private*. - -A *public* subscription: -- is used when bootstrapping to use essential services (IRC, email, Monero, etc.) -- is static and is refreshed every 12 hours from Monero's @address-book server -- allows you to safely share the subscription with everyone as it is publically available (anyone who shares the same public subscription will also be able to resolve the same hostname to the same destination as you) - -A *private* subscription: -- is used exclusively by you and is not shared with others unless you explicitly choose to share the file -- default file is `private_hosts.txt` in your @data-directory - -### Updating a private subscription - -You can use a @jump-service to manually update your private subscription. The updated subscription will then be fed into the @address-book for you to use. - -### Notes -To learn how to subscribe to multiple subscriptions, see the [user-guide](https://gitlab.com/kovri-project/kovri-docs/blob/master/i18n/en/user_guide.md). diff --git a/_i18n/en/resources/moneropedia/transports.md b/_i18n/en/resources/moneropedia/transports.md deleted file mode 100644 index 01225e66..00000000 --- a/_i18n/en/resources/moneropedia/transports.md +++ /dev/null @@ -1,18 +0,0 @@ ---- -tags: ["kovri"] -terms: ["Transports", "Transport"] -summary: "The two encrypted transport layers for Kovri" ---- - -### The Basics - -@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 - -@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 @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) diff --git a/_i18n/en/resources/moneropedia/tunnel.md b/_i18n/en/resources/moneropedia/tunnel.md deleted file mode 100644 index 94369ad2..00000000 --- a/_i18n/en/resources/moneropedia/tunnel.md +++ /dev/null @@ -1,35 +0,0 @@ ---- -tags: ["kovri"] -terms: ["Tunnel", "Tunnels"] -summary: "Uni-directional virtual paths that pass messages through a defined sequence of I2P routers" ---- - -### The Basics - -When you communicate over @I2P (visit an @eepsite / use a @garlic-service), you'll first need to connect to a peer by using @transports and then build virtual *tunnels*. These virtual tunnels are temporary, uni-directional paths that pass information through a defined sequence of @I2P routers to your @destination. Tunnels are built, and then used, with layered @garlic-encryption and are a general-purpose mechanism to transport all @I2NP @messages. - -Each peer builds, at a minimum, *two* uni-directional tunnels: one for **outbound traffic**, and one for **inbound traffic**. These tunnels are classified as either **inbound tunnels** (where @messages come toward the creator of the tunnel) or **outbound tunnels** (where the tunnel creator sends @messages away from the creator of the tunnel). Thus, *four* tunnels are required for a single round-trip @message and reply to your @destination (two for your, two for your destination). - -### In-depth information - -From @Java-I2P: - -> -Within I2P, @messages are passed in one direction through a virtual tunnel of peers, using whatever means are available to pass the @message on to the next hop. Messages arrive at the tunnel's gateway, get bundled up and/or fragmented into fixed-size @tunnel @messages, and are forwarded on to the next hop in the tunnel, which processes and verifies the validity of the @message and sends it on to the next hop, and so on, until it reaches the @tunnel endpoint. That endpoint takes the messages bundled up by the gateway and forwards them as instructed - either to another router, to another tunnel on another router, or locally. - -> -Tunnels all work the same, but can be segmented into two different groups - inbound tunnels and outbound tunnels. The inbound tunnels have an untrusted gateway which passes messages down towards the tunnel creator, which serves as the tunnel endpoint. For outbound tunnels, the tunnel creator serves as the gateway, passing messages out to the remote endpoint. - -> -The tunnel's creator selects exactly which peers will participate in the tunnel, and provides each with the necessary configuration data. They may have any number of hops. It is the intent to make it hard for either participants or third parties to determine the length of a tunnel, or even for colluding participants to determine whether they are a part of the same tunnel at all (barring the situation where colluding peers are next to each other in the tunnel). - -### Notes - -From @Java-I2P: - -> -@I2P is an inherently packet switched network, even with these tunnels, allowing it to take advantage of multiple tunnels running in parallel, increasing resilience and balancing load. Even though the tunnels within I2P bear a resemblance to a circuit switched network, everything within I2P is strictly message based - tunnels are merely accounting tricks to help organize the delivery of messages. No assumptions are made regarding reliability or ordering of messages, and retransmissions are left to higher levels (e.g. I2P's client layer streaming library). - -### Documentation - -For specification and detailed documentation, visit the [Tunnel-Routing](https://geti2p.net/en/docs/how/tunnel-routing) and [Tunnel-Implementation](https://geti2p.net/en/docs/tunnels/implementation) page. diff --git a/_i18n/es/resources/moneropedia/base32-address.md b/_i18n/es/resources/moneropedia/base32-address.md deleted file mode 100644 index 0e3a88e2..00000000 --- a/_i18n/es/resources/moneropedia/base32-address.md +++ /dev/null @@ -1,26 +0,0 @@ ---- -tags: ["kovri"] -terms: ["Base32-address", "Base32-addresses"] -summary: "Base32 encoded hash of a Base64 address" ---- - -{% include untranslated.html %} -### The Basics - -A Base32 address is a shortened, encoded version of an @I2P address. The Base32 address is the first part in a `.b32.i2p` hostname. - -Example: - -`i35yftyyb22xhcvghmev46t5knefur5v66qzekkajatwfwhyklvq.b32.i2p` - -where - -`i35yftyyb22xhcvghmev46t5knefur5v66qzekkajatwfwhyklvq` is the Base32 address. - -### In-depth Information - -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. - -### Notes - -**Note: `.b32` is not a sub-domain of `.i2p`** diff --git a/_i18n/es/resources/moneropedia/base64-address.md b/_i18n/es/resources/moneropedia/base64-address.md deleted file mode 100644 index b9985658..00000000 --- a/_i18n/es/resources/moneropedia/base64-address.md +++ /dev/null @@ -1,21 +0,0 @@ ---- -tags: ["kovri"] -terms: ["Base64-address", "Base64-addresses"] -summary: "Base64 encoded I2P destination" ---- - -{% include untranslated.html %} -### The Basics - -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: - -``` -AQZGLAMpI9Q0l0kmMj1vpJJYK3CjLp~fE3MfvE-e7KMKjI5cPOH6EN8m794uHJ6b09qM8mb9VEv1lVLEov~usVliTSXCSHuRBOCIwIOuDNU0AbVa4BpIx~2sU4TxKhoaA3zQ6VzINoduTdR2IJhPvI5xzezp7dR21CEQGGTbenDslXeQ4iLHFA2~bzp1f7etSl9T2W9RID-KH78sRQmzWnv7dbhNodMbpO6xsf1vENf6bMRzqD5vgHEHZu2aSoNuPyYxDU1eM6--61b2xp9mt1k3ud-5WvPVg89RaU9ugU5cxaHgR927lHMCAEU2Ax~zUb3DbrvgQBOTHnJEx2Fp7pOK~PnP6ylkYKQMfLROosLDXinxOoSKP0UYCh2WgIUPwE7WzJH3PiJVF0~WZ1dZ9mg00c~gzLgmkOxe1NpFRNg6XzoARivNVB5NuWqNxr5WKWMLBGQ9YHvHO1OHhUJTowb9X90BhtHnLK2AHwO6fV-iHWxRJyDabhSMj1kuYpVUBQAEAAcAAA== -``` - - -### In-depth Information - -See @destination for details behind @base64-address diff --git a/_i18n/es/resources/moneropedia/data-directory.md b/_i18n/es/resources/moneropedia/data-directory.md deleted file mode 100644 index 761cfd46..00000000 --- a/_i18n/es/resources/moneropedia/data-directory.md +++ /dev/null @@ -1,21 +0,0 @@ ---- -tags: ["kovri"] -terms: ["Data-Directory"] -summary: "Where essential kovri data for runtime is stored" ---- - -{% include untranslated.html %} -### The Basics - -Depending on your OS, @Kovri currently stores all run-time data in the following directory: - -- Linux/FreeBSD: - - `$HOME/.kovri` - -- OSX: - - `$HOME/Library/Application\ Support/Kovri` - -- Windows: - - `"$APPDATA"\\Kovri` - -This includes all configuration files, @address-book, certificates, and resources. diff --git a/_i18n/es/resources/moneropedia/eepsite.md b/_i18n/es/resources/moneropedia/eepsite.md deleted file mode 100644 index cd450d97..00000000 --- a/_i18n/es/resources/moneropedia/eepsite.md +++ /dev/null @@ -1,29 +0,0 @@ ---- -tags: ["kovri"] -terms: ["Eepsite", "Hidden-Service", "Garlic-Site", "Garlic-Service"] -summary: "A website or service hosted within the I2P network" ---- - -{% include untranslated.html %} -### The Basics - -Is it [**EEP!** *(in response to the site's content)*](https://en.wikipedia.org/wiki/Onomatopoeia), or **end-to-end protocol**, or something else entirely different? - -While the original definition of eepsite has been lost with time, its use-case remains: an eepsite is a website or service that is hosted within (and only accessible by) the @I2P network. - -### In-depth Information - -Alternate names include: - -1. *Hidden Service* - - because the site/service is *hidden* within the @I2P network and can only be visited within the network -2. *Garlic Site* - - because the website utilizes @I2P's @garlic-routing technology as a means of communicating with a client - - because the service is hosted as a website and not any other type of service -3. *Garlic Service* - - because the service utilizes @I2P's @garlic-routing technology as a means of communicating with a client - - because the service is specific to services like IRC, email, or a Monero peer (but may also include websites) - -### Notes - -To learn how to setup an Eepsite (Hidden Service, Garlic Site, Garlic Service) visit the @Kovri [user-guide](https://gitlab.com/kovri-project/kovri-docs/blob/master/i18n/en/user_guide.md). diff --git a/_i18n/es/resources/moneropedia/floodfill.md b/_i18n/es/resources/moneropedia/floodfill.md deleted file mode 100644 index cccd9011..00000000 --- a/_i18n/es/resources/moneropedia/floodfill.md +++ /dev/null @@ -1,14 +0,0 @@ ---- -tags: ["kovri"] -terms: ["Floodfill"] -summary: "An I2P router which maintains a distributed network-database" ---- - -{% include untranslated.html %} -### The Basics - -By actively managing a distributed network-database, a router with *floodfill* capability has the ability to help maintain network stability and resiliancy while also being decentralized and trust-less. - -### In-depth information - -Though floodfill itself is a simple storage system, the technical underpinnings of floodfill as it relates to @network-database and other protocols within @I2P are much more complex. Visit the [Network Database](https://geti2p.net/en/docs/how/network-database) page for details. diff --git a/_i18n/es/resources/moneropedia/garlic-encryption.md b/_i18n/es/resources/moneropedia/garlic-encryption.md deleted file mode 100644 index a0548b3c..00000000 --- a/_i18n/es/resources/moneropedia/garlic-encryption.md +++ /dev/null @@ -1,24 +0,0 @@ ---- -tags: ["kovri"] -terms: ["Garlic-Encryption", "Layered-Encryption"] -summary: "Layered encryption as implemented in Kovri / I2P" ---- - -{% include untranslated.html %} -### The Basics - -@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 - -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. diff --git a/_i18n/es/resources/moneropedia/garlic-routing.md b/_i18n/es/resources/moneropedia/garlic-routing.md deleted file mode 100644 index 4a1d26b9..00000000 --- a/_i18n/es/resources/moneropedia/garlic-routing.md +++ /dev/null @@ -1,44 +0,0 @@ ---- -tags: ["kovri"] -terms: ["Garlic-Routing"] -summary: "Routing technology as implemented in Kovri" ---- - -{% include untranslated.html %} -### 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. - -The @Garlic-Encryption of @Garlic-Routing is similar to the @Layered-Encryption of [Onion Routing](https://en.wikipedia.org/wiki/Onion_routing) and effectively conceals the IP address of the sender and secures information sent from the sender to its @destination (and vice-versa). - -### 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](http://www.freehaven.net/papers.html) (Section 8.1.1) as derived from the term Onion Routing. - -As recent as October of 2016, [#tor-dev](https://oftc.net/WebChat/) has offered insight into the creation of the term *@garlic-routing*: - -[Nick Mathewson](https://en.wikipedia.org/wiki/The_Tor_Project,_Inc): ->[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](https://en.wikipedia.org/wiki/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 was 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 (similar to the @layered-encryption in Onion Routing) -- Bundling multiple @messages together (garlic cloves) -- ElGamal/AES @encryption - -*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 - -- In terms of Onion/Garlic Routing, another way to envision layered @encryption is by replacing the onion/garlic with a [Matryoshka doll](https://en.wikipedia.org/wiki/Matryoshka_doll) - with each outer/inner doll having a lock and public key to the next/previous doll -- For more technical details on Garlic Routing, read the @Java-I2P entry on [Garlic Routing](https://geti2p.net/en/docs/how/garlic-routing) diff --git a/_i18n/es/resources/moneropedia/i2np.md b/_i18n/es/resources/moneropedia/i2np.md deleted file mode 100644 index 1e7841ae..00000000 --- a/_i18n/es/resources/moneropedia/i2np.md +++ /dev/null @@ -1,27 +0,0 @@ ---- -tags: ["kovri"] -terms: ["I2NP"] -summary: "The I2P Network Protocol: the mechanism in which I2NP messages are sent over the I2P network" ---- - -{% include untranslated.html %} -### The Basics - -From @Java-I2P: - -> -@I2NP manages the routing and mixing of messages between routers, as well as the selection of what transports to use when communicating with a peer for which there are multiple common transports supported - -### In-depth information - -From @Java-I2P: - -> -@I2NP (@I2P Network Protocol) @messages can be used for one-hop, router-to-router, point-to-point @messages. By @encrypting and wrapping @messages in other @messages, they can be sent in a secure way through multiple hops to the ultimate @destination. @I2NP does not specify nor require any particular @transport layer but does require at least one @transport in use. - -> -Whenever a @destination wants to send a message to to another @destination, it provides its local router with both the @destination structure and the raw bytes of the message to be sent. The router then determines where to send it, delivers it through outbound @tunnels, instructing the end point to pass it along to the appropriate inbound @tunnel, where it is passed along again to that @tunnel's end point and made available to the target for reception. - -### Notes - -Read more about the @I2NP [protocol](https://geti2p.net/en/docs/protocol/i2np) and [specification](https://geti2p.net/spec/i2np). diff --git a/_i18n/es/resources/moneropedia/i2p.md b/_i18n/es/resources/moneropedia/i2p.md deleted file mode 100644 index 7a6980c3..00000000 --- a/_i18n/es/resources/moneropedia/i2p.md +++ /dev/null @@ -1,30 +0,0 @@ ---- -tags: ["kovri"] -terms: ["I2P"] -summary: "The Invisible Internet Project: an anonymizing overlay network" ---- - -{% include untranslated.html %} -### Monero - -For Monero's implementation of @I2P, see @Kovri. For a comparison of @I2P to [Tor](https://torproject.org/), read the [Comparison](https://geti2p.net/en/comparison/tor) page. - -### The Basics - -From @Java-I2P: - ->The I2P network provides strong privacy protections for communication over the Internet. Many activities that would risk your privacy on the public Internet can be conducted anonymously inside I2P. - -### In-depth information - -From @Java-I2P: - ->I2P is an anonymous overlay network - a network within a network. It is intended to protect communication from dragnet surveillance and monitoring by third parties such as ISPs. - ->I2P is used by many people who care about their privacy: activists, oppressed people, journalists and whistleblowers, as well as the average person. - ->No network can be "perfectly anonymous". The continued goal of I2P is to make attacks more and more difficult to mount. Its anonymity will get stronger as the size of the network increases and with ongoing academic review. - -### Notes - -@I2P documentation and specifications are available [here](https://geti2p.net/docs/). diff --git a/_i18n/es/resources/moneropedia/i2pcontrol.md b/_i18n/es/resources/moneropedia/i2pcontrol.md deleted file mode 100644 index b419423c..00000000 --- a/_i18n/es/resources/moneropedia/i2pcontrol.md +++ /dev/null @@ -1,16 +0,0 @@ ---- -tags: ["kovri"] -terms: ["I2PControl"] -summary: "An API inteface for Kovri and Java-I2P that allows simple remote control" ---- - -{% include untranslated.html %} -### The Basics - -@I2Pcontrol is a [JSONRPC2](https://en.wikipedia.org/wiki/JSON-RPC) [API](https://en.wikipedia.org/wiki/Application_programming_interface) for @Kovri and @Java-I2P which allows an @I2PControl client to remote control/monitor a running instance. - -Two available @I2PControl clients are: [qtoopie](https://github.com/EinMByte/qtoopie) (C++ client) and [itoopie](https://github.com/i2p/i2p.itoopie) (Java client). Read `kovri.conf` to configure @I2PControl for @Kovri. - -### In-depth information - -Details and specification available on the [I2PControl](https://geti2p.net/en/docs/api/i2pcontrol) page. diff --git a/_i18n/es/resources/moneropedia/in-net.md b/_i18n/es/resources/moneropedia/in-net.md deleted file mode 100644 index ec3c5c8a..00000000 --- a/_i18n/es/resources/moneropedia/in-net.md +++ /dev/null @@ -1,14 +0,0 @@ ---- -tags: ["kovri"] -terms: ["In-net"] -summary: "Within the I2P network" ---- - -{% include untranslated.html %} -### The Basics - -**In-net** is a [colloquial](https://en.wikipedia.org/wiki/Colloquial) term of which describes activities, protocols, or functionality that exist *only* within the @I2P network. - -### In-depth information - -Example: *in-net download* would be defined as downloading *only* within @I2P. diff --git a/_i18n/es/resources/moneropedia/java-i2p.md b/_i18n/es/resources/moneropedia/java-i2p.md deleted file mode 100644 index 8a21da5d..00000000 --- a/_i18n/es/resources/moneropedia/java-i2p.md +++ /dev/null @@ -1,14 +0,0 @@ ---- -tags: ["kovri"] -terms: ["Java-I2P"] -summary: "The original implementation of I2P - written in Java" ---- - -{% include untranslated.html %} -### The Basics - -The term "Java I2P" is often used to describe the original @I2P implementation currently most known and used today. There are various other @I2P implementations, including @Kovri; all of which look up to the original Java implementation. - -### Notes - -To download/learn more about the Java implementation, visit their [website](https://geti2p.net/). diff --git a/_i18n/es/resources/moneropedia/jump-service.md b/_i18n/es/resources/moneropedia/jump-service.md deleted file mode 100644 index a62c5276..00000000 --- a/_i18n/es/resources/moneropedia/jump-service.md +++ /dev/null @@ -1,33 +0,0 @@ ---- -tags: ["kovri"] -terms: ["Jump-Service"] -summary: "An I2P website service that adds addresses to your address book" ---- - -{% include untranslated.html %} -### The Basics - -In your @I2P configured web browser, you can use a Jump Service to *jump* to an @I2P address that you don't have in your @address-book. Once you've *jumped* to the address, the address will be saved into your @address-book. - -### In-depth Information - -In an @I2P configured browser, visit: http://stats.i2p/i2p/lookup.html (courtesy of @Java-I2P's lead developer *zzz*) - -Then, you'll have two options: - -1. *Hostname lookup* the address you wish to visit and then manually copy/paste the result -2. *Jump* to the @I2P website by entering the @I2P hostname (**recommended**) - -### Using hostname lookup - -For example, entering `pinkpaste.i2p` into the *Hostname lookup* box (and then submitting) will return: - -``` -pinkpaste.i2p=m-HrPrIAsdxts0WM~P4mE8mt9P7g-QTaBvu7Gc6Nl0UX7Vwck-i~RvOPfK6W~kfdRvwhNTqevkBL2UF5l36We02Aiywu7kB2xOHRkze68h-Tg2ewvRVwokohguCD2G3wwAEz~7FVda2avYDCb9-N6TfuzxKLnmhPMvbNSjGL7ZsD2p-h207R3-2kvuMV9bfu-K~w9NI9XJhIyufvUnFYc2jnTVg8PbaR4UP57cNaOO2YIMPkbr6~yTcIu9B1sUfHK6-N~6virQDOxW4M-62rjnZkLpaCtkOsXslmCwZI--TkZ6hKi1kXZvNmJRE1rYfffYRFn38zhaqszeETX8HiIvahZhXF5fNumBziYdmLdw8hkuN1A~emU6Xz9g~a1Ixfsq1Qr~guYoOtaw-0rOFxNRS9yMehE-2LCb8c-cAg6z5OdlN4qJDl~ZHgru4d~EHp~BpAK3v7u2Gi-8l1ygVW-1CHVna~fwnbOPN3ANPwh6~~yUit0Cx1f54XiNRn6-nPBQAEAAcAAA== -``` - -Copy/paste this host=@base64-address pairing into your **private** @subscription. - -### Directly jumping - -For example, entering `pinkpaste.i2p` into the *Jump* box (and then submitting) will automatically redirect you to the website **and** insert the @locally-unique-host into @address-book. diff --git a/_i18n/es/resources/moneropedia/lease-set.md b/_i18n/es/resources/moneropedia/lease-set.md deleted file mode 100644 index 412f2005..00000000 --- a/_i18n/es/resources/moneropedia/lease-set.md +++ /dev/null @@ -1,24 +0,0 @@ ---- -tags: ["kovri"] -terms: ["LeaseSet", "LeaseSets"] -summary: "Contains all currently authorized Leases for a particular I2P Destination" ---- - -{% include untranslated.html %} -### The Basics - -A Lease-Set contains a set of authorized @leases (and other related information) for a particular @destination. - -### In-depth information - -A Lease-Set contains: - -- all of the currently authorized @leases for a particular @destination -- the public key to which garlic messages can be encrypted (see @garlic-routing) -- the signing public key that can be used to revoke this particular version of the structure - -The Lease-Set is one of the two structures stored in the @network-database (the other being @router-info), and is keyed under the SHA256 of the contained @destination. - -### Notes - -For further details, read @Java-I2P's [LeaseSet](https://geti2p.net/en/docs/how/network-database#leaseSet) diff --git a/_i18n/es/resources/moneropedia/lease.md b/_i18n/es/resources/moneropedia/lease.md deleted file mode 100644 index cfb13659..00000000 --- a/_i18n/es/resources/moneropedia/lease.md +++ /dev/null @@ -1,14 +0,0 @@ ---- -tags: ["kovri"] -terms: ["Lease", "Leases"] -summary: "Authorizes an I2P tunnel to receive messages targeting a destination" ---- - -{% include untranslated.html %} -### The Basics - -A lease defines the authorization for a particular @I2P @tunnel to receive a @messages targeting a @destination. - -### In-depth information - -For further details, read @Java-I2P's [Lease](https://geti2p.net/spec/common-structures#lease) diff --git a/_i18n/es/resources/moneropedia/message.md b/_i18n/es/resources/moneropedia/message.md deleted file mode 100644 index 975277a3..00000000 --- a/_i18n/es/resources/moneropedia/message.md +++ /dev/null @@ -1,32 +0,0 @@ ---- -tags: ["kovri"] -terms: ["Message", "Messages"] -summary: "The mechanisms in which information travels within I2P" ---- - -{% include untranslated.html %} -### The Basics - -*Messages* (which exist on top of the @transports layer), contain varying types of information that are needed for the network but, most importantly, everything you see, do, send, or receive, will come and go in the form of *messages*. - -There are 2 essential types of *messages* in @I2P: - -- @Tunnel messages -- @I2NP messages - -Essentially: *@tunnel messages* **contain** @I2NP **message fragments** which are then [reassembled](https://geti2p.net/en/docs/tunnels/implementation) at certain points within a @tunnel's path. - -### In-depth information - -@I2NP messages have a close relationship with @tunnel @messages so it is easy to get the term *messages* confused when reading @Java-I2P specifications: - -> -1. First, the tunnel gateway accumulates a number of I2NP messages and preprocesses them into tunnel messages for delivery. -2. Next, that gateway encrypts that preprocessed data, then forwards it to the first hop. -3. That peer, and subsequent tunnel participants, unwrap a layer of the encryption, verifying that it isn't a duplicate, then forward it on to the next peer. -4. Eventually, the tunnel messages arrive at the endpoint where the I2NP messages originally bundled by the gateway are reassembled and forwarded on as requested. - -### Notes - -- @I2NP @messages need to be fragmented because they are variable in size (from 0 to almost 64 KB) and @tunnel @messages are fixed-size (approximately 1 KB). -- For details and specifications, visit the [I2NP spec](https://geti2p.net/spec/i2np) and [Tunnel Message spec](https://geti2p.net/spec/tunnel-message) diff --git a/_i18n/es/resources/moneropedia/network-database.md b/_i18n/es/resources/moneropedia/network-database.md deleted file mode 100644 index ac94231a..00000000 --- a/_i18n/es/resources/moneropedia/network-database.md +++ /dev/null @@ -1,24 +0,0 @@ ---- -tags: ["kovri"] -terms: ["Network-Database"] -summary: "A distributed database which contains needed router information so the network can stay intact" ---- - -{% include untranslated.html %} -### The Basics - -@network-database is a [distributed database](https://en.wikipedia.org/wiki/Distributed_database) which contains router information that peers must use so the network can stay intact. - -### In-depth information - -From @Java-I2P: - -> -@I2P's @network-database is a specialized distributed database, containing just two types of data - router contact information (@Router-Infos) and @destination contact information (@LeaseSets). Each piece of data is signed by the appropriate party and verified by anyone who uses or stores it. In addition, the data has liveliness information within it, allowing irrelevant entries to be dropped, newer entries to replace older ones, and protection against certain classes of attack. - -> -The @network-database is distributed with a simple technique called "@floodfill", where a subset of all routers, called "@floodfill routers", maintains the distributed database. - -### Notes - -Read [Network-Database](https://geti2p.net/en/docs/how/network-database) for details. diff --git a/_i18n/es/resources/moneropedia/ntcp.md b/_i18n/es/resources/moneropedia/ntcp.md deleted file mode 100644 index 4c3f68b2..00000000 --- a/_i18n/es/resources/moneropedia/ntcp.md +++ /dev/null @@ -1,33 +0,0 @@ ---- -tags: ["kovri"] -terms: ["NTCP"] -summary: "NIO-Based TCP (Non-blocking I/O based TCP): one of two Kovri transports" ---- - -{% include untranslated.html %} -### The Basics - -*NIO-Based TCP (Non-blocking I/O based TCP)* is one of two encrypted @transports for @Kovri. - -Similar to @SSU, @NTCP's *primary* purpose is to securely transmit @in-net @I2NP messages through @tunnels but, unlike @SSU, @NTCP functions solely over encrypted [TCP](https://en.wikipedia.org/wiki/Transmission_Control_Protocol). - -### In-depth information - - - Passes along individual @I2NP messages (both Standard and Time Sync) after: - - TCP has been established - - Establishment Sequence has been completed - - Uses the following @encryption: - - 2048-bit [Diffie-Hellman](https://en.wikipedia.org/wiki/Diffie-hellman) - - [AES-256](https://en.wikipedia.org/wiki/Advanced_Encryption_Standard)/[CBC](https://en.wikipedia.org/wiki/Block_cipher_modes_of_operation) - - Establishment Sequence has the following *states*: - - Pre-establishment - - Establishment - - Post-establishment or "Established" - - Uses the following from the @network-database: - - Transport name: NTCP - - Host: IP (IPv4 or IPv6) or host name (shortened IPv6 address (with "::") is allowed) - - Port: 1024 - 65535 - -### Notes - -For further details, read @Java-I2P's [NTCP](https://geti2p.net/en/docs/transport/ntcp) diff --git a/_i18n/es/resources/moneropedia/reseed.md b/_i18n/es/resources/moneropedia/reseed.md deleted file mode 100644 index 179f34c5..00000000 --- a/_i18n/es/resources/moneropedia/reseed.md +++ /dev/null @@ -1,16 +0,0 @@ ---- -tags: ["kovri"] -terms: ["Reseed"] -summary: "The method of which Kovri uses to bootstrap into the I2P network" ---- - -{% include untranslated.html %} -### The Basics - -When you start @Kovri for the first time (or if it's been offline for a long time), @Kovri will need a list of peers to connect to so it can [bootstrap](https://en.wikipedia.org/wiki/Bootstrap) into the @I2P network. @Kovri gets these peers from a special file stored on a reseed server. On this file are all the various pieces of information @Kovri needs in order to connect with @I2P peers. - -### In-depth information - -@Kovri has a list of [hard-coded](https://en.wikipedia.org/wiki/Hard-coded) reseed servers available to fetch from. These servers securely serve an [SU3](https://geti2p.net/spec/updates#su3) file (signed with a cryptographic @signature) over @clearnet with [HTTPS](https://en.wikipedia.org/wiki/HTTPS). This SU3 file contains information that's used to verify both the integrity of the file and its content. - -Aside from the technical elements needed to verify and process the file, the file's main contents consist of a series of @router-info files which @Kovri and @I2P routers use to locate and communicate with other @I2P peers. These peers are then stored into a @network-database. diff --git a/_i18n/es/resources/moneropedia/router-info.md b/_i18n/es/resources/moneropedia/router-info.md deleted file mode 100644 index cb190f9d..00000000 --- a/_i18n/es/resources/moneropedia/router-info.md +++ /dev/null @@ -1,67 +0,0 @@ ---- -tags: ["kovri"] -terms: ["Router-Info", "Router-infos"] -summary: "A data structure or file which contains an I2P peer's needed network information" ---- - -{% include untranslated.html %} -### The Basics - -@Router-Info is a data structure (periodically written to a [binary file](https://en.wikipedia.org/wiki/Binary_file)) which contains all needed information to locate, identify, and communicate with an @I2P peer. @Router-Info includes IP address, router identity, other misc. technical details; is needed for @network-database and is published to @floodfill routers. - -### In-depth information - -In human-readable form, Router-Info may look like this: - -``` -Identity: [RouterIdentity: -Hash: nYZ5Qe7gQ-~QgfgJVRUG4c0JnVeVqzM~duUX1EGT1ek= -Certificate: [Certificate: type: Key certificate -Crypto type: 0 -Sig type: 7 (EdDSA_SHA512_Ed25519)] -PublicKey: [PublicKey: size: 256] -SigningPublicKey: [SigningPublicKey EdDSA_SHA512_Ed25519: size: 32] -Padding: 96 bytes] -Signature: [Signature EdDSA_SHA512_Ed25519: size: 64] -Published: Sun Oct 09 01:34:59 UTC 2016 -Options (5): - [caps] = [LfR] - [netId] = [2] - [netdb.knownLeaseSets] = [37] - [netdb.knownRouters] = [2435] - [router.version] = [0.9.26] -Addresses (4): -[RouterAddress: -Type: SSU -Cost: 4 -Options (5): - [caps] = [BC] - [host] = [2a01:e35:8b5c:b240:71a2:6750:8d4:47fa] - [key] = [nYZ5Qe7gQ-~QgfgJVRUG4c0JnVeVqzM~duUX1EGT1ek=] - [mtu] = [1472] - [port] = [22244]] -[RouterAddress: -Type: NTCP -Cost: 9 -Options (2): - [host] = [2a01:e35:8b5c:b240:71a2:6750:8d4:47fa] - [port] = [22244]] -[RouterAddress: -Type: SSU -Cost: 6 -Options (4): - [caps] = [BC] - [host] = [88.181.203.36] - [key] = [nYZ5Qe7gQ-~QgfgJVRUG4c0JnVeVqzM~duUX1EGT1ek=] - [port] = [22244]] -[RouterAddress: -Type: NTCP -Cost: 11 -Options (2): - [host] = [88.181.203.36] - [port] = [22244]]] -``` - -### Notes - -For details and specification, visit @Java-I2P [Network Database](https://geti2p.net/en/docs/how/network-database) page. diff --git a/_i18n/es/resources/moneropedia/ssu.md b/_i18n/es/resources/moneropedia/ssu.md deleted file mode 100644 index cbdadfdc..00000000 --- a/_i18n/es/resources/moneropedia/ssu.md +++ /dev/null @@ -1,25 +0,0 @@ ---- -tags: ["kovri"] -terms: ["SSU"] -summary: "Secure Semi-reliable UDP: one of two Kovri transports" ---- - -{% include untranslated.html %} -### The Basics - -*Secure Semi-reliable UDP* is one of two encrypted @transports for @Kovri. - -Similar to @NTCP, @SSU's *primary* purpose is to securely transmit @in-net @I2NP messages through @tunnels but, unlike @NTCP, @SSU functions solely over encrypted [UDP](https://en.wikipedia.org/wiki/User_Datagram_Protocol). - -### In-depth information - -- Like @NTCP, @SSU is a connection-oriented, point-to-point data transport -- Termed *semi-reliable* because @SSU will repeatedly retransmit *unacknowledged* messages (up to maximum number then dropped) -- @SSU also provides several unique services (in addition to its function as a @transport layer): - - IP detection (local inspection or with [peer testing](https://geti2p.net/en/docs/transport/ssu#peerTesting)) - - [NAT](https://en.wikipedia.org/wiki/Network_address_translation) traversal (using [introducers](https://geti2p.net/en/docs/transport/ssu#introduction)) - - [Firewall](https://en.wikipedia.org/wiki/Firewall_%28computing%29) status and, if implemented, @SSU can notify @NTCP if the external address or firewall status changes - -### Notes - -For further details, read @Java-I2P's [SSU](https://geti2p.net/en/docs/transport/ssu) diff --git a/_i18n/es/resources/moneropedia/subscription.md b/_i18n/es/resources/moneropedia/subscription.md deleted file mode 100644 index bfb4b0bc..00000000 --- a/_i18n/es/resources/moneropedia/subscription.md +++ /dev/null @@ -1,46 +0,0 @@ ---- -tags: ["kovri"] -terms: ["Subscription"] -summary: "A file used by address book which contains I2P hosts paired with I2P destinations" ---- - -{% include untranslated.html %} -### The Basics - -A subscription is a file which contains a list of `.i2p` hosts paired with their respective @destination. Subscriptions are used by the @address-book. - -### In-depth information - -Similar to how a [hosts file](https://en.wikipedia.org/wiki/Hosts_(file)) can map an internet hostname to a specified address, a subscription matches a `.i2p` address to @base64-address by using the following format (no spaces allowed): `host=address` - -More specifically, a subscription pairs a @locally-unique-host to @base64-address. - -Example: - -``` -anonimal.i2p=AQZGLAMpI9Q0l0kmMj1vpJJYK3CjLp~fE3MfvE-e7KMKjI5cPOH6EN8m794uHJ6b09qM8mb9VEv1lVLEov~usVliTSXCSHuRBOCIwIOuDNU0AbVa4BpIx~2sU4TxKhoaA3zQ6VzINoduTdR2IJhPvI5xzezp7dR21CEQGGTbenDslXeQ4iLHFA2~bzp1f7etSl9T2W9RID-KH78sRQmzWnv7dbhNodMbpO6xsf1vENf6bMRzqD5vgHEHZu2aSoNuPyYxDU1eM6--61b2xp9mt1k3ud-5WvPVg89RaU9ugU5cxaHgR927lHMCAEU2Ax~zUb3DbrvgQBOTHnJEx2Fp7pOK~PnP6ylkYKQMfLROosLDXinxOoSKP0UYCh2WgIUPwE7WzJH3PiJVF0~WZ1dZ9mg00c~gzLgmkOxe1NpFRNg6XzoARivNVB5NuWqNxr5WKWMLBGQ9YHvHO1OHhUJTowb9X90BhtHnLK2AHwO6fV-iHWxRJyDabhSMj1kuYpVUBQAEAAcAAA== -``` - -1. `anonimal.i2p` is the @locally-unique-host -2. `=` is the separator -3. Everything that remains is the @base64-address - -### Subscription types - -For @Kovri, there are two types of subscription files: *public* and *private*. - -A *public* subscription: -- is used when bootstrapping to use essential services (IRC, email, Monero, etc.) -- is static and is refreshed every 12 hours from Monero's @address-book server -- allows you to safely share the subscription with everyone as it is publically available (anyone who shares the same public subscription will also be able to resolve the same hostname to the same destination as you) - -A *private* subscription: -- is used exclusively by you and is not shared with others unless you explicitly choose to share the file -- default file is `private_hosts.txt` in your @data-directory - -### Updating a private subscription - -You can use a @jump-service to manually update your private subscription. The updated subscription will then be fed into the @address-book for you to use. - -### Notes -To learn how to subscribe to multiple subscriptions, see the [user-guide](https://gitlab.com/kovri-project/kovri-docs/blob/master/i18n/en/user_guide.md). diff --git a/_i18n/es/resources/moneropedia/transports.md b/_i18n/es/resources/moneropedia/transports.md deleted file mode 100644 index b1471cd6..00000000 --- a/_i18n/es/resources/moneropedia/transports.md +++ /dev/null @@ -1,19 +0,0 @@ ---- -tags: ["kovri"] -terms: ["Transports", "Transport"] -summary: "The two encrypted transport layers for Kovri" ---- - -{% include untranslated.html %} -### The Basics - -@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 - -@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 @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) diff --git a/_i18n/es/resources/moneropedia/tunnel.md b/_i18n/es/resources/moneropedia/tunnel.md deleted file mode 100644 index a9ebfaaa..00000000 --- a/_i18n/es/resources/moneropedia/tunnel.md +++ /dev/null @@ -1,36 +0,0 @@ ---- -tags: ["kovri"] -terms: ["Tunnel", "Tunnels"] -summary: "Uni-directional virtual paths that pass messages through a defined sequence of I2P routers" ---- - -{% include untranslated.html %} -### The Basics - -When you communicate over @I2P (visit an @eepsite / use a @garlic-service), you'll first need to connect to a peer by using @transports and then build virtual *tunnels*. These virtual tunnels are temporary, uni-directional paths that pass information through a defined sequence of @I2P routers to your @destination. Tunnels are built, and then used, with layered @garlic-encryption and are a general-purpose mechanism to transport all @I2NP @messages. - -Each peer builds, at a minimum, *two* uni-directional tunnels: one for **outbound traffic**, and one for **inbound traffic**. These tunnels are classified as either **inbound tunnels** (where @messages come toward the creator of the tunnel) or **outbound tunnels** (where the tunnel creator sends @messages away from the creator of the tunnel). Thus, *four* tunnels are required for a single round-trip @message and reply to your @destination (two for your, two for your destination). - -### In-depth information - -From @Java-I2P: - -> -Within I2P, @messages are passed in one direction through a virtual tunnel of peers, using whatever means are available to pass the @message on to the next hop. Messages arrive at the tunnel's gateway, get bundled up and/or fragmented into fixed-size @tunnel @messages, and are forwarded on to the next hop in the tunnel, which processes and verifies the validity of the @message and sends it on to the next hop, and so on, until it reaches the @tunnel endpoint. That endpoint takes the messages bundled up by the gateway and forwards them as instructed - either to another router, to another tunnel on another router, or locally. - -> -Tunnels all work the same, but can be segmented into two different groups - inbound tunnels and outbound tunnels. The inbound tunnels have an untrusted gateway which passes messages down towards the tunnel creator, which serves as the tunnel endpoint. For outbound tunnels, the tunnel creator serves as the gateway, passing messages out to the remote endpoint. - -> -The tunnel's creator selects exactly which peers will participate in the tunnel, and provides each with the necessary configuration data. They may have any number of hops. It is the intent to make it hard for either participants or third parties to determine the length of a tunnel, or even for colluding participants to determine whether they are a part of the same tunnel at all (barring the situation where colluding peers are next to each other in the tunnel). - -### Notes - -From @Java-I2P: - -> -@I2P is an inherently packet switched network, even with these tunnels, allowing it to take advantage of multiple tunnels running in parallel, increasing resilience and balancing load. Even though the tunnels within I2P bear a resemblance to a circuit switched network, everything within I2P is strictly message based - tunnels are merely accounting tricks to help organize the delivery of messages. No assumptions are made regarding reliability or ordering of messages, and retransmissions are left to higher levels (e.g. I2P's client layer streaming library). - -### Documentation - -For specification and detailed documentation, visit the [Tunnel-Routing](https://geti2p.net/en/docs/how/tunnel-routing) and [Tunnel-Implementation](https://geti2p.net/en/docs/tunnels/implementation) page. diff --git a/_i18n/fr/resources/moneropedia/base32-address.md b/_i18n/fr/resources/moneropedia/base32-address.md deleted file mode 100644 index a7e253d4..00000000 --- a/_i18n/fr/resources/moneropedia/base32-address.md +++ /dev/null @@ -1,25 +0,0 @@ ---- -tags: ["kovri"] -terms: ["Base32-address", "Base32-addresses", "adresse-Base32", "adresses-Base32"] -summary: "Hachage encodé en Base32 d'une adresse Base64" ---- - -### Les Bases - -Une adresse Base32 est une version encodée, plus courte, d'une adresse @I2P. L'adresse Base32 est la première partie d'un nom d'hôte `.b32.i2p`. - -Exemple : - -`i35yftyyb22xhcvghmev46t5knefur5v66qzekkajatwfwhyklvq.b32.i2p` - -où - -`i35yftyyb22xhcvghmev46t5knefur5v66qzekkajatwfwhyklvq` est l'adresse Base32. - -### Informations détaillées - -Finalement, une adresse Base32 est une chaîne de 52 caractères [représentation encodée en Base32](https://en.wikipedia.org/wiki/Base32) du hachage SHA-256 complet d'une @adresse-Base64 @I2P. - -### Remarques - -**Remarque : `.b32` n'est pas un sous-domaine de `.i2p`** diff --git a/_i18n/fr/resources/moneropedia/base64-address.md b/_i18n/fr/resources/moneropedia/base64-address.md deleted file mode 100644 index 59815130..00000000 --- a/_i18n/fr/resources/moneropedia/base64-address.md +++ /dev/null @@ -1,20 +0,0 @@ ---- -tags: ["kovri"] -terms: ["Base64-address", "Base64-addresses", "adresse-Base64", "adresses-Base64"] -summary: "Destination I2P encodée en Base64" ---- - -### Les Bases - -Une @adresse-base64 est une @destination @I2P de 516 caractères [encodés en Base64](https://fr.wikipedia.org/wiki/Base64). Les @adresses-base64 sont utilisées en premier lieu pour les @carnet-d'adresses, @service-de-rebond et également en interne. - -Exemple : - -``` -AQZGLAMpI9Q0l0kmMj1vpJJYK3CjLp~fE3MfvE-e7KMKjI5cPOH6EN8m794uHJ6b09qM8mb9VEv1lVLEov~usVliTSXCSHuRBOCIwIOuDNU0AbVa4BpIx~2sU4TxKhoaA3zQ6VzINoduTdR2IJhPvI5xzezp7dR21CEQGGTbenDslXeQ4iLHFA2~bzp1f7etSl9T2W9RID-KH78sRQmzWnv7dbhNodMbpO6xsf1vENf6bMRzqD5vgHEHZu2aSoNuPyYxDU1eM6--61b2xp9mt1k3ud-5WvPVg89RaU9ugU5cxaHgR927lHMCAEU2Ax~zUb3DbrvgQBOTHnJEx2Fp7pOK~PnP6ylkYKQMfLROosLDXinxOoSKP0UYCh2WgIUPwE7WzJH3PiJVF0~WZ1dZ9mg00c~gzLgmkOxe1NpFRNg6XzoARivNVB5NuWqNxr5WKWMLBGQ9YHvHO1OHhUJTowb9X90BhtHnLK2AHwO6fV-iHWxRJyDabhSMj1kuYpVUBQAEAAcAAA== -``` - - -### Informations détaillées - -Voir @destination pour les détails des @adresses-base64 diff --git a/_i18n/fr/resources/moneropedia/data-directory.md b/_i18n/fr/resources/moneropedia/data-directory.md deleted file mode 100644 index 4c30a2e1..00000000 --- a/_i18n/fr/resources/moneropedia/data-directory.md +++ /dev/null @@ -1,20 +0,0 @@ ---- -tags: ["kovri"] -terms: ["Data-Directory", "répertoire-de-données"] -summary: "Où les données essentielles pour l'exécution de kovri sont stockées." ---- - -### Les Bases - -Dépendamment de votre OS, @Kovri stocke toutes les données pour son fonctionnement dans le répertoire suivant : - -- Linux/FreeBSD: - - `$HOME/.kovri` - -- OSX: - - `$HOME/Library/Application\ Support/Kovri` - -- Windows: - - `"$APPDATA"\\Kovri` - -Cela inclus tous les fichiers de configuration, @carnet-d'adresses, certificats et ressources. diff --git a/_i18n/fr/resources/moneropedia/eepsite.md b/_i18n/fr/resources/moneropedia/eepsite.md deleted file mode 100644 index c0c24180..00000000 --- a/_i18n/fr/resources/moneropedia/eepsite.md +++ /dev/null @@ -1,28 +0,0 @@ ---- -tags: ["kovri"] -terms: ["Eepsite", "Hidden-Service", "Garlic-Site", "Garlic-Service", "site-eep", "service-caché", "site-en-ail", "service-en-ail"] -summary: "Un site web ou service hébergé au sein du réseau I2P." ---- - -### Les Bases - -Est-ce [**EEP!** *(en réponse au contenu du site)*](https://fr.wikipedia.org/wiki/Onomatop%C3%A9e), ou **end-to-end protocol** (*protocol de bout-en-bout*), ou quelque chose de totalement différent ? - -Tandis que la définition originelle de site eep s'est perdue au fil du temps, son cas d'usage demeure : un site eep est un site web ou un service qui est hébergé (et uniquement accessible depuis) le réseau @I2P. - -### Informations détaillées - -d'autres noms comprennent : - -1. *Service Caché* - - Car le site ou service est *caché* au sein du réseau @I2P et ne peut être visité que depuis ce réseau -2. *Site en ail* - - Car le site utilise la technologie de @routage-en-ail d'@I2P comme moyen de communication avec le client - - Car le service hébergé est un site web et pas un autre type de service -3. *Service en ail* - - Car le service utilise la technologie de @routage-en-ail d'@I2P comme moyen de communication avec le client - - Car le service est propre à des services comme IRC, e-mail ou un correspondant Monero (mais peut également inclure des sites web) - -### Remarques - -Pour en savoir plus sur la mise en place d'un site eep (service caché, site en ail, service en ail), consultez le [guide utilisateur](https://gitlab.com/kovri-project/kovri-docs/blob/master/i18n/fr/user_guide.md) de @Kovri. diff --git a/_i18n/fr/resources/moneropedia/floodfill.md b/_i18n/fr/resources/moneropedia/floodfill.md deleted file mode 100644 index d19cc3f8..00000000 --- a/_i18n/fr/resources/moneropedia/floodfill.md +++ /dev/null @@ -1,13 +0,0 @@ ---- -tags: ["kovri"] -terms: ["Floodfill"] -summary: "Un routeur I2P qui maintient une base de données réseau distribuée" ---- - -### Les Bases - -En gérant activement une base de donnée réseau distribuée, un routeur avec la capacité *floodfill* est en mesure d'aider au maintient de la stabilité et de la résilience du réseau tout en étant également décentralisé et sans nécessité de confiance. - -### Informations détaillées - -Bien que *floodfill* ne soit qu'un simple système de stockage, la technique sous-jacente est bien plus complexe car elle s'appuie sur la @base-de-données-réseau et autres protocoles d'@I2P. Rendez-vous sur la page [Base de données Réseau](https://geti2p.net/fr/docs/how/network-database) pour plus d'informations. diff --git a/_i18n/fr/resources/moneropedia/garlic-encryption.md b/_i18n/fr/resources/moneropedia/garlic-encryption.md deleted file mode 100644 index 7e968d55..00000000 --- a/_i18n/fr/resources/moneropedia/garlic-encryption.md +++ /dev/null @@ -1,23 +0,0 @@ ---- -tags: ["kovri"] -terms: ["Garlic-Encryption", "Layered-Encryption", "chiffrement-en-ail", "chiffrement-par-couche"] -summary: "Chiffrement par couche tel qu'implémenté dans Kovri / I2P" ---- - -### Les Bases - -Le @chiffrement-en-ail est l'implémentation d'@I2P du @chiffrement-par-couche basé sur @messages (similaire au [routage en oignon](https://en.wikipedia.org/wiki/Onion_routing). - -En @chiffrant les @messages en couches, cela permet à un @message d'être routé à travers une séquence de mandataires sans leur permettre (ni à aucun intermédiaire) de lire le contenu du @message. Le @chiffrement-par-couche est une fonctionnalité fondamentale de @Kovri, @I2P et [Tor](https://torproject.org), et est la pierre angulaire garantissant l'anonymat au sein de ces surcouches réseaux. - -### Information détaillées - -Pour le @chiffrement-en-ail, les principales différences entre @Kovri / @I2P et tor sont : - -- @Kovri / @I2P groupe plusieurs @messages ensemble pour former des "gousses" d'ail - - autant de messages que nécessaires peuvent être concaténés dans une "gousse" au lieu de *seulement* un seul message -- @Kovri / @I2P utilise le @chiffrement [ElGamal](https://fr.wikipedia.org/wiki/Cryptosyst%C3%A8me_de_ElGamal) et [AES](https://en.wikipedia.org/wiki/Advanced_Encryption_Standard) pour les @messages et les @transports - -### Remarque - -Pourplus de détail, voir @routage-en-ail. diff --git a/_i18n/fr/resources/moneropedia/garlic-routing.md b/_i18n/fr/resources/moneropedia/garlic-routing.md deleted file mode 100644 index 9d663028..00000000 --- a/_i18n/fr/resources/moneropedia/garlic-routing.md +++ /dev/null @@ -1,43 +0,0 @@ ---- -tags: ["kovri"] -terms: ["Garlic-Routing", "routage-en-ail"] -summary: "Technologie de routage telle qu'implémentée dans Kovri" ---- - -### Les Bases - -Le terme de *@routage-en-ail* a une histoire aux interprétations variées. A l'heure actuelle, Monero définit le *@routage-en-ail* comme la méthode selon laquelle @Kovri et @I2P créent une surcouche réseau anonyme d'homologue sur Internet basé sur @messages. - -Le @chiffrement-en-ail du @routage-en-ail est similaire au @chiffrement-par-couche du [routage en oignon](https://en.wikipedia.org/wiki/Onion_routing), il dissimule efficacement l'adresse IP de l'émetteur et sécurise les informations transmises depuis l'émetteur vers sa @destination (et vice-versa). - -### Histoire - -Sous forme écrite, le terme *@routage-en-ail* a été vu pour la première fois sous sa forme anglaise *@garlic-routing* début Juin 2000 dans [Free Haven Master's thesis](http://www.freehaven.net/papers.html) de Roger Dingledine's (Rubrique 8.1.1) comme dérivé du terme Routage en Onion. - -Plus récemment en Octobre 2016, [#tor-dev](https://oftc.net/WebChat/) a offert un aperçu de la création du terme *@routage-en-ail* : - -[Nick Mathewson](https://en.wikipedia.org/wiki/The_Tor_Project,_Inc): ->[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](https://en.wikipedia.org/wiki/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. - -*Remarque : l'utilisation des citations précédentes a été autorisée par Nick Mathewson and Roger Dingledine* - -### Informations détaillées - -En terme techniques, pour @Kovri et @I2P, le *@routage-en-ail* se traduit en l'un / tout ce qui suit : - -- Le @chiffrement-par-couche (similaire au @chiffrement par couche du routage en oignon) -- Regrouper de multiples @messages ensemble (gousses d'ail) -- @Chiffrement ElGamal / AES - -*Remarque : Bien que [Tor](https://torproject.org/) emploie @layered-encryption, Tor n'utilise pas ElGamal et n'est pas basé sur des messages.* - -**Apprenez en plus sur le @chiffrement-en-ail.** - -### Remarques - -- En terme de routage en oignon / en ail, une autre manière de voir les @chiffrements par couche est de rempacer oignon / ail par une [poupée russe](https://fr.wikipedia.org/wiki/Poup%C3%A9e_russe) - avec chaque poupée extérieure / intérieure ayant un verrou et une clef publique pour la prochaine / précédente poupée -- Pour plus de détails technique sur le routage en ail, lisez l'article @I2P-Java sur le [Routage en ail](https://geti2p.net/fr/docs/how/garlic-routing) diff --git a/_i18n/fr/resources/moneropedia/i2np.md b/_i18n/fr/resources/moneropedia/i2np.md deleted file mode 100644 index 8b559c65..00000000 --- a/_i18n/fr/resources/moneropedia/i2np.md +++ /dev/null @@ -1,26 +0,0 @@ ---- -tags: ["kovri"] -terms: ["I2NP"] -summary: "Protocole réseau I2P (I2P Network Protocol) : le mécanisme par lequel des messages I2NP sont envoyés sur le réseau I2P" ---- - -### Les Bases - -Traduit depuis @I2P-Java : - -> -@I2NP gère le routage et le mélange des messages entre les routeurs, de même que la sélection des transports à utiliser lors de la communication avec un pair qui a en commun de multiples transports supportés - -### Informations détaillées - -Traduit depuis @I2P-Java : - -> -les @messages @I2NP (@I2P Network Protocol - Protocol Réseau @I2P) peuvent être utilisés pour des @messages point-à-point d'un seul saut, routeur à routeur. En @chiffrant et emballant les @messages dans d'autres @messages, ils peuvent être transmits de manière sécurisé à travers plusieurs sauts jusqu'à la @destination finale. @I2NP ne spécifie et ne requiert aucune couche de @transport particulière mais requière au moins l'utilisation d'un @transport. - -> -Lorsqu'une @destination souhaite envoyer un message à une autre @destination, elle fournie à son routeur local la structure de @destination ainsi que les octets bruts du message en à envoyer. Le routeur détermine alors où l'envoyer, le distribue à travers des @tunnels sortant, en indiquant le point de terminaison auquel l'envoyer ainsi que le @tunnel entrant approprié, où il est de nouveau transmis à ce point de terminaison de @tunnel et rendu disponible pour réception sur la cible. - -### Remarque - -Apprenez en plu à propos du [protocole](https://geti2p.net/fr/docs/protocol/i2np) et des [spécifications](https://geti2p.net/spec/i2np) @I2NP. diff --git a/_i18n/fr/resources/moneropedia/i2p.md b/_i18n/fr/resources/moneropedia/i2p.md deleted file mode 100644 index b441f492..00000000 --- a/_i18n/fr/resources/moneropedia/i2p.md +++ /dev/null @@ -1,29 +0,0 @@ ---- -tags: ["kovri"] -terms: ["I2P"] -summary: "Le Projet Internet Invisible (Invisible Internet Project) : une surcouche réseau d'anonymisation" ---- - -### Monero - -Pour l'implémentation Monero de @I2P, voir @Kovri. Pour une comparaison d'@I2P avec [Tor](https://torproject.org/), lisez la page [Comparaison](https://geti2p.net/fr/comparison/tor). - -### Les Bases - -Traduit depuis @I2P-Java : - ->Le réseau I2P fournit une forte protection de la confidentialité pour les communications sur Internet. De nombreuses activités qui pourraient mettre en péril votre confidentialité sur l'Internet publique peuvent être réalisées de manière anonyme sur I2P. - -### Informations détaillées - -Traduit depuis @I2P-Java : - ->I2P est une surcouche réseau anonyme - un réseau au travers d'un réseau. Il est conçu pour protéger les communications des fillets d'une surveillance ou d'une observation par des tièrce partie comme les FAI. - ->I2P est utilisé par de nombreuses personnes qui se soucient de leur confidentialité : activistes, personnes opprimées, journalistes et lanceurs d'alerte, ainsi que par des personnes ordinaires. - ->Aucun réseau ne peut être "parfaitement anonyme". l'objectif permanent d'I2P est de rendre les attaques de plus en plus difficiles à monter. Son anonymat se renforcera avec la croissance du réseau et grace aux revue académique régulières. - -### Notes - -la documentation et les spécifications d'@I2P sont disponibles [ici](https://geti2p.net/fr/docs/). diff --git a/_i18n/fr/resources/moneropedia/i2pcontrol.md b/_i18n/fr/resources/moneropedia/i2pcontrol.md deleted file mode 100644 index c54985b2..00000000 --- a/_i18n/fr/resources/moneropedia/i2pcontrol.md +++ /dev/null @@ -1,15 +0,0 @@ ---- -tags: ["kovri"] -terms: ["I2PControl"] -summary: "Une interface API pour Kovri et I2P qui permet un simple contrôle distant" ---- - -### Les Bases - -@I2Pcontrol est une [API](https://fr.wikipedia.org/wiki/Interface_de_programmation) [JSONRPC2](https://en.wikipedia.org/wiki/JSON-RPC) pour @Kovri et @I2P-Java qui permet à un client @I2PControl de contrôler ou surveiller une instance en fonctionnement. - -Deux clients @I2PControl sont : [qtoopie](https://github.com/EinMByte/qtoopie) (client C++) et [itoopie](https://github.com/i2p/i2p.itoopie) (client Java). Consultez `kovri.conf` pour configurer @I2PControl pour @Kovri. - -### Informations détaillées - -Les détails et spécifications sont disponibles sur la page [I2PControl](https://geti2p.net/fr/docs/api/i2pcontrol). diff --git a/_i18n/fr/resources/moneropedia/in-net.md b/_i18n/fr/resources/moneropedia/in-net.md deleted file mode 100644 index 411e42d6..00000000 --- a/_i18n/fr/resources/moneropedia/in-net.md +++ /dev/null @@ -1,13 +0,0 @@ ---- -tags: ["kovri"] -terms: ["In-net", "interne-au-réseau", "internes-au-réseau"] -summary: "Au sein du réseau I2P" ---- - -### Les Bases - -**Interne au réseau** est un terme [courant](https://fr.wikipedia.org/wiki/Registre_de_langue) qui décrit les activités, protocoles, ou fonctionnalités qui n'existent *que* sur le réseau @I2P. - -### Informations détaillées - -Exemple : *téléchargement interne au réseau* serait définit comme télécharger *uniquement* au sein d'@I2P. diff --git a/_i18n/fr/resources/moneropedia/java-i2p.md b/_i18n/fr/resources/moneropedia/java-i2p.md deleted file mode 100644 index 464997a5..00000000 --- a/_i18n/fr/resources/moneropedia/java-i2p.md +++ /dev/null @@ -1,13 +0,0 @@ ---- -tags: ["kovri"] -terms: ["Java-I2P", "I2P-Java"] -summary: "L'implémentation originelle d'I2P - écrite en Java" ---- - -### Les Bases - -Le terme "Java I2P" est souvent utilisé pour décrire l'implémentation originelle d'@I2P, actuellement la plus connue et la plus utilisée. Il y a de nombreuses autres implémentations d'@I2P, incluant @Kovri. Elles cherchent toutes à améliorer l'implémentation Java originelle. - -### Remarque - -Pour télécharger l'implémentation Java ou en apprendre plus, visitez leur [site web](https://geti2p.net/fr/). diff --git a/_i18n/fr/resources/moneropedia/jump-service.md b/_i18n/fr/resources/moneropedia/jump-service.md deleted file mode 100644 index 64f02dfd..00000000 --- a/_i18n/fr/resources/moneropedia/jump-service.md +++ /dev/null @@ -1,32 +0,0 @@ ---- -tags: ["kovri"] -terms: ["Jump-Service", "service-de-rebond"] -summary: "Un service sur un site I2P qui ajoute une adresse à votre carnet d'adresse." ---- - -### Les Bases - -Dans votre navigateur web configuré pour @I2P, vous pouvez utiliser un service de rebond pour *rebondir* sur une adresse @I2P que vous n'avez pas encore dans votre @carnet-d'adresses. Une fois que vous avez *rebondit* sur l'adresse, celle-ci est sauvegardée dans votre @carnet-d'adresses. - -### Informations détaillées - -Dans un navigateur configuré pour @I2P, rendez-vous sur : http://stats.i2p/i2p/lookup.html (une amabilité du développeur principal d'@I2P-Java *zzz*) - -Vous aurez alors deux options : - -1. Recherchez le nom d'hôte (*Hostname lookup*) de l'adresse que vous souhaitez visiter en copiez-collez manuellement le résultat. -2. Rebondissez (*Jump*) vers le site web @I2P entrant le nom d'hôte @I2P (**recommandé**) - -### Utiliser la recherche de nom d'hôte - -Par exemple, entrez `pinkpaste.i2p` dans le champ *Hostname lookup* (puis cliquez sur envoyer (*submit*)) va renvoyer : - -``` -pinkpaste.i2p=m-HrPrIAsdxts0WM~P4mE8mt9P7g-QTaBvu7Gc6Nl0UX7Vwck-i~RvOPfK6W~kfdRvwhNTqevkBL2UF5l36We02Aiywu7kB2xOHRkze68h-Tg2ewvRVwokohguCD2G3wwAEz~7FVda2avYDCb9-N6TfuzxKLnmhPMvbNSjGL7ZsD2p-h207R3-2kvuMV9bfu-K~w9NI9XJhIyufvUnFYc2jnTVg8PbaR4UP57cNaOO2YIMPkbr6~yTcIu9B1sUfHK6-N~6virQDOxW4M-62rjnZkLpaCtkOsXslmCwZI--TkZ6hKi1kXZvNmJRE1rYfffYRFn38zhaqszeETX8HiIvahZhXF5fNumBziYdmLdw8hkuN1A~emU6Xz9g~a1Ixfsq1Qr~guYoOtaw-0rOFxNRS9yMehE-2LCb8c-cAg6z5OdlN4qJDl~ZHgru4d~EHp~BpAK3v7u2Gi-8l1ygVW-1CHVna~fwnbOPN3ANPwh6~~yUit0Cx1f54XiNRn6-nPBQAEAAcAAA== -``` - -Copiez-collez ce couple host=@adresse-base64 dans vos @souscriptions **privée**. - -### Rebond direct - -Par exemple, entrez `pinkpaste.i2p` dans le champ *Jump* (puis cliquez sur envoyer (*submit*)) va automatiquement vous rediriger vers le site web **et** insérer l'@hôte-unique-localement dans votre @carnet-d'adresses. diff --git a/_i18n/fr/resources/moneropedia/lease-set.md b/_i18n/fr/resources/moneropedia/lease-set.md deleted file mode 100644 index 2ac1dab4..00000000 --- a/_i18n/fr/resources/moneropedia/lease-set.md +++ /dev/null @@ -1,23 +0,0 @@ ---- -tags: ["kovri"] -terms: ["LeaseSet", "LeaseSets", "lot-de-baux", "lots-de-baux"] -summary: "Contient tous les baux actuellement autorisés pour une destination I2P spécifique" ---- - -### Les Bases - -Un Lot de baux contient un lot de @baux autorisés (et d'autres informations liés) pour une @destination spécifique. - -### Informations détaillées - -Un lot de baux contient : - -- Tous les baux actuellement autorisés pour une @destination spécifique -- La clef publique avec laquelle les messages en ail sont chiffrés (voir @routage-en-ail) -- La clef de signature publique qui peut être utilisée pour révoquer cette version spécifique de la structure - -Le lot de baux est l'une des deux structures stockées dans la @base-de-donnée-réseau (l'autre étant les @infos-des-routeurs), et verrouillé dans le SHA256 de la @destination en question. - -### Remarque - -Pour plus de détail, lisez le [lot de baux](https://geti2p.net/fr/docs/how/network-database#leaseSet) d'@I2P-Java. diff --git a/_i18n/fr/resources/moneropedia/lease.md b/_i18n/fr/resources/moneropedia/lease.md deleted file mode 100644 index 9802af3b..00000000 --- a/_i18n/fr/resources/moneropedia/lease.md +++ /dev/null @@ -1,13 +0,0 @@ ---- -tags: ["kovri"] -terms: ["Lease", "Leases", "bail", "baux"] -summary: "Autorise un tunnel I2P à recevoir des messages ciblant une destination" ---- - -### Les Bases - -Un bail définit les autorisations d'un @tunnel @I2P spécifique à recevoir des @messages ciblant une @destination. - -### Informations détaillées - -Pour plus de détails, lisez la page [Bail](https://geti2p.net/spec/common-structures#lease) de @I2P-Java diff --git a/_i18n/fr/resources/moneropedia/message.md b/_i18n/fr/resources/moneropedia/message.md deleted file mode 100644 index 54ca8f56..00000000 --- a/_i18n/fr/resources/moneropedia/message.md +++ /dev/null @@ -1,31 +0,0 @@ ---- -tags: ["kovri"] -terms: ["Message", "Messages"] -summary: "Le mécanisme à travers lequel les informations circulent au sein d'I2P" ---- - -### Les Bases - -Les *Messages* (qui existent au dessus de la couche @transport) contiennent différents types d'informations qui sont necessaries au réseau, mais surtout, tout ce que vous voyez, faites, envoyez ou recevez sera reçu et envoyé sous la forme de *messages*. - -Il y a essentiellement deux types de *messages* dans @I2P : - -- les messages de @tunnels -- les messages @I2NP - -En substance : les *messages de @tunnel* **contiennent** des **fragments de message** @I2NP qui sont [réassemblés](https://geti2p.net/fr/docs/tunnels/implementation) à certains point du chemin du @tunnel. - -### Informations détaillées - -Les messages @I2NP ont un lien étroit avec les @messages de @tunnels au point qu'il est facile de confondre les termes @messages en lisant les spécifications @I2P-Java : - -> -1. D'abord, la passerelle du tunnel accumule une quantité de messages I2NP et les prétraite dans des messages de tunnels pour distribution. -2. Puis, cette passerelle chiffre les données prétraitées et les transmet au premier saut. -3. Ce pair, et les participants suivant du tunnel, déballent une couche du chiffrement, vérifient qu'il ne s'agit pas d'un doublon, et transmettent le message au pair suivant. -4. Finalement, les messages du tunnel arrivent au point de terminaison où les messages I2NP originellement empaquetés par la passerelle sont réassemblés et transmis comme demandé. - -### Remarques - -- Les @messages @I2NP doivent être fragmentés car ils ont une taille variable (de 0 à environt 64 Ko) et les @messages de @tunnels ont une taille fixe (environ 1 Ko). -- Pour plus de détaille et les spécifications, rendez-vous sur les [spécifications I2NP](https://geti2p.net/spec/i2np) et les [spécifications de message de tunnel](https://geti2p.net/spec/tunnel-message) diff --git a/_i18n/fr/resources/moneropedia/network-database.md b/_i18n/fr/resources/moneropedia/network-database.md deleted file mode 100644 index 859d0c87..00000000 --- a/_i18n/fr/resources/moneropedia/network-database.md +++ /dev/null @@ -1,23 +0,0 @@ ---- -tags: ["kovri"] -terms: ["Network-Database", "base-de-données-réseau"] -summary: "Une base de données distribuée qui contient les informations de routeurs nécessaire pour que le réseau reste intact" ---- - -### Les Bases - -Une @base-de-données-réseau est une [base de données distribuée](https://fr.wikipedia.org/wiki/Base_de_donn%C3%A9es_distribu%C3%A9e) qui contient les informations des routeurs que les pairs doivent utiliser afin que le réseau reste intact. - -### Informations détaillées - -Traduit depuis @I2P-Java: - -> -La @base-de-données-réseau d'@IEP est une base de données distribuée spécialisée qui contient uniquement deux types de données : les informations de contact des routeurs (@Infos-des-routeurs) et les informations de contact des @destinations (@Lots-de-baux). Chaque donnée est signée par la partie appropriée et vérifiée par tous ceux qui l'utilisent ou la conservent. De plus, la donnée contient une information de durée de vie, permettant aux entrées désuètes d'êtres supprimées, aux nouvelles entrées de remplacer les anciennes, et une protection vis-à-vis de certaines classes d'attaques. - -> -La @base-de-données-réseau est distribué par une technique simple appelée "@floodfill", selon laquelle une portions de tous les routeurs, appelés "routeurs @floodfill", maintiennent et distribuent la base de données. - -### Notes - -Lisez [Base de Données](https://geti2p.net/fr/docs/how/network-database) pour plus de détails. diff --git a/_i18n/fr/resources/moneropedia/ntcp.md b/_i18n/fr/resources/moneropedia/ntcp.md deleted file mode 100644 index 878214ad..00000000 --- a/_i18n/fr/resources/moneropedia/ntcp.md +++ /dev/null @@ -1,32 +0,0 @@ ---- -tags: ["kovri"] -terms: ["NTCP"] -summary: "NIO-Based TCP (TCP basé sur des E/S non-bloquantes) : l'un des transports de Kovri" ---- - -### Les Bases - -*NIO-Based TCP (TCP basé sur des E/S non-bloquantes)* est l'un des deux @transports chiffrés de @Kovri. - -Tout comme @USS, la *principale* raison d'être de @NTCP est de transmettre de manière sécurisé les messages @I2NP @internes-au-réseaumais, contrairement à @USS, @NTCP fonctionne exclusivement sur du [TCP](https://fr.wikipedia.org/wiki/Transmission_Control_Protocol) chiffré. - -### Informations détaillées - -- Passe sûr les messages @I2NP individuel (à la fois Standard et de synchronisation temporelle) après : - - l'établissement de TCP - - la finalisation de la séquence d'établissement -- Utilise les @chiffrements suivants : - - [Diffie-Hellman](https://fr.wikipedia.org/wiki/%C3%89change_de_cl%C3%A9s_Diffie-Hellman) 2048 bits - - [AES-256](https://fr.wikipedia.org/wiki/Advanced_Encryption_Standard)/[CBC](https://fr.wikipedia.org/wiki/Mode_d%27op%C3%A9ration_(cryptographie)) -- La séquence d'établissement suit les *états* suivants : - - Pré-établissement - - Établissement - - Post-établissement ou "Établit" -- Utilise de la @base-de-données-réseau : - - Nom du transport : NTCP - - Hôte : IP (IPv4 ou IPv6) ou nom d'hôte (adresses IPv6 raccourcies (avec "::") autorisées) - - Port : 1024 - 65535 - -### Remarque - -Pour plus de détails, lisez [NTCP](https://geti2p.net/fr/docs/transport/ntcp) de @I2P-Java. diff --git a/_i18n/fr/resources/moneropedia/reseed.md b/_i18n/fr/resources/moneropedia/reseed.md deleted file mode 100644 index 322c4fc4..00000000 --- a/_i18n/fr/resources/moneropedia/reseed.md +++ /dev/null @@ -1,15 +0,0 @@ ---- -tags: ["kovri"] -terms: ["Reseed", "réensemencement"] -summary: "La méthode que Kovri utilise pour s'amorcer sur le réseau I2P" ---- - -### Les Bases - -Lorsque vous démarrez @Kovri pour la première fois (ou s'il a été arrêté longtemps), @Kovri a besoin d'une liste de pairs auxquels se connecter afin qu'il puisse s'[amorcer](https://en.wikipedia.org/wiki/Bootstrapping) dans le réseau @I2P. @Kovri obtient ces pairs à partir d'un fichier spécifique stocké sur un serveur de réensemencement. Les diverses données dont @Kovri a besoin pour se connecter avec des pairs @I2P se trouvent dans ce fichier. - -### Informations détaillées - -@Kovri dispose d'une liste de serveur de réensemencement [programmée en dur](https://en.wikipedia.org/wiki/Hard-coded) à partir desquels récupérer les données. Ces serveurs servent un fichier [SU3](https://geti2p.net/spec/updates#su3) de manière sécurisée (signé avec une @signature cryptographique) sur le @réseau-en-clair avec [HTTPS](https://fr.wikipedia.org/wiki/HTTPS). Ce fichier SU3 contient les informations nécessaires à la vérification à la fois de l'intégrité et du contenu de ce fichier. - -Conjointement aux éléments techniques nécessaires pour vérifier et traiter le fichier, le contenu principal du fichier est une série de fichier d'@info-des-routeurs que les routeurs @Kovri et @I2P utilisent pour trouver et communiquer avec d'autres pairs @I2P. Ces pairs sont ensuite stockés dans une @base-de-données-réseau. diff --git a/_i18n/fr/resources/moneropedia/router-info.md b/_i18n/fr/resources/moneropedia/router-info.md deleted file mode 100644 index 2baea798..00000000 --- a/_i18n/fr/resources/moneropedia/router-info.md +++ /dev/null @@ -1,66 +0,0 @@ ---- -tags: ["kovri"] -terms: ["Router-Info", "Router-infos", "Info-des-routeurs", "Infos-des-routeurs"] -summary: "Une structure de données ou un fichier qui contient les informations réseau nécessaires pour un homologue I2P" ---- - -### Les Bases - -Les @infos-des-routeurs sont une structure de données (périodiquement écrite dans un [fichier binaire](https://fr.wikipedia.org/wiki/Fichier_binaire)) qui contient toutes les informations nécessaires pour localiser, identifier et communiquer avec un homologue @I2P. Les @infos-des-routeurs inclues l'adresse IP, l'identité du routeur et d'autres détails techniques divers. Elle est nécessaire à la @base-de-données-réseau et est publiée aux routeurs @floodfill. - -### Informations détaillées - -Sous une forme lisible par l'homme, les Infos des routeurs ressemble à cela : - -``` -Identity: [RouterIdentity: -Hash: nYZ5Qe7gQ-~QgfgJVRUG4c0JnVeVqzM~duUX1EGT1ek= -Certificate: [Certificate: type: Key certificate -Crypto type: 0 -Sig type: 7 (EdDSA_SHA512_Ed25519)] -PublicKey: [PublicKey: size: 256] -SigningPublicKey: [SigningPublicKey EdDSA_SHA512_Ed25519: size: 32] -Padding: 96 bytes] -Signature: [Signature EdDSA_SHA512_Ed25519: size: 64] -Published: Sun Oct 09 01:34:59 UTC 2016 -Options (5): - [caps] = [LfR] - [netId] = [2] - [netdb.knownLeaseSets] = [37] - [netdb.knownRouters] = [2435] - [router.version] = [0.9.26] -Addresses (4): -[RouterAddress: -Type: USS -Cost: 4 -Options (5): - [caps] = [BC] - [host] = [2a01:e35:8b5c:b240:71a2:6750:8d4:47fa] - [key] = [nYZ5Qe7gQ-~QgfgJVRUG4c0JnVeVqzM~duUX1EGT1ek=] - [mtu] = [1472] - [port] = [22244]] -[RouterAddress: -Type: NTCP -Cost: 9 -Options (2): - [host] = [2a01:e35:8b5c:b240:71a2:6750:8d4:47fa] - [port] = [22244]] -[RouterAddress: -Type: USS -Cost: 6 -Options (4): - [caps] = [BC] - [host] = [88.181.203.36] - [key] = [nYZ5Qe7gQ-~QgfgJVRUG4c0JnVeVqzM~duUX1EGT1ek=] - [port] = [22244]] -[RouterAddress: -Type: NTCP -Cost: 11 -Options (2): - [host] = [88.181.203.36] - [port] = [22244]]] -``` - -### Remarque - -Pour de détails et spécifications, consultez la page [Base de donnée réseau](https://geti2p.net/fr/docs/how/network-database) de @I2P-Java. diff --git a/_i18n/fr/resources/moneropedia/ssu.md b/_i18n/fr/resources/moneropedia/ssu.md deleted file mode 100644 index f77b12e4..00000000 --- a/_i18n/fr/resources/moneropedia/ssu.md +++ /dev/null @@ -1,24 +0,0 @@ ---- -tags: ["kovri"] -terms: ["SSU", "USS"] -summary: "UDP Semi-fiable Sécurisé : l'un des deux transports de Kovri" ---- - -### Les Bases - -*UDP Semi-fiable Sécurisé* est l'un des deux @transports chiffrés de @Kovri. - -Similaire à @NTCP, le *premier* rôle d'@USS est de transmettre les messages @I2NP @interne-au-réseau de manière sécurisé à travers des @tunnels, mais contrairement à @NTCP, @USS fonctionne uniquement sur de l'[UDP](https://fr.wikipedia.org/wiki/User_Datagram_Protocol) chiffré. - -### Informations détaillées - -- Comme @NTCP, @USS est un transport de donné point-à-point, orienté connexion. -- Désigné *semi-fiable* cas @USS va retransmettre à plusieurs reprises les messages *non acquittés* (jusqu'à une certaine limite, puis les abandonner) -- @USS fournit également plusieurs services uniques (en plus de sa fonction de couche de @transport) : - - Détection d'IP (inspection locale ou avec [test d'homologue](https://geti2p.net/fr/docs/transport/ssu#peerTesting)) - - [NAT](https://en.wikipedia.org/wiki/Network_address_translation) traversal (en utilisant des [introducteurs](https://geti2p.net/fr/docs/transport/ssu#introduction)) - - États de [pare-feu](https://fr.wikipedia.org/wiki/Pare-feu_(informatique)) et, si implémenté, @USS peut notifier @NTCP d'un changement d'adresse externe ou d'état de pare-feu - -### Remarque - -Pour plus de détails, lisez [USS](https://geti2p.net/fr/docs/transport/ssu) de @I2P-Java diff --git a/_i18n/fr/resources/moneropedia/subscription.md b/_i18n/fr/resources/moneropedia/subscription.md deleted file mode 100644 index 103178fe..00000000 --- a/_i18n/fr/resources/moneropedia/subscription.md +++ /dev/null @@ -1,45 +0,0 @@ ---- -tags: ["kovri"] -terms: ["Subscription", "souscription", "souscriptions"] -summary: "Un fichier utilisé par le carnet d'adresses qui contient les hôtes I2P associés aux destinations I2P" ---- - -### Les Bases - -Une souscription est un fichier qui contient une liste d'hôtes `.i2p` associés à leurs @destinations respectives. Les souscriptions sont utilisées par le @carnet-d'adresses. - -### Informations détaillées - -De la même manière qu'un [fichier hosts](https://fr.wikipedia.org/wiki/Hosts) peut faire correspondre un nom d'hôte internet à une adresse spécifique, une souscription fait correspondre une adresse `.i2p` à une @adresse-base64 en utilisant le format suivant (espaces interdits) : `hôte=adresse` - -Plus spécifiquement, une souscription associe un @hôte-unique-localement à une @adresse-base64. - -Exemple: - -``` -anonimal.i2p=AQZGLAMpI9Q0l0kmMj1vpJJYK3CjLp~fE3MfvE-e7KMKjI5cPOH6EN8m794uHJ6b09qM8mb9VEv1lVLEov~usVliTSXCSHuRBOCIwIOuDNU0AbVa4BpIx~2sU4TxKhoaA3zQ6VzINoduTdR2IJhPvI5xzezp7dR21CEQGGTbenDslXeQ4iLHFA2~bzp1f7etSl9T2W9RID-KH78sRQmzWnv7dbhNodMbpO6xsf1vENf6bMRzqD5vgHEHZu2aSoNuPyYxDU1eM6--61b2xp9mt1k3ud-5WvPVg89RaU9ugU5cxaHgR927lHMCAEU2Ax~zUb3DbrvgQBOTHnJEx2Fp7pOK~PnP6ylkYKQMfLROosLDXinxOoSKP0UYCh2WgIUPwE7WzJH3PiJVF0~WZ1dZ9mg00c~gzLgmkOxe1NpFRNg6XzoARivNVB5NuWqNxr5WKWMLBGQ9YHvHO1OHhUJTowb9X90BhtHnLK2AHwO6fV-iHWxRJyDabhSMj1kuYpVUBQAEAAcAAA== -``` - -1. `anonimal.i2p` est l'@hôte-unique-localement -2. `=` est le séparateur -3. Tout ce qu'il reste est l'@adresse-base64 - -### Types de souscriptions - -Pour @Kovri, il y a deux types de fichiers de souscriptions : *publique* et *privé*. - -Une souscription *publique* : -- est utilisée lors de l'amorçage pour utiliser les services essentiels (IRC, email, Monero, etc.) -- est statique et est mise à jour toutes les 12 heures depuis le serveur de @carnet-d'adresses de Monero -- vous permet de partager les souscriptions avec tout le monde car elle est publiquement disponible (quiconque partage la même souscription publique pourra également résoudre le même nom d'hôte vers la même destination que vous) - -Une souscription *privée* : -- est utilisée exclusivement par vous et n'est pas partagée avec d'autres à moins que vous ne choisissiez explicitement de partager le fichier -- le fichier par défaut est `private_hosts.txt` dans votre @répertoire-de-données - -### Mettre à jour une souscription privée - -Vous pouvez utiliser un @service-de-rebond pour mettre à jour manuellement votre souscription privée. La souscription mise à jour sera alors insérée dans votre @carnet-d'adresses pour que vous puissiez l'utiliser. - -### Remarque -Pour savoir comment souscrire à de multiples souscriptions, voir le [guide utilisateur](https://gitlab.com/kovri-project/kovri-docs/blob/master/i18n/fr/user_guide.md). diff --git a/_i18n/fr/resources/moneropedia/transports.md b/_i18n/fr/resources/moneropedia/transports.md deleted file mode 100644 index cf62c3ec..00000000 --- a/_i18n/fr/resources/moneropedia/transports.md +++ /dev/null @@ -1,18 +0,0 @@ ---- -tags: ["kovri"] -terms: ["Transports", "Transport"] -summary: "Les deux couches de transport chiffrées de Kovri" ---- - -### Les Bases - -@I2P contient deux technologies de couches de transport qui permettent à @Kovri d'utiliser des connexions [TCP/IP](https://fr.wikipedia.org/wiki/Tcp/ip) en toute sécurité. Ces technologies (@USS et @NTCP) sont appelées *@transports*. - -### Informations détaillées - -@USS est de l'[UDP](https://fr.wikipedia.org/wiki/User_Datagram_Protocol) chiffré et @NTCP est du [TCP](https://fr.wikipedia.org/wiki/Transmission_Control_Protocol) chiffré. Ils fournissent le @chiffrement de la [couche de transport](https://fr.wikipedia.org/wiki/Couche_transport) afin que les @messages de niveau supérieur puissent être envoyés à travers les @tunnels sur le réseau @I2P. - -### Remarques - -- Apprenez en plus à propos des transports d'@I2P sur la page [Transport](https://geti2p.net/fr/docs/transport) -- Apprenez en plus à propos de la couche de transport au sein du [modèle OSI](https://fr.wikipedia.org/wiki/Mod%C3%A8le_OSI) diff --git a/_i18n/fr/resources/moneropedia/tunnel.md b/_i18n/fr/resources/moneropedia/tunnel.md deleted file mode 100644 index 2610308b..00000000 --- a/_i18n/fr/resources/moneropedia/tunnel.md +++ /dev/null @@ -1,35 +0,0 @@ ---- -tags: ["kovri"] -terms: ["Tunnel", "Tunnels"] -summary: "Chemins virtuels unidirectionnels qui transmettent les messages à travers une séquence de routeurs I2P définie" ---- - -### Les Bases - -Lorsque vous communiquez sur @I2P (visitez un @site-eep ou utilisez un @service-en-ail), vous commencez par vous connecter à un homologue en utilisant les @transports puis vous construisez des *tunnels* virtuels. Ces tunnels virtuels sont des chemins temporaires et unidirectionnels qui transmettent l'information vers votre @destination à travers une séquence définie de routeurs @I2P. Les tunnels sont construits, puis utilisés, avec le @chiffrement-en-ail par couche et sont un mécanisme générique de transports de tous les @messages @I2NP. - -Chaque homologue construit, au minimum, *deux* tunnels unidirectionnels : un pour le **trafic sortant** et un pour le **trafic entrant**. Ces tunnels sont classés soit en tant que **tunnels entrants** (où les @messages arrivent en provenance du créateur du tunnel) ou en **tunnels sortants** (ou le créateur du tunnel envoie des @messages). Ainsi, *quatre* tunnels sont nécessaires pour un seul @message aller-retour et sa réponse à votre @destination (deux pour vous, deux pour votre destination). - -### Informations détaillées - -Traduit depuis @I2P-Java : - -> -Au sein d'I2P, les @messages sont transmis dans une direction à travers un tunnel virtuel d'homologues, en utilisant n'importe quel moyen disponible pour transmettre le @message au saut suivant. Les messages arrivent à la passerelle du tunnel, sont regroupés et/ou fragmentés en @messages de @tunnel à taille fixe, et sont transmis au prochain saut du tunnel, qui traite et vérifie la validité du @message et l'envoie au saut suivant, et ainsi de suite, jusqu'à ce qu'il atteigne le point de terminaison du @tunnel. Ce point de terminaison prend le message groupé par la passerelle et le transmet comme demandé, soit à un autre routeur, à un autre tunnel sur un autre routeur, ou localement. - -> -Les tunnels fonctionnent tous de la même façon, mais peuvent être classés en deux groupes différents : les tunnels entrants et les tunnels sortants. Les tunnels entrants ont une passerelle non approuvé qui transmet les messages jusqu'au créateur du tunnel, qui sert de point de terminaison du tunnel. Pour les tunnels sortants, le créateur du tunnel sert de passerelle, transmettant les messages vers le point de terminaison distant. - -> -Le créateur du tunnel choisit précisément quels homologues vont participer au tunnel, et fournit à chacun les données de configuration nécessaires. Ils peuvent avoir n'importe quel nombre de sauts. C'est dans le but de rendre difficile aux participants et tierces parties de déterminer la longueur d'un tunnel, ou même pour des participants connivents de déterminer s'ils font ou non partie du même tunnel (sauf en cas de connivence entre homologues côte à côte dans le tunnel). - -### Remarque - -Traduit depuis @I2P-Java : - -> -@I2P est intrinsèquement un réseau de commutation de paquet, même avec ces tunnels, permettant de tirer parti de multiples tunnels fonctionnant en parallèle en augmentant la résilience et la répartition de charge. Même si les tunnels au sein d'I2P se rapprochent d'un réseau à commutation de circuits, tout dans I2P est strictement basé sur les messages : les tunnels sont principalement des astuces de comptabilité qui aident à organiser la transmission des messages. Aucune hypothèse n'est faite quant à la fiabilité ou l'ordonnancement des messages, et le soin des retransmissions est laissé aux couches supérieures (p.ex. la librairie de diffusion de la couche client d'I2P). - -### Documentation - -Pour les spécifications et la documentation détaillée, rendez-vous sur les pages [Tunnel-Routing](https://geti2p.net/fr/docs/how/tunnel-routing) et [Tunnel-Implementation](https://geti2p.net/en/docs/tunnels/implementation). diff --git a/_i18n/it/resources/moneropedia/base32-address.md b/_i18n/it/resources/moneropedia/base32-address.md deleted file mode 100644 index 0e3a88e2..00000000 --- a/_i18n/it/resources/moneropedia/base32-address.md +++ /dev/null @@ -1,26 +0,0 @@ ---- -tags: ["kovri"] -terms: ["Base32-address", "Base32-addresses"] -summary: "Base32 encoded hash of a Base64 address" ---- - -{% include untranslated.html %} -### The Basics - -A Base32 address is a shortened, encoded version of an @I2P address. The Base32 address is the first part in a `.b32.i2p` hostname. - -Example: - -`i35yftyyb22xhcvghmev46t5knefur5v66qzekkajatwfwhyklvq.b32.i2p` - -where - -`i35yftyyb22xhcvghmev46t5knefur5v66qzekkajatwfwhyklvq` is the Base32 address. - -### In-depth Information - -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. - -### Notes - -**Note: `.b32` is not a sub-domain of `.i2p`** diff --git a/_i18n/it/resources/moneropedia/base64-address.md b/_i18n/it/resources/moneropedia/base64-address.md deleted file mode 100644 index b9985658..00000000 --- a/_i18n/it/resources/moneropedia/base64-address.md +++ /dev/null @@ -1,21 +0,0 @@ ---- -tags: ["kovri"] -terms: ["Base64-address", "Base64-addresses"] -summary: "Base64 encoded I2P destination" ---- - -{% include untranslated.html %} -### The Basics - -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: - -``` -AQZGLAMpI9Q0l0kmMj1vpJJYK3CjLp~fE3MfvE-e7KMKjI5cPOH6EN8m794uHJ6b09qM8mb9VEv1lVLEov~usVliTSXCSHuRBOCIwIOuDNU0AbVa4BpIx~2sU4TxKhoaA3zQ6VzINoduTdR2IJhPvI5xzezp7dR21CEQGGTbenDslXeQ4iLHFA2~bzp1f7etSl9T2W9RID-KH78sRQmzWnv7dbhNodMbpO6xsf1vENf6bMRzqD5vgHEHZu2aSoNuPyYxDU1eM6--61b2xp9mt1k3ud-5WvPVg89RaU9ugU5cxaHgR927lHMCAEU2Ax~zUb3DbrvgQBOTHnJEx2Fp7pOK~PnP6ylkYKQMfLROosLDXinxOoSKP0UYCh2WgIUPwE7WzJH3PiJVF0~WZ1dZ9mg00c~gzLgmkOxe1NpFRNg6XzoARivNVB5NuWqNxr5WKWMLBGQ9YHvHO1OHhUJTowb9X90BhtHnLK2AHwO6fV-iHWxRJyDabhSMj1kuYpVUBQAEAAcAAA== -``` - - -### In-depth Information - -See @destination for details behind @base64-address diff --git a/_i18n/it/resources/moneropedia/data-directory.md b/_i18n/it/resources/moneropedia/data-directory.md deleted file mode 100644 index 761cfd46..00000000 --- a/_i18n/it/resources/moneropedia/data-directory.md +++ /dev/null @@ -1,21 +0,0 @@ ---- -tags: ["kovri"] -terms: ["Data-Directory"] -summary: "Where essential kovri data for runtime is stored" ---- - -{% include untranslated.html %} -### The Basics - -Depending on your OS, @Kovri currently stores all run-time data in the following directory: - -- Linux/FreeBSD: - - `$HOME/.kovri` - -- OSX: - - `$HOME/Library/Application\ Support/Kovri` - -- Windows: - - `"$APPDATA"\\Kovri` - -This includes all configuration files, @address-book, certificates, and resources. diff --git a/_i18n/it/resources/moneropedia/eepsite.md b/_i18n/it/resources/moneropedia/eepsite.md deleted file mode 100644 index cd450d97..00000000 --- a/_i18n/it/resources/moneropedia/eepsite.md +++ /dev/null @@ -1,29 +0,0 @@ ---- -tags: ["kovri"] -terms: ["Eepsite", "Hidden-Service", "Garlic-Site", "Garlic-Service"] -summary: "A website or service hosted within the I2P network" ---- - -{% include untranslated.html %} -### The Basics - -Is it [**EEP!** *(in response to the site's content)*](https://en.wikipedia.org/wiki/Onomatopoeia), or **end-to-end protocol**, or something else entirely different? - -While the original definition of eepsite has been lost with time, its use-case remains: an eepsite is a website or service that is hosted within (and only accessible by) the @I2P network. - -### In-depth Information - -Alternate names include: - -1. *Hidden Service* - - because the site/service is *hidden* within the @I2P network and can only be visited within the network -2. *Garlic Site* - - because the website utilizes @I2P's @garlic-routing technology as a means of communicating with a client - - because the service is hosted as a website and not any other type of service -3. *Garlic Service* - - because the service utilizes @I2P's @garlic-routing technology as a means of communicating with a client - - because the service is specific to services like IRC, email, or a Monero peer (but may also include websites) - -### Notes - -To learn how to setup an Eepsite (Hidden Service, Garlic Site, Garlic Service) visit the @Kovri [user-guide](https://gitlab.com/kovri-project/kovri-docs/blob/master/i18n/en/user_guide.md). diff --git a/_i18n/it/resources/moneropedia/floodfill.md b/_i18n/it/resources/moneropedia/floodfill.md deleted file mode 100644 index cccd9011..00000000 --- a/_i18n/it/resources/moneropedia/floodfill.md +++ /dev/null @@ -1,14 +0,0 @@ ---- -tags: ["kovri"] -terms: ["Floodfill"] -summary: "An I2P router which maintains a distributed network-database" ---- - -{% include untranslated.html %} -### The Basics - -By actively managing a distributed network-database, a router with *floodfill* capability has the ability to help maintain network stability and resiliancy while also being decentralized and trust-less. - -### In-depth information - -Though floodfill itself is a simple storage system, the technical underpinnings of floodfill as it relates to @network-database and other protocols within @I2P are much more complex. Visit the [Network Database](https://geti2p.net/en/docs/how/network-database) page for details. diff --git a/_i18n/it/resources/moneropedia/garlic-encryption.md b/_i18n/it/resources/moneropedia/garlic-encryption.md deleted file mode 100644 index a0548b3c..00000000 --- a/_i18n/it/resources/moneropedia/garlic-encryption.md +++ /dev/null @@ -1,24 +0,0 @@ ---- -tags: ["kovri"] -terms: ["Garlic-Encryption", "Layered-Encryption"] -summary: "Layered encryption as implemented in Kovri / I2P" ---- - -{% include untranslated.html %} -### The Basics - -@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 - -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. diff --git a/_i18n/it/resources/moneropedia/garlic-routing.md b/_i18n/it/resources/moneropedia/garlic-routing.md deleted file mode 100644 index 4a1d26b9..00000000 --- a/_i18n/it/resources/moneropedia/garlic-routing.md +++ /dev/null @@ -1,44 +0,0 @@ ---- -tags: ["kovri"] -terms: ["Garlic-Routing"] -summary: "Routing technology as implemented in Kovri" ---- - -{% include untranslated.html %} -### 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. - -The @Garlic-Encryption of @Garlic-Routing is similar to the @Layered-Encryption of [Onion Routing](https://en.wikipedia.org/wiki/Onion_routing) and effectively conceals the IP address of the sender and secures information sent from the sender to its @destination (and vice-versa). - -### 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](http://www.freehaven.net/papers.html) (Section 8.1.1) as derived from the term Onion Routing. - -As recent as October of 2016, [#tor-dev](https://oftc.net/WebChat/) has offered insight into the creation of the term *@garlic-routing*: - -[Nick Mathewson](https://en.wikipedia.org/wiki/The_Tor_Project,_Inc): ->[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](https://en.wikipedia.org/wiki/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 was 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 (similar to the @layered-encryption in Onion Routing) -- Bundling multiple @messages together (garlic cloves) -- ElGamal/AES @encryption - -*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 - -- In terms of Onion/Garlic Routing, another way to envision layered @encryption is by replacing the onion/garlic with a [Matryoshka doll](https://en.wikipedia.org/wiki/Matryoshka_doll) - with each outer/inner doll having a lock and public key to the next/previous doll -- For more technical details on Garlic Routing, read the @Java-I2P entry on [Garlic Routing](https://geti2p.net/en/docs/how/garlic-routing) diff --git a/_i18n/it/resources/moneropedia/i2np.md b/_i18n/it/resources/moneropedia/i2np.md deleted file mode 100644 index 1e7841ae..00000000 --- a/_i18n/it/resources/moneropedia/i2np.md +++ /dev/null @@ -1,27 +0,0 @@ ---- -tags: ["kovri"] -terms: ["I2NP"] -summary: "The I2P Network Protocol: the mechanism in which I2NP messages are sent over the I2P network" ---- - -{% include untranslated.html %} -### The Basics - -From @Java-I2P: - -> -@I2NP manages the routing and mixing of messages between routers, as well as the selection of what transports to use when communicating with a peer for which there are multiple common transports supported - -### In-depth information - -From @Java-I2P: - -> -@I2NP (@I2P Network Protocol) @messages can be used for one-hop, router-to-router, point-to-point @messages. By @encrypting and wrapping @messages in other @messages, they can be sent in a secure way through multiple hops to the ultimate @destination. @I2NP does not specify nor require any particular @transport layer but does require at least one @transport in use. - -> -Whenever a @destination wants to send a message to to another @destination, it provides its local router with both the @destination structure and the raw bytes of the message to be sent. The router then determines where to send it, delivers it through outbound @tunnels, instructing the end point to pass it along to the appropriate inbound @tunnel, where it is passed along again to that @tunnel's end point and made available to the target for reception. - -### Notes - -Read more about the @I2NP [protocol](https://geti2p.net/en/docs/protocol/i2np) and [specification](https://geti2p.net/spec/i2np). diff --git a/_i18n/it/resources/moneropedia/i2p.md b/_i18n/it/resources/moneropedia/i2p.md deleted file mode 100644 index 7a6980c3..00000000 --- a/_i18n/it/resources/moneropedia/i2p.md +++ /dev/null @@ -1,30 +0,0 @@ ---- -tags: ["kovri"] -terms: ["I2P"] -summary: "The Invisible Internet Project: an anonymizing overlay network" ---- - -{% include untranslated.html %} -### Monero - -For Monero's implementation of @I2P, see @Kovri. For a comparison of @I2P to [Tor](https://torproject.org/), read the [Comparison](https://geti2p.net/en/comparison/tor) page. - -### The Basics - -From @Java-I2P: - ->The I2P network provides strong privacy protections for communication over the Internet. Many activities that would risk your privacy on the public Internet can be conducted anonymously inside I2P. - -### In-depth information - -From @Java-I2P: - ->I2P is an anonymous overlay network - a network within a network. It is intended to protect communication from dragnet surveillance and monitoring by third parties such as ISPs. - ->I2P is used by many people who care about their privacy: activists, oppressed people, journalists and whistleblowers, as well as the average person. - ->No network can be "perfectly anonymous". The continued goal of I2P is to make attacks more and more difficult to mount. Its anonymity will get stronger as the size of the network increases and with ongoing academic review. - -### Notes - -@I2P documentation and specifications are available [here](https://geti2p.net/docs/). diff --git a/_i18n/it/resources/moneropedia/i2pcontrol.md b/_i18n/it/resources/moneropedia/i2pcontrol.md deleted file mode 100644 index b419423c..00000000 --- a/_i18n/it/resources/moneropedia/i2pcontrol.md +++ /dev/null @@ -1,16 +0,0 @@ ---- -tags: ["kovri"] -terms: ["I2PControl"] -summary: "An API inteface for Kovri and Java-I2P that allows simple remote control" ---- - -{% include untranslated.html %} -### The Basics - -@I2Pcontrol is a [JSONRPC2](https://en.wikipedia.org/wiki/JSON-RPC) [API](https://en.wikipedia.org/wiki/Application_programming_interface) for @Kovri and @Java-I2P which allows an @I2PControl client to remote control/monitor a running instance. - -Two available @I2PControl clients are: [qtoopie](https://github.com/EinMByte/qtoopie) (C++ client) and [itoopie](https://github.com/i2p/i2p.itoopie) (Java client). Read `kovri.conf` to configure @I2PControl for @Kovri. - -### In-depth information - -Details and specification available on the [I2PControl](https://geti2p.net/en/docs/api/i2pcontrol) page. diff --git a/_i18n/it/resources/moneropedia/in-net.md b/_i18n/it/resources/moneropedia/in-net.md deleted file mode 100644 index ec3c5c8a..00000000 --- a/_i18n/it/resources/moneropedia/in-net.md +++ /dev/null @@ -1,14 +0,0 @@ ---- -tags: ["kovri"] -terms: ["In-net"] -summary: "Within the I2P network" ---- - -{% include untranslated.html %} -### The Basics - -**In-net** is a [colloquial](https://en.wikipedia.org/wiki/Colloquial) term of which describes activities, protocols, or functionality that exist *only* within the @I2P network. - -### In-depth information - -Example: *in-net download* would be defined as downloading *only* within @I2P. diff --git a/_i18n/it/resources/moneropedia/java-i2p.md b/_i18n/it/resources/moneropedia/java-i2p.md deleted file mode 100644 index 8a21da5d..00000000 --- a/_i18n/it/resources/moneropedia/java-i2p.md +++ /dev/null @@ -1,14 +0,0 @@ ---- -tags: ["kovri"] -terms: ["Java-I2P"] -summary: "The original implementation of I2P - written in Java" ---- - -{% include untranslated.html %} -### The Basics - -The term "Java I2P" is often used to describe the original @I2P implementation currently most known and used today. There are various other @I2P implementations, including @Kovri; all of which look up to the original Java implementation. - -### Notes - -To download/learn more about the Java implementation, visit their [website](https://geti2p.net/). diff --git a/_i18n/it/resources/moneropedia/jump-service.md b/_i18n/it/resources/moneropedia/jump-service.md deleted file mode 100644 index a62c5276..00000000 --- a/_i18n/it/resources/moneropedia/jump-service.md +++ /dev/null @@ -1,33 +0,0 @@ ---- -tags: ["kovri"] -terms: ["Jump-Service"] -summary: "An I2P website service that adds addresses to your address book" ---- - -{% include untranslated.html %} -### The Basics - -In your @I2P configured web browser, you can use a Jump Service to *jump* to an @I2P address that you don't have in your @address-book. Once you've *jumped* to the address, the address will be saved into your @address-book. - -### In-depth Information - -In an @I2P configured browser, visit: http://stats.i2p/i2p/lookup.html (courtesy of @Java-I2P's lead developer *zzz*) - -Then, you'll have two options: - -1. *Hostname lookup* the address you wish to visit and then manually copy/paste the result -2. *Jump* to the @I2P website by entering the @I2P hostname (**recommended**) - -### Using hostname lookup - -For example, entering `pinkpaste.i2p` into the *Hostname lookup* box (and then submitting) will return: - -``` -pinkpaste.i2p=m-HrPrIAsdxts0WM~P4mE8mt9P7g-QTaBvu7Gc6Nl0UX7Vwck-i~RvOPfK6W~kfdRvwhNTqevkBL2UF5l36We02Aiywu7kB2xOHRkze68h-Tg2ewvRVwokohguCD2G3wwAEz~7FVda2avYDCb9-N6TfuzxKLnmhPMvbNSjGL7ZsD2p-h207R3-2kvuMV9bfu-K~w9NI9XJhIyufvUnFYc2jnTVg8PbaR4UP57cNaOO2YIMPkbr6~yTcIu9B1sUfHK6-N~6virQDOxW4M-62rjnZkLpaCtkOsXslmCwZI--TkZ6hKi1kXZvNmJRE1rYfffYRFn38zhaqszeETX8HiIvahZhXF5fNumBziYdmLdw8hkuN1A~emU6Xz9g~a1Ixfsq1Qr~guYoOtaw-0rOFxNRS9yMehE-2LCb8c-cAg6z5OdlN4qJDl~ZHgru4d~EHp~BpAK3v7u2Gi-8l1ygVW-1CHVna~fwnbOPN3ANPwh6~~yUit0Cx1f54XiNRn6-nPBQAEAAcAAA== -``` - -Copy/paste this host=@base64-address pairing into your **private** @subscription. - -### Directly jumping - -For example, entering `pinkpaste.i2p` into the *Jump* box (and then submitting) will automatically redirect you to the website **and** insert the @locally-unique-host into @address-book. diff --git a/_i18n/it/resources/moneropedia/lease-set.md b/_i18n/it/resources/moneropedia/lease-set.md deleted file mode 100644 index 412f2005..00000000 --- a/_i18n/it/resources/moneropedia/lease-set.md +++ /dev/null @@ -1,24 +0,0 @@ ---- -tags: ["kovri"] -terms: ["LeaseSet", "LeaseSets"] -summary: "Contains all currently authorized Leases for a particular I2P Destination" ---- - -{% include untranslated.html %} -### The Basics - -A Lease-Set contains a set of authorized @leases (and other related information) for a particular @destination. - -### In-depth information - -A Lease-Set contains: - -- all of the currently authorized @leases for a particular @destination -- the public key to which garlic messages can be encrypted (see @garlic-routing) -- the signing public key that can be used to revoke this particular version of the structure - -The Lease-Set is one of the two structures stored in the @network-database (the other being @router-info), and is keyed under the SHA256 of the contained @destination. - -### Notes - -For further details, read @Java-I2P's [LeaseSet](https://geti2p.net/en/docs/how/network-database#leaseSet) diff --git a/_i18n/it/resources/moneropedia/lease.md b/_i18n/it/resources/moneropedia/lease.md deleted file mode 100644 index cfb13659..00000000 --- a/_i18n/it/resources/moneropedia/lease.md +++ /dev/null @@ -1,14 +0,0 @@ ---- -tags: ["kovri"] -terms: ["Lease", "Leases"] -summary: "Authorizes an I2P tunnel to receive messages targeting a destination" ---- - -{% include untranslated.html %} -### The Basics - -A lease defines the authorization for a particular @I2P @tunnel to receive a @messages targeting a @destination. - -### In-depth information - -For further details, read @Java-I2P's [Lease](https://geti2p.net/spec/common-structures#lease) diff --git a/_i18n/it/resources/moneropedia/message.md b/_i18n/it/resources/moneropedia/message.md deleted file mode 100644 index 975277a3..00000000 --- a/_i18n/it/resources/moneropedia/message.md +++ /dev/null @@ -1,32 +0,0 @@ ---- -tags: ["kovri"] -terms: ["Message", "Messages"] -summary: "The mechanisms in which information travels within I2P" ---- - -{% include untranslated.html %} -### The Basics - -*Messages* (which exist on top of the @transports layer), contain varying types of information that are needed for the network but, most importantly, everything you see, do, send, or receive, will come and go in the form of *messages*. - -There are 2 essential types of *messages* in @I2P: - -- @Tunnel messages -- @I2NP messages - -Essentially: *@tunnel messages* **contain** @I2NP **message fragments** which are then [reassembled](https://geti2p.net/en/docs/tunnels/implementation) at certain points within a @tunnel's path. - -### In-depth information - -@I2NP messages have a close relationship with @tunnel @messages so it is easy to get the term *messages* confused when reading @Java-I2P specifications: - -> -1. First, the tunnel gateway accumulates a number of I2NP messages and preprocesses them into tunnel messages for delivery. -2. Next, that gateway encrypts that preprocessed data, then forwards it to the first hop. -3. That peer, and subsequent tunnel participants, unwrap a layer of the encryption, verifying that it isn't a duplicate, then forward it on to the next peer. -4. Eventually, the tunnel messages arrive at the endpoint where the I2NP messages originally bundled by the gateway are reassembled and forwarded on as requested. - -### Notes - -- @I2NP @messages need to be fragmented because they are variable in size (from 0 to almost 64 KB) and @tunnel @messages are fixed-size (approximately 1 KB). -- For details and specifications, visit the [I2NP spec](https://geti2p.net/spec/i2np) and [Tunnel Message spec](https://geti2p.net/spec/tunnel-message) diff --git a/_i18n/it/resources/moneropedia/network-database.md b/_i18n/it/resources/moneropedia/network-database.md deleted file mode 100644 index ac94231a..00000000 --- a/_i18n/it/resources/moneropedia/network-database.md +++ /dev/null @@ -1,24 +0,0 @@ ---- -tags: ["kovri"] -terms: ["Network-Database"] -summary: "A distributed database which contains needed router information so the network can stay intact" ---- - -{% include untranslated.html %} -### The Basics - -@network-database is a [distributed database](https://en.wikipedia.org/wiki/Distributed_database) which contains router information that peers must use so the network can stay intact. - -### In-depth information - -From @Java-I2P: - -> -@I2P's @network-database is a specialized distributed database, containing just two types of data - router contact information (@Router-Infos) and @destination contact information (@LeaseSets). Each piece of data is signed by the appropriate party and verified by anyone who uses or stores it. In addition, the data has liveliness information within it, allowing irrelevant entries to be dropped, newer entries to replace older ones, and protection against certain classes of attack. - -> -The @network-database is distributed with a simple technique called "@floodfill", where a subset of all routers, called "@floodfill routers", maintains the distributed database. - -### Notes - -Read [Network-Database](https://geti2p.net/en/docs/how/network-database) for details. diff --git a/_i18n/it/resources/moneropedia/ntcp.md b/_i18n/it/resources/moneropedia/ntcp.md deleted file mode 100644 index 4c3f68b2..00000000 --- a/_i18n/it/resources/moneropedia/ntcp.md +++ /dev/null @@ -1,33 +0,0 @@ ---- -tags: ["kovri"] -terms: ["NTCP"] -summary: "NIO-Based TCP (Non-blocking I/O based TCP): one of two Kovri transports" ---- - -{% include untranslated.html %} -### The Basics - -*NIO-Based TCP (Non-blocking I/O based TCP)* is one of two encrypted @transports for @Kovri. - -Similar to @SSU, @NTCP's *primary* purpose is to securely transmit @in-net @I2NP messages through @tunnels but, unlike @SSU, @NTCP functions solely over encrypted [TCP](https://en.wikipedia.org/wiki/Transmission_Control_Protocol). - -### In-depth information - - - Passes along individual @I2NP messages (both Standard and Time Sync) after: - - TCP has been established - - Establishment Sequence has been completed - - Uses the following @encryption: - - 2048-bit [Diffie-Hellman](https://en.wikipedia.org/wiki/Diffie-hellman) - - [AES-256](https://en.wikipedia.org/wiki/Advanced_Encryption_Standard)/[CBC](https://en.wikipedia.org/wiki/Block_cipher_modes_of_operation) - - Establishment Sequence has the following *states*: - - Pre-establishment - - Establishment - - Post-establishment or "Established" - - Uses the following from the @network-database: - - Transport name: NTCP - - Host: IP (IPv4 or IPv6) or host name (shortened IPv6 address (with "::") is allowed) - - Port: 1024 - 65535 - -### Notes - -For further details, read @Java-I2P's [NTCP](https://geti2p.net/en/docs/transport/ntcp) diff --git a/_i18n/it/resources/moneropedia/reseed.md b/_i18n/it/resources/moneropedia/reseed.md deleted file mode 100644 index 179f34c5..00000000 --- a/_i18n/it/resources/moneropedia/reseed.md +++ /dev/null @@ -1,16 +0,0 @@ ---- -tags: ["kovri"] -terms: ["Reseed"] -summary: "The method of which Kovri uses to bootstrap into the I2P network" ---- - -{% include untranslated.html %} -### The Basics - -When you start @Kovri for the first time (or if it's been offline for a long time), @Kovri will need a list of peers to connect to so it can [bootstrap](https://en.wikipedia.org/wiki/Bootstrap) into the @I2P network. @Kovri gets these peers from a special file stored on a reseed server. On this file are all the various pieces of information @Kovri needs in order to connect with @I2P peers. - -### In-depth information - -@Kovri has a list of [hard-coded](https://en.wikipedia.org/wiki/Hard-coded) reseed servers available to fetch from. These servers securely serve an [SU3](https://geti2p.net/spec/updates#su3) file (signed with a cryptographic @signature) over @clearnet with [HTTPS](https://en.wikipedia.org/wiki/HTTPS). This SU3 file contains information that's used to verify both the integrity of the file and its content. - -Aside from the technical elements needed to verify and process the file, the file's main contents consist of a series of @router-info files which @Kovri and @I2P routers use to locate and communicate with other @I2P peers. These peers are then stored into a @network-database. diff --git a/_i18n/it/resources/moneropedia/router-info.md b/_i18n/it/resources/moneropedia/router-info.md deleted file mode 100644 index cb190f9d..00000000 --- a/_i18n/it/resources/moneropedia/router-info.md +++ /dev/null @@ -1,67 +0,0 @@ ---- -tags: ["kovri"] -terms: ["Router-Info", "Router-infos"] -summary: "A data structure or file which contains an I2P peer's needed network information" ---- - -{% include untranslated.html %} -### The Basics - -@Router-Info is a data structure (periodically written to a [binary file](https://en.wikipedia.org/wiki/Binary_file)) which contains all needed information to locate, identify, and communicate with an @I2P peer. @Router-Info includes IP address, router identity, other misc. technical details; is needed for @network-database and is published to @floodfill routers. - -### In-depth information - -In human-readable form, Router-Info may look like this: - -``` -Identity: [RouterIdentity: -Hash: nYZ5Qe7gQ-~QgfgJVRUG4c0JnVeVqzM~duUX1EGT1ek= -Certificate: [Certificate: type: Key certificate -Crypto type: 0 -Sig type: 7 (EdDSA_SHA512_Ed25519)] -PublicKey: [PublicKey: size: 256] -SigningPublicKey: [SigningPublicKey EdDSA_SHA512_Ed25519: size: 32] -Padding: 96 bytes] -Signature: [Signature EdDSA_SHA512_Ed25519: size: 64] -Published: Sun Oct 09 01:34:59 UTC 2016 -Options (5): - [caps] = [LfR] - [netId] = [2] - [netdb.knownLeaseSets] = [37] - [netdb.knownRouters] = [2435] - [router.version] = [0.9.26] -Addresses (4): -[RouterAddress: -Type: SSU -Cost: 4 -Options (5): - [caps] = [BC] - [host] = [2a01:e35:8b5c:b240:71a2:6750:8d4:47fa] - [key] = [nYZ5Qe7gQ-~QgfgJVRUG4c0JnVeVqzM~duUX1EGT1ek=] - [mtu] = [1472] - [port] = [22244]] -[RouterAddress: -Type: NTCP -Cost: 9 -Options (2): - [host] = [2a01:e35:8b5c:b240:71a2:6750:8d4:47fa] - [port] = [22244]] -[RouterAddress: -Type: SSU -Cost: 6 -Options (4): - [caps] = [BC] - [host] = [88.181.203.36] - [key] = [nYZ5Qe7gQ-~QgfgJVRUG4c0JnVeVqzM~duUX1EGT1ek=] - [port] = [22244]] -[RouterAddress: -Type: NTCP -Cost: 11 -Options (2): - [host] = [88.181.203.36] - [port] = [22244]]] -``` - -### Notes - -For details and specification, visit @Java-I2P [Network Database](https://geti2p.net/en/docs/how/network-database) page. diff --git a/_i18n/it/resources/moneropedia/ssu.md b/_i18n/it/resources/moneropedia/ssu.md deleted file mode 100644 index cbdadfdc..00000000 --- a/_i18n/it/resources/moneropedia/ssu.md +++ /dev/null @@ -1,25 +0,0 @@ ---- -tags: ["kovri"] -terms: ["SSU"] -summary: "Secure Semi-reliable UDP: one of two Kovri transports" ---- - -{% include untranslated.html %} -### The Basics - -*Secure Semi-reliable UDP* is one of two encrypted @transports for @Kovri. - -Similar to @NTCP, @SSU's *primary* purpose is to securely transmit @in-net @I2NP messages through @tunnels but, unlike @NTCP, @SSU functions solely over encrypted [UDP](https://en.wikipedia.org/wiki/User_Datagram_Protocol). - -### In-depth information - -- Like @NTCP, @SSU is a connection-oriented, point-to-point data transport -- Termed *semi-reliable* because @SSU will repeatedly retransmit *unacknowledged* messages (up to maximum number then dropped) -- @SSU also provides several unique services (in addition to its function as a @transport layer): - - IP detection (local inspection or with [peer testing](https://geti2p.net/en/docs/transport/ssu#peerTesting)) - - [NAT](https://en.wikipedia.org/wiki/Network_address_translation) traversal (using [introducers](https://geti2p.net/en/docs/transport/ssu#introduction)) - - [Firewall](https://en.wikipedia.org/wiki/Firewall_%28computing%29) status and, if implemented, @SSU can notify @NTCP if the external address or firewall status changes - -### Notes - -For further details, read @Java-I2P's [SSU](https://geti2p.net/en/docs/transport/ssu) diff --git a/_i18n/it/resources/moneropedia/subscription.md b/_i18n/it/resources/moneropedia/subscription.md deleted file mode 100644 index bfb4b0bc..00000000 --- a/_i18n/it/resources/moneropedia/subscription.md +++ /dev/null @@ -1,46 +0,0 @@ ---- -tags: ["kovri"] -terms: ["Subscription"] -summary: "A file used by address book which contains I2P hosts paired with I2P destinations" ---- - -{% include untranslated.html %} -### The Basics - -A subscription is a file which contains a list of `.i2p` hosts paired with their respective @destination. Subscriptions are used by the @address-book. - -### In-depth information - -Similar to how a [hosts file](https://en.wikipedia.org/wiki/Hosts_(file)) can map an internet hostname to a specified address, a subscription matches a `.i2p` address to @base64-address by using the following format (no spaces allowed): `host=address` - -More specifically, a subscription pairs a @locally-unique-host to @base64-address. - -Example: - -``` -anonimal.i2p=AQZGLAMpI9Q0l0kmMj1vpJJYK3CjLp~fE3MfvE-e7KMKjI5cPOH6EN8m794uHJ6b09qM8mb9VEv1lVLEov~usVliTSXCSHuRBOCIwIOuDNU0AbVa4BpIx~2sU4TxKhoaA3zQ6VzINoduTdR2IJhPvI5xzezp7dR21CEQGGTbenDslXeQ4iLHFA2~bzp1f7etSl9T2W9RID-KH78sRQmzWnv7dbhNodMbpO6xsf1vENf6bMRzqD5vgHEHZu2aSoNuPyYxDU1eM6--61b2xp9mt1k3ud-5WvPVg89RaU9ugU5cxaHgR927lHMCAEU2Ax~zUb3DbrvgQBOTHnJEx2Fp7pOK~PnP6ylkYKQMfLROosLDXinxOoSKP0UYCh2WgIUPwE7WzJH3PiJVF0~WZ1dZ9mg00c~gzLgmkOxe1NpFRNg6XzoARivNVB5NuWqNxr5WKWMLBGQ9YHvHO1OHhUJTowb9X90BhtHnLK2AHwO6fV-iHWxRJyDabhSMj1kuYpVUBQAEAAcAAA== -``` - -1. `anonimal.i2p` is the @locally-unique-host -2. `=` is the separator -3. Everything that remains is the @base64-address - -### Subscription types - -For @Kovri, there are two types of subscription files: *public* and *private*. - -A *public* subscription: -- is used when bootstrapping to use essential services (IRC, email, Monero, etc.) -- is static and is refreshed every 12 hours from Monero's @address-book server -- allows you to safely share the subscription with everyone as it is publically available (anyone who shares the same public subscription will also be able to resolve the same hostname to the same destination as you) - -A *private* subscription: -- is used exclusively by you and is not shared with others unless you explicitly choose to share the file -- default file is `private_hosts.txt` in your @data-directory - -### Updating a private subscription - -You can use a @jump-service to manually update your private subscription. The updated subscription will then be fed into the @address-book for you to use. - -### Notes -To learn how to subscribe to multiple subscriptions, see the [user-guide](https://gitlab.com/kovri-project/kovri-docs/blob/master/i18n/en/user_guide.md). diff --git a/_i18n/it/resources/moneropedia/transports.md b/_i18n/it/resources/moneropedia/transports.md deleted file mode 100644 index b1471cd6..00000000 --- a/_i18n/it/resources/moneropedia/transports.md +++ /dev/null @@ -1,19 +0,0 @@ ---- -tags: ["kovri"] -terms: ["Transports", "Transport"] -summary: "The two encrypted transport layers for Kovri" ---- - -{% include untranslated.html %} -### The Basics - -@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 - -@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 @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) diff --git a/_i18n/it/resources/moneropedia/tunnel.md b/_i18n/it/resources/moneropedia/tunnel.md deleted file mode 100644 index a9ebfaaa..00000000 --- a/_i18n/it/resources/moneropedia/tunnel.md +++ /dev/null @@ -1,36 +0,0 @@ ---- -tags: ["kovri"] -terms: ["Tunnel", "Tunnels"] -summary: "Uni-directional virtual paths that pass messages through a defined sequence of I2P routers" ---- - -{% include untranslated.html %} -### The Basics - -When you communicate over @I2P (visit an @eepsite / use a @garlic-service), you'll first need to connect to a peer by using @transports and then build virtual *tunnels*. These virtual tunnels are temporary, uni-directional paths that pass information through a defined sequence of @I2P routers to your @destination. Tunnels are built, and then used, with layered @garlic-encryption and are a general-purpose mechanism to transport all @I2NP @messages. - -Each peer builds, at a minimum, *two* uni-directional tunnels: one for **outbound traffic**, and one for **inbound traffic**. These tunnels are classified as either **inbound tunnels** (where @messages come toward the creator of the tunnel) or **outbound tunnels** (where the tunnel creator sends @messages away from the creator of the tunnel). Thus, *four* tunnels are required for a single round-trip @message and reply to your @destination (two for your, two for your destination). - -### In-depth information - -From @Java-I2P: - -> -Within I2P, @messages are passed in one direction through a virtual tunnel of peers, using whatever means are available to pass the @message on to the next hop. Messages arrive at the tunnel's gateway, get bundled up and/or fragmented into fixed-size @tunnel @messages, and are forwarded on to the next hop in the tunnel, which processes and verifies the validity of the @message and sends it on to the next hop, and so on, until it reaches the @tunnel endpoint. That endpoint takes the messages bundled up by the gateway and forwards them as instructed - either to another router, to another tunnel on another router, or locally. - -> -Tunnels all work the same, but can be segmented into two different groups - inbound tunnels and outbound tunnels. The inbound tunnels have an untrusted gateway which passes messages down towards the tunnel creator, which serves as the tunnel endpoint. For outbound tunnels, the tunnel creator serves as the gateway, passing messages out to the remote endpoint. - -> -The tunnel's creator selects exactly which peers will participate in the tunnel, and provides each with the necessary configuration data. They may have any number of hops. It is the intent to make it hard for either participants or third parties to determine the length of a tunnel, or even for colluding participants to determine whether they are a part of the same tunnel at all (barring the situation where colluding peers are next to each other in the tunnel). - -### Notes - -From @Java-I2P: - -> -@I2P is an inherently packet switched network, even with these tunnels, allowing it to take advantage of multiple tunnels running in parallel, increasing resilience and balancing load. Even though the tunnels within I2P bear a resemblance to a circuit switched network, everything within I2P is strictly message based - tunnels are merely accounting tricks to help organize the delivery of messages. No assumptions are made regarding reliability or ordering of messages, and retransmissions are left to higher levels (e.g. I2P's client layer streaming library). - -### Documentation - -For specification and detailed documentation, visit the [Tunnel-Routing](https://geti2p.net/en/docs/how/tunnel-routing) and [Tunnel-Implementation](https://geti2p.net/en/docs/tunnels/implementation) page. diff --git a/_i18n/nl/resources/moneropedia/base32-address.md b/_i18n/nl/resources/moneropedia/base32-address.md deleted file mode 100644 index 9737f7c0..00000000 --- a/_i18n/nl/resources/moneropedia/base32-address.md +++ /dev/null @@ -1,25 +0,0 @@ ---- -tags: ["kovri"] -terms: ["Base32-address", "Base32-addresses"] -summary: "Base32 encoded hash of a Base64 address" ---- - -### The Basics - -A Base32 address is a shortened, encoded version of an @I2P address. The Base32 address is the first part in a `.b32.i2p` hostname. - -Example: - -`i35yftyyb22xhcvghmev46t5knefur5v66qzekkajatwfwhyklvq.b32.i2p` - -where - -`i35yftyyb22xhcvghmev46t5knefur5v66qzekkajatwfwhyklvq` is the Base32 address. - -### In-depth Information - -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. - -### Notes - -**Note: `.b32` is not a sub-domain of `.i2p`** diff --git a/_i18n/nl/resources/moneropedia/base64-address.md b/_i18n/nl/resources/moneropedia/base64-address.md deleted file mode 100644 index 56a0589a..00000000 --- a/_i18n/nl/resources/moneropedia/base64-address.md +++ /dev/null @@ -1,20 +0,0 @@ ---- -tags: ["kovri"] -terms: ["Base64-address", "Base64-addresses"] -summary: "Base64 encoded I2P destination" ---- - -### The Basics - -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: - -``` -AQZGLAMpI9Q0l0kmMj1vpJJYK3CjLp~fE3MfvE-e7KMKjI5cPOH6EN8m794uHJ6b09qM8mb9VEv1lVLEov~usVliTSXCSHuRBOCIwIOuDNU0AbVa4BpIx~2sU4TxKhoaA3zQ6VzINoduTdR2IJhPvI5xzezp7dR21CEQGGTbenDslXeQ4iLHFA2~bzp1f7etSl9T2W9RID-KH78sRQmzWnv7dbhNodMbpO6xsf1vENf6bMRzqD5vgHEHZu2aSoNuPyYxDU1eM6--61b2xp9mt1k3ud-5WvPVg89RaU9ugU5cxaHgR927lHMCAEU2Ax~zUb3DbrvgQBOTHnJEx2Fp7pOK~PnP6ylkYKQMfLROosLDXinxOoSKP0UYCh2WgIUPwE7WzJH3PiJVF0~WZ1dZ9mg00c~gzLgmkOxe1NpFRNg6XzoARivNVB5NuWqNxr5WKWMLBGQ9YHvHO1OHhUJTowb9X90BhtHnLK2AHwO6fV-iHWxRJyDabhSMj1kuYpVUBQAEAAcAAA== -``` - - -### In-depth Information - -See @destination for details behind @base64-address diff --git a/_i18n/nl/resources/moneropedia/data-directory.md b/_i18n/nl/resources/moneropedia/data-directory.md deleted file mode 100644 index abe307f2..00000000 --- a/_i18n/nl/resources/moneropedia/data-directory.md +++ /dev/null @@ -1,20 +0,0 @@ ---- -tags: ["kovri"] -terms: ["Data-Directory"] -summary: "Where essential kovri data for runtime is stored" ---- - -### The Basics - -Depending on your OS, @Kovri currently stores all run-time data in the following directory: - -- Linux/FreeBSD: - - `$HOME/.kovri` - -- OSX: - - `$HOME/Library/Application\ Support/Kovri` - -- Windows: - - `"$APPDATA"\\Kovri` - -This includes all configuration files, @address-book, certificates, and resources. diff --git a/_i18n/nl/resources/moneropedia/eepsite.md b/_i18n/nl/resources/moneropedia/eepsite.md deleted file mode 100644 index efb16e1a..00000000 --- a/_i18n/nl/resources/moneropedia/eepsite.md +++ /dev/null @@ -1,28 +0,0 @@ ---- -tags: ["kovri"] -terms: ["Eepsite", "Hidden-Service", "Garlic-Site", "Garlic-Service"] -summary: "A website or service hosted within the I2P network" ---- - -### The Basics - -Is it [**EEP!** *(in response to the site's content)*](https://en.wikipedia.org/wiki/Onomatopoeia), or **end-to-end protocol**, or something else entirely different? - -While the original definition of eepsite has been lost with time, its use-case remains: an eepsite is a website or service that is hosted within (and only accessible by) the @I2P network. - -### In-depth Information - -Alternate names include: - -1. *Hidden Service* - - because the site/service is *hidden* within the @I2P network and can only be visited within the network -2. *Garlic Site* - - because the website utilizes @I2P's @garlic-routing technology as a means of communicating with a client - - because the service is hosted as a website and not any other type of service -3. *Garlic Service* - - because the service utilizes @I2P's @garlic-routing technology as a means of communicating with a client - - because the service is specific to services like IRC, email, or a Monero peer (but may also include websites) - -### Notes - -To learn how to setup an Eepsite (Hidden Service, Garlic Site, Garlic Service) visit the @Kovri [user-guide](https://gitlab.com/kovri-project/kovri-docs/blob/master/i18n/en/user_guide.md). diff --git a/_i18n/nl/resources/moneropedia/floodfill.md b/_i18n/nl/resources/moneropedia/floodfill.md deleted file mode 100644 index f2cb5f04..00000000 --- a/_i18n/nl/resources/moneropedia/floodfill.md +++ /dev/null @@ -1,13 +0,0 @@ ---- -tags: ["kovri"] -terms: ["Floodfill"] -summary: "An I2P router which maintains a distributed network-database" ---- - -### The Basics - -By actively managing a distributed network-database, a router with *floodfill* capability has the ability to help maintain network stability and resiliancy while also being decentralized and trust-less. - -### In-depth information - -Though floodfill itself is a simple storage system, the technical underpinnings of floodfill as it relates to @network-database and other protocols within @I2P are much more complex. Visit the [Network Database](https://geti2p.net/en/docs/how/network-database) page for details. diff --git a/_i18n/nl/resources/moneropedia/garlic-encryption.md b/_i18n/nl/resources/moneropedia/garlic-encryption.md deleted file mode 100644 index 271d7f0c..00000000 --- a/_i18n/nl/resources/moneropedia/garlic-encryption.md +++ /dev/null @@ -1,23 +0,0 @@ ---- -tags: ["kovri"] -terms: ["Garlic-Encryption", "Layered-Encryption"] -summary: "Layered encryption as implemented in Kovri / I2P" ---- - -### The Basics - -@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 - -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. diff --git a/_i18n/nl/resources/moneropedia/garlic-routing.md b/_i18n/nl/resources/moneropedia/garlic-routing.md deleted file mode 100644 index 6e4865e3..00000000 --- a/_i18n/nl/resources/moneropedia/garlic-routing.md +++ /dev/null @@ -1,43 +0,0 @@ ---- -tags: ["kovri"] -terms: ["Garlic-Routing"] -summary: "Routing technology as implemented in Kovri" ---- - -### 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. - -The @Garlic-Encryption of @Garlic-Routing is similar to the @Layered-Encryption of [Onion Routing](https://en.wikipedia.org/wiki/Onion_routing) and effectively conceals the IP address of the sender and secures information sent from the sender to its @destination (and vice-versa). - -### 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](http://www.freehaven.net/papers.html) (Section 8.1.1) as derived from the term Onion Routing. - -As recent as October of 2016, [#tor-dev](https://oftc.net/WebChat/) has offered insight into the creation of the term *@garlic-routing*: - -[Nick Mathewson](https://en.wikipedia.org/wiki/The_Tor_Project,_Inc): ->[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](https://en.wikipedia.org/wiki/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 was 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 (similar to the @layered-encryption in Onion Routing) -- Bundling multiple @messages together (garlic cloves) -- ElGamal/AES @encryption - -*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 - -- In terms of Onion/Garlic Routing, another way to envision layered @encryption is by replacing the onion/garlic with a [Matryoshka doll](https://en.wikipedia.org/wiki/Matryoshka_doll) - with each outer/inner doll having a lock and public key to the next/previous doll -- For more technical details on Garlic Routing, read the @Java-I2P entry on [Garlic Routing](https://geti2p.net/en/docs/how/garlic-routing) diff --git a/_i18n/nl/resources/moneropedia/i2np.md b/_i18n/nl/resources/moneropedia/i2np.md deleted file mode 100644 index 556f59ee..00000000 --- a/_i18n/nl/resources/moneropedia/i2np.md +++ /dev/null @@ -1,26 +0,0 @@ ---- -tags: ["kovri"] -terms: ["I2NP"] -summary: "The I2P Network Protocol: the mechanism in which I2NP messages are sent over the I2P network" ---- - -### The Basics - -From @Java-I2P: - -> -@I2NP manages the routing and mixing of messages between routers, as well as the selection of what transports to use when communicating with a peer for which there are multiple common transports supported - -### In-depth information - -From @Java-I2P: - -> -@I2NP (@I2P Network Protocol) @messages can be used for one-hop, router-to-router, point-to-point @messages. By @encrypting and wrapping @messages in other @messages, they can be sent in a secure way through multiple hops to the ultimate @destination. @I2NP does not specify nor require any particular @transport layer but does require at least one @transport in use. - -> -Whenever a @destination wants to send a message to to another @destination, it provides its local router with both the @destination structure and the raw bytes of the message to be sent. The router then determines where to send it, delivers it through outbound @tunnels, instructing the end point to pass it along to the appropriate inbound @tunnel, where it is passed along again to that @tunnel's end point and made available to the target for reception. - -### Notes - -Read more about the @I2NP [protocol](https://geti2p.net/en/docs/protocol/i2np) and [specification](https://geti2p.net/spec/i2np). diff --git a/_i18n/nl/resources/moneropedia/i2p.md b/_i18n/nl/resources/moneropedia/i2p.md deleted file mode 100644 index 26ef9c46..00000000 --- a/_i18n/nl/resources/moneropedia/i2p.md +++ /dev/null @@ -1,29 +0,0 @@ ---- -tags: ["kovri"] -terms: ["I2P"] -summary: "The Invisible Internet Project: an anonymizing overlay network" ---- - -### Monero - -For Monero's implementation of @I2P, see @Kovri. For a comparison of @I2P to [Tor](https://torproject.org/), read the [Comparison](https://geti2p.net/en/comparison/tor) page. - -### The Basics - -From @Java-I2P: - ->The I2P network provides strong privacy protections for communication over the Internet. Many activities that would risk your privacy on the public Internet can be conducted anonymously inside I2P. - -### In-depth information - -From @Java-I2P: - ->I2P is an anonymous overlay network - a network within a network. It is intended to protect communication from dragnet surveillance and monitoring by third parties such as ISPs. - ->I2P is used by many people who care about their privacy: activists, oppressed people, journalists and whistleblowers, as well as the average person. - ->No network can be "perfectly anonymous". The continued goal of I2P is to make attacks more and more difficult to mount. Its anonymity will get stronger as the size of the network increases and with ongoing academic review. - -### Notes - -@I2P documentation and specifications are available [here](https://geti2p.net/docs/). diff --git a/_i18n/nl/resources/moneropedia/i2pcontrol.md b/_i18n/nl/resources/moneropedia/i2pcontrol.md deleted file mode 100644 index 5491fc4e..00000000 --- a/_i18n/nl/resources/moneropedia/i2pcontrol.md +++ /dev/null @@ -1,15 +0,0 @@ ---- -tags: ["kovri"] -terms: ["I2PControl"] -summary: "An API inteface for Kovri and Java-I2P that allows simple remote control" ---- - -### The Basics - -@I2Pcontrol is a [JSONRPC2](https://en.wikipedia.org/wiki/JSON-RPC) [API](https://en.wikipedia.org/wiki/Application_programming_interface) for @Kovri and @Java-I2P which allows an @I2PControl client to remote control/monitor a running instance. - -Two available @I2PControl clients are: [qtoopie](https://github.com/EinMByte/qtoopie) (C++ client) and [itoopie](https://github.com/i2p/i2p.itoopie) (Java client). Read `kovri.conf` to configure @I2PControl for @Kovri. - -### In-depth information - -Details and specification available on the [I2PControl](https://geti2p.net/en/docs/api/i2pcontrol) page. diff --git a/_i18n/nl/resources/moneropedia/in-net.md b/_i18n/nl/resources/moneropedia/in-net.md deleted file mode 100644 index 884d40f0..00000000 --- a/_i18n/nl/resources/moneropedia/in-net.md +++ /dev/null @@ -1,13 +0,0 @@ ---- -tags: ["kovri"] -terms: ["In-net"] -summary: "Within the I2P network" ---- - -### The Basics - -**In-net** is a [colloquial](https://en.wikipedia.org/wiki/Colloquial) term of which describes activities, protocols, or functionality that exist *only* within the @I2P network. - -### In-depth information - -Example: *in-net download* would be defined as downloading *only* within @I2P. diff --git a/_i18n/nl/resources/moneropedia/java-i2p.md b/_i18n/nl/resources/moneropedia/java-i2p.md deleted file mode 100644 index ede62818..00000000 --- a/_i18n/nl/resources/moneropedia/java-i2p.md +++ /dev/null @@ -1,13 +0,0 @@ ---- -tags: ["kovri"] -terms: ["Java-I2P"] -summary: "The original implementation of I2P - written in Java" ---- - -### The Basics - -The term "Java I2P" is often used to describe the original @I2P implementation currently most known and used today. There are various other @I2P implementations, including @Kovri; all of which look up to the original Java implementation. - -### Notes - -To download/learn more about the Java implementation, visit their [website](https://geti2p.net/). diff --git a/_i18n/nl/resources/moneropedia/jump-service.md b/_i18n/nl/resources/moneropedia/jump-service.md deleted file mode 100644 index 60619ede..00000000 --- a/_i18n/nl/resources/moneropedia/jump-service.md +++ /dev/null @@ -1,32 +0,0 @@ ---- -tags: ["kovri"] -terms: ["Jump-Service"] -summary: "An I2P website service that adds addresses to your address book" ---- - -### The Basics - -In your @I2P configured web browser, you can use a Jump Service to *jump* to an @I2P address that you don't have in your @address-book. Once you've *jumped* to the address, the address will be saved into your @address-book. - -### In-depth Information - -In an @I2P configured browser, visit: http://stats.i2p/i2p/lookup.html (courtesy of @Java-I2P's lead developer *zzz*) - -Then, you'll have two options: - -1. *Hostname lookup* the address you wish to visit and then manually copy/paste the result -2. *Jump* to the @I2P website by entering the @I2P hostname (**recommended**) - -### Using hostname lookup - -For example, entering `pinkpaste.i2p` into the *Hostname lookup* box (and then submitting) will return: - -``` -pinkpaste.i2p=m-HrPrIAsdxts0WM~P4mE8mt9P7g-QTaBvu7Gc6Nl0UX7Vwck-i~RvOPfK6W~kfdRvwhNTqevkBL2UF5l36We02Aiywu7kB2xOHRkze68h-Tg2ewvRVwokohguCD2G3wwAEz~7FVda2avYDCb9-N6TfuzxKLnmhPMvbNSjGL7ZsD2p-h207R3-2kvuMV9bfu-K~w9NI9XJhIyufvUnFYc2jnTVg8PbaR4UP57cNaOO2YIMPkbr6~yTcIu9B1sUfHK6-N~6virQDOxW4M-62rjnZkLpaCtkOsXslmCwZI--TkZ6hKi1kXZvNmJRE1rYfffYRFn38zhaqszeETX8HiIvahZhXF5fNumBziYdmLdw8hkuN1A~emU6Xz9g~a1Ixfsq1Qr~guYoOtaw-0rOFxNRS9yMehE-2LCb8c-cAg6z5OdlN4qJDl~ZHgru4d~EHp~BpAK3v7u2Gi-8l1ygVW-1CHVna~fwnbOPN3ANPwh6~~yUit0Cx1f54XiNRn6-nPBQAEAAcAAA== -``` - -Copy/paste this host=@base64-address pairing into your **private** @subscription. - -### Directly jumping - -For example, entering `pinkpaste.i2p` into the *Jump* box (and then submitting) will automatically redirect you to the website **and** insert the @locally-unique-host into @address-book. diff --git a/_i18n/nl/resources/moneropedia/lease-set.md b/_i18n/nl/resources/moneropedia/lease-set.md deleted file mode 100644 index dc1c4a24..00000000 --- a/_i18n/nl/resources/moneropedia/lease-set.md +++ /dev/null @@ -1,23 +0,0 @@ ---- -tags: ["kovri"] -terms: ["LeaseSet", "LeaseSets"] -summary: "Contains all currently authorized Leases for a particular I2P Destination" ---- - -### The Basics - -A Lease-Set contains a set of authorized @leases (and other related information) for a particular @destination. - -### In-depth information - -A Lease-Set contains: - -- all of the currently authorized @leases for a particular @destination -- the public key to which garlic messages can be encrypted (see @garlic-routing) -- the signing public key that can be used to revoke this particular version of the structure - -The Lease-Set is one of the two structures stored in the @network-database (the other being @router-info), and is keyed under the SHA256 of the contained @destination. - -### Notes - -For further details, read @Java-I2P's [LeaseSet](https://geti2p.net/en/docs/how/network-database#leaseSet) diff --git a/_i18n/nl/resources/moneropedia/lease.md b/_i18n/nl/resources/moneropedia/lease.md deleted file mode 100644 index c5a78058..00000000 --- a/_i18n/nl/resources/moneropedia/lease.md +++ /dev/null @@ -1,13 +0,0 @@ ---- -tags: ["kovri"] -terms: ["Lease", "Leases"] -summary: "Authorizes an I2P tunnel to receive messages targeting a destination" ---- - -### The Basics - -A lease defines the authorization for a particular @I2P @tunnel to receive a @messages targeting a @destination. - -### In-depth information - -For further details, read @Java-I2P's [Lease](https://geti2p.net/spec/common-structures#lease) diff --git a/_i18n/nl/resources/moneropedia/message.md b/_i18n/nl/resources/moneropedia/message.md deleted file mode 100644 index 5cce553b..00000000 --- a/_i18n/nl/resources/moneropedia/message.md +++ /dev/null @@ -1,31 +0,0 @@ ---- -tags: ["kovri"] -terms: ["Message", "Messages"] -summary: "The mechanisms in which information travels within I2P" ---- - -### The Basics - -*Messages* (which exist on top of the @transports layer), contain varying types of information that are needed for the network but, most importantly, everything you see, do, send, or receive, will come and go in the form of *messages*. - -There are 2 essential types of *messages* in @I2P: - -- @Tunnel messages -- @I2NP messages - -Essentially: *@tunnel messages* **contain** @I2NP **message fragments** which are then [reassembled](https://geti2p.net/en/docs/tunnels/implementation) at certain points within a @tunnel's path. - -### In-depth information - -@I2NP messages have a close relationship with @tunnel @messages so it is easy to get the term *messages* confused when reading @Java-I2P specifications: - -> -1. First, the tunnel gateway accumulates a number of I2NP messages and preprocesses them into tunnel messages for delivery. -2. Next, that gateway encrypts that preprocessed data, then forwards it to the first hop. -3. That peer, and subsequent tunnel participants, unwrap a layer of the encryption, verifying that it isn't a duplicate, then forward it on to the next peer. -4. Eventually, the tunnel messages arrive at the endpoint where the I2NP messages originally bundled by the gateway are reassembled and forwarded on as requested. - -### Notes - -- @I2NP @messages need to be fragmented because they are variable in size (from 0 to almost 64 KB) and @tunnel @messages are fixed-size (approximately 1 KB). -- For details and specifications, visit the [I2NP spec](https://geti2p.net/spec/i2np) and [Tunnel Message spec](https://geti2p.net/spec/tunnel-message) diff --git a/_i18n/nl/resources/moneropedia/network-database.md b/_i18n/nl/resources/moneropedia/network-database.md deleted file mode 100644 index eb3925cd..00000000 --- a/_i18n/nl/resources/moneropedia/network-database.md +++ /dev/null @@ -1,23 +0,0 @@ ---- -tags: ["kovri"] -terms: ["Network-Database"] -summary: "A distributed database which contains needed router information so the network can stay intact" ---- - -### The Basics - -@network-database is a [distributed database](https://en.wikipedia.org/wiki/Distributed_database) which contains router information that peers must use so the network can stay intact. - -### In-depth information - -From @Java-I2P: - -> -@I2P's @network-database is a specialized distributed database, containing just two types of data - router contact information (@Router-Infos) and @destination contact information (@LeaseSets). Each piece of data is signed by the appropriate party and verified by anyone who uses or stores it. In addition, the data has liveliness information within it, allowing irrelevant entries to be dropped, newer entries to replace older ones, and protection against certain classes of attack. - -> -The @network-database is distributed with a simple technique called "@floodfill", where a subset of all routers, called "@floodfill routers", maintains the distributed database. - -### Notes - -Read [Network-Database](https://geti2p.net/en/docs/how/network-database) for details. diff --git a/_i18n/nl/resources/moneropedia/ntcp.md b/_i18n/nl/resources/moneropedia/ntcp.md deleted file mode 100644 index 69d10a3f..00000000 --- a/_i18n/nl/resources/moneropedia/ntcp.md +++ /dev/null @@ -1,32 +0,0 @@ ---- -tags: ["kovri"] -terms: ["NTCP"] -summary: "NIO-Based TCP (Non-blocking I/O based TCP): one of two Kovri transports" ---- - -### The Basics - -*NIO-Based TCP (Non-blocking I/O based TCP)* is one of two encrypted @transports for @Kovri. - -Similar to @SSU, @NTCP's *primary* purpose is to securely transmit @in-net @I2NP messages through @tunnels but, unlike @SSU, @NTCP functions solely over encrypted [TCP](https://en.wikipedia.org/wiki/Transmission_Control_Protocol). - -### In-depth information - - - Passes along individual @I2NP messages (both Standard and Time Sync) after: - - TCP has been established - - Establishment Sequence has been completed - - Uses the following @encryption: - - 2048-bit [Diffie-Hellman](https://en.wikipedia.org/wiki/Diffie-hellman) - - [AES-256](https://en.wikipedia.org/wiki/Advanced_Encryption_Standard)/[CBC](https://en.wikipedia.org/wiki/Block_cipher_modes_of_operation) - - Establishment Sequence has the following *states*: - - Pre-establishment - - Establishment - - Post-establishment or "Established" - - Uses the following from the @network-database: - - Transport name: NTCP - - Host: IP (IPv4 or IPv6) or host name (shortened IPv6 address (with "::") is allowed) - - Port: 1024 - 65535 - -### Notes - -For further details, read @Java-I2P's [NTCP](https://geti2p.net/en/docs/transport/ntcp) diff --git a/_i18n/nl/resources/moneropedia/reseed.md b/_i18n/nl/resources/moneropedia/reseed.md deleted file mode 100644 index 59727311..00000000 --- a/_i18n/nl/resources/moneropedia/reseed.md +++ /dev/null @@ -1,15 +0,0 @@ ---- -tags: ["kovri"] -terms: ["Reseed"] -summary: "The method of which Kovri uses to bootstrap into the I2P network" ---- - -### The Basics - -When you start @Kovri for the first time (or if it's been offline for a long time), @Kovri will need a list of peers to connect to so it can [bootstrap](https://en.wikipedia.org/wiki/Bootstrap) into the @I2P network. @Kovri gets these peers from a special file stored on a reseed server. On this file are all the various pieces of information @Kovri needs in order to connect with @I2P peers. - -### In-depth information - -@Kovri has a list of [hard-coded](https://en.wikipedia.org/wiki/Hard-coded) reseed servers available to fetch from. These servers securely serve an [SU3](https://geti2p.net/spec/updates#su3) file (signed with a cryptographic @signature) over @clearnet with [HTTPS](https://en.wikipedia.org/wiki/HTTPS). This SU3 file contains information that's used to verify both the integrity of the file and its content. - -Aside from the technical elements needed to verify and process the file, the file's main contents consist of a series of @router-info files which @Kovri and @I2P routers use to locate and communicate with other @I2P peers. These peers are then stored into a @network-database. diff --git a/_i18n/nl/resources/moneropedia/router-info.md b/_i18n/nl/resources/moneropedia/router-info.md deleted file mode 100644 index ad50c13f..00000000 --- a/_i18n/nl/resources/moneropedia/router-info.md +++ /dev/null @@ -1,66 +0,0 @@ ---- -tags: ["kovri"] -terms: ["Router-Info", "Router-infos"] -summary: "A data structure or file which contains an I2P peer's needed network information" ---- - -### The Basics - -@Router-Info is a data structure (periodically written to a [binary file](https://en.wikipedia.org/wiki/Binary_file)) which contains all needed information to locate, identify, and communicate with an @I2P peer. @Router-Info includes IP address, router identity, other misc. technical details; is needed for @network-database and is published to @floodfill routers. - -### In-depth information - -In human-readable form, Router-Info may look like this: - -``` -Identity: [RouterIdentity: -Hash: nYZ5Qe7gQ-~QgfgJVRUG4c0JnVeVqzM~duUX1EGT1ek= -Certificate: [Certificate: type: Key certificate -Crypto type: 0 -Sig type: 7 (EdDSA_SHA512_Ed25519)] -PublicKey: [PublicKey: size: 256] -SigningPublicKey: [SigningPublicKey EdDSA_SHA512_Ed25519: size: 32] -Padding: 96 bytes] -Signature: [Signature EdDSA_SHA512_Ed25519: size: 64] -Published: Sun Oct 09 01:34:59 UTC 2016 -Options (5): - [caps] = [LfR] - [netId] = [2] - [netdb.knownLeaseSets] = [37] - [netdb.knownRouters] = [2435] - [router.version] = [0.9.26] -Addresses (4): -[RouterAddress: -Type: SSU -Cost: 4 -Options (5): - [caps] = [BC] - [host] = [2a01:e35:8b5c:b240:71a2:6750:8d4:47fa] - [key] = [nYZ5Qe7gQ-~QgfgJVRUG4c0JnVeVqzM~duUX1EGT1ek=] - [mtu] = [1472] - [port] = [22244]] -[RouterAddress: -Type: NTCP -Cost: 9 -Options (2): - [host] = [2a01:e35:8b5c:b240:71a2:6750:8d4:47fa] - [port] = [22244]] -[RouterAddress: -Type: SSU -Cost: 6 -Options (4): - [caps] = [BC] - [host] = [88.181.203.36] - [key] = [nYZ5Qe7gQ-~QgfgJVRUG4c0JnVeVqzM~duUX1EGT1ek=] - [port] = [22244]] -[RouterAddress: -Type: NTCP -Cost: 11 -Options (2): - [host] = [88.181.203.36] - [port] = [22244]]] -``` - -### Notes - -For details and specification, visit @Java-I2P [Network Database](https://geti2p.net/en/docs/how/network-database) page. diff --git a/_i18n/nl/resources/moneropedia/ssu.md b/_i18n/nl/resources/moneropedia/ssu.md deleted file mode 100644 index a7b2eb5b..00000000 --- a/_i18n/nl/resources/moneropedia/ssu.md +++ /dev/null @@ -1,24 +0,0 @@ ---- -tags: ["kovri"] -terms: ["SSU"] -summary: "Secure Semi-reliable UDP: one of two Kovri transports" ---- - -### The Basics - -*Secure Semi-reliable UDP* is one of two encrypted @transports for @Kovri. - -Similar to @NTCP, @SSU's *primary* purpose is to securely transmit @in-net @I2NP messages through @tunnels but, unlike @NTCP, @SSU functions solely over encrypted [UDP](https://en.wikipedia.org/wiki/User_Datagram_Protocol). - -### In-depth information - -- Like @NTCP, @SSU is a connection-oriented, point-to-point data transport -- Termed *semi-reliable* because @SSU will repeatedly retransmit *unacknowledged* messages (up to maximum number then dropped) -- @SSU also provides several unique services (in addition to its function as a @transport layer): - - IP detection (local inspection or with [peer testing](https://geti2p.net/en/docs/transport/ssu#peerTesting)) - - [NAT](https://en.wikipedia.org/wiki/Network_address_translation) traversal (using [introducers](https://geti2p.net/en/docs/transport/ssu#introduction)) - - [Firewall](https://en.wikipedia.org/wiki/Firewall_%28computing%29) status and, if implemented, @SSU can notify @NTCP if the external address or firewall status changes - -### Notes - -For further details, read @Java-I2P's [SSU](https://geti2p.net/en/docs/transport/ssu) diff --git a/_i18n/nl/resources/moneropedia/subscription.md b/_i18n/nl/resources/moneropedia/subscription.md deleted file mode 100644 index 78ef1bf4..00000000 --- a/_i18n/nl/resources/moneropedia/subscription.md +++ /dev/null @@ -1,45 +0,0 @@ ---- -tags: ["kovri"] -terms: ["Subscription"] -summary: "A file used by address book which contains I2P hosts paired with I2P destinations" ---- - -### The Basics - -A subscription is a file which contains a list of `.i2p` hosts paired with their respective @destination. Subscriptions are used by the @address-book. - -### In-depth information - -Similar to how a [hosts file](https://en.wikipedia.org/wiki/Hosts_(file)) can map an internet hostname to a specified address, a subscription matches a `.i2p` address to @base64-address by using the following format (no spaces allowed): `host=address` - -More specifically, a subscription pairs a @locally-unique-host to @base64-address. - -Example: - -``` -anonimal.i2p=AQZGLAMpI9Q0l0kmMj1vpJJYK3CjLp~fE3MfvE-e7KMKjI5cPOH6EN8m794uHJ6b09qM8mb9VEv1lVLEov~usVliTSXCSHuRBOCIwIOuDNU0AbVa4BpIx~2sU4TxKhoaA3zQ6VzINoduTdR2IJhPvI5xzezp7dR21CEQGGTbenDslXeQ4iLHFA2~bzp1f7etSl9T2W9RID-KH78sRQmzWnv7dbhNodMbpO6xsf1vENf6bMRzqD5vgHEHZu2aSoNuPyYxDU1eM6--61b2xp9mt1k3ud-5WvPVg89RaU9ugU5cxaHgR927lHMCAEU2Ax~zUb3DbrvgQBOTHnJEx2Fp7pOK~PnP6ylkYKQMfLROosLDXinxOoSKP0UYCh2WgIUPwE7WzJH3PiJVF0~WZ1dZ9mg00c~gzLgmkOxe1NpFRNg6XzoARivNVB5NuWqNxr5WKWMLBGQ9YHvHO1OHhUJTowb9X90BhtHnLK2AHwO6fV-iHWxRJyDabhSMj1kuYpVUBQAEAAcAAA== -``` - -1. `anonimal.i2p` is the @locally-unique-host -2. `=` is the separator -3. Everything that remains is the @base64-address - -### Subscription types - -For @Kovri, there are two types of subscription files: *public* and *private*. - -A *public* subscription: -- is used when bootstrapping to use essential services (IRC, email, Monero, etc.) -- is static and is refreshed every 12 hours from Monero's @address-book server -- allows you to safely share the subscription with everyone as it is publically available (anyone who shares the same public subscription will also be able to resolve the same hostname to the same destination as you) - -A *private* subscription: -- is used exclusively by you and is not shared with others unless you explicitly choose to share the file -- default file is `private_hosts.txt` in your @data-directory - -### Updating a private subscription - -You can use a @jump-service to manually update your private subscription. The updated subscription will then be fed into the @address-book for you to use. - -### Notes -To learn how to subscribe to multiple subscriptions, see the [user-guide](https://gitlab.com/kovri-project/kovri-docs/blob/master/i18n/en/user_guide.md). diff --git a/_i18n/nl/resources/moneropedia/transports.md b/_i18n/nl/resources/moneropedia/transports.md deleted file mode 100644 index 01225e66..00000000 --- a/_i18n/nl/resources/moneropedia/transports.md +++ /dev/null @@ -1,18 +0,0 @@ ---- -tags: ["kovri"] -terms: ["Transports", "Transport"] -summary: "The two encrypted transport layers for Kovri" ---- - -### The Basics - -@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 - -@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 @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) diff --git a/_i18n/nl/resources/moneropedia/tunnel.md b/_i18n/nl/resources/moneropedia/tunnel.md deleted file mode 100644 index 94369ad2..00000000 --- a/_i18n/nl/resources/moneropedia/tunnel.md +++ /dev/null @@ -1,35 +0,0 @@ ---- -tags: ["kovri"] -terms: ["Tunnel", "Tunnels"] -summary: "Uni-directional virtual paths that pass messages through a defined sequence of I2P routers" ---- - -### The Basics - -When you communicate over @I2P (visit an @eepsite / use a @garlic-service), you'll first need to connect to a peer by using @transports and then build virtual *tunnels*. These virtual tunnels are temporary, uni-directional paths that pass information through a defined sequence of @I2P routers to your @destination. Tunnels are built, and then used, with layered @garlic-encryption and are a general-purpose mechanism to transport all @I2NP @messages. - -Each peer builds, at a minimum, *two* uni-directional tunnels: one for **outbound traffic**, and one for **inbound traffic**. These tunnels are classified as either **inbound tunnels** (where @messages come toward the creator of the tunnel) or **outbound tunnels** (where the tunnel creator sends @messages away from the creator of the tunnel). Thus, *four* tunnels are required for a single round-trip @message and reply to your @destination (two for your, two for your destination). - -### In-depth information - -From @Java-I2P: - -> -Within I2P, @messages are passed in one direction through a virtual tunnel of peers, using whatever means are available to pass the @message on to the next hop. Messages arrive at the tunnel's gateway, get bundled up and/or fragmented into fixed-size @tunnel @messages, and are forwarded on to the next hop in the tunnel, which processes and verifies the validity of the @message and sends it on to the next hop, and so on, until it reaches the @tunnel endpoint. That endpoint takes the messages bundled up by the gateway and forwards them as instructed - either to another router, to another tunnel on another router, or locally. - -> -Tunnels all work the same, but can be segmented into two different groups - inbound tunnels and outbound tunnels. The inbound tunnels have an untrusted gateway which passes messages down towards the tunnel creator, which serves as the tunnel endpoint. For outbound tunnels, the tunnel creator serves as the gateway, passing messages out to the remote endpoint. - -> -The tunnel's creator selects exactly which peers will participate in the tunnel, and provides each with the necessary configuration data. They may have any number of hops. It is the intent to make it hard for either participants or third parties to determine the length of a tunnel, or even for colluding participants to determine whether they are a part of the same tunnel at all (barring the situation where colluding peers are next to each other in the tunnel). - -### Notes - -From @Java-I2P: - -> -@I2P is an inherently packet switched network, even with these tunnels, allowing it to take advantage of multiple tunnels running in parallel, increasing resilience and balancing load. Even though the tunnels within I2P bear a resemblance to a circuit switched network, everything within I2P is strictly message based - tunnels are merely accounting tricks to help organize the delivery of messages. No assumptions are made regarding reliability or ordering of messages, and retransmissions are left to higher levels (e.g. I2P's client layer streaming library). - -### Documentation - -For specification and detailed documentation, visit the [Tunnel-Routing](https://geti2p.net/en/docs/how/tunnel-routing) and [Tunnel-Implementation](https://geti2p.net/en/docs/tunnels/implementation) page. diff --git a/_i18n/pl/resources/moneropedia/base32-address.md b/_i18n/pl/resources/moneropedia/base32-address.md deleted file mode 100644 index 21753d5f..00000000 --- a/_i18n/pl/resources/moneropedia/base32-address.md +++ /dev/null @@ -1,25 +0,0 @@ ---- -tags: ["kovri"] -terms: ["Base32-address", "Base32-addresses", "adres-Base32", "adresu-Base32", "adresie-Base32"] -summary: "Zakodowany hasz Base32 adresu Base64." ---- - -### Podstawy - -Adres Base32 jest skróconą i zakodowaną wersją adresu @I2P. Jest on pierwszą częścią nazwy hosta `.b32.i2p`. - -Przykład: - -`i35yftyyb22xhcvghmev46t5knefur5v66qzekkajatwfwhyklvq.b32.i2p` - -gdzie - -`i35yftyyb22xhcvghmev46t5knefur5v66qzekkajatwfwhyklvq` jest adresem Base32. - -### Szczegółowe informacje - -Ostatnio adres Base32 składa się z 52 znaków i jest [zaszyfrowaną kodem Base32 reprezentacją] (https://en.wikipedia.org/wiki/Base32) pełnego hasza SHA-256 @adresu-base64 sieci @I2P. - -### Adnotacje - -**Uwaga: `.b32` nie jest subdomeną `.i2p`** diff --git a/_i18n/pl/resources/moneropedia/base64-address.md b/_i18n/pl/resources/moneropedia/base64-address.md deleted file mode 100644 index e487f485..00000000 --- a/_i18n/pl/resources/moneropedia/base64-address.md +++ /dev/null @@ -1,20 +0,0 @@ ---- -tags: ["kovri"] -terms: ["Base64-address", "Base64-addresses", "adres-base64", "adresu-base64", "adresie-base64", "adresem-base64"] -summary: "Zakodowany w Base64 adres I2P" ---- - -### Podstawy - -@adres-base64 składa się z 516 znaków i jest [zakodowanym w Base64](https://en.wikipedia.org/wiki/Base64) adresem @I2P. Adresy Base64 są głównie używane w @książce-adresowej, @opcji-przeskakiwania, a także wewnętrznie. - -Przykład: - -``` -AQZGLAMpI9Q0l0kmMj1vpJJYK3CjLp~fE3MfvE-e7KMKjI5cPOH6EN8m794uHJ6b09qM8mb9VEv1lVLEov~usVliTSXCSHuRBOCIwIOuDNU0AbVa4BpIx~2sU4TxKhoaA3zQ6VzINoduTdR2IJhPvI5xzezp7dR21CEQGGTbenDslXeQ4iLHFA2~bzp1f7etSl9T2W9RID-KH78sRQmzWnv7dbhNodMbpO6xsf1vENf6bMRzqD5vgHEHZu2aSoNuPyYxDU1eM6--61b2xp9mt1k3ud-5WvPVg89RaU9ugU5cxaHgR927lHMCAEU2Ax~zUb3DbrvgQBOTHnJEx2Fp7pOK~PnP6ylkYKQMfLROosLDXinxOoSKP0UYCh2WgIUPwE7WzJH3PiJVF0~WZ1dZ9mg00c~gzLgmkOxe1NpFRNg6XzoARivNVB5NuWqNxr5WKWMLBGQ9YHvHO1OHhUJTowb9X90BhtHnLK2AHwO6fV-iHWxRJyDabhSMj1kuYpVUBQAEAAcAAA== -``` - - -### Szczegółowe informacje - -Przejdź do strony @węzła-docelowego po więcej informacji na temat @adresu-base64. diff --git a/_i18n/pl/resources/moneropedia/data-directory.md b/_i18n/pl/resources/moneropedia/data-directory.md deleted file mode 100644 index 9688b6d9..00000000 --- a/_i18n/pl/resources/moneropedia/data-directory.md +++ /dev/null @@ -1,20 +0,0 @@ ---- -tags: ["kovri"] -terms: ["Data-Directory", "katalog-danych", "katalogu-danych", "katalogowi-danych"] -summary: "Miejsce przechowywania kluczowych danych Kovri w czasie jego pracy." ---- - -### Podstawy - -W zależności od twojego systemu operacyjnego, @Kovri obecnie przechowuje wszystkie dane wykonawcze w następujących folderach: - -- Linux/FreeBSD: - - `$HOME/.kovri` - -- OSX: - - `$HOME/Library/Application\ Support/Kovri` - -- Windows: - - `"$APPDATA"\\Kovri` - -Zawierają one wszystkie pliki konfiguracyjne, @książkę-adresową, certyfikaty i zasoby. diff --git a/_i18n/pl/resources/moneropedia/eepsite.md b/_i18n/pl/resources/moneropedia/eepsite.md deleted file mode 100644 index f93bd3b9..00000000 --- a/_i18n/pl/resources/moneropedia/eepsite.md +++ /dev/null @@ -1,26 +0,0 @@ ---- -tags: ["kovri"] -terms: ["Eepsite", "Hidden-Service", "Garlic-Site", "Garlic-Service", "ukryty-serwis", "strona-czosnkowa", "serwis-czosnkowy", "serwisu-czosnkowego"] -summary: "Strona lub serwis internetowy zamieszczony w sieci I2P." ---- - -### Podstawy - -Oryginalna definicja pojęcia "eepsite" zagubiła się wraz z upływem czasu, jednak najczęstszym jego rozumieniem jest strona internetowa lub serwis internetowy zamieszczony w sieci @I2P i dostępny jedynie za jej pomocą. - -### Szczegółowe informacje - -Innymi nazwami eepsite są - -1. *Ukryty Serwis* - - ponieważ strona lub serwis jest *ukryty* wewnątrz sieci @I2P i może zostać wyświetlony jedynie za jej pomocą -2. *Strona Czosnkowa* - - ponieważ strona korzysta z technologii @trasowania-czosnkowego sieci I2P jako środka komunikacji z klientem - - ponieważ serwis jest hostowany jako strona internetowa, a nie inny rodzaj serwisu -3. *Serwis Czosnkowy* - - ponieważ strona korzysta z technologii @trasowania-czosnkowego sieci I2P jako środka komunikacji z klientem - - ponieważ serwis jest sprecyzowany do takich usług jak IRC, e-mail lub peer Monero (ale może także uwzględniać strony internetowe) - -### Adnotacje - -Aby dowiedzieć się, jak skonfigurować Eepsite (Ukryty Serwis, Stronę Czosnkową, Serwis Czosnkowy), przejdź do [przewodnika dla użytkowników](https://gitlab.com/kovri-project/kovri-docs/blob/master/i18n/en/user_guide.md) @Kovri. diff --git a/_i18n/pl/resources/moneropedia/floodfill.md b/_i18n/pl/resources/moneropedia/floodfill.md deleted file mode 100644 index ea2a72d5..00000000 --- a/_i18n/pl/resources/moneropedia/floodfill.md +++ /dev/null @@ -1,13 +0,0 @@ ---- -tags: ["kovri"] -terms: ["Floodfill"] -summary: "Router sieci I2P, który utrzymuje bazę danych rozproszonej sieci." ---- - -### Podstawy - -Poprzez aktywne zarządzanie bazą danych rozproszonej sieci, router ze zdolnością *floodfill* ma możliwość pomóc w utrzymaniu stabilności i prężności sieci, będąc równocześnie zdecentralizowanym i bez-zaufania. - -### Szczegółowe informacje - -Mimo że floodfill sam w sobie jest prostym systemem przechowywania, jego podstawy techniczne w powiązaniu z @bazą-danych-sieci i innymi protokołami wewnątrz sieci @I2P są znacznie bardzej skomplikowane. Przejdź do [Bazy Danych Sieci](https://geti2p.net/en/docs/how/network-database) po więcej szczegółów. diff --git a/_i18n/pl/resources/moneropedia/garlic-encryption.md b/_i18n/pl/resources/moneropedia/garlic-encryption.md deleted file mode 100644 index 27e8b7d4..00000000 --- a/_i18n/pl/resources/moneropedia/garlic-encryption.md +++ /dev/null @@ -1,23 +0,0 @@ ---- -tags: ["kovri"] -terms: ["Garlic-Encryption", "Layered-Encryption", "szyfrowanie-czosnkowe", "szyfrowaniu-czosnkowemu", "szyfrowaniem-czosnkowym", "szyfrowanie-warstwowe", "szyfrowaniem-warstwowym", "szyfrowaniu-warstwowemu", "szyfrowania-warstwowego"] -summary: "Szyfrowanie warstwowe wdrożone w Kovri / I2P" ---- - -### Podstawy - -Szyfrowanie "czosnkowe" jest implementacją @szyfrowania-warstwowego opartego na @wiadomości w sieci @I2P (podobną do opartego na przepływie [trasowania cebulowego](https://en.wikipedia.org/wiki/Onion_routing)). - -Poprzez @szyfrowanie wiadomości w warstwach, wiadomość jest prowadzona przez serię proxy, nie pozwalając na to, aby proxy (lub inny pośrednik) mógł odczytać jej treść. @Szyfrowanie-warstwowe jest główną charakterystyką @Kovri, @I2P oraz sieci [Tor](https://torproject.org) i jest podstawą dla zabezpieczenia anonimowości w tych sieciach warstwowych. - -### Szczegółowe informacje - -Głównymi różnicami pomiędzy Kovri/I2P a Tor w zakresie szyfrowania czosnkowego są: - -- @Kovri/@I2P łączy wiele wiadomości razem, tworząc "ząbki czosnku" -- na "ząbek czosnku" może składać się dowolny numer wiadomości, a nie *tylko jedna* wiadomość -- @Kovri/@I2P korzysta z algorytmu [ElGamal](https://en.wikipedia.org/wiki/ElGamal)/[AES](https://en.wikipedia.org/wiki/Advanced_Encryption_Standard) dla wiadomości i transportu. - -### Adnotacje - -Aby dowiedzieć się więcej, przejdź do strony @trasowanie-czosnkowe. diff --git a/_i18n/pl/resources/moneropedia/garlic-routing.md b/_i18n/pl/resources/moneropedia/garlic-routing.md deleted file mode 100644 index b6bf869a..00000000 --- a/_i18n/pl/resources/moneropedia/garlic-routing.md +++ /dev/null @@ -1,42 +0,0 @@ ---- -tags: ["kovri"] -terms: ["Garlic-Routing", "trasowanie-czosnkowe", "trasowania-czosnkowego", "trasowaniu-czosnkowym", "trasowaniem-czosnkowym"] -summary: "Technologia trasowania (rutingu, rutowania) wdrożona w Kovri." ---- - -### Podstawy - -Pojęcie *trasowanie czosnkowe* posiada wiele interpretacji. Aktualnie Monero definiuje je jako metodę, którą @Kovri i @I2P tworzą anonimową sieć nakładkową peerów internetowych opartą na @wiadomościach. - -@Szyfrowanie-czosnkowe trasowania czosnkowego jest podobne do @szyfrowania-warstwowego w [trasowaniu cebulowym](https://en.wikipedia.org/wiki/Onion_routing) i efektywnie ukrywa adresy IP nadawcy oraz zabezpiecza informacje wysłane do @węzła-docelowego (i vice-versa). - -### Historia - -W formie pisanej pojęcie *garlic routing* pojawiło się w czerwcu 2000 roku w pracy dyplomowej Rogera Dingledine'a [Free Haven](http://www.freehaven.net/papers.html) (Sekcja 8.1.1) jako pochodna pojęcia "trasowanie cebulowe". - -W październiku 2016 roku kanał [#tor-dev](https://oftc.net/WebChat/) zaproponował stworzenie pojęcia "trasowanie czosnkowe": - -[Nick Mathewson](https://en.wikipedia.org/wiki/The_Tor_Project,_Inc): ->[Myślę, że chodziło o wymyślenie jakiejś rośliny, której struktura odwzorowywałaby topologię "nieszczelnej rury" sieci Tor, ale nie sądzę, że poprzestaniemy na jednej.] - -[Roger Dingledine](https://en.wikipedia.org/wiki/Roger_Dingledine): ->Podczas burzy mózgów przy pisaniu "Free Haven" był moment, w którym opisywaliśmy mechanizmy trasowania i ktoś powiedział "trasowanie czosnkowe!" i wszyscy się zaśmiali. Byliśmy pewni, że wymyśliliśmy nową nazwę. - -*Uwaga: na użycie cytowanych wypowiedzi wyrazili zgodę Nick Mathewson i Roger Dingledine* - -### Szczegółowe informacje - -W kategoriach technicznych, trasowanie czosnkowe w @Kovri i @I2P oznacza wszystkie poniższe: - -- @szyfrowanie-warstwowe (podobnie do szyfrowania warstwowego w trasowaniu cebulowym) -- łączenie ze sobą wielu @wiadomości (tworzenie "ząbków czosnku") -- @szyfrowanie algorytmem ElGamal/AES - -*Uwaga: mimo że [Tor](https://torproject.org/) korzysta z szyfrowania warstwowego, nie używa on algorytmu ElGamal i nie jest oparty na wiadomościach.* - -**Czytaj więcej na stroine @szyfrowanie-czosnkowe.** - -### Adnotacje - -- W kategoriach trasowania cebulowego/czosnkowego, innym sposobem na wizualizację szyfrowania warstwowego jest zastąpienie cebuli/czosnku [matrioszką](https://en.wikipedia.org/wiki/Matryoshka_doll) - każda lalka jest blokadą posiadającym publiczny klucz do kolejnej lub poprzedniej lalki. -- Aby dowiedzieć się więcej na temat trasowania czosnkowego, przejdź do strony @Java-I2P w [trasowaniu czosnkowym](https://geti2p.net/en/docs/how/garlic-routing). diff --git a/_i18n/pl/resources/moneropedia/i2np.md b/_i18n/pl/resources/moneropedia/i2np.md deleted file mode 100644 index 06493bcf..00000000 --- a/_i18n/pl/resources/moneropedia/i2np.md +++ /dev/null @@ -1,26 +0,0 @@ ---- -tags: ["kovri"] -terms: ["I2NP"] -summary: "Protokół sieci I2P: mechanizm, za pomocą ktąrego wiadomości I2NP są przesyłane do sieci I2P." ---- - -### Podstawy - -Za: @Java-I2P: - -> -@I2NP zarządza trasowaniem i mieszaniem wiadomości pomiędzy routerami oraz wybiera rodzaj transportu gdy komunikacja z peerem może się odbyć za pomocą wielu środków. - -### Szczegółowe informacje - -Za: @Java-I2P: - -> -@wiadomości I2NP (Protokół Sieci I2P) mogą zostać użyte do pojedynczego hopu, router-to-router lub point-to-point. Poprzez @szyfrowanie oraz zawieranie wiadomości w innych wiadomościach, możliwe jest wysyłanie ich bezpieczną drogą przez wiele hopów aż do @węzła końcowego. I2NP nie uściśla ani nie wymaga żadnej konkretnej warstwy @transportu, ale wymaga użycia przynajmniej jednego środka. - -> -Za każdym razem gdy węzeł końcowy chce wysłać wiadomość do innego węzła końcowego, udostępnia on swój lokalny router ze strukturą węzła końcowego oraz surowe bajty wiadomości, która ma być wysłana. Następnie router decyduje dokąd ją wysłać, dostarcza ją poprzez wychodzące @tunele, informując punkt końcowy, aby przekazał ją do odpowiedniego tunelu przychodzącego, gdzie zostaje ona przekazana ponownie do tunelu punktu końcowego i udostępniona odbiorcy. - -### Adnotacje - -Przeczytaj więcej o [protokole I2NP](https://geti2p.net/en/docs/protocol/i2np) oraz jego [specyfikacjach](https://geti2p.net/spec/i2np). diff --git a/_i18n/pl/resources/moneropedia/i2p.md b/_i18n/pl/resources/moneropedia/i2p.md deleted file mode 100644 index 529d152c..00000000 --- a/_i18n/pl/resources/moneropedia/i2p.md +++ /dev/null @@ -1,29 +0,0 @@ ---- -tags: ["kovri"] -terms: ["I2P"] -summary: "Projekt Niewidzialny Internet: anonimizująca sieć nakładkowa." ---- - -### Monero - -Aby dowiedzieć się o implementacji I2P przez Monero, przejdź do @Kovri. Aby porównać I2P z siecią [Tor](https://torproject.org/), przejdź do [porównania](https://geti2p.net/en/comparison/tor). - -### Podstawy - -Za @Java-I2P: - ->Sieć I2P dostarcza silną ochronę prywatności dla komunikacji internetowej. Wiele aktywności, które wystawiają twoją prywatność na zagrożenia w publicznym Internecie, może być prowadzonych anonimowo wewnątrz I2P. - -### Szczegółowe informacje - -Za @Java-I2P: - ->I2P jest anonimową siecią nakładkową - siecią wewnątrz sieci. Jest ona przeznaczona do ochrony komunikacji przed inwigilacją oraz monitorowaniem przez osoby trzecie, takie jak dostawcy usług internetowych. - ->Z I2P korzysta wiele osób troszczących się o swoją prywatność: aktywiści, osoby represjonowane, dziennikarze, informatorzy oraz przeciętni użytkownicy. - ->Żadna sieć nie może być "idealnie anonimowa". Ciągłym celem I2P jest sprawianie, że ataki staną się coraz trudniejsze do dokonania. Jej anonimowość staje się silniejsza wraz z rozrostem sieci i rozwojem bieżących badań akademickich. - -### Adnotacje - -Dokumenty I2P oraz specyfikacje dostępne są [tutaj](https://geti2p.net/docs/). diff --git a/_i18n/pl/resources/moneropedia/i2pcontrol.md b/_i18n/pl/resources/moneropedia/i2pcontrol.md deleted file mode 100644 index f1caf24a..00000000 --- a/_i18n/pl/resources/moneropedia/i2pcontrol.md +++ /dev/null @@ -1,15 +0,0 @@ ---- -tags: ["kovri"] -terms: ["I2PControl"] -summary: "Interfejs programowania aplikacji dla Kovri i Java-I2P pozwalający na prostą zdalną kontrolę." ---- - -### Podstawy - -I2Pcontrol jest interfejsem programowania aplikacji(https://en.wikipedia.org/wiki/Application_programming_interface) [JSONRPC2](https://en.wikipedia.org/wiki/JSON-RPC) dla @Kovri i @Java-I2P, który pozwala klientowi na zdalną kontrolę i monitoring uruchomionej instancji. - -Dwoma dostępnymi klientami I2PControl są: [qtoopie](https://github.com/EinMByte/qtoopie) (klient C++) i [itoopie](https://github.com/i2p/i2p.itoopie) (klient Java). Przejdź do `kovri.conf`, aby skonfigurować I2PControl dla Kovri. - -### Szczegółowe informacje - -Szczegóły i informacje dostępne są na stronie [I2PControl](https://geti2p.net/en/docs/api/i2pcontrol). diff --git a/_i18n/pl/resources/moneropedia/in-net.md b/_i18n/pl/resources/moneropedia/in-net.md deleted file mode 100644 index e2e862d1..00000000 --- a/_i18n/pl/resources/moneropedia/in-net.md +++ /dev/null @@ -1,13 +0,0 @@ ---- -tags: ["kovri"] -terms: ["In-net"] -summary: "Wewnątrz sieci I2P" ---- - -### Podstawy - -**In-net** jest [kolokwialnym](https://en.wikipedia.org/wiki/Colloquial) pojęciem opisującym aktywności, protokoły i funkcjonalności istniejące *wyłącznie* wewnątrz sieci @I2P. - -### Szczegółowe informacje - -Przykład: *ściąganie in-net* to ściąganie plików *wyłącznie* wewnątrz I2P. diff --git a/_i18n/pl/resources/moneropedia/java-i2p.md b/_i18n/pl/resources/moneropedia/java-i2p.md deleted file mode 100644 index 1251f3c2..00000000 --- a/_i18n/pl/resources/moneropedia/java-i2p.md +++ /dev/null @@ -1,13 +0,0 @@ ---- -tags: ["kovri"] -terms: ["Java-I2P"] -summary: "Oryginalna implementacja sieci I2P, napisana w Javie." ---- - -### Podstawy - -Pojęcie "Java I2P" jest często stosowane do opisania oryginalnej implementacji sieci @I2P, obecnie najbardziej znanej i używanej. Istnieje wiele implementacji I2P, w tym @Kovri, wszystkie oparte na oryginalnej implementacji Java. - -### Adnotacje - -Aby ściągnąć lub dowiedzieć się więcej o implementacji Java, odwiedź [stronę I2P](https://geti2p.net/). diff --git a/_i18n/pl/resources/moneropedia/jump-service.md b/_i18n/pl/resources/moneropedia/jump-service.md deleted file mode 100644 index 65778909..00000000 --- a/_i18n/pl/resources/moneropedia/jump-service.md +++ /dev/null @@ -1,32 +0,0 @@ ---- -tags: ["kovri"] -terms: ["Jump-Service", "opcja-przeskakiwania", "opcji-przeskakiwania"] -summary: "Serwis strony w sieci I2P, który dodaje adresy do twojej książki adresowej." ---- - -### Podstawy - -W skonfigurowanej przeglądarce sieci I2P możesz skorzystać z serwisu przeskakiwania do *przeskoczenia* do adresu @I2P, który nie znajduje się w twojej @książce-adresowej. Po przeskoczeniu do adresu, zostanie on w niej zapisany. - -### Szczegółowe informacje - -W skonfigurowanej przeglądarce sieci I2P przejdź do strony http://stats.i2p/i2p/lookup.html (uprzejmość głównego dewelopera @Java-I2P - *zzz*). - -Następnie pojawią się dwie opcje: - -1. *Hostname Lookup* do wyszukiwania nazwa hosta adresu, do którego chcesz przejść, a następnie ręcznego skopiowania i wklejenia rezultatu -2. *Jump* do przeskoczenia do strony I2P poprzez wpisanie nazwy hosta I2P (**zalecane**). - -### Korzystanie z hostname lookup - -Przykładowo wpisanie `pinkpaste.i2p` do okna *Hostname lookup* (a następnie zatwierdzenie) da następujący rezultat: - -``` -pinkpaste.i2p=m-HrPrIAsdxts0WM~P4mE8mt9P7g-QTaBvu7Gc6Nl0UX7Vwck-i~RvOPfK6W~kfdRvwhNTqevkBL2UF5l36We02Aiywu7kB2xOHRkze68h-Tg2ewvRVwokohguCD2G3wwAEz~7FVda2avYDCb9-N6TfuzxKLnmhPMvbNSjGL7ZsD2p-h207R3-2kvuMV9bfu-K~w9NI9XJhIyufvUnFYc2jnTVg8PbaR4UP57cNaOO2YIMPkbr6~yTcIu9B1sUfHK6-N~6virQDOxW4M-62rjnZkLpaCtkOsXslmCwZI--TkZ6hKi1kXZvNmJRE1rYfffYRFn38zhaqszeETX8HiIvahZhXF5fNumBziYdmLdw8hkuN1A~emU6Xz9g~a1Ixfsq1Qr~guYoOtaw-0rOFxNRS9yMehE-2LCb8c-cAg6z5OdlN4qJDl~ZHgru4d~EHp~BpAK3v7u2Gi-8l1ygVW-1CHVna~fwnbOPN3ANPwh6~~yUit0Cx1f54XiNRn6-nPBQAEAAcAAA== -``` - -Skopiuj i wklej to połączenie @adresu-base64 hosta do swojej **prywatnej** @subskrypcji. - -### Przeskakiwanie bezpośrednie - -Na przykład wpisanie `pinkpaste.i2p` do okna *Hostname lookup* (a następnie zatwierdzenie) automatycznie przeniesie cię do strony **oraz** wstawi @lokalnie-unikalnego-hosta do książki adresowej. diff --git a/_i18n/pl/resources/moneropedia/lease-set.md b/_i18n/pl/resources/moneropedia/lease-set.md deleted file mode 100644 index 311cefaa..00000000 --- a/_i18n/pl/resources/moneropedia/lease-set.md +++ /dev/null @@ -1,23 +0,0 @@ ---- -tags: ["kovri"] -terms: ["LeaseSet", "LeaseSets"] -summary: "Zestaw wszystkich aktualnie zautoryzowanych leasów dla pojedynczego węzła docelowego I2P." ---- - -### Podstawy - -Lease-Set jest zestawem zautoryzowanych @leasów (i pozostałych istotnych informacji) dla pojedynczego @węzła-docelowego sieci @I2P. - -### Szczegółowe informacje - -Lease Set zawiera: - -- wszystkie aktualnie zautoryzowane leasy dla pojedynczego węzła docelowego -- publiczny klucz, według którego zaszyfrowane mogą być @wiadomości (zobacz: @trasowanie-czosnkowe) -- publiczny klucz podpisu, który może zostać użyty do unieważnienia danej wersji struktury - -Lease Set jest jedną z dwóch struktur przechowywanych w @bazie-danych-sieci (drugą są @informacje-o-routerze) i zaszyfrowany jest funkcją SHA256 zawartego @węzła-docelowego. - -### Adnotacje - -Aby dowiedzieć się więcej, przejdź do strony [LeaseSet](https://geti2p.net/en/docs/how/network-database#leaseSet) @Java-I2P. diff --git a/_i18n/pl/resources/moneropedia/lease.md b/_i18n/pl/resources/moneropedia/lease.md deleted file mode 100644 index 1219718b..00000000 --- a/_i18n/pl/resources/moneropedia/lease.md +++ /dev/null @@ -1,13 +0,0 @@ ---- -tags: ["kovri"] -terms: ["Lease", "Leases", "leasów"] -summary: "Autoryzuje tunel sieci I2P do otrzymywania wiadomości przeznaczonych do węzła docelowego." ---- - -### Podstawy - -Lease definiuje autoryzację pojedynczego @tunelu sieci @I2P do otrzymywania @wiadomości przeznaczonych do @węzła-docelowego. - -### Szczegółowe informacje - -Aby dowiedzieć się więcej, przejdź do strony na temat [Lease'u](https://geti2p.net/spec/common-structures#lease) w @Java-I2P. diff --git a/_i18n/pl/resources/moneropedia/message.md b/_i18n/pl/resources/moneropedia/message.md deleted file mode 100644 index 35428c54..00000000 --- a/_i18n/pl/resources/moneropedia/message.md +++ /dev/null @@ -1,31 +0,0 @@ ---- -tags: ["kovri"] -terms: ["Message", "Messages", "wiadomość", "wiadomości", "wiadomością", "wiadomościami", "wiadomościom", "wiadomościach"] -summary: "Mechanizm, dzięki któremu informacje są przekazywane wewnątrz sieci I2P." ---- - -### Podstawy - -*Wiadomości* (które istnieją w wierzchniej warstwie @transportu), zawierają różne informacje potrzebne sieci, ale przede wszystkim to, co widzisz, robisz, wysyłasz i otrzymujesz, jest transportowane za pomocą *wiadomości*. - -Istnieją dwa podstawowe rodzaje *wiadomości* w sieci @I2P: - -- wiadomości tunelowe -- wiadomości I2NP - -Zasadniczo to: *wiadomości tunelowe* **zawierają** **fragmenty wiadomości** @I2NP, które następnie są [składane w całość](https://geti2p.net/en/docs/tunnels/implementation) w pewnym momencie ścieżki tunelowej. - -### Szczegółowe informacje - -Wiadomości @I2NP są blisko związane z wiadomościami tunelowymi, co sprawia, że łatwo pomylić pojęcie *wiadomości* przy czytaniu specyfikacji sieci @Java-I2P: - -> -1. Najpierw furtka tunelu zbiera wiele wiadomości I2NP i przetwarza je w wiadomości tunelowe do wysłania. -2. Następnie furtka szyfruje przetworzone dane i przekazuje je do pierwszego hopu. -3. Peer i kolejni uczestnicy tunelu odkrywają warstwę szyfrowania, weryfikując ją przeciwko duplikatom, a następnie przekazuje dalej do kolejnego peeru. -4. Na końcu wiadomość tunelowa dochodzi do punktu końcowego, gdzie pierwotnie zwinięte przy furtce wiadomości I2NP są składane w całość i przekazywane zgodnie z poleceniem. - -### Adnotacje - -- Wiadomości I2NP muszą być podzielone, ponieważ różnią się rozmiarem (od 0 do prawie 64 KB), a wiadomości tunelowe mają stały rozmiar (około 1 KB). -- Aby dowiedzieć się więcej na temat szczegółów i specyfikacji, przejdź do strony [specyfikacji I2NP](https://geti2p.net/spec/i2np) oraz [specyfikacji wiadomości tunelowych](https://geti2p.net/spec/tunnel-message). diff --git a/_i18n/pl/resources/moneropedia/network-database.md b/_i18n/pl/resources/moneropedia/network-database.md deleted file mode 100644 index 44fef4f5..00000000 --- a/_i18n/pl/resources/moneropedia/network-database.md +++ /dev/null @@ -1,23 +0,0 @@ ---- -tags: ["kovri"] -terms: ["Network-Database", "baza-danych-sieci", "bazie-danych-sieci", "bazą-danych-sieci", "bazy-danych-sieci"] -summary: "Rozproszona baza danych zawierająca potrzebne informacje na temat routera, aby sieć pozostała nienaruszona." ---- - -### Podstawy - -Baza danych sieci jest [rozproszoną bazą danych](https://en.wikipedia.org/wiki/Distributed_database) zawierającą informacje na temat routera, które muszą być używane przez peerów, aby sieć pozostała nienaruszona. - -### Szczegółowe informacje - -Za: @Java-I2P: - -> -Baza danych sieci @I2P jest specjalną rozproszoną bazą danych zawierającą tylko dwa rodzaje danych - informacje kontaktowe routera (@informacje-o-routerze) oraz informacje kontaktowe @węzła docelowego (@LeaseSets). Każda informacja jest podpisana przez odpowiednią stronę i zweryfikowana przez kogokolwiek, kto jej używa lub ją przechowuje. Dodatkowo dane posiadają informacje na temat żywotności, zezwalając na odrzucenie nieistotnych wprowadzeń, nadpisywanie nowszych wprowadzeń nad starszymi oraz na ochronę przed pewnymi rodzajami ataków. - -> -Baza danych sieci jest rozproszona poprzez prostą technikę zwaną "@floodfill", w której jest utrzymywana przez podzbiór wszystkich routerów, zwanych "routerami floodfill". - -### Adnotacje - -Aby dowiedzieć się więcej, przejdź do [bazy danych sieci](https://geti2p.net/en/docs/how/network-database). diff --git a/_i18n/pl/resources/moneropedia/ntcp.md b/_i18n/pl/resources/moneropedia/ntcp.md deleted file mode 100644 index 11b476dd..00000000 --- a/_i18n/pl/resources/moneropedia/ntcp.md +++ /dev/null @@ -1,32 +0,0 @@ ---- -tags: ["kovri"] -terms: ["NTCP"] -summary: "Protokół Kontroli Transmisji oparty na nieblokowaniu wejścia/wyjścia: jeden z dwóch środków transportów Kovri." ---- - -### Podstawy - -*Protokół Kontroli Transmisji oparty na nieblokowaniu wejścia/wyjścia (NTCP)* jest jednym z dwóch szyfrowanych środków @transportu w @Kovri. - -Podobnie do @SSU, *głównym* przeznaczeniem NTCP jest bezpieczny transport @wiadomości @in-net w sieci @I2NP poprzez @tunele, jednak w odróżnieniu od SSU, NTCP działa jedynie za pomocą zaszyfrowanego [Protokołu Kontroli Transmisji](https://en.wikipedia.org/wiki/Transmission_Control_Protocol). - -### Szczegółowe informacje - - Przekazuje pojedyncze wiadomości I2NP, po tym jak: - - został ustanowiony Protokół Kontroli Transmisji - - została ukończona sekwencja ustanowienia - Korzysta z następujących @szyfrowań: - - 2048-bitowy [Diffie-Hellman](https://en.wikipedia.org/wiki/Diffie-hellman) - - [AES-256](https://en.wikipedia.org/wiki/Advanced_Encryption_Standard)/[CBC](https://en.wikipedia.org/wiki/Block_cipher_modes_of_operation) -Sekwencja ustanowienia składa się z następujących *stanów*: - - Pre-ustanowienie - - ustanowienie - - Post-ustanowienie or "Ustanowione" - Korzysta z następujących charakterystyk @bazy-danych-sieci: - - Nazwa środka transportu: NTCP - - Host: IP (IPv4 lub IPv6) lub nazwa hosta (skrócony adres IPv6 (wraz z "::") jest dozwolony) - - Port: 1024 - 65535 - -### Adnotacje - -Aby dowiedzieć się więcej, przejdź do strony [NTCP](https://geti2p.net/en/docs/transport/ntcp) @Java-I2P. diff --git a/_i18n/pl/resources/moneropedia/reseed.md b/_i18n/pl/resources/moneropedia/reseed.md deleted file mode 100644 index d6fb1d52..00000000 --- a/_i18n/pl/resources/moneropedia/reseed.md +++ /dev/null @@ -1,15 +0,0 @@ ---- -tags: ["kovri"] -terms: ["Reseed", "reseeda"] -summary: "Metoda, za pomocą której Kovri uruchamia sieć I2P." ---- - -### Podstawy - -Gdy uruchamiasz @Kovri po raz pierwszy (lub jeśli był wyłączony przez dłuższy czas), będzie on potrzebował listy peerów, z którymi się skontaktuje, aby dokonać [bootstrapu](https://en.wikipedia.org/wiki/Bootstrap) do sieci @I2P. Kovri bierze tę listę ze specjalnego pliku przechowywanego na serwerze reseed. W pliku tym znajdują się wszystkie informacje, których Kovri potrzebuje do połączenia się z peerami I2P. - -### Szczegółowe informacje - -Kovri posiada listę [mocno zakodowanych](https://en.wikipedia.org/wiki/Hard-coded) serwerów reseed, dostępnych aby z nich pobierać. Serwery te bezpiecznie serwują plik [SU3](https://geti2p.net/spec/updates#su3), opatrzony kryptograficznym @podpisem, ponad siecią @clearnet przy użyciu [HTTPS](https://en.wikipedia.org/wiki/HTTPS). Plik SU3 zawiera informacje służące do weryfikacji integralności pliku i jego zawartości. - -Poza elementami technicznymi koniecznymi do weryfikacji i przetworzenia, plik ten zawiera przede wszystkim serię plików z @informacjami-o-routerze, których routery Kovri i I2P używają do lokalizacji i komunikacji z pozostałymi peerami I2P, którzy następnie zapisywani są w @bazie-danych-sieci. diff --git a/_i18n/pl/resources/moneropedia/router-info.md b/_i18n/pl/resources/moneropedia/router-info.md deleted file mode 100644 index 9f4fddf2..00000000 --- a/_i18n/pl/resources/moneropedia/router-info.md +++ /dev/null @@ -1,66 +0,0 @@ ---- -tags: ["kovri"] -terms: ["Router-Info", "Router-infos", "informacje-o-routerze", "informacjom-o-routerze", "informacjami-o-routerze", "informacji-o-routerze"] -summary: "Struktura danych lub plik zawierający potrzebne informacje sieciowe na temat peerów I2P." ---- - -### Podstawy - -Informacje o routerze są strukturą danych (cyklicznie zapisywaną w [pliku binarnym](https://en.wikipedia.org/wiki/Binary_file)), która zawiera wszystkie informacje potrzebne do zlokalizowania, zidentyfikowania i skomunikowania się z peerem sieci @I2P. Zawiera ona adres IP, tożsammość routera i inne szczegóły techniczne potrzebne do @bazy-danych-sieci i jest publikowana do routerów @floodfill. - -### Szczegółowe informacje - -Czytelna forma informacji o routerze może wyglądać następująco: - -``` -Identity: [RouterIdentity: -Hash: nYZ5Qe7gQ-~QgfgJVRUG4c0JnVeVqzM~duUX1EGT1ek= -Certificate: [Certificate: type: Key certificate -Crypto type: 0 -Sig type: 7 (EdDSA_SHA512_Ed25519)] -PublicKey: [PublicKey: size: 256] -SigningPublicKey: [SigningPublicKey EdDSA_SHA512_Ed25519: size: 32] -Padding: 96 bytes] -Signature: [Signature EdDSA_SHA512_Ed25519: size: 64] -Published: Sun Oct 09 01:34:59 UTC 2016 -Options (5): - [caps] = [LfR] - [netId] = [2] - [netdb.knownLeaseSets] = [37] - [netdb.knownRouters] = [2435] - [router.version] = [0.9.26] -Addresses (4): -[RouterAddress: -Type: SSU -Cost: 4 -Options (5): - [caps] = [BC] - [host] = [2a01:e35:8b5c:b240:71a2:6750:8d4:47fa] - [key] = [nYZ5Qe7gQ-~QgfgJVRUG4c0JnVeVqzM~duUX1EGT1ek=] - [mtu] = [1472] - [port] = [22244]] -[RouterAddress: -Type: NTCP -Cost: 9 -Options (2): - [host] = [2a01:e35:8b5c:b240:71a2:6750:8d4:47fa] - [port] = [22244]] -[RouterAddress: -Type: SSU -Cost: 6 -Options (4): - [caps] = [BC] - [host] = [88.181.203.36] - [key] = [nYZ5Qe7gQ-~QgfgJVRUG4c0JnVeVqzM~duUX1EGT1ek=] - [port] = [22244]] -[RouterAddress: -Type: NTCP -Cost: 11 -Options (2): - [host] = [88.181.203.36] - [port] = [22244]]] -``` - -### Adnotacje - -Aby dowiedzieć się więcej na temat specyfikacji, przejdź do strony [Bazy Danych Sieci](https://geti2p.net/en/docs/how/network-database) @Java-I2P. diff --git a/_i18n/pl/resources/moneropedia/ssu.md b/_i18n/pl/resources/moneropedia/ssu.md deleted file mode 100644 index bb0735d5..00000000 --- a/_i18n/pl/resources/moneropedia/ssu.md +++ /dev/null @@ -1,24 +0,0 @@ ---- -tags: ["kovri"] -terms: ["SSU"] -summary: "Bezpieczny Semi niezawodny Protokół Pakietów Użytkownika: jeden z dwóch środków transportu Kovri." ---- - -### Podstawy - -*Bezpieczny Semi niezawodny Protokół Pakietów Użytkownika (SS UDP)* jest jednym z dwóch szyfrowanych środków @transportu w @Kovri. - -Podobnie do @NTCP, głównym przeznaczeniem NTCP jest bezpieczny transport @wiadomości @in-net w sieci @I2NP poprzez @tunele, jednak w odróżnieniu od NTCP, SSU działa jedynie za pomocą zaszyfrowanego [Protokołu Pakietów Użytkownika](https://en.wikipedia.org/wiki/User_Datagram_Protocol). - -### Szczegółowe informacje - -- Tak jak i NTCP, SSU jest zorientowanym na połączenie środkiem transportu danych od punktu do punktu -- Pojęcie *semi-niezawodny* bierze się z ciągłej retransmisji *niepotwierdzonych* wiadomości (aż do maksymalnej liczby, a następnie spada) -- SSU dostarcza również wiele pojedynczych usług (poza swoją główną funkcją jako warstwy transportowej): - - wykrywanie IP (poprzez kontrolę lokalną lub za pomocą [testu peerów](https://geti2p.net/en/docs/transport/ssu#peerTesting)) - - [Translacja Adresów Sieciowych](https://en.wikipedia.org/wiki/Network_address_translation) przy użyciu [introduktorów](https://geti2p.net/en/docs/transport/ssu#introduction) - - status [Firewall](https://en.wikipedia.org/wiki/Firewall_%28computing%29) oraz, jeśli wdrożone, SSU może informować NTCP o zmianie statusu adresu zewnętrznego lub firewalla - -### Adnotacje - -Aby dowiedzieć się więcej, przejdź do strony [SSU](https://geti2p.net/en/docs/transport/ssu) @Java-I2P. diff --git a/_i18n/pl/resources/moneropedia/subscription.md b/_i18n/pl/resources/moneropedia/subscription.md deleted file mode 100644 index febbd5c7..00000000 --- a/_i18n/pl/resources/moneropedia/subscription.md +++ /dev/null @@ -1,46 +0,0 @@ ---- -tags: ["kovri"] -terms: ["Subscription", "subskrypcja", "subskrypcji", "subskrypcją", "subskrypcję", "subsckrypcji"] -summary: "Plik używany przez książkę adresową zawierający hosty I2P sparowane z węzłami docelowymi I2P." ---- - -### Podstawy - -Subskrypcja jest plikiem, który zawiera listę hostów `.i2p` sparowanych z odpowiednimi @węzłami-docelowymi. Subskrypcje używane są przez @książki-adresowe. - -### Szczegółowe informacje - -Podobnie do tego, jak [plik hostów](https://en.wikipedia.org/wiki/Hosts_(file)) łączy nazwę hostu internetowego z konkretnym adresem, subskrypcja przypisuje adres `.i2p` do @adresu-base64 poprzez użycie następującego formatu (bez spacji): `host=address` - -Dokładniej, subskrypcja paruje @lokalnie-unikalny-host z @adresem-base64. - -Przykład: - -``` -anonimal.i2p=AQZGLAMpI9Q0l0kmMj1vpJJYK3CjLp~fE3MfvE-e7KMKjI5cPOH6EN8m794uHJ6b09qM8mb9VEv1lVLEov~usVliTSXCSHuRBOCIwIOuDNU0AbVa4BpIx~2sU4TxKhoaA3zQ6VzINoduTdR2IJhPvI5xzezp7dR21CEQGGTbenDslXeQ4iLHFA2~bzp1f7etSl9T2W9RID-KH78sRQmzWnv7dbhNodMbpO6xsf1vENf6bMRzqD5vgHEHZu2aSoNuPyYxDU1eM6--61b2xp9mt1k3ud-5WvPVg89RaU9ugU5cxaHgR927lHMCAEU2Ax~zUb3DbrvgQBOTHnJEx2Fp7pOK~PnP6ylkYKQMfLROosLDXinxOoSKP0UYCh2WgIUPwE7WzJH3PiJVF0~WZ1dZ9mg00c~gzLgmkOxe1NpFRNg6XzoARivNVB5NuWqNxr5WKWMLBGQ9YHvHO1OHhUJTowb9X90BhtHnLK2AHwO6fV-iHWxRJyDabhSMj1kuYpVUBQAEAAcAAA== -``` - -1. `anonimal.i2p`jest @lokalnie-unikalnym-hostem -2. `=` jest separatorem -3. Wszystko pozostałe jest @adresem-base64 - -### Rodzaje subskrypcji - -Istnieją dwa rodzaje plików subskrypcji w @Kovri: *publiczne* i *prywatne*. - -Subskrypcja *publiczna*: -- jest używana podczas ładowania podstawowych usług, takich jak IRC, e-mail, Monero itd. -- jest statyczna i odświeżana co 12 godzin przez serwer @książki-adresowej Monero -- pozwala na bezpieczne dzielene się subskrypcją ze wszystkimi, ponieważ jest publicznie dostępna (każdy, kto posiada tę samą publiczną subskrypcję, będzie mógł również przypisać tę samą nazwę hosta do tego samego węzła docelowego, co ty). - -Subskrypcja *prywatna*: -- jest używana wyłącznie przez ciebie i nie jest dzielona z innymi użytkownikami, chyba że wyraźnie zdecydujesz na jej upublicznienie -- plikiem domyślnym jest `private_hosts.txt` w twoim @katalogu-danych. - -### Aktualizowanie prywatnej subskrypcji - -Możesz skorzystać z @opcji-przeskakiwania, aby ręcznie zaktualizować swoją prywatną subskrypcję. Zaktualizowany plik zostanie następnie włączony do książki adresowej i gotowy do użycia. - -### Adnotacje - -Aby dowiedzieć się, w jaki sposób zapisać się do wielu subskrypcji, przejdź do [przewodnika dla użytkowników](https://gitlab.com/kovri-project/kovri-docs/blob/master/i18n/en/user_guide.md). diff --git a/_i18n/pl/resources/moneropedia/transports.md b/_i18n/pl/resources/moneropedia/transports.md deleted file mode 100644 index bf9179d7..00000000 --- a/_i18n/pl/resources/moneropedia/transports.md +++ /dev/null @@ -1,18 +0,0 @@ ---- -tags: ["kovri"] -terms: ["Transports", "Transport", "Transporty", "Transport", "transportowi", "transportem", "transportami", "transportowej", "transportu"] -summary: "Dwie zaszyfrowane warstwy transportu w Kovri." ---- - -### Podstawy - -Sieć @I2P składa się z dwóch zaszyfrowanych technologii warstw transportu, które umożliwiają @Kovri na bezpieczne korzystanie z połączeń [TCP/IP](https://en.wikipedia.org/wiki/Tcp/ip). Technologie te (@SSU i @NTCP) nazywają się *transportami*. - -### Szczegółowe informacje - -@SSU jest zaszyfrowanym [Protokołem Pakietów Użytkownika](https://en.wikipedia.org/wiki/User_Datagram_Protocol), a @NTCP jest zaszyfrowanym [Protokołem Sterowania Transmisją](https://en.wikipedia.org/wiki/Transmission_Control_Protocol). Obie technologie oparte są na @szyfrowaniu w [warstwie transportu](https://en.wikipedia.org/wiki/Transport_layer), aby @wiadomości na wyższych poziomach mogły być wysyłane przez @tunele wewnątrz sieci @I2P. - -### Adnotacje - -- Przeczytaj o transportach sieci @I2P [tutaj](https://geti2p.net/en/docs/transport). -- Przeczytaj o warstwach transportu wewnątrz [modelu OSI](https://en.wikipedia.org/wiki/OSI_model). diff --git a/_i18n/pl/resources/moneropedia/tunnel.md b/_i18n/pl/resources/moneropedia/tunnel.md deleted file mode 100644 index ea40dec9..00000000 --- a/_i18n/pl/resources/moneropedia/tunnel.md +++ /dev/null @@ -1,35 +0,0 @@ ---- -tags: ["kovri"] -terms: ["Tunnel", "Tunnels", "tunel", "tunele", "tunelem", "tunelowi", "tunelom", "tunelami", "tunelowe", "tunelu"] -summary: "Jednokierunkowe ścieżki wirtualne, które przekazują wiadomości przez ustaloną sekwencję routerów sieci I2P." ---- - -### Podstawy - -Gdy korzystasz z sieci @I2P (odwiedzasz @eepsite lub używasz @serwisu-czosnkowego), najpierw musisz połączyć się z peerem za pomocą środka @transportu, a następnie stworzyć wirtualne *tunele*. Tunele te są czasowymi, jednokierunkowymi ścieżkami, które przekazują @wiadomości przez ustaloną sekwencję routerów sieci I2P aż do @węzła-końcowego. Są zbudowane i korzystają z warstwowego @szyfrowania-czosnkowego, a ich głównym przeznaczeniem jest transport wszystkich wiadomości @I2NP. - -Każdy peer buduje przynajmniej *dwa* jednokierunkowe tunele: jeden dla **ruchu wejściowego** i jeden dla **ruchu wyjściowego**. Tunele te są nazywane albo **tunelami wejścia** (gdzie wiadomości skierowane są do twórcy tunelu) lub **tunelami wyjścia** (gdzie to twórca tunelu wysyła wiadomości), stąd aby wiadomość została przekazana w obie strony i odpowiedziana węzłowi końcowego potrzebne są *cztery* tunele (dwa dla twórcy i dwa dla odbiorcy). - -### Szczegółowe informacje - -Za: @Java-I2P: - -> -Wewnątrz sieci I2P wiadomości przekazywane są w jednym kierunku przez wirtualne tunele peerów, które używają jakiegokolwiek dostępnego środka, aby przesłać wiadomość do następnego hopu. Wiadomości dochodzą do furtki @tunelu, są łączone i/lub dzielone do stałych rozmiarów i następnie przekazywane dalej do następnego hopu w tunelu, który je przetwarza i weryfikuje ich ważność i przesyła dalej aż dotrą do końca tunelu. Punkt końcowy przekazuje złączoną przy furtce wiadomość zgodnie z instrukcjami - do kolejnego routera, do innego tunelu lub lokalnie. - -> -Wszystkie tunele działają tak samo, ale mogą być podzielona na dwie grupy: tunele wejścia i tunele wyjścia. Tunele wejścia posiadają niezaufaną furtkę, która przekazuje wiadomości w kierunku twórcy tunelu będącego jego punktem końcowym. W tunelach wyjścia to twórca służy jako furtka przekazująca wiadomości do oddalonego punktu końcowego. - -> -Twórca tunelu wybiera który konkretny peer weźmie udział w tunelu i zapewnia wszystkim niezbędne dane konfiguracyjne. Tunele mogą składać się z dowolnej liczby hopów. Założeniem jest utrudnić członkom oraz osobom trzecim odgadnięcie długości tunelu, a nawet nie ujawniać uczestnikom, czy należą do tego samego tunelu (z wyjątkiem sytuacji, gdy znajdują się oni obok siebie). - -### Adnotacje - -Za: @Java-I2P: - -> -I2P jest z natury siecią z komutacją pakietów, nawet posiadając tunele, co pozwala na uruchomienie wielu tuneli równolegle, zwiększając jej elastyczność i obciążenie równoważące. Mimo że tunele w sieci I2P przypominają sieć z komutacją łączy, wszystko wewnątrz niej jest ściśle oparte na wiadomościach, a tunele są jedynie środkiem na organizację ich dostawy. Nie ma żadnych założeń dotyczących niezawodności lub porządkowania wiadomości, a retransmisje pozostają na wyższych poziomach (np. w bibliotece strumieniowej warstwy klienta I2P). - -### Dokumenty - -Aby przeczytać specyfikacje i szczegółową dokumentację, przejdź do strony [trasowania tunelowego](https://geti2p.net/en/docs/how/tunnel-routing) i [implementacji tunelów](https://geti2p.net/en/docs/tunnels/implementation). diff --git a/_i18n/pt-br/resources/moneropedia/base32-address.md b/_i18n/pt-br/resources/moneropedia/base32-address.md deleted file mode 100644 index 0e3a88e2..00000000 --- a/_i18n/pt-br/resources/moneropedia/base32-address.md +++ /dev/null @@ -1,26 +0,0 @@ ---- -tags: ["kovri"] -terms: ["Base32-address", "Base32-addresses"] -summary: "Base32 encoded hash of a Base64 address" ---- - -{% include untranslated.html %} -### The Basics - -A Base32 address is a shortened, encoded version of an @I2P address. The Base32 address is the first part in a `.b32.i2p` hostname. - -Example: - -`i35yftyyb22xhcvghmev46t5knefur5v66qzekkajatwfwhyklvq.b32.i2p` - -where - -`i35yftyyb22xhcvghmev46t5knefur5v66qzekkajatwfwhyklvq` is the Base32 address. - -### In-depth Information - -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. - -### Notes - -**Note: `.b32` is not a sub-domain of `.i2p`** diff --git a/_i18n/pt-br/resources/moneropedia/base64-address.md b/_i18n/pt-br/resources/moneropedia/base64-address.md deleted file mode 100644 index b9985658..00000000 --- a/_i18n/pt-br/resources/moneropedia/base64-address.md +++ /dev/null @@ -1,21 +0,0 @@ ---- -tags: ["kovri"] -terms: ["Base64-address", "Base64-addresses"] -summary: "Base64 encoded I2P destination" ---- - -{% include untranslated.html %} -### The Basics - -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: - -``` -AQZGLAMpI9Q0l0kmMj1vpJJYK3CjLp~fE3MfvE-e7KMKjI5cPOH6EN8m794uHJ6b09qM8mb9VEv1lVLEov~usVliTSXCSHuRBOCIwIOuDNU0AbVa4BpIx~2sU4TxKhoaA3zQ6VzINoduTdR2IJhPvI5xzezp7dR21CEQGGTbenDslXeQ4iLHFA2~bzp1f7etSl9T2W9RID-KH78sRQmzWnv7dbhNodMbpO6xsf1vENf6bMRzqD5vgHEHZu2aSoNuPyYxDU1eM6--61b2xp9mt1k3ud-5WvPVg89RaU9ugU5cxaHgR927lHMCAEU2Ax~zUb3DbrvgQBOTHnJEx2Fp7pOK~PnP6ylkYKQMfLROosLDXinxOoSKP0UYCh2WgIUPwE7WzJH3PiJVF0~WZ1dZ9mg00c~gzLgmkOxe1NpFRNg6XzoARivNVB5NuWqNxr5WKWMLBGQ9YHvHO1OHhUJTowb9X90BhtHnLK2AHwO6fV-iHWxRJyDabhSMj1kuYpVUBQAEAAcAAA== -``` - - -### In-depth Information - -See @destination for details behind @base64-address diff --git a/_i18n/pt-br/resources/moneropedia/data-directory.md b/_i18n/pt-br/resources/moneropedia/data-directory.md deleted file mode 100644 index 761cfd46..00000000 --- a/_i18n/pt-br/resources/moneropedia/data-directory.md +++ /dev/null @@ -1,21 +0,0 @@ ---- -tags: ["kovri"] -terms: ["Data-Directory"] -summary: "Where essential kovri data for runtime is stored" ---- - -{% include untranslated.html %} -### The Basics - -Depending on your OS, @Kovri currently stores all run-time data in the following directory: - -- Linux/FreeBSD: - - `$HOME/.kovri` - -- OSX: - - `$HOME/Library/Application\ Support/Kovri` - -- Windows: - - `"$APPDATA"\\Kovri` - -This includes all configuration files, @address-book, certificates, and resources. diff --git a/_i18n/pt-br/resources/moneropedia/eepsite.md b/_i18n/pt-br/resources/moneropedia/eepsite.md deleted file mode 100644 index cd450d97..00000000 --- a/_i18n/pt-br/resources/moneropedia/eepsite.md +++ /dev/null @@ -1,29 +0,0 @@ ---- -tags: ["kovri"] -terms: ["Eepsite", "Hidden-Service", "Garlic-Site", "Garlic-Service"] -summary: "A website or service hosted within the I2P network" ---- - -{% include untranslated.html %} -### The Basics - -Is it [**EEP!** *(in response to the site's content)*](https://en.wikipedia.org/wiki/Onomatopoeia), or **end-to-end protocol**, or something else entirely different? - -While the original definition of eepsite has been lost with time, its use-case remains: an eepsite is a website or service that is hosted within (and only accessible by) the @I2P network. - -### In-depth Information - -Alternate names include: - -1. *Hidden Service* - - because the site/service is *hidden* within the @I2P network and can only be visited within the network -2. *Garlic Site* - - because the website utilizes @I2P's @garlic-routing technology as a means of communicating with a client - - because the service is hosted as a website and not any other type of service -3. *Garlic Service* - - because the service utilizes @I2P's @garlic-routing technology as a means of communicating with a client - - because the service is specific to services like IRC, email, or a Monero peer (but may also include websites) - -### Notes - -To learn how to setup an Eepsite (Hidden Service, Garlic Site, Garlic Service) visit the @Kovri [user-guide](https://gitlab.com/kovri-project/kovri-docs/blob/master/i18n/en/user_guide.md). diff --git a/_i18n/pt-br/resources/moneropedia/floodfill.md b/_i18n/pt-br/resources/moneropedia/floodfill.md deleted file mode 100644 index cccd9011..00000000 --- a/_i18n/pt-br/resources/moneropedia/floodfill.md +++ /dev/null @@ -1,14 +0,0 @@ ---- -tags: ["kovri"] -terms: ["Floodfill"] -summary: "An I2P router which maintains a distributed network-database" ---- - -{% include untranslated.html %} -### The Basics - -By actively managing a distributed network-database, a router with *floodfill* capability has the ability to help maintain network stability and resiliancy while also being decentralized and trust-less. - -### In-depth information - -Though floodfill itself is a simple storage system, the technical underpinnings of floodfill as it relates to @network-database and other protocols within @I2P are much more complex. Visit the [Network Database](https://geti2p.net/en/docs/how/network-database) page for details. diff --git a/_i18n/pt-br/resources/moneropedia/garlic-encryption.md b/_i18n/pt-br/resources/moneropedia/garlic-encryption.md deleted file mode 100644 index a0548b3c..00000000 --- a/_i18n/pt-br/resources/moneropedia/garlic-encryption.md +++ /dev/null @@ -1,24 +0,0 @@ ---- -tags: ["kovri"] -terms: ["Garlic-Encryption", "Layered-Encryption"] -summary: "Layered encryption as implemented in Kovri / I2P" ---- - -{% include untranslated.html %} -### The Basics - -@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 - -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. diff --git a/_i18n/pt-br/resources/moneropedia/garlic-routing.md b/_i18n/pt-br/resources/moneropedia/garlic-routing.md deleted file mode 100644 index 4a1d26b9..00000000 --- a/_i18n/pt-br/resources/moneropedia/garlic-routing.md +++ /dev/null @@ -1,44 +0,0 @@ ---- -tags: ["kovri"] -terms: ["Garlic-Routing"] -summary: "Routing technology as implemented in Kovri" ---- - -{% include untranslated.html %} -### 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. - -The @Garlic-Encryption of @Garlic-Routing is similar to the @Layered-Encryption of [Onion Routing](https://en.wikipedia.org/wiki/Onion_routing) and effectively conceals the IP address of the sender and secures information sent from the sender to its @destination (and vice-versa). - -### 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](http://www.freehaven.net/papers.html) (Section 8.1.1) as derived from the term Onion Routing. - -As recent as October of 2016, [#tor-dev](https://oftc.net/WebChat/) has offered insight into the creation of the term *@garlic-routing*: - -[Nick Mathewson](https://en.wikipedia.org/wiki/The_Tor_Project,_Inc): ->[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](https://en.wikipedia.org/wiki/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 was 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 (similar to the @layered-encryption in Onion Routing) -- Bundling multiple @messages together (garlic cloves) -- ElGamal/AES @encryption - -*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 - -- In terms of Onion/Garlic Routing, another way to envision layered @encryption is by replacing the onion/garlic with a [Matryoshka doll](https://en.wikipedia.org/wiki/Matryoshka_doll) - with each outer/inner doll having a lock and public key to the next/previous doll -- For more technical details on Garlic Routing, read the @Java-I2P entry on [Garlic Routing](https://geti2p.net/en/docs/how/garlic-routing) diff --git a/_i18n/pt-br/resources/moneropedia/i2np.md b/_i18n/pt-br/resources/moneropedia/i2np.md deleted file mode 100644 index 1e7841ae..00000000 --- a/_i18n/pt-br/resources/moneropedia/i2np.md +++ /dev/null @@ -1,27 +0,0 @@ ---- -tags: ["kovri"] -terms: ["I2NP"] -summary: "The I2P Network Protocol: the mechanism in which I2NP messages are sent over the I2P network" ---- - -{% include untranslated.html %} -### The Basics - -From @Java-I2P: - -> -@I2NP manages the routing and mixing of messages between routers, as well as the selection of what transports to use when communicating with a peer for which there are multiple common transports supported - -### In-depth information - -From @Java-I2P: - -> -@I2NP (@I2P Network Protocol) @messages can be used for one-hop, router-to-router, point-to-point @messages. By @encrypting and wrapping @messages in other @messages, they can be sent in a secure way through multiple hops to the ultimate @destination. @I2NP does not specify nor require any particular @transport layer but does require at least one @transport in use. - -> -Whenever a @destination wants to send a message to to another @destination, it provides its local router with both the @destination structure and the raw bytes of the message to be sent. The router then determines where to send it, delivers it through outbound @tunnels, instructing the end point to pass it along to the appropriate inbound @tunnel, where it is passed along again to that @tunnel's end point and made available to the target for reception. - -### Notes - -Read more about the @I2NP [protocol](https://geti2p.net/en/docs/protocol/i2np) and [specification](https://geti2p.net/spec/i2np). diff --git a/_i18n/pt-br/resources/moneropedia/i2p.md b/_i18n/pt-br/resources/moneropedia/i2p.md deleted file mode 100644 index 7a6980c3..00000000 --- a/_i18n/pt-br/resources/moneropedia/i2p.md +++ /dev/null @@ -1,30 +0,0 @@ ---- -tags: ["kovri"] -terms: ["I2P"] -summary: "The Invisible Internet Project: an anonymizing overlay network" ---- - -{% include untranslated.html %} -### Monero - -For Monero's implementation of @I2P, see @Kovri. For a comparison of @I2P to [Tor](https://torproject.org/), read the [Comparison](https://geti2p.net/en/comparison/tor) page. - -### The Basics - -From @Java-I2P: - ->The I2P network provides strong privacy protections for communication over the Internet. Many activities that would risk your privacy on the public Internet can be conducted anonymously inside I2P. - -### In-depth information - -From @Java-I2P: - ->I2P is an anonymous overlay network - a network within a network. It is intended to protect communication from dragnet surveillance and monitoring by third parties such as ISPs. - ->I2P is used by many people who care about their privacy: activists, oppressed people, journalists and whistleblowers, as well as the average person. - ->No network can be "perfectly anonymous". The continued goal of I2P is to make attacks more and more difficult to mount. Its anonymity will get stronger as the size of the network increases and with ongoing academic review. - -### Notes - -@I2P documentation and specifications are available [here](https://geti2p.net/docs/). diff --git a/_i18n/pt-br/resources/moneropedia/i2pcontrol.md b/_i18n/pt-br/resources/moneropedia/i2pcontrol.md deleted file mode 100644 index b419423c..00000000 --- a/_i18n/pt-br/resources/moneropedia/i2pcontrol.md +++ /dev/null @@ -1,16 +0,0 @@ ---- -tags: ["kovri"] -terms: ["I2PControl"] -summary: "An API inteface for Kovri and Java-I2P that allows simple remote control" ---- - -{% include untranslated.html %} -### The Basics - -@I2Pcontrol is a [JSONRPC2](https://en.wikipedia.org/wiki/JSON-RPC) [API](https://en.wikipedia.org/wiki/Application_programming_interface) for @Kovri and @Java-I2P which allows an @I2PControl client to remote control/monitor a running instance. - -Two available @I2PControl clients are: [qtoopie](https://github.com/EinMByte/qtoopie) (C++ client) and [itoopie](https://github.com/i2p/i2p.itoopie) (Java client). Read `kovri.conf` to configure @I2PControl for @Kovri. - -### In-depth information - -Details and specification available on the [I2PControl](https://geti2p.net/en/docs/api/i2pcontrol) page. diff --git a/_i18n/pt-br/resources/moneropedia/in-net.md b/_i18n/pt-br/resources/moneropedia/in-net.md deleted file mode 100644 index ec3c5c8a..00000000 --- a/_i18n/pt-br/resources/moneropedia/in-net.md +++ /dev/null @@ -1,14 +0,0 @@ ---- -tags: ["kovri"] -terms: ["In-net"] -summary: "Within the I2P network" ---- - -{% include untranslated.html %} -### The Basics - -**In-net** is a [colloquial](https://en.wikipedia.org/wiki/Colloquial) term of which describes activities, protocols, or functionality that exist *only* within the @I2P network. - -### In-depth information - -Example: *in-net download* would be defined as downloading *only* within @I2P. diff --git a/_i18n/pt-br/resources/moneropedia/java-i2p.md b/_i18n/pt-br/resources/moneropedia/java-i2p.md deleted file mode 100644 index 8a21da5d..00000000 --- a/_i18n/pt-br/resources/moneropedia/java-i2p.md +++ /dev/null @@ -1,14 +0,0 @@ ---- -tags: ["kovri"] -terms: ["Java-I2P"] -summary: "The original implementation of I2P - written in Java" ---- - -{% include untranslated.html %} -### The Basics - -The term "Java I2P" is often used to describe the original @I2P implementation currently most known and used today. There are various other @I2P implementations, including @Kovri; all of which look up to the original Java implementation. - -### Notes - -To download/learn more about the Java implementation, visit their [website](https://geti2p.net/). diff --git a/_i18n/pt-br/resources/moneropedia/jump-service.md b/_i18n/pt-br/resources/moneropedia/jump-service.md deleted file mode 100644 index a62c5276..00000000 --- a/_i18n/pt-br/resources/moneropedia/jump-service.md +++ /dev/null @@ -1,33 +0,0 @@ ---- -tags: ["kovri"] -terms: ["Jump-Service"] -summary: "An I2P website service that adds addresses to your address book" ---- - -{% include untranslated.html %} -### The Basics - -In your @I2P configured web browser, you can use a Jump Service to *jump* to an @I2P address that you don't have in your @address-book. Once you've *jumped* to the address, the address will be saved into your @address-book. - -### In-depth Information - -In an @I2P configured browser, visit: http://stats.i2p/i2p/lookup.html (courtesy of @Java-I2P's lead developer *zzz*) - -Then, you'll have two options: - -1. *Hostname lookup* the address you wish to visit and then manually copy/paste the result -2. *Jump* to the @I2P website by entering the @I2P hostname (**recommended**) - -### Using hostname lookup - -For example, entering `pinkpaste.i2p` into the *Hostname lookup* box (and then submitting) will return: - -``` -pinkpaste.i2p=m-HrPrIAsdxts0WM~P4mE8mt9P7g-QTaBvu7Gc6Nl0UX7Vwck-i~RvOPfK6W~kfdRvwhNTqevkBL2UF5l36We02Aiywu7kB2xOHRkze68h-Tg2ewvRVwokohguCD2G3wwAEz~7FVda2avYDCb9-N6TfuzxKLnmhPMvbNSjGL7ZsD2p-h207R3-2kvuMV9bfu-K~w9NI9XJhIyufvUnFYc2jnTVg8PbaR4UP57cNaOO2YIMPkbr6~yTcIu9B1sUfHK6-N~6virQDOxW4M-62rjnZkLpaCtkOsXslmCwZI--TkZ6hKi1kXZvNmJRE1rYfffYRFn38zhaqszeETX8HiIvahZhXF5fNumBziYdmLdw8hkuN1A~emU6Xz9g~a1Ixfsq1Qr~guYoOtaw-0rOFxNRS9yMehE-2LCb8c-cAg6z5OdlN4qJDl~ZHgru4d~EHp~BpAK3v7u2Gi-8l1ygVW-1CHVna~fwnbOPN3ANPwh6~~yUit0Cx1f54XiNRn6-nPBQAEAAcAAA== -``` - -Copy/paste this host=@base64-address pairing into your **private** @subscription. - -### Directly jumping - -For example, entering `pinkpaste.i2p` into the *Jump* box (and then submitting) will automatically redirect you to the website **and** insert the @locally-unique-host into @address-book. diff --git a/_i18n/pt-br/resources/moneropedia/lease-set.md b/_i18n/pt-br/resources/moneropedia/lease-set.md deleted file mode 100644 index 412f2005..00000000 --- a/_i18n/pt-br/resources/moneropedia/lease-set.md +++ /dev/null @@ -1,24 +0,0 @@ ---- -tags: ["kovri"] -terms: ["LeaseSet", "LeaseSets"] -summary: "Contains all currently authorized Leases for a particular I2P Destination" ---- - -{% include untranslated.html %} -### The Basics - -A Lease-Set contains a set of authorized @leases (and other related information) for a particular @destination. - -### In-depth information - -A Lease-Set contains: - -- all of the currently authorized @leases for a particular @destination -- the public key to which garlic messages can be encrypted (see @garlic-routing) -- the signing public key that can be used to revoke this particular version of the structure - -The Lease-Set is one of the two structures stored in the @network-database (the other being @router-info), and is keyed under the SHA256 of the contained @destination. - -### Notes - -For further details, read @Java-I2P's [LeaseSet](https://geti2p.net/en/docs/how/network-database#leaseSet) diff --git a/_i18n/pt-br/resources/moneropedia/lease.md b/_i18n/pt-br/resources/moneropedia/lease.md deleted file mode 100644 index cfb13659..00000000 --- a/_i18n/pt-br/resources/moneropedia/lease.md +++ /dev/null @@ -1,14 +0,0 @@ ---- -tags: ["kovri"] -terms: ["Lease", "Leases"] -summary: "Authorizes an I2P tunnel to receive messages targeting a destination" ---- - -{% include untranslated.html %} -### The Basics - -A lease defines the authorization for a particular @I2P @tunnel to receive a @messages targeting a @destination. - -### In-depth information - -For further details, read @Java-I2P's [Lease](https://geti2p.net/spec/common-structures#lease) diff --git a/_i18n/pt-br/resources/moneropedia/message.md b/_i18n/pt-br/resources/moneropedia/message.md deleted file mode 100644 index 975277a3..00000000 --- a/_i18n/pt-br/resources/moneropedia/message.md +++ /dev/null @@ -1,32 +0,0 @@ ---- -tags: ["kovri"] -terms: ["Message", "Messages"] -summary: "The mechanisms in which information travels within I2P" ---- - -{% include untranslated.html %} -### The Basics - -*Messages* (which exist on top of the @transports layer), contain varying types of information that are needed for the network but, most importantly, everything you see, do, send, or receive, will come and go in the form of *messages*. - -There are 2 essential types of *messages* in @I2P: - -- @Tunnel messages -- @I2NP messages - -Essentially: *@tunnel messages* **contain** @I2NP **message fragments** which are then [reassembled](https://geti2p.net/en/docs/tunnels/implementation) at certain points within a @tunnel's path. - -### In-depth information - -@I2NP messages have a close relationship with @tunnel @messages so it is easy to get the term *messages* confused when reading @Java-I2P specifications: - -> -1. First, the tunnel gateway accumulates a number of I2NP messages and preprocesses them into tunnel messages for delivery. -2. Next, that gateway encrypts that preprocessed data, then forwards it to the first hop. -3. That peer, and subsequent tunnel participants, unwrap a layer of the encryption, verifying that it isn't a duplicate, then forward it on to the next peer. -4. Eventually, the tunnel messages arrive at the endpoint where the I2NP messages originally bundled by the gateway are reassembled and forwarded on as requested. - -### Notes - -- @I2NP @messages need to be fragmented because they are variable in size (from 0 to almost 64 KB) and @tunnel @messages are fixed-size (approximately 1 KB). -- For details and specifications, visit the [I2NP spec](https://geti2p.net/spec/i2np) and [Tunnel Message spec](https://geti2p.net/spec/tunnel-message) diff --git a/_i18n/pt-br/resources/moneropedia/network-database.md b/_i18n/pt-br/resources/moneropedia/network-database.md deleted file mode 100644 index ac94231a..00000000 --- a/_i18n/pt-br/resources/moneropedia/network-database.md +++ /dev/null @@ -1,24 +0,0 @@ ---- -tags: ["kovri"] -terms: ["Network-Database"] -summary: "A distributed database which contains needed router information so the network can stay intact" ---- - -{% include untranslated.html %} -### The Basics - -@network-database is a [distributed database](https://en.wikipedia.org/wiki/Distributed_database) which contains router information that peers must use so the network can stay intact. - -### In-depth information - -From @Java-I2P: - -> -@I2P's @network-database is a specialized distributed database, containing just two types of data - router contact information (@Router-Infos) and @destination contact information (@LeaseSets). Each piece of data is signed by the appropriate party and verified by anyone who uses or stores it. In addition, the data has liveliness information within it, allowing irrelevant entries to be dropped, newer entries to replace older ones, and protection against certain classes of attack. - -> -The @network-database is distributed with a simple technique called "@floodfill", where a subset of all routers, called "@floodfill routers", maintains the distributed database. - -### Notes - -Read [Network-Database](https://geti2p.net/en/docs/how/network-database) for details. diff --git a/_i18n/pt-br/resources/moneropedia/ntcp.md b/_i18n/pt-br/resources/moneropedia/ntcp.md deleted file mode 100644 index 4c3f68b2..00000000 --- a/_i18n/pt-br/resources/moneropedia/ntcp.md +++ /dev/null @@ -1,33 +0,0 @@ ---- -tags: ["kovri"] -terms: ["NTCP"] -summary: "NIO-Based TCP (Non-blocking I/O based TCP): one of two Kovri transports" ---- - -{% include untranslated.html %} -### The Basics - -*NIO-Based TCP (Non-blocking I/O based TCP)* is one of two encrypted @transports for @Kovri. - -Similar to @SSU, @NTCP's *primary* purpose is to securely transmit @in-net @I2NP messages through @tunnels but, unlike @SSU, @NTCP functions solely over encrypted [TCP](https://en.wikipedia.org/wiki/Transmission_Control_Protocol). - -### In-depth information - - - Passes along individual @I2NP messages (both Standard and Time Sync) after: - - TCP has been established - - Establishment Sequence has been completed - - Uses the following @encryption: - - 2048-bit [Diffie-Hellman](https://en.wikipedia.org/wiki/Diffie-hellman) - - [AES-256](https://en.wikipedia.org/wiki/Advanced_Encryption_Standard)/[CBC](https://en.wikipedia.org/wiki/Block_cipher_modes_of_operation) - - Establishment Sequence has the following *states*: - - Pre-establishment - - Establishment - - Post-establishment or "Established" - - Uses the following from the @network-database: - - Transport name: NTCP - - Host: IP (IPv4 or IPv6) or host name (shortened IPv6 address (with "::") is allowed) - - Port: 1024 - 65535 - -### Notes - -For further details, read @Java-I2P's [NTCP](https://geti2p.net/en/docs/transport/ntcp) diff --git a/_i18n/pt-br/resources/moneropedia/reseed.md b/_i18n/pt-br/resources/moneropedia/reseed.md deleted file mode 100644 index 179f34c5..00000000 --- a/_i18n/pt-br/resources/moneropedia/reseed.md +++ /dev/null @@ -1,16 +0,0 @@ ---- -tags: ["kovri"] -terms: ["Reseed"] -summary: "The method of which Kovri uses to bootstrap into the I2P network" ---- - -{% include untranslated.html %} -### The Basics - -When you start @Kovri for the first time (or if it's been offline for a long time), @Kovri will need a list of peers to connect to so it can [bootstrap](https://en.wikipedia.org/wiki/Bootstrap) into the @I2P network. @Kovri gets these peers from a special file stored on a reseed server. On this file are all the various pieces of information @Kovri needs in order to connect with @I2P peers. - -### In-depth information - -@Kovri has a list of [hard-coded](https://en.wikipedia.org/wiki/Hard-coded) reseed servers available to fetch from. These servers securely serve an [SU3](https://geti2p.net/spec/updates#su3) file (signed with a cryptographic @signature) over @clearnet with [HTTPS](https://en.wikipedia.org/wiki/HTTPS). This SU3 file contains information that's used to verify both the integrity of the file and its content. - -Aside from the technical elements needed to verify and process the file, the file's main contents consist of a series of @router-info files which @Kovri and @I2P routers use to locate and communicate with other @I2P peers. These peers are then stored into a @network-database. diff --git a/_i18n/pt-br/resources/moneropedia/router-info.md b/_i18n/pt-br/resources/moneropedia/router-info.md deleted file mode 100644 index cb190f9d..00000000 --- a/_i18n/pt-br/resources/moneropedia/router-info.md +++ /dev/null @@ -1,67 +0,0 @@ ---- -tags: ["kovri"] -terms: ["Router-Info", "Router-infos"] -summary: "A data structure or file which contains an I2P peer's needed network information" ---- - -{% include untranslated.html %} -### The Basics - -@Router-Info is a data structure (periodically written to a [binary file](https://en.wikipedia.org/wiki/Binary_file)) which contains all needed information to locate, identify, and communicate with an @I2P peer. @Router-Info includes IP address, router identity, other misc. technical details; is needed for @network-database and is published to @floodfill routers. - -### In-depth information - -In human-readable form, Router-Info may look like this: - -``` -Identity: [RouterIdentity: -Hash: nYZ5Qe7gQ-~QgfgJVRUG4c0JnVeVqzM~duUX1EGT1ek= -Certificate: [Certificate: type: Key certificate -Crypto type: 0 -Sig type: 7 (EdDSA_SHA512_Ed25519)] -PublicKey: [PublicKey: size: 256] -SigningPublicKey: [SigningPublicKey EdDSA_SHA512_Ed25519: size: 32] -Padding: 96 bytes] -Signature: [Signature EdDSA_SHA512_Ed25519: size: 64] -Published: Sun Oct 09 01:34:59 UTC 2016 -Options (5): - [caps] = [LfR] - [netId] = [2] - [netdb.knownLeaseSets] = [37] - [netdb.knownRouters] = [2435] - [router.version] = [0.9.26] -Addresses (4): -[RouterAddress: -Type: SSU -Cost: 4 -Options (5): - [caps] = [BC] - [host] = [2a01:e35:8b5c:b240:71a2:6750:8d4:47fa] - [key] = [nYZ5Qe7gQ-~QgfgJVRUG4c0JnVeVqzM~duUX1EGT1ek=] - [mtu] = [1472] - [port] = [22244]] -[RouterAddress: -Type: NTCP -Cost: 9 -Options (2): - [host] = [2a01:e35:8b5c:b240:71a2:6750:8d4:47fa] - [port] = [22244]] -[RouterAddress: -Type: SSU -Cost: 6 -Options (4): - [caps] = [BC] - [host] = [88.181.203.36] - [key] = [nYZ5Qe7gQ-~QgfgJVRUG4c0JnVeVqzM~duUX1EGT1ek=] - [port] = [22244]] -[RouterAddress: -Type: NTCP -Cost: 11 -Options (2): - [host] = [88.181.203.36] - [port] = [22244]]] -``` - -### Notes - -For details and specification, visit @Java-I2P [Network Database](https://geti2p.net/en/docs/how/network-database) page. diff --git a/_i18n/pt-br/resources/moneropedia/ssu.md b/_i18n/pt-br/resources/moneropedia/ssu.md deleted file mode 100644 index cbdadfdc..00000000 --- a/_i18n/pt-br/resources/moneropedia/ssu.md +++ /dev/null @@ -1,25 +0,0 @@ ---- -tags: ["kovri"] -terms: ["SSU"] -summary: "Secure Semi-reliable UDP: one of two Kovri transports" ---- - -{% include untranslated.html %} -### The Basics - -*Secure Semi-reliable UDP* is one of two encrypted @transports for @Kovri. - -Similar to @NTCP, @SSU's *primary* purpose is to securely transmit @in-net @I2NP messages through @tunnels but, unlike @NTCP, @SSU functions solely over encrypted [UDP](https://en.wikipedia.org/wiki/User_Datagram_Protocol). - -### In-depth information - -- Like @NTCP, @SSU is a connection-oriented, point-to-point data transport -- Termed *semi-reliable* because @SSU will repeatedly retransmit *unacknowledged* messages (up to maximum number then dropped) -- @SSU also provides several unique services (in addition to its function as a @transport layer): - - IP detection (local inspection or with [peer testing](https://geti2p.net/en/docs/transport/ssu#peerTesting)) - - [NAT](https://en.wikipedia.org/wiki/Network_address_translation) traversal (using [introducers](https://geti2p.net/en/docs/transport/ssu#introduction)) - - [Firewall](https://en.wikipedia.org/wiki/Firewall_%28computing%29) status and, if implemented, @SSU can notify @NTCP if the external address or firewall status changes - -### Notes - -For further details, read @Java-I2P's [SSU](https://geti2p.net/en/docs/transport/ssu) diff --git a/_i18n/pt-br/resources/moneropedia/subscription.md b/_i18n/pt-br/resources/moneropedia/subscription.md deleted file mode 100644 index bfb4b0bc..00000000 --- a/_i18n/pt-br/resources/moneropedia/subscription.md +++ /dev/null @@ -1,46 +0,0 @@ ---- -tags: ["kovri"] -terms: ["Subscription"] -summary: "A file used by address book which contains I2P hosts paired with I2P destinations" ---- - -{% include untranslated.html %} -### The Basics - -A subscription is a file which contains a list of `.i2p` hosts paired with their respective @destination. Subscriptions are used by the @address-book. - -### In-depth information - -Similar to how a [hosts file](https://en.wikipedia.org/wiki/Hosts_(file)) can map an internet hostname to a specified address, a subscription matches a `.i2p` address to @base64-address by using the following format (no spaces allowed): `host=address` - -More specifically, a subscription pairs a @locally-unique-host to @base64-address. - -Example: - -``` -anonimal.i2p=AQZGLAMpI9Q0l0kmMj1vpJJYK3CjLp~fE3MfvE-e7KMKjI5cPOH6EN8m794uHJ6b09qM8mb9VEv1lVLEov~usVliTSXCSHuRBOCIwIOuDNU0AbVa4BpIx~2sU4TxKhoaA3zQ6VzINoduTdR2IJhPvI5xzezp7dR21CEQGGTbenDslXeQ4iLHFA2~bzp1f7etSl9T2W9RID-KH78sRQmzWnv7dbhNodMbpO6xsf1vENf6bMRzqD5vgHEHZu2aSoNuPyYxDU1eM6--61b2xp9mt1k3ud-5WvPVg89RaU9ugU5cxaHgR927lHMCAEU2Ax~zUb3DbrvgQBOTHnJEx2Fp7pOK~PnP6ylkYKQMfLROosLDXinxOoSKP0UYCh2WgIUPwE7WzJH3PiJVF0~WZ1dZ9mg00c~gzLgmkOxe1NpFRNg6XzoARivNVB5NuWqNxr5WKWMLBGQ9YHvHO1OHhUJTowb9X90BhtHnLK2AHwO6fV-iHWxRJyDabhSMj1kuYpVUBQAEAAcAAA== -``` - -1. `anonimal.i2p` is the @locally-unique-host -2. `=` is the separator -3. Everything that remains is the @base64-address - -### Subscription types - -For @Kovri, there are two types of subscription files: *public* and *private*. - -A *public* subscription: -- is used when bootstrapping to use essential services (IRC, email, Monero, etc.) -- is static and is refreshed every 12 hours from Monero's @address-book server -- allows you to safely share the subscription with everyone as it is publically available (anyone who shares the same public subscription will also be able to resolve the same hostname to the same destination as you) - -A *private* subscription: -- is used exclusively by you and is not shared with others unless you explicitly choose to share the file -- default file is `private_hosts.txt` in your @data-directory - -### Updating a private subscription - -You can use a @jump-service to manually update your private subscription. The updated subscription will then be fed into the @address-book for you to use. - -### Notes -To learn how to subscribe to multiple subscriptions, see the [user-guide](https://gitlab.com/kovri-project/kovri-docs/blob/master/i18n/en/user_guide.md). diff --git a/_i18n/pt-br/resources/moneropedia/transports.md b/_i18n/pt-br/resources/moneropedia/transports.md deleted file mode 100644 index b1471cd6..00000000 --- a/_i18n/pt-br/resources/moneropedia/transports.md +++ /dev/null @@ -1,19 +0,0 @@ ---- -tags: ["kovri"] -terms: ["Transports", "Transport"] -summary: "The two encrypted transport layers for Kovri" ---- - -{% include untranslated.html %} -### The Basics - -@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 - -@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 @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) diff --git a/_i18n/pt-br/resources/moneropedia/tunnel.md b/_i18n/pt-br/resources/moneropedia/tunnel.md deleted file mode 100644 index a9ebfaaa..00000000 --- a/_i18n/pt-br/resources/moneropedia/tunnel.md +++ /dev/null @@ -1,36 +0,0 @@ ---- -tags: ["kovri"] -terms: ["Tunnel", "Tunnels"] -summary: "Uni-directional virtual paths that pass messages through a defined sequence of I2P routers" ---- - -{% include untranslated.html %} -### The Basics - -When you communicate over @I2P (visit an @eepsite / use a @garlic-service), you'll first need to connect to a peer by using @transports and then build virtual *tunnels*. These virtual tunnels are temporary, uni-directional paths that pass information through a defined sequence of @I2P routers to your @destination. Tunnels are built, and then used, with layered @garlic-encryption and are a general-purpose mechanism to transport all @I2NP @messages. - -Each peer builds, at a minimum, *two* uni-directional tunnels: one for **outbound traffic**, and one for **inbound traffic**. These tunnels are classified as either **inbound tunnels** (where @messages come toward the creator of the tunnel) or **outbound tunnels** (where the tunnel creator sends @messages away from the creator of the tunnel). Thus, *four* tunnels are required for a single round-trip @message and reply to your @destination (two for your, two for your destination). - -### In-depth information - -From @Java-I2P: - -> -Within I2P, @messages are passed in one direction through a virtual tunnel of peers, using whatever means are available to pass the @message on to the next hop. Messages arrive at the tunnel's gateway, get bundled up and/or fragmented into fixed-size @tunnel @messages, and are forwarded on to the next hop in the tunnel, which processes and verifies the validity of the @message and sends it on to the next hop, and so on, until it reaches the @tunnel endpoint. That endpoint takes the messages bundled up by the gateway and forwards them as instructed - either to another router, to another tunnel on another router, or locally. - -> -Tunnels all work the same, but can be segmented into two different groups - inbound tunnels and outbound tunnels. The inbound tunnels have an untrusted gateway which passes messages down towards the tunnel creator, which serves as the tunnel endpoint. For outbound tunnels, the tunnel creator serves as the gateway, passing messages out to the remote endpoint. - -> -The tunnel's creator selects exactly which peers will participate in the tunnel, and provides each with the necessary configuration data. They may have any number of hops. It is the intent to make it hard for either participants or third parties to determine the length of a tunnel, or even for colluding participants to determine whether they are a part of the same tunnel at all (barring the situation where colluding peers are next to each other in the tunnel). - -### Notes - -From @Java-I2P: - -> -@I2P is an inherently packet switched network, even with these tunnels, allowing it to take advantage of multiple tunnels running in parallel, increasing resilience and balancing load. Even though the tunnels within I2P bear a resemblance to a circuit switched network, everything within I2P is strictly message based - tunnels are merely accounting tricks to help organize the delivery of messages. No assumptions are made regarding reliability or ordering of messages, and retransmissions are left to higher levels (e.g. I2P's client layer streaming library). - -### Documentation - -For specification and detailed documentation, visit the [Tunnel-Routing](https://geti2p.net/en/docs/how/tunnel-routing) and [Tunnel-Implementation](https://geti2p.net/en/docs/tunnels/implementation) page. diff --git a/_i18n/ru/resources/moneropedia/base32-address.md b/_i18n/ru/resources/moneropedia/base32-address.md deleted file mode 100644 index 87112d07..00000000 --- a/_i18n/ru/resources/moneropedia/base32-address.md +++ /dev/null @@ -1,25 +0,0 @@ ---- -tags: ["kovri"] -terms: ["Base32-address", "Base32-addresses", "адрес-Base32", "адресом-Base32", "адреса-Base32", "Base32-адрес"] -summary: "Base32 является закодированным представлением хеша адреса Base64" ---- - -### Основная информация - -Адрес Base32 является сокращённой, закодированной версией адреса @I2P. Адрес Base32 является первой частью имени хоста `b32.i2p`. - -Пример: - -`i35yftyyb22xhcvghmev46t5knefur5v66qzekkajatwfwhyklvq.b32.i2p` - -где - -`i35yftyyb22xhcvghmev46t5knefur5v66qzekkajatwfwhyklvq` является адресом Base32. - -### Углублённая информация - -В конечном счёте адрес Base32 является состоящим из 52 символов [закодированным представлением Base32](https://en.wikipedia.org/wiki/Base32) полного хеша SHA-256 @I2P @Base64-адреса. - -### Примечания - -**Примечание: `.b32` не является поддоменом `.i2p.`** diff --git a/_i18n/ru/resources/moneropedia/base64-address.md b/_i18n/ru/resources/moneropedia/base64-address.md deleted file mode 100644 index 59c92a4b..00000000 --- a/_i18n/ru/resources/moneropedia/base64-address.md +++ /dev/null @@ -1,20 +0,0 @@ ---- -tags: ["kovri"] -terms: ["Base64-address", "Base64-addresses", "адреса-Base64", "адрес-Base64", "Адрес-Base64", "Адреса-Base64", "адресом-Base64", "Base64-адреса", "Base64-адресом", "Base64-адрес"] -summary: "Aдрес Base64 является закодированным I2P" ---- - -### Основная информация - -@Base64-адреса является [закодированным Base64](https://en.wikipedia.org/wiki/Base64) @I2P адресом @назначения, состоящим из 516 символов. @Base64-адреса в первую очередь используются @адресной-книгой, @jump-service, а также внутренне. - -Пример: - -``` -AQZGLAMpI9Q0l0kmMj1vpJJYK3CjLp~fE3MfvE-e7KMKjI5cPOH6EN8m794uHJ6b09qM8mb9VEv1lVLEov~usVliTSXCSHuRBOCIwIOuDNU0AbVa4BpIx~2sU4TxKhoaA3zQ6VzINoduTdR2IJhPvI5xzezp7dR21CEQGGTbenDslXeQ4iLHFA2~bzp1f7etSl9T2W9RID-KH78sRQmzWnv7dbhNodMbpO6xsf1vENf6bMRzqD5vgHEHZu2aSoNuPyYxDU1eM6--61b2xp9mt1k3ud-5WvPVg89RaU9ugU5cxaHgR927lHMCAEU2Ax~zUb3DbrvgQBOTHnJEx2Fp7pOK~PnP6ylkYKQMfLROosLDXinxOoSKP0UYCh2WgIUPwE7WzJH3PiJVF0~WZ1dZ9mg00c~gzLgmkOxe1NpFRNg6XzoARivNVB5NuWqNxr5WKWMLBGQ9YHvHO1OHhUJTowb9X90BhtHnLK2AHwO6fV-iHWxRJyDabhSMj1kuYpVUBQAEAAcAAA== -``` - - -### Углублённая информация - -Более подробная информация, касающаяся @Base64-адреса, содержится в разделе адрес @назначения. diff --git a/_i18n/ru/resources/moneropedia/data-directory.md b/_i18n/ru/resources/moneropedia/data-directory.md deleted file mode 100644 index b2b67842..00000000 --- a/_i18n/ru/resources/moneropedia/data-directory.md +++ /dev/null @@ -1,20 +0,0 @@ ---- -tags: ["kovri"] -terms: ["Data-Directory", "директории-данных", "директория-данных"] -summary: "Место хранения основных данные Kovri для их выполнения" ---- - -### Основная информация - -В зависимости от операционной системы, которую вы используете, на данный момент @Kovri сохраняет данные работы в следующей директории: - -- Linux / FreeBSD: - - `$HOME/.kovri` - -- OSX: - - `$HOME/Library/Application\ Support/Kovri` - -- Windows: - - `"$APPDATA"\\Kovri` - -Сохраняются данные всех файлов конфигурации, @адресной-книги, сертификатов и ресурсов. diff --git a/_i18n/ru/resources/moneropedia/eepsite.md b/_i18n/ru/resources/moneropedia/eepsite.md deleted file mode 100644 index f49e8220..00000000 --- a/_i18n/ru/resources/moneropedia/eepsite.md +++ /dev/null @@ -1,28 +0,0 @@ ---- -tags: ["kovri"] -terms: ["Eepsite", "Hidden-Service", "Garlic-Site", "Garlic-Service", "чесночная-служба", "чесночный-сайт", "скрытая-служба"] -summary: "Веб-сайт или служба, размещенная в сети I2P" ---- - -### Основная информация - -Это [**EEP!** *(если следовать контенту, размещённому на сайте)*](https://en.wikipedia.org/wiki/Onomatopoeia), **протокол сквозной передачи** или что-то совершенно иное? - -Несмотря на то, что оригинальное определение Eepsite со временем было утрачено, его предназначение остаётся прежним: Eepsite является веб-сайтом или службой в составе @I2P сети (или доступной через эту сеть). - -### Углублённая информация - -Среди альтернативных названий Eepsite есть следующие: - -1. *Cкрытая служба* - - поскольку сайт / служба *скрыты* в пределах @I2P сети, и доступ к ним можно получить также только в пределах этой сети. -2. *"Чесночный" сайт* - - поскольку для связи с клиентом веб-сайт использует технологию @чесночной-маршрутизации @I2P - - поскольку служба размещается как веб-сайт, а не как любой другой тип службы -3. *"Чесночная" служба* - - поскольку для связи с клиентом служба использует технологию @чесночной-маршрутизации @I2P - - поскольку служба является характерной для таких служб, как IRC, электронная почта или одноранговый узел Monero (но также может включать в себя веб-сайты) - -### Примечания - -Чтобы узнать, как настроить Eepsite (Hidden Service, Garlic Site, Garlic Service), следует ознакомиться с [руководством пользователя](https://gitlab.com/kovri-project/kovri-docs/blob/master/i18n/en/user_guide.md) @Kovri. diff --git a/_i18n/ru/resources/moneropedia/floodfill.md b/_i18n/ru/resources/moneropedia/floodfill.md deleted file mode 100644 index 3284d001..00000000 --- a/_i18n/ru/resources/moneropedia/floodfill.md +++ /dev/null @@ -1,13 +0,0 @@ ---- -tags: ["kovri"] -terms: ["Floodfill", "заполнение", "заполнения"] -summary: "Маршрутизатор I2P, который поддерживает распределенную сетевую базу данных" ---- - -### Основная информация - -Путём активного управления распределённой базой данных сети, *floodfill*-маршрутизатор способствует поддержанию стабильности и устойчивости сети, сохраняя при этом её децентрализованность при отсутствии необходимости в доверии. - -### Углублённая информация - -Несмотря на то, что floodfill является просто системой хранения, технические основы floodfill намного сложнее, так как она связана с @базой-данных-сети и другими протоколами в пределах @I2P. Подробная информация содержится на странице [база данных сети](https://geti2p.net/en/docs/how/network-database). diff --git a/_i18n/ru/resources/moneropedia/garlic-encryption.md b/_i18n/ru/resources/moneropedia/garlic-encryption.md deleted file mode 100644 index e6314cec..00000000 --- a/_i18n/ru/resources/moneropedia/garlic-encryption.md +++ /dev/null @@ -1,23 +0,0 @@ ---- -tags: ["kovri"] -terms: ["Garlic-Encryption", "Layered-Encryption", "чесночного-шифрования", "чесночное-шифрование", "Чесночное-шифрование", "чесночным-шифрованием", "многоуровневое-шифрование", "Многоуровневое-шифрование", "чесночную-службу"] -summary: "Многоуровневое шифрование, реализованное в Kovri / I2P" ---- - -### Основная информация - -@Чесночное-шифрование является @I2P реализацией @сообщения, в основе которой лежит @многоуровневое-шифрование (подобно потоковому [луковому шифрованию](https://en.wikipedia.org/wiki/Onion_routing)). - -@Шифрование @сообщений по уровням позволяет направить @сообщение по маршруту, состоящему из последовательности прокси-узлов. При этом такие прокси-узлы (или любые другие посредники) не смогут прочитать содержание @сообщения. @Многоуровневое-шифрование является фундаментальной особенностью @Kovri, @I2P и [Tor](https://torproject.org), а также краеугольным камнем обеспечения анонимности в пределах этих оверлейных сетей. - -### Углублённая информация - -В случае с @чесночным-шифрованием основное различие между @Kovri / @I2P и Tor заключается в следующем: - -- @Kovri / @I2P связывает вместе множество @сообщений, формируя "чесночные зубки" - - такой "зубок" может содержать *любое* количество сообщений, а не только одно единственное -- @Kovri / @I2P использует [ElGamal](https://en.wikipedia.org/wiki/ElGamal) / [AES](https://en.wikipedia.org/wiki/Advanced_Encryption_Standard) @шифрование @сообщений и @транспортного уровня. - -### Примечание - -Более подробная информация содержится в статье @чесночная-маршрутизация. diff --git a/_i18n/ru/resources/moneropedia/garlic-routing.md b/_i18n/ru/resources/moneropedia/garlic-routing.md deleted file mode 100644 index 286708a6..00000000 --- a/_i18n/ru/resources/moneropedia/garlic-routing.md +++ /dev/null @@ -1,42 +0,0 @@ ---- -tags: ["kovri"] -terms: ["Garlic-Routing", "чесночная-маршрутизация", "чесночной-маршрутизации"] -summary: "Технология маршрутизации, реализованная в Kovri" ---- - -### Основная информация - -Термин *чесночная маршрутизация* имеет противоречивую историю и самые разные интерпретации. В настоящий момент с точки зрения Monero чесночная маршрутизация определяется как метод, используя который @Kovri и @I2P могут создать основанную на обмене @сообщениями анонимную оверлейную сеть одноранговых интернет-узлов. - -@Чесночное-шифрование или @чесночная-маршрутизация похожа на @многоуровневое-шифрование, используемое при [луковой маршрутизации](https://en.wikipedia.org/wiki/Onion_routing), и позволяет эффективно скрыть IP-адрес отправителя и обезопасить информацию, высланную отправителем по адресу @назначения (и наоборот). - -### История - -Впервые термин *"чесночная маршрутизация"* появился в начале июня 2000 в кандидатской работе Роджера Динглдина (Roger Dingledine) Схема управления [Free Haven Master's](http://www.freehaven.net/papers.html) (раздел 8.1) как производный от термина "луковая маршрутизация". - -Совсем недавно, в октябре 2016, [#tor-dev](https://oftc.net/WebChat/) предложил подробно разобраться в сути термина *"чесночная маршрутизация"*: - -[Ник Мэтьюсон](https://en.wikipedia.org/wiki/The_Tor_Project,_Inc): ->[Я вижу в этом некоторую попытку создать механизм, структура которого напоминала бы топологию leaky-pipe сети Tor, но я не уверен, что мы даже каким-то образом брали её за основу.] - -[Роджер Динглдин](https://en.wikipedia.org/wiki/Roger_Dingledine): ->Во время мозгового штурма Free Haven был момент, когда мы пытались определить механизм маршрутизации, и кто-то сказал: "Чесночная маршрутизация"! И все засмеялись, и на тот момент мы все были уверены в том, что придумали новое название. - -*Примечание Разрешение на использование приведённых выше цитат было получено непосредственно у Ника Мэтьюсона и Роджера Динглдина.* - -### Углублённая информация - -С технической точки зрения в случае с @Kovri и @I2P термин *"чесночная маршрутизация"* подходит к любому / всем указанным ниже процессам: - -- @многоуровневое-шифрование (подобное многоуровневому шифрованию, используемому при луковой маршрутизации) -- объединение множества @сообщений (в "чесночные зубки") -- ElGamal/AES @шифрование. - -*Примечание Несмотря на то, что [Tor](https://torproject.org/) использует @многоуровневое-шифрование, он не использует ElGamal и не основан на обмене сообщениями.* - -**Больше информации содержится в статье @чесночное-шифрование.** - -### Примечания - -- С точки зрения чесночной / луковой маршрутизации на многоуровневое @шифрование можно взглянуть по-другому, заменив луковую / чесночную структуру [матрёшкой](https://en.wikipedia.org/wiki/Matryoshka_doll), в которой у каждой находящейся снаружи / внутри матрёшки будет свой замок и публичный ключ от следующей / предыдущей матрёшки. -- Более подробное техническое описание чесночной маршрутизации содержится в статье @Java-I2P, в разделе, касающемся [чесночной маршрутизации](https://geti2p.net/en/docs/how/garlic-routing) diff --git a/_i18n/ru/resources/moneropedia/i2np.md b/_i18n/ru/resources/moneropedia/i2np.md deleted file mode 100644 index 6f646fc4..00000000 --- a/_i18n/ru/resources/moneropedia/i2np.md +++ /dev/null @@ -1,26 +0,0 @@ ---- -tags: ["kovri"] -terms: ["I2NP"] -summary: "Сетевой протокол I2P: механизм, в котором сообщения I2NP отправляются в сетях I2P" ---- - -### Основная информация - -Из статьи @Java-I2P: - -> -@I2NP управляет маршрутизацией и смешиванием сообщений между маршрутизаторами, равно как и выбором транспортного протокола, который будет использоваться для связи с одноранговым узлом, поддерживающим множество общих транспортных протоколов. - -### Углублённая информация - -Из статьи @Java-I2P: - -> -Сообщения @I2NP (сетевой протокол @I2P) могут использоваться для односкачковой передачи @сообщений от маршрутизатора к маршрутизатору, от точки к точке. @Шифрование и "завёртывание" одних @сообщений в другие обеспечивают их безопасную многократную пересылку вплоть до конечного адреса @назначения. @I2NP не указывает и не требует какого-либо определённого @транспортного уровня, но этому протоколу необходим по крайней мере один такой уровень, который он смог бы использовать. - -> -Всякий раз, когда необходимо отправить @сообщение на другой адрес @назначения, требуется дать локальному маршрутизатору данные структуры такого адреса @назначения, а также необработанные байты отправляемого сообщения. Затем маршрутизатор определяет, куда отправить его, пересылает сообщение через выходящие @туннели и указывает конечной точке пропустить его к соответствующему входящему @туннелю, где он снова пропускается к конечной точке такого туннеля, и делает его доступным для получения адресатом. - -### Примечания - -Дополнительная информация по [протоколу](https://geti2p.net/en/docs/protocol/i2np) и [спецификации](https://geti2p.net/spec/i2np) I2NP. diff --git a/_i18n/ru/resources/moneropedia/i2p.md b/_i18n/ru/resources/moneropedia/i2p.md deleted file mode 100644 index 1f312b62..00000000 --- a/_i18n/ru/resources/moneropedia/i2p.md +++ /dev/null @@ -1,29 +0,0 @@ ---- -tags: ["kovri"] -terms: ["I2P"] -summary: "Проект Невидимый Интернет: анонимизирующая оверлейная сеть" ---- - -### Monero - -Реализация @I2P для Monero описана в статье @Kovri. Для сравнения @I2P и [Tor](https://torproject.org/) перейдите на страницу [Сравнение](https://geti2p.net/en/comparison/tor). - -### Основная информация - -Из статьи @Java-I2P: - ->Сеть I2P обеспечивает высокий уровень защиты анонимности данных, передаваемых по сети интернет. Многие действия, которые могли бы подвергнуть вашу анонимность риску в публичной сети интернет, могут совершаться анонимно внутри I2P. - -### Углублённая информация - -Из статьи @Java-I2P: - ->I2P является анонимной оверлейной сетью, то есть сетью в сети. Она предназначена для защиты передаваемых данных от наблюдения и мониторинга третьими сторонами, например, поставщиками услуг сети Интернет. - ->I2P используется многими людьми, которым не безразлична собственная анонимность: активистами, притесняемыми, журналистами и осведомителями, "подсадными утками", а также среднестатистическими пользователями. - ->Сеть не может быть "идеально анонимной". Неизменная цель I2P состоит в том, чтобы максимально усложнить процесс проведения атаки. Уровень анонимности будет расти по мере разрастания сети, а также благодаря академическим исследованиям, которые проводятся в этой области. - -### Примечания - -Документацию и спецификации @I2P можно взять [здесь](https://geti2p.net/docs/). diff --git a/_i18n/ru/resources/moneropedia/i2pcontrol.md b/_i18n/ru/resources/moneropedia/i2pcontrol.md deleted file mode 100644 index ba165ec2..00000000 --- a/_i18n/ru/resources/moneropedia/i2pcontrol.md +++ /dev/null @@ -1,15 +0,0 @@ ---- -tags: ["kovri"] -terms: ["I2PControl"] -summary: "API интерфейс для Kovri и Java-I2P, который позволяет простое дистанционное управление" ---- - -### Основная информация - -@I2PControl — это прикладной пользовательский интерфейс [API](https://en.wikipedia.org/wiki/Application_programming_interface) [JSONRPC2](https://en.wikipedia.org/wiki/JSON-RPC) для @Kovri и @Java-I2P, позволяющий клиенту @I2PControl удалённо контролировать / отслеживать запущенное событие. - -Существует два доступных клиента @I2PControl: [qtoopie](https://github.com/EinMByte/qtoopie) (C++) и [itoopie](https://github.com/i2p/i2p.itoopie) (Java). Чтобы конфигурировать @I2PControl для @Kovri, следует прочитать `kovri.conf`. - -### Углублённая информация - -С подробной информацией и спецификацией можно ознакомиться на странице [I2PControl](https://geti2p.net/en/docs/api/i2pcontrol). diff --git a/_i18n/ru/resources/moneropedia/in-net.md b/_i18n/ru/resources/moneropedia/in-net.md deleted file mode 100644 index 7345d5f2..00000000 --- a/_i18n/ru/resources/moneropedia/in-net.md +++ /dev/null @@ -1,13 +0,0 @@ ---- -tags: ["kovri"] -terms: ["In-net", "адресом-конечной-точки"] -summary: "Сеть в рамках I2P" ---- - -### Основная информация - -**In-net** — это [разговорный](https://en.wikipedia.org/wiki/Colloquial) термин, описывающий события, протоколы или функции, которые существуют *только* в пределах сети @I2P - -### Углублённая информация - -Пример: in-net download (*внутрисетевая загрузка*) будет означать загрузку, осуществляемую только в @I2P. diff --git a/_i18n/ru/resources/moneropedia/java-i2p.md b/_i18n/ru/resources/moneropedia/java-i2p.md deleted file mode 100644 index 833a9128..00000000 --- a/_i18n/ru/resources/moneropedia/java-i2p.md +++ /dev/null @@ -1,13 +0,0 @@ ---- -tags: ["kovri"] -terms: ["Java-I2P"] -summary: "Исходная реализация I2P - написанная на Java" ---- - -### Основная информация - -Термин "Java-I2P" часто используется для описания оригинальной реализации @I2P, наиболее известной и используемой на сегодняшний день. Существуют различные другие варианты реализации @I2P, включая @Kovri, и все они ориентируются на оригинальную реализацию на языке Java. - -### Примечания - -Чтобы загрузить / узнать больше о реализации Java, посетите их [вебсайт](https://geti2p.net/). diff --git a/_i18n/ru/resources/moneropedia/jump-service.md b/_i18n/ru/resources/moneropedia/jump-service.md deleted file mode 100644 index 8a1da9f6..00000000 --- a/_i18n/ru/resources/moneropedia/jump-service.md +++ /dev/null @@ -1,32 +0,0 @@ ---- -tags: ["kovri"] -terms: ["Jump-Service", "служба-переключения"] -summary: "Сервис веб-сайтов I2P, который добавляет веб-сайт в вашу адресную книгу" ---- - -### Основная информация - -Конфигурированный под @I2P веб-браузер позволяет использовать службу Jump Service для *переключения* на @I2P адрес, которого нет в вашей @адресной-книге. Как только вы *переключитесь* на него, он будет занесён в вашу @адресную-книгу. - -### Углублённая информация - -Через конфигурированный под @I2P браузер зайдите на страницу http://stats.i2p/i2p/lookup.html (ссылка любезно предоставлена ведущим разработчиком @Java-I2P *zzz*) - -Вам будут предложены две опции: - -1. Опция *Hostname lookup* (поиск по имени хост-узла) позволит вам найти адрес, по которому вы хотите перейти, вручную скопировать / вставить результаты -2. Опция *Jump* (переключиться) позволит перейти на @I2P веб-сайт. Для этого будет необходимо ввести имя @I2P хоста (**рекомендуется**) - -### Как использовать опцию Hostname lookup - -Например, вы можете ввести (и затем подтвердить) `pinkpaste.i2p` в диалоговое окно *Hostname lookup*, в результате чего получите: - -``` -pinkpaste.i2p=m-HrPrIAsdxts0WM~P4mE8mt9P7g-QTaBvu7Gc6Nl0UX7Vwck-i~RvOPfK6W~kfdRvwhNTqevkBL2UF5l36We02Aiywu7kB2xOHRkze68h-Tg2ewvRVwokohguCD2G3wwAEz~7FVda2avYDCb9-N6TfuzxKLnmhPMvbNSjGL7ZsD2p-h207R3-2kvuMV9bfu-K~w9NI9XJhIyufvUnFYc2jnTVg8PbaR4UP57cNaOO2YIMPkbr6~yTcIu9B1sUfHK6-N~6virQDOxW4M-62rjnZkLpaCtkOsXslmCwZI--TkZ6hKi1kXZvNmJRE1rYfffYRFn38zhaqszeETX8HiIvahZhXF5fNumBziYdmLdw8hkuN1A~emU6Xz9g~a1Ixfsq1Qr~guYoOtaw-0rOFxNRS9yMehE-2LCb8c-cAg6z5OdlN4qJDl~ZHgru4d~EHp~BpAK3v7u2Gi-8l1ygVW-1CHVna~fwnbOPN3ANPwh6~~yUit0Cx1f54XiNRn6-nPBQAEAAcAAA== -``` - -Скопируйте / вставьте этот парный Base64 адрес хост-узла в вашу **приватную** @подписку - -### Переключение напрямую - -Например, после введения (и последующего подтверждения) вами `pinkpaste.i2p` вы будете автоматически перенаправлены на веб-сайт, а адрес @локально-уникального-хоста будет также автоматически записан в @адресную-книгу. diff --git a/_i18n/ru/resources/moneropedia/lease-set.md b/_i18n/ru/resources/moneropedia/lease-set.md deleted file mode 100644 index 9dabe5c9..00000000 --- a/_i18n/ru/resources/moneropedia/lease-set.md +++ /dev/null @@ -1,23 +0,0 @@ ---- -tags: ["kovri"] -terms: ["LeaseSet", "LeaseSets", "набор-разрешений"] -summary: "Содержит все разрешенные для конкретного адреса назначения I2P" ---- - -### Основная информация - -@LeaseSet содержит набор @разрешений-на-временное-использование (и другую связанную информацию) для определённого адреса @назначения. - -### Углублённая информация - -Углублённая информация: - -- все действительные на текущий момент @разрешения-на-временное-использование для определённого адреса назначения -- публичный ключ, под который могут быть зашифрованы чесночные сообщения (см. @чесночная-маршрутизация) -- публичный ключ подписи, который может использоваться для отмены определённой версии структуры - -Lease-Set является одной из двух структур, которые хранятся в @сетевой-базе-данных (другой структурой является информация маршрутизатора), и имеет ключи, соответствующие SHA256 адреса @назначения. - -### Примечания - -Более подробная информация содержится в разделе [LeaseSet](https://geti2p.net/en/docs/how/network-database#leaseSet) на странице @Java-I2P. diff --git a/_i18n/ru/resources/moneropedia/lease.md b/_i18n/ru/resources/moneropedia/lease.md deleted file mode 100644 index bf207533..00000000 --- a/_i18n/ru/resources/moneropedia/lease.md +++ /dev/null @@ -1,13 +0,0 @@ ---- -tags: ["kovri"] -terms: ["Lease", "Leases", "разрешение-на-временное-использование", "временное-использование", "разрешения-на-временное-использование", "разрешений-на-временное-использование", "разрешений-на-временнoе-использование"] -summary: "Авторизовать I2P туннель для получения сообщений, предназначенных адресату" ---- - -### Основная информация - -Это разрешение на то, чтобы определённый @I2P @туннель принимал @сообщения, направленные на @адрес-назначения. - -### Углублённая информация - -Более подробная информация содержится в разделе [Lease](https://geti2p.net/spec/common-structures#lease) (разрешение на временное использование) на странице @Java-I2P. diff --git a/_i18n/ru/resources/moneropedia/message.md b/_i18n/ru/resources/moneropedia/message.md deleted file mode 100644 index 7ad67abb..00000000 --- a/_i18n/ru/resources/moneropedia/message.md +++ /dev/null @@ -1,31 +0,0 @@ ---- -tags: ["kovri"] -terms: ["Message", "Messages", "сообщений", "сообщениями", "сообщения", "сообщение", "соoбщениям", "сообщению"] -summary: "Механизмы, в которых информация перемещается в I2P" ---- - -### Основная информация - -*Сообщения* (на верхнем уровне @транспортного протокола) содержат различные типы информации, необходимой сети, но, что более важно, всё, что вы видите, делаете, отправляете или получаете принимает форму и становится *сообщениями*. - -В @I2P существует 2 важных типа @сообщений: - -- @туннельные сообщения -- @I2NP сообщения - -Преимущественно *@туннельные сообщения* **содержат фрагменты** @I2NP сообщений, которые затем [собираются](https://geti2p.net/en/docs/tunnels/implementation) заново в определённых точках @туннеля. - -### Углублённая информация - -@I2NP сообщения имеют близкое отношение к @туннeльным @соoбщениям, поэтому легко неправильно интерпретировать термин *"сообщения"*, когда читаешь спецификации @Java-I2P: - -> -1. Во-первых, в шлюзе туннеля накапливаются и проходят предварительную обработку ряд I2NP сообщений для последующей передачи в туннель для доставки. -2. Затем шлюз шифрует данные, прошедшие предварительную обработку, и направляет их на первый транзитный участок. -3. Одноранговый узел и последующие участники туннеля снимают уровень шифрования, проверяя, не дублируется ли он, а затем направляют сообщение следующему одноранговому узлу. -4. В конечном счёте туннельные сообщения прибывают в конечную точку, где I2NP сообщения связываются шлюзом и собираются заново, после чего направляются в соответствии с запросом. - -### Примечания - -- @I2NP @сообщения необходимо фрагментировать, поскольку они имеют различный размер (от 0 до почти 64 KB), а @туннельные @сообщения имеют фиксированный размер -- Подробную информацию и спецификации можно найти на страницах [спецификаций I2NP](https://geti2p.net/spec/i2np) и [спецификаций туннельных сообщений](https://geti2p.net/spec/tunnel-message) diff --git a/_i18n/ru/resources/moneropedia/network-database.md b/_i18n/ru/resources/moneropedia/network-database.md deleted file mode 100644 index a011d0b8..00000000 --- a/_i18n/ru/resources/moneropedia/network-database.md +++ /dev/null @@ -1,23 +0,0 @@ ---- -tags: ["kovri"] -terms: ["Network-Database", "сетевая-база-данных", "сетевой-базе-данных", "сетевой-базы-данных", "базе-данных-сети", "базой-данных-сети"] -summary: "Распределенная база данных, которая содержит необходимую информацию о маршрутизаторе, чтобы сохранялась целостность сети." ---- - -### Основная информация - -@Сетевая-база-данных является [распределённой базой данных](https://en.wikipedia.org/wiki/Distributed_database), в которой содержится информация маршрутизатора, которую одноранговые узлы используют, чтобы сохранялась целостность сети. - -### Углублённая информация - -Из статьи @Java-I2P: - -> -@Сетевая-база-данных @I2P является специализированной распределённой базой данных, содержащей только два типа данных: контактная информация маршрутизатора (@информация-маршрутизатора) и контактная информация адреса @назначения (@LeaseSets). Каждая часть данных подписывается соответствующей стороной и верифицируется тем, кто использует или хранит её. Помимо этого, данные содержат "живую" информацию, позволяющую сбрасывать нерелевантные вводные данные, заменять старые вводные данные более новыми, а также обеспечивающую защиту против определённых классов атаки. - -> -Распределение @сетевой-базы-данных происходит с применением простого метода, известного как @Floodfill, когда поднабор маршрутизаторов, называемых "маршрутизаторами заполнения" поддерживает распределённую базу данных. - -### Примечания - -Подробности можно найти на странице [сетевая база данных](https://geti2p.net/en/docs/how/network-database). diff --git a/_i18n/ru/resources/moneropedia/ntcp.md b/_i18n/ru/resources/moneropedia/ntcp.md deleted file mode 100644 index 0d1b5fa2..00000000 --- a/_i18n/ru/resources/moneropedia/ntcp.md +++ /dev/null @@ -1,32 +0,0 @@ ---- -tags: ["kovri"] -terms: ["NTCP"] -summary: "TCP на основе NIO (неблокирующий TCP трафик на основе ввода-вывода): один из двух транспортных средств Kovri" ---- - -### Основная информация - -*NIO-Based TCP (TAP на основе неблокируемого ввода-вывода)* является одним из двух зашифрованных @транспортных механизмов @Kovri. - -Подобно @SSU *первоочередной* целью @NTCP является безопасная передача внутрисетевых (@In-net) @I2NP сообщений по @туннелям. Однако в отличие от @SSU @NTCP работает исключительно через зашифрованный [TCP](https://en.wikipedia.org/wiki/Transmission_Control_Protocol). - -### Углублённая информация - - - Пропускает отдельные @I2NP сообщения (как стандартные, так и с синхронизацией по времени) после того, как: - - будет установлено соединение TCP - - будет завершена последовательность установки. - - Использует следующие методы @шифрования: - - 2048-битный алгоритм [Диффи-Хеллмана](https://en.wikipedia.org/wiki/Diffie-hellman) - - [AES-256](https://en.wikipedia.org/wiki/Advanced_Encryption_Standard)/[CBC](https://en.wikipedia.org/wiki/Block_cipher_modes_of_operation) - - Последовательность установки может находиться в следующих *состояниях*: - - предустановка - - установка - - постустановка или "установлено" - - Использует следующую информацию из @сетевой-базы-данных: - - название транспортного протокола: NTCP - - хост: IP (IPv4 или Ipv6) или имя хоста (допускается использование сокращённого IPv6 адреса (с "::")) - - порт: 1024 - 65535 - -### Примечания - -Более подробная информация содержится на странице [NTCP](https://geti2p.net/en/docs/transport/ntcp) @Java-I2P. diff --git a/_i18n/ru/resources/moneropedia/reseed.md b/_i18n/ru/resources/moneropedia/reseed.md deleted file mode 100644 index 0453e8ac..00000000 --- a/_i18n/ru/resources/moneropedia/reseed.md +++ /dev/null @@ -1,15 +0,0 @@ ---- -tags: ["kovri"] -terms: ["Reseed", "повторное-определение", "повторное-заполнение"] -summary: "Метод, который Kovri использует для загрузки в сеть I2P" ---- - -### Основная информация - -Когда вы впервые используете @Kovri (или же сеть была долгое время в режиме офлайн), @Kovri понадобится список одноранговых узлов для соединения, чтобы автоматически [загрузиться](https://en.wikipedia.org/wiki/Bootstrap) в сеть @I2P. @Kovri получает этот список узлов из специального файла, который хранится на сервере повторного заполнения (reseed-сервере). Этот файл содержит всю информацию, необходимую @Kovri для соединения с одноранговыми узлами @I2P. - -### Углублённая информация - -@Kovri есть список [аппаратно устанавливаемых](https://en.wikipedia.org/wiki/Hard-coded) reseed-серверов, чтобы получить информацию. Эти серверы в безопасном режиме передают [SU3](https://geti2p.net/spec/updates#su3) файл (подписанный @криптографической-подписью) по @клирнету, используя протокол HTTPS. Этот SU3 файл содержит информацию, которая используется для верификации как целостности файла, так и его содержания. - -Помимо технических элементов, необходимых для верификации и обработки файла, основное содержание файла также включает в себя файлы @информации-маршрутизатора, которые маршрутизаторы @Kovri и @I2P используют для нахождения и связи с другими одноранговыми узлами @I2P. Затем данные этих одноранговых узлов сохраняются в @базе-данных-сети. diff --git a/_i18n/ru/resources/moneropedia/router-info.md b/_i18n/ru/resources/moneropedia/router-info.md deleted file mode 100644 index 0deef1fc..00000000 --- a/_i18n/ru/resources/moneropedia/router-info.md +++ /dev/null @@ -1,66 +0,0 @@ ---- -tags: ["kovri"] -terms: ["Router-Info", "Router-infos", "информация-маршрутизатора", "информации-маршрутизатора"] -summary: "Структура данных или файл, содержащий необходимую сетевую информацию I2P узла" ---- - -### Основная информация - -@Информация-маршрутизатора представляет собой структуру (периодически записываемую в форме [двоичного файла](https://en.wikipedia.org/wiki/Binary_file)), содержащую всю информацию, необходимую для определения местонахождения и связи с одноранговым узлом @I2P. Информация маршрутизатора включает в себя IP-адрес, идентификационную информацию маршрутизатора, другие технические подробности, и она необходима для базы данных сети, а также публикуется для маршрутизаторов @заполнения. - -### Углублённая информация - -В удобной для восприятия человеком форме информация маршрутизатора может выглядеть так: - -``` -Identity: [RouterIdentity: -Hash: nYZ5Qe7gQ-~QgfgJVRUG4c0JnVeVqzM~duUX1EGT1ek= -Certificate: [Certificate: type: Key certificate -Crypto type: 0 -Sig type: 7 (EdDSA_SHA512_Ed25519)] -PublicKey: [PublicKey: size: 256] -SigningPublicKey: [SigningPublicKey EdDSA_SHA512_Ed25519: size: 32] -Padding: 96 bytes] -Signature: [Signature EdDSA_SHA512_Ed25519: size: 64] -Published: Sun Oct 09 01:34:59 UTC 2016 -Options (5): - [caps] = [LfR] - [netId] = [2] - [netdb.knownLeaseSets] = [37] - [netdb.knownRouters] = [2435] - [router.version] = [0.9.26] -Addresses (4): -[RouterAddress: -Type: SSU -Cost: 4 -Options (5): - [caps] = [BC] - [host] = [2a01:e35:8b5c:b240:71a2:6750:8d4:47fa] - [key] = [nYZ5Qe7gQ-~QgfgJVRUG4c0JnVeVqzM~duUX1EGT1ek=] - [mtu] = [1472] - [port] = [22244]] -[RouterAddress: -Type: NTCP -Cost: 9 -Options (2): - [host] = [2a01:e35:8b5c:b240:71a2:6750:8d4:47fa] - [port] = [22244]] -[RouterAddress: -Type: SSU -Cost: 6 -Options (4): - [caps] = [BC] - [host] = [88.181.203.36] - [key] = [nYZ5Qe7gQ-~QgfgJVRUG4c0JnVeVqzM~duUX1EGT1ek=] - [port] = [22244]] -[RouterAddress: -Type: NTCP -Cost: 11 -Options (2): - [host] = [88.181.203.36] - [port] = [22244]]] -``` - -### Примечания - -С подробностями и спецификацией можно ознакомиться на странице @Java-I2P [Network Database](https://geti2p.net/en/docs/how/network-database). diff --git a/_i18n/ru/resources/moneropedia/ssu.md b/_i18n/ru/resources/moneropedia/ssu.md deleted file mode 100644 index 786fc2a4..00000000 --- a/_i18n/ru/resources/moneropedia/ssu.md +++ /dev/null @@ -1,24 +0,0 @@ ---- -tags: ["kovri"] -terms: ["SSU"] -summary: "SSU - это один из двух транспортных средств Kovri" ---- - -### Основная информация - -SSU (Secure Semi-reliable UDP) является одной из двух технологий шифрования на @транспортном уровне @Kovri. - -Подобно @NTCP *основной* целью @SSU является безопасная передача внутрисетевых @I2NP сообщений по @туннелям, но, в отличие от @NTCP, @SSU работает только с протоколом [UDP](https://en.wikipedia.org/wiki/User_Datagram_Protocol). - -### Углублённая информация - -- Как и @NTCP, @SSU является ориентированной на соединение "точка-точка" транспортной технологией данных -- Технология называется *semi-reliable* ("полунадёжной"), так как @SSU многократно передаёт *неподтверждённые* сообщения (вплоть до максимального количества, после чего сообщение сбрасывается) -- @SSU также обеспечивает несколько уникальных сервисов (в дополнение к своей функции @транспортного уровня): - - обнаружение IP (путём локальной проверки или [тестирования одноранговых узлов](https://geti2p.net/en/docs/transport/ssu#peerTesting)) - - прослеживание [NAT](https://en.wikipedia.org/wiki/Network_address_translation) (при помощи [вводных элементов](https://geti2p.net/en/docs/transport/ssu#introduction)) - - статус [Firewall](https://en.wikipedia.org/wiki/Firewall_%28computing%29) и, если такая функция будет реализована, @SSU будет уведомлять @NTCP об изменениях статуса внешнего адреса или Firewall - -### Примечания - -Подробности на странице @Java-I2P [SSU](https://geti2p.net/en/docs/transport/ssu) diff --git a/_i18n/ru/resources/moneropedia/subscription.md b/_i18n/ru/resources/moneropedia/subscription.md deleted file mode 100644 index 4a368efc..00000000 --- a/_i18n/ru/resources/moneropedia/subscription.md +++ /dev/null @@ -1,47 +0,0 @@ ---- -tags: ["kovri"] -terms: ["Subscription", "подпиской", "подписка", "подписке", "подписки", "подписку"] -summary: "Файл, используемый адресной книгой, который содержит I2P хосты в паре с I2P назначениями" ---- - -### Основная информация - -Подпиской называется файл, содержащий список `.i2p` хостов, связанных с соответствующим адресом @назначения. Подписки используются @адресной-книгой. - -### Углублённая информация - -Подобно тому как [файл хостов](https://en.wikipedia.org/wiki/Hosts_(file)) может присвоить интернет имя хоста указанному адресу, подписка связывает `.i2p` адрес с @Base64-адресом, используя следующий формат (использование пробелов не допускается): `host=address` - -Если говорить более конкретно, подписка связывает @локально-уникальный-хост с @Base64-адресом. - -Например: - -``` -anonimal.i2p=AQZGLAMpI9Q0l0kmMj1vpJJYK3CjLp~fE3MfvE-e7KMKjI5cPOH6EN8m794uHJ6b09qM8mb9VEv1lVLEov~usVliTSXCSHuRBOCIwIOuDNU0AbVa4BpIx~2sU4TxKhoaA3zQ6VzINoduTdR2IJhPvI5xzezp7dR21CEQGGTbenDslXeQ4iLHFA2~bzp1f7etSl9T2W9RID-KH78sRQmzWnv7dbhNodMbpO6xsf1vENf6bMRzqD5vgHEHZu2aSoNuPyYxDU1eM6--61b2xp9mt1k3ud-5WvPVg89RaU9ugU5cxaHgR927lHMCAEU2Ax~zUb3DbrvgQBOTHnJEx2Fp7pOK~PnP6ylkYKQMfLROosLDXinxOoSKP0UYCh2WgIUPwE7WzJH3PiJVF0~WZ1dZ9mg00c~gzLgmkOxe1NpFRNg6XzoARivNVB5NuWqNxr5WKWMLBGQ9YHvHO1OHhUJTowb9X90BhtHnLK2AHwO6fV-iHWxRJyDabhSMj1kuYpVUBQAEAAcAAA== -``` - -Где: - -1. `anonimal.i2p` является @локально-уникальным-хостом -2. `=` является разделителем -3. а всё остальное является @Base64-адресом - -### Типы подписки - -В случае с @Kovri существует два типа файлов подписки: *публичные* и *приватные*. - -*Публичная* подписка: -- используется при автоматической загрузке для использования важных сервисов (IRC, электронной почты, Monero и т. д.) -- является статичной и обновляется каждые 12 часов с сервера @адресной-книги Monero -- позволяет безопасно делиться своей подпиской с кем угодно, так как является публично доступной (все, кто используют одну и ту же публичную подписку, также смогут привязать то же имя хоста к тому же адресу назначения, что и вы) - -*Приватная* подписка: -- используется исключительно вами, и её нельзя использовать совместно с кем-либо ещё, если только вы сами не примете решение поделиться файлом -- по умолчанию этим файлом является файл `private_hosts.txt` в вашей @директории-данных - -### Обновление приватной подписки - -Вы можете использовать службу переключения @Jump-Service, чтобы вручную обновить вашу приватную подписку. Обновлённая подписка затем будет сохранена в @адресной-книге, и вы снова сможете ею пользоваться. - -### Примечания -Чтобы узнать, как завести множество подписок, ознакомьтесь с [руководством пользователя](https://gitlab.com/kovri-project/kovri-docs/blob/master/i18n/en/user_guide.md). diff --git a/_i18n/ru/resources/moneropedia/transports.md b/_i18n/ru/resources/moneropedia/transports.md deleted file mode 100644 index 1aee8a81..00000000 --- a/_i18n/ru/resources/moneropedia/transports.md +++ /dev/null @@ -1,18 +0,0 @@ ---- -tags: ["kovri"] -terms: ["Transports", "Transport", "шифрование-транспортного-уровня", "транспортного", "транспортные-протоколы", "транспортных", "транспортном", "транспорты"] -summary: "Два зашифрованных транспортных уровня для Kovri" ---- - -### Основная информация - -@I2P использует две технологии шифрования транспортного уровня, что позволяет @Kovri безопасно использовать [TCP / IP](https://en.wikipedia.org/wiki/Tcp/ip) соединения. Эти технологии (@SSU и @NTCP) называются *транспортными*. - -### Углублённая информация - -@SSU является зашифрованным протоколом [UDP](https://en.wikipedia.org/wiki/User_Datagram_Protocol) а @NTCP - зашифрованным протоколом [TCP](https://en.wikipedia.org/wiki/Transmission_Control_Protocol). Они обеспечивают возможность @шифрования на [транспортном уровне](https://en.wikipedia.org/wiki/Transport_layer). Это позволяет отправлять по @туннелям @I2P сети @сообщения более высокого уровня. - -### Примечания - -- О @I2P технологиях транспортного уровня можно прочитать на странице [транспорта](https://geti2p.net/en/docs/transport) -- О транспортном уровне можно прочитать в статье по [модели OSI](https://en.wikipedia.org/wiki/OSI_model) diff --git a/_i18n/ru/resources/moneropedia/tunnel.md b/_i18n/ru/resources/moneropedia/tunnel.md deleted file mode 100644 index 43377f9b..00000000 --- a/_i18n/ru/resources/moneropedia/tunnel.md +++ /dev/null @@ -1,35 +0,0 @@ ---- -tags: ["kovri"] -terms: ["Tunnel", "Tunnels", "туннелям", "туннельным", "туннельное", "туннельные", "туннель", "туннельное-шифрование", "туннели", "туннелю", "туннeльные", "туннеля", "туннельным", "туннельное", "туннелям"] -summary: "Однонаправленные виртуальные сети, которые передают сообщения через определенную последовательность I2P маршрутизаторов" ---- - -### Основная информация - -Когда вы связываетесь по @I2P (посетите @Eepsite / используйте @чесночную-службу), вам, прежде всего, необходимо соединиться с одноранговым узлом, используя @транспорты, а затем построить виртуальные *туннели*. Эти виртуальные туннели являются временными, однонаправленными путями передачи информации в порядке определённой последовательности @I2P маршрутизаторов к адресу @назначения. Туннели сначала строятся, а затем используются при помощи @чесночного-шифрования и являются универсальным механизмом передачи всех @I2NP @сообщений. - -Каждый одноранговый узел строит как минимум *два* однонаправленных туннеля: один предназначен для **выходного трафика**, а другой — для **входящего трафика**. Эти туннели классифицируются либо как **входящие туннели** (когда @сообщения передаются в направлении создателя туннеля), либо как **выходящие туннели** (когда создатель туннеля отправляет @сообщения в направлении от себя). Таким образом, для кругового прохождения @сообщения и получения ответа по вашему адресу @назначения необходимо *четыре туннеля* (два для вас и два для адреса назначения). - -### Углублённая информация - -From @Java-I2P: - -> -В сети I2P @сообщения передаются в одном направлении по виртуальному туннелю между одноранговыми узлами, при этом используются доступные средства, позволяющие @сообщению пройти до следующего транзитного участка. Сообщения принимаются в шлюз @туннеля, связываются и / или фрагментируются в сообщения туннеля фиксированного размера, после чего направляются до следующего транзитного участка туннеля, где происходит обработка и верифицируется действительность @сообщения, после чего оно отправляется на следующий транзитный участок и так далее, до тех пор, пока оно не достигнет конечной точки @туннеля. В этой точке сообщения связываются шлюзом и направляются в соответствии с инструкцией: либо другому маршрутизатору, в другой туннель на другой маршрутизатор, либо локально. - -> -Все туннели работают одинаково, но их можно разбить на две разные группы: входящие и выходящие туннели. У входящих туннелей ненадёжный шлюз пропускает сообщения к создателю туннеля, который и является конечной точкой туннеля. В случае с выходящими туннелями их создатель служит шлюзом, пропускающим сообщения к удалённой точке. - -> -Создатель туннеля выбирает те узлы, которые будут входить в состав туннеля, и обеспечивает каждого из них необходимыми данными конфигурации. Количество транзитных участков может быть любым. Это делается для того, чтобы другим участникам или третьей стороне было сложно определить длину туннеля, или же даже для того, чтобы сговаривающиеся участники не могли вообще определить, являются ли они участниками одного и того же туннеля (это исключает возможность возникновения ситуации, когда сговорившиеся узлы оказываются в сети рядом друг с другом). - -### Примечания - -Из статьи @Java-I2P: - -> -@I2P является пакетной коммутируемой сетью даже с учётом наличия этих туннелей, что позволяет пользоваться преимуществом использования множества туннелей, работающих параллельно. Это повышает устойчивость сети и сбалансированность нагрузки. Даже несмотря на то, что I2P туннели напоминают сеть с коммутацией каналов, всё в I2P строго завязано на сообщениях — туннели являются просто ухищрением, позволяющим организовать доставку сообщений. Нет никаких условий, касающихся надёжности или порядка сообщений, а ретрансляция происходит на более высоких уровнях (например, потоковой библиотеки клиентского уровня I2P). - -### Документация - -Спецификации и подробную документацию можно найти на страницах [туннельная маршрутизация](https://geti2p.net/en/docs/how/tunnel-routing) и [реализация туннелей](https://geti2p.net/en/docs/tunnels/implementation). diff --git a/_i18n/tr/resources/moneropedia/base32-address.md b/_i18n/tr/resources/moneropedia/base32-address.md deleted file mode 100644 index 9737f7c0..00000000 --- a/_i18n/tr/resources/moneropedia/base32-address.md +++ /dev/null @@ -1,25 +0,0 @@ ---- -tags: ["kovri"] -terms: ["Base32-address", "Base32-addresses"] -summary: "Base32 encoded hash of a Base64 address" ---- - -### The Basics - -A Base32 address is a shortened, encoded version of an @I2P address. The Base32 address is the first part in a `.b32.i2p` hostname. - -Example: - -`i35yftyyb22xhcvghmev46t5knefur5v66qzekkajatwfwhyklvq.b32.i2p` - -where - -`i35yftyyb22xhcvghmev46t5knefur5v66qzekkajatwfwhyklvq` is the Base32 address. - -### In-depth Information - -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. - -### Notes - -**Note: `.b32` is not a sub-domain of `.i2p`** diff --git a/_i18n/tr/resources/moneropedia/base64-address.md b/_i18n/tr/resources/moneropedia/base64-address.md deleted file mode 100644 index 56a0589a..00000000 --- a/_i18n/tr/resources/moneropedia/base64-address.md +++ /dev/null @@ -1,20 +0,0 @@ ---- -tags: ["kovri"] -terms: ["Base64-address", "Base64-addresses"] -summary: "Base64 encoded I2P destination" ---- - -### The Basics - -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: - -``` -AQZGLAMpI9Q0l0kmMj1vpJJYK3CjLp~fE3MfvE-e7KMKjI5cPOH6EN8m794uHJ6b09qM8mb9VEv1lVLEov~usVliTSXCSHuRBOCIwIOuDNU0AbVa4BpIx~2sU4TxKhoaA3zQ6VzINoduTdR2IJhPvI5xzezp7dR21CEQGGTbenDslXeQ4iLHFA2~bzp1f7etSl9T2W9RID-KH78sRQmzWnv7dbhNodMbpO6xsf1vENf6bMRzqD5vgHEHZu2aSoNuPyYxDU1eM6--61b2xp9mt1k3ud-5WvPVg89RaU9ugU5cxaHgR927lHMCAEU2Ax~zUb3DbrvgQBOTHnJEx2Fp7pOK~PnP6ylkYKQMfLROosLDXinxOoSKP0UYCh2WgIUPwE7WzJH3PiJVF0~WZ1dZ9mg00c~gzLgmkOxe1NpFRNg6XzoARivNVB5NuWqNxr5WKWMLBGQ9YHvHO1OHhUJTowb9X90BhtHnLK2AHwO6fV-iHWxRJyDabhSMj1kuYpVUBQAEAAcAAA== -``` - - -### In-depth Information - -See @destination for details behind @base64-address diff --git a/_i18n/tr/resources/moneropedia/data-directory.md b/_i18n/tr/resources/moneropedia/data-directory.md deleted file mode 100644 index abe307f2..00000000 --- a/_i18n/tr/resources/moneropedia/data-directory.md +++ /dev/null @@ -1,20 +0,0 @@ ---- -tags: ["kovri"] -terms: ["Data-Directory"] -summary: "Where essential kovri data for runtime is stored" ---- - -### The Basics - -Depending on your OS, @Kovri currently stores all run-time data in the following directory: - -- Linux/FreeBSD: - - `$HOME/.kovri` - -- OSX: - - `$HOME/Library/Application\ Support/Kovri` - -- Windows: - - `"$APPDATA"\\Kovri` - -This includes all configuration files, @address-book, certificates, and resources. diff --git a/_i18n/tr/resources/moneropedia/eepsite.md b/_i18n/tr/resources/moneropedia/eepsite.md deleted file mode 100644 index efb16e1a..00000000 --- a/_i18n/tr/resources/moneropedia/eepsite.md +++ /dev/null @@ -1,28 +0,0 @@ ---- -tags: ["kovri"] -terms: ["Eepsite", "Hidden-Service", "Garlic-Site", "Garlic-Service"] -summary: "A website or service hosted within the I2P network" ---- - -### The Basics - -Is it [**EEP!** *(in response to the site's content)*](https://en.wikipedia.org/wiki/Onomatopoeia), or **end-to-end protocol**, or something else entirely different? - -While the original definition of eepsite has been lost with time, its use-case remains: an eepsite is a website or service that is hosted within (and only accessible by) the @I2P network. - -### In-depth Information - -Alternate names include: - -1. *Hidden Service* - - because the site/service is *hidden* within the @I2P network and can only be visited within the network -2. *Garlic Site* - - because the website utilizes @I2P's @garlic-routing technology as a means of communicating with a client - - because the service is hosted as a website and not any other type of service -3. *Garlic Service* - - because the service utilizes @I2P's @garlic-routing technology as a means of communicating with a client - - because the service is specific to services like IRC, email, or a Monero peer (but may also include websites) - -### Notes - -To learn how to setup an Eepsite (Hidden Service, Garlic Site, Garlic Service) visit the @Kovri [user-guide](https://gitlab.com/kovri-project/kovri-docs/blob/master/i18n/en/user_guide.md). diff --git a/_i18n/tr/resources/moneropedia/floodfill.md b/_i18n/tr/resources/moneropedia/floodfill.md deleted file mode 100644 index f2cb5f04..00000000 --- a/_i18n/tr/resources/moneropedia/floodfill.md +++ /dev/null @@ -1,13 +0,0 @@ ---- -tags: ["kovri"] -terms: ["Floodfill"] -summary: "An I2P router which maintains a distributed network-database" ---- - -### The Basics - -By actively managing a distributed network-database, a router with *floodfill* capability has the ability to help maintain network stability and resiliancy while also being decentralized and trust-less. - -### In-depth information - -Though floodfill itself is a simple storage system, the technical underpinnings of floodfill as it relates to @network-database and other protocols within @I2P are much more complex. Visit the [Network Database](https://geti2p.net/en/docs/how/network-database) page for details. diff --git a/_i18n/tr/resources/moneropedia/garlic-encryption.md b/_i18n/tr/resources/moneropedia/garlic-encryption.md deleted file mode 100644 index 271d7f0c..00000000 --- a/_i18n/tr/resources/moneropedia/garlic-encryption.md +++ /dev/null @@ -1,23 +0,0 @@ ---- -tags: ["kovri"] -terms: ["Garlic-Encryption", "Layered-Encryption"] -summary: "Layered encryption as implemented in Kovri / I2P" ---- - -### The Basics - -@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 - -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. diff --git a/_i18n/tr/resources/moneropedia/garlic-routing.md b/_i18n/tr/resources/moneropedia/garlic-routing.md deleted file mode 100644 index 6e4865e3..00000000 --- a/_i18n/tr/resources/moneropedia/garlic-routing.md +++ /dev/null @@ -1,43 +0,0 @@ ---- -tags: ["kovri"] -terms: ["Garlic-Routing"] -summary: "Routing technology as implemented in Kovri" ---- - -### 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. - -The @Garlic-Encryption of @Garlic-Routing is similar to the @Layered-Encryption of [Onion Routing](https://en.wikipedia.org/wiki/Onion_routing) and effectively conceals the IP address of the sender and secures information sent from the sender to its @destination (and vice-versa). - -### 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](http://www.freehaven.net/papers.html) (Section 8.1.1) as derived from the term Onion Routing. - -As recent as October of 2016, [#tor-dev](https://oftc.net/WebChat/) has offered insight into the creation of the term *@garlic-routing*: - -[Nick Mathewson](https://en.wikipedia.org/wiki/The_Tor_Project,_Inc): ->[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](https://en.wikipedia.org/wiki/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 was 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 (similar to the @layered-encryption in Onion Routing) -- Bundling multiple @messages together (garlic cloves) -- ElGamal/AES @encryption - -*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 - -- In terms of Onion/Garlic Routing, another way to envision layered @encryption is by replacing the onion/garlic with a [Matryoshka doll](https://en.wikipedia.org/wiki/Matryoshka_doll) - with each outer/inner doll having a lock and public key to the next/previous doll -- For more technical details on Garlic Routing, read the @Java-I2P entry on [Garlic Routing](https://geti2p.net/en/docs/how/garlic-routing) diff --git a/_i18n/tr/resources/moneropedia/i2np.md b/_i18n/tr/resources/moneropedia/i2np.md deleted file mode 100644 index 556f59ee..00000000 --- a/_i18n/tr/resources/moneropedia/i2np.md +++ /dev/null @@ -1,26 +0,0 @@ ---- -tags: ["kovri"] -terms: ["I2NP"] -summary: "The I2P Network Protocol: the mechanism in which I2NP messages are sent over the I2P network" ---- - -### The Basics - -From @Java-I2P: - -> -@I2NP manages the routing and mixing of messages between routers, as well as the selection of what transports to use when communicating with a peer for which there are multiple common transports supported - -### In-depth information - -From @Java-I2P: - -> -@I2NP (@I2P Network Protocol) @messages can be used for one-hop, router-to-router, point-to-point @messages. By @encrypting and wrapping @messages in other @messages, they can be sent in a secure way through multiple hops to the ultimate @destination. @I2NP does not specify nor require any particular @transport layer but does require at least one @transport in use. - -> -Whenever a @destination wants to send a message to to another @destination, it provides its local router with both the @destination structure and the raw bytes of the message to be sent. The router then determines where to send it, delivers it through outbound @tunnels, instructing the end point to pass it along to the appropriate inbound @tunnel, where it is passed along again to that @tunnel's end point and made available to the target for reception. - -### Notes - -Read more about the @I2NP [protocol](https://geti2p.net/en/docs/protocol/i2np) and [specification](https://geti2p.net/spec/i2np). diff --git a/_i18n/tr/resources/moneropedia/i2p.md b/_i18n/tr/resources/moneropedia/i2p.md deleted file mode 100644 index 26ef9c46..00000000 --- a/_i18n/tr/resources/moneropedia/i2p.md +++ /dev/null @@ -1,29 +0,0 @@ ---- -tags: ["kovri"] -terms: ["I2P"] -summary: "The Invisible Internet Project: an anonymizing overlay network" ---- - -### Monero - -For Monero's implementation of @I2P, see @Kovri. For a comparison of @I2P to [Tor](https://torproject.org/), read the [Comparison](https://geti2p.net/en/comparison/tor) page. - -### The Basics - -From @Java-I2P: - ->The I2P network provides strong privacy protections for communication over the Internet. Many activities that would risk your privacy on the public Internet can be conducted anonymously inside I2P. - -### In-depth information - -From @Java-I2P: - ->I2P is an anonymous overlay network - a network within a network. It is intended to protect communication from dragnet surveillance and monitoring by third parties such as ISPs. - ->I2P is used by many people who care about their privacy: activists, oppressed people, journalists and whistleblowers, as well as the average person. - ->No network can be "perfectly anonymous". The continued goal of I2P is to make attacks more and more difficult to mount. Its anonymity will get stronger as the size of the network increases and with ongoing academic review. - -### Notes - -@I2P documentation and specifications are available [here](https://geti2p.net/docs/). diff --git a/_i18n/tr/resources/moneropedia/i2pcontrol.md b/_i18n/tr/resources/moneropedia/i2pcontrol.md deleted file mode 100644 index 5491fc4e..00000000 --- a/_i18n/tr/resources/moneropedia/i2pcontrol.md +++ /dev/null @@ -1,15 +0,0 @@ ---- -tags: ["kovri"] -terms: ["I2PControl"] -summary: "An API inteface for Kovri and Java-I2P that allows simple remote control" ---- - -### The Basics - -@I2Pcontrol is a [JSONRPC2](https://en.wikipedia.org/wiki/JSON-RPC) [API](https://en.wikipedia.org/wiki/Application_programming_interface) for @Kovri and @Java-I2P which allows an @I2PControl client to remote control/monitor a running instance. - -Two available @I2PControl clients are: [qtoopie](https://github.com/EinMByte/qtoopie) (C++ client) and [itoopie](https://github.com/i2p/i2p.itoopie) (Java client). Read `kovri.conf` to configure @I2PControl for @Kovri. - -### In-depth information - -Details and specification available on the [I2PControl](https://geti2p.net/en/docs/api/i2pcontrol) page. diff --git a/_i18n/tr/resources/moneropedia/in-net.md b/_i18n/tr/resources/moneropedia/in-net.md deleted file mode 100644 index 884d40f0..00000000 --- a/_i18n/tr/resources/moneropedia/in-net.md +++ /dev/null @@ -1,13 +0,0 @@ ---- -tags: ["kovri"] -terms: ["In-net"] -summary: "Within the I2P network" ---- - -### The Basics - -**In-net** is a [colloquial](https://en.wikipedia.org/wiki/Colloquial) term of which describes activities, protocols, or functionality that exist *only* within the @I2P network. - -### In-depth information - -Example: *in-net download* would be defined as downloading *only* within @I2P. diff --git a/_i18n/tr/resources/moneropedia/java-i2p.md b/_i18n/tr/resources/moneropedia/java-i2p.md deleted file mode 100644 index ede62818..00000000 --- a/_i18n/tr/resources/moneropedia/java-i2p.md +++ /dev/null @@ -1,13 +0,0 @@ ---- -tags: ["kovri"] -terms: ["Java-I2P"] -summary: "The original implementation of I2P - written in Java" ---- - -### The Basics - -The term "Java I2P" is often used to describe the original @I2P implementation currently most known and used today. There are various other @I2P implementations, including @Kovri; all of which look up to the original Java implementation. - -### Notes - -To download/learn more about the Java implementation, visit their [website](https://geti2p.net/). diff --git a/_i18n/tr/resources/moneropedia/jump-service.md b/_i18n/tr/resources/moneropedia/jump-service.md deleted file mode 100644 index 60619ede..00000000 --- a/_i18n/tr/resources/moneropedia/jump-service.md +++ /dev/null @@ -1,32 +0,0 @@ ---- -tags: ["kovri"] -terms: ["Jump-Service"] -summary: "An I2P website service that adds addresses to your address book" ---- - -### The Basics - -In your @I2P configured web browser, you can use a Jump Service to *jump* to an @I2P address that you don't have in your @address-book. Once you've *jumped* to the address, the address will be saved into your @address-book. - -### In-depth Information - -In an @I2P configured browser, visit: http://stats.i2p/i2p/lookup.html (courtesy of @Java-I2P's lead developer *zzz*) - -Then, you'll have two options: - -1. *Hostname lookup* the address you wish to visit and then manually copy/paste the result -2. *Jump* to the @I2P website by entering the @I2P hostname (**recommended**) - -### Using hostname lookup - -For example, entering `pinkpaste.i2p` into the *Hostname lookup* box (and then submitting) will return: - -``` -pinkpaste.i2p=m-HrPrIAsdxts0WM~P4mE8mt9P7g-QTaBvu7Gc6Nl0UX7Vwck-i~RvOPfK6W~kfdRvwhNTqevkBL2UF5l36We02Aiywu7kB2xOHRkze68h-Tg2ewvRVwokohguCD2G3wwAEz~7FVda2avYDCb9-N6TfuzxKLnmhPMvbNSjGL7ZsD2p-h207R3-2kvuMV9bfu-K~w9NI9XJhIyufvUnFYc2jnTVg8PbaR4UP57cNaOO2YIMPkbr6~yTcIu9B1sUfHK6-N~6virQDOxW4M-62rjnZkLpaCtkOsXslmCwZI--TkZ6hKi1kXZvNmJRE1rYfffYRFn38zhaqszeETX8HiIvahZhXF5fNumBziYdmLdw8hkuN1A~emU6Xz9g~a1Ixfsq1Qr~guYoOtaw-0rOFxNRS9yMehE-2LCb8c-cAg6z5OdlN4qJDl~ZHgru4d~EHp~BpAK3v7u2Gi-8l1ygVW-1CHVna~fwnbOPN3ANPwh6~~yUit0Cx1f54XiNRn6-nPBQAEAAcAAA== -``` - -Copy/paste this host=@base64-address pairing into your **private** @subscription. - -### Directly jumping - -For example, entering `pinkpaste.i2p` into the *Jump* box (and then submitting) will automatically redirect you to the website **and** insert the @locally-unique-host into @address-book. diff --git a/_i18n/tr/resources/moneropedia/lease-set.md b/_i18n/tr/resources/moneropedia/lease-set.md deleted file mode 100644 index dc1c4a24..00000000 --- a/_i18n/tr/resources/moneropedia/lease-set.md +++ /dev/null @@ -1,23 +0,0 @@ ---- -tags: ["kovri"] -terms: ["LeaseSet", "LeaseSets"] -summary: "Contains all currently authorized Leases for a particular I2P Destination" ---- - -### The Basics - -A Lease-Set contains a set of authorized @leases (and other related information) for a particular @destination. - -### In-depth information - -A Lease-Set contains: - -- all of the currently authorized @leases for a particular @destination -- the public key to which garlic messages can be encrypted (see @garlic-routing) -- the signing public key that can be used to revoke this particular version of the structure - -The Lease-Set is one of the two structures stored in the @network-database (the other being @router-info), and is keyed under the SHA256 of the contained @destination. - -### Notes - -For further details, read @Java-I2P's [LeaseSet](https://geti2p.net/en/docs/how/network-database#leaseSet) diff --git a/_i18n/tr/resources/moneropedia/lease.md b/_i18n/tr/resources/moneropedia/lease.md deleted file mode 100644 index c5a78058..00000000 --- a/_i18n/tr/resources/moneropedia/lease.md +++ /dev/null @@ -1,13 +0,0 @@ ---- -tags: ["kovri"] -terms: ["Lease", "Leases"] -summary: "Authorizes an I2P tunnel to receive messages targeting a destination" ---- - -### The Basics - -A lease defines the authorization for a particular @I2P @tunnel to receive a @messages targeting a @destination. - -### In-depth information - -For further details, read @Java-I2P's [Lease](https://geti2p.net/spec/common-structures#lease) diff --git a/_i18n/tr/resources/moneropedia/message.md b/_i18n/tr/resources/moneropedia/message.md deleted file mode 100644 index 5cce553b..00000000 --- a/_i18n/tr/resources/moneropedia/message.md +++ /dev/null @@ -1,31 +0,0 @@ ---- -tags: ["kovri"] -terms: ["Message", "Messages"] -summary: "The mechanisms in which information travels within I2P" ---- - -### The Basics - -*Messages* (which exist on top of the @transports layer), contain varying types of information that are needed for the network but, most importantly, everything you see, do, send, or receive, will come and go in the form of *messages*. - -There are 2 essential types of *messages* in @I2P: - -- @Tunnel messages -- @I2NP messages - -Essentially: *@tunnel messages* **contain** @I2NP **message fragments** which are then [reassembled](https://geti2p.net/en/docs/tunnels/implementation) at certain points within a @tunnel's path. - -### In-depth information - -@I2NP messages have a close relationship with @tunnel @messages so it is easy to get the term *messages* confused when reading @Java-I2P specifications: - -> -1. First, the tunnel gateway accumulates a number of I2NP messages and preprocesses them into tunnel messages for delivery. -2. Next, that gateway encrypts that preprocessed data, then forwards it to the first hop. -3. That peer, and subsequent tunnel participants, unwrap a layer of the encryption, verifying that it isn't a duplicate, then forward it on to the next peer. -4. Eventually, the tunnel messages arrive at the endpoint where the I2NP messages originally bundled by the gateway are reassembled and forwarded on as requested. - -### Notes - -- @I2NP @messages need to be fragmented because they are variable in size (from 0 to almost 64 KB) and @tunnel @messages are fixed-size (approximately 1 KB). -- For details and specifications, visit the [I2NP spec](https://geti2p.net/spec/i2np) and [Tunnel Message spec](https://geti2p.net/spec/tunnel-message) diff --git a/_i18n/tr/resources/moneropedia/network-database.md b/_i18n/tr/resources/moneropedia/network-database.md deleted file mode 100644 index eb3925cd..00000000 --- a/_i18n/tr/resources/moneropedia/network-database.md +++ /dev/null @@ -1,23 +0,0 @@ ---- -tags: ["kovri"] -terms: ["Network-Database"] -summary: "A distributed database which contains needed router information so the network can stay intact" ---- - -### The Basics - -@network-database is a [distributed database](https://en.wikipedia.org/wiki/Distributed_database) which contains router information that peers must use so the network can stay intact. - -### In-depth information - -From @Java-I2P: - -> -@I2P's @network-database is a specialized distributed database, containing just two types of data - router contact information (@Router-Infos) and @destination contact information (@LeaseSets). Each piece of data is signed by the appropriate party and verified by anyone who uses or stores it. In addition, the data has liveliness information within it, allowing irrelevant entries to be dropped, newer entries to replace older ones, and protection against certain classes of attack. - -> -The @network-database is distributed with a simple technique called "@floodfill", where a subset of all routers, called "@floodfill routers", maintains the distributed database. - -### Notes - -Read [Network-Database](https://geti2p.net/en/docs/how/network-database) for details. diff --git a/_i18n/tr/resources/moneropedia/ntcp.md b/_i18n/tr/resources/moneropedia/ntcp.md deleted file mode 100644 index 69d10a3f..00000000 --- a/_i18n/tr/resources/moneropedia/ntcp.md +++ /dev/null @@ -1,32 +0,0 @@ ---- -tags: ["kovri"] -terms: ["NTCP"] -summary: "NIO-Based TCP (Non-blocking I/O based TCP): one of two Kovri transports" ---- - -### The Basics - -*NIO-Based TCP (Non-blocking I/O based TCP)* is one of two encrypted @transports for @Kovri. - -Similar to @SSU, @NTCP's *primary* purpose is to securely transmit @in-net @I2NP messages through @tunnels but, unlike @SSU, @NTCP functions solely over encrypted [TCP](https://en.wikipedia.org/wiki/Transmission_Control_Protocol). - -### In-depth information - - - Passes along individual @I2NP messages (both Standard and Time Sync) after: - - TCP has been established - - Establishment Sequence has been completed - - Uses the following @encryption: - - 2048-bit [Diffie-Hellman](https://en.wikipedia.org/wiki/Diffie-hellman) - - [AES-256](https://en.wikipedia.org/wiki/Advanced_Encryption_Standard)/[CBC](https://en.wikipedia.org/wiki/Block_cipher_modes_of_operation) - - Establishment Sequence has the following *states*: - - Pre-establishment - - Establishment - - Post-establishment or "Established" - - Uses the following from the @network-database: - - Transport name: NTCP - - Host: IP (IPv4 or IPv6) or host name (shortened IPv6 address (with "::") is allowed) - - Port: 1024 - 65535 - -### Notes - -For further details, read @Java-I2P's [NTCP](https://geti2p.net/en/docs/transport/ntcp) diff --git a/_i18n/tr/resources/moneropedia/reseed.md b/_i18n/tr/resources/moneropedia/reseed.md deleted file mode 100644 index 59727311..00000000 --- a/_i18n/tr/resources/moneropedia/reseed.md +++ /dev/null @@ -1,15 +0,0 @@ ---- -tags: ["kovri"] -terms: ["Reseed"] -summary: "The method of which Kovri uses to bootstrap into the I2P network" ---- - -### The Basics - -When you start @Kovri for the first time (or if it's been offline for a long time), @Kovri will need a list of peers to connect to so it can [bootstrap](https://en.wikipedia.org/wiki/Bootstrap) into the @I2P network. @Kovri gets these peers from a special file stored on a reseed server. On this file are all the various pieces of information @Kovri needs in order to connect with @I2P peers. - -### In-depth information - -@Kovri has a list of [hard-coded](https://en.wikipedia.org/wiki/Hard-coded) reseed servers available to fetch from. These servers securely serve an [SU3](https://geti2p.net/spec/updates#su3) file (signed with a cryptographic @signature) over @clearnet with [HTTPS](https://en.wikipedia.org/wiki/HTTPS). This SU3 file contains information that's used to verify both the integrity of the file and its content. - -Aside from the technical elements needed to verify and process the file, the file's main contents consist of a series of @router-info files which @Kovri and @I2P routers use to locate and communicate with other @I2P peers. These peers are then stored into a @network-database. diff --git a/_i18n/tr/resources/moneropedia/router-info.md b/_i18n/tr/resources/moneropedia/router-info.md deleted file mode 100644 index ad50c13f..00000000 --- a/_i18n/tr/resources/moneropedia/router-info.md +++ /dev/null @@ -1,66 +0,0 @@ ---- -tags: ["kovri"] -terms: ["Router-Info", "Router-infos"] -summary: "A data structure or file which contains an I2P peer's needed network information" ---- - -### The Basics - -@Router-Info is a data structure (periodically written to a [binary file](https://en.wikipedia.org/wiki/Binary_file)) which contains all needed information to locate, identify, and communicate with an @I2P peer. @Router-Info includes IP address, router identity, other misc. technical details; is needed for @network-database and is published to @floodfill routers. - -### In-depth information - -In human-readable form, Router-Info may look like this: - -``` -Identity: [RouterIdentity: -Hash: nYZ5Qe7gQ-~QgfgJVRUG4c0JnVeVqzM~duUX1EGT1ek= -Certificate: [Certificate: type: Key certificate -Crypto type: 0 -Sig type: 7 (EdDSA_SHA512_Ed25519)] -PublicKey: [PublicKey: size: 256] -SigningPublicKey: [SigningPublicKey EdDSA_SHA512_Ed25519: size: 32] -Padding: 96 bytes] -Signature: [Signature EdDSA_SHA512_Ed25519: size: 64] -Published: Sun Oct 09 01:34:59 UTC 2016 -Options (5): - [caps] = [LfR] - [netId] = [2] - [netdb.knownLeaseSets] = [37] - [netdb.knownRouters] = [2435] - [router.version] = [0.9.26] -Addresses (4): -[RouterAddress: -Type: SSU -Cost: 4 -Options (5): - [caps] = [BC] - [host] = [2a01:e35:8b5c:b240:71a2:6750:8d4:47fa] - [key] = [nYZ5Qe7gQ-~QgfgJVRUG4c0JnVeVqzM~duUX1EGT1ek=] - [mtu] = [1472] - [port] = [22244]] -[RouterAddress: -Type: NTCP -Cost: 9 -Options (2): - [host] = [2a01:e35:8b5c:b240:71a2:6750:8d4:47fa] - [port] = [22244]] -[RouterAddress: -Type: SSU -Cost: 6 -Options (4): - [caps] = [BC] - [host] = [88.181.203.36] - [key] = [nYZ5Qe7gQ-~QgfgJVRUG4c0JnVeVqzM~duUX1EGT1ek=] - [port] = [22244]] -[RouterAddress: -Type: NTCP -Cost: 11 -Options (2): - [host] = [88.181.203.36] - [port] = [22244]]] -``` - -### Notes - -For details and specification, visit @Java-I2P [Network Database](https://geti2p.net/en/docs/how/network-database) page. diff --git a/_i18n/tr/resources/moneropedia/ssu.md b/_i18n/tr/resources/moneropedia/ssu.md deleted file mode 100644 index a7b2eb5b..00000000 --- a/_i18n/tr/resources/moneropedia/ssu.md +++ /dev/null @@ -1,24 +0,0 @@ ---- -tags: ["kovri"] -terms: ["SSU"] -summary: "Secure Semi-reliable UDP: one of two Kovri transports" ---- - -### The Basics - -*Secure Semi-reliable UDP* is one of two encrypted @transports for @Kovri. - -Similar to @NTCP, @SSU's *primary* purpose is to securely transmit @in-net @I2NP messages through @tunnels but, unlike @NTCP, @SSU functions solely over encrypted [UDP](https://en.wikipedia.org/wiki/User_Datagram_Protocol). - -### In-depth information - -- Like @NTCP, @SSU is a connection-oriented, point-to-point data transport -- Termed *semi-reliable* because @SSU will repeatedly retransmit *unacknowledged* messages (up to maximum number then dropped) -- @SSU also provides several unique services (in addition to its function as a @transport layer): - - IP detection (local inspection or with [peer testing](https://geti2p.net/en/docs/transport/ssu#peerTesting)) - - [NAT](https://en.wikipedia.org/wiki/Network_address_translation) traversal (using [introducers](https://geti2p.net/en/docs/transport/ssu#introduction)) - - [Firewall](https://en.wikipedia.org/wiki/Firewall_%28computing%29) status and, if implemented, @SSU can notify @NTCP if the external address or firewall status changes - -### Notes - -For further details, read @Java-I2P's [SSU](https://geti2p.net/en/docs/transport/ssu) diff --git a/_i18n/tr/resources/moneropedia/subscription.md b/_i18n/tr/resources/moneropedia/subscription.md deleted file mode 100644 index 78ef1bf4..00000000 --- a/_i18n/tr/resources/moneropedia/subscription.md +++ /dev/null @@ -1,45 +0,0 @@ ---- -tags: ["kovri"] -terms: ["Subscription"] -summary: "A file used by address book which contains I2P hosts paired with I2P destinations" ---- - -### The Basics - -A subscription is a file which contains a list of `.i2p` hosts paired with their respective @destination. Subscriptions are used by the @address-book. - -### In-depth information - -Similar to how a [hosts file](https://en.wikipedia.org/wiki/Hosts_(file)) can map an internet hostname to a specified address, a subscription matches a `.i2p` address to @base64-address by using the following format (no spaces allowed): `host=address` - -More specifically, a subscription pairs a @locally-unique-host to @base64-address. - -Example: - -``` -anonimal.i2p=AQZGLAMpI9Q0l0kmMj1vpJJYK3CjLp~fE3MfvE-e7KMKjI5cPOH6EN8m794uHJ6b09qM8mb9VEv1lVLEov~usVliTSXCSHuRBOCIwIOuDNU0AbVa4BpIx~2sU4TxKhoaA3zQ6VzINoduTdR2IJhPvI5xzezp7dR21CEQGGTbenDslXeQ4iLHFA2~bzp1f7etSl9T2W9RID-KH78sRQmzWnv7dbhNodMbpO6xsf1vENf6bMRzqD5vgHEHZu2aSoNuPyYxDU1eM6--61b2xp9mt1k3ud-5WvPVg89RaU9ugU5cxaHgR927lHMCAEU2Ax~zUb3DbrvgQBOTHnJEx2Fp7pOK~PnP6ylkYKQMfLROosLDXinxOoSKP0UYCh2WgIUPwE7WzJH3PiJVF0~WZ1dZ9mg00c~gzLgmkOxe1NpFRNg6XzoARivNVB5NuWqNxr5WKWMLBGQ9YHvHO1OHhUJTowb9X90BhtHnLK2AHwO6fV-iHWxRJyDabhSMj1kuYpVUBQAEAAcAAA== -``` - -1. `anonimal.i2p` is the @locally-unique-host -2. `=` is the separator -3. Everything that remains is the @base64-address - -### Subscription types - -For @Kovri, there are two types of subscription files: *public* and *private*. - -A *public* subscription: -- is used when bootstrapping to use essential services (IRC, email, Monero, etc.) -- is static and is refreshed every 12 hours from Monero's @address-book server -- allows you to safely share the subscription with everyone as it is publically available (anyone who shares the same public subscription will also be able to resolve the same hostname to the same destination as you) - -A *private* subscription: -- is used exclusively by you and is not shared with others unless you explicitly choose to share the file -- default file is `private_hosts.txt` in your @data-directory - -### Updating a private subscription - -You can use a @jump-service to manually update your private subscription. The updated subscription will then be fed into the @address-book for you to use. - -### Notes -To learn how to subscribe to multiple subscriptions, see the [user-guide](https://gitlab.com/kovri-project/kovri-docs/blob/master/i18n/en/user_guide.md). diff --git a/_i18n/tr/resources/moneropedia/transports.md b/_i18n/tr/resources/moneropedia/transports.md deleted file mode 100644 index 01225e66..00000000 --- a/_i18n/tr/resources/moneropedia/transports.md +++ /dev/null @@ -1,18 +0,0 @@ ---- -tags: ["kovri"] -terms: ["Transports", "Transport"] -summary: "The two encrypted transport layers for Kovri" ---- - -### The Basics - -@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 - -@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 @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) diff --git a/_i18n/tr/resources/moneropedia/tunnel.md b/_i18n/tr/resources/moneropedia/tunnel.md deleted file mode 100644 index 94369ad2..00000000 --- a/_i18n/tr/resources/moneropedia/tunnel.md +++ /dev/null @@ -1,35 +0,0 @@ ---- -tags: ["kovri"] -terms: ["Tunnel", "Tunnels"] -summary: "Uni-directional virtual paths that pass messages through a defined sequence of I2P routers" ---- - -### The Basics - -When you communicate over @I2P (visit an @eepsite / use a @garlic-service), you'll first need to connect to a peer by using @transports and then build virtual *tunnels*. These virtual tunnels are temporary, uni-directional paths that pass information through a defined sequence of @I2P routers to your @destination. Tunnels are built, and then used, with layered @garlic-encryption and are a general-purpose mechanism to transport all @I2NP @messages. - -Each peer builds, at a minimum, *two* uni-directional tunnels: one for **outbound traffic**, and one for **inbound traffic**. These tunnels are classified as either **inbound tunnels** (where @messages come toward the creator of the tunnel) or **outbound tunnels** (where the tunnel creator sends @messages away from the creator of the tunnel). Thus, *four* tunnels are required for a single round-trip @message and reply to your @destination (two for your, two for your destination). - -### In-depth information - -From @Java-I2P: - -> -Within I2P, @messages are passed in one direction through a virtual tunnel of peers, using whatever means are available to pass the @message on to the next hop. Messages arrive at the tunnel's gateway, get bundled up and/or fragmented into fixed-size @tunnel @messages, and are forwarded on to the next hop in the tunnel, which processes and verifies the validity of the @message and sends it on to the next hop, and so on, until it reaches the @tunnel endpoint. That endpoint takes the messages bundled up by the gateway and forwards them as instructed - either to another router, to another tunnel on another router, or locally. - -> -Tunnels all work the same, but can be segmented into two different groups - inbound tunnels and outbound tunnels. The inbound tunnels have an untrusted gateway which passes messages down towards the tunnel creator, which serves as the tunnel endpoint. For outbound tunnels, the tunnel creator serves as the gateway, passing messages out to the remote endpoint. - -> -The tunnel's creator selects exactly which peers will participate in the tunnel, and provides each with the necessary configuration data. They may have any number of hops. It is the intent to make it hard for either participants or third parties to determine the length of a tunnel, or even for colluding participants to determine whether they are a part of the same tunnel at all (barring the situation where colluding peers are next to each other in the tunnel). - -### Notes - -From @Java-I2P: - -> -@I2P is an inherently packet switched network, even with these tunnels, allowing it to take advantage of multiple tunnels running in parallel, increasing resilience and balancing load. Even though the tunnels within I2P bear a resemblance to a circuit switched network, everything within I2P is strictly message based - tunnels are merely accounting tricks to help organize the delivery of messages. No assumptions are made regarding reliability or ordering of messages, and retransmissions are left to higher levels (e.g. I2P's client layer streaming library). - -### Documentation - -For specification and detailed documentation, visit the [Tunnel-Routing](https://geti2p.net/en/docs/how/tunnel-routing) and [Tunnel-Implementation](https://geti2p.net/en/docs/tunnels/implementation) page. diff --git a/_i18n/zh-cn/resources/moneropedia/base32-address.md b/_i18n/zh-cn/resources/moneropedia/base32-address.md deleted file mode 100644 index 9737f7c0..00000000 --- a/_i18n/zh-cn/resources/moneropedia/base32-address.md +++ /dev/null @@ -1,25 +0,0 @@ ---- -tags: ["kovri"] -terms: ["Base32-address", "Base32-addresses"] -summary: "Base32 encoded hash of a Base64 address" ---- - -### The Basics - -A Base32 address is a shortened, encoded version of an @I2P address. The Base32 address is the first part in a `.b32.i2p` hostname. - -Example: - -`i35yftyyb22xhcvghmev46t5knefur5v66qzekkajatwfwhyklvq.b32.i2p` - -where - -`i35yftyyb22xhcvghmev46t5knefur5v66qzekkajatwfwhyklvq` is the Base32 address. - -### In-depth Information - -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. - -### Notes - -**Note: `.b32` is not a sub-domain of `.i2p`** diff --git a/_i18n/zh-cn/resources/moneropedia/base64-address.md b/_i18n/zh-cn/resources/moneropedia/base64-address.md deleted file mode 100644 index 56a0589a..00000000 --- a/_i18n/zh-cn/resources/moneropedia/base64-address.md +++ /dev/null @@ -1,20 +0,0 @@ ---- -tags: ["kovri"] -terms: ["Base64-address", "Base64-addresses"] -summary: "Base64 encoded I2P destination" ---- - -### The Basics - -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: - -``` -AQZGLAMpI9Q0l0kmMj1vpJJYK3CjLp~fE3MfvE-e7KMKjI5cPOH6EN8m794uHJ6b09qM8mb9VEv1lVLEov~usVliTSXCSHuRBOCIwIOuDNU0AbVa4BpIx~2sU4TxKhoaA3zQ6VzINoduTdR2IJhPvI5xzezp7dR21CEQGGTbenDslXeQ4iLHFA2~bzp1f7etSl9T2W9RID-KH78sRQmzWnv7dbhNodMbpO6xsf1vENf6bMRzqD5vgHEHZu2aSoNuPyYxDU1eM6--61b2xp9mt1k3ud-5WvPVg89RaU9ugU5cxaHgR927lHMCAEU2Ax~zUb3DbrvgQBOTHnJEx2Fp7pOK~PnP6ylkYKQMfLROosLDXinxOoSKP0UYCh2WgIUPwE7WzJH3PiJVF0~WZ1dZ9mg00c~gzLgmkOxe1NpFRNg6XzoARivNVB5NuWqNxr5WKWMLBGQ9YHvHO1OHhUJTowb9X90BhtHnLK2AHwO6fV-iHWxRJyDabhSMj1kuYpVUBQAEAAcAAA== -``` - - -### In-depth Information - -See @destination for details behind @base64-address diff --git a/_i18n/zh-cn/resources/moneropedia/data-directory.md b/_i18n/zh-cn/resources/moneropedia/data-directory.md deleted file mode 100644 index abe307f2..00000000 --- a/_i18n/zh-cn/resources/moneropedia/data-directory.md +++ /dev/null @@ -1,20 +0,0 @@ ---- -tags: ["kovri"] -terms: ["Data-Directory"] -summary: "Where essential kovri data for runtime is stored" ---- - -### The Basics - -Depending on your OS, @Kovri currently stores all run-time data in the following directory: - -- Linux/FreeBSD: - - `$HOME/.kovri` - -- OSX: - - `$HOME/Library/Application\ Support/Kovri` - -- Windows: - - `"$APPDATA"\\Kovri` - -This includes all configuration files, @address-book, certificates, and resources. diff --git a/_i18n/zh-cn/resources/moneropedia/eepsite.md b/_i18n/zh-cn/resources/moneropedia/eepsite.md deleted file mode 100644 index efb16e1a..00000000 --- a/_i18n/zh-cn/resources/moneropedia/eepsite.md +++ /dev/null @@ -1,28 +0,0 @@ ---- -tags: ["kovri"] -terms: ["Eepsite", "Hidden-Service", "Garlic-Site", "Garlic-Service"] -summary: "A website or service hosted within the I2P network" ---- - -### The Basics - -Is it [**EEP!** *(in response to the site's content)*](https://en.wikipedia.org/wiki/Onomatopoeia), or **end-to-end protocol**, or something else entirely different? - -While the original definition of eepsite has been lost with time, its use-case remains: an eepsite is a website or service that is hosted within (and only accessible by) the @I2P network. - -### In-depth Information - -Alternate names include: - -1. *Hidden Service* - - because the site/service is *hidden* within the @I2P network and can only be visited within the network -2. *Garlic Site* - - because the website utilizes @I2P's @garlic-routing technology as a means of communicating with a client - - because the service is hosted as a website and not any other type of service -3. *Garlic Service* - - because the service utilizes @I2P's @garlic-routing technology as a means of communicating with a client - - because the service is specific to services like IRC, email, or a Monero peer (but may also include websites) - -### Notes - -To learn how to setup an Eepsite (Hidden Service, Garlic Site, Garlic Service) visit the @Kovri [user-guide](https://gitlab.com/kovri-project/kovri-docs/blob/master/i18n/en/user_guide.md). diff --git a/_i18n/zh-cn/resources/moneropedia/floodfill.md b/_i18n/zh-cn/resources/moneropedia/floodfill.md deleted file mode 100644 index f2cb5f04..00000000 --- a/_i18n/zh-cn/resources/moneropedia/floodfill.md +++ /dev/null @@ -1,13 +0,0 @@ ---- -tags: ["kovri"] -terms: ["Floodfill"] -summary: "An I2P router which maintains a distributed network-database" ---- - -### The Basics - -By actively managing a distributed network-database, a router with *floodfill* capability has the ability to help maintain network stability and resiliancy while also being decentralized and trust-less. - -### In-depth information - -Though floodfill itself is a simple storage system, the technical underpinnings of floodfill as it relates to @network-database and other protocols within @I2P are much more complex. Visit the [Network Database](https://geti2p.net/en/docs/how/network-database) page for details. diff --git a/_i18n/zh-cn/resources/moneropedia/garlic-encryption.md b/_i18n/zh-cn/resources/moneropedia/garlic-encryption.md deleted file mode 100644 index 271d7f0c..00000000 --- a/_i18n/zh-cn/resources/moneropedia/garlic-encryption.md +++ /dev/null @@ -1,23 +0,0 @@ ---- -tags: ["kovri"] -terms: ["Garlic-Encryption", "Layered-Encryption"] -summary: "Layered encryption as implemented in Kovri / I2P" ---- - -### The Basics - -@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 - -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. diff --git a/_i18n/zh-cn/resources/moneropedia/garlic-routing.md b/_i18n/zh-cn/resources/moneropedia/garlic-routing.md deleted file mode 100644 index 6e4865e3..00000000 --- a/_i18n/zh-cn/resources/moneropedia/garlic-routing.md +++ /dev/null @@ -1,43 +0,0 @@ ---- -tags: ["kovri"] -terms: ["Garlic-Routing"] -summary: "Routing technology as implemented in Kovri" ---- - -### 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. - -The @Garlic-Encryption of @Garlic-Routing is similar to the @Layered-Encryption of [Onion Routing](https://en.wikipedia.org/wiki/Onion_routing) and effectively conceals the IP address of the sender and secures information sent from the sender to its @destination (and vice-versa). - -### 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](http://www.freehaven.net/papers.html) (Section 8.1.1) as derived from the term Onion Routing. - -As recent as October of 2016, [#tor-dev](https://oftc.net/WebChat/) has offered insight into the creation of the term *@garlic-routing*: - -[Nick Mathewson](https://en.wikipedia.org/wiki/The_Tor_Project,_Inc): ->[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](https://en.wikipedia.org/wiki/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 was 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 (similar to the @layered-encryption in Onion Routing) -- Bundling multiple @messages together (garlic cloves) -- ElGamal/AES @encryption - -*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 - -- In terms of Onion/Garlic Routing, another way to envision layered @encryption is by replacing the onion/garlic with a [Matryoshka doll](https://en.wikipedia.org/wiki/Matryoshka_doll) - with each outer/inner doll having a lock and public key to the next/previous doll -- For more technical details on Garlic Routing, read the @Java-I2P entry on [Garlic Routing](https://geti2p.net/en/docs/how/garlic-routing) diff --git a/_i18n/zh-cn/resources/moneropedia/i2np.md b/_i18n/zh-cn/resources/moneropedia/i2np.md deleted file mode 100644 index 556f59ee..00000000 --- a/_i18n/zh-cn/resources/moneropedia/i2np.md +++ /dev/null @@ -1,26 +0,0 @@ ---- -tags: ["kovri"] -terms: ["I2NP"] -summary: "The I2P Network Protocol: the mechanism in which I2NP messages are sent over the I2P network" ---- - -### The Basics - -From @Java-I2P: - -> -@I2NP manages the routing and mixing of messages between routers, as well as the selection of what transports to use when communicating with a peer for which there are multiple common transports supported - -### In-depth information - -From @Java-I2P: - -> -@I2NP (@I2P Network Protocol) @messages can be used for one-hop, router-to-router, point-to-point @messages. By @encrypting and wrapping @messages in other @messages, they can be sent in a secure way through multiple hops to the ultimate @destination. @I2NP does not specify nor require any particular @transport layer but does require at least one @transport in use. - -> -Whenever a @destination wants to send a message to to another @destination, it provides its local router with both the @destination structure and the raw bytes of the message to be sent. The router then determines where to send it, delivers it through outbound @tunnels, instructing the end point to pass it along to the appropriate inbound @tunnel, where it is passed along again to that @tunnel's end point and made available to the target for reception. - -### Notes - -Read more about the @I2NP [protocol](https://geti2p.net/en/docs/protocol/i2np) and [specification](https://geti2p.net/spec/i2np). diff --git a/_i18n/zh-cn/resources/moneropedia/i2p.md b/_i18n/zh-cn/resources/moneropedia/i2p.md deleted file mode 100644 index 26ef9c46..00000000 --- a/_i18n/zh-cn/resources/moneropedia/i2p.md +++ /dev/null @@ -1,29 +0,0 @@ ---- -tags: ["kovri"] -terms: ["I2P"] -summary: "The Invisible Internet Project: an anonymizing overlay network" ---- - -### Monero - -For Monero's implementation of @I2P, see @Kovri. For a comparison of @I2P to [Tor](https://torproject.org/), read the [Comparison](https://geti2p.net/en/comparison/tor) page. - -### The Basics - -From @Java-I2P: - ->The I2P network provides strong privacy protections for communication over the Internet. Many activities that would risk your privacy on the public Internet can be conducted anonymously inside I2P. - -### In-depth information - -From @Java-I2P: - ->I2P is an anonymous overlay network - a network within a network. It is intended to protect communication from dragnet surveillance and monitoring by third parties such as ISPs. - ->I2P is used by many people who care about their privacy: activists, oppressed people, journalists and whistleblowers, as well as the average person. - ->No network can be "perfectly anonymous". The continued goal of I2P is to make attacks more and more difficult to mount. Its anonymity will get stronger as the size of the network increases and with ongoing academic review. - -### Notes - -@I2P documentation and specifications are available [here](https://geti2p.net/docs/). diff --git a/_i18n/zh-cn/resources/moneropedia/i2pcontrol.md b/_i18n/zh-cn/resources/moneropedia/i2pcontrol.md deleted file mode 100644 index 5491fc4e..00000000 --- a/_i18n/zh-cn/resources/moneropedia/i2pcontrol.md +++ /dev/null @@ -1,15 +0,0 @@ ---- -tags: ["kovri"] -terms: ["I2PControl"] -summary: "An API inteface for Kovri and Java-I2P that allows simple remote control" ---- - -### The Basics - -@I2Pcontrol is a [JSONRPC2](https://en.wikipedia.org/wiki/JSON-RPC) [API](https://en.wikipedia.org/wiki/Application_programming_interface) for @Kovri and @Java-I2P which allows an @I2PControl client to remote control/monitor a running instance. - -Two available @I2PControl clients are: [qtoopie](https://github.com/EinMByte/qtoopie) (C++ client) and [itoopie](https://github.com/i2p/i2p.itoopie) (Java client). Read `kovri.conf` to configure @I2PControl for @Kovri. - -### In-depth information - -Details and specification available on the [I2PControl](https://geti2p.net/en/docs/api/i2pcontrol) page. diff --git a/_i18n/zh-cn/resources/moneropedia/in-net.md b/_i18n/zh-cn/resources/moneropedia/in-net.md deleted file mode 100644 index 884d40f0..00000000 --- a/_i18n/zh-cn/resources/moneropedia/in-net.md +++ /dev/null @@ -1,13 +0,0 @@ ---- -tags: ["kovri"] -terms: ["In-net"] -summary: "Within the I2P network" ---- - -### The Basics - -**In-net** is a [colloquial](https://en.wikipedia.org/wiki/Colloquial) term of which describes activities, protocols, or functionality that exist *only* within the @I2P network. - -### In-depth information - -Example: *in-net download* would be defined as downloading *only* within @I2P. diff --git a/_i18n/zh-cn/resources/moneropedia/java-i2p.md b/_i18n/zh-cn/resources/moneropedia/java-i2p.md deleted file mode 100644 index ede62818..00000000 --- a/_i18n/zh-cn/resources/moneropedia/java-i2p.md +++ /dev/null @@ -1,13 +0,0 @@ ---- -tags: ["kovri"] -terms: ["Java-I2P"] -summary: "The original implementation of I2P - written in Java" ---- - -### The Basics - -The term "Java I2P" is often used to describe the original @I2P implementation currently most known and used today. There are various other @I2P implementations, including @Kovri; all of which look up to the original Java implementation. - -### Notes - -To download/learn more about the Java implementation, visit their [website](https://geti2p.net/). diff --git a/_i18n/zh-cn/resources/moneropedia/jump-service.md b/_i18n/zh-cn/resources/moneropedia/jump-service.md deleted file mode 100644 index 60619ede..00000000 --- a/_i18n/zh-cn/resources/moneropedia/jump-service.md +++ /dev/null @@ -1,32 +0,0 @@ ---- -tags: ["kovri"] -terms: ["Jump-Service"] -summary: "An I2P website service that adds addresses to your address book" ---- - -### The Basics - -In your @I2P configured web browser, you can use a Jump Service to *jump* to an @I2P address that you don't have in your @address-book. Once you've *jumped* to the address, the address will be saved into your @address-book. - -### In-depth Information - -In an @I2P configured browser, visit: http://stats.i2p/i2p/lookup.html (courtesy of @Java-I2P's lead developer *zzz*) - -Then, you'll have two options: - -1. *Hostname lookup* the address you wish to visit and then manually copy/paste the result -2. *Jump* to the @I2P website by entering the @I2P hostname (**recommended**) - -### Using hostname lookup - -For example, entering `pinkpaste.i2p` into the *Hostname lookup* box (and then submitting) will return: - -``` -pinkpaste.i2p=m-HrPrIAsdxts0WM~P4mE8mt9P7g-QTaBvu7Gc6Nl0UX7Vwck-i~RvOPfK6W~kfdRvwhNTqevkBL2UF5l36We02Aiywu7kB2xOHRkze68h-Tg2ewvRVwokohguCD2G3wwAEz~7FVda2avYDCb9-N6TfuzxKLnmhPMvbNSjGL7ZsD2p-h207R3-2kvuMV9bfu-K~w9NI9XJhIyufvUnFYc2jnTVg8PbaR4UP57cNaOO2YIMPkbr6~yTcIu9B1sUfHK6-N~6virQDOxW4M-62rjnZkLpaCtkOsXslmCwZI--TkZ6hKi1kXZvNmJRE1rYfffYRFn38zhaqszeETX8HiIvahZhXF5fNumBziYdmLdw8hkuN1A~emU6Xz9g~a1Ixfsq1Qr~guYoOtaw-0rOFxNRS9yMehE-2LCb8c-cAg6z5OdlN4qJDl~ZHgru4d~EHp~BpAK3v7u2Gi-8l1ygVW-1CHVna~fwnbOPN3ANPwh6~~yUit0Cx1f54XiNRn6-nPBQAEAAcAAA== -``` - -Copy/paste this host=@base64-address pairing into your **private** @subscription. - -### Directly jumping - -For example, entering `pinkpaste.i2p` into the *Jump* box (and then submitting) will automatically redirect you to the website **and** insert the @locally-unique-host into @address-book. diff --git a/_i18n/zh-cn/resources/moneropedia/lease-set.md b/_i18n/zh-cn/resources/moneropedia/lease-set.md deleted file mode 100644 index dc1c4a24..00000000 --- a/_i18n/zh-cn/resources/moneropedia/lease-set.md +++ /dev/null @@ -1,23 +0,0 @@ ---- -tags: ["kovri"] -terms: ["LeaseSet", "LeaseSets"] -summary: "Contains all currently authorized Leases for a particular I2P Destination" ---- - -### The Basics - -A Lease-Set contains a set of authorized @leases (and other related information) for a particular @destination. - -### In-depth information - -A Lease-Set contains: - -- all of the currently authorized @leases for a particular @destination -- the public key to which garlic messages can be encrypted (see @garlic-routing) -- the signing public key that can be used to revoke this particular version of the structure - -The Lease-Set is one of the two structures stored in the @network-database (the other being @router-info), and is keyed under the SHA256 of the contained @destination. - -### Notes - -For further details, read @Java-I2P's [LeaseSet](https://geti2p.net/en/docs/how/network-database#leaseSet) diff --git a/_i18n/zh-cn/resources/moneropedia/lease.md b/_i18n/zh-cn/resources/moneropedia/lease.md deleted file mode 100644 index c5a78058..00000000 --- a/_i18n/zh-cn/resources/moneropedia/lease.md +++ /dev/null @@ -1,13 +0,0 @@ ---- -tags: ["kovri"] -terms: ["Lease", "Leases"] -summary: "Authorizes an I2P tunnel to receive messages targeting a destination" ---- - -### The Basics - -A lease defines the authorization for a particular @I2P @tunnel to receive a @messages targeting a @destination. - -### In-depth information - -For further details, read @Java-I2P's [Lease](https://geti2p.net/spec/common-structures#lease) diff --git a/_i18n/zh-cn/resources/moneropedia/message.md b/_i18n/zh-cn/resources/moneropedia/message.md deleted file mode 100644 index 5cce553b..00000000 --- a/_i18n/zh-cn/resources/moneropedia/message.md +++ /dev/null @@ -1,31 +0,0 @@ ---- -tags: ["kovri"] -terms: ["Message", "Messages"] -summary: "The mechanisms in which information travels within I2P" ---- - -### The Basics - -*Messages* (which exist on top of the @transports layer), contain varying types of information that are needed for the network but, most importantly, everything you see, do, send, or receive, will come and go in the form of *messages*. - -There are 2 essential types of *messages* in @I2P: - -- @Tunnel messages -- @I2NP messages - -Essentially: *@tunnel messages* **contain** @I2NP **message fragments** which are then [reassembled](https://geti2p.net/en/docs/tunnels/implementation) at certain points within a @tunnel's path. - -### In-depth information - -@I2NP messages have a close relationship with @tunnel @messages so it is easy to get the term *messages* confused when reading @Java-I2P specifications: - -> -1. First, the tunnel gateway accumulates a number of I2NP messages and preprocesses them into tunnel messages for delivery. -2. Next, that gateway encrypts that preprocessed data, then forwards it to the first hop. -3. That peer, and subsequent tunnel participants, unwrap a layer of the encryption, verifying that it isn't a duplicate, then forward it on to the next peer. -4. Eventually, the tunnel messages arrive at the endpoint where the I2NP messages originally bundled by the gateway are reassembled and forwarded on as requested. - -### Notes - -- @I2NP @messages need to be fragmented because they are variable in size (from 0 to almost 64 KB) and @tunnel @messages are fixed-size (approximately 1 KB). -- For details and specifications, visit the [I2NP spec](https://geti2p.net/spec/i2np) and [Tunnel Message spec](https://geti2p.net/spec/tunnel-message) diff --git a/_i18n/zh-cn/resources/moneropedia/network-database.md b/_i18n/zh-cn/resources/moneropedia/network-database.md deleted file mode 100644 index eb3925cd..00000000 --- a/_i18n/zh-cn/resources/moneropedia/network-database.md +++ /dev/null @@ -1,23 +0,0 @@ ---- -tags: ["kovri"] -terms: ["Network-Database"] -summary: "A distributed database which contains needed router information so the network can stay intact" ---- - -### The Basics - -@network-database is a [distributed database](https://en.wikipedia.org/wiki/Distributed_database) which contains router information that peers must use so the network can stay intact. - -### In-depth information - -From @Java-I2P: - -> -@I2P's @network-database is a specialized distributed database, containing just two types of data - router contact information (@Router-Infos) and @destination contact information (@LeaseSets). Each piece of data is signed by the appropriate party and verified by anyone who uses or stores it. In addition, the data has liveliness information within it, allowing irrelevant entries to be dropped, newer entries to replace older ones, and protection against certain classes of attack. - -> -The @network-database is distributed with a simple technique called "@floodfill", where a subset of all routers, called "@floodfill routers", maintains the distributed database. - -### Notes - -Read [Network-Database](https://geti2p.net/en/docs/how/network-database) for details. diff --git a/_i18n/zh-cn/resources/moneropedia/ntcp.md b/_i18n/zh-cn/resources/moneropedia/ntcp.md deleted file mode 100644 index 69d10a3f..00000000 --- a/_i18n/zh-cn/resources/moneropedia/ntcp.md +++ /dev/null @@ -1,32 +0,0 @@ ---- -tags: ["kovri"] -terms: ["NTCP"] -summary: "NIO-Based TCP (Non-blocking I/O based TCP): one of two Kovri transports" ---- - -### The Basics - -*NIO-Based TCP (Non-blocking I/O based TCP)* is one of two encrypted @transports for @Kovri. - -Similar to @SSU, @NTCP's *primary* purpose is to securely transmit @in-net @I2NP messages through @tunnels but, unlike @SSU, @NTCP functions solely over encrypted [TCP](https://en.wikipedia.org/wiki/Transmission_Control_Protocol). - -### In-depth information - - - Passes along individual @I2NP messages (both Standard and Time Sync) after: - - TCP has been established - - Establishment Sequence has been completed - - Uses the following @encryption: - - 2048-bit [Diffie-Hellman](https://en.wikipedia.org/wiki/Diffie-hellman) - - [AES-256](https://en.wikipedia.org/wiki/Advanced_Encryption_Standard)/[CBC](https://en.wikipedia.org/wiki/Block_cipher_modes_of_operation) - - Establishment Sequence has the following *states*: - - Pre-establishment - - Establishment - - Post-establishment or "Established" - - Uses the following from the @network-database: - - Transport name: NTCP - - Host: IP (IPv4 or IPv6) or host name (shortened IPv6 address (with "::") is allowed) - - Port: 1024 - 65535 - -### Notes - -For further details, read @Java-I2P's [NTCP](https://geti2p.net/en/docs/transport/ntcp) diff --git a/_i18n/zh-cn/resources/moneropedia/reseed.md b/_i18n/zh-cn/resources/moneropedia/reseed.md deleted file mode 100644 index 59727311..00000000 --- a/_i18n/zh-cn/resources/moneropedia/reseed.md +++ /dev/null @@ -1,15 +0,0 @@ ---- -tags: ["kovri"] -terms: ["Reseed"] -summary: "The method of which Kovri uses to bootstrap into the I2P network" ---- - -### The Basics - -When you start @Kovri for the first time (or if it's been offline for a long time), @Kovri will need a list of peers to connect to so it can [bootstrap](https://en.wikipedia.org/wiki/Bootstrap) into the @I2P network. @Kovri gets these peers from a special file stored on a reseed server. On this file are all the various pieces of information @Kovri needs in order to connect with @I2P peers. - -### In-depth information - -@Kovri has a list of [hard-coded](https://en.wikipedia.org/wiki/Hard-coded) reseed servers available to fetch from. These servers securely serve an [SU3](https://geti2p.net/spec/updates#su3) file (signed with a cryptographic @signature) over @clearnet with [HTTPS](https://en.wikipedia.org/wiki/HTTPS). This SU3 file contains information that's used to verify both the integrity of the file and its content. - -Aside from the technical elements needed to verify and process the file, the file's main contents consist of a series of @router-info files which @Kovri and @I2P routers use to locate and communicate with other @I2P peers. These peers are then stored into a @network-database. diff --git a/_i18n/zh-cn/resources/moneropedia/router-info.md b/_i18n/zh-cn/resources/moneropedia/router-info.md deleted file mode 100644 index ad50c13f..00000000 --- a/_i18n/zh-cn/resources/moneropedia/router-info.md +++ /dev/null @@ -1,66 +0,0 @@ ---- -tags: ["kovri"] -terms: ["Router-Info", "Router-infos"] -summary: "A data structure or file which contains an I2P peer's needed network information" ---- - -### The Basics - -@Router-Info is a data structure (periodically written to a [binary file](https://en.wikipedia.org/wiki/Binary_file)) which contains all needed information to locate, identify, and communicate with an @I2P peer. @Router-Info includes IP address, router identity, other misc. technical details; is needed for @network-database and is published to @floodfill routers. - -### In-depth information - -In human-readable form, Router-Info may look like this: - -``` -Identity: [RouterIdentity: -Hash: nYZ5Qe7gQ-~QgfgJVRUG4c0JnVeVqzM~duUX1EGT1ek= -Certificate: [Certificate: type: Key certificate -Crypto type: 0 -Sig type: 7 (EdDSA_SHA512_Ed25519)] -PublicKey: [PublicKey: size: 256] -SigningPublicKey: [SigningPublicKey EdDSA_SHA512_Ed25519: size: 32] -Padding: 96 bytes] -Signature: [Signature EdDSA_SHA512_Ed25519: size: 64] -Published: Sun Oct 09 01:34:59 UTC 2016 -Options (5): - [caps] = [LfR] - [netId] = [2] - [netdb.knownLeaseSets] = [37] - [netdb.knownRouters] = [2435] - [router.version] = [0.9.26] -Addresses (4): -[RouterAddress: -Type: SSU -Cost: 4 -Options (5): - [caps] = [BC] - [host] = [2a01:e35:8b5c:b240:71a2:6750:8d4:47fa] - [key] = [nYZ5Qe7gQ-~QgfgJVRUG4c0JnVeVqzM~duUX1EGT1ek=] - [mtu] = [1472] - [port] = [22244]] -[RouterAddress: -Type: NTCP -Cost: 9 -Options (2): - [host] = [2a01:e35:8b5c:b240:71a2:6750:8d4:47fa] - [port] = [22244]] -[RouterAddress: -Type: SSU -Cost: 6 -Options (4): - [caps] = [BC] - [host] = [88.181.203.36] - [key] = [nYZ5Qe7gQ-~QgfgJVRUG4c0JnVeVqzM~duUX1EGT1ek=] - [port] = [22244]] -[RouterAddress: -Type: NTCP -Cost: 11 -Options (2): - [host] = [88.181.203.36] - [port] = [22244]]] -``` - -### Notes - -For details and specification, visit @Java-I2P [Network Database](https://geti2p.net/en/docs/how/network-database) page. diff --git a/_i18n/zh-cn/resources/moneropedia/ssu.md b/_i18n/zh-cn/resources/moneropedia/ssu.md deleted file mode 100644 index a7b2eb5b..00000000 --- a/_i18n/zh-cn/resources/moneropedia/ssu.md +++ /dev/null @@ -1,24 +0,0 @@ ---- -tags: ["kovri"] -terms: ["SSU"] -summary: "Secure Semi-reliable UDP: one of two Kovri transports" ---- - -### The Basics - -*Secure Semi-reliable UDP* is one of two encrypted @transports for @Kovri. - -Similar to @NTCP, @SSU's *primary* purpose is to securely transmit @in-net @I2NP messages through @tunnels but, unlike @NTCP, @SSU functions solely over encrypted [UDP](https://en.wikipedia.org/wiki/User_Datagram_Protocol). - -### In-depth information - -- Like @NTCP, @SSU is a connection-oriented, point-to-point data transport -- Termed *semi-reliable* because @SSU will repeatedly retransmit *unacknowledged* messages (up to maximum number then dropped) -- @SSU also provides several unique services (in addition to its function as a @transport layer): - - IP detection (local inspection or with [peer testing](https://geti2p.net/en/docs/transport/ssu#peerTesting)) - - [NAT](https://en.wikipedia.org/wiki/Network_address_translation) traversal (using [introducers](https://geti2p.net/en/docs/transport/ssu#introduction)) - - [Firewall](https://en.wikipedia.org/wiki/Firewall_%28computing%29) status and, if implemented, @SSU can notify @NTCP if the external address or firewall status changes - -### Notes - -For further details, read @Java-I2P's [SSU](https://geti2p.net/en/docs/transport/ssu) diff --git a/_i18n/zh-cn/resources/moneropedia/subscription.md b/_i18n/zh-cn/resources/moneropedia/subscription.md deleted file mode 100644 index 78ef1bf4..00000000 --- a/_i18n/zh-cn/resources/moneropedia/subscription.md +++ /dev/null @@ -1,45 +0,0 @@ ---- -tags: ["kovri"] -terms: ["Subscription"] -summary: "A file used by address book which contains I2P hosts paired with I2P destinations" ---- - -### The Basics - -A subscription is a file which contains a list of `.i2p` hosts paired with their respective @destination. Subscriptions are used by the @address-book. - -### In-depth information - -Similar to how a [hosts file](https://en.wikipedia.org/wiki/Hosts_(file)) can map an internet hostname to a specified address, a subscription matches a `.i2p` address to @base64-address by using the following format (no spaces allowed): `host=address` - -More specifically, a subscription pairs a @locally-unique-host to @base64-address. - -Example: - -``` -anonimal.i2p=AQZGLAMpI9Q0l0kmMj1vpJJYK3CjLp~fE3MfvE-e7KMKjI5cPOH6EN8m794uHJ6b09qM8mb9VEv1lVLEov~usVliTSXCSHuRBOCIwIOuDNU0AbVa4BpIx~2sU4TxKhoaA3zQ6VzINoduTdR2IJhPvI5xzezp7dR21CEQGGTbenDslXeQ4iLHFA2~bzp1f7etSl9T2W9RID-KH78sRQmzWnv7dbhNodMbpO6xsf1vENf6bMRzqD5vgHEHZu2aSoNuPyYxDU1eM6--61b2xp9mt1k3ud-5WvPVg89RaU9ugU5cxaHgR927lHMCAEU2Ax~zUb3DbrvgQBOTHnJEx2Fp7pOK~PnP6ylkYKQMfLROosLDXinxOoSKP0UYCh2WgIUPwE7WzJH3PiJVF0~WZ1dZ9mg00c~gzLgmkOxe1NpFRNg6XzoARivNVB5NuWqNxr5WKWMLBGQ9YHvHO1OHhUJTowb9X90BhtHnLK2AHwO6fV-iHWxRJyDabhSMj1kuYpVUBQAEAAcAAA== -``` - -1. `anonimal.i2p` is the @locally-unique-host -2. `=` is the separator -3. Everything that remains is the @base64-address - -### Subscription types - -For @Kovri, there are two types of subscription files: *public* and *private*. - -A *public* subscription: -- is used when bootstrapping to use essential services (IRC, email, Monero, etc.) -- is static and is refreshed every 12 hours from Monero's @address-book server -- allows you to safely share the subscription with everyone as it is publically available (anyone who shares the same public subscription will also be able to resolve the same hostname to the same destination as you) - -A *private* subscription: -- is used exclusively by you and is not shared with others unless you explicitly choose to share the file -- default file is `private_hosts.txt` in your @data-directory - -### Updating a private subscription - -You can use a @jump-service to manually update your private subscription. The updated subscription will then be fed into the @address-book for you to use. - -### Notes -To learn how to subscribe to multiple subscriptions, see the [user-guide](https://gitlab.com/kovri-project/kovri-docs/blob/master/i18n/en/user_guide.md). diff --git a/_i18n/zh-cn/resources/moneropedia/transports.md b/_i18n/zh-cn/resources/moneropedia/transports.md deleted file mode 100644 index 01225e66..00000000 --- a/_i18n/zh-cn/resources/moneropedia/transports.md +++ /dev/null @@ -1,18 +0,0 @@ ---- -tags: ["kovri"] -terms: ["Transports", "Transport"] -summary: "The two encrypted transport layers for Kovri" ---- - -### The Basics - -@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 - -@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 @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) diff --git a/_i18n/zh-cn/resources/moneropedia/tunnel.md b/_i18n/zh-cn/resources/moneropedia/tunnel.md deleted file mode 100644 index 94369ad2..00000000 --- a/_i18n/zh-cn/resources/moneropedia/tunnel.md +++ /dev/null @@ -1,35 +0,0 @@ ---- -tags: ["kovri"] -terms: ["Tunnel", "Tunnels"] -summary: "Uni-directional virtual paths that pass messages through a defined sequence of I2P routers" ---- - -### The Basics - -When you communicate over @I2P (visit an @eepsite / use a @garlic-service), you'll first need to connect to a peer by using @transports and then build virtual *tunnels*. These virtual tunnels are temporary, uni-directional paths that pass information through a defined sequence of @I2P routers to your @destination. Tunnels are built, and then used, with layered @garlic-encryption and are a general-purpose mechanism to transport all @I2NP @messages. - -Each peer builds, at a minimum, *two* uni-directional tunnels: one for **outbound traffic**, and one for **inbound traffic**. These tunnels are classified as either **inbound tunnels** (where @messages come toward the creator of the tunnel) or **outbound tunnels** (where the tunnel creator sends @messages away from the creator of the tunnel). Thus, *four* tunnels are required for a single round-trip @message and reply to your @destination (two for your, two for your destination). - -### In-depth information - -From @Java-I2P: - -> -Within I2P, @messages are passed in one direction through a virtual tunnel of peers, using whatever means are available to pass the @message on to the next hop. Messages arrive at the tunnel's gateway, get bundled up and/or fragmented into fixed-size @tunnel @messages, and are forwarded on to the next hop in the tunnel, which processes and verifies the validity of the @message and sends it on to the next hop, and so on, until it reaches the @tunnel endpoint. That endpoint takes the messages bundled up by the gateway and forwards them as instructed - either to another router, to another tunnel on another router, or locally. - -> -Tunnels all work the same, but can be segmented into two different groups - inbound tunnels and outbound tunnels. The inbound tunnels have an untrusted gateway which passes messages down towards the tunnel creator, which serves as the tunnel endpoint. For outbound tunnels, the tunnel creator serves as the gateway, passing messages out to the remote endpoint. - -> -The tunnel's creator selects exactly which peers will participate in the tunnel, and provides each with the necessary configuration data. They may have any number of hops. It is the intent to make it hard for either participants or third parties to determine the length of a tunnel, or even for colluding participants to determine whether they are a part of the same tunnel at all (barring the situation where colluding peers are next to each other in the tunnel). - -### Notes - -From @Java-I2P: - -> -@I2P is an inherently packet switched network, even with these tunnels, allowing it to take advantage of multiple tunnels running in parallel, increasing resilience and balancing load. Even though the tunnels within I2P bear a resemblance to a circuit switched network, everything within I2P is strictly message based - tunnels are merely accounting tricks to help organize the delivery of messages. No assumptions are made regarding reliability or ordering of messages, and retransmissions are left to higher levels (e.g. I2P's client layer streaming library). - -### Documentation - -For specification and detailed documentation, visit the [Tunnel-Routing](https://geti2p.net/en/docs/how/tunnel-routing) and [Tunnel-Implementation](https://geti2p.net/en/docs/tunnels/implementation) page. diff --git a/_i18n/zh-tw/resources/moneropedia/base32-address.md b/_i18n/zh-tw/resources/moneropedia/base32-address.md deleted file mode 100644 index 9737f7c0..00000000 --- a/_i18n/zh-tw/resources/moneropedia/base32-address.md +++ /dev/null @@ -1,25 +0,0 @@ ---- -tags: ["kovri"] -terms: ["Base32-address", "Base32-addresses"] -summary: "Base32 encoded hash of a Base64 address" ---- - -### The Basics - -A Base32 address is a shortened, encoded version of an @I2P address. The Base32 address is the first part in a `.b32.i2p` hostname. - -Example: - -`i35yftyyb22xhcvghmev46t5knefur5v66qzekkajatwfwhyklvq.b32.i2p` - -where - -`i35yftyyb22xhcvghmev46t5knefur5v66qzekkajatwfwhyklvq` is the Base32 address. - -### In-depth Information - -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. - -### Notes - -**Note: `.b32` is not a sub-domain of `.i2p`** diff --git a/_i18n/zh-tw/resources/moneropedia/base64-address.md b/_i18n/zh-tw/resources/moneropedia/base64-address.md deleted file mode 100644 index 56a0589a..00000000 --- a/_i18n/zh-tw/resources/moneropedia/base64-address.md +++ /dev/null @@ -1,20 +0,0 @@ ---- -tags: ["kovri"] -terms: ["Base64-address", "Base64-addresses"] -summary: "Base64 encoded I2P destination" ---- - -### The Basics - -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: - -``` -AQZGLAMpI9Q0l0kmMj1vpJJYK3CjLp~fE3MfvE-e7KMKjI5cPOH6EN8m794uHJ6b09qM8mb9VEv1lVLEov~usVliTSXCSHuRBOCIwIOuDNU0AbVa4BpIx~2sU4TxKhoaA3zQ6VzINoduTdR2IJhPvI5xzezp7dR21CEQGGTbenDslXeQ4iLHFA2~bzp1f7etSl9T2W9RID-KH78sRQmzWnv7dbhNodMbpO6xsf1vENf6bMRzqD5vgHEHZu2aSoNuPyYxDU1eM6--61b2xp9mt1k3ud-5WvPVg89RaU9ugU5cxaHgR927lHMCAEU2Ax~zUb3DbrvgQBOTHnJEx2Fp7pOK~PnP6ylkYKQMfLROosLDXinxOoSKP0UYCh2WgIUPwE7WzJH3PiJVF0~WZ1dZ9mg00c~gzLgmkOxe1NpFRNg6XzoARivNVB5NuWqNxr5WKWMLBGQ9YHvHO1OHhUJTowb9X90BhtHnLK2AHwO6fV-iHWxRJyDabhSMj1kuYpVUBQAEAAcAAA== -``` - - -### In-depth Information - -See @destination for details behind @base64-address diff --git a/_i18n/zh-tw/resources/moneropedia/data-directory.md b/_i18n/zh-tw/resources/moneropedia/data-directory.md deleted file mode 100644 index abe307f2..00000000 --- a/_i18n/zh-tw/resources/moneropedia/data-directory.md +++ /dev/null @@ -1,20 +0,0 @@ ---- -tags: ["kovri"] -terms: ["Data-Directory"] -summary: "Where essential kovri data for runtime is stored" ---- - -### The Basics - -Depending on your OS, @Kovri currently stores all run-time data in the following directory: - -- Linux/FreeBSD: - - `$HOME/.kovri` - -- OSX: - - `$HOME/Library/Application\ Support/Kovri` - -- Windows: - - `"$APPDATA"\\Kovri` - -This includes all configuration files, @address-book, certificates, and resources. diff --git a/_i18n/zh-tw/resources/moneropedia/eepsite.md b/_i18n/zh-tw/resources/moneropedia/eepsite.md deleted file mode 100644 index efb16e1a..00000000 --- a/_i18n/zh-tw/resources/moneropedia/eepsite.md +++ /dev/null @@ -1,28 +0,0 @@ ---- -tags: ["kovri"] -terms: ["Eepsite", "Hidden-Service", "Garlic-Site", "Garlic-Service"] -summary: "A website or service hosted within the I2P network" ---- - -### The Basics - -Is it [**EEP!** *(in response to the site's content)*](https://en.wikipedia.org/wiki/Onomatopoeia), or **end-to-end protocol**, or something else entirely different? - -While the original definition of eepsite has been lost with time, its use-case remains: an eepsite is a website or service that is hosted within (and only accessible by) the @I2P network. - -### In-depth Information - -Alternate names include: - -1. *Hidden Service* - - because the site/service is *hidden* within the @I2P network and can only be visited within the network -2. *Garlic Site* - - because the website utilizes @I2P's @garlic-routing technology as a means of communicating with a client - - because the service is hosted as a website and not any other type of service -3. *Garlic Service* - - because the service utilizes @I2P's @garlic-routing technology as a means of communicating with a client - - because the service is specific to services like IRC, email, or a Monero peer (but may also include websites) - -### Notes - -To learn how to setup an Eepsite (Hidden Service, Garlic Site, Garlic Service) visit the @Kovri [user-guide](https://gitlab.com/kovri-project/kovri-docs/blob/master/i18n/en/user_guide.md). diff --git a/_i18n/zh-tw/resources/moneropedia/floodfill.md b/_i18n/zh-tw/resources/moneropedia/floodfill.md deleted file mode 100644 index f2cb5f04..00000000 --- a/_i18n/zh-tw/resources/moneropedia/floodfill.md +++ /dev/null @@ -1,13 +0,0 @@ ---- -tags: ["kovri"] -terms: ["Floodfill"] -summary: "An I2P router which maintains a distributed network-database" ---- - -### The Basics - -By actively managing a distributed network-database, a router with *floodfill* capability has the ability to help maintain network stability and resiliancy while also being decentralized and trust-less. - -### In-depth information - -Though floodfill itself is a simple storage system, the technical underpinnings of floodfill as it relates to @network-database and other protocols within @I2P are much more complex. Visit the [Network Database](https://geti2p.net/en/docs/how/network-database) page for details. diff --git a/_i18n/zh-tw/resources/moneropedia/garlic-encryption.md b/_i18n/zh-tw/resources/moneropedia/garlic-encryption.md deleted file mode 100644 index 271d7f0c..00000000 --- a/_i18n/zh-tw/resources/moneropedia/garlic-encryption.md +++ /dev/null @@ -1,23 +0,0 @@ ---- -tags: ["kovri"] -terms: ["Garlic-Encryption", "Layered-Encryption"] -summary: "Layered encryption as implemented in Kovri / I2P" ---- - -### The Basics - -@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 - -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. diff --git a/_i18n/zh-tw/resources/moneropedia/garlic-routing.md b/_i18n/zh-tw/resources/moneropedia/garlic-routing.md deleted file mode 100644 index 6e4865e3..00000000 --- a/_i18n/zh-tw/resources/moneropedia/garlic-routing.md +++ /dev/null @@ -1,43 +0,0 @@ ---- -tags: ["kovri"] -terms: ["Garlic-Routing"] -summary: "Routing technology as implemented in Kovri" ---- - -### 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. - -The @Garlic-Encryption of @Garlic-Routing is similar to the @Layered-Encryption of [Onion Routing](https://en.wikipedia.org/wiki/Onion_routing) and effectively conceals the IP address of the sender and secures information sent from the sender to its @destination (and vice-versa). - -### 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](http://www.freehaven.net/papers.html) (Section 8.1.1) as derived from the term Onion Routing. - -As recent as October of 2016, [#tor-dev](https://oftc.net/WebChat/) has offered insight into the creation of the term *@garlic-routing*: - -[Nick Mathewson](https://en.wikipedia.org/wiki/The_Tor_Project,_Inc): ->[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](https://en.wikipedia.org/wiki/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 was 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 (similar to the @layered-encryption in Onion Routing) -- Bundling multiple @messages together (garlic cloves) -- ElGamal/AES @encryption - -*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 - -- In terms of Onion/Garlic Routing, another way to envision layered @encryption is by replacing the onion/garlic with a [Matryoshka doll](https://en.wikipedia.org/wiki/Matryoshka_doll) - with each outer/inner doll having a lock and public key to the next/previous doll -- For more technical details on Garlic Routing, read the @Java-I2P entry on [Garlic Routing](https://geti2p.net/en/docs/how/garlic-routing) diff --git a/_i18n/zh-tw/resources/moneropedia/i2np.md b/_i18n/zh-tw/resources/moneropedia/i2np.md deleted file mode 100644 index 556f59ee..00000000 --- a/_i18n/zh-tw/resources/moneropedia/i2np.md +++ /dev/null @@ -1,26 +0,0 @@ ---- -tags: ["kovri"] -terms: ["I2NP"] -summary: "The I2P Network Protocol: the mechanism in which I2NP messages are sent over the I2P network" ---- - -### The Basics - -From @Java-I2P: - -> -@I2NP manages the routing and mixing of messages between routers, as well as the selection of what transports to use when communicating with a peer for which there are multiple common transports supported - -### In-depth information - -From @Java-I2P: - -> -@I2NP (@I2P Network Protocol) @messages can be used for one-hop, router-to-router, point-to-point @messages. By @encrypting and wrapping @messages in other @messages, they can be sent in a secure way through multiple hops to the ultimate @destination. @I2NP does not specify nor require any particular @transport layer but does require at least one @transport in use. - -> -Whenever a @destination wants to send a message to to another @destination, it provides its local router with both the @destination structure and the raw bytes of the message to be sent. The router then determines where to send it, delivers it through outbound @tunnels, instructing the end point to pass it along to the appropriate inbound @tunnel, where it is passed along again to that @tunnel's end point and made available to the target for reception. - -### Notes - -Read more about the @I2NP [protocol](https://geti2p.net/en/docs/protocol/i2np) and [specification](https://geti2p.net/spec/i2np). diff --git a/_i18n/zh-tw/resources/moneropedia/i2p.md b/_i18n/zh-tw/resources/moneropedia/i2p.md deleted file mode 100644 index 26ef9c46..00000000 --- a/_i18n/zh-tw/resources/moneropedia/i2p.md +++ /dev/null @@ -1,29 +0,0 @@ ---- -tags: ["kovri"] -terms: ["I2P"] -summary: "The Invisible Internet Project: an anonymizing overlay network" ---- - -### Monero - -For Monero's implementation of @I2P, see @Kovri. For a comparison of @I2P to [Tor](https://torproject.org/), read the [Comparison](https://geti2p.net/en/comparison/tor) page. - -### The Basics - -From @Java-I2P: - ->The I2P network provides strong privacy protections for communication over the Internet. Many activities that would risk your privacy on the public Internet can be conducted anonymously inside I2P. - -### In-depth information - -From @Java-I2P: - ->I2P is an anonymous overlay network - a network within a network. It is intended to protect communication from dragnet surveillance and monitoring by third parties such as ISPs. - ->I2P is used by many people who care about their privacy: activists, oppressed people, journalists and whistleblowers, as well as the average person. - ->No network can be "perfectly anonymous". The continued goal of I2P is to make attacks more and more difficult to mount. Its anonymity will get stronger as the size of the network increases and with ongoing academic review. - -### Notes - -@I2P documentation and specifications are available [here](https://geti2p.net/docs/). diff --git a/_i18n/zh-tw/resources/moneropedia/i2pcontrol.md b/_i18n/zh-tw/resources/moneropedia/i2pcontrol.md deleted file mode 100644 index 5491fc4e..00000000 --- a/_i18n/zh-tw/resources/moneropedia/i2pcontrol.md +++ /dev/null @@ -1,15 +0,0 @@ ---- -tags: ["kovri"] -terms: ["I2PControl"] -summary: "An API inteface for Kovri and Java-I2P that allows simple remote control" ---- - -### The Basics - -@I2Pcontrol is a [JSONRPC2](https://en.wikipedia.org/wiki/JSON-RPC) [API](https://en.wikipedia.org/wiki/Application_programming_interface) for @Kovri and @Java-I2P which allows an @I2PControl client to remote control/monitor a running instance. - -Two available @I2PControl clients are: [qtoopie](https://github.com/EinMByte/qtoopie) (C++ client) and [itoopie](https://github.com/i2p/i2p.itoopie) (Java client). Read `kovri.conf` to configure @I2PControl for @Kovri. - -### In-depth information - -Details and specification available on the [I2PControl](https://geti2p.net/en/docs/api/i2pcontrol) page. diff --git a/_i18n/zh-tw/resources/moneropedia/in-net.md b/_i18n/zh-tw/resources/moneropedia/in-net.md deleted file mode 100644 index 884d40f0..00000000 --- a/_i18n/zh-tw/resources/moneropedia/in-net.md +++ /dev/null @@ -1,13 +0,0 @@ ---- -tags: ["kovri"] -terms: ["In-net"] -summary: "Within the I2P network" ---- - -### The Basics - -**In-net** is a [colloquial](https://en.wikipedia.org/wiki/Colloquial) term of which describes activities, protocols, or functionality that exist *only* within the @I2P network. - -### In-depth information - -Example: *in-net download* would be defined as downloading *only* within @I2P. diff --git a/_i18n/zh-tw/resources/moneropedia/java-i2p.md b/_i18n/zh-tw/resources/moneropedia/java-i2p.md deleted file mode 100644 index ede62818..00000000 --- a/_i18n/zh-tw/resources/moneropedia/java-i2p.md +++ /dev/null @@ -1,13 +0,0 @@ ---- -tags: ["kovri"] -terms: ["Java-I2P"] -summary: "The original implementation of I2P - written in Java" ---- - -### The Basics - -The term "Java I2P" is often used to describe the original @I2P implementation currently most known and used today. There are various other @I2P implementations, including @Kovri; all of which look up to the original Java implementation. - -### Notes - -To download/learn more about the Java implementation, visit their [website](https://geti2p.net/). diff --git a/_i18n/zh-tw/resources/moneropedia/jump-service.md b/_i18n/zh-tw/resources/moneropedia/jump-service.md deleted file mode 100644 index 60619ede..00000000 --- a/_i18n/zh-tw/resources/moneropedia/jump-service.md +++ /dev/null @@ -1,32 +0,0 @@ ---- -tags: ["kovri"] -terms: ["Jump-Service"] -summary: "An I2P website service that adds addresses to your address book" ---- - -### The Basics - -In your @I2P configured web browser, you can use a Jump Service to *jump* to an @I2P address that you don't have in your @address-book. Once you've *jumped* to the address, the address will be saved into your @address-book. - -### In-depth Information - -In an @I2P configured browser, visit: http://stats.i2p/i2p/lookup.html (courtesy of @Java-I2P's lead developer *zzz*) - -Then, you'll have two options: - -1. *Hostname lookup* the address you wish to visit and then manually copy/paste the result -2. *Jump* to the @I2P website by entering the @I2P hostname (**recommended**) - -### Using hostname lookup - -For example, entering `pinkpaste.i2p` into the *Hostname lookup* box (and then submitting) will return: - -``` -pinkpaste.i2p=m-HrPrIAsdxts0WM~P4mE8mt9P7g-QTaBvu7Gc6Nl0UX7Vwck-i~RvOPfK6W~kfdRvwhNTqevkBL2UF5l36We02Aiywu7kB2xOHRkze68h-Tg2ewvRVwokohguCD2G3wwAEz~7FVda2avYDCb9-N6TfuzxKLnmhPMvbNSjGL7ZsD2p-h207R3-2kvuMV9bfu-K~w9NI9XJhIyufvUnFYc2jnTVg8PbaR4UP57cNaOO2YIMPkbr6~yTcIu9B1sUfHK6-N~6virQDOxW4M-62rjnZkLpaCtkOsXslmCwZI--TkZ6hKi1kXZvNmJRE1rYfffYRFn38zhaqszeETX8HiIvahZhXF5fNumBziYdmLdw8hkuN1A~emU6Xz9g~a1Ixfsq1Qr~guYoOtaw-0rOFxNRS9yMehE-2LCb8c-cAg6z5OdlN4qJDl~ZHgru4d~EHp~BpAK3v7u2Gi-8l1ygVW-1CHVna~fwnbOPN3ANPwh6~~yUit0Cx1f54XiNRn6-nPBQAEAAcAAA== -``` - -Copy/paste this host=@base64-address pairing into your **private** @subscription. - -### Directly jumping - -For example, entering `pinkpaste.i2p` into the *Jump* box (and then submitting) will automatically redirect you to the website **and** insert the @locally-unique-host into @address-book. diff --git a/_i18n/zh-tw/resources/moneropedia/lease-set.md b/_i18n/zh-tw/resources/moneropedia/lease-set.md deleted file mode 100644 index dc1c4a24..00000000 --- a/_i18n/zh-tw/resources/moneropedia/lease-set.md +++ /dev/null @@ -1,23 +0,0 @@ ---- -tags: ["kovri"] -terms: ["LeaseSet", "LeaseSets"] -summary: "Contains all currently authorized Leases for a particular I2P Destination" ---- - -### The Basics - -A Lease-Set contains a set of authorized @leases (and other related information) for a particular @destination. - -### In-depth information - -A Lease-Set contains: - -- all of the currently authorized @leases for a particular @destination -- the public key to which garlic messages can be encrypted (see @garlic-routing) -- the signing public key that can be used to revoke this particular version of the structure - -The Lease-Set is one of the two structures stored in the @network-database (the other being @router-info), and is keyed under the SHA256 of the contained @destination. - -### Notes - -For further details, read @Java-I2P's [LeaseSet](https://geti2p.net/en/docs/how/network-database#leaseSet) diff --git a/_i18n/zh-tw/resources/moneropedia/lease.md b/_i18n/zh-tw/resources/moneropedia/lease.md deleted file mode 100644 index c5a78058..00000000 --- a/_i18n/zh-tw/resources/moneropedia/lease.md +++ /dev/null @@ -1,13 +0,0 @@ ---- -tags: ["kovri"] -terms: ["Lease", "Leases"] -summary: "Authorizes an I2P tunnel to receive messages targeting a destination" ---- - -### The Basics - -A lease defines the authorization for a particular @I2P @tunnel to receive a @messages targeting a @destination. - -### In-depth information - -For further details, read @Java-I2P's [Lease](https://geti2p.net/spec/common-structures#lease) diff --git a/_i18n/zh-tw/resources/moneropedia/message.md b/_i18n/zh-tw/resources/moneropedia/message.md deleted file mode 100644 index 5cce553b..00000000 --- a/_i18n/zh-tw/resources/moneropedia/message.md +++ /dev/null @@ -1,31 +0,0 @@ ---- -tags: ["kovri"] -terms: ["Message", "Messages"] -summary: "The mechanisms in which information travels within I2P" ---- - -### The Basics - -*Messages* (which exist on top of the @transports layer), contain varying types of information that are needed for the network but, most importantly, everything you see, do, send, or receive, will come and go in the form of *messages*. - -There are 2 essential types of *messages* in @I2P: - -- @Tunnel messages -- @I2NP messages - -Essentially: *@tunnel messages* **contain** @I2NP **message fragments** which are then [reassembled](https://geti2p.net/en/docs/tunnels/implementation) at certain points within a @tunnel's path. - -### In-depth information - -@I2NP messages have a close relationship with @tunnel @messages so it is easy to get the term *messages* confused when reading @Java-I2P specifications: - -> -1. First, the tunnel gateway accumulates a number of I2NP messages and preprocesses them into tunnel messages for delivery. -2. Next, that gateway encrypts that preprocessed data, then forwards it to the first hop. -3. That peer, and subsequent tunnel participants, unwrap a layer of the encryption, verifying that it isn't a duplicate, then forward it on to the next peer. -4. Eventually, the tunnel messages arrive at the endpoint where the I2NP messages originally bundled by the gateway are reassembled and forwarded on as requested. - -### Notes - -- @I2NP @messages need to be fragmented because they are variable in size (from 0 to almost 64 KB) and @tunnel @messages are fixed-size (approximately 1 KB). -- For details and specifications, visit the [I2NP spec](https://geti2p.net/spec/i2np) and [Tunnel Message spec](https://geti2p.net/spec/tunnel-message) diff --git a/_i18n/zh-tw/resources/moneropedia/network-database.md b/_i18n/zh-tw/resources/moneropedia/network-database.md deleted file mode 100644 index eb3925cd..00000000 --- a/_i18n/zh-tw/resources/moneropedia/network-database.md +++ /dev/null @@ -1,23 +0,0 @@ ---- -tags: ["kovri"] -terms: ["Network-Database"] -summary: "A distributed database which contains needed router information so the network can stay intact" ---- - -### The Basics - -@network-database is a [distributed database](https://en.wikipedia.org/wiki/Distributed_database) which contains router information that peers must use so the network can stay intact. - -### In-depth information - -From @Java-I2P: - -> -@I2P's @network-database is a specialized distributed database, containing just two types of data - router contact information (@Router-Infos) and @destination contact information (@LeaseSets). Each piece of data is signed by the appropriate party and verified by anyone who uses or stores it. In addition, the data has liveliness information within it, allowing irrelevant entries to be dropped, newer entries to replace older ones, and protection against certain classes of attack. - -> -The @network-database is distributed with a simple technique called "@floodfill", where a subset of all routers, called "@floodfill routers", maintains the distributed database. - -### Notes - -Read [Network-Database](https://geti2p.net/en/docs/how/network-database) for details. diff --git a/_i18n/zh-tw/resources/moneropedia/ntcp.md b/_i18n/zh-tw/resources/moneropedia/ntcp.md deleted file mode 100644 index 69d10a3f..00000000 --- a/_i18n/zh-tw/resources/moneropedia/ntcp.md +++ /dev/null @@ -1,32 +0,0 @@ ---- -tags: ["kovri"] -terms: ["NTCP"] -summary: "NIO-Based TCP (Non-blocking I/O based TCP): one of two Kovri transports" ---- - -### The Basics - -*NIO-Based TCP (Non-blocking I/O based TCP)* is one of two encrypted @transports for @Kovri. - -Similar to @SSU, @NTCP's *primary* purpose is to securely transmit @in-net @I2NP messages through @tunnels but, unlike @SSU, @NTCP functions solely over encrypted [TCP](https://en.wikipedia.org/wiki/Transmission_Control_Protocol). - -### In-depth information - - - Passes along individual @I2NP messages (both Standard and Time Sync) after: - - TCP has been established - - Establishment Sequence has been completed - - Uses the following @encryption: - - 2048-bit [Diffie-Hellman](https://en.wikipedia.org/wiki/Diffie-hellman) - - [AES-256](https://en.wikipedia.org/wiki/Advanced_Encryption_Standard)/[CBC](https://en.wikipedia.org/wiki/Block_cipher_modes_of_operation) - - Establishment Sequence has the following *states*: - - Pre-establishment - - Establishment - - Post-establishment or "Established" - - Uses the following from the @network-database: - - Transport name: NTCP - - Host: IP (IPv4 or IPv6) or host name (shortened IPv6 address (with "::") is allowed) - - Port: 1024 - 65535 - -### Notes - -For further details, read @Java-I2P's [NTCP](https://geti2p.net/en/docs/transport/ntcp) diff --git a/_i18n/zh-tw/resources/moneropedia/reseed.md b/_i18n/zh-tw/resources/moneropedia/reseed.md deleted file mode 100644 index 59727311..00000000 --- a/_i18n/zh-tw/resources/moneropedia/reseed.md +++ /dev/null @@ -1,15 +0,0 @@ ---- -tags: ["kovri"] -terms: ["Reseed"] -summary: "The method of which Kovri uses to bootstrap into the I2P network" ---- - -### The Basics - -When you start @Kovri for the first time (or if it's been offline for a long time), @Kovri will need a list of peers to connect to so it can [bootstrap](https://en.wikipedia.org/wiki/Bootstrap) into the @I2P network. @Kovri gets these peers from a special file stored on a reseed server. On this file are all the various pieces of information @Kovri needs in order to connect with @I2P peers. - -### In-depth information - -@Kovri has a list of [hard-coded](https://en.wikipedia.org/wiki/Hard-coded) reseed servers available to fetch from. These servers securely serve an [SU3](https://geti2p.net/spec/updates#su3) file (signed with a cryptographic @signature) over @clearnet with [HTTPS](https://en.wikipedia.org/wiki/HTTPS). This SU3 file contains information that's used to verify both the integrity of the file and its content. - -Aside from the technical elements needed to verify and process the file, the file's main contents consist of a series of @router-info files which @Kovri and @I2P routers use to locate and communicate with other @I2P peers. These peers are then stored into a @network-database. diff --git a/_i18n/zh-tw/resources/moneropedia/router-info.md b/_i18n/zh-tw/resources/moneropedia/router-info.md deleted file mode 100644 index ad50c13f..00000000 --- a/_i18n/zh-tw/resources/moneropedia/router-info.md +++ /dev/null @@ -1,66 +0,0 @@ ---- -tags: ["kovri"] -terms: ["Router-Info", "Router-infos"] -summary: "A data structure or file which contains an I2P peer's needed network information" ---- - -### The Basics - -@Router-Info is a data structure (periodically written to a [binary file](https://en.wikipedia.org/wiki/Binary_file)) which contains all needed information to locate, identify, and communicate with an @I2P peer. @Router-Info includes IP address, router identity, other misc. technical details; is needed for @network-database and is published to @floodfill routers. - -### In-depth information - -In human-readable form, Router-Info may look like this: - -``` -Identity: [RouterIdentity: -Hash: nYZ5Qe7gQ-~QgfgJVRUG4c0JnVeVqzM~duUX1EGT1ek= -Certificate: [Certificate: type: Key certificate -Crypto type: 0 -Sig type: 7 (EdDSA_SHA512_Ed25519)] -PublicKey: [PublicKey: size: 256] -SigningPublicKey: [SigningPublicKey EdDSA_SHA512_Ed25519: size: 32] -Padding: 96 bytes] -Signature: [Signature EdDSA_SHA512_Ed25519: size: 64] -Published: Sun Oct 09 01:34:59 UTC 2016 -Options (5): - [caps] = [LfR] - [netId] = [2] - [netdb.knownLeaseSets] = [37] - [netdb.knownRouters] = [2435] - [router.version] = [0.9.26] -Addresses (4): -[RouterAddress: -Type: SSU -Cost: 4 -Options (5): - [caps] = [BC] - [host] = [2a01:e35:8b5c:b240:71a2:6750:8d4:47fa] - [key] = [nYZ5Qe7gQ-~QgfgJVRUG4c0JnVeVqzM~duUX1EGT1ek=] - [mtu] = [1472] - [port] = [22244]] -[RouterAddress: -Type: NTCP -Cost: 9 -Options (2): - [host] = [2a01:e35:8b5c:b240:71a2:6750:8d4:47fa] - [port] = [22244]] -[RouterAddress: -Type: SSU -Cost: 6 -Options (4): - [caps] = [BC] - [host] = [88.181.203.36] - [key] = [nYZ5Qe7gQ-~QgfgJVRUG4c0JnVeVqzM~duUX1EGT1ek=] - [port] = [22244]] -[RouterAddress: -Type: NTCP -Cost: 11 -Options (2): - [host] = [88.181.203.36] - [port] = [22244]]] -``` - -### Notes - -For details and specification, visit @Java-I2P [Network Database](https://geti2p.net/en/docs/how/network-database) page. diff --git a/_i18n/zh-tw/resources/moneropedia/ssu.md b/_i18n/zh-tw/resources/moneropedia/ssu.md deleted file mode 100644 index a7b2eb5b..00000000 --- a/_i18n/zh-tw/resources/moneropedia/ssu.md +++ /dev/null @@ -1,24 +0,0 @@ ---- -tags: ["kovri"] -terms: ["SSU"] -summary: "Secure Semi-reliable UDP: one of two Kovri transports" ---- - -### The Basics - -*Secure Semi-reliable UDP* is one of two encrypted @transports for @Kovri. - -Similar to @NTCP, @SSU's *primary* purpose is to securely transmit @in-net @I2NP messages through @tunnels but, unlike @NTCP, @SSU functions solely over encrypted [UDP](https://en.wikipedia.org/wiki/User_Datagram_Protocol). - -### In-depth information - -- Like @NTCP, @SSU is a connection-oriented, point-to-point data transport -- Termed *semi-reliable* because @SSU will repeatedly retransmit *unacknowledged* messages (up to maximum number then dropped) -- @SSU also provides several unique services (in addition to its function as a @transport layer): - - IP detection (local inspection or with [peer testing](https://geti2p.net/en/docs/transport/ssu#peerTesting)) - - [NAT](https://en.wikipedia.org/wiki/Network_address_translation) traversal (using [introducers](https://geti2p.net/en/docs/transport/ssu#introduction)) - - [Firewall](https://en.wikipedia.org/wiki/Firewall_%28computing%29) status and, if implemented, @SSU can notify @NTCP if the external address or firewall status changes - -### Notes - -For further details, read @Java-I2P's [SSU](https://geti2p.net/en/docs/transport/ssu) diff --git a/_i18n/zh-tw/resources/moneropedia/subscription.md b/_i18n/zh-tw/resources/moneropedia/subscription.md deleted file mode 100644 index 78ef1bf4..00000000 --- a/_i18n/zh-tw/resources/moneropedia/subscription.md +++ /dev/null @@ -1,45 +0,0 @@ ---- -tags: ["kovri"] -terms: ["Subscription"] -summary: "A file used by address book which contains I2P hosts paired with I2P destinations" ---- - -### The Basics - -A subscription is a file which contains a list of `.i2p` hosts paired with their respective @destination. Subscriptions are used by the @address-book. - -### In-depth information - -Similar to how a [hosts file](https://en.wikipedia.org/wiki/Hosts_(file)) can map an internet hostname to a specified address, a subscription matches a `.i2p` address to @base64-address by using the following format (no spaces allowed): `host=address` - -More specifically, a subscription pairs a @locally-unique-host to @base64-address. - -Example: - -``` -anonimal.i2p=AQZGLAMpI9Q0l0kmMj1vpJJYK3CjLp~fE3MfvE-e7KMKjI5cPOH6EN8m794uHJ6b09qM8mb9VEv1lVLEov~usVliTSXCSHuRBOCIwIOuDNU0AbVa4BpIx~2sU4TxKhoaA3zQ6VzINoduTdR2IJhPvI5xzezp7dR21CEQGGTbenDslXeQ4iLHFA2~bzp1f7etSl9T2W9RID-KH78sRQmzWnv7dbhNodMbpO6xsf1vENf6bMRzqD5vgHEHZu2aSoNuPyYxDU1eM6--61b2xp9mt1k3ud-5WvPVg89RaU9ugU5cxaHgR927lHMCAEU2Ax~zUb3DbrvgQBOTHnJEx2Fp7pOK~PnP6ylkYKQMfLROosLDXinxOoSKP0UYCh2WgIUPwE7WzJH3PiJVF0~WZ1dZ9mg00c~gzLgmkOxe1NpFRNg6XzoARivNVB5NuWqNxr5WKWMLBGQ9YHvHO1OHhUJTowb9X90BhtHnLK2AHwO6fV-iHWxRJyDabhSMj1kuYpVUBQAEAAcAAA== -``` - -1. `anonimal.i2p` is the @locally-unique-host -2. `=` is the separator -3. Everything that remains is the @base64-address - -### Subscription types - -For @Kovri, there are two types of subscription files: *public* and *private*. - -A *public* subscription: -- is used when bootstrapping to use essential services (IRC, email, Monero, etc.) -- is static and is refreshed every 12 hours from Monero's @address-book server -- allows you to safely share the subscription with everyone as it is publically available (anyone who shares the same public subscription will also be able to resolve the same hostname to the same destination as you) - -A *private* subscription: -- is used exclusively by you and is not shared with others unless you explicitly choose to share the file -- default file is `private_hosts.txt` in your @data-directory - -### Updating a private subscription - -You can use a @jump-service to manually update your private subscription. The updated subscription will then be fed into the @address-book for you to use. - -### Notes -To learn how to subscribe to multiple subscriptions, see the [user-guide](https://gitlab.com/kovri-project/kovri-docs/blob/master/i18n/en/user_guide.md). diff --git a/_i18n/zh-tw/resources/moneropedia/transports.md b/_i18n/zh-tw/resources/moneropedia/transports.md deleted file mode 100644 index 01225e66..00000000 --- a/_i18n/zh-tw/resources/moneropedia/transports.md +++ /dev/null @@ -1,18 +0,0 @@ ---- -tags: ["kovri"] -terms: ["Transports", "Transport"] -summary: "The two encrypted transport layers for Kovri" ---- - -### The Basics - -@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 - -@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 @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) diff --git a/_i18n/zh-tw/resources/moneropedia/tunnel.md b/_i18n/zh-tw/resources/moneropedia/tunnel.md deleted file mode 100644 index 94369ad2..00000000 --- a/_i18n/zh-tw/resources/moneropedia/tunnel.md +++ /dev/null @@ -1,35 +0,0 @@ ---- -tags: ["kovri"] -terms: ["Tunnel", "Tunnels"] -summary: "Uni-directional virtual paths that pass messages through a defined sequence of I2P routers" ---- - -### The Basics - -When you communicate over @I2P (visit an @eepsite / use a @garlic-service), you'll first need to connect to a peer by using @transports and then build virtual *tunnels*. These virtual tunnels are temporary, uni-directional paths that pass information through a defined sequence of @I2P routers to your @destination. Tunnels are built, and then used, with layered @garlic-encryption and are a general-purpose mechanism to transport all @I2NP @messages. - -Each peer builds, at a minimum, *two* uni-directional tunnels: one for **outbound traffic**, and one for **inbound traffic**. These tunnels are classified as either **inbound tunnels** (where @messages come toward the creator of the tunnel) or **outbound tunnels** (where the tunnel creator sends @messages away from the creator of the tunnel). Thus, *four* tunnels are required for a single round-trip @message and reply to your @destination (two for your, two for your destination). - -### In-depth information - -From @Java-I2P: - -> -Within I2P, @messages are passed in one direction through a virtual tunnel of peers, using whatever means are available to pass the @message on to the next hop. Messages arrive at the tunnel's gateway, get bundled up and/or fragmented into fixed-size @tunnel @messages, and are forwarded on to the next hop in the tunnel, which processes and verifies the validity of the @message and sends it on to the next hop, and so on, until it reaches the @tunnel endpoint. That endpoint takes the messages bundled up by the gateway and forwards them as instructed - either to another router, to another tunnel on another router, or locally. - -> -Tunnels all work the same, but can be segmented into two different groups - inbound tunnels and outbound tunnels. The inbound tunnels have an untrusted gateway which passes messages down towards the tunnel creator, which serves as the tunnel endpoint. For outbound tunnels, the tunnel creator serves as the gateway, passing messages out to the remote endpoint. - -> -The tunnel's creator selects exactly which peers will participate in the tunnel, and provides each with the necessary configuration data. They may have any number of hops. It is the intent to make it hard for either participants or third parties to determine the length of a tunnel, or even for colluding participants to determine whether they are a part of the same tunnel at all (barring the situation where colluding peers are next to each other in the tunnel). - -### Notes - -From @Java-I2P: - -> -@I2P is an inherently packet switched network, even with these tunnels, allowing it to take advantage of multiple tunnels running in parallel, increasing resilience and balancing load. Even though the tunnels within I2P bear a resemblance to a circuit switched network, everything within I2P is strictly message based - tunnels are merely accounting tricks to help organize the delivery of messages. No assumptions are made regarding reliability or ordering of messages, and retransmissions are left to higher levels (e.g. I2P's client layer streaming library). - -### Documentation - -For specification and detailed documentation, visit the [Tunnel-Routing](https://geti2p.net/en/docs/how/tunnel-routing) and [Tunnel-Implementation](https://geti2p.net/en/docs/tunnels/implementation) page. diff --git a/resources/moneropedia/base32-address.md b/resources/moneropedia/base32-address.md deleted file mode 100644 index b3e14358..00000000 --- a/resources/moneropedia/base32-address.md +++ /dev/null @@ -1,10 +0,0 @@ ---- -layout: moneropedia -title: titles.moneropedia -entry: moneropedia.entries.base32-address ---- - -@moneropedia_article - -{% t global.lang_tag %} -{% tf resources/moneropedia/base32-address.md %} diff --git a/resources/moneropedia/base64-address.md b/resources/moneropedia/base64-address.md deleted file mode 100644 index 38405f93..00000000 --- a/resources/moneropedia/base64-address.md +++ /dev/null @@ -1,10 +0,0 @@ ---- -layout: moneropedia -title: titles.moneropedia -entry: moneropedia.entries.base64-address ---- - -@moneropedia_article - -{% t global.lang_tag %} -{% tf resources/moneropedia/base64-address.md %} diff --git a/resources/moneropedia/data-directory.md b/resources/moneropedia/data-directory.md deleted file mode 100644 index f45c8161..00000000 --- a/resources/moneropedia/data-directory.md +++ /dev/null @@ -1,10 +0,0 @@ ---- -layout: moneropedia -title: titles.moneropedia -entry: moneropedia.entries.data-directory ---- - -@moneropedia_article - -{% t global.lang_tag %} -{% tf resources/moneropedia/data-directory.md %} diff --git a/resources/moneropedia/eepsite.md b/resources/moneropedia/eepsite.md deleted file mode 100644 index 5cfa374c..00000000 --- a/resources/moneropedia/eepsite.md +++ /dev/null @@ -1,10 +0,0 @@ ---- -layout: moneropedia -title: titles.moneropedia -entry: moneropedia.entries.eepsite ---- - -@moneropedia_article - -{% t global.lang_tag %} -{% tf resources/moneropedia/eepsite.md %} diff --git a/resources/moneropedia/floodfill.md b/resources/moneropedia/floodfill.md deleted file mode 100644 index 00a8ea28..00000000 --- a/resources/moneropedia/floodfill.md +++ /dev/null @@ -1,10 +0,0 @@ ---- -layout: moneropedia -title: titles.moneropedia -entry: moneropedia.entries.floodfill ---- - -@moneropedia_article - -{% t global.lang_tag %} -{% tf resources/moneropedia/floodfill.md %} diff --git a/resources/moneropedia/garlic-encryption.md b/resources/moneropedia/garlic-encryption.md deleted file mode 100644 index 689f6b25..00000000 --- a/resources/moneropedia/garlic-encryption.md +++ /dev/null @@ -1,10 +0,0 @@ ---- -layout: moneropedia -title: titles.moneropedia -entry: moneropedia.entries.garlic-encryption ---- - -@moneropedia_article - -{% t global.lang_tag %} -{% tf resources/moneropedia/garlic-encryption.md %} diff --git a/resources/moneropedia/garlic-routing.md b/resources/moneropedia/garlic-routing.md deleted file mode 100644 index 846cce42..00000000 --- a/resources/moneropedia/garlic-routing.md +++ /dev/null @@ -1,10 +0,0 @@ ---- -layout: moneropedia -title: titles.moneropedia -entry: moneropedia.entries.garlic-routing ---- - -@moneropedia_article - -{% t global.lang_tag %} -{% tf resources/moneropedia/garlic-routing.md %} diff --git a/resources/moneropedia/i2np.md b/resources/moneropedia/i2np.md deleted file mode 100644 index 18242629..00000000 --- a/resources/moneropedia/i2np.md +++ /dev/null @@ -1,10 +0,0 @@ ---- -layout: moneropedia -title: titles.moneropedia -entry: moneropedia.entries.i2np ---- - -@moneropedia_article - -{% t global.lang_tag %} -{% tf resources/moneropedia/i2np.md %} diff --git a/resources/moneropedia/i2p.md b/resources/moneropedia/i2p.md deleted file mode 100644 index 801d1db8..00000000 --- a/resources/moneropedia/i2p.md +++ /dev/null @@ -1,10 +0,0 @@ ---- -layout: moneropedia -title: titles.moneropedia -entry: moneropedia.entries.i2p ---- - -@moneropedia_article - -{% t global.lang_tag %} -{% tf resources/moneropedia/i2p.md %} diff --git a/resources/moneropedia/i2pcontrol.md b/resources/moneropedia/i2pcontrol.md deleted file mode 100644 index 4027ad52..00000000 --- a/resources/moneropedia/i2pcontrol.md +++ /dev/null @@ -1,10 +0,0 @@ ---- -layout: moneropedia -title: titles.moneropedia -entry: moneropedia.entries.i2pcontrol ---- - -@moneropedia_article - -{% t global.lang_tag %} -{% tf resources/moneropedia/i2pcontrol.md %} diff --git a/resources/moneropedia/in-net.md b/resources/moneropedia/in-net.md deleted file mode 100644 index 35c07d2e..00000000 --- a/resources/moneropedia/in-net.md +++ /dev/null @@ -1,10 +0,0 @@ ---- -layout: moneropedia -title: titles.moneropedia -entry: moneropedia.entries.in-net ---- - -@moneropedia_article - -{% t global.lang_tag %} -{% tf resources/moneropedia/in-net.md %} diff --git a/resources/moneropedia/java-i2p.md b/resources/moneropedia/java-i2p.md deleted file mode 100644 index 2cd3c73d..00000000 --- a/resources/moneropedia/java-i2p.md +++ /dev/null @@ -1,10 +0,0 @@ ---- -layout: moneropedia -title: titles.moneropedia -entry: moneropedia.entries.java-i2p ---- - -@moneropedia_article - -{% t global.lang_tag %} -{% tf resources/moneropedia/java-i2p.md %} diff --git a/resources/moneropedia/jump-service.md b/resources/moneropedia/jump-service.md deleted file mode 100644 index ea8d8263..00000000 --- a/resources/moneropedia/jump-service.md +++ /dev/null @@ -1,10 +0,0 @@ ---- -layout: moneropedia -title: titles.moneropedia -entry: moneropedia.entries.jump-service ---- - -@moneropedia_article - -{% t global.lang_tag %} -{% tf resources/moneropedia/jump-service.md %} diff --git a/resources/moneropedia/lease-set.md b/resources/moneropedia/lease-set.md deleted file mode 100644 index f63660e7..00000000 --- a/resources/moneropedia/lease-set.md +++ /dev/null @@ -1,10 +0,0 @@ ---- -layout: moneropedia -title: titles.moneropedia -entry: moneropedia.entries.lease-set ---- - -@moneropedia_article - -{% t global.lang_tag %} -{% tf resources/moneropedia/lease-set.md %} diff --git a/resources/moneropedia/lease.md b/resources/moneropedia/lease.md deleted file mode 100644 index 303b8fee..00000000 --- a/resources/moneropedia/lease.md +++ /dev/null @@ -1,10 +0,0 @@ ---- -layout: moneropedia -title: titles.moneropedia -entry: moneropedia.entries.lease ---- - -@moneropedia_article - -{% t global.lang_tag %} -{% tf resources/moneropedia/lease.md %} diff --git a/resources/moneropedia/message.md b/resources/moneropedia/message.md deleted file mode 100644 index b4c20dd6..00000000 --- a/resources/moneropedia/message.md +++ /dev/null @@ -1,10 +0,0 @@ ---- -layout: moneropedia -title: titles.moneropedia -entry: moneropedia.entries.message ---- - -@moneropedia_article - -{% t global.lang_tag %} -{% tf resources/moneropedia/message.md %} diff --git a/resources/moneropedia/network-database.md b/resources/moneropedia/network-database.md deleted file mode 100644 index 23cbd262..00000000 --- a/resources/moneropedia/network-database.md +++ /dev/null @@ -1,10 +0,0 @@ ---- -layout: moneropedia -title: titles.moneropedia -entry: moneropedia.entries.network-database ---- - -@moneropedia_article - -{% t global.lang_tag %} -{% tf resources/moneropedia/network-database.md %} diff --git a/resources/moneropedia/ntcp.md b/resources/moneropedia/ntcp.md deleted file mode 100644 index 347532f6..00000000 --- a/resources/moneropedia/ntcp.md +++ /dev/null @@ -1,10 +0,0 @@ ---- -layout: moneropedia -title: titles.moneropedia -entry: moneropedia.entries.ntcp ---- - -@moneropedia_article - -{% t global.lang_tag %} -{% tf resources/moneropedia/ntcp.md %} diff --git a/resources/moneropedia/reseed.md b/resources/moneropedia/reseed.md deleted file mode 100644 index 0ca5cf6e..00000000 --- a/resources/moneropedia/reseed.md +++ /dev/null @@ -1,10 +0,0 @@ ---- -layout: moneropedia -title: titles.moneropedia -entry: moneropedia.entries.reseed ---- - -@moneropedia_article - -{% t global.lang_tag %} -{% tf resources/moneropedia/reseed.md %} diff --git a/resources/moneropedia/router-info.md b/resources/moneropedia/router-info.md deleted file mode 100644 index f836210c..00000000 --- a/resources/moneropedia/router-info.md +++ /dev/null @@ -1,10 +0,0 @@ ---- -layout: moneropedia -title: titles.moneropedia -entry: moneropedia.entries.router-info ---- - -@moneropedia_article - -{% t global.lang_tag %} -{% tf resources/moneropedia/router-info.md %} diff --git a/resources/moneropedia/ssu.md b/resources/moneropedia/ssu.md deleted file mode 100644 index 80c48a4c..00000000 --- a/resources/moneropedia/ssu.md +++ /dev/null @@ -1,10 +0,0 @@ ---- -layout: moneropedia -title: titles.moneropedia -entry: moneropedia.entries.ssu ---- - -@moneropedia_article - -{% t global.lang_tag %} -{% tf resources/moneropedia/ssu.md %} diff --git a/resources/moneropedia/subscription.md b/resources/moneropedia/subscription.md deleted file mode 100644 index 10610703..00000000 --- a/resources/moneropedia/subscription.md +++ /dev/null @@ -1,10 +0,0 @@ ---- -layout: moneropedia -title: titles.moneropedia -entry: moneropedia.entries.subscription ---- - -@moneropedia_article - -{% t global.lang_tag %} -{% tf resources/moneropedia/subscription.md %} diff --git a/resources/moneropedia/transports.md b/resources/moneropedia/transports.md deleted file mode 100644 index 04aecf6f..00000000 --- a/resources/moneropedia/transports.md +++ /dev/null @@ -1,10 +0,0 @@ ---- -layout: moneropedia -title: titles.moneropedia -entry: moneropedia.entries.transports ---- - -@moneropedia_article - -{% t global.lang_tag %} -{% tf resources/moneropedia/transports.md %} diff --git a/resources/moneropedia/tunnel.md b/resources/moneropedia/tunnel.md deleted file mode 100644 index 839a5e8c..00000000 --- a/resources/moneropedia/tunnel.md +++ /dev/null @@ -1,10 +0,0 @@ ---- -layout: moneropedia -title: titles.moneropedia -entry: moneropedia.entries.tunnel ---- - -@moneropedia_article - -{% t global.lang_tag %} -{% tf resources/moneropedia/tunnel.md %}