2 ms·
| SSL (hopefully compromised minimally by non-SSL resources) There's a reason browsers don't display a secure logo on HTTPS connections with non-HTTPS resource
by mtogo 15y ago
| SSL (hopefully compromised minimally by non-SSL resources)
There's a reason browsers don't display a secure logo on HTTPS connections with non-HTTPS resources: it's not secure. It's not "minimally compromised", it's compromised. If my server has one service with one vulnerability, it's not "minimally vulnerable", it's vulnerable.
| I don't see any reason not to give the minority SSL
I was being sarcastic.
| Isn't it perfectly plausible that 80% of a site's users don't give a hoot about security, but 20% do?
It's not even about the users. The site should not ever be mixing HTTP with HTTPS on the same page.
- mquander 15y agoYeah, I agree with that. It's a stupid problem, but the problem exists, and until we are allowed to forcefully seize the servers of people who implement shitty software and fix the problems, it won't go away, so it's worth trying to do the best thing possible for users.