Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#28356 - [snort] Missing settings from default config
Attached to Project:
Community Packages
Opened by Ed Brindley (electrified) - Friday, 10 February 2012, 21:24 GMT
Last edited by Lukas Fleischer (lfleischer) - Monday, 05 March 2012, 20:48 GMT
Opened by Ed Brindley (electrified) - Friday, 10 February 2012, 21:24 GMT
Last edited by Lukas Fleischer (lfleischer) - Monday, 05 March 2012, 20:48 GMT
|
DetailsSnort 2.9.2.1
The latest VRT rulesets depend on various config settings that are missing from the shipped config file, this stops Snort from starting. I copied the following lines from the example config at: http://labs.snort.org/snort/2920/snort.conf to get it working # List of file data ports for file inspection portvar FILE_DATA_PORTS [$HTTP_PORTS,110,143] # List of GTP ports for GTP preprocessor portvar GTP_PORTS [2123,2152,3386] |
This task depends upon
Closed by Lukas Fleischer (lfleischer)
Monday, 05 March 2012, 20:48 GMT
Reason for closing: No response
Monday, 05 March 2012, 20:48 GMT
Reason for closing: No response
Comment by Lukas Fleischer (lfleischer) -
Saturday, 25 February 2012, 01:32 GMT
We ship the default config file upstream provides. Does it actually make sense to add config settings that are required by a specific rule set only?