Skip to content

mohitmishra786/low-level-dev-skills / skills/runtimes/binary-hardening

binary-hardening

Verified

Binary hardening skill for security-hardened C/C++ builds. Use when enabling RELRO, PIE, stack canaries, FORTIFY_SOURCE, CFI sanitizers, shadow stack, or seccomp-bpf syscall filtering. Covers checksec analysis, compiler and linker flags for hardened builds, and NSA/CISA-recommended mitigations. Activates on queries about binary hardening, checksec, RELRO, PIE, stack canaries, FORTIFY_SOURCE, CFI, shadow stack, or seccomp.

FileKindSize
SKILL.mdskill md7.9 KB
references/hardening-flags.mdmarkdown2.9 KB

references/hardening-flags.md

View on GitHub
# Binary Hardening Flags Reference

Source: <https://best.openssf.org/Compiler-Hardening-Guides/Compiler-Options-Hardening-Guide-for-C-and-C++>

## Complete Hardened Build Commands

### GCC (Linux)

```bash
CFLAGS="-O2 -pipe \
  -Wall -Wformat -Wformat-security -Werror=format-security \
  -fstack-protector-strong \
  -fstack-clash-protection \
  -fcf-protection \
  -D_FORTIFY_SOURCE=3 \
  -D_GLIBCXX_ASSERTIONS \
  -fPIE"

CXXFLAGS="${CFLAGS} -D_GLIBCXX_ASSERTIONS"

LDFLAGS="-pie \
  -Wl,-z,relro \
  -Wl,-z,now \
  -Wl,-z,noexecstack \
  -Wl,-z,nodlopen \
  -Wl,-z,nodump \
  -Wl,--as-needed"

gcc ${CFLAGS} ${LDFLAGS} -o prog main.c
```

### Clang (Linux)

```bash
CFLAGS="-O2 \
  -fstack-protector-strong \
  -fstack-clash-protection \
  -D_FORTIFY_SOURCE=3 \
  -fPIE \
  -fsanitize=safe-stack"

LDFLAGS="-pie \
  -Wl,-z,relro -Wl,-z,now -Wl,-z,noexecstack \
  -fsanitize=safe-stack"

clang ${CFLAGS} ${LDFLAGS} -o prog main.c
```

### Shared Libraries

```bash
# Shared library hardening (note: -fPIC not -fPIE)
CFLAGS="-O2 -fPIC -fstack-protector-strong -D_FORTIFY_SOURCE=2"
LDFLAGS="-shared -Wl,-z,relro -Wl,-z,now -Wl,-z,noexecstack"

gcc ${CFLAGS} ${LDFLAGS} -o libfoo.so foo.c
```

## Flag Reference Table

| Flag | Compiler | Linker | Effect |
|------|----------|--------|--------|
| `-fstack-protector-strong` | GCC/Clang | — | Stack canary on at-risk functions |
| `-fstack-protector-all` | GCC/Clang | — | Stack canary on ALL functions (slow) |
| `-fstack-clash-protection` | GCC ≥8/Clang ≥11 | — | Prevents stack-heap collision |
| `-fcf-protection` | GCC ≥8/Clang | — | Intel CET: IBT + shadow stack |
| `-D_FORTIFY_SOURCE=2` | GCC/Clang | — | Checked libc wrappers (level 2) |
| `-D_FORTIFY_SOURCE=3` | GCC ≥12/Clang ≥12 | — | More thorough FORTIFY |
| `-fPIE` | GCC/Clang | — | Compile as PIE (requires `-pie` to link) |
| `-pie` | — | GCC/Clang | Link as position-independent executable |
| `-Wl,-z,relro` | — | GCC/Clang (ld) | Mark GOT read-only after relocation |
| `-Wl,-z,now` | — | GCC/Clang (ld) | Eager binding → Full RELRO |
| `-Wl,-z,noexecstack` | — | GCC/Clang (ld) | Non-executable stack (NX) |
| `-Wl,-z,separate-code` | — | GCC/Clang (ld) | Separate code/data PT_LOAD segments |
| `-fsanitize=cfi` | Clang + LTO | — | Control flow integrity (needs -flto) |
| `-fsanitize=safe-stack` | Clang | — | SafeStack (separate unsafe stack) |
| `-Wformat -Wformat-security` | GCC/Clang | — | Warn on format string issues |
| `-Werror=format-security` | GCC/Clang | — | Error on dangerous format strings |

## Distribution Defaults

| Distro | Default hardening |
|--------|------------------|
| Debian/Ubuntu | PIE, RELRO, canary, FORTIFY=2 |
| Fedora/RHEL | PIE, Full RELRO, canary, FORTIFY=3 (Fedora 38+) |
| Alpine | PIE, RELRO, canary (musl-based) |
| Arch Linux | PIE, RELRO, canary, FORTIFY=2 |

Check what your distro uses:

```bash
dpkg-buildflags --query   # Debian/Ubuntu
rpm --eval "%{build_cflags}"  # Fedora/RHEL
```
rea-analysis-optimizationmorluto/reaOptimize REA providers and shared analysis workflows for agent context, latency, CPU, and memory while preserving correctness and Evidence. Use for analysis bottlenecks and cache or query design; CI/test-suite optimization belongs to rea-ci-tests-audit.Stars: 472kUpdated Claude CodeCodexVerifiedInstall
rea-ci-tests-auditmorluto/reaAudit REA CI and test suites for correctness, fixture drift, false passes, and measured performance; use for suite or workflow investigations and efficiency changes, rather than ordinary feature testing or a single test failure.Stars: 472kUpdated Claude CodeCodexVerifiedInstall
rea-tool-designmorluto/reaAudit, investigate, design, or change REA investigation tools, CLI/MCP contracts, provider capabilities, and Evidence semantics.Stars: 472kUpdated Claude CodeCodexVerifiedInstall
ponytail-auditDietrichGebert/ponytailQuality audit of the whole repo: bugs, security, real load, missing tests, speed, and what to delete. Most important first.Stars: 194kUpdated Claude CodeCodexVerifiedInstall