[146378] in cryptography@c2.net mail archive
Re: [Cryptography] Good private email
daemon@ATHENA.MIT.EDU (Alexandre Anzala-Yamajako)
Mon Aug 26 12:46:27 2013
X-Original-To: cryptography@metzdowd.com
In-Reply-To: <CAFH29tp-c4qTu4ax5CHjy8LvoWYE1rKdgk+DNEVDDFWBFAD9aA@mail.gmail.com>
Date: Mon, 26 Aug 2013 18:44:13 +0200
From: Alexandre Anzala-Yamajako <anzalaya@gmail.com>
To: Richard Salz <rich.salz@gmail.com>
Cc: "cryptography@metzdowd.com" <cryptography@metzdowd.com>
Errors-To: cryptography-bounces+crypto.discuss=bloom-picayune.mit.edu@metzdowd.com
--===============6496098730100583937==
Content-Type: multipart/alternative; boundary=20cf307d02345aa3b704e4dc772b
--20cf307d02345aa3b704e4dc772b
Content-Type: text/plain; charset=ISO-8859-1
This is everything *but* PRISM-proof : it doesn t solve the metadata issue
and your directory server containing public keys could very well be forced
by a law enforcement agency ( in the best case scenario because it could
also be the mafia) to answer the fbi/mafia public key on any request made
to it.
On Monday, August 26, 2013, Richard Salz wrote:
> I don't think you need all that much to get good secure private email.
> You need a client that can make PEM pretty seamless; reduce it to a
> button that says "encrypt when possible." You need the client to be
> able to generate a keypair, upload the public half, and pull down
> (seamlessly) recipient public keys. You need a server to store and
> return those keys. You need an installed base to kickstart the network
> effect.
>
> Who has that? Apple certainly; Microsoft could; Google perhaps
> (although not reading email is against their business model). Maybe
> even the FB API.
>
> It's not perfect -- seems to me the biggest weakness is (a) the client
> could double-encrypt for TLA's to read, or (b) it could give you the
> wrong key so your mail only goes to the bad guy -- but it's a hell of
> a lot better than we have now and I'd say it's more than good enough.
>
> Thoughts?
> _______________________________________________
> The cryptography mailing list
> cryptography@metzdowd.com <javascript:;>
> http://www.metzdowd.com/mailman/listinfo/cryptography
>
--
Alexandre Anzala-Yamajako
--20cf307d02345aa3b704e4dc772b
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
This is everything *but* PRISM-proof : it doesn t solve the metadata issue =
and your directory server containing public keys could very well be forced =
by a law enforcement agency ( in the best case scenario because it could al=
so be the mafia) to answer the fbi/mafia public key on any request made to =
it.<span></span><br>
<br>On Monday, August 26, 2013, Richard Salz wrote:<br><blockquote class=
=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padd=
ing-left:1ex">I don't think you need all that much to get good secure p=
rivate email.<br>
=A0You need a client that can make PEM pretty seamless; reduce it to a<br>
button that says "encrypt when possible." =A0You need the client =
to be<br>
able to generate a keypair, upload=A0the public half, and pull down<br>
(seamlessly) recipient public keys. =A0You need a server to store and<br>
return those keys. You need an installed base to kickstart the network<br>
effect.<br>
<br>
Who has that? =A0Apple certainly; Microsoft could; Google perhaps<br>
(although not reading email is against their business model). Maybe<br>
even the FB API.<br>
<br>
It's not perfect -- seems to me the biggest weakness is (a) the client<=
br>
could double-encrypt for TLA's to read, or (b) it could give you the<br=
>
wrong key so your mail only goes to the bad guy -- but it's a hell of<b=
r>
a lot better than we have now and I'd say it's more than good enoug=
h.<br>
<br>
Thoughts?<br>
_______________________________________________<br>
The cryptography mailing list<br>
<a href=3D"javascript:;" onclick=3D"_e(event, 'cvml', 'cryptogr=
aphy@metzdowd.com')">cryptography@metzdowd.com</a><br>
<a href=3D"http://www.metzdowd.com/mailman/listinfo/cryptography" target=3D=
"_blank">http://www.metzdowd.com/mailman/listinfo/cryptography</a><br>
</blockquote><br><br>-- <br>Alexandre Anzala-Yamajako<br><br><br><br>
--20cf307d02345aa3b704e4dc772b--
--===============6496098730100583937==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
_______________________________________________
The cryptography mailing list
cryptography@metzdowd.com
http://www.metzdowd.com/mailman/listinfo/cryptography
--===============6496098730100583937==--
