full-disclosure - Re: Exploitation of unused IPv6-capabilities

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <87ab9mozlk.fsf@mid.deneb.enyo.de>
Date: Tue, 20 Jan 2009 14:51:03 +0100
From: Florian Weimer <fw@...eb.enyo.de>
To: Sebastian Krahmer <krahmer@...e.de>
Cc: "Lukas Th. Hey" <hey@...r.nl>, full-disclosure@...ts.grok.org.uk
Subject: Re: Exploitation of unused IPv6-capabilities

* Sebastian Krahmer:

> What do you mean by that? I looked at the glibc resolver,
> it might be that if getaddrinfo() does not get proper
> ai_family arguments of AF_INET, it will accept AAAA records.
> So, the application which thinks is using IPv4 DNS resolving
> will eventually connect using IPv6?

The original reason for using getaddrinfo was to make applications
IPv6-aware.  In order to push at least some traffic over IPv6,
getaddrinfo implementations typically prefer IPv6 over IPv4.  However,
this comes into play only if the name has got an AAAA in the first
place, which is still rare (except perhaps for DNS and mail servers).

_______________________________________________
Full-Disclosure - We believe in it.
Charter: http://lists.grok.org.uk/full-disclosure-charter.html
Hosted and sponsored by Secunia - http://secunia.com/