setkeycreatecon is not needed. Users should inherited key context if it was already...

Signed-off-by: Marcela Mašláňová <mmaslano@redhat.com>

diff --git a/src/security.c b/src/security.c
index 34c940e4d3242bc0b68ee19e5c0c3336e65e4b76..83c7d7e978add09d92da1e9412b4bd0a6cfb8c42 100644 (file)
--- a/src/security.c
+++ b/src/security.c
@@ -424,7 +424,7 @@ static int cron_change_selinux_range(user * u, security_context_t ucontext) {
                }
        }
 
-       if (setexeccon(ucontext) < 0 || setkeycreatecon(ucontext) < 0) {
+       if (setexeccon(ucontext) < 0) {
                if (security_getenforce() > 0) {
                        if (asprintf
                                (&msg, "Could not set exec or keycreate context to %s for user",
@@ -437,7 +437,7 @@ static int cron_change_selinux_range(user * u, security_context_t ucontext) {
                else {
                        if (asprintf
                                (&msg,
-                                       "Could not set exec or keycreate context to %s for user,"
+                                       "Could not set exec context to %s for user,"
                                        " but SELinux in permissive mode, continuing",
                                        (char *) ucontext) >= 0) {
                                log_it(u->name, getpid(), "WARNING", msg, 0);