romenskiy2012/curl
1
0
Fork 0
mirror of https://github.com/curl/curl.git synced 2026-08-24 15:23:36 +03:00
Code Issues Projects Releases Packages Wiki Activity

tests: add basic ECH tests

Browse source 
Test 4000 and 4001

Closes #17192
This commit is contained in:
sftcd 2025-04-25 18:26:04 +01:00 • committed by Daniel Stenberg
parent e2a23d5d0d
commit 460ead61b6
No known key found for this signature in database
GPG key ID: 5CC908FDB71E12C2
7 changed files with 124 additions and 6 deletions
Download patch file Download diff file Expand all files Collapse all files

17
docs/ECH.md
View file

@ -476,3 +476,20 @@ and then reuse that in another invocation.
Both our OpenSSL fork and BoringSSL/AWS-LC have APIs for both controlling GREASE
and accessing and logging ``retry_configs``, it seems wolfSSL has neither.
### Testing ECH
We have yet to add a robust test setup for ECH as that requires an ECH-enabled
test server.
We have added two basic tests though, aiming to ensure that the client sends a
GREASE or real ECH extension when requested, and reacts correctly to the
failure of ECH in the latter case. (Given that `stunnel` has no ECH support.)
As with other similar tests, those tests require the `stunnel` tool be
installed. On Ubuntu `sudo apt install stunnel4` achieves that.
The test cases are:
- data/test4000: GREASE ECH, expected result: connection succeeds
- data/test4001: real ECH, connection fails with error 101 (ECH required)