Install from packages - #47
Merged
Merged
Conversation
Contributor
Author
|
I imagine @jtimberman will be happy with @tas50's changes in #52 and I'm keen to get this merged so I went ahead and rebased my changes on those. RuboCop still comes back clean. |
WUI is apparently unmaintained, unsupported and somewhat buggy. It also lacks up-to-date packages, probably for that reason. Alternatives such as LightSIEM have been suggested.
…instead of from source. Unfortunately there are no packages currently available for Arch. A missing or empty agent_server_ip attribute or client.keys file now prevents the service from attempting to start. See the README for details.
lsb-release is pre-installed on the Debian basebox but wasn't present on our production servers. Ohai uses it to set the node['lsb']['codename'] attribute.
Contributor
Author
|
Rebased again on the latest. The new Chef Specs die horribly as you might expect. I lack the time to deal with these and obviously they weren't an issue at the time I did the work. |
|
This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This addresses issue #44. This is obviously a big change and many of the attributes have now been removed as the installer is no longer used. Some of the changes were driven by my upcoming authd pull request so see that for further details. Despite all that, I tried to respect the existing recipes so that they would continue to do the same thing.
It's a shame that WUI had to go but I did not wish to waste effort on a dead project.
I have made use of the new yum-atomic cookbook but an existing problem with it will prevent these changes from working on Debian/Ubuntu until brianhays/yum-atomic#1 is fixed.
I had wanted to use the standalone "ossec" repository rather than the larger "atomic" one but the guy behind those told me that the former is no longer maintained.
I have prevented OSSEC from attempting to start under certain problematic scenarios. The most annoying of these, where an empty client.keys prevents the server from listening, has been raised in ossec/ossec-hids#662.
The DEB packages were missing the
ossec-batch-manager.plscript but I contacted the maintainer and he added it. However, he only added it to the server package. This is fine as things stand but if #42 gets merged, it'll need to be added to the agent package too. I have raised this in santiago-bassett/ossec-debian#1.The loss of some attributes may inconvenience some users so the next challenge is to make the configuration more attribute-driven. My initial aim was only to get the agents talking to the server so I'll take a short break from this and come back to it later.