TunnelYard v2.7.0

TunnelYard 2.7.0

Rebrand to TunnelYard

• Renamed the product to TunnelYard. The GitHub repository is
  LucasCavalheri/tunnel-yard, the desktop id is lucas.cavalheri.tunnelyard,
  and packages/binaries use the tunnel-yard slug.
• New profile metadata uses # tunnel-yard-* markers. Existing profiles and
  installations migrate compatibly, including macOS and Windows directories.
• Rebranded the Astro website and added architecture/package selection with
  direct downloads resolved from the published release assets.
• Documented exploratory Linux RAM measurements and their methodology.

In-app updates

• Download and install applies the matching GitHub release artifact on
  Linux (deb/rpm or portable binary), macOS (.app from the disk image or
  portable binary) and Windows (portable or Program Files, with UAC when needed).
• The Linux tray now refreshes per-profile status when tunnels change, and no
  longer draws the coral mark as a red overlay badge on GNOME.

TunnelYard v2.6.0

TunnelYard 2.6.0

Product interface refresh

• Reworked the native desktop surface to match the website hero: compact
  operations rail, centered brand bar, dark workspace, profile cards and live
  console.
• Moved secondary controls into Preferences so the main tunnel view stays
  focused on connecting and monitoring environments.
• Added a visual connection journey and a multi-tunnel network animation to
  the landing page, with meaningful motion and reduced-motion support.
• Fixed the Linux development build so cargo run no longer requires a
  distro-specific Fontconfig development package.

TunnelYard v2.5.0

TunnelYard 2.5.0

Multi-architecture release

• Added native Linux x64 and ARM64 release builds.
• Added Debian (.deb) and RPM (.rpm) packages for Linux x64 and ARM64.
• Debian packages accept both the current polkitd/pkexec split and older
  policykit-1 transitional packages.
• Added executable Linux .tar.gz archives so downloaded binaries retain
  their execute permission.
• Added a universal macOS binary containing Intel and Apple Silicon slices.
• Added a universal macOS .dmg installer.
• The macOS binary and application bundle are ad-hoc signed during packaging.
• Added native Windows x64 and ARM64 GUI builds.
• Made release metadata architecture-aware so the updater can identify the
  matching platform artifact.
• Made the APT repository infer and publish amd64 and arm64 package
  indexes instead of hard-coding amd64.
• Windows ARM64 now fails closed when the pinned x64 OpenConnect installer is
  selected; a native OpenConnect + Wintun ARM64 package is still required for
  VPN connections on that target.

TunnelYard v2.0.0

TunnelYard 2.0.0

TunnelYard 2.0 introduces a new native desktop experience built on GPUI Kit while
keeping the existing VPN engine, profiles and privilege boundaries intact.

Highlights

• Rebuilt the desktop shell with GPUI Kit 0.6: native title bar, buttons,
  inputs, switches, icons, scroll containers and theme integration
• Refined the window around a compact operations rail, searchable profile
  cards, fixed-height live console and a scrolling profile editor
• Preserved multi-tunnel control, tray behavior, pt-BR/EN, setup bootstrap,
  notifications and update checks across the UI migration

Breaking changes

• Raised the minimum supported Rust version to 1.90
• Removed the legacy --screenshot CLI option because the GPUI renderer does
  not expose an equivalent live-window capture API

TunnelYard v1.2.0

TunnelYard 1.2.0

First native Rust desktop host. Electron, Node and the Chromium shell are gone.
Profiles stay as openfortivpn .conf files; the GUI process still never runs as
root or Administrator.

What changed

• Native eframe/egui desk: profile list, editor, live console, setup gate,
  light/dark theme, pt-BR + EN
• Close the window to park in the tray; Quit in the sidebar or tray menu
  disconnects then exits
• Linux/macOS continue to use openfortivpn; Windows continues to use
  OpenConnect 9.21 + Wintun
• Privileged work stays in packaging/ helpers (PolicyKit, macOS administrator
  prompt, Windows UAC)
• In-app update check opens the GitHub release page; it does not download or
  run installers

Downloads

File	Platform
tunnel-yard-linux-x64	Linux
tunnel-yard-macos	macOS
tunnel-yard-windows-x64.exe	Windows x64

chmod +x tunnel-yard-linux-x64
./tunnel-yard-linux-x64

On first launch the app can install the platform VPN client. Unsigned binaries
may trigger SmartScreen / Gatekeeper.

Upgrading from 1.1.x (Electron)

This is a new desktop host, not an installer drop-in. Do not use the in-app
updater in 1.1.x to apply this release — those builds look for .deb /
.rpm / .dmg / NSIS .exe packages, which this tag does not ship.

1. Download the binary for your OS from this page
2. Quit the old Electron app
3. Run the new binary
4. Existing .conf profiles continue to work:
   • Linux: /etc/openfortivpn
   • macOS: ~/Library/Application Support/TunnelYard/profiles
   • Windows: %APPDATA%\TunnelYard\profiles

Distro packages (.deb / .rpm / .dmg) for the Rust host are not produced
yet. Older 1.1.x tags still have the Electron-era installers.

Validation

Automated checks cover configuration translation, certificate pins, native
status policy and i18n. Windows MTU, split-DNS and service probes were checked
on a real FortiGate session in 1.1.x; other gateways and macOS still need
native acceptance testing. Windows currently supports IPv4 SSL VPN. SAML and
all MFA variants are not verified.

TunnelYard v1.1.7

Installing updates on Windows

• Launch the downloaded installer through ShellExecute so Windows raises
  the UAC prompt. The per-machine installer requires administrator
  rights, which CreateProcess refuses outright — updating from inside
  the application failed with spawn ... EACCES.
• Report a declined elevation prompt instead of quitting the running
  application. The spawn failure arrived asynchronously and escaped the
  surrounding error handling, crashing the main process.
• Attach the same error handling to the macOS update helper.

Upgrading to this version from 1.1.6 or earlier still needs the
installer to be run manually, because the fix lives in the update path.

Application icon and form focus

• Replace the placeholder application mark with the shield icon used in
  the interface. Windows takes its taskbar and toast-notification icons
  from the installed executable, so both now match the window.
• Give desktop notifications an explicit icon instead of the shell default.
• Restore a visible focus indicator on profile fields, buttons and toggles;
  the previous ring was too faint to see over the dark surface.
• public/icon.svg is now the single source for the mark, rasterized by
  npm run build:icons.

Earlier in 1.1.x

• Apply and verify the MTU negotiated for each session before installing tunnel IP/routes.
• Validate adapter, IP, routes and effective MTU before showing connected; optionally check an internal TCP service configured in the profile editor.
• Recheck isolated service-probe failures without reauthenticating; show verification in progress and disconnect after three consecutive failures. Topology loss remains immediate.
• Detect tunnel loss and stale supervisor status; stop retrying rejected cookies or sessions where the gateway forbids reconnect-after-drop.
• Apply Fortinet split-DNS with scoped Windows NRPT policies and remove owned settings on disconnect.
• Retain secure CA/fingerprint verification and distinguish an unknown-CA warning from a verified certificate pin.
• Install application updates from official releases only.

Packages

• .deb — Debian / Ubuntu / Mint
• .rpm — Fedora / RHEL / Rocky / Alma / openSUSE
• .dmg / .zip — macOS, Intel and Apple Silicon (requires openfortivpn via Homebrew)
• .exe — Windows x64 (setup installs OpenConnect 9.21 on first use)

All platforms import openfortivpn .conf profiles. See the README for
Windows option compatibility and signing / notarization notes.

New platforms: validation limits

Windows and macOS support is new. Automated checks cover profile
translation, local TLS/authentication and network cleanup logic.
Windows MTU, service reachability and split-DNS were also checked on a
real FortiGate session; other gateways and macOS still require native validation.
Windows currently supports IPv4 SSL VPN. SAML and all MFA variants
are not verified. The packages may trigger SmartScreen/Gatekeeper
warnings when signing credentials are not configured.

Install / upgrade (Debian & Ubuntu)

After installing once, updates come with sudo apt upgrade:

sudo apt install ./tunnel-yard_*_amd64.deb
# postinst installs the archive key and APT source automatically
sudo apt update && sudo apt upgrade

Or add the repo manually:

curl -fsSL https://lucascavalheri.github.io/tunnel-yard/apt/tunnel-yard-archive-keyring.asc \
  | sudo tee /usr/share/keyrings/tunnel-yard-archive-keyring.asc >/dev/null
echo 'deb [arch=amd64 signed-by=/usr/share/keyrings/tunnel-yard-archive-keyring.asc] https://lucascavalheri.github.io/tunnel-yard/apt ./' \
  | sudo tee /etc/apt/sources.list.d/tunnel-yard.list
sudo apt update && sudo apt install tunnel-yard

Fedora / RPM

sudo dnf install ./tunnel-yard-*.x86_64.rpm

TunnelYard v1.1.6

Application icon and form focus

• Replace the placeholder application mark with the shield icon used in
  the interface. Windows takes its taskbar and toast-notification icons
  from the installed executable, so both now match the window.
• Give desktop notifications an explicit icon instead of the shell default.
• Restore a visible focus indicator on profile fields, buttons and toggles;
  the previous ring was too faint to see over the dark surface.
• public/icon.svg is now the single source for the mark, rasterized by
  npm run build:icons.

Earlier in 1.1.x

• Apply and verify the MTU negotiated for each session before installing tunnel IP/routes.
• Validate adapter, IP, routes and effective MTU before showing connected; optionally check an internal TCP service configured in the profile editor.
• Recheck isolated service-probe failures without reauthenticating; show verification in progress and disconnect after three consecutive failures. Topology loss remains immediate.
• Detect tunnel loss and stale supervisor status; stop retrying rejected cookies or sessions where the gateway forbids reconnect-after-drop.
• Apply Fortinet split-DNS with scoped Windows NRPT policies and remove owned settings on disconnect.
• Retain secure CA/fingerprint verification and distinguish an unknown-CA warning from a verified certificate pin.
• Install application updates from official releases only.

Packages

• .deb — Debian / Ubuntu / Mint
• .rpm — Fedora / RHEL / Rocky / Alma / openSUSE
• .dmg / .zip — macOS, Intel and Apple Silicon (requires openfortivpn via Homebrew)
• .exe — Windows x64 (setup installs OpenConnect 9.21 on first use)

All platforms import openfortivpn .conf profiles. See the README for
Windows option compatibility and signing / notarization notes.

New platforms: validation limits

Windows and macOS support is new. Automated checks cover profile
translation, local TLS/authentication and network cleanup logic.
Windows MTU, service reachability and split-DNS were also checked on a
real FortiGate session; other gateways and macOS still require native validation.
Windows currently supports IPv4 SSL VPN. SAML and all MFA variants
are not verified. The packages may trigger SmartScreen/Gatekeeper
warnings when signing credentials are not configured.

Install / upgrade (Debian & Ubuntu)

After installing once, updates come with sudo apt upgrade:

sudo apt install ./tunnel-yard_*_amd64.deb
# postinst installs the archive key and APT source automatically
sudo apt update && sudo apt upgrade

Or add the repo manually:

curl -fsSL https://lucascavalheri.github.io/tunnel-yard/apt/tunnel-yard-archive-keyring.asc \
  | sudo tee /usr/share/keyrings/tunnel-yard-archive-keyring.asc >/dev/null
echo 'deb [arch=amd64 signed-by=/usr/share/keyrings/tunnel-yard-archive-keyring.asc] https://lucascavalheri.github.io/tunnel-yard/apt ./' \
  | sudo tee /etc/apt/sources.list.d/tunnel-yard.list
sudo apt update && sudo apt install tunnel-yard

Fedora / RPM

sudo dnf install ./tunnel-yard-*.x86_64.rpm

TunnelYard v1.1.5

Windows tunnel reliability

• Apply and verify the MTU negotiated for each session before installing tunnel IP/routes.
• Validate adapter, IP, routes and effective MTU before showing connected; optionally check an internal TCP service configured in the profile editor.
• Recheck isolated service-probe failures without reauthenticating; show verification in progress and disconnect after three consecutive failures. Topology loss remains immediate.
• Detect tunnel loss and stale supervisor status; stop retrying rejected cookies or sessions where the gateway forbids reconnect-after-drop.
• Apply Fortinet split-DNS with scoped Windows NRPT policies and remove owned settings on disconnect.
• Retain secure CA/fingerprint verification and distinguish an unknown-CA warning from a verified certificate pin.

Packages

• .deb — Debian / Ubuntu / Mint
• .rpm — Fedora / RHEL / Rocky / Alma / openSUSE
• .dmg / .zip — macOS, Intel and Apple Silicon (requires openfortivpn via Homebrew)
• .exe — Windows x64 (setup installs OpenConnect 9.21 on first use)

All platforms import openfortivpn .conf profiles. See the README for
Windows option compatibility and signing / notarization notes.

New platforms: validation limits

Windows and macOS support is new. Automated checks cover profile
translation, local TLS/authentication and network cleanup logic.
Windows MTU, service reachability and split-DNS were also checked on a
real FortiGate session; other gateways and macOS still require native validation.
Windows currently supports IPv4 SSL VPN. SAML and all MFA variants
are not verified. The packages may trigger SmartScreen/Gatekeeper
warnings when signing credentials are not configured.

Install / upgrade (Debian & Ubuntu)

After installing once, updates come with sudo apt upgrade:

sudo apt install ./tunnel-yard_*_amd64.deb
# postinst installs the archive key and APT source automatically
sudo apt update && sudo apt upgrade

Or add the repo manually:

curl -fsSL https://lucascavalheri.github.io/tunnel-yard/apt/tunnel-yard-archive-keyring.asc \
  | sudo tee /usr/share/keyrings/tunnel-yard-archive-keyring.asc >/dev/null
echo 'deb [arch=amd64 signed-by=/usr/share/keyrings/tunnel-yard-archive-keyring.asc] https://lucascavalheri.github.io/tunnel-yard/apt ./' \
  | sudo tee /etc/apt/sources.list.d/tunnel-yard.list
sudo apt update && sudo apt install tunnel-yard

Fedora / RPM

sudo dnf install ./tunnel-yard-*.x86_64.rpm

TunnelYard v1.1.4

Windows tunnel reliability

• Apply and verify the MTU negotiated for each session before installing tunnel IP/routes.
• Validate adapter, IP, routes and effective MTU before showing connected; optionally check an internal TCP service configured in the profile editor.
• Recheck isolated service-probe failures without reauthenticating; show verification in progress and disconnect after three consecutive failures. Topology loss remains immediate.
• Detect tunnel loss and stale supervisor status; stop retrying rejected cookies or sessions where the gateway forbids reconnect-after-drop.
• Apply Fortinet split-DNS with scoped Windows NRPT policies and remove owned settings on disconnect.
• Retain secure CA/fingerprint verification and distinguish an unknown-CA warning from a verified certificate pin.

Packages

• .deb — Debian / Ubuntu / Mint
• .rpm — Fedora / RHEL / Rocky / Alma / openSUSE
• .dmg / .zip — macOS, Intel and Apple Silicon (requires openfortivpn via Homebrew)
• .exe — Windows x64 (setup installs OpenConnect 9.21 on first use)

All platforms import openfortivpn .conf profiles. See the README for
Windows option compatibility and signing / notarization notes.

New platforms: validation limits

Windows and macOS support is new. Automated checks cover profile
translation, local TLS/authentication and network cleanup logic.
Windows MTU, service reachability and split-DNS were also checked on a
real FortiGate session; other gateways and macOS still require native validation.
Windows currently supports IPv4 SSL VPN. SAML and all MFA variants
are not verified. The packages may trigger SmartScreen/Gatekeeper
warnings when signing credentials are not configured.

Install / upgrade (Debian & Ubuntu)

After installing once, updates come with sudo apt upgrade:

sudo apt install ./tunnel-yard_*_amd64.deb
# postinst installs the archive key and APT source automatically
sudo apt update && sudo apt upgrade

Or add the repo manually:

curl -fsSL https://lucascavalheri.github.io/tunnel-yard/apt/tunnel-yard-archive-keyring.asc \
  | sudo tee /usr/share/keyrings/tunnel-yard-archive-keyring.asc >/dev/null
echo 'deb [arch=amd64 signed-by=/usr/share/keyrings/tunnel-yard-archive-keyring.asc] https://lucascavalheri.github.io/tunnel-yard/apt ./' \
  | sudo tee /etc/apt/sources.list.d/tunnel-yard.list
sudo apt update && sudo apt install tunnel-yard

Fedora / RPM

sudo dnf install ./tunnel-yard-*.x86_64.rpm

TunnelYard v1.1.3

Windows tunnel reliability

• Apply and verify the MTU negotiated for each session before installing tunnel IP/routes.
• Validate adapter, IP, routes and effective MTU before showing connected; optionally check an internal TCP service configured in the profile editor.
• Recheck isolated service-probe failures without reauthenticating; show verification in progress and disconnect after three consecutive failures. Topology loss remains immediate.
• Detect tunnel loss and stale supervisor status; stop retrying rejected cookies or sessions where the gateway forbids reconnect-after-drop.
• Apply Fortinet split-DNS with scoped Windows NRPT policies and remove owned settings on disconnect.
• Retain secure CA/fingerprint verification and distinguish an unknown-CA warning from a verified certificate pin.

Packages

• .deb — Debian / Ubuntu / Mint
• .rpm — Fedora / RHEL / Rocky / Alma / openSUSE
• .dmg / .zip — macOS, Intel and Apple Silicon (requires openfortivpn via Homebrew)
• .exe — Windows x64 (setup installs OpenConnect 9.21 on first use)

All platforms import openfortivpn .conf profiles. See the README for
Windows option compatibility and signing / notarization notes.

New platforms: validation limits

Windows and macOS support is new. Automated checks cover profile
translation, local TLS/authentication and network cleanup logic.
Windows MTU, service reachability and split-DNS were also checked on a
real FortiGate session; other gateways and macOS still require native validation.
Windows currently supports IPv4 SSL VPN. SAML and all MFA variants
are not verified. The packages may trigger SmartScreen/Gatekeeper
warnings when signing credentials are not configured.

Install / upgrade (Debian & Ubuntu)

After installing once, updates come with sudo apt upgrade:

sudo apt install ./tunnel-yard_*_amd64.deb
# postinst installs the archive key and APT source automatically
sudo apt update && sudo apt upgrade

Or add the repo manually:

curl -fsSL https://lucascavalheri.github.io/tunnel-yard/apt/tunnel-yard-archive-keyring.asc \
  | sudo tee /usr/share/keyrings/tunnel-yard-archive-keyring.asc >/dev/null
echo 'deb [arch=amd64 signed-by=/usr/share/keyrings/tunnel-yard-archive-keyring.asc] https://lucascavalheri.github.io/tunnel-yard/apt ./' \
  | sudo tee /etc/apt/sources.list.d/tunnel-yard.list
sudo apt update && sudo apt install tunnel-yard

Fedora / RPM

sudo dnf install ./tunnel-yard-*.x86_64.rpm