Hacker News Reader

Comment by dublinben | Hacker News Reader

From what you've described, it seems like i2p would satisfy the requirements of your first paragraph and Freenet would satisfy the requirements of the second. Both of these networks have been around for over a decade, so they're not as in vogue as newer projects.

View on HN

I have only slightly looked at i2p, but sadly appears the only impl requires a JVM. I have researched freenet and it does not appear to provide plausible deniability for public data (sorry on mobile and can't link easily).

It does provide plausible deniability, since you have no control over what files go to your node (files are spread as people request them) and they are encrypted, hence you can't easily know what they contain.

Both [0] and [1] seem to suggest that if you make the data "public" then someone can know they have a piece.

"It is hard, but not impossible, to determine which files that are stored in your local Freenet Datastore"

"Of course, the decryption keys, which are contained in links to the files, may be publically posted on some other site - they have to be if the site creator wants people to visit their site. But if you've never had knowledge of that link, which is very plausible if there are thousands of Freenet sites, you can't be expected to know what is contained in the encrypted files in your Freenet node."

0 - http://security.stackexchange.com/questions/12811/how-does-f...

1 - https://wiki.freenetproject.org/Plausible_deniability

If you feel brave, you could try the C++ implementation of the i2p router, purplei2p[1] (aka i2pd[2]). Last time I tried, there were a few rough edges, but it is now over two years old, so it has probably improved (or you may even improve it yourself!).

[1] https://purplei2p.github.io/ [2] https://github.com/PurpleI2P/i2pd

there is a c++ implementation of I2P[0].

0. https://github.com/PurpleI2P/i2pd

Reply on news.ycombinator.com