Debian Codegraph @

debian/control

raw
1 Source: libfile-policy-perl
2 Maintainer: Debian Perl Group <[email protected]>
3 Uploaders: Florian Schlichting <[email protected]>
4 Section: perl
5 Testsuite: autopkgtest-pkg-perl
6 Priority: optional
7 Build-Depends: debhelper-compat (= 13)
8 Build-Depends-Indep: perl,
9 libtest-pod-perl,
10 libtest-pod-coverage-perl,
11 libtest-assertions-perl,
12 liblog-trace-perl,
13 libfile-slurp-perl
14 Standards-Version: 3.9.8
15 Vcs-Browser: https://salsa.debian.org/perl-team/modules/packages/libfile-policy-perl
16 Vcs-Git: https://salsa.debian.org/perl-team/modules/packages/libfile-policy-perl.git
17 Homepage: https://metacpan.org/release/File-Policy
18
19 Package: libfile-policy-perl
20 Architecture: all
21 Depends: ${perl:Depends},
22 ${misc:Depends},
23 libtest-assertions-perl,
24 liblog-trace-perl,
25 libfile-slurp-perl
26 Multi-Arch: foreign
27 Description: simple policy for file I/O functions
28 File::Policy defines the policy for file I/O with modules such as
29 File::Slurp::WithinPolicy. The purpose is to allow systems administrators to
30 define locations and restrictions for applications' file I/O and give app
31 developers a policy to follow. Note that the module doesn't ENFORCE the policy
32 - application developers can choose to ignore it (and systems administrators
33 can choose not to install their applications if they do!).
34 .
35 You may control which policy gets applied by creating a File::Policy::Config
36 module with an IMPLEMENTATION constant. You may write your own policy as a
37 module within the File::Policy:: namespace.
38 .
39 By default (if no File::Policy::Config is present), the File::Policy::Default
40 policy gets applied which doesn't impose any restrictions and provides
41 reasonable default locations for temporary and log files.
42 .
43 The motivation behind this module was a standard, flexible approach to allow
44 a site wide file policy to be defined. This will be most useful in large
45 environments where a few sysadmins are responsible for code written by many
46 other people. Simply ensuring that submitted code calls check_safe() ensures
47 file access is sane, reducing the amount of effort required to do a security
48 audit.