From 20cf9ed7ef57e36a3be39e7a25e0097777fb5e19 Mon Sep 17 00:00:00 2001 From: Mark Nottingham Date: Wed, 11 Mar 2015 11:44:28 +1100 Subject: [PATCH] Edits from Roger and Linus --- dnsop-onion-tld/draft.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/dnsop-onion-tld/draft.md b/dnsop-onion-tld/draft.md index 837d4ed1..5f8a482c 100644 --- a/dnsop-onion-tld/draft.md +++ b/dnsop-onion-tld/draft.md @@ -160,12 +160,12 @@ communicating with is correct, as attackers may be able to find keys which produce service names that are visually or apparently semantically similar to the desired service. -Also, users need be aware of the difference between a .onion name used and +Also, users need to understand the difference between a .onion name used and accessed directly via Tor-capable software, versus .onion subdomains of other TLDs and providers (e.g., the difference between example.onion and example.onion.tld). -The cryptographic label for an .onion name is constructed by applying a +The cryptographic label for a .onion name is constructed by applying a function to the public key of the server, the output of which is rendered as a string and concatenated with the string ".onion". Dependent upon the specifics of the function used, an attacker may be able to find a key that