β BoringSSL Rejects JSSE TLS 1.3 HTTPS Connections When status_request Extension Is Disabled
BoringSSL is an SSL library deployed on some popular websites such as those run by Google/YouTube. An interoperability issue with the BoringSSL library can lead to a connection failure if TLSv1.3 is presented as the only enabled protocol in the ClientHello message and the certificate status_request extension is disabled. Enabling the certificate status_request extension by setting the jdk.tls.client.enableStatusRequestExtension system property to true will provide mitigation in such scenarios.
I would think some sort of browser caching, but...I've restarted the browser and used private modes. It's weird, but Safari works. I'm not concerned about it.
Issyk Kul is bigger, but Karakul Lake is closer to China and much closer to disputed territories.
The disputed territories in the west are already domestic and foreign issues.
I highly doubt China is going to take Kabul, but if you look at a map of Afghanistan, you'll see why the Wakhan corridor shouldn't likely be a hard get. China's west needs water. That part of Afghanistan has water. The unanswerable question tho is...will Beijing ever care?
wouldn't be surprised if there's a revolt in the west of the country, but I don't think we'll see Roman-style civil war.
A lot of that land in the west is disputed. The most likely scenario for Chinese involvement would be a Crimea-type seizure of the Wakhan Corridor Nature Refuge. Taking something like Tajikistan, or parts of it along with that would produce fewer headlines internationally.
If China cares about its west, then taking Issyk Kul would be strategic, but that would be a pretty big shift in priorities.
I can get to it in lynx, so not sure what is happening. Phone probably preferable to lynx but maybe I should set up vnc of ssh -X on my personal machine. Options