Skip to content

CryptBridge 0.13.1

Choose a tag to compare

@github-actions github-actions released this 22 Nov 10:14
ac109f4

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

Safer with your data. No new features: this release closes gaps where files or keys could be lost in rare cases.

Windows

  • Settings survive a power cut. The settings file is written safely to the disk, and the last good version is kept as settings.dat.bak. If the file is ever damaged, CryptBridge takes the backup back by itself and tells you. Before, a damaged file looked like a wrong app password, or CryptBridge started empty.
  • Disconnecting or quitting during a copy now warns you. Until now only uploads already waiting were counted, not a file still being copied onto the drive.
  • Moving the cache is refused while files in it still wait for their upload. Before, they stayed behind in the old folder and were never uploaded.
  • A full cache and failed uploads are now shown at the drive and as a red tray icon, instead of only "waiting".
  • Shutting down or signing out while uploads run: Windows now shows that CryptBridge is still writing files, so you can wait. Without the app lock, the drives are also closed cleanly when you sign out.
  • After resetting a forgotten app password, CryptBridge says if files were left in the cache.
  • LAN full access: a note that an upload from a device that breaks off stays as a shorter file.
  • Your settings, vaults and the app lock stay as they are. rclone stays at 1.75.2.

Linux server

  • Every vault is checked before it is mounted: its cloud folder must be there and the keys must open it. A renamed or emptied folder no longer shows up as an empty vault that new files would split.
  • A cloud that cannot be reached during setup is no longer taken for an empty folder.
  • Cache notes that cannot be read count as files still waiting for their upload.

Updating

  • Windows: quit CryptBridge (wait until no uploads are running), replace CryptBridge.exe with the new one and start it. On the first save, settings.dat.bak appears next to your settings.
  • Server: run sudo cryptbridge setup once, so that the vault services get the new check. Your vaults and keys stay.

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.