The comparison table scored Signal wrong, in our favour (relay#11) #117

Merged

paulhitt merged 1 commits from accuracy/signal-post-quantum-ratchet into main 2026-09-06 22:25:50 +00:00

Conversation 8 Commits 1 Files Changed 1

+8 -4

paulhitt commented 2026-09-05 00:28:18 +00:00 (Migrated from gitlab.com)

Copy Link

Copy Source

/comparison scored Signal No on "post-quantum in the ongoing
ratchet". Signal shipped exactly that: the Sparse Post-Quantum Ratchet,
announced 2025-10-02, combined with their Double Ratchet as the "Triple
Ratchet" — continuous post-quantum key agreement, not just PQXDH's initial
handshake.

Wrong in the direction that flatters us, on a page whose own closing
note calls that a bug and asks to be told. Verified from signal.org/blog/spqr
rather than from memory, because the whole problem with this row was
somebody being confident.

The knock-on sentence went with it. "Apple is ahead of everyone here on
post-quantum" was true only while Signal's cell said No; both carry it
through the ongoing conversation, and the paragraph now says we are not
ahead of anyone on that row and names the date this page was wrong.

Our own two cells were checked at the same time and are RIGHT — I
went in expecting to correct those too. Android's ML-KEM-768 is
BouncyCastle's FIPS 203 implementation, not a stub, and iOS's is CryptoKit
MLKEM768, unconditional since the deployment target moved to 26.0. The
cross-engine interop proves it end to end: "Android picks v3 for an iPhone
peer", "the first Android envelope carries a PQ ratchet step", "a v3
session survives being archived and restored mid-conversation".

659 tests pass.

Co-Authored-By: Claude Opus 5 noreply@anthropic.com

`/comparison` scored Signal **No** on "post-quantum in the ongoing ratchet". Signal shipped exactly that: the Sparse Post-Quantum Ratchet, announced 2025-10-02, combined with their Double Ratchet as the "Triple Ratchet" — continuous post-quantum key agreement, not just PQXDH's initial handshake. **Wrong in the direction that flatters us**, on a page whose own closing note calls that a bug and asks to be told. Verified from signal.org/blog/spqr rather than from memory, because the whole problem with this row was somebody being confident. The knock-on sentence went with it. "Apple is ahead of everyone here on post-quantum" was true only while Signal's cell said No; both carry it through the ongoing conversation, and the paragraph now says we are not ahead of anyone on that row and names the date this page was wrong. **Our own two cells were checked at the same time and are RIGHT** — I went in expecting to correct those too. Android's ML-KEM-768 is BouncyCastle's FIPS 203 implementation, not a stub, and iOS's is CryptoKit `MLKEM768`, unconditional since the deployment target moved to 26.0. The cross-engine interop proves it end to end: "Android picks v3 for an iPhone peer", "the first Android envelope carries a PQ ratchet step", "a v3 session survives being archived and restored mid-conversation". 659 tests pass. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>

paulhitt commented 2026-09-05 00:28:18 +00:00 (Migrated from gitlab.com)

Copy Link

Copy Source

assigned to @paulhitt

assigned to @paulhitt

paulhitt (Migrated from gitlab.com) scheduled this pull request to auto merge when all checks succeed 2026-09-05 00:28:27 +00:00

paulhitt commented 2026-09-05 00:29:30 +00:00 (Migrated from gitlab.com)

Copy Link

Copy Source

mentioned in issue #11

mentioned in issue #11

paulhitt commented 2026-09-06 21:36:29 +00:00 (Migrated from gitlab.com)

Copy Link

Copy Source

aborted the automatic merge because the source branch was updated. Learn more.

aborted the automatic merge because the source branch was updated. [Learn more](https://gitlab.com/help/ci/pipelines/merge_trains.md#merge-request-dropped-from-the-merge-train).

paulhitt commented 2026-09-06 21:36:30 +00:00 (Migrated from gitlab.com)

Copy Link

Copy Source

added 29 commits

• 42d79e38...e9a6b506 - 28 commits from branch main
• 773e8654 - The comparison table scored Signal wrong, in our favour (relay#11)

Compare with previous version

added 29 commits <ul><li>42d79e38...e9a6b506 - 28 commits from branch <code>main</code></li><li>773e8654 - The comparison table scored Signal wrong, in our favour (relay#11)</li></ul> [Compare with previous version](/paulhitt/flamenet-relay/-/merge_requests/54/diffs?diff_id=2007744115&start_sha=42d79e38bfac0b0a7d6a3eb0aba210cc02ec801f)

paulhitt commented 2026-09-06 22:25:50 +00:00 (Migrated from gitlab.com)

Copy Link

Copy Source

mentioned in commit 6e184347ca

mentioned in commit 6e184347ca3d0d4056673ca7a99a213255f9a506

paulhitt (Migrated from gitlab.com) merged commit 6e184347ca into main 2026-09-06 22:25:50 +00:00

paulhitt commented 2026-09-07 10:00:27 +00:00 (Migrated from gitlab.com)

Copy Link

Copy Source

mentioned in commit 1b915b0591

mentioned in commit 1b915b059165b716c43a1291099847edade61715

paulhitt commented 2026-09-07 10:00:28 +00:00 (Migrated from gitlab.com)

Copy Link

Copy Source

mentioned in merge request !73

mentioned in merge request !73

paulhitt commented 2026-09-09 18:58:57 +00:00 (Migrated from gitlab.com)

Copy Link

Copy Source

changed the description

changed the description

Sign in to join this conversation.

Reviewers

No Reviewers

Labels

Clear labels

accuracy

A public page claims something the code does not do

architecture

blocked:apple

Waiting on App Store review

bug

ci

deploy

docs

federation

hardening

idea

investigation

ops

Deploy, CI, infrastructure

parity

One platform has it and the other does not

planning

privacy

Changes what is stored, or what we say is stored

reliability

scalability

security

self-hosting

signup

stability

tech-debt

tooling

unwired

Built in the engine, not reachable from the UI

verification

No labels

Milestone

No items

No Milestone

Projects

Clear projects

No projects

Assignees

Clear assignees

extant2000git

No Assignees

1 Participants

Notifications

Subscribe

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: extant2000/flamenet-relay#117