/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 debian/mandos-client.config

  • 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:
debian/mandos-client.config
1
 
#! /bin/sh
2
 
#
3
 
# config        Mandos Debconf configuration.
4
 
#
5
 
 
6
 
# Source debconf library.
7
 
. /usr/share/debconf/confmodule
8
 
if ! db_version 2.0; then
9
 
    echo "mandos.config: need DebConf 2.0 or later"
10
 
    exit 1
11
 
fi
12
 
 
13
 
set -e
14
 
umask 022
15
 
 
16
 
# Now, interaction.  Batch it in case any front ends can use this.
17
 
db_beginblock
18
 
 
19
 
# If this is a first time install then prompt 
20
 
if [ "$1" = "configure" -a "$2" != "" ]; then
21
 
        db_input high mandos-client/not-yet-configured || true
22
 
fi
23
 
 
24
 
db_endblock
25
 
db_go || true
26
 
 
27
 
exit 0