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]

Date:	Wed, 14 May 2008 20:47:40 +0300
From:	Rémi Denis-Courmont <rdenis@...phalempin.com>
To:	Ulrich Drepper <drepper@...hat.com>
Cc:	Gerrit Renker <gerrit@....abdn.ac.uk>,
	Arnaldo Carvalho de Melo <acme@...hat.com>,
	David Stevens <dlstevens@...ibm.com>,
	David Miller <davem@...emloft.net>, dccp@...r.kernel.org,
	netdev@...r.kernel.org
Subject: Re: [RFC] [DCCP]: Deprecate SOCK_DCCP in favour of SOCK_DGRAM

Le Tuesday 13 May 2008 22:14:07 Ulrich Drepper, vous avez écrit :
> Rémi Denis-Courmont wrote:
> > In any case, getaddrinfo() should be patched to
> > [...]
>
> What should be the behavior is socktype and protocol are zero?  Should
> these two types be returned by default?  What others?  So far we return
> TCP, UDP, and raw socket information.  I'd rather keep the list short
> but since we already have raw sockets in there (because they are in
> POSIX) I won't reject anything that's more useful than raw sockets.

Well... I've always wondered what the use of both zeroes was supposed to be.

In AI_PASSIVE mode, it makes no sense, since there is no way you can handle 
passive SOCK_STREAM sockets (bind+listen+accept) and "passive" SOCK_DGRAM 
sockets in any common way (bind+recvfrom+sendto).

Even in active mode (connect+send), I cannot figure out how to share 
SOCK_STREAM code with SOCK_DGRAM code, given the incompatible end-of-file and 
datagram boundaries semantics (or lack thereof).

Hence, it seems that both zeroes is only of use to enumerate the supported 
protocol (yeah right...). If that's so adding DCCP and even UDP-Lite would be 
OK, even though they are corner-case protocols. Do you intend to 
implement "dccp" when parsing /etc/services, though?

Frankly, I have no definite answer, and I'm not any kind of standard body to 
make one in the first place :P

-- 
Rémi Denis-Courmont
http://www.remlab.net/
--
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