Profile Unsigner

Profile Unsigner

Remove the signature from .mobileconfig profiles and .pkg installers, so you can read and edit them. Runs only on your Mac and never sends files anywhere.

Signed profiles are stored as binary CMS data, so you can't open them in a text editor or upload them to Jamf Pro as a payload to edit. Profile Unsigner gives you back the plain profile. Use Profile Signer to sign it again afterwards.

How to use it

1. Drop one or more .mobileconfig or .pkg files onto the window, or click Choose Files…
2. Each file is processed straight away and listed, newest first. A file that couldn't be processed shows the reason.
3. Click Save… on a row to save that file, or Save All… to choose a folder for every file that hasn't been saved yet. Clear empties the list.

Unsigned files are named <name>_unsigned.mobileconfig or <name>_unsigned.pkg. The original file is never changed.

What it does

File	Result
.mobileconfig	The CMS signature is removed and the profile is saved as readable XML. A profile that isn't signed is saved as XML too
.pkg	The signature is removed from the package's table of contents, and its checksum is recalculated. The files inside aren't changed

Messages

Message	Meaning
File is not a signed profile or valid plist	The file isn't a configuration profile
Could not extract payload from signed profile	The signature couldn't be read, or holds no profile
Package does not appear to be signed	The package has no signature to remove
Not a .mobileconfig or .pkg file / Not a valid .pkg file	Check the file type

An unsigned package won't pass Gatekeeper when it's opened by hand. Packages deployed by Jamf Pro don't need to be signed.

Permissions: none. Profile Unsigner doesn't connect to Jamf Pro.