Posted on 05-05-2016 01:32 PM
We've tried using the integrated OS X Firewall but ran into issues while using Cisco Jabber. When whitelisted, Jabber would prompt to allow/deny connections and since users aren't admins here, they were unable to use Jabber. This appears to be a known issue as others on this forum have had the same issue with Jabber.
Is anyone using a 3rd party firewall software that is easy to manage and monitor via Casper?
Posted on 05-05-2016 08:28 PM
Install via Self Service ? you could set that firewall exception at the time of install ? Seems simpler then any 3rd party alternative ?
Have a look at http://krypted.com/tag/manage-firewall-os-x-command-line/
Posted on 05-06-2016 02:39 PM
I've tried setting it via a bash script. The problem is even when the program is added to the firewall exception to always allow, it sometimes still prompts to allow/deny access, then prompts for admin password.
I've been using this..
checkFirewall=/usr/libexec/ApplicationFirewall/socketfilterfw --getglobalstate | awk '{print $3}'
if [[ "$checkFirewall" == "disabled." ]]; then
/usr/libexec/ApplicationFirewall/socketfilterfw --setglobalstate on
/usr/libexec/ApplicationFirewall/socketfilterfw --add /Applications/Cisco Jabber.app
/usr/libexec/ApplicationFirewall/socketfilterfw --add /Applications/Skype.app
else
echo "Firewall is already enabled"
fi
exit 0
Posted on 05-09-2016 11:30 AM
I've also tried to add the binary file /usr/libexec/ApplicationFirewall/socketfilterfw --add /Applications/Cisco Jabber.app/Contents/MacOS/Cisco Jabber to no avail
Some machines still prompt to allow/deny firewall when making external calls using Jabbber.
Posted on 05-09-2016 11:49 AM
Are all your system using the same version of Jabber? Same OS ?
If not I'm suspecting that the newer version might be allowed due to code signing certs and therefore not prompt ?
If you can duplicate the prompt, maybe try running Composer to see whats being "written" when Allow is selected ?
Posted on 05-09-2016 01:36 PM
I like the Composer idea. I'll give that a shot. Thanks!
They're all running the same version, mixed OS between 10.10.5 and 10.11.4
Posted on 06-15-2016 09:50 PM
@bbot did you find the solution in the end? This is happening to me now.
Thanks
Posted on 06-17-2016 09:25 AM
@tkimpton No solution yet... It's been a huge pain /w Cisco Jabber and the built-in OS X application firewall...
Posted on 07-04-2016 10:41 AM
I had this today trying to make a call. I reset my firewall and then it worked. This is what i did
#!/bin/bash
# turn the firewall off
/usr/libexec/ApplicationFirewall/socketfilterfw --setglobalstate off
# remove the plist file
rm -rf /Library/Preferences/com.apple.alf.plist
# remove Cisco Jabber if it is in the list
/usr/libexec/ApplicationFirewall/socketfilterfw --remove "/Applications/Cisco Jabber.app" > /dev/null 2>&1
# turn the firewall on
/usr/libexec/ApplicationFirewall/socketfilterfw --setglobalstate on
launchctl unload /System/Library/LaunchAgents/com.apple.alf.useragent.plist > /dev/null 2>&1
launchctl unload /System/Library/LaunchDaemons/com.apple.alf.agent.plist > /dev/null 2>&1
launchctl load /System/Library/LaunchAgents/com.apple.alf.useragent.plist > /dev/null 2>&1
launchctl load /System/Library/LaunchDaemons/com.apple.alf.agent.plist
Posted on 08-05-2016 03:34 AM