3 ms·
It's not really much of a comparison if you pick things like 'the security mechanism breaks in some way' and no similar failure modes of the 'no security' varia
by pvg 6y ago
It's not really much of a comparison if you pick things like 'the security mechanism breaks in some way' and no similar failure modes of the 'no security' variant. It's a serious usability problem if an insecure interaction gives you bogus information or if all your accounts are compromised because you use the same password everywhere.
- jedberg 6y agoBut that’s the point. Security introduces new failure modes that make usability worse. Again I’m not saying it’s bad, quite the opposite. I’m just saying we have to acknowledge it’s always a trade off.
- pvg 6y agoIf that's the point it seems like a particularly inaccurate and cherry-picky one. Security is not what's introducing the failure modes, the adversarial universe is. The no-security solutions have catastrophically worse usability in that reality. You're comparing the usability of things with security features with the usability of things without security in a hypothetical non-adversarial environment. I can posit a world in which security features never fail or introduce usability friction, that wouldn't be a useful starting point for a comparison either.
- deleted 6y ago[deleted]
- strogonoff 6y agoGeneralizing your point, introducing or expanding on any feature or functionality always implies proportional degradation of some other feature via new failure modes. (“Security feature” being a special case.) First, does that always hold true? Second—if we pretend it’s an axiom—careful and competent approach may allow to shift such degradation to aspects orthogonal to usability (instead of being perceivable by end user, failure modes could cause overhead, say, to maintenance or engineering teams).