Skip to content

Releases: burnersen/CryptBridge

Release list

CryptBridge 0.12.1

CryptBridge 0.12.1 Latest
Latest

Choose a tag to compare

View all tags
@github-actions github-actions released this 31 Oct 05:52
v0.12.1
150333b
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

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

Assets 11
Loading

CryptBridge 0.12.0

CryptBridge 0.12.0

Choose a tag to compare

View all tags
@github-actions github-actions released this 30 Oct 22:31
v0.12.0
55f51b2
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

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

Uploads no longer take your whole line. Copying many films to a drive used to fill the upload of your internet line, and on DSL games lagged and video calls stuttered meanwhile. Now you decide how fast CryptBridge uploads.

Windows

  • New on the Settings tab: Uploads.
    • Files uploaded at the same time: 1 to 16. The default stays 4, as before.
    • Upload speed limit in MB/s. Empty means no limit, as before. Set it a little below your upload speed: a speed test shows it in Mbit/s, divide by 8 for MB/s (40 Mbit/s is 5 MB/s).
  • Changes take effect at once, also for uploads that are already running. No reconnecting needed.
  • Downloads are never limited. Opening files and streaming films, also over the LAN access, always run at full speed. Vaults on this PC or a USB drive are not slowed down either.
  • Both values count for all drives and clouds together. See Upload speed.
  • Google Drive: the guide now says clearly that your own Google app needs no branding check or verification. If Google complains about the homepage or the privacy policy, ignore it: what counts is In production on the Audience page, then sign in again once.
  • 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. Going back to 0.11 later is possible: it simply ignores the new upload settings.
  • 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
Loading

CryptBridge 0.11.0

CryptBridge 0.11.0

Choose a tag to compare

View all tags
@burnersen burnersen released this 17 Oct 20:26
v0.11.0
44d4301

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

MEGA joins as the fifth cloud. CryptBridge now locks your files in pCloud, Google Drive, OneDrive, Dropbox and MEGA, also all five at the same time.

Windows

  • Add MEGA at Vaults tab > Add cloud account: type your e-mail address and password right in CryptBridge, plus the six-digit code of your authenticator app if your account has two-factor authentication. No browser and no own app needed.
  • Your MEGA password is not stored. CryptBridge signs in once and keeps only the session MEGA hands out; the password and the code are forgotten right away. When you start CryptBridge again, it carries on without signing in again. Should MEGA end the session (for example after a password change), CryptBridge asks you to sign in again.
  • MEGA does not tell CryptBridge about changes made elsewhere, so files you add on another device or at mega.nz show up in your drive after about a minute.
  • Good to know: MEGA blocks sign-ins for a while after very many in a short time, and free MEGA accounts may only download a certain amount at a time. See Cloud accounts.
  • Your settings, vaults and the app lock stay as they are. rclone stays at 1.75.2.

Linux server

  • MEGA vaults work on the server, too. The transfer block carries the MEGA session; the server needs no password either.
  • Run the new setup.sh before you add a MEGA vault. An older setup does not know MEGA yet and refuses the block with "The transfer block holds no valid cloud sign-in" (the block itself is fine).
  • Your vaults in the other clouds work as before.

README

  • New screenshots of the Windows program and the server menu.

Updating

  • Windows: replace CryptBridge.exe with the new one and start it. Going back to an older CryptBridge later is possible, but it shows a MEGA account only as "not signed in".
  • Server: only needed for MEGA vaults. Download the new setup.sh (see the server guide) and run it; your settings and vaults are kept.

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
Loading

CryptBridge 0.10.1

CryptBridge 0.10.1

Choose a tag to compare

View all tags
@burnersen burnersen released this 17 Oct 18:36
v0.10.1
2f53fc3

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

A security update. CryptBridge works exactly as before.

Windows

  • Built with Go 1.27.2. Go 1.27.0, which 0.10.0 was built with, has known security issues in its network, TLS and file functions. Go 1.27.2 fixes them, and the library golang.org/x/crypto is updated to v0.58.0 as well. govulncheck finds no known issue that affects CryptBridge.
  • Your settings, vaults and the app lock stay as they are. rclone stays at 1.75.2: coming from 0.10.0, nothing is downloaded and the firewall rule of the LAN access keeps working.

Linux server

  • Nothing changed apart from the version number. You do not need to run setup.sh again.

Updating

  • Windows: 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
Loading

CryptBridge 0.10.0

CryptBridge 0.10.0

Choose a tag to compare

View all tags
@burnersen burnersen released this 17 Oct 17:48
v0.10.0
b87a989

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

CryptBridge now uses exactly one rclone version, the one it is tested with (rclone 1.75.2), on Windows and on the Linux server, and keeps it up to date by itself.

Windows

  • Exactly the tested rclone. Every download is checked against a checksum built into CryptBridge. It comes from rclone.org first, then from rclone's release on GitHub, then from the copy kept with this release.
  • Updates by itself. If CryptBridge downloaded an older rclone before, it now replaces it at start without a click and shows the progress. rclone stays in the same place, so the firewall rule of the LAN access keeps working.
  • The first download stays your choice: without rclone, CryptBridge still shows Download rclone.
  • The About page names WinFsp's copyright and links its repository.

Linux server

  • The setup installs exactly rclone 1.75.2, checked against a built-in checksum, and replaces any other version. The services restart with it.

Updating

  • Windows: replace CryptBridge.exe with the new one and start it.
  • Server: download setup.sh again and run it. To keep everything as it is, press Enter at Add a vault, or renew one with a new transfer block? and at Keep the streaming account?:
curl -fsSLO https://raw.githubusercontent.com/burnersen/CryptBridge/main/linux/setup.sh && sudo bash setup.sh

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
Loading

CryptBridge 0.9.1

CryptBridge 0.9.1

Choose a tag to compare

View all tags
@burnersen burnersen released this 17 Oct 10:49
v0.9.1
effabeb

A website on the Linux server (nginx with WordPress, for example) and streaming now take turns on ports 80 and 443 without any work by hand.

Linux server

  • Streaming on pauses your website for you. If another web server uses ports 80 and 443 when you switch streaming on (menu item 2, sudo cryptbridge streaming on or the setup), CryptBridge names it and asks: Pause nginx while streaming is on? Press Enter for yes. Answer n and streaming simply stays off.
  • Streaming off brings it back. Switching streaming off asks: Start nginx again? Press Enter, and the web server runs again just as it did before, including whether it starts with the server. While streaming is on, it does not start after a restart of the server, so it cannot take the ports from streaming.
  • Only what CryptBridge paused. A web server that you switched off yourself is never started. If there is no other web server, nothing is asked.
  • Nothing is left half done. If another program still keeps the ports, or streaming cannot start, the paused web server is started again at once.
  • Uninstall offers to start a paused web server again, and keeps ports 80 and 443 open in the firewall while a website uses them.
  • cryptbridge opens the menu, as the texts always said (it started the setup). To run the setup again, use sudo cryptbridge setup or menu item 6.
  • The setup no longer accepts a number as the desktop user.

Updating

  • Server: download setup.sh again and run it. To keep everything as it is, press Enter at Add a vault, or renew one with a new transfer block? and at Keep the streaming account?:
curl -fsSLO https://raw.githubusercontent.com/burnersen/CryptBridge/main/linux/setup.sh && sudo bash setup.sh
  • Windows: nothing changes in the program itself (only its version number). Updating is optional.

Downloads

  • CryptBridge.exe: Windows 11 (64-bit), needs WinFsp
  • setup.sh: Linux server (Ubuntu / Debian)
Loading

CryptBridge 0.9.0

CryptBridge 0.9.0

Choose a tag to compare

View all tags
@burnersen burnersen released this 17 Oct 07:14
v0.9.0
6533f2d

Several vaults on one Linux server, each in a folder of its own.

Linux server

  • As many vaults as you like, in different clouds. Every vault is a folder in ~/CryptBridge, and your video player sees each one as a folder of the same share (same address, user and password as before). Each vault runs on its own: one can be switched off, or fail, while the others keep working.
  • Add a vault with sudo cryptbridge vault add, or Vaults > Add a vault in the cryptbridge menu, and paste its transfer block. The setup suggests the vault's name from the Windows program as the folder name. A block of a vault that is on the server already renews it (for example after signing in again) instead of adding it twice.
  • Switch a vault off and on. Switched off, it is unmounted and its folder disappears, for the video players too. It stays off, also after a restart of the server, until you switch it on again. Files waiting for their upload stay on the server and go up once it is on again.
  • Delete a vault from the server. Only the server's copy goes: its keys, its cache and its folder. Your files in the cloud are not touched. If files still wait for their upload, CryptBridge says how many and asks first.
  • The menu has a new item 3: Vaults: add, switch on/off, delete. The other items moved down by one. cryptbridge vault lists the vaults with their check codes; sudo cryptbridge vault on NAME, off NAME and delete NAME work without the menu.

Windows

  • The transfer block now carries the vault's name, so that the server can suggest it.
  • The guide for your own pCloud app names the new server command.

Updating

  • Server: download setup.sh again and run it:
curl -fsSLO https://raw.githubusercontent.com/burnersen/CryptBridge/main/linux/setup.sh && sudo bash setup.sh

Your vault moves into a folder of its own in ~/CryptBridge (you choose its name), and files waiting for their upload move along. In your video player the films are then one folder deeper: open the share again (Infuse may need to update its library).

  • Windows: recommended, so that new transfer blocks carry the vault's name. Older blocks still work; the server then suggests the name of the vault's folder in the cloud.

Downloads

  • CryptBridge.exe: Windows 11 (64-bit), needs WinFsp
  • setup.sh: Linux server (Ubuntu / Debian)
Loading

CryptBridge 0.8.3

CryptBridge 0.8.3

Choose a tag to compare

View all tags
@burnersen burnersen released this 17 Oct 05:56
v0.8.3
14b69ab

Streaming on the Linux server can now be switched off and on again, for example to free ports 80 and 443 for a test website.

Linux server

  • Switch streaming off and on. The cryptbridge menu has a new item 2: Switch streaming off (frees ports 80 and 443, e.g. for a website). The same works as a command: sudo cryptbridge streaming off and sudo cryptbridge streaming on.
    • Off: Caddy (the HTTPS part for your video player) stops, so another web server such as nginx or Apache can use ports 80 and 443. The vault folder on the server keeps working; only video players cannot connect.
    • Stays off until you switch it on again: also after a restart of the server, after Restart CryptBridge and after running the setup again.
    • On: if another program still uses port 80 or 443, CryptBridge names it, shows the command to stop it and leaves streaming off. Stop your website first, then switch streaming on.
  • The status shows "switched off" instead of a warning while streaming is off.
  • The other menu items moved down by one: Restart CryptBridge is now 3, Uninstall is 6.

Updating

  • Server: download setup.sh again and run it. Answer y to Keep the cloud sign-in and vault keys from the last setup?:
curl -fsSLO https://raw.githubusercontent.com/burnersen/CryptBridge/main/linux/setup.sh && sudo bash setup.sh
  • Windows: nothing changes in the program itself (only its version number). Updating is optional.

Downloads

  • CryptBridge.exe: Windows 11 (64-bit), needs WinFsp
  • setup.sh: Linux server (Ubuntu / Debian)
Loading

CryptBridge 0.8.2

CryptBridge 0.8.2

Choose a tag to compare

View all tags
@burnersen burnersen released this 16 Oct 21:51
v0.8.2
25feecb

The Linux server setup no longer stops halfway when another web server is in the way, and it explains IP addresses right away.

Linux server setup

  • Another web server on port 80 or 443 is found first. A website running on the server (for example with nginx or Apache) used to stop the setup at the very end of the HTTPS step. The cryptbridge command and the desktop icons were then missing. Now the setup checks these ports right at the start, names the program and asks whether to stop it (default: no).
    • Stop it: the setup goes on with HTTPS as usual.
    • Keep it: everything else is set up (vault folder, cryptbridge command, desktop icons) and only HTTPS is skipped. Once the ports are free, run sudo cryptbridge setup.
  • IP addresses are explained. An IP address such as 157.173.96.238 gets no trusted certificate, so video players refuse the connection. The setup now says so at once and asks for a name again, for example a free one from DuckDNS. If you keep the IP anyway, the setup no longer waits 3 minutes for a certificate that never comes.
  • The HTTPS check says how long it may take ("up to 3 minutes"), so it does not look like a hang.

Updating

  • Server: download setup.sh again and run it. Answer y to Keep the cloud sign-in and vault keys from the last setup?:
curl -fsSLO https://raw.githubusercontent.com/burnersen/CryptBridge/main/linux/setup.sh && sudo bash setup.sh
  • Windows: nothing changes in the program itself (only its version number). Updating is optional.

Downloads

  • CryptBridge.exe: Windows 11 (64-bit), needs WinFsp
  • setup.sh: Linux server (Ubuntu / Debian)
Loading

CryptBridge 0.8.1

CryptBridge 0.8.1

Choose a tag to compare

View all tags
@burnersen burnersen released this 16 Oct 20:38
v0.8.1
bf34c48

Bringing a vault to your Linux server is now more forgiving.

Easier transfer to the Linux server

  • A typo in the code is no longer a restart. If the code is wrong, the setup asks for it again, up to three times. The pasted block stays.
  • Copied codes just work. Copying can bring invisible characters along, and you cannot see them because the code is typed hidden. The setup now ignores everything that cannot be part of a code, as well as spaces, dashes and lower case.
  • Copy code button. It sits next to the code on the page of the vault, so you do not have to select the code with the mouse.
  • The setup command is in the window. The Linux server card shows the command to run on the server, with a Copy button.
  • Block and code stay together. Once a block is shown, the button reads Create a new block. A new block always gets a new code, so use the block and the code that are shown together.

Updating

  • Windows: replace CryptBridge.exe. Your settings and vaults stay as they are.
  • Server: nothing to do for a server that is running. The next time you paste a transfer block, download setup.sh again first:
curl -fsSLO https://raw.githubusercontent.com/burnersen/CryptBridge/main/linux/setup.sh && sudo bash setup.sh

Downloads

  • CryptBridge.exe: Windows 11 (64-bit), needs WinFsp
  • setup.sh: Linux server (Ubuntu / Debian)
Loading