On 24.09.2013 09:29, Chris Lauritzen wrote:
Now here is the new issue, when the client installs it should read in
the client.keys file when the service starts. If you read my orginal
question you can see that is was working except I was trying to embed
all the keys in a single file. The file that is copied now only has
the one key in the file. The agent is NOT reading in the client.keys
file now. If I open the file on the workstation and copy and paste it
imports the key correctly so I know that the client.keys file that is
being copied is correct. So why is it not reading in the file during
the install as it was before? The file is a standard txt file, it's
named correctly, the key that is in the file works if I manually add
it so what I am missing here?
Let me throw some things out there...
Perhaps this is an issue with CR/LF vs LF only?
Double extension with extensions hidden?
Are you adding the encoded representation of the key/hostname/agent ID
or does it look just like the entry that is on the manager?
Are there any messages in ossec.log?
Have you enabled debugging in internal_options.conf?
--
---
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.
