Date: Thu, 20 Nov 2014 20:10:05 +0000 From: bugzilla-noreply@freebsd.org To: freebsd-bugs@FreeBSD.org Subject: [Bug 195231] New: ssh tries AF_INET6 even when system is built with NO_INET6 [patch] Message-ID: <bug-195231-8@https.bugs.freebsd.org/bugzilla/>
next in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=195231 Bug ID: 195231 Summary: ssh tries AF_INET6 even when system is built with NO_INET6 [patch] Product: Base System Version: 10.1-STABLE Hardware: Any OS: Any Status: Needs Triage Severity: Affects Some People Priority: --- Component: bin Assignee: freebsd-bugs@FreeBSD.org Reporter: mi@ALDAN.algebra.com Created attachment 149652 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=149652&action=edit Patch secure/usr.bin/ssh and crypto/openssh to skip IPv6 addresses I build my world with NO_INET6 set -- until my ISP offers IPv6, there is just no point. After upgrading to 10.1, one of the cronjobs here started to generate (and e-mail) a warning: socket: Address family not supported by protocol family The warning comes from crypto/openssh/sshconnect.c and the attached patch shuts it off. It seems necessary to patch the imported source (of OpenSSH), but I can't think of another way to do it properly... Maybe, the resolver should not return the AAAA-records on non-INET6 systems, but that seems bogus: the records exist and the resolver ought to return them without trying to foresee, how the caller might (mis)use them. Please, review the attached patch. It changes the existing if into a switch making it easier to #ifdef individual options later (some day we might have a NO_INET4 option). -- You are receiving this mail because: You are the assignee for the bug.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-195231-8>