Kinguard not affected by latest libssh bug

I myself almost choked on my morning coffee yesterday when i read about the vulnerability in libssh, CVE-2018-10933.

SSH is the bread and butter for any safe and secure communication and file transfer in the Unix world and is of course available in the Kinguard platform to give the user total control over their device.

After some reading however the conclusion is that neither the source code in the Kinguard platform nor the external components that we utilize uses libssh. We use OpenSSH and Dropbear as means for ssh which both are unaffected by the bug.

Further more the Kinguard system does not even run a SSH server if the user have not enabled “Shell access” in the network admin interface.