> Dennis Clarke writes: >> Its a real mish mash of how do you want to proceed? You can keep the >> OpenSSH included in Solaris 10 but you can't get the high encryption > > Important nit here: Sun's SSH is Sun's SSH. It is *NOT* OpenSSH.
True .. its a derivitive. Still missing the aes256-cbc ciphers etc etc for various reasons. Mostly government export controls, not technical. > Though the source code itself was originally derived from OpenSSH, it > is not identical to any particular version or patch of OpenSSH, and it > has its own patch and support train. > > I suspect this is near the root of the original misunderstanding. > Sun's SSH is a separate product. Looking at OpenSSH for vulnerability > or patch information is not much more useful than looking at SSH, > Inc., or, for that matter, at Microsoft. > >> Personally I just use svcadm to disable the Sun shipped OpenSSH and >> then I go with the packages from Blastwave. Works like a charm. > > Unless, of course, you want auditing to work right or want support > from Sun. Auditing ? Please explain. Do you mean the entries in wtmpx etc etc ? As for Support ... gee ... get a support contract like I told you to. I have one ... he has one .. they have theirs. Do YOU ?? insert Uncle SAM poster here dc _______________________________________________ opensolaris-discuss mailing list [email protected]
