Re: usbhidaction(1) is unvel(2)ed too strictly to run programs.

2022-08-02 Thread Ricardo Mestre
Thanks for testing, it's committed now! On 09:33 Mon 01 Aug , Hector Velasco wrote: > Hi Ricardo: > > I tested the patch and it's working great. The solution seems obvious > now that I see it :). >

Re: usbhidaction(1) is unvel(2)ed too strictly to run programs.

2022-08-01 Thread Hector Velasco
Hi Ricardo: I tested the patch and it's working great. The solution seems obvious now that I see it :). suzaku@burningdawn:~ $ > doas rcctl stop usbhidaction suzaku@burningdawn:~ $ > doas usbhidaction -v -c /etc/usbhidaction.conf -f /dev/uhid2 PARSE:1 Consumer:Volume_Increment, 1, 'sndioctl

Re: usbhidaction(1) is unvel(2)ed too strictly to run programs.

2022-08-01 Thread Ricardo Mestre
ouch, how did I miss the call to execl(3) on docmd()? silly me! OK? Index: usbhidaction.c === RCS file: /cvs/src/usr.bin/usbhidaction/usbhidaction.c,v retrieving revision 1.24 diff -u -p -u -r1.24 usbhidaction.c --- usbhidaction.c

Re: usbhidaction(1) is unvel(2)ed too strictly to run programs.

2022-07-30 Thread Theo de Raadt
I suspect it should unveil("/", "x") It is better than not doing anything.

usbhidaction(1) is unvel(2)ed too strictly to run programs.

2022-07-30 Thread Hector Velasco
Hello Misc. TL;DR: usbhidaction(1) is unveil(2)ed too strictly to run programs. I'm running: kern.version=OpenBSD 7.1 (GENERIC.MP) #3: Sun May 15 10:27:01 MDT 2022 r...@syspatch-71-amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP Complete dmesg at the bottom. I use usbhidaction to