-
Notifications
You must be signed in to change notification settings - Fork 93
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
update min-version required #335
Conversation
Suricata-Update, and if its not looking at it, that was the idea. So if a ruleset had a |
We have no idea. |
Found this ticket https://redmine.openinfosecfoundation.org/issues/4930, I wonder if we should do that at some point as well? |
Indeed. |
No. We're talking about a change every few years, I think its fine in code. I'm just trying to decide whether we drop this in 1.3.x, or a new 1.4. I'm thinking of dropping it in 1.3.x. |
Are there risks to existing users? |
Only to users who are running Suricata-Update unbundled from Suricata, on a system with no Suricata in their PATH and are expecting to get 4.0.0 rules. So potentially. |
Seems low enough risk to me, so lets merge this. |
Merged via #339. Thanks! |
Jason, who are the consumers of
min-version
keys? https://github.com/OISF/suricata-intel-index/blob/master/index.yaml#L59Do we always know that these external sources do support the said min-versions even now?