NetBSD Problem Report #53748

From martin@duskware.de  Tue Nov 27 19:15:58 2018
Return-Path: <martin@duskware.de>
Received: from mail.netbsd.org (mail.netbsd.org [199.233.217.200])
	(using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
	(Client CN "mail.NetBSD.org", Issuer "mail.NetBSD.org CA" (not verified))
	by mollari.NetBSD.org (Postfix) with ESMTPS id 823367A1CC
	for <gnats-bugs@gnats.NetBSD.org>; Tue, 27 Nov 2018 19:15:58 +0000 (UTC)
From: martin@NetBSD.org
Reply-To: martin@NetBSD.org
To: gnats-bugs@NetBSD.org
Subject: ssh/sshd unusable on i386/current
X-Send-Pr-Version: 3.95

>Number:         53748
>Category:       bin
>Synopsis:       ssh/sshd unusable on i386/current
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    bin-bug-people
>State:          closed
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Tue Nov 27 19:20:00 +0000 2018
>Closed-Date:    Thu Feb 21 12:55:42 +0000 2019
>Last-Modified:  Thu Feb 21 12:55:42 +0000 2019
>Originator:     Martin Husemann
>Release:        NetBSD 8.99.25
>Organization:
The NetBSD Foundation, Inc.
>Environment:
System: NetBSD night-porter.duskware.de 8.99.25 NetBSD 8.99.25 (PORTER) #7: Thu Nov 8 10:00:36 CET 2018 martin@seven-days-to-the-wolves.aprisoft.de:/work/src/sys/arch/i386/compile/PORTER i386
Architecture: i386
Machine: i386
>Description:

Since (I believe) the last openssl update, sshd and ssh on this
machine are unusable. Sshd becomes unresponsive, it takes ages
to log in or attempts time out. Once loged in, everything works
fine for that session.
Suspecting broken BN lib code for the KEX phase.

My cpu is old, but not exactly that slow (even my mac68k can do ssh
sessions, even if initial log in takes 70s, but that is on a 40 MHz
machine, not a GHZ one)

CPU on this i386:

cpu0 at mainbus0 apid 0
cpu0: Intel(R) Pentium(R) 4 CPU 2.60GHz, id 0xf29
cpu0: package 0, core 0, smt 0
cpu1 at mainbus0 apid 1
cpu1: Intel(R) Pentium(R) 4 CPU 2.60GHz, id 0xf29
cpu1: package 0, core 0, smt 1


>How-To-Repeat:
run -current, try to ssh in ?
Can anyoe reproduce it or is there some other failure specific to my
machine?

>Fix:
n/a

>Release-Note:

>Audit-Trail:

State-Changed-From-To: open->closed
State-Changed-By: martin@NetBSD.org
State-Changed-When: Thu, 21 Feb 2019 12:55:42 +0000
State-Changed-Why:
Fallout from broken network hardware


>Unformatted:

Home	PR Database Search