Page 1 of 1

Aggressive Code Signature Enforcement

Posted: Fri Aug 24, 2018 6:20 pm
by Zafira
I am running the 4.1.4 nightly 5188 build in Mojave, I've noticed a very aggravating regression: users cannot allow applications with unsigned/invalid code signatures to have temporary allow rules. The alert only permits users to deny the message. If it is necessary to permit the application to access the network (e.g. Homebrew-built applications), a user has to go into the ruleset and manually enable it, but it can't just be a temporary rule.

Is this a known issue?

Re: Aggressive Code Signature Enforcement

Posted: Sun Aug 26, 2018 5:54 am
by steve2237
I disabled LS as the code signature enforcement do also include legitimate Apps like PathFinder, Transmission etc quite a pain in the butt