4 ms·
So how's about the browsers/root-programme operators simply stop bundling a root store? Instead, they could hive-off their root programme into an independent o
by denton-scratch 3y ago
So how's about the browsers/root-programme operators simply stop bundling a root store?
Instead, they could hive-off their root programme into an independent operation. Make it possible for the user to choose which root store they want. Does EIDAS mandate that browsers must provide a root store?
I occasionally pick over my root store(s) looking for government-run root-certs for governments I don't need to trust. But the names of those root certs aren't transparent; you have to research each one before you can safely distrust it.
Most government-run roots are only needed by citizens of that country; e.g. countries that issue government electronic ID that you need for things like voting (which isn't that common). So I'd choose a minimal root store, and then perhaps add back groups of certs, based on what my specific needs were. This could be managed through a slick UI.
It would be extra cool if browser manufacturers could restrict government-issued CAs to attesting subdomains of their CC-TLD. It's nuts that (e.g.) the Turkish and Hungarian governments can attest any domain they want.
- nerdbert 3y agoIf it doesn't exist already, surely this would be demand for this as a browser extension in the event that article 45 passes.
- denton-scratch 3y agoYeah, I've never tried to write a browser extension. I'd foul it up; but I'd be glad to help if anyone else wants to have a go. And it is needed now; there's no need to wait until this proposal goes through. The other side of the coin is that you'd then get a community of root-block lists (and root-add lists), like AdBlock lists.