News for hackers. Stuff that matters.
Re:Ask HN: It's 2011. Why is web encryption still coupled wi... by rdl on Saturday May 07, 2011 @05:12PM (#2524571)
Passive MITM is MUCH higher risk in the wild than active MITM. Active MITM also generally disrupts service or otherwise leaves evidence, so it eventually gets found; passive can go on forever.

The best thing would be opportunistic encryption, possibly using cached keys, for all traffic, combined with endpoint authentication (and maybe multiple levels, like SSL, SSL-EV, SSL-Real-Authentication-By-Humans) on top of that. Ideally, as close as possible as end to end, but if some security wasn't end to end, it might still be useful (i.e. various wireless and wired lan security protocols).

Re:Ask HN: It's 2011. Why is web encryption still coupled wi... by noduerme on Saturday May 07, 2011 @05:23PM (#2524601)
Don't forget too that most browsers will poll the user whether to accept a self-signed cert for the page the user's trying to load, but will simply fail when a service in that page tries to pull data over SSL from a domain with a self-signed cert. Flash, JS, etc.

I've been experimenting recently with spreading out databases geographically and letting clients (and to a lesser extent, DNS) do the bulk of the load balancing on data-intensive projects. I've gotten some great results. But right now, users would have to pre-visit a page at each data site and approve it in the browser. Or I could get a massively expensive wildcard cert and then make A-records for each of those sites, but I'd rather just access them straight through their IP addresses for speed.

The whole thing just irks me. All I want to do is make sure this line is encrypted between the end user and their ISP. That should be mandatory these days; but instead I have to pay for a cert on every single DB server?!

Re:Ask HN: It's 2011. Why is web encryption still coupled wi... by Locke1689 on Saturday May 07, 2011 @06:22PM (#2524734)
All I want to do is make sure this line is encrypted between the end user and their ISP

No you don't. What you want is to make the line secure. Encryption alone does not make a secure line. Period.