Received: from sss.sss.pgh.pa.us (sss.pgh.pa.us [206.210.65.6]) by hub.org (8.9.2/8.9.1) with ESMTP id KAA48626 for ; Wed, 10 Feb 1999 10:23:00 -0500 (EST) (envelope-from tgl@sss.pgh.pa.us) Received: from sss.sss.pgh.pa.us (localhost [127.0.0.1]) by sss.sss.pgh.pa.us (8.9.1/8.9.1) with ESMTP id KAA11083; Wed, 10 Feb 1999 10:22:16 -0500 (EST) To: Bob VonMoss cc: pgsql-interfaces@postgreSQL.org Subject: Re: [INTERFACES] Re: connecting: unix socket? Yes. TCPIP port? No.-i? Yes. In-reply-to: Your message of Wed, 10 Feb 1999 01:23:27 -0600 <36C133EE.87B0D643@bigfoot.com> Date: Wed, 10 Feb 1999 10:22:15 -0500 Message-ID: <11081.918660135@sss.pgh.pa.us> From: Tom Lane Bob VonMoss writes: > We've tried: > host my_db 0.0.0.0 0.0.0.0 ident sameuser As you already found out, that won't work if you're not running an ident daemon on your connecting machine. (You aren't *really* running with an 0.0.0.0 mask are you? That means anyone anywhere on the net can get into your database, if they can reach the machine it's on...) > host my_db 0.0.0.0 0.0.0.0 password sameuser See the documentation: # password: Authentication is done by matching a password supplied in clear # by the host. If AUTH_ARGUMENT is specified then the password # is compared with the user's entry in that file (in the $PGDATA # directory). See pg_passwd(1). If it is omitted then the # password is compared with the user's entry in the pg_shadow # table. Unless your admin made a file named "sameuser" to store Postgres passwords in, this will not work. I think you want to remove "sameuser". (Also, did he remember to set a Postgres password for you?) > I'm hoping that it will eventually work through JDBC, but it doesn't > work with > psql -h my-isp.com -d my_db > Same messages: "User authentication failed" Even if the host system were correctly configured for password authentication, this psql invocation would fail since you didn't supply a username and password. Need -u option. regards, tom lane