Re: Security implications of config-file-location patch

From: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Peter Eisentraut <peter_e(at)gmx(dot)net>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: Security implications of config-file-location patch
Date: 2004-10-09 21:56:21
Message-ID: 200410092156.i99LuL421447@candle.pha.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Tom Lane wrote:
> Peter Eisentraut <peter_e(at)gmx(dot)net> writes:
> > Tom Lane wrote:
> >> As of CVS tip, if you are using the config-file-location-changing
> >> features, anybody can find out the data directory location via
> >> "show pgdata";
>
> > Btw., couldn't we come up with a more descriptive parameter name than
> > "pgdata"?
>
> Sure. Actually it was just bothering me that "-c pgdata" didn't mean
> quite the same thing as setting PGDATA in the environment. Do you like
> "data_dir" or "data_directory" for the GUC variable?

I was going to suggest 'data_dir' but I see 'directory' is fully spelled
out in all other GUC variables in postgresql.conf, so let's use
'data_directory'.

--
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

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Bruce Momjian 2004-10-09 22:09:35 Re: [BUGS] BUG #1270: stack overflow in thread in fe_getauthname
Previous Message Kevin Brown 2004-10-09 21:01:02 Re: First set of OSDL Shared Mem scalability results, some wierdness ...