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

Binary "update_ruleset" misbehaviour when canceling the update. #390

Open
jm404 opened this issue May 8, 2019 · 0 comments
Open

Binary "update_ruleset" misbehaviour when canceling the update. #390

jm404 opened this issue May 8, 2019 · 0 comments

Comments

@jm404
Copy link

jm404 commented May 8, 2019

Hi team!

I've noticed an weird behaviour when canceling the update of the rules using /var/ossec/bin/update_ruleset.

Context:

  • OS: Ubuntu 16.04
  • Clean installation of Wazuh Manager 3.9 (Revision: 3918) using DEB packages.

Problem:

After executing /var/ossec/bin/update_ruleset -b 3.9 and the message "Ossec requires a restart to apply updates. Do you want to restart OSSEC now? As I understood, when rejecting, the update aborts. But the update is applied and OSSEC is not restarted. This could cause confussion since lot of people could understand that the script is asking for verification in order to update, not verification to restart OSSEC.

IMHO, there should a confirmation in order to update ruleset since this could cause an unwanted update.

issue_core

Steps to reproduce:

  • Install Wazuh Manager 3.9 from deb packages.
  • Execute /var/ossec/bin/update_ruleset -b 3.9

Regards!

Jose

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

No branches or pull requests

3 participants