-
Notifications
You must be signed in to change notification settings - Fork 187
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
Agent deploy command for macOS #5466
Labels
Comments
2 tasks
Hi @gdiazlo , As part of wazuh/wazuh-packages#2205 implementation, echo -e 'WAZUH_MANAGER="192.168.1.10"\nWAZUH_AGENT_GROUP="default"' > /tmp/wazuh_envs Old environment variables should
|
This was
linked to
pull requests
May 23, 2023
6 tasks
This was
linked to
pull requests
May 23, 2023
6 tasks
6 tasks
6 tasks
6 tasks
6 tasks
UpdateDue to some optimizations in terms of usability and macOS availability of certain commands, the final specs about CLI installation command are
Examples: sudo echo "WAZUH_MANAGER='1.1.1.1' && WAZUH_MANAGER_PORT='7777' && WAZUH_PROTOCOL='udp' && WAZUH_REGISTRATION_SERVER='2.2.2.2' && WAZUH_REGISTRATION_PORT='8888' && WAZUH_REGISTRATION_PASSWORD='password' && WAZUH_KEEP_ALIVE_INTERVAL='10' && WAZUH_TIME_RECONNECT='10' && WAZUH_REGISTRATION_CA='/Library/Ossec/etc/testsslmanager.cert' && WAZUH_REGISTRATION_CERTIFICATE='/Library/Ossec/etc/testsslmanager.cert' && WAZUH_REGISTRATION_KEY='/Library/Ossec/etc/testsslmanager.key' && WAZUH_AGENT_NAME='test-agent' && WAZUH_AGENT_GROUP='test-group' && ENROLLMENT_DELAY='10'" > /tmp/wazuh_envs && sudo installer -pkg wazuh-agent-4.4.3-0.commitb384726.pkg -target / |
6 tasks
4 tasks
This was referenced Sep 12, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Description
The command to start the agent in macOS should be run by root, so we need to add sudo as part of the command.
The command
/Library/Ossec/bin/wazuh-control start
should be
sudo /Library/Ossec/bin/wazuh-control start
Also, the package name is going to be updated. We must update the installation command with the new name when it is available.
The text was updated successfully, but these errors were encountered: