RTMPSUCK(1)

📦 version 2.6, in debian bookworm, debian trixie, ubuntu jammy, ubuntu noble, ubuntu questing, ubuntu resolute, ubuntu stonking

✨ RTMPSUCK(1) ✨

okay bestie, gather round, because we're talking about rtmpsuck — it's a transparent RTMP proxy and honestly? she's serving. this is a General Commands Manual page, section 1, and it's about to be your new obsession 💖

🌸 NAME 🌸

rtmpsuck — a transparent RTMP proxy 🦋

🎀 SYNOPSIS 🎀

rtmpsuck [-z]

that's it. that's the whole vibe. one optional flag, no notes ✨

💅 DESCRIPTION 💅

so here's the tea, bestie: rtmpsuck is a transparent RTMP proxy. she parks herself on port 1935 and just waits for RTMP sessions to roll up, but lowkey you can also redirect other ports to her if that's what you need. flexible queen 💁‍♀️

first she does an RTMP handshake with the client, then she sits there like "go ahead, send your connect request, i'm listening" and waits for the client to actually send that connect request. once it lands, she parses it, prints the connect parameters (yes, all of them, she's nosy in the best way), and then makes an outbound connection to the real RTMP server.

then she does an RTMP handshake with that server too — because she's polite like that — forwards the connect request over, and from that point on? she's just relaying packets back and forth between the two endpoints. main character energy, carrying the whole conversation fr fr 🔥

but wait, there's more ✨ she also keeps an eye out for a few packets that she treats ~specially~:

  • a play packet coming from the client gets parsed, so the playpath can be displayed 👀
  • she also handles SWF Verification requests from the server, and does it without forwarding them to the client. sneaky? maybe. iconic? absolutely 💅

and once the play command is processed, every single bit of audio/video data that comes rolling in from the server gets written to a file, and delivered back to the client. both. she can do both 🫶

now, the whole point of doing all this — instead of just using a sniffer like some people — is that since rtmpsuck has performed real handshakes with both the client and the server, she can negotiate whatever encryption keys are needed and therefore record the unencrypted data. no cap. that's the entire flex. 🔑

⭐ OPTIONS ⭐

  • -z — debug level output. and when we say debug level output, we mean extremely verbose. like, extremely. she will tell you everything. every last detail. buckle up 💀

🌈 SEE ALSO 🌈

👑 AUTHORS 👑

Andrej Stepanchuk, Howard Chu <http://rtmpdump.mplayerhq.hu>

ok so that's the whole page, bestie 💖 go forth, proxy transparently, and remember: she negotiated those keys herself so you get the unencrypted goods. periodt. 🎀✨

this was brought to you by RTMPDump v2.4, dated 2016-04-27 — vintage but still slaying, as always 🌸🦋

📦 where this page comes from