Differences
This shows you the differences between two versions of the page.
Both sides previous revision Previous revision Next revision | Previous revision | ||
users:toxdns [2017/07/11 20:00] aklyn outline the actual problems and what the page got wrong |
— (current) | ||
---|---|---|---|
Line 1: | Line 1: | ||
- | ===== ToxDNS ===== | ||
- | ToxDNS is a tox ID-to-name mapping service. It allows users to shorten their regular, somewhat long, Tox IDs, with short and readable IDs, that closely resemble the format of an email address. An example of a ToxDNS service in use is **groupbot@utox.org**, | ||
- | |||
- | ToxDNS servers are [[https:// | ||
- | |||
- | [The " | ||
- | |||
- | ==== What you might want to know about ToxDNS ==== | ||
- | |||
- | Some people have some concerns about how ToxDNS services could be used maliciously, | ||
- | |||
- | [The main concern is not denial of service but the lack of reliability of the result of a " | ||
- | |||
- | The argumentation below is both incomplete and misleading, but I leave the text as it was for reference; MITM by hijacking on the network level at a name/id lookup is not mentioned; impersonation by preregistering a rogue id is not mentioned; impersonation by guessing a password is referred to as MITM which is hardly fair; a malicious or compromised server which at will redirects certain lookups to rogue ids is not mentioned; all of these lead not only to the possibility of talking to a wrong party but for MITM while talking to the right party (!), which is not possible to exclude -- aklyn] | ||
- | |||
- | **Impersonating a user(MITM) by switching the Tox ID associated with the username:** If someone compromised your account on a ToxDNS Service or a server hosting ToxDNS records, they might be able to replace the Tox ID associated with the username. New users looking up a Tox ID using the compromised username would be directed to the wrong Tox ID. To minimize the chance of such a thing occurring, use a long, unique, random password for your ToxDNS account, and set the ID to be unchangable if the server supports it. This will not connect you with your intended friend and it does not give anyone access to your private key or any current or previous chat sessions keys. | ||
- | |||
- | **Malicious Service Operator gathering metadata on Tox ID's as they are registered: | ||
- | |||
- | **Denial of Service against a ToxDNS Service:** If someone denies users access to the ToxDNS service they wish to use to lookup an ID, then they will not be able to look up ID's at that service. If this is a concern, you might join multiple ToxDNS services, host your own ToxDNS service, or distribute your whole Tox ID in text form or using a [[users: | ||
- | |||
- | It should be noted that none of these area actually problems with ToxDNS itself. The first two are malicious activities that could be undertaken on a server, the third is just somebody taking a site down or blocking access to a site. | ||
- | |||
- | [all of these areas represent a fundamental problem of using a service which is insecure by design, to initiate a more secure one - the final security is not better than of the weakest part in the chain - aklyn] | ||
- | ===== ToxDNS Services ===== | ||
- | As of yet, there is no official ToxDNS service. All services listed here are run by volunteers, use at your own risk. | ||
- | |||
- | | ^ Owner ^ Description | ||
- | ^ [[http:// | ||
- | | | ||
- | |||
- | ===== Run your own ===== | ||
- | Don't want to trust a third party service? Want to use your own cool domain? Or want to contribute by hosting your own public service? You can quickly and easily install a ToxDNS service to run on your own server! | ||
- | |||
- | Some of the many open-source ToxDNS services include: | ||
- | * https:// | ||
- | * https:// | ||
- | * https:// | ||
- | |||
- | ==== Installation ==== | ||
- | (help wanted) | ||
- | |||
- | [[users: | ||
- | |||
- | [[users: |