openssh unix dev - Jan 2023 - Upstream forwarding test failure

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.

On Wed, 25 Jan 2023 at 19:29, Darren Tucker <dtucker at dtucker.net>
wrote:
[...]
> 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
You can grab it from here:
https://github.com/daztucker/openssh-portable/commit/b54b39349e1a64cbbb9b56b0f8b91a35589fb528

It's not fully baked, but it should at least give you some more
insight into the case you are looking at:

$ make t-exec LTESTS=forwarding

and check the logs in regress/log (the oldest and newest are likely to
be the most interesting).

-- 
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.