| 1 |
Source: libdbix-safe-perl |
| 2 |
Maintainer: Debian Perl Group <[email protected]> |
| 3 |
Uploaders: gregor herrmann <[email protected]> |
| 4 |
Section: perl |
| 5 |
Testsuite: autopkgtest-pkg-perl |
| 6 |
Priority: optional |
| 7 |
Build-Depends: debhelper-compat (= 13) |
| 8 |
Build-Depends-Indep: libdbi-perl <!nocheck>, |
| 9 |
perl |
| 10 |
Standards-Version: 4.6.2 |
| 11 |
Vcs-Browser: https://salsa.debian.org/perl-team/modules/packages/libdbix-safe-perl |
| 12 |
Vcs-Git: https://salsa.debian.org/perl-team/modules/packages/libdbix-safe-perl.git |
| 13 |
Homepage: https://metacpan.org/release/DBIx-Safe |
| 14 |
Rules-Requires-Root: no |
| 15 |
|
| 16 |
Package: libdbix-safe-perl |
| 17 |
Architecture: all |
| 18 |
Depends: ${misc:Depends}, |
| 19 |
${perl:Depends}, |
| 20 |
libdbi-perl |
| 21 |
Description: safe wrapper to DBI interface |
| 22 |
The purpose of the DBIx::Safe module is to give controlled, limited access to |
| 23 |
an application, rather than simply passing it a raw database handle through |
| 24 |
DBI. DBIx::Safe acts as a wrapper to the database, by only allowing through |
| 25 |
the commands you tell it to. It filters all things related to the database |
| 26 |
handle - methods and attributes. |
| 27 |
. |
| 28 |
The typical usage is for your application to create a database handle via a |
| 29 |
normal DBI call to new(), then pass that to DBIx::Safe->new(), which will |
| 30 |
return you a DBIx::Safe object. After specifying exactly what is and what is |
| 31 |
not allowed, you can pass the object to the untrusted application. The object |
| 32 |
will act very similar to a DBI database handle, and in most cases can be used |
| 33 |
interchangeably. |
| 34 |
. |
| 35 |
By default, nothing is allowed to run at all. There are many things you can |
| 36 |
control. You can specify which SQL commands are allowed, by indicating the |
| 37 |
first word in the SQL statement (e.g. 'SELECT'). You can specify which |
| 38 |
database methods are allowed to run (e.g. 'ping'). You can specify a regular |
| 39 |
expression that allows matching SQL statements to run (e.g. 'qr{SET |
| 40 |
TIMEZONE}'). You can specify a regular expression that is NOT allowed to run |
| 41 |
(e.g. qr(UPDATE xxx}). Finally, you can indicate which database attributes |
| 42 |
are allowed to be read and changed (e.g. 'PrintError'). For all of the above, |
| 43 |
there are matching methods to remove them as well. |