Good morning, Henrik.
I was wondering if you would consider including a spec file in the
tarball, so that those of us running RPM based distro's (RHEL, CentOS,
etc) could use rpmbuild to build RPMs for our systems.
Thanks.
--
Mike Burger
http://www.bubbanfriends.org
"It's always suicide-mission this, save-the-planet that. No one ever just
stops by to say 'hi' anymore." --Colonel Jack O'Neill, SG1
From noon on August 3rd thru noon on August 4, I'll be participating in a
24 hour cycling relay to benefit the CASAs for Kids fund. If you'd care to
donate, please visit:
casasforkidsfund.kintera.org/faf/donorReg/donorPledge.asp?ievent=1051384&supId=388504798
Thank you.
Hi,
I have released version 4.3.12 of Xymon on Sourceforge, and it is
available from http://sourceforge.net/projects/xymon/files/Xymon/4.3.12/
. Due to a security bugfix, I strongly recommend upgrading to this
version.
Regards,
Henrik
NOTE: This release includes a bugfix for a security issue
in the xymond_history and xymond_rrd modules. A "drophost"
command sent to the xymond port (default: 1984) from an IP
listed in the --admin-senders access control list can be
used to delete files owned by the user running the xymond
daemon. This is allowed by default, so it is highly recommended
List of changes:
* rev 7211
* Security fix: Guard against directory traversal via hostname in
"drophost" commands
* Fix crash in xymongen introduced in 4.3.11
* SCO client: Fix overflow in memory calculation when >2 GB memory
* Fix so "include" and "directory" definitions in configuration files
now handle <tab> after the keyword
* Fix for the Xymon webpage menu on iPad's and Android (touch devices)
* Fix "drophost" handling so the host data directory is also cleared
* xymond_rrd now processes data from "clear" status messages
* Xymon clients now report the version number in the client data
* Linux clients now align "ps" output so it is more readable.
* New "generic" client message handler allows log/file monitoring from
systems that are not known to Xymon.
* The Xymon client now works if invoked with a relative path to the
runclient.sh script
* Other minor / internal bugfixes