Bug 987101
Summary: | SELinux is preventing /usr/libexec/fprintd from 'execute' accesses on the file /usr/bin/netstat. | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Rafal Boruc <rafiii48> |
Component: | nss | Assignee: | Elio Maldonado Batiz <emaldona> |
Status: | CLOSED EOL | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | unspecified | Docs Contact: | |
Priority: | unspecified | ||
Version: | 19 | CC: | dominick.grift, dwalsh, emaldona, kdudka, kengert, mgrepl, rrelyea |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | x86_64 | ||
OS: | Unspecified | ||
Whiteboard: | abrt_hash:8f2e7a7bffd040fb30e280de8d52979b9ffe130bd8cb3cb6ae2be82b726cfdbf | ||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2015-02-17 16:18:25 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Rafal Boruc
2013-07-22 17:44:19 UTC
This smells like an libnss problem where it used to exec netstat to generate randomness? Elio, we shouldn't be using netstat anymore. Please make sure that's the case in fedora (maybe an update turned it's use back on?). This would be softoken if it's happening in NSS. bob Bob, NSS still contains the code to run netstat. However, it will be used in a fallback scenario - only if NO (zero) entropy bytes could be obtained using other strategies. http://mxr.mozilla.org/nss/source/lib/freebl/unix_rand.c?mark=816,912-920,946-947#912 While function RNG_SystemInfoForRNG does a lot, only one line is responsible for the decision to skip or use netstat: bytes = RNG_FileUpdate("/dev/urandom", SYSTEM_RNG_SEED_COUNT); If /dev/urandom were unaccessible (can't stat or can't read from), it would result in a zero result and netstat being used. Is that scenario possible? THat is probably it. fprintd attempted to read /dev/urandom and SELinux blocked it. Rafal were you using ldap for your users? > That is probably it. fprintd attempted to read /dev/urandom and
> SELinux blocked it.
Oh we need to be very careful about blocking /dev/urandom. If NSS didn't have any fallback, you would wind up with no entropy in your keys.
bob
So should I just give every domain the ability to read it? Could a bad one drain all of the entropy? This message is a notice that Fedora 19 is now at end of life. Fedora has stopped maintaining and issuing updates for Fedora 19. It is Fedora's policy to close all bug reports from releases that are no longer maintained. Approximately 4 (four) weeks from now this bug will be closed as EOL if it remains open with a Fedora 'version' of '19'. 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. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 19 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, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. 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. Fedora 19 changed to end-of-life (EOL) status on 2015-01-06. Fedora 19 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. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed. |