On Mon, 24 Sep 2012, Jon Trulson wrote:
> If I read this right, the connection will only be rejected if a
> request come in over IP6 - which should not be able to happen with
> current CDE, right?
Depending on your operating system + libc combination you may
send an IPv4 connection to (x)inetd from the ToolTalk client
and yet the daemon will receive a dualstack socket, because
(x)inetd supports both. In FreeBSD's /etc/inetd.conf you can
say "rpc/udp4" or something like that:
The protocol must be a valid protocol or ``unix''. Examples are ``tcp''
or ``udp'', both of which imply IPv4 for backward compatibility. The
names ``tcp4'' and ``udp4'' specify IPv4 only. The names ``tcp6'' and
``udp6'' specify IPv6 only. The names ``tcp46'' and ``udp46'' specify
that the entry accepts both IPv4 and IPv6 connections via a wildcard
AF_INET6 socket. Rpc based services are specified with the ``rpc/tcp''
or ``rpc/udp'' service type. One can use specify IPv4 and/or IPv6 with
the 4, 6 or 46 suffix, for example ``rpc/tcp6'' or ``rpc/udp46''. TCPMUX
services must use ``tcp'', ``tcp4'', ``tcp6'' or ``tcp46''.
I guess that xinetd can do exactly the same. There is some
heavy discussion about dual stack socket in the community,
OpenBSD doesn't have them enabled (at least be default),
FreeBSD can have them switched off using kernel tuning parameter (they
are on by default).
//Marcin
------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and
threat landscape has changed and how IT managers can respond. Discussions
will include endpoint security, mobile security and the latest in malware
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
cdesktopenv-devel mailing list
cdesktopenv-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/cdesktopenv-devel
