Dealing with some old networking code or how to discover that SOCKS5 is from 1996.
@lanodan@queer.hacktivis.me For first-gen corporate gateways, if I recall correctly from the RFC.
@lanodan@queer.hacktivis.me Proxy-based MITM is at least the honest kind. IDS/IPS and transparent proxies are the evil ones, especially passive IDS which is fundamentally insecure given the number of conntrack corner cases.
@lanodan@queer.hacktivis.me And thankfully it's what made the Great Firewall exploitable in the early 2010s.
Hackers: send a forged FIN with invalid checksum.
Great Firewall: Aha, the connection is gone! Stop conntrack.
Hackers: Aha, the Great Firewall is gone!
@lanodan@queer.hacktivis.me https://github.com/codegooglecom/scholarzhang/blob/master/west-chamber/extensions/xt_ZHANG.c#L81
@lanodan@queer.hacktivis.me The 2010s DNS spoofing code was also vulnerable to a buffer overflow exploit that caused OOB reads, leaking random traffic it was monitoring. If anything, the linked OP taught a generation of developers that the Great Firewall was just like any Big Corp/Gov software, full of bugs.
March 1996 in fact, kind of late but well happy 30 years socks5!