On Apr 3, 2013 10:33 PM, "Jeremy Laidman" <user-71895fb2e44c@xymon.invalid>
wrote:
On 4 April 2013 12:55, Jeremy Laidman <user-71895fb2e44c@xymon.invalid> wrote:
You can do various VPN type things, such as using stunnel or ssh
tunnels (with key auth).
Also, this: http://lists.xymon.com/archive/2011-October/032866.html
In summary, the client-side can use curl to send a web "POST" message to
the Xymon server using an https:// type URL. Encryption solved. The
Xymon server can do whatever authentication is required (password,
client-side certificate, or none).
Just to clarify - on the Xymon server side it's Apache that handles the
client authentication, and there are many docs describing that. Xymon
itself is not involved in the authentication or encryption.
I also found that the xymoncgi handler sends back to the client any
client-local configuration that it finds, so it isn't just a one way street.
Ralph Mitchell