On Sep 16, 2017, at 1:27 PM, Andy Goth <andrew.m.g...@gmail.com> wrote: > > Indeed, 1.1.0f is a version which includes the BIO_ADDR type, which is a > union containing struct sockaddr_in6 among others. I don't think there's any > question Fossil is trying to read an IPv6 address structure as if it were > IPv4.
Has anyone tried addressing this? I still see it on my Raspberry Pi running a recent version of Raspbian. The symptom is that Fossil claims to be talking to IP 2.0.1.187 during “sync” calls. Since I haven’t seen it on any of my 64-bit hosts, I’m guessing it has something to do with a peculiarity on 32-bit Linux. It also seems to require a fairly recent version of Linux. An old 32-bit CentOS 5 box (kernel ~10 years old) here doesn’t do it, nor does a recent Ubuntu 64-bit system, but current Raspbian on a Pi 3 does do it, which is a kissing cousin to Ubuntu. I’m dredging this old thread up in case someone can slide a fix for this into Fossil 2.5. I’m not especially bothered by it, but then, I don’t depend on watching the IP as a guard against spoofing. _______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
