Those are the ones you can tweak for now via about:config at runtime (or vi
~/.mozilla/firefox/$YOURPROFILE/prefs.js if it doesnt start)
If you want to disable a pledge, put a random invalid string in the config key.
Of course, you'll get zero support from me.
I've been using those without issues for the past two weeks, but always in a
desktop environment (Xfce). For some of you who don't run desktop sessions and
have no dbus-daemon running, maybe you should start it somehow within your
session, otherwise the content process seems to try spawning it via glib at the
first use, and gets killed as it has no 'proc' or 'exec' rights. Tough luck.
If you get an abort from pledge, collect:
- what you were doing, on which website, etc etc
- firefox stdout, to figure out the various processes/pids running
- what process was killed, for which syscall (ie in dmesg)
- have a look at ~/firefox.core via egdb, try to get a meaningful trace of the
codepath that triggered the pledge. There might be dragons/hidden signal
- try to reproduce the crash inside ktrace/kdump (ie start ffx via 'ktrace -di
-t cp -- firefox', thx kn@)
- the codebase is huge, but try to figure out where that codepath is.
https://dxr.mozilla.org/mozilla-release/source/ is here for that
- try adding a missing pledge. There are already many (way too many, some might
say), but maybe some are missing for valid usecases. I don't know, i don't
have such usecases. Those WFM.
All that to say, please try to figure out stuff by yourself before sending me
sparse info that wont help at all.
"Right-click, save page as" fails every time here. The main process is
killed with getpw pledge.
Debug information below, but considering the main process already
has things like rpath and exec, I don't think "read-only opening of
files in /etc for the getpwnam(3), getgrnam(3), getgrouplist(3), and
initgroups(3) family of functions" makes things any worse, so OK to add