X-Recipient:	archive-cygwin AT delorie DOT com
DKIM-Filter:	OpenDKIM Filter v2.11.0 sourceware.org 73FC63992CBD
DKIM-Signature:	v=1; a=rsa-sha256; c=relaxed/relaxed; d=cygwin.com;
	s=default; t=1628181948;
	bh=hw5/bmZ/r5IH1ht4HsolGIDUZOh4YMRSbarJZP3s44I=;
	h=Date:To:Subject:In-Reply-To:References:List-Id:List-Unsubscribe:
	List-Archive:List-Post:List-Help:List-Subscribe:From:Reply-To:
	From;
	b=HeUYaBTI9TozJFBGndX4Di8xnuXlAEKMPRh17R6RwaLNFwm0rxn2/APzPTIfjlAa5
	l0eabcHK1mYvBDCgOnm0fGlk1jsiSLJSc6vY9yC6cXdZGzMdluUEHRBFExw2CnKI2K
	2rlyQmQOY+28phP9+3LbgiUGETVGC0w3hwsFT5ec=
X-Original-To:	cygwin AT cygwin DOT com
Delivered-To:	cygwin AT cygwin DOT com
DMARC-Filter:	OpenDMARC Filter v1.4.1 sourceware.org 161583992CA4
DKIM-Filter:	OpenDKIM Filter v2.10.3 conssluserg-05.nifty.com 175GhQCo002371
X-Nifty-SrcIP:	[110.4.221.123]
Date:	Fri, 6 Aug 2021 01:43:31 +0900
To:	cygwin AT cygwin DOT com
Subject:	Re: SSHD causes 100% CPU load
Message-Id:	<20210806014331.899fb21f181e664663c328ae@nifty.ne.jp>
In-Reply-To:	<YQv+rEqA8WiWdkVA@calimero.vinschen.de>
References:	<145999495 DOT 20210426124252 AT cfos DOT de>
	<1342428656 DOT 20210428072302 AT yandex DOT ru>
	<20210805191242 DOT b29a3904cbc4d082bdc3dd37 AT nifty DOT ne DOT jp>
	<YQv+rEqA8WiWdkVA AT calimero DOT vinschen DOT de>
X-Mailer:	Sylpheed 3.7.0 (GTK+ 2.24.30; i686-pc-mingw32)
Mime-Version:	1.0
X-Spam-Status:	No, score=-3.6 required=5.0 tests=BAYES_00, DKIM_SIGNED,
	DKIM_VALID, DKIM_VALID_AU, DKIM_VALID_EF, NICE_REPLY_A, RCVD_IN_DNSWL_NONE,
	RCVD_IN_MSPIKE_H2, SPF_HELO_NONE, SPF_PASS,
	TXREP autolearn=ham autolearn_force=no version=3.4.4
X-Spam-Checker-Version:	SpamAssassin 3.4.4 (2020-01-24) on
	server2.sourceware.org
X-BeenThere:	cygwin AT cygwin DOT com
X-Mailman-Version:	2.1.29
List-Id:	General Cygwin discussions and problem reports <cygwin.cygwin.com>
List-Unsubscribe:	<https://cygwin.com/mailman/options/cygwin>,
	<mailto:cygwin-request AT cygwin DOT com?subject=unsubscribe>
List-Archive:	<https://cygwin.com/pipermail/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-request AT cygwin DOT com?subject=help>
List-Subscribe:	<https://cygwin.com/mailman/listinfo/cygwin>,
	<mailto:cygwin-request AT cygwin DOT com?subject=subscribe>
From:	Takashi Yano via Cygwin <cygwin AT cygwin DOT com>
Reply-To:	Takashi Yano <takashi DOT yano AT nifty DOT ne DOT jp>
Errors-To:	cygwin-bounces+archive-cygwin=delorie DOT com AT cygwin DOT com
Sender:	"Cygwin" <cygwin-bounces+archive-cygwin=delorie DOT com AT cygwin DOT com>

Hi Corinna,

On Thu, 5 Aug 2021 17:07:24 +0200
Corinna Vinschen wrote:
> Could you perhaps bisect the issue on your machine?

In my environment, this does not happen with 8.4p1-1 and 8.4p1-2.
However it happens with 8.5p1-1.

> The fact that using Windows ssh is an issue makes me wonder if this is
> some kind of pty problem.

With command 'ssh user AT localhost ls', pty does not allocated.
It seems that this issue does not happen if -t option (allocate
tty) is specified. So I think this is not a pty problem.

In order to look into this problem, I tried to build openssh-8.5p1-1
from source, however it cause the error in configure stage:

...
checking for pkg-config... (cached) /usr/bin/pkg-config
checking if /usr/bin/pkg-config knows about libfido2... no
checking for fido_init in -lfido2... no
configure: error: no usable libfido2 found
*** ERROR: configure failed

despite libfido2-devel had been installed.

$ cygcheck -c libfido2-devel
Cygwin Package Information
Package              Version        Status
libfido2-devel       1.5.0-1        OK

How can I solve this error?

-- 
Takashi Yano <takashi DOT yano AT nifty DOT ne DOT jp>

-- 
Problem reports:      https://cygwin.com/problems.html
FAQ:                  https://cygwin.com/faq/
Documentation:        https://cygwin.com/docs.html
Unsubscribe info:     https://cygwin.com/ml/#unsubscribe-simple

- Raw text -