v1.2.2

Changed

• The VPN core is TrustTunnel 1.1.7, up from 1.1.5, with newer DNS and TLS
  libraries.
  • It fixes a crash that could happen when an HTTP/3 connection attempt was
    cut short by the network going away, as on waking from sleep or switching
    Wi-Fi.
  • Linux: when NetworkManager briefly swapped default routes, as it does when
    Wi-Fi reconnects or its connectivity check changes its mind, the core could
    decide there was no network at all. With the kill switch on, FreeTunnel then
    waited for a network that was already there. The core keeps the real default
    route through such swaps now.
  • A DNS server given by name rather than address, such as
    udp://dns.example.com, was skipped, and a config with no other DNS server
    failed to connect. The name is now looked up through public DNS and the
    server is used. A name only your own network knows, such as router.lan, is
    not found this way: give the server's address instead.
  • A server whose certificate has an empty part in its name, as only unusual
    hand-made certificates do, used to connect. It is now refused during the
    handshake, even with "Skip certificate check" on, and the log speaks of a
    decode error (DECODE_ERROR).

Fixed

• DNS servers separated by spaces or semicolons work. The config editor
  accepts "1.1.1.1 8.8.8.8" as well as "1.1.1.1, 8.8.8.8", but the list was
  handed to the VPN core split on commas only, as one server. Such a config
  failed to connect; with the new core it would have connected with no working
  DNS. Each server is its own entry now.
• Boxes fit what they hold.
  • A question such as "Add a VPN server from this link?" came in a card spread
    across the window around two short lines. Questions, and the messages that
    appear at the bottom of the window, are now as wide as their longest line.
  • The list of configs under the name on Home had a fixed width: wide around
    short names, while a long one was cut all the same. It is now as wide as the
    longest name, within the window. The menu for adding a config was as wide
    around its three short items; it now fits them.
  • Names were cut where the window had room for them: the active config on Home,
    and addresses, domains, profiles and applications on the Split and Settings
    pages. They are cut only where the window ends now. In the config list, the
    connected config's name was left little room by its ping, "connected" and the
    three buttons; the buttons take less of the row now, so the name has more.
  • Save and Cancel in the config editor grow to fit longer words, as in Russian.
  • A choice or a menu item longer than the window can show ends in "…". It used
    to stop at the edge, part of it hidden under the tick.
• Links respond over their words. "Check for updates", the log file's path
  and "Choose a file instead…" took a click anywhere on their row, far to the
  right of the words.
• Messages at the bottom of the window
  • A name with no spaces in it, such as a long file name, ran past both edges.
    It wraps now.
  • A message longer than three lines was cut, and the part left out was often
    the one saying what to do. Up to six lines show now, and a long message stays
    up longer.
  • On Home a message sat across the speed tiles and cut them in half. A short
    one now shows between the config name and the tiles, and a longer one covers
    the tiles instead. In a window of the default size, the longest messages, of
    five or six lines, can still reach up over the config name.
• The config list on Home and the drop-down lists close when the window is
  resized. They stayed open, away from what they belong to.
• Updates in Settings
  • The download arrow tipped onto its side under the pointer, and the retry
    arrow turned against its own direction. Now the download arrow, under the
    pointer, bends round clockwise into ↻; clicked, that ↻ turns while the update
    downloads, and if the pointer leaves without a click it straightens back into
    ↓. The retry arrow leans the way it goes.
  • Once an update was downloaded, the arrow and the line beside it both opened
    the release web page. After the download they offer nothing more: the
    installer, the disk image or the folder with the file has been opened. On
    Linux, if FreeTunnel could not open that folder, the line says where the file
    is and offers the release page.
  • When FreeTunnel runs as an AppImage and could not replace its own file, the
    row said so, but the arrow and the line still opened the release page. They
    now offer ↻, which downloads the update again and tries once more, for when
    the file can be written to.
  • After a failed download the row offers what can help. A release with nothing
    for your system offers its page (↗). One that is unsigned, or whose
    signature does not match, is checked for again rather than downloaded again.
    Other failures are retried as before.
  • A check or a download whose connection stopped answering showed "Checking…"
    or the same percentage for many minutes, and nothing in the row could be
    clicked meanwhile. It now gives up after 30 seconds without progress, and
    says the server stopped responding.
  • While an update downloads, the arrow turns, and while FreeTunnel checks for
    one, three dots hop in turn. A "…" stood beside the line instead, and it did
    not move whether the download did or not.
  • On Windows, and when FreeTunnel runs as an AppImage, installing an update
    closes FreeTunnel, and the VPN goes down with it. The line offering the
    update now says so.
  • Windows: if the downloaded installer could not be started, as when the
    administrator prompt was answered No, FreeTunnel quit all the same, and the
    VPN went down with it. It now stays open and says so, and ↻ tries again.
  • Changing the language announced an available update again.
• Home
  • The logo's pulse while connecting or disconnecting never moved. It pulses now.
  • Clicking the session time under the logo, or the space beside the logo,
    disconnected. Only the logo does now.
  • When a connection started or ended, the config name under the logo jumped
    while the logo glided. Both glide now.
  • With no configs, clicking the logo said "Select a config first", with none to
    select, and "Add a config" under it only switched to the Configs page. Both
    now open the menu for adding one. So does the + beside the config name, which
    also only switched to the Configs page.
• Configs
  • While a config was connecting, or FreeTunnel was switching to another one,
    nothing in the list said so. The active config now says "connecting…" until
    it says "connected".
  • The button that opens a config for editing showed ⋯, which suggests a menu.
    It shows a pencil now.
  • With no configs, "Add a config" looked like faint placeholder text and did
    not respond to the pointer, though it could be clicked. It is a link now, like
    the same words on Home.
• Light theme: text on dark buttons is white again. Since 1.2.1 the Save
  label in the config editor and the name on the chosen profile were black on
  dark grey. Hovering chips, hotkey fields and the Cancel buttons also showed
  almost no change; it does now.
• Tray menu: while connecting, the first item read "Connecting…" like a
  status, and choosing it cancelled the connection. It reads "Cancel connecting"
  now. While disconnecting it cannot be chosen, since it did nothing then.
• Hover and pointer
  • With a question, the config editor, "Add an application", the config list
    on Home, a drop-down list or a menu open, what lay behind still lit up under
    the pointer, though a click there never reached it. It no longer reacts.
  • A few buttons showed the hand pointer, where the others and the window's own
    buttons show the arrow. They show the arrow now; links keep the hand.
  • The back arrow in the config editor responds a little around it, as the one in
    "Add an application" does.
  • A hotkey field flickered as it started or stopped listening for keys.
  • The links at the bottom of Settings underline under the pointer, like the
    others.
  • The drop-down lists fade out as they fade in, and list rows fade their
    highlight everywhere.
• Adding an application no longer freezes the window the first time. On
  Windows, reading every Start Menu shortcut could stall the window for a while.
  The list is now read in the background, and the picker says it is looking.

Installing

• Linux: install the .deb on Debian/Ubuntu/Pop!_OS
  (sudo apt install ./freetunnel-linux-x86_64.deb) — it bundles its own Qt
  and appears in the app menu. Or run the portable AppImage
  (chmod +x freetunnel-linux-x86_64.AppImage && ./freetunnel-linux-x86_64.AppImage).
• macOS: open the .dmg and drag FreeTunnel to Applications. The app is
  ad-hoc signed but not notarized, so on first launch right-click it → Open
  (or run xattr -dr com.apple.quarantine /Applications/FreeTunnel.app).
• Windows: run the Setup.exe. SmartScreen may warn — choose
  "More info" → "Run anyway".

Verify your download against SHA256SUMS.txt (signed as SHA256SUMS.txt.sig).

Every commit in this release: v1.2.1...v1.2.2

v1.2.1

Security

• Split tunnelling by application could send a connection the wrong way. To
  tell which program a connection belongs to, the app looked its port number up
  in the system's list of open sockets. But one number can be in use by two
  programs at once: on different network addresses, or once over IPv4 and once
  over IPv6. This is not rare, because local services, containers and the system
  itself hold ports of their own. When the two collided, the app could answer
  about the wrong one.

  It went wrong both ways. A connection from a program you listed could be taken
  for "not one of yours": with the mode set to "Through VPN", it went outside the
  tunnel instead of through it, unless an address or domain on your list also
  covered where it was going. And a connection from some other program could be
  taken for yours, and follow your rule instead of the rest of your settings.

  Sockets are now told apart by address as well as by number. Two cases are still
  beyond what the app can see: two connections from the same address and port to
  different places, and, on Windows, an IPv6 socket that takes no IPv4 traffic.

Changed

• The window fits in with your system.
  • macOS 26 and 27: the window buttons and corners now match other current
    apps, where they looked like an older macOS. The app icon has a dark
    rounded-square background of its own, so macOS no longer puts it inside a
    grey one. Dragging the window by its top edge works on a trackpad, and
    double-clicking there zooms or minimises it as set in System Settings.
  • Windows: the window no longer gives up what Windows gives an ordinary
    window. It has a shadow, and on Windows 11 rounded corners. It snaps when you
    drag it to an edge of the screen, and on Windows 11 hovering over the maximise
    button shows the Snap Layouts choices. Right-clicking the empty part of the
    top of the window, or pressing Alt+Space, opens the window menu. The buttons
    in the corner are drawn to match Windows 11's. This is new on Windows; if the
    window misbehaves, please open an issue.
  • Linux: on GNOME and Pop!_OS 22.04 the window buttons are the ones your
    desktop uses, in the places it puts them. On Pop!_OS 22.04 as it comes that
    is minimise and close, with no maximise, and on GNOME as it comes only close.
    Where there is no tray icon, closing still quits the app; Super+H hides the
    window instead. With Pop's theme or GNOME's standard look the buttons also
    look like the desktop's own. Double-, middle- and right-clicking the top of
    the window do what the desktop is set to do, except rolling the window up or
    maximising it in one direction only. A right-click opens the window manager's
    own menu where the window manager supports that, as GNOME's does. Change the
    layout in Tweaks and the window follows at once. On other desktops, such as
    KDE or XFCE, the app cannot read these settings, and keeps three buttons on
    the right.
• Windows: the program says what it is. The app and its installer now carry
  their name and version, and File Properties shows them. Before, the name and
  version fields there were empty.
• FreeTunnel now needs macOS 12 or later. 1.2.0 said it needed macOS 11, but
  it could not start there either: the Qt libraries it is built on need 12.
• Global hotkeys are off until you turn them on. The keys they came with,
  Ctrl+Shift+T, E and D (⌘⇧T, E and D on macOS), are what browsers and terminals
  use to reopen a closed tab and more, and a global hotkey takes its keys away
  from every other program. If you used them as they came, turn them back on in
  Settings → Hotkeys. If you had changed any of the keys, your hotkeys stay as
  they were.
• A hotkey needs Ctrl, Alt or Meta (⌘, ⌥ or ⌃ on macOS), unless it is one of
  F1–F12. Enter, Tab or a letter pressed in the field used to become a hotkey for
  the whole system. Backspace or Delete in the field now removes a hotkey, and
  one that FreeTunnel could not register, because another program or the desktop
  has it, shows in red.
• Config names keep their spaces and punctuation. "Germany · Frankfurt" used
  to be listed as "Germany___Frankfurt". Only characters that some system does
  not allow in a file name, such as / \ : * ? " < > |, are replaced, and
  characters that draw nothing are left out. Configs you already have keep their
  names.

Fixed

• Linux: «Show FreeTunnel» in the tray menu did not bring the window back on
  GNOME and Pop!_OS, and neither did starting FreeTunnel again while it was
  running. The window stayed minimised and only asked for attention: the request
  reached the app from the panel rather than as a click on the window, and the
  window manager took it for another program trying to steal focus. It now comes
  forward, and a window closed while maximised comes back maximised.
• Linux: the "System" theme showed a light window on a dark desktop on GNOME
  and Pop!_OS. It follows the desktop's light or dark setting now, including when
  you switch it while the app is open. Other desktops are followed the same way
  if they tell apps whether they are light or dark; not all of them do.
• macOS 27: clicking the menu-bar icon could make the app quit. This is a
  fault in the Qt version FreeTunnel is built on, and the app now works around
  it.
• Connecting
  • Switching to a config whose server was down showed no error. The app said
    "Connecting…" for as long as it kept retrying, and ignored the next config
    you picked. The error now shows, and the next pick switches.
  • Picking another config while a switch was still connecting could leave the
    tunnel on the first one while the app showed the second. The last pick wins.
  • Saving the config you are connecting with, say with its password corrected,
    starts the attempt again with what you saved. So does changing a rule or the
    kill switch while connecting. The attempt used to go on with the old
    settings until you reconnected.
  • A connection the VPN core refused at once could stay on "Connecting…" until
    you clicked.
  • Choosing the ticked config in the tray menu only removed its tick. It now
    turns the connection off, or on when it was off.
  • Double-clicking the logo connected and at once cancelled. It now counts as
    one click.
  • After deleting the active config, the next start could make a different
    config active, and with "Connect on startup" connect to it.
  • Windows: without wintun.dll next to FreeTunnel.exe, Connect waited a minute
    and then blamed the administrator prompt. It now says wintun.dll is missing,
    before asking for administrator rights.
• Tray and window
  • Linux: clicking the tray icon did nothing. A click on KDE, or a double-click
    on GNOME, now brings the window back.
  • Linux: when the tray came up after FreeTunnel, as a panel can at login,
    there was no tray icon for the whole session, and the window's close button
    quit the app. The icon now appears once the tray does.
  • Linux: the tray menu dropped an underscore from config names. An underscore
    there now shows as a space, because desktops read underscores in menus in
    ways that no spelling of one gets right everywhere.
  • When something started from the tray failed while the window was hidden,
    the error showed only inside the hidden window, and was gone before you saw
    it. It is also sent as a notification now, and waits in the window until
    you open it.
  • Minimising a maximised window made it come back at normal size. It stays
    maximised.
  • macOS: freetunnel://toggle, connect and disconnect no longer bring back a
    window hidden in the menu bar.
  • macOS: «Show FreeTunnel» in the menu-bar menu did nothing after ⌘H or Hide
    Others.
  • macOS: clicking the Dock icon took a zoomed or full-screen window out of zoom
    or full screen. A tt:// link left a window minimised to the Dock where it
    was, with the question about the import inside it.
  • macOS: the red button in full screen left an empty black screen. The window
    now leaves full screen first.
  • macOS: ⌘W hides the window like the red button, and ⌘M minimises it. Neither
    did anything.
  • Windows: a second launch or a tt:// link could leave the running window
    behind others.
• Configs and questions
  • Renaming a config only by letter case, "work" to "Work", gave "Work-2" on
    Windows and macOS.
  • When a config was added while the export menu or the delete question was
    open (from a link, a file or the clipboard), exporting or deleting could act
    on the config next to the one you chose. A copied deep link then carried
    that config's password.
  • Escape in the file dialog for a certificate or an application closed the
    editor or the application picker behind it, and on Linux could crash the
    app.
  • In the question about importing a link, a long server name was cut off at
    both ends, and clicking inside the question cancelled it. In Russian, three
    buttons ran into its edges.
  • An import question that appeared over the editor's "Discard unsaved
    changes?" did not get Return and Escape: Return discarded the edits behind
    it.
  • A hotkey field still recording under a question took the Return meant for
    the question as its hotkey. Questions now take the keyboard while they are
    open.
  • Tab moves between the fields of the config editor.
  • After a failed Save, the error covered the editor's Save button and took the
    next click. Over the editor, messages now show at the top.
  • On an empty Configs page, «Add a config» could not be clicked.
• Settings, Split and Logs
  • Logs: Clear left the old log on screen if some of it was selected, and a
    selection stopped the view from updating at all. With logging off, the page
    now says so instead of waiting for lines that will not come.
  • Settings: th...

v1.2.0

Added

• Split tunnelling by application. Next to the addresses on the Split
  tunnelling page you can now name programs, and they follow whichever way round
  the split is already set: with "all traffic except the listed" they leave the
  tunnel, with "only the listed" they are the only ones inside it. Add a program
  from the list of what is installed on the machine, by dragging its icon onto
  the page, or by picking the file yourself.

  On macOS a rule covers the application rather than one file inside it. A
  browser does its networking from a separate helper process, so a rule naming
  the program you actually picked would otherwise never match a single one of
  its connections.

  Nothing extra has to be installed for this: no driver, no system extension, no
  permission dialog. Which program a connection belongs to is worked out by
  asking the operating system who owns the socket it came from, on the
  connection itself, so a rule added while the VPN is up applies to the next
  connection rather than the next session.

  Programs belong to the profile, the same as the addresses above them, so a set
  for work and a set for everything else switch together. Any list you had before
  this release becomes the starting list of every profile you already had, which
  is what it used to mean.

Security

• If you chose HTTP/3 as the protocol for a config, the server's certificate
  was not being checked at all. The connection was made before the check could
  be armed, so none of the three things that normally establish trust ran: not
  the system's list of certificate authorities, not a certificate you imported
  with the config, not even the "skip verification" switch. In practice that
  means someone positioned between you and the server — on a shared Wi-Fi
  network, or at your provider — could have presented any certificate, and the
  app would have accepted it and sent your traffic and password through them.
  This is fixed in the VPN core this release moves to.

  Configs on HTTP/2 were never affected, and HTTP/2 is what new configs use
  unless you change it. If you use HTTP/3, please update.

  One consequence to expect: a self-signed server on HTTP/3 will now be refused
  with a certificate error if the config does not carry the server's certificate
  or have verification switched off. Re-import the config from its link — the
  certificate travels inside it — or turn verification off deliberately.

• Windows: a program running as another user of this computer could give
  FreeTunnel orders. A second launch forwards freetunnel:// and tt:// links
  to the window already open, over a local channel that is supposed to accept
  only connections from you. On the receiving side that check was asking about
  the wrong end of the connection, so it described this very process and could
  never refuse anything. Anything that reached the channel could switch the VPN
  on or off, or hand it a server link to import.

Fixed

• The Linux .deb could not be installed on a current system. It asked for a
  package Debian 13 and Ubuntu 25.04 no longer ship, with a fallback name that
  has never existed in either. It asks for pkexec now — the program that
  actually starts the privileged part.
• Updating on Linux could leave nothing running. The replacement was started
  while the copy being replaced still held the channel above, so it handed itself
  over to a program that was in the middle of quitting and then exited. Both
  disappeared, and the app had to be started again by hand.
• Editing a server could save over a different one. The editor remembered
  which row of the list it opened on, and a config imported meanwhile is added to
  the top and moves every row down. Saving after that wrote the form over
  whichever server had taken that place — silently, and leaving the original
  behind as a duplicate. It remembers the file now, and says so plainly if that
  file has been deleted in the meantime.
• A config file could be rewritten into something nothing can read. Anything
  in it this app does not itself write — a setting from your provider spread over
  several lines — was cut off after its first line whenever the file was saved
  back, which happens on import and on every connect. A certificate written in
  any form other than the one this app uses was read as empty and then written
  back as empty, so a pinned server certificate was lost from the file.
  Configurations that use single quotes, which are perfectly ordinary, were read
  as blank entirely.
• Sharing a config as a link dropped all but the first certificate when it
  pinned a chain rather than a single one.
• The app could sit on "Connecting…" for good. If something else on the
  computer was already using the port the privileged helper picks, the app would
  connect to it, wait for an answer that was never coming, and show nothing —
  after you had already entered your administrator password. It now gives up and
  says what happened.
• macOS: "Start at login" could say it was on while doing nothing. The entry
  records where the app was when you switched it on, and on macOS that is usually
  not where it ends up — people run it from the disk image or from Downloads and
  move it to Applications afterwards. Nothing rewrote it, and the switch went on
  claiming to be on for good.
• Windows: the Start menu and desktop shortcuts went into one account. The
  program is installed for the whole machine, but its shortcuts landed in the
  profile of whichever account Windows ran the installer as — often not the one
  that asked for it. They are made for all users now, and an upgrade clears the
  old ones rather than leaving a second copy of each.
• Settings no longer freezes while it opens. It was checking for a password
  keyring three times over, each check stopping the interface while it ran. It
  asks once; and the notice about a missing keyring now goes away once one is
  there, instead of staying until the app is restarted.
• HTTP/3: the app could keep saying it was connected after the connection had
  actually died, leaving traffic going nowhere until you reconnected by hand.
• HTTP/3: a config listing several server addresses could crash the privileged
  helper while connecting, which ends the connection attempt.
• HTTP/3: each connection attempt to a server with several addresses leaked a
  network handle. Enough of them and the app would start reconnecting on its own.

Installing

• Linux: install the .deb on Debian/Ubuntu/Pop!_OS
  (sudo apt install ./freetunnel-linux-x86_64.deb) — it bundles its own Qt
  and appears in the app menu. Or run the portable AppImage
  (chmod +x freetunnel-linux-x86_64.AppImage && ./freetunnel-linux-x86_64.AppImage).
• macOS: open the .dmg and drag FreeTunnel to Applications. The app is
  ad-hoc signed but not notarized, so on first launch right-click it → Open
  (or run xattr -dr com.apple.quarantine /Applications/FreeTunnel.app).
• Windows: run the Setup.exe. SmartScreen may warn — choose
  "More info" → "Run anyway".

Verify your download against SHA256SUMS.txt (signed as SHA256SUMS.txt.sig).

Every commit in this release: v1.1.9...v1.2.0

v1.1.9

Fixed

• macOS: FreeTunnel no longer dies with a crash if you close it while it is
  getting ready to connect. That is the moment macOS asks whether the app may
  read the password saved for this config, and quitting while the system's
  prompt was on screen ended the app abruptly instead of letting it close.

Changed

• The privileged helper now shuts down in an orderly way when something asks it
  to stop — logging out, or shutting the machine down with the VPN still on. It
  takes the tunnel down on the way out. Before it was stopped where it stood,
  and the routes and DNS it had set up were left for whatever came next to
  clear away.

Installing

• Linux: install the .deb on Debian/Ubuntu/Pop!_OS
  (sudo apt install ./freetunnel-linux-x86_64.deb) — it bundles its own Qt
  and appears in the app menu. Or run the portable AppImage
  (chmod +x freetunnel-linux-x86_64.AppImage && ./freetunnel-linux-x86_64.AppImage).
• macOS: open the .dmg and drag FreeTunnel to Applications. The app is
  ad-hoc signed but not notarized, so on first launch right-click it → Open
  (or run xattr -dr com.apple.quarantine /Applications/FreeTunnel.app).
• Windows: run the Setup.exe. SmartScreen may warn — choose
  "More info" → "Run anyway".

Verify your download against SHA256SUMS.txt (signed as SHA256SUMS.txt.sig).

Every commit in this release: v1.1.8...v1.1.9

v1.1.8

Fixed

• macOS: clicking the menu-bar icon no longer opens the main window. It only
  shows the menu, as it always should have.
• macOS: clicking the Dock icon brings the window back after you close it. This
  stopped working in 1.1.7 and did nothing at all until now.
• Windows: installing an update over a running FreeTunnel no longer fails partway
  through. The installer now closes it first — cleanly, so your connection is
  taken down properly rather than cut — and this works whether you update from
  inside the app or run the installer yourself.
• Windows: a link opened while FreeTunnel is already running no longer does
  nothing. Longer links were being dropped on their way to the running copy.
• Windows: uninstalling now removes the "launch at startup" entry. It used to be
  left behind, so Windows kept trying to start a program that was gone.
• Windows: the installer is no longer garbled when shown in Russian.
• "Through VPN" with no rules no longer sends all of your traffic outside the
  tunnel while showing you as connected. The full tunnel stays on, and the app
  says why.
• A split-tunnel rule written as ".example.com" now works. It was accepted,
  listed back to you, and quietly never applied.
• The kill switch is no longer taken down while the app reconnects after a
  network change or sleep.
• Linux: the update button now installs the update, or tells you it cannot.
  It used to report success and do nothing.
• Linux: "launch at system startup" now works for AppImage builds, and the
  switch no longer reports "on" when the entry it wrote can no longer start
  anything.
• Linux: global hotkeys are correctly reported as unavailable on Wayland,
  including when the app runs through XWayland. The previous advice on how to
  make them work led into exactly the case where they silently do not.
• Pressing Enter now confirms a dialog, and Escape reliably cancels one — on some
  screens Escape did nothing at all.
• Update checks no longer skip a release: 1.2.0-rc10 is now correctly newer than
  1.2.0-rc9.
• The Downloads/upgrade path no longer offers a package that cannot run on your
  system: the Linux package now states the system version it actually needs.

Security

• Linux: the elevated helper is now started from a path the kernel confirms,
  not one named by environment variables. A process able to set the app's
  environment could previously have the administrator prompt run a file of its
  choosing.
• A link that adds a server now shows which server it is, and warns when the name
  mixes alphabets — the trick behind a name that looks like one you already
  trust.
• An update is now verified to belong to the release being offered, not merely to
  be signed by us. Older releases can no longer be replayed to hold you back on
  an earlier build.

Installing

• Linux: install the .deb on Debian/Ubuntu/Pop!_OS
  (sudo apt install ./freetunnel-linux-x86_64.deb) — it bundles its own Qt
  and appears in the app menu. Or run the portable AppImage
  (chmod +x freetunnel-linux-x86_64.AppImage && ./freetunnel-linux-x86_64.AppImage).
• macOS: open the .dmg and drag FreeTunnel to Applications. The app is
  ad-hoc signed but not notarized, so on first launch right-click it → Open
  (or run xattr -dr com.apple.quarantine /Applications/FreeTunnel.app).
• Windows: run the Setup.exe. SmartScreen may warn — choose
  "More info" → "Run anyway".

Verify your download against SHA256SUMS.txt (signed as SHA256SUMS.txt.sig).

Every commit in this release: v1.1.7...v1.1.8

v1.1.7

Fixed

• The window no longer freezes while your computer asks permission to use your
  saved password. It used to lock up, cursor and all, when you pressed Connect,
  and when you opened, saved, copied, exported or deleted a server.
• Cancelling, or switching to another server, during that wait no longer starts
  a connection you did not ask for.
• The app no longer crashes when you quit, disconnect or switch servers while a
  connection is still being set up.
• Connect is no longer silently ignored after you cancel a connection attempt.
• Changing a setting such as the kill switch during a long connection attempt no
  longer drops a working connection.
• Adding a server while connected no longer shows you as connected to the new
  one while your traffic still goes through the old one.
• Editing a server no longer destroys it when its password cannot be saved.
• Your saved servers no longer disappear if the app is interrupted while saving.
  On Windows, a server list damaged by a crash or a full disk is now repaired
  instead of being rebuilt from scratch at every launch.
• Adding two servers with the same name in quick succession no longer overwrites
  one of them, and no longer puts a long number in its name.
• A link naming a server you already have now asks whether to replace it or keep
  both, instead of deciding for you.
• A failed check for a new version now shows a retry button and the real reason
  it failed. It used to show what looked like a download for an update that did
  not exist, and pressing it started a download instead of checking again.
• Escape closes the topmost window again, even with a drop-down open.
• Ctrl+Q / Cmd+Q can be recorded as a shortcut without quitting the app on the
  spot.
• Delete, export and scrolling in the server list keep working after a server
  arrives in the background.
• Connection details appear in the log again, and Clear logs empties it
  immediately instead of waiting until you disconnect.
• In Russian, the import confirmation, the update-failure notice and the kill
  switch label are translated.

Security

• The VPN could stay fully active, with your traffic still routed through it,
  while the app showed Disconnected — if you switched it off exactly as a
  connection was finishing.
• Another program on your computer could impersonate the app's privileged part
  while you were being asked for your administrator password, take your VPN
  password, and then show you as connected while nothing was protected.
• A server link could replace a server you already had without asking, or hand
  your existing password to the server named in the link.
• Updates are verified before they are installed, so the app cannot be made to
  run a tampered version — or an older, deliberately vulnerable one.
• On Windows, uninstalling could delete everything else in the folder you had
  installed into. The installer now refuses a folder that already holds other
  files.
• On Linux, the app tells you when your system has no password keyring, instead
  of behaving as though your VPN password had been stored securely. Its settings
  folder is no longer readable by other people using the same computer.

Changed

• The confirmation shown for a server link now says what the link actually does.
  It no longer stacks two questions on top of each other, drops the generic
  advice to only add servers you trust, and warns about the one thing you cannot
  check yourself: when the link turns off verification of the server's identity.

Installing

• Linux: install the .deb on Debian/Ubuntu/Pop!_OS
  (sudo apt install ./freetunnel-linux-x86_64.deb) — it bundles its own Qt
  and appears in the app menu. Or run the portable AppImage
  (chmod +x freetunnel-linux-x86_64.AppImage && ./freetunnel-linux-x86_64.AppImage).
• macOS: open the .dmg and drag FreeTunnel to Applications. The app is
  ad-hoc signed but not notarized, so on first launch right-click it → Open
  (or run xattr -dr com.apple.quarantine /Applications/FreeTunnel.app).
• Windows: run the Setup.exe. SmartScreen may warn — choose
  "More info" → "Run anyway".

Verify your download against SHA256SUMS.txt (signed as SHA256SUMS.txt.sig).

Every commit in this release: v1.1.6...v1.1.7

v1.1.6

Builds are unsigned (see README for first-run notes).

• Linux: install the .deb on Debian/Ubuntu/Pop!_OS
  (sudo apt install ./freetunnel-linux-x86_64.deb) — it bundles its
  own Qt and integrates into the app menu. Or run the portable
  AppImage (chmod +x freetunnel-linux-x86_64.AppImage && ./freetunnel-linux-x86_64.AppImage).
• macOS: the app is ad-hoc signed but not notarized. On first launch
  right-click the app → Open (or run
  xattr -dr com.apple.quarantine /Applications/FreeTunnel.app).
• Windows: SmartScreen may warn — choose "More info" → "Run anyway".

Full Changelog: v1.1.5...v1.1.6

Build tools mirror (2026-08-02)

Reviewed copies of the third-party tools the Linux release job runs, mirrored here so the build does not depend on a mutable upstream release.

linuxdeploy and its Qt plugin publish only a continuous release that is rewritten in place — there is no immutable upstream reference to pin, and the asset ids turn over on every rebuild. apt.llvm.org/llvm.sh is executed as root to configure the release compiler. Fetching all three from here means an upstream rebuild can no longer change what a release build runs, and updating them is a deliberate act.

asset	origin	sha256
linuxdeploy-x86_64.AppImage	linuxdeploy/linuxdeploy @ continuous	421ca71d5c69ea97c6309276232990d43df1dcece0edfaa26bbf926ff96ed12e
linuxdeploy-plugin-qt-x86_64.AppImage	linuxdeploy/linuxdeploy-plugin-qt @ continuous	be1b7e166bf9975cfb694ebe6759ba40502ffc6196440d3e64aa90c4dbd67e9f
llvm.sh	apt.llvm.org/llvm.sh	9474ecd78b52aba6e923976b1e9773f5613027cc7e237b9956986cb536e02a36

Refreshing: download from upstream, diff/review, upload here under a new build-tools-<date> tag, and update the URLs and digests in .github/workflows/build.yml. The digests are still verified after download, so a corrupted mirror fails the build too.

v1.1.5

Builds are unsigned (see README for first-run notes).

• Linux: install the .deb on Debian/Ubuntu/Pop!_OS
  (sudo apt install ./freetunnel-linux-x86_64.deb) — it bundles its
  own Qt and integrates into the app menu. Or run the portable
  AppImage (chmod +x freetunnel-linux-x86_64.AppImage && ./freetunnel-linux-x86_64.AppImage).
• macOS: the app is ad-hoc signed but not notarized. On first launch
  right-click the app → Open (or run
  xattr -dr com.apple.quarantine /Applications/FreeTunnel.app).
• Windows: SmartScreen may warn — choose "More info" → "Run anyway".

What's Changed

• Bump actions/setup-python from 6.3.0 to 7.0.0 by @dependabot[bot] in #8
• Bump actions/checkout from 7.0.0 to 7.0.1 by @dependabot[bot] in #9

Full Changelog: v1.1.4...v1.1.5

v1.1.4

Builds are unsigned (see README for first-run notes).

• Linux: install the .deb on Debian/Ubuntu/Pop!_OS
  (sudo apt install ./freetunnel-linux-x86_64.deb) — it bundles its
  own Qt and integrates into the app menu. Or run the portable
  AppImage (chmod +x freetunnel-linux-x86_64.AppImage && ./freetunnel-linux-x86_64.AppImage).
• macOS: the app is ad-hoc signed but not notarized. On first launch
  right-click the app → Open (or run
  xattr -dr com.apple.quarantine /Applications/FreeTunnel.app).
• Windows: SmartScreen may warn — choose "More info" → "Run anyway".

What's Changed

• Bump softprops/action-gh-release from 3.0.1 to 3.0.2 by @dependabot[bot] in #7

Full Changelog: v1.1.3...v1.1.4