Nauthilus 4.0 Patch Releases
This page lists the changes of the patch releases that follow Nauthilus 4.0.0, newest first. The current
release is v4.0.9, published on November 12, 2026.
All patch releases keep the v4 configuration model. Read the entries between your installed version and the target version; the items marked Action need an operator step.
Rebuild every private native plugin against the exact source and Go toolchain of the release you deploy. pluginapi/v1
gained one field in v4.0.3 and is otherwise unchanged across these releases.
4.0.9
Published as tag v4.0.9 on November 12, 2026. Backend tempfail causes and empty credentials with subject providers.
- An empty password or username answers
Invalid login or passwordagain when a subject provider is scheduled insubject_analysiswithrun_if.auth_stateany,unauthenticated, or the default. From v4.0.0 to v4.0.8 such a request ended as a temporary failure withtempfail_reason=policy_indeterminate checkpoint=subject_analysis status_code=provider_unavailableand no other log line. A provider withauth_state: authenticatedwas not affected. - The cause: a request that the host settles without a backend result skips the subject providers with the reason
backend_unavailable, and the evaluator did not accept that reason as a regular skip. It does now, so the request reachesauth_decision. - A backend temporary failure stays a temporary failure. It is now selected by the builtin
standard_backend_tempfailrule withoutcome_marker=auth.outcome.backend_tempfail. - The terminal tempfail WARN line names a failed backend with
tempfail_reason=backend_tempfail, lists the providers that had no backend result to analyze inskipped_providers(instance:reason), and carries the first technical error intempfail_error. Action: alerts and queries ontempfail_reason=policy_indeterminateno longer match backend outages. Addbackend_tempfailwhere they should. - A native plugin backend failure names a bounded cause in the backend error:
plugin call failedwith the result class (error,timeout,canceled,panic,admission_limited),plugin reported a temporary failurewith the plugin'sStatusMessage.CodeandDefaultText, or the invalid result part. Raw plugin errors stay out of host logs. pluginapi/v1is unchanged. Rebuild every private native plugin against the exact v4.0.9 source and Go 1.27.4.
4.0.8
Published as tag v4.0.8 on November 12, 2026. DNS lookup retries, socket pool, and Go 1.27.4.
- All outbound DNS lookups (RBL checks, the client IP reverse lookup, the Lua
nauthilus_dnsmodule, and the connection monitor) share one long-lived client. - A lookup sends up to
runtime.clients.dns.attemptsqueries (default3) insideruntime.clients.dns.timeout. An additional attempt starts after eachruntime.clients.dns.retry_interval(defaulttimeout / attempts) while the earlier attempts keep running, and the first definitive answer wins. Before, one lost UDP datagram always ended inlookup <name>: i/o timeoutafter the full timeout. Action: the default applies without a configuration change, and a slow or lossy resolver can receive up toattemptsqueries per lookup. Setattempts: 1to keep the previous single-query behavior. - "Name does not exist" ends a lookup without a retry, so RBL lookups for unlisted addresses still send one query.
runtime.clients.dns.pool_size(default0, disabled) keeps that many idle UDP sockets per resolver and reuses them instead of opening one socket per query.runtime.clients.dns.pool_max_uses(default256) replaces a socket after that many queries.- New metrics:
dns_lookups_total{result,attempts}anddns_pool_sockets_total{source}. - The new settings require a restart, like the existing DNS settings. Lookup results, RBL scoring, and error handling are unchanged.
- The toolchain moves to Go 1.27.4, because Go 1.27.3 carries a
net/httpvulnerability (GO-2026-6859) that is reachable in the server. Action: rebuild every private native plugin against the exact v4.0.8 source and Go 1.27.4.
See DNS client.
4.0.7
Published as tag v4.0.7 on November 10, 2026. Request termination causes and cancel sources.
- The HTTP server records why a connection ended (client disconnected, connection deadline exceeded, connection closed locally, connection failed) and attaches the cause to the request context.
- A request ended by the client logs
msg="Client Closed Request"at NOTICE withstatus=499. Action: v4.0.6 logged this line at WARN. Alerts or queries that select it by level must use NOTICE. - A request whose connection ended for a server-side reason logs
msg="Request connection terminated"at WARN. - Both lines carry
errorwith the transport cause andduration_ms. HTTP auth requests also carryclient_ipandprotocolonce the auth handler has resolved them. Authentication application failed(HTTP and gRPC), request-boundNative plugin call failedlines, and the terminal tempfail WARN line carryrequest_context_error,request_context_cause, andcancel_source.cancel_sourceisrequestwhen the own request context ended,foreignwhen the cancellation came from work shared with another request or from an internal deadline, and empty when no cancellation is involved.- gRPC still answers an application error that wraps a cancellation or deadline with
CanceledorDeadlineExceeded. - Authentication decisions, temporary failures, and response bodies are unchanged.
See Request termination and cancel sources.
4.0.6
Published as tag v4.0.6 on November 10, 2026. Username syntax, tempfail causes, and identity lookup checks.
- Usernames are rejected only for invalid UTF-8 and control characters. Spaces and IMAP atom specials reach the
backends, and percent-decoded nginx headers such as
Vorname%20Nachnameare no longer refused. An unsafeauthenticateusername is answered like an empty one withInvalid login or passwordinstead of400 Bad Request. A missing username key stays400, andlookup_identityover gRPC keepsInvalidArgument. - LDAP filters expand the legacy
%splaceholder and%{...}macros in one pass, so a username that contains macro syntax stays literal. - Every temporary failure writes the terminal WARN line, including decisions without a selected policy rule and JSON
and CBOR requests. The line uses
Temporary server problem, try again laterasmsgand names the cause withtempfail_reason,checkpoint,status_code,policy_set,policy_rule, andoutcome_marker. Queries that match the oldmsg="Temporary server problem"as a prefix still match. status_messagein the summary log lines, Luarequest.status_message, and native post-action snapshots report the text the client receives, includingauth.response.failure_messageandauth.response.tempfail_message.lookup_identity(HTTPmode=no-auth, gRPCLookupIdentity, IdP no-auth lookups) no longer schedules the TLS-encryption and RBL checks by default. A domain plan that bindsauthn/builtin/tls_encryptionorauthn/builtin/rbltolookup_identitynow runs them in no-auth mode. An RBL opt-in multiplies block-list query volume, because lookup traffic is usually far higher than login traffic.- Action: Configuration load rejects
authn/builtin/brute_forceandauthn/builtin/relay_domainsbindings tolookup_identity, which were silent no-ops before. Remove suchactionsentries before upgrading. Native plugin call failed,lua_vm_acquire_failed, and the LDAP poolreply_channel_blocked_dropwarning carry the requestsession.
See Credential syntax and empty credentials and Built-in authentication providers.
4.0.5
Published as tag v4.0.5 on November 9, 2026. Credential result in logs and subject rejection state.
- The final auth log field
authnreports the credential check. A verified password that a subject source rejects afterwards, for example because the protocol is inactive, logsauthenticated=fail authz=false authn=trueinstead ofauthn=false. Wrong or empty credentials, rejections before the credential check, and technical failures keepauthn=false. Action: Log queries that readauthn=falseas "denied" must useauthenticatedinstead. - A Lua subject rejection or Lua subject error leaves the request unauthenticated, as a native subject rejection
already did. Post-actions and request snapshots see a failed login with the failure status code, and
run_if: authenticatedproviders and password checks such ashaveibeenpwndno longer run after a Lua rejection. Access decisions do not change.
4.0.4
Published as tag v4.0.4 on November 9, 2026. Dependency update and internal cleanup.
github.com/go-jose/go-jose/v4moves to v4.1.6 for GHSA-mgcc-cww5-fp2q (denial of service when parsing JWKs with RSA keys). The module is an indirect dependency of the OIDC test client.- An unused internal HTTP auth setup path is removed. Request handling does not change. Go code that imported the
removed
server/coresetup symbols must use the auth application service instead.
4.0.3
Published as tag v4.0.3 on November 9, 2026. Empty credentials, operator response texts, and RBL analytics.
- An empty username or password value is no longer a malformed request. HTTP JSON, CBOR, form, header, nginx, and
Basic requests and gRPC
Authenticateanswer it as an ordinary failed login withInvalid login or passwordthrough the built-instandard_empty_usernameandstandard_empty_passwordrules. A missing credential key and JSON or CBORnullstill return400 Bad Request.lookup_identitykeeps its temporary failure. Empty-credential failures run no backend and do not update brute-force buckets. auth.response.failure_messageandauth.response.tempfail_messageoverride the generic failure and temporary-failure texts in HTTPAuth-Statusheaders, plain-text bodies, and gRPC authority responses. See Response texts.- Native plugins receive
RequestSnapshot.Diagnostics.RBLMatchedListswith every configured RBL list that listed the client IP, in configuration order, also below the RBL threshold. RBL list facts, includingauth.rbl.matched_lists, are deterministic and in configuration order. - The host publishes
plugin.exchange.feature.rblandplugin.exchange.feature.brute_force. The native ClickHouse plugin therefore listsrblandbrute_forceindecision_sources. Dashboards should query membership, for examplehas(splitByChar(',', decision_sources), 'rbl'), instead of exact strings. - Action: The native ClickHouse plugin writes the new
rbl_listscolumn. Add it before deploying the plugin; see ClickHouse plugin. The Luaactions/clickhouse.luaaction is retired and receives neither change. github.com/andybalholm/brotliv1.2.7,github.com/klauspost/compressv1.20.2, andgolang.org/x/netv0.62.0 fix GO-2026-6888, GO-2026-6865, and GO-2026-6860.
4.0.2
Published as tag v4.0.2 on October 26, 2026. The DKIM2 intelligence plugin moved out of the core.
- The toolchain moves to Go 1.27.3, because Go 1.27.2 carries a
crypto/x509vulnerability that is reachable through JWT verification.github.com/getkin/kin-openapimoves to v0.149.0. - The images bundle
geoip,clickhouse,haveibeenpwnd, andreputationonly./usr/local/lib/nauthilus/plugins/dkim2-intelligence.soand its.minisigare no longer shipped. The plugin is maintained as an external native plugin and owns the DKIM2 Policy integration. - Action: Operators who load
dkim2_intelligencemust supply the external artifact built from the exact release source tree, toolchain, and build tags, with its checksum and detached signature, in the immutable plugin directory. An artifact built for an earlier release, including the one bundled with v4.0.1, is rejected before it is loaded. - Existing
policytargets, providers, and plugin bindings that reference the DKIM2 namespace keep working once the external artifact is installed. scripts/convert-static-reputation.pyconverts only reputation overrides andip_override_networksand rejectscontractsinput. The admin client still accepts artifacts written by earlier converter versions.
See DKIM2 Intelligence plugin.
4.0.1
Published as tag v4.0.1 on October 12, 2026. MFA recovery code and cache consistency fixes.
- Account caches are invalidated after local and authority MFA writes. A cache failure is logged and does not reject the persisted change.
- LDAP recovery codes are consumed atomically by deleting the exact stored value, bound to the current identity. The browser frontend and the gRPC authority share the same consumption path, and stored values are compared in constant time. Backends that can only replace the whole recovery-code list need an atomic consumer.
- Recovery codes entered on the TOTP step are accepted through the authoritative backend, also when the cached recovery list is missing or empty. A used code stays rejected on replay.
- Corrupt LDAP recovery values are skipped with a warning that contains no secret.