Bug 2152002
| Summary: | SELinux is preventing fprintd from read, write access on the chr_file 050. | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Kamil Páral <kparal> |
| Component: | selinux-policy | Assignee: | Zdenek Pytela <zpytela> |
| Status: | CLOSED EOL | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | unspecified | Docs Contact: | |
| Priority: | medium | ||
| Version: | 37 | CC: | dwalsh, lvrabec, mmalik, omosnacek, pkoncity, vmojzis, zpytela |
| Target Milestone: | --- | Keywords: | Triaged |
| Target Release: | --- | ||
| Hardware: | x86_64 | ||
| OS: | Unspecified | ||
| Whiteboard: | abrt_hash:003fd949f46b2c22a1cb68640fb6a1942febf582ae1b958e570f4df8d4453f4c;VARIANT_ID=workstation; | ||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2023-12-06 11:40:23 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: | |||
This is a dup of bz#2087101. Do you know how to reproduce it or when exactly this happens? Do you have any special settings for fprintd? No, I really don't know how to trigger it. I tried suspending and resuming a few more times, but the denial hasn't repeated, even after reboot. I don't have any custom configuration, I don't use the fingerprint reader, I haven't touched it at all since I installed the OS. Perhaps a race condition of sorts? Perhaps a related problem: https://bugzilla.redhat.com/show_bug.cgi?id=2217872 This message is a reminder that Fedora Linux 37 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora Linux 37 on 2023-12-05. 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 EOL if it remains open with a 'version' of '37'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, change the 'version' to a later Fedora Linux version. Note that the version field may be hidden. Click the "Show advanced fields" button if you do not see it. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora Linux 37 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 Linux, you are encouraged to change the 'version' to a later version prior to this bug being closed. Fedora Linux 37 entered end-of-life (EOL) status on None. Fedora Linux 37 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 Linux please feel free to reopen this bug against that version. Note that the version field may be hidden. Click the "Show advanced fields" button if you do not see the version field. If you are unable to reopen this bug, please file a new report against an active release. Thank you for reporting this bug and we are sorry it could not be fixed. |
Description of problem: I resumed my laptop and logged in, that's all. SELinux is preventing fprintd from read, write access on the chr_file 050. ***** Plugin device (91.4 confidence) suggests **************************** If you want to allow fprintd to have read write access on the 050 chr_file Then you need to change the label on 050 to a type of a similar device. Do # semanage fcontext -a -t SIMILAR_TYPE '050' # restorecon -v '050' ***** Plugin catchall (9.59 confidence) suggests ************************** If you believe that fprintd should be allowed read write access on the 050 chr_file by default. Then you should report this as a bug. You can generate a local policy module to allow this access. Do allow this access for now by executing: # ausearch -c 'fprintd' --raw | audit2allow -M my-fprintd # semodule -X 300 -i my-fprintd.pp Additional Information: Source Context system_u:system_r:fprintd_t:s0 Target Context system_u:object_r:device_t:s0 Target Objects 050 [ chr_file ] Source fprintd Source Path fprintd Port <Unknown> Host (removed) Source RPM Packages Target RPM Packages SELinux Policy RPM selinux-policy-targeted-37.15-1.fc37.noarch Local Policy RPM selinux-policy-targeted-37.15-1.fc37.noarch Selinux Enabled True Policy Type targeted Enforcing Mode Enforcing Host Name (removed) Platform Linux (removed) 6.0.11-300.fc37.x86_64 #1 SMP PREEMPT_DYNAMIC Fri Dec 2 20:47:45 UTC 2022 x86_64 x86_64 Alert Count 1 First Seen 2022-12-08 21:28:35 CET Last Seen 2022-12-08 21:28:35 CET Local ID 961be7c5-316f-42f8-8bc8-854bc8d002fd Raw Audit Messages type=AVC msg=audit(1670531315.15:658): avc: denied { read write } for pid=157925 comm="fprintd" name="050" dev="devtmpfs" ino=2052 scontext=system_u:system_r:fprintd_t:s0 tcontext=system_u:object_r:device_t:s0 tclass=chr_file permissive=0 Hash: fprintd,fprintd_t,device_t,chr_file,read,write Version-Release number of selected component: selinux-policy-targeted-37.15-1.fc37.noarch Additional info: component: selinux-policy reporter: libreport-2.17.4 hashmarkername: setroubleshoot kernel: 6.0.11-300.fc37.x86_64 type: libreport Potential duplicate: bug 2087101