Format:Apple provisioning profile
| On this wiki | Facts · Code · Notes · Topics |
|---|
embedded.mobileprovision / .mobileprovision: a CMS (PKCS#7) signed blob wrapping an XML plist with the app id, team, certificates, device list and the entitlements the app may claim.
Structure
The file is a DER CMS (PKCS#7 SignedData) structure, not text; it starts with 30 80 or 30 82 (ASN.1 SEQUENCE). The signed content is an XML plist (<?xml ... <plist version="1.0">), so the plist can be pulled out of the raw file by searching for <?xml and </plist>; proper tools parse the CMS and take its content. blacktop/ipsw does it with a PKCS#7 parser and then a plist decoder (pkg/appstore/provision.go, function extractProfileUUID, reading the UUID key). On a Mac the same plist is printed by security cms -D -i embedded.mobileprovision. Unverified: that command from memory.
Files live in the app bundle as embedded.mobileprovision, and on a Mac in ~/Library/MobileDevice/Provisioning Profiles/<UUID>.mobileprovision (ipsw's comment names that folder and the UUID filename).
Plist keys
Unverified (typical keys from memory, not read in source in this pass): Name, UUID, AppIDName, ApplicationIdentifierPrefix, TeamIdentifier, TeamName, CreationDate, ExpirationDate, TimeToLive, Platform, DeveloperCertificates (array of DER certificates), ProvisionedDevices (UDIDs; present for development and ad hoc, absent for App Store and enterprise), ProvisionsAllDevices (enterprise), Entitlements (dictionary), Version.
Entitlements
The Entitlements dictionary lists what the signed app may claim, for example application-identifier, com.apple.developer.team-identifier, get-task-allow (true in development builds, which allows debuggers to attach), aps-environment, keychain-access-groups, app groups. The effective entitlements of the executable are stored in its own code signature as an XML plist blob (0xFADE7171) and a DER blob (0xFADE7172) (Format:Mach-O/Code signature), and must be a subset of what the profile allows. Extracting them from the Mach-O does not need the profile.
Reversing notes
- The profile tells you the signing team, expiry and whether the build is development, ad hoc, enterprise or App Store (device list and
get-task-allowgive it away). - It carries certificates, not private keys; do not publish device identifiers found in a profile.
See Format:IPA, Platform:IOS.
Code & repositories
- https://github.com/blacktop/ipsw @
a9eae76e8b1e901e4a03dd530defac8a1b33f91a· license: MIT
ipsw (MIT): internal/commands/macho/ipa.go reads IPA Payload layout; pkg/appstore/provision.go parses mobileprovision as PKCS#7 plus plist
Tested on: source read, not run: source read, not run · checked 2026-10-18; last activity 2026-10-16; Note: the latest release ships binaries; the wiki links only the source, never the binaries