Kevin Chadwick <m8il1i...@gmail.com> wrote: > On 1/21/21 2:58 PM, Kevin Chadwick wrote: > >>> 840 beep CALL pledge(0xc0000f4000,0xc0000ae384) > >>> 840 beep STRU promise="stdio rpath wpath cpath dpath tmppath inet > >>> mcast fattr chown flock unix d\ > >>> ns getpw sendfd recvfd tape tty proc exec prot_exec settime ps vminfo > >>> id pf route wroute audio v\ > >>> ideo bpf unveil error" > >>> 840 beep STRU execpromise="" > >>> 840 beep RET pledge 0 > >>> > >> Whatever you are trying to do is ridiculous. > > Absolutely. In fact the program itself is pointless to pledge, playing a > > beep to > > the speaker. However, I had pledge disabled in my binaries due to the > > syscall 74 > > Go bug that was fixed. This is just testing with the most permissable > > settings. > > Perhaps that in itself could cause an issue. > > Is execpromise="" equivalent to passing null in c as a nil string in Go is > initialised to "" (function sig = string) > > Perhaps I should ktrace the whacky full promise passsed as execpromise too?
I wonder what happens if I point this thing at my foot.
