Bug#164768: libc: IPv6 still not correct.
On Thu, Oct 17, 2002 at 10:49:06AM +0100, Jonathan Amery wrote:
> > On Wed, Oct 16, 2002 at 09:50:10PM +0100, Matthew Vernon wrote:
> > > [Please preserve the X-Debbugs-CC line]
> ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
> > > Ben Collins writes:
> > > > And as I've said in the past numerous times. The fact that every other
> > > > IPv6 using program (including apache, bind, telnet, etc.) get this
> > > > right, and sshd doesn't, isn't libc's fault.
> > > >
> > > > I've pushed this over to sshd, and we wont accept the error here.
> > > ssh is using getpeername() in accordance with the manual. The
> > > structure that getpeername() returns is causing gatenameinfo() to
> > > barf. That seems to me to be unambiguously a bug.
> > Only because kernel 2.2 is broken, not becuase glibc is. The reason is
> > because kernel 2.2 uses an old obsolete api.
>
> Firstly - this is not a bug in sshd - sshd is interacting with libc's
> API in good faith.
>
> Secondly - it is the job of libc to ensure that the APIs it exposes
> function correctly. If the IPv6 code in 2.2 is incompatible with
> these APIs then libc should not be attempting to provide IPv6 on
> systems with a 2.2 kernel, rather than functioning outside of the APIs
> that it claims to implement.
No, sshd should be checking the validity of the data that is returned to
it.
--
Debian - http://www.debian.org/
Linux 1394 - http://www.linux1394.org/
Subversion - http://subversion.tigris.org/
Deqo - http://www.deqo.com/
Reply to: