As far as I understand these messages, apparmor prohibits nscd to mmap these files with PROT_EXEC. But I have looked at the nscd sourcecode, and PROT_EXEC is not used anywhere, it just mmaps these files in PROT_READ | PROT_WRITE mode…
Any ideas what might be going on here?
(This all happens on OpenSUSE 11.0 / 32bit with current updates.)
As far as I understand you, you are basically telling me to configure apparmor to ignore these access violations and allow nscd to mmap these files with PROT_EXEC.
To me it makes no sense to use PROT_EXEC on these files, and nscd does not seem to even try to do that! I’ve looked at the source code and it only mmaps them in PROT_READ|PROT_WRITE mode.
I will set the nscd profile to complain for now though, to see if that has an effect on another issue I have with vpnclient.
I would still really like to know how these reports can even occurr in the first place.