Host and Secure Feeds
Patch Extend is currently in beta and available for testing. We're actively refining the feature and building out comprehensive documentation. We recommend evaluating it in a test environment before deploying to production, and we welcome your feedback as we continue to improve!
File vs web​
Type | URI | Notes |
|---|---|---|
file | Absolute path on the Mac (for example /Library/Application Support/…/feed.json) | Must be readable by root / the Patch process; keep write access administrator-controlled |
web | https://… feed URL | Optional feed-level Authentication (bearer or custom header) |
Configure feeds with a profile—see Configuring Patch Extend and Getting Started.
Who can write an unsigned file feed​
An unsigned feed (RequireSignature: false) is trusted once Patch can read it. Feed JSON can include version-check commands and install actions, so who can modify the file is a trust decision.
For local file feeds, keep administrator-controlled write access on both the feed file and the directory that contains it. Someone who can write the directory can replace a root:wheel / 644 feed file even if they cannot rewrite that inode in place.
Recommended baseline:
- Directory and file owned by an administrator-controlled account (for example
root:wheel) - Directory mode such as
755(writable only by the owner; not group- or world-writable) - Feed file mode such as
644so Patch (running as root) can read it while non-admin users cannot rewrite it - Avoid granting write via group membership or ACLs to non-admin principals on either the file or the directory
RequireSignature: false is a supported configuration, not a temporary stand-in for feed signing. Treat the feed like other admin-managed policy: control who can change the file or the HTTPS origin that serves it. Feed signing (RequireSignature: true with a trusted public key) is a separate integrity control; customer-facing signing tooling is not part of this documentation yet, so these pages do not require signed feeds for real deployments.
Feed authentication vs package authentication​
These are separate:
- Feed host auth — how Patch downloads the feed JSON. Set on the profile entry under
Authentication(bearerorheaderwith token / header name). This does not automatically authenticate package downloads. - Package download auth — how Patch downloads each app’s installer. Put credentials in the package
urlwhen the storage system expects that (common for Azure Blob SAS query strings), or use optional per-packagedownloadHeaderswhen the server needs headers (for exampleReferer).
Azure Blob SAS (package URL)​
Hosts can embed short-lived Azure SAS tokens in each package url when they generate the feed JSON:
https://contosoapps.blob.core.windows.net/patch-packages/ExampleApp-1.2.3.pkg?sv=…&sig=…
In the feed:
"url": "https://contosoapps.blob.core.windows.net/patch-packages/ExampleApp-1.2.3.pkg?sv=2024-11-04&sp=r&se=2026-11-06T18:00:00Z&sig=…"
(Example shape only—use tokens from your storage account.)
Choose a SAS lifetime that covers the window from when Patch reads the feed through when it downloads the package (including retries). Serving a brand-new token on every feed response only helps for clients that actually fetch that response before using the package URL.
TTLSeconds on the profile is optional and present for feed cache configuration. Do not assume a documented client default or a force-refresh procedure until your Patch build documents that behavior.
Package integrity​
It is recommended that authors populate package integrity (sha256, fileSize) so Patch can verify downloaded media. That is package integrity, not feed configuration signing.
fileSize is the on-disk byte length of the downloaded package (zip, dmg, pkg, …)—not the size after extraction. After you have the package file locally:
# Byte size for integrity.fileSize
stat -f%z /path/to/package.zip
# Hex digest for integrity.sha256
shasum -a 256 /path/to/package.zip
Example feed fragment:
"integrity": {
"sha256": "880d1f4b4474935fca5723ffbda0995376716d8bc94e499ff5a54cbc7b9be702",
"fileSize": 5230342
}