openssh unix dev - Jan 2023 - Upstream forwarding test failure

Dear colleagues,

I came across an upstream test suite failure on Fedora 36.
The test in question is forwarding, the output is

=========adding
modulifile='/home/dbelyavs/work/upstream/openssh-portable/moduli' to
sshd_config
using cached key type ssh-ed25519
using cached key type sk-ssh-ed25519 at openssh.com
using cached key type ecdsa-sha2-nistp256
using cached key type ecdsa-sha2-nistp384
using cached key type ecdsa-sha2-nistp521
using cached key type sk-ecdsa-sha2-nistp256 at openssh.com
using cached key type ssh-dss
using cached key type ssh-rsa
wait for sshd
start forwarding, fork to background
transfer over forwarded channels and check result
exit on -L forward failure
connection not termintated, but should (0)
exit on -R forward failure
connection not termintated, but should (0)
simple clear forwarding
clear local forward
clear remote forward
stdio forwarding
config file: start forwarding, fork to background
config file: transfer over forwarded channels and check result
transfer over chained unix domain socket forwards and check result
wait for sshd to exit
failed local and remote forwarding
make[1]: *** [Makefile:224: t-exec] Error 1
make[1]: Leaving directory
'/home/dbelyavs/work/upstream/openssh-portable/regress'
make: *** [Makefile:724: t-exec] Error 2
=========
The test (especially built from upstream) shouldn't be affected by Fedora
cryptography limitations. Unfortunately I also can't get any clues from
regress/failed_ssh.log

Any help will be appreciated. Many thanks in advance!

-- 
Dmitry Belyavskiy

On Wed, 25 Jan 2023 at 01:38, Dmitry Belyavskiy <dbelyavs at redhat.com>
wrote:
[...]
> The test (especially built from upstream) shouldn't be affected by
Fedora
> cryptography limitations. Unfortunately I also can't get any clues from
> regress/failed_ssh.log
Unfortunately we don't do a good job with debug logging for the tests
where there's more than one ssh/sshd pair, and the forwarding tests
like this one are one example of that.

I have a part-done patch that logs the output from all ssh and sshd
instances to separate datestamped files.  I'll see if I can tidy that
up for you to try, but in the meantime check to see if there's
anything else listening in range of TEST_SSH_PORT (4242 by default)
and up.

-- 
Darren Tucker (dtucker at dtucker.net)
GPG key 11EAA6FA / A86E 3E07 5B19 5880 E860  37F4 9357 ECEF 11EA A6FA (new)
    Good judgement comes with experience. Unfortunately, the experience
usually comes from bad judgement.