Selinux

The blog posts have slowed down a bit lately because I’ve been heads down on a security project at work.

If you’re running Fedora 22 and you’ve recently updated to systemd-219-24.

I’ve decided to start a series of posts called “Chronicles of SELinux” where I hope to educate more users on how to handle SELinux denials with finesse rather than simply disabling it entirely.

I’ve been working with some Fedora environments in chroots and I ran into a peculiar SELinux AVC denial a short while ago:

I talked about the joys of running my own mail server last week only to find that my mail server was broken yesterday.

I’m in the process of trying Fedora 20 on my retina MacBook and I ran into a peculiar issue with Chrome.

Getting started with LXC is a bit awkward and I’ve assembled this guide for anyone who wants to begin experimenting with LXC containers in Fedora 20.

The confined user support in SELinux is handy for ensuring that users aren’t able to do something that they shouldn’t.

It’s been a little while since I last posted about installing Xen on Fedora, so I figured that Fedora 19’s beta release was as good a time as any to write a new post.

While rolling through my RSS feeds, I found a great presentation by David Quigley titled “Demystifying SELinux”.

This article appeared in SC Magazine and I’ve posted it here as well.

After many discussions with fellow Linux users, I’ve come to realize that most seem to disable SELinux rather than understand why it’s denying access.

If you try to run Xen without libvirt on Fedora 17 with SELinux in enforcing mode, you’ll be butting heads with SELinux in no time.

If you want to forward e-mail from root to another user, you can usually place a .

SELinux isn’t a technology that’s easy to tackle for newcomers.

I’m using SELinux more often now on my Fedora 15 installations and I came up against a peculiar issue today on a new server.