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: <20080513134631.GA7024@gerrit.erg.abdn.ac.uk>
Date:	Tue, 13 May 2008 14:46:31 +0100
From:	Gerrit Renker <gerrit@....abdn.ac.uk>
To:	Remi Denis-Courmont <rdenis@...phalempin.com>
Cc:	netdev@...r.kernel.org, dccp@...r.kernel.org,
	Arnaldo <acme@...hat.com>
Subject: Re: [RFC] [DCCP]: Deprecate SOCK_DCCP in favour of SOCK_DGRAM

| 
| DCCP clearly fails the POSIX definition of SOCK_DGRAM in different ways.
| 
| I think this is not a good idea.
| 
Thanks for the clarification. Even in Posix, datagram = connection-less.
Plus the issues with older kernel releases. Question resolved, no SOCK_DGRAM.

| > It also relieves the libc writers from having to support another socket
| > type.
| 
| As long as SOCK_DCCP-or-whatever is not automatically selected when
| ai_socktype is nul, this should be both easy to implement in libc *and*
| backward compatible (applications will not try to use DCCP implicitly).
| 
There are two possibilities:
 * as additional supported protocol (there are many new transport
   protocols, perhaps there is some kind of modular support),
 * if DCCP service codes are part of the lookup, then getting library
   support can take longer (algorithm changes).

Both may take a while until available. In the meantime it would be good
to find some smart workaround for getaddrinfo, as changes in the internals
so far required to fix applications several times.
--
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