> For the complete documentation index, see [llms.txt](https://docs.defguard.net/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.defguard.net/in-depth/architecture-decision-records/1.6.md).

# 1.6

## 2025-10-16 Desktop client auto-provisioning

In order to support client auto-provisioning of the desktop client we've introduced support for initializing the client from a provisioning file ([#627](https://github.com/DefGuard/client/pull/627)). If a client is "uninitialized" (has no instance configured) it can read required enrollment config from a file stored in app data directory. The process is explained further in the [docs](/features/desktop-client-auto-provisioning.md#client-side-implementation-details).

This file-based approach allows us to support provisioning on various platforms independent of the specific tooling used by system administrators.

Furthermore since the majority of users are on the Windows platform we also updated our MSI package to support provisioning scenarios in Active Directory and Entra ID environments as described [here](/features/desktop-client-auto-provisioning/auto-provisioning-in-windows-environments.md#windows-auto-provisioning).

To enable this functionality we also needed to introduce a change to the OpenID directory sync functionality - when using Microsoft provider it is now possible to create users in Defguard during sync, without waiting for the first login.

## BoringTun

BoringTun is an implementation of the [WireGuard® protocol](https://www.wireguard.com/protocol/) designed for portability and speed. It is written in [Rust](https://rust-lang.org/) and was originally published by Cloudflare.

In the Defguard ecosystem, BoringTun is an important building block for running WireGuard functionality in user space where a kernel implementation is unavailable, unsuitable, or not the preferred integration model. This makes it especially useful on platforms where portability and embedding matter.

The Defguard team uses a fork of the [original repository](https://github.com/cloudflare/boringtun) with the following changes:

* [Swift](https://www.swift.org/) bindings using [UniFFI](https://mozilla.github.io/uniffi-rs)
* cleaned-up code
* dependencies updated regularly

BoringTun is used by [wireguard-rs](https://github.com/defGuard/wireguard-rs), which serves as a foundation for Defguard Gateway, and by [Defguard Client](https://github.com/defGuard/client) for handling VPN tunnels on [macOS](https://www.apple.com/os/macos/).

In practice, this means BoringTun helps Defguard support WireGuard-based connectivity in environments where kernel-level WireGuard integration is not the default approach. It also allows the project to build platform-specific integrations on top of a shared Rust implementation.
