/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: 2014-06-08 03:10:08 UTC
  • mto: (237.7.272 trunk)
  • mto: This revision was merged to the branch mainline in revision 317.
  • Revision ID: teddy@recompile.se-20140608031008-mc9bd7b024a3q0y0
Address a very theoretical possible security issue in mandos-client.

If there were to run some sort of "cleaner" process for /run/tmp (or
/tmp), and mandos-client were to run for long enough for that cleaner
process to remove the temporary directory for GPGME, there was a
possibility that another unprivileged process could trick the (also
unprivileged) mandos-client process to remove other files or symlinks
which the unprivileged mandos-client process was allowed to remove.
This is not currently known to have been exploitable, since there are
no known initramfs environments running such cleaner processes.

* plugins.d/mandos-client.c (main): Use O_NOFOLLOW when opening
                                    tempdir for cleaning.

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