Repository navigation
Replies: 1 comment
|
any ideas ? issues ? |
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Recently #173 was merged.
this feature works as follows (if enabled). and we need testers on High DPI networks (e.g. Russia, Iran, China, etc)
first, the idea:
the idea is, that on a single shared port (e.g.
:443) we listen for Both HTTP and EMAIL (IMAP, SMTP) protocols, and distinguish them using the packets ALPN or handshake HEADERS (CLIENT HELLO)network topology / handling:
the way we flag/handle them:
Testing it !! ( Important Part!!)
we have multiple layers of testing that you can do:
1. one command per property
-alpn imap* OK … IMAP4rev1 ready-alpn smtp220 … ESMTP-alpn h2-alpn, then typeGET / HTTP/1.1+ blank lineHTTP/1.1 200-alpn,-servername imap.mail.example.org* OK …-alpn, neutral SNI, typeEHLO x220 …-alpn imapon :993* OK …-alpn h2,http/1.1on :993Two ways to read a failure wrong: alert 120 on
-alpn h2is correct; and a connection reset instead of an alert means a middlebox, not the server.2. the harness (
tests/highdpi-smoke/)Same command from an unfiltered network and from the network under test — the pair is the result. It classifies why, which is the part
opensslandnccan't:TCP_TIMEOUT(blackholed port) vsTLS_RESET(killed after ClientHello — the DPI signature) vsTLS_ALPN_REFUSED(server's own alert) vsTLS_CERT_MISMATCHvsNO_DATA.Tier A walks every row of the table above. Tier B (
--tier b --repeat 20) is the interesting one for censorship: it fires seven ClientHello shapes at the same IP in the same minute and reports a kill rate per shape, so "theimaptoken itself is being punished" shows up asalpn-imapdying whilebrowser-likedoesn't. Tier C (--tier c, needsMADMAIL_SMOKE_USER/_PASS) does a real LOGIN, holds IDLE for minutes, and uploads 16 KB/512 KB to catch throttling and connection reaping.Toggle interaction is worth testing too, since it's new:
3. the official client
two accounts pinned to 443:
It configures both accounts, waits for
IMAP_INBOX_IDLE, sends a message across, then holds idle looking for error events.Manually in the Delta Chat app: advanced login, IMAP and SMTP both set to your mail host on port 443, security SSL/TLS. Delta Chat offers the ALPN tokens on non-standard ports automatically. The convincing version of this test is on a network that actually blocks 993/465 (or block them locally with a firewall rule) and confirming it still syncs and sends.
For Thunderbird/Apple Mail/K-9 you're testing signal 2, and they only work if the certificate covers
imap.<domain>/smtp.<domain>—madmail installorders a single-name cert, so without extra SANs that path fails for PKI reasons, not routing ones.tests/highdpi-smoke/server-setup.shprints the certbot command.Finally, the honest scope limit: ALPN tokens are in the cleartext ClientHello, so
imapon 443 is as visible to an inspecting middlebox as port 993 was. This defeats port blocking, not traffic analysis — and it needs L4 passthrough, so it can't work behind a TLS-terminating CDN.All reactions