Date: Thu, 9 Nov 2023 17:09:55 -0500
From: Bruce Momjian <bruce@momjian.us>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: greatvovan@gmail.com, pgsql-docs@lists.postgresql.org
Subject: Re: User mapping security
Message-ID: <ZU1Ys5jo9C99Wh4Y@momjian.us>
References: <156324246053.1191.5972769566826595079@wrigleys.postgresql.org>
 <ZU1SOvgnwbBawgzN@momjian.us>
 <1258588.1699567413@sss.pgh.pa.us>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <1258588.1699567413@sss.pgh.pa.us>
Archived-At: 
 <https://www.postgresql.org/message-id/ZU1Ys5jo9C99Wh4Y%40momjian.us>
Precedence: bulk

On Thu, Nov  9, 2023 at 05:03:33PM -0500, Tom Lane wrote:
> Bruce Momjian <bruce@momjian.us> writes:
> > On Tue, Jul 16, 2019 at 02:01:00AM +0000, PG Doc comments form wrote:
> >> I suppose it should be warned on the pages that foreign credentials with be
> >> stored as simple text and will be available for viewing in pg_user_mappings.
> 
> > I know this is four years old, but the attached patch documents it.  I
> > don't think postgresql-fdw needs it since it relies on user mapping and
> > discourages passwords in the connection string.
> 
> This is far too alarmist.  It ignores the privilege restrictions that
> are built into the pg_user_mappings view.  Random users can't see
> umoptions.

True.  I wasn't sure how much of an issue it was to expose passwords at
the SQL level, but I will drop the idea.

-- 
  Bruce Momjian  <bruce@momjian.us>        https://momjian.us
  EDB                                      https://enterprisedb.com

  Only you can decide what is important to you.