11 Commits

Include renames

Author	SHA1	Message	Date
jschoubben	e2136ec0c9	The vault takes a handing whole once, refusals and all, and names the refused users in its last adoption (review of the adoption, ADR 0547 clause 9)	2026-10-26 12:03:14 +01:00
jschoubben	f0fd53281b	The vault says once why a look of the bus module's have adopted nothing, and again when it changes (ADR 0547 clause 9)	2026-10-26 11:37:14 +01:00
jschoubben	fb039250f6	The vault adopts the hashes of the bus accounts it holds no value for from the bus node's handing (ADR 0547 clause 9, issue 1945) ... take-over waits on a hash for every user of the loaded list, and the vault holds no value for the controller's own account, the node accounts and the enrolled devices. The bus node's engine now hands every loaded user's hash in the bus module's have, sealed to the vault's key (mesh-host and mesh-sdk on the same branch). The vault answers its key in node-key, reads the haves (manifest reads node-engine.have, granted from the manifest, no controller change), watches the bus module's have, opens the handing with its own key, and writes each user it holds no value for into bus-accounts marked adopted, with the list and node it came from, saying account-hashed. It never touches a user whose covered account it holds or whose key is its own hash, writes an adopted key again only for another hash, and refuses a handing from any node the assignments do not name as holding the bus module. Tools: account_adopt adopts now from the have as the watch does; secret_own, unnarrowed by module, lists the adopted accounts and the last adoption.	2026-10-26 11:36:33 +01:00
jschoubben	e7aaa8420e	Vault: name a hash record's secret in a field called of, so the runtime accepts it ... The runtime refuses a state field whose name ends in secret, so no bus-account hash could be written on novox. The test state now applies the same check. Issue: 1945	2026-10-26 09:25:35 +01:00
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
jschoubben	60a3823f0e	mesh-vault reads an ended assignment as a removed key (issue 1098)	2026-10-18 02:37:28 +02:00
fix-vault-pas@novox	5a00596908	Make the vault ask a software-issuing provider's tool itself for holders that hold nothing (issue 928)	2026-10-16 19:34:11 +02:00
fix-vault-pas@novox	0dab4475cd	Answer an unreadable assignment as not yet, never a refusal (issue 928)	2026-10-16 19:30:15 +02:00
mesh-tools	0260ae92f6	Feature 57 (config and provisioning): release the catalogue, the reviewed release branch merged with main, on top of main	2026-10-16 09:42:45 +00:00