[Bug 733001] pluginscanner: Selinux enhanced file rights not handled correctly

[GStreamer (bugzilla.gnome.org)]

https://bugzilla.gnome.org/show_bug.cgi?id=733001
  GStreamer | gstreamer (core) | git

--- Comment #9 from kasberger at heidenhain.de 2014-10-29 08:34:44 UTC ---
Generally here is a misunderstanding of SELinux concepts and how it provides
access and execution rights. It is widespreeded on all distributions. If you
want to know more then please read this article
https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/4/html/SELinux_Guide/index.html

But introducing the SELinux machinery for a one special case could be a little
bit too much overhead. I have implemented this my code and it is working. 

Even if this directory is simply execute protected I run into the same issue.
The question is : should a plugin be blacklist  permanently because at the time
of the first read it I was not accessible/executeable ? 
IMO if we have a cache then it should intelligent enough to handle this.
Otherwise the user has to manipulate its system manually. And this is never ok.

If I do not get any reply I will it rest in peace


in gst_registry.c : gst_registry_scan_path_level(

if (g_module_supported () != FALSE) {
    flags = G_MODULE_BIND_LOCAL | G_MODULE_BIND_LAZY;
        module = g_module_open (filename, flags);
        if (module == NULL) {
          GST_TRACE_OBJECT (context->registry, "%s file is secured by SELinux,
ignoring",filename);
          g_free (filename);
          continue;
        }
        g_module_close(module);
    }

-- 
Configure bugmail: https://bugzilla.gnome.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
You are the assignee for the bug.