Yes, it does.
I extracted 'unveilcommands' function from doas.c and put it into a
standalone program to run it.
It turned out the result was the same as in doas command. When I disable
unveil, then it works fine.
niedz., 20 sty 2019 o 22:31 Ted Unangst <t...@tedunangst.com> napisał(a):
> Dariusz Sendkowski wrote:
> > I investigated the problem a little more and found, that when there is a
> > non-existent directory entry in my PATH, the problem occurs. If all of
> the
> > directories from my PATH exist, then it works fine.
>
> To help isolate the problem, if you disable unveil, does it work?
>
>
> Index: doas.c
> ===================================================================
> RCS file: /cvs/src/usr.bin/doas/doas.c,v
> retrieving revision 1.74
> diff -u -p -r1.74 doas.c
> --- doas.c 17 Jan 2019 05:35:35 -0000 1.74
> +++ doas.c 20 Jan 2019 21:30:55 -0000
> @@ -409,8 +409,6 @@ main(int argc, char **argv)
> if (setenv("PATH", safepath, 1) == -1)
> err(1, "failed to set PATH '%s'", safepath);
> }
> - if (unveilcommands(getenv("PATH"), cmd) == 0)
> - goto fail;
>
> if (pledge("stdio rpath getpw exec id", NULL) == -1)
> err(1, "pledge");
>
