/mandos/trunk

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

« back to all changes in this revision

Viewing changes to debian/mandos-client.lintian-overrides

  • Committer: Teddy Hogeborn
  • Date: 2024-09-16 21:01:52 UTC
  • Revision ID: teddy@recompile.se-20240916210152-0xbv4b15jyho9ydk
Override lintian experimental tag "executable-in-usr-lib"

Lintian reports executable files in /usr/lib, since binaries which are
executed internally are supposed to be stored in /usr/libexec.  But
the executables we store in /usr/lib are all files to be copied into
the initial RAM disk image, and are never executed from their storage
location in /usr/lib.  Except one; the Dracut module-setup.sh file.
But that file seems to be required to be executable; the
module-setup.sh file of every other Dracut module is also an
executable file.

* debian/mandos-client.lintian-overrides: Override experimental tag
  "executable-in-usr-lib" about files which are not actually executed
  from this location, and only exist to be copied to the initial RAM
  disk image.  Also the Dracut module-setup.sh file, which merely
  follows the pattern of all other Dracut module-setup.sh files from
  other Dracut modules.

Show diffs side-by-side

added added

removed removed

Lines of Context:
debian/mandos-client.lintian-overrides
20
20
mandos-client binary: elevated-privileges 4755 root/root [usr/lib/*/mandos/plugins.d/usplash]
21
21
mandos-client binary: elevated-privileges 4755 root/root [usr/lib/*/mandos/plugins.d/plymouth]
22
22
 
 
23
# These binaries are never executed in a running system, or from this
 
24
# directory.  These files exist only to be copied from here into the
 
25
# initial RAM disk image.
 
26
mandos-client binary: executable-in-usr-lib [usr/lib/*/mandos/mandos-to-cryptroot-unlock]
 
27
mandos-client binary: executable-in-usr-lib [usr/lib/*/mandos/plugin-helpers/mandos-client-iprouteadddel]
 
28
mandos-client binary: executable-in-usr-lib [usr/lib/*/mandos/plugin-runner]
 
29
mandos-client binary: executable-in-usr-lib [usr/lib/*/mandos/plugins.d/askpass-fifo]
 
30
mandos-client binary: executable-in-usr-lib [usr/lib/*/mandos/plugins.d/mandos-client]
 
31
mandos-client binary: executable-in-usr-lib [usr/lib/*/mandos/plugins.d/password-prompt]
 
32
mandos-client binary: executable-in-usr-lib [usr/lib/*/mandos/plugins.d/plymouth]
 
33
mandos-client binary: executable-in-usr-lib [usr/lib/*/mandos/plugins.d/splashy]
 
34
mandos-client binary: executable-in-usr-lib [usr/lib/*/mandos/plugins.d/usplash]
 
35
 
 
36
# This is the official directory for Dracut plugins, which are all
 
37
# executable shell script files.
 
38
mandos-client binary: executable-in-usr-lib [usr/lib/dracut/modules.d/90mandos/module-setup.sh]
 
39
# These files are never executed in a running system, or from this
 
40
# directory. These files exist only to be copied from here into the
 
41
# initial RAM disk image by the dracut/90mandos/module-setup.sh
 
42
# script.
 
43
mandos-client binary: executable-in-usr-lib [usr/lib/dracut/modules.d/90mandos/cmdline-mandos.sh]
 
44
mandos-client binary: executable-in-usr-lib [usr/lib/dracut/modules.d/90mandos/password-agent]
 
45
 
23
46
# The directory /etc/mandos/plugins.d can be used by local system
24
47
# administrators to place plugins in, overriding and complementing
25
48
# /usr/lib/<arch>/mandos/plugins.d, and must be likewise protected.