Skip to content

Server-side crypto invariants #562

Closed

Description

@codebestia

Write apps/backend/docs/concepts-crypto-invariants.md covering lib/ciphertextInvariant.ts and lib/signalInvariants.ts — the guards that keep the server from ever accepting or storing material it must not hold, and the security-ci job that regression-tests them.

Acceptance criteria:

  • States the invariants plainly: the server stores ciphertext only, and never accepts session state, ratchet state, or private keys on any inbound payload
  • Documents findForbiddenSessionStateField and the rejected field names, and that rejection happens before any database lookup
  • Explains why the relevant Zod schemas are .strict() — a non-strict schema silently strips a forbidden field instead of rejecting the request
  • Documents the security-ci regression job that keeps these enforced

Activity

  1. attyolu commented on Aug 29, 2026

    @attyolu

    @attyolu has applied to work on this issue as part of the Stellar Wave Program's 8th wave.

    Hello please assign this issue to me I will definitely do a great job solving

    ℹ️ Repo Maintainers: To accept this application, review their application or assign @attyolu to this issue.

  2. BigManly4 commented on Aug 30, 2026

    @BigManly4

    @BigManly4 has applied to work on this issue as part of the Stellar Wave Program's 8th wave.

    I'd like to contribute to this issue. As a full-stack and backend developer with open-source experience, I'll provide a high-quality implementation and keep the discussion updated throughout the process.

    ℹ️ Repo Maintainers: To accept this application, review their application or assign @BigManly4 to this issue.

  3. drips-wave commented on Aug 30, 2026

    @drips-wave

    Congratulations, @BigManly4! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on August 31, 2026.

    🧑‍💻 @BigManly4: Please resolve the issue such that the repo's maintainers have enough time to review your contribution before the due date. You'll earn Points for completing the issue on-time, which will make you eligible for a share of the Stellar Wave Program's reward pool.

    Warning

    When opening a PR, please link it to this issue to ensure it gets tracked accurately. Points are awarded when this issue is marked as completed by the maintainer.

    🤠 Repo maintainers: Please keep an eye on the contributor's progress and review their work before the due date. You can manage this issue, including adjusting its complexity and points, here.

    🌊 Happy Wave 🌊

  4. github-actions commented on Aug 31, 2026

    @github-actions

    Closed by #599, merged into dev.

  5. drips-wave commented on Aug 31, 2026

    @drips-wave

    This issue has been completed by @BigManly4 as part of the Stellar Wave Program's 8th Wave 🥳

    😎 @BigManly4: You earned 200 Points for completing this issue! After the current Wave ends, you'll be eligible for a percentage of the Wave's reward pool based on the percentage of total points you've earned. Learn more here. You can also Leave a review to share your experience working on this issue.

    🧑‍💻 Repo maintainers: How'd the contributor do? Leave a review to share your experience working with them.

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

Metadata

Metadata

Assignees

Labels

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions