netdev - Re: [RFC] [DCCP]: Deprecate SOCK_DCCP in favour of SOCK

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: <20080513093718.GA24185@gerrit.erg.abdn.ac.uk>
Date:	Tue, 13 May 2008 10:37:18 +0100
From:	Gerrit Renker <gerrit@....abdn.ac.uk>
To:	David Miller <davem@...emloft.net>
Cc:	netdev@...r.kernel.org, dccp@...r.kernel.org, acme@...hat.com
Subject: Re: [RFC] [DCCP]: Deprecate SOCK_DCCP in favour of SOCK_DGRAM

| 
| > Is there support for this change or are there reasons to keep SOCK_DCCP?
| 
| You'll have to accept it forever since there have been several
| kernel releases already with DCCP support added and there are
| applications out there.
| 
And maybe it is not necessary or worth to change it. 

But there is a problem, the cause is not necessarily the above:

 * using an ai_socktype=0 used to work for DCCP; on dual-stack hosts,
   IPv6 addresses were returned first, so that both IPv6 and IPv4
   clients (v6-mapped-v4) could connect to the server,

 * within the last three months there was a change in the lookup
   behaviour so that now IPv4 addresses are returned first on dual
   stack hosts when AF_UNSPEC is specified with ai_socktype=0,

 * changing preference values in /etc/gai.conf did not help,

 * the only fix was the following (pretend to be UDP):

	if (inSettings->mProtocol == IPPROTO_DCCP)
		hints.ai_socktype = SOCK_DGRAM;

Maybe there is a better fix for this.
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html