aboutsummaryrefslogtreecommitdiffstats
path: root/erts/configure.in
diff options
context:
space:
mode:
authorRaimo Niskanen <[email protected]>2010-12-02 16:49:19 +0100
committerRaimo Niskanen <[email protected]>2010-12-02 16:49:19 +0100
commit0d79832e450c49e51f5fd7149f5f72930ef1f966 (patch)
treee6dccd01323eee60fed8551cc15730c8b3405919 /erts/configure.in
parent2a01369408762b651785083aad8d3778bfe30e71 (diff)
downloadotp-0d79832e450c49e51f5fd7149f5f72930ef1f966.tar.gz
otp-0d79832e450c49e51f5fd7149f5f72930ef1f966.tar.bz2
otp-0d79832e450c49e51f5fd7149f5f72930ef1f966.zip
Stop using uncertain flags for getaddrinfo()
The AI_V4MAPPED flag is falling out of grace in modern IPv6 stacks, for security reasons, e.g. FreeBSD do not document it any longer. The AI_ADDRCONFIG flag have got unclear semantics on the same OS.
Diffstat (limited to 'erts/configure.in')
-rw-r--r--erts/configure.in4
1 files changed, 0 insertions, 4 deletions
diff --git a/erts/configure.in b/erts/configure.in
index 544ff9790a..f99a86a899 100644
--- a/erts/configure.in
+++ b/erts/configure.in
@@ -1734,11 +1734,7 @@ if test $have_getaddrinfo = yes; then
[
struct addrinfo hints, *ai;
memset(&hints, 0, sizeof(hints));
-#ifndef __WIN32__
- hints.ai_flags = (AI_CANONNAME|AI_V4MAPPED|AI_ADDRCONFIG);
-#else
hints.ai_flags = AI_CANONNAME;
-#endif
hints.ai_socktype = SOCK_STREAM;
hints.ai_family = AF_INET6;
if (getaddrinfo("::", NULL, &hints, &ai) == 0) {