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

Flatpak version of Firefox nightly doesn't pick up chrome-gnome-shell #97

Closed
gitjod opened this issue Sep 7, 2018 · 4 comments
Closed

Comments

@gitjod
Copy link

gitjod commented Sep 7, 2018

I installed the flatpak of Firefox nightly on Fedora Silverblue 28 and have chrome-gnome-shell installed: https://gitlab.gnome.org/GNOME/chrome-gnome-shell.

The rpm version of Firefox installed on the system picks up chrome-gnome-shell fine but the flatpak version doesn't. When I go to https://extensions.gnome.org/ in the flatpak firefox it see the message on the webpage: "Although GNOME Shell integration extension is running, native host connector is not detected. Refer documentation for instructions about installing connector."

I don't know if this is a firefox nightly issue or a flatpak issue

@rmader
Copy link

rmader commented Sep 9, 2018

Well that sounds right, actually :) Flatpak is a sandbox after all.
Basically there are two scenarios:

  • you installed chrome-gnome-shell on the system. Then firefox is not allowed to talk to it and some portal would be needed. And most importantly, the user would need to get asked for permission to change her shell. I guess many people would say 'no' here, as the whole benefit of the sandbox would be lost. Seriously, being able to install GS-extensions is equal to full control over the users session. Imagine an app on your phone asking for full permissions to do anything.
  • you installed chrome-gnome-shell in the same sandbox as firefox. Then it shouldn't be able to do anything by design

Off-topic: I have to say I really hope the gnome devs change their mind about how they distribute gs-extensions. GS-extensions are highly security sensitive. I don't think a website is the right spot for them. People should be able to install them through gnome-software, that's were they belong.

@gitjod
Copy link
Author

gitjod commented Sep 9, 2018

Thanks yes your points make sense. I tried both installing chrome-gnome-shell on the system and installing it in the same sandbox as firefox. This worked for flash-plugin but as you point out in the case of chrome-gnome-shell it wouldn't work. Basically chrome-gnome-shell can't see outside the sandbox.

@gitjod gitjod closed this as completed Sep 9, 2018
@gitjod
Copy link
Author

gitjod commented Sep 10, 2018

Given chrome-gnome-shell when installed on the system works with google-chrome which is sandboxed, the expectation should be that it should work with a flatpaked firefox in a similar manner. Is there anyway you can achieve this with your flatpak of firefox or are you reluctant to do this given your understandable reservations that you have expressed in your comment above?

@gitjod gitjod reopened this Sep 10, 2018
@wvengen
Copy link

wvengen commented Sep 10, 2018

Google Chrome is not (generally) sandboxed as an app, but has ways to effectively 'sandbox' code running on a webpage. This is quite different from Firefox running as a flatpak, which sandboxes the whole app. So even if Firefox itself misbehaves, it is still protected by the sandbox. So the answer is that Firefox can't install GNOME Shell extensions without introducing serious security concerns as explained above.

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

3 participants