Re: SET SESSION AUTHORIZATION superuser limitation.

From: Robert Haas <robertmhaas(at)gmail(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Dmitry Igrishin <dmitigr(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: SET SESSION AUTHORIZATION superuser limitation.
Date: 2015-12-21 14:49:56
Message-ID: CA+TgmoZC2iYO94BDdVytQW-Gvc_M2k6-MLw2ki+f=t2qNdXWhA@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Sun, Dec 20, 2015 at 1:47 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> The syntax you propose exposes the user's password in cleartext in
> the command, where it is likely to get captured in logs for example.
> That's not going to do.

Of course, right now, the ALTER USER ... PASSWORD command has that
problem which is, uh, bad.

--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Victor Wagner 2015-12-21 14:50:13 Re: Patch: Implement failover on libpq connect level.
Previous Message Simon Riggs 2015-12-21 14:45:40 Re: ToDo list update for BRIN indexes