summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorJakub Hrozek <jhrozek@redhat.com>2012-11-01 20:18:23 +0100
committerJakub Hrozek <jhrozek@redhat.com>2012-11-05 00:14:06 +0100
commite9d8563c0c715dde27325583a1e3c8cf234c6357 (patch)
tree01194197c6ed2bce033f0910a42ff5530178ccb8
parent09a45954fe790a623099e813bfc2a7cf6b0b57c7 (diff)
downloadsssd-e9d8563c0c715dde27325583a1e3c8cf234c6357.tar.gz
sssd-e9d8563c0c715dde27325583a1e3c8cf234c6357.tar.xz
sssd-e9d8563c0c715dde27325583a1e3c8cf234c6357.zip
PAM: Do not leak fd after SELinux context file is written
https://fedorahosted.org/sssd/ticket/1619 We don't close the fd when we write the selinux login file in the pam responder. This results in a fd leak.
-rw-r--r--src/responder/pam/pamsrv_cmd.c1
1 files changed, 1 insertions, 0 deletions
diff --git a/src/responder/pam/pamsrv_cmd.c b/src/responder/pam/pamsrv_cmd.c
index 2b20544d1..bb0d8db38 100644
--- a/src/responder/pam/pamsrv_cmd.c
+++ b/src/responder/pam/pamsrv_cmd.c
@@ -443,6 +443,7 @@ static errno_t write_selinux_login_file(const char *username, char *string)
} else {
ret = EOK;
}
+ close(fd);
fd = -1;
done: