github junkerderprovinz/bombvault v9.2.0

latest releases: v10.6.0, v10.5.5, v10.5.3...
one month ago

BombVault instances pair by twelve words. Enter the same phrase on each of your instances and they form a group that finds itself on the local network and reaches across networks through an end-to-end encrypted relay. The fleet token and typing another instance's APP_KEY are gone, so read Upgrading before you update. The interface follows GlimStone 3.0.2, and the Anomalies page has one card per item.

✨ Added

Pairing by phrase

  • Twelve words pair your instances. Press Create phrase under Instances, Pairing on the first instance and Enter phrase on every other one. The words come from the BIP39 list, so a mistyped or swapped word is caught at once, and the page names the word and its position.
  • Three numbered cards explain how it works before any button does anything: read the words here, type them there, done.
  • On the same network, members talk directly. On different networks they meet at a relay you pick on the same tab. The project relay needs no setup and is the one KnightLoader uses too. Your own relay is the BombVault Relay container, or one of your instances with Serve as relay switched on. No relay keeps the group to one network.
  • Everything between members is end-to-end encrypted with a key worked out from the words, which never leaves an instance. A relay sees which instance a message is for, how big it is and when it comes, and nothing else. A relay reached over plain ws:// or http:// is allowed for a local setup, with a warning that its key then travels unencrypted.
  • The group carries the Fleet scorecard, Mesh off-site offers and what a receiver or pull source needs. Backups never go over the relay. A receiver or pull source gets the other instance's restic password and repository location, never its APP_KEY, so it can read that instance's backups and nothing else.
  • Pairing needs a login password. The twelve words open the backups of every instance in the group, so creating, entering and showing them is only possible after signing in, as with the recovery kit. Showing the words again always asks for the password.

Interface

  • The Anomalies page shows one card per item with open findings, worst first. Each finding is one line that opens to its figures and actions, and a card has one main action: restore the last good backup for a critical finding, otherwise acknowledge. Three tiles at the top count critical findings, warnings and notes and hide a level on click. Closed findings sit behind one row at the end, with their notes. Monitoring on each card holds what the Items tab held.
  • Test buttons show their result on themselves. Test connection, Send test, Check and Check now turn green with Connected, Sent or Passed and a check, or red with Not connected, Not sent or Failed and a cross, and shake. The reason for a failure stands in one line above the buttons.
  • A Look tab in Settings holds language, theme, corners, motion, labels and colours, with the language first.
  • The About card gives and reports with the same buttons as the README, and the mail envelope opens under the pointer.
  • Dragging a row in a start-order list or a dashboard card lifts it under the pointer and lands it in its gap.

🎨 Changed

  • Every selector spans its card, and a selector in a toolbar keeps its own width. The dashboard's backup history strip is a full selector.
  • Pages start with their content. The large heading and the line under it are gone from every page; the sidebar already says where you are. Screen readers still get the page name.
  • Settings has the same maximum width as every other page.
  • On a phone, the tabs of Settings and Instances are separate badges.
  • The page behind a window is blurred and darkened, and a system set to reduce transparency keeps only the darkening.
  • Button glyphs match the size of their words, and a closed dropdown steps with the mouse wheel only while it has focus.
  • The activity log's "Jump to latest" button sits centred at the bottom of the log, clear of the scrollbar, with a downward arrow.

🗑️ Removed

  • The fleet token. Instances are no longer added by address and token; they join the group.
  • Typing another instance's APP_KEY for a receiver or a pull source. You pick the instance from the group instead. The APP_KEY is still asked for in one place: restoring from the repository of an instance that is gone, on the Recovery tab.

🐛 Fixed

  • A repository address with a password but no user name (https://:secret@host) is masked in logs and messages like any other.

🌐 Translations

  • The Pairing tab, the relay card, the Anomalies cards, the test results and the Look tab in all 42 languages.
  • Pairing by phrase in the documentation in all 26 documentation languages.

Upgrading

  • Pair your instances after the update. Fleet peers, receivers and pull sources you set up before keep their settings and keep working, marked Pair again. Set a login password on each instance if it has none, create a phrase on one of them and enter it on the others; each entry then takes over its group member.
  • Stored APP_KEYs of other instances are removed during the update. BombVault keeps only the restic password it needs from each and compacts the database so the old values are gone from the file.
  • Settings, schedules and repositories carry over as they are.

Don't miss a new bombvault release

NewReleases is sending notifications on new releases.