Shell Roff
Latest commit bcb03d3 Feb 21, 2017 @slimm609 updated readme
Failed to load latest commit information.
extras added gitignore and rpm spec Feb 18, 2017
tests signed update Oct 27, 2016
.gitignore added gitignore and rpm spec Feb 18, 2017
ChangeLog signed update Oct 27, 2016
LICENSE.txt add LICENSE.txt Sep 12, 2015 updated readme Feb 21, 2017
checksec signed update Dec 30, 2016
checksec.sig signed update Dec 30, 2016


Checksec is a bash script to check the properties of executables (like PIE, RELRO, PaX, Canaries, ASLR, Fortify Source). It has been originally written by Tobias Klein and the original source is available here:


Last Update: 2016-12-30


Install the binutils via brew brew install binutils


normal (or --format cli)

$ --file /bin/ls
RELRO           STACK CANARY      NX            PIE             RPATH      RUNPATH      FILE
Partial RELRO   Canary found      NX enabled    No PIE          No RPATH   No RUNPATH   /bin/ls


$ --output csv --file /bin/ls
Partial RELRO,Canary found,NX enabled,No PIE,No RPATH,No RUNPATH,/bin/ls


$ --output xml --file /bin/ls
<?xml version="1.0" encoding="UTF-8"?>
<file relro="partial" canary="yes" nx="yes" pie="no" rpath="no" runpath="no" filename='/bin/ls'/>


$ --output json --file /bin/ls  
{ "file": { "relro":"partial","canary":"yes","nx":"yes","pie":"no","rpath":"no","runpath":"no","filename":"/bin/ls" } }

Fortify test in cli

$ --fortify-proc 1
* Process name (PID)                         : init (1)
* FORTIFY_SOURCE support available (libc)    : Yes
* Binary compiled with FORTIFY_SOURCE support: Yes

------ EXECUTABLE-FILE ------- . -------- LIBC --------
FORTIFY-able library functions | Checked function names
fdelt_chk                      | __fdelt_chk
read                           | __read_chk
syslog_chk                     | __syslog_chk
fprintf_chk                    | __fprintf_chk
vsnprintf_chk                  | __vsnprintf_chk
fgets                          | __fgets_chk
strncpy                        | __strncpy_chk
snprintf_chk                   | __snprintf_chk
memset                         | __memset_chk
strncat_chk                    | __strncat_chk
memcpy                         | __memcpy_chk
fread                          | __fread_chk
sprintf_chk                    | __sprintf_chk


* Number of checked functions in libc                : 78
* Total number of library functions in the executable: 116
* Number of FORTIFY-able functions in the executable : 13
* Number of checked functions in the executable      : 7
* Number of unchecked functions in the executable    : 6

Kernel test in Cli

$ --kernel
* Kernel protection information:

Description - List the status of kernel protection mechanisms. Rather than
inspect kernel mechanisms that may aid in the prevention of exploitation of
userspace processes, this option lists the status of kernel configuration
options that harden the kernel itself against attack.

Kernel config: /proc/config.gz

    GCC stack protector support:            Enabled
    Strict user copy checks:                Disabled
    Enforce read-only kernel data:          Disabled
    Restrict /dev/mem access:               Enabled
    Restrict /dev/kmem access:              Enabled

* grsecurity / PaX: Auto GRKERNSEC

    Non-executable kernel pages:            Enabled
    Non-executable pages:                   Enabled
    Paging Based Non-executable pages:      Enabled
    Restrict MPROTECT:                      Enabled
    Address Space Layout Randomization:     Enabled
    Randomize Kernel Stack:                 Enabled
    Randomize User Stack:                   Enabled
    Randomize MMAP Stack:                   Enabled
    Sanitize freed memory:                  Enabled
    Sanitize Kernel Stack:                  Enabled
    Prevent userspace pointer deref:        Enabled
    Prevent kobject refcount overflow:      Enabled
    Bounds check heap object copies:        Enabled
    JIT Hardening:                          Enabled
    Thread Stack Random Gaps:               Enabled
    Disable writing to kmem/mem/port:       Enabled
    Disable privileged I/O:                 Enabled
    Harden module auto-loading:             Enabled
    Chroot Protection:                      Enabled
    Deter ptrace process snooping:          Enabled
    Larger Entropy Pools:                   Enabled
    TCP/UDP Blackhole:                      Enabled
    Deter Exploit Bruteforcing:             Enabled
    Hide kernel symbols:                    Enabled

* Kernel Heap Hardening: No KERNHEAP

The KERNHEAP hardening patchset is available here:

Kernel Test in XML

$ --output xml --kernel
<?xml version="1.0" encoding="UTF-8"?>
<kernel config='/boot/config-3.11-2-amd64' gcc_stack_protector='yes' strict_user_copy_check='no' ro_kernel_data='yes' restrict_dev_mem_access='yes' restrict_dev_kmem_access='no'>
    <grsecurity config='no' />
    <kernheap config='no' />

Kernel Test in Json

$ --output json --kernel
{ "kernel": { "KernelConfig":"/boot/config-3.11-2-amd64","gcc_stack_protector":"yes","strict_user_copy_check":"no","ro_kernel_data":"yes","restrict_dev_mem_access":"yes","restrict_dev_kmem_access":"no" },{ "grsecurity_config":"no" },{ "kernheap_config":"no" } }


Due to the original structure of the script the --output argument should be placed first on the command line arguments. Doing differently would require really big changes in the code.