Project

General

Profile

Actions

Bug #4215

closed

Documented "--merged" option doesn't exist

Added by Michael Schem almost 4 years ago. Updated over 3 years ago.

Status:
Closed
Priority:
Normal
Assignee:
Target version:
Affected Versions:
Effort:
low
Difficulty:
low
Label:

Description

As documented https://suricata-update.readthedocs.io/en/1.2.0/update.html#cmdoption-merged

% suricata-update --merged="out.rules" 
usage: suricata-update [-h] <command> ...
suricata-update: error: unrecognized arguments: --merged=out.rules

Related issues 1 (1 open0 closed)

Related to Suricata-Update - Feature #2659: Define the output rules file name.FeedbackJoel SamarooActions
Actions #1

Updated by Michael Schem almost 4 years ago

If this features is added, it would be awesome if you could specify the path and the filename as that argument, which would mean --output wouldn't be needed.

Actions #2

Updated by Jason Ish almost 4 years ago

As merged is the default we should probably remove this command line option. There has been requests for a flag to set the output filename which maybe we should consider. I do worry that as rulesets start to use datasets (I hope they do) and other external files this will lead to confusion as someone may set the output filename to be /over/here/my.rules, but the associated files end up /somewhere/over/here/where/the/default/output/directory is.

Related issue: https://redmine.openinfosecfoundation.org/issues/2659

Actions #3

Updated by Jason Ish almost 4 years ago

  • Related to Feature #2659: Define the output rules file name. added
Actions #4

Updated by Jason Ish over 3 years ago

  • Status changed from New to Assigned
  • Assignee changed from Shivani Bhardwaj to Jason Ish
  • Target version set to 1.2.1
Actions #5

Updated by Jason Ish over 3 years ago

  • Status changed from Assigned to Closed

Merged as part of 1.2.1 by removing this option from the documentation: https://github.com/OISF/suricata-update/pull/271

If the option of specifying a filename is still desired, please followup on on issue #2659.

Actions

Also available in: Atom PDF