News for hackers. Stuff that matters.
Re:Mozilla SSL policy bad for the Web by tptacek on Friday August 22, 2008 @08:24PM (#284359)
I missed this comment because it's 4 days old, and I waste too much time here so that's like 5 clicks back through my comment history. But here's the answer to that: the first time you connect to a site, your browser has no certificate to "remember". People are unwilling to accept a security model that doesn't protect their first access to B of A, especially when a security model that does is available.
Re:Mozilla SSL policy bad for the Web by mindslight on Saturday August 23, 2008 @07:30PM (#284893)
(And who knows if you'll get this. Interesting that HN fails at direct discussions)

The current usage model doesn't protect my initial access to BoA without me verifying that:

1. I've got a https connection

2. I haven't been redirected away to a rogue (SSL) site

You see the (https url)->(page retrieval) process as uniformly trusted (correct me if I'm wrong). I see stratification based on which third parties are doing the verification. Perhaps I'll have to wait for the emergence of a protocol explicitly designed for such things.

Re:Mozilla SSL policy bad for the Web by tptacek on Saturday September 20, 2008 @07:29PM (#310128)
(1) is why browsers have a little "key" icon.

(2) is not a real problem; your browser won't let you hit a "rogue" SSL site without clicking through a scary warning.