diff options
author | Jakub Hrozek <jhrozek@redhat.com> | 2012-11-01 20:18:23 +0100 |
---|---|---|
committer | Jakub Hrozek <jhrozek@redhat.com> | 2012-11-01 20:32:35 +0100 |
commit | 56d894d8354c263b38fbf5c04fec1d25d26ef021 (patch) | |
tree | 42367d18977c4e9edff72b1615151ff358816ed9 | |
parent | 851d0158241fcc0a0796682c43f9e5ca8f2fb673 (diff) | |
download | sssd-56d894d8354c263b38fbf5c04fec1d25d26ef021.tar.gz sssd-56d894d8354c263b38fbf5c04fec1d25d26ef021.tar.xz sssd-56d894d8354c263b38fbf5c04fec1d25d26ef021.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.c | 1 |
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: |