>Additionally can you explain how he got the architecture "wrong"? See Moxie Marlinspike's post from last November: http://www.thoughtcrime.org/blog/lavabit-c

>Additionally can you explain how he got the architecture "wrong"? See Moxie Marlinspike's post from last November: http://www.thoughtcrime.org/blog/lavabit-critique/ http://www.thoughtcrime.org/blog/lavabit-critique/ You can't entrust a server with encryption / decryption, nor with supplying the tools to do it locally, e.g., via JS downloaded as part of a web interaction. Service providers can be subpoenaed, threatened, infiltrated, bribed, or hacked. Or they can just turn evil. All crypto must take place on the client, using carefully vetted tools.