after a report from another user, i had a deeper look and now i wonder if it's related to sandboxing on OpenBSD. as of 118 the rdd process only has read/write access to /tmp (for shm temporary files), and very few syscalls per our pledge sandboxing policy. adding `/usr/local/lib` seems to changes thing as in now the rdd process apparently 'supports' video/avc ``` [Child 92806: Main Thread]: D/PlatformDecoderModule Sandbox RDD decoder supports requested type video/avc ``` but to have mp4 decoding 'working' i also need to add `prot_exec` to pledge syscall classes, which is a rather large hole for a process supposed to do remote data decoding. so, what changed in 119 regarding video decoding and subprocesses, between utility and rdd ?
Bug 1856301 Comment 4 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
after a report from another user, i had a deeper look and now i wonder if it's related to sandboxing on OpenBSD. as of 118 the rdd process only has read/write access to /tmp (for shm temporary files), and very few syscalls per our pledge sandboxing policy. adding `/usr/local/lib` seems to changes thing as in now the rdd process apparently 'supports' video/avc ``` [Child 92806: Main Thread]: D/PlatformDecoderModule Sandbox RDD decoder supports requested type video/avc ``` but to have mp4 decoding 'working' i also need to add `prot_exec` to pledge syscall classes, which is an annoyance (allows PROT_EXEC on mmap'ed regions) for a process supposed to do remote data decoding. so, what changed in 119 regarding video decoding and subprocesses, between utility and rdd ?