I don't believe this particular change materially improves security, since it isn't representing an end-to-end behaviour, but if it raises awareness and challenges mass surveillance then so much the better.
Personally I would like them to advocate for other necessary infrastructure advances and include, for non-IPv6-capable MTAs, an icon of a lurching monster that refuses to die.
Really that's bothers me greatly. Email is the example of a successful open protocol and by all means you should try and do it yourself. The less we are reliant on these giant companies the better and to abdicate email to google just because they've achieved critical mass is to wipe 25 years of internet history under the carpet.
Decentralization is good, not bad.
If installing and operating a compliant email server is too hard then we should make that easier, not push to get everybody to switch over to some corporation.
For comparison: the sidelining of XMPP by corporate interests was awfully disappointing; the centralisation of social networking feeds is downright heartbreaking. But none of that should put us off trying and trying again. Everyone with an interest in how the Internet protocol stack works in context should try running their own mail service, it's a fantastic and low-cost way to gain insight.
I'm frightened as well that google is taking over email. As long as people rely on web based email, there's no hope for actually encrypting email. TLS is nice, but really, it doesn't mean much. Your email is stored plain text on Google's servers anyways.
> everyone is going to switch, now
The article is pretty clear that gmail users can keep emailing others who don't support TLS or authentication; they will just now see an additional icon informing them of that condition. Nobody is being demanded to switch anything.
disclaimer: works for Google
What are the SSL certificate authority requirements?
We do not accept self-signed certificates. For a certificate to be valid it needs to chain up to a valid CA, like one in the Mozilla CA list.
As a recipient of all kinds of mail, I'm okay with that. I'd rather not see that unencrypted email than have it QUANTUM INSERT'd or whatever the Chinese equivalent is.
How many months is a "few"?
Without SPF/DKIM you can't be authenticated. Google is showing the user that they cannot verify the sender.
Without TLS email is sent in the clear. Google is showing the user that sensitive information will be visible when sent over the network.
You can run your server fine without this, but users will be warned that you're not following best practices.
It is not Gmail's fault that you're late to best practices.
Fixed that for you.
Well, except they are. Before, yes, they were just best practices. It was great if you had them but by no means required and didn't really impact your experience much if at all. With this switch, though, they became requirements to getting a "normal" experience in Gmail. Even having a warning is a degraded experience at this point.
If I ran a restaurant that provided extra services, that doesn't stop anyone else from opening a restaurant and provide similar levels of service.
Most people are not capable of running their own mail server. The convenience of services like Google, plus the risk of turning your mail box into a spam machine, vastly outweighs the downsides for most people.
> Most people are not capable of running their own mail server.
I think that is a big part of the problem. It should be relatively straightforward for someone who isn't a full-time email server administrator to setup a mail server correctly, but it's not. At least, it wasn't easy last time I tried it with Postfix and (iirc) Courier on Ubuntu. All the cryptography options are disabled by default and you have to spend a lot of time figuring out which ones should be turned on, where to stick the certificate files and how they should be formatted, how to get Courier and Postfix to talk to each other, etc...
Maybe there's an easy solution (besides "pay someone a monthly fee to manage this all for me") that I'm oblivious to, but it seemed like I was on a well-travelled path and it was a lot harder than it should have been.
http://arstechnica.com/information-technology/2014/02/how-to...
It shows how to set up SPF, DKIM, TLS, anti-spam filtering, Sieve, certificate-based authentication (I still haven't figured out how to do this with an iPhone), and so on. The only bolt-on it references but doesn't explore and I actually used is the Z-Push package to implement ActiveSync.
Do you encrypt the email on disk, or are they stored in plain text?
That, I think, is why the distribution managers don't make the default configurations a little more friendly/sane; most users aren't interested in installing a MTA to do anything but local delivery or smarthosting, and the people who are, are probably going to tweak the configs to death anyway, so it's not worth spending the time making it run well and securely straight out of the box.
It wouldn't be too hard to build a "mailserver in a box" with (say) Debian + Postfix + LetsEncrypt + BIND that you could stand up in an hour and be reasonably secure (and I'd be kinda surprised if that doesn't exist in some form already), but I don't know how many people would want it who aren't running mailservers already, and have the capability of doing so.
As with so many things in AWS, it's left up to the customer to inform AWS that a) you're running a mail server, b) what the purpose/use case is and c) request they configure the reverse lookup associated with the elastic IP you've allocated.
Source: I've been running public facing SMTP servers in EC2 for years with no issues.
https://aws.amazon.com/ses/faqs/
Still, unless you're running a server for a lot of people and you have tons of free time, you'll discover that it's more expensive than paying any of a bunch of people to take care of email for you.
Source: I work at FastMail
I'm having high hopes for Ubuntu 16.04 having a more recent version on board. Then I will try to switch from postfix again. Because as you've said, it's really straightforward to set up :)
Certs weren't free for business use until let's encrypt.
The pervasiveness of self-signed certificates for SMTP servers means that rejecting them would drop large amounts of email. STARTTLS is basically useful for thwarting passive collection of network traffic.
And if I can point your MX records there, via hijack or any other means, then I have a valid SSL certificate for receiving your email.
DKIM (which does not use a CA-issued certificate, it uses a public key published in DNS) is the technology that's intended to authenticate the email sender. It still wouldn't stop phishing attacks where the purported email sender is something like "[email protected]" though, and I don't know that there really is a good technical solution to that sort of thing.
Except everything you send and receive with your Gmail account is read by them and whatever government agencies anyway... So what's the point?
As a publicly traded company, it optimizes for GOOG. I have nothing against google, but I do think there is not enough skepticism our fear about them eating the whole stack.
* Receive gmail link from friend. * Use Chrome Browser as gateway to internet. * Use DNS to resolve that URL. * Site built on Angular and has new SPDY tags. * Libraries and Fonts served from CDN.
see something unclear at the url.
* use google search to find that link * google analytics beacons on both websites report your traffic.
I am concerned about the temptation for google to get up to something naughty. Luckily, as we now, it is an undisputed fact that our data is 100% safe with google and there are no organizations trying to actively attack their network or intercede. We also know, that compromising an individual (either an employee or a customer of google) is 100% impossible, never has happened, and never conceivably could happen. So it isn't a big deal.
So, is the issue you can't run a mailserver? Maybe. Maybe not.
You can't crawl many valuable sites now, unless you are google bot or a big vendor.
2 (3 if we count microsoft) companies can ban you from competing on mobile.
etc.
The slight losses in some areas to optimize for what google wants are small. In aggregate, they are wildly irresponsible for us to accept and we shoudlnt.
False. The voting stock are not traded, so the founders still have irrevocable rights to do whatever they please.
I meant, and you correctly pointed out was not clear or a particularly good way to verbalize, that google like most companies does what is best for itself. In googles case this is a combination of maximizing shareholder value and the vision various thoughtleaders in the company have.
I do not believe google is evil or bad.
I used to believe this.
I now believe that google is doing a lot of great things. However by achieving horizontal success in almost every area of such a powerful concept, it effects how the landscape develops and does cause many issues.
Even if we accept google is mostly good, and I mostly do, it is concerning. I hope that their voluntary meta structure will allow them to distribute fault tolerance and limit power consolidation.
As far as "I take issue with Google making the decision that everyone is going to switch, now and with out sufficient warning." it would be nice to get some notice on these changes no doubt but email is shit. It just is but we are stuck with it and at least google is attempting to drag it forward even if in doing so they leave some outdated servers/services behind. I'll take more secure of infinitely backwards compatible any day.
So email is shitty because providers fuck with it at the mailserver level (i think this is the case, and have heard that about providers) as it doesn't seem to be a problem at the view level.
So this is sort of the issue. We couldn't get consensus on this early on, so no one was able to force standardization, now only a few players have the ability to define standards but they all own large scale messaging channels outside of email.
edit: meant to say that browsers obviously view html and css3 is pretty good as well. We could probably standardize this enough to allow people to write emails in this format and embed imagery. We would not allow JS for obvious reasons, but sending cool emails would be fun and we could also add new features. I mean, the web has developed somewhat shittily, but adding a few new features outside of like the 16 original tags would be cool. Not sure what percentage of tags and attributes actually work, but then again, no one is...
I don't think it needs to be changed, really. It will stay this useful forever, probably.
What does that mean? A mail server can be a small perl script running on an embedded computer, or it can be a hundred front-end SMTP servers using a database as a back end datastore, there's no real infrastructure limit other than being able to make and receive connections on TCP port 25.
Measurably.
And as to "sufficient warning," sure, I can see that it would be nice to have given people like you more lead time. But then again, "GMail has always supported encryption in transit using TLS," and if you care about running your own email server, it feels to me like the writing has been on the wall for that one for a long time.
insecure mail server
I understand gmail's problem, and I don't have a better solution, but it's not just about insecure mail servers.
The DKIM authentication just requires a self-signed certificate. It doesn't need to be signed by a CA, I believe.
If there are any potential downsides to these things I'm interested to hear them, but it seems like they're generally agreed good practices, and hosting your own mail means you're signing up for some ongoing learning and maintenance anyway.
They pretty much had to do something to improve e-mail's abysmal confidentiality and authenticity, and at least they used open technologies which can be configured on a Debian VPS in a couple of hours using a HOWTO.
I've run my own email server for about 15 years. Every now and then I have to drop everything and implement some new technology that Gmail demands I have. Granted SPF, DMARC and TLS are all great technologies but I take issue with Google making the decision that everyone is going to switch, now and with out sufficient warning.