News for hackers. Stuff that matters.

A comment on Why TLS 1.3 isn't in browsers yet. Parent comment

Re:Why TLS 1.3 isn't in browsers yet by Paul-ish on Wednesday December 27, 2017 @10:12PM (#16020051)
This is always the proposed answer whenever someone wants to introduce X potentially insecure API. It is lazy IMO. It requires the potentially uninformed user to make a critical decision. Plus, if we introduced every insecure-but-we-prompt API proposed, the user would be inundated with prompts and it would reduce their productivity.
[ Parent | on HN ]
Re:Why TLS 1.3 isn't in browsers yet by MertsA on Thursday December 28, 2017 @02:29AM (#16020841)
Forget impacting their productivity, we've already seen what happens when you defer these questions to the user. They always hit yes or okay. It's like it's not even there, people would view mindlessly accepting prompts like that's just how you're meant to use a computer.
[ Parent | on HN ]
Re:Why TLS 1.3 isn't in browsers yet by ascorbic on Thursday December 28, 2017 @03:03AM (#16020926)
More important than reducing productivity is the problem that prompt-overload conditions people to just blindly click accept.
[ Parent | on HN ]