Skip to content

Harden DropPoint receiver lifecycle and storage#331

Open
shunichironomura wants to merge 1 commit into
mainfrom
droppoint-receiver-compliance
Open

Harden DropPoint receiver lifecycle and storage#331
shunichironomura wants to merge 1 commit into
mainfrom
droppoint-receiver-compliance

Conversation

@shunichironomura

Copy link
Copy Markdown
Member

Summary

  • enforce strict DropPoint protocol-v2, multipart, manifest, MIME, timestamp, base64url, and canonical filename validation
  • persist owner-only resumable receiver state and atomically install verified bundles with durable identity receipts
  • commit local attachment records before close, resume close after restart, and scrub capabilities only after terminal handling
  • centralize bounded HTTP behavior and capability redaction, and add jittered retry handling for receiver polling
  • import the normative DropPoint policy fixtures and document the durable bundle layout

Testing

  • just check-all
  • end-to-end mock-relay coverage for pickup, durable installation, execution recording, restart, close retry, and secret removal

@shunichironomura shunichironomura self-assigned this Jul 12, 2026
@shunichironomura
shunichironomura force-pushed the droppoint-receiver-compliance branch from 9cc853d to 014212b Compare July 15, 2026 06:26
@shunichironomura
shunichironomura force-pushed the droppoint-receiver-compliance branch from 014212b to ef571ac Compare July 16, 2026 07:23
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