Skip to main content

Connect 4.1.1 and 4.1.2

· 6 min read
Tera Insights Team
Tera Insights Team
tiCrypt Team

Two releases shipped on 30 September. 4.1.1 carries the substance: transfers are faster and no longer hang, Windows installs from an MSIX package that upgrades in place, and about thirty fixes land across deployments, cloud drives and SFTP. 4.1.2 adds a reworked Windows window frame.

Installing and upgrading​

Windows now installs from an MSIX package. Installing a newer package upgrades in place and keeps your deployments, application versions, keys and settings. Leftovers from a previous installation are cleaned up on first start, a desktop shortcut is created, and uninstalling from Settings > Apps removes everything the package installed. This needs Windows 10 version 1809 or later, or Windows 11.

The macOS installer shows what you are installing. It carries tiCrypt Connect's name and icon and a welcome page with the version, and it offers Install for me only, which needs no administrator password, alongside the system-wide install. This needs macOS 11 Big Sur or later.

The in-app update setting is gone. It had stopped working. Install the latest installer to update Connect.

Transfers​

Two things changed: how fast transfers run, and what happens when one stops responding.

SFTP pushes are much faster. Up to 64 chunks are now in flight per file. Previously each chunk waited for the one before it, which put a ceiling on throughput that no amount of bandwidth could lift. Connections to an unreachable host now fail quickly instead of waiting, and idle SFTP sessions are kept alive.

Connections to the tiCrypt server are reused across requests, and use HTTP/2 where the server offers it.

A transfer that stops responding now fails instead of hanging. A request that gets no reply times out after two minutes per chunk, or thirty seconds for sign-in checks, and the transfer reports the failure. Slow transfers are unaffected and keep running.

Progress is reported four times a second per transfer, so the interface stays responsive while large transfers are running.

Cloud drives and SFTP​

  • Box folders can be pulled, and large Box folders are pulled completely rather than truncated.
  • Cloud provider sign-in shows the provider's own reason when a sign-in is refused or has expired, instead of failing silently. Two sign-ins can be in progress at once, and each sign-in link works exactly once.
  • Signing in again replaces the previous session and closes its connections, for both SFTP servers and cloud providers. Signing out closes them. Each request runs once, however many times the web app reconnects.
  • Files pulled over SFTP keep their names in the Vault. They previously arrived with random characters appended.
  • SFTP connection errors name the server and the reason.
  • Pull-only providers are marked read-only, so the web app no longer offers push actions that could not succeed.
  • Google Drive listings request only the fields they use.

The Connect window​

On Windows, Connect's toolbar is now the title bar (4.1.2). The native title bar is gone. Minimize, maximize and close sit at the right edge of Connect's own toolbar. Drag the toolbar to move the window, double-click it to maximize or restore, and snap to a screen edge as before.

Everything below shipped in 4.1.1:

  • Native macOS menus (About, Edit, Window) and Windows keyboard shortcuts: Ctrl+R to reload, Ctrl+D to return to Connect, Ctrl+W and Ctrl+Q to quit.
  • Open Connect in your browser from the tiCrypt menu as a signed-in tab, with Cmd+Option+B on macOS or Ctrl+Alt+B on Windows. Opening Connect's local address without a session now shows a notice with a button to open a signed-in tab.
  • Connect works in a browser tab again, including transfers between the Vault and local drives.
  • The application is named tiCrypt Connect in the menu bar, the Dock and the bundle, and the macOS build is signed correctly.
  • On macOS the computer's own disk is listed as Macintosh HD rather than "My Computer".
  • Window position and size are remembered separately from the running application's, and fitted to the screen. The macOS toolbar strip no longer shows in full screen.
  • On Windows, closing the Connect window quits the application.

Deployments and versions​

  • Deployment cards can be reordered by drag and drop, and the order is remembered.
  • Esc leaves delete mode and returns to the deployments, as it already closed the add-deployment and add-version dialogs.
  • Version Manager: re-uploading an installed version no longer creates a duplicate, beta versions are ordered correctly, and each version is listed once.
  • Deployment tooltips and the version footer update when a version is selected or removed, the deployment grid scrolls, and delete-mode and empty-state text are corrected.
  • Connect no longer exits on a bad deployment. A missing deployment, a broken deployment file, or a broken version are all handled, and broken versions can be deleted.
  • Start-up failures appear in a dialog instead of a silent exit, and a busy launcher database is retried.
  • The "Click to retry" caption on unreachable deployments matches the rest of the launcher.

Security​

  • The local API requires Connect's session key. Only Connect's own window, and browser tabs opened from the tiCrypt menu, can use it. Cross-origin access is limited to Connect's own window, and browser-tab sessions are bound to Connect's own address, so pages on other local ports cannot use them.
  • Multi-factor sign-in accepts only http and https addresses, and accepts replies only from the sign-in page. The same address restriction applies to "open in browser".
  • Requests made on behalf of the app, such as update checks, connect only to the public address they validated, and every redirect is checked.
  • The deployment configuration is no longer written to the log, including its registration token, and the session key is redacted from it.

Under the hood​

  • The desktop framework moved from Wails 2.12 to 2.15 (4.1.2).
  • The interface framework moved from Angular 19 to 22, with TypeScript 6 (4.1.1).
  • Interface templates and styles were tidied.

Upgrading​

Download the installer for your platform from the Releases page. There is no configuration change and no migration.

On Windows, the newer MSIX package upgrades in place and keeps your deployments, application versions, keys and settings. On macOS, the installer offers "Install for me only", which needs no administrator password.

Questions about a specific deployment: contact our team.