> making it trusted locally That is precisely the problem. Most proprietary systems don't let you touch the trust store at all. Even "open" platforms like Andr

> making it trusted locally That is precisely the problem. Most proprietary systems don't let you touch the trust store at all. Even "open" platforms like Android have been locking down the ability to do anything to the trust store.[1] With that said, if we assume the user is only using Google Chrome and not an alternative browser, then typing "thisisunsafe" on the TLS error page should let one elide trust store modifications entirely. I cannot guarantee this is the case for HTTP/3 since the reverse proxies I deal with still use HTTP/2. [1] https://httptoolkit.com/blog/android-14-breaks-system-certificate-installation/ https://httptoolkit.com/blog/android-14-breaks-system-certif...