<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>SELinux on SystemsGolive</title><link>https://systemsgolive.com/tags/selinux/</link><description>Recent content in SELinux on SystemsGolive</description><generator>Hugo -- gohugo.io</generator><language>en</language><copyright>© 2026 systemsgolive.com and Mickael Asghar. All rights reserved.</copyright><lastBuildDate>Wed, 28 Jan 2026 11:54:16 +0000</lastBuildDate><atom:link href="https://systemsgolive.com/tags/selinux/index.xml" rel="self" type="application/rss+xml"/><item><title>SELinux Context Mismatch: The Hidden Culprit in LDAP Certificate Renewal</title><link>https://systemsgolive.com/post/ldap-cert-renewal-selinux-context-issue/</link><pubDate>Wed, 28 Jan 2026 11:54:16 +0000</pubDate><guid>https://systemsgolive.com/post/ldap-cert-renewal-selinux-context-issue/</guid><description>
An internal LDAP certificate renewal failed due to incorrect SELinux contexts on transferred certificate files. Despite correct permissions and ownership, OpenLDAP couldn't initialise TLS. Using `restorecon` to fix the security context resolved the issue immediately, highlighting the importance of SELinux context verification in certificate deployments.</description></item></channel></rss>