> On 9. 2. 2023, at 22:11, mart...@tildeslash.com wrote:
>
>
>
>> On 9. 2. 2023, at 20:22, sashk via This is the general mailing list for
>> monit wrote:
>>
>> Hi,
>>
>>> Google the error and solution. Either update SSL on the cable modem
>>> “server” if you can or modify Monit (the
> On 9. 2. 2023, at 20:22, sashk via This is the general mailing list for monit
> wrote:
>
> Hi,
>
>> Google the error and solution. Either update SSL on the cable modem “server”
>> if you can or modify Monit (the client) yourself.
>
>
> Upgrading ssl is not possible on cable modem,
Idézem/Quoting sashk via This is the general mailing list for monit
:
Hi,
Google the error and solution. Either update SSL on the cable modem
“server” if you can or modify Monit (the client) yourself.
Upgrading ssl is not possible on cable modem, therefore as I stated
in my original
list for monit
Subject: Re: ssl: unsafe legacy renegotiation
Hi,
> Google the error and solution. Either update SSL on the cable modem “server”
> if you can or modify Monit (the client) yourself.
Upgrading ssl is not possible on cable modem, therefore as I stated in my
original
Hi,
> Google the error and solution. Either update SSL on the cable modem “server”
> if you can or modify Monit (the client) yourself.
Upgrading ssl is not possible on cable modem, therefore as I stated in my
original email:
>> It seems re-configuring OpenSSL it is possible to do
Google the error and solution. Either update SSL on the cable modem “server” if
you can or modify Monit (the client) yourself.
> On 9 Feb 2023, at 14:29, sashk via This is the general mailing list for monit
> wrote:
>
> Hello,
>
> I have a very old device, which I cannot replace, but would
Hello,
I have a very old device, which I cannot replace, but would like to monitor. It
uses TLSv1 for SSL and I’d like to check that it is online by querying its
https port. I have following check:
check host cable_modem with address 192.168.1.1
if failed port 443 protocol https status =
