pg.ddx.io pgsql-interfaces@postgresql.org mailing list archive
help / color / mirror / Atom feedpg_pwd problem, 2nd try
3+ messages / 3 participants
[nested] [flat]
* pg_pwd problem, 2nd try
@ 2000-02-22 21:09 Ken J. Wright <ken@ori-ind.com>
0 siblings, 1 reply; 3+ messages in thread
From: Ken J. Wright @ 2000-02-22 21:09 UTC (permalink / raw)
To: pgsql-interfaces
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?
Ken
^ permalink raw reply [nested|flat] 3+ messages in thread
* Re: [INTERFACES] pg_pwd problem, 2nd try
@ 2000-02-22 23:21 Tom Lane <tgl@sss.pgh.pa.us>
parent: Ken J. Wright <ken@ori-ind.com>
0 siblings, 1 reply; 3+ messages in thread
From: Tom Lane @ 2000-02-22 23:21 UTC (permalink / raw)
To: Ken J. Wright <ken@ori-ind.com>; +Cc: Peter Eisentraut <peter_e@gmx.net>; pgsql-interfaces
"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
^ permalink raw reply [nested|flat] 3+ messages in thread
* Re: [INTERFACES] pg_pwd problem, 2nd try
@ 2000-02-23 01:29 Peter Eisentraut <peter_e@gmx.net>
parent: Tom Lane <tgl@sss.pgh.pa.us>
0 siblings, 0 replies; 3+ messages in thread
From: Peter Eisentraut @ 2000-02-23 01:29 UTC (permalink / raw)
To: Tom Lane <tgl@sss.pgh.pa.us>; +Cc: Ken J. Wright <ken@ori-ind.com>; pgsql-interfaces
On 2000-02-22, Tom Lane mentioned:
> "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?
Uh, you should not use pg_passwd to change pg_pwd. It should only be used
to create auxilliary password files for pg_hba.conf lines like
.... passwd my_separate_password_file
> Peter changed the backend's idea about the format of pg_pwd, but
Not really. Only the unused fields are filled in with dummies.
> I guess he forgot about pg_passwd ...
Unrelated. See above.
> I wonder whether we even need pg_passwd in its present form anymore.
> Maybe it should just issue an ALTER USER command?
Nope.
--
Peter Eisentraut Sernanders väg 10:115
peter_e@gmx.net 75262 Uppsala
http://yi.org/peter-e/ Sweden
^ permalink raw reply [nested|flat] 3+ messages in thread
end of thread, other threads:[~2000-02-23 01:29 UTC | newest]
Thread overview: 3+ messages (download: mbox mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
2000-02-22 21:09 pg_pwd problem, 2nd try Ken J. Wright <ken@ori-ind.com>
2000-02-22 23:21 ` Tom Lane <tgl@sss.pgh.pa.us>
2000-02-23 01:29 ` Peter Eisentraut <peter_e@gmx.net>
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