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

Firefox asking for permission every time #80

Closed
real-or-random opened this issue Dec 26, 2020 · 4 comments
Closed

Firefox asking for permission every time #80

real-or-random opened this issue Dec 26, 2020 · 4 comments

Comments

@real-or-random
Copy link

real-or-random commented Dec 26, 2020

Like #68 but for Firefox.

Workaround is to set security.external_protocol_requires_permission to false but it would be nice if there was a way to make sure URIs opened by the extension do not trigger the warning.

@japhir
Copy link

japhir commented Feb 5, 2021

I've encountered the same issue, thanks for mentioning the workaround! :)

@wehlutyk
Copy link

Also had the same issue, thanks for the workaround!

As mentioned on this reddit thread, it does sound like a security hole, so it would be nice to have a per-protocol setting.

@wehlutyk
Copy link

@sprig
Copy link
Owner

sprig commented Aug 28, 2024

It's not a security hole but rather a security feature, as one would not normally want pages/extensions to be able to send arbitrary URLs to the OS, which could potentially execute arbitrary code (especially in emacs). As far as I know there is no permission API that would allow one to disable the confirmation and rather needs to be set from the user end.

To expand on @wehlutyk's link, it looks like it might be possible to do this from the user-end in firefox by going to about:config and adding a setting for network.protocol-handler.external.org-protocol;
Screenshot 2024-08-28 at 08 51 04
However, at least in my case firefox complains of failure to capture after enabling this (although the capture actually is successful and proceeds with no confirmation dialog). However note that this would potentially allow arbitrary sites to send org-protocol links to emacs, and although likely extremely niche, I would still be weary of the security implications of this.

@sprig sprig closed this as completed Aug 28, 2024
@sprig sprig pinned this issue Aug 28, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants