Skip to content

CryptBridge 0.13.2

Latest

Choose a tag to compare

@github-actions github-actions released this 22 Nov 11:04
9dba740

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

Security update. CryptBridge works exactly as in 0.13.1.

Windows

  • Built with Go 1.27.4, which fixes a flaw in Go's own HTTP code (GO-2026-6859). CryptBridge talks to the cloud services and to GitHub over HTTPS, so updating is recommended.
  • Updated libraries: golang.org/x/crypto 0.59.0 (fixes GO-2026-5932; CryptBridge did not use the affected code), x/net, x/sys and x/text.
  • Your settings, vaults and the app lock stay as they are. rclone stays at 1.75.2.

Linux server

  • Nothing changed, only the version number.

README

  • A clear disclaimer: CryptBridge is free hobby software without any warranty. Keep backups of your important files and print every vault's emergency sheet.

Updating

  • Windows: quit CryptBridge (wait until no uploads are running), replace CryptBridge.exe with the new one and start it.
  • Server: nothing to do. sudo cryptbridge setup is not needed for this version.

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

💜 Happy with CryptBridge? A ⭐ on GitHub is the easiest way to let me know, and it helps CryptBridge qualify for free code signing, so the Windows warning goes away for everyone. Or tell me what you use it for.