News for hackers. Stuff that matters.
Re:Forced Exposure by rlpb on Tuesday August 20, 2013 @06:03AM (#6242665)
How feasible is Freenet for email? We can use PGP today, but the metadata is available to all. But what journalists who need to communicate more anonymously that that used pseudonymous PGP keys - one per story, rather one per person, and posted encrypted messages on Freenet?
Re:Forced Exposure by fmoq on Tuesday August 20, 2013 @10:29AM (#6243899)
It works. Freenet has Freemail[0]. I'd like to bring attention to I2PBote[1] too.

Both of these solutions are distributed, encrypted entirely (even metadata) and solve email's privacy problems.

[0] http://freenetproject.org/freemail.html

[1] http://i2pbote.i2p.us/

Re:Forced Exposure by nwh on Tuesday August 20, 2013 @06:18AM (#6242717)
When you think about totalitarian internet monitoring, like the one the US seem to have, there's almost no point aiming for anonymity. Almost all sensible means are broken when you have deep levels of traffic interception in many countries.

The Tor Anonymity Router mentions the types of monitoring they attempt to subvert, and mention that full internet monitoring is not one of their design goals. This is simply because with any low-latency system, correlation between the entry and exit can be obtained. Similar attacks exist for networks such as Bitcoin for similar reasons.

> But what journalists who need to communicate more anonymously that that used pseudonymous PGP keys - one per story

In this case you run into troubles with authenticity. Without persistent keys being authenticated in some way (see "web of trust"), there's no way in telling if the person is communicating with a government proxy or the real target journalist.

That's the issue with the "encrypt everything" mantra, authenticity is stupid difficult to verify.

Re:Forced Exposure by einhverfr on Tuesday August 20, 2013 @06:33AM (#6242771)
I think Tor would be a better idea of what to try to emulate, but the full envelope (including envelope from) would have to be encrypted such that it would be decrypted at the end-point.

I think something sufficiently secure is possible for email. I think it would require a whole new set of protocols and approaches, and for some things (like voice) it is not.

Re:Forced Exposure by kaoD on Tuesday August 20, 2013 @06:23AM (#6242729)
It's just non-feasible. Freenet is a distributed file/web database, not realtime internet.
Re:Forced Exposure by dvdkhlng on Tuesday August 20, 2013 @07:47AM (#6243024)
Should be feasible with GNUnet [1] which has pretty generic foundations for implementing anonymous and secure peer-to-peer services. Think of an encrypted overlay network that uses addresses that cannot be linked to IP addresses and relaying transfer mechanisms that are hardened against traffic analysis attacks.

There seems to be research under way to get a messaging protocol built into GNUnet. Google turns up this pdf [2] for example.

[1] https://gnunet.org/

[2] http://rp.delaat.net/2012-2013/p88/presentation.pdf

Re:Forced Exposure by rlpb on Tuesday August 20, 2013 @06:31AM (#6242760)
Email does not have to be real time.
Re:Forced Exposure by kaoD on Tuesday August 20, 2013 @06:57AM (#6242837)
Maybe realtime was not the best choice of a word, but Freenet cannot handle email in any case.

Freenet is a global distributed p2p file database. Email does not fit that medium.

Re:Forced Exposure by rlpb on Tuesday August 20, 2013 @08:09AM (#6243123)
> Email does not fit that medium.

Why not?

Email can be implemented in a global p2p file database. Every "email" simply adds another file. Privacy can be ensured with encryption (as long as the encryption is not broken, at least). See existing Freenet message boards for an example.

It may not be Internet RFC821/822 (and subsequent standards) Email, but it is email.

What part of this will not fit the Freenet model?

Re:Forced Exposure by kaoD on Tuesday August 20, 2013 @08:16AM (#6243163)
How would you send the new file to your recipient?
Re:Forced Exposure by rlpb on Tuesday August 20, 2013 @08:29AM (#6243231)
The same way that message boards do this already on Freenet.

See https://freenetproject.org/understand.html.

Something like:

Publish a site using a USK (perhaps one per recipient), containing all encrypted messages sent recently. Update the site with an additional message when you need to send one. The recipient checks it for updates periodically.

I'm not sure if my understanding is inaccurate, but since Frost already achieves something like this, I don't see that it's automatically impossible such as what you seem to be inferring.

In fact, now that I look, there's: https://freenetproject.org/freemail.html

I'm dubious about the safety of using non-Freenet clients, but surely this demonstrates that it's possible to build a messaging system built over Freenet?

Re:Forced Exposure by kaoD on Tuesday August 20, 2013 @08:44AM (#6243302)
Yep, you're right.