pg.ddx.io  pgsql-bugs@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: PG Bug reporting form <noreply@postgresql.org>
To: pgsql-bugs@lists.postgresql.org
Cc: mail@goessmann.io
Subject: BUG #16652: SELECT pg_reload_conf(); returning true despite loading config has failed
Date: Sat, 03 Oct 2020 19:32:58 +0000
Message-ID: <16652-58dd6028047058a6@postgresql.org> (raw)

The following bug has been logged on the website:

Bug reference:      16652
Logged by:          Christoph Gößmann
Email address:      mail@goessmann.io
PostgreSQL version: 11.4
Operating system:   CentOS Linux 7
Description:        

I recently edited the contents of pg_hba.conf and made a mistake there. I
chose method "peer" for a "host" connection type. When reloading the
configuration with via "SELECT pg_reload_conf();" the log rightfully states
the following:

LOG:  peer authentication is only supported on local sockets
CONTEXT:  line 97 of configuration file
"/cluster/work/lawecon/Work/goessmann/pg_server/pg_data/pg_hba.conf"
LOG:  pg_hba.conf was not reloaded

But: 

The command "SELECT pg_reload_conf();" returns TRUE, letting the admin
believe that the new configuration is active and that potentially new IP
rejects or other security modifications now are active (if performed at the
same opportunity) -- especially since users typically do not check the logs
regularly if there is no problem they are aware of. 

Eventually, the misconfiguration will become evident when the database
cluster is restarted, but in many configurations this can take a long time
-- potentially leaving the database cluster exposed while anticipating that
some newly established security rules are active.



view thread (2+ messages)  latest in thread

Message-ID: <16652-58dd6028047058a6@postgresql.org>
Permalink:  ../16652-58dd6028047058a6@postgresql.org/
Also on:    postgresql.org/message-id/16652-58dd6028047058a6@postgresql.org

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-bugs@postgresql.org
  Cc: noreply@postgresql.org, pgsql-bugs@lists.postgresql.org, mail@goessmann.io
  Subject: Re: BUG #16652: SELECT pg_reload_conf(); returning true despite loading config has failed
  In-Reply-To: <16652-58dd6028047058a6@postgresql.org>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox