Skip to content
This repository has been archived by the owner. It is now read-only.

Setup should create snort.stats if user chooses Suricata #257

Closed
GoogleCodeExporter opened this issue Mar 24, 2015 · 4 comments
Closed

Setup should create snort.stats if user chooses Suricata #257

GoogleCodeExporter opened this issue Mar 24, 2015 · 4 comments

Comments

@GoogleCodeExporter
Copy link

@GoogleCodeExporter GoogleCodeExporter commented Mar 24, 2015

Otherwise, Sguil complains about missing snort.stats.

Original issue reported on code.google.com by doug.bu...@gmail.com on 13 Apr 2012 at 6:08

@GoogleCodeExporter
Copy link
Author

@GoogleCodeExporter GoogleCodeExporter commented Mar 24, 2015

Added the following to /usr/local/bin/setup:


    # Setup should create snort.stats to prevent Sguil errors when running Suricata
    touch /nsm/sensor_data/"$SENSORNAME"/snort.stats

Original comment by doug.bu...@gmail.com on 24 Apr 2012 at 8:50

  • Added labels: ****
  • Removed labels: ****

@GoogleCodeExporter
Copy link
Author

@GoogleCodeExporter GoogleCodeExporter commented Mar 24, 2015

Packaged:
/usr/bin/fpm -s dir -t deb -n securityonion-setup -v 20120425 
/usr/local/bin/setup

Original comment by doug.bu...@gmail.com on 24 Apr 2012 at 8:50

  • Added labels: ****
  • Removed labels: ****

@GoogleCodeExporter
Copy link
Author

@GoogleCodeExporter GoogleCodeExporter commented Mar 24, 2015

Tested by:
Scott Runnels
David Zawdie

Original comment by doug.bu...@gmail.com on 25 Apr 2012 at 10:05

  • Added labels: ****
  • Removed labels: ****

@GoogleCodeExporter
Copy link
Author

@GoogleCodeExporter GoogleCodeExporter commented Mar 24, 2015

Published:
http://securityonion.blogspot.com/2012/04/security-onion-20120425-now-available.
html

Original comment by doug.bu...@gmail.com on 25 Apr 2012 at 10:06

  • Changed state: Verified
  • Added labels: ****
  • Removed labels: ****

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
1 participant