/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.lintian-overrides

  • 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.lintian-overrides
 
1
# This config file will normally have encrypted secret client keys in
 
2
# it, so it must be kept unreadable for non-root users.
 
3
#
 
4
mandos binary: non-standard-file-perm etc/mandos/clients.conf 0600 != 0644
 
5
mandos: init.d-script-needs-depends-on-lsb-base etc/init.d/mandos (line 46)
 
6
 
 
7
# The debconf templates is only used for displaying information
 
8
# detected in the postinst, not for saving answers to questions, so we
 
9
# don't need a .config file.
 
10
mandos binary: no-debconf-config
 
11
 
 
12
# The notice displayed from the postinst script really is critical
 
13
mandos binary: postinst-uses-db-input