From: "J. Roeleveld" <joost@antarean.org>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] PosgreSQL - pg_hba.conf localhost access only
Date: Thu, 25 Apr 2013 18:57:14 +0200 [thread overview]
Message-ID: <5143a65c1353774fbe6556e10d34612a.squirrel@www.antarean.org> (raw)
In-Reply-To: <20130425123519.GD24932@syscon7.inet>
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 I still can
>>> connect to postgresql from another computer via Firefox.
>>
>>Joseph,
>>
>>Let me put it in really simple terms:
>>1) Firefox is NOT a database client, it can NOT connect to a database
>>2) Firefox IS a webbrowser, it ONLY connects to a webserver
>>
>>This means, Postgresql will NOT see ANY connection made by Firefox.
>>
>>The website you have running ON TOP OFF apache makes the connection to
>>Postgresql.
>>
>>Eg. it goes like the following:
>>
>>User <-> Firefox <-> Apache/website <-> Postgresql
>>
>>Any of the above can ONLY see their immediate neighbour.
>>
>>--
>>Joost
>
> 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 group-ownership. Your pg_hba.conf file
will have a setting that allows Apache to connect.
> Is there a way to force sequence:
> Apache/website <-> pg_hba.conf <-> Postgresql
Postgresql will always read the pg_hba.conf file and use that to determine
who can and can not connect directly to Postgresql.
--
Joost
next prev parent reply other threads:[~2013-04-25 16:57 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-23 0:17 [gentoo-user] PosgreSQL - pg_hba.conf localhost access only Joseph
2013-04-23 8:07 ` J. Roeleveld
2013-04-23 12:37 ` Joseph
2013-04-23 13:44 ` Douglas J Hunley
2013-04-23 13:57 ` J. Roeleveld
2013-04-23 15:47 ` Joseph
2013-04-23 18:10 ` J. Roeleveld
2013-04-23 22:16 ` Joseph
2013-04-24 5:11 ` J. Roeleveld
2013-04-24 12:40 ` Joseph
2013-04-24 20:27 ` J. Roeleveld
2013-04-24 23:48 ` Joseph
2013-04-25 7:14 ` J. Roeleveld
2013-04-25 0:23 ` Joseph
2013-04-25 5:16 ` Dustin C. Hatch
2013-04-25 5:48 ` Joseph
2013-04-25 7:10 ` J. Roeleveld
2013-04-25 12:35 ` Joseph
2013-04-25 16:57 ` J. Roeleveld [this message]
2013-04-25 18:26 ` Joseph
2013-04-26 6:59 ` J. Roeleveld
2013-04-27 0:25 ` James Cloos
2013-04-27 1:11 ` Joseph
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5143a65c1353774fbe6556e10d34612a.squirrel@www.antarean.org \
--to=joost@antarean.org \
--cc=gentoo-user@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox