search

holepunchto / hyperswarm

A distributed networking stack for connecting peers.
https://docs.holepunch.to
MIT License
1.06k stars 85 forks source link

Privacy Preserving in Hyperswarm #81

Closed raphael10-collab closed 2 years ago

raphael10-collab commented 3 years ago

In search for info about privacy preserving DHTs, I found these interesting papers:

https://www.gpestana.com/blog/in-pursuit-of-private-dhts/

"Some of the desirable properties of a private and metadata resistant DHT are:

    Anonymity for producers of content: tracking down who was the originator of content stored in the DHT should not be possible.

    Anonymity for consumers of content: nodes that request content from the DHT should not be linked to the requested content by external actors.

    Plausible deniability of the files hosted in the network nodes: when peers query for content in the DHT, they should not be able to identify which peers are storing the content.
"

https://raw.githubusercontent.com/gpestana/p2psec/master/papers/privacy_preserving_dht/privacy_preserving_dht.pdf

https://www.gpestana.com/papers/everyone-is-naked-rev.pdf

where privacy vulnerabilities within a DHT are described.

In the last paragraph of the second paper, few Privacy Enhancing Technologies (PETs) are outlined and suggested for DHTs. Namely: Onion Routines, and cryptographic tools: Multi-Party Computation and Zero Knowledge primitives.

What are the mechanisms and the tools deployed in Hyperswarm in order to enhance and preserve, as much as possible, privacy? Would it be feasibly to implement the Onion Routines within Hyperswarm?

raphael10-collab commented 3 years ago

Hi Hyperswarm people! I found this on-going javascript implementation of onion protocol: https://github.com/Ayms/node-Tor . Please, have a look at it. It would be awesome if Hyperswarm would incorporate and use it. Looking forward to your feedback

mafintosh commented 2 years ago

Moving this to the DHT issue for now where I replied.