[GH-ISSUE #2744] Firefox doesn't work with W^X enforced by firejail #1724

Closed
opened 2026-05-05 08:23:29 -06:00 by gitea-mirror · 12 comments
Owner

Originally created by @KOLANICH on GitHub (Jun 3, 2019).
Original GitHub issue: https://github.com/netblue30/firejail/issues/2744

Originally created by @KOLANICH on GitHub (Jun 3, 2019). Original GitHub issue: https://github.com/netblue30/firejail/issues/2744
gitea-mirror 2026-05-05 08:23:29 -06:00
Author
Owner

@chiraag-nataraj commented on GitHub (Jun 3, 2019):

Which version of Firefox? Which version of firejail?

<!-- gh-comment-id:498345933 --> @chiraag-nataraj commented on GitHub (Jun 3, 2019): Which version of Firefox? Which version of firejail?
Author
Owner

@Vincent43 commented on GitHub (Jun 3, 2019):

This is expected. browsers aren't compatible with W^X.

<!-- gh-comment-id:498354952 --> @Vincent43 commented on GitHub (Jun 3, 2019): This is expected. browsers aren't compatible with W^X.
Author
Owner

@KOLANICH commented on GitHub (Jun 3, 2019):

https://jandemooij.nl/blog/2015/12/29/wx-jit-code-enabled-in-firefox/

<!-- gh-comment-id:498376146 --> @KOLANICH commented on GitHub (Jun 3, 2019): https://jandemooij.nl/blog/2015/12/29/wx-jit-code-enabled-in-firefox/
Author
Owner

@KOLANICH commented on GitHub (Jun 3, 2019):

Which version of Firefox?

The latest one in Ubuntu repo.

Which version of firejail?

The one built today from git.

<!-- gh-comment-id:498376507 --> @KOLANICH commented on GitHub (Jun 3, 2019): >Which version of Firefox? The latest one in Ubuntu repo. >Which version of firejail? The one built today from git.
Author
Owner

@chiraag-nataraj commented on GitHub (Jun 3, 2019):

Okay, but GTK+ and Qt don't like W^X. At all. There's a lot more to this than just the JIT compiler.

<!-- gh-comment-id:498377207 --> @chiraag-nataraj commented on GitHub (Jun 3, 2019): Okay, but GTK+ and Qt don't like W^X. At all. There's a lot more to this than just the JIT compiler.
Author
Owner

@chiraag-nataraj commented on GitHub (Jun 3, 2019):

It doesn't look like we enable W^X for Firefox in the profiles we distribute, so I'm confused as to why you opened this issue, to be honest. The fact that Firefox (and pretty much every graphical program) doesn't work with W^X is a problem to file in their bug trackers, not on here.

This would be more understandable if we mistakenly enabled W^X for Firefox or something, but we're not doing that.

<!-- gh-comment-id:498378603 --> @chiraag-nataraj commented on GitHub (Jun 3, 2019): It doesn't look like we enable W^X for Firefox in the profiles we distribute, so I'm confused as to why you opened this issue, to be honest. The fact that Firefox (and pretty much _every_ graphical program) doesn't work with W^X is a problem to file in _their_ bug trackers, not on here. This would be more understandable if we mistakenly enabled W^X for Firefox or something, but we're not doing that.
Author
Owner

@chiraag-nataraj commented on GitHub (Jun 3, 2019):

I'm going to go ahead and close this since there isn't much we can do about it from our end. Feel free to re-open if I misunderstood something.

<!-- gh-comment-id:498378959 --> @chiraag-nataraj commented on GitHub (Jun 3, 2019): I'm going to go ahead and close this since there isn't much we can do about it from our end. Feel free to re-open if I misunderstood something.
Author
Owner

@KOLANICH commented on GitHub (Jun 3, 2019):

The fact that Firefox (and pretty much every graphical program) doesn't work with W^X is a problem to file in their bug trackers, not on here.

Definitely. But we need to track compatibility issues on our side too. Maybe a special issue which head post is updated by a bot reading specially formatted comments in profiles?

Okay, but GTK+ and Qt don't like W^X.

Yeah, if it is a case, this is surely their bugs.

<!-- gh-comment-id:498395749 --> @KOLANICH commented on GitHub (Jun 3, 2019): >The fact that Firefox (and pretty much every graphical program) doesn't work with W^X is a problem to file in their bug trackers, not on here. Definitely. But we need to track compatibility issues on our side too. Maybe a special issue which head post is updated by a bot reading specially formatted comments in profiles? >Okay, but GTK+ and Qt don't like W^X. Yeah, if it is a case, this is surely their bugs.
Author
Owner

@chiraag-nataraj commented on GitHub (Jun 3, 2019):

This isn't a compatibility issue, though. There's literally nothing we can do from our end besides disabling the flag for that profile. File bugs upstream and see if they'll change things. I highly suspect they won't :/

<!-- gh-comment-id:498398110 --> @chiraag-nataraj commented on GitHub (Jun 3, 2019): This isn't a compatibility issue, though. There's literally nothing we can do from our end besides disabling the flag for that profile. File bugs upstream and see if they'll change things. I highly suspect they won't :/
Author
Owner

@Vincent43 commented on GitHub (Jun 3, 2019):

That article is quite dated so it's hard to figure what current status is. Also as already noted above support W^X in some part of app doesn't mean the whole running process under firejail will support it. Someone in comments stated that you have to build firefox with --disable-ion (is it still valid?) but the cost is quite high. There are also some jit related options in config you may try disabling.

<!-- gh-comment-id:498403906 --> @Vincent43 commented on GitHub (Jun 3, 2019): That article is quite dated so it's hard to figure what current status is. Also as already noted above support W^X in some part of app doesn't mean the whole running process under firejail will support it. [Someone in comments](https://jandemooij.nl/blog/2015/12/29/wx-jit-code-enabled-in-firefox/#comment-2432767666) stated that you have to build firefox with `--disable-ion` (is it still valid?) but the cost is quite high. There are also [some jit related options in config](https://en.wikibooks.org/wiki/Grsecurity/Application-specific_Settings#Firefox_(or_Iceweasel_in_Debian)) you may try disabling.
Author
Owner

@SkewedZeppelin commented on GitHub (Jun 3, 2019):

@Vincent43

(is it still valid?)

https://searchfox.org/mozilla-central/source/js/src/devtools/automation/variants/nojit
seems so, who knows if it actually works
iirc on some platforms like POWER it ships disabled, so it should I guess?

<!-- gh-comment-id:498406000 --> @SkewedZeppelin commented on GitHub (Jun 3, 2019): @Vincent43 > (is it still valid?) https://searchfox.org/mozilla-central/source/js/src/devtools/automation/variants/nojit seems so, who knows if it actually works iirc on some platforms like POWER it ships disabled, so it should I guess?
Author
Owner
<!-- gh-comment-id:498414956 --> @KOLANICH commented on GitHub (Jun 3, 2019): https://bugzilla.mozilla.org/show_bug.cgi?id=1338207 https://bugzilla.mozilla.org/show_bug.cgi?id=1371877
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: github-starred/firejail#1724
No description provided.