Skip to content

Several fixes for command wodle#504

Merged
chemamartinez merged 6 commits into3.2from
3.2-fix-command-win
Apr 5, 2018
Merged

Several fixes for command wodle#504
chemamartinez merged 6 commits into3.2from
3.2-fix-command-win

Conversation

@chemamartinez
Copy link
Contributor

This PR adds several fixes for the Command module including the following:

  • Fix control when checking if the remote commands are allowed to be executed by agents when a command is configured in the ossec.conf.

  • Added a timeout to wait for the command output.

  • Send command output messages to the manager to the correct agent queue.

@chemamartinez chemamartinez requested a review from vikman90 April 2, 2018 18:09
Copy link
Member

@vikman90 vikman90 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The remote command switch option fix is awesome.
The wm_sendmsg() function call is very convenient.

But the timeout would prevent the command wodle from executing long term processes or even daemons (undefined duration processes).

If the command timeout is desirable, it should be a per-command option, and allow infinite timeout.

@chemamartinez chemamartinez merged commit 79438a3 into 3.2 Apr 5, 2018
@vikman90 vikman90 deleted the 3.2-fix-command-win branch April 6, 2018 05:42
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

Successfully merging this pull request may close these issues.

2 participants