user425890uhh wrote:esseti wrote:RockGrumbler wrote:I have experienced this bug as well. In the initial warning I choose to ignore and nothing happens. I found a work around by using the link at the top of the dialogue window that exposes the rule. This brings up the rule in the configuration app. Then I chose to edit the rule, change nothing, and hit OK. After this I am prompted with a question to ignore code signatures. When I agree at this point, it seems to take effect and the problem is resolved, or at least the code signature is ignored. I'm on OS X 10.13 and using a Cisco VPN client.
this workaround actually works.
- edit the rules and do nothing
- edit the rules and uncheck " code signature checking"
- disable the bloking rule
at least now something works, let's see how long it last
The check box and text to disable code signature checking for my AnyConnect rules is grayed out. I'm unable to disable code signature checking for those rules.
Users browsing this forum: No registered users and 3 guests