How to Install and Uninstall libdbix-safe-perl Package on Kali Linux
Last updated: November 22,2024
1. Install "libdbix-safe-perl" package
In this section, we are going to explain the necessary steps to install libdbix-safe-perl on Kali Linux
$
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 Kali Linux:
$
sudo apt remove
libdbix-safe-perl
Copied
$
sudo apt autoclean && sudo apt autoremove
Copied
3. Information about the libdbix-safe-perl package on Kali Linux
Package: libdbix-safe-perl
Version: 1.2.5-3
Installed-Size: 40
Maintainer: Debian Perl Group
Architecture: all
Depends: perl:any, libdbi-perl
Size: 13652
SHA256: a811dd79119df6e13e3794368d311d4c185d140add6d2427f624d38c1bda8dbe
SHA1: 60d65fa1e01ee9dfae784ec5e9ddc663bb93f744
MD5sum: e97fa2698ff9c485cb79d303e8593c42
Description: 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:
Homepage: https://metacpan.org/release/DBIx-Safe
Tag: devel::lang:perl, devel::library, implemented-in::perl, role::shared-lib
Section: perl
Priority: optional
Filename: pool/main/libd/libdbix-safe-perl/libdbix-safe-perl_1.2.5-3_all.deb
Version: 1.2.5-3
Installed-Size: 40
Maintainer: Debian Perl Group
Architecture: all
Depends: perl:any, libdbi-perl
Size: 13652
SHA256: a811dd79119df6e13e3794368d311d4c185d140add6d2427f624d38c1bda8dbe
SHA1: 60d65fa1e01ee9dfae784ec5e9ddc663bb93f744
MD5sum: e97fa2698ff9c485cb79d303e8593c42
Description: 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:
Homepage: https://metacpan.org/release/DBIx-Safe
Tag: devel::lang:perl, devel::library, implemented-in::perl, role::shared-lib
Section: perl
Priority: optional
Filename: pool/main/libd/libdbix-safe-perl/libdbix-safe-perl_1.2.5-3_all.deb