Bryan Steele <brynet@gmail.com> wrote:
> In addition to what Stuart said, irssi is using libperl here for perl
> scripts, which means the irssi unveil will be applied to them. There
> are many uses for perl scripts, and many involve reading arbitrary files
> and there's no way to know that upfront.
Keep in mind unveil is different from pledge.
With pledge, you get killed. Unacceptably inconvenient to have that in
a sustained runtime, when you suddenly trigger a new feature.
With unveil, a hidden file is EACCES or ENOENT therefore a deeply
complicated feature may *subtly misbehave* if it continues operation
in the absence of a control file or something.
I think making this a getopt flag is a disaster.
It was done with chrome *temporarily* during test phases, but sustained
use of flags tied to low-level features is seriously user hostile.
No comments:
Post a Comment