Code Signing

From FM Plugin Wikipedia
Jump to: navigation, search

The following page covers the steps to code sign your plugin

Mac OS X - XCode

Requirements: You need to have a Mac Developer Signing Certificate from Apple.

1) Open your 'Target' Plugin and under the 'Signing' section, tick the 'Automatically manage signing' option. You'll need to select your 'Team'

2) Build your plugin.


Note: If your plugin includes a step to copy the plugin to the FileMaker Extensions folder, make sure the 'Code Sign On Copy' option is also ticked - otherwise the plugin will not be code signed for the first build after making a change.


You can verify your plugin is code signed correctly in the terminal using: codesign --verify --verbose=4 IDMA.fmplugin

kent:Extensions kent$ codesign --verify --verbose=4 IDMA.fmplugin
IDMA.fmplugin: valid on disk
IDMA.fmplugin: satisfies its Designated Requirement

Windows - Visual Studio

Requirements: You need to have purchased a Code Signing certificate (.pfx) (I've purchased my certificate from Comodo CA)

1) Open the Properties for your project in Microsoft Visual Studio

2) Select Build Events --> Post-Build Event

3) Edit the 'Command Line' and add to the start: signtool sign /f {Path To Certificate} /p {password} /tr "$(TargetPath)"

4) Build Your Project.


Once you've built your project, you can get Properties on the output file to verify your signature