Changeset 2238
- Timestamp:
- 08/29/08 00:09:32 (3 months ago)
- Files:
-
- psad/trunk/CREDITS (modified) (1 diff)
- psad/trunk/psad.8 (modified) (23 diffs)
Legend:
- Unmodified
- Added
- Removed
- Modified
- Copied
- Moved
psad/trunk/CREDITS
r2234 r2238 390 390 - Suggested moving dependencies into the deps/ directory to build a common 391 391 architecture for bundling the cipherdyne.org projects for Debian. 392 - Submitted patches for documentation fixes in various psad man pages. 392 393 393 394 Erik Heidt psad/trunk/psad.8
r2150 r2238 74 74 .B /var/log/psad/fwdata 75 75 is parsed for old scans, but any file can be specified through the use 76 of the --messages-file command line option. For example it might be useful76 of the \-\-messages-file command line option. For example it might be useful 77 77 to point psad at your 78 78 .B /var/log/messages … … 139 139 .BR \-m "\fR,\fP " \-\^\-messages-file\ \<file> 140 140 This option is used to specify the file that will be parsed in analysis 141 mode (see the --Analyze-msgs option). The default path is the psad141 mode (see the \-\-Analyze-msgs option). The default path is the psad 142 142 data file 143 143 .B /var/log/psad/fwdata. … … 187 187 .BR \-B ", " \-\^\-Benchmark 188 188 Run psad in benchmark mode. By default benchmark mode will simulate 189 a scan of 10,000 packets (see the --packets option) and then report189 a scan of 10,000 packets (see the \-\-packets option) and then report 190 190 the elapsed time. This is useful to see how fast psad can process 191 191 packets on a specific machine. … … 209 209 can be made to 210 210 override this path by specifying a different file on the command 211 line with the --config option.211 line with the \-\-config option. 212 212 .TP 213 213 .BR \-\^\-signatures\ \<signatures-file> … … 223 223 system. New signatures can be included and modifications to existing 224 224 signatures can be made to the signature file and psad will import 225 the changes upon receiving a HUP signal (see the --HUP command line225 the changes upon receiving a HUP signal (see the \-\-HUP command line 226 226 option) without having to restart the psad process. 227 227 .B psad … … 230 230 .TP 231 231 .BR \-e ", " \-\^\-email-analysis 232 Send alert emails when run in --Analyze-msgs mode. Depending on the size of233 the iptables logfile, using the --email-analysis option could extend the runtime232 Send alert emails when run in \-\-Analyze-msgs mode. Depending on the size of 233 the iptables logfile, using the \-\-email-analysis option could extend the runtime 234 234 of psad by quite a bit since normally both DNS and whois lookups will be issued 235 235 against each scanning IP address. As usual these lookups can be disabled with 236 the --no-rdns and --no-whois options respectively.236 the \-\-no-rdns and \-\-no-whois options respectively. 237 237 .TP 238 238 .BR \-w ", " \-\^\-whois-analysis 239 239 By default 240 240 .B psad 241 does not issue whois lookups when running in --Analyze-msgs mode. The242 --whois-analysis option will override this behavior (when run in analysis mode)241 does not issue whois lookups when running in \-\-Analyze-msgs mode. The 242 \-\-whois-analysis option will override this behavior (when run in analysis mode) 243 243 and instruct psad to issue whois lookups against IP addresses from which scans 244 244 or other suspect traffic has originated. … … 281 281 can be made to 282 282 override this path by specifying a different file on the command 283 line with the --fw-search option.283 line with the \-\-fw-search option. 284 284 .TP 285 285 .BR \-\^\-fw-list-auto … … 296 296 .B psad 297 297 will not delete the auto-generated iptables chains (see the IPT_AUTO_CHAIN 298 keywords in psad.conf) if the --Flush option is given. The --fw-del-chains298 keywords in psad.conf) if the \-\-Flush option is given. The \-\-fw-del-chains 299 299 option overrides this behavior and deletes the auto-blocking chains from a 300 300 running iptables firewall. … … 306 306 system. All IP addresses are removed from the resulting output, so it is 307 307 safe to post to the psad list, or communicate to others. This option is 308 most often used with --Dump-conf.308 most often used with \-\-Dump-conf. 309 309 .TP 310 310 .BR \-\^\-fw-block-ip\ \<ip> … … 375 375 a .gnu file by convention). Normally 376 376 .B psad builds all of the graphing directives based on various --gnuplot 377 command line arguments, but the --gnuplot-template switch allows you to377 command line arguments, but the \-\-gnuplot-template switch allows you to 378 378 override this behavior. 379 379 .TP … … 454 454 will write these message to 455 455 .B /var/log/psad/errs/fwerrorlog 456 by default. Passing the --no-ipt-errors option will make psad ignore456 by default. Passing the \-\-no-ipt-errors option will make psad ignore 457 457 all such erroneous firewall messages. 458 458 .TP 459 459 .BR \-\^\-no-whois 460 460 By default psad will issue a whois query against any IP from which 461 a scan has originated, but this can be disabled with the --no-whois461 a scan has originated, but this can be disabled with the \-\-no-whois 462 462 command line argument. 463 463 .TP … … 467 467 whether or not the firewall has a compatible configuration (i.e. 468 468 iptables has been configured to log packets). Passing the 469 --no-fwcheck or --log-server options will disable this check.469 \-\-no-fwcheck or \-\-log-server options will disable this check. 470 470 .TP 471 471 .BR \-\^\-no-auto-dl … … 492 492 By default psad will attempt to passively (i.e. without sending 493 493 any packets) fingerprint the remote operating system from which 494 a scan originates. Passing the --no-passive-os option will494 a scan originates. Passing the \-\-no-passive-os option will 495 495 disable this feature. 496 496 .TP … … 499 499 normally attempts to find the name associated with a 500 500 scanning IP address, but this feature can be disabled with 501 the --no-rdns command line argument.501 the \-\-no-rdns command line argument. 502 502 .TP 503 503 .BR \-\^\-no-kmsgsd … … 511 511 By default for iptables firewalls psad will determine whether 512 512 or not your machine is listening on a port for which a TCP 513 signature has been matched. Specifying --no-netstat513 signature has been matched. Specifying \-\-no-netstat 514 514 disables this feature. 515 515 .TP … … 531 531 employ to parse iptables messages. Using configuration directive within 532 532 this file, psad can be configured to parse all iptables messages or only 533 those that match specific log prefix strings (see the --log-prefix option533 those that match specific log prefix strings (see the \-\-log-prefix option 534 534 to iptables). 535 535 .RE … … 553 553 .B /etc/psad/snort_rules/*.rules 554 554 .RS 555 Snort rules files that are consulted by default unless the --no-snort-sids555 Snort rules files that are consulted by default unless the \-\-no-snort-sids 556 556 commmand line argument is given. 557 557 .RE … … 623 623 scan activity. However, if FW_SEARCH_ALL is set to "N", psad 624 624 will only parse those iptables log messages that match certain search 625 strings that appear in iptables logs with the --log-prefix option. This is625 strings that appear in iptables logs with the \-\-log-prefix option. This is 626 626 useful for restricting psad to only operate on specific iptables chains or 627 627 rules. The strings that will be searched for are defined with the FW_MSG_SEARCH … … 635 635 uses to identify iptables messages that should be parsed for scan activity. 636 636 These search strings should match the log prefix strings specified 637 in the iptables ruleset with the --log-prefix option, and the default value637 in the iptables ruleset with the \-\-log-prefix option, and the default value 638 638 for FW_MSG_SEARCH is "DROP". Note that 639 639 .B psad … … 796 796 to analyzing the 797 797 .B /var/log/messages 798 file if the -m option is not specified):798 file if the \-m option is not specified): 799 799 .PP 800 800 .B # psad -A -m <iptables logfile> … … 836 836 allowed should be blocked by the firewall ruleset. By default, psad attempts 837 837 to determine whether or not the firewall has been configured in this way. This 838 feature can be disabled with the --no-fwcheck or --log-server options. The839 --log-server option is useful if psad is running on a syslog logging server838 feature can be disabled with the \-\-no-fwcheck or \-\-log-server options. The 839 \-\-log-server option is useful if psad is running on a syslog logging server 840 840 that is separate from the firewall. For more information on compatible iptables 841 841 rulesets, see the … … 853 853 this file. 854 854 .SH DIAGNOSTICS 855 The --debug option can be used to display crucial information855 The \-\-debug option can be used to display crucial information 856 856 about the psad data structures on STDOUT as a scan generates firewall 857 log messages. --debug disables daemon mode execution.857 log messages. \-\-debug disables daemon mode execution. 858 858 .PP 859 859 Another more effective way to peer into the runtime execution of psad … … 886 886 always welcome as well. 887 887 .PP 888 -For iptables firewalls as of Linux kernel version 2.4.26, if the ip_conntrack888 For iptables firewalls as of Linux kernel version 2.4.26, if the ip_conntrack 889 889 module is loaded (or compiled into the kernel) and the firewall has been 890 890 configured to keep state of connections, occasionally packets that are supposed
