From: | Andreas Pflug <pgadmin(at)pse-consulting(dot)de> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Andrew Dunstan <andrew(at)dunslane(dot)net>, pgsql-patches(at)postgresql(dot)org |
Subject: | Re: IPV4 addresses on IPV6 machines in pg_hba.conf |
Date: | 2003-09-05 21:46:04 |
Message-ID: | 3F59041C.1000709@pse-consulting.de |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-patches |
Tom Lane wrote:
>I thought this was still really messy, so I modified it to use a
>separate "promote v4 address to v6" subroutine. I've applied the
>attached patch (plus docs). It's not very well tested since I don't
>have an IPv6 setup here; please check that it does what you want.
>
It SEGVs. Reason is that the memcpy of the promote_v4_to_v6_XXX
functions assumes that the sockaddr_storage is large enough to hold an
IPV6 address, which appears to be not true. Since the struct isn't
created by a plain malloc() and returned by free(), but assembled by
getaddrinfo() according to the family's requirement, I don't see a way
how to fix this. IMHO the struct needs to be created officially by
getaddrinfo(), which will lead more or less the the same solution I
posted previously.
Regards,
Andreas
From | Date | Subject | |
---|---|---|---|
Next Message | Robert Treat | 2003-09-05 22:01:14 | Re: note on dropped columns in pg_attribute |
Previous Message | Tom Lane | 2003-09-05 21:40:57 | Re: note on dropped columns in pg_attribute |