News for hackers. Stuff that matters.
Re:Ask HN: Why doesn't someone provide JS encrypted webmail by tptacek on Monday October 04, 2010 @01:54PM (#1756563)
There are two very good reasons why nobody should bother doing this.

First: browser Javascript is the most hostile possible environment in which to implement cryptography. From actual experience: you are better off trying to implement crypto in a microcontroller, with kilobyte-denominated space for code storage, no cold-start entropy, and a few tens of bytes headroom for negotiation. Seriously: do that first, before trying (and inevitably failing) to run the Javascript gauntlet[1].

Second: the security economics of mail drastically favor Google over anything you come up with, even if you're really good. That's because the cost of a sitewide compromise at Google is stratospheric. Google is maximally incented to protect their service and has the resources and mindshare to do so. Nobody cares about someone else's bespoke mail service. People who care about mail security but don't trust Google just VPN to a private mail server.

Incidentally, Fortune 500 companies grappled with this problem many moons ago, and have adopted the strategy of "things that need to be sent over secure email will instead send links to an HTTPS web application we run onsite and call 'secure email' even though it's really just 'private file sharing'". Which makes it doubly hard to pitch this as a product idea: most of your market has already rejected the model you're considering.

This is a bad startup idea. Avoid it.

[1] For starters: in browser JS, every function call can be redefined arbitrarily many times before it gets key material, web content is allowed to influence or even rewrite that code, there's no effective way to verify code before running it, code is pulled from multiple sites, there are browser "chrome"-level security flaws still being discovered, there's no solid secure random number generation, functions are timeable, there are solid implementations of only a very few algorithms, and what remains to be implement is hazard-prone. Writing crypto code in JS is hubris, pure and simple.

Re:Ask HN: Why doesn't someone provide JS encrypted webmail by appl3star on Tuesday October 05, 2010 @05:04AM (#1759062)
1) "Second: the security economics of mail drastically favor Google over anything you come up with, even if you're really good. That's because the cost of a sitewide compromise at Google is stratospheric."

This cannot be a serious answer: Some chinese already compromised Google a few months go - they stole the "Gaia" source code. Gaia is the single-sign-on solution for all Google services! Just because they are not unsing it on a big scale you can be sure there are people using exploits found from the source code to log into Google accounts.

2) "People who care about mail security but don't trust Google just VPN to a private mail server."

A VPN in general can be considered secure. If configured properly. Same for a mail server and for the network behind the VPN. In general: I would recommend a secure file sharing environment focussed on security & encryption. And no, that´s not Dropbox or box.net.

There is no better solution than GnuPG/PGP client encryption. Or at least partially secured file sharing offers like datainherit.com or cloudsafe.com

Re:Ask HN: Why doesn't someone provide JS encrypted webmail by tptacek on Tuesday October 05, 2010 @12:22PM (#1760314)
You think I trust "DSwiss.com", the "Swiss bank for information assets", founded in 2006, more than I trust the largest technology company in the world --- and presumably one of the top 10 spenders on software security worldwide?

Sorry, no, I don't. Maybe you can name one person I'd have heard of who has assessed any piece of their source code?

Re:Ask HN: Why doesn't someone provide JS encrypted webmail by astine on Monday October 04, 2010 @02:21PM (#1756669)
Not that I have any interest in this as a startup idea, but could the issues with Javascript be avoid by using Flash instead?
Re:Ask HN: Why doesn't someone provide JS encrypted webmail by tptacek on Monday October 04, 2010 @02:29PM (#1756704)
So basically, you'd be taking all the security obstacles of browser Javascript, and adding to them: having two Javascript interpreters to worry about, having an additional set of interfaces to secure (between the browser and the plugin), and never being entirely sure of what the attack surface for the Flash plugin is, since it's closed-source.

No, probably not a win.

Re:Ask HN: Why doesn't someone provide JS encrypted webmail by astine on Monday October 04, 2010 @02:37PM (#1756738)
Was wondering, thanks.
Re:Ask HN: Why doesn't someone provide JS encrypted webmail by baltcode on Monday October 04, 2010 @04:59PM (#1757407)
I'm not worried about Google being compromised by a third party. I believe my mail host should not be able to read my email. VPN to a private mail server is good, but I dont want to have to trust the mailserver. It might be a bad startup idea if you expect people to pay you 5 bucks a month for an account (may be). But what if it runs like any other mail host, and lives through advertising? Or better still is build on top of one the free vanilla insecure hosts?
Re:Ask HN: Why doesn't someone provide JS encrypted webmail by danudey on Monday October 04, 2010 @05:06PM (#1757435)
This is the sort of thing PGP was invented for. Why not use that?
Re:Ask HN: Why doesn't someone provide JS encrypted webmail by baltcode on Monday October 04, 2010 @05:00PM (#1757412)
I agree about the JS issues. Surely, someone out there has an idea to tackle these issues?