pads.conf(8)

πŸ“¦
version 1.2 Β· 2 versions
, in fedora 43, fedora 44

πŸ’– pads.conf(8) πŸ’–

System Manager's Manual β€” pads.conf, bestie. Yes, the whole manual. Sit down, get comfy, we're doing config file lore today. πŸŽ€


✨ NAME ✨

pads.conf β€” it's the config file for pads, that's the whole vibe. 🌸


πŸ¦‹ DESCRIPTION πŸ¦‹

Okay so this page is literally the field guide to the pads(8) configuration file format. That's it. That's the job. πŸ“–

Two things get totally ignored, no thoughts head empty:

  • empty lines πŸ’€
  • any line that starts with # (those are your comments, babes) πŸŽ€

πŸ‘‘ PARAMETERS πŸ‘‘

Every knob you can turn, coming right up. No skips, no skimming, we're listing all of them. ✨

  • daemon [0/1] β€” this one decides whether the app dips into the background like a true background character. 0 = Disable, 1 = Enable. 🫢
  • pid_file <file> β€” the filename of the pads PID file. Heads up: if you're planning on living that daemon mode life, you should set this. Set it, bestie. πŸ™ˆ
  • sig_file <file> β€” an alternate location for the pads-signature-list file. ✨
  • mac_file <file> β€” an alternate location for the pads-ether-codes file. πŸ’…
  • user <username> β€” the name of the user pads will run as when it gets started as root. πŸ‘‘
  • group <groupname> β€” same energy: the name of the group pads will run as when started as root. 🧚
  • interface <interface> β€” the name of the interface PADS will listen to. Ears open, bestie. πŸ‘‚
  • filter <filter> β€” a libpcap filter applied to the PADS session. For example, if you wanna filter only SSH traffic, you'd specify "filter 'port 22'". πŸ“
  • network <network> β€” a comma separated list of networks to be monitored. Only assets found in these networks get recorded, so be picky. For example: "network 192.168.0.0/24,192.168.1.0/24,10.10.10.0/24". 🌈
  • output screen β€” this output plugin shows PADS data right on the screen. When you're using the configuration file, it defaults to off. πŸ“Ί
  • output csv: <filename> [readonly] β€” this output plugin writes PADS data to a CSV file. Optionally you can hand it a CSV filename as an argument. And if you want the file used only to populate the internal known assets list but never ever updated, then use the readonly option β€” that's the move when you've got a baseline and you wanna use it for intrusion detection. Iconic, honestly. πŸ”₯
  • output fifo: <filename> β€” this output plugin writes PADS data to a FIFO file. Optionally a FIFO filename can be specified as an argument. πŸ’œ
  • output prelude: <profilename> β€” this output plugin writes PADS data as IDMEF alerts via prelude. Optionally you can add a profile name if you want something different than the default of pads. ⭐

🌸 SEE ALSO 🌸

  • pads(8) β€” go read it, it's the moment. 🫢

Copyright (C) 2005 Matt Shelton <matt@mattshelton.com> β€” protect it, respect it. πŸŽ€


πŸ› BUGS πŸ›

Found a bug? Please send bug reports to the author. Don't be shy, they want to hear it. πŸ’Œ


✨ AUTHORS ✨

Matt Shelton <matt@mattshelton.com> β€” the main character who wrote all of this. πŸ‘‘


k bye bestie, this page is from 2005/06/17 and it's part of the System Manager's Manual, and yes it's still serving. πŸ’–βœ¨πŸŽ€πŸ¦‹πŸŒΈπŸ’…πŸ«Ά

πŸ“¦ where this page comes from