We sign our Troi plug-ins
Every day it becomes more important that people can trust the software that is installed on their computer. To help you trust our software, and more specifically our plug-ins for FileMaker, we now sign our software code. When you check our plug-ins you should get a valid signature, with the right name.
The macOS versions of our plug-ins are signed with this:
Name: Developer ID Application: Troi Automatisering (325BA5VM75) Issued by: Developer ID Certification Authority
On Windows our plug-ins are signed like this:
Name: Troi Automatisering V.O.F. Issued by: COMODO RSA Code Signing CA
Verify the Signature
You can use the Troi File Plug-in to check the status of a plug-in with the TrFile_GetCodeSignInfo function.
On macOS you can also verify if a plug-in is signed properly with the terminal. First open the terminal app and go to the folder of the plug-in. Then this command will verify if the plug-in has a valid code sign certificate (in this example our Troi File Plug-in):
codesign --verify --verbose=4 Troi_File.fmplugin
On Windows you can also verify if a plug-in is signed properly, by getting the properties of the plug-in. Right click on the plug-in and select Properties. Then click on the “Digital Signatures” tab:
The Digital Signatures tab of Troi File Plug-in, signed by Troi Automatisering V.O.F.
You can get further details by clicking on the Details button and view the certificate too:
Details of Digital Signature and the Certificate of Troi File Plug-in .
Overview of signed plug-ins
All our current plug-ins are signed on macOS. In the table below you can see which of our current plug-ins are also signed on Windows.
|Activator Plug-in||4.5.1||–||not signed on Windows|
|Text Plug-in||4.5||–||not signed on Windows|
* This is the first version that was signed
More signatures to come for Windows
We will add code signatures for Windows for the remaining unsigned plug-ins when we update them.
- Wikipedia: Code Signing which explains code signing in detail.