Redis: Quietly Failing Configs Get a Voice
Today's changes center on making Redis speak up when configuration values are misleading or dangerous by default — from TLS peer name wildcards to memory limits that silently vanish — while a separate cluster refactor simplifies ownership of background trim jobs.
Duration: PT2M49S
Episode overview
This episode is a short developer briefing from Redis.
It explains recent repository work in plain language.
- Show: Redis
- Published: 2026-08-28T13:14:12Z
- Audio duration: PT2M49S
Transcript excerpt
This excerpt keeps the crawler page concise. Listen to the episode or use the RSS feed for the full update.
Good morning. It's August 28th, 2026, and this is your Redis developer briefing.
The clearest thread running through today's activity is Redis getting more vocal about configuration values that look fine but quietly do the wrong thing.
Start with PR 15684, from hristostaykov-del. A `tls-expected-peer-name` entry starting with a dot isn't a hostname to OpenSSL — it's a parent domain, matching any subdomain at any depth. Configure `.com` and you've effectively accepted almost any signed certificate. That behavior already existed; this PR just makes…
PR 15720, from jmsmg, follows the same instinct in a different spot. A `maxmemory` value with no digits — say the number got dropped and you're left with just "gb" — parses as zero, which means no memory limit at all, with no error. Meanwhile a typo like "bla" gets properly rejected. This PR keeps the old parsing…
Both PRs share a philosophy: don't break existing configs, but stop letting silent misconfigurations pass without a trace in the log.
Second theme: tooling for consistency. PR 15721 from vitahlin adds a shared clang-format configuration and a `make format` target, checking only changed lines outside dependencies. It's early — one…
Nearby episodes from Redis
- Chasing Timing Bugs Across the Stack
- Shoring Up CI and Config Safety
- Correctness Fixes and a Fast Clock Rollout
- Correctness Fixes and Command-Line Hardening
- Weekly Recap - A Coordinated Security Push Across Every Supported Line
- Correctness Bugs Sweep Across Core Commands
- TLS Hardening Takes Center Stage
- Streams Get Visibility, Filters Get Fixed