Project

General

Profile

Actions
Copy link

Feature #2659

open
JS CT

Define the output rules file name.

Feature #2659: Define the output rules file name.

Added by Joel Samaroo almost 8 years ago. Updated 5 days ago.

Status:
Triaged
Priority:
Normal
Assignee:
Community Ticket
Target version:
TBD
Effort:
Difficulty:
Label:

Description

This issue is to track the ability to define the output rules file name from user input, so that the output file name isn’t always suricata.rules.

Related issues 1 (0 open — 1 closed)

Related to Suricata-Update - Bug #4215: Documented "--merged" option doesn't existClosedJason IshActions

JS Updated by Joel Samaroo almost 8 years ago Actions
Copy link
 #1

Created pull request #61 for the solution to be merged into master code:

sample output and expected behavior:

$ suricata-update --local ~/suricata_test/jsamaroo-custom.rules --disable-conf ~/suricata_test/disable o ~/suricata_test/ -r jsamaroo-custom.rules
7/11/2018 - 03:46:44 - <Warning> -- No suricata application binary found on path.
7/11/2018 -- 03:46:44 - <Info> -- Using default Suricata version of 4.0.0
7/11/2018 -- 03:46:44 - <Info> -- Loading /home/jsamaroo/suricata_test/disable. * 7/11/2018 -- 03:46:44 - <Info> -- Setting output rule filename to jsamaroo-custom.rules*
7/11/2018 -- 03:46:44 - <Warning> -- Cache directory does not exist and could not be created. /var/tmp will be used instead.
7/11/2018 -- 03:46:44 - <Info> -- No sources configured, will use Emerging Threats Open
7/11/2018 -- 03:46:44 - <Info> -- Checking https://rules.emergingthreats.net/open/suricata-4.0.0/emerging.rules.tar.gz.md5.
7/11/2018 -- 03:46:44 - <Info> -- Remote checksum has not changed. Not fetching.
7/11/2018 -- 03:46:44 - <Info> -- Loading local file /home/jsamaroo/suricata_test/jsamaroo-custom.rules
7/11/2018 -- 03:46:44 - <Warning> -- No distribution rule directory found.
7/11/2018 -- 03:46:44 - <Info> -- Ignoring file rules/emerging-deleted.rules
7/11/2018 -- 03:46:52 - <Info> -- Loaded 47514 rules.
7/11/2018 -- 03:46:52 - <Info> -- Disabled 1 rules.
7/11/2018 -- 03:46:52 - <Info> -- Enabled 0 rules.
7/11/2018 -- 03:46:52 - <Info> -- Modified 0 rules.
7/11/2018 -- 03:46:52 - <Info> -- Dropped 0 rules.
7/11/2018 -- 03:46:52 - <Info> -- Enabled 0 rules for flowbit dependencies.
7/11/2018 -- 03:46:52 - <Info> -- Backing up current rules. * 7/11/2018 -- 03:46:57 - <Info> -- Writing rules to /home/jsamaroo/suricata_test/jsamaroo-custom.rules: total: 23757; enabled: 18856; added: 0; removed 0; modified: 1*
7/11/2018 -- 03:46:58 - <Info> -- No suricata application binary found, skipping test.
7/11/2018 -- 03:46:58 - <Info> -- Done.

JS Updated by Joel Samaroo over 7 years ago Actions
Copy link
 #2

Removed ‘-r’ flag and added logic to check whether no-merge option was provided and if so would print an error and exit, since the —output-rule-filename would have no effect. A new PR was submitted in github to track this as #79.

SB Updated by Shivani Bhardwaj over 7 years ago Actions
Copy link
 #3

  • Status changed from New to Feedback
  • Target version set to TBD
  • Effort deleted (low)
  • Difficulty deleted (low)

JI Updated by Jason Ish over 5 years ago Actions
Copy link
 #5

  • Related to Bug #4215: Documented "--merged" option doesn't exist added

PA Updated by Philippe Antoine 20 days ago Actions
Copy link
 #6

  • Assignee changed from Joel Samaroo to Jason Ish

Jason, what do you want to do with this ? The suricata-update PR has been closed apparently

JI Updated by Jason Ish 5 days ago Actions
Copy link
 #7

  • Status changed from Feedback to Triaged
  • Assignee changed from Jason Ish to Community Ticket

I think I'd be open to this now, we've resolved the datasets, filemd5 lists, etc. Going to set back to community ticket.

Actions
Copy link

Also available in: PDF Atom