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