Re: cpan perl module - plperlu danger?

From: merlyn(at)stonehenge(dot)com (Randal L(dot) Schwartz)
To: "A(dot)M(dot)" <agentm(at)themactionfaction(dot)com>
Cc: pgsql-general(at)postgresql(dot)org
Subject: Re: cpan perl module - plperlu danger?
Date: 2006-06-22 14:56:03
Message-ID: 86fyhx1bp8.fsf@blue.stonehenge.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

>>>>> "A" == A M <agentm(at)themactionfaction(dot)com> writes:

A> [But even Safe.pm has had
A> dozens of bugs revealed over the years- caveat emptor.]

Eeeh? Proof please? That's just FUD-raking.

From what I recall, there have been a few clever leakages that have been fixed
rather rapidly.

"few" ne "dozens".

The main problem with Safe is that it's at the wrong granularity (per opcode,
not per semantic operation).

But let's not be throwing the baby out with the bathwater... Safe is 99.97% of
the way there.

--
Randal L. Schwartz - Stonehenge Consulting Services, Inc. - +1 503 777 0095
<merlyn(at)stonehenge(dot)com> <URL:http://www.stonehenge.com/merlyn/>
Perl/Unix/security consulting, Technical writing, Comedy, etc. etc.
See PerlTraining.Stonehenge.com for onsite and open-enrollment Perl training!

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Relyea, Mike 2006-06-22 14:56:53 Re: Out of memory error in 8.1.0 Win32
Previous Message Richard Broersma Jr 2006-06-22 14:53:33 Re: OLEDB Provider for Postgres