Thread: use inet_pton() instead of inet_addr() for ipv4/6

Hi, our regular package checking discovered that in postgresql-odbc is
using inet_addr() call (which is not ipv6 compliant).  I tried to look at
it and it was used just for parsing of ipv4 addresses.  It is not a big
deal (the worst thing what can happen is that ipv6 addresses will cost a
little bit more time to be resolved).

Better solution would be imo to use inet_pton() call for both ipv4 and
ipv6 address families.  Patch is attached, any comment is welcome!

Pavel

Hi Pavel,

(2013/12/06 19:58), Pavel Raiskup wrote:
> Hi, our regular package checking discovered that in postgresql-odbc is
> using inet_addr() call (which is not ipv6 compliant).  I tried to look at
> it and it was used just for parsing of ipv4 addresses.  It is not a big
> deal (the worst thing what can happen is that ipv6 addresses will cost a
> little bit more time to be resolved).
>
> Better solution would be imo to use inet_pton() call for both ipv4 and
> ipv6 address families.  Patch is attached, any comment is welcome!

Thanks for the patch.
I will take care of it.

regards,
Hiroshi Inoue




--
I am using the free version of SPAMfighter.
SPAMfighter has removed 1069 of my spam emails to date.
Get the free SPAMfighter here: http://www.spamfighter.com/len

Do you have a slow PC? Try a Free scan
http://www.spamfighter.com/SLOW-PCfighter?cid=sigen