Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.debian.user > #238844 > unrolled thread

debian10/11 ssh from ipv6 address not in /etc/hosts.allow = sshd segfault segfault

Back to article view | Back to linux.debian.user

Contents

  debian10/11 ssh from ipv6 address not in /etc/hosts.allow = sshd  segfault segfault raf <debian@raf.org> - 2021-08-17 03:20 +0200
    Re: debian10/11 ssh from ipv6 address not in /etc/hosts.allow = sshd  segfault segfault Andy Smith <andy@strugglers.net> - 2021-08-19 18:30 +0200
      Re: debian10/11 ssh from ipv6 address not in /etc/hosts.allow = sshd  segfault segfault raf <debian@raf.org> - 2021-08-20 02:10 +0200

#238844 — debian10/11 ssh from ipv6 address not in /etc/hosts.allow = sshd segfault segfault

Hi,

I just noticed many many sshd segfaults listed in
/var/log/kern.log. There are two versions. They look
like this:

  sshd[1086]: segfault at 7fff615eaec8 ip
  00007ff2a586f42f sp 00007fff615eaed0 error 6 in
  libwrap.so.0.7.6[7ff2a586e000+5000]

  sshd[1094]: segfault at 7ffcd3ff6f08 ip
  00007f18d4f5dac7 sp 00007ffcd3ff6ed0 error 6 in
  libc-2.31.so[7f18d4f2a000+14b000]

The hex addresses are different each time, but the rest
is the same.

It happens every time there's an incoming ssh
connection attempt via IPv6 when the IPv6 address isn't
listed in /ertc/hosts.allow. There are many because
it's a cronned backup.

I am using /etc/hosts.allow for sshd and have a mixture
of IPv4 and IPv6 addresses in it.

When I added the IPv6 address in question to
/etc/hosts.allow, the segfaults stopped and the
connections worked.

This started 2 days before I upgraded to debian11 and
there was a different version number for libc (so it's
not new), but it's still happening with debian11.

It might be a bug in libwrap0 (whose version number
didn't change much), or in how openssh-server is using
it.

cheers,
raf

[toc] | [next] | [standalone]

#239051

Hello,

On Tue, Aug 17, 2021 at 11:17:05AM +1000, raf wrote:
> I just noticed many many sshd segfaults listed in
> /var/log/kern.log. There are two versions. They look
> like this:
> 
>   sshd[1086]: segfault at 7fff615eaec8 ip
>   00007ff2a586f42f sp 00007fff615eaed0 error 6 in
>   libwrap.so.0.7.6[7ff2a586e000+5000]
> 
>   sshd[1094]: segfault at 7ffcd3ff6f08 ip
>   00007f18d4f5dac7 sp 00007ffcd3ff6ed0 error 6 in
>   libc-2.31.so[7f18d4f2a000+14b000]

I think you should report this as a bug against openssh source
package and see if you get any assistance. As the segfaults happen
inside libwrap and libc it could end up being a bug in either of
those instead, or in how sshd uses them, but let's see.

Using "reportbug openssh-server" is probably the easiest.

Cheers,
Andy

-- 
https://bitfolk.com/ -- No-nonsense VPS hosting

[toc] | [prev] | [next] | [standalone]

#239072

On Thu, Aug 19, 2021 at 04:25:34PM +0000, Andy Smith <andy@strugglers.net> wrote:

> Hello,
> 
> On Tue, Aug 17, 2021 at 11:17:05AM +1000, raf wrote:
> > I just noticed many many sshd segfaults listed in
> > /var/log/kern.log. There are two versions. They look
> > like this:
> > 
> >   sshd[1086]: segfault at 7fff615eaec8 ip
> >   00007ff2a586f42f sp 00007fff615eaed0 error 6 in
> >   libwrap.so.0.7.6[7ff2a586e000+5000]
> > 
> >   sshd[1094]: segfault at 7ffcd3ff6f08 ip
> >   00007f18d4f5dac7 sp 00007ffcd3ff6ed0 error 6 in
> >   libc-2.31.so[7f18d4f2a000+14b000]
> 
> I think you should report this as a bug against openssh source
> package and see if you get any assistance. As the segfaults happen
> inside libwrap and libc it could end up being a bug in either of
> those instead, or in how sshd uses them, but let's see.
>
> Using "reportbug openssh-server" is probably the easiest.

> Cheers,
> Andy

Thanks. I did that already. I just posted it to the list as well
in case it helped others while waiting for a fix.

cheers,
raf

[toc] | [prev] | [standalone]

Back to top | Article view | linux.debian.user

csiph-web