Re: Parsing errors in pg_hba.conf - Mailing list pgsql-hackers

From Alvaro Herrera
Subject Re: Parsing errors in pg_hba.conf
Date
Msg-id 20081027121933.GA3866@alvh.no-ip.org
Whole thread Raw
In response to Parsing errors in pg_hba.conf  (Magnus Hagander <magnus@hagander.net>)
Responses Re: Parsing errors in pg_hba.conf
List pgsql-hackers
Magnus Hagander wrote:
> In a number of places in pg_hba.conf, we don't actually log what goes
> wrong - instead we just goto a label that will log "invalid token \"%s\"".
> 
> Is there any special reason for this, other than the fact that it was
> the easy way out? I think it would be reasonable to for example log
> "hostssl not supported on this platform" instead of that, when USE_SSL
> is not defined, etc.

Without actually looking at what you're considering, I think it could be
a security bug if you were to disclose all the details to the user.
Perhaps the details can be passed to errdetail_log() to avoid this
problem.

-- 
Alvaro Herrera                                http://www.CommandPrompt.com/
The PostgreSQL Company - Command Prompt, Inc.


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: new correlation metric
Next
From: Tom Lane
Date:
Subject: Re: Parsing errors in pg_hba.conf