hardening: clarify the whitelist logic

Per @Ericson2314's suggestion [1], make it more clear that the active
hardenings are decided via whitelist; the blacklist is merely for the
debug messages.

1: 36d5ce41d4 (r133279731)
This commit is contained in:
Charles Strahan 2018-03-05 21:06:07 -05:00
parent 9920923cde
commit cc7ce57f86
No known key found for this signature in database
GPG key ID: BB47AB4B8489B5A5

View file

@ -1,21 +1,25 @@
allHardeningFlags=(fortify stackprotector pie pic strictoverflow format relro bindnow)
hardeningCFlags=()
declare -A hardeningDisableMap=()
declare -A hardeningEnableMap=()
# Create table of unsupported flags for this toolchain.
for flag in @hardening_unsupported_flags@; do
hardeningDisableMap[$flag]=1
done
# Intentionally word-split in case 'NIX_HARDENING_ENABLE' is defined in Nix. The
# array expansion also prevents undefined variables from causing trouble with
# `set -u`.
for flag in ${NIX_HARDENING_ENABLE-}; do
if [[ -z "${hardeningDisableMap[$flag]-}" ]]; then
hardeningEnableMap[$flag]=1
done
# Remove unsupported flags.
if (( "${NIX_DEBUG:-0}" >= 1 )); then
declare -A hardeningDisableMap=()
fi
for flag in @hardening_unsupported_flags@; do
[[ -n ${hardeningEnableMap[$flag]} ]] || continue
if (( "${NIX_DEBUG:-0}" >= 1 )); then
hardeningDisableMap[$flag]=1
fi
unset hardeningEnableMap[$flag]
done
if (( "${NIX_DEBUG:-0}" >= 1 )); then