Skip to content

RestoreSafe 2.1.0

Choose a tag to compare

@phsc84 phsc84 released this 18 Oct 16:49
· 12 commits to main since this release
735395c

RestoreSafe 2.1 makes the YubiKey easier to check and harder to lose: a page that tells you whether your YubiKey is ready and opens your backups, and a recovery code with every YubiKey.

Highlights

  • YubiKey page. At the bottom of the sidebar while you use a YubiKey: whether Windows and your YubiKey are ready (FIDO2, firmware), Test YubiKey… to check that it opens your backups, help with the PIN, a reset and FIDO2, and technical details to copy into a bug report. It updates as soon as you plug a YubiKey in or pull it out.
  • No lockout with a YubiKey. New keys with a YubiKey always come with a recovery code, so a lost or broken YubiKey doesn't lose your backups. A new recovery code stays on screen until you tick I have stored my recovery code. If your YubiKey no longer unlocks your keys, for example after a reset, the backup offers new keys and a full backup instead of failing.
  • One YubiKey for a backup. A backup doesn't start while two YubiKeys are connected, so it's always clear which one holds your keys.
  • An out-of-date config.yaml no longer stops RestoreSafe. At start, a dialog names settings RestoreSafe no longer uses and settings that are missing, and Update config.yaml fixes both, keeping a copy of the previous file.

Also: failed backups, restores and verifications are logged as errors with their reason, and three bugs are fixed, among them a backup that stopped when a folder was deleted while it ran.

Under the hood, 2.1.0 went through a full review of the code: more tests, a stricter CI, and simpler code in many places. The review found two of the bugs listed under Fixed in the CHANGELOG.

Before you update from 2.0

  • Spare YubiKey: 2.1 has none. If you registered a spare YubiKey with 2.0, start again with new backups: 2.1 can't open the backups made with those keys and lists them as damaged on Restore backup, and your first 2.1 backup creates new keys and a full backup of every folder by itself. RestoreSafe 2.0.0 can still restore the old backups, so keep it as long as you keep them. Remove yubikey_spare from config.yaml, or let the dialog at start do it.
  • Recovery code: keys you created with a YubiKey in 2.0 stay as they are. If they have no recovery code, click New keys + full backup… at your next backup to get one.
  • Backups made with 2.0 without a spare YubiKey open in 2.1 as before; the backup format is unchanged.

Download

  1. Download RestoreSafe-2.1.0.zip below.
  2. Extract it to any folder. When you update, replace RestoreSafe.exe and keep your config.yaml.

RestoreSafe is not signed with a paid code-signing certificate, so on first start Windows may show "Windows protected your PC" (SmartScreen, "unknown publisher"). Click More info, then Run anyway. Windows asks only on the first start of a downloaded version.

On Windows 11 with Smart App Control turned on, Windows may block RestoreSafe without offering Run anyway. Smart App Control allows only programs that are signed or known to Microsoft. To run RestoreSafe, turn it off in Windows Security → App & browser control → Smart App Control settings. On older Windows 11 versions it can only be turned on again by reinstalling Windows.

Optional, for checking that the download is unchanged: download SHA256SUMS.txt into the same folder as the ZIP and run this in PowerShell there. It prints True:

(Get-FileHash .\RestoreSafe-2.1.0.zip).Hash -eq (Get-Content .\SHA256SUMS.txt).Split(' ')[0]

Requires Windows 64-bit; for a YubiKey, Windows 11 version 22H2 or later. Built with Go 1.27.2.

The full list of changes is in the CHANGELOG.