Обсуждение: Authentication by password

Hello,

I'm sure this has been covered before, but the ML archive search engine is
down (?!).

After telling postgresql not to trust anyone, but always use password/crypt
as the authenticaton method (pg_hdb.conf), I can't seem to get the
postmaster to authenticate against the right password.

What I've done is:

1) Create user U with createuser
2) Log in as postgres to a database A
3) UPDATE pg_user SET passwd='mypassword' WHERE usename='U';

But after that 'mypassword' is not accepted when trying to log in as user U.

What am I doing wrong?

I was thinking the passwords might be encrypted in the db; but then the
"password" authentication mechanism would be impossible, so that can't be it.

Thank you,

--
/ Peter Schuller, InfiDyne Technologies HB

PGP userID: 0x5584BD98 or 'Peter Schuller <peter.schuller@infidyne.com>'
Key retrival: Send an E-Mail to getpgpkey@scode.infidyne.com
E-Mail: peter.schuller@infidyne.com Web: http://scode.infidyne.com

ALTER USER postgres WITH PASSWORD 'yourpassword';

On Mon, 12 Mar 2001, Peter Schuller wrote:

> Hello,
>
> I'm sure this has been covered before, but the ML archive search engine is
> down (?!).
>
> After telling postgresql not to trust anyone, but always use password/crypt
> as the authenticaton method (pg_hdb.conf), I can't seem to get the
> postmaster to authenticate against the right password.
>
> What I've done is:
>
> 1) Create user U with createuser
> 2) Log in as postgres to a database A
> 3) UPDATE pg_user SET passwd='mypassword' WHERE usename='U';
>
> But after that 'mypassword' is not accepted when trying to log in as user U.
>
> What am I doing wrong?
>
> I was thinking the passwords might be encrypted in the db; but then the
> "password" authentication mechanism would be impossible, so that can't be it.
>
> Thank you,
>
>