MeridianMeridian

redb 4.0 Released: XML Routes, Lazy References, Unique Keys and WS-Trust Across the Ecosystem

The redb ecosystem has delivered a major simultaneous release across all core components, bringing redb.Core, redb.Route, redb.Tsak and redb.Identity to version 4.0.0. The update introduces declarative XML routing, lazy object references, unique key constraints, and a full WS-Trust SOAP facade while closing multiple security issues reported through external audits and community feedback. Seventy-six NuGet packages, seven container images and platform archives for Windows and Linux are now available, with the Pro edition remaining free and license-free throughout the 4.x line. Significant internal changes include a unified expression language, support for modern data formats such as Protobuf and Avro, and improved handling of distributed caches and OpenTelemetry metrics. Security hardening covers header sanitization in all identity facades, consent-page protections, dashboard access controls and a switch to bcrypt password hashing. Existing clusters must be stopped before upgrade because mixed versions are not supported, and large databases require a maintenance window for schema changes and partial index creation.

HabrTranslated from Russian

Read at source

redb 4.0 delivers a coordinated major release across the entire ecosystem, updating redb.Core, redb.Route, redb.Tsak and redb.Identity in a single 4.0.0 version. Seventy-six NuGet packages, seven container images in GHCR and archives for Windows and Linux are now published. The Pro edition remains free and does not require a license key on the entire 4.x line.

redb.Route receives ten new packages and a substantial engine redesign. Declarative routes can now be defined in .route.xml files using the new redb.Route.Xml package and loaded into the same fluent DSL used for C# routes. The redb.Route.TestKit allows testing without brokers or route modifications through AdviceRoute, MockEndpoints and NotifyBuilder. Additional packages provide Scriban and Liquid templates, CSV, Protobuf, Avro and YAML data formats, JSONata transformations, in-memory or distributed caching, and XPath 2.0 support.

The routing engine now uses a single expression language and compiler for conditions, values and templates. New functions include stats, format, uuid and the modulo operator. The bean component allows custom objects to be used as endpoints with dependency injection. REST DSL, OpenAPI 3.0.3 generation, OpenTelemetry metrics inside routes and removal of Newtonsoft.Json in favour of System.Text.Json are also included.

Hosting improvements cover concurrent request limits with 429 responses, automatic consumer scaling for RabbitMQ, AMQP 1.0, IBM MQ, SQS and MQTT, WebSocket and SignalR support on the shared Kestrel host, and trusted proxy handling for X-Forwarded headers. Kafka consumers now preserve unprocessed records on partition revocation, and connectors for S3, Firebase and LLM providers received multiple stability and feature updates.

redb.Core introduces lazy references that load only on first access to Props when EnableLazyReferences is active, and unique keys via the new ValueUnique mechanism and [RedbUnique] attribute. Unique constraints are enforced by database indexes for scalars, nested objects, collections and entire subtrees. Schema upgrades are applied at startup with typed exceptions when rights are insufficient. CancellationToken support, save interceptors, per-request isolation levels and maintenance operations such as AnalyzeAsync are now available across PostgreSQL, MSSQL and SQLite.

redb.Tsak cluster coordination now relies on unique database keys from redb.Core. XML-only modules can be loaded and reloaded at runtime. The dashboard distinguishes load shedding from idle routes, Audit and Dead-letter pages are functional on PostgreSQL, and trusted proxy configuration is exposed for API throttling.

redb.Identity adds a WS-Trust SOAP facade supporting Issue, Validate, Cancel and Renew operations. Access tokens now include audience claims according to RFC 9068. The administrative console has been rebuilt with full pages instead of dialogs, and DPoP support behind TLS-terminating proxies has been improved.

Several security issues were addressed. Internal headers are now stripped on all three identity facades. Consent pages validate signed tickets and Origin headers. Introspection responses are restricted to token audiences. Dashboard pages require authentication with role-based access. Module signatures are verified on every load path, and the default password hasher is now bcrypt.

Clusters must be fully stopped before upgrading because mixed versions are unsupported. Large databases require a maintenance window for schema changes performed under exclusive locks. Full change logs are published at redb.ru/releases.

OpenTelemetryPostgreSQLRabbitMQredb.Identityredb.Routeredb.CoreWS-Trust
ShareXFacebookLinkedInReddit
Meridian digestThe week's most consequential security stories, distilled into one briefing.See the digest

More in Other

Mail.ru Reduces Lifetime 1TB Cloud Storage Promo to Standard 8GB Quota for Select Users
Other

Mail.ru Reduces Lifetime 1TB Cloud Storage Promo to Standard 8GB Quota for Select Users

Mail.ru has begun notifying a small group of long-term Cloud Mail users that their complimentary 1TB storage, originally granted through a 2013-2014 app installation promotion, will be reduced to the standard 8GB free tier. Affected users receive personalized deadlines, with some facing storage limits starting 30 October and final deletion of excess files scheduled for 30 January 2027. The company confirmed the change impacts fewer than 0.5 percent of Cloud Mail users and stated that core free features remain available. Once the 8GB limit is exceeded, uploads, edits, and sharing are blocked while users have three months to download data or purchase additional space before files move to the trash for 14 days prior to permanent removal. This follows a similar reduction of lifetime 100GB storage performed by the service in 2024.

AntiMalwareOct 29, 2026Translated from Russian

Kimi K3 Open Model Surpasses Closed AI Leaders with Million-Token Context and 896 Experts
Other

Kimi K3 Open Model Surpasses Closed AI Leaders with Million-Token Context and 896 Experts

Kimi K3 is an open-weights model that outperforms closed systems from GPT and Anthropic on several independent benchmarks. Developers achieved this by scaling three dimensions simultaneously: one million tokens of context, deeper layers, and 896 Mixture-of-Experts specialists. The team replaced the standard KV-cache with a fixed-size state matrix updated via the delta-rule, solving numerical instability by clamping the forgetting coefficient alpha between e^-5 and 1. Sequential state updates were parallelized across chips, GPUs, and multi-GPU nodes using the open-source FlashKDA kernel built on CUTLASS. Inter-layer information flow was preserved through learned pseudo-queries that selectively retrieve relevant outputs from prior blocks rather than passing full activations. Load balancing across 896 routed experts uses per-expert quantile thresholds and a distributed histogram method to guarantee fair token allocation without full sorting.

HabrOct 29, 2026Translated from Russian

Innostage Completes Functional Testing of PT NGFW 1.10.3 Across 156 Criteria
Other

Innostage Completes Functional Testing of PT NGFW 1.10.3 Across 156 Criteria

Innostage has published the second part of its evaluation of PT NGFW version 1.10.3, focusing on functional capabilities rather than raw performance. The testing covered 156 individual checks grouped into categories such as basic technical features, firewalling, IDS/IPS, web filtering, malware protection, logging, routing, deployment, cryptographic controls and access management. Out of the total, 136 checks passed fully, seven passed with remarks, and 13 did not meet the predefined criteria. Key confirmed functions include high-availability clustering, centralized management via PT-MNGT, AD-based rule application, Site-to-Site VPN, TLS inspection, and Syslog integration with external security systems. Several advanced scenarios, including custom block pages, application risk classification, and centralized software distribution, were not confirmed under the test conditions. The report provides detailed protocol notes that help organizations map product capabilities against their specific infrastructure and regulatory requirements.

HabrOct 29, 2026Translated from Russian