Issue upgrading FAH client to 7.6.9 on MacOS 10.15.4

[Michael_Smith]

Howdy folders! I'm trying to upgrade my FAH client from 7.5.1 to 7.6.9. After I download and open the package, I get the following message:

“fah-installer_7.6.9_x86_64.pkg” can’t be opened because Apple cannot check it for malicious software.
This software needs to be updated. Contact the developer for more information.

My google-fu has failed me. Is this a known issue? If so, what's the fix? Many thanks!

(Not an emergency - the old client is running fine, so far. I just like to keep up to date when I can.)

[Joe_H]

Older versions were signed with a developer credential that is not accepted for Mojave and Catalina as Apple has added additional requirements for signing. They are looking into that, but may not be able to meet those requirements.

However you can OK the use of the installer with admin privileges and install the software anyways. That is done on the Security control panel.

[Michael_Smith]

Thanks Joe_H, I was able to find some instructions with that hint (at https://www.imore.com/how-open-apps-any ... and-mojave) and was able to install the client. (Please note: these instructions almost certainly violate one's organization's security policies. Fortunately I'm a lone individual who owns his own laptop and has some idea what he's doing. One proceeds at one's own risk.)

Thanks again,
Michael_Smith

[calxalot]

If you’re logged in to an account with administrator privileges, all you have to do is right-click (or control-click) on the installer package and select Open from the contextual menu.

[Joe_H]

Also, going to the Security panel right after attempting to open the Installer will give you the option to OK it as a one time thing. The directions on that website give you the option to always ignore Gatekeeper.

[calxalot]

Always ignore gatekeeper is BAD thing.

[valkraider]

Yes, completely turning off Gatekeeper is a bad thing. That should never be an instruction.

But even making an exception for turning off a certain application is also an unnecessary risk. It is 2020, signing and notorizing code is not a new thing and is more and more becoming the norm.

I literally ran into this last night with the open-source text editor Atom. They had a build which broke the notarization, and would not install on a Mac - but it was quickly patched and the nightly now installs again correctly signed and notarized.

With all the attention FaH is getting, there has to be one single volunteer who can help with this. I have offered up my assistance from an administrative perspective - I would be happy to help push things through. I can't do much from a code perspective though. Also - I have to think that Apple would happily donate resources to help out with this project - similar to how Microsoft has.

We should not be asking people to choose between helping to cure diseases, and weakening security on their computer.

It's a bad thing to do, and it also presents a strange barrier to new people wanting to come online and pitch in.

[Michael_Smith]

Always ignore gatekeeper is BAD thing.

Totally agreed - I ended up downloading the package, turning off network, turning off gatekeeper, installing package, turning on gatekeeper, turning on network.

Also agreed that it would be nice if we could get the code properly signed. But beggars can't be choosers.