I'm not sure where I'm going wrong here, but I've been giving doas(1)
a whirl and ran into something that's left be a bit puzzled.
I have some scripts in ~/bin, and my user account has PATH set
as desired. I can run things out of that dir as expected without
invoking doas, but attempting to prefix the command with doas in the
same manner I previously did with sudo doesn't seem to work.
Without doas:
$ ls -lA ~/bin
total 8
-rwxr-xr-x 1 avj avj 22 Aug 26 11:31 testes
$ cat ~/bin/testes
#!/bin/sh
echo testes, testes, 123
$ echo $PATH
/home/avj/bin:/bin:/sbin:/usr/bin:/usr/sbin
$ which testes
/home/avj/bin/testes
$ testes
testes, testes, 123
With doas:
$ cat /etc/doas.conf
permit nopass keepenv { PATH PS1 SSH_AUTH_SOCK } :wheel
$ id
uid=1001(avj) gid=1001(avj) groups=1001(avj), 0(wheel)
$ doas which testes
/home/avj/bin/testes
$ doas testes
doas: testes: command not found
I also tried just a simple "permit nopass :wheel" in doas.conf and
the result was the same. I also tried tossing that path into root's
.profile just for fun, but still no dice.
kern.version:
OpenBSD 5.8-current (GENERIC.MP) #1299: Mon Aug 31 05:32:01 MDT 2015
dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP
Which fundamental concept am I missing here?
Thanks,
--avj
