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: <20080514080942.GB4462@gerrit.erg.abdn.ac.uk>
Date:	Wed, 14 May 2008 09:09:42 +0100
From:	Gerrit Renker <gerrit@....abdn.ac.uk>
To:	Ulrich Drepper <drepper@...hat.com>
Cc:	R?mi Denis-Courmont <rdenis@...phalempin.com>,
	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

| 
| 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.
| 
| - --
RFC 3493 says that 0 for socktype/protocol means that caller will accept
any socket type / protocol, so presumably this does include DCCP and UDP-Lite.

It would be just _great_ if getaddrinfo() could support Remi's cases for DCCP
(RFC 4340) and UDP-Lite (RFC 3828). So far it is only possible to get an
address by "cheating", i.e. pretending to getaddrinfo to be TCP or UDP. This
does not really work well and still causes lots of problems/broken applications.

Gerrit
--
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