Skip site navigation (1) Skip section navigation (2)

Re: Updated instrumentation patch

From: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>
To: Magnus Hagander <mha(at)sollentuna(dot)net>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>,PostgreSQL-patches <pgsql-patches(at)postgresql(dot)org>
Subject: Re: Updated instrumentation patch
Date: 2005-07-30 15:38:54
Message-ID: 200507301538.j6UFcs206070@candle.pha.pa.us (view raw or flat)
Thread:
Lists: pgsql-patches
Magnus Hagander wrote:
> 
> > > > Also, as I already said, marking it as PGC_POSTMASTER is 
> > simply not 
> > > > adequate security.  Once we have some sort of remote 
> > admin feature, 
> > > > I would expect it to support adjustment of even postmaster-level 
> > > > options (this would mean forcing a database restart of 
> > course) --- 
> > > > you can hardly say that you have a complete remote admin 
> > solution if 
> > > > you can't change shared_buffers or max_connections.
> > > 
> > > The point is you cannot *enable* it once it is *disabled*. Thus you 
> > > cannot *elevate* your privileges. Thus not a security issue.
> > 
> > I think any secure solution is going to have to block all 
> > write access to postgresql.conf, and that includes all the 
> > COPY TO and all the untrusted languages.
> 
> Exactly. But we won't get that for 8.1. So for now, we block all write
> access through *new* functions, per the "let's at least not add more
> security holes" rule.

As far as I know, the only new functionality the patch adds _over_ copy
is the ability to write nulls, and rename/unlink.  Should we just throw
an error when writing null bytes?

-- 
  Bruce Momjian                        |  http://candle.pha.pa.us
  pgman(at)candle(dot)pha(dot)pa(dot)us               |  (610) 359-1001
  +  If your life is a hard drive,     |  13 Roberts Road
  +  Christ can be your backup.        |  Newtown Square, Pennsylvania 19073

In response to

pgsql-patches by date

Next:From: Bruce MomjianDate: 2005-07-30 15:46:37
Subject: Re: Patch to mention cost-based delay in vacuum reference
Previous:From: Magnus HaganderDate: 2005-07-30 15:29:09
Subject: Re: Updated instrumentation patch

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group