accept incoming network comm?

[Julia123]

Ever since I updated to DP 8.0 - 8.04, I've had the warning when DP is opening "Do you want the application "Digital Performer.app to accept incoming network connections?"
I have gone into the firewall preferences and have DP selected to allow incoming connections as the warning suggests, but it does not fix the problem. I've looked around online and there are suggestions to change the problem application's name and do other things that I don't understand enough to risk messing things up. Has anyone had this issue with DP and fixed it? Thanks--

[bayswater]

I had the same experience, and was unable to find any firewall settings that made it stop. It stopped after one of the Mountain Lion updates.

[MIDI Life Crisis]

Get Little Snitch!

[FMiguelez]

I get that annoying message too. Not with DP, but with VE Pro in only one of the slaves.

I've made sure anything related to VSL has permission to receive comms in the firewall's advanced preferences, but no matter what I do, the message pops up every time I open VE Pro...

[NazRat]

Do you have an OSC controller configured? That might be the source because OSC listens on ports for connections. I don't use the Mac firewall so not sure on what the configuration would be. If you remove any configured OSC controller and the message goes away, you'll know that's the source.

[MIDI Life Crisis]

LITTLE SNITCH!

[billf]

As MLC says above, get Little Snitch. That should be a required app for security purposes on any Mac that is hooked to the network.

[FMiguelez]

I do have little snitch in my laptop.

I can try installing it in the slave, but how would that help? Wouldn't it just alert me that a connection is being solicited? Then I could accept or decline, but then what?

(Obviously I haven't used LS much. It annoyed me and I disabled it long ago, but if you think that could help, perhaps you can tell me more, please?)

[MIDI Life Crisis]

As MLC says above, get Little Snitch. That should be a required app for security purposes on any Mac that is hooked to the network.

People who don't have it just don't realize how many apps phone home. They also don't realize how many seemingly innocent emails also access all sports of websites collecting data. LS is the easiest way to stop an infected or malicious app from blowing up your system.

Stopping DP, Adobe, et al (especially et al!) from phoning home or calling a friend is just the tip of the iceberg. You can actually SEE what's going on, how much is being transferred at what speed, etc., and control it all.

Just do it. End of story!

FM - once you set a rule to allow or disallow forever, the app obeys (and you can change the rule). THe only exception is apps that check the local network for additional programs running (such as Quickeys). But that's not going out to the internet. If you haven't updated to version 3, do so. June 18, 2013 ver 3.1.1 was released.

[bayswater]

I do have little snitch in my laptop.

I can try installing it in the slave, but how would that help? Wouldn't it just alert me that a connection is being solicited? Then I could accept or decline, but then what?

(Obviously I haven't used LS much. It annoyed me and I disabled it long ago, but if you think that could help, perhaps you can tell me more, please?)

Little snitch doesn't control incoming traffic, just outgoing traffic from your Mac. So to use it to stop these messages, you stop DP, or VE, or whatever, from sending out a message to it's home site. Then the home site will not be sending back a message that causes your Mac to ask if it should be accepted. Not a real solution to the original problem, but it gets you where you want. In your case, remove all the rules associated with VE, then the first time you are asked if it can send out a message, set LS to deny all outgoing requests on all ports to all sites for all time. It might then sit in the corner and sulk but you'll get some peace and quiet.

[NazRat]

Little snitch doesn't control incoming traffic, just outgoing traffic from your Mac.

You might want to look into that. The new version has inbound capabilities.

So to use it to stop these messages, you stop DP, or VE, or whatever, from sending out a message to it's home site. Then the home site will not be sending back a message that causes your Mac to ask if it should be accepted.

Your computer does not ask to accept return traffic for connections that you initiate. When it does ask is if you start an app that listens for connections that other apps or computers initiate to those apps on your machine. Apps like VEP and DP's OSC capability set themselves up to listen for incoming connections (for VEP the server is listening for other Vienna components to contact it and DP is listening for an OSC controller app on your iWhatever to initiate a connect. The difference is that these connections are initiated by other apps and devices and the firewall just wants to make sure you're good with it.

[bayswater]

Little snitch doesn't control incoming traffic, just outgoing traffic from your Mac.

You might want to look into that. The new version has inbound capabilities.

Yes, I saw some basic inbound stuff but these rules do not appear to be editable. My poorly made point was that the application of LS to solve the OP's problem involves managing outgoing messages, not incoming.

So to use it to stop these messages, you stop DP, or VE, or whatever, from sending out a message to it's home site. Then the home site will not be sending back a message that causes your Mac to ask if it should be accepted.

Your computer does not ask to accept return traffic for connections that you initiate. When it does ask is if you start an app that listens for connections that other apps or computers initiate to those apps on your machine.

Then why does the question to allow incoming communications to DP stop when you prevent outgoing communications from DP via Little Snitch?

[NazRat]

Because if you don't allow any outbound communication, letting anything connect (inbound) to DP would be useless. I can't say for sure how DP is programmed, but if DP is not allowed an outbound connection to start, it just wouldn't bother listening for anything. I'm surprised you haven't had any issue with DP8 authentication, because the first thing it does is phone home to see who you are - not quite sure how they keep you at the two machine max when folks deny outbound traffic or keep machines offline.

[cuttime]

Still on v 7 here, but is "Check for Updates Automatically" still an option under the "Help" menu?

[bayswater]

I'm surprised you haven't had any issue with DP8 authentication, because the first thing it does is phone home to see who you are - not quite sure how they keep you at the two machine max when folks deny outbound traffic or keep machines offline.

I was wondering that too. My assumption is that it keeps a count of the net of authorizations and de-authorization, and the connection only has to be active to do one of the two operations, but not to run DP. I don't have the outbound prevention on for DP8/OS ML anyway. As I mentioned above, the problem went away at the time of one of the ML updates. It looked like there had been a problem with the ability of the firewall to recall that I had already permitted inbound access. Besides, wouldn't the authorization be a separate process from DP, subject to different rules?