Securely Launching Processes with a HAM
QNX SDP8.0High Availability Framework Developer's GuideDeveloper
HAM often needs to launch multiple different processes in a system all with different capabilities. Using a secure launcher wedge process allows this to be done securely.
When you run HAM with the -s secure_launcher command line option, all process launches (with the exception of Guardian creation) will be routed through the specified program, with the original program to be launched becoming the first argument to the secure_launcher and the rest of the arguments cascading from there.
For example, if you launch HAM:
ham -s /path/to/launcher
And a process creates a restart action with a call such as:
ham_action_restart(cond, "restart",
"/my/path/to/program -a -b bravo", 0);
Then, HAM will create a resulting command line equivalent to:
/path/to/launcher /my/path/to/program -a -b bravo
Note:
Normally when HAM launches a process (without -s), the UID is forced to that of the process that sent HAM the
process-creation action. If -s is specified, HAM doesn't specify the UID at the process creation time.
A common choice for the secure_launcher is secpollaunch.
Page updated: