FreshPorts -- The Place For Ports If you buy from Amazon USA, please support us by using this link.
Follow us

I am looking for an LTO tape library. Do you have one to spare?
Commit found by message id
Mon, 5 Dec 2011
[ 11:44:19 sunpoet ] Original commit 
p5-DBIx-Safe databases files touched by this commit Safer access to your database through a DBI database handle
- Add p5-DBIx-Safe 1.2.5

The purpose of DBIx::Safe 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

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.


Feature safe:   yes

Number of ports [& non-ports] in this commit: 2

show all files

User Login
Create account

Servers and bandwidth provided by
New York Internet, SuperNews, and RootBSD

This site
What is FreshPorts?
About the authors
How big is it?
The latest upgrade!

Enter Keywords:

Latest Vulnerabilities
asterisk11Sep 18
squidSep 18
squid33Sep 18
dbusSep 17
nginxSep 16
nginx-develSep 16
phpmyadminSep 13
ossec-hids-clientSep 11
ossec-hids-localSep 11
ossec-hids-serverSep 11
chromiumSep 09
trafficserverSep 05
apache22*Sep 03
apache22-event-mpm*Sep 03
apache22-itk-mpm*Sep 03

8 vulnerabilities affecting 19 ports have been reported in the past 14 days

* - modified, not new

All vulnerabilities

Deleted ports
Sanity Test Failures

NEW Graphs (Javascript)

Calculated hourly:
Port count 24094
Broken 121
Deprecated 90
Ignore 385
Forbidden 17
Restricted 203
Vulnerable 22
Expired 2
Set to expire 85
Interactive 0
new 24 hours 0
new 48 hours5
new 7 days35
new fortnight70
new month236

Servers and bandwidth provided by
New York Internet, SuperNews, and RootBSD
Valid HTML, CSS, and RSS.
Copyright © 2000-2014 Dan Langille. All rights reserved.