Domain authorization about kadnode HOT 4 CLOSED

• the length of query is kind of arbitrary. I just hope that any domain that it will be used for is a maximum of 255 bytes long. The query might be a 32byte public key in base16 or base32, or any domain you see in the browser (meet.mydomain.com).
• the port is the DHT port, but is also shared for the authentication via BOB (see function dht_handler() since we have no channel to store the extra port and we only would need a singkel port forwarding . To distinguish the traffic we check for the first three bytes of each packet to start with BOB, if not, then it is a DHT packet). Authentication via TLS/HTTPS is done via port 443, but I forgot how that is working right now and need to read the code.
• the lifetime of an annoucement is the time until the announcement is removed (> time(NULL), can be LONG_MAX for infinity)
• the refresh time of an announcement is the next time, to refresh the entries in the DHT network.

from kadnode.

I think an announcement payload may be encrypted, but I think that would require changes of the DHT implementation. I have not really tried yet.

from kadnode.

Thank you for the answers. Hope I'll find a time on the week to play and learn more.
Meanwhile I watched the video where explained how Tor onion services are using DHT https://youtu.be/Di7qAVidy1Y?t=1683

So an attacker can create a DHT node with a hash similar to domain and it can see how many of requests are for the site. Not a big deal for unanimous KadNode but still maybe it's possible to grab some privacy improvements from Tor.

from kadnode.

https://donncha.is/2013/05/trawling-tor-hidden-services/

from kadnode.