Encryption plug-in adds new script steps and online help for FileMaker Pro 16.
Alphen aan den Rijn, Netherlands, August 15, 2017–Troi today announced the immediate availability of Troi Encryptor Plug-in 4.0 for FileMaker Pro 16.
What is Troi Encryptor Plug-in?
Troi Encryptor Plug-in is a very powerful tool for securing your FileMaker data, exporting or emailing your data without risk and importing safely back into FileMaker. All from within FileMaker you can:
- encrypt text or container fields, using the powerful 256-bit AES encryption scheme, so that your sensitive data is secure
- export encrypted data that can be sent safely across internet, for example via email. No risk that someone will read or change the data while in transit
- use the decryption functions to restore the original information after you have imported the received email or export file back into FileMaker, with the assurance that nobody will have tampered with it
- exchange AES-encrypted data with other systems (like for example PHP-mcrypt)
- verify data integrity and sources with SHA-1 message digests
- encode text in Base64
- make conversions to and from binary
- compress databases with large text fields
- save and retrieve passwords to and from the keychain of the operating system
What is new in version 4.0?
We rewrote Troi Encryptor Plug-in for FileMaker 16 and it now has the following new functionality:
- Tested and made compatible with FileMaker Pro 16.
- Fixed several bugs, rewrote and modernized the code in several places and made further improvements.
- Updated the User Guide and the Reference.fmp12 file.
- Made various minor changes to the example files to better work with FileMaker Pro 16.
- Updated the code by adding improved namespace handling to make the plug-in more robust.
Extra features when running FileMaker Pro 16
Version 4.0 adds the following new features when running in FileMaker 16:
- The Encryptor Plug-in adds multiple script steps when running in FileMaker Pro 16. You can select these script steps in the script steps pane in Script Workspace, or you can begin typing the script step name, then choose the script step from the list that appears. The script steps expand the possible actions you can perform with FileMaker Pro. Only steps that perform an action have been added as a script step. Functions that just manipulate data and have no side effect (like for example Encr_EncryptRijndaelAES) are only available as an external function.
The following three script steps are added:
- Save Password to Keychain
- Get Password from Keychain
- Delete Password from Keychain
- Added new scripts to the EncryptAES example file, which demonstrate how to use the new external script steps of FileMaker Pro 16. The examples check if FileMaker Pro 16 is running and will select these new scripts.
- Added support for online help for the functions and script steps of the plug-in. You can now easily get online help from the Troi website, by clicking the Help button (the small question mark button) next to the function description in the functions pane or the script step description in the script steps pane.
Apart from these additions we fixed several bugs and made various further improvements. More detailed information on all changes and improvements implemented in Troi Encryptor Plug-in 4.0 can be found at: https://www.troi.com/products/encryptorplugin/
Pricing & Availability
A fully functional demo version of Troi Encryptor Plug-in 4.0 is available for downloading at: https://www.troi.com/products/encryptorplugin/
Licenses cost US$ 79 per user. Details on developer licenses and multi-user discounts can be found on our web site. You can order licenses from our web site.
Version 4.0 needs a new registration. The upgrade is free for users who bought a license for Troi Encryptor Plug-in on or after July 5, 2016. Eligible users will be sent a new registration. Contact us if you have not received yours after August 18, 2017.
Upgrades from licenses bought before July 5, 2016 are available from US$ 39 per user. Upgrade prices for other licenses can be found on our web site. You can order upgrades from our web site.
I have a question about hosting my filemaker database. If I buy a license for 5 people form here: https://store.filemaker.com/filemaker-cloud , will I also need to purchase 5 normal FileMaker 16 Pro Client licenses so people can actually connect to the database? I don't quite understand how this works yet, maybe someone can help me out. Do I get the client licenses with the purchase of a server license? I need 5 people to be able to access it. Thanks in advance,
I have the following problem. I'm working on a solution for the owner of several restaurants. Each restaurant has meetings once or twice a month. How would I structure the tables so that I could have a layout on which I select a restaurant and then inside a portal I get a list of all employees. On the portal for each row I want to have a button or checkbox to mark if an employee is present or not.
I already have the following tables:
Restaurants, Employees and Meetings
So far I have a relationship between the Restaurants and Employees table which I use to assign employees to a restaurant, and a relationship between the Meeting and Restaurant table, which allows me to show all employees that work at a selected restaurant using a portal on the meetings layout. How do I proceed to solve my problem? Do I create another table MeetingAttendees or something similar that I use to keep track of people attending a meeting? How would I create a relationship then to allow me to mark certain employees as present and absent?
Thanks in advance,
We are running FM server 16 with FM pro 16 and FM Go 16 clients. We have do not use SSL certs as yet. When opening databases on the go client, the user is presented with a dialog stating that the connection is not secure and would they like to proceed. Secondly, programmatic access to the server is failing due to this new error being returned from the first "ping" of the server. I understand this is normal behaviour but obviously we want to get rid of this.
We need to sign our server. The problem is that it is used on the intranet only and CA's will not sign machines that are not public facing. We will not be making our server public facing.
What are the best practices surrounding getting this machine certified?
Any help appreciated.