Notarization Mode: Non-Notarized Bash Script From VPN

[RetroWindow]

We are seeing the attached alert on our two Macs which are running a VPN (IVPN.net). On my wife's computer she may have multiple pop-ups appear sequentially which I have not personally experienced.

I have found a single rule related to IVPN which is allowed. I understand that clicking "Allow" in an alert is not saved between System and BlockBlock reboots, which I assume is the reason why the "temporarily" checkbox is greyed-out. (And why the rule is allowed when I look it up.)

Why can't I allow the script to run permanently since it is from a trusted app that I installed? I've read the documentation a couple times but I haven't found an answer (or understand if one does exist).

At this point we will have to forgo using the Notarization Mode until we have a resolution.

Many thanks- GV

[RetroWindow]

FWIW, I received this reply from IVPN support:

"Our development team has not had the opportunity to comment on the issue, though I can confirm that IVPN App's DMG installer file is notarized, though it seems that the firewall.sh shell script might fall outside this larger notarization umbrella."

[objective-see]

(in theory) BB should only trigger this alert on non-notarized scripts that have the quarantine attribute set (i.e. they come from the Internet).

Can you run, from a terminal:
xattr -rc /Applications/IVPN.app/Contents/Resources/ect/firewall.sh

This will just clear any extended attributes, so then, BB shouldn't alert you about it anymore! Though pls lmk if it still does 🙏🏽

[RetroWindow]

I ran the command on both Macs and this was the result:

xattr: No such file: /Applications/IVPN.app/Contents/Resources/ect/firewall.sh

Is this what you expected? I have limited experience using Terminal. . .

We recently haven't seen more alerts but I'll get back to you if we do.

[RetroWindow]

Having other business on GitHub today I noticed that I allowed this issue to lapse in my consciousness; sorry about that.

FWIW, we have continued to get BlockBlock alerts and the only fix is to disable Notarization Mode.