redb 3.4.0 Adds Replay Checkpoints, Shared Runtime Layer and Declarative Secrets Handling for .NET Ecosystem
redb 3.4.0 introduces four major capabilities aimed at the day-after-deployment phase of running integration routes on .NET. The ecosystem comprises typed storage redb on top of Postgres, MSSQL and SQLite, the integration engine redb.Route that provides more than thirty connectors modeled on Apache Camel, the redb.Tsak runtime with dashboard, hot-reload and clustering, and redb.Identity implementing OIDC and OAuth 2.1.
The first feature, replay checkpoints, lets developers mark safe points inside a route using the Replayable DSL method. When a downstream step fails, the exchange snapshot captured at the last checkpoint can be replayed without re-executing earlier side effects such as card charges. The mechanism relies on a new IExchange.Snapshot primitive that performs a deep isolated copy, avoiding the shared-body behavior of the existing Clone method used by splitters.
Failed exchanges that carried a checkpoint are automatically placed into a dead-letter queue table. Operators can list, replay or discard these exchanges through the dashboard, REST API or CLI commands. Retention is handled by a standard cron route rather than an internal timer.
The second major change separates the framework assemblies into a Libs/shared directory. Early bootstrap code installs a custom assembly resolver so that redb.Core, providers and connectors are loaded from the shared location. Replacing a single DLL now patches the running system without rebuilding Tsak archives or container images. Version checks ensure that only patch-level differences between the shared layer and the host are permitted.
Secret handling has been moved from heuristic lists to declarative attributes. Endpoint option properties marked with [Sensitive] are automatically redacted by EndpointUri.Sanitize before any logging, OpenTelemetry tagging or health-check output occurs. All thirty-seven credential-bearing options across twenty-two connectors have been annotated.
Finally, the runtime now enforces role-based access on management APIs, records persistent audit events and verifies cryptographic signatures on modules loaded at runtime. redb.Identity has adopted the common ecosystem version number so that compatibility questions are answered by a single version digit.
Related articles
HTTP Methods Explained: GET, POST, PUT, PATCH, DELETE and the New QUERY Standard
HTTP methods define the actions a client requests from a server regarding a resource. The core semantics are outlined in RFC 9110, with extensions for specialized protocols. A new standardized method called QUERY was introduced in June 2026 via RFC 10008 to handle complex queries that include a request body while remaining safe and idempotent. The article details safe and idempotent properties, compares each method including GET, HEAD, POST, PUT, PATCH, DELETE, OPTIONS, TRACE, CONNECT, and QUERY, and explains their correct usage to avoid breaking caches, proxies, and infrastructure expectations. It also covers WebDAV extensions and other registered methods in the IANA registry.
From Web Perimeter Breaches to Domain Takeover: How Standoff Hackbase Trains Pentesters on Real Corporate Infrastructure
wr3dmast3r, a senior pentester and BSCP certification guide author, rose to first place on the Standoff Hackbase ranking by shifting focus from initial perimeter access to full internal infrastructure compromise. The platform replicates large-scale corporate networks from various industries, forcing participants to map service relationships, harvest credentials, escalate privileges, and chain pivots across segments. Unlike CTF challenges that end with a single flag, Hackbase tasks require building complete attack paths that can lead to data theft, process disruption, or cross-domain movement. The interview highlights practical techniques such as time-boxing hypotheses, manually modeling infrastructure after automated scans, and using AI only as an information accelerator rather than an autonomous operator. wr3dmast3r also details a memorable chain that began with a bot, moved through VPN and Outlook access, leveraged SCCM tokens for privilege escalation, and ended with compromise of a second domain containing the target system.
OTUS Publishes September Digest of Free Lessons on Linux Administration, PostgreSQL, CI/CD and Infrastructure Security
OTUS has released a new digest listing free September webinars aimed at infrastructure engineers, DevOps specialists and system administrators. The program covers practical topics including Linux server configuration, PostgreSQL 18 performance tuning, high-availability clusters with Patroni, CI/CD pipelines in GitLab, eBPF observability and infrastructure security practices. All sessions are delivered by practicing OTUS instructors who share real-world production experience. Separate tracks address RAID and LVM management, GPO policies, release management in 1C environments, Go profiling, mitmproxy traffic analysis and responsible use of AI tools for incident investigation and code review. The webinars run throughout September at 19:00 or 20:00 Moscow time and require only free registration. The digest also includes sessions on career growth from tech lead to CTO and effective responsibility distribution for team leads.
Top LLMs Misidentify Poisonous Mushrooms in Every Ninth Case, Benchmark Shows
Polish developer Piotr Migdal evaluated leading large language models on their ability to identify mushrooms from photographs, using a dataset of 1040 images covering 55 species common in Poland. The images came from the FungiTastic dataset derived from the Atlas of Danish Fungi, with expert labels and partial DNA confirmation. Models were asked to return the five most likely species names in Latin without additional training or tools. Gemini 3.8 Flash performed best with 65 percent top-1 accuracy and 85 percent top-5 accuracy, followed closely by other Gemini variants. However, safety-critical errors remained high: Gemini models labeled poisonous mushrooms as edible in roughly 11 percent of cases, while GPT-5.6 Sol reached 24 percent, Claude Opus 5 reached 29 percent, and Qwen 3.8 27B reached 36 percent. The study did not ask models directly whether a mushroom was edible; species identifications were later cross-checked against toxicity tables.