Re: postgresql and LDAP

From: Gregory Stark <stark(at)enterprisedb(dot)com>
To: Emanuel Calvo Franco <postgres(dot)arg(at)gmail(dot)com>
Cc: General PostgreSQL List <pgsql-general(at)postgresql(dot)org>
Subject: Re: postgresql and LDAP
Date: 2009-03-10 13:42:45
Message-ID: 8763ih7aui.fsf@oxford.xeocode.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Emanuel Calvo Franco <postgres(dot)arg(at)gmail(dot)com> writes:

> 2009/3/10 Gregory Stark <stark(at)enterprisedb(dot)com>:
>> Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> writes:
>>> However, a tip that might help is that there should be more information
>>> about the problem in the postmaster log.  We intentionally don't send
>>> details about the conf file's contents to the client...
>>
>> Perhaps we should send a HINT to the client saying to consult the postmaster
>> logs?

egg on my face -- we already *do* have such a hint:

ereport(FATAL,
(errcode(ERRCODE_CONFIG_FILE_ERROR),
errmsg("missing or erroneous pg_hba.conf file"),
errhint("See server log for details.")));

> IMHO I think is quite dangerous because someone with experience could guess
> some security details.

How?

--
Gregory Stark
EnterpriseDB http://www.enterprisedb.com
Ask me about EnterpriseDB's 24x7 Postgres support!

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Ivan Sergio Borgonovo 2009-03-10 15:21:21 Re: bug?: permission denied for schema on "on delete set null"
Previous Message Andreas Wenk 2009-03-10 13:31:56 Re: bug?: permission denied for schema on "on delete set null"