Skip to content

v1.1.3

Choose a tag to compare

@github-actions github-actions released this 31 Oct 22:17
· 2415 commits to master since this release
032f09e

KiviDB v1.1.3

This is a security release. Everyone on 1.1.x, and on the 1.2.0 release candidates, should upgrade. It fixes three vulnerabilities, all reported by @Parikalp-Bhardwaj:

  • GHSA-58x5-jq4h-h6rr: a TLS client that never finishes its handshake could hold up new connections (denial of service). maxclients is now enforced, and counts TLS clients from the start of their handshake.
  • GHSA-rhrj-pgm8-2686: a write to a key whose time to live had passed, but which active expiry had not yet removed, could be acknowledged and then lost.
  • GHSA-pjrr-m43f-m5g3: overlapping AOF checkpoints, or a crash at the wrong moment of one, could lose acknowledged writes or bring back deleted keys.

What's in 1.1.3

1.1.3 is a patch release of 1.1.0, made from 1.1.2. Besides the three fixes above:

  • A cluster master back without its data no longer wipes its replicas. A master that restarts empty (no persistence, or its files lost) tells its replicas not to copy its empty dataset.
  • Keys expire on replicas and in the AOF as they do on the master: the master now sends a DEL for every key it expires.
  • A master drops a replica that has gone silent, after repl-timeout.
  • Search: HNSW graphs are whole again after an AOF replay; a write in one database no longer touches another's indexes; expired keys, RENAME and RENAMENX keep the indexes up to date; FT.DROPINDEX index DD reaches replicas and the AOF as the documents it deleted; a missing index is reported in Redis 8's words.

CHANGELOG.md has the full list.

Before you upgrade

  • Replicas and clusters: upgrade the replicas first, then their master. A 1.1.2 replica does not understand a 1.1.3 master's "don't copy my empty dataset": once the master stops waiting, after 30 seconds, the replica syncs and drops its data, as 1.1.2 did. With the replicas on 1.1.3 first, nothing is lost.
  • maxclients is now enforced, and a config file may set it. Check it is high enough for your connection count (default 10000).
  • Data files from 1.1.0 to 1.1.2 load unchanged.

Binary variants

Each OS/architecture ships four binaries — pick the one that matches your needs:

Tarball suffix Features included When to use
(none) — Minimal / constrained environments
-lua Lua scripting EVAL / EVALSHA
-tls TLS termination Encrypted client connections
-full Lua + TLS Recommended general-purpose build

Full changelog: CHANGELOG.md

License: GNU Affero General Public License v3 (AGPL-3.0-only)

Code of conduct: CODE_OF_CONDUCT.md


Changes since v1.1.2:

What's Changed

Full Changelog: v1.1.2...v1.1.3