> irssi doesn't exec plugins but load them, so the x flag is useless for
> the scripts directory.
Although irssi scripts aren't themselves exec'd, often they need to
execute things themselves, which could be in $HOME or any of the
standard directories {,/usr,/usr/local}/{bin,sbin} or potentially
elsewhere. Though this gets killed by the pledge anyway even if the
file/directory was unveiled.
(btw plugins are a different thing, they are dlopen'd modules, like
the ones for xmpp/otr/icb - these can be loaded at any time including
after irssi startup, often need to pull in shared libraries from
/usr/local/lib, and often need to do their own initialisation).
> I had lot of feedback about this change not being plugin friendly, but I
> had no real feedback either. I would say that if it kills your plugins,
> just use flag -u or maybe I should make this feature non default and
> activate it with -u?
I don't particularly trust irssi so I have run it as another uid for a
long time, but I never thought of trying to use pledge with it, I don't
see how to do it without some standard actions resulting in the process
failing to live up to its promises and getting killed.
It feels to me that if pledge is added at all, it should be non-default,
some of the scripts that it breaks are very common (the first one I ran
into was the widely used adv_windowlist.pl which wants to exec /bin/stty).
