Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.
Bug 1001703
Summary: | SELinux is preventing /usr/libexec/sssd/krb5_child from 'write' accesses on the key . | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Stephen Gallagher <sgallagh> |
Component: | selinux-policy | Assignee: | Lukas Vrabec <lvrabec> |
Status: | CLOSED EOL | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | unspecified | Docs Contact: | |
Priority: | unspecified | ||
Version: | 19 | CC: | abokovoy, amessina, dominick.grift, dwalsh, lvrabec, mgrepl, plautrba, rmainz, ssorce |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | x86_64 | ||
OS: | Unspecified | ||
Whiteboard: | abrt_hash:0e273eb3a58d6ccbe7b82f2689866cf5c60d5afc4e40c6541459b863939bf603 | ||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2015-02-18 11:25:20 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: | |||
Bug Depends On: | 1063827 | ||
Bug Blocks: |
Description
Stephen Gallagher
2013-08-27 14:38:16 UTC
Note we will need access also from rpc.gssd when nfs with sec=krb5 is configured. Openssh may also need to create/access the keyring to store forwarded credentials or create a new ccache when pam_krb5 is used. I needed the following when "default_ccache_name = KEYRING:persistent:%{uid}" is added to /etc/krb5.conf, using selinux-policy-3.12.1-119.fc20. module fixkernelkeyring 1.0; require { type sssd_t; type gssd_t; class key { write setattr read view }; } #============= gssd_t ============== allow gssd_t sssd_t:key { read write setattr }; #============= sssd_t ============== allow sssd_t gssd_t:key { read write view }; For F20 I have created bug 1063827. These are more mislabeled keys. We do not label keys correctly. I am pretty sure the keys here are owned by an unconfined_t process. Not sshd_t or gssd_t. But they are getting labeled incorrectly. sssd_t should be calling setkeycreatecon(USERTYPE) before creating the key, to get it to make some sense. ALso I have no idea why there is a gssd_t key? Is this also a key owned by a user? Or does gssd create its own keyring? I supposed that this happens when rpc.gssd acquires a ticket on behalf of the user. When a iuser walks an NFS mountpoint rpc.gssd will lookup the credentials and if not available will acquire a ticket for the remote NFS server. This ticket is stored in a key and linked to the user keyring. Does the keyring end up with the equivalent of the UID of the user? If so we really need to get the keyring to be labeled as the users label keyring. unconfined_u:unconfined_r:unconfined_t:s0 If the user process was running, it could just do a getpidcon or getpeercon of the user process and then a setkeycreatecon() before creating the keyring. 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. |