Ah, gotcha. Still, with that being said, anyone know how the key is
actually generated in the first place? I could use that to bulk
generate my server side client.keys, and replicate that to my DC,
which I can then source for my log in script.
My issue is twofold: Many boxes to manage, and they c
Oh, and that's what I do, is just grab the line from client.keys and send it
over to the agent install script. I tried using the batch manager output, but
it doesn't work... Another reason sudo is needed on the Linux side (or changed
permissions).
--
James Pulver
LEPP Computer Group
Cornell Uni
I'm not sure about DHCP scopes - we pretty much use all static IPs except
laptops.
--
James Pulver
LEPP Computer Group
Cornell University
-Original Message-
From: ossec-list@googlegroups.com [mailto:ossec-list@googlegroups.com] On
Behalf Of Scott Mace
Sent: Friday, November 18, 2011 12
Thanks for the scripts, they look awesome, but as someone pointed out
in another thread, the ossec-batch-manager.pl script will not work
with dhcp scopes, and errors out with duplicate IP msg.
So I started looking at the client.keys file on the server, and it
looks like you can just extract the lin
IDK, what OS are you running Ossec server on? Mine is SL5 (basically RHEL5)...
maybe the output is different from mine? Try running plink manually from the
command line and see what it spits out - maybe something different from
"password:"?
Did you give the password with the space after the la
