Vault: read own secrets' generations, and hash each bus account it is handed for the grants part (issue 1945, ADR 0547 clause 9) #486

Merged

mesh-tools merged 3 commits from fix/1945-vault-own-read into main 2026-10-26 07:48:04 +00:00

Conversation 2 Commits 3 Files Changed 9

+713 -15

3 Commits

Author	SHA1	Message	Date
jschoubben	1c55e5d44d	Vault: take and hash a process's own bus account (broker-<process id>) as a covered account, so take-over is not held by every process user ... The controller hands each process account of a core or moved module with origin issued (ADR 0436 §2); the vault took only broker and provisioner-broker, refused these and never hashed them. Owed hashes are now said once per pass, and account_hash says who asked when it refuses too (review round 1). Issue: 1945	2026-10-26 02:35:57 +01:00
jschoubben	32b912cfe5	Vault: hash each bus account it is handed into bus-accounts.<user>, once per generation, so the grants part can compose the user list without the controller ... The controller still mints each covered account and hands it to the vault (ADR 0374); ADR 0547 clause 9 has the vault write the bcrypt hash of what it holds into its own state, readable by the grants part, and say account-hashed. It hashes on keep, at start every held account with no key of its generation, and again by hand (account_hash); a refused write is owed and written at the next pass. secret_own says per bus account whether this generation's hash is written. Issue: 1945	2026-10-26 02:28:28 +01:00
jschoubben	e572937d97	Vault: secret_own reads the module-own secrets it keeps, as fingerprints, so a generation can be told without the value ... Issue: 1945	2026-10-26 02:09:03 +01:00