> Also, how would this affect the > `iceweasel-hardened' package? I'm pretty sure that it'll be easily > transferable, but I have little knowledge of Abrowser. At it's core, the hardened package is three components: 1) Two extra prefs.js files are added to the /usr/lib/iceweasel/browser/defaults/preferences folder. 2) firejail with a few non-default profile parameters 3) A loader script that cats the contents of the invalidly named prefs.js into the second prefs.js on run and blanks it on close so that users can easily fallback to non-restricted parameters if required.
All three are easily modified to another Firefox fork since they are so similar. Replace every usage of iceweasel with icecat or abrowser and it's pretty much done. A few preferences might not be valid, since mainline adds/removes/tweaks preferences nearly every release compared to ESR, but in large they are almost identical and the browser ignores preferences it doesn't support. Personally, I ended up just placing the prefs.js manually and editing the /etc/firejail/icecat.local with the extra parameters to avoid how the package creates the prefs.js with 777 permissions. -jc
signature.asc
Description: This is a digitally signed message part.
_______________________________________________ Dev mailing list [email protected] https://lists.parabola.nu/mailman/listinfo/dev
