>On Tue, Oct 16, 2012 at 7:51 PM, Stephen Smalley <sds@xxxxxxxxxxxxx> wrote: >> >> @ Stephen, do you know how mandatory for SELinux is to have the whole argv >> struct? Is it just because of rpm_execcon() API or? > > It is because presently rpm_execcon() performs the exec call. If the > exec call is handled by the caller, then we only need the executable > path. Likewise with envp; we do not need it if the caller performs the > exec. We would just move the remaining logic to set up the exec context > from libselinux rpm_execcon() into the rpm selinux plugin code; as rpm > is the only user of it, there is no real reason for it to live in > libselinux vs being part of an rpm plugin. Good, thank you for clarifying this! This is what I was hoping can be the case. I will change the hook to have only path passed for now. Best Regards, Elena. -- This message was distributed to subscribers of the selinux mailing list. If you no longer wish to subscribe, send mail to majordomo@xxxxxxxxxxxxx with the words "unsubscribe selinux" without quotes as the message.
