RemoteFlow 0.6.0

RemoteFlow 0.6.0 adds automatic backup, and finally opens the credential vault it needed to keep a passphrase in.

Automatic backup

Backup has been manual since it existed, which means the archive you have is the one you last remembered to make — usually the one from before the change you now want to undo.

Turn it on under Backup → Automatic. Every change to a connection, folder or tag writes a fresh archive about thirty seconds after you stop editing, so a rename, a retag and a move produce one backup rather than three.

• The destination is a place you already configured. A folder on this computer, or an SFTP connection or storage account from your own connection list — not a second place to set up a server.
• Archives include your saved credentials, encrypted with a passphrase you set once and which is kept in your system credential store, never in RemoteFlow's database. Without it a restored backup gives you back a list of hostnames and nothing you can sign in with. If no passphrase is set, RemoteFlow writes nothing and says so rather than quietly making an archive you cannot restore from.
• You choose how many to keep. Older ones are removed after each successful run, and files RemoteFlow did not write are never touched — a manual export sitting in the same folder is safe.
• Failures wait for you on the Backup page rather than interrupting what you are doing. It reports when the last run happened, where it went, and what went wrong, and retries at the next change and the next launch.

The credential vault now opens

On a computer with no system keyring RemoteFlow can use — most often Linux without libsecret — saved passwords and keys live in an encrypted file of its own. Nothing ever opened that file, so on those machines credentials silently could not be saved or read at all.

If that describes your machine, RemoteFlow now asks for a vault passphrase when it starts: once to choose one the first time, with a confirmation box and a warning that nothing else holds a copy, and once to recall it on later launches. A wrong passphrase can be retyped. Declining leaves RemoteFlow running without saved secrets rather than failing to start, and the Backup page offers a way back in without restarting.

Machines with a working keyring — Windows, macOS, and Linux with libsecret — are untouched and see no prompt.

Downloads

Four Windows artefacts, named for the version and the runtime identifier (win-x64 or win-arm64):

File	What it is
RemoteFlow-0.6.0-win-x64.zip	Portable build for Intel and AMD machines.
RemoteFlow-0.6.0-win-arm64.zip	Portable build for ARM machines.
RemoteFlow-0.6.0-win-x64-setup.exe	Per-user installer for x64.
RemoteFlow-0.6.0-win-arm64-setup.exe	Per-user installer for ARM64.

The zips are self-contained: they run on a clean Windows with no .NET runtime installed. The installers are per-user, need no elevation, and leave your connections and settings in place when you uninstall unless you ask for them to be removed.

Four Linux artefacts, in two shapes. The Debian packages use Debian's own naming because apt and dpkg expect it:

File	What it is
remoteflow_0.6.0_amd64.deb	Debian/Ubuntu package for Intel and AMD machines.
remoteflow_0.6.0_arm64.deb	The same for ARM machines.
RemoteFlow-0.6.0-linux-x64.tar.gz	Portable build for Intel and AMD machines.
RemoteFlow-0.6.0-linux-arm64.tar.gz	The same for ARM machines.

Install the package with sudo apt install ./remoteflow_0.6.0_amd64.deb.

Verifying your download

checksums.txt lists the SHA-256 of every file above.

sha256sum --check --ignore-missing checksums.txt

On Windows without sha256sum:

Get-FileHash .\RemoteFlow-0.6.0-win-x64.zip -Algorithm SHA256

These builds are not code-signed, so Windows SmartScreen will warn that the publisher is unknown. That is expected and is not a sign of a corrupted download; the checksum is how you tell the difference.

---

Full changelog: v0.5.0...v0.6.0