Обсуждение: Authentication Woes

Hello,

After installing the latest cvs tree this morning, I cannot use
createuser and createdb. They break when trying to run psql. I can
connect with psql to the template1 database after setting up hba to use
password authentication and starting it with the -u option.

Does the hba still use trust and ident as well? Is there a primer on the
new authentication scheme?

I am moving up from 6.1.0 on Linux.

Thanks,


-James

On Tue, 20 Jan 1998, James Hughes wrote:

>
> Hello,
>
> After installing the latest cvs tree this morning, I cannot use
> createuser and createdb. They break when trying to run psql. I can
> connect with psql to the template1 database after setting up hba to use
> password authentication and starting it with the -u option.
>
> Does the hba still use trust and ident as well? Is there a primer on the
> new authentication scheme?
>
> I am moving up from 6.1.0 on Linux.

    v6.1.0 would have used TCP/IP for communications exclusively...
v6.3 moved to using Unix Domain Sockets as default, with TCP/IP disabled
by default.  To "mirror" the old behavior, add the -i option to your
startup script and youshould be okay...

On Tue, 20 Jan 1998, The Hermit Hacker wrote:

>
>     v6.1.0 would have used TCP/IP for communications exclusively...
> v6.3 moved to using Unix Domain Sockets as default, with TCP/IP disabled
> by default.  To "mirror" the old behavior, add the -i option to your
> startup script and youshould be okay...
>
>

OK, I should have said that the only way I can run psql is after making
an entry in pg_hba.conf to enable passwords, starting the postmaster
with the "-i" option then using the "-u" option with psql. The
createuser and createdb scripts will not run regardless.

Maybe I have other problems?? I am going to dig a little bit deeper :)


-James

On Tue, 20 Jan 1998, James Hughes wrote:

>
>
> On Tue, 20 Jan 1998, The Hermit Hacker wrote:
>
> >
> >     v6.1.0 would have used TCP/IP for communications exclusively...
> > v6.3 moved to using Unix Domain Sockets as default, with TCP/IP disabled
> > by default.  To "mirror" the old behavior, add the -i option to your
> > startup script and youshould be okay...
> >
> >
>
> OK, I should have said that the only way I can run psql is after making
> an entry in pg_hba.conf to enable passwords, starting the postmaster
> with the "-i" option then using the "-u" option with psql. The
> createuser and createdb scripts will not run regardless.
>
> Maybe I have other problems?? I am going to dig a little bit deeper :)

I have the same problem with 6.2.1. Authentication using passwords works,
but createuser (and probably the other scripts) fail. 'createuser -a
password' fails to use -u to actually ask for username/password. To
prevent having to type this 10 times during createuser, you could get it
from the script and then do 'echo "username\npassword" | psql ...'. I
tried this on another program (one of mine which uses the
prompt_for_password function from psql) and it works.

Maarten

_____________________________________________________________________________
|     Maarten Boekhold, Faculty of Electrical Engineering TU Delft,   NL    |
|           Computer Architecture and Digital Technique section             |
|                          M.Boekhold@et.tudelft.nl                         |
-----------------------------------------------------------------------------