Re: Security implications of config-file-location patch - Mailing list pgsql-hackers

From Bruce Momjian
Subject Re: Security implications of config-file-location patch
Date
Msg-id 200410092156.i99LuL421447@candle.pha.pa.us
Whole thread Raw
In response to Re: Security implications of config-file-location patch  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: Security implications of config-file-location patch
List pgsql-hackers
Tom Lane wrote:
> Peter Eisentraut <peter_e@gmx.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@candle.pha.pa.us               |  (610)
359-1001+  If your life is a hard drive,     |  13 Roberts Road +  Christ can be your backup.        |  Newtown Square,
Pennsylvania19073
 


pgsql-hackers by date:

Previous
From: Gaetano Mendola
Date:
Subject: Re: postgres vulnerability
Next
From: Bruce Momjian
Date:
Subject: Re: [BUGS] BUG #1270: stack overflow in thread in fe_getauthname