News for hackers. Stuff that matters.
Re:What's next Google? Dropping SMTP support? by UnoriginalGuy on Thursday May 16, 2013 @08:15AM (#5718162)
People keep banging on about "plain text, plain text" what is wrong with plain text? And what is wrong with SMTP?

Also email attachments can be binary encoded, base64 is just one option.

People are free to say that SMTP is "bad" or "broken" but they have to say exactly why that is the case. And "there are multiple different implementations" is a pretty poor justification, as a SMTP replacement would likely have the same issue (or worse).

Re:What's next Google? Dropping SMTP support? by dsr_ on Thursday May 16, 2013 @08:27AM (#5718222)
Multiple implementations are a strength. In fact, you won't see a good replacement for SMTP without multiple independent implementations.

(What will it look like? I would guess it will look like a two-part service, with one protocol for servers to talk to each other and another for clients to talk to servers. Servers will send tiny notifications to other servers that mail is available for their subscribers; then the receiving servers will retrieve the mail and cache it or store it for clients. This changes the spam problem fundamentally by requiring some persistence on the part of the sending server.)

Re:What's next Google? Dropping SMTP support? by laumars on Thursday May 16, 2013 @08:42AM (#5718287)
I would like to see the replacement of SMTP be designed along with a redesign of e-mails themselves as well.

I'd like to see the HTML that is supported in e-mails standardised, so there's no more issues about which clients will render what. I'd like to see the failure notices standardised, so that invalid e-mail addresses produce a standard "404-like" response, and so on.

The problem isn't so much that we have multiple implementations (I agree that can potentially be a strength). The problem is that there's very little that's consistent across the platforms.

Re:What's next Google? Dropping SMTP support? by npsimons on Thursday May 16, 2013 @10:37AM (#5718808)
I'd like to see the HTML that is supported in e-mails standardised

Count me out. It wasn't even two weeks ago that we had the story here about how The Onion was hacked because somebody clicked on an obfuscated HTML URL in email.

Re:What's next Google? Dropping SMTP support? by laumars on Thursday May 16, 2013 @02:08PM (#5720024)
While we're at it, let's all abandon HTML5 and have every browser doing their own thing, because people occasional fall for fake anti-virus ads. </sarcasm>

We can't stop social engineering like that - it's completely unavoidable. Which is why banks and payment providers regularly tell people not to follow links asking for bank details (etc). Yeah it sucks that The Onion got hacked that way, but your argument is doesn't fix that. Your argument is nothing more than cutting of your nose to spite your face (ie advocating an inconsistent platform for legitimate e-mails despite anchor tags working on every client already).

At least if e-mail was completely redesigned, then we could have banks provide a unique cert that hangs in the e-mail header and can support the authenticity claim of the sender (I'm sure there's ways around that idea I've just presented - but that was just off the top of my head. Any such design would obviously need to be thoroughly thought out)

Re:What's next Google? Dropping SMTP support? by raylu on Thursday May 16, 2013 @02:26PM (#5720167)
I think he's saying we should instead have text-only e-mail, because that's both standard and has a tiny attack surface.
Re:What's next Google? Dropping SMTP support? by laumars on Thursday May 16, 2013 @04:02PM (#5720809)
That doesn't fix anything either. Many clients make URLs clickable (even with text-only emails) and even if those clients didn't do that, someone will just copy and paste a URL into the address bar without looking. Given that the average user isn't an expert on domain names, it's not actually that hard to trick them into thinking that face.book.com isn't the same as facebook.com (and even those that are savvy enough to know the difference might misread the link and get fooled occasionally).

So like I said before, it's impossible to prevent social engineering.

Re:What's next Google? Dropping SMTP support? by raylu on Thursday May 16, 2013 @09:23PM (#5722240)
It's impossible to prevent all cases of social engineering with a purely technical solution, this is true. But that doesn't mean that we should disregard how much easier phishing attacks are with the advent of HTML mail. The goal here is not so much to stop social engineering dead in its tracks as to prevent some of the low-effort attacks that do happen.
Re:What's next Google? Dropping SMTP support? by laumars on Friday May 17, 2013 @07:26AM (#5723672)
But again, I refer you to my HTML5 example. Should we dumb down what websites are capable of rendering to prevent social engineering via the web?

What you're proposing is making things harder to work in the hope that human intelligence will prevail. But the problem is that these cases are where human intelligence has failed, so making things harder is just counter productive. And this is why you can't prevent social engineering from happening and why crippling technology and creating a worse user experience just to try catch a few fringe cases is just a backwards approach to handling the issue.

Instead what we need is methods in place to verify the authenticity of senders and better education to users so that don't make silly mistakes like installing random "virus scanners" from web ads or clicking strange URLs in e-mails (and the URLs themselves could be standardised. eg no sub-domains become clickable, to prevent people falling for face.book.com).

Re:What's next Google? Dropping SMTP support? by npsimons on Friday May 17, 2013 @01:29PM (#5725648)
But again, I refer you to my HTML5 example. Should we dumb down what websites are capable of rendering to prevent social engineering via the web?

Strawman; we're talking about email, where the combination of header forging and HTML mis-labeling are what's really dangerous, not web pages.

Re:What's next Google? Dropping SMTP support? by laumars on Friday May 17, 2013 @03:19PM (#5726236)
No, we're talking about social engineering and the principle is the same regardless of whether it's e-mail or websites. You take a page -be that of an e-mail or website- make it look legitimate, and get people to follow dodgy links or download dodgy programs. You see the same thing with Facebook malware as well (which spreads by social engineering). So maybe we should close Facebook apps down.....actually, I'd be in favour of that last point hehehe.

Claiming this is a straw man argument only demonstrates how unwilling you are to view this from another's perspective. At least I've listened to your arguments and come up with potential workarounds.

Re:What's next Google? Dropping SMTP support? by npsimons on Friday May 17, 2013 @01:27PM (#5725637)
The very fact that in HTML, a URL can look like a totally legitimate URL (the part between the &gt; and the &lt), and yet the "a href=" could be anything, makes HTML a bad idea for email, where headers can be easily forged. Sure people can (and do) copy and paste, but having it in HTML just makes it that much harder to check a URL. Don't even get me started about the "onmouseover" events that can further obscure the true href.
Re:What's next Google? Dropping SMTP support? by laumars on Friday May 17, 2013 @03:24PM (#5726258)
I'd already addressed the hypertext argument in this discussion somewhere. And that point is one of the reasons why I want HTML standardised in e-mails, so we can remove the potentially harmful things like that from the e-mail spec and make it simpler for developers to create formated content (that's also safe for the end users) which will be rendered correctly across the various clients.

So yes, I do agree with you that anchor tags are misused in phishing mail, but let's make that a reason to fix the specification rather than just ignoring the issues completely (or worse yet, officially removing HTML and then letting 3rd party developers invent their own broken specs and us ending back exactly where were are now).

As for your comment about mouse over events, you can't have Javascript in HTML e-mails so that point is completely irrelevant.

Re:What's next Google? Dropping SMTP support? by pyre on Thursday May 16, 2013 @02:37PM (#5720267)
You can't put the genie back in the bottle, unfortunately. Most people use clients that support HTML right now, and a new format that doesn't support some sort of rich text decoration (like HTML) isn't going to become popular enough to matter.
Re:What's next Google? Dropping SMTP support? by loup-vaillant on Thursday May 16, 2013 @05:37PM (#5721339)
A ridiculously cheap and powerful alternative to HTML (or any other static format for that matter), would be a bytecode format intended to be executed in a sandboxed virtual machine. Possibly something like Flash. That should give you all the bells and whistles you could possibly want with a document format.

Now, there still are some loose ends about various screen sizes, preferred font family and size, and of course allowing textual searches, but those parameters should be few enough to be less problematic that HTML is right now.

Re:What's next Google? Dropping SMTP support? by pyre on Friday May 17, 2013 @01:41AM (#5722867)
Really? Flash is more secure than HTML? Maybe we should just embed Java applets in emails? This still doesn't solve the "click a link that takes them elsewhere" issue that was brought up.
Re:What's next Google? Dropping SMTP support? by loup-vaillant on Friday May 17, 2013 @04:35AM (#5723265)
I did say "sandboxed", did I not? Just have your VM refuse to download anything before you click somewhere, and let it compute the relevant URL so it can show it to you the way Firefox does. If this is too harsh, then relax the restriction to only download to, say, the domain name of the current main URL. If this is still too harsh, then have a NoScript like button to relax restrictions manually, on a case by case basis.

It would disable any form of cross scripting by default, which in my opinion is a better state of affairs than HTML alone is right now (now, you can embed an external image in a web page, and bam, Facebook knows what you read).

Re:What's next Google? Dropping SMTP support? by jackinloadup on Thursday May 16, 2013 @01:53PM (#5719932)
I wonder if this could be fixed by displaying SSL certificate status next to email titles. Much like browsers do for websites. This way before you open or at least before you click anything in the email you can see the validity of the sender.
Re:What's next Google? Dropping SMTP support? by marssaxman on Thursday May 16, 2013 @02:05PM (#5720004)
I'd like to see it standardized that HTML is not supported in e-mails. Email worked fine before HTML came along and all the good email is still HTML-free... in my experience, only robots use HTML.
Re:What's next Google? Dropping SMTP support? by smnrchrds on Thursday May 16, 2013 @03:14PM (#5720505)
Plain text works fine in ASCII world. But if you ever need to read bi-directional emails like I did(e.g. Arabic text with some English words) you will understand the necessity of using HTML in email. Without proper formatting and markup that HTML offers, English words seem to fly around the text and end up at semi-random places.

I wish to see better support for non-ASCII plain text in email clients and web browsers, but until the HTML is all I have.

Re:What's next Google? Dropping SMTP support? by laumars on Thursday May 16, 2013 @02:23PM (#5720143)
While the vast majority of my correspondence is plain text formatted. I do think there's a place for markup. Something that can embed images, provide different formatting styling (bold, italics, underline, colours and perhaps even sizes). It's also nice having an option between serif, sans serif and monospaced typefaces.

Then there's hyperlinks. If not like HTML anchor tags were the hypertext is independent to the destination, but still some method to follow links in e-mails as a lot of online registration requires email activation that way.

So do think there is a benefit for some level of markup in e-mails.

Re:What's next Google? Dropping SMTP support? by wtbob on Thursday May 16, 2013 @02:37PM (#5720260)
> Then there's hyperlinks. If not like HTML anchor tags were the hypertext is independent to the destination, but still some method to follow links in e-mails as a lot of online registration requires email activation that way.

Well, there's the (IIRC) RFC-specified way to write URLs within '<URL:' and '>' pairs, e.g. <URL:https://news.ycombinator.com/>; (interestingly, the HN URL-finder doesn't support that).

Re:What's next Google? Dropping SMTP support? by laumars on Thursday May 16, 2013 @04:04PM (#5720822)
There's a million different ways it can be done. I only suggest a HTML-derived format because of familiarity.
Re:What's next Google? Dropping SMTP support? by saraid216 on Thursday May 16, 2013 @02:31PM (#5720210)
How come I didn't see this stuff come up when Google was all, "We are going to replace email with Wave!"
Re:What's next Google? Dropping SMTP support? by EvilLook on Thursday May 16, 2013 @08:52AM (#5718332)
>What will it look like? I would guess it will look like a two-part service, with one protocol for servers to talk to each other and another for clients to talk to servers.

So SMTP and POP3/IMAP?

>Servers will send tiny notifications to other servers that mail is available for their subscribers; then the receiving servers will retrieve the mail and cache it or store it for clients. This changes the spam problem fundamentally by requiring some persistence on the part of the sending server.

So NNTP?

Re:What's next Google? Dropping SMTP support? by pyre on Thursday May 16, 2013 @02:32PM (#5720224)

  | So SMTP and POP3/IMAP?
I think that the 'clients to talk to servers' part is referring to sending email, unless you think the webmail is the only way to send email. POP/IMAP are for reading email from the receiving server, not for sending out new emails.

  | So NNTP?
I was under the impression that most Usenet networks used UUCP.
Re:What's next Google? Dropping SMTP support? by ethomson on Thursday May 16, 2013 @05:47PM (#5721385)
> POP/IMAP are for reading email from the receiving server, not for sending out new emails.

They probably shouldn't be, though, there's an IMAP extension for submission.

> I was under the impression that most Usenet networks used UUCP.

No, NNTP. UUCP hasn't been used seriously for over a decade.

Yours, news.ycombinator.com!ethomson

Re:What's next Google? Dropping SMTP support? by pyre on Friday May 17, 2013 @01:20AM (#5722809)

  | No, NNTP. UUCP hasn't been used seriously for
  | over a decade.
Looked it up and it seems you are mostly[1] right. Some time ago, I picked up the notion that most large Usenet networks synced articles between each other using UUCP, but clients used NNTP to pull down articles for reading. Not being a very avid Usenet user, I just took this at face value (also not knowing much about UUCP, like the fact that it used Layer 1 or Layer 2 protocol prior to TCP/IP).

[1] According to Wikipedia, UUCP was still in use in 2006 for at least one software product.

Re:What's next Google? Dropping SMTP support? by claudius on Friday May 17, 2013 @03:35AM (#5723138)
Some people apparently use UUCP-over-SSH to get mails from their remote mailservers to their local ones, because, you know, fetchmail is evil or something.
Re:What's next Google? Dropping SMTP support? by EvilLook on Monday May 20, 2013 @07:41PM (#5740937)
Or because it allows them to have a disconnected SMTP server that receives mail. It would be the solution that I would use if I had a multi-user mail server on a network that only occasionally dialed up to the Internet to send/receive mail but was otherwise disconnected.
Re:What's next Google? Dropping SMTP support? by laumars on Thursday May 16, 2013 @08:27AM (#5718221)
> People keep banging on about "plain text, plain text" what is wrong with plain text?

Well it's not exactly secure, for one thing.

> Also email attachments can be binary encoded, base64 is just one option.

base64 is a method for encoding binary. You cannot send raw binary other ASCII - which is why base64 is used in SMTP.

> People are free to say that SMTP is "bad" or "broken" but they have to say exactly why that is the case.

Actually I have given a long list of reasons every time I've complained about SMTP[1][2]

[1] https://news.ycombinator.com/item?id=5510910 [2] https://news.ycombinator.com/item?id=5297472

Re:What's next Google? Dropping SMTP support? by UnoriginalGuy on Thursday May 16, 2013 @08:37AM (#5718269)
>Well it's not exactly secure, for one thing.

No more or less secure than HTTP/HTTPS. In fact exactly as secure as...

>base64 is a method for encoding binary. You cannot send raw binary other ASCII - which is why base64 is used in SMTP.

http://tools.ietf.org/html/rfc3030

http://tools.ietf.org/html/rfc2045

http://en.wikipedia.org/wiki/MIME#Content-Transfer-Encoding

>Actually I have given a long list of reasons every time I've complained about SMTP >https://news.ycombinator.com/item?id=5510910 https://news.ycombinator.com/item?id=5297472

Your list is full of misinformation.

- Base64 thing is nonsense. As already stated SMTP supports binary and has for a long time.

- SMTPS is fairly well supported. In fact I currently connect to nothing which lacks it, and my email client auto-selects it when setting up new connections. Most of the hosts as far as I know support SMTPS out-of-the-box.

- SMTP reply codes are standardised (http://www.ietf.org/rfc/rfc1893.txt)

- HTML is standardised.

- SMTP is not designed to be real-time. That is what IM is designed to provide.

Re:What's next Google? Dropping SMTP support? by laumars on Thursday May 16, 2013 @08:58AM (#5718360)
> No more or less secure than HTTP/HTTPS. In fact exactly as secure as...

HTTPS is end to end encryption. In the instances that SMTP traffic is encrypted, it's only node to node. So SMTPS is less secure than HTTPS.

> http://tools.ietf.org/html/rfc3030

It's still not /the/ standard though, just /a/ standard; and one that's not particularly well supported in my experience. Most of the SMTP servers I've dealt with have archived and transmitted binary content over base64.

> Your list is full of misinformation.

Please don't be rude. And to address your bullet points:

- already addressed the binary / base64 remark

- already addressed the SMTPS remark

- yes, but those response codes are rarely transmitted back up the stack (and when they are, with a horribly garbled error). I'm talking about rebuilding the entire stack - from client to server - so that users get meaningful responses.

- of course HTTP is standardised. I never said it wasn't. So please don't turn this into a dumb trolling match where you make shit up to win an argument.

- I know SMTP isn't designed to be real time. But there's absolutely no reason why e-mails shouldn't be real time in the modern world. Simply citing IM's as an argument misses the point. IM's are for conversations. Emails are for memos. There's no reason why memo's shouldn't be sent real time. In fact, Android's Gmail notifications are real time. Exchange pushes mail to Outlook clients in real time. There's no reason why real-time shouldn't be the standard for all e-mails. (note: we're not talking about real time character update. Just a standard system for pushing messages instead of the client periodically polling for updates).

Re:What's next Google? Dropping SMTP support? by UnoriginalGuy on Thursday May 16, 2013 @09:12AM (#5718422)
> HTTPS is end to end encryption. In the instances that SMTP traffic is encrypted, it's only node to node. So in this instance SMTPS is less secure than HTTPS.

Sorry, not following you. HTTPS and SMTPS are both end to end encryption schemes. In fact they both use SSL in a similar way to secure traffic.

> It's still not /the/ standard though, just /a/ standard; and one that's not particularly well supported in my experience.

Really? Strange. I transmit binary data every day over email and I've never had an issue with a recipient not receiving it.

Which mail server and version in particular are you having issues with?

In general almost all of the "big names" in mail servers support more than just base64 as standard.

> yes, but those response codes are rarely transmitted back up the stack

I'm looking in my mail server logs right now, and am seeing a response code from a third party server for every email we forward. Our mail server then determines what to do with each code, and I can manually add additional handlers (e.g. code XXX do THIS, code YYY do THAT).

> I know SMTP isn't designed to be real time. But there's absolutely no reason why e-mails shouldn't be real time in the modern world.

Cost is a reason. Delivery assurance is another (e.g. if it fails to deliver the first time, do you retry for hours or just give up?). The fact that some clients are still on slow/off-line connections is a very good reason (e.g. phones that come in and out of cellular range, people on dial-up, people out in the middle of nowhere who get internet for an hour once a week, etc).

Re:What's next Google? Dropping SMTP support? by laumars on Thursday May 16, 2013 @09:30AM (#5718499)
> Sorry, not following you. HTTPS and SMTPS are both end to end encryption schemes. In fact they both use SSL in a similar way to secure traffic.

Yeah sorry, I explained my point abysmally there. What I meant was e-mails are only encrypted on a node-to-node basis but obviously a proportion of that transport isn't over SMTP. (My complaints are about the entire e-mail stack where as you're focusing on just SMTP, so there may have been a degree of us talking past each other).

> I'm looking in my mail server logs right now, and am seeing a response code from a third party server for every email we forward. Our mail server then determines what to do with each code, and I can manually add additional handlers (e.g. code XXX do THIS, code YYY do THAT).

We're definitely talking past each here. I'm on about client side not server side. (I should have been more clear from the outset that my complaints are about the entire email stack rather than specifically against SMTP)

> Cost is a reason. Delivery assurance is another (e.g. if it fails to deliver the first time, do you retry for hours or just give up?). The fact that some clients are still on slow/off-line connections is a very good reason (e.g. phones that come in and out of cellular range, people on dial-up, people out in the middle of nowhere who get internet for an hour once a week, etc).

None of that is really an issue though. 1) we already have mail servers that retry for hours 2) we already have instant push mechanisms for e-mails on phones 3) you're actually reducing the network overhead by eliminating the POP3/IMAP handshakes every n minutes in favor of an idle TCP/IP connection with periodic pings.

> Really? Strange. I transmit binary data every day over email and I've never had an issue with a recipient not receiving it. Which mail server and version in particular are you having issues with?

Maybe the base64 conversion is happening at my end then. It's never caused an issue as such (we have the capacity to cope with base64), it was just one of many niggles with the mismatch of the whole ecosystem. But I'll happily concede that I was wrong about the binary point :) (I don't particularly want to announce to the world what software and versions we're running at work for reasons that I hope you appreciate)

Re:What's next Google? Dropping SMTP support? by jimbobimbo on Thursday May 16, 2013 @02:46PM (#5720341)
I think I follow your point about SMTP being secure only node-to-node, but doesn't S/MIME (PGP, etc.) solve the problem of security?
Re:What's next Google? Dropping SMTP support? by laumars on Thursday May 16, 2013 @04:08PM (#5720841)
Totally, but that's not standardised across the clients either (plus there's a few different competing solutions for e-mail encryption). This is why I want to redesign the entire stack - to ensure that such solutions are standard across the ecosystem and available by default.
Re:What's next Google? Dropping SMTP support? by popee on Thursday May 16, 2013 @10:54AM (#5718899)
> But there's absolutely no reason why e-mails shouldn't be real time in the modern world.

You should look at SIP. It's combination of HTTP,SMTP,... and is really great protocol for hackers and creative people. Bad side of SIP is that it's friking huge, but this is because there are lot of extensions (btw even IM is SIP extension).

Re:What's next Google? Dropping SMTP support? by jfb on Thursday May 16, 2013 @09:07AM (#5718397)
I'm interested in djb's IM2000 [1] proposal. Change the underlying model from a postal service one; adapt the infrastructure to the use cases. "Plain text" is not the problem with SMTP.

[1] http://cr.yp.to/im2000.html

Re:What's next Google? Dropping SMTP support? by freehunter on Thursday May 16, 2013 @08:39AM (#5718279)
>what is wrong with plain text?

Plain text means anyone can read your message while it's going over the wire. That person sitting next to you in the coffee shop? He's running a packet sniffer and is reading everything you send, because it's plain text.

-- edit: In information security, plaintext means unencrypted. That's true for SMTP, and that's what I'm referring to. Am I wrong?

Re:What's next Google? Dropping SMTP support? by npsimons on Thursday May 16, 2013 @10:46AM (#5718858)
That's true for SMTP, and that's what I'm referring to. Am I wrong?

You are making the same mistake other posters were making, confusing two different definitions of "plain text". The one we're talking about is ASCII versus some binary obfuscated format (such as MS Word). Both can be encrypted and made equally as secure. Plain text formats are much more amenable to grepping, grokking and manipulation; they make locking out competing implementations harder. See "Keep Knowledge in Plain Text": http://pragmatictips.com/20

In addition, most arguments about "space savings" are rendered moot by compression (which usually works better on plain text), the fact that binary formats in practice almost always take up more space for the same content (even when uncompressed), and most importantly, storage and bandwidth have rendered the size argument totally irrelevant.

Re:What's next Google? Dropping SMTP support? by UnoriginalGuy on Thursday May 16, 2013 @08:42AM (#5718286)
> Plain text means anyone can read your message while it's going over the wire.

Plain text is a style of encoding information (e.g. binary, XML, JSON, plain text, etc). Encryption determines if someone can intercept your message.

Something can be both plain text and secure, like HTTPS for one example.

Re:What's next Google? Dropping SMTP support? by freehunter on Thursday May 16, 2013 @09:02AM (#5718375)
Plaintext is also a way of saying unencrypted, which SMTP is. By default, SMTP is plain text and plaintext, but you can send SMTP over SSL to make it plain text and encrypted.

http://en.wikipedia.org/wiki/Plain_text

http://en.wikipedia.org/wiki/Plaintext

Re:What's next Google? Dropping SMTP support? by Osmium on Thursday May 16, 2013 @08:58AM (#5718361)
It's my understanding that people often use "plaintext" in contrast to "ciphertext", so it's not unreasonable for someone to read "plaintext" and think "unencrypted".
Re:What's next Google? Dropping SMTP support? by npsimons on Thursday May 16, 2013 @10:49AM (#5718873)
Except in a discussion such as this one, where we're explicitly talking about Google locking out competitors by replacing plain (ASCII) text protocols with proprietary binary ones.
Re:What's next Google? Dropping SMTP support? by laumars on Thursday May 16, 2013 @02:12PM (#5720053)
To be fair, this discussion is a huge tangent about e-mail protocols. So both definitions of plain text could be contextually valid.
Re:What's next Google? Dropping SMTP support? by daeken on Thursday May 16, 2013 @01:27PM (#5719760)
I've been trying to force myself to use "cleartext" instead of "plaintext" to alleviate this ambiguity. It's remarkably hard to do after so long, though.