Skip to content

📝 Document how to stop clients spoofing op src - #754

Draft
alecgibson wants to merge 1 commit into
mainfrom
worktree-glittery-dazzling-kahan
Draft

alecgibson wants to merge 1 commit into
mainfrom
worktree-glittery-dazzling-kahan

Conversation

@alecgibson

Copy link
Copy Markdown
Collaborator

Fixes #733

At the moment, a client can submit an op with another client's src and next seq, and the server will then drop that client's real op as a duplicate, while still acking it.

We can't enforce ownership of src in the library without a protocol change, since the handshake id is also chosen by the client. Instead, this change documents that src is client-chosen, and adds a middleware recipe that scopes it to the authenticated user.

🤖 Generated with Claude Code

Co-Authored-By: Claude [email protected]

Fixes #733

At the moment, a client can submit an op with another client's `src`
and next `seq`, and the server will then drop that client's real op as
a duplicate, while still acking it.

We can't enforce ownership of `src` in the library without a protocol
change, since the handshake `id` is also chosen by the client. Instead,
this change documents that `src` is client-chosen, and adds a
middleware recipe that scopes it to the authenticated user.

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude <[email protected]>
@coveralls

Copy link
Copy Markdown

Coverage Status

coverage: 97.851%. remained the same — worktree-glittery-dazzling-kahan into main

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

A client can spoof another client's op src/seq to silently drop its edits

2 participants