astelm/telemt
1
0
Fork 0
mirror of https://github.com/telemt/telemt.git synced 2026-11-01 05:12:02 +03:00
Code Issues Packages Projects Releases Wiki Activity

Bnd.addr/port details in KDF Docs

Browse Source
This commit is contained in:
Alexey
2026-10-27 19:36:22 +03:00
parent 8dd1938924
commit 4eef3d8608
3 changed files with 12 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/Architecture/Middle-end/KDF-internals/MIDDLE-END-KDF.en.md
+4
View File
@@ -39,3 +39,7 @@ The C-implementation provides **no mechanism to ignore the port**:
If a port is `0`, it is still incorporated into the KDF as `0`.
There is **no conditional logic to exclude ports**
### How does Telemt select a SOCKS KDF source?
A valid public SOCKS `BND.ADDR/BND.PORT` with a nonzero port supplies the complete KDF source tuple, ahead of configured/discovered NAT information. Its family must match the logical ME destination, independently of the TCP family used to reach SOCKS. IPv4-mapped IPv6 destinations count as IPv4 and require a native IPv4 BND tuple; IPv4-compatible destinations remain IPv6. `strict` rejects unavailable/invalid BND; `compat` retains the existing fallback. This does not change KDF fields, ports, SOCKS CONNECT destination encoding, public-address checks, or STUN behavior.