Project

General

Profile

Actions
Copy link

Support #3407

closed

Exclusion of source after removal from update.yaml

Added by Tiago F. about 5 years ago. Updated about 5 years ago.

Status:
Closed
Priority:
Normal
Assignee:
Shivani Bhardwaj
Affected Versions:
1.1.0
Label:

Description

How to reproduce:

Add

sources:
- A
- B
- C

Run suricata-update.

Edit update.yaml and remove "B". On next run, suricata-update will still fetch the removed (from update.yaml) source.

Expected behavior: suricata-update should consider entries that were removed from update.yaml as sources that should be removed/disabled.

Actions
Copy link
 #1

Updated by Jason Ish about 5 years ago

Can you run the 'list-enabled-sources' command? Maybe the same source was added/enabled with the add-source or enable-source command which does not store its configuration in update.yaml.

Actions
Copy link
 #2

Updated by Tiago F. about 5 years ago

Jason Ish wrote:

Can you run the 'list-enabled-sources' command? Maybe the same source was added/enabled with the add-source or enable-source command which does not store its configuration in update.yaml.

Hey Jason,

That was exactly it. I incorrectly assumed update.yaml was going to take precedence over everything, but like you mentioned, as soon as I listed the sources, I was given sources from both locations (update.yaml and suricata-update itself).

Thank you!

Actions
Copy link
 #3

Updated by Shivani Bhardwaj about 5 years ago

  • Tracker changed from Bug to Support
  • Status changed from New to Closed
Actions
Copy link

Also available in: Atom PDF