Re:publica 15: Google Promotes Privacy, But Not Too Much
tutanota.de
tutanota.de
In case anybody hasn't read it yet, Philip Zimmermann's essay on why he wrote PGP is very relevant to this discussion. Google is effectively saying envelopes are not meant for common use.
Did you send everything by postcard back in the snail-mail days, only using an envelope when the contents was very-important? If someone saw you mailing an envelope, did they suspiciously ask what was so important that you needed to hide it? No, wrapping your mail in an envelope was commonplace.
This is what we need to do for digital messages: wrap them in an envelope (encryption). More importantly, we need a culture that sees sending encryption as normal. You may not be sending anything important at the moment, but other people are, and if encryption is only used for "important" things, it invites suspicion.
If Google has a problem with this, I suggest they find a new business plan.
And then sell that to the highest bidder.
It has been at the forefront of pushing SMTP to SMTP encryption and HTTPS everywhere. Google has to spread (and perhaps seriously believes in) the idea that they transfer data securely, unreadable by the Five Eyes. Because the perception that Google is in bed with the NSA et al. is seriously undermining their reputation (especially in Europe).
On the other hand, scanning content for ads requires that they have unfettered access to user data. If by implementing good end-to-end encryption e-mail would not be visible to them anymore, their abilities to do user profiling of those on and not on GMail would be impeded seriously.
If you want real privacy, you should move out of the Google ecosystem. Their terms of use are too far-reaching and their interest in your data too large to assume that they would go all-in with complete end to end encryption of everything.
Plus they're encrypted so only they know it. Also, I'm not from the US so MY government doesn't have access to their data.
You could.. you know... change that.. https://duckduckgo.com
> Also, I'm not from the US so MY government doesn't have access to their data
Because the US doesn't have any allies that participate in data sharing, and definitely doesn't intercept data in transit over the greater internet and on Google's internal network...
Oh wait..
THAT's where Google's position, or at least this Google spokesman's position is wrong: I'll give up both some convenience and some money to get more privacy.
Paying for more privacy is not and probabably will never be an option.
It's completely against their current models. They're basically telling advertisers: You know that product we were selling you, that made us billions of dollars together? We're not selling it to you anymore, but it's still making us money.
FWIW, Wikipedia says Google has five million customers for the gmail-for-business product, each of which pays $50-60 per year per user. If you assume an average of two employees per customer that's a half-billion dollars per year. If you believe the numbers in e.g. http://www.quora.com/How-much-does-Google-earn-from-ads-per-... the ad-supported gmail revenue must be peanuts by comparison.
I did switch off of gmail for general use, but I forward some emails to my old gmail account for experimenting with Google Now on my Android phone. For example, I will forward emails confirming airline reservations and car rentals so that information ends up in Google Calender and Google Now. For the same reason I sometimes will turn on location services on my phone.
I use Firefox for my web browsing, but use Chrome when visiting Google, Facebook, and Twitter web properties. I check cookies set in Firefox to make sure I have not enabled tracking.
I am making some real compromises in privacy and convenience, but for now this 'middle road' works for me.
In WW2, the Allied Navies faced two main naval code strategies: Germany's and Japan's. Roughly, the Japanese Navy sent their routing information in plaintext, while the Kriegsmarin sent it in ciphertext. Because the German routing instructions were encrypted, each node had to be able to decrypt universally. Capture one U-boat, and, well, we all saw the movie.
In contrast, the Japanese navy sent the routing information in the clear, so transceiving stations only had to read the routing information and transmit the ciphertext verbatim: capture a Japanese sub and you can only decode messages sent to that sub. However, because the routing information was visible in all transmissions, a lot of sideband avenues were opened up (you may not know what Yamamoto was sending to the Coral Sea fleet, but you're damn sure interested in the fact that he was talking to them at 2am this morning, particularly since you can then watch what they do.)
Anyways, not directly relevant to the article but a cool example of how far back this question goes.
A different key for each vessel would mean several passes through the encryption machine, key tables distributed through several places, and the requirement of specialized workforce where otherwise just typing stuff in a machine would do. And all the errors that come with manually dealing with that, all during a major war.
^^^ That.
If they really said that, that's amazingly weak and clumsy.
I would have been impressed if they had openly said it's because they can't analyze your email for ads and targeting.
In fact I'd be very impressed if they said up front, briefly and not implied in a ToS book, that the reason you get free email is so they can read your email.
The fact that they went with a dodge suggests they know that they risk a lot of blowback if people started to learn about their actual business plan.
For the few emails I send where the value of the security provided exceeds the lost value due to being unable to search I can, using their extension, enable end-to-end encryption.
This system suits my needs perfectly, I appreciate that others may want all the emails they send to be encrypted but why should Google cater to this - they cannot make any money from encrypted emails.
One email sent the wrong way when tired. One change in legislation (to e.g. retrospectively criminalise an activity or legalise a certain type of snooping). Now your company's IP is compromised. Or now your in jail. Or now you can be blackmailed.
Furthermore the idea that you will be encrypting the mail may cause tired future you to write something you wouldn't put on a post card.
So unless you are perfect and never ever click in the wrong place good luck in this brave world of ours.
Also, the Constitution can be amended. We can't guarantee that ex post facto laws will remain unconstitutional for the duration of your lifetime.
Also, states are technically not obliged to abide by the US constitution.
The last paragraph is correct in context. Specifically, with regards to encryption, states are allowed to do whatever they want because the Constitution doesn't mention encryption and because of the 10th amendment, which states:
The powers not delegated to the United States by the Constitution, nor prohibited by it to the States, are reserved to the States respectively, or to the people.
The last paragraph is also correct because the ex post facto law clause of the Constitution only applies to Congress, not the states [1]
[1] https://en.wikipedia.org/wiki/Article_One_of_the_United_Stat...
The point is that these email records are permanent not ephemeral. And therefore they have to be viewed in a more nuanced light.
For example something does not have to be a crime to come back and bite you. This could be a job losing issue, an issue that prevents you from running for public office, or even a blackmail issue. For example (and I'm not stating my position on this issue) opposing gay marriage used to in the US be an acceptable moral stance. According to what happened to Brenden Eich this is no longer the case and emails on the topic someone sent 10 years ago might come back to hurt them today.
"Ukraine’s Parliament Votes To Open Soviet-Era KGB Archives To Public" http://www.ibtimes.com/ukraines-parliament-votes-open-soviet...
In "The Internet With a Human Face", Maciej Cegłowski asks:
"What happens if Facebook goes out of business, like so many of the social networks that came before it? Or if Facebook gets acquired by a credit agency? How about if it gets acquired by Rupert Murdoch, or taken private by a hedge fund?
"What happens to all that data?"
That's just one of the problems we're facing.
Claiming that I don't personally feel the need for a fully enclosed, solid steel cubicle to get changed in doesn't mean I'm happy to get naked in public. I feel that whilst the changing cubicle you find at a public swimming pool wouldn't prevent a determined actor from invading your privacy it provides adequate privacy for me.
Yes, servers at Google can read my email - I'm willing to accept the risk of a Googler committing a fireable offence and going through my emails.
Google's been attacked by national intelligence agents. Notably from China, targeting emails of Tibetian activists. With potentially life-ending condequences.
Hackers and theives. Corporate takeovers. The NSA, or GRU, or Mossad, or MI6, ore any of the other various state intelligence agencies throughout the world. Drugs gangs throughout Central and South America. Rogue contractors have been known to walk out of Google with gigabytes of highly secure information. Oh, my error, that was the fucking National Security Agency.
If Google can read your email, anyone can. The only question is how the dice roll.
1. You could travel to another country where they arrest you for something unencrypted you did online in a country where it was legal. This has already happened. [1]
2. Your communications could become evidence in court that you "always had radical leanings." So while you're not convicted for what you did online, it still becomes evidence against you. I suspect this has already happened.
3. You could travel to another country where retroactive laws are allowed, and get caught because of something you said in the past in the US.
4. The US could eventually allow retroactive laws, and catch you for something you did before retroactive laws were allowed.
Note: these are just ways you could get in trouble with the law; not mentioned are things like your reputation being destroyed, death threats, identity theft, or malware due to lack of encryption. I also have not mentioned ways in which your friends could get in trouble because of something unencrypted you did online.
[1] http://www.cnn.com/2015/03/05/middleeast/american-arrested-i...
Video: http://youtu.be/pbF0sVdOjRw
[1] http://www.thoughtcrime.org/blog/gpg-and-me/
[2] http://www.forbes.com/sites/parmyolson/2013/08/09/e-mails-bi...
Yet another casualty of "software as a service". There could be better search tools on the client, but the fad for the last decade has been to push vendor lock-in and data mining instead of installable client apps. So now the full consequences of those choices are starting to be recognized.
You may want to reconsider either dedicating some sort of portable device to be your email that you carry with you, a multi-account system the separates private email from the the email you can access remotely, or resigning yourself and those communicate with to sending using only postcards (non-end-to-end-encrypted email).
Here is my concern with the WOT: it's not clear what signatures mean. It could mean "This guy can give out valid signatures" or "I verified that this guy's name is John Doe" or "This is the key used to sign Debian isos", but these are all implicit. Typically it's the first two which makes it hard to use PGP with pseudonyms. When you verify a signature in PGP you want the following chain:
o--I trust this guy's signatures-->o--I trust this guy's signatures-->o--I know this guy-->o
Other concerns: any way to rotate the master key would be nice. I wouldn't assume that my master key won't be compromised in the next 50 years .Then I would have to rebuild my whole WOT and revoke my previous master key (If I can). Key distributon should be decentralized.
Maybe I'm missing something, but this is my takeaway and I really tried to like PGP and gnupg. Maybe Google will solve some of these concerns on their interface but I wouldn't bet on it. I'm not surprised that PGP isn't widely used. I would really like a safe end-to-end encryption implementation that is easy to use.
Who's right?
User-unfriendliness ≠ "not meant for"
For the majority of people, this is too much. People should not be expected to spend time manually checking the signatures on a key, and should likewise not be expected to get signatures for their key. They should not have to worry about key revocation. If a solution is not as easy as email is at the moment, it's not a solution.
So, the problems that need to be solved in an automated manner:
Finding a public key, verifying it to be authentic beyond all reasonable doubt, making it so that a new user can be trusted. Revoking the key if the device is compromised.
These problems are not new - they've been around since PGP was invented. Yet, there is seemingly no compelling answer to them that doesn't involve bringing your passport to a key signing party.
All of the end-to-end encryption systems I've seen either have some complicated handshake process before one can communicate with another, or are unauthenticated.
So, anyone who argues for widespread end-to-end encrypted communication must provide evidence that such a system can actually be produced in a way that is totally transparent to the user.
Google's doing well with this software - they're massively reducing the barrier to entry for PGP; I just don't see why people are complaining about their preaching of security gospel.
The only reason I trust the source of an email by its "from" address is because of the history of correspondence with that person from that address. Yes, if it is compromised, I may not realize it right away, or I may (see: phishing emails from virus/malware infestations), but by and large it works as advertised.
Same thing with usernames in forums. There's a certain cred that is eventually attached to a username over time.
If I use the same public key to represent myself in all my communication "for a while", then there's implicit trust that it's me there, for the same reasons.
Key revocation is admittedly not as simple, if I want to continue to maintain my "trust balance" somehow. What happens if I switch email addresses? "Hi guys, this is my new email address." What if I was compromised and someone else did that? (Well, how often does that happen in real life?)
Perhaps you could keep one key super secret (and offline) and sign all new day-to-day keys with it. I don't know.
What I'm saying is- Treat it like email. Forget trying to centralize who owns what key. Forget trying to exercise absolute control over trust in a given key. The key(s) I use "most of the time" is "me". If I need to revoke it, I will suffer some in the short term, but I will quickly build my cred back up by using a new one.
If it was more widespread then perhaps we could centralize SOME third-party signing. Say I could go to a bank and they could sign my key saying "this key definitely belongs to lectrick", and it would work because the bank's public key is known-trusted.
In order for anyone to trust your key at all you need to make it available out of band.
This is because otherwise, your email provider could simply man-in-the-middle you (or them); and they have no way of working out.
The first time they email you, their key is already compromised. You then build up your trust for them; but you've trusted an attacker. The system is worse than useless.
This is worse than (say) TLS because TLS, you generally do not connect through a single access point. Email is far more centralised.
So, they need to get your key from outside the communication system, somehow.
Because there are at least two projects which address this: FAUST and Fair Anonymity:
http://arxiv.org/pdf/1412.4707v1.pdf
I very strongly encourage Eric to have his team look at these, or other options, and back the motherluving frell out of whatever seems viable.
Listening to his Re:publica conversation with EFF's Jillian York, the topic comes up, but best I can tell he doesn't know of these.
At 17m 50s in the presentation, the question of using Google services over Tor is raised.
That's ... an issue I've had some experience with:
"How to kill your Google account: Access it via Tor"
https://www.reddit.com/r/dredmorbius/comments/2w618r/how_to_...
First off, I totally get the abuse angle. Most of my specific complaint with my own experience wasn't over Google's challenge process to my attempted Tor access. Rather, it was over the company's policies and procedures for account recovery. Multi-factor auth is well and good, but I've yet to find a way to activate an option other than phone-based auth without providing Google with a phone number. Which for a number of valid reasons I cannot or will not do.
(Grosse states that "you should not even have to give us a phone number", and that there are internal debates on the subject. Yay.)
More specifically, the problem is that the question "Who are you?" is proving to be the most expensive operation in all of computing. Because you're fucked either way you get it wrong. Lock someone out when you should let 'em in, and you're fucked. Let someone in when you should've locked 'em out, and you're fucked. And all you get to look at is 1s and 0s on the wire.
I detail that in more length in this comment to my dreddit post:
https://www.reddit.com/r/dredmorbius/comments/2w618r/how_to_...
(I'll also note that Grosse specifically notes that PKI works great, ahem, Yonatan Zunger....)
So: first, Google's really got to revise and fix its account recovery processes.
But that identity thing: Grosse goes on at length noting that Tor exit nodes aggregate a lot of traffic activity, and that Google effectively relies strongly on IP address as an indicator of identity.
The fair, and anonymous, reputation systems mentioned above are specifically intended to work over Tor. Which is to say, people are tackling the problem. Nothing in Grosse's presentation gave any indication that he's aware of this fact. For sheer technical competence reasons, he should be.