Skip to content
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

V4.8 / V4.9 / V5.0 var-ossec-etc-ossec-server.conf.j2 does not support offline update for cve #1258

Open
Wykx-Sama opened this issue Apr 12, 2024 · 2 comments

Comments

@Wykx-Sama
Copy link

Just noticed that the line for offline cve providing isn't in the template, i think it can be great to just leave it as a comment for ppl using Wazuh offline.

  <vulnerability-detection>
    <enabled>{{ wazuh_manager_config.vulnerability_detection.enabled }}</enabled>
    <indexer-status>{{ wazuh_manager_config.vulnerability_detection.indexer_status }}</indexer-status>
    <feed-update-interval>{{ wazuh_manager_config.vulnerability_detection.feed_update_interval }}</feed-update-interval>
  </vulnerability-detection>
@Wykx-Sama Wykx-Sama changed the title V4.8 / V4.9 var-ossec-etc-ossec-server.conf.j2 does not support offline update for cve V4.8 / V4.9 / V5.0 var-ossec-etc-ossec-server.conf.j2 does not support offline update for cve Apr 12, 2024
@Wykx-Sama
Copy link
Author

@

@Wykx-Sama Wykx-Sama closed this as not planned Won't fix, can't repro, duplicate, stale Apr 12, 2024
@Wykx-Sama Wykx-Sama reopened this Apr 12, 2024
@jonhattan
Copy link

It would be great to configure offline cve from a single role variable.

In the meantime, here's a proposal to allow overriding any template from the calling playbook. This enables to configure it or any other thing. #1337

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants