wazuh-ansible VS wazuh-packages

To improve the context, I'd like to add the point I started to invest time. It's the Wazuh Ansible playbook that made me think about it. https://github.com/wazuh/wazuh-ansible

found something from GitHub discussions; was able to remove a pre-removal-script first:

Hello u/HerefortheLAN! As a workaround, you can install the agent from sources. The process is a little more involved than installing a package, but you can use this step-by-step guide: https://documentation.wazuh.com/current/deployment-options/wazuh-from-sources/wazuh-agent/index.html Please note that the issue that you mentioned is currently being worked on here, so a fix for this should be available relatively soon. Let us know if you have any problems with this. Regards!

Hello u/zmiramf The error message you are getting is because you are setting the IP value between <>, the IP must be in the format key: value On the other hand, please note that you are posting a public IP address and anyone viewing this post can see it, for security reasons you may want to edit the post to not show a public IP. I have created this issue to improve the config.yml file and avoid the use of such delimiters if it proceeds. As my coworker correctly comments, if you use the -a option it does not fail because the config.yml file is auto-generated, but if you want to use the functionality of generating the certificates independently, you must set the IP values as I have commented.

First of all, the Wazuh dashboard, created from Kibana, is an individual package, and as so, could be replaced by another package, and this could be not based on Kibana. Depending on the features you are missing in the default Wazuh dashboard, maybe it would be better to use a simpler solution. One options is to just create new visualizations from inside the installed dashboard. Another option would be creating a different package with the modifications you see fit. - For the first option, here you have a tutorial, as it has not yet been added to the documentation: https://github.com/wazuh/wazuh-documentation/issues/5511 - For the second option, all code to create the packages is located in https://github.com/wazuh/wazuh-packages. If none of this solutions is enough for your problem, the APIs you would need to control in your custom dashboards are the ones for the Wazuh server and the Wazuh indexer: - Wazuh API(accessed by port 55000): https://documentation.wazuh.com/current/user-manual/api/index.html#restful-api - Indexer API(accessed by port 9200): https://www.elastic.co/guide/en/elasticsearch/reference/current/rest-apis.html

We will investigate this issue, please stay tuned: https://github.com/wazuh/wazuh-packages/issues/2030

Upgrading to Ubuntu 22 includes some upgrades to the GLIBC library and dependencies that trigger an error in the Filebeat module. We included a fix into Filebeat configuration file to avoid seccomp usage in the Filebeat. Take a look at our Filebeat configuration template https://github.com/wazuh/wazuh-packages/blob/v4.3.10/unattended_installer/config/filebeat/filebeat.yml

We are working on creating an installation package for Alpine systems, we estimate that version 4.4.0 of Wazuh will already have this type of installation, you can follow the progress here: https://github.com/wazuh/wazuh-packages/pull/1715

So I created a PR to solve that issue: instead of rolling back whole wazuh-* installations, it just reverts to the backed up default state, then removes the backup.

We have detected this problem. We opened this issue to solve as soon as possible https://github.com/wazuh/wazuh-packages/issues/1694 Meanwhile, you could harden your installation with the proposed solution mentioned in the issue. I hope it helps you, don't hesitate to ask us if you have any doubts.