The C compiler's sanitizing options introduce code in the output binary which is fragile and not very security conscious. It has become clear that sanitizing is only really meant for use while debugging.
As a side effect, this makes compilation faster, as the Makefile, for production builds, no longer runs the compiler repeatedly to find all its currently supported sanitizing options.
* Makefile (DEBUG): Add "$(SANITIZE)". (SANITIZE): Comment out. (CFLAGS): Remove "$(SANITIZE)". (plugins.d/mandos-client): Revert back to use plain $(LINK.c), since we no longer need to remove the leak sanitizer by overriding CFLAGS.
|| dpkg --compare-versions "$2" eq "1.8.0-1~bpo9+1"; then
61
if grep --quiet --regexp='^[[:space:]]*key_id[[:space:]]*=[[:space:]]*[Ee]3[Bb]0[Cc]44298[Ff][Cc]1[Cc]149[Aa][Ff][Bb][Ff]4[Cc]8996[Ff][Bb]92427[Aa][Ee]41[Ee]4649[Bb]934[Cc][Aa]495991[Bb]7852[Bb]855[[:space:]]*$' /etc/mandos/clients.conf; then