3 ms·
The key exchange and identification for encrypted X is always the hard part. For encrypted SNI, keys are expected to be published via DNS, which GFW is happy t
by toast0 7y ago
The key exchange and identification for encrypted X is always the hard part.
For encrypted SNI, keys are expected to be published via DNS, which GFW is happy to disrupt.
Once you get a key, you have to send the key identifier in the clear (otherwise, the service doesn't know how to decrypt; unless you want to just do trial decryption with all available keys and hope that doesn't use too much CPU); the key identifier becomes the enforcement target at this point, unless you're on a host that shares ESNI keys among the many sites it hosts and is not acceptable collateral damage.