Re: [HACKERS] pg_hba.conf hostname todo

2006-12-27 Thread Tom Lane
Stephen Frost <[EMAIL PROTECTED]> writes: > While a wildcard does make sense (ie: www*.postgresql.org), I would > generally expect 'commandprompt.com' to mean '*.commandprompt.com' > implicitly. No, that would be a really bad idea. It's not unlikely that commandprompt.com refers to a specific hos

Re: [HACKERS] pg_hba.conf hostname todo

2006-12-27 Thread Andrew Dunstan
Stephen Frost wrote: * Andrew Dunstan ([EMAIL PROTECTED]) wrote: Before we rehearse the discussion we had in June again, please review it. It ended on these sensible words from Tom at http://archives.postgresql.org/pgsql-hackers/2006-02/msg00550.php : I'd have to disagree with this se

Re: [HACKERS] pg_hba.conf hostname todo

2006-12-27 Thread Stephen Frost
* Andrew Dunstan ([EMAIL PROTECTED]) wrote: > Before we rehearse the discussion we had in June again, please review > it. It ended on these sensible words from Tom at > http://archives.postgresql.org/pgsql-hackers/2006-02/msg00550.php : I'd have to disagree with this sentiment and agree with Gre

Re: [HACKERS] pg_hba.conf hostname todo

2006-12-27 Thread Andrew Dunstan
Joshua D. Drake wrote: Hello, Per the TODO list: Allow pg_hba.conf to specify host names along with IP addresses Host name lookup could occur when the postmaster reads the pg_hba.conf file, or when the backend starts. Another solution would be to reverse lookup the connection IP and check th

Re: [HACKERS] pg_hba.conf hostname todo

2006-12-27 Thread Joshua D. Drake
On Wed, 2006-12-27 at 17:02 -0500, Stephen Frost wrote: > * Joshua D. Drake ([EMAIL PROTECTED]) wrote: > > On Wed, 2006-12-27 at 16:41 -0500, Stephen Frost wrote: > > > I'm inclined towards doing the reverse-DNS of the connecting IP and then > > > checking that the forward of that matches. > > > >

Re: [HACKERS] pg_hba.conf hostname todo

2006-12-27 Thread Steve Atkins
On Dec 27, 2006, at 1:47 PM, Joshua D. Drake wrote: On Wed, 2006-12-27 at 16:41 -0500, Stephen Frost wrote: * Joshua D. Drake ([EMAIL PROTECTED]) wrote: Allow pg_hba.conf to specify host names along with IP addresses Excellent. Host name lookup could occur when the postmaster reads the p

Re: [HACKERS] pg_hba.conf hostname todo

2006-12-27 Thread Stephen Frost
* Joshua D. Drake ([EMAIL PROTECTED]) wrote: > On Wed, 2006-12-27 at 16:41 -0500, Stephen Frost wrote: > > I'm inclined towards doing the reverse-DNS of the connecting IP and then > > checking that the forward of that matches. > > Hmm what if it doesn't? Which is the case any many scenario. My tho

Re: [HACKERS] pg_hba.conf hostname todo

2006-12-27 Thread Magnus Hagander
>>> Host name lookup could occur when the postmaster reads the pg_hba.conf >>> file, or when the backend starts. Another solution would be to reverse >>> lookup the connection IP and check that hostname against the host names >>> in pg_hba.conf. We could also then check that the host name maps to t

Re: [HACKERS] pg_hba.conf hostname todo

2006-12-27 Thread Joshua D. Drake
On Wed, 2006-12-27 at 16:41 -0500, Stephen Frost wrote: > * Joshua D. Drake ([EMAIL PROTECTED]) wrote: > > Allow pg_hba.conf to specify host names along with IP addresses > > Excellent. > > > Host name lookup could occur when the postmaster reads the pg_hba.conf > > file, or when the backend sta

Re: [HACKERS] pg_hba.conf hostname todo

2006-12-27 Thread Stephen Frost
* Joshua D. Drake ([EMAIL PROTECTED]) wrote: > Allow pg_hba.conf to specify host names along with IP addresses Excellent. > Host name lookup could occur when the postmaster reads the pg_hba.conf > file, or when the backend starts. Another solution would be to reverse > lookup the connection IP a