> Just because I'm interested, is this with the official Fedora shorewall > package? Isn't this whole "bug" about the "don't put executable code into > /usr/share but /usr/lib[exec] instead" thing discussed recently on this > list? > No idea.
> At least I have changed my rpms for RHEL to use /usr/libexec and I think > the Fedora maintainer did the same (but the package may not have been > released yet). > I agree with your point about lib(exec) - make sense, though getparams is not the only executable in that directory, the only problem, however, seems to be with this file. It is not for the first time either. I remember I had similar problems with ipset executing during shorewall start up (simply because of a wrong context assigned by the SELinux policy) - the bug was fixed, only to appear yet again as soon as FC14 was released. Since then I am maintaining my own (patched) version of the policy to avoid this king of headache on a regular basis. ------------------------------------------------------------------------------ Achieve unprecedented app performance and reliability What every C/C++ and Fortran developer should know. Learn how Intel has extended the reach of its next-generation tools to help boost performance applications - inlcuding clusters. http://p.sf.net/sfu/intel-dev2devmay _______________________________________________ Shorewall-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/shorewall-users
