Description of problem: When I try to restore SELinux contexts on /var/lib/git catalog, .ssh subdirectory is labeled as git_sys_content_t instead of labeling as ssh_home_t. It breaks access to .ssh/authorized_keys and because of that to git repositories. # semanage fcontext -l | grep "/var/lib/git" /var/lib/git(/.*)? all files system_u:object_r:git_sys_content_t:s0 ... # semanage fcontext -l | grep "\.ssh" ... /var/lib/[^/]+/\.ssh(/.*)? all files system_u:object_r:ssh_home_t:s0 ... # sestatus SELinux status: enabled SELinuxfs mount: /sys/fs/selinux SELinux root directory: /etc/selinux Loaded policy name: targeted Current mode: enforcing Mode from config file: enforcing Policy MLS status: enabled Policy deny_unknown status: allowed Memory protection checking: actual (secure) Max kernel policy version: 33 # uname -r 5.11.7-200.fc33.x86_64 Version-Release number of selected component (if applicable): # rpm -q selinux-policy selinux-policy-targeted selinux-policy-3.14.6-35.fc33.noarch selinux-policy-targeted-3.14.6-35.fc33.noarch How reproducible: always Steps to Reproduce: 1. mkdir /var/lib/git 2. mkdir /var/lib/git/.ssh 3. restorecon -rv /var/lib/git Actual results: # restorecon -rv /var/lib/git Relabeled /var/lib/git from unconfined_u:object_r:var_lib_t:s0 to unconfined_u:object_r:git_sys_content_t:s0 Relabeled /var/lib/git/.ssh from unconfined_u:object_r:ssh_home_t:s0 to unconfined_u:object_r:git_sys_content_t:s0 Expected results: # restorecon -rv /var/lib/git Relabeled /var/lib/git from unconfined_u:object_r:var_lib_t:s0 to unconfined_u:object_r:git_sys_content_t:s0 Additional info: I got the same results with CentOS 8.3 # rpm -q selinux-policy selinux-policy-targeted selinux-policy-3.14.3-54.el8_3.2.noarch selinux-policy-targeted-3.14.3-54.el8_3.2.noarch # sestatus SELinux status: enabled SELinuxfs mount: /sys/fs/selinux SELinux root directory: /etc/selinux Loaded policy name: targeted Current mode: enforcing Mode from config file: enforcing Policy MLS status: enabled Policy deny_unknown status: allowed Memory protection checking: actual (secure) Max kernel policy version: 32 # uname -r 4.18.0-240.15.1.el8_3.x86_64
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.