diff options
Diffstat (limited to 'packages/meshbay-node/tests')
| -rw-r--r-- | packages/meshbay-node/tests/test_link_invites.py | 2 | ||||
| -rw-r--r-- | packages/meshbay-node/tests/test_webrtc_transport.py | 2 |
2 files changed, 2 insertions, 2 deletions
diff --git a/packages/meshbay-node/tests/test_link_invites.py b/packages/meshbay-node/tests/test_link_invites.py index f5081d2..10f9ca8 100644 --- a/packages/meshbay-node/tests/test_link_invites.py +++ b/packages/meshbay-node/tests/test_link_invites.py @@ -4,7 +4,7 @@ Invitation links: a code bound to no account until somebody redeems it. A link is sent to someone who may not have an account yet, so its code cannot name one. That makes it a bearer code at the node — the hub's ticket, bound to a verified address, is what decides who can reach the node at all -(docs/invite-links.md §3). Everything here is a way a bearer code could be made +(docs/MESHBAY_DESIGN.md §3.4). Everything here is a way a bearer code could be made to mean more than "one new member of this group, once", or a way an unbound row could leak into the code paths written for bound ones. The second family is the one to watch: `user_id = ''` must never read as "anyone" (AV1). diff --git a/packages/meshbay-node/tests/test_webrtc_transport.py b/packages/meshbay-node/tests/test_webrtc_transport.py index c0dc6d1..0245c4e 100644 --- a/packages/meshbay-node/tests/test_webrtc_transport.py +++ b/packages/meshbay-node/tests/test_webrtc_transport.py @@ -1449,7 +1449,7 @@ async def _bearer_join(transport, sk_hub, user_id, peer_id, code, x25519_keypair async def test_a_link_is_issued_signed_redeemed_once_and_cancellable( sk_node, sk_hub, gek, shared_dir, tmp_path, x25519_keypair): """ - Invitation links over a real DataChannel (docs/invite-links.md §3.4). + Invitation links over a real DataChannel (docs/MESHBAY_NODE_PROTOCOL.md §8.6). The operator signs `invite_link_create` naming the outcome, `link:<group>`; the first account to bring the code is admitted and handed the key; the |