News for hackers. Stuff that matters.
Re:This is why sites choose to stay vulnerable to Firesheep by zmmmmm on Sunday November 07, 2010 @06:36PM (#1880728)
Any browser which doesn't warn about that in some way is essentially broken. (Yes, I see you cited Safari as one, but it must the the only one as far as I know - it does remove the padlock, but that seems pretty inadequate ...)

EDIT: I do take your point in that I think IE is the only browser that actually blocks the content. The others warn about it but still load it, by which time, of course, the damage is done.

Re:This is why sites choose to stay vulnerable to Firesheep by othermaciej on Monday November 08, 2010 @05:27AM (#1882019)
Our theory is that an SSL site including non-SSL content is no better or worse, in terms of security, than a completely non-SSL site.

What is the purpose of warning more prominently in the scenario described, than in the scenario where the user goes to a non-SSL site in the first page, or is redirected from an SSL login form to a non-SSL page?