On 21 Mar 2014, at 12:27, Ted Lemon wrote:
> On Mar 21, 2014, at 7:40 AM, Robin Wilton <[email protected]> wrote: >> Even if an email goes from my browser to Google's servers over https, and >> goes between Google's servers over https, I did not see a commitment to >> encryption of the email when it is at rest, rather than in motion... > > Best is the enemy of good enough. To compromise your mail on the server, > they have to compromise the server. To compromise it in flight, they just > have to tap the network. > Oh, I'm not suggesting that deployment of https should be deferred until there's end-to-end encryption. I'll certainly take https if it's offered. I was just pointing out that this announcement doesn't represent a change in Google's business model of monetizing the contents of Gmail correspondence. R Robin Wilton Technical Outreach Director - Identity and Privacy Internet Society email: [email protected] Phone: +44 705 005 2931 Twitter: @futureidentity
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________ perpass mailing list [email protected] https://www.ietf.org/mailman/listinfo/perpass
