| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | David Helgason <david(at)uti(dot)is> |
| Cc: | Andrew Dunstan <andrew(at)dunslane(dot)net>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: plperl Safe restrictions |
| Date: | 2004-10-15 15:18:45 |
| Message-ID: | [email protected] |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers pgsql-patches |
David Helgason <david(at)uti(dot)is> writes:
> A postgres question I don't know the answer to is whether allowing the
> user to trigger a segfault is a security problem.
It would not be cool for a trusted language to allow such things, that's
for sure.
You could debate back and forth about whether we ought to allow it and
warn that some versions of Perl may have exploitable bugs, but I'd
prefer to err on the side of conservatism.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2004-10-15 15:27:05 | Re: plans for bitmap indexes? |
| Previous Message | Tom Lane | 2004-10-15 15:16:05 | Re: plperl Safe restrictions |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andrew Dunstan | 2004-10-15 15:27:36 | Re: plperl Safe restrictions |
| Previous Message | Tom Lane | 2004-10-15 15:16:05 | Re: plperl Safe restrictions |