You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit 360a8e7
Browse filesBrowse the repository at this point in the historyBrowse files
Copy file name to clipboardExpand all lines: docs/push-gateway-deployment.md
+26Lines changed: 26 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -45,6 +45,32 @@ select among multiple application profiles.
45
45
46
46
Optional endpoint quota policy variables are `BUZZ_PUSH_ENDPOINT_QUOTA_WINDOW_SECONDS` (default `10`, max `86400`) and `BUZZ_PUSH_ENDPOINT_QUOTA_MAX_DELIVERIES` (default `10`, max `10000`). These are Buzz policy hypotheses, not Apple-published limits; tune under load while retaining a hard ceiling.
47
47
48
+
## Personal device development
49
+
50
+
A development-signed iOS app uses Apple's development App Attest environment.
51
+
The ordinary gateway binary rejects those attestations. For an isolated personal
52
+
stack, build with Cargo feature `personal-dev-app-attest` (Docker build argument
53
+
`BUZZ_PUSH_CARGO_FEATURES=personal-dev-app-attest`) and set
54
+
`BUZZ_PUSH_APP_ATTEST_ENVIRONMENT=development`. The default remains `production`,
55
+
including in that special build; ordinary builds reject the development setting.
56
+
The gateway accepts exactly the selected AAGUID and still verifies the pinned
57
+
Apple root, certificate chain, nonce, application identity, public key,
58
+
credential ID, and counter. This is not a simulator or attestation bypass.
59
+
60
+
Set `BUZZ_PUSH_DOGFOOD_APP_ATTEST_APP_ID` to the personal `TEAMID.bundle-id`,
61
+
`BUZZ_PUSH_DOGFOOD_APNS_TOPIC` to that same bundle ID,
62
+
`BUZZ_PUSH_DOGFOOD_APNS_ENVIRONMENT=sandbox`, and supply its APNs certificate.
63
+
This isolated stack reuses the single `buzz-ios-dogfood` wire profile for its
64
+
server-owned personal identity; it does not add a production application profile.
65
+
Do not point distributed dogfood clients at this personal gateway.
66
+
67
+
Build the mobile client with the personal team and parent bundle ID, its matching
68
+
`.NotificationService` extension, development APNs/App Attest entitlements, and
69
+
an explicit `BUZZ_PUSH_GATEWAY_URL`. See `mobile/README.md` for gitignored signing
70
+
overrides. Both targets need matching provisioning profiles; the parent profile
71
+
must include the capabilities in `Runner.entitlements`. Validate enrollment and
72
+
notification presentation on a physical device, not a simulator.
73
+
48
74
## Secret and key rotation rules
49
75
50
76
Mount the App Attest root read-only and startup will reject any byte mismatch. The sole accepted artifact is Apple’s **Apple App Attestation Root CA** from `https://www.apple.com/certificateauthority/Apple_App_Attestation_Root_CA.pem`: certificate SHA-256 fingerprint `1C:B9:82:3B:A2:8B:A6:AD:2D:33:A0:06:94:1D:E2:AE:4F:51:3E:F1:D4:E8:31:B9:F7:E0:FA:7B:62:42:C9:32`; exact PEM-file SHA-256 `c778d09ac341f7fd9f8f3b19e2b815af6aed4ad4490e1e92c05cb355212a5013`. Treat an Apple root rotation as a reviewed code/config rollout, not an unpinned mount replacement. Mount the APNs certificate identity and both AEAD keyrings from a secret manager; never place values in an image, manifest, log, or metrics label. Keep the current AEAD key first and retain decrypt-only predecessors until every capability/token encrypted under them has expired or been re-encrypted. Grant and token key ids and bytes must be distinct. Rotation is an operator rollout: add the new current key while retaining predecessors, deploy, wait through the retention window, then remove the old key.
0 commit comments