/mandos/release

To get this branch, use:
bzr branch http://bzr.recompile.se/loggerhead/mandos/release

« back to all changes in this revision

Viewing changes to initramfs-tools-hook-conf

  • Committer: Teddy Hogeborn
  • Date: 2019-07-14 22:39:15 UTC
  • mto: This revision was merged to the branch mainline in revision 384.
  • Revision ID: teddy@recompile.se-20190714223915-aqjkms3t3taa6tye
Only use sanitizing options when debugging

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.

Show diffs side-by-side

added added

removed removed

Lines of Context:
initramfs-tools-hook-conf
1
 
# -*- shell-script -*-
2
 
 
3
 
# if mkinitramfs is started by mkinitramfs-kpkg, mkinitramfs-kpkg has
4
 
# already touched the initrd file with umask 022 before we had a
5
 
# chance to affect it.  We cannot allow a readable initrd file,
6
 
# therefore we must fix this now.
7
 
if [ -e "${outfile}" ] \
8
 
    && [ `stat --format=%s "${outfile}"` -eq 0 ]; then
9
 
    rm "${outfile}"
10
 
    (umask 027; touch "${outfile}")
11
 
fi
12
 
 
13
 
UMASK=027