<p dir="ltr">Bote mail on I2P seems to have everything but forward secrecy. It is serverless and uses DHT for delivery and public keys as addresses, with all emails being encrypted. There are Bote-SMTP proxies you can use (same warning as for Tor outproxies apply, use PGP!) </p>
<p dir="ltr">- Sent from my phone</p>
<div class="gmail_quote">Den 19 nov 2013 01:19 skrev "elijah" <<a href="mailto:elijah@riseup.net">elijah@riseup.net</a>>:<br type="attribution"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
On 11/18/2013 09:37 AM, Josh Steiner wrote:<br>
<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<a href="http://www.kickstarter.com/projects/ladar/lavabits-dark-mail-initiative" target="_blank">http://www.kickstarter.com/<u></u>projects/ladar/lavabits-dark-<u></u>mail-initiative</a><br>
<br>
Basically, it is an initiative to open source the lavabit's internal<br>
code and turn it into a new secure mail protocol they are calling<br>
"Dark Mail"<br>
</blockquote>
<br>
The really annoying thing is that lavabit's platform and Dark Mail are totally incompatible and have nothing to do with one another. So the kickstarter is meaningless.<br>
<br>
* lavabit's prior software allowed the service provider to encrypt a user's IMAP disk storage individually to the password of the user.<br>
* darkmail is a project driven mostly by silentcircle that is to create something entirely new that is email-like, but not email.<br>
<br>
In case you missed it, moxie did a pretty good job explaining why lavabit's old code should die and should most definitely NOT be open sourced or used by anyone: <a href="http://www.thoughtcrime.org/blog/lavabit-critique/" target="_blank">http://www.thoughtcrime.org/<u></u>blog/lavabit-critique/</a><br>
<br>
This critique was later posted to arstechnica, and then later there was an exchange on reddit under Ladar's AMA in which Ladar doubled down on his completely unjustified claims and Moxie doubled down on lavabit being total snakeoil:<br>
<br>
<a href="http://www.reddit.com/r/IAmA/comments/1qetvk/i_am_ladar_levison_owner_and_operator_of_lavabit/" target="_blank">http://www.reddit.com/r/IAmA/<u></u>comments/1qetvk/i_am_ladar_<u></u>levison_owner_and_operator_of_<u></u>lavabit/</a><br>
<br>
It is not pretty. Moxie is correct, of course, but a valid defense of the lavabit model would have been to talk about how US law treats data at rest very differently than data in transit. This was not the approach Ladar pursued. It does not totally matter, because that potential justification doesn't hold true anymore based on what we now know. So, really, there is no justification for making the lavabit approach open source.<br>
<br>
The darkmail project is interesting in that they have promised all things to all people:<br>
<br>
* end-to-end client-side encryption<br>
* automatic management of keys<br>
* not email, but xmpp used in an email-like way<br>
* but maybe also gateways to email for backward compatibility<br>
* asynchronous forward secrecy and metadata protection via SCIMP 2.0<br>
* thunderbird extension<br>
* local imap & smtp server so you can use existing mail user agent<br>
* open protocol and open source code so anyone can adopt<br>
* tools to make it easy for a service provider to use<br>
<br>
Because we don't have any details yet on darkmail it is impossible to critique. What we do know is that SCIMP 1.0 doesn't have the properties that are promised, and they can't be added without basically a whole new protocol. But I think darkmail is exciting and is making the right promises (total end-to-end security). I certainly hope they will answer my emails :)<br>
<br>
Of course, LEAP (<a href="https://leap.se/email" target="_blank">https://leap.se/email</a>) already does almost everything that darkmail wants to do, with the one caveat that currently we use SMTP exclusively and rely on the service provider for PFS and metadata protection (although we have a plan to fix this in the future).<br>
<br>
-elijah<br>
______________________________<u></u>_________________<br>
Guardian-dev mailing list<br>
<br>
Post: <a href="mailto:Guardian-dev@lists.mayfirst.org" target="_blank">Guardian-dev@lists.mayfirst.<u></u>org</a><br>
List info: <a href="https://lists.mayfirst.org/mailman/listinfo/guardian-dev" target="_blank">https://lists.mayfirst.org/<u></u>mailman/listinfo/guardian-dev</a><br>
<br>
To Unsubscribe<br>
Send email to: <a href="mailto:Guardian-dev-unsubscribe@lists.mayfirst.org" target="_blank">Guardian-dev-unsubscribe@<u></u>lists.mayfirst.org</a><br>
Or visit: <a href="https://lists.mayfirst.org/mailman/options/guardian-dev/natanael.l%40gmail.com" target="_blank">https://lists.mayfirst.org/<u></u>mailman/options/guardian-dev/<u></u>natanael.l%40gmail.com</a><br>
<br>
You are subscribed as: <a href="mailto:natanael.l@gmail.com" target="_blank">natanael.l@gmail.com</a><br>
</blockquote></div>