News for hackers. Stuff that matters.

danoctavian

What is your domain?
That's a good point. You still need those. I don't believe there's any way around it whenever you're using a decentralized network like the DHT, you need to somehow "get into" the network, so you need to know someone from it.
It's not production ready, it's quite flaky because of the NAT penetration. it sometimes works, sometimes doesn't. It's a POC, i don't have the bandwidth now to make it robust.It's meant to showcase it's possible.

i coded it a while ago and then though to post it just now. (it actually took longer but i just pushed all code in 1 day)

Well BitTorrent's own project Bleep uses the Bittorrent network as well.

Their protocol is more complex however. Their goals are to hide who is talking who, from entities that might just be scraping the DHT. With bluntly, you can tell who is talking to who, by looking at what peers advertised on the rendezvous node.

Because they have control over the bittorrent protocol, they can go ahead and make changes to it that make NAT penetration easier (a 3rd party peer with a public address acts as a facilitator for putting 2 peers behind NAT in contact) or they can allow for arbitrary data to be stored in the DHT.

proof of concept code for making secure connections between 2 peers by knowing only each other's public keys. (no servers or IP knowledge involved, featuring NAT penetration).

uses the bittorrent DHT. code is hacky, written for fun.

As opposed to Bleep and Tox, it works right now with no extra protocol or network.