Yes! that's it, thanks heaps.
I had a .pgpass file in the home directory of the client PC. It's
possible PgAdmin III or some other program created it.
Thanks heaps, now I know it was not actually a security issue with my
server.
On Wed, 2007-02-28 at 17:15 -0800, Jeff Frost wrote:
On Thu, 1
Hi all,
I have a server (Ubuntu 6.10 to be exact) running PostgresQL 8.1.4.
On that server I have a user account, called ynui, and I also have a
postgres user called ynui, they have the same password. Now the
server's IP is 192.168.0.1
My main postgres conf has in it:
listen_addresses =
On Thu, 1 Mar 2007, Rob van der Linde wrote:
On that server I have a user account, called ynui, and I also have a
postgres user called ynui, they have the same password. Now the
server's IP is 192.168.0.1
My main postgres conf has in it:
listen_addresses = 'localhost,192.168.0.1'
my
Yes, pgadmin3 uses .pgpass to store its connection info - so that's your
likely culprit.
On Thu, 1 Mar 2007, Rob van der Linde wrote:
I had a .pgpass file in the home directory of the client PC. It's
possible PgAdmin III or some other program created it.
--
Jeff Frost, Owner [EMAIL
