Solved. As these things usually are, it was simple in hindsight.
# ls -ld /
drwxr-x--- 13 root wheel 512 Mar 7 15:09 /
I was looking at a ktrace trying to run the "doas -u im3 id -p" and saw
it trying all the possible paths, and that gave me the hunch to check
permissions on the root.
14751 doas CALL execve(0x7f7ffffcc870,0x7f7ffffcdfd0,0x1c5559226680)
14751 doas NAMI "/sbin/id"
14751 doas RET execve -1 errno 13 Permission denied
14751 doas CALL execve(0x7f7ffffcc870,0x7f7ffffcdfd0,0x1c5559226680)
14751 doas NAMI "/usr/sbin/id"
14751 doas RET execve -1 errno 13 Permission denied
14751 doas CALL execve(0x7f7ffffcc870,0x7f7ffffcdfd0,0x1c5559226680)
14751 doas NAMI "/bin/id"
14751 doas RET execve -1 errno 13 Permission denied
14751 doas CALL execve(0x7f7ffffcc870,0x7f7ffffcdfd0,0x1c5559226680)
14751 doas NAMI "/usr/bin/id"
14751 doas RET execve -1 errno 13 Permission denied
14751 doas CALL execve(0x7f7ffffcc870,0x7f7ffffcdfd0,0x1c5559226680)
14751 doas NAMI "/usr/X11R6/bin/id"
14751 doas RET execve -1 errno 13 Permission denied
14751 doas CALL execve(0x7f7ffffcc870,0x7f7ffffcdfd0,0x1c5559226680)
14751 doas NAMI "/usr/local/sbin/id"
14751 doas RET execve -1 errno 13 Permission denied
14751 doas CALL execve(0x7f7ffffcc870,0x7f7ffffcdfd0,0x1c5559226680)
14751 doas NAMI "/usr/local/bin/id"
14751 doas RET execve -1 errno 13 Permission denied
I have an idea how that happened, I had changed my default umask in
/etc/login.conf from 022 to 027, so that new files would get created
without any "other" permissions.
Something must have "recreated" the / directory? Thus wiping the r-x
permission for "other" users. The timestamp shown on / roughly
corresponds (from memory) to my running of the openup command.
So, changing default umask to 027 is a "bad" idea? Or is this something
that shouldn't really be happening?
Allan