Bug 987179
Summary: | SELinux is preventing /usr/libexec/kde4/kdm_config from using the 'net_admin' capabilities. | ||||||
---|---|---|---|---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Juan Orti <jorti> | ||||
Component: | kde-workspace | Assignee: | Than Ngo <than> | ||||
Status: | CLOSED EOL | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||
Severity: | unspecified | Docs Contact: | |||||
Priority: | unspecified | ||||||
Version: | 19 | CC: | dominick.grift, dvratil, dwalsh, jgrulich, jorti, jreznik, kevin, ltinkl, mbriza, mgrepl, rdieter, rnovacek, than | ||||
Target Milestone: | --- | ||||||
Target Release: | --- | ||||||
Hardware: | x86_64 | ||||||
OS: | Unspecified | ||||||
Whiteboard: | abrt_hash:e34284a47c60254b014fc195d12762ceaf69c8975471bf764f913f546cbaf000 | ||||||
Fixed In Version: | Doc Type: | Bug Fix | |||||
Doc Text: | Story Points: | --- | |||||
Clone Of: | Environment: | ||||||
Last Closed: | 2015-02-17 16:18:45 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: | |||||||
Attachments: |
|
Description
Juan Orti
2013-07-22 21:26:03 UTC
Just interested why net_admin is needed by kdm_config. CAP_NET_ADMIN Perform various network-related operations: * interface configuration; * administration of IP firewall, masquerading, and accounting; * modify routing tables; * bind to any address for transparent proxying; * set type-of-service (TOS) * clear driver statistics; * set promiscuous mode; * enabling multicasting; * use setsockopt(2) to set the following socket options: SO_DEBUG, SO_MARK, SO_PRIORITY (for a pri‐ ority outside the range 0 to 6), SO_RCVBUFFORCE, and SO_SNDBUFFORCE. Good question, reporter, can you describe which kdm options you were configuring when this occurred? (Offhand, I'd say kdm_config probably does not require this access, but that doesn't explain why the denial happened in the first place) Created attachment 778109 [details]
/etc/kde/kdm/kdmrc
I don't remember to touch anything in the kdm config since upgrading to F19, when I only changed the theme to Schrödinger's Cat.
I also get surprised when I saw this error, because I don't do anything special with kdm, only logon and shutdown.
kdm_config is just a parser of the kdmrc file. I don't think it does anything else than sending parsed values over a socket to the kdm daemon. I'll take a look if it's doing anything from the actions listed by Miroslav. 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. |