From: Tom Lane <tgl@sss.pgh.pa.us>
To: Bruce Momjian <bruce@momjian.us>
cc: greatvovan@gmail.com, pgsql-docs@lists.postgresql.org
Subject: Re: User mapping security
In-reply-to: <ZU1SOvgnwbBawgzN@momjian.us>
References: <156324246053.1191.5972769566826595079@wrigleys.postgresql.org>
 <ZU1SOvgnwbBawgzN@momjian.us>
Comments: In-reply-to Bruce Momjian <bruce@momjian.us>
	message dated "Thu, 09 Nov 2023 16:42:18 -0500"
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <1258587.1699567413.1@sss.pgh.pa.us>
Content-Transfer-Encoding: quoted-printable
Date: Thu, 09 Nov 2023 17:03:33 -0500
Message-ID: <1258588.1699567413@sss.pgh.pa.us>
Archived-At: 
 <https://www.postgresql.org/message-id/1258588.1699567413%40sss.pgh.pa.us>
Precedence: bulk

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 wit=
h be
>> stored as simple text and will be available for viewing in pg_user_mapp=
ings.

> 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.

			regards, tom lane