pg.ddx.io  pgsql-interfaces@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Jan Wieck <janwieck@Yahoo.com>
To: CMVV <cmvilaverde@mail.telepac.pt>
Cc: pgsql-interfaces@postgreSQL.org
Subject: Re: pl/perl and security
Date: Thu, 8 Feb 2001 07:10:08 -0500 (EST)
Message-ID: <200102081210.HAA03543@jupiter.greatbridge.com> (raw)
In-Reply-To: <95otpc$hj4$1@news.tht.net>

CMVV wrote:
> Hi,
>
> I have discovered that in pl/perl we cannot make use of file handling.
> The README file in ../pl/plperl give us an hint with an example of a
> badfunc().
> What are the security reasons to do so, since with postgresql extensions
> (functions) written in C language we can do anything with flat files ?
> Can this security issue with pl/perl be overrided ?
> If so, how can i hack it ?
> It will be so nice to manage files from server-based functions written in
> pl/perl.
> Thanx

    The  security  issue  is  that  PL/Perl  is  designed to be a
    trusted procedural language. Meaning, any  unprivileged  user
    can create functions in it. Having file access, which is done
    under the UNIX-userid running  the  postmaster  process,  any
    user could modify your pg_hba.conf ...

    The  same  applies for PL/Tcl, why there will be an untrusted
    PL/TclU in 7.1, where only DB superusers can define functions
    in it.

    I'm not a Perl guy, but AFAIK you can modify the command mask
    used for the perl interpreter in the PL handler. But be  sure
    to restrict your patched version of PL/Perl to superusers, or
    accept that you created a big security hole.


Jan

--

#======================================================================#
# It's easier to get forgiveness for being wrong than for being right. #
# Let's break this rule - forgive me.                                  #
#================================================== JanWieck@Yahoo.com #



_________________________________________________________
Do You Yahoo!?
Get your free @yahoo.com address at http://mail.yahoo.com




view thread (2+ messages)

Message-ID: <200102081210.HAA03543@jupiter.greatbridge.com>
Permalink:  ../200102081210.HAA03543@jupiter.greatbridge.com/
Also on:    postgresql.org/message-id/200102081210.HAA03543@jupiter.greatbridge.com

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-interfaces@postgresql.org
  Cc: janwieck@Yahoo.com, cmvilaverde@mail.telepac.pt
  Subject: Re: pl/perl and security
  In-Reply-To: <200102081210.HAA03543@jupiter.greatbridge.com>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox