Yong Sheng Gong
-- Mailing list: https://launchpad.net/~quantum-core Post to : [email protected] Unsubscribe : https://launchpad.net/~quantum-core More help : https://help.launchpad.net/ListHelp
-- Mailing list: https://launchpad.net/~quantum-core Post to : [email protected] Unsubscribe : https://launchpad.net/~quantum-core More help : https://help.launchpad.net/ListHelp
Hi Dan, Garyk,
I think the root cause is:
ip_exec_dnsmasq: DnsmasqFilter, /sbin/ip, root
dnsmasq: DnsmasqFilter, /sbin/dnsmasq, root
dnsmasq_usr: DnsmasqFilter, /usr/sbin/dnsmasq, root
most of our filters do not match the needed command with the command defined in rootwrapper filter files.
For this bug, because DnsmasqFilter does not try to match the wanted dnsmasq with the /sbin/ip defined in dhcp.filters file, we select the first rule.
It seems we will allow the user to specify any command to run in rootwrapper filter files. For example, I can define ip_exec_dnsmasq: DnsmasqFilter, /path/to/anyprogramtorun, root although our quantum is trying to run dnsmasq, but we will match and change to run anyprogramtorun.