SSH.pm probe init is hard-coded to use 127.0.0.1

[FliesLikeABrick]

SSH.pm performs a hard-coded test against 127.0.0.1, presumably as a positive control to prove that ssh-keyscan operates as-expected and assuming that 127.0.0.1 is a known-good target to perform this test.

However, if smokeping is running in a container or other (hardened resource such as an Internet-facing slave/poller without SSH running, etc) environment that does not have openssh listening on 127.0.0.1 -- this test fails and Smokeping fails to start.

The documentation does not clarify the purpose of this test, so I am stating that assumption above about why this test is performed in the first place (as a blocking/mandatory part of Smokeping's daemon start-up)

Ideally:

• This startup test would be more configurable, either making it optional or allowing the target to be specified
• documentation would clarify the reason this test is performed on startup

[FliesLikeABrick]

Linked PR is open @oetiker - we would love to get this in upstream to avoid (or reduce the urgency of) creating an internal fork for our environment

[FliesLikeABrick]

PR is at #432