TCPXTRACT(1)

πŸ’– TCPXTRACT πŸ’–

okay bestie, welcome to the tcpxtract page β€” manual section 1, user commands, iykyk πŸ’…


✨ NAME ✨

tcpxtract β€” extract files from captured network packets πŸ¦‹

like... it goes through your packet captures and pulls actual files out of them. main character energy fr fr.


🌸 SYNOPSIS 🌸

tcpxtract [OPTIONS] [[-d <DEVICE>] [-f <FILE>]]

that's it, that's the whole vibe. options first, then you pick your source: a device, a file, or both in brackets like the original says. πŸŽ€


🌈 DESCRIPTION 🌈

πŸ’œ Valid options include:

  • --file, -f <FILE> β€” use this to specify an input capture file instead of a device. like, you already have the pcap sitting there? point at it. πŸ“
  • --device, -d <DEVICE> β€” use this to specify an input device (i.e. eth0). live capture hours, we're listening straight off the wire. πŸ”₯
  • --config, -c <FILE> β€” use FILE as the config file. your settings, your rules, no cap. βš™οΈ
  • --output, -o <DIRECTORY> β€” dump files to DIRECTORY instead of current directory. bc letting everything explode into your cwd is giving chaos πŸ’€
  • --version, -v β€” display the version number of this program. short, sweet, iconic. ⭐
  • --help, -h β€” display this lovely screen. and yes, it is lovely, thank you for noticing 🫢

ngl bestie, that's genuinely every single option on this page. no secret flags hiding, no deleted lore. we keep it πŸ’―

so anyway β€” this was tcpxtract v1.0.1, dated October 2005, living in section 1 of the manual like the little legend it is. mwah πŸ’‹ periodt. πŸŽ€βœ¨