Skip to content

Production build: transit v2 and sealed PQC responses in docs/ - #6

Merged
0c-coder merged 1 commit into
heroku-deployfrom
fix/drop-req-press-opcodes
Sep 16, 2026
Merged

0c-coder merged 1 commit into
heroku-deployfrom
fix/drop-req-press-opcodes

Conversation

@0c-coder

Copy link
Copy Markdown
Owner

Rebuild of docs/ so the deployed bundle carries the transit v2 framing and the sealed PQC composite responses. Source already merged in #5.

Verified in the built bundle: transit_seal/transit_open/transit_select and transit_framed present, the [3,0,5] version gate present, tagLength:128 on the v2 path with tagLength:0 surviving only in the v1 fallback, and no maxPacketSize=228 / COMPOSITE_MAX_PACKET=228 left.

…docs/

Rebuild of docs/ from the current source. What is new in the bundle:

- The FIDO2 transit framing, [counter(4)][ciphertext][tag(16)] with
  IV = [dir][counter][zero], replacing an all-zero IV and tagLength 0.
- transit_select(), which reads the firmware version out of the plain OKCONNECT
  response and falls back to the old scheme below 3.0.5, so nothing breaks
  against firmware in the field.
- Chunks at 224 rather than 228, which changes no chunk count.
- transit_framed() on the composite polls, now that okpqc.cpp seals its
  responses instead of sending shared secrets in the clear.

Verified in the built bundle: transit_seal/open/select and transit_framed are
present, the [3,0,5] version gate is there, tagLength:128 is on the v2 path
(tagLength:0 survives only in the v1 fallback), and no maxPacketSize=228 or
COMPOSITE_MAX_PACKET=228 remains.
@0c-coder
0c-coder merged commit 59f7f3b into heroku-deploy Sep 16, 2026
3 checks passed
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.

2 participants