How to Install and Uninstall libdbix-safe-perl Package on Ubuntu 20.10 (Groovy Gorilla)
Last updated: November 07,2024
1. Install "libdbix-safe-perl" package
Learn how to install libdbix-safe-perl on Ubuntu 20.10 (Groovy Gorilla)
$
sudo apt update
Copied
$
sudo apt install
libdbix-safe-perl
Copied
2. Uninstall "libdbix-safe-perl" package
Please follow the guidance below to uninstall libdbix-safe-perl on Ubuntu 20.10 (Groovy Gorilla):
$
sudo apt remove
libdbix-safe-perl
Copied
$
sudo apt autoclean && sudo apt autoremove
Copied
3. Information about the libdbix-safe-perl package on Ubuntu 20.10 (Groovy Gorilla)
Package: libdbix-safe-perl
Architecture: all
Version: 1.2.5-2
Priority: optional
Section: universe/perl
Origin: Ubuntu
Maintainer: Ubuntu Developers
Original-Maintainer: Debian Perl Group
Bugs: https://bugs.launchpad.net/ubuntu/+filebug
Installed-Size: 67
Depends: perl, libdbi-perl
Filename: pool/universe/libd/libdbix-safe-perl/libdbix-safe-perl_1.2.5-2_all.deb
Size: 13634
MD5sum: efd00ff95e051765bd1dad138496ac2a
SHA1: dd7d46f468b3f09189adcea96e561843e6996181
SHA256: 2cc98b225262f481495124e1f12b2b93493990b40708f81229703b939ad615e2
SHA512: 5af572f83c9014df45a43e9ca2197911b349d647be4c87ea633401992fd1b65d36d17265d2907a3fc0eee0f4bde15934b79b467ff2d53f6a6b247881dc1cda61
Homepage: https://metacpan.org/release/DBIx-Safe
Description-en: safe wrapper to DBI interface
The purpose of the DBIx::Safe module is to give controlled, limited access to
an application, rather than simply passing it a raw database handle through
DBI. DBIx::Safe acts as a wrapper to the database, by only allowing through
the commands you tell it to. It filters all things related to the database
handle - methods and attributes.
.
The typical usage is for your application to create a database handle via a
normal DBI call to new(), then pass that to DBIx::Safe->new(), which will
return you a DBIx::Safe object. After specifying exactly what is and what is
not allowed, you can pass the object to the untrusted application. The object
will act very similar to a DBI database handle, and in most cases can be used
interchangeably.
.
By default, nothing is allowed to run at all. There are many things you can
control. You can specify which SQL commands are allowed, by indicating the
first word in the SQL statement (e.g. 'SELECT'). You can specify which
database methods are allowed to run (e.g. 'ping'). You can specify a regular
expression that allows matching SQL statements to run (e.g. 'qr{SET
TIMEZONE}'). You can specify a regular expression that is NOT allowed to run
(e.g. qr(UPDATE xxx}). Finally, you can indicate which database attributes
are allowed to be read and changed (e.g. 'PrintError'). For all of the above,
there are matching methods to remove them as well.
Description-md5: 3f02a19c7e269d9d679e7e0581c217b3
Architecture: all
Version: 1.2.5-2
Priority: optional
Section: universe/perl
Origin: Ubuntu
Maintainer: Ubuntu Developers
Original-Maintainer: Debian Perl Group
Bugs: https://bugs.launchpad.net/ubuntu/+filebug
Installed-Size: 67
Depends: perl, libdbi-perl
Filename: pool/universe/libd/libdbix-safe-perl/libdbix-safe-perl_1.2.5-2_all.deb
Size: 13634
MD5sum: efd00ff95e051765bd1dad138496ac2a
SHA1: dd7d46f468b3f09189adcea96e561843e6996181
SHA256: 2cc98b225262f481495124e1f12b2b93493990b40708f81229703b939ad615e2
SHA512: 5af572f83c9014df45a43e9ca2197911b349d647be4c87ea633401992fd1b65d36d17265d2907a3fc0eee0f4bde15934b79b467ff2d53f6a6b247881dc1cda61
Homepage: https://metacpan.org/release/DBIx-Safe
Description-en: safe wrapper to DBI interface
The purpose of the DBIx::Safe module is to give controlled, limited access to
an application, rather than simply passing it a raw database handle through
DBI. DBIx::Safe acts as a wrapper to the database, by only allowing through
the commands you tell it to. It filters all things related to the database
handle - methods and attributes.
.
The typical usage is for your application to create a database handle via a
normal DBI call to new(), then pass that to DBIx::Safe->new(), which will
return you a DBIx::Safe object. After specifying exactly what is and what is
not allowed, you can pass the object to the untrusted application. The object
will act very similar to a DBI database handle, and in most cases can be used
interchangeably.
.
By default, nothing is allowed to run at all. There are many things you can
control. You can specify which SQL commands are allowed, by indicating the
first word in the SQL statement (e.g. 'SELECT'). You can specify which
database methods are allowed to run (e.g. 'ping'). You can specify a regular
expression that allows matching SQL statements to run (e.g. 'qr{SET
TIMEZONE}'). You can specify a regular expression that is NOT allowed to run
(e.g. qr(UPDATE xxx}). Finally, you can indicate which database attributes
are allowed to be read and changed (e.g. 'PrintError'). For all of the above,
there are matching methods to remove them as well.
Description-md5: 3f02a19c7e269d9d679e7e0581c217b3