Skip to content

docs: name two disruption limits in the security design - #60

Merged
Privex-chat merged 2 commits into
mainfrom
docs/disruption-limits
Sep 27, 2026
Merged

Privex-chat merged 2 commits into
mainfrom
docs/disruption-limits

Conversation

@Privex-chat

Copy link
Copy Markdown
Owner

Documents two limits the owner decided to accept and document, not build around. Docs only; no code change.

§7, What Privex does not protect against: disruption by whoever holds a session token or sits in the path. That covers:

  • a valid session token (up to 24 h);
  • the TLS-terminating proxy;
  • a compromised server.

Any of these can:

  • Make new contacts' first messages fail. They can upload or replace the account's one-time prekeys, which are unsigned by design, as in Signal/X3DH. A first message that uses one fails to decrypt, and the recipient sees "couldn't be decrypted".
  • Empty the message queue by confirming its messages.

They can't read anything; that needs the signed prekey and identity private keys. The same parties could simply drop traffic anyway. Signing one-time prekeys would stop only a token-only attacker, for whom there's no realistic path (see #57), so it isn't built.

§8, Known limitations: one mailbox per account. Live messages go to the newest open connection (#58). With two active devices, the one that can't decrypt a message (its chat session lives on the other device) confirms it, and the other never gets it. Per-device mailboxes would reveal your device count to the server, so they aren't built.

🤖 Generated with Claude Code

- What Privex doesn't protect against: whoever holds a session token, the
  TLS-terminating proxy, or a compromised server can make new contacts' first
  messages fail (one-time prekeys are unsigned by design, as in Signal) or empty
  the message queue - never read anything.
- Known limitations: one mailbox per account - with two active devices, the one
  that can't decrypt a message confirms it and the other never gets it;
  per-device mailboxes would reveal your device count, so they aren't built.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@Privex-chat

Copy link
Copy Markdown
Owner Author

@coderabbitai review

@coderabbitai

coderabbitai Bot commented Sep 27, 2026 •

Copy link
Copy Markdown
Contributor

Warning

Review limit reached

Next included review available in 41 minutes.

Check out review usage here.

View limit details

Limit details: You’ve used the included review currently available.

You've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository.

Learn how review limits work.

Review configuration:

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Advanced

Run ID: 62f297ec-4d26-4296-abe1-50cd3d9b47c3

📥 Commits

Reviewing files that changed from the base of the PR and between af6ba58 and b3b3347.

📒 Files selected for processing (1)
  • docs/SECURITY_DESIGN.md

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands.

@coderabbitai

coderabbitai Bot commented Sep 27, 2026 •

Copy link
Copy Markdown
Contributor
⚠️ Action not completed

Review rate limited.

Note: CodeRabbit is an incremental review system and does not re-review already reviewed commits. This command is applicable only when automatic reviews are paused.

- A token holder isn't in the path, so only the proxy or server can drop traffic.
- Signal signs its one-time post-quantum prekeys; the comparison is to its
  one-time curve prekeys, which Privex's are.
- Any new chat session draws a one-time prekey, not just a new contact's.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@Privex-chat
Privex-chat merged commit 938431a into main Sep 27, 2026
3 of 4 checks passed
@Privex-chat
Privex-chat deleted the docs/disruption-limits branch September 27, 2026 13:46
@Privex-chat

Copy link
Copy Markdown
Owner Author

@coderabbitai review

@coderabbitai

coderabbitai Bot commented Sep 27, 2026 •

Copy link
Copy Markdown
Contributor
⚠️ Action not completed

Pull request is closed.

Note: CodeRabbit is an incremental review system and does not re-review already reviewed commits. This command is applicable only when automatic reviews are paused.

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.

1 participant