Call for testing: OpenSSH 10.4

[Dmitry Belyavskiy]

Dear Damien,

On Sun, Jul 5, 2026 at 2:11 AM Damien Miller <djm at mindrot.org> wrote:

>
>
> On Sat, 4 Jul 2026, Felix Fehlauer wrote:
>
> > On 7/2/26 01:25, Damien Miller wrote:
> > > On Wed, 1 Jul 2026, Felix Fehlauer via openssh-unix-dev wrote:
> > >
> > [...]
> > >
> > > That might mean that something is already using port 3322 on your
> machine.
> > >
> > > Try changing the 'base=33' variable in regress/forwarding.sh to
> something
> > > else (e.g. try "94") and see if that helps.
> > >
> > > -d
> >
> > Sorry for the late reply.
> >
> > I cannot find anything running on port 3322, but indeed changing the
> base to
> > 94 makes the test pass.
> >
> > However, unless the tests are executed with the insecure LEGACY crypto
> policy,
> > they still fail with:
>
> Yes, we want to test rsa/sha1 if its available but Redhat doesn't seem to
> offer any clean way to detect it at runtme.
>
> Redhat's patch to sshd has it attempt an extra rsa/sha1 signature per
> connection because of a lack of a better way to do it. RSA signatures
> aren't super expensive, but this seems like a wasteful way to find out
> (effectively) whether a flag has been set.
>

> Is it really per-connection? I was sure it happens in the main sshd
process and then inherited by a child.

-- 
Dmitry Belyavskiy