Bluntly: Serverless, NAT-breaking P2P with public keys and BitTorrent DHT
1–10 of 17 posts
Re: Bluntly: Serverless, NAT-breaking P2P with public keys and BitTorrent DHT
#2proof 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.
Re: Bluntly: Serverless, NAT-breaking P2P with public keys and BitTorrent DHT
#3proof 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.
The idea of piggybacking on bittorrent DHT network is great :)
Just out of interest, do you know of any other systems that do that?
Re: Bluntly: Serverless, NAT-breaking P2P with public keys and BitTorrent DHT
#4proof 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.
The idea of piggybacking on bittorrent DHT network is great :) Just out of interest, do you know of any other systems that do that?
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.
Re: Bluntly: Serverless, NAT-breaking P2P with public keys and BitTorrent DHT
#5Congrats, the idea is great (I have something similar in my TODO list).
Now the next step is to implement file transfer and self-hosted web server with social network app and you have decentralized internet :)
Re: Bluntly: Serverless, NAT-breaking P2P with public keys and BitTorrent DHT
#6proof 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.
The idea of piggybacking on bittorrent DHT network is great :) Just out of interest, do you know of any other systems that do that?
Retroshare uses Bittorrent DHT http://retroshare.sourceforge.net/
Re: Bluntly: Serverless, NAT-breaking P2P with public keys and BitTorrent DHT
#7proof 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.
The idea of piggybacking on bittorrent DHT network is great :) Just out of interest, do you know of any other systems that do that?
I do the same in rakoshare (https://github.com/rakoo/rakoshare). Humans exchange a well-known id, from which a rendez-vous id is derived. This rendez-vous id is used for all interested peers to meet and exchange ips and ports.
After that, it's the job of every one to try to connect to the other side. Sadly, if there's a NAT on each side, it's not enough...
Re: Bluntly: Serverless, NAT-breaking P2P with public keys and BitTorrent DHT
#8Looks like a flurry of work on Mar 25 & 26, then no commits since then. Do you consider this complete / ready for production?
Re: Bluntly: Serverless, NAT-breaking P2P with public keys and BitTorrent DHT
#9Congrats, the idea is great (I have something similar in my TODO list). Now the next step is to implement file transfer and self-hosted web server with social network app and you have decentralized internet :)
Don't forget adding some payment forwarding to enable federation: http://dev.blockcypher.com/#payments. That would also take care of the public key to public key enablement.
Re: Bluntly: Serverless, NAT-breaking P2P with public keys and BitTorrent DHT
#10proof 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.
The idea of piggybacking on bittorrent DHT network is great :) Just out of interest, do you know of any other systems that do that?
retroshare uses DHT
It also uses PGP keys to facilitate encryption, authenticity, and a comprehensive web of trust