On Thu, April 25, 2013 20:26, Joseph wrote:
On 04/25/13 18:57, J. Roeleveld wrote:
So pg_hba.conf only controls direct connections to postgreSQL.
Correct.
Since apache group is in postgres user; apache was given permission
to
access the database in this case py-passing the setting in
J == Joseph syscon...@gmail.com writes:
J In my pg_hba.conf I have:
J localall all trust
J hostall all 127.0.0.1/32trust
J I was under impression that this is configuration is for localhost
On 04/26/13 20:25, James Cloos wrote:
J == Joseph syscon...@gmail.com writes:
J In my pg_hba.conf I have:
J local all all trust
J hostall all 127.0.0.1/32trust
J I was under impression that this is
On Thu, April 25, 2013 07:48, Joseph wrote:
SNIP
I just tried as you suggested, the only active line in: pg_hba.conf
local all all trust
anything else is commented out. I restarted the server but I still can
connect to postgresql from another computer via Firefox.
Joseph,
Let
On Thu, April 25, 2013 01:48, Joseph wrote:
On 04/24/13 22:27, J. Roeleveld wrote:
[snip]
Thank you for explanation.
That is what I'm confused about. When I connect to pstgresql
database from the same machine as postgres is running on I can
understand.
It is a local connection from localhost
On 04/25/13 09:10, J. Roeleveld wrote:
On Thu, April 25, 2013 07:48, Joseph wrote:
SNIP
I just tried as you suggested, the only active line in: pg_hba.conf
local all all trust
anything else is commented out. I restarted the server but I still can
connect to postgresql from
On Thu, April 25, 2013 14:35, Joseph wrote:
On 04/25/13 09:10, J. Roeleveld wrote:
On Thu, April 25, 2013 07:48, Joseph wrote:
SNIP
I just tried as you suggested, the only active line in: pg_hba.conf
local all all trust
anything else is commented out. I restarted the server but
On 04/25/13 18:57, J. Roeleveld wrote:
So pg_hba.conf only controls direct connections to postgreSQL.
Correct.
Since apache group is in postgres user; apache was given permission to
access the database in this case py-passing the setting in pg_hba.conf
Wrong, Postgresql does not check
On 04/24/13 07:11, J. Roeleveld wrote:
On Wed, April 24, 2013 00:16, Joseph wrote:
On 04/23/13 20:10, J. Roeleveld wrote:
SNIP
I am guessing Apache is running on the same machine as your Postgresql
server?
In this case. The connection will always originate from localhost and
Postgresql is
Joseph syscon...@gmail.com wrote:
On 04/24/13 07:11, J. Roeleveld wrote:
On Wed, April 24, 2013 00:16, Joseph wrote:
On 04/23/13 20:10, J. Roeleveld wrote:
SNIP
I am guessing Apache is running on the same machine as your
Postgresql
server?
In this case. The connection will always originate
On 04/24/13 22:27, J. Roeleveld wrote:
[snip]
Thank you for explanation.
That is what I'm confused about. When I connect to pstgresql
database from the same machine as postgres is running on I can
understand.
It is a local connection from localhost (127.0.0.1) so everybody is
allowed but I
On 04/24/13 22:27, J. Roeleveld wrote:
The connection to the database is done by apache. Apache connects from the
server where Apache is running.
Postgresql does not know nor even care where the connection to apache
originates from. It only sees apache connecting to it.
If you want to
On 4/24/2013 19:23, Joseph wrote:
The above is not correct as users from any machine on a local network
can connect to my database.
In the scenario you described, as Joost explained, the users on your
network are *not* connecting to your database; they are connecting to a
website. The web
On 04/25/13 00:16, Dustin C. Hatch wrote:
On 4/24/2013 19:23, Joseph wrote:
The above is not correct as users from any machine on a local network
can connect to my database.
In the scenario you described, as Joost explained, the users on your
network are *not* connecting to your database;
On Tue, April 23, 2013 02:17, Joseph wrote:
In my pg_hba.conf I have:
local all all trust
hostall all 127.0.0.1/32trust
I was under impression that this is configuration is for localhost
127.0.0.1 access
On 04/23/13 10:07, J. Roeleveld wrote:
On Tue, April 23, 2013 02:17, Joseph wrote:
In my pg_hba.conf I have:
local all all trust
hostall all 127.0.0.1/32trust
I was under impression that this is
On Tue, Apr 23, 2013 at 8:37 AM, Joseph syscon...@gmail.com wrote:
Even with a single line in pg_hba.conf
local all all trust
all other machine on the network can connect to my postgresql database.
did you restart postgresql? editing pg_hba.conf requires a restart to take
effect
--
On Tue, April 23, 2013 14:37, Joseph wrote:
On 04/23/13 10:07, J. Roeleveld wrote:
On Tue, April 23, 2013 02:17, Joseph wrote:
In my pg_hba.conf I have:
local all all trust
hostall all 127.0.0.1/32
On 04/23/13 15:57, J. Roeleveld wrote:
On Tue, April 23, 2013 14:37, Joseph wrote:
On 04/23/13 10:07, J. Roeleveld wrote:
On Tue, April 23, 2013 02:17, Joseph wrote:
In my pg_hba.conf I have:
local all all trust
hostall all
Joseph syscon...@gmail.com wrote:
On 04/23/13 15:57, J. Roeleveld wrote:
On Tue, April 23, 2013 14:37, Joseph wrote:
On 04/23/13 10:07, J. Roeleveld wrote:
On Tue, April 23, 2013 02:17, Joseph wrote:
In my pg_hba.conf I have:
local all all
On 04/23/13 20:10, J. Roeleveld wrote:
[snip]
I'm using SQL-Ledger (firefox) to access the postgresql.
Brief history:
I had a problem in the past when I upgraded to posgresql-9.1, all of a
sudden I could not access the sql-ledger.
The solution was to add postgres group to apache user.
The
On Wed, April 24, 2013 00:16, Joseph wrote:
On 04/23/13 20:10, J. Roeleveld wrote:
SNIP
I am guessing Apache is running on the same machine as your Postgresql
server?
In this case. The connection will always originate from localhost and
Postgresql is behaving as it should.
You will need to
In my pg_hba.conf I have:
local all all trust
hostall all 127.0.0.1/32trust
I was under impression that this is configuration is for localhost 127.0.0.1
access only.
But to my surprise I can access my
23 matches
Mail list logo
