Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

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

Open
hkokko opened this issue Nov 25, 2019 · 5 comments
Labels
type: installation issue issues related to installation

Comments

@hkokko
Copy link

hkokko commented Nov 25, 2019

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
Copy link
Collaborator

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.

@antoinerg antoinerg added the type: installation issue issues related to installation label Jan 21, 2020
@jonmmease
Copy link
Contributor

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
Copy link
Author

hkokko commented Jan 25, 2020

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
Copy link

jcsmit commented Apr 22, 2020

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
Copy link

lum4chi commented Apr 28, 2020

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!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type: installation issue issues related to installation
Projects
None yet
Development

No branches or pull requests

5 participants