libfile-policy-perl 1.005-4 source package in Ubuntu

Changelog

libfile-policy-perl (1.005-4) unstable; urgency=medium

  [ Debian Janitor ]
  * Apply multi-arch hints. + libfile-policy-perl: Add Multi-Arch: foreign.

 -- Jelmer Vernooij <email address hidden>  Wed, 07 Dec 2022 22:48:57 +0000

Upload details

Uploaded by:
Debian Perl Group
Uploaded to:
Sid
Original maintainer:
Debian Perl Group
Architectures:
all
Section:
perl
Urgency:
Medium Urgency

See full publishing history Publishing

Series Pocket Published Component Section
Oracular release universe perl
Noble release universe perl
Mantic release universe perl
Lunar release universe perl

Builds

Lunar: [FULLYBUILT] amd64

Downloads

File Size SHA-256 Checksum
libfile-policy-perl_1.005-4.dsc 2.2 KiB a4b30bed41cd0548c52ff84bea55f73cdcdf3af60ed00222342242bf9b4e0ce7
libfile-policy-perl_1.005.orig.tar.gz 13.9 KiB 56be77e527a708c4403212ffefd9ee280aef2aa8794bac625ce8035dc854f7b9
libfile-policy-perl_1.005-4.debian.tar.xz 3.2 KiB 310365096c205184fd7e8980080473c30f9c72d2a80a2ea4b9728733525de939

Available diffs

No changes file available.

Binary packages built by this source

libfile-policy-perl: 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.