I looked at the code an it's only using a plain socket. Does anyone have a
branch/fork of check_mk that allows the check_mk check on 6556 to be via SSL?
(I.e. proxied through stunnel in this case.)
If not, then I'll probably have to do it for a client requirement.
(HIPAA compliance sadly).
···
--
Allan Bailey
zirpubolci@gmail.com
There are 2 hard problems in computer science:
caching, naming, off-by-1 errors.
Follow up to my own question: someone on IRC pointed me to
https://mathias-kettner.de/checkmk_datasource_programs.html
So I'll try using that and stunnel.
cheers
-a
···
On Thu, Feb 19, 2015 at 8:32 AM, allan bailey <zirpubolci@gmail.com> wrote:
I looked at the code an it's only using a plain socket. Does anyone have a
branch/fork of check_mk that allows the check_mk check on 6556 to be via SSL?
(I.e. proxied through stunnel in this case.)
If not, then I'll probably have to do it for a client requirement.
(HIPAA compliance sadly).
--
Allan Bailey
zirpubolci@gmail.com
There are 2 hard problems in computer science:
caching, naming, off-by-1 errors.
--
Allan Bailey
zirpubolci@gmail.com
There are 2 hard problems in computer science:
caching, naming, off-by-1 errors.