<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN">
<html><body>
<p>Den 2014-03-17 13:17, Jeremy Laidman skrev:</p>
<blockquote type="cite" style="padding-left:5px; border-left:#1010ff 2px solid; margin-left:5px; width:100%">
<div dir="ltr">
<div class="gmail_extra">
<div class="gmail_quote">On 14 March 2014 21:42, Henrik Størner <span><<a href="mailto:henrik@hswn.dk">henrik@hswn.dk</a>></span> wrote:<br />
<blockquote class="gmail_quote" style="margin: 0px 0px 0px 0.8ex; border-left-width: 1px; border-left-color: #cccccc; border-left-style: solid; padding-left: 1ex;">It has been reported before, and is usually caused by the client data containing a very long list of network connections.</blockquote>
</div>
<br />Would it be possible to have xymond recognise a client data message that is compressed and auto-decompress it? Then we could insert a "| gzip" into xymonclient.sh, and many of these problems would go away.</div>
<div class="gmail_extra"> </div>
<div class="gmail_extra">In fact, having a generic pre-processor plug-in framework could be really useful beyond just compression. It could perform authentication to compare status/data message signatures against public keys (or certs) stored in a xymon-hostkeys.cfg file, and reject messages that don't match the signing key for a host. A plug-in for encryption would work the same way.</div>
<div class="gmail_extra"> </div>
</div>
</blockquote>
<div class="gmail_extra">Much of this has already been put into version 5: Compression, TLS encryption and client authentication via client SSL certificates. So it is pretty much done.</div>
<div class="gmail_extra"> </div>
<div class="gmail_extra">Regards,<br />Henrik</div>
<div class="gmail_extra"> </div>
<p> </p>
<div> </div>
</body></html>