Re:Circumventing Deep Packet Inspection with Socat and Rot13
by jortr0n on Sunday February 27, 2022 @07:11AM
(#30487621)
The use of rot13 was just an amusement in this case given its vintage. Replacing rot13 with any other simple stdin/stdout transcoder should be simple to do via the socat invocation, eg base64, a sed replace command, gzip/gunzip, even an actual symmetric encryption protocol like AES, etc.
[ Parent
| on HN ]
Re:Circumventing Deep Packet Inspection with Socat and Rot13
by usr1106 on Sunday February 27, 2022 @07:32AM
(#30487778)
So if you contol both ends any kind of obfuscation will defeat deep packet inspection, as long as the same obfuscation is not widely used so that the inspection software can check for it.
But if you do not control both ends, let's say you want many customers or even the public to connect to your server that's not an option.
Re:Circumventing Deep Packet Inspection with Socat and Rot13
by Thiez on Sunday February 27, 2022 @10:12AM
(#30489117)
> as long as the same obfuscation is not widely used so that the inspection software can check for it.
I imagine there are only so many things you can detect with DPI before the network connection becomes (even more) prohibitively slow. And you can check for rot13 or base64 or common compression algorithms (but beware of zip bombs), but you can't check for properly encrypted data since it will appear as random bits.