github junkerderprovinz/bombvault v10.6.5

one hour ago

A login password is optional everywhere in BombVault, and a node that keeps its own backups says what blocks it when Apply cannot reach it.

✨ Added

  • A waiting release's notes in the app. Once Check for updates finds a newer release, What's new opens its notes in a window, with GitHub one click away in the foot. BombVault fetches the notes of that one release only, so the update check keeps its share of GitHub's rate limit.
  • Version and Components cards in the Android app. The app's settings show BombVault's number with What's new and say where updates come from: Google Play, F-Droid, or the release page for an APK installed by hand. GlimStone's number stands in the Components card.

🎨 Design

  • Follows GlimStone 4.8.5. The Version card says "Not checked yet" until you press Check for updates, so "Up to date" always has a check behind it. On a narrow card a Components row moves its status and number under the name together, and nothing gets cut off.

⚡ Improved

  • A login password is optional for everything. Without one, the recovery kit, the bug report, the flash ZIP, exports with credentials, app backups, nodes and key deposits work like the rest of the interface. With a password nothing changes: these still need a sign-in at this instance, and a paired phone's session is not enough. Two-factor authentication, passkeys and OAuth sign-in for MCP clients still ask for a password first, since each is an extra way in.
  • Fortress apps open without a password. The browser gets a visitor cookie of its own for the tabs it opens, so another member's pages open from Instances right away. Setting a password later closes those tabs, and a BombVault without a password opens from the other apps of the fortress too.
  • Any password length. The 12-character minimum is gone from the Security page and from the reset on the login page. A shorter password gets a friendly hint that a longer one is much harder to guess, and it saves all the same.
  • MCP keys and API tokens under any address. Keys, tokens and certificate names can be made under any host name, a public one behind a reverse proxy included. Without a password the card still says that anyone who can open the page can make one.

🐛 Fixed

  • Keeping backups on the node no longer spins forever. Apply on a port the provider's firewall blocks kept going for most of an hour with nothing in the log. Home now checks the node's rest-server within 30 seconds using the node's certificate, gives each repository two minutes, and says which port to open or that a different server answers there. Thanks to @LukasStipar for the report.
  • A slow rest-server download no longer times out. The node downloads the rest-server image in the background, and home asks again for up to two minutes. If the download is still running by then, BombVault says so and asks you to try again in a few minutes.
  • Opening an older app from the fortress. When an app in the fortress still wants a login before it opens, the message asks for an update of that app instead of a password.

🌐 Translations

  • Every new sentence in all 42 languages. That covers the password hint, the node's rest-server messages and the Version card's new states, and the docs follow in all 26.

Don't miss a new bombvault release

NewReleases is sending notifications on new releases.