mirror of
https://github.com/monero-project/monero-site.git
synced 2025-01-11 05:15:28 +00:00
Remove links to deleted Moneropedia entries from other resources
This commit is contained in:
parent
594e614c42
commit
5f4e58e67c
52 changed files with 147 additions and 147 deletions
|
@ -18,5 +18,5 @@ A Canonically-unique host is defined by remote authoritative sources; usually th
|
|||
|
||||
### Notes
|
||||
|
||||
- Monero primarily uses @canonically-unique-host resolution while @I2P only uses @locally-unique-host resolution.
|
||||
- @I2P's and @Kovri's self-assigned top-level domain is currently `.i2p` and @Kovri intends to only process/use the `.i2p` [top-level domain](https://en.wikipedia.org/wiki/Top_level_domain)
|
||||
- Monero primarily uses @canonically-unique-host resolution while I2P only uses @locally-unique-host resolution.
|
||||
- I2P's and @Kovri's self-assigned top-level domain is currently `.i2p` and @Kovri intends to only process/use the `.i2p` [top-level domain](https://en.wikipedia.org/wiki/Top_level_domain)
|
||||
|
|
|
@ -25,8 +25,8 @@ Since a traditional [VPN](https://en.wikipedia.org/wiki/VPN) cannot save you fro
|
|||
|
||||
These technologies protect you from clearnet by building an anonymous network **over** clearnet to keep your transmissions both encrypted **and** anonymous.
|
||||
|
||||
Here is an accurate, [interactive diagram](https://www.eff.org/pages/tor-and-https) provided by the [EFF](https://www.eff.org/) which describes *clearnet* as it relates to **Tor**. The concept also (somewhat) applies to @Kovri and @I2P in terms of anonymity with the exception that:
|
||||
Here is an accurate, [interactive diagram](https://www.eff.org/pages/tor-and-https) provided by the [EFF](https://www.eff.org/) which describes *clearnet* as it relates to **Tor**. The concept also (somewhat) applies to @Kovri and I2P in terms of anonymity with the exception that:
|
||||
|
||||
- @Kovri does not use exit nodes when connecting to an @eepsite
|
||||
- Your traffic never need to leave the @I2P network
|
||||
- You do not need HTTPS to use @Kovri (with the exception of @reseed)
|
||||
- @Kovri does not use exit nodes when connecting to an eepsite
|
||||
- Your traffic never need to leave the I2P network
|
||||
- You do not need HTTPS to use @Kovri (with the exception of reseed)
|
||||
|
|
|
@ -27,8 +27,8 @@ The purpose of encryption is to ensure that only somebody who is authorized to a
|
|||
@Kovri implements various types of encryption in *at least* 4 essential capacities:
|
||||
|
||||
- @Reseed for bootstrapping
|
||||
- @Garlic-routing: three layers of encryption (@garlic-encryption) are used to verify the secure delivery of @messages to the recipient/peer/@destination
|
||||
- @Tunnel encryption: garlic messages are passed through a @tunnel and encrypted by the @tunnel gateway to the @tunnel endpoint
|
||||
- @Transport layer encryption prevents the ability to decrypt @messages at the [media layer](https://en.wikipedia.org/wiki/OSI_model)
|
||||
- @Garlic-routing: three layers of encryption (@garlic-encryption) are used to verify the secure delivery of messages to the recipient/peer/destination
|
||||
- @Tunnel encryption: garlic messages are passed through a tunnel and encrypted by the tunnel gateway to the tunnel endpoint
|
||||
- @Transport layer encryption prevents the ability to decrypt messages at the [media layer](https://en.wikipedia.org/wiki/OSI_model)
|
||||
|
||||
For details on the types of encryption and cryptographic @signatures used in @Kovri and @I2P, visit @Java-I2P's [Cryptography](https://geti2p.net/spec/cryptography)
|
||||
For details on the types of encryption and cryptographic @signatures used in @Kovri and I2P, visit @Java-I2P's [Cryptography](https://geti2p.net/spec/cryptography)
|
||||
|
|
|
@ -13,9 +13,9 @@ A locally-unique host is a [FQDN](https://en.wikipedia.org/wiki/FQDN) defined by
|
|||
|
||||
You have the option to share your interpretation of how the host is resolved (e.g., `localhost` always resolves to `127.0.0.1`) but the resolution is not canonically enforced (e.g., someone else can map `localhost` to any arbitrary IP address).
|
||||
|
||||
Hosts in a public subscription can be considered @canonically-unique-host's within the @I2P network but, ultimately, you are free to re-define them as you wish.
|
||||
Hosts in a public subscription can be considered @canonically-unique-host's within the I2P network but, ultimately, you are free to re-define them as you wish.
|
||||
|
||||
### Notes
|
||||
|
||||
- Monero primarily uses @canonically-unique-host resolution while @I2P only uses @locally-unique-host resolution.
|
||||
- @I2P's and @Kovri's assigned top-level domain is currently `.i2p` and @Kovri intends to only process/use the `.i2p` [top-level domain](https://en.wikipedia.org/wiki/Top_level_domain)
|
||||
- Monero primarily uses @canonically-unique-host resolution while I2P only uses @locally-unique-host resolution.
|
||||
- I2P's and @Kovri's assigned top-level domain is currently `.i2p` and @Kovri intends to only process/use the `.i2p` [top-level domain](https://en.wikipedia.org/wiki/Top_level_domain)
|
||||
|
|
|
@ -19,4 +19,4 @@ Ein kanonisch einzigartiger Host wird durch rechnerferne, maßgebende Quellen de
|
|||
### Anmerkungen
|
||||
|
||||
- Monero nutzt primär die Auflösung des kanonisch einzigartigen Hosts, während I2P ausschließlich die Auflösung des @Lokal-einzigartigen-Hosts verwendet.
|
||||
- Die an I2P und @Kovri zugewiesene Top-Level-Domain ist derzeit `.i2p`; @Kovri beabsichtigt, einzig die `.i2p`-[Top-Level-Domain](https://de.wikipedia.org/wiki/Top-Level-Domain) zu nutzen und zu verarbeiten.
|
||||
- Die an I2P und @Kovri zugewiesene Top-Level-Domain ist derzeit `.i2p`; @Kovri beabsichtigt, einzig die `.i2p`-[Top-Level-Domain](https://de.wikipedia.org/wiki/Top-Level-Domain) zu nutzen und zu verarbeiten.
|
||||
|
|
|
@ -13,9 +13,9 @@ A locally-unique host is a [FQDN](https://en.wikipedia.org/wiki/FQDN) defined by
|
|||
|
||||
You have the option to share your interpretation of how the host is resolved (e.g., `localhost` always resolves to `127.0.0.1`) but the resolution is not canonically enforced (e.g., someone else can map `localhost` to any arbitrary IP address).
|
||||
|
||||
Hosts in a public subscription can be considered @canonically-unique-host's within the @I2P network but, ultimately, you are free to re-define them as you wish.
|
||||
Hosts in a public subscription can be considered @canonically-unique-host's within the I2P network but, ultimately, you are free to re-define them as you wish.
|
||||
|
||||
### Notes
|
||||
|
||||
- Monero primarily uses @canonically-unique-host resolution while @I2P only uses @locally-unique-host resolution.
|
||||
- @I2P's and @Kovri's assigned top-level domain is currently `.i2p` and @Kovri intends to only process/use the `.i2p` [top-level domain](https://en.wikipedia.org/wiki/Top_level_domain)
|
||||
- Monero primarily uses @canonically-unique-host resolution while I2P only uses @locally-unique-host resolution.
|
||||
- I2P's and @Kovri's assigned top-level domain is currently `.i2p` and @Kovri intends to only process/use the `.i2p` [top-level domain](https://en.wikipedia.org/wiki/Top_level_domain)
|
||||
|
|
|
@ -18,5 +18,5 @@ A Canonically-unique host is defined by remote authoritative sources; usually th
|
|||
|
||||
### Notes
|
||||
|
||||
- Monero primarily uses @canonically-unique-host resolution while @I2P only uses @locally-unique-host resolution.
|
||||
- @I2P's and @Kovri's self-assigned top-level domain is currently `.i2p` and @Kovri intends to only process/use the `.i2p` [top-level domain](https://en.wikipedia.org/wiki/Top_level_domain)
|
||||
- Monero primarily uses @canonically-unique-host resolution while I2P only uses @locally-unique-host resolution.
|
||||
- I2P's and @Kovri's self-assigned top-level domain is currently `.i2p` and @Kovri intends to only process/use the `.i2p` [top-level domain](https://en.wikipedia.org/wiki/Top_level_domain)
|
||||
|
|
|
@ -25,8 +25,8 @@ Since a traditional [VPN](https://en.wikipedia.org/wiki/VPN) cannot save you fro
|
|||
|
||||
These technologies protect you from clearnet by building an anonymous network **over** clearnet to keep your transmissions both encrypted **and** anonymous.
|
||||
|
||||
Here is an accurate, [interactive diagram](https://www.eff.org/pages/tor-and-https) provided by the [EFF](https://www.eff.org/) which describes *clearnet* as it relates to **Tor**. The concept also (somewhat) applies to @Kovri and @I2P in terms of anonymity with the exception that:
|
||||
Here is an accurate, [interactive diagram](https://www.eff.org/pages/tor-and-https) provided by the [EFF](https://www.eff.org/) which describes *clearnet* as it relates to **Tor**. The concept also (somewhat) applies to @Kovri and I2P in terms of anonymity with the exception that:
|
||||
|
||||
- @Kovri does not use exit nodes when connecting to an @eepsite
|
||||
- Your traffic never need to leave the @I2P network
|
||||
- You do not need HTTPS to use @Kovri (with the exception of @reseed)
|
||||
- @Kovri does not use exit nodes when connecting to an eepsite
|
||||
- Your traffic never need to leave the I2P network
|
||||
- You do not need HTTPS to use @Kovri (with the exception of reseed)
|
||||
|
|
|
@ -27,8 +27,8 @@ The purpose of encryption is to ensure that only somebody who is authorized to a
|
|||
@Kovri implements various types of encryption in *at least* 4 essential capacities:
|
||||
|
||||
- @Reseed for bootstrapping
|
||||
- @Garlic-routing: three layers of encryption (@garlic-encryption) are used to verify the secure delivery of @messages to the recipient/peer/@destination
|
||||
- @Tunnel encryption: garlic messages are passed through a @tunnel and encrypted by the @tunnel gateway to the @tunnel endpoint
|
||||
- @Transport layer encryption prevents the ability to decrypt @messages at the [media layer](https://en.wikipedia.org/wiki/OSI_model)
|
||||
- @Garlic-routing: three layers of encryption (@garlic-encryption) are used to verify the secure delivery of messages to the recipient/peer/destination
|
||||
- @Tunnel encryption: garlic messages are passed through a tunnel and encrypted by the tunnel gateway to the tunnel endpoint
|
||||
- @Transport layer encryption prevents the ability to decrypt messages at the [media layer](https://en.wikipedia.org/wiki/OSI_model)
|
||||
|
||||
For details on the types of encryption and cryptographic @signatures used in @Kovri and @I2P, visit @Java-I2P's [Cryptography](https://geti2p.net/spec/cryptography)
|
||||
For details on the types of encryption and cryptographic @signatures used in @Kovri and I2P, visit @Java-I2P's [Cryptography](https://geti2p.net/spec/cryptography)
|
||||
|
|
|
@ -13,9 +13,9 @@ A locally-unique host is a [FQDN](https://en.wikipedia.org/wiki/FQDN) defined by
|
|||
|
||||
You have the option to share your interpretation of how the host is resolved (e.g., `localhost` always resolves to `127.0.0.1`) but the resolution is not canonically enforced (e.g., someone else can map `localhost` to any arbitrary IP address).
|
||||
|
||||
Hosts in a public subscription can be considered @canonically-unique-host's within the @I2P network but, ultimately, you are free to re-define them as you wish.
|
||||
Hosts in a public subscription can be considered @canonically-unique-host's within the I2P network but, ultimately, you are free to re-define them as you wish.
|
||||
|
||||
### Notes
|
||||
|
||||
- Monero primarily uses @canonically-unique-host resolution while @I2P only uses @locally-unique-host resolution.
|
||||
- @I2P's and @Kovri's assigned top-level domain is currently `.i2p` and @Kovri intends to only process/use the `.i2p` [top-level domain](https://en.wikipedia.org/wiki/Top_level_domain)
|
||||
- Monero primarily uses @canonically-unique-host resolution while I2P only uses @locally-unique-host resolution.
|
||||
- I2P's and @Kovri's assigned top-level domain is currently `.i2p` and @Kovri intends to only process/use the `.i2p` [top-level domain](https://en.wikipedia.org/wiki/Top_level_domain)
|
||||
|
|
|
@ -18,5 +18,5 @@ A Canonically-unique host is defined by remote authoritative sources; usually th
|
|||
|
||||
### Notes
|
||||
|
||||
- Monero primarily uses @canonically-unique-host resolution while @I2P only uses @locally-unique-host resolution.
|
||||
- @I2P's and @Kovri's self-assigned top-level domain is currently `.i2p` and @Kovri intends to only process/use the `.i2p` [top-level domain](https://en.wikipedia.org/wiki/Top_level_domain)
|
||||
- Monero primarily uses @canonically-unique-host resolution while I2P only uses @locally-unique-host resolution.
|
||||
- I2P's and @Kovri's self-assigned top-level domain is currently `.i2p` and @Kovri intends to only process/use the `.i2p` [top-level domain](https://en.wikipedia.org/wiki/Top_level_domain)
|
||||
|
|
|
@ -25,8 +25,8 @@ Since a traditional [VPN](https://en.wikipedia.org/wiki/VPN) cannot save you fro
|
|||
|
||||
These technologies protect you from clearnet by building an anonymous network **over** clearnet to keep your transmissions both encrypted **and** anonymous.
|
||||
|
||||
Here is an accurate, [interactive diagram](https://www.eff.org/pages/tor-and-https) provided by the [EFF](https://www.eff.org/) which describes *clearnet* as it relates to **Tor**. The concept also (somewhat) applies to @Kovri and @I2P in terms of anonymity with the exception that:
|
||||
Here is an accurate, [interactive diagram](https://www.eff.org/pages/tor-and-https) provided by the [EFF](https://www.eff.org/) which describes *clearnet* as it relates to **Tor**. The concept also (somewhat) applies to @Kovri and I2P in terms of anonymity with the exception that:
|
||||
|
||||
- @Kovri does not use exit nodes when connecting to an @eepsite
|
||||
- Your traffic never need to leave the @I2P network
|
||||
- You do not need HTTPS to use @Kovri (with the exception of @reseed)
|
||||
- @Kovri does not use exit nodes when connecting to an eepsite
|
||||
- Your traffic never need to leave the I2P network
|
||||
- You do not need HTTPS to use @Kovri (with the exception of reseed)
|
||||
|
|
|
@ -27,8 +27,8 @@ The purpose of encryption is to ensure that only somebody who is authorized to a
|
|||
@Kovri implements various types of encryption in *at least* 4 essential capacities:
|
||||
|
||||
- @Reseed for bootstrapping
|
||||
- @Garlic-routing: three layers of encryption (@garlic-encryption) are used to verify the secure delivery of @messages to the recipient/peer/@destination
|
||||
- @Tunnel encryption: garlic messages are passed through a @tunnel and encrypted by the @tunnel gateway to the @tunnel endpoint
|
||||
- @Transport layer encryption prevents the ability to decrypt @messages at the [media layer](https://en.wikipedia.org/wiki/OSI_model)
|
||||
- @Garlic-routing: three layers of encryption (@garlic-encryption) are used to verify the secure delivery of messages to the recipient/peer/destination
|
||||
- @Tunnel encryption: garlic messages are passed through a tunnel and encrypted by the tunnel gateway to the tunnel endpoint
|
||||
- @Transport layer encryption prevents the ability to decrypt messages at the [media layer](https://en.wikipedia.org/wiki/OSI_model)
|
||||
|
||||
For details on the types of encryption and cryptographic @signatures used in @Kovri and @I2P, visit @Java-I2P's [Cryptography](https://geti2p.net/spec/cryptography)
|
||||
For details on the types of encryption and cryptographic @signatures used in @Kovri and I2P, visit @Java-I2P's [Cryptography](https://geti2p.net/spec/cryptography)
|
||||
|
|
|
@ -13,9 +13,9 @@ A locally-unique host is a [FQDN](https://en.wikipedia.org/wiki/FQDN) defined by
|
|||
|
||||
You have the option to share your interpretation of how the host is resolved (e.g., `localhost` always resolves to `127.0.0.1`) but the resolution is not canonically enforced (e.g., someone else can map `localhost` to any arbitrary IP address).
|
||||
|
||||
Hosts in a public subscription can be considered @canonically-unique-host's within the @I2P network but, ultimately, you are free to re-define them as you wish.
|
||||
Hosts in a public subscription can be considered @canonically-unique-host's within the I2P network but, ultimately, you are free to re-define them as you wish.
|
||||
|
||||
### Notes
|
||||
|
||||
- Monero primarily uses @canonically-unique-host resolution while @I2P only uses @locally-unique-host resolution.
|
||||
- @I2P's and @Kovri's assigned top-level domain is currently `.i2p` and @Kovri intends to only process/use the `.i2p` [top-level domain](https://en.wikipedia.org/wiki/Top_level_domain)
|
||||
- Monero primarily uses @canonically-unique-host resolution while I2P only uses @locally-unique-host resolution.
|
||||
- I2P's and @Kovri's assigned top-level domain is currently `.i2p` and @Kovri intends to only process/use the `.i2p` [top-level domain](https://en.wikipedia.org/wiki/Top_level_domain)
|
||||
|
|
|
@ -18,5 +18,5 @@ Un hôte canonique unique est défini par des sources autoritaires distantes, co
|
|||
|
||||
### Remarques
|
||||
|
||||
- Monero utilise en premier lieu la résolution de @hôte-canonique-unique alors que @I2P utilise uniquement la résolution d'@hôte-unique-localement.
|
||||
- le domaine de premier niveau auto-attribué de @I2P et @Kovri est actuellement `.i2p` et @Kovri se destine à n'utiliser et ne traiter que le [domaine de premier niveau](https://fr.wikipedia.org/wiki/Top_level_domain) `.i2p`.
|
||||
- Monero utilise en premier lieu la résolution de @hôte-canonique-unique alors que I2P utilise uniquement la résolution d'@hôte-unique-localement.
|
||||
- le domaine de premier niveau auto-attribué de I2P et @Kovri est actuellement `.i2p` et @Kovri se destine à n'utiliser et ne traiter que le [domaine de premier niveau](https://fr.wikipedia.org/wiki/Top_level_domain) `.i2p`.
|
||||
|
|
|
@ -20,13 +20,13 @@ et même si vous utilisez [HTTPS](https://fr.wikipedia.org/wiki/HyperText_Transf
|
|||
Comme un [VPN](https://fr.wikipedia.org/wiki/R%C3%A9seau_priv%C3%A9_virtuel) traditionnel ne peut pas vous épargner du réseau en clair (comme vous utilisez toujours le réseau en clair (bien que vous soyez mieux mandaté que sans un VPN)), vous devriez utiliser une *surcouche réseau anonyme* pour éviter d'utiliser le réseau en clair directement :
|
||||
|
||||
- @Kovri
|
||||
- @I2P-Java
|
||||
- I2P-Java
|
||||
- [Tor](https://torproject.org/)
|
||||
|
||||
Ces technologies vous protègent du réseau en clair en construisant un réseau anonyme **par dessus** le réseau en clair pour garder vos transmissions à la fois chiffrées **et** anonymes.
|
||||
|
||||
Voici un [diagramme interactif](https://www.eff.org/pages/tor-and-https) précis fournit par l'[EFF](https://www.eff.org/) qui décrit comment **Tor** se relie au *réseau en clair*. Le principe est également applicable (en partie) à @Kovri et @I2P en termes d'anonymat, à l'exception des points suivants :
|
||||
Voici un [diagramme interactif](https://www.eff.org/pages/tor-and-https) précis fournit par l'[EFF](https://www.eff.org/) qui décrit comment **Tor** se relie au *réseau en clair*. Le principe est également applicable (en partie) à @Kovri et I2P en termes d'anonymat, à l'exception des points suivants :
|
||||
|
||||
- @Kovri n'utilise pas de nœud de sortie lors d'une connexion à un @site-eep
|
||||
- Votre trafic ne quite jamais le réseau @I2P
|
||||
- Votre trafic ne quite jamais le réseau I2P
|
||||
- Vous n'avez pas besoin de HTTPS pour utiliser @Kovri (à l'exception du @réensemencement)
|
||||
|
|
|
@ -27,8 +27,8 @@ La sécurité d'un système de chiffrement doit reposer sur le secret de la clé
|
|||
@Kovri implémente différents types de chiffrements pour *au moins* 4 capacités essentielles :
|
||||
|
||||
- @réensemencement pour amorce
|
||||
- @Routage-en-ail : trois niveau de chiffrement (@chiffrement-en-ail) sont utilisé pour vérifier la distribution sécurisée des @messages au destinataire ou homologue de @destination
|
||||
- Chiffrement de @Tunnel : les messages en ail sont envoyés à travers un @tunnel et chiffrés par la passerelle de ce @tunnel vers le point de terminaison du @tunnel
|
||||
- Une couche de @Transport chiffrée empêche la capacité à déchiffrer un @messages sur la [couche liaison](https://fr.wikipedia.org/wiki/Mod%C3%A8le_OSI)
|
||||
- @Routage-en-ail : trois niveau de chiffrement (@chiffrement-en-ail) sont utilisé pour vérifier la distribution sécurisée des messages au destinataire ou homologue de destination
|
||||
- Chiffrement de @Tunnel : les messages en ail sont envoyés à travers un tunnel et chiffrés par la passerelle de ce tunnel vers le point de terminaison du tunnel
|
||||
- Une couche de @Transport chiffrée empêche la capacité à déchiffrer un messages sur la [couche liaison](https://fr.wikipedia.org/wiki/Mod%C3%A8le_OSI)
|
||||
|
||||
Pour plus de détails sur les types de chiffrement et les @signatures cryptographiques utilisez dans @Kovri et @I2P, consultez la page [Cryptographie](https://geti2p.net/spec/cryptography) d'@I2P-Java.
|
||||
Pour plus de détails sur les types de chiffrement et les @signatures cryptographiques utilisez dans @Kovri et I2P, consultez la page [Cryptographie](https://geti2p.net/spec/cryptography) d'I2P-Java.
|
||||
|
|
|
@ -13,9 +13,9 @@ Un hôte unique localement est un [FQDN](https://fr.wikipedia.org/wiki/FQDN) que
|
|||
|
||||
Vous avez la possibilité de partager votre interprétation du mécanisme de résolution d'un hôte (p.ex. `localhost` est toujours résolu en `127.0.0.1`) mais la résolution n'est pas appliquée de manière canonique (p.ex. quelqu'un d'autre pourrait faire correspondre `localhost` à une adresse IP arbitraire).
|
||||
|
||||
Les hôtes des souscriptions publiques peuvent être considérés comme des @hôtes-canoniques-uniques au sein du réseau @I2P, mais finalement vous êtes libre de les redéfinir selon vos désirs.
|
||||
Les hôtes des souscriptions publiques peuvent être considérés comme des @hôtes-canoniques-uniques au sein du réseau I2P, mais finalement vous êtes libre de les redéfinir selon vos désirs.
|
||||
|
||||
### Remarques
|
||||
|
||||
- Monero utilise principalement la résolution d'@hôtes-canoniques-uniques alors que @I2P utilise uniquement la résolution d'@hôte-unique-localement.
|
||||
- Le domaine de premier niveau actuel d'@I2P et @Kovri est `.i2p` et @Kovri se destine à traiter / utiliser uniquement le [domaine de premier niveau](https://fr.wikipedia.org/wiki/Domaine_de_premier_niveau) `.i2p`.
|
||||
- Monero utilise principalement la résolution d'@hôtes-canoniques-uniques alors que I2P utilise uniquement la résolution d'@hôte-unique-localement.
|
||||
- Le domaine de premier niveau actuel d'I2P et @Kovri est `.i2p` et @Kovri se destine à traiter / utiliser uniquement le [domaine de premier niveau](https://fr.wikipedia.org/wiki/Domaine_de_premier_niveau) `.i2p`.
|
||||
|
|
|
@ -18,5 +18,5 @@ A Canonically-unique host is defined by remote authoritative sources; usually th
|
|||
|
||||
### Notes
|
||||
|
||||
- Monero primarily uses @canonically-unique-host resolution while @I2P only uses @locally-unique-host resolution.
|
||||
- @I2P's and @Kovri's self-assigned top-level domain is currently `.i2p` and @Kovri intends to only process/use the `.i2p` [top-level domain](https://en.wikipedia.org/wiki/Top_level_domain)
|
||||
- Monero primarily uses @canonically-unique-host resolution while I2P only uses @locally-unique-host resolution.
|
||||
- I2P's and @Kovri's self-assigned top-level domain is currently `.i2p` and @Kovri intends to only process/use the `.i2p` [top-level domain](https://en.wikipedia.org/wiki/Top_level_domain)
|
||||
|
|
|
@ -25,8 +25,8 @@ Since a traditional [VPN](https://en.wikipedia.org/wiki/VPN) cannot save you fro
|
|||
|
||||
These technologies protect you from clearnet by building an anonymous network **over** clearnet to keep your transmissions both encrypted **and** anonymous.
|
||||
|
||||
Here is an accurate, [interactive diagram](https://www.eff.org/pages/tor-and-https) provided by the [EFF](https://www.eff.org/) which describes *clearnet* as it relates to **Tor**. The concept also (somewhat) applies to @Kovri and @I2P in terms of anonymity with the exception that:
|
||||
Here is an accurate, [interactive diagram](https://www.eff.org/pages/tor-and-https) provided by the [EFF](https://www.eff.org/) which describes *clearnet* as it relates to **Tor**. The concept also (somewhat) applies to @Kovri and I2P in terms of anonymity with the exception that:
|
||||
|
||||
- @Kovri does not use exit nodes when connecting to an @eepsite
|
||||
- Your traffic never need to leave the @I2P network
|
||||
- You do not need HTTPS to use @Kovri (with the exception of @reseed)
|
||||
- @Kovri does not use exit nodes when connecting to an eepsite
|
||||
- Your traffic never need to leave the I2P network
|
||||
- You do not need HTTPS to use @Kovri (with the exception of reseed)
|
||||
|
|
|
@ -27,8 +27,8 @@ The purpose of encryption is to ensure that only somebody who is authorized to a
|
|||
@Kovri implements various types of encryption in *at least* 4 essential capacities:
|
||||
|
||||
- @Reseed for bootstrapping
|
||||
- @Garlic-routing: three layers of encryption (@garlic-encryption) are used to verify the secure delivery of @messages to the recipient/peer/@destination
|
||||
- @Tunnel encryption: garlic messages are passed through a @tunnel and encrypted by the @tunnel gateway to the @tunnel endpoint
|
||||
- @Transport layer encryption prevents the ability to decrypt @messages at the [media layer](https://en.wikipedia.org/wiki/OSI_model)
|
||||
- @Garlic-routing: three layers of encryption (@garlic-encryption) are used to verify the secure delivery of messages to the recipient/peer/destination
|
||||
- @Tunnel encryption: garlic messages are passed through a tunnel and encrypted by the tunnel gateway to the tunnel endpoint
|
||||
- @Transport layer encryption prevents the ability to decrypt messages at the [media layer](https://en.wikipedia.org/wiki/OSI_model)
|
||||
|
||||
For details on the types of encryption and cryptographic @signatures used in @Kovri and @I2P, visit @Java-I2P's [Cryptography](https://geti2p.net/spec/cryptography)
|
||||
For details on the types of encryption and cryptographic @signatures used in @Kovri and I2P, visit @Java-I2P's [Cryptography](https://geti2p.net/spec/cryptography)
|
||||
|
|
|
@ -13,9 +13,9 @@ A locally-unique host is a [FQDN](https://en.wikipedia.org/wiki/FQDN) defined by
|
|||
|
||||
You have the option to share your interpretation of how the host is resolved (e.g., `localhost` always resolves to `127.0.0.1`) but the resolution is not canonically enforced (e.g., someone else can map `localhost` to any arbitrary IP address).
|
||||
|
||||
Hosts in a public subscription can be considered @canonically-unique-host's within the @I2P network but, ultimately, you are free to re-define them as you wish.
|
||||
Hosts in a public subscription can be considered @canonically-unique-host's within the I2P network but, ultimately, you are free to re-define them as you wish.
|
||||
|
||||
### Notes
|
||||
|
||||
- Monero primarily uses @canonically-unique-host resolution while @I2P only uses @locally-unique-host resolution.
|
||||
- @I2P's and @Kovri's assigned top-level domain is currently `.i2p` and @Kovri intends to only process/use the `.i2p` [top-level domain](https://en.wikipedia.org/wiki/Top_level_domain)
|
||||
- Monero primarily uses @canonically-unique-host resolution while I2P only uses @locally-unique-host resolution.
|
||||
- I2P's and @Kovri's assigned top-level domain is currently `.i2p` and @Kovri intends to only process/use the `.i2p` [top-level domain](https://en.wikipedia.org/wiki/Top_level_domain)
|
||||
|
|
|
@ -18,5 +18,5 @@ A Canonically-unique host is defined by remote authoritative sources; usually th
|
|||
|
||||
### Notes
|
||||
|
||||
- Monero primarily uses @canonically-unique-host resolution while @I2P only uses @locally-unique-host resolution.
|
||||
- @I2P's and @Kovri's self-assigned top-level domain is currently `.i2p` and @Kovri intends to only process/use the `.i2p` [top-level domain](https://en.wikipedia.org/wiki/Top_level_domain)
|
||||
- Monero primarily uses @canonically-unique-host resolution while I2P only uses @locally-unique-host resolution.
|
||||
- I2P's and @Kovri's self-assigned top-level domain is currently `.i2p` and @Kovri intends to only process/use the `.i2p` [top-level domain](https://en.wikipedia.org/wiki/Top_level_domain)
|
||||
|
|
|
@ -25,8 +25,8 @@ Since a traditional [VPN](https://en.wikipedia.org/wiki/VPN) cannot save you fro
|
|||
|
||||
These technologies protect you from clearnet by building an anonymous network **over** clearnet to keep your transmissions both encrypted **and** anonymous.
|
||||
|
||||
Here is an accurate, [interactive diagram](https://www.eff.org/pages/tor-and-https) provided by the [EFF](https://www.eff.org/) which describes *clearnet* as it relates to **Tor**. The concept also (somewhat) applies to @Kovri and @I2P in terms of anonymity with the exception that:
|
||||
Here is an accurate, [interactive diagram](https://www.eff.org/pages/tor-and-https) provided by the [EFF](https://www.eff.org/) which describes *clearnet* as it relates to **Tor**. The concept also (somewhat) applies to @Kovri and I2P in terms of anonymity with the exception that:
|
||||
|
||||
- @Kovri does not use exit nodes when connecting to an @eepsite
|
||||
- Your traffic never need to leave the @I2P network
|
||||
- You do not need HTTPS to use @Kovri (with the exception of @reseed)
|
||||
- @Kovri does not use exit nodes when connecting to an eepsite
|
||||
- Your traffic never need to leave the I2P network
|
||||
- You do not need HTTPS to use @Kovri (with the exception of reseed)
|
||||
|
|
|
@ -27,8 +27,8 @@ The purpose of encryption is to ensure that only somebody who is authorized to a
|
|||
@Kovri implements various types of encryption in *at least* 4 essential capacities:
|
||||
|
||||
- @Reseed for bootstrapping
|
||||
- @Garlic-routing: three layers of encryption (@garlic-encryption) are used to verify the secure delivery of @messages to the recipient/peer/@destination
|
||||
- @Tunnel encryption: garlic messages are passed through a @tunnel and encrypted by the @tunnel gateway to the @tunnel endpoint
|
||||
- @Transport layer encryption prevents the ability to decrypt @messages at the [media layer](https://en.wikipedia.org/wiki/OSI_model)
|
||||
- @Garlic-routing: three layers of encryption (@garlic-encryption) are used to verify the secure delivery of messages to the recipient/peer/destination
|
||||
- @Tunnel encryption: garlic messages are passed through a tunnel and encrypted by the tunnel gateway to the tunnel endpoint
|
||||
- @Transport layer encryption prevents the ability to decrypt messages at the [media layer](https://en.wikipedia.org/wiki/OSI_model)
|
||||
|
||||
For details on the types of encryption and cryptographic @signatures used in @Kovri and @I2P, visit @Java-I2P's [Cryptography](https://geti2p.net/spec/cryptography)
|
||||
For details on the types of encryption and cryptographic @signatures used in @Kovri and I2P, visit @Java-I2P's [Cryptography](https://geti2p.net/spec/cryptography)
|
||||
|
|
|
@ -13,9 +13,9 @@ A locally-unique host is a [FQDN](https://en.wikipedia.org/wiki/FQDN) defined by
|
|||
|
||||
You have the option to share your interpretation of how the host is resolved (e.g., `localhost` always resolves to `127.0.0.1`) but the resolution is not canonically enforced (e.g., someone else can map `localhost` to any arbitrary IP address).
|
||||
|
||||
Hosts in a public subscription can be considered @canonically-unique-host's within the @I2P network but, ultimately, you are free to re-define them as you wish.
|
||||
Hosts in a public subscription can be considered @canonically-unique-host's within the I2P network but, ultimately, you are free to re-define them as you wish.
|
||||
|
||||
### Notes
|
||||
|
||||
- Monero primarily uses @canonically-unique-host resolution while @I2P only uses @locally-unique-host resolution.
|
||||
- @I2P's and @Kovri's assigned top-level domain is currently `.i2p` and @Kovri intends to only process/use the `.i2p` [top-level domain](https://en.wikipedia.org/wiki/Top_level_domain)
|
||||
- Monero primarily uses @canonically-unique-host resolution while I2P only uses @locally-unique-host resolution.
|
||||
- I2P's and @Kovri's assigned top-level domain is currently `.i2p` and @Kovri intends to only process/use the `.i2p` [top-level domain](https://en.wikipedia.org/wiki/Top_level_domain)
|
||||
|
|
|
@ -18,5 +18,5 @@ Zasadniczy unikalny host jest definiowany przez zdalne autorytatywne źródła,
|
|||
|
||||
### Adnotacje
|
||||
|
||||
- Monero głównie używa zasadniczego unikalnego hosta, podczas gdy @I2P korzysta jedynie z @lokalnego-unikalnego-hosta.
|
||||
- Monero głównie używa zasadniczego unikalnego hosta, podczas gdy I2P korzysta jedynie z @lokalnego-unikalnego-hosta.
|
||||
- Własną przypisaną domeną najwyższego poziomu sieci I2P i Kovri jest obecnie `.i2p`, a Kovri planuje używać jedynie [domeny najwyższego poziomu] `.i2p`(https://en.wikipedia.org/wiki/Top_level_domain).
|
||||
|
|
|
@ -25,8 +25,8 @@ Ponieważ tradycyjna [VPN](https://en.wikipedia.org/wiki/VPN) nie uchroni cię o
|
|||
|
||||
Powyższe technologie chronią przed clearnetem poprzez tworzenie anonimowej sieci **ponad** clearnetem, aby twoje transmisje były zaszyfrowane **i** anonimowe.
|
||||
|
||||
Tutaj znajdziesz dokładny, [interaktywny diagram](https://www.eff.org/pages/tor-and-https) stworzony przez [EFF](https://www.eff.org/), który opisuje *clearnet* w porównaniu z siecią **Tor**. Pojęcie to odnosi się po części do sieci @Kovri i @I2P pod względem anonimowości, z poniższymi różnicami:
|
||||
Tutaj znajdziesz dokładny, [interaktywny diagram](https://www.eff.org/pages/tor-and-https) stworzony przez [EFF](https://www.eff.org/), który opisuje *clearnet* w porównaniu z siecią **Tor**. Pojęcie to odnosi się po części do sieci @Kovri i I2P pod względem anonimowości, z poniższymi różnicami:
|
||||
|
||||
- @Kovri nie korzysta z węzłów wyjściowych przy połączeniu z @eepsite
|
||||
- @Kovri nie korzysta z węzłów wyjściowych przy połączeniu z eepsite
|
||||
- twoje obciążenie nigdy nie musi opuszczać sieć I2P
|
||||
- nie potrzebujesz HTTPS, aby używać Kovri (za wyjątkiem @reseeda).
|
||||
- nie potrzebujesz HTTPS, aby używać Kovri (za wyjątkiem reseeda).
|
||||
|
|
|
@ -32,4 +32,4 @@ Celem szyfrowania jest zapewnienie, że jedynie osoba upoważniona do dostępu d
|
|||
- szyfrowanie @tunelowe: wiadomości "czosnkowe" są przesyłane przez @tunel i szyfrowane przez furtkę @tunelu aż do punktu końcowego @tunelu
|
||||
- szyfrowanie warstwy @transportowej zapobiega rozszyfrowaniu wiadomości w [warstwie medialnej](https://en.wikipedia.org/wiki/OSI_model)
|
||||
|
||||
Aby dowiedzieć się więcej na temat rodzajów szyfrowania oraz @podpisów kryptograficznych używanych w @Kovri i @I2P, odwiedź stronę o [kryptografii] @Java-I2P (https://geti2p.net/spec/cryptography).
|
||||
Aby dowiedzieć się więcej na temat rodzajów szyfrowania oraz @podpisów kryptograficznych używanych w @Kovri i I2P, odwiedź stronę o [kryptografii] @Java-I2P (https://geti2p.net/spec/cryptography).
|
||||
|
|
|
@ -13,7 +13,7 @@ Lokalnie unikalny host jest [Pełną, Jendoznaczną Nazwą Domenową](https://en
|
|||
|
||||
Możesz podzielić się swoją interpretacją tego, jak ustalany jest host, np. `localhost` zawsze jest ustalony jako `127.0.0.1`, ale to ustalenie nie jest ogólnie egzekwowane (np. ktoś może przypisać `localhost` do dowolnego adresu IP).
|
||||
|
||||
Hosty w publicznej subskrypcji mogą być uważane za @zasadnicze-unikalne-hosty wewnątrz sieci @I2P, jednak ostatecznie to od ciebie zależy, jak je zdefiniujesz.
|
||||
Hosty w publicznej subskrypcji mogą być uważane za @zasadnicze-unikalne-hosty wewnątrz sieci I2P, jednak ostatecznie to od ciebie zależy, jak je zdefiniujesz.
|
||||
|
||||
### Adnotacje
|
||||
|
||||
|
|
|
@ -18,5 +18,5 @@ A Canonically-unique host is defined by remote authoritative sources; usually th
|
|||
|
||||
### Notes
|
||||
|
||||
- Monero primarily uses @canonically-unique-host resolution while @I2P only uses @locally-unique-host resolution.
|
||||
- @I2P's and @Kovri's self-assigned top-level domain is currently `.i2p` and @Kovri intends to only process/use the `.i2p` [top-level domain](https://en.wikipedia.org/wiki/Top_level_domain)
|
||||
- Monero primarily uses @canonically-unique-host resolution while I2P only uses @locally-unique-host resolution.
|
||||
- I2P's and @Kovri's self-assigned top-level domain is currently `.i2p` and @Kovri intends to only process/use the `.i2p` [top-level domain](https://en.wikipedia.org/wiki/Top_level_domain)
|
||||
|
|
|
@ -25,8 +25,8 @@ Since a traditional [VPN](https://en.wikipedia.org/wiki/VPN) cannot save you fro
|
|||
|
||||
These technologies protect you from clearnet by building an anonymous network **over** clearnet to keep your transmissions both encrypted **and** anonymous.
|
||||
|
||||
Here is an accurate, [interactive diagram](https://www.eff.org/pages/tor-and-https) provided by the [EFF](https://www.eff.org/) which describes *clearnet* as it relates to **Tor**. The concept also (somewhat) applies to @Kovri and @I2P in terms of anonymity with the exception that:
|
||||
Here is an accurate, [interactive diagram](https://www.eff.org/pages/tor-and-https) provided by the [EFF](https://www.eff.org/) which describes *clearnet* as it relates to **Tor**. The concept also (somewhat) applies to @Kovri and I2P in terms of anonymity with the exception that:
|
||||
|
||||
- @Kovri does not use exit nodes when connecting to an @eepsite
|
||||
- Your traffic never need to leave the @I2P network
|
||||
- You do not need HTTPS to use @Kovri (with the exception of @reseed)
|
||||
- @Kovri does not use exit nodes when connecting to an eepsite
|
||||
- Your traffic never need to leave the I2P network
|
||||
- You do not need HTTPS to use @Kovri (with the exception of reseed)
|
||||
|
|
|
@ -27,8 +27,8 @@ The purpose of encryption is to ensure that only somebody who is authorized to a
|
|||
@Kovri implements various types of encryption in *at least* 4 essential capacities:
|
||||
|
||||
- @Reseed for bootstrapping
|
||||
- @Garlic-routing: three layers of encryption (@garlic-encryption) are used to verify the secure delivery of @messages to the recipient/peer/@destination
|
||||
- @Tunnel encryption: garlic messages are passed through a @tunnel and encrypted by the @tunnel gateway to the @tunnel endpoint
|
||||
- @Transport layer encryption prevents the ability to decrypt @messages at the [media layer](https://en.wikipedia.org/wiki/OSI_model)
|
||||
- @Garlic-routing: three layers of encryption (@garlic-encryption) are used to verify the secure delivery of messages to the recipient/peer/destination
|
||||
- @Tunnel encryption: garlic messages are passed through a tunnel and encrypted by the tunnel gateway to the tunnel endpoint
|
||||
- @Transport layer encryption prevents the ability to decrypt messages at the [media layer](https://en.wikipedia.org/wiki/OSI_model)
|
||||
|
||||
For details on the types of encryption and cryptographic @signatures used in @Kovri and @I2P, visit @Java-I2P's [Cryptography](https://geti2p.net/spec/cryptography)
|
||||
For details on the types of encryption and cryptographic @signatures used in @Kovri and I2P, visit @Java-I2P's [Cryptography](https://geti2p.net/spec/cryptography)
|
||||
|
|
|
@ -13,9 +13,9 @@ A locally-unique host is a [FQDN](https://en.wikipedia.org/wiki/FQDN) defined by
|
|||
|
||||
You have the option to share your interpretation of how the host is resolved (e.g., `localhost` always resolves to `127.0.0.1`) but the resolution is not canonically enforced (e.g., someone else can map `localhost` to any arbitrary IP address).
|
||||
|
||||
Hosts in a public subscription can be considered @canonically-unique-host's within the @I2P network but, ultimately, you are free to re-define them as you wish.
|
||||
Hosts in a public subscription can be considered @canonically-unique-host's within the I2P network but, ultimately, you are free to re-define them as you wish.
|
||||
|
||||
### Notes
|
||||
|
||||
- Monero primarily uses @canonically-unique-host resolution while @I2P only uses @locally-unique-host resolution.
|
||||
- @I2P's and @Kovri's assigned top-level domain is currently `.i2p` and @Kovri intends to only process/use the `.i2p` [top-level domain](https://en.wikipedia.org/wiki/Top_level_domain)
|
||||
- Monero primarily uses @canonically-unique-host resolution while I2P only uses @locally-unique-host resolution.
|
||||
- I2P's and @Kovri's assigned top-level domain is currently `.i2p` and @Kovri intends to only process/use the `.i2p` [top-level domain](https://en.wikipedia.org/wiki/Top_level_domain)
|
||||
|
|
|
@ -18,5 +18,5 @@ summary: "Хост, который канонически разрешен к а
|
|||
|
||||
### Примечания
|
||||
|
||||
- Monero в первую очередь использует принятие решение по @канонически-уникальному-хосту, в то время как @I2P использует только решение по @локально-уникальному-хосту.
|
||||
- Назначившим самого себя доменом @I2P и @Kovri верхнего уровня на данный момент является `.i2p`, @Kovri отвечает только за обработку / использование [домена верхнего уровня](https://en.wikipedia.org/wiki/Top_level_domain) `.i2p`.
|
||||
- Monero в первую очередь использует принятие решение по @канонически-уникальному-хосту, в то время как I2P использует только решение по @локально-уникальному-хосту.
|
||||
- Назначившим самого себя доменом I2P и @Kovri верхнего уровня на данный момент является `.i2p`, @Kovri отвечает только за обработку / использование [домена верхнего уровня](https://en.wikipedia.org/wiki/Top_level_domain) `.i2p`.
|
||||
|
|
|
@ -25,8 +25,8 @@ summary: "Интернет, в котором построены сети ано
|
|||
|
||||
Эти технологии защитят вас от клирнета путём построения анонимной сети **поверх** самого клирнета, в результате чего передаваемые вами данные будут как зашифрованными, так **и** анонимными.
|
||||
|
||||
Здесь вы можете увидеть [интерактивную диаграмму](https://www.eff.org/pages/tor-and-https), предоставленную [EFF](https://www.eff.org/) и описывающую, как работает *клирнет* и Tor. Эта концепция также (некоторым образом) применима к @Kovri и @I2P с точки зрения анонимности за исключением следующего:
|
||||
Здесь вы можете увидеть [интерактивную диаграмму](https://www.eff.org/pages/tor-and-https), предоставленную [EFF](https://www.eff.org/) и описывающую, как работает *клирнет* и Tor. Эта концепция также (некоторым образом) применима к @Kovri и I2P с точки зрения анонимности за исключением следующего:
|
||||
|
||||
- @Kovri не использует выходных узлов при соединении с @eepsite
|
||||
- Ваш трафик никогда не выходит за пределы сети @I2P;
|
||||
- @Kovri не использует выходных узлов при соединении с eepsite
|
||||
- Ваш трафик никогда не выходит за пределы сети I2P;
|
||||
- Вам не нужен HTTPS, чтобы использовать @Kovri (за исключением Reseed).
|
||||
|
|
|
@ -31,4 +31,4 @@ summary: "Процесс кодирования сообщений или инф
|
|||
- @туннельное шифрование - "чесночные" сообщения проходят через @туннель и шифруются @туннельным шлюзом до прибытия в конечную точку;
|
||||
- @шифрование-транспортного-уровня не позволяет расшифровать сообщения на [медийном уровне](https://en.wikipedia.org/wiki/OSI_model)
|
||||
|
||||
Подробная информация по типам шифрования и криптографическим @подписям, используемым @Kovri и @I2P, содержится в разделе [Криптография](https://geti2p.net/spec/cryptography) на @Java-I2P.
|
||||
Подробная информация по типам шифрования и криптографическим @подписям, используемым @Kovri и I2P, содержится в разделе [Криптография](https://geti2p.net/spec/cryptography) на @Java-I2P.
|
||||
|
|
|
@ -13,9 +13,9 @@ summary: "Хост, определенный вами и разрешенный
|
|||
|
||||
Вы можете поделиться собственной интерпретацией разрешения хоста (например, `localhost` всегда будет иметь разрешение `127.0.0.1`), но разрешение не является канонически принудительным (например, кто-то может присвоить значение `localhost` любому произвольному IP-адресу).
|
||||
|
||||
В сети @I2P хосты в публичной подписке могут рассматриваться как канонически уникальные, однако в конечном счёте вы можете определять их так, как вам будет угодно.
|
||||
В сети I2P хосты в публичной подписке могут рассматриваться как канонически уникальные, однако в конечном счёте вы можете определять их так, как вам будет угодно.
|
||||
|
||||
### Примечания
|
||||
|
||||
- Monero в первую очередь использует разрешение @канонически-уникального-хоста, в то время как @I2P использует только разрешение @локально-уникального-хоста.
|
||||
- В настоящее время доменом верхнего уровня для @I2P's и @Kovri является `.i2p`, и @Kovri в перспективе будет только обрабатывать данные/использовать только [домена верхнего уровня](https://en.wikipedia.org/wiki/Top_level_domain) `.i2p`
|
||||
- Monero в первую очередь использует разрешение @канонически-уникального-хоста, в то время как I2P использует только разрешение @локально-уникального-хоста.
|
||||
- В настоящее время доменом верхнего уровня для I2P's и @Kovri является `.i2p`, и @Kovri в перспективе будет только обрабатывать данные/использовать только [домена верхнего уровня](https://en.wikipedia.org/wiki/Top_level_domain) `.i2p`
|
||||
|
|
|
@ -18,5 +18,5 @@ A Canonically-unique host is defined by remote authoritative sources; usually th
|
|||
|
||||
### Notes
|
||||
|
||||
- Monero primarily uses @canonically-unique-host resolution while @I2P only uses @locally-unique-host resolution.
|
||||
- @I2P's and @Kovri's self-assigned top-level domain is currently `.i2p` and @Kovri intends to only process/use the `.i2p` [top-level domain](https://en.wikipedia.org/wiki/Top_level_domain)
|
||||
- Monero primarily uses @canonically-unique-host resolution while I2P only uses @locally-unique-host resolution.
|
||||
- I2P's and @Kovri's self-assigned top-level domain is currently `.i2p` and @Kovri intends to only process/use the `.i2p` [top-level domain](https://en.wikipedia.org/wiki/Top_level_domain)
|
||||
|
|
|
@ -25,8 +25,8 @@ Since a traditional [VPN](https://en.wikipedia.org/wiki/VPN) cannot save you fro
|
|||
|
||||
These technologies protect you from clearnet by building an anonymous network **over** clearnet to keep your transmissions both encrypted **and** anonymous.
|
||||
|
||||
Here is an accurate, [interactive diagram](https://www.eff.org/pages/tor-and-https) provided by the [EFF](https://www.eff.org/) which describes *clearnet* as it relates to **Tor**. The concept also (somewhat) applies to @Kovri and @I2P in terms of anonymity with the exception that:
|
||||
Here is an accurate, [interactive diagram](https://www.eff.org/pages/tor-and-https) provided by the [EFF](https://www.eff.org/) which describes *clearnet* as it relates to **Tor**. The concept also (somewhat) applies to @Kovri and I2P in terms of anonymity with the exception that:
|
||||
|
||||
- @Kovri does not use exit nodes when connecting to an @eepsite
|
||||
- Your traffic never need to leave the @I2P network
|
||||
- You do not need HTTPS to use @Kovri (with the exception of @reseed)
|
||||
- @Kovri does not use exit nodes when connecting to an eepsite
|
||||
- Your traffic never need to leave the I2P network
|
||||
- You do not need HTTPS to use @Kovri (with the exception of reseed)
|
||||
|
|
|
@ -27,8 +27,8 @@ The purpose of encryption is to ensure that only somebody who is authorized to a
|
|||
@Kovri implements various types of encryption in *at least* 4 essential capacities:
|
||||
|
||||
- @Reseed for bootstrapping
|
||||
- @Garlic-routing: three layers of encryption (@garlic-encryption) are used to verify the secure delivery of @messages to the recipient/peer/@destination
|
||||
- @Tunnel encryption: garlic messages are passed through a @tunnel and encrypted by the @tunnel gateway to the @tunnel endpoint
|
||||
- @Transport layer encryption prevents the ability to decrypt @messages at the [media layer](https://en.wikipedia.org/wiki/OSI_model)
|
||||
- @Garlic-routing: three layers of encryption (@garlic-encryption) are used to verify the secure delivery of messages to the recipient/peer/destination
|
||||
- @Tunnel encryption: garlic messages are passed through a tunnel and encrypted by the tunnel gateway to the tunnel endpoint
|
||||
- @Transport layer encryption prevents the ability to decrypt messages at the [media layer](https://en.wikipedia.org/wiki/OSI_model)
|
||||
|
||||
For details on the types of encryption and cryptographic @signatures used in @Kovri and @I2P, visit @Java-I2P's [Cryptography](https://geti2p.net/spec/cryptography)
|
||||
For details on the types of encryption and cryptographic @signatures used in @Kovri and I2P, visit @Java-I2P's [Cryptography](https://geti2p.net/spec/cryptography)
|
||||
|
|
|
@ -13,9 +13,9 @@ A locally-unique host is a [FQDN](https://en.wikipedia.org/wiki/FQDN) defined by
|
|||
|
||||
You have the option to share your interpretation of how the host is resolved (e.g., `localhost` always resolves to `127.0.0.1`) but the resolution is not canonically enforced (e.g., someone else can map `localhost` to any arbitrary IP address).
|
||||
|
||||
Hosts in a public subscription can be considered @canonically-unique-host's within the @I2P network but, ultimately, you are free to re-define them as you wish.
|
||||
Hosts in a public subscription can be considered @canonically-unique-host's within the I2P network but, ultimately, you are free to re-define them as you wish.
|
||||
|
||||
### Notes
|
||||
|
||||
- Monero primarily uses @canonically-unique-host resolution while @I2P only uses @locally-unique-host resolution.
|
||||
- @I2P's and @Kovri's assigned top-level domain is currently `.i2p` and @Kovri intends to only process/use the `.i2p` [top-level domain](https://en.wikipedia.org/wiki/Top_level_domain)
|
||||
- Monero primarily uses @canonically-unique-host resolution while I2P only uses @locally-unique-host resolution.
|
||||
- I2P's and @Kovri's assigned top-level domain is currently `.i2p` and @Kovri intends to only process/use the `.i2p` [top-level domain](https://en.wikipedia.org/wiki/Top_level_domain)
|
||||
|
|
|
@ -6,7 +6,7 @@ summary: "Base32 encoded hash of a Base64 address"
|
|||
|
||||
### 基础知识
|
||||
|
||||
Base32地址是一个@I2P地址的截短编码版本,Base32地址是 `.b32.i2p` 主机名的第一部分。
|
||||
Base32地址是一个I2P地址的截短编码版本,Base32地址是 `.b32.i2p` 主机名的第一部分。
|
||||
|
||||
例如:
|
||||
|
||||
|
@ -18,7 +18,7 @@ Base32地址是一个@I2P地址的截短编码版本,Base32地址是 `.b32.i2p
|
|||
|
||||
### 深度信息
|
||||
|
||||
基本上,Base32地址是52个字符长的,@I2P网络@Base64地址的完整SHA-256哈希的 [Base32编码表示](https://en.wikipedia.org/wiki/Base32)。
|
||||
基本上,Base32地址是52个字符长的,I2P网络@Base64地址的完整SHA-256哈希的 [Base32编码表示](https://en.wikipedia.org/wiki/Base32)。
|
||||
|
||||
### 备注
|
||||
|
||||
|
|
|
@ -6,7 +6,7 @@ summary: "Base64 encoded I2P destination"
|
|||
|
||||
### 基础知识
|
||||
|
||||
@Base64地址是由516个字符组成的 [Base64编码](https://en.wikipedia.org/wiki/Base64) @I2P @目标。@base64地址主要用于@地址薄、@跳转服务以及内部。
|
||||
@Base64地址是由516个字符组成的 [Base64编码](https://en.wikipedia.org/wiki/Base64) I2P @目标。base64地址主要用于@地址薄、@跳转服务以及内部。
|
||||
|
||||
例如:
|
||||
|
||||
|
@ -17,4 +17,4 @@ AQZGLAMpI9Q0l0kmMj1vpJJYK3CjLp~fE3MfvE-e7KMKjI5cPOH6EN8m794uHJ6b09qM8mb9VEv1lVLE
|
|||
|
||||
### 深度信息
|
||||
|
||||
有关@base64地址的更多详细信息,请参见@目标
|
||||
有关base64地址的更多详细信息,请参见@目标
|
|
@ -19,5 +19,5 @@ summary: "A host that is canonically resolved to an address or set of addresses"
|
|||
|
||||
### 备注
|
||||
|
||||
- 门罗币主要使用@标准唯一主机解析,而@I2P只使用@本地唯一主机解析。
|
||||
- @I2P和@Kovri的自定义顶级域名当前为`.i2p`,@Kovri只打算处理/使用 `.i2p` [顶级域名](https://en.wikipedia.org/wiki/Top_level_domain)
|
||||
- 门罗币主要使用@标准唯一主机解析,而I2P只使用@本地唯一主机解析。
|
||||
- I2P和@Kovri的自定义顶级域名当前为`.i2p`,@Kovri只打算处理/使用 `.i2p` [顶级域名](https://en.wikipedia.org/wiki/Top_level_domain)
|
||||
|
|
|
@ -25,9 +25,9 @@ summary: "The Internet in which anonymous overlay networks are built upon"
|
|||
|
||||
这些技术通过在明网上建立一个匿名网络,从而使您的传输经过加密**并**匿名,以从明网中保护你,
|
||||
|
||||
这是一个由[EFF](https://www.eff.org/pages/tor&https)提供的准确的[交互式图表](https://www.eff.org/),它描述了*明网*与**洋葱路由器**的关系。这个概念也(在一定程度上)适用于@Kovri和@I2P的匿名性,除了:
|
||||
这是一个由[EFF](https://www.eff.org/pages/tor&https)提供的准确的[交互式图表](https://www.eff.org/),它描述了*明网*与**洋葱路由器**的关系。这个概念也(在一定程度上)适用于@Kovri和I2P的匿名性,除了:
|
||||
|
||||
- @Kovri在连接到@eep站点时不使用出口节点
|
||||
- 您的流量永远不需要离开@I2P网络
|
||||
- 您的流量永远不需要离开I2P网络
|
||||
- 不需要HTTPS来使用@Kovri (@补种的情况除外)
|
||||
|
||||
|
|
|
@ -33,4 +33,4 @@ summary: "The process of encoding messages or information in a way that only aut
|
|||
- @隧道加密:大蒜消息通过@隧道传递,并由@隧道网关加密到@隧道端点
|
||||
- @传输层加密防止在[媒体层](https://en.wikipedia.org/wiki/OSI_model)解密@消息
|
||||
|
||||
有关@Kovri和@I2P中使用的各类型的加密和加密@签名的详细信息,请访问@Java-I2P的[密码学](https://geti2p.net/spec/cryptography)。
|
||||
有关@Kovri和I2P中使用的各类型的加密和加密@签名的详细信息,请访问@Java-I2P的[密码学](https://geti2p.net/spec/cryptography)。
|
||||
|
|
|
@ -12,9 +12,9 @@ summary: "A host defined by you and resolved only by you"
|
|||
|
||||
您可以选择共享您对主机解析方式的诠释(例如,“本地主机”总是解析为“127.0.0.1”),但是解析被不正规的执行(例如,其他人可以将“本地主机”映射到任意IP地址)。
|
||||
|
||||
在@I2P网络中,公共订阅中的主机可以被认为是@标准唯一主机,但最终,您可以自由地重新定义它们。
|
||||
在I2P网络中,公共订阅中的主机可以被认为是@标准唯一主机,但最终,您可以自由地重新定义它们。
|
||||
|
||||
### 备注
|
||||
|
||||
- 门罗币主要使用@标准唯一主机解析,而@I2P只使用@本地唯一主机解析。
|
||||
- @I2P和@Kovri的自定义顶级域名当前为 `.i2p` ,@Kovri只打算处理/使用 `.i2p` [顶级域名](https://en.wikipedia.org/wiki/Top_level_domain)
|
||||
- 门罗币主要使用@标准唯一主机解析,而I2P只使用@本地唯一主机解析。
|
||||
- I2P和@Kovri的自定义顶级域名当前为 `.i2p` ,@Kovri只打算处理/使用 `.i2p` [顶级域名](https://en.wikipedia.org/wiki/Top_level_domain)
|
||||
|
|
|
@ -18,5 +18,5 @@ A Canonically-unique host is defined by remote authoritative sources; usually th
|
|||
|
||||
### Notes
|
||||
|
||||
- Monero primarily uses @canonically-unique-host resolution while @I2P only uses @locally-unique-host resolution.
|
||||
- @I2P's and @Kovri's self-assigned top-level domain is currently `.i2p` and @Kovri intends to only process/use the `.i2p` [top-level domain](https://en.wikipedia.org/wiki/Top_level_domain)
|
||||
- Monero primarily uses @canonically-unique-host resolution while I2P only uses @locally-unique-host resolution.
|
||||
- I2P's and @Kovri's self-assigned top-level domain is currently `.i2p` and @Kovri intends to only process/use the `.i2p` [top-level domain](https://en.wikipedia.org/wiki/Top_level_domain)
|
||||
|
|
|
@ -25,8 +25,8 @@ Since a traditional [VPN](https://en.wikipedia.org/wiki/VPN) cannot save you fro
|
|||
|
||||
These technologies protect you from clearnet by building an anonymous network **over** clearnet to keep your transmissions both encrypted **and** anonymous.
|
||||
|
||||
Here is an accurate, [interactive diagram](https://www.eff.org/pages/tor-and-https) provided by the [EFF](https://www.eff.org/) which describes *clearnet* as it relates to **Tor**. The concept also (somewhat) applies to @Kovri and @I2P in terms of anonymity with the exception that:
|
||||
Here is an accurate, [interactive diagram](https://www.eff.org/pages/tor-and-https) provided by the [EFF](https://www.eff.org/) which describes *clearnet* as it relates to **Tor**. The concept also (somewhat) applies to @Kovri and I2P in terms of anonymity with the exception that:
|
||||
|
||||
- @Kovri does not use exit nodes when connecting to an @eepsite
|
||||
- Your traffic never need to leave the @I2P network
|
||||
- You do not need HTTPS to use @Kovri (with the exception of @reseed)
|
||||
- @Kovri does not use exit nodes when connecting to an eepsite
|
||||
- Your traffic never need to leave the I2P network
|
||||
- You do not need HTTPS to use @Kovri (with the exception of reseed)
|
||||
|
|
|
@ -27,8 +27,8 @@ The purpose of encryption is to ensure that only somebody who is authorized to a
|
|||
@Kovri implements various types of encryption in *at least* 4 essential capacities:
|
||||
|
||||
- @Reseed for bootstrapping
|
||||
- @Garlic-routing: three layers of encryption (@garlic-encryption) are used to verify the secure delivery of @messages to the recipient/peer/@destination
|
||||
- @Tunnel encryption: garlic messages are passed through a @tunnel and encrypted by the @tunnel gateway to the @tunnel endpoint
|
||||
- @Transport layer encryption prevents the ability to decrypt @messages at the [media layer](https://en.wikipedia.org/wiki/OSI_model)
|
||||
- @Garlic-routing: three layers of encryption (@garlic-encryption) are used to verify the secure delivery of messages to the recipient/peer/destination
|
||||
- @Tunnel encryption: garlic messages are passed through a tunnel and encrypted by the tunnel gateway to the tunnel endpoint
|
||||
- @Transport layer encryption prevents the ability to decrypt messages at the [media layer](https://en.wikipedia.org/wiki/OSI_model)
|
||||
|
||||
For details on the types of encryption and cryptographic @signatures used in @Kovri and @I2P, visit @Java-I2P's [Cryptography](https://geti2p.net/spec/cryptography)
|
||||
For details on the types of encryption and cryptographic @signatures used in @Kovri and I2P, visit @Java-I2P's [Cryptography](https://geti2p.net/spec/cryptography)
|
||||
|
|
|
@ -13,9 +13,9 @@ A locally-unique host is a [FQDN](https://en.wikipedia.org/wiki/FQDN) defined by
|
|||
|
||||
You have the option to share your interpretation of how the host is resolved (e.g., `localhost` always resolves to `127.0.0.1`) but the resolution is not canonically enforced (e.g., someone else can map `localhost` to any arbitrary IP address).
|
||||
|
||||
Hosts in a public subscription can be considered @canonically-unique-host's within the @I2P network but, ultimately, you are free to re-define them as you wish.
|
||||
Hosts in a public subscription can be considered @canonically-unique-host's within the I2P network but, ultimately, you are free to re-define them as you wish.
|
||||
|
||||
### Notes
|
||||
|
||||
- Monero primarily uses @canonically-unique-host resolution while @I2P only uses @locally-unique-host resolution.
|
||||
- @I2P's and @Kovri's assigned top-level domain is currently `.i2p` and @Kovri intends to only process/use the `.i2p` [top-level domain](https://en.wikipedia.org/wiki/Top_level_domain)
|
||||
- Monero primarily uses @canonically-unique-host resolution while I2P only uses @locally-unique-host resolution.
|
||||
- I2P's and @Kovri's assigned top-level domain is currently `.i2p` and @Kovri intends to only process/use the `.i2p` [top-level domain](https://en.wikipedia.org/wiki/Top_level_domain)
|
||||
|
|
Loading…
Reference in a new issue