> Some examples that will need consideration for unveil(2): > - mount(2) > - unmount(2) > - quotactl(2) > - chroot(2) > - getfh(2) > - acct(2) > - coredump() > - loadfirmware() - I think ifconfig(1) could make the kernel loading a > firmware for some network card > > so having ni_unveil separated from ni_pledge could be good to be able to > manage these namei() calls in unveiled programs. >
And yes, I am in violent agreement with this :) this lets us have a cleaner separation and unveil things that aren't pledgeable.
