search

plotly / orca

Command line application for generating static images of interactive plotly charts
MIT License
294 stars 40 forks source link

Mac OS X: Getting rid of "Do you want the application" orca.app to accept incoming network connections #269

Open hkokko opened 4 years ago

hkokko commented 4 years ago

Is there a command line parameter or something else to get rid of the above dialog box. It comes up every time I run my python plotly application. My app works with "deny" and I would not like to give the "Allow"

antoinerg commented 4 years ago

Maybe @jonmmease could help out. I don't have a Mac at the moment and I am not familiar with Mac OS X permission system.

jonmmease commented 4 years ago

For context, when used with plotly.py orca is run as a subprocess and plotly.py communicates with it over a local network port. As far as I know, that means you will need to give orca.app "allow" permissions.

Since it is a subprocess, I believe you will only be giving these permissions to the orca.app process, not to your own application.

hkokko commented 4 years ago

plot.ly with orca.app seems to work whether I choose to deny or allow the permission. I would just love to get rid of the dialog every time I run my program...

jcsmit commented 4 years ago

I also had this issue and managed to resolve it by signing the application causing the prompt to be raised. In this case it would be orca.app (and possibly unsigned libraries inside the app package) that have to be signed.

I found the solution here: https://apple.stackexchange.com/a/150711, but it boils down to running

codesign --force --sign - /path/to/application.app

which performs "ad-hoc signing" of the application. Alternatively, you can use

codesign --force --sign <certname> /path/to/application.app

to sign using a certificate (https://apple.stackexchange.com/a/121010).

The way I understand it is that the permission dialog is shown on the first launch, but if the application is not signed the response is not saved - hence the reoccurring dialog.

lum4chi commented 4 years ago

I was able to get rid of the problem adding --deep and as super user, so:

sudo codesign --force --deep --sign - /path/to/application.app

Nevertheless you save me a lot of clicking, thank you!