Thanks Bill. This makes complete sense. In fact it is something I had
tested (searching through log for a match). I was curious if there is a way
to have OSSEC perform TLS version checks rather than introducing a
script/program that looks for TLS, writes to a log and then have OSSEC
parse
Easiest is to write a local rule using the Match directive Example
Found TLS version Lower than V1.2
You can use ossec-logtest to verify the results
was it helpful?
On Friday, May 4, 2018 at 7:23:08 PM UTC-4, DG wrote:
>
> Hi,
>
> I am a total newb to ossec so I apologize ahead of time. I
Hi folks,
just a follow-up on this thread (for google addicts ;):
There was quite a discussion on this ticket:
https://trac.prelude-ids.org/ticket/299
This was actually a problem between Ossec being compiled without compression
on the client side talking to the Prelude Manager which needed
on prelude-manager side i get the following error :
TLS error: A TLS packet with unexpected length was received and then
prelude-manager closes the connection.
On Jul 9, 8:57 pm, Ori [EMAIL PROTECTED] wrote:
Hello everybody,
I Recently installed OSSEC on OpenBSD 4.3 with prelude,
but i
