aboutsummaryrefslogtreecommitdiffstats
path: root/packages/meshbay-common/src/meshbay_common/adminop.py
diff options
context:
space:
mode:
Diffstat (limited to 'packages/meshbay-common/src/meshbay_common/adminop.py')
-rw-r--r--packages/meshbay-common/src/meshbay_common/adminop.py8
1 files changed, 8 insertions, 0 deletions
diff --git a/packages/meshbay-common/src/meshbay_common/adminop.py b/packages/meshbay-common/src/meshbay_common/adminop.py
index fe4be83..4e28f65 100644
--- a/packages/meshbay-common/src/meshbay_common/adminop.py
+++ b/packages/meshbay-common/src/meshbay_common/adminop.py
@@ -37,6 +37,14 @@ OP_FILE_DELETE = "file_delete"
OP_DIR_DELETE = "dir_delete"
OP_INVITE_CREATE = "invite_create"
OP_MEMBER_REVOKE = "member_revoke"
+# Rotating the group key is what actually takes it away from a revoked member:
+# revocation stops the node serving the *next* key, and they still hold the
+# current one. The node generates the new key itself with its own CSPRNG, so
+# nothing arriving over MNP contributes key material — the C5b rule is about
+# key material from outside, not about the instruction.
+OP_GEK_ROTATE = "gek_rotate"
+# Forgetting a pinned identity, so someone can pair again after losing a device.
+OP_MEMBER_UNPIN = "member_unpin"
# OP_GEK_BUNDLE_STORE is gone. Members no longer hand the node key material at
# all: the node holds the GEK and wraps it itself, for a key the recipient proved
# they hold (see `join.py` and docs/invite-pairing-v1.md). The operation existed