Bug 1648701
| Summary: | SELinux is preventing mandb from 'search' accesses on the directory /var/lib/snapd. | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Mai Ling <mailinglists35> |
| Component: | snapd | Assignee: | Zygmunt Krynicki <me> |
| Status: | CLOSED EOL | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | unspecified | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 33 | CC: | achinovnikov, akirosspower, allan.poulsen, anatoli, antonio_fortes, artemio.silva, atbakken, atenrok, a.wellbrock, baqueiro.jorge, ctompkins, danie.dejager, dani, dasgeekchannel, dirk, dwalsh, gburlats, helpdextron, hlopes, hx, jani.heinonen, jayabharat, jonathonpoppleton, juanramonls, kaiser3000_20, kevinfreeman1101, lordfoom, lucas, lukas.mr, lvrabec, matbos, mcostabox, me, mstuff, ndbecker2, ngompa13, noodny, offers, oleg-sz, pbabinca, peterthecoder, pgn674, plautrba, pnickerson, robertogv64, rocketraman, sajjaddns, sayantanguharay, sb, shellzsh42, s.kieske, stephenfin, sthyx, stiece, surfernsk, svpastime, taitos.fci, taslim, tedroche, thomas, tim.dillenberger, tonay, truls, warren98103, wdejan, yyasar71, zpuszko |
| Target Milestone: | --- | Keywords: | Reopened |
| Target Release: | --- | ||
| Hardware: | x86_64 | ||
| OS: | Unspecified | ||
| Whiteboard: | abrt_hash:8fb1976f00047197afba3614d5ec7b0a8948a38631d1ee2f4850dc6f7aedc01b;VARIANT_ID=workstation; | ||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2021-11-30 16:36:32 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 of problem: If I use dnf to install a package, selinux warns me about this error, specifically, when running some scriptlets after the installations. I can reproduce this problem by installing a package with dnf. Version-Release number of selected component: selinux-policy-3.14.2-42.fc29.noarch Additional info: reporter: libreport-2.9.6 hashmarkername: setroubleshoot kernel: 4.19.4-300.fc29.x86_64 type: libreport Description of problem: i was trying to run an electron wrapper app, so installed GConf2 and then tried to run the app. Honestly I don't know what i am doing. Version-Release number of selected component: selinux-policy-3.14.2-42.fc29.noarch Additional info: reporter: libreport-2.9.6 hashmarkername: setroubleshoot kernel: 4.19.5-300.fc29.x86_64 type: libreport Description of problem: sudo dnf distro-sync --setopt=deltarpm=0 did this right after upgrade to F29, and Selinux triggered the error Additional info: reporter: libreport-2.9.7 hashmarkername: setroubleshoot kernel: 4.19.10-300.fc29.x86_64 type: libreport Description of problem: rebooted Version-Release number of selected component: selinux-policy-3.14.2-47.fc29.noarch Additional info: reporter: libreport-2.9.7 hashmarkername: setroubleshoot kernel: 4.19.15-300.fc29.x86_64 type: libreport Description of problem: Install or remove rpm pkg. Version-Release number of selected component: selinux-policy-3.14.2-47.fc29.noarch Additional info: reporter: libreport-2.9.7 hashmarkername: setroubleshoot kernel: 4.20.3-200.fc29.x86_64 type: libreport Description of problem: Problem happened few minutes after I updated my OS Version-Release number of selected component: selinux-policy-3.14.2-47.fc29.noarch Additional info: reporter: libreport-2.9.7 hashmarkername: setroubleshoot kernel: 4.20.4-200.fc29.x86_64 type: libreport Description of problem: Just booted my laptop Version-Release number of selected component: selinux-policy-3.14.2-47.fc29.noarch Additional info: reporter: libreport-2.9.7 hashmarkername: setroubleshoot kernel: 4.20.4-200.fc29.x86_64 type: libreport *** Bug 1673682 has been marked as a duplicate of this bug. *** Description of problem: Background process. Seems to be the mandb indexer trying to scan snapd Version-Release number of selected component: selinux-policy-3.14.2-47.fc29.noarch Additional info: reporter: libreport-2.9.7 hashmarkername: setroubleshoot kernel: 4.20.6-200.fc29.x86_64 type: libreport Description of problem: Description of problem: 1. sudo dnf install snapd 2. sudo systemctl enable --now snapd.socket 3. sudo ln -s /var/lib/snapd/snap /snap SELinux errors all over the place. Version-Release number of selected component: selinux-policy-3.14.2-48.fc29.noarch Additional info: reporter: libreport-2.10.0 hashmarkername: setroubleshoot kernel: 4.20.8-200.fc29.x86_64 type: libreport *** Bug 1687816 has been marked as a duplicate of this bug. *** *** Bug 1689996 has been marked as a duplicate of this bug. *** Description of problem: NO puedo instalar Android Studio y Eclipse desde Snap Version-Release number of selected component: selinux-policy-3.14.2-53.fc29.noarch Additional info: reporter: libreport-2.10.0 hashmarkername: setroubleshoot kernel: 5.0.5-200.fc29.x86_64 type: libreport *** Bug 1700019 has been marked as a duplicate of this bug. *** Description of problem: Installed snapd $ sudo dnf install snapd $ systemctl enable snapd $ systemctl start snapd After running this commands SE Linux continues to report bugs related to snaps. Version-Release number of selected component: selinux-policy-3.14.3-32.fc30.noarch Additional info: reporter: libreport-2.10.0 hashmarkername: setroubleshoot kernel: 5.0.10-300.fc30.x86_64 type: libreport Description of problem: Installed snapd and error started appearing. Version-Release number of selected component: selinux-policy-3.14.3-29.fc30.noarch Additional info: reporter: libreport-2.10.0 hashmarkername: setroubleshoot kernel: 5.0.9-301.fc30.x86_64 type: libreport Description of problem: I think this SELinux alert appears in my notification tray whenever I dnf install an update. It might also happen at system startup. Version-Release number of selected component: selinux-policy-3.14.3-35.fc30.noarch Additional info: reporter: libreport-2.10.0 hashmarkername: setroubleshoot kernel: 5.0.16-300.fc30.x86_64 type: libreport Description of problem: suite a la mise jour du kernal en .17 au demarrage de la session. Version-Release number of selected component: selinux-policy-3.14.3-37.fc30.noarch Additional info: reporter: libreport-2.10.0 hashmarkername: setroubleshoot kernel: 5.0.17-300.fc30.x86_64 type: libreport Description of problem: Automatic update Version-Release number of selected component: selinux-policy-3.14.3-37.fc30.noarch Additional info: reporter: libreport-2.10.0 hashmarkername: setroubleshoot kernel: 5.0.17-300.fc30.x86_64 type: libreport Description of problem: SELinux alert appears while booting my laptop running Fedora 30 (Workstation Edition), Kernel: Linux 5.1.7-300.fc30.x86_64. Version-Release number of selected component: selinux-policy-3.14.3-37.fc30.noarch Additional info: reporter: libreport-2.10.0 hashmarkername: setroubleshoot kernel: 5.1.7-300.fc30.x86_64 type: libreport Description of problem: This happens after a dnf update completes. The snapd package was removed sometime before I started to get these alerts. Version-Release number of selected component: selinux-policy-3.14.2-59.fc29.noarch Additional info: reporter: libreport-2.10.0 hashmarkername: setroubleshoot kernel: 5.0.19-200.fc29.x86_64 type: libreport Description of problem: I don't know... (While browsing for new Wallpapers.) Version-Release number of selected component: selinux-policy-3.14.3-39.fc30.noarch Additional info: reporter: libreport-2.10.0 hashmarkername: setroubleshoot kernel: 5.1.12-300.fc30.x86_64 type: libreport Description of problem: installed snapd and then caprine and spotify. Error came after Spotify had installed and running Version-Release number of selected component: selinux-policy-3.14.3-39.fc30.noarch Additional info: reporter: libreport-2.10.0 hashmarkername: setroubleshoot kernel: 5.1.12-300.fc30.x86_64 type: libreport Description of problem: This might be triggered when gnome-software is run Version-Release number of selected component: selinux-policy-3.14.3-39.fc30.noarch Additional info: reporter: libreport-2.10.0 hashmarkername: setroubleshoot kernel: 5.1.12-300.fc30.x86_64 type: libreport Description of problem: Installed snap, got SELinux Alerts Version-Release number of selected component: selinux-policy-3.14.3-39.fc30.noarch Additional info: reporter: libreport-2.10.0 hashmarkername: setroubleshoot kernel: 5.1.15-300.fc30.x86_64 type: libreport Description of problem: Bug happened during a dnf update. Version-Release number of selected component: selinux-policy-3.14.3-39.fc30.noarch Additional info: reporter: libreport-2.10.1 hashmarkername: setroubleshoot kernel: 5.0.11-200.fc29.x86_64 type: libreport Description of problem: I did `dnf update`. After update was completed, this occured. Version-Release number of selected component: selinux-policy-3.14.3-39.fc30.noarch Additional info: reporter: libreport-2.10.1 hashmarkername: setroubleshoot kernel: 5.1.16-300.fc30.x86_64 type: libreport Description of problem: I Installed Snap via yum Then I installed Spotify I then restarted XFCE. When I updated DNF, I got the SE Linux alert. Version-Release number of selected component: selinux-policy-3.14.3-39.fc30.noarch Additional info: reporter: libreport-2.10.1 hashmarkername: setroubleshoot kernel: 5.1.16-300.fc30.x86_64 type: libreport Description of problem: I installed Snapd on my fedora os and SELinux got a bug I want it to get access to Mandb. Version-Release number of selected component: selinux-policy-3.14.3-40.fc30.noarch Additional info: reporter: libreport-2.10.1 hashmarkername: setroubleshoot kernel: 5.1.17-300.fc30.x86_64 type: libreport Description of problem: After installing snapd Version-Release number of selected component: selinux-policy-3.14.3-41.fc30.noarch Additional info: reporter: libreport-2.10.1 hashmarkername: setroubleshoot kernel: 5.1.18-300.fc30.x86_64 type: libreport Description of problem: Every time there is an update for a week or two now. Version-Release number of selected component: selinux-policy-3.14.3-42.fc30.noarch Additional info: reporter: libreport-2.10.1 hashmarkername: setroubleshoot kernel: 5.1.19-300.fc30.x86_64 type: libreport Description of problem: updated Version-Release number of selected component: selinux-policy-3.14.3-42.fc30.noarch Additional info: reporter: libreport-2.10.1 hashmarkername: setroubleshoot kernel: 5.1.19-300.fc30.x86_64 type: libreport Description of problem: As per instructions on https://snapcraft.io/docs/installing-snap-on-fedora 1. sudo dnf install snapd 2. sudo ln -s /var/lib/snapd/snap /snap 3. reboot Version-Release number of selected component: selinux-policy-3.14.3-42.fc30.noarch Additional info: reporter: libreport-2.10.1 hashmarkername: setroubleshoot kernel: 5.1.20-300.fc30.x86_64 type: libreport Description of problem: Seems to happen with dnf operations. I have snapd installed and running. Version-Release number of selected component: selinux-policy-3.14.2-60.fc29.noarch Additional info: reporter: libreport-2.10.1 hashmarkername: setroubleshoot kernel: 5.1.18-200.fc29.x86_64 type: libreport Anybody to update the version to Fedora 30? Description of problem: Attempting to install Dropbox in Fedora MATE 30. Version-Release number of selected component: selinux-policy-3.14.3-43.fc30.noarch Additional info: reporter: libreport-2.10.1 hashmarkername: setroubleshoot kernel: 5.2.8-200.fc30.x86_64 type: libreport Description of problem: During routine dnf update 21-Aug-2019 Version-Release number of selected component: selinux-policy-3.14.2-64.fc29.noarch Additional info: reporter: libreport-2.10.1 hashmarkername: setroubleshoot kernel: 5.1.21-200.fc29.x86_64 type: libreport Description of problem: Installed npm / nodejs via Visual Studio Code terminal Version-Release number of selected component: selinux-policy-3.14.3-43.fc30.noarch Additional info: reporter: libreport-2.10.1 hashmarkername: setroubleshoot kernel: 5.2.8-200.fc30.x86_64 type: libreport Description of problem: Just updating using dnfdragora Version-Release number of selected component: selinux-policy-3.14.3-43.fc30.noarch Additional info: reporter: libreport-2.10.1 hashmarkername: setroubleshoot kernel: 5.2.9-200.fc30.x86_64 type: libreport Description of problem: This isue appears! Version-Release number of selected component: selinux-policy-3.14.3-43.fc30.noarch Additional info: reporter: libreport-2.10.1 hashmarkername: setroubleshoot kernel: 5.2.9-200.fc30.x86_64 type: libreport This message is a reminder that Fedora 29 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora 29 on 2019-11-26. 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 Fedora 'version' of '29'. 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 29 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 29 changed to end-of-life (EOL) status on 2019-11-26. Fedora 29 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. This is still an issue on Fedora 33. I have relablled the filesystem. No impact, sadly. This message is a reminder that Fedora 33 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora 33 on 2021-11-30. 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 Fedora 'version' of '33'. 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 33 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 33 changed to end-of-life (EOL) status on 2021-11-30. Fedora 33 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. |
Description of problem: SELinux is preventing mandb from 'search' accesses on the directory /var/lib/snapd. ***** Plugin catchall (100. confidence) suggests ************************** If you believe that mandb should be allowed search access on the snapd directory 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 'mandb' --raw | audit2allow -M my-mandb # semodule -X 300 -i my-mandb.pp Additional Information: Source Context system_u:system_r:mandb_t:s0 Target Context system_u:object_r:snappy_var_lib_t:s0 Target Objects /var/lib/snapd [ dir ] Source mandb Source Path mandb Port <Unknown> Host (removed) Source RPM Packages Target RPM Packages snapd-2.36-1.fc29.x86_64 Policy RPM selinux-policy-3.14.2-42.fc29.noarch Selinux Enabled True Policy Type targeted Enforcing Mode Enforcing Host Name (removed) Platform Linux (removed) 4.20.0-0.rc1.git1.2.fc30.x86_64 #1 SMP Tue Nov 6 22:29:17 UTC 2018 x86_64 x86_64 Alert Count 4 First Seen 2018-11-11 21:56:29 EET Last Seen 2018-11-11 21:56:29 EET Local ID 7b8b78bf-f8a3-4b27-b497-7b336e9899ce Raw Audit Messages type=AVC msg=audit(1541966189.890:391): avc: denied { search } for pid=6859 comm="mandb" name="snapd" dev="sda3" ino=95339 scontext=system_u:system_r:mandb_t:s0 tcontext=system_u:object_r:snappy_var_lib_t:s0 tclass=dir permissive=0 Hash: mandb,mandb_t,snappy_var_lib_t,dir,search Version-Release number of selected component: selinux-policy-3.14.2-42.fc29.noarch Additional info: component: selinux-policy reporter: libreport-2.9.6 hashmarkername: setroubleshoot kernel: 4.20.0-0.rc1.git1.2.fc30.x86_64 type: libreport