From: Tom Lane <tgl@sss.pgh.pa.us>
To: Ken J. Wright <ken@ori-ind.com>
Cc: Peter Eisentraut <peter_e@gmx.net>
Cc: pgsql-interfaces@postgreSQL.org
Subject: Re: [INTERFACES] pg_pwd problem, 2nd try
Date: Tue, 22 Feb 2000 18:21:46 -0500
Message-ID: <26301.951261706@sss.pgh.pa.us> (raw)
In-Reply-To: <3.0.1.32.20000222130908.00b9f950@ori-ind.com>
References: <3.0.1.32.20000222130908.00b9f950@ori-ind.com>
"Ken J. Wright" <ken@ori-ind.com> writes:
> If I use the ALTER USER sql statement, the file pg_pwd gets written in an
> older plain text format & the user can no longer authenticate. However,
> using pg_passwd from the command line reates a file similar to /etc/passwd
> including the username and an encrypted password. Known problem?
It is now ;-)
Peter changed the backend's idea about the format of pg_pwd, but
I guess he forgot about pg_passwd ...
I wonder whether we even need pg_passwd in its present form anymore.
Maybe it should just issue an ALTER USER command?
regards, tom lane
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-interfaces@postgresql.org
Cc: tgl@sss.pgh.pa.us, ken@ori-ind.com, peter_e@gmx.net
Subject: Re: [INTERFACES] pg_pwd problem, 2nd try
In-Reply-To: <26301.951261706@sss.pgh.pa.us>
* 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