Vault Manager v0.7.4

Vault Manager v0.7.4

"Become the owner" now appears when you actually need it. If a node already has an owner and this
computer is not one of them, the box for redeeming an owner code was hidden — which is precisely the
situation it exists for.

What was wrong

Vault Manager decided whether to show that box by asking does this node have an owner? — when the
question it meant was does this computer hold owner on it? Those are different, and the difference
hid the control on every node that already had an owner.

That made the app's own instructions impossible to follow. When you create an owner code for a second
computer, Vault Manager tells you: "On the other device, open 'Become the owner' and paste this code
there." That other computer would ask the node, be told it already has an owner, and hide the very
panel it had just been sent to.

So there was no way through the app to:

• add a second computer as an owner of your node, or
• get back in on a computer whose credentials were lost, using an owner code.

The fix

The panel now appears whenever the node is claimed and this computer is not already an owner of
it — including on a computer that holds no record of the node at all, which is the case that surfaced
this.

The wording changed with it. Telling someone their node "has no owner yet" when it plainly has one
reads as a fault and teaches people to distrust the screen. When the node does have an owner, it now
says so and names the two real ways forward: an owner code created on a computer that is an owner,
or your recovery key.

If you have lost every owner device

That case does not need an owner code and never did — use "Lost access to a node you own?" under
Identity & ownership with your recovery key. It has always been there, but it sits inside a
collapsed section, which is easy to walk past.

Verification

220 unit tests, the call-site, page-structure and TLS guards, and three walkthroughs driven
against the built application — a first-run walk, a full run through a damaged profile, and a new one
for this fix, driven against a real node that genuinely reports having an owner, because a stand-in
would have agreed with the old behaviour.

The guard for this fix was checked by deliberately reintroducing the fault five ways — including
putting the wrong question back one line further up, where the first version of the test could not
see it. All five were caught.

Also added: the release process now refuses to publish a version number that already exists with
different contents, so one version can never mean two different programs.

Downloads

Published under both VaultManager-* and VaultFlasher-* names; the bytes are identical.

NSIS setup.exe  sha256  fe14ee25d1363f663f75a3604bdaa8ab63b61002111e3280e2b72fddba42f5bf
MSI             sha256  86f907416df5b02bf7cfcc556c8f55b152f67d331b881450751d27a42c268adf

⚠ Compare hashes, not sizes.