On 01/21/2011 08:11 AM, Mark Constable wrote:
Package: courier-mta
Version: 0.65.0-3
Severity: normal
It seems this default setting may contradict RFC 3493.
On 01/20/2011 03:31 PM, Sam Varshavchik wrote:
Courier's code relies on being able to use IPv6 sockets to connect to
either IPv4 or IPv6 addresses. There is no way to configure that an IPv4
socket be used for IPv4 addresses, and IPv6 sockets for IPv6 addresses.
Doing something like this requires some code rewriting.
Wouldn't the easiest fix be to use IPV6_V6ONLY mentioned in section 5.3
of RFC 3493?
No, that's something that's unrelated.
But RFC 3493 also serves as a clear counterexample to what Debian's doing.
The language in section 3.7 is just as clear as day:
Applications may use AF_INET6 sockets to open TCP connections to IPv4
nodes, or send UDP packets to IPv4 nodes, by simply encoding the
destination's IPv4 address as an IPv4-mapped IPv6 address, and
passing that address, within a sockaddr_in6 structure, in the
connect() or sendto() call.
The upstream author said this issue will be next on his "chopping block".
Regards
Racke
--
LinuXia Systems => http://www.linuxia.de/
Expert Interchange Consulting and System Administration
ICDEVGROUP => http://www.icdevgroup.org/
Interchange Development Team
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
