← Back to BLACKWIRE CIPHER BUREAU SECURITY UPDATE Terminal window showing Lonewolf 0.3 release notes on GitHub

The GitHub release page for Lonewolf 0.3.0, highlighting federation and TLS features.

LONEWOLF 0.3 RELEASE ENABLES XMPP FEDERATION AND TLS

*Lonewolf 0.3 adds server‑to‑server federation, direct TLS, and new client extensions. The Rust‑based XMPP server remains pre‑1.0 but moves toward full compliance and clustering.*

By CIPHER Bureau - BLACKWIRE  |  November 13, 2026, 21:00 CET  |  Lonewolf, XMPP, federation, TLS, Rust

On 13 November at 14:22 UTC, the lonewolf‑im project pushed version 0.3.0 of its Rust‑written XMPP server. The update marks a functional leap: federation opens the server to the wider XMPP ecosystem, while direct TLS hardens client connections from the first byte. New extensions bring private storage and version reporting to desktop clients, and credential handling steps up with optional SCRAM‑SHA‑512. The release stays pre‑1.0, runs as a single node, and promises full compliance and clustering on the roadmap. Operators can compile the code with a standard Rust toolchain on Linux or macOS, and the project remains Apache‑2.0 licensed.

What does federation mean for Lonewolf users?

Version 0.3.0 introduces federation, allowing Lonewolf nodes to exchange messages, presence, IQs, and roster subscriptions with external XMPP servers. If a host presents a valid certificate and a public DNS name, federation activates automatically without extra configuration. Peer authentication relies solely on certificates; the remote server must support SASL EXTERNAL. Server Dialback is not supported. When both sides support XEP‑0288, a single connection carries traffic in both directions. Stanza size and idle limits are advertised upfront via XEP‑0478. Certificate revocation lists are fetched over plain HTTP, but connections proceed if a CRL cannot be retrieved, unless disabled with s2s.tls.fetch_crls = false.

How does direct TLS improve client connections?

Direct TLS arrives in 0.3.0, enabling clients and servers to start encrypted sessions from the first byte (XEP‑0368). Dedicated listeners handle outbound federation, discovering both STARTTLS and direct TLS endpoints. This reduces handshake latency and eliminates the need for opportunistic STARTTLS upgrades. The feature coexists with existing STARTTLS paths, ensuring backward compatibility while offering a more secure default for new deployments.

Lonewolf can now talk to other XMPP servers, unlocking federation by default.

Which new extensions benefit desktop XMPP clients?

The release adds Private XML Storage (XEP‑0049) for client‑side settings and legacy bookmarks, and Software Version (XEP‑0092) to answer server identity queries without exposing the underlying operating system unless explicitly enabled. Both extensions are enabled by default. Short‑lived certificates can be managed via letsencrypt.certificate_profile, pulling profiles advertised by the CA and renewing early when profiles change. SCRAM‑SHA‑512 and SCRAM‑SHA‑512‑PLUS are now optional, though they stem from an expired Internet‑Draft and lack IANA registration. Enabling them stores credentials unreadable by v0.2.0, complicating rollbacks.

How can operators build and run Lonewolf 0.3?

The source is available as tar.gz or zip. Building requires a stable Rust toolchain and a system linker on Linux or macOS. The command cargo build --release --locked -p lonewolf -p lonewolfctl -p lonewolfbench compiles the server, control utility, and benchmark tool. The benchmark binary is now named lonewolfbench, replacing the former lonewolf-bench. The quick‑start guide walks users through configuration. Lonewolf remains a single‑node, pre‑1.0 release under the Apache‑2.0 license. Full XMPP compliance and clustering are slated for future releases.

Frequently asked questions

What new federation capabilities does Lonewolf 0.3 provide?

Lonewolf 0.3 enables server‑to‑server messaging, presence, IQs, and roster subscriptions with other XMPP servers, using certificate‑only authentication and optional direct TLS.

How does direct TLS work in Lonewolf 0.3?

Direct TLS starts encrypted sessions from the first byte via dedicated listeners, supporting both STARTTLS and direct TLS endpoints for outbound federation.

What are the build requirements for Lonewolf 0.3?

Building Lonewolf 0.3 requires a stable Rust toolchain and a system linker on Linux or macOS, using cargo build with the specified packages.

Version 0.3.0 positions Lonewolf as a serious contender in the XMPP space, delivering federation and modern TLS without sacrificing the simplicity of a single‑node deployment. While full compliance and clustering remain future work, the added extensions and credential options signal a clear trajectory toward enterprise‑grade readiness. Operators who value open‑source, Rust‑based security now have a viable, standards‑compliant server that can integrate into existing federated networks today.

Sources: [Hacker News – Lonewolf 0.3 – A standalone XMPP server written in Rust]