secureblue: Chromium: "DefaultJavascriptJitSetting":2 breaks BigBlueButton
Happened recently, BBB website didnt load any UI, did not initiate portal/permission requests and the site stayed blank.
Meanwhile on self compiled Firefox (using hardened-malloc) they worked perfectly.
The profile was vanilla, excluded from using the VPN using mullvad-exclude chromium (as this is also my vanilla profile).
This report is incomplete and I will add terminal output, test if it was the VPNs fault (maybe blocked nonproxied WebRTC?) and also test on upstream Fedora. I could not see which part failed, WebRTC most likely.
(Btw on Vanadium (GrapheneOS) BBB works.)
Image used: kinoite-laptop-userns-main-hardened, a week ago.
About this issue
- Original URL
- State: closed
- Created 3 years ago
- Comments: 18
Added an FAQ on enablement
https://github.com/secureblue/secureblue/blob/live/FAQ.md#i-need-javascript-jit-in-chromium-how-do-i-enable-it
In case anyone comes across this thread, you can accomplish local overrides using additional files that are later in the alphabet, like so: https://github.com/secureblue/secureblue/issues/213#issuecomment-1975266245
I am able to repro this. Can you check whether you can repro with a blank policy file and without hardened_malloc on a standard ublue image?
If you can repro with that setup, then please cut a ticket to the fedora chromium package or possibly to upstream chromium. If you can’t please open a new issue here.
You can also try using
nixto install chromium to check for a repro with the nix chromium package, and if you can repro there as well, then definitely create an issue to upstream chromium at https://issues.chromium.org/issuesIt is a personal choice in that you are focused on getting your own local changes into their own separate files, without thinking about what this means for the broader project. For every single line of the chromium config file, the modprobe blacklist, and the sysctl file, someone might need to flip the setting back to how it was by default. This means having a separate file for every single configuration line, meaning hundreds of separate files. But you haven’t even acknowledged this because you are just asking for your own personal changes to have separate files without caring about the broader implications.
No, they would have to maintain it themselves. This is due to the nature of how rpm-ostree systems work. All users still get updates in
/usr, and it’s up to the user to merge that with local changes they’ve made if any.This isn’t ideal but I’m not aware of a way around this. What we would need is patchfiles instead of full overrides. As far as I’m aware, there’s nothing like this that’s supported.
https://github.com/secureblue/secureblue/commit/99aaa5b802953f5291fe2cab5691c9c9a976a9af
coincidentally, upstream chrome changed how JIT is managed and I removed the command line switch, so you can now configure allowing V8 per-site by adding your own separate policies file and adding sites to
JavaScriptJitAllowedForSites