I've modified and compiled the latest 2.7.1 beta to accept or import the OSSEC Client Key's via the -i and -y patches contributed in 2010 https://groups.google.com/forum/#!msg/ossec-dev/jFBoWmZluLM/AWd-UhlK88kJ They had to be applied more by hand, but they work very well nonetheless. So now manage-agents.exe -y -i very-long-slash-archaic-and-seemingly-uneeded-key-here imports the key very well. I'm curious if anyone knows how to use NSIS to make decisions to import the key into the correct host when it's run based on a list or file with a list. I've created an exported list of hostnames and keys, but I have wild-card IP's, so I'd have to rely on hostname->key to determine which key to use. NSIS would (pseudo code) if hostname = array($hostname,$key) then exec "manage-agents.exe -y -i" $key \n This way I can package the static list I have (200+ hosts) into the nsis package so it can run manage-agents after the install and then even restart the service after the import. Anyone know NSIS language well enough for that? -rich
-- --- 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/groups/opt_out.
