| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Stephen Frost <sfrost(at)snowman(dot)net> |
| Cc: | Magnus Hagander <magnus(at)hagander(dot)net>, Christopher Head <chris2k01(at)hotmail(dot)com>, pgsql-bugs <pgsql-bugs(at)postgresql(dot)org> |
| Subject: | Re: BUG #5559: Full SSL verification fails when hostaddr provided |
| Date: | 2010-07-15 15:58:06 |
| Message-ID: | 6245.1279209486@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
Stephen Frost <sfrost(at)snowman(dot)net> writes:
> Reviewing what's currently on developer.postgresql.org, here's what I
> think the docs would read and what the associated code behavior should
> be (which I think it's pretty close to already, but perhaps not
> entirely..):
I think this is overcomplicated and probably wrong in detail.
I suggest that we document hostaddr as being an auxiliary field that is
not intended to be the primary source of the host name, but merely saves
libpq from having to do a forward DNS lookup. In some cases it will
work to supply hostaddr without host, but in others it won't. We should
also state that supplying it does not guarantee no DNS lookups occur,
because these external auth libraries will do one anyway.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Stephen Frost | 2010-07-15 20:03:05 | Re: BUG #5559: Full SSL verification fails when hostaddr provided |
| Previous Message | Stephen Frost | 2010-07-15 12:59:11 | Re: BUG #5559: Full SSL verification fails when hostaddr provided |