System-wide sandboxing framework - sandbox-app-launcher

Well, that’s fixed and was an interesting exercise. However, I think the wrapper creation inside sal is quite ugly code wise.

Do we really need a dynamically generated wrapper script?

The only dynamic parts are really just A) set -x, bash xtrace for debugging or not which is not super important and could be implemented to only do that if some variable is set and B)

"/path/to/app" "${@}"

i.e. path to binary and command line options. All three variables (debug, app_path and args) could be set in sal. Then we could have a “static” script in a different file. sal would set appropriate variables and the script would serve the same purpose. No more need to have 1 script per application or dynamic wrapper script generation.

What do you think?

1 Like