SEO

Has anyone else tried to install the latest sco-built openssh

on a pre-5.0.7 box?

I just installed it on 5.0.6, and after resolving a few issues with
the way prngd and sshd are started up on 5.0.7 (required changes to
/etc/tcp and /etc/default/tcp and /tcp/files/no_luid/cmdtable), prngd
and sshd start and stop from "tcp start|stop" as expected, except in
the end, I couldn't use it because when I tried to "ssh localhost" ssh
itself worked, in that it negotiated the initial
handshake/keys/password, but then login failed with a license error
from ifor_pmd.

WTF???

Just wondering if anyone else ever even tried that and got the same
error.
If no one has tried it, then I guess I'd like to bring it to everyones
attention and say to SCO that this rather blows if they did it on
purpose for some reason.

What are they gaining? I already have a self built copy of the exact
same version, with even greater functionality (chroot patch), which I
have had in reasonably heavy production use for some months so it's
even "proven" by now. Where do they come off hooking the licence
manager in to a completely free open-source program?

Even if it has to do with the fact that 5.0.7 is back to hard user
licence counts vs 5.0.6 soft counts, this 5.0.6 box isn't even using
it's base 5 users since it's just a backup box that I rsync over ssh
to once a night.

I only tried to use the sco-built version instead of mine because
generally I see that as the best way to avoid difficulty in the long
run whenever possible.

On the other hand, if someone has done it and had no problem, I'd
appreciate any comments on what they did.