PacketFence - BTS - PacketFence | |||||
| View Issue Details | |||||
| ID | Project | Category | View Status | Date Submitted | Last Update |
| 0000846 | PacketFence | public | 2009-11-12 10:31 | 2011-01-26 15:43 | |
| Reporter | obilodeau | ||||
| Assigned To | obilodeau | ||||
| Priority | high | Severity | minor | Reproducibility | sometimes |
| Status | closed | Resolution | fixed | ||
| Platform | OS | OS Version | |||
| Product Version | |||||
| Target Version | Fixed in Version | ||||
| fixed in git revision | |||||
| fixed in mtn revision | |||||
| Summary | 0000846: snort 2.8.5 doesn't have the -o command-line option | ||||
| Description | snort 2.8.5 doesn't have the -o command-line option, its not documented on the manpage Here's an extract of the README provided by snort (obviously out of date): -o Change the order in which the rules are applied to packets. Instead of being applied in the standard Alert->Pass->Log order, this will apply them in Pass->Alert->Log order, allowing people to avoid having to make huge BPF command line arguments to filter their alert rules. In snort's changelog: 2009-07-13 Ryan Jordan <ryan.jordan@sourcefire.com> [...] * snort.8: Removed obsolete option -o Now, do we really need it? I will need to test. | ||||
| Steps To Reproduce | |||||
| Additional Information | |||||
| Tags | No tags attached. | ||||
| Relationships | |||||
| Attached Files | |||||
| Issue History | |||||
| Date Modified | Username | Field | Change | ||
| 2009-11-12 10:31 | obilodeau | New Issue | |||
| 2009-11-12 10:31 | obilodeau | Status | new => assigned | ||
| 2009-11-12 10:31 | obilodeau | Assigned To | => obilodeau | ||
| 2009-11-19 14:42 | obilodeau | Note Added: 0001406 | |||
| 2009-11-19 14:42 | obilodeau | Status | assigned => resolved | ||
| 2009-11-19 14:42 | obilodeau | Resolution | open => fixed | ||
| 2011-01-26 15:43 | obilodeau | Status | resolved => closed | ||
| Notes | |||||
|
|
|||||
|
|
||||