Featured Articles

WordPress Multisite on the Darknet (Mercator .onion alias)
Continuous Documentation: Hosting Read the Docs on GitHub Pages (2/2)
Detecting (Malicious) Unicode in GitHub PRs
WordPress Profiling with XHProf (Debugging & Optimizing Speed)
Introducing BusKill: A Kill Cord for your Laptop
Hardening Guide for phpList
previous arrow
next arrow

Enabling SELinux strict on RHEL5

I've been playing around with SELinux at work recently. Not surprisingly, I was struggling to get SELINUXTYPE=strict to work properly. Unfortunately, all "google results for 'enabling selinux strict' would return were dead ends. People would enable selinux strict, kernel panic, and 'fix' it by disabling selinux.

Well, a co-worker of mine *was* able to successfully enable selinux's strict policy on RHEL5 (CentOS 5). He gave me this guide to post to the world for others to see how (thanks Mykola):

Michael Altfield

Hi, I’m Michael Altfield. I write articles about opsec, privacy, and devops ➡

About Michael


. . . → Read More: Enabling SELinux strict on RHEL5

eHome -- are you home?

Alright, this is bullshit.

I bought an eHome wireless NIC a while ago for really cheap. Haven't heard of eHome? Neither had I, but it didn't take me long to realize that it was actually part of D-Link Corporation when I sent my rebates to a DLink corporate address, and when I read the message: "Copyright © D-Link Corporation/D-Link Systems, Inc. All rights reserved. eHome Networking and the eHome Networking logo are registered trademarks of D-Link Corporation or its subsidiaries in the United States and other countries..."

So, I figured: D-Link is a popular company, they're not going anywhere, they sell tons of devices, so my chipset is probably well supported in Linux, right? Wrong.

Michael Altfield

Hi, I’m Michael Altfield. I write articles about opsec, privacy, and devops ➡

About Michael


. . . → Read More: eHome -- are you home?