catborise 8dfe4d7713 fix(gstfsd): a key added to an SELinux guest gets the guest's labels ... Files that libguestfs creates have no SELinux label. On an enforcing guest (RHEL, Rocky, Alma, Fedora) sshd may not read the unlabeled /root/.ssh/authorized_keys, so a key added from the panel did not let anyone log in ("avc: denied { read } ... unlabeled_t"). After writing a key, gstfsd now relabels /root/.ssh with the guest's own file contexts (/etc/selinux/<SELINUXTYPE>/contexts/files/file_contexts), as virt-customize does. Guests without an SELinux policy or with SELinux disabled are left as they are. If the guest needs labels but the host's libguestfs cannot set them, the request fails before anything is written. A root password needs no labelling: /etc/shadow keeps its file and label.		2026-10-08 16:19:24 +03:00
..
consolecallback	remove css urls, add missing socketio requirements, fix cookie import, and rearrange socketiod connetion	2022-07-21 13:31:37 +03:00
gstfsd	fix(gstfsd): a key added to an SELinux guest gets the guest's labels	2026-10-08 16:19:24 +03:00