Auth: authorize releases by identity on any device (not only the device with the contract receipt) #3

Open
opened 2026-10-10 18:23:08 +00:00 by rhelwig · 3 comments
Owner

Right now the ability to approve a release depends on which device holds the owner-specific contract's registration receipt. Approval should depend only on the identity.

Seen on 2026-10-10: the phone (Pixel 4a, Auth 0.1.15) said "This release does not match a verified contract on this device." It had the same imported identity (rhelwig7). Only the tablet, which registered the contract, could approve.

Wanted: any device with the identity's keys can authorize. Options:

  • Add a "verify existing contract" flow that fetches the contract from Platform, checks the owner, schema hash and ID against the release, and saves a receipt on that device without registering again.
  • Or derive verification from Platform state instead of a local receipt.

Device-independent approval must not weaken the existing contract-mismatch protections.

Follow-up notes: https://git.ronhelwig.com/rhelwig/DecentSite/src/branch/main/docs/PUBLISH-FOLLOWUPS-2026-10-10.md

Right now the ability to approve a release depends on which device holds the owner-specific contract's registration receipt. Approval should depend only on the identity. **Seen on 2026-10-10:** the phone (Pixel 4a, Auth 0.1.15) said "This release does not match a verified contract on this device." It had the same imported identity (rhelwig7). Only the tablet, which registered the contract, could approve. **Wanted:** any device with the identity's keys can authorize. Options: - Add a "verify existing contract" flow that fetches the contract from Platform, checks the owner, schema hash and ID against the release, and saves a receipt on that device without registering again. - Or derive verification from Platform state instead of a local receipt. Device-independent approval must not weaken the existing contract-mismatch protections. Follow-up notes: https://git.ronhelwig.com/rhelwig/DecentSite/src/branch/main/docs/PUBLISH-FOLLOWUPS-2026-10-10.md
Author
Owner

Fixed on branch fix/auth-verify-contract-any-device (6eb5b5b), Auth 0.1.17.

A device that imported the owner identity but didn’t register the owner-specific contract now proof-verifies the contract named in the release QR on Platform (read-only, no fee). The contract must be owned by the release owner, have the exact bundled v1 schema, and not be a shared-registry contract. Only then does Auth save a local receipt (source: platform-verification) and open the review. Mismatched existing receipts and pending registrations still fail closed. Release-time contract, key, nonce and fee checks are unchanged.

Phone path: scan any release QR from Admin once → Auth verifies the contract → receipt saved → review opens.

Tests: tests/auth-engine.test.ts, ReviewDestinationTest. Docs: DECENTSITE-AUTH.md, SPECS.md, IMPLEMENTATION-PLAN.md. Close after an on-device check on the phone.

Fixed on branch `fix/auth-verify-contract-any-device` (`6eb5b5b`), Auth **0.1.17**. A device that imported the owner identity but didn’t register the owner-specific contract now proof-verifies the contract named in the release QR on Platform (read-only, no fee). The contract must be owned by the release owner, have the exact bundled v1 schema, and not be a shared-registry contract. Only then does Auth save a local receipt (`source: platform-verification`) and open the review. Mismatched existing receipts and pending registrations still fail closed. Release-time contract, key, nonce and fee checks are unchanged. **Phone path:** scan any release QR from Admin once → Auth verifies the contract → receipt saved → review opens. Tests: `tests/auth-engine.test.ts`, ReviewDestinationTest. Docs: DECENTSITE-AUTH.md, SPECS.md, IMPLEMENTATION-PLAN.md. Close after an on-device check on the phone.
Author
Owner

Merged to main in d379421 (merge of fix/auth-verify-contract-any-device @ 6eb5b5b on top of PR #8). Ships in Auth 0.1.18 (versionCode 19), which combines this with continue-on-fail (#4). The two parallel 0.1.17 branches were reconciled; no 0.1.17 build is the release of record.

  • Tests: 166/166 Node tests pass; Kotlin :protocol:test passes.
  • Mainnet debug APK built on the laptop with the same debug signing key as 0.1.15/0.1.16 (cert SHA-256 9312fcfd…ef1ea3): ~/Projects/DecentSite-auth-credits/apk/decentsite-auth-0.1.18-mainnet-debug.apk.
  • Changelog: docs/DECENTSITE-AUTH.md (0.1.18 section).

Leaving open until the phone (Pixel 4a) smoke-tests a release scan with 0.1.18.

Merged to `main` in d379421 (merge of `fix/auth-verify-contract-any-device` @ 6eb5b5b on top of PR #8). Ships in **Auth 0.1.18** (versionCode 19), which combines this with continue-on-fail (#4). The two parallel 0.1.17 branches were reconciled; no 0.1.17 build is the release of record. - Tests: 166/166 Node tests pass; Kotlin `:protocol:test` passes. - Mainnet debug APK built on the laptop with the same debug signing key as 0.1.15/0.1.16 (cert SHA-256 9312fcfd…ef1ea3): `~/Projects/DecentSite-auth-credits/apk/decentsite-auth-0.1.18-mainnet-debug.apk`. - Changelog: `docs/DECENTSITE-AUTH.md` (0.1.18 section). Leaving open until the phone (Pixel 4a) smoke-tests a release scan with 0.1.18.
Author
Owner

Reminder: this can't be closed until the Pixel smoke test is done. The any-device contract verify shipped in Auth 0.1.18 and is included in 0.1.20, which is on the tablet now. To close it: install 0.1.20 on the Pixel 4a, scan a release QR there, and confirm it reads the owner contract from Platform (read-only, no fee), saves a receipt and opens review without the "does not match a verified contract on this device" error.

Reminder: this can't be closed until the Pixel smoke test is done. The any-device contract verify shipped in Auth 0.1.18 and is included in 0.1.20, which is on the tablet now. To close it: install 0.1.20 on the Pixel 4a, scan a release QR there, and confirm it reads the owner contract from Platform (read-only, no fee), saves a receipt and opens review without the "does not match a verified contract on this device" error.
Sign in to join this conversation.
No labels
feature request
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
rhelwig/DecentSite#3
No description provided.