3 ms·
There's no technical info in the article. This one (link from the article) seems to be more resourceful on details: http://engineering.bittorrent.com/2013/12/19
by drdaeman 12y ago
There's no technical info in the article. This one (link from the article) seems to be more resourceful on details: http://engineering.bittorrent.com/2013/12/19/update-on-bittorrent-chat/ http://engineering.bittorrent.com/2013/12/19/update-on-bitto...
The interesting part is their claim they somehow made DHT public key to IP discovery (mapping) "encrypted" and "secure". Sadly, I hadn't found any further details.
- Mandatum 12y agoIt would still require centralised servers for the mapping, in which case wouldn't it become immaterial?
- AnthonyMouse 12y agoUsing a public key to authenticate an IP address is trivial. You just sign the address (and a timestamp for how long it's valid) with the private key. Making it private is the interesting bit. Obviously you can't have privacy in the sense that someone who knows your public key can't use it to discover your IP address, because doing that is the DHT's purpose. So what they're probably talking about is that somebody observing the DHT can't use it to learn public keys, IP addresses or both. But it would be nontrivial to do that in a way that isn't useless (e.g. storing under public key fingerprint instead of public key: now you don't have my public key, and having fingerprint is totally different, right?)