HardenedLinux

We are "patient" zero, so we hardened ourselves!

Jan 10, 2016 - 6 minute read - Guide

Hardening your desktop: Linux Mint with PaX/Grsecurity

By citypw

–[ CONTENTS

  1. About this doc

  2. Build and install customized kernel with PaX/Grsecurity patch

  3. PaX flags: paxctl-ng & pax-bites

  4. Kernel tuning

  5. Networking

  6. Sandboxing: seccomp

  7. Crypto

    6.1 Entropy

    6.2 Daily bread

##–[ 0. About this documentation We just celebrated another new year a couple of days ago, which means it’s 2016 already. A another new year usually just brings us to another fight. FOSS is still our fortress, as always.

  • People may quite excited about we are getting one step closer to the Singularity.
  • People may praise about how great of technological evolution will be.
  • People may just stuck in some shitty places and get drunk and going out of nowhere.
  • People may……….well, it’s none of my fuc*ing business.

I just reviewed the current status of GNU/Linux distros. Sadly to say, only a few distros( Aphine, Gentoo, etc) shipped PaX/Grsecurity by default. Even worse if you take a glance at the GNU/Linux desktop field. The GUI is looking better than ever before. But the sense of security is almost like a decade ago. This is what make me ticks, to write this doc. I’m trying to show you there’s a pretty easy way to do the whole process of hardening your desktop/laptop. I choose Linux Mint 17 as exmaple for two reasons.

1, I’m a Linux Mint user since Linut Mint 15. I personally like MATE and I hate GNOME3;-)

2, Linux Mint is the highest rank GNU/Linux distro in past 5 years( at least) according to DistroWatch.

##–[ 1. Build and install customized kernel with PaX/Grsecurity patch

I assumed you have Linux Mint 17 installed on your laptop or PC already. The 1st thing to do is install some packages will be used in the building of PaX/Grsecurity kernel:

Then, download linux kernel 4.3.3 and PaX/Grsecurity test patch for 4.3.3( note: for any commercial purpose use, I’m highly recommend you to use PaX/Grsecurity stable patch). Then, you could use my config to build kernel:

Then you should see some .deb files and you can use dpkg to install your new kernel:

Now you should have multiple kernel options. Comment two lines in /etc/default/grub if you want to choose which kernel to bootup:

And run:

Before reboot, plz make sure you install some popular applications:

##–[ 2. PaX flags: paxctl-ng & pax-bites

PaX flags is provided by PaX/Grsecurity to tell the kernel which mitigations should be used in the specific binary. More flags are enabled, more security you gains. But some binaries doesn’t work with some PaX flags, e.g: JIT can’t work with MPROTECT. For the sake of making PaX/Grsecurity work with Linux Mint, we’ll have to disable some mitigations in some binaries. I wrote a tool is called pax-bites, which utilize paxctl-ng to add/delete PaX flags. The config file of pax-bites is very easy to write. The format is like this:

For example, I’m using this config:

The very limited number of applications on Linut Mint GNU/Linux have been tested by us( I and other members of Hardenedlinux community). If you find some applications won’t work correctly caused by PaX flags, you can write your own config( plz let us know) or just file a bug by our github repo.

##–[ 3. Kernel tuning

The current sysctl.conf. We will do more work on this. Any detail about security-related kernel tuning, you might want to check Debian security checklist.

##–[ 4. Networking

Iptables is a eay-to-use stateful firewall. It’s very important to let your desktop/laptop have it. Some policies has been tested. You can use it directly. Any feedback or improvement are always welcome.

You might be interested in how iptables/netfilter works.

##–[ 5. Sandbox: Seccomp-bpf based implementation

The sandboxing technolog has a very long history of evolution journey in past decades. Here we’re just going through Seccomp based implementation. Seccomp is being merged into vanilla kernel since 2.6.12. Seccomp can not support complicated task because it whitelisted a few system calls for computing-only task. Anyway, it’s not what we talk about here. We only care about Seccomp’s extension: Seccomp-bpf.

There are two approaches to sandboxing the application you choose:

  • You can add Seccomp-bpf polices into the application by tweaking the polices via prctl(). IMOHO, it’s quite like pledge() system call in latest OpenBSD. Here’s some examples from Kees Cook( Yeah, that Kees who helped out to brings the real sense of security into kernel upstream;-))

  • Use a external wrapper program to exec the application with Seccomp-bpf filtering polices.

The 1st approach is developer-only. Because you’ll have to modify the source code add those polices into it. Otherwise, I don’t think this gonna happen in GNU/Linux community. OpenBSD community are trying add pledge() into diverse applications but…the people who cares about security from OpenBSD community were called “ bunch of masturbating monkeys” by Linus Torvalds….

The 2nd approach seems quite flexible. Here are two options:

  • Playpen, developed by Daniel Micay.

  • Firejail, developed/maintained by a group of people.

I choose firejail, because the community provides a bunch of sandboxing polices for some popular applications( firefox, vlc, chromium, etc). It’s almost like off-the-shell stuff. You can download the latest version of firejail and install it by package or compile it from source code. Note that the default Seccomp-bpf policies doesn’t have any system call whitelists, which mean it is a sandbox without filtering any syscalls basically. So write your own one if you want.

##–[ 6. Crypto

Crypto engineering has been playing a very important role in past decade. System security & crypto engineering are like twins. One can’t live without another. Use crypto without system hardening is like building your infrastructre on sand. Only hardening the system without using crypto is like archer’s holding a fancy Elf silver-bow but doesn’t have any arrows at all. Don’t forget the goal of infosec is to protect the fuc*ing information in 3 basic dimensions: C(onfidentiality), I(ntegrity) and A(vailability).

##—-[ 6.1 Entropy

Entropy is matter to private/session keys. It’d be a big deal if you’re using GNU/Linux as server. Desktop won’t be have much trouble about it. PaX/Grsecurity increased entropy for the kernel somehow. You may still want to install a daemon to ensuring the system always has enough entrop. Let the cryptographers worries about blocking/non-blocking issues on random/urandom. All you need to know is Haveged will be very helpful to your server/desktop. You can install it via:

##—-[ 6.2 Daily bread

It can bring you anonymity. Download it here.

Encryption/Decryption email with GPG is not a bad idea. You may also want to try opmsg.