Issues with Avast and another program

[lmltnetworks]

Hi all,

Mac OS 10.8.3

I currently running meraki agent which installs two services in /usr/sbin/m_agent and /user/sbin/m_agent_upgrade. The problem I have is that avast is preventing these services from accessing the cloud servers.

I thought I could add an exclusion in preferences for "file system shield" but you cannot access /usr as its a hidden directory, even if you unhide the directory it does not matter you still cannot map to it. I even tried creating an alias but his does not work either.

I then decided to see if the meraki agent should shed some light and this was the output.

client pcc23.meraki.com:993 timed out

So it trys to make an SSL connection via port 993.

Again this cannot be excluded under "Web Shield" as it only permits http(80)/https(443).

So my only option is to disable my AV for the interim.

PLEASE can anyone help or advise me on a possible solution? I already have a trouble ticket with Meraki as well.

[specimen9999]

You can just disable the webshield for secure connections.

[lmltnetworks]

You can just disable the webshield for secure connections.

Disable will test again but I still think the issue is more related to File System Shield.

[lmltnetworks]

I decided to uninstall it and go with Sophos for now.

[tumic]

I then decided to see if the meraki agent should shed some light and this was the output.

client pcc23.meraki.com:993 timed out

So it trys to make an SSL connection via port 993.

Again this cannot be excluded under "Web Shield" as it only permits http(80)/https(443).

Port 993 is IMAPS (secured IMAP), so it is the mailshield, not the webshield that is causing the issue.
If you disable SSL support in the mailshield by unchecking the "Scan secured connections" checkbox
in the mailshield preferences, then it should start working.

However, this is just a workaround. To get the root of the issue, it would be necessary to find out, why
the connection timeouts. My personal guess is that the meraki error message is wrong and in fact it is
a SSL certificate issue (the meraki agent does most probably not use the system keychain) that prevents
the meraki agent from connecting.