stable-20170410

The main focus of this release is on security, with minor changes to service startup scripts and featuring an SELinux policy module for ktserver (supported out-of-the-box on RHEL/CentOS, but maybe usable on other Linux distributions as well).

Kyoto Tycoon's security model is based on serving clients on a internal network as, by design, it provides no authentication mechanism. The new SELinux policy module intends to prevent a malicious client from exploiting ktserver to attack other services on the same machine, or other machines on the same network. It's a safeguard against unknown security vulnerabilities.

Full list of changes:

• Added an SELinux policy module for ktserver and matching .rpm package (make rpm-selinux)
• Fix startup failure when the local machine's hostname isn't resolvable
• Fixed minor compilation warnings (bugs)
• Fixed minor documentation issues
• Added automatic log rotation to .deb and .rpm packages
• Log to journald on RHEL/CentOS 7 (.rpm package)
• Fixed minor issues with packaging and service startup scripts
• Speed up build on macOS and FreeBSD

snapshot-20151209

Production ready release with minor changes:

• Build with LZO support by default;
• Use systemd instead of sysv initscripts on CentOS 7;
• Other minor packaging fixes and improvements.

snapshot-20150317

Production ready release with minor changes:

• Read-only mode for memcached clients (better security for web frontends);
• Packaging fixes for Debian;
• New packaging for RHEL/CentOS (make rpm) and Arch Linux (make arch);
• Fix debug builds on MacOS X.

snapshot-20150131

Production ready release with platform support and packaging changes:

• List keys by prefix match or regex using the ktremotemgr tool;
• Fixes to enable builds on MacOS X and FreeBSD;
• make deb to create debian packages (including init scripts and unprivileged execution).

snapshot-20150102

Production ready release with a conservative set of changes:

• Fixes missing includes that break compilation with recent versions of gcc;
• Fixes several method return type mismatches that triggered compiler warnings;
• Global Makefile to produce a standard build for both components in a single step;
• Several build process improvements (configure scripts).