I'm coming back to using ossec after a couple of years at a job where we weren't using it, and I am remembering that in the old installation, we had a key compiled into the agent, so we deployed this agent to the target machines and no other agent config was needed.
In looking at the docs for 2.8.1, I'm not seeing that, instead I'm seeing a process of installing the binary, then generating a unique key for that agent on the server and deploying that unique key to the machine to be monitored. I realize that there are some advantages to every agent having a unique key, but there are also advantages to being able to have a completely sealed agent that can be deployed. Namely in an environment where a lot of VMs are created, it would be very nice to be able to have an agent as part of the VM template image instead of having a very manual step afterwords to install the agent. Am I just remembering things wrong about how we did things at my prior company? or is there a way to do this that I'm not seeing in the documentation? David Lang -- --- You received this message because you are subscribed to the Google Groups "ossec-list" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
