Good tip! Thank you.
-Original Message-
From: pgsql-general-ow...@postgresql.org
[mailto:pgsql-general-ow...@postgresql.org] On Behalf Of John R Pierce
Sent: Friday, February 22, 2013 2:35 PM
To: pgsql-general@postgresql.org
Subject: Re: [GENERAL] confirming security.
On 2/22/2013 8
On 2/22/2013 8:13 AM, Maz Mohammadi wrote:
Ahhh yesit is now...
===
# TYPE DATABASEUSERADDRESS METHOD
# "local" is for Unix domain socket connections only
#local all all trust
# IPv4 local connecti
..@gmail.com]
Sent: Friday, February 22, 2013 10:58 AM
To: Maz Mohammadi
Cc: John R Pierce; pgsql-general@postgresql.org
Subject: Re: [GENERAL] confirming security.
On 02/22/2013 07:50 AM, Maz Mohammadi wrote:
> Thx John,
>
> It got me a long way. I actually have a more complex installation
On 02/22/2013 07:50 AM, Maz Mohammadi wrote:
Thx John,
It got me a long way. I actually have a more complex installation (I
think) that I originally thought on my test linux box. Looks like all
the files that I modify are under /var/lib/post../coord.
I added the line.. to pg_hba.conf
hostssl
21, 2013 11:04 PM
To: pgsql-general@postgresql.org
Subject: Re: [GENERAL] confirming security.
On 2/21/2013 7:55 PM, Maz Mohammadi wrote:
When I start the server, there is no change in the authentication. I can still
login using psql for the same person.
did you disable other authentication methods in pg
On 2/21/2013 7:55 PM, Maz Mohammadi wrote:
When I start the server, there is no change in the authentication. I
can still login using psql for the same person.
did you disable other authentication methods in pg_hba.conf ? I
would leave the LOCAL line as peer, and use ssl for HOST line
