On Mon, 24 Sep 2012, Jon Trulson wrote:
> On Mon, 24 Sep 2012, Marcin Cieslak wrote:
>
> >
> > Would that make sense to add "flags = IPv4" for IPv6-enabled
> > systems (until of course our daemons support IPv6)?
> >
> > //Marcin
> >
>
> Will it matter?
I don't for for Linux and xinetd, but I had
to explicitly configure CDE RPC services to
be IPv4-only, otherwise they might get a AF_INET/AF_INET6
dual socket where localhost may appear as AF_INET6 ::1
lib/tt/bin/ttdbserverd/db_server_svc.C even explicitly
rejects such connections:
269 if (getsockname(0, (struct sockaddr *) &saddr, &asize) == 0) {
270
271 // We were given a socket. This means we were started
272 // from inetd.
273 if (saddr.sin_family != AF_INET) {
274 _tt_syslog(0, LOG_ERR, "saddr.sin_family != AF_I
NET");
275 exit(1);
276 }
277
278 start_mode = STARTED_FROM_INETD;
279 errstr = 0;
We have to stick with IPv4 until we switch to the proper TI-RPC API.
But maybe there is some magic in xinetd to prevent problems?
//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
