diff options
| author | Christophe Besson <cbesson@gmail.com> | 2026-10-15 12:32:24 +0200 |
|---|---|---|
| committer | Christophe Besson <cbesson@gmail.com> | 2026-10-15 12:32:24 +0200 |
| commit | e0a1036e0fee15b3c6c83f3e935d50f472a2e776 (patch) | |
| tree | 75d28932b3010ebe3781b4f36dffed19dae74297 /packaging/deb/meshbay-client | |
| parent | a0be6bfcac07a256949082e935e1be06753ab872 (diff) | |
| download | meshbay-e0a1036e0fee15b3c6c83f3e935d50f472a2e776.tar.gz | |
fix(node): an operator who was a member first holds the authority at once
A member pinned on the node who then redeems the operator pairing code was
written down as the operator but the node kept its "nobody can authorize"
flag until it restarted: every admin operation — removing a folder, inviting,
the apps' settings — was refused meanwhile. Only a key paired fresh set it.
The join result now names `operator` for an account holding the node-wide
operator row, whatever its row in the group says. The page and the CLI read
that role to know what to offer, and refused before asking deletions the node
would have accepted. Nothing is granted by it: every admin operation is still
checked against the operators' keys.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Diffstat (limited to 'packaging/deb/meshbay-client')
0 files changed, 0 insertions, 0 deletions