Skip to content

CryptBridge 0.12.1

Latest

Choose a tag to compare

@github-actions github-actions released this 31 Oct 05:52
150333b

You only need CryptBridge.exe. Everything else is an optional backup.

Backup copies, unchanged originals:

Did you use an rclone of your own so far (on the PATH or next to CryptBridge.exe)? CryptBridge now uses exactly rclone 1.75.2: click Download rclone once, and if you use the LAN access, allow it in the Windows firewall once more.

What's new

Built on GitHub, ready for code signing. CryptBridge works exactly as in 0.12.0. This release is about where the exe comes from.

Windows

  • Built by GitHub Actions from the source in this repository, never on a private PC, with the tests running against exactly the pinned rclone. A dry run checks the whole build without publishing anything.
  • Code signing prepared: free code signing through the SignPath Foundation is applied for. Until it is active CryptBridge.exe stays unsigned. Only CryptBridge.exe will ever be signed; the rclone and WinFsp copies stay the unchanged originals. What CryptBridge sends where, what it changes on your system and how to uninstall it: code signing policy.
  • New in the README: how to uninstall CryptBridge completely.
  • Your settings, vaults and the app lock stay as they are. rclone stays at 1.75.2.

Linux server

  • Nothing changed. Updating the server is not needed.

Updating

  • Windows: quit CryptBridge (wait until no uploads are running), replace CryptBridge.exe with the new one and start it.
  • Server: nothing to do.

Downloads

  • CryptBridge.exe: Windows 11 (64-bit), needs WinFsp
  • setup.sh: Linux server (Ubuntu / Debian)
  • Backup copies (optional, see above): the four rclone ZIP files, winfsp-2.1.25156.msi, rclone-LICENSE.txt, WinFsp-LICENSE.txt

CryptBridge.exe is not code signed, so Windows SmartScreen may warn. Code signing policy