People have been saying that CAs are a bad idea since CAs were first proposed.

The problem is that those same people tend to disappear as soon as you ask "So what should we do instead?"

wolvoleo 2 hours ago | parent | next [-]

For starters, limit CAs to a specific scope. It's pretty insane a Chinese or Indian CA can certify websites in the Netherlands.

In the 90s vision of a truly globalised world that might have made sense but in today's geopolitical reality it's insane.

If this had been in place already, instead breaking the internet this would have been purely a regional issue.

▲

arccy 2 hours ago | parent [-]

oh no you want some trendy .in or other domain name? sorry can't use your favorite CA, got to use the crappy one that leaked keys

	▲	wolvoleo 2 hours ago \| parent [-]
		Well yeah, or have the website define which CA they use, and don't let any of the others certify it. Apparently there is already DANE for this but webbrowsers don't check it. Besides, there could be more CAs supporting .in of course. And it becomes a matter of responsibility to the local government. And national TLDs aren't meant to be trendy anyway. Many have restrictions on them to local businesses anyway, it would make sense to have the local domain authority have control over choosing CAs as well.

▲

VorpalWay 2 hours ago | parent | prev [-]

You could store the public key for each website in DNS. But now you moved the trust problem to DNSSEC. So far I haven't heard about issues like this for DNSSEC, but then again it is not a massive target currently.