Red Hat Bugzilla – Bug 445584
ldap_open() call is causing a leaked file descriptor in pam_ldap module
Last modified: 2009-07-14 14:12:52 EDT
Description of problem:
This is causing lots of SELinux avc messages
Need to add a patch like the attached to close the file descriptor on exec.
Not sure if this patch is correct.
Created attachment 304798 [details]
Attempt at closing fd on exec
*** Bug 445564 has been marked as a duplicate of this bug. ***
Dan, opendap is not the same thing as openldap.
All of my cron jobs are also complaining about access to crond_t:tcp_socket and
system_crond_t:fifo_file. Is this related, or is it a different bug?
(In reply to comment #4)
> All of my cron jobs are also complaining about access to crond_t:tcp_socket and
> system_crond_t:fifo_file. Is this related, or is it a different bug?
This is definitely a different bug. Please fill one against cronie (or what your
crond provider is).
Let's wait for their response.
Jan it is not a different bug. The cronnie problem is caused by cronnie calling
openldap in its pam configuration to check the uid, It then execs the app and
the app gets the leaked file descriptor.
Changing version to '9' as part of upcoming Fedora 9 GA.
More information and reason for this action is here:
(In reply to comment #7)
> Jan it is not a different bug. The cronnie problem is caused by cronnie calling
> openldap in its pam configuration to check the uid.
Shouldn't cronie (and pam) release all its resources, e.g. LDAP connection,
before executing the binary? I know, fcntl(s, F_SETFD, FD_CLOEXEC); does the
same automatically, but it prevents an application intentionally pass LDAP
connection to executed binary. That's perfectly valid usage.
Turns out the bug is in nss_ldap, Sorry about the confusion.
So just out of curiosity, how do you diagnose a bug like that? The selinux logs
only reported anonymous sockets with weird integer identifers.
Well actually just seeing this for a very long time.
Usually you see a confined domain trying to access a file that it has nothing to
do with. For example I saw an AVC today that showed consoletype trying to read
dhcp.leases file. I know that consoletype has nothing to do with this file so I
know it is a leaked file descriptor. If you know a confined app does not use
networking and you see it trying to read/write a tcp_socket, you know it is a leak.
*** Bug 447078 has been marked as a duplicate of this bug. ***
*** Bug 443661 has been marked as a duplicate of this bug. ***
This should fixed by libldap if we build against 2.4.10 (which fixed the above-mentioned ITS) or later, and the candidate fixes in the update system should be building against at least that version.
This message is a reminder that Fedora 9 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 9. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as WONTFIX if it remains open with a Fedora
'version' of '9'.
Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version prior to Fedora 9's end of life.
Bug Reporter: Thank you for reporting this issue and we are sorry that
we may not be able to fix it before Fedora 9 is end of life. If you
would still like to see this bug fixed and are able to reproduce it
against a later version of Fedora please change the 'version' of this
bug to the applicable version. If you are unable to change the version,
please add a comment here and someone will do it for you.
Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.
The process we are following is described here:
Fedora 9 changed to end-of-life (EOL) status on 2009-07-10. Fedora 9 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.
If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version.
Thank you for reporting this bug and we are sorry it could not be fixed.