You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
cloudabi-run (running in the Posix world) can't set all Capsicum rights properly on the file descriptors it opens. It'll have to ask cloudabi-reexec (running in the CloudABI world) to disable some rights on the file descriptors it gets, if that was originally specified in the Yaml file.
Right now, cloudabi-exec takes an argdata sequence of two items: The file descriptor of the executable to run, and the argdata to provide to that program.
We could simply add an (optional) third item to that sequence, which describes what rights the file descriptors should have. This could be a map, mapping file descriptors to a 2-tuple (sequence) containing (fs_rights_base, fs_rights_inheriting), both as integers.
The text was updated successfully, but these errors were encountered:
Maybe, while we're at it, we should consider replacing the sequence by a full map with string keys. Fair chance we want to add even more features over time.
cloudabi-run
(running in the Posix world) can't set all Capsicum rights properly on the file descriptors it opens. It'll have to askcloudabi-reexec
(running in the CloudABI world) to disable some rights on the file descriptors it gets, if that was originally specified in the Yaml file.Right now,
cloudabi-exec
takes an argdata sequence of two items: The file descriptor of the executable to run, and the argdata to provide to that program.We could simply add an (optional) third item to that sequence, which describes what rights the file descriptors should have. This could be a map, mapping file descriptors to a 2-tuple (sequence) containing
(fs_rights_base, fs_rights_inheriting)
, both as integers.The text was updated successfully, but these errors were encountered: