Dominick Grift wrote: > On Sat, 2011-09-24 at 16:06 +0200, Antonio Trande wrote: > >> This problem is appeared with chrome executable: >> >> SELinux is preventing /opt/google/chrome/chrome from execmod access on the file >> /opt/google/chrome/chrome. >> >> setroubleshoot suggests to change the label on '/opt/google/chrome/chrome' how textrel_shlib_t type or to allow chrome to have execmod access on the chrome file. >> But does not happen always (never to me). >> >> >> Could you give more infos about this behavior ? >> > > I can tell you that this is bad behaviour by chrome. I can tell you that > this issue is known but that this issue is obviously not fixed yet. > http://code.google.com/p/chromium/issues/detail?id=87704 is the bug report about it for Chrome. -- selinux mailing list selinux@xxxxxxxxxxxxxxxxxxxxxxx https://admin.fedoraproject.org/mailman/listinfo/selinux
